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] 2008-05 Anycast for DLV zones
- Previous message (by thread): [address-policy-wg] 2008-05 Anycast for DLV zones
- Next message (by thread): [address-policy-wg] Anycasting for TLDs and ENUM
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
michael.dillon at bt.com
michael.dillon at bt.com
Mon Jun 22 13:20:00 CEST 2009
> This of > course does not stop someone like ISC using a chunk of their > existing address space to provide anycast service for > dlv.isc.org (or whatever). IMO, it's up to the DLV > cheerleaders to make the case that their zones are > "important" enough to deserve special anycast allocations. Your example is essentially saying there is no barrier for a holder of an anycast address block, to offer more than one anycast service from that block. I think that address policy should be addressing that general case of an anycast network services provider rather than dealing with various special cases of applications that require anycast network services. --Michael Dillon
- Previous message (by thread): [address-policy-wg] 2008-05 Anycast for DLV zones
- Next message (by thread): [address-policy-wg] Anycasting for TLDs and ENUM
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]