1. DNS and IP Scalability Communication Systems Design 2002

2. 2 DNS and IP Scalability  Members  Daniel Hedberg  Liyi Meng  Patrick Brosset  Thomas Wetterberg  YanHong Xu  Principal  B.Svante Eriksson, SCINT  Coach  Fredrik Lilieblad

3. 3 Overview  Why  What  How  SWOT  Summary  Cooperation between projects

4. 4 Why  Internet Scalability  IP address space  Bandwidth

5. 5 Why (cont.)  DNS and IP Scalability  IPv6  Transition - from IPv4 to IPv6  DNS  Emerging services

6. 6 Overview  Why  What  How  SWOT  Summary  Cooperation between projects

7. 7 What we have done  DNS  Root servers  Transition  Applications  Security  IP  IPv6  Transition IPv4 to IPv6  Routing  Emerging services  Mobility  Real-time

8. 8 What we will do  IP transition  Has already started  ~30 years to complete

9. 9 IP transition Time periodNetwork topology ~1 yearIsolated IPv6 networks ~2 years Migration to IPv6 of some core networks >10 yearsIsolated IPv4 networks

10. 10 IP Transition Mechanism IPv6 over IPv4 tunnels IPv6 over dedicated datalink IPv6 over MPLS backbone Using dual stack backbone Using translation mechanism

11. 11 IPv6 over IPv4 tunnels Manually Configured Tunnel, Tunnel Broker Automatic IPv4-compatible Tunnel Automatic 6to4 Tunnel, ISATAP Tunnel Shipworm...

12. 12 IPv6 over dedicated datalink or MPLS Forward packet without IP header processing

13. 13 Using dual stack backbone All the Routers support both IPv6 and IPv4

14. 14 IP Translation Mechanisms Translate IPv6 header into IPv4 header. NAT-PT, TCP-UDP relay, BIS, SIIT DSTM, SOCKS-Based IPv6/IPv4 Gateway...

15. 15 DNS transition  Possible problems  Mixed IP environment  A6 record

16. 16 Overview  Why  What  How  SWOT  Summary  Cooperation between projects

17. 17 How  Test different combinations of:  Network scenarios  Traffic scenarios  Goal:  Compare performance and find limitations of different transition mechanisms

18. 18 Network scenarios  Combinations of:  Network topologies  Transition mechanisms  Tested on:  KTH network resources  6bone

19. 19 Traffic scenarios  Future services will affect the characteristics of IP traffic  Headers – security, mobility  Payload – Real-time, P2P File-sharing, etc.

20. 20 Overview  Why  What  How  SWOT  Summary  Cooperation between projects

21. 21 SWOT analysis  Strengths  Divers group  Cultural background  Educational background  Close cooperation with the principal  Weaknesses  No prior project experience  Goal formulation  Different schedule  Studies at different institutions

22. 22 SWOT analysis  Opportunities  Very hot topic  Interests from external parties  Easy to get access information  Threats  Field of study constantly change  Risk of results becoming irrelevant  Possible technical limitations  Software and/or hardware not available

23. 23 Overview  Why  What  How  SWOT  Summary  Cooperation between projects

24. 24 Summary  The transition to IPv6 has started, but will take time  Many different transition mechanisms  Tests on different scenarios to compare performance and limitations

25. 25 Overview  Why  What  How  SWOT  Summary  Cooperation between projects

26. 26 Help offered  IP transition  DNS  Internet Politics

27. 27 Help needed  Network configuration  Selection of method for traffic analysis  Demand estimations of future applications