Re: [Softwires] New Version Notification for draft-fsc-softwire-dhcp4o6-saddr-opt-00.txt

[[e-mail]]

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 :)

  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?

  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?
 
  Nothing else.

  Thanks a lot.

BRs,
Linda Wang


<[e-mail]> 写于 2014-08-14 16:00:18:

> <[e-mail]> 
> 2014-08-14 16:00
> 
> 收件人
> 
> <[e-mail]>, <[e-mail]>, 
> 
> 抄送
> 
> <[e-mail]>
> 
> 主题
> 
> 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.