Re: [DNSOP] SVCB without A/AAAA records at the service name

Ben Schwartz <bemasc@google.com> Tue, 19 January 2021 15:09 UTC

MIME-Version: 1.0
References: <2e1054a0-5a7a-4d62-92a1-095217af82bb@www.fastmail.com> <CAHbrMsCaVER+xDjznjRK4cSjqc+g855GNV2QCfewvCqh=E1FMw@mail.gmail.com> <87098be5-765c-4481-b990-bdb2c936173d@www.fastmail.com>
In-Reply-To: <87098be5-765c-4481-b990-bdb2c936173d@www.fastmail.com>
From: Ben Schwartz <bemasc@google.com>
Date: Tue, 19 Jan 2021 10:09:45 -0500
Message-ID: <CAHbrMsCu1bYcEuT2R3g5M9aUBQguVeWhiyZpDH=JzSEPpc=iqg@mail.gmail.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: dnsop <dnsop@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="0000000000004b47be05b9423b6a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/JY8EyHFs2z0m4sBdYB9zdJsXBrk>
Subject: Re: [DNSOP] SVCB without A/AAAA records at the service name
Precedence: list

On Sun, Jan 17, 2021 at 5:57 PM Martin Thomson <mt@lowentropy.net> wrote:

> On Sat, Jan 16, 2021, at 06:01, Ben Schwartz wrote:
> > FWIW, I think this is really an editorial question.
> ...
> > https://github.com/MikeBishop/dns-alt-svc/pull/288
> ...
> > https://github.com/MikeBishop/dns-alt-svc/pull/289
>
> Neither of these work for me.  Both do the same thing in different ways.
> Both are unspecific about what changes might be made to the algorithm.


To my eye, #288 looks extremely specific.  I'm surprised we disagree about
this!


>   That leads to far less certainty about how the information is consumed
> than I think is sensible.
>
> What I'm looking for here is for the specification to describe what
> happens when the protocol needs to fall back to A/AAAA and what happens
> when it does not.


I think #288 is quite "specific" about what happens in that case.  (Whether
it's "sensible" is a separate question.)


>   The first is important, because that is what HTTP will need.  The second
> because I think that is a better approach for any new protocol (I had hoped
> that webtransport would be able to take advantage of this, but they made a
> different choice for reasons I'm yet to understand).
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>

Attachment: smime.p7s

[DNSOP] SVCB without A/AAAA records at the servic… Martin Thomson
Re: [DNSOP] SVCB without A/AAAA records at the se… Shane Kerr
Re: [DNSOP] SVCB without A/AAAA records at the se… Paul Vixie
Re: [DNSOP] SVCB without A/AAAA records at the se… Ben Schwartz
Re: [DNSOP] SVCB without A/AAAA records at the se… Eric Orth
Re: [DNSOP] SVCB without A/AAAA records at the se… Martin Thomson
Re: [DNSOP] SVCB without A/AAAA records at the se… Ben Schwartz
Re: [DNSOP] SVCB without A/AAAA records at the se… Martin Thomson
Re: [DNSOP] SVCB without A/AAAA records at the se… Ben Schwartz
Re: [DNSOP] SVCB without A/AAAA records at the se… Martin Thomson
Re: [DNSOP] SVCB without A/AAAA records at the se… Ben Schwartz
Re: [DNSOP] SVCB without A/AAAA records at the se… Hollenbeck, Scott
Re: [DNSOP] SVCB without A/AAAA records at the se… Ben Schwartz
Re: [DNSOP] SVCB without A/AAAA records at the se… Hollenbeck, Scott
Re: [DNSOP] SVCB without A/AAAA records at the se… Ben Schwartz
Re: [DNSOP] SVCB without A/AAAA records at the se… Hollenbeck, Scott
Re: [DNSOP] SVCB without A/AAAA records at the se… Ben Schwartz
Re: [DNSOP] SVCB without A/AAAA records at the se… Martin Thomson

Re: [DNSOP] SVCB without A/AAAA records at the service name

Attachment: smime.p7s