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] PI for Not-DNS Anycast.
- Previous message (by thread): [address-policy-wg] 2007-05 Discussion Period extended until 9 July 2007 (IPv6 ULA-Central)
- Next message (by thread): [address-policy-wg] PI for Not-DNS Anycast.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andy Davidson
andy at nosignal.org
Tue Jun 12 22:58:53 CEST 2007
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 ? Many thanks Andy
- Previous message (by thread): [address-policy-wg] 2007-05 Discussion Period extended until 9 July 2007 (IPv6 ULA-Central)
- Next message (by thread): [address-policy-wg] PI for Not-DNS Anycast.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]