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] 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
Mon Feb 28 17:49:24 CET 2005
On Mon, Feb 28, 2005 at 05:14:56PM +0100, Elmar K. Bins wrote: > > You can also ask the other transit upstream to announce your /48 for > > you. > > Mind you, I prefer to advertise myself, and, as discussed, am in the > lucky position that my transit ISPs are reasonable. Unfortunately this mainly leads to bad connectivity as half of the IPv6 world filters /48. Results are overly long AS_PATHs and really ugly transit connections upteen times over the big ponds. Not in your case as you can peer directly at DECIX and Space.Net's quite well connected upstream Tiscali doesn't filter, but for other /48 wannabe-multihomers this looks MUCH worse. Random example: http://www.sixxs.net/tools/grh/lg/?find=2001:418::/32 PA more-specific "multihoming" is _not_ a solution. If your link to the PA-space providing ISP is down, you're unreachable from a lot of sites. And routing problem debugging becomes a major pain. Anyway, this isn't about DNS nameserver anycasting anymore, so... :-) 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 ]