Re: [DNSOP] draft-wkumari-dnsop-alt-tld-04

2015-02-13 Thread Ed Pascoe
I like this draft and I think the sooner this becomes a reality the better. Its seems like every other week there a new application that adds "dns discoverability" via a made up root zone. Combine this with the new round of TLD applications that are expected in the next year or two and its going t

Re: [DNSOP] call for adoption: draft-vandergaast-dnsop-edns-client-subnet

2015-02-13 Thread Peter DeVries
My dayjob supports this as well and has been running resolvers with similar functionality implemented for a while now. We are looking to switch to edns-clent-subnet once it is standardized and have been approached by parties willing to invest in development. Peter On Thu, Feb 12, 2015 at 1:51 A

Re: [DNSOP] call for adoption: draft-vandergaast-dnsop-edns-client-subnet

2015-02-13 Thread Marcus Grando
Thinking more about this I figure out some things. First, the resolver query needs to include ECS and can't be a regular query, that's need to verify end to end ECS support, but I think it's not a big problem. I think we need a official way to detect if authoritative has support or not and it need

Re: [DNSOP] draft-wkumari-dnsop-alt-tld-04

2015-02-13 Thread Edward Lewis
What Paul mentions below raises the specter of name collisions - the activation of a name resulting in undermining a errant system which, until the activation, wasn’t all that bothered by the name being inactive. Search lists have been one root cause suggested and sometimes even observed as contri

Re: [DNSOP] call for adoption: draft-vandergaast-dnsop-edns-client-subnet

2015-02-13 Thread Livingood, Jason
On 2/13/15, 9:05 AM, "Livingood, Jason" mailto:jason_living...@cable.comcast.com>> wrote: we've got running code in bind. and no doubt other product. Should be also in Nominet’s resolver. BTW, I meant NomiNUM not NomiNET. Darned Nomi* names. ;-) JL _