Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Rebecca VanRheenen <rvanrheenen@amsl.com>
In-Reply-To: <20240823132657.69DAD7FA73@rfcpa.rfc-editor.org>
Date: Fri, 23 Aug 2024 11:17:29 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3BE01903-50F9-4F8C-AFEE-94CA0D79C1F0@amsl.com>
References: <20240823132657.69DAD7FA73@rfcpa.rfc-editor.org>
To: Paul Wouters <paul.wouters@aiven.io>
Message-ID-Hash: UFWJANVSMEB35OEH6UI3Z3WGQJ4LQGCP
CC: RFC Editor <rfc-editor@rfc-editor.org>, kamil.milewski@plum.pl,
 nagendra@cs.stanford.edu, tls@ietf.org
Precedence: list
Subject: =?utf-8?q?=5BTLS=5DRe=3A_=5BEditorial_Errata_Reported=5D_RFC6347_=288089=29?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/tls/_y9CTtyp6M_HeIPUDteFReECT8k>

Hi Paul,

We are unable to verify this erratum that the submitter marked as =
editorial, so we changed the Type to =E2=80=9CTechnical=E2=80=9D. As =
Stream Approver, please review and set the Status and Type accordingly =
(see the definitions at https://www.rfc-editor.org/errata-definitions/).

Notes:
* RFC 6347 has been obsoleted by RFC 9147. We see similar blocks of code =
in Section 5.2 and Appendix A.2 of RFC 9147.
* For information about errata on obsolete RFCs, see #7 in the IESG =
Statement on "IESG Processing of RFC Errata for the IETF Stream=E2=80=9D =
(https://datatracker.ietf.org/doc/statement-iesg-iesg-processing-of-rfc-er=
rata-for-the-ietf-stream-20210507/).

You may review the report at:=20
https://www.rfc-editor.org/errata/eid8089

Information on how to verify errata reports can be found at:=20
https://www.rfc-editor.org/how-to-verify/

Further information on errata can be found at:=20
https://www.rfc-editor.org/errata.php

Best regards,
RFC Editor/rv


> On Aug 23, 2024, at 6:26 AM, RFC Errata System =
<rfc-editor@rfc-editor.org> wrote:
>=20
> The following errata report has been submitted for RFC6347,
> "Datagram Transport Layer Security Version 1.2".
>=20
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid8089
>=20
> --------------------------------------
> Type: Editorial
> Reported by: Kamil Milewski <kamil.milewski@plum.pl>
>=20
> Section: 4.2.2
>=20
> Original Text
> -------------
>   struct {
>     HandshakeType msg_type;
>     uint24 length;
>     uint16 message_seq;                               // New field
>     uint24 fragment_offset;                           // New field
>     uint24 fragment_length;                           // New field
>     select (HandshakeType) {
>       case hello_request: HelloRequest;
>       case client_hello:  ClientHello;
>       case hello_verify_request: HelloVerifyRequest;  // New type
>       case server_hello:  ServerHello;
>       case certificate:Certificate;
>       case server_key_exchange: ServerKeyExchange;
>       case certificate_request: CertificateRequest;
>       case server_hello_done:ServerHelloDone;
>       case certificate_verify:  CertificateVerify;
>       case client_key_exchange: ClientKeyExchange;
>       case finished: Finished;
>     } body;
>   } Handshake;
>=20
> Corrected Text
> --------------
>   struct {
>     HandshakeType msg_type;
>     uint24 length;
>     uint16 message_seq;                               // New field
>     uint24 fragment_offset;                           // New field
>     uint24 fragment_length;                           // New field
>     select (HandshakeType) {
>       case hello_request: HelloRequest;
>       case client_hello:  ClientHello;
>       case server_hello:  ServerHello;
>       case hello_verify_request: HelloVerifyRequest;  // New field
>       case certificate:Certificate;
>       case server_key_exchange: ServerKeyExchange;
>       case certificate_request: CertificateRequest;
>       case server_hello_done:ServerHelloDone;
>       case certificate_verify:  CertificateVerify;
>       case client_key_exchange: ClientKeyExchange;
>       case finished: Finished;
>     } body; } Handshake;
>=20
> Notes
> -----
> Change the order of cases inside select field to keep it:
> 1. In ascending order
> 2. Consistent with the structure in 4.3.2
>=20
> Instructions:
> -------------
> This erratum is currently posted as "Reported". (If it is spam, it=20
> will be removed shortly by the RFC Production Center.) Please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party =20
> will log in to change the status and edit the report, if necessary.
>=20
> --------------------------------------
> RFC6347 (draft-ietf-tls-rfc4347-bis-06)
> --------------------------------------
> Title               : Datagram Transport Layer Security Version 1.2
> Publication Date    : January 2012
> Author(s)           : E. Rescorla, N. Modadugu
> Category            : PROPOSED STANDARD
> Source              : Transport Layer Security
> Stream              : IETF
> Verifying Party     : IESG
>=20