1 / 9

Philosophy of “REAL” IPv6 network operation

Philosophy of “REAL” IPv6 network operation. Shin Miyakawa NTT Multimedia Communications Laboratories Palo Alto, California, USA IPv6 summit in Osaka Japan / December 2000. Speaker’s position. As an “IPv6 fundamentalist” purposely

jalena
Download Presentation

Philosophy of “REAL” IPv6 network operation

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. Philosophy of “REAL”IPv6 network operation Shin Miyakawa NTT Multimedia Communications Laboratories Palo Alto, California, USA IPv6 summit in Osaka Japan / December 2000

  2. Speaker’s position • As an “IPv6 fundamentalist” purposely • This presentation does not represent company’s views nor opinions

  3. What is the best practice to operate IPv6 network ? • We need to be careful about • Available implementation • Legacy • Standardization • We need to think about plans despite unclear situation • For now, the next year and few years later • We must have concrete philosophy.

  4. Philosophy of the design • IMHO, the concept of the design of IPv6 is; • Big enough address space with simple structure • that provides us with • Original “End-to-End” environment • A lot of benefits from NAT free network • Fast processing It is so simple and functional enough.

  5. Philosophy of the operation • Same as design • should be just SIMPLE so that it’s • IN-EXPENSIVE • STABLE • SCALABLE • Think simple !

  6. IPv6 network operation • “Pure IPv6 network + Application Gateway(s) to IPv4 network” is the way to go. • Routing protocol, E-mail, DNS etc, etc. for v6 should be on v6. • Those for v4 should remain on v4. • dual stack operation???... I suspect... • Just for edge of the network only where it is needed. • We can not do this for now • actually we can do this if we use only KAME... • but anyway within few years

  7. Taking care about legacy • Co-existence with IPv4 • NAT hides usage of private address • Application GW hides usage of IPv6 • SAMETHING! So, use IPv6 wherever NAT is needed! • It is painful to add new protocol onto existing network • simply avoid as much as you can • That is just like “put new wine in old bottles” • Create new network and move onto it • If you need to access legacy, use AGW

  8. Operate ISP network and IX • Logically, we should have separate systems for v4 and v6 • Note that they can share same hardware and links • IPv6 network can simulate IPv4 network but not vice versa

  9. Conclusion • To design, install and operate IPv6 network, let’s think SIMPLE to achieve • IN-EXPENSIVE, • STABLE and • SCALABLE network • Pure IPv6 is the goal. Definitely. • It seems strange ? But it is!

More Related