Re: [TLS] [Technical Errata Reported] RFC5246 (5036)

Eric Rescorla <ekr@rtfm.com> Fri, 09 June 2017 14:03 UTC

MIME-Version: 1.0
In-Reply-To: <20170609135502.A314AB80D5B@rfc-editor.org>
References: <20170609135502.A314AB80D5B@rfc-editor.org>
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 09 Jun 2017 15:02:59 +0100
Message-ID: <CABcZeBOyHQm+LhutLTKvuj9+yk1wEq9gUzHVu4FKwhR4PGCb+Q@mail.gmail.com>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: Tim Dierks <tim@dierks.org>, Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>, Joseph Salowey <joe@salowey.net>, sean+ietf@sn3rd.com, stefan.goeman@devoteam.com, "tls@ietf.org" <tls@ietf.org>
Content-Type: multipart/alternative; boundary="f403045eb768ba7b850551876f20"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/L81yGisNaBOAhYAk4_e8xY-IkZg>
Subject: Re: [TLS] [Technical Errata Reported] RFC5246 (5036)
Precedence: list

This erratum is incorrect.

Here is the definition of SessionID:
      opaque SessionID<0..32>;

The angle brackets mean that it is variable length and the 0..32 means that
there is
a one-byte length field.

On Fri, Jun 9, 2017 at 2:55 PM, RFC Errata System <rfc-editor@rfc-editor.org
> wrote:

> The following errata report has been submitted for RFC5246,
> "The Transport Layer Security (TLS) Protocol Version 1.2".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata/eid5036
>
> --------------------------------------
> Type: Technical
> Reported by: Stefan Goeman <stefan.goeman@devoteam.com>
>
> Section: 7.4.1.2
>
> Original Text
> -------------
> The ClientHello Structure indicates that a SessionID could be present.
> However if I take a wireshark of a TLS session I always see a "Session
> ID Length" field, either with value 0 or value 32
>
> Corrected Text
> --------------
> In the ClientHello structure and ServerHello structure, include
> a 1 byte "Session ID Length" field.
>
> Notes
> -----
> The ClientHello Structure indicates that a SessionID could be present.
> However if I take a wireshark of a TLS session I always see a
> "Session ID Length" field, either with value 0 or value 32.
>
> 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
> can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC5246 (draft-ietf-tls-rfc4346-bis-10)
> --------------------------------------
> Title               : The Transport Layer Security (TLS) Protocol Version
> 1.2
> Publication Date    : August 2008
> Author(s)           : T. Dierks, E. Rescorla
> Category            : PROPOSED STANDARD
> Source              : Transport Layer Security
> Area                : Security
> Stream              : IETF
> Verifying Party     : IESG
>

[TLS] [Technical Errata Reported] RFC5246 (5036) RFC Errata System
Re: [TLS] [Technical Errata Reported] RFC5246 (50… Eric Rescorla