Dear all, I have some concerns about current map-dhcp-05 document. From my understanding, this draft has been changed to "softwire-dhcp", to cover all DHCPv6-related provisioning for softwire mechanisms. But I'm confused with the descriptions about lw4o6 and the provisioning.
In order to improve the document and push map, lw4o6 and softwire-dhcp further, I think there should be some updates on it. Here are the issues/suggestions: 0) MAP & lw4o6 are parallel solutions, rather than lw4o6 is a subset of MAP. Softwire-dhcp should claim this, and remove "Lightweight 4over6 is a strict subset of MAP-E". 1) MAP uses DHCPv6 as the provisioning mechanism. DHCPv6 is optional for lw4over6, used for stateless provisioning (static mode) 2) Dynamic IPv4 address assignment uses DHCPv4-over-DHCPv6 (IMHO it's the default case of lw4o6). DHCPv4-over-DHCPv6 enable & server address options can be put into containers, to enable the function. 3) use DHCPv4-over-DHCPv6 to provision additional configuration information for both lw4o6 & MAP. 4) Softwire-dhcp should make a normative reference to DHCPv4-over-DHCPv6. I have also submitted two tickets to the tracker : #27 for the "subset" issue, and #28 for DHCPv4-over-DHCPv6 issues. I'd like to ask the WG whether these should be considered. Thanks! Best Regards, Cong Liu ---------- Forwarded message ---------- From: softwire issue tracker <[email protected]> Date: 2013/10/29 Subject: [softwire] #28: Dealing with DHCPv4-over-DHCPv6 To: [email protected], [email protected] Cc: [email protected] #28: Dealing with DHCPv4-over-DHCPv6 The current map-dhcp-05 draft covers static IPv4 provisioning for lw4o6, but does not cover dynamic IPv4 provisioning. Dynamic IPv4 provisioning is an important part of lw4o6. Current lw4over6-02 document says "An lwB4 MUST support dynamic port-restricted IPv4 address provisioning." According to current specification, dynamic IPv4 provisioning is the default working mode of lw4o6. And there is consensus in dhc wg that DHCPv4-over-DHCPv6 is the best underlying approach for IPv4 provisioning over IPv6 network, especially for dynamic provisioning. Since map-dhcp has been changed into "softwire-dhcp" to cover both MAP and lw4o6, it should cover the dynamic mode of lw4o6 and have a description of using DHCPv4-over-DHCPv6. The document should make a normative reference to DHCPv4-over-DHCPv6. -- -------------------------+------------------------------------------------- Reporter: | Owner: draft-ietf-softwire-map- [email protected] | [email protected] Type: defect | Status: new Priority: major | Milestone: Component: map-dhcp | Version: Severity: Active WG | Keywords: Document | -------------------------+------------------------------------------------- Ticket URL: <http://tools.ietf.org/wg/softwire/trac/ticket/28> softwire <http://tools.ietf.org/softwire/>
_______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
