[DMM] Alissa Cooper's Discuss on draft-ietf-dmm-4283mnids-05: (with DISCUSS)
Alissa Cooper <alissa@cooperw.in> Wed, 04 October 2017 15:32 UTC
Return-Path: <alissa@cooperw.in>
X-Original-To: dmm@ietf.org
Delivered-To: dmm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D6799132320; Wed, 4 Oct 2017 08:32:42 -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-dmm-4283mnids@ietf.org, Dapeng Liu <max.ldp@alibaba-inc.com>, dmm-chairs@ietf.org, max.ldp@alibaba-inc.com, dmm@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150713116283.24119.10845442671289032350.idtracker@ietfa.amsl.com>
Date: Wed, 04 Oct 2017 08:32:42 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/_VOM6Lav38iU6XvUU73LcdSL0XI>
Subject: [DMM] Alissa Cooper's Discuss on draft-ietf-dmm-4283mnids-05: (with DISCUSS)
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Oct 2017 15:32:43 -0000
Alissa Cooper has entered the following ballot position for draft-ietf-dmm-4283mnids-05: 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-dmm-4283mnids/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- I have updated my DISCUSS position. Thanks for addressing my question about identifier types that do not uniquely identify one node. I previously supported Stephen's DISCUSS and I don't think the issues he raised have been addressed. The argument the document gives for standardizing options for privacy-sensitive identifiers is that it "will avoid additional look-up steps." Why is this sufficient justification given the slippery slope that Stephen describes? In my previous ballot I was also wondering if all of these identifiers are already in common use in MIPv6 without a standard, if there is some privacy improvement that standardization could contribute. I see the new requirement for payload encryption, but nothing about, e.g., encrypting the identifiers, or limiting their transmission to the initial binding, or generating a different cryptographic identifier for each new network attachment. So the benefit of just standardizing the options as-is still seems outweighed by the potential privacy risks as this spec is defined.
- [DMM] Alissa Cooper's Discuss on draft-ietf-dmm-4… Alissa Cooper
- Re: [DMM] Alissa Cooper's Discuss on draft-ietf-d… Sri Gundavelli (sgundave)