40 likes | 153 Views
A Transition Scenario Caused by IPv4 Address Scarcity. Dave Thaler dthaler@microsoft.com. 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.
E N D
A Transition Scenario Caused by IPv4 Address Scarcity Dave Thalerdthaler@microsoft.com IETF 70: V6OPS
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 Client’s Local network Server’s Local network Internet Host Host IETF 70: V6OPS
Transition solution space today • IPv6 capable apps/hosts talking across an IPv4-only network • TunnelBroker, 6to4, Teredo, ISATAP, 6over4, etc • IPv4 capable apps/hosts talking across an IPv6-only network: • DSTM [expired draft] • 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
Scenario caused by IPv4 address scarcity • 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 e.g. Web Browser e.g. Web Server Client’s Local network Server’s Local network Internet IPv4-only Host Dual Stack Host No public IPv4 address IETF 70: V6OPS