Hiya,

On 02/09/2025 15:38, Watson Ladd wrote:
What's wrong with experiments in the experimental category?

Do you mean why not proceed to an RFC as usual?

We could, from my POV. OTOH, in this case there's only the one
implementation that we know of (mine) and that's only been
used in a test setup, so it doesn't seem unreasonable to wait
and see if someone else implements.

More comprehensive read through coming,

Thanks!

Cheers,
S.

but I do think the experimental
category is supposed to be for experiments and useful.

Astra mortemque praestare gradatim

On Tue, Sep 2, 2025, 6:41 AM Stephen Farrell <stephen.farr...@cs.tcd.ie>
wrote:


Hiya,

We made a bunch of editorial changes after the comments
received at IETF-123 with which the commenters seem ok,
so the authors would like to ask if the chairs think this
is ready for WGLC. (We understand the plan is to park it
after that awaiting more implementation experience which
is fine.)

There are no outstanding issues or PRs on the git repo. [1]

Cheers,
S.

[1] https://github.com/sftcd/wkesni

On 02/09/2025 14:30, internet-dra...@ietf.org wrote:
Internet-Draft draft-ietf-tls-wkech-09.txt is now available. It is a
work item
of the Transport Layer Security (TLS) WG of the IETF.

     Title:   A well-known URI for publishing service parameters
     Authors: Stephen Farrell
              Rich Salz
              Benjamin Schwartz
     Name:    draft-ietf-tls-wkech-09.txt
     Pages:   18
     Dates:   2025-09-02

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 origin, in collaboration with DNS infrastructure elements,
     to publish and rotate its own ECH keys.  Other service bindng data
     such as information about TLS supported groups is unlikely to change
     quickly, but the 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 datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-tls-wkech/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-tls-wkech-09

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-tls-wkech-09

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


_______________________________________________
TLS mailing list -- tls@ietf.org
To unsubscribe send an email to tls-le...@ietf.org

_______________________________________________
TLS mailing list -- tls@ietf.org
To unsubscribe send an email to tls-le...@ietf.org



Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

_______________________________________________
TLS mailing list -- tls@ietf.org
To unsubscribe send an email to tls-le...@ietf.org

Reply via email to