[v6ops] Alissa Cooper's Discuss on draft-ietf-v6ops-unique-ipv6-prefix-per-host-12: (with DISCUSS)

Alissa Cooper <alissa@cooperw.in> Thu, 12 October 2017 13:53 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: v6ops@ietf.org
Delivered-To: v6ops@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AC3E134515; Thu, 12 Oct 2017 06:53:46 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper <alissa@cooperw.in>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-v6ops-unique-ipv6-prefix-per-host@ietf.org, Ron Bonica <rbonica@juniper.net>, draft-ietf-v6ops-unique-ipv6-prefix-per-host.all@ietf.org, v6ops-chairs@ietf.org, rbonica@juniper.net, v6ops@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150781642636.16695.9645155481311700959.idtracker@ietfa.amsl.com>
Date: Thu, 12 Oct 2017 06:53:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/P2nawYd_ghaJ3GdjS5Ej92zMI8I>
Subject: [v6ops] Alissa Cooper's Discuss on draft-ietf-v6ops-unique-ipv6-prefix-per-host-12: (with DISCUSS)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 12 Oct 2017 13:53:46 -0000

Alissa Cooper has entered the following ballot position for
draft-ietf-v6ops-unique-ipv6-prefix-per-host-12: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-v6ops-unique-ipv6-prefix-per-host/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

I've put in a DISCUSS because I think the point I raise below warrants further
discussion, unless the WG already discussed it and concluded otherwise.

Section 7 says:

"However, when combining both IPv6 privacy extensions and a unique
   IPv6 Prefix per Host a reduced privacy experience for the subscriber
   is introduced, because a prefix may be associated with a subscriber,
   even when the subscriber implemented IPv6 privacy extensions RFC4941
   [RFC4941]."

If an operator assigns the same unique prefix to the same host every time the
host connects to the network, the unlinkability benefits of using IPv6 privacy
extensions are completely negated. It seems reasonable to me for this document
to normatively RECOMMEND that operators assign a different unique prefix to a
returning host for the purpose of limiting linkability to the lifetime of the
host's connection to the network. I'm sure there are exception cases where this
wouldn't make sense, and some examples of those could be given. But by default
this seems to me like a reasonable recommendation to mitigate the privacy risk
introduced by the unique prefix, while the attacks described in Section 1 would
also still be mitigated.

Did the WG discuss this?