1 / 7

Guidance for ISPs’ provision of IPv6 transition scheme to ICPs

Guidance for ISPs’ provision of IPv6 transition scheme to ICPs. <draft-qin-v6ops-icp-transition-00> Jacni Qin Guangyi Liu 76 th IETF, Hiroshima, Japan. Background. In short, IPv6 deployment models are revisited. Some new transition tools are developed to complement the existing ones.

aitana
Download Presentation

Guidance for ISPs’ provision of IPv6 transition scheme to ICPs

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. Guidance for ISPs’ provision of IPv6 transition scheme to ICPs <draft-qin-v6ops-icp-transition-00> Jacni Qin Guangyi Liu 76th IETF, Hiroshima, Japan

  2. Background • In short, • IPv6 deployment models are revisited. • Some new transition tools are developed to complement the existing ones. • Meanwhile, there are several portions and phases in the whole transition process. • The transition of servers is an important one mentioned in RFC5211.

  3. Background • ISPs, • “How can I use these transition tools, especially the newly developed ones, to provide transition scheme to my customers (ICPs using their Data Center services)?”

  4. Approaches • Dual Stack • “The most well-understood one …” • NAT64 • To use it for “IPv6 Internet to an IPv4 network” , and put the NAT64 boxes near the servers. • Stateless translation (“IVI”) • To move servers into IPv6 networks while the IPv4 reachability could be “retained”.

  5. Contents/Scope • Operation of these tools • How to get started? • Limitations, • Capacity, reliability, load balancing, • Security • … • Topology, locations of “boxes” • Other issues …

  6. For Next Steps • Shall we draft a document like this? There are some comments related, • “Sounds reasonable; make sense to document recommended deployment practices in a separated BCP document …” • “not useful, it just repeats stuff we already know.” • If yes, shall we do the other scenarios? • “to avoid adding a lot of operational scenarios to the protocol documents …”

  7. Thanks!

More Related