attachment
<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi there,<br class=""><div class="">
<div><br class=""></div><div>Going to return to the "main thread" ("printer-serial-number") in a second reply. But on the subject of "printer-device-id"...</div><div><br class=""><blockquote type="cite" class=""><div class="">On Dec 1, 2020, at 10:13 AM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com" class="">blueroofmusic@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div dir="ltr" class=""><div class="">Hi Mike,</div><div class=""><br class=""></div><div class="">Right. 5107.2, in order to preserve space for the important info (interpreters</div><div class="">and MIME types), does NOT allow other keywords in a conformant string</div><div class="">(except for vendor proprietary ones on the right hand end of the string).</div></div></div></blockquote><div><br class=""></div>We all seem to agree that the scope of 5107.2 is limited to the values specified for the "COMMAND SET" or "CMD" Device ID capability key, It makes no assertions about any of the other capability keys, whether standard ("MFG" / "MANUFACTURER", "MDL" / "MODEL") or otherwise.</div><div><br class=""></div><div>The "SN" is a separate capability key e.g. "MFG:PWG;MDL:Fake Printer;CMD:image/pwg-raster;SN:12345678;"</div><div><br class=""></div><div>I think the PWG's perspective ought to be that vendors SHOULD NOT put PII in this or any IPP attributes that don't require authentication. Our "IPP Privacy Attributes v1.0 (PRIVACY)" doesn't seem to look at PII in the Printer itself, more of a focus on Job and Document PII?</div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class="">Of course, we're deprecating IEEE 1284 Device ID entirely in IPP, so this is</div><div class="">not the right place to hide serial number info.</div></div></div></blockquote><div><br class=""></div>The IANA IPP Registry doesn't show it to be deprecated currently. I don't have any objections to deprecating it, but I am aware of some driver systems that are using IPP as a replacement for SNMP, but they still depend on 1284 Device ID for driver matching, and taking this away from them would cause them to look elsewhere. Then again, we are deprecating, not obsoleting, so it is still "around".</div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class="">Cheers,<br class=""></div><div class="">- Ira<br class=""></div><div class=""><div class=""><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><i class=""><font size="1" class="">Ira McDonald (Musician / Software Architect)</font></i></div><div class=""><i class=""><font size="1" class="">Chair - SAE Trust Anchors and Authentication TF<br class=""></font></i></div><div dir="ltr" class=""><i class=""><font size="1" class="">Co-Chair - TCG Trusted Mobility Solutions WG</font></i></div><div class=""><i class=""><font size="1" class="">Co-Chair - TCG Metadata Access Protocol SG<br class=""></font></i></div><div dir="ltr" class=""><i class=""><font size="1" class="">Chair - Linux Foundation Open Printing WG<br class="">Secretary - IEEE-ISTO Printer Working Group<br class="">Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br class="">IETF Designated Expert - IPP & Printer MIB<br class="">Blue Roof Music / High North Inc<br class=""><a style="color:rgb(51,51,255)" href="http://sites.google.com/site/blueroofmusic" target="_blank" class="">http://sites.google.com/site/blueroofmusic</a><br class=""><a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" target="_blank" class="">http://sites.google.com/site/highnorthinc</a><br class="">mailto: <a href="mailto:blueroofmusic@gmail.com" target="_blank" class="">blueroofmusic@gmail.com</a><br class="">(permanent) PO Box 221 Grand Marais, MI 49839 906-494-2434</font></i></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div><br class=""></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Dec 1, 2020 at 12:05 PM Michael Sweet <<a href="mailto:msweet@msweet.org" class="">msweet@msweet.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Ira,<br class="">
<br class="">
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?!?<br class="">
<br class="">
<br class="">
> On Dec 1, 2020, at 11:44 AM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com" target="_blank" class="">blueroofmusic@gmail.com</a>> wrote:<br class="">
> <br class="">
> Hi,<br class="">
> <br class="">
> Although IEEE 1284 Device ID does allow a keyword for a serial number,<br class="">
> the PWG 5107.2-2010 standard ABNF does NOT allow serial number in a<br class="">
> conformant Device ID string.<br class="">
> <br class="">
> May be in the wild, but not something relevant for IPP interoperability.<br class="">
> <br class="">
> Cheers,<br class="">
> - Ira<br class="">
> <br class="">
> Ira McDonald (Musician / Software Architect)<br class="">
> Chair - SAE Trust Anchors and Authentication TF<br class="">
> Co-Chair - TCG Trusted Mobility Solutions WG<br class="">
> Co-Chair - TCG Metadata Access Protocol SG<br class="">
> Chair - Linux Foundation Open Printing WG<br class="">
> Secretary - IEEE-ISTO Printer Working Group<br class="">
> Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br class="">
> IETF Designated Expert - IPP & Printer MIB<br class="">
> Blue Roof Music / High North Inc<br class="">
> <a href="http://sites.google.com/site/blueroofmusic" rel="noreferrer" target="_blank" class="">http://sites.google.com/site/blueroofmusic</a><br class="">
> <a href="http://sites.google.com/site/highnorthinc" rel="noreferrer" target="_blank" class="">http://sites.google.com/site/highnorthinc</a><br class="">
> mailto: <a href="mailto:blueroofmusic@gmail.com" target="_blank" class="">blueroofmusic@gmail.com</a><br class="">
> (permanent) PO Box 221 Grand Marais, MI 49839 906-494-2434<br class="">
> <br class="">
> <br class="">
> On Tue, Dec 1, 2020 at 10:30 AM Michael Sweet via ipp <<a href="mailto:ipp@pwg.org" target="_blank" class="">ipp@pwg.org</a>> wrote:<br class="">
> Smith,<br class="">
> <br class="">
> > On Dec 1, 2020, at 8:59 AM, Kennedy, Smith (Wireless & IPP Standards) <<a href="mailto:smith.kennedy@hp.com" target="_blank" class="">smith.kennedy@hp.com</a>> wrote:<br class="">
> ><br class="">
> > Hi Mike,<br class="">
> ><br class="">
> > No objections to adding this but a few thoughts:<br class="">
> ><br class="">
> > - PII concerns?<br class="">
> <br class="">
> 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.<br class="">
> <br class="">
> > - Overlap with the key/value pairs provided by "printer-device-id" - the "SN" key isn't standardized but is out there...<br class="">
> <br class="">
> 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...<br class="">
> <br class="">
> ________________________<br class="">
> Michael Sweet<br class="">
> <br class="">
> <br class="">
> <br class="">
> _______________________________________________<br class="">
> ipp mailing list<br class="">
> <a href="mailto:ipp@pwg.org" target="_blank" class="">ipp@pwg.org</a><br class="">
> <a href="https://www.pwg.org/mailman/listinfo/ipp" rel="noreferrer" target="_blank" class="">https://www.pwg.org/mailman/listinfo/ipp</a><br class="">
<br class="">
________________________<br class="">
Michael Sweet<br class="">
<br class="">
<br class="">
<br class="">
</blockquote></div>
</div></blockquote></div><br class=""></div></body></html>