attachment
<div dir="ltr"><div><div>Hi,<br><br></div>+1 to Mike's comment. Make it declarative ("is") rather than normative.</div><div>If filtering wasn't performed, then this new operation would be useless.</div><div><br></div><div>Cheers,</div><div>- Ira</div><div><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr">Ira McDonald (Musician / Software Architect)<br>Co-Chair - TCG Trusted Mobility Solutions WG<br>Chair - Linux Foundation Open Printing WG<br>Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music / High North Inc<br><a style="color:rgb(51,51,255)" href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br><a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</a><br>mailto: <a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>Jan-April: 579 Park Place Saline, MI 48176 734-944-0094<br>May-Dec: PO Box 221 Grand Marais, MI 49839 906-494-2434<br><br><div style="display:inline"></div><div style="display:inline"></div><div style="display:inline"></div><div></div><div></div><div></div><div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Tue, Nov 7, 2017 at 10:21 AM, Michael Sweet <span dir="ltr"><<a href="mailto:msweet@apple.com" target="_blank">msweet@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space">Smith,<div><br></div><div>I don't see how we can validate conformance for this MUST, particularly when the default (open) policy will return the same attributes and values as Get-Printer-Attributes. I suggest we simply declare the intended behavior:</div><div><br></div><div> "... the response is filtered based on the most authenticated user."</div><div><div class="h5"><div><br></div><div><br></div><div><div><blockquote type="cite"><div>On Nov 6, 2017, at 11:56 PM, Kennedy, Smith (Wireless Architect) <<a href="mailto:smith.kennedy@hp.com" target="_blank">smith.kennedy@hp.com</a>> wrote:</div><br class="m_-3497582364322691676Apple-interchange-newline"><div><div style="word-wrap:break-word;line-break:after-white-space">Ah, good catch. I suggest we replace "can" with "shall" in that first paragraph:<div><br></div><div><blockquote style="font-family:LucidaGrande;margin:0px 0px 0px 40px;border:none;padding:0px"><div><div style="font-size:14px"><b>4 Get-User-Printer-Attributes Operation</b></div><div>The Get-User-Printer-Attributes operation is semantically analogous to the Get-Printer-Attributes operation [RFC8011] but the response MUST be filtered based on the most authenticated user. The authenticated user (see section 9.3 of [RFC8011]) performing this operation MUST be either a User permitted to create Print Jobs or an Operator or Administrator of the Printer. Otherwise, the Printer MUST reject the operation and return 'client-error-forbidden', 'client-error-not-<wbr>authenticated', or 'client-error-not-authorized' as appropriate.</div><div><br></div><div>The Client MUST be prepared to handle an HTTP authentication challenge in response to a Get-User-Printer-Attributes operation request. If the Client initiates the Get-User-Printer-Attributes operation over a non-TLS connection, the Client MUST be prepared to receive an HTTP 426 response to upgrade the connection to TLS [RFC2817]. See [RFC8010] and [RFC8011] for authentication methods that require a secure channel.</div><div><br></div><div>A Printer MUST support all the same operation attributes for a Get-User-Printer-Attributes operation that it supports with a Get-Printer-Attributes operation, including those a Client can use to request a filtered response: “document-format” [RFC8011]; “first-index” [PWG5100.13]; “limit” [PWG5100.13]; and any of the attributes named by “printer-get-attributes-<wbr>supported” [PWG5100.13].</div><div><br></div></div></blockquote></div><div><br></div><div><br><div><br>
<div><br><blockquote type="cite"><div>On Nov 6, 2017, at 9:16 PM, <a href="mailto:wamwagner@comcast.net" target="_blank">wamwagner@comcast.net</a> wrote:</div><br class="m_-3497582364322691676Apple-interchange-newline"><div><div class="m_-3497582364322691676WordSection1" style="font-family:LucidaGrande;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Looks good…except I am trying to remember why we weasleword and say that the response “can” be filtered, whereas we use standard compliance terms elsewhere. I vaguely recall this being discussed, but the implication is that a printer could respond without filtering. If that were the intent, I expect that we would use ‘MAY’.</div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Thanks, Bill Wagner</div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div><div style="border-style:solid none none;border-top-width:1pt;border-top-color:rgb(225,225,225);padding:3pt 0in 0in"><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif;border:none;padding:0in"><b>From:<span class="m_-3497582364322691676Apple-converted-space"> </span></b><a href="mailto:smith.kennedy@hp.com" style="color:rgb(149,79,114);text-decoration:underline" target="_blank">Kennedy, Smith (Wireless Architect)</a><br><b>Sent:<span class="m_-3497582364322691676Apple-converted-space"> </span></b>Monday, November 6, 2017 6:26 PM<br><b>To:<span class="m_-3497582364322691676Apple-converted-space"> </span></b><a href="mailto:msweet@apple.com" style="color:rgb(149,79,114);text-decoration:underline" target="_blank">Michael Sweet</a><br><b>Cc:<span class="m_-3497582364322691676Apple-converted-space"> </span></b><a href="mailto:wamwagner@comcast.net" style="color:rgb(149,79,114);text-decoration:underline" target="_blank">William A Wagner</a>;<span class="m_-3497582364322691676Apple-converted-space"> </span><a href="mailto:ipp@pwg.org" style="color:rgb(149,79,114);text-decoration:underline" target="_blank">PWG IPP WG Reflector</a><br><b>Subject:<span class="m_-3497582364322691676Apple-converted-space"> </span></b>Re: [IPP] Updated stable draft of IPP Get-User-Printer-<wbr>Attributesisnow available for review</div></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">How about this for an update to section 4:<u></u><u></u></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div></div><blockquote style="margin-left:30pt;margin-right:0in"><div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><b><span style="font-size:10.5pt">4 Get-User-Printer-Attributes Operation</span></b><span style="font-size:10.5pt"><u></u><u></u></span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">The Get-User-Printer-Attributes operation is semantically analogous to the Get-Printer-Attributes operation [RFC8011] but the response can be filtered based on the most authenticated user. The authenticated user (see section 9.3 of [RFC8011]) performing this operation MUST be either a User permitted to create Print Jobs or an Operator or Administrator of the Printer. Otherwise, the Printer MUST reject the operation and return 'client-error-forbidden', 'client-error-not-<wbr>authenticated', or 'client-error-not-authorized' as appropriate.<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">The Client MUST be prepared to handle an HTTP authentication challenge in response to a Get-User-Printer-Attributes operation request. If the Client initiates the Get-User-Printer-Attributes operation over a non-TLS connection, the Client MUST be prepared to receive an HTTP 426 response to upgrade the connection to TLS [RFC2817]. See [RFC8010] and [RFC8011] for authentication methods that require a secure channel.<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">A Printer MUST support all the same operation attributes for a Get-User-Printer-Attributes operation that it supports with a Get-Printer-Attributes operation, including those used by a Client to request a filtered response: “document-format” [RFC8011]; “first-index” [PWG5100.13]; “limit” [PWG5100.13]; and any of the attributes named by “printer-get-attributes-<wbr>supported” [PWG5100.13].<u></u><u></u></div></div></div></blockquote><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div><div><p class="MsoNormal" style="margin:0in 0in 12pt;font-size:11pt;font-family:Calibri,sans-serif">Smith<br><br><u></u><u></u></p></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><br><br><u></u><u></u></div><blockquote style="margin-top:5pt;margin-bottom:5pt"><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">On Nov 6, 2017, at 2:49 PM, Michael Sweet <<a href="mailto:msweet@apple.com" style="color:rgb(149,79,114);text-decoration:underline" target="_blank">msweet@apple.com</a>> wrote:<u></u><u></u></div></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div><div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Smith/Bill,<u></u><u></u></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Perhaps we can use something in section 4 like the following:<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div></div><blockquote style="margin-left:30pt;margin-right:0in"><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Access Rights: The authenticated user (see section 9.3 of [RFC8011]) performing this operation must be either a User permitted to create Print Jobs or an Operator or Administrator of the Printer. Otherwise, the Printer MUST reject the operation and return 'client-error-forbidden', 'client-error-not-<wbr>authenticated', or 'client-error-not-authorized' as appropriate.<u></u><u></u></div></div></blockquote><div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">That mirrors the wording from other operations defined in RFC 8011 and other places and makes it clear that the operation is provided for Users that want to print.<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Thoughts?<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">(As for the format debate, I always have used the PDF versions for review because Word does not preserve the layout of text - local fonts and margins for your last used printer will mess things up every time...)<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><br><br><u></u><u></u></div><blockquote style="margin-top:5pt;margin-bottom:5pt"><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">On Nov 6, 2017, at 4:08 PM,<span class="m_-3497582364322691676Apple-converted-space"> </span><a href="mailto:wamwagner@comcast.net" style="color:rgb(149,79,114);text-decoration:underline" target="_blank">wamwagner@comcast.net</a><span class="m_-3497582364322691676Apple-converted-space"> </span>wrot<wbr>e:<u></u><u></u></div></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div><div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Hi Smith,<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">A few comments:<u></u><u></u></div></div><ol start="1" style="margin-bottom:0in;margin-top:0in" type="1"><li class="MsoNormal" style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Although the standard compliance terms are used, (MUST, SHOULD, etc.) Section 2 does not include the standard reference defining these terms.<u></u><u></u></li><li class="MsoNormal" style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Section 4 line 150 (in the non-redline pdf): “… Attributes operation [RFC8011] but can be authenticated …” suggests that the operation is authenticated, which I don’t think is a typical way of indicating that the operation may prompt a sequence to authenticate the user. Prehaps rewording to “ … Attributes operation [RFC8011] except that the response can be filtered based on the most authenticated user and to effect this, the operation can prompt a sequence to authenticate the user.” Or something like that.<u></u><u></u></li></ol><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"> <u></u><u></u></div></div><div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">On a more general topic, for whatever reason, the PWG has typically provided drafts in MS Word and PDF formats. The ‘odt’ format is not compatible with , at least, my version of MS Word to the extent that opening it in MS Word produces a incorrectly displayed document subject to extensive editorial comments. The Process states “ Internal working versions of PWG documents should be available in an agreed upon, widely available word processing format, to provide for collaboration between document editors and contributors. For example, Microsoft WORD and HTML are common<span class="m_-3497582364322691676apple-converted-space"> </span><u></u><u></u></div></div></div><div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">revisable formats in use, today. “ For those not familiar with your use of Open Office, perhaps it would be better to include a note in your draft announcements that the .odt extension files should be viewed with Apache Open Office, not MS Word.<u></u><u></u></div></div></div><div style="margin-left:0.5in"><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"> <u></u><u></u></div></div><div style="margin-left:0.5in"><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Thanks, Bill Wagner<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"> <u></u><u></u></div></div><div><div><div><div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"> <u></u><u></u></div></div></div></div></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"> <u></u><u></u></div></div><div style="border-style:solid none none;border-top-width:1pt;border-top-color:rgb(225,225,225);padding:3pt 0in 0in"><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><b>From:<span class="m_-3497582364322691676apple-converted-space"> </span></b><a href="mailto:smith.kennedy@hp.com" style="color:rgb(149,79,114);text-decoration:underline" target="_blank"><span style="color:rgb(149,79,114)">Kennedy, Smith (Wireless Architect)</span></a><br><b>Sent:<span class="m_-3497582364322691676apple-converted-space"> </span></b>Saturday, November 4, 2017 12:44 AM<br><b>To:<span class="m_-3497582364322691676apple-converted-space"> </span></b><a href="mailto:ipp@pwg.org" style="color:rgb(149,79,114);text-decoration:underline" target="_blank"><span style="color:rgb(149,79,114)">PWG IPP WG Reflector</span></a><br><b>Subject:<span class="m_-3497582364322691676apple-converted-space"> </span></b>[IPP] Updated stable draft of IPP Get-User-Printer-Attributes isnow available for review<u></u><u></u></div></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"> <u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Greetings,<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"> <u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">An updated stable draft of IPP Get-User-Printer-Attributes is now available for review:<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"> <u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><a href="https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippgupa-20171103.pdf" style="color:rgb(149,79,114);text-decoration:underline" target="_blank">https://ftp.pwg.org/pub/pwg/<wbr>ipp/wd/wd-ippgupa-20171103.pdf</a><u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><a href="https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippgupa-20171103.odt" style="color:rgb(149,79,114);text-decoration:underline" target="_blank">https://ftp.pwg.org/pub/pwg/<wbr>ipp/wd/wd-ippgupa-20171103.odt</a><u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><a href="https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippgupa-20171103-rev.pdf" style="color:rgb(149,79,114);text-decoration:underline" target="_blank">https://ftp.pwg.org/pub/pwg/<wbr>ipp/wd/wd-ippgupa-20171103-<wbr>rev.pdf</a><u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><a href="https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippgupa-20171103-rev.odt" style="color:rgb(149,79,114);text-decoration:underline" target="_blank">https://ftp.pwg.org/pub/pwg/<wbr>ipp/wd/wd-ippgupa-20171103-<wbr>rev.odt</a><u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"> <u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Changes are minor:<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">* Fixed a broken bookmark cross reference in section 3.1<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">* Fixed a few instances of passive voice<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">* Some other editorial fixes<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"> <u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Cheers,<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Smith<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"> <u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">/**<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"> <span class="m_-3497582364322691676apple-converted-space"> </span>Smith Kennedy<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"> <span class="m_-3497582364322691676apple-converted-space"> </span>Wireless & Standards Architect - IPG-PPS<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"> <span class="m_-3497582364322691676apple-converted-space"> </span>Standards - IEEE ISTO PWG / Bluetooth SIG / Wi-Fi Alliance / NFC Forum / USB-IF<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"> <span class="m_-3497582364322691676apple-converted-space"> </span>Chair, IEEE ISTO Printer Working Group<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"> <span class="m_-3497582364322691676apple-converted-space"> </span>HP Inc.<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">*/<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"> <u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"> <u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"> <u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"> <u></u><u></u></div></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:8.5pt;font-family:Menlo-Regular,serif">______________________________<wbr>_________________<br>ipp mailing list<br><a href="mailto:ipp@pwg.org" style="color:rgb(149,79,114);text-decoration:underline" target="_blank">ipp@pwg.org</a><br><a href="https://www.pwg.org/mailman/listinfo/ipp" style="color:rgb(149,79,114);text-decoration:underline" target="_blank">https://www.pwg.org/mailman/<wbr>listinfo/ipp</a></span><u></u><u></u></div></div></blockquote></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div><div><div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-family:"Andale Mono",serif">______________________________<wbr>___________________________<br>Michael Sweet, Senior Printing System Engineer</span></div></div></div></div></div></div></div></blockquote></div></div></div></div></blockquote></div><br></div></div></div></div></blockquote></div><br><div>
<span class="m_-3497582364322691676Apple-style-span" style="border-collapse:separate;color:rgb(0,0,0);font-family:'Andale Mono';font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;border-spacing:0px"><div style="word-wrap:break-word"><span class="m_-3497582364322691676Apple-style-span" style="border-collapse:separate;color:rgb(0,0,0);font-family:'Andale Mono';font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;border-spacing:0px"><div style="word-wrap:break-word">______________________________<wbr>___________________________<br>Michael Sweet, Senior Printing System Engineer</div></span></div></span>
</div>
<br></div></div></div></div><br>______________________________<wbr>_________________<br>
ipp mailing list<br>
<a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>
<a href="https://www.pwg.org/mailman/listinfo/ipp" rel="noreferrer" target="_blank">https://www.pwg.org/mailman/<wbr>listinfo/ipp</a><br>
<br></blockquote></div><br></div>