On Tue, Mar 26, 2019 at 7:23 PM Brian Dickson > We need to start with the base requirements, which is, "I want an apex RR > that allows HTTP browser indirection just as if there was a CNAME there". > Sibling records do not behave like CNAMEs, no matter what extra hacks get > applied; CNAME processing is done by the resolver. > The options are, new RRtypes that require resolver upgrades, or RRtypes that > are handled by the client application (browser), which benefit from (but do > not require) resolver upgrades. >
I see a huge problem there, let's call it IPv6 problem. During the transition phase to this new RR we need to have a fallback, right? How long do we need to have that fallback for old resolvers and browsers? I'd say approximately until DNS has been replaced by some other tech. If we are lucky DoH would solve it by doing what those previously mentioned companies are doing now on their servers, but then we would cry again that it's the wrong solution. _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
