Re: IPv6 support in d-i

Hi,

On Sat, Sep 08, 2012 at 03:03:56PM +0200, Michelle Konzack wrote:
> Hello Florian Lohoff,
> 
> Am 2012-09-08 13:30:39, hacktest Du folgendes herunter:
> > NAT64 breaks to much stuff - My humble guess working for ISPs and
> > dealing with IPv6 introduction is that we will see DualStack "forever"
> > with RFC1918 adresses and NAT44 ...
> 
> I consider already to give Static IPv6 adresses to my customers (free.fr
> and alice-dsl.de do the same) which should solv some problems...
> 
> What do you think about?

I'd like to see that happening - The Internet or IP was always thought
as a peer to peer or "any to any" communication protocol. With NAT
and Dynamic IP Addresses breaking this principle. There was no
server and no client definition in the original thoughts of IP.

> I have more IPv6 addresses,  as  I  need  to  provide  Baden-Wuertemberg
> internet access and take over Google.  :-D

My guess is that our "Privacy" people will prohibit static prefixes
for subscribers. Most people havent heard about privacy extensions and
the size of prefixes e.g. /56 where to hide a single workstation.

Tracking subscribers or users by cookies is much simpler than by IP
Address.

Flo
-- 
Florian Lohoff                                                 [email protected]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQIVAwUBUEuWnpDdQSDLCfIvAQjWYxAAmEM6LjHYIvE3x+qJFYNrorIVyRWC/DZk
tqpZ/iEn4qSZiX92l5xY53oHZGE9HIFWwyPkS4uyqbOV5Wa1OXhN4vfN6i1rGrbR
SHoKmzOKdA2YRGRavle73ehB4ecB0uVT+R9LhZz3WuR3NXqSjSZ0Kb3jmiY9FQzo
ty+wQjU8YgEwOfyQIQfze8VFcKqhPpym4fLh2gVAl34k2Ai3U9T+McDs3KJYzXqx
cPYHu0r6e6q7EaK0LBV4AHubxCjFI+CtjR6mNzaySA6reOomumJAlWoWIErO7k1H
+EAm2FZJ6kNX4iPt2xbFiqLrennhBO8gNkSdslFXKFQKCAdGdqRyccZ4ns/XG0fF
WRNwTJXoyKgVzjGLCxeZAQPZffAJWbDS1fC2KqDe7F5Y5pPPdgsFYdcj7jsDaOKe
FaMGZa6uyZCS09qY+CK+it8unfHjSozWOP5+C0KCI+xGDKKGgDytDH1xMYpwEY9p
YXcYaJNTbMKvk/NoLUB/m7FqMj81uF8LMsLplsP3KwNdxQNKNsTifgBM2xSNP6Wp
KzSdH6Oi/TvO3HLduGBiMoiJR7PvKDhutQia2zcnk/tE56yBei5tfDBaea/RMFjt
LnKHS/a21HLxycKS58zA0sgkE0Ii+fzFuT3RpitiGYEa2132+SegX4ekjE7mH4YU
bWn8bvXN28E=
=2qBE
-----END PGP SIGNATURE-----