> Begin forwarded message: > > From: "Sabrina Tanamal via RT" <[email protected]> > Subject: [IANA #1180852] Last Call: <draft-ietf-quic-tls-32.txt> (Using TLS > to Secure QUIC) to Proposed Standard > Date: November 16, 2020 at 19:07:09 GMT+2 > Cc: [email protected], [email protected], [email protected], [email protected], > [email protected], [email protected], > [email protected], [email protected], [email protected] > Resent-From: <[email protected]> > Resent-To: [email protected], [email protected] > Reply-To: [email protected] > > (BEGIN IANA COMMENTS) > > IESG/Authors/WG Chairs: > > The IANA Functions Operator has completed its review of > draft-ietf-quic-tls-32. If any part of this review is inaccurate, please let > us know. > > The IANA Functions Operator understands that, upon approval of this document, > there is a single action which we must complete. > > In the TLS ExtensionType Values registry on the Transport Layer Security > (TLS) Extensions registry page located at: > > https://www.iana.org/assignments/tls-extensiontype-values/ > > a single, new value is to be registered as follows: > > Value: [ TBD-at-Registration ] > Extension Name: quic_transport_parameters > TLS 1.3: CH, EE > Recommended: Y > Reference: [ RFC-to-be ] > > As this document requests registrations in a Specification Required (see RFC > 8126) registry, we will initiate the required Expert Review via a separate > request. This review must be completed before the document's IANA state can > be changed to "IANA OK." > > The IANA Functions Operator understands that this is the only action required > to be completed upon approval of this document. > > Note: The actions requested in this document will not be completed until the > document has been approved for publication as an RFC. This message is meant > only to confirm the list of actions that will be performed. > > Thank you, > > Sabrina Tanamal > Senior IANA Services Specialist > > (END IANA COMMENTS) >
signature.asc
Description: Message signed with OpenPGP
