That doesn't really deal with a change of address at the client. As an
example, I'm thinking of a CE that changes its address regularly for
privacy reasons. Of course, one answer you may give me is that
autonomous address changes by the CE are out of scope or not allowed.
Tom
On 02/07/2014 12:32 AM, Qi Sun wrote:
Dear Tom,
Thanks for the comment.
There is some text in the Sec 9 in draft-ietf-dhc-dhcpv4-over-dhcpv6-09, which
may be related to this:
If the IPv6 configuration that contained the 4o6
Server Address option subsequently expires, or if the renewed IPv6
configuration does not contain the 4o6 Server Address option, the
client MUST stop using DHCPv4 over DHCPv6 to request or renew IPv4
configuration. However, the client continues to request 4o6 Server
Address option in the messages sent to the DHCPv6 server as long as
it desires to use DHCPv4 over DHCPv6.
So if a CE changes the binding IPv6 address in the context of normal DHCPv6
operation, it has a chance to update the information to the DHCP server.
Best Regards,
Qi
On Jul 2, 2014, at 10:46 AM, Tom Taylor <[email protected]> wrote:
Suppose a CE changes the IPv6 address it uses for tunnel endpoint subsequent to
the initial establishment of the tunnel. What would the message flow be between
the CE and the DHCP server(s) to update the latter?
Tom Taylor
On 01/07/2014 7:28 AM, Qi Sun wrote:
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
...
_______________________________________________
Softwires mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/softwires
