A Transition Scenario Caused by IPv4 Address Scarcity
4
IETF 70: V6OPS 1 A Transition Scenario Caused by IPv4 Address Scarcity Dave Thaler [email protected]
description
A Transition Scenario Caused by IPv4 Address Scarcity. Dave Thaler [email protected]. Transitioning to IPv6. Different entities may transition at different times Each can be v4-only, v6-only, or v4/v6 This means there’s a large number of possible scenarios…. Client App. Server App. - PowerPoint PPT Presentation
Transcript of A Transition Scenario Caused by IPv4 Address Scarcity
IETF 70: V6OPS 2
Transitioning to IPv6
• Different entities may transition at different times– Each can be v4-only, v6-only, or v4/v6
• This means there’s a large number of possible scenarios…
Host Host
Client’sLocal
network
Server’sLocal
network
Internet
ClientApp
ServerApp
IETF 70: V6OPS 3
Transition solution space today
1. IPv6 capable apps/hosts talking across an IPv4-only network– TunnelBroker, 6to4, Teredo, ISATAP, 6over4, etc
2. IPv4 capable apps/hosts talking across an IPv6-only network:– DSTM [expired draft]
3. IPv4-only app/host talking to IPv6-only host/app (and vice versa):– NAT-PT [deprecated]– BITS, BITA (IPv4-only app on dual-stack node)– TRT (UDP/TCP-only)
IETF 70: V6OPS 4
Scenario caused by IPv4 address scarcity
IPv4-onlyHost
DualStackHost
Client’sLocal
network
Server’sLocal
networkInternet
e.g. WebBrowser
e.g. WebServer
No public IPv4 address
• Port is fixed, so NATv4 only supports 1• NAT-PT (e.g., in client’s local network) might work, but deprecated• There may be other solutions (e.g., DSTM-like?)• The IETF should have some story for this scenario
