[address-policy-wg] PI for Not-DNS Anycast.
- Previous message (by thread): [address-policy-wg] PI for Not-DNS Anycast.
- Next message (by thread): [address-policy-wg] PI for Not-DNS Anycast.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Joao Damas
Joao_Damas at isc.org
Tue Jun 12 23:23:38 CEST 2007
On 12 Jun 2007, at 22:58, Andy Davidson wrote: > > Hi, > > Can I get the community's thoughts on this, please .. > > I think we have a well defined policy on what to do when someone > needs some PI in order to run an Anycasted DNS service. We set out > a family of requirements based on geographic diversity, for > instance, that clearly states what should be in place when a > request for PI for DNS use is made. > > What if a company wants to try to deploy an anycasted production > service for something which is not DNS ? It could be a proprietary > protocol, or something standard like http. Is the community view > that they should just deaggregate some of their PA - which I don't > like the sound of - or apply for PI in the normal way, and pretend > anycast isn't necessarily involved ? They could also state their case in this wg. Sounds far more reasonable. Joao Damas
- Previous message (by thread): [address-policy-wg] PI for Not-DNS Anycast.
- Next message (by thread): [address-policy-wg] PI for Not-DNS Anycast.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]