attachment-0001
<br clear="all">Hi,<br><br>I've just posted another Internet-Draft of IPP over HTTP Transport Binding and<br>'<span><span class="il">ipps</span></span>'<span></span> <span>URI</span> Scheme to:<br>
<br>
<a href="ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-04-20111122.txt" target="_blank">ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-04-20111122.txt</a><br>
- plaintext Internet-Draft format (warning - contains explicit formfeed characters)<br>
<br>
<a href="ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-04-20111122.pdf" target="_blank">ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-04-20111122.pdf</a><br>
- PDF of plaintext w/ line numbers (review *this* one)<br><br>
<a href="ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-04-20111122.htm" target="_blank">ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-04-20111122.htm</a><br>
- HTML format<br><br>This document has already been accepted and posted to the IETF I-D repository.<br>
<br>
This document was created by a complete rewrite IPP <span>URI</span> Scheme
[RFC3510].<br><br>This version has numerous editorial changes from our complete review during <br>the IPP WG call on 19 August - see Change History below.<br><br>
Comments?<br><br>Cheers,<br>- Ira<br><br>------------------------------------<br>Change History<br><br> 22 November 2011 - draft-mcdonald-ipps-uri-scheme-04.txt <br><br> Editorial - Global - Fixed typos and indentation, per IPP WG review.<br>
<br> Editorial - Revised Introduction and Acknowledgments to say 'project<br> for mobile, ubiquitous printing with generic drivers', per IPP WG<br> review. <br><br> Editorial - Revised sections 3.1 and 3.2 (transport bindings) to add <br>
references to HTTP POST and section 4 of RFC 2910, per IPP WG<br> review. <br><br> Editorial - Revised sections 3.1 and 3.2 (transport bindings) to add <br> section references to all well-known standards (connection setup,<br>
etc.), per IPP WG review. <br><br> Editorial - Revised section 4.2 (syntax) to move note from from<br> section 4.6 (examples) and explain why literal IP addresses should<br> NOT be used in 'ipps' URI, per IPP WG review. <br>
<br> Editorial - Revised sections 4.6.1 and 4.6.2 (examples) to replace<br> '<a href="http://abc.com">abc.com</a>' w/ '<a href="http://example.com">example.com</a>' (per IETF) and replace '/printer' path<br>
element w/ '/ipp' (better practice), per IPP WG review. <br><br> Editorial - Revised section 5.2 (Printer conformance) to fold former<br> (c) and (d) into a single requirement for standard port 631 and<br>
reordered other requirements to group MUSTs before SHOULDs, per IPP<br> WG review. <br><br> Editorial - Revised section 5.2 (Printer conformance) to add backward<br> reference to section 4.2 for rationale for not using IP literal<br>
addresses, per IPP WG review. <br><br> Editorial - Revised section 6 (IANA) to explicitly state that 'ipps' <br> uses secure communications using HTTP over TLS, per IPP WG review.<br><br> Editorial - Revised section 7 (Security) to cleanup numerous loose<br>
ends, per IPP WG review. <br><br> Editorial - Revised section 8 (References) to cleanup typos and<br> links, per IPP WG review. <br><div style="display:inline"></div><div style="display:inline"></div><div style="display:inline">
</div><div></div><div></div><div></div><div></div><br>
<div style="visibility: hidden; left: -5000px;" id="avg_ls_inline_popup"></div>
<br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.