IETF Logo Mail Archive

[TLS] [IANA #1413503] expert review for draft-ietf-tls-esni (tls-extensiontype-values)

David Dong via RT <drafts-expert-review-comment@iana.org> Mon, 21 April 2025 21:22 UTC

Return-Path: <iana-shared@iana.org>
X-Original-To: tls@mail2.ietf.org
Delivered-To: tls@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 4A0ED1F009C2; Mon, 21 Apr 2025 14:22:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -3.179
X-Spam-Level:
X-Spam-Status: No, score=-3.179 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sooQPy_T6D8s; Mon, 21 Apr 2025 14:22:42 -0700 (PDT)
Received: from smtp.lax.icann.org (smtp.lax.icann.org [IPv6:2620:0:2d0:201::1:81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 6D0A31F009BD; Mon, 21 Apr 2025 14:22:42 -0700 (PDT)
Received: from request7.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp.lax.icann.org (Postfix) with ESMTP id E412CE037C; Mon, 21 Apr 2025 21:22:41 +0000 (UTC)
Received: by request7.lax.icann.org (Postfix, from userid 48) id C9A1EC0A8EB4; Mon, 21 Apr 2025 21:22:41 +0000 (UTC)
RT-Owner: david.dong
From: David Dong via RT <drafts-expert-review-comment@iana.org>
In-Reply-To: <rt-5.0.3-1335530-1744423265-1214.1413503-9-0@icann.org>
References: <RT-Ticket-1413503@icann.org> <rt-5.0.3-1543-1740196928-1914.1413503-9-0@icann.org> <rt-5.0.3-773292-1740508539-1867.1413503-9-0@icann.org> <928EF6E2-2EF5-48D1-9F7D-F7CCBD909AAD@akamai.com> <rt-5.0.3-970672-1740594390-1330.1413503-9-0@icann.org> <rt-5.0.3-2597149-1741296715-18.1413503-9-0@icann.org> <rt-5.0.3-186449-1742002071-605.1413503-9-0@icann.org> <rt-5.0.3-1949884-1742853882-623.1413503-9-0@icann.org> <rt-5.0.3-1035737-1743639792-325.1413503-9-0@icann.org> <rt-5.0.3-1335530-1744423265-1214.1413503-9-0@icann.org>
Message-ID: <rt-5.0.3-535738-1745270561-84.1413503-9-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1413503
X-Managed-BY: RT 5.0.3 (http://www.bestpractical.com/rt/)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Mon, 21 Apr 2025 21:22:41 +0000
MIME-Version: 1.0
Message-ID-Hash: NW7NPAVYQ5QH3MWLK4OEX7CME4WDZUPN
X-Message-ID-Hash: NW7NPAVYQ5QH3MWLK4OEX7CME4WDZUPN
X-MailFrom: iana-shared@iana.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: nicholas.sullivan+ietf@gmail.com, tls@ietf.org, tls-reg-review@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: drafts-expert-review-comment@iana.org
Subject: [TLS] [IANA #1413503] expert review for draft-ietf-tls-esni (tls-extensiontype-values)
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/fbDucM2zNs5ira2xFCONW-7E5ns>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Owner: <mailto:tls-owner@ietf.org>
List-Post: <mailto:tls@ietf.org>
List-Subscribe: <mailto:tls-join@ietf.org>
List-Unsubscribe: <mailto:tls-leave@ietf.org>

Dear Yoav Nir (cc: tls WG, tls-reg-review mailing list),

Following up on this; as a designated expert for the TLS ExtensionType Values registry, can you review the proposed registration in draft-ietf-tls-esni-23 for us? Please note that Nick Sullivan is a co-author for this draft and that Rich has already approved.

Please see:

https://datatracker.ietf.org/doc/draft-ietf-tls-esni/

The due date was March 18.

If this is OK, when the IESG approves the document for publication, we'll make the registration at:

https://www.iana.org/assignments/tls-extensiontype-values/

We'll act after both experts approve the registration.

With thanks,

David Dong
IANA Services Sr. Specialist

On Sat Apr 12 02:01:05 2025, david.dong wrote:
> Dear Yoav Nir (cc: tls WG, tls-reg-review mailing list),
> 
> Following up on this; as a designated expert for the TLS ExtensionType
> Values registry, can you review the proposed registration in draft-
> ietf-tls-esni-23 for us? Please note that Nick Sullivan is a co-author
> for this draft and that Rich has already approved.
> 
> Please see:
> 
> https://datatracker.ietf.org/doc/draft-ietf-tls-esni/
> 
> The due date was March 18.
> 
> If this is OK, when the IESG approves the document for publication,
> we'll make the registration at:
> 
> https://www.iana.org/assignments/tls-extensiontype-values/
> 
> We'll act after both experts approve the registration.
> 
> With thanks,
> 
> David Dong
> IANA Services Sr. Specialist
> 
> On Thu Apr 03 00:23:12 2025, david.dong wrote:
> > Dear Yoav Nir (cc: tls WG, tls-reg-review mailing list),
> >
> > Following up on this; as a designated expert for the TLS
> > ExtensionType
> > Values registry, can you review the proposed registration in draft-
> > ietf-tls-esni-23 for us? Please note that Nick Sullivan is a co-
> > author
> > for this draft and that Rich had already approved.
> >
> > Please see:
> >
> > https://datatracker.ietf.org/doc/draft-ietf-tls-esni/
> >
> > The due date was March 18.
> >
> > If this is OK, when the IESG approves the document for publication,
> > we'll make the registration at:
> >
> > https://www.iana.org/assignments/tls-extensiontype-values/
> >
> > We'll act after both experts approve the registration.
> >
> > With thanks,
> >
> > David Dong
> > IANA Services Sr. Specialist
> >
> > On Mon Mar 24 22:04:42 2025, david.dong wrote:
> > > Dear Yoav Nir (cc: tls WG, tls-reg-review mailing list),
> > >
> > > Following up on this; as a designated expert for the TLS
> > > ExtensionType
> > > Values registry, can you review the proposed registration in draft-
> > > ietf-tls-esni-23 for us? Please note that Nick Sullivan is a co-
> > > author
> > > for this draft and that Rich had already approved.
> > >
> > > Please see:
> > >
> > > https://datatracker.ietf.org/doc/draft-ietf-tls-esni/
> > >
> > > The due date was March 18.
> > >
> > > If this is OK, when the IESG approves the document for publication,
> > > we'll make the registration at:
> > >
> > > https://www.iana.org/assignments/tls-extensiontype-values/
> > >
> > > We'll act after both experts approve the registration.
> > >
> > > With thanks,
> > >
> > > David Dong
> > > IANA Services Sr. Specialist
> > >
> > >
> > > On Sat Mar 15 01:27:51 2025, david.dong wrote:
> > > > Dear Yoav Nir (cc: tls WG, tls-reg-review mailing list),
> > > >
> > > > Following up on this; as a designated expert for the TLS
> > > > ExtensionType
> > > > Values registry, can you review the proposed registration in
> > > > draft-
> > > > ietf-tls-esni-23 for us? Please note that Nick Sullivan is a co-
> > > > author
> > > > for this draft and that Rich had already approved.
> > > >
> > > > Please see:
> > > >
> > > > https://datatracker.ietf.org/doc/draft-ietf-tls-esni/
> > > >
> > > > The due date is March 18.
> > > >
> > > > If this is OK, when the IESG approves the document for
> > > > publication,
> > > > we'll make the registration at:
> > > >
> > > > https://www.iana.org/assignments/tls-extensiontype-values/
> > > >
> > > > We'll act after both experts approve the registration.
> > > >
> > > > With thanks,
> > > >
> > > > David Dong
> > > > IANA Services Sr. Specialist
> > > >
> > > >
> > > > On Thu Mar 06 21:31:55 2025, david.dong wrote:
> > > > > Dear Yoav Nir (cc: tls WG, tls-reg-review mailing list),
> > > > >
> > > > > As a designated expert for the TLS ExtensionType Values
> > > > > registry,
> > > > > can
> > > > > you review the proposed registration in draft-ietf-tls-esni-23
> > > > > for
> > > > > us?
> > > > > Please note that Nick Sullivan is a co-author for this draft
> > > > > and
> > > > > that
> > > > > Rich had already approved.
> > > > >
> > > > > Please see:
> > > > >
> > > > > https://datatracker.ietf.org/doc/draft-ietf-tls-esni/
> > > > >
> > > > > The due date is March 18.
> > > > >
> > > > > If this is OK, when the IESG approves the document for
> > > > > publication,
> > > > > we'll make the registration at:
> > > > >
> > > > > https://www.iana.org/assignments/tls-extensiontype-values/
> > > > >
> > > > > We'll act after both experts approve the registration.
> > > > >
> > > > > With thanks,
> > > > >
> > > > > David Dong
> > > > > IANA Services Sr. Specialist
> > > > >
> > > > > On Wed Feb 26 18:26:30 2025, david.dong wrote:
> > > > > > Hi Nick,
> > > > > >
> > > > > > Yes, that's correct; this review request is for the two new
> > > > > > registrations in section 11.1 in the TLS ExtensionType Values
> > > > > > registry, which has the registration procedure of
> > > > > > Specification
> > > > > > Required.
> > > > > >
> > > > > > Thank you.
> > > > > >
> > > > > > Best regards,
> > > > > >
> > > > > > David Dong
> > > > > > IANA Services Sr. Specialist
> > > > > >
> > > > > > On Wed Feb 26 08:10:28 2025, nicholas.sullivan@gmail.com
> > > > > > wrote:
> > > > > > > I’m conflicted out as mentioned, but I want to clarify:
> > > > > > > this
> > > > > > > request
> > > > > > > is for
> > > > > > > the code points in the existing extension (section 11.1),
> > > > > > > not
> > > > > > > the
> > > > > > > request
> > > > > > > for the alert code point (11.2) or the new extension
> > > > > > > registry
> > > > > > > (11.3),
> > > > > > > correct?
> > > > > > >
> > > > > > > On Wed, Feb 26, 2025 at 3:15 AM Salz, Rich
> > > > > > > <rsalz@akamai.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > I approve.
> > > > > > > >
> > > > > > > > The draft does not say if the existing TLS DE's will do
> > > > > > > > the
> > > > > > > > new
> > > > > > > > table, but
> > > > > > > > I am okay with taking on that additional workload :)
> > > > > > > >
> > > > > > > >

v2.37.1 | Report a Bug | By Email | System Status