The following routing policy should be applied by the networks connected to the M6Bone.

1. Aggregation and prefixes filtering

1.1. End-Sites

The end-sites connected to the M6Bone should at least advertise their site prefix (/48), even if IPv6 multicast is not available in the whole site. Any prefix longer than /48 will be filtered in the rest of the network.

1.2. ISPs providing an IPv6 multicast service

The ISPs providing an IPv6 multicast service must perform the same aggregation they do for IPv6 unicast.

They must not advertise the prefixes of their customers (/48) but the prefix allocated to the ISP.

1.3. Networks offering transit

As IPv6 multicast is in most of the cases not yet available as a service by ISPs, many sites connect to the M6Bone directly, bypassing their local ISP via an IPv6 multicast tunnel.

The prefix of these sites (/48) has to be routed in all the M6Bone, as no aggregation can be done by the site’s ISP.

ipv6 prefix-list m6bone-transit seq 5 permit 2001::/16 le 48
ipv6 prefix-list m6bone-transit seq 10 permit 3ffe::/16 le 48

2. BGP peerings

Networks connecting to the M6Bone must use public Autonomous Systems. Private AS are not accepted, or aggregation performed by ISPs should remove these AS from the global IPv6 multicast BGP table.