Re: [dhcwg] Alignment between softwire-map-dhcp and dhc-dhcpv4-over-dhcpv6 drafts

Ole Troan <> Thu, 07 November 2013 23:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9A8ED21E8094; Thu, 7 Nov 2013 15:24:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -10.537
X-Spam-Status: No, score=-10.537 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id bwsrLgGDKFlE; Thu, 7 Nov 2013 15:24:25 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 55CDE11E812F; Thu, 7 Nov 2013 15:24:24 -0800 (PST)
X-Files: signature.asc : 496
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FAO8ffFKQ/khM/2dsb2JhbABagwfAGYEnFnSCJQEBBAF5BQsLDjhXBi6HYAa9QY9ZB4MggRADkC6ZaIMnOw
X-IronPort-AV: E=Sophos; i="4.93,654,1378857600"; d="asc'?scan'208"; a="18867041"
Received: from ([]) by with ESMTP; 07 Nov 2013 23:24:23 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id rA7NOJw6008215 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 7 Nov 2013 23:24:19 GMT
Content-Type: multipart/signed; boundary="Apple-Mail=_244C2386-FBAE-43A3-B6CD-9FD2B3E8B2F9"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
From: Ole Troan <>
In-Reply-To: <>
Date: Fri, 8 Nov 2013 00:24:18 +0100
Message-Id: <>
References: <>
To: Ian Farrer <>
X-Mailer: Apple Mail (2.1816)
Cc: Softwires <>, " WG" <>,,
Subject: Re: [dhcwg] Alignment between softwire-map-dhcp and dhc-dhcpv4-over-dhcpv6 drafts
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 07 Nov 2013 23:24:31 -0000


> From a discussion with Bernie and Tomeck earlier: To give some clarity about what the different 4o6 provisioning mechanisms are suitable for, can we add in some text to bound the scope of map-dhcp to provisioning static v4 configuration parameters (i.e. precluding dynamic v4 leasing) with no additional DHCPv4 options and add in an informative pointer to using DHCPv4 over DHCPv6 for dynamic/additional options?
> Likewise, I’m putting a similar back pointer to MAP-DHCP in the dhc-v4-configuration draft:
> For the most simple IPv4 provisioning case, where the client only needs to receive a static IPv4 address range assignment (with no dynamic address leasing or additional IPv4 configuration), DHCPv6 based approaches [ietf-softwire-map-dhcp] may provide a suitable solution.
> The DHCPv4oDHCPv6 doc should have a similar pointer to map-dhcp for static as well.

could you propose some text?
I'm not quite sure what bounding of scope you'd like to see.
all the lifetimes of configuration information defined in MAP DHCP are bounded by the lifetimes of the tunnel,
i.e. the lifetime of the End-user IPv6 prefix.

the IPv4 address assignment will be as dynamic as the underlaying IPv6 assignment is.

what using DHCPv4 address leases gets you, is separate lease times. given that, this mode is incompatible with MAP-T and -E,
I'm not quite sure what this document can say about it?