Hi Ivan et. al,

On top of these problems add the incorrect RFC behavior of MS (i.e. Win 7) clients when dealing prefixes whose lifetime is set to 0) and you end up puzzled. Should I deploy IPv6 on on top of PPPoE ? or directly on ethernet ifces ? should I ask my CPE vendors to break the strict RFC behavior ( for MS clients)?

Cheers,
Dimitris

On 27/7/2011 5:26 μμ, Ivan Pepelnjak wrote:

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.html

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

-- 
------------------------

Dimitrios K. Kalogeras

Electrical Engineer Ph.D.
Network Engineer
Netmode NTUA Lab
_____________________________________
skype: aweboy
voice: +30-210-772 1448
fax:     +30-210-772 1866
e-mail: D.Kalogeras@noc.ntua.gr