Qi， That's exactly what I want to express. Now it's addressed. Thanks.
Here, I have another question: some content in section 1: The service provider can then use this binding information to provision other functional elements in their network accordingly (such as the border router). What would be provisioned by using this binding information? And also, I am not very sure that I have gotten the true purpose of this solution. If you can elaborate more details, it would be much more better. Thanks and BRs, Linda Wang Qi Sun <[email protected]> 写于 2014-08-09 10:06:13: > Qi Sun <[email protected]> > 2014-08-09 10:06 > 收件人 > > [email protected], > > 抄送 > > Softwires WG <[email protected]> > > 主题 > > Re: [Softwires] New Version Notification for draft-fsc-softwire- > dhcp4o6-saddr-opt-00.txt > > Hi Linda, > > Thanks for the comment. > > If the OPTION_DHCP4O6_SADDR_HINT doesn’t take effect, then the > client would pass back to the server the IPv6 address to which it > would use to bind IPv4. It depends on the client’s preference/configuration. > > There is some text in Section 4: > The OPTION_DHCP4O6_SADDR_HINT is used by the server to indicate a > preferred prefix that the client should use to bind IPv4 > configuration to. If received this sub-option, the client MUST > perform a longest prefix match between cipv6-prefix-hint and all > prefixes configured on the device. The selected prefix MUST then be > used to bind the received IPv4 configuration to. Otherwise, the > client can select any valid /128 IPv6 prefix. > > But it seems the _otherwise_ part might cause confusion. We will > revise that in the next version. > > Thanks, > Qi > > On Aug 5, 2014, at 3:05 PM, [email protected] wrote: > > > Hi, Qi, > > > > Suppose the preferred prefix in the OPTION_DHCP4O6_SADDR_HINT > doesn't match any prefixes configured on the device, > > what IPv6 address would be passed back to the DHCP 4o6 Server? > > > > BRs, > > Linda Wang > > > > "Softwires" <[email protected]> 写于 2014-07-01 19:28:39: > > > > > Qi Sun <[email protected]> > > > 发件人: "Softwires" <[email protected]> > > > > > > 2014-07-01 19:28 > > > > > > 收件人 > > > > > > Softwires WG <[email protected]>, > > > > > > 抄送 > > > > > > 主题 > > > > > > [Softwires] Fwd: New Version Notification for draft-fsc-softwire- > > > dhcp4o6-saddr-opt-00.txt > > > > > > Dear all, > > > > > > We have submitted a new draft about using DHCPv4 over DHCPv6 with > > > some IPv4-over-IPv6 softwire mechanisms. This draft follows the > > > essence of the ’Softwire DHCP Options’ document with a new container > > > grouping related sub-options. > > > > > > Comments are more than welcome. > > > > > > Best Regards, > > > Qi > > > > > > Begin forwarded message: > > > > > > From: [email protected] > > > Subject: New Version Notification for draft-fsc-softwire-dhcp4o6- > > > saddr-opt-00.txt > > > Date: July 1, 2014 at 7:24:28 PM GMT+8 > > > To: Yong Cui <[email protected]>, Ian Farrer < > > > [email protected]>, "Qi Sun" > <[email protected]>, Qi Sun < > > > [email protected]>, "Ian Farrer" <[email protected] > > > >, "Yong Cui" <[email protected]> > > > > > > > > > A new version of I-D, draft-fsc-softwire-dhcp4o6-saddr-opt-00.txt > > > has been successfully submitted by Qi Sun and posted to the > > > IETF repository. > > > > > > Name: draft-fsc-softwire-dhcp4o6-saddr-opt > > > Revision: 00 > > > Title: DHCPv4 over DHCPv6 Source Address Option > > > Document date: 2014-06-30 > > > Group: Individual Submission > > > Pages: 8 > > > URL: http://www.ietf.org/internet-drafts/draft-fsc- > > > softwire-dhcp4o6-saddr-opt-00.txt > > > Status: https://datatracker.ietf.org/doc/draft-fsc-softwire- > > > dhcp4o6-saddr-opt/ > > > Htmlized: http://tools.ietf.org/html/draft-fsc-softwire- > > > dhcp4o6-saddr-opt-00 > > > > > > > > > Abstract: > > > DHCPv4 over DHCPv6 [I-D.ietf-dhc-dhcpv4-over-dhcpv6] describes a > > > mechanism for dynamically configuring IPv4 over an IPv6-only network. > > > For DHCPv4 over DHCPv6 to function with some IPv4-over-IPv6 softwire > > > mechanisms, the operator must obtain information about the IPv4 > > > address and Port Set ID allocated to the DHCP 4o6 client, as well as > > > the /128 IPv6 prefix that the client will use as the source of IPv4- > > > in-IPv6 tunnel. This memo defines a DHCPv6 container option and two > > > DHCPv6 sub-options, to communicate the source tunnel IPv6 address > > > between the DHCP 4o6 client and server. It is designed to work in > > > conjunction with the IPv4 address allocation process. > > > > > > > > > > > > > > > Please note that it may take a couple of minutes from the time > of submission > > > until the htmlized version and diff are available at tools.ietf.org. > > > > > > The IETF Secretariat > > > > > > > > _______________________________________________ > > > Softwires mailing list > > > [email protected] > > > https://www.ietf.org/mailman/listinfo/softwires >
_______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
