[ipv6-wg] IPv6 prefix delegation BCOP document - draft v.2 for review.

Hi Jens,

Regarding the stable addresses, I understand what you mean, but data protection people need to realize that with a non-persistent prefix, as it last for several hours/days/months (depending on each ISP policy), people can also be “tracked”, and you will not find an ISP that change the prefix every few minutes, because that will break the customers Internet functionality, right? Not to forget that right now there are much better ways to track people from browsers/big data that believing that addresses identify people. This is a different discussion, but I think is totally wrong to consider IP addresses as personal data, because an address is not a perfect way to identify people.

Regarding prefix length, you’re right in part, but I did a survey that shows that many ISPs are doing it right, we just need to wake up those that do it wrong to improve their deployments. Market competition will help here: because some do correctly, customers may change provider when others do it wrong. Here is the last presentation of the survey:

https://ripe73.ripe.net/programme/meeting-plan/plenary/

Regards,
Jordi
 

-----Mensaje original-----
De: ipv6-wg <ipv6-wg-bounces at ripe.net> en nombre de Jens Link <lists at quux.de>
Organización: - 
Responder a: <lists at quux.de>
Fecha: sábado, 13 de mayo de 2017, 10:16
Para: "ipv6-wg at ripe.net" <ipv6-wg at ripe.net>
Asunto: Re: [ipv6-wg] IPv6 prefix delegation BCOP document - draft v.2 for review.

    Jan Zorz - Go6 <jan at go6.si> writes:
    
    Hi,
    
    > Draft version 2 is now available for reading at
    > https://sinog.si/docs/draft-IPv6pd-BCOP-v2.pdf
    
    I like but I don't see it happening.
    
    1. Stable Addresses - Data protection people will have a hart attack
       when they read this. As will many customers. Don't get me wrong I
       *do* want a stable prefix at home but many people don't. Changing
       addresses gives them some pseudo anonymity and the warm feeling that
       they are not traceable and secure. 
    
       And stable addresses are a way to make money. sys4 has a office in
       Munich and VDSL from M-Net. We pay extra for one stable IPv4 address but
       they wont hand out a stable IPv6 prefix. If you want stable v6 you
       have to buy their SDSL products which are way more expensive. We
       don't want to run any service in the office. We just want stable
       addresses for equipment and some training / lab VMs in the office.
    
    2. Prefix length. I totally agree: Handout a /48 or /56. But this doesn't
       happen right now. And I don't think provider who have v6 now wont
       change their ways of doing things. I'm a customer of Kabel Deutschland
       an I can get either DS-Lite with a /64 or a public IPv4 Address (I
       chose the later an tunnel my own IPv6). For some CPEs (provided by
       KDG) they handout a /62. A friend recently told be about another
       provider handing out /57. Unfortunately the competitors are not much
       better.
    
       Then there are the smalltown providers providing FTTH[1] who think
       that becoming an ISP is easy. They don't become an LIR, they get a
       /2x from their upstream and I guess they wont get much more then a
       /48 *if* they do implement IPv6 (but right now NAT seems to work to
       well and people are happy that they have faster internet then
       before).
    
    Jens
    
    [1] Which is not alwas FTTH. But people know the name from the news.
    -- 
    ----------------------------------------------------------------------------
    | Foelderichstr. 40   | 13595 Berlin, Germany           | +49-151-18721264 |
    | http://blog.quux.de | jabber: jenslink at quux.de        | ---------------  | 
    ----------------------------------------------------------------------------
    
    
    



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

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.