This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/address-policy-wg@ripe.net/
[address-policy-wg] Policy Change Request - Allow address allocations for anycast DNS operation
- Previous message (by thread): [address-policy-wg] Policy Change Request - Allow address allocations for anycast DNS operation
- Next message (by thread): [address-policy-wg] Policy Change Request - Allow address allocations for anycast DNS operation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andreas Bäß/Denic
baess at denic.de
Wed Jun 9 14:26:04 CEST 2004
> It depends on how tight we want to knit the mesh (and emphasise > conservation et.al. :-) That is indeed the question that we have to agree to. > >I thought that those who are attracted by the policy will have no problem > >justifying it and RIPE would have no problem to ask people returning the > >networks if they do not use them as stated in the policy. But maybe > >my thinking is too positive here. > I guess everything which essentially gives you easy access to a PI /24 > (/32 for that matter in the long run) is going to attract interest, at > least eventually. > > Thus here are my questions for double-checking my own mental picture and > assumptions: > > - the applicant has to be an established LIR - correct? I have don't think that this should be an imperative. Do you really think that LIRs should not be able to request such an allocation on behalf of a customer that would like to do that? > - as setting up a server and finding slaves, plus anycast in general is > not really rocket science: is there any closer definiton of "Operators > providing DNS for a zone served by a number of name servers..." - > would my own domain (say - netcraft.at) qualify as well? If I recall it correctly we have opened the intial qualification from TLD DNS operators to a broader scope knowingly to include those who feel that their DNS operation is important enough for them to run this kind of infrastructure in that particular way i.e. anycasting with a number of NS that would break the 512 limit in a "signifacant" number of responses. What I have heard so far the expected number of requests for this kind of allocations will be in a range that most believe that it is not necessary to knit the mesh too tight but give a credit to the applicant. > - and trying to reclaim that address space would be pretty cumbersome > for both parties, I guess, unless the zone (all zones on those > servers?) go(es) away _completely_ ?! If someone finds it cumbersome to renumber because he has to return the resources granted to do dns anycasting he probably should not apply for this resource ;-) Cheers Andreas
- Previous message (by thread): [address-policy-wg] Policy Change Request - Allow address allocations for anycast DNS operation
- Next message (by thread): [address-policy-wg] Policy Change Request - Allow address allocations for anycast DNS operation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]