[DMM] Mirja Kühlewind's Discuss on draft-ietf-dmm-4283mnids-04: (with DISCUSS)
"Mirja Kuehlewind" <ietf@kuehlewind.net> Fri, 10 February 2017 17:08 UTC
Return-Path: <ietf@kuehlewind.net>
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 50D0E129A50; Fri, 10 Feb 2017 09:08:07 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mirja Kuehlewind <ietf@kuehlewind.net>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148674648728.29247.8373715746303934157.idtracker@ietfa.amsl.com>
Date: Fri, 10 Feb 2017 09:08:07 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/pTUO1dCYegfyqY7nAJwOfeo6eFo>
Cc: max.ldp@alibaba-inc.com, draft-ietf-dmm-4283mnids@ietf.org, dmm-chairs@ietf.org, dmm@ietf.org
Subject: [DMM] Mirja Kühlewind's Discuss on draft-ietf-dmm-4283mnids-04: (with DISCUSS)
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 10 Feb 2017 17:08:10 -0000
Mirja Kühlewind has entered the following ballot position for draft-ietf-dmm-4283mnids-04: 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 would realy like to see the following changes in the security considerations section: OLD "If used in the MNID extension as defined in this document, the packet including the MNID extension should be encrypted so that personal information or trackable identifiers would not be inadvertently disclosed to passive observers." NEW "If used in the MNID extension as defined in this document, the packet including the MNID extension SHOULD be encrypted so that personal information or trackable identifiers would not be inadvertently disclosed to passive observers." Or even better make it a MUST? Is there a reason for only having a SHOULD? as well as the following change: OLD "Moreover, MNIDs containing sensitive identifiers might only be used for signaling during initial network entry. " NEW "Moreover, MNIDs containing sensitive identifiers MUST only be used for signaling during initial network entry and MUST NOT be leaked to other networks."
- [DMM] Mirja Kühlewind's Discuss on draft-ietf-dmm… Mirja Kuehlewind
- Re: [DMM] Mirja Kühlewind's Discuss on draft-ietf… Suresh Krishnan
- Re: [DMM] Mirja Kühlewind's Discuss on draft-ietf… Mirja Kuehlewind (IETF)
- Re: [DMM] Mirja Kühlewind's Discuss on draft-ietf… Charlie Perkins
- Re: [DMM] Mirja Kühlewind's Discuss on draft-ietf… Suresh Krishnan
- Re: [DMM] Mirja Kühlewind's Discuss on draft-ietf… Mirja Kühlewind
- Re: [DMM] Mirja Kühlewind's Discuss on draft-ietf… Charlie Perkins
- Re: [DMM] Mirja Kühlewind's Discuss on draft-ietf… Mirja Kühlewind