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] Anycasting for TLDs and ENUM
- Previous message (by thread): [address-policy-wg] Anycasting for TLDs and ENUM
- Next message (by thread): [address-policy-wg] The final /8 policy proposals (2008-06 and 2009-04)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Masataka Ohta
mohta at necom830.hpcl.titech.ac.jp
Mon Jun 22 14:52:20 CEST 2009
Jim Reid wrote: > To get back to the anycast allocation provisions, the new policy says > these allocations are for DNS service for TLDs and ENUM Tier-1 > delegations. So if the holders of these blocks used them for other > things, they'd presumably be in violation of that policy. For essential services, it's fine to allocate an entire /24 or /16 for an anycast address that there is no point to have address blocks for multiple anycast addresses. Masataka Ohta
- Previous message (by thread): [address-policy-wg] Anycasting for TLDs and ENUM
- Next message (by thread): [address-policy-wg] The final /8 policy proposals (2008-06 and 2009-04)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]