Re: [Ila] [5gangip] Fwd: New Version Notification for draft-herbert-ipv6-prefix-address-privacy-00.txt

Mikael Abrahamsson <swmike@swm.pp.se> Wed, 21 February 2018 14:55 UTC

Return-Path: <swmike@swm.pp.se>
X-Original-To: ila@ietfa.amsl.com
Delivered-To: ila@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CC51127419; Wed, 21 Feb 2018 06:55:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level:
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 ynL0Gy1KNImw; Wed, 21 Feb 2018 06:55:35 -0800 (PST)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11585126DFB; Wed, 21 Feb 2018 06:55:35 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id CF1DDAF; Wed, 21 Feb 2018 15:55:32 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1519224932; bh=xUfRX4Th9SPgm02tXGN7mf1yTPEwlqcDu0dBZ97OrTc=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=Ufvi1SGt6IOkYh9T3AJZ5ZhvpeOJ6nrcozsCK78/DLuay49Jb0MgP6MJeDM2EhLQH y7+yZC95k3biScCVvu3Dgvg8jnTRMEBbb3HgvO57D8Z35oLefvrieuJpT8JpjKu4JM ++oPMX2JBk7eCdWFcYilNhg6v4rR2I9vABp9ozLg=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id CCF4F9F; Wed, 21 Feb 2018 15:55:32 +0100 (CET)
Date: Wed, 21 Feb 2018 15:55:32 +0100
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Tom Herbert <tom@quantonium.net>
cc: int-area@ietf.org, ila@ietf.org, 5GANGIP <5gangip@ietf.org>
In-Reply-To: <CAPDqMeqajavRJ85fUkrdxg1Bjz54kHuWfqbnGgpM7Br7T6MVmQ@mail.gmail.com>
Message-ID: <alpine.DEB.2.20.1802211549260.3478@uplift.swm.pp.se>
References: <151906718318.18731.8986618406430268357.idtracker@ietfa.amsl.com> <CAPDqMeqajavRJ85fUkrdxg1Bjz54kHuWfqbnGgpM7Br7T6MVmQ@mail.gmail.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ila/OEtUNlajipzxA65HSUBIhk2pZAY>
Subject: Re: [Ila] [5gangip] Fwd: New Version Notification for draft-herbert-ipv6-prefix-address-privacy-00.txt
X-BeenThere: ila@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Identifier Locator Addressing <ila.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ila>, <mailto:ila-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ila/>
List-Post: <mailto:ila@ietf.org>
List-Help: <mailto:ila-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ila>, <mailto:ila-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Feb 2018 14:55:38 -0000

On Mon, 19 Feb 2018, Tom Herbert wrote:

> This draft discusses issue of privacy in IPv6 network prefix assignment. 
> Specifically the privacy problems of an assigned network prefix becoming 
> a persistent identifier for devices (e.g. /64 assignment to devices in 
> mobile networks).  The use of identifier/locator split is suggested as a 
> solution.

Current state of available address for a PDN is /64. In most 
implementations I am aware of, if the PDN is brought down, and then up 
again, a new /64 will be used. The host can therefore control this part of 
"privacy", cycle PDN when it feels it's appropriate to get new address 
space to avoid tracking. I am supportive of this approach and any spatial 
overlap of multiple PDNs/address space approach, so that connections can 
be moved over to use the new address, gracefully.

I consider anything that gives the host less than /64 worth of addresses a 
regression from current situation. We can always discuss if /80 is enough 
etc, but anyhow, it's a regression that should be presented front and 
center by any proposed change to current state of affairs.

I have now read section 6 twice, and I still have no idea how many usable 
addresses the host has available to itself according to 
draft-herbert-ipv6-prefix-address-privacy-00.

Can you please enlighten me?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se