AS8681 – JT : IPv6 Deployment

Home : Peering Policy : IPv6 : BGP Communities via IPv4


IPv4 defines a 32-bit address. This means there are 2^32 (4,294,967,296) unique IPv4 addresses available. This may sound like a big number but unfortunately on a global scale it isn’t, and most of the available IPv4 address pool is already allocated and the Internet is simply running out of IP addresses.
The address shortage problem is aggravated by the fact that portions of the IP address space have not been efficiently allocated. Current estimates put IPv4 depletion around 2011.

In anticipation of the scalability problems with IPv4, the Internet Engineering Task Force (IETF) has produced a comprehensive set of specifications that define the next generation Internet Protocol known as IPv6. IPv6 is based on 128-bit addresses, creating a much larger address pool.

  • Total IPv4 Addresses : 4,294,967,296
  • Total IPv6 Addresses : 340,282,366,920,938,463,463,374,607,431,768,211,456
  • IPv4 Addresses per Customer : 1
  • IPv6 Addresses per Customer : 18,446,744,073,709,551,616

Once fully deployed, IPv6 should solve the IPv4 address shortage and enable a huge number of new applications ranging from mobile communications, home automation and high-definition video.

Engineering Deployment

JT is currently performing a limited Engineering Deployment of IPv6 across its IP/MPLS core infrastructure.
The purpose of the deployment is to provide greater manageability and survivability for its own infrastructure as well as to provide
a platform for the development of new IPv6 products and services. This should give JT a head start when full-scale commercial
IPv6 deployment is required in the future.

  • AS8681 IPv6 Assignment : 2a02:c28::/32

The deployment is fully dual-stacked and is being carried out using MT ISIS and BGP. Each BGP-speaking device within AS8681 will carry the full IPv6 routing table.

JT intends its IPv6 connectivity to be at least as reliable as its existing IPv4 infrastructure and connectivity, and thus uses no tunneling or other
interim transition technologies on its core network and accepts only native peering and transit.

Public Peering

JT is actively seeking new IPv6 peering relationships with other networks across the London Internet Exchange (LINX). We also participate in the LINX Multi Lateral Peering (MLP) Route-Server.

  • LINX Brocade : 2001:7f8:4::21e9:1
  • LINX Extreme : 2001:7f8:4:1::21e9:1

Please contact to request a session.