1 / 19

IPv6 on vBNS+

IPv6 on vBNS+. Greg Miller NANOG - Albuquerque, NM June 12, 2000 http://www.vbns.net. vBNS Overview. High-Performance Backbone for R&E community sponsored by U.S. NSF. Charter: foster research and education; develop and offer advanced services: high-bandwidth IPv4 (1st OC-3 backbone in US)

clovis
Download Presentation

IPv6 on vBNS+

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IPv6 on vBNS+ Greg Miller NANOG - Albuquerque, NM June 12, 2000 http://www.vbns.net

  2. vBNS Overview • High-Performance Backbone for R&E community sponsored by U.S. NSF. • Charter: foster research and education; develop and offer advanced services: • high-bandwidth IPv4 (1st OC-3 backbone in US) • native IP multicast • native IPv6 • IP QoS • traffic measurement and analysis

  3. vBNS Evolution • The vBNS was built in 1995 as an OC-3 IP-over-ATM backbone. • Initially interconnected 5 NSF-funded supercomputer centers. • User community grew to include top ~100 U.S. R&E institutions by mid-1998. • Strong relationships and peering with many international R&E networks. • Adopted as the initial Internet2 backbone.

  4. The vBNS Today • Dual technology backbone: OC-12 ATM and OC-12/OC-48 POS trunks. • Multi-vendor backbone: Cisco & Juniper. • MPLS deployed in March 2000. • End of NSF funding in April 2000. • Three-year, no-cost extension of contract. • vBNS+: commercialization and expansion of user community to include corporate R&D labs, govt agencies, education, ...

  5. vBNS IPv6 Service Overview • Native (not tunneled) IPv6-over-ATM on the vBNS backbone since July 1998. • Dedicated hardware (Cisco 4700s with OC3/ATM) for IPv6 routing. • Full mesh of PVCs among the IPv6 routers. • Native and tunneled connections to vBNS-attached institutions. • Backbone provider (pTLA) for the global 6bone.

  6. 6 6 6 6 vBNS IPv6 Router Locations

  7. vBNS POP Architecture vBNS Backbone OC48c Juniper M40 OC12mon OC12c OC12c T1 through OC12c ports for ATM network service access T1 through OC12c ports for private-line access Fore ASX-1000 ATM switch o o o o o o OC12c OC3c OC3c Cisco 7507 (IPv4) Sun Ultra2 Cisco 4700 (IPv6) Management Ethernet mgt router Management IP network

  8. vBNS IPv6 Service Details • IPv6 routers fully meshed with ATM PVCs. • RIPng is the IGP. :-( • BGP4+ peering with other 6bone sites. • Static routes or BGP4+ peering with vBNS-attached institutions. • Most connections are native (over ATM), with some IPv6-over-IPv4 tunnels. • DNS supports AAAA and PTR records. • IPv6-capable web server: www.vbns.net

  9. IPv6 Trunking Details vBNS POP Cisco 4700 (IPv6) vBNS POP Cisco 4700 (IPv6) ATM switch Juniper M40 Juniper M40 ATM switch native IPv6 PVCs tunnel vBNS ATM Backbone customer IPv4 router customer IPv6 router customer IPv6 router tunneled customer ATM switch Juniper M40 native customer Cisco 4700 (IPv6) vBNS POP

  10. Trunking IPv6 Over MPLS vBNS POP vBNS POP Cisco 4700 (IPv6) Cisco 4700 (IPv6) Juniper M40 ATM switch ATM switch Juniper M40 native IPv6 LSPs tunnel vBNS MPLS Backbone customer IPv4 router customer IPv6 router customer IPv6 router tunneled customer Juniper M40 ATM switch native customer Cisco 4700 (IPv6) vBNS POP

  11. Address Delegation • Two types of connections offered: • transit site: • offers connectivity and aggregation for other sites that are topologically behind it • is delegated a /32 address block to number its own site and those behind it • leaf site: • stub site that does not offer transit to other sites • is delegated a /48 address block to number the site • Try to follow topological hierarchy • good testbed for multihoming issues

  12. vBNS IPv6 Address Assignment 6bone Address Format: 24 bits 24 bits 16 bits 64 bits pTLA NLA2 SLA 0x3FFE Interface ID 8 bits vBNS Address Format: 24 bits 24 bits 16 bits 64 bits 0x3FFE 0x28 SLA Interface ID NLA2 Site ID 8 8 16 bits vBNS leaf sites are assigned a Site ID under NLA2=0xFF vBNS transit sites are assigned an NLA2

  13. vBNS IPv6 Logical Network Map Viagenie/CA*net2 UUNET Sprint APAN/WIDE WIDE Abilene Fibertel/TCI ESnet UUNET-UK Trumpet CAIRN Texas AP Moscow State Univ 6TAP SUNY- Buffalo VA Tech Chicago MIT San Francisco Perryman, MD ODU San Diego PSC UVA PSU SDSC SoX/ GA Tech UCSD vBNS POP pTLA Transit Site Exchange Point Leaf Site native tunnel

  14. vBNS IPv6 Routing Policy • We provide transit for IPv6. • We enforce “6Bone Routing Practice” ID recommendations • For peering sessions with other pTLAs: • accept only /24’s (except ours), /28’s, & /35’s • announce only /24’s (including ours), /28’s, & /35’s • For Leaf and Transit sites: • accept only delegated prefix (/32 or /48) • announce everything

  15. Commercializing the IPv6 Service: vBNS+ • IPv6 service is bundled with vBNS+ subscription. No additional charge. • “Quasi-production” - experimentation is encouraged. • Not restricted by an Authorized Use Policy. • vBNS+ has been delegated production IPv6 address space (a sub-TLA) from ARIN. • Renumbering is underway in the backbone. • Address space to be delegated to customers.

  16. Areas for future work • Experimentation with transition mechanisms (6over4, 6to4, etc.). • Better integration of v4 and v6. • Trunking IPv6 over MPLS rather than ATM. • Test new stuff: OSPFv6, A6 records, . . . • Need more applications • IRC, WWW content, napster, gnutella??? • multiplayer game contests?

  17. Why are we doing this? • It falls under our charter. • Competitive edge. • Community service - to help advance the development of the technology. • Unfortunately, not because customers are asking us for it (although a few are). • If we build it, will they come?

More Related