1 / 6

Sprintlink IPv6

This document outlines Sprintlink's journey and strategic goals for IPv6 deployment, focusing on value-add for customers and peers since its inception in Q4 1997. Initially, Sprintlink operated with a minimal number of peers and customers, but by Q1 2000, it scaled significantly. With existing infrastructure lacking redundancy, future plans aim to enhance networking capabilities through native customer peering, robust IGP deployment, and improved DNS services. Key constraints include outdated router vendor code and scalability challenges in routing tables, highlighting the need for application development and dynamic IGP functionalities.

tolinka
Télécharger la présentation

Sprintlink IPv6

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. Sprintlink IPv6 rob rockell rrockell@sprint.net

  2. Goals • play • Value-Add for customers and others • free • not under SLA • Test Implementations, think about problems

  3. Timing • Started 4Q 1997 • (3ffe:2900::/24) • 4Q 1998: • about 10 peers, about 5 customers • 1Q 2000: • 28 peers, over 50 downstream customers

  4. NOW All peer/cust connex tunneled All equipment old, no redundancy FUTURE Get to exchanges somehow, provide for native customer peering Deploy good stable IGP, and provide redundant services (DNS, etc...) Plans for IPv6

  5. Constraints • Router Vendor Code: • unstable and lacking support: • Dynamic IGP • BGP functionality • Next-header functionality • Applications: • Need more apps. • no traffic on 6bone (barely).

  6. Constraints • Protocol: • Multi-homing? • Address allocation, auto(re)-configuration, routing table scalability.

More Related