Re: [v6ops] Is addressing privacy via NAT really achieving much compared to a privacy goal of anonymity? (Re: A common problem with SLAAC in "renumbering" scenarios)

Tom Herbert <tom@herbertland.com> Fri, 22 February 2019 17:11 UTC

Return-Path: <tom@herbertland.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB6A6130F32 for <v6ops@ietfa.amsl.com>; Fri, 22 Feb 2019 09:11:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.com
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 VVJIyUHX_Lnb for <v6ops@ietfa.amsl.com>; Fri, 22 Feb 2019 09:11:22 -0800 (PST)
Received: from mail-qt1-x844.google.com (mail-qt1-x844.google.com [IPv6:2607:f8b0:4864:20::844]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D16E8130F14 for <v6ops@ietf.org>; Fri, 22 Feb 2019 09:11:21 -0800 (PST)
Received: by mail-qt1-x844.google.com with SMTP id s1so3307477qte.5 for <v6ops@ietf.org>; Fri, 22 Feb 2019 09:11:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HhY23CnDz/ABwxl23wmePBRcOWqV/h5kk2zb2avDqQs=; b=ejR53xV8fcDqDT1uWpY2LtkWdgKTSfTiUpxjkG8fg0CsqKkjsm4k7I5ZvPdiCIMtoR 13wmueOZJZ7XaL9XaBDFZN9HtVA4RL+L9xlDeHHENUhww+hxFVu1uQPeaMIcGPVwL3Ul e02Q0IPaLzffuoDZuxJlZ5pNGb7qc+Hbt390Qd2JJUYPs2NSmc4kzQzWuV9dgqEdyhpq dJpFaYJABuPCwm0Bs7isq5rnn+8/IP6CnM6Gz0qZ8nPcp5ZHM/IL0YUFO5F1kM7lgNZp uDGTJRrOXRqJX5LeIYq+7+BWBSKgnV8xQeTXj7CBkpxkDSvrFya2G8N7PE+1+vrJjwtT yYHg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HhY23CnDz/ABwxl23wmePBRcOWqV/h5kk2zb2avDqQs=; b=EL7BRWYdIrvvQ4Kj45ZNV3ZYVQv2yzThMLzlPOT4XmXgt3rxhYsX/jITpNBmOAd//4 R6Mr0niLYYtEgxm63/5OoKB5b+Xu9k7BrqlzVDEhkK9JXWAnXIYpgLEMej6U/fzv2R/Q wRAEvATV0837Qt5NOFGYymaKwlekDtd8MPZwjmQkvq34dWICYPyVYo3cz7wrs6wfjuep kcI2wmbWk4KdsnSdSBSA4FJKTy9XOHqMRTXchyve++b0b7+qLsqulp6sN4dKvvEryfgA sAyDD78pj9TM8wlIH1Xu+cZtSWmnH03WKOuZxOmLKdnZ723qlB4gZPShVfqJb6yoqtMh y8yg==
X-Gm-Message-State: AHQUAuadm3/Ux71H2iR/pn4fKrqGxh/hctVhM911pNmtc1avrXlMgrF7 94qurdiqQF8l0QIinTl1p3Fht4oQyV4mS+MnyT5tVg==
X-Google-Smtp-Source: AHgI3IbIFqUjbi7vOPnxWWJaQamHmzKhlcq5EHWaYWTvMJc/mub07qGPvAsEKy2mX/gAMQyyooD4+8aQoEOVzdkVFvg=
X-Received: by 2002:a0c:8dc2:: with SMTP id u2mr3969836qvb.168.1550855480581; Fri, 22 Feb 2019 09:11:20 -0800 (PST)
MIME-Version: 1.0
References: <6D78F4B2-A30D-4562-AC21-E4D3DE019D90@consulintel.es> <B6E2EC33-EEAF-40D0-AFCC-BDAFA9134ACD@consulintel.es> <20190220113603.GK71606@Space.Net> <28fbc2c305c640c9afb3704050f6e8d7@boeing.com> <20190220213107.GS71606@Space.Net> <019c552eb1624d348641d6930829fd1f@boeing.com> <CAKD1Yr0HBG+rhyFWg9zh0t3mW486Mjx9umjn+CRqAZg4z9r0dg@mail.gmail.com> <20190221073530.GT71606@Space.Net> <CAO42Z2wmB2W52b4MZ2h9sW5E9cQKm-HRjyf--q8C26jezS7LXQ@mail.gmail.com> <a73818d31db7422b99a524bc431b00ed@boeing.com> <CAO42Z2z9-48Gbb_Exf+oWUqDO=axSLpZBtqeDcxkAoFq5OziGw@mail.gmail.com> <CALx6S3624hnGauG1HaSWPMvQw0t2Q5R3gb8W4R8w3kuK7dcrWQ@mail.gmail.com> <CAO42Z2wOyTDrp5FNnBZ6KMOPT86o6n8rWRhXWdtSU_AOR9mV2A@mail.gmail.com>
In-Reply-To: <CAO42Z2wOyTDrp5FNnBZ6KMOPT86o6n8rWRhXWdtSU_AOR9mV2A@mail.gmail.com>
From: Tom Herbert <tom@herbertland.com>
Date: Fri, 22 Feb 2019 09:11:09 -0800
Message-ID: <CALx6S37FQVx=Hw3yLGfg-SkCwECc1JZkbcsqxrYLw6Pw5izdfw@mail.gmail.com>
To: Mark Smith <markzzzsmith@gmail.com>
Cc: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>, IPv6 Operations <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/skQ3TLbQ3U1WzKgyIUKujZmmnIU>
Subject: Re: [v6ops] Is addressing privacy via NAT really achieving much compared to a privacy goal of anonymity? (Re: A common problem with SLAAC in "renumbering" scenarios)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Feb 2019 17:11:24 -0000

On Thu, Feb 21, 2019 at 11:35 PM Mark Smith <markzzzsmith@gmail.com> wrote:
>
> Hi Tom,
>
> On Fri, 22 Feb 2019 at 10:04, Tom Herbert <tom@herbertland.com> wrote:
> >
> > On Thu, Feb 21, 2019 at 2:46 PM Mark Smith <markzzzsmith@gmail.com> wrote:
> > >
> > > On Fri, 22 Feb 2019 at 08:53, Manfredi (US), Albert E
> > > <albert.e.manfredi@boeing.com> wrote:
> > > >
>
> <snip>
>
> > >
> > > So I think there's commonly a big different between works and works
> > > well. NAT may work, however compared to stateless IPv6 (and IPv4)
> > > forwarding, it doesn't work anywhere as near as well.
> > >
> > Mark,
> >
> > I agreee with that with one exception. I believe that NAT/IPv4 can
> > offer better privacy in addressing than IPv6 given current addess
> > allocation methods.
> >
>
> So I don't think addressing privacy via NAT is really all that
> valuable if there are many other ways, some quite easy, to uniquely
> identify an anonymity desiring end-point/end-user, whose effectiveness
> aren't impacted at all by NAT.
>
> For example, this website is coming over IPv4 for me, and I'm using
> IPv4+NAPT. If IPv4+NAPT was that effective at anonymity, I shouldn't
> be able to tracked.
>
> https://amiunique.org/
>
> Yet it is saying I can be with both Chrome and Firefox on Fedora 29 in
> Incognito/Private windows mode on this host. It says the same about my
> Android 9 phone with Chrome in Incognito mode.
>
> Going into the detail of how, they don't seem to be using IP address
> at all for any identification, it is all browser attributes.
>
> We have IPv6 temporary addresses, which makes using addresses harder
> to use to identify a node. I think that is a lot better than nothing.

Mark,

Yes, but by that same rationale a simple substitution cipher is better
than nothing in cryptography!

What pretty much any conversation about privacy in addressing seems to
lacking is a quantitative description of privacy and any empiracal
data on the impact that privacy mechanisms, like those defined in
RFC4941, have had. You might say it "makes using addresses harder to
use to identify a node". But then the obvious question is _how_ much
harder? Is this really protecting anyone's privacy, or it is just a
minor inconvenience to attackers and only giving users a false sense
of security?

The irony is that CGN seems to have the best supporting evidence for
being a mechanism that impacts privacy, but it was never even intended
to be a privacy mechanism. The evidence is in the form of concerns
form law enforcement that the privacy side effect is too strong and
impedes their investigations
(https://www.theregister.co.uk/2017/10/18/europol_cgnat/).

So I don't think "Is addressing privacy via NAT really achieving much
compared to a privacy goal of anonymity?" is the right question. The
right question to ask is "Is addressing privacy via any IETF defined
mechanism achieving much compared to a privacy goal of anonymity?"

Tom

> However, I don't see how IPv6 NAT would improve it much, and it
> introduces the other drawbacks of NAT.
>
> Regards,
> Mark.
>
>
>
>
>
>
>
>
>
>
>
>
> > Tom
> >
> > > Regards,
> > > Mark.
> > >
> > >
> > >
> > > > Bert
> > >
> > > _______________________________________________
> > > v6ops mailing list
> > > v6ops@ietf.org
> > > https://www.ietf.org/mailman/listinfo/v6ops