Hi Mike,
Right. 5107.2, in order to preserve space for the important info
(interpreters
and MIME types), does NOT allow other keywords in a conformant string
(except for vendor proprietary ones on the right hand end of the string).
Of course, we're deprecating IEEE 1284 Device ID entirely in IPP, so this is
not the right place to hide serial number info.
Cheers,
- Ira
*Ira McDonald (Musician / Software Architect)*
*Chair - SAE Trust Anchors and Authentication TF*
*Co-Chair - TCG Trusted Mobility Solutions WG*
*Co-Chair - TCG Metadata Access Protocol SG*
*Chair - Linux Foundation Open Printing WGSecretary - IEEE-ISTO Printer
Working GroupCo-Chair - IEEE-ISTO PWG Internet Printing Protocol WGIETF
Designated Expert - IPP & Printer MIBBlue Roof Music / High North
Inchttp://sites.google.com/site/blueroofmusic
<http://sites.google.com/site/blueroofmusic>http://sites.google.com/site/highnorthinc
<http://sites.google.com/site/highnorthinc>mailto: blueroofmusic at gmail.com
<blueroofmusic at gmail.com>(permanent) PO Box 221 Grand Marais, MI 49839
906-494-2434*
On Tue, Dec 1, 2020 at 12:05 PM Michael Sweet <msweet at msweet.org> wrote:
> Ira,
>> I don't see any mention of SERIALNUMBER or SN in 5107.2 - I thought that
> just standardized the COMMAND SET or CMD values in the device ID?!?
>>> > On Dec 1, 2020, at 11:44 AM, Ira McDonald <blueroofmusic at gmail.com>
> wrote:
> >
> > Hi,
> >
> > Although IEEE 1284 Device ID does allow a keyword for a serial number,
> > the PWG 5107.2-2010 standard ABNF does NOT allow serial number in a
> > conformant Device ID string.
> >
> > May be in the wild, but not something relevant for IPP interoperability.
> >
> > Cheers,
> > - Ira
> >
> > Ira McDonald (Musician / Software Architect)
> > Chair - SAE Trust Anchors and Authentication TF
> > Co-Chair - TCG Trusted Mobility Solutions WG
> > Co-Chair - TCG Metadata Access Protocol SG
> > Chair - Linux Foundation Open Printing WG
> > Secretary - IEEE-ISTO Printer Working Group
> > Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
> > IETF Designated Expert - IPP & Printer MIB
> > Blue Roof Music / High North Inc
> > http://sites.google.com/site/blueroofmusic> > http://sites.google.com/site/highnorthinc> > mailto: blueroofmusic at gmail.com> > (permanent) PO Box 221 Grand Marais, MI 49839 906-494-2434
> >
> >
> > On Tue, Dec 1, 2020 at 10:30 AM Michael Sweet via ipp <ipp at pwg.org>
> wrote:
> > Smith,
> >
> > > On Dec 1, 2020, at 8:59 AM, Kennedy, Smith (Wireless & IPP Standards) <
>smith.kennedy at hp.com> wrote:
> > >
> > > Hi Mike,
> > >
> > > No objections to adding this but a few thoughts:
> > >
> > > - PII concerns?
> >
> > Not directly - this identifies the printer, not an individual. If the
> value was propagated outside of IPP with other personal information it
> might be used to identify someone ("Mike" printed to a printer with serial
> number 12345678, it must be Mike Sweet and not Mike Jones). But this is
> purely informational from the Printer to the Client, for
> maintenance/support purposes.
> >
> > > - Overlap with the key/value pairs provided by "printer-device-id" -
> the "SN" key isn't standardized but is out there...
> >
> > Last time I checked (but I no longer have a copy...) IEEE-1284 defines
> SERIALNUMBER (official abbreviation SN, also SER and SERN in the wild) to
> hold this. But "printer-device-id" isn't something we want in the long
> term (only needed for drivers) and implementation of the serial number in
> the device ID is spotty at best...
> >
> > ________________________
> > Michael Sweet
> >
> >
> >
> > _______________________________________________
> > ipp mailing list
> > ipp at pwg.org> > https://www.pwg.org/mailman/listinfo/ipp>> ________________________
> Michael Sweet
>>>>-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20201201/a2cccef1/attachment.html>