> I would suggest writing an Internet-Draft to start the discussion. You are the second person to make this suggestion. Can you help me understand what is unclear or missing from the current (W3C-formatted) document, linked in my initial mail?
>From my perspective, there are a number of mature technical organizations >(like the IETF and W3C) each with their own preferred document formats. The >relative pros and cons of document formats are quite minor - it's the content >that matters. Converting between document formats is time-consuming, for >little benefit. I could have an AI agent do this conversion, of course, but I >don't think that would generate much benefit either. Thanks, Will ________________________________ From: S Moonesamy <[email protected]> Sent: Wednesday, April 8, 2026 12:32 PM To: Will Bartlett <[email protected]>; [email protected] <[email protected]> Subject: Re: [EXTERNAL] Re: [DNSOP] Advice sought: DNS record type for FedCM well-known file delegation [You don't often get email from [email protected]. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] Hi Will, At 11:56 AM 08-04-2026, Will Bartlett wrote: >I'm familiar with RFC 8615. It says: > > > Note that this specification defines neither how to determine the > hostname to use to find the well-known URI for a particular > application, nor the scope of the metadata discovered by > dereferencing the well-known URI; both should be defined by the > application itself. Yes. >I am seeking advice on this (hostname) aspect of the problem, which >RFC 8615 specifies is out of its scope. > >Specifically, I am evaluating whether/how to use DNS to indicate the >authoritative hostname for a registrable domain through an RFC 8552 >"Underscored and Globally Scoped DNS Node Names" . I looked at RFC 8555. You could try a similar approach (provisioning a DNS record) as a starting point. I would suggest writing an Internet-Draft to start the discussion. Regards, S. Moonesamy
_______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
