On Wed, 25 Mar 2015, JF Tremblay wrote:
Actually, why would the customer trigger this? Is there a good use case
for this? In my mind, this is purely triggered from the ISP side, when a
network event is planned to happen.
Because some customers feel that changing addresses is a privacy thing.
They might want their ISP to provide a CPE with a button that says "change
home prefix now".
Here’s a cable-oriented scenario (sorry, this is my background). In the cable
world, providing a perfectly stable prefix for home customers is quite
challenging, because the underlying physical network changes on a regular basis
to accommodate physical network growth and changes (usually once or twice a
year per user). It’s possible to provide stable prefixes, but it involves
significant engineering and operational effort (hence a cost).
An alternative for cable operators is to provide smooth IPv6 renumbering.
Here’s how it could work. This is basically a simpler flavor of RFC4192.
1. The customer gets PD1 from CMTS A. (a /56 out a /40 for example). Stable
operation.
2. A week in advance of a network change, a move from CMTS A to CMTS B, the
customer gets a reduced DHCPv6 lease time to 24h.
3. 24h before the change, the client gets two prefixes PD1 and PD2, out of A
and B /40s respectively. PD1 has a preferred lifetime of 0 and a valid lifetime
of 24h.
How does it "get" PD2? This is what I don't understand. You just all of a
sudden next time the DHCPv6-PD communication happens, send two prefixes
and then the client will accept these and start using them? The home
gateway doesn't actually have to ask for it, you can just send it a bunch
of prefixes?
--
Mikael Abrahamsson email: [email protected]
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
