Re: #385: HTTP2 Upgrade / Negotiation

Hi,

I'm not an expert here, but yes, there are lots of ways to badly design
your DNS and incur delays - but there are also reasonable ones. This is not
substantially different than the 'out of baliwick' DNS issues from the 90's
right? but that also shows it is resolvable within the current record type
framework, as you say in this case by using the same name which is what I
think we're all envisioning.

something like

www.example.com 86400 IN A 10.10.10.100
_http2tls._tcp.www.example.com. 86400 IN SRV 0 5 443 www.example.com.


there is nothing really unworkable about using a different target name, it
just might incur delays (depending on cache state) that remove the value of
the scheme. So don't do that :)

-Patrick

[eliot, sorry for the double send to you - meant to send it to the list the
first time.]

On Wed, Oct 24, 2012 at 4:41 AM, Eliot Lear <lear@cisco.com> wrote:


A solution to this issue is to use the same name.  That guarantees the
same authority.

Eliot