Hi，all， My question has addressed. Thanks!
BRs, Linda Wang Qi Sun <[email protected]> 写于 2014-08-18 10:47:10: > Qi Sun <[email protected]> > 2014-08-18 10:47 > > 收件人 > > [email protected], > > 抄送 > > "[email protected]" <[email protected]>, [email protected] > > 主题 > > Re: [Softwires] New Version Notification for draft-fsc-softwire- > dhcp4o6-saddr-opt-00.txt > > Hi Linda, > > Please see inline. > > Thanks, > Qi > > On Aug 15, 2014, at 3:46 PM, [email protected] wrote: > > Hi Ian, > > Thanks for your explaination. Now I get the main purpose and I > really guess it would be better > understood if you can put your words below in the new version of this draft :) > > [Qi] We will do some rewording to make it clearer. > > > And now I guess this draft may be the companion draft of a new > draft about how to synchronise > the binding table in the border router. Am I right? > > [Qi] This draft is scoped for communicating the bound v6 address to > the DHCP 4o6 Server. The synchronisation process is handled in > http://tools.ietf.org/html/draft-liu-softwire-lw4over6-dhcp- > deployment-04#section-4.5 . > > > What's more, here are some editorial errors as follow, it would be > better if they can be revised. > Section 5.1: cipv6-hintlen or cipv6-boundlen ? cipv6-prefix-hint > or cipv6-bound-prefix? > > [Qi] Thanks for pointing it out. Should be: cipv6-hintlen/cipv6-prefix-hint. > > Thanks for comments~ > > > Nothing else. > > Thanks a lot. > > BRs, > Linda Wang > > > <[email protected]> 写于 2014-08-14 16:00:18: > > > <[email protected]> > > 2014-08-14 16:00 > > > > 收件人 > > > > <[email protected]>, <[email protected]>, > > > > 抄送 > > > > <[email protected]> > > > > 主题 > > > > Re: [Softwires] New Version Notification for draft-fsc-softwire- > > dhcp4o6-saddr-opt-00.txt > > > > Hi Linda, > > > > Please see below. > > > > Thanks, > > Ian > > > > 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. > > > > [ian] For lw4o6 (and other A+P based softwire mechanisms), the > > provisioning system for client softwire configuration and the > > softwire border router (lwAFTR) have to be completely aligned so > > that traffic can be correctly routed. > > > > If you have dynamic IP address leasing, as is possible with > > DHCPv4o6, then the border router has to be updated with the current > > client address leases and also the IPv6 addresses that are being > > used as tunnel endpoints. > > > > As the DHCPv4o6 server is managing the address leasing, this draft > > provides a way that it can also store the IPv6 address that it’s > > clients will use for building their softwire tunnels meaning that > > there is a single point in the network storing this information. > > This information will then be used to synchronise the binding table > > in the border router, although how this is done isn’t in the scope > > of this draft. > > > > http://datatracker.ietf.org/doc/draft-liu-softwire-lw4over6-dhcp-deployment > > / describes the overall architecture in more details.
_______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
