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/[email protected]/
[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 ]
Alexander Koch
koch at tiscali.net
Thu Mar 24 11:34:08 CET 2005
On Thu, 24 March 2005 11:13:36 +0100, Iljitsch van Beijnum wrote: > > _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.) Strongest argument so far. Besides the point that I agree with the argument a /32 is probably oversized, be it v6 or not. Now that we have to take special care of the filters we place anyway, why not do one approach, and that's pretty much it. > Also, for reasons of flap dampening exceptions and the like it's good > to have these addresses in a single block. Yes, excellent point, I agree with that for sure! I do not want to think of some fancy BGP Flap Damping advisories that gives me 7 /32 blocks I should not be damping or so. Argh. Regards, Alexander -- Alexander Koch <koch at tiscali.net> / ako4-ripe Phone +49 6103 916 480, Fax +49 6103 916 464
- 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 ]