Original message From: 神明達哉
> In my understanding of the discussion we all agree that it will take a> very
> long time until we have B. So, in the end, the deployability
> seems to depend on how soon we can have situation A and how convenient> the
> implementations are. It
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Domain Name System Operations WG of the IETF.
Title : Extended DNS Errors
Authors : Warren Kumari
Evan Hunt
At Fri, 21 Sep 2018 12:03:13 +0100,
Tony Finch wrote:
> > Perhaps primary server implementations may eventually have some level
> > of support that makes this provisioning much less painful (in a way
> > other than performing on-demand resolution). If and when many popular
> > implementations
On 21 September 2018 at 09:12, Dan York wrote:
>
> I do think this is a path we need to go. We need *something* like CNAME
> at the apex. Either CNAME itself or something that works in the same way
> but might have a different name.
>
I would still like to see something SRV-like for HTTP, but
On Sep 20, 2018, at 2:13 AM, Mukund Sivaraman
mailto:m...@mukund.org>> wrote:
SRV is most elegant. IMO we should push the resolver-side CNAME handling
change through so one day in the future it is available widely.
+1
I do think this is a path we need to go. We need *something* like CNAME
神明達哉 wrote:
>
> I'm not sure how we can expect this model to deploy in practice. With
> this model, the zone admin will need to develop an additional script
> or something integrated into whatever the provisioning framework they
> are using. Is that the assumption?
I would like it to be
I think people here may be intereted in this draft as well. Comments are
welcome.
Davey
-- Forwarded message -
From: Davey Song
Date: Fri, 21 Sep 2018 at 14:31
Subject: Fwd: New Version Notification for
draft-v6ops-xie-network-happyeyeballs-00.txt
To:
Hi folks,
I just
