Re: [DNSOP] [Ext] Questions / concerns with draft-ietf-dnsop-svcb-https (in RFC Editor queue)

2022-08-29 Thread Viktor Dukhovni
On Mon, Aug 29, 2022 at 09:32:24PM +, Warren Kumari wrote: > > * For the rfc1123 section 2 topic, it may make sense to clarify the text > > to say "domain name" rather than "hostname": > >> An "alternative endpoint" is a hostname, port number, and other > >> associated instructions

Re: [DNSOP] [Ext] Questions / concerns with draft-ietf-dnsop-svcb-https (in RFC Editor queue)

2022-08-29 Thread Warren Kumari
On Mon, Aug 29, 2022 at 12:33 PM, Erik Nygren wrote: > Catching up on this thread, I agree with Ben Schwartz, Tommy Pauly, and > Eric Orth > that the current behavior makes sense and that no fundamental technical > change is needed. > I've been watching this thread and following along - it has

Re: [DNSOP] [Ext] Questions / concerns with draft-ietf-dnsop-svcb-https (in RFC Editor queue)

2022-08-29 Thread Viktor Dukhovni
On Mon, Aug 29, 2022 at 12:33:55PM -0400, Erik Nygren wrote: > On paths forward on the draft as it stands to clarify without making > significant technical changes (which I don't think are necessary): > > * Are there particular clarifications we can/should add to help make > the current behavior

Re: [DNSOP] [Ext] Questions / concerns with draft-ietf-dnsop-svcb-https (in RFC Editor queue)

2022-08-29 Thread Erik Nygren
Catching up on this thread, I agree with Ben Schwartz, Tommy Pauly, and Eric Orth that the current behavior makes sense and that no fundamental technical change is needed. No matter what we do, odd faults and misconfigurations will happen and Postel's law applies. Client implementers will try and