Outline. Background IETF activities Solutions & problems Next steps

Transcription

1

2 Outline Background IETF activities Solutions & problems Next steps

3 The Plan IPv4 Free Pool Size of the Internet IPv6 Deployment

4 The Reality IPv4 Free Pool Today Size of the Internet? IPv6 Deployment

5 Background Does this cause us to reconsider whether our IPv6 deployment and transition toolbox is adequate? Or the need for new tools to deal with the pain of IPv4 address shortage? The situation with NAT-PT Input from the service providers and corporate network managers

6 This Is Important! The way we deploy IPv4 NATs changes as there is less address space We cannot deploy IPv6 in all situations where we would like to I see many potential future outcomes, some of them bleak Is there something that we can do to help provide better solutions and to help IPv4-IPv6 co-existence

7 State of the Art This is not a claim that the existing tools should no longer be used for instance, Dual Stack with an IPv4 NAT is still what most networks would likely want to use Similarly, existing tunneling mechanisms for IPv6 transition continue to be valid Focus is on new situations, such as when a NAT does not even have one address, or when RFC 1918 space runs out

8 Recent IETF Activities Several discussions in Dublin An interim meeting in Montreal New charter for SOFTWIRE WG Proposed new charter for BEHAVE WG

9 Montreal Outcome A better understanding of how different solutions A well attended interim meeting in Montreal on October 1st-2nd Focused on improved IPv4 NATs, tunneling to solve RFC 1918 shortage, and IPv4 IPv6 translation Strong consensus that we need we need both tunneling and translation based solutions to address different scenarios

10 Solutions and Problems

11 IPv6 to home gateways as a side effect Space Home gateway and service provider router tunnel IPv4 over IPv6 Often combined with a NAT on the provider router to share one address

12 Port Borrowing Public IPv4 Address Shortage IPv6 (A+P),... Again, as a side-effect gateways get IPv6 Shared public address, separate port ranges NAT stays here Port-based forwarding here Each subscriber gets only a fraction of a public address; a port range Can be implemented in various ways: an extension of the tunneling approach, mapping port ranges to

13 Translation IPv6 Hosts Reaching IPv4 Hosts IPv6 host An example appl IPv4 servers ication is IPv6 hosts connecting to IPv4-only servers E.g., Windows 7 Direct Access Enables unilateral IPv6 deployment

14 More on Translation Work will address four cases: connecting a specific IPvX-only network to the IPvY Internet, with initiation on either side IPv6 access to a set of IPv4 servers IPv6-only branch office connecting to IPv4 Internet IPv4 access to a set of IPv6 servers The last IPv4 holdout accessing the IPv6 Internet

15 More on Translation 2 Documents under development include framework, packet translation, state maintenance, and DNS parts Challenges include DNSSEC and preventing dual stack hosts accidentally selecting a path through a translator The two ways to improve over NAT-PT: simply a better specification and focusing on constrained scenarios

16 Next Steps Please provide feedback Here, on the list, or in the IETF meetings Upcoming meeting in Minneapolis ( Interim meetings in Malta (Jan Pro gre ss the specifications from BEHAVE and SOFTWIRE

17 Further Reading RFC 4213 RFC 2766