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] Policy Change Request - Allow address allocations for anycast DNS operation
- Previous message (by thread): [address-policy-wg] Policy Change Request - Allow address allocations for anycast DNS operation
- Next message (by thread): [address-policy-wg] Policy Change Request - Allow address allocations for anycast DNS operation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andreas Bäß/Denic
baess at denic.de
Fri Jun 11 16:55:06 CEST 2004
> >> Don't you think the policy ought to be more relaxed and allow the > >> server manager for the zone to decide how many of their servers they > >> want to anycast? > > > > i think the point intended is that the address space *must* be used > > for anycast, and not just another address grab. yes? > Well, no one doubts that is the intention here, that is why I suggested > a different wording earlier, so the motivation is clear. My question > is, why limit it to anycast one of the servers? Can you help me and explain what the advantage of offering multiple anycast servers in comparison to a single anycast server is? Andreas
- Previous message (by thread): [address-policy-wg] Policy Change Request - Allow address allocations for anycast DNS operation
- Next message (by thread): [address-policy-wg] Policy Change Request - Allow address allocations for anycast DNS operation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]