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] New AS Number Block allocated to the RIPE NCC
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Iljitsch van Beijnum
iljitsch at muada.com
Wed Mar 2 14:55:17 CET 2005
On 2-mrt-05, at 14:46, Nils Ketelsen wrote: >> Keeping the aggregate up isn't hard to do > Making a backup, that still relies on the first provider to work is > only of > limited use. I want a backup, that also works if Provider1 loses all > his > peers, burns down, goes bankrupt etc. Another party can set up a route server at an exchange point that injects a backup route for the aggregate, or multiple ISPs can share an aggregate. The specifics aren't all that interesting, the point is that there are more ways to skin a cat than doing everything the way we always did but now with longer addresses.
- Previous message (by thread): [address-policy-wg] IPv6 access to K-root
- Next message (by thread): [address-policy-wg] New AS Number Block allocated to the RIPE NCC
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]