| > 4. Routing Policies for the 6bone This document describes the use of 3ffe::/16 space: The 6BONE. | Does that one apply for people using 2001:: space? No. | 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! The 6bone is a layered network on top of the current public IPv4 networks, where people in the early 90s started testing their protocol implementation mainly using 5f and 3f (top 8 bits) prefixes. It grew, policy was made, people joined the 6bone to test on ISP rollout and such things. Due to the costs involved with LIR allocation (either pay ARIN, or pay an engineer to fight with RIPE for 4 months), lots of people stuck to 6bone space. It is sequentially allocated by Bob Fink (fink@es.net) and the DNS is maintained by Bill Manning (bmanning@isi.edu) who also maintains a global '6bone mailinglist' which discusses lots of technical issues from time to time. It's a majordomo@isi.edu list called '6bone'. The problem is: people on the 6bone are not always operators. Some are kids with cablemodems announcing to their (tunneled) peers origins as 64001 or networks that have never been allocated in the first place. Another strange situation is that because nobody had a decent shared medium to create native IPv6 peerings in the old days, people would erect tunnels to just about everywhere. For example, an Amsterdam based company would peer over a tunnel to someone in California and in New York. Because the AS path lengths are almost always NOT an indication on how the traffic flows, traffic simply bounces around everywhere and not taking the optimal routes. This should be avoided of course in the production network (which still tunnels quite a bit, of course). | Just being curious... :-) I sometimes envie you for not knowing what the 6bone is. And to come back to RFC2772, I was always a strict filter person and kick and stomp any of my peers that feed me crap, but after recent events (ripe42 is one of them) I am strongly thinking on easing my filters up a little to allow for /48 to make it into my route tables. groet, Pim -- __________________ Met vriendelijke groet, /\ ___/ Pim van Pelt /- \ _/ Business Internet Trends BV PBVP1-RIPE /--- \/ __________________