Pim van Pelt <pim@bit.nl> writes:
| What is "the 6bone" anyway? I find it strange that somebody who is at ripe meetings presenting routing table information (and brokenness) never took the time to actually find out what 'these weird 3ffe' addresses are!
You completely missed Gert's question. Of course he knows what 3ffe is, but that was not the question. The question was how to precisely define it, in nowadays reality,
| Just being curious... :-) I sometimes envie you for not knowing what the 6bone is.
You still didn't define what the 6bone comprises. Any site which received an allocation? Wait, that's not sufficient since you can have a pNLA/pSLA without allocation. Any site which announces 3FFE prefixes? Well, then not all of them are bound by the agreement. Any site with a entry in the 6bone whois? Can I sign the agreement and not announce /48 to other 6bone sites, but announce to non-6bone sites? Back to the original question: I'd rather take Pekka's more practical approach and say that even the 6bone rules make allowances for e.g. a /48 announcement from RIPE as long as it's scope is limited. Allow it to be announced by RIPE to direct peers, and from them to their customers, but don't give any guarantee that it is globally visible. For true global multihoming of important services like whois, techniques can be used that work in IPv4 already: get two assignments, two AAAA records for the services, and possible some DNS magic with short TTLs and an "intelligent" DNS server to turn off AAAA answers if that uplink is seriously broken. Robert