Ivan My understanding is that while a previous prefix cannot be removed by setting the lifetime to 0 (for the reason you cited) it can be deprecated instantly by setting the preferred timer to 0. Which has the same net effect of using the new prefix. -éric
-----Original Message----- From: ipv6-wg-admin@ripe.net [mailto:ipv6-wg-admin@ripe.net] On Behalf Of Ivan Pepelnjak Sent: mercredi 27 juillet 2011 10:26 To: 'Tim Chown' Cc: ipv6-wg@ripe.net Subject: RE: [ipv6-wg] dynamic or static IPv6 prefixes to residential customers
There's a minimum timeout of 2 hours hard-coded in the SLAAC RFC to prevent DoS attacks. Some details here:
http://blog.ioshints.info/2010/12/small-site-multihoming-in-ipv6-mission.htm...
Then there's the failure to detect PPPoE session loss:
http://blog.ioshints.info/2010/10/dhcpv6-over-pppoe-total-disaster.html
Last but definitely not least, CPEs tend to copy lease time from DHCPv6 PD to SLAAC prefix validity time (and I found no way to change that behavior in Cisco IOS), so you either overload your DHCPv6 server by using short leases or risk having delegated prefixes that will stay in the customer's CPEs for a long time.
Ivan
-----Original Message----- From: ipv6-wg-admin@ripe.net [mailto:ipv6-wg-admin@ripe.net] On Behalf Of Tim Chown Sent: Wednesday, July 27, 2011 4:08 PM To: ipv6-wg Subject: Re: [ipv6-wg] dynamic or static IPv6 prefixes to residential customers
On 27 Jul 2011, at 14:45, Ivan Pepelnjak wrote:
Unfortunately you have to do static prefix delegation because it's impossible to renumber the customer's inside LAN within a reasonable time interval with today's state of IPv6 SLAAC.
Why impossible?
Tim