[v6ops] Re: v6ops Digest, Vol 168, Issue 29

[Daryll Swer <[e-mail]>]

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

I am not following this. So in SP networks that I built myself, residential
broadband users gets a permanent (lifetime) /56 ia_pd that never changes
(unless there's drastic re-numbering at ISP level itself). The prefix will
be renewed after the set timer on DHCPv6 server in conjunction with
AAA/RADIUS.

As others have suggested, if you are a large ISP and RIR fees isn't a
problem, the said /56 will become a /48, again permanent (lifetime).

> I think some German telecoms used to do this as a privacy message
I do not entertain conspiracy theories about big bro and dynamic IPs. I'd
rather not discuss “privacy” related on this subject.

> Where are you seeing this irl, and how does it happen?

Oh, this is 100% the case in India, for 99.99% of IPv6-enabled ISP:
1. They only give a /64 single ia_pd — there goes VLANs.
2. The ia_pd changes upon reboot/every few hours
3. End users complain about broken IPv6 for #2, I've seen it myself, that's
why I opted for my own /32 RIR assigned block.

A few example ASes? AS9498, AS9829 etc.

You can pretty much just Google “Dynamic IPv6 breaks SLAAC” and find tons
of complaints from users all over the world.

Documented here neatly:
https://www.6connect.com/blog/is-your-isp-constantly-changing-the-delegated-ipv6-prefix-on-your-cpe-router/

*--*
Best Regards
Daryll Swer
Website: daryllswer.com
<https://mailtrack.io/l/3ededf2b5c95f30f02a7519c30645e5c5467e868?url=https%3A%2F%2Fwww.daryllswer.com&u=2153471&signature=1ed1c5c8c261169a>


On Sat, 10 Aug 2024 at 03:43, Ted Lemon <[e-mail]> 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]>
>
>> 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]> 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]>
>>> 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]>
>>>> 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]
>>>> >     To unsubscribe send an email to [e-mail]
>>>> >
>>>>
>>> _______________________________________________
>>> v6ops mailing list -- [e-mail]
>>> To unsubscribe send an email to [e-mail]
>>>
>> [image: 45efe8dfc775213ded0fc41c7d84ccccb0d6aa20]
>> _______________________________________________
>> v6ops mailing list -- [e-mail]
>> To unsubscribe send an email to [e-mail]
>>
>