Hi dnsop, A new version of this draft has been posted to the tracker, the main changes are:
* More rationale for the well-known service parameter key in the introduction section, including an example * Some minor clarifications following feedback Comments are welcome! Cheers, Jim On 2026-10-19, 12:36, "[email protected]" <[email protected]> wrote: This Message Is From an External Sender This message came from outside your organization. A new version of Internet-Draft draft-mk-dnsop-svcb-well-known-01.txt has been successfully submitted by Jim Mozley and posted to the IETF repository. Name: draft-mk-dnsop-svcb-well-known Revision: 01 Title: An SVCB Service Parameter for Well-Known URI Paths Date: 2026-10-19 Group: Individual Submission Pages: 9 URL: https://www.ietf.org/archive/id/draft-mk-dnsop-svcb-well-known-01.txt Status: https://datatracker.ietf.org/doc/draft-mk-dnsop-svcb-well-known/ HTMLized: https://datatracker.ietf.org/doc/html/draft-mk-dnsop-svcb-well-known Diff: https://author-tools.ietf.org/iddiff?url2=draft-mk-dnsop-svcb-well-known-01 Abstract: This document defines the "well-known" Service Parameter Key (SvcParamKey) for SVCB and HTTPS resource records. It carries one or more well-known URI suffixes, identifying resources under "/.well- known/" that are available at the service endpoint. It specifies the presentation and wire formats and requests registration of the key with IANA. The IETF Secretariat
_______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
