On 4 Nov 2018, at 11:10, Ray Bellis wrote: > -1
:-) > What are the semantics of this? The semantics is exactly like a CNAME + HTTP Redirect. Provisioning is like any provisioning in the DNS, with the advantage that you can delegate the prefix:ed domain just like you can do with any _tcp and similar prefix domain to whatever administrative entity that manage the web. You can that way separate the DNS and web administration between two different entities. That some people want a record at the apex is a big mistake as one that way must mix explicitly the administration of that name between two entities that do different things. See how well the AD delegation works where you can split the AD functionality from the DNS functionality by doing "the right delegations", which makes enterprise DNS much easier to set up than if (more) stuff is to be entered at the apex. We have apex overload, and that must be taken care of. Patrik > - What appears in the user's UI when the URI record completely replaces the > site name entered by the user? > > - Which domain name is the SSL cert validated against? > > - Which domain name appears in the HTTP Host: header? > > - What is the HTTP "Origin" of the resultint content, > and which domain's cookies are accepted / sent? > > - What if there's also a URI record for 'example-lb-frontend.hosting.namn.se' > ? > > - How do I provision a wildcard record for this? > > I see absolutely zero chance of the web community embracing this. > > Ray > > _______________________________________________ > DNSOP mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dnsop
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
