Thanks for bringing this draft to IETF for review. As a matter of process, I think this proposal is primarily relevant to the HTTPBIS working group, and should be reviewed there, not here.
On the content: It seems like the main potential benefit of this proposal is to fail faster in certain cases, by skipping HTTP requests that would return a 404 response. For this to work, the SvcParam needs to be specified as an exhaustive list of all .well-known/ endpoints on the host. (Otherwise, absence from the list does not allow the client to skip the HTTP request.) However, many HTTP origins have a large number* of resources available in .well-known, which would result in bloated HTTPS records. There are also operational friction concerns: adding and removing .well-known resources now requires updating two different systems, and errors may occur when they disagree. Given these issues, and the obvious security concerns, I don't think we should pursue this design. However, I do encourage you to share the work with HTTPBIS for additional review. --Ben Schwartz * For the MASQUE protocols, there are actually _infinitely_ many .well-known resources, but that could be accommodated by listing the template string. On Wed, Sep 16, 2026 at 9:48 AM Jim Mozley <[email protected]> wrote: > > > > 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://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-mk-dnsop-svcb-well-known-00.txt__;!!Bt8RZUm9aw!5mTgEbtiiPpyMULn7l3DaEoMb9mvIZJnbP_dwBYqo43FN7Bpn13wHfuFpIfcNBfsqiQbYjRRrmG4A0SadywbRQjeqfk$ > > Status: > > https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-mk-dnsop-svcb-well-known__;!!Bt8RZUm9aw!5mTgEbtiiPpyMULn7l3DaEoMb9mvIZJnbP_dwBYqo43FN7Bpn13wHfuFpIfcNBfsqiQbYjRRrmG4A0SadywbrphxABY$ > > HTMLized: > > https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-mk-dnsop-svcb-well-known__;!!Bt8RZUm9aw!5mTgEbtiiPpyMULn7l3DaEoMb9mvIZJnbP_dwBYqo43FN7Bpn13wHfuFpIfcNBfsqiQbYjRRrmG4A0Sadywb9z2NMBQ$ > > > > 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]
