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] RE: Question
- Previous message (by thread): [address-policy-wg] RE: Question
- Next message (by thread): [address-policy-wg] RE: Question
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Maxim V. Tulyev
maxtul at merezha.net
Thu Apr 20 11:08:20 CEST 2006
Hi, > (thanks for doing proper quoting - which is *below* *properly trimmed* > original articles) This sticks to me as the good FIDONet behaviour ;) > > it does _NOT_ work for IPv6 in the wild, by the way. > Well, YMMV, but my customers claim "it does work" - with IPv6, and in > the wild. I tried to announce network 2001:4058::/48, and in fact, I couldn't get working connectivity. Of course, if you have two channels, and one of them also announces entire /32, it will be "seems to work", because you will get incoming traffic from there. But if that channel fails, you will lose connectivity at all. So, why? Local peerings? Something else? That's NOT like PI or more specific IPv4 that can be announced and is working in the wild as an independent part of Internet. -- WBR, Maxim V. Tulyev (MT6561-RIPE, 2:463/253 at FIDO)
- Previous message (by thread): [address-policy-wg] RE: Question
- Next message (by thread): [address-policy-wg] RE: Question
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]