#1 - support doing the work to finalize the edns-client-subnet standard. now... (I hope my inline response is accepted by the readers of this wg's list, I would note that someone's quoting is all jacked up... oh well)
<pull up waders> On Thu, May 8, 2014 at 12:17 PM, Paul Vixie <p...@redbarn.org> wrote: > > > Ralf Weber wrote: > > ... > > There is madness, but the madness is in mixing authoritative and recursive > functions in one server and not in using DNS to direct traffic. > It seems, to me at least, that a bunch of the problems with dns 'tricks' which are more than: "Oh good, my zone loads! Lookey, I have an A record! what is an A record again?" are that folk should not play with sharp knives if they aren't prepared to get cut occasionally. Ideally you understand the implications of tricks like: bind views dns anycast edns-client-subnet etc before you deploy them... That's all beside the point of good documentation being available to support inter-operability between vendor code for these features though. Should the IETF mint a standard for 'feature-X' in the software system that makes up the DNS? Where's the bar used to measure whether or not a feature has critical enough mass/interest to be written up? Should all feature ideas get adopted and then those which prove to wither be permitted to die out before WGLC? > > while i'm on record has holding that view, it turns out that RFC 1035 does > describe recursion and authority as co-residing in a server. so while this > is in my view a dangerous practice and a bad idea, it's well supported by > the scriptures. > > > After all that's what all lookups do, give you an IP address you connect to. > > > i don't think so. dns lookups have many purposes unrelated to returning IP > addresses. i'd like to see 100 more things like SSHFP this decade. ah, so you seem to be in the camp of 'let a thousand flowers bloom' or whatever... that seems like fun as well. Back on topic though, should the edns-client-subnet work get attention and potentially move forward in this WG? -chris _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
