Stephen,
Small nit regarding the definition :
Zone factory (ZF): an entity that has write-access to the DNS
and similar text in the intro.
First, it leaves unclear what THE DNS means (although clear from later on that
you are talking about the authoritative DNS server)
and so you mean write access to the authoritative DNS server's zone files or
zone database (or "binding data" if you prefer).
So, something l like
Zone factory (ZF): an entity that has write-access to the authoritative DNS
server zone database.
In addition, I am not sure that the ZF really needs real "write access".
Later on you use the term "publish" as in
ZF publishes new HTTPS RR
which implies a separate ZF entity with a pub/sub interface
in which case the ZF has no "write access" to the DNS internals,
it merely publishes information that the DNS server can decide to consume.
Y(J)S
-----Original Message-----
From: Stephen Farrell <[email protected]>
Sent: Monday, July 7, 2025 7:04 PM
To: [email protected]
Subject: [EXTERNAL] [TLS] Re: I-D Action: draft-ietf-tls-wkech-08.txt
External Email: Be cautious do not click links or open attachments unless you
recognize the sender and know the content is safe
Hiya,
I figure this one's about ready for WGLC so if given the chance to present it
in Madrid, asking for that'd be the last slide:-)
As the chairs prefer, that could be started before, during or after Madrid.
Cheers,
S.
PS: Not sure if a pressie in Madrid is needed, as the changes since -07 are
modest, though not entirely trivial, so happy to do a pressie, or to just ask
for WGLC and see if that causes any upset:-)
On 07/07/2025 16:44, [email protected] wrote:
> Internet-Draft draft-ietf-tls-wkech-08.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-08.txt
> Pages: 18
> Dates: 2025-07-07
>
> 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. The data can include Encrypted ClientHello (ECH)
> configurations, allowing the origin, in collaboration with DNS
> infrastructure elements, to publish and rotate its own ECH keys.
>
> Note
>
> This note is to be removed before publishing as an RFC.
>
> The source for this draft is in https://github.com/sftcd/wkesni/
> Issues and PRs are welcome there too.
>
> 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-08
>
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-tls-wkech-08
>
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
>
>
> _______________________________________________
> TLS mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
This message is intended only for the designated recipient(s). It may contain
confidential or proprietary information. If you are not the designated
recipient, you may not review, copy or distribute this message. If you have
mistakenly received this message, please notify the sender by a reply e-mail
and delete this message. Thank you.
_______________________________________________
TLS mailing list -- [email protected]
To unsubscribe send an email to [email protected]
