1 / 6

Gateway-Initiated 4over6 Deployment draft-chen-softwire-gw-init-4over6

Gateway-Initiated 4over6 Deployment draft-chen-softwire-gw-init-4over6. Yuchi Chen (Presenter) IETF 87 in Berlin, Jul. 2013. GI-4over6 Scenario. Typical Lw4over6 Scenario IPv4 address and port set is provisioned to the lwB4 GI-4over6 Scenario

trory
Download Presentation

Gateway-Initiated 4over6 Deployment draft-chen-softwire-gw-init-4over6

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. Gateway-Initiated 4over6 Deploymentdraft-chen-softwire-gw-init-4over6 Yuchi Chen (Presenter) IETF 87 in Berlin, Jul. 2013

  2. GI-4over6 Scenario • Typical Lw4over6 Scenario • IPv4 address and port set is provisioned to the lwB4 • GI-4over6 Scenario • IPv4 address and port set is provisioned to the device behind the 4over6 gateway (lwB4) IPv4 Network IPv6 Network Local IPv4 link IPv4 Internet IPv4-in-IPv6 tunnel End device 4over6 gateway (LwB4) LwAFTR Pb. addr. & ports Provision public IPv4 address & port set

  3. Necessary Assumption IPv4 Network IPv6 Network IPv4-in-IPv6 tunnel Local IPv4 link IPv4 Internet v4addr-1 & Portset-1 v6addr-1 LwAFTR & 4o6 Server End device 4over6 Gateway • Configuration on 4over6 Gateway in advance • Provisioned with tunnel endpoint addr - v6addr-1 (DHCPv6) • Provisioned with an public IPv4 addr & port set – v4addr-1 & Portset-1(DHCPv4-over-DHCPv6) • 4o6 Server is implemented on LwAFTR • Multiple end devices behind the same 4over6 GW will not be provisoned with the same shared IPv4 address

  4. Control Plane Behavior Local IPv4 link IPv6 Network IPv4 Network Tunnel concentrator & 4o6 server Wrap DHCP Request into BOOTREQUESTV6 IPv4-in-IPv6 tunnel DHCP Request DHCPv4-over-DHCPv6 DHCP Request 4over6 gateway End device DHCP Reply (ACK) Extract DHCP Reply from BOOTREPLYV6 DHCPv4-over-DHCPv6 DHCP Reply (ACK) Routing to end device is configured {v4 a+p ,v6 addr} binding is added into the binding table IPv4 addr & port set is configured

  5. Data Plane Behavior • End device • Sends v4 packets using the v4addr & port set that it has been assigned • 4over6 Gateway • Encapsulates outbound v4 packets & decapsulates inbound v4-in-v6 packets • Uses a routing table indexed by v4addr & port set to deliver inbound v4 packets • Performs no NAPT44 function • LwAFTR • No difference with the behavior of LwAFTR in original lw4over6

  6. Next Step • Any interest to continue this work? • Comments?

More Related