Congrats to all those who participated in making this an RFC!

spt

> On Mar 4, 2026, at 00:50, [email protected] wrote:
> 
> A new Request for Comments is now available in online RFC libraries.
> 
> 
>        RFC 9848
> 
>        Title:      Bootstrapping TLS Encrypted ClientHello with 
>                    DNS Service Bindings 
>        Author:     B. Schwartz,
>                    M. Bishop,
>                    E. Nygren
>        Status:     Standards Track
>        Stream:     IETF
>        Date:       March 2026
>        Mailbox:    [email protected],
>                    [email protected],
>                    [email protected]
>        Pages:      9
>        Updates/Obsoletes/SeeAlso:   None
> 
>        I-D Tag:    draft-ietf-tls-svcb-ech-08.txt
> 
>        URL:        https://www.rfc-editor.org/info/rfc9848
> 
>        DOI:        10.17487/RFC9848
> 
> To use TLS Encrypted ClientHello (ECH), the client needs to learn the
> ECH configuration for a server before it attempts a connection to the
> server.  This specification provides a mechanism for conveying the
> ECH configuration information via DNS, using a SVCB or HTTPS resource
> record (RR).
> 
> This document is a product of the Transport Layer Security Working Group of 
> the IETF.
> 
> This is now a Proposed Standard.
> 
> STANDARDS TRACK: This document specifies an Internet Standards Track
> protocol for the Internet community, and requests discussion and suggestions
> for improvements.  Please refer to the current edition of the Official
> Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
> standardization state and status of this protocol.  Distribution of this 
> memo is unlimited.
> 
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>  https://www.ietf.org/mailman/listinfo/ietf-announce
>  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
> 
> For searching the RFC series, see https://www.rfc-editor.org/search
> For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
> 
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to [email protected].  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
> 
> 
> The RFC Editor Team
> 
> 
> _______________________________________________
> IETF-Announce mailing list -- [email protected]
> To unsubscribe send an email to [email protected]

_______________________________________________
TLS mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to