attachment
<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Ira,<div><br></div><div>RFC 3510 already says this in section 4.6.2:</div><div><br></div><div><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always;"> IPP Printers that conform to this specification SHOULD only generate
IPP Job URLs (for example, in the "job-uri" attribute in a 'Print-
Job' response) by appending exactly one path component to the
corresponding IPP Printer URL (for interoperability).
</pre></div><div><br></div><div><br></div><div><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always;">Of the manufacturers that are currently represented in my home office, I see the following kinds of job URIs:</pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always;"><br></pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always;"> 1. <a href="ipp://host.example.com/ipp/print/job-0123">ipp://host.example.com/ipp/print/job-0123</a> [zero-filled to 4 digits]</pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always;"> 2. <a href="ipp://host.example.com/ipp/print/job-123">ipp://host.example.com/ipp/print/job-123</a> [no zero-fill]</pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always;"><span style="font-size: 1em;"> 3. <a href="ipp://host.example.com/ipp/print/job123">ipp://host.example.com/ipp/print/job123</a> [no hyphen]</span></pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always;"><span style="font-size: 1em;"> 4. <a href="ipp://host.example.com/ipp/print/123">ipp://host.example.com/ipp/print/123</a> [no "job" prefix]</span></pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always;"> 4. <a href="ipp://host.example.com/jobs/123">ipp://host.example.com/jobs/123</a> [different path prefix]</pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always;"><br></pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always;">Only the last format is unambiguous (and is in fact the format that CUPS uses). The others *could* be used, but only if we prohibited printer-uri values of the same form, i.e., implementations would need to add a leading underscore or something to the printer URI to avoid confusion...</pre></div><div><br></div><div>We could use a query string instead of a path component to make it unambiguous, e.g.:</div><div><br></div><div> <a href="ipp://host.example.com/ipp/print?job-id=123">ipp://host.example.com/ipp/print?job-id=123</a></div><div><br></div><div>However, RFC 3510 says the following:</div><div><br></div><div><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always;"> Historical Note: During the development of this document,
consideration was given to the addition of standard IPP URL
parameters for the client authentication and security mechanisms.
However, based on a strong IETF IPP Working Group consensus, no
parameters were added to the "ipp" URL scheme as originally defined
in IPP Protocol [<a href="http://tools.ietf.org/html/rfc2910" title=""IPP/1.1 Encoding and Transport [IPP Protocol]"">RFC2910</a>] in September 2000, for reasons of backwards
compatibility with the many currently shipping implementations of
IPP/1.1.
</pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always;"><br></pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always;">I don't know whether this statement is valid these days, or what shipping implementations had problems with query strings/parameters.</pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always;"><br></pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always;">Another option is to deprecate the "job-uri" attribute entirely. I can remember being "shouted down" during the development of notifications when I asked whether we wanted a notify-subscription-uri attribute - "job-uri's are vile things and we don't want to make the same mistake twice" (or something along those lines).</pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always;"><br></pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always;">Thoughts?</pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always;"><br></pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always;"><br></pre></div><div><div><div>On Aug 6, 2014, at 4:27 PM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div><div><div><div><div><div>Hi Pete,<br><br>+1.<br><br></div>I *could* add this as a SHOULD in the IETF "ipps:" URI Scheme draft<br></div><div>for print services (and reference IPP FaxOut and IPP Scan for the other<br>
</div><div>service paths?).<br><br></div>It can't be a MUST, because it would break deployed usage with CUPS<br></div>of "ipps:" (since administrators won't have observed all any convention).<br><br></div>
<div>I would also like to add guidance (with SHOULD) in the "ipps:" URI Scheme<br></div><div>for Job URI values (e.g., derived from the print queue's URI by adding exactly <br>one component which SHOULD include the integer "job-id" value as a string).<br>
<br></div><div>Remembering that, when it's finally published, the "ipps:" RFC will have high<br></div><div>visibility for implementors.<br></div><div><br>Opinions?<br></div></div><br>Cheers,<br></div>- Ira<br>
<br></div><div class="gmail_extra"><br clear="all"><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>
Winter 579 Park Place Saline, MI 48176 734-944-0094<br>Summer 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>
<br><br><div class="gmail_quote">On Wed, Aug 6, 2014 at 3:51 PM, 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">+1.<div><br></div><div>We can add it to section 7.1 (service URIs)</div><div><br></div><div><br></div><div><div><div class=""><div>On Aug 6, 2014, at 3:43 PM, Zehler, Peter <<a href="mailto:Peter.Zehler@xerox.com" target="_blank">Peter.Zehler@xerox.com</a>> wrote:</div>
<br></div><blockquote type="cite">
<div link="blue" vlink="purple" lang="EN-US">
<div><div class=""><p class="MsoNormal">All,<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Given that IPP FaxOut and IPP Scan have set requirements on the path components of the service’s URL perhaps the new implementers guide can do the same for print (e.g. “ipp/print”). I would hope going forward any additional service mappings
will have similar path component requirements.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">The requirement in scan is<u></u><u></u></p><p class="MsoNormal">“Each instance of a Scan Service is identified by a URI. The path component of an IPP Scan URI MUST be “/ipp/scan” for the only (or default) instance of the service on an Imaging Device and “/ipp/scan/instance-name” for each additional,
non-default instance on the Imaging Device.”<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p></div><p class="MsoNormal"><span style="font-family:"Impact","sans-serif";color:navy">Peter Zehler</span><span style="color:#1f497d"><br>
<br>
</span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy"><span><image001.png></span><br>
</span></p><div class=""><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">Email:
</span><a href="mailto:Peter.Zehler@Xerox.com" target="_blank"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:blue">Peter.Zehler@Xerox.com</span></a><span style="color:#1f497d"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">Office: <a href="tel:%2B1%20%28585%29%20265-8755" value="+15852658755" target="_blank">+1 (585) 265-8755</a><u></u><u></u></span></div><div><br class="webkit-block-placeholder"></div><div class=""><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">Mobile: <a href="tel:%2B1%20%28585%29%20329-9508" value="+15853299508" target="_blank">+1 (585) 329-9508</a></span><span style="color:#1f497d"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">FAX: <a href="tel:%2B1%20%28585%29%20265-7441" value="+15852657441" target="_blank">+1 (585) 265-7441</a></span><span style="color:#1f497d"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">US Mail: Peter Zehler</span><span style="color:#1f497d"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">PARC, A Xerox Company</span><span style="color:#1f497d"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">800 Phillips Rd.</span><span style="color:#1f497d"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">M/S 128-27E</span><span style="color:#1f497d"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">Webster NY, 14580-9701</span><span style="color:#1f497d">
</span><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:#1f497d"><u></u><u></u></span></p><p class="MsoNormal"><u></u> <u></u></p>
</div></div>
</div>
_______________________________________________<br>ipp mailing list<br><a href="mailto:ipp@pwg.org" target="_blank">ipp@pwg.org</a><br><a href="https://www.pwg.org/mailman/listinfo/ipp" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br>
</blockquote></div><br><div>
<span style="border-collapse: separate; 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;"><span style="border-collapse: separate; 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;"><div style="word-wrap:break-word">
_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair</div></span></span>
</div>
<br></div></div><br>_______________________________________________<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" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; font-family: 'Andale Mono'; border-spacing: 0px;"><span class="Apple-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; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair</div></span></span>
</div>
<br></div></body></html>