[v6ops] Re: Dynamic addresses

[Tim Chown <[e-mail]>]

Hi,

From: Brian E Carpenter <[e-mail]>
Date: Saturday, 10 August 2024 at 00:28
To: Ted Lemon <[e-mail]>, Daryll Swer <[e-mail]>
Cc: The Multach's <[e-mail]>, [e-mail] <[e-mail]>
Subject: [v6ops] Dynamic addresses
[Public service announcement: as of now, I'm spam-filtering messages with 'Digest' subject headers.]

My ISP used to change my prefix whenever there was a power cut and the modem restarted. Now, it appears to be stable.

But I don't understand the statement "breaks SLAAC on the LAN". A change of prefix renumbers the LAN, but that doesn't break SLAAC, it just causes SLAAC to renumber everything. It will only break active sessions.

If the 6724-update draft does advance, at least where that’s implemented and ULAs are advertised local communications will not be affected.

Tim


Regards
    Brian

On 10-Aug-24 10:13, Ted Lemon wrote:
> In order to do this, they would have to not renew a previously assigned prefix. I think some German telecoms used to do this as a privacy message, but it was operationally very difficult because it doubled demand for prefixes.
>
> Where are you seeing this irl, and how does it happen?
>
> Op vr 9 aug 2024 om 15:08 schreef Daryll Swer <contact=[e-mail] <mailto:[e-mail]>>
>
>     Tim, is there something we can do to encourage not only "more than a /64", but also encourage "static ia_pd to ensure the customer will not experience broken IPv6 connectivity due to ever changing prefixes".
>
>     Too many ISPs out there do dynamic IPs and breaks SLAAC on the LAN.
>
>     I feel this draft could be a powerful tool, in the hands of the end user to get these ISPs doing the right way of IPv6 more often.
>
>     --
>     Sent from my iPhone
>
>
>     On Fri, 9 Aug 2024 at 7:37 PM, Timothy Winters <[e-mail] <mailto:[e-mail]>> wrote:
>
>         Yes.  I've seen several instances of /64 being used for container networks on CPEs.
>
>         ~Tim
>
>         On Fri, Aug 9, 2024 at 9:38 AM The Multach's <[e-mail] <mailto:[e-mail]>> wrote:
>
>             So are these considered a LAN link prefix assignment under 7084 L2:
>
>             - Assignment of a /64 prefix for internal IPv6 communication between a
>             primary SoC and a secondary chip (e.g., a Wi-Fi chip which uses IPv6).
>
>             - Assignment of a /64 prefix for usage by an internal container or VM.
>
>
>             On 8/9/2024 7:56 AM, Timothy Winters wrote:
>              >
>              >
>              > On Thu, Aug 8, 2024 at 10:58 PM The Multach's <[e-mail] <mailto:[e-mail]>> wrote:
>              >
>              >     The following, while being user focused, fails to take into
>              >     account that
>              >     some of those prefixes may be used internally (or reserved for
>              >     internal
>              >     use) by the CPE or for ISP purposes and not assignable:
>              >
>              >     "SHOULD" (or an elongated exception for the above) would be more
>              >     appropriate.
>              >
>              >     LPD-4: After LAN link prefix assignment the IPv6 CE Router MUST
>              >     make the
>              >     remaining IPv6 prefixes available to other routers via Prefix
>              >     Delegation.
>              >
>              > I think this covers that case.   After local assignment, unused
>              > prefixes MUST be made available.
>              > LPD-2:  The IPv6 CE Router MUST assign a prefix from the delegated
>              >            prefix as specified by L-2 [RFC7084].
>              >
>              > 7084
>              >    L-2:   The IPv6 CE router MUST assign a separate /64 from its
>              >           delegated prefix(es) (and ULA prefix if configured to provide
>              >           ULA addressing) for each of its LAN interfaces.
>              >
>              >
>              >     _______________________________________________
>              >     v6ops mailing list -- [e-mail] <mailto:[e-mail]>
>              >     To unsubscribe send an email to [e-mail] <mailto:[e-mail]>
>              >
>
>         _______________________________________________
>         v6ops mailing list -- [e-mail] <mailto:[e-mail]>
>         To unsubscribe send an email to [e-mail] <mailto:[e-mail]>
>
>     45efe8dfc775213ded0fc41c7d84ccccb0d6aa20​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​ _______________________________________________
>     v6ops mailing list -- [e-mail] <mailto:[e-mail]>
>     To unsubscribe send an email to [e-mail] <mailto:[e-mail]>
>
>
> _______________________________________________
> v6ops mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
_______________________________________________
v6ops mailing list -- [e-mail]
To unsubscribe send an email to [e-mail]