On 06/11/2018 04:07, Joe Abley wrote:
Specifically, I s the wildcard owner name a real problem in the grand
scheme of things? I understand that wildcards are used by some people
for names that feature in HTTP URIs, but I'm struggling to imagine
using a wildcard at a zone cut; [...]
You're not wrong, because most often the wildcard is indeed a label
below that cut.
However, the intent is that this record would eventually replace *all*
use of CNAME for web redirection regardless of whether at the zone cut
or not.
This isn't a wildcard example, but here's a re-post of a currently
impossible zone configuration from one of my emails Sunday:
$ORIGIN example.com
@ IN SOA ...
IN NS ...
company-division IN MX <company mail system>
company-division IN CNAME <cdn web host>
Replacing that CNAME with HTTP makes this configuration possible.
To be clear, the rules are clear and you should feel as empowered as
anybody to apply for an early assignment of an RRTYPE and start
writing code. If I sounded like I was arguing against that I
definitely apologise!
No worries! :)
However I think that a more coordinated approach that involves people
from both web and DNS communities to understand the problem space is
more sensible, though, and more likely to be productive for this
working group. It's not clear to me that either community has a great
track record just guessing at what the other one wants.
I've been actively socialising this with web people since Saturday even
before the draft was submitted. I'm going to be talking about it
briefly at HTTP-bis this morning.
This draft is IMHO not so much a "guess", but a "starting point" based
on what web folks said at the side meeting in Montreal.
Yes, it'll require browser implementors to update their code, but the
alternative is breaking the camel's back.
cheers,
Ray
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
