Re: A common problem with SLAAC in "renumbering" scenarios

[JORDI PALET MARTINEZ <[e-mail]>]

    Mark Smith wrote on 14/02/2019 04:46:
    > So to me, the cheapest and best solution is for the an ISP to provide
    > a static/stable PD prefix to the customer (even though I've written
    > code to try to mitigate it i.e. . DeprecatePrefix and
    > DecrementLifetimes in radvd in the past.)
    
    Mark,
    
    Largely, I agree with your rationale on this.  The problem is that ISPs 
    will be loath to commit to a stable prefix for the lifetime of a 
    customer account.  This approach doesn't scale for larger providers 
    because it commits them to making routing compromises for the lifetime 
    of customer accounts, e.g. injecting dynamically assigned prefixes into 
    their routing tables.  Accretion of configuration fossils causes long 
    term complexity problems.


Why not? This is already happening in IPv4. I've got from a major operator in Spain (and other operators in other countries do the same), the same IPv4 address for decades! I'm talking about residential services, with both DSL and GPON. Not to mention business services were you actually pay for that static address a monthly fee.

Any contract can have special clauses, that clearly indicate that "in case of major technology or network changes or similar events, renumbering can happen and in those situations the customers will be alerted with a minimum of 1 month" (this is just an example, I can think in many alternative wordings).
    
    



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.