attachment
Hi,<br><br>BEWARE - they're changing the product token (TLS/1.0 --> TLS)<br>in RFC 2817 - I can't imagine how this will be backward compatible.<br><br>Cheers,<br>- Ira<br><br clear="all"><div><div class="gmail_signature"><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></div>
<br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">RFC Errata System</b> <span dir="ltr"><<a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>></span><br>Date: Thu, Nov 20, 2014 at 6:17 PM<br>Subject: [TLS] [Technical Errata Reported] RFC2817 (4187)<br>To: <a href="mailto:rohit@4k-associates.com">rohit@4k-associates.com</a>, <a href="mailto:lawrence@agranat.com">lawrence@agranat.com</a>, <a href="mailto:stephen.farrell@cs.tcd.ie">stephen.farrell@cs.tcd.ie</a>, <a href="mailto:Kathleen.Moriarty.ietf@gmail.com">Kathleen.Moriarty.ietf@gmail.com</a>, <a href="mailto:turners@ieca.com">turners@ieca.com</a>, <a href="mailto:joe@salowey.net">joe@salowey.net</a><br>Cc: <a href="mailto:fielding@gbiv.com">fielding@gbiv.com</a>, <a href="mailto:tls@ietf.org">tls@ietf.org</a>, <a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a><br><br><br>The following errata report has been submitted for RFC2817,<br>
"Upgrading to TLS Within HTTP/1.1".<br>
<br>
--------------------------------------<br>
You may review the report below and at:<br>
<a href="http://www.rfc-editor.org/errata_search.php?rfc=2817&eid=4187" target="_blank">http://www.rfc-editor.org/errata_search.php?rfc=2817&eid=4187</a><br>
<br>
--------------------------------------<br>
Type: Technical<br>
Reported by: Roy T. Fielding <<a href="mailto:fielding@gbiv.com">fielding@gbiv.com</a>><br>
<br>
Section: 7.2<br>
<br>
Original Text<br>
-------------<br>
The Draft Standard for HTTP/1.1 [1] specifies that these tokens obey<br>
the production for 'product':<br>
<br>
product = token ["/" product-version]<br>
product-version = token<br>
<br>
[...]<br>
<br>
This specification defines the protocol token "TLS/1.0" as the<br>
identifier for the protocol specified by The TLS Protocol [6].<br>
<br>
<br>
Corrected Text<br>
--------------<br>
The Draft Standard for HTTP/1.1 [1] specifies that these tokens obey<br>
the production for 'product':<br>
<br>
product = token ["/" product-version]<br>
product-version = token<br>
<br>
[...]<br>
<br>
This specification defines the product token "TLS" as the<br>
identifier for the protocol specified by The TLS Protocol [6].<br>
When a specific version of TLS is desired, it is indicated by<br>
appending a slash ("/") and the TLS version number as the<br>
product-version (e.g., "TLS/1.0").<br>
<br>
<br>
Notes<br>
-----<br>
This erratum clarifies that "TLS" is the product token and any TLS version number (currently DIGIT "." DIGIT) is the product-version token. This has already been corrected in the Upgrade Token Registry.<br>
<br>
Instructions:<br>
-------------<br>
This erratum is currently posted as "Reported". If necessary, please<br>
use "Reply All" to discuss whether it should be verified or<br>
rejected. When a decision is reached, the verifying party (IESG)<br>
can log in to change the status and edit the report, if necessary.<br>
<br>
--------------------------------------<br>
RFC2817 (draft-ietf-tls-http-upgrade-05)<br>
--------------------------------------<br>
Title : Upgrading to TLS Within HTTP/1.1<br>
Publication Date : May 2000<br>
Author(s) : R. Khare, S. Lawrence<br>
Category : PROPOSED STANDARD<br>
Source : Transport Layer Security<br>
Area : Security<br>
Stream : IETF<br>
Verifying Party : IESG<br>
<br>
_______________________________________________<br>
TLS mailing list<br>
<a href="mailto:TLS@ietf.org">TLS@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/tls" target="_blank">https://www.ietf.org/mailman/listinfo/tls</a><br>
</div><br>