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] IPv6 access to K-root
- Previous message (by thread): [address-policy-wg] IPv6 access to K-root
- Next message (by thread): [address-policy-wg] IPv6 access to K-root
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Roesen
dr at cluenet.de
Wed Mar 2 11:45:29 CET 2005
On Wed, Mar 02, 2005 at 11:38:50AM +0100, Iljitsch van Beijnum wrote: > >Doing more-specific multihoming makes ONLY sense when planning to > >filter > >them at some point in time. Unfortunately at exactly this point, this > >scheme fails. This cannot be fixed in time and with education, this is > >a very fundamental problem of this approach. > > No, it's not. Keeping the aggregate up isn't hard to do, and all the > other stuff is even easier. "isn't hard to do". Yeah, I have seen vomitting horses, right in front of the pharmacy. With prescription in their mouth. What do you do against intradomain routing problems? Loops? DDoS congestion? With proper BGP multihoming you (as end site) can just withdraw your announcement via this problematic uplink. Doesn't help you with more-specific pseudomultihoming and people filtering the more-specific. Traffic to you still ends up in the problem area. Regards, Daniel -- CLUE-RIPE -- Jabber: dr at cluenet.de -- dr at IRCnet -- PGP: 0xA85C8AA0
- Previous message (by thread): [address-policy-wg] IPv6 access to K-root
- Next message (by thread): [address-policy-wg] IPv6 access to K-root
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]