Re-, Except "IPv4 addressing"-related configuration, what additional configuration parameters can be provisioned with DHCPv4 and not with DHCPv6? Why in the future, an IPv6-enabled node will require to retrieve configuration using DHCPv4-over-DHCPv6 and not directly using DHCPv6?
Cheers, Med >-----Message d'origine----- >De : Qi Sun [mailto:[email protected]] >Envoyé : lundi 15 avril 2013 07:56 >À : BOUCADAIR Mohamed OLNC/OLN >Cc : Tomek Mrugalski; [email protected]; Softwires ([email protected]) >Objet : Re: [dhcwg] Adoption call on draft-scskf-dhc-dhcpv4-over-dhcpv6 > > >Dear Med, > >Thanks for your response. Here is my understanding. > >IMHO, defining options in DHCPv6 seems to introduce less complexity in >protocol. However, we do not know for now which options are needed in the >future. If we have to port DHCPv4 options into DHCPv6, how many times >should we do the work? Like one new option per 2 years, or redefining all >DHCPv4 options into DHCPv6 at one time? The proposed solution tries to >avoid polluting the DHCPv6 option space, which is necessary for transition >in DHCP. > >Another point is that, defining option(s) / container would require the >DHCPv6 engine to handle DHCPv4 options, which would introduce more >complexity to the logic and implementation of end points. The proposed >solution leverages the DHCPv4 engine for DHCPv4 messages / options and >DHCPv6 engine for DHCPv6 messages / options. The end points would >compatible to both DHCPv4 process and DHCPv6 process. This is more suitable >for the transition. > >A third consideration is, in the case of IPv6 transition, the DHCP client >(on the tunnel endpoint) is bound to be modified. We think it better to >modify the client completely for the transition purpose. > >Last but not the least, the proposed solution is based on the DHCPv6 >infrastructure, which has been deployed in operators' networks. > >The DHCPv4 over DHCPv6 mechanism is an architectural development for DHCP >protocol to meet the requirements for configuring IPv4 parameters across >the IPv6 network. We think it is important for the DHC WG to work on it. > >Best Regards, >Qi Sun >(Sorry for resending, try to synchronize with softwire ML...) > >On 2013-4-12, at 下午7:47, <[email protected]> ><[email protected]> wrote: > >> Dear all, >> >> (I cc sofwtire as this work is also relevant for the working group.) >> >> I do not support this work as it induces more complexity compared to just >defining adequate option in dhcpv6. Defining one container or few DHCPv6 >options is much more simpler that the proposed approach. >> >> Cheers, >> Med >> >>> -----Message d'origine----- >>> De : [email protected] [mailto:[email protected]] De la part >de >>> Tomek Mrugalski >>> Envoyé : mercredi 3 avril 2013 19:41 >>> À : [email protected] >>> Objet : [dhcwg] Adoption call on draft-scskf-dhc-dhcpv4-over-dhcpv6 >>> >>> Hi all, >>> >>> This draft is a result of the discussion we had during last meeting in >>> Orlando. We have very productive discussion about IPv4 hosts >>> configuration in IPv6-only network. After we reached what looked like a >>> consensus in the meeting room, couple folks volunteered to write down >>> the draft that summarizes that perceived consensus. This draft is a >>> product of this effort. >>> >>> As requested by authors, we are announcing adotion call on >>> draft-scskf-dhc-dhcpv4-over-dhcpv6-01. This call is being initiated to >>> confirm whether there is WG consensus to adopt this work as DHC WG >>> draft. Please state whether or not you're in favor of the adoption by >>> replying to this mail. If you are not in favor, please also state your >>> objections in your response. This adoption call will complete on 2013- >04- >>> 17. >>> >>> Regards, >>> Bernie & Tomek >>> >>> On 03.04.2013 19:20, Marcin Siodelski wrote: >>>> In the name of authors of draft-scskf-dhc-dhcpv4-over-dhcpv6 I am >asking >>>> for adoption of this document by DHC WG. >>>> >>>> The latest version (-01) is available here: >>>> >>>> http://www.ietf.org/internet-drafts/draft-scskf-dhc-dhcpv4-over-dhcpv6- >>> 01.txt >>>> http://tools.ietf.org/html/draft-scskf-dhc-dhcpv4-over-dhcpv6-01 >>>> >>>> This document describes a mechanism whereby IPv4 client obtains its >>>> configuration from the DHCPv4 server separated from the client by IPv6- >>>> only network having DHCPv6 service. This mechanism is frequently >>>> referred as "DHCPv4-over-DHCPv6". >>>> >>>> The DHCPv4 client's request is carried in the newly defined DHCPv6 >>>> messages/option to/from the server and can be sent either through a >>>> relay or directly. >>>> >>>> Cheers, >>>> Marcin >>>> >>>> >>>> >>>> _______________________________________________ >>>> dhcwg mailing list >>>> [email protected] >>>> https://www.ietf.org/mailman/listinfo/dhcwg >>>> >>> >>> _______________________________________________ >>> dhcwg mailing list >>> [email protected] >>> https://www.ietf.org/mailman/listinfo/dhcwg >> _______________________________________________ >> dhcwg mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/dhcwg _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
