attachment

<div dir="ltr"><div dir="ltr">Hi,<br><br>I&#39;ve just <span>posted</span> another Internet-<span>Draft</span> of <span><span><span>IPP</span></span></span> over HTTPS Transport Binding and<br>&#39;<span><span><span><span><span><span><span>ipps</span></span></span></span></span></span></span>&#39;<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-13-20140703.txt" target="_blank">ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-13-20140703.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-13-20140703.pdf" target="_blank">ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-13-20140703.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 *minor* editorial changes since the previous version.<br>
</div><br>
Comments?<br><br>Cheers,<br>- Ira<br><br>--------------------------------<br><br><div><div dir="ltr">Change History<br><br>   3 July 2014 - draft-mcdonald-ipps-uri-scheme-13txt <br>   Editorial - Revised section 4.2 Syntax of &#39;ipps&#39; URI Scheme, to<br>

   replace old &#39;path-absolute&#39; from RFC 2616 with &#39;absolute-path&#39; from<br>   [RFC7230], per IEEE-ISTO PWG IPP WG review.  <br><br>   Editorial - Revised section 2.2 Abbreviations, section 3 IPP over<br>   HTTPS Transport Binding, section 4.2 Syntax of &#39;ipps&#39; URI Scheme,<br>

   section 4.7 Comparisons of &#39;ipps&#39; URI, section 7.2 Attacks and<br>   Defenses, section 9.1 Normative References, and section 10 Appendix A<br>   - Summary of IPP URL Scheme, to replace [RFC2616] with either<br>

   [RFC7230] or [HTTP1.1] - a new collective reference to [RFC7230],<br>   [RFC7231], [RFC7232], [RFC7233], [RFC7234], and [RFC7235], per<br>   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>
</div>