Hiya,
This version just updates refs as ECH is now RFC9849. We've no good news as to a 2nd implementation so I guess this stays parked for now. (Which is ok.) Cheers, S. -------- Forwarded Message -------- Subject: New Version Notification for draft-ietf-tls-wkech-12.txt Date: Sun, 03 May 2026 06:14:45 -0700 From: [email protected]To: Benjamin Schwartz <[email protected]>, Rich Salz <[email protected]>, Stephen Farrell <[email protected]>
A new version of Internet-Draft draft-ietf-tls-wkech-12.txt has been successfully submitted by Stephen Farrell and posted to the IETF repository. Name: draft-ietf-tls-wkech Revision: 12 Title: A well-known URI for publishing service parameters Date: 2026-05-03 Group: tls Pages: 21 URL: https://www.ietf.org/archive/id/draft-ietf-tls-wkech-12.txt Status: https://datatracker.ietf.org/doc/draft-ietf-tls-wkech/ HTMLized: https://datatracker.ietf.org/doc/html/draft-ietf-tls-wkech Diff: https://author-tools.ietf.org/iddiff?url2=draft-ietf-tls-wkech-12 Abstract: We define a well-known URI at which an HTTP origin can inform an authoritative DNS server, or other interested parties, about its Service Bindings. Service binding data can include Encrypted ClientHello (ECH) configurations, that may change frequently. This allows the HTTP origin, in collaboration with DNS infrastructure elements, to publish and rotate its own ECH keys. Other service binding data such as information about TLS supported groups is unlikely to change quickly, but the HTTP origin is much more likely to have accurate information when changes do occur. Service data published via this mechanism is typically available via an HTTPS or SVCB resource record. The IETF Secretariat
OpenPGP_signature.asc
Description: OpenPGP digital signature
_______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
