Re: Address privacy (was: Re: RFC4941bis: consequences of many addresses for the network)

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 25 January 2020 19:21 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 AD8D1120071 for <ipv6@ietfa.amsl.com>; Sat, 25 Jan 2020 11:21:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 y-3AUukw-XoX for <ipv6@ietfa.amsl.com>; Sat, 25 Jan 2020 11:21:25 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B06BB120044 for <ipv6@ietf.org>; Sat, 25 Jan 2020 11:21:24 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id F40FD3897B; Sat, 25 Jan 2020 14:20:44 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id EC7EA1419; Sat, 25 Jan 2020 14:21:19 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ted Lemon <mellon@fugue.com>
cc: Christian Huitema <huitema@huitema.net>, 6man WG <ipv6@ietf.org>
Subject: Re: Address privacy (was: Re: RFC4941bis: consequences of many addresses for the network)
In-Reply-To: <CBB23ABE-A7A3-4208-873C-E47EE063E34B@fugue.com>
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>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.1.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Sat, 25 Jan 2020 14:21:19 -0500
Message-ID: <11855.1579980079@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/xvGxpWixnSaXOqajTcmmTMcaXto>
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: Sat, 25 Jan 2020 19:21:27 -0000

Ted Lemon <mellon@fugue.com> wrote:
    > Another solution that could be useful is to do connections through an
    > anonymity concentrator that tunnels your flow to the selected server.
    > The idea here is that your ISP (but it doesn’t have to be your ISP!)
    > has a bunch of anonymity boxes sitting in their data centers, and when
    > you want to connect to foo.com <http://foo.com/>, you establish a
    > connection to the anonymity server.   The anonymity server constructs a
    > new 5-tuple using its own fixed IP address.   This is effectively a NAT
    > translation, and of course it can maintain a set of IP addresses large

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 Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-