Native IPv6 peering
Since October 2000 Cable & Wireless offers native IPv6 peering at the INXS. For the Beta phase, it was a seperate VLAN and all members who wanted to set up IPv6 peerings were required to install an extra port in their routers or to install a second box at the INXS for the connection to the IPv6 peering LAN.
Since 2003, the VLANs for IPv4 unicast and IPv6 unicast have merged. Hence an additional port is not longer required for IPv6 Unicast peering.
Requirements for IPv6 Peering at the INXS
- Anyone who wants to peer IPv6 at the INXS must be a regular INXS member.
- The interested party must have an allocation received from one of accredited RIRs (RIPE, APNIC, ARIN) - A 6bone pTLA is not sufficient!
IPv6 addressing on the INXS peering LAN
| Prefix | Usage |
|---|---|
| MUC unicast: | 2001:7f8:2c:1000::/64 |
| MUC multicast: | 2001:7f8:2c:2000::/64 |
the following description should make it very easy for members to find out their peering LAN addresses for both IPv6 unicast and multicast:
- 2001:7f8:2c:1000::A5AA:AAAA:P
-
- A- ASN Field
- This field has a leading A5 (symbolic for "AS") followed by the ASN of the member representing this ASN in decimal form with leading zeroes.
- P- Port
- is an enumerator for the members INXS port (to support multiple peering ports)
The following example 2001:7f8:2c:1000::A501:2345:1/64 would according to the addressing scheme be the peering LAN IP in Munich, used for IPv6 unicast, and the member uses ASN 12345 and uses this IP address on the members first port.
Addresses from the blocks 2001:650:0:200::/64 and 2001:650:F807::/60 must be returned.
For changes in the reverse DNS zones, please send us an e-mail with the fully qualified domain-name.
If you have any questions, please contact us via e-mail at info@inxs.de.