attachment
<div dir="ltr">Hi,<br><br>I've just <span>posted</span> another Internet-<span>Draft</span> of <span><span><span>IPP</span></span></span> over HTTPS Transport Binding and<br>'<span><span><span><span><span><span><span>ipps</span></span></span></span></span></span></span>'<span></span> <span><span><span><span><span><span><span>URI</span></span></span></span></span></span></span> <span>Scheme</span> to:<br>
<br>
<a href="ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-15-20141027.txt" target="_blank">ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-15-20141027.txt</a><br>
- plaintext Internet-<span>Draft</span> format (warning - contains explicit formfeed characters)<br>
<br>
<a href="ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-15-20141027.pdf" target="_blank">ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-15-20141027.pdf</a><br>
- PDF of plaintext w/ line numbers (review *this* one)<br><br>
This document has already been accepted and <span>posted</span> to the IETF I-D repository.<br><br></div><div>This document is parallel to, but does not update or obsolete, RFC 3510.<br><br>
This version has many *minor* editorial changes since the previous version<br>and is based on requests from S. Mooneswamy (IETF reviewer), Barry Leiba<br>(IETF Apps AD), and IEEE-ISTO PWG IPP WG review.<br>
</div><br>
Comments?<br><br>Cheers,<br>- Ira<br><br>--------------------------------<br><div dir="ltr"><div dir="ltr"><br><div><div dir="ltr">Change History</div></div></div></div><div><div dir="ltr"><br> 27 October 2014 - draft-mcdonald-ipps-uri-scheme-15.txt <br><br> Editorial - Kept "Intended Status" as "Standards Track", with AD<br> sponsoring, per advice of Barry Leiba on 22 October 2014. <br><br> Editorial - Revised Abstract to delete mention of submission from<br> PWG, per advice of S. Mooneswamy on 13 October 2014 and Barry Leiba<br> on 22 October 2014. <br><br> Editorial - Revised Boilerplate to reflect IETF standards-track, per<br> advice of Barry Leiba on 22 October 2014. <br><br> Editorial - Revised Introduction and Acknowledgments to say "This<br> document has been submitted to IETF...", per advice of Barry Leiba on<br> 22 October 2014. <br><br> Editorial - Replaced "this memo" with "this document", per advice of<br> S. Mooneswamy on 13 October 2014 and Barry Leiba on 22 October 2014.<br><br> Editorial - Replaced [RFC2818] with [RFC7230] for HTTPS and deleted<br> [RFC2818] from references, per advice of S. Mooneswamy on 13 October<br> 2014. <br><br> Editorial - Revised section 1.1 Structure of this Document to correct<br> list of sections per revisions in this draft, per IEEE-ISTO PWG IPP<br> WG review, <br><br> Editorial - Kept section 2.2 Abbreviations to become Appendix A, as a<br> compromise to request to remove entirely, per discussion with<br> S. Mooneswamy on 13 October 2014. <br><br> Editorial - Revised section 3 IPP over HTTPS Transport Binding to<br> delete (redundant) first paragraph, per advice of S. Mooneswamy on 13<br> October 2014. <br><br> Editorial - Revised section 3 IPP over HTTPS Transport Binding to add<br> reference to [RFC7230] for 'https' URI scheme in bullet (2), per<br> advice of S. Mooneswamy on 13 October 2014. <br><br> Editorial - Revised section 3 IPP over HTTPS Transport Binding to<br> delete (redundant) "reliable" qualifier of a TCP transport layer<br> connection in bullet (3), per advice of S. Mooneswamy on 13 October<br> 2014. <br><br> Editorial - Revised section 3 IPP over HTTPS Transport Binding to<br> replace "TLS 1.2 [RFC5246], or later TLS version," with "TLS 1.2<br> [RFC5246] or higher version" in bullet (4), consistent with TLS<br> future-proofing in current HTTP/2.0 draft, per IEEE-ISTO PWG IPP WG<br> review, rejecting request of S. Mooneswamy on 13 October 2014. <br><br> Editorial - Revised section 3 IPP over HTTPS Transport Binding to<br> delete (out-of-date) reference to [RFC2910] in bullet (6), per advice<br> of S. Mooneswamy on 13 October 2014. <br><br> Editorial - Revised section 3 IPP over HTTPS Transport Binding to<br> delete references to Security Considerations in other documents, per<br> advice of S. Mooneswamy on 13 October 2014. <br><br> Editorial - Revised section 4.1 Applicability of 'ipps' URI Scheme to<br> delete references to Security Considerations in other documents, per<br> advice of S. Mooneswamy on 13 October 2014. <br><br> Editorial - Revised section 4.2 Syntax of 'ipps' URI Scheme to<br> replace out-of-date reference to [RFC2911] w/ [STD66] (i.e., RFC<br> 3986), per advice of S. Mooneswamy on 13 October 2014. <br><br> Editorial - Revised section 4.2 Syntax of 'ipps' URI Scheme to move<br> conformance requirement out of "Note" and rewrite conformance that<br> IPP Printers SHOULD NOT *generate* 'ipps' URI longer than 255 octets,<br> due to known implementation bugs in many older IPP Clients, per<br> advice of S. Mooneswamy on 13 October 2014. <br><br> Editorial - Revisions section 4.3 Associated Port for 'ipps' URI<br> Scheme to move conformance requirement out of "Note", per advice of<br> S. Mooneswamy on 13 October 2014. <br><br> Editorial - Revised section 4.4 and References to change "MIME type"<br> or "MIME media type" to "media type" and "[MIMEREG]"to "[MEDIAREG]", <br> per advice of Barry Leiba on 22 October 2014. <br><br> Editorial - Revised section 4.6.1 to correct plural/singular<br> confusion, per advice of Barry Leiba on 22 October 2014. <br><br> Editorial - Deleted section 4.6.2 Examples of 'ipps' URI for Jobs,<br> because IPP "job-uri" attribute will be deprecated in the future, per<br> IEEE-ISTO PWG IPP WG review. <br><br> Editorial - Delete section 5 Applicability of this Specification<br> because it was redundant with conformance imperatives in section 4,<br> per advice of S. Mooneswamy on 13 October 2014. <br><br> Editorial - Kept IESG as change controller in (former) section 6 IANA<br> Considerations (since the document remains standards-track),<br> rejecting request of S. Mooneswamy on 13 October 2014. <br><br> Editorial - Revised (former) section 7.3 TLS Version Requirements to <br> replace "TLS 1.2 [RFC5246], or later TLS version," with "TLS 1.2<br> [RFC5246] or higher version", consistent with TLS future-proofing in<br> current HTTP/2.0 draft, per IEEE-ISTO PWG IPP WG review, rejecting<br> request of S. Mooneswamy on 13 October 2014. <br><br> Editorial - Deleted Appendix A - Summary of IPP URL Scheme, due to<br> ambiguity and for future-proofing, per IEEE-ISTO PWG 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></div></div>