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 proposal: #alpha: TLD Anycast Allocation Policy
- Previous message (by thread): [address-policy-wg] Policy proposal: #alpha: TLD Anycast Allocation Policy
- Next message (by thread): [address-policy-wg] Policy proposal: #alpha: TLD Anycast Allocation Policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Iljitsch van Beijnum
iljitsch at muada.com
Thu Mar 24 11:13:36 CET 2005
On 24-mrt-05, at 9:53, Wilfried Woeber, UniVie/ACOnet wrote: > But "per default" when you announce something in v6-world, you are > "supposed" to announce a /32 Yes. > (or maybe a /35) No, certainly not those. > _and_ filter anything that is longer than that. That's what it says in the documents but then ARIN started to give out /48s so this policy doesn't work anymore. (Noboby bothered to change the documents that say it's ok to filter, though.) So the can of complexity worms has been opened, wasting address space (even though there is a lot to waste) has no upside anymore. Also, for reasons of flap dampening exceptions and the like it's good to have these addresses in a single block.
- Previous message (by thread): [address-policy-wg] Policy proposal: #alpha: TLD Anycast Allocation Policy
- Next message (by thread): [address-policy-wg] Policy proposal: #alpha: TLD Anycast Allocation Policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]