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 ]
Iljitsch van Beijnum
iljitsch at muada.com
Wed Mar 2 12:15:59 CET 2005
On 2-mrt-05, at 11:45, Daniel Roesen wrote: > What do you do against intradomain routing problems? Loops? DDoS > congestion? Read my book, it's all in there. > 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. I appreciate that having your own prefix in the global table makes lots of stuff easier, but what if everyone wants this? It just doesn't scale. As for the DoS issue, your transit ISPs can create blackhole communities so you can have them blackhole the traffic for individual /32s (if desired) when those are under attack by announcing even more specific more specifics with this community on them.
- 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 ]