Re: [DNSOP] opportunistic refresh and Happy Eyeballs

[Viktor Dukhovni <[e-mail]>]

On Tue, Aug 15, 2017 at 10:28:15AM -0700, Paul Vixie wrote:

> > There has been much discussion about doing away with any/255 and I
> > seem to recall some discussion of a ANYA type which would return AAAA
> > and A.
> > 
> > This is something I see value in being implemented.
> 
> as i've said every few years when this proposal comes up, it's unnec'y.
> 
> We can specify that AAAA be sent as additional data for QTYPE=A, and
> that A be sent as additional data when QTYPE=AAAA.
> 
> given identical deployment curves along both the ANYA and
> additional-data timelines, we will get identical results.

+1, by far simpler/cleaner than adding a new RR type.

On Tue, Aug 15, 2017 at 11:28:41AM -0700, Paul Vixie wrote:

> > This WG has already spent years trying to rearchitect the A/AAAA lookup.
> 
> that goal has been sought since longer than this wg has existed.
> 
> however, adding the other kind of address record to the additional data
> section is something anyone can do, it breaks nothing, it will only be used
> opportunistically.
> 
> adding it to the answer section would be more problematic.
> 
> but no rfc is needed to give permission, and since these records could be
> signed and can in any case be cached, the impact would be immediate.

With no need to change stub or caching resolvers.  Just the
authoritative servers can be upgraded incrementally.  Though
multi-stage caches might benefit from similar logic in the upstream
cache.  This has a clear advantage over introducing new query types.

-- 
	Viktor.