Hi Jim,
I've read draft-mk-svcb-well-known-00. A clean, well-scoped draft. Defining
"well-known" as a general primitive that other specifications can reference is
the right design, and the motivating cases are persuasive.
I have a few questions:
1. Section 2.2, order preservation is specified, but not whether the same
suffix may appear more than once in a list. For example, "A suffix SHOULD NOT
appear more than once in a list; a decoder MUST tolerate duplicates"? Or is
there a reason to leave this unspecified?
2. Section 2.2, "A suffix may extend below a registered well-known name where
that registration allows it". How does an implementer tell whether a given
registration allows subpaths? Would a concrete example be helpful?
3. Section 5, the draft advises publishers to keep advertisements compact.
Would a brief operational note be added, or is the number of suffixes best left
entirely to the publisher?
4. Section 7, I'd like to register support for the suffix-only choice; it
matches the form used by IANA "Well-Known URIs" registry and saves octets on
the wire. No change requested—just noting a preference among the open issues.
Best
Guozhen Dong
在 2026年9月16日 21:35，Jim Mozley<[email protected]> 写道：
Hi dnsop, This draft defines an SVCB and HTTPS record parameter for well-known
URI path suffixes for services that use them. Your comments are most welcome.
Regards, the authors > Begin forwarded message: > > A new version of
Internet-Draft draft-mk-dnsop-svcb-well-known-00.txt has been > successfully
submitted by Jim Mozley and posted to the > IETF repository. > > Name:
draft-mk-dnsop-svcb-well-known > Revision: 00 > Title: An SVCB Service
Parameter for Well-Known URI Paths > Date: 2026-09-16 > Group: Individual
Submission > Pages: 9 > URL:
https://www.ietf.org/archive/id/draft-mk-dnsop-svcb-well-known-00.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 > >
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]
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]
