[address-policy-wg] 2008-05 Anycast for DLV zones

On 22 Jun 2009, at 09:27, Florian Weimer wrote:

>>> Which part of the Internet depends on it?
>>
>> See above. Pretty much anything doing lookups in e164.arpa: Asterisk
>> servers, various other SIP services, VoIP providers, smartphones,  
>> etc.
>> ENUM may have a low usage. But unlike DLV, ENUM is not just for
>> consenting adults: everything and anything can do an ENUM lookup
>> straight out of the box.
>
> I don't think this is how things work.

It is. Compare and contrast the effort needed to setup DLV (and make  
it work) on a DNS server with that needed for an ENUM lookup. Now do  
the same thing for on-going maintenance and administration of both  
technologies. Why this discussion has popped up in address-policy-wg  
and not dns-wg is "interesting"....

Anyway, I fail to see what point you're making or what relevance it  
has. Please don't bother to do that now: I'm long past caring. FWIW  
any clarifications you provide probably shouldn't go to this list.  
Discussions about ENUM query rates are best taken to the ENUM WG or  
maybe the DNS WG.

There's a consensus here to have anycast allocations for Tier-1 ENUM  
delegations. It's not clear whether you agree or disagree with that.  
You've never said either way: at least not that I remember. Instead,  
you've tried to open up a rat-hole about making DLV a special case.

When you suggested DLV zones deserved anycast allocations, nobody on  
this list appears to have been in favour of that. IIRC few people  
explained why DLV zones did not merit these allocations. At least not  
at present. That looks to be the consensus position, not that I speak  
for this list/WG of course.

I also note that although you seem keen to open up and explore rat- 
holes, you're not coming forward with anything constructive: eg  
amended text for a policy proposal or even new drafts in support of  
your point of view. This is not productive. I strongly suggest you end  
this discussion -- what have DNS query rates under e164.arpa got to do  
with address allocation? -- or take it somewhere else. It's no longer  
relevant or appropriate for address-policy-wg at ripe.net.

To summarise, the recent updates to the NCC's address policy allow for  
anycast allocations to be made for "important" DNS zones: TLDs and  
Tier-1 ENUM delegations. These are considered  to be critical  
infrastructure (for some definition of that term), not just by the  
technical community but by governments and regulators. It is therefore  
responsible and prudent for the NCC to have an addressing policy that  
facilitates a technology (anycasting) which can improve the robustness  
and stability of those important DNS zones.

DLV is not considered as important by these communities. At least not  
yet. If and when DLV gets that recognition, or appears to be getting  
it, that will be the time for amending the address policy to  
accommodate anycast for DLV. This of course does not stop someone like  
ISC using a chunk of their existing address space to provide anycast  
service for dlv.isc.org (or whatever). IMO, it's up to the DLV  
cheerleaders to make the case that their zones are "important" enough  
to deserve special anycast allocations. That case has still to be made.