[IPP] Fwd: [TLS] [Technical Errata Reported] RFC2817 (4187)

[IPP] Fwd: [TLS] [Technical Errata Reported] RFC2817 (4187)

[IPP] Fwd: [TLS] [Technical Errata Reported] RFC2817 (4187)

Ira McDonald blueroofmusic at gmail.com
Fri Nov 21 16:55:14 UTC 2014


Hi,

BEWARE - they're changing the product token (TLS/1.0 --> TLS)
in RFC 2817 - I can't imagine how this will be backward compatible.

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music / High North Inc
http://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthinc
mailto: blueroofmusic at gmail.com
Winter  579 Park Place  Saline, MI  48176  734-944-0094
Summer  PO Box 221  Grand Marais, MI 49839  906-494-2434


---------- Forwarded message ----------
From: RFC Errata System <rfc-editor at rfc-editor.org>
Date: Thu, Nov 20, 2014 at 6:17 PM
Subject: [TLS] [Technical Errata Reported] RFC2817 (4187)
To: rohit at 4k-associates.com, lawrence at agranat.com, stephen.farrell at cs.tcd.ie,
Kathleen.Moriarty.ietf at gmail.com, turners at ieca.com, joe at salowey.net
Cc: fielding at gbiv.com, tls at ietf.org, rfc-editor at rfc-editor.org


The following errata report has been submitted for RFC2817,
"Upgrading to TLS Within HTTP/1.1".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=2817&eid=4187

--------------------------------------
Type: Technical
Reported by: Roy T. Fielding <fielding at gbiv.com>

Section: 7.2

Original Text
-------------
   The Draft Standard for HTTP/1.1 [1] specifies that these tokens obey
   the production for 'product':

      product         = token ["/" product-version]
      product-version = token

[...]

   This specification defines the protocol token "TLS/1.0" as the
   identifier for the protocol specified by The TLS Protocol [6].


Corrected Text
--------------
   The Draft Standard for HTTP/1.1 [1] specifies that these tokens obey
   the production for 'product':

      product         = token ["/" product-version]
      product-version = token

[...]

   This specification defines the product token "TLS" as the
   identifier for the protocol specified by The TLS Protocol [6].
   When a specific version of TLS is desired, it is indicated by
   appending a slash ("/") and the TLS version number as the
   product-version (e.g., "TLS/1.0").


Notes
-----
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.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary.

--------------------------------------
RFC2817 (draft-ietf-tls-http-upgrade-05)
--------------------------------------
Title               : Upgrading to TLS Within HTTP/1.1
Publication Date    : May 2000
Author(s)           : R. Khare, S. Lawrence
Category            : PROPOSED STANDARD
Source              : Transport Layer Security
Area                : Security
Stream              : IETF
Verifying Party     : IESG

_______________________________________________
TLS mailing list
TLS at ietf.org
https://www.ietf.org/mailman/listinfo/tls
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20141121/4e0698c0/attachment.html>


More information about the ipp mailing list