BT 21CN Network IPv6 Transformation Mircea Pisica IP and Data Architect 21CN, Global Networks & Computing Infrastructure BT Innovate and Design 14 Dec 2010 Ghent Belgium
Agenda BT 21CN Overview IPV6 on BT 21CN Platforms
Our 21 st Century Network Vision 21CN is the foundation for BT s transformation to a global, customer-centric and software driven communications partner Delivering next generation communications services and capabilities that enable our customers to achieve more It provides customers with greater direct control of their services through automation and self-service And enabling our customers to innovate on BT s platforms, themselves or in collaboration with BT
Global 21CN Platforms: Three layers
IPv6 Network Transformation objectives BT s OSS, BSS, SDKs & 3 rd party apps APPS Consolidation Standardisation Virtualisation Network Computing Storage ++ Cloud Services BT & non-bt customers UK Global Global Global Global Global UK Global Networks & UK platforms Data Centres IPv6 enabling NETWORKS COMPUTING Global Cloud Content Centres ONE Global Network platform fibre Exchanges Multi-service node In 1,500 Global sites Cloud centre = exchange + data centre
Enable IPv6 on UK &Global Infrastructure and services Network Application Services IP Contact Centre SIP Trunking Hosted VoIP UC Conferencing Telepresence Application Acceleration Product: AAI Global Mobility Apps Cloud Storage IP4/IPv6 Based Applications Business Application Delivery Cloud Compute NNIs 3 rd Parties Cloud & Content Federations Infrastructure Services Virtual Private Cloud & Public Cloud Network & cloud services SDK Voice CDN SIP & Content Peering Infrastructure Ethernet VPN Common Access Aggregation (Packet Based) IP VPN (6VPE) Packet Core (MPLS) (dual stack) Optical Transport (WDM) Peering VPN NNI (IP & Ethernet) : Peering & Transit Leased Ethernet or Lambda/Fibre
Agenda BT 21CN Overview IPV6 on BT 21CN Platforms
IPv6 on BT s platforms 21CN (21st century network) Summary notes: We are implementing IPv6 on 21CN platforms not necessarily because we can afford it, but because we can t afford not to. There is NO IPv6 transition at once rather seen as integration of IPv6 on existing IPv4 routed networks/ platforms or end-devices. Over 90% of the installed IP Hardware within 21CN Platforms is IPv6 capable Align IPv6 development strategy to 21CN Transformation strategy. Performed detailed IPv6 feasibility studies and analyze risks within each 21CN Platform/Service
IPV6 Overview within BT networks Many ways to deliver IPv6 services to end users, most important is end to end IPv6 traffic forwarding as applications are located at the edge Service providers and enterprises may have different deployment needs and mechanisms but basic steps are common Establish an IPv6 Addressing strategy (avoid errors from early IPv4 use of BT Diamond IP IP Control) Evaluate the Routing and Signalling protocol(s) Scalability and Convergence IPv6 services (QoS, Multicast, Mobility, DNS, Broadband, Voice/IP, Video, Content, Cloud Computing ) Backbone Security and Firewalls (extra licences for IPv6) Network management Use IPv4 only or Dual Stack (increase security) Resources are shared between the two protocols (IPv4 and IPV6) for both Control and Forwarding Planes. Evaluate processor utilization and router memory requirements Reduced memory space on HW deployed 32bits machine Perform scalability tests on 32bits and 64bits multi-core HW By now, most vendors have HW forwarding for IPv6 providing very good performance but not all vendors have a full support of all the IPv6 features.
IPV6 Status on BT s 21CN Networks BT Design Council approved IPv6 developing activity for 21CN networks Develop IPV6 Network Performance and Security Testing models( build different family tests: Performance, Stress, Conformance/Compliance, Interoperability, Robustness, Negative, Inopportune testing) Analyze IPv6 CP/FP/MP performances Focus on Route-Reflector IPv6 performance testing (Global and Address Family Planes) tests completed Follow up IPv6 roadmaps with accepted 21CN vendor community Enabled IPv6 on BT Global (AS5400 totally dual stack) completed Enable IPv6 on BT UK (AS2856) on going Performed IPv6 Risk Impact Analysis with UK and Global L3VPN -Select 6VPE Architectural model for L3VPN Services Deploy Trial Test environment on GS MPLS Backbone (on going) BT Broadband IPv6 Trial Tests (Retail and Wholesale) on 20CN and 21CN completed Critical status due to IPv4 address space exhaustion. Start IPv6 Trial tests on Multi Service Edge platform on going (Resolve Broadband Aggregation Accounting issues due to dual-stack mode) BT Content Work with vendor to offer IPv6 feature on existing content devices expected Q1/2011.Now use of URL Redirecting rather Native IPv6 Content Caching BT Cloud Computing Define IPv6 connectivity architecture BT Cloud Computing Labs connectivity to BT Global - completed BT Professional Services (BT INS or BT Counterpane) Evaluate Tools and people expertise on configuring/supporting IPv6 on different network elements
IPv6 20CN BB PPP connections terminated on centralised BRAS which hands out IPv4 address. LPA routes IPv4 address. Home Hub will connect PPP and request an IPv4 address. D S L A M Native IPv6 packets tunnelled across v4 network from EU to TMAN and onto v6 peering BRAS LPA TMAN v6 and v4 connectivity. v6 v4 Use v6 in v4 tunnelling over existing IPSC PTA infrastructure. IPSC will remain IPv4 only over the PPP with no changes to the product.
IPv6 21CN BB First Step PPP connections terminated on BRAS which hands out IPv4 and IPv6 address. BEA routes IPv4 and IPv6 address. TMAN IPv4 and IPv6 service management and connection. Home Hub will connect and request an IPv4 and IPv6 address. M S A N DHCP to network more able than PPP on hub to ask for just v6 address if LAN side is just v6 BRAS BEA TMAN v6 and v4 connectivity. v6 v4 Can be optional initially and then gradually push it out to more EUs This first step does not solve IPv4 address exhaustion, but it starts us on the path to roll out IPv6
IPv6 21CN BB - Final Step Significant v4 hosted content and significant amount of v4 only CPE will still exist when we start to exhaust v4 addressing PPP connections terminated on BRAS which hands out private IPv4 and public IPv6 address. BEA routes IPv4 and IPv6 address. TMAN IPv4 and IPv6 service management and connection. Home Hub will connect and request a private IPv4 and public IPv6 address. M S A N BRAS BEA TMAN NAT v6 connectivity directly and v4 connectivity via NAT box. v6 v4 This starts to solve IPv4 address exhaustion. It provides a private IPv4 address to end user and then NAPT to publicly route to v4 content.
Backup slides
IPV6 Addressing BT organizations currently have: 2A00:2000:: /22 allocated to BT 2A00:2010::/32 Global 21CN Cloud Computing (AS5400/AS12641) 2A00:2390::/32 UK 21CN Cloud Computing (AS2850) 2001:618::/32 (UK) 2001:740::/32 (initially used in Germany now expanded in Global Backbone AS5400) + 2A00:2000::/32 2A00:2300:: /25 allocated to BT UK - AS2856 2001:7C8::/32 (Ireland) 2001:AC0::/32 (Spain) Options for infrastructure and assignment: Apply for new BT allocation structure Use new allocation for infrastructure BT GS registry needs to support IPv6 LIR function for both 21CN Global IA and 21CN Global MPLS backbones
BT AS5400 IPv6 connectivity PEERS: Consulintel, AS16206 ChinaTelecom, AS38035 NTT Verio, AS2914 LINX Route Collector, AS5459 Nida Korea, AS17832 RETN, AS9002 Virgin Radio, AS34763 Hurricane, AS6939 Google, AS15169 Telitalia, AS6762 Tele2, AS1257 RIS, AS12654 Tiscali, AS3257 OPENTRANSIT, AS5511 NetAccess, AS8001 CWEU, AS1273 UPC, AS6830 JansenSystemberatung6, AS42184 DTAG6, AS3320 VerizonB6, AS12702 KPNEurorings6, AS286 Telia6, AS1299 COMMUNITY6, AS8844 ATRATO6, AS8844 NORIS6, AS12337 TUDarmstadt6, AS8365 Customers: IKS, AS15725 TMT, AS16316 InfraServ, AS12853 SaudiTelecom,AS8895 BTGSSAU, AS8903 European Commission Cisco Networker Camps SWIFT(AS48075) Transits: Level3 Transit, AS3356 Global Crossing Transit, AS3549