s. daniel park soohng.park@samsung

DHCP Option for Configuring IPv6-in-IPv4 Tunnels<draft-daniel-dhc-ipv6in4-opt-01>

DHC WG – 59th IETF

S. Daniel Parksoohng.park@samsung.com

59th IETF – DHC WG , Seoul

Background

• This DHCPv4 option allows a dual host to bootstrap itself into a disconnected IPv6 infrastructure – for example, a dual-stack host on an IPv4-only link.

• to provide configured tunnel end point automatically• for the simple configured tunnel

• for the IPv4/6 dual host

59th IETF – DHC WG , Seoul

Overview

IPv4/6

IPv4 IPv6

IPv4

Code Length CTEP Order in Sequence

0 1 2 3

0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

| OPTION_CTEP | Len | CTEP Addr1 |

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

| CTEP Addr 1 | Subnet Mask 1 |

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

| Subnet Mask 1 | CTEP Addr 2 |

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

| CTEP Addr 2 | Subnet Mask 2 |

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

| Subnet Mask 2 |. . .

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

IPv6-in

-IPv4

IPv6

IPv6 connectivity

59th IETF – DHC WG , Seoul

Comments from ML

• What exactly is the subnet mask used for ? - Bernie

• IPv6 network information – Bernie• IPv4 address of the tunnel endpoint• IPv6 address and prefix-length for the IPv6 network reachable

• The receiving host encapsulates and forwards any IPv6 datagrams that match the IPv6 prefix in an IPv4 datagram sent to the IPv4 tunnel endpoint address. - Ralph

• Ambiguous word – Bernie• IPv6-in-IPv4 vs IPv6-over-IPv4

• Are the prefix length and prefix really needed ? - Bernie

59th IETF – DHC WG , Seoul

Changes from 00

• not published because of cutoff. It will be available soon

• added Multiple Tunnel End Point Considerations section to clarify how both single TEP and multiple TEP are considered… • generally single TEP is used for IPv6 connectivity and all packet

are reached to the same point

• in multiple TEP, the routes will be tried in a round robin fashion if an host load-sharing is honored

• accepted as WG Item ?