andre at tomt.net
Thu Feb 14 15:55:47 CET 2013
On 13. feb. 2013 18:14, Bernd Walter wrote:
> With the current IPv4 situation they put everything into clouds with all
> the security implications.
> My hope was that with IPv6 the return of static addresses will come back
> again the way I was used from the early days when I started using the
> But they get dynamic prefixes and most providers (of which some have
> little choice) only offer static address option for commercial customers.
> Same as with IPv4, where end users can't opt for static address(es).
> You need a registered business to get such a contract - sigh.
> With IPv6 there is an implication because it is not only the single
> public address which change - the whole internal network gets renumered
> on redial-in.
> The IPv6 based light switch can't talk to the IPv6 based light bulb anymore
> for some time fraction because your DSL flapped.
> There are some slow transition mechanics, but those are limited to a small
> overlapping time - don't forget another ISP customer might use your
> prefious network now.
> The public addresses changes - no matter how you handle this situation.
> The only option is to use internal addresses.
> Link local addresses won't allow a split network, although many people
> live with a single flat network at home this is not really advised with
> home automation in place.
> ULA addresses are required as the only solution since PI are even less
> available than static PA.
If your prefix changes every time you dial in then your ISP is broken.
The norm for dynamic prefixes are long leasetimes and mapping stored
persistently by DUID and/or customer. There are some edge cases where
the prefix can change, but "dialling in" or reconnecting should not be
one of them. If you see something else in the field, please shame 'em :)
More information about the ipv6-ops