[address-policy-wg] 2008-05 New Draft Documents Published (Anycasting Assignments for TLDs and Tier 0/1 ENUM)

Hi all,

1) I fully support this policy to move forward. As a matter of fact,
 AFNIC is preparing an in-house Anycast solution, to be deployed soon
 for a first group of nodes. Later, we intend to deploy other groups
 and we will then need to rely on this policy to ask for extra
 Prefixes. Btw, for our two other running Anycast groups, our choice
 is a priori to let the Anycast operator ask for address resources
 they need (a way to mutualize those resources among their customers,
 thus less address consumption globally).

2) I don't have a strong opinion on using or not "Critical
   infrastructure expression. Nonetheless, I would prefer we rather
   avoid that expression in this kind of document (I know it's too
   late for DNS Root Servers). This might be interpreted by some
   publicauthorities as an elevation of the TLDs DNS service to a rank
   of other well-known "Critical infrastructures" like Water or
   Electricity. I'm not sure we have reached that level of criticity
   equivalence today, nor am I sure that TLD operators want to spread
   this perception nowadays. Instead, maybe something less
   "loaded/exposing" such as "Key/Essential service/infrastructure"
   (choose a combination as you like) would be more appropriate for
   this document.

Cheers,

Mohsen.

 On 16 Apr, Peter Koch wrote:
 | On Thu, Apr 16, 2009 at 09:00:36PM +0900, Randy Bush wrote:
 | 
 | > i like "critical infrastructre."  this is because, while i understand
 | > that the roots need golden space, and i can almost see that anycasted
 | > services need micro-allocations, i do not feel that tlds per se are
 | > critical in the sense that they need golden space.
 | 
 | that would suggest an external reference to the term and other evaluation
 | criteria than those proposed.  Also, could you elaborate on the difference
 | between "micro-allocations" and "golden space"?
 | 
 | > there is a reason the dns maps from names to addresses.  use it.
 | 
 | Sure, we use anycast to support performant and resilient mapping.
 | 
 | -Peter

-- 
--
//===================================================================\\
| Mohsen Souissi             		             	              |
| AFNIC - Responsable R&D                                             |
| Mohsen.Souissi at nic.fr  | Tél./Fax : 01 39 30 83 40 / 01 39 30 83 01 |
\\===================================================================//