Re: Address privacy

Fernando Gont <fgont@si6networks.com> Tue, 28 January 2020 01:52 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA8D53A0855 for <ipv6@ietfa.amsl.com>; Mon, 27 Jan 2020 17:52:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iiOzdJjrNmSK for <ipv6@ietfa.amsl.com>; Mon, 27 Jan 2020 17:52:44 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D80F43A0858 for <ipv6@ietf.org>; Mon, 27 Jan 2020 17:52:43 -0800 (PST)
Received: from [192.168.100.103] (unknown [186.183.48.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 4F5DB86B9E; Tue, 28 Jan 2020 02:36:46 +0100 (CET)
Subject: Re: Address privacy
To: Michael Richardson <mcr+ietf@sandelman.ca>, 6man WG <ipv6@ietf.org>
References: <03C832CE-7282-4320-BF1B-4CB7167FE6BE@employees.org> <MN2PR11MB3565330989D411525D30B90DD80F0@MN2PR11MB3565.namprd11.prod.outlook.com> <80207E17-AE8E-4D19-B516-D2E6AB70721E@employees.org> <8D5610EA-49D3-483E-BB7A-67D67BC89346@jisc.ac.uk> <DE7B0688-230F-4A5C-8E24-9EAED9FD9FEB@puck.nether.net> <CAO42Z2zXwVnzemRqyqy78czpHjZm0nhkCJgVrx=-fmt+C6MnSA@mail.gmail.com> <1962.1579823388@localhost> <f83ab037-9125-bb74-dbac-68850aeb1020@huitema.net> <CBB23ABE-A7A3-4208-873C-E47EE063E34B@fugue.com> <11855.1579980079@localhost> <CALx6S36V_VjaxhELYcsgDYLWsCkj20p6gtiY9T9Q=9-9Oibyjw@mail.gmail.com> <32626.1580060558@localhost>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <dff9a76d-c813-efd5-950c-9660e7607ba9@si6networks.com>
Date: Mon, 27 Jan 2020 20:32:44 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <32626.1580060558@localhost>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/1JjPYR7_FfJ6uQH9mEJfnKnbnNM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2020 01:52:46 -0000

On 26/1/20 14:42, Michael Richardson wrote:
> 
> Tom Herbert <tom@herbertland.com> wrote:
>      >> Except that instead of doing it at layer 4, you do it with IPsec, and extrude
>      >> that /128 to your machine.  This is already a thing :-)
>      >>
>      >> > Another solution I’ve considered is to have a giant anonymity mesh,
>      >> > with every ISP’s user participating, and forward flows through this
>      >> > mesh, treating each customer as an anonymity server.   I think this is
>      >>
>      >> This is also a thing called Tor.
>      >>
>      > Michael,
> 
>      > Doesn't that require that the users must explicitly configure when
>      > they want privacy? I think a general solution should be transparent to
> 
> Yes, I agree, it requires explicit configuration.
> I agree that this is not a good thing.
> 
>      > the user and "just works" to ensure their privacy. That in fact is one
>      > of the arguments for NAT. If there is a significantly large enough
>      > pool of users behind a NAT device, then the obfuscation is transparent
>      > to the use and seems to be pretty good privacy (good enough that law
>      > enforcement is concerned about NAT). I suppose a similar effect could
>      > be achieved with a transparent proxy.
> 
> Yes, and I think that more and more LEA will grow ever concerned about this
> situation, and it *is* pushing IPv6 adoption. 

This somehow implies that criminals are expected to switch to v6 rather 
than continue to use v4 to hide their activities.


-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492