Re: [Int-dir] INT-DIR review of draft-ietf-6lo-privacy-considerations-03

Dave Thaler <dthaler@microsoft.com> Mon, 31 October 2016 19:36 UTC

Return-Path: <dthaler@microsoft.com>
X-Original-To: int-dir@ietfa.amsl.com
Delivered-To: int-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 590A9129AA1; Mon, 31 Oct 2016 12:36:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.022
X-Spam-Level:
X-Spam-Status: No, score=-102.022 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_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 TtoY9K_6T5VA; Mon, 31 Oct 2016 12:36:13 -0700 (PDT)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0120.outbound.protection.outlook.com [104.47.33.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0BAD129A97; Mon, 31 Oct 2016 12:35:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=JFrjHEWFEj3bxv+dP7Vv6X6IA+bbrGCh+Fr8/npoTYE=; b=ispnmiwHnTokQDM2pJv18ThMhueAzdHjLQICck98zcaUjfiRL2sy1vcFu+bqgDC8f9rn5u45qoypm1bPp5EzHDZNpzLNZ4XoUMlEcwW5Jo94XE9oNq04BGJXDminQO7pZIDPJBcolQ7CVpK5HktFQwLweTr3pB5Z0Hu57uYCUh8=
Received: from CY1PR03MB2265.namprd03.prod.outlook.com (10.166.207.17) by CY1PR03MB2268.namprd03.prod.outlook.com (10.166.207.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.693.12; Mon, 31 Oct 2016 19:35:40 +0000
Received: from CY1PR03MB2265.namprd03.prod.outlook.com ([10.166.207.17]) by CY1PR03MB2265.namprd03.prod.outlook.com ([10.166.207.17]) with mapi id 15.01.0679.020; Mon, 31 Oct 2016 19:35:40 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: 神明達哉 <jinmei@wide.ad.jp>, "<int-dir@ietf.org>" <int-dir@ietf.org>, "int-ads@tools.ietf.org" <int-ads@tools.ietf.org>, "draft-ietf-6lo-privacy-considerations.all@ietf.org" <draft-ietf-6lo-privacy-considerations.all@ietf.org>
Thread-Topic: INT-DIR review of draft-ietf-6lo-privacy-considerations-03
Thread-Index: AQHSGBPcg5lB3ywphEaMPk+P2EvUXqDDKXVg
Date: Mon, 31 Oct 2016 19:35:40 +0000
Message-ID: <CY1PR03MB22656BF2E17BD1EAE70DED6CA3AE0@CY1PR03MB2265.namprd03.prod.outlook.com>
References: <CAJE_bqe97985RSZsKiUcuFogmoYbS6gT=cYEcE-75qbPNYd2hA@mail.gmail.com>
In-Reply-To: <CAJE_bqe97985RSZsKiUcuFogmoYbS6gT=cYEcE-75qbPNYd2hA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=dthaler@microsoft.com;
x-originating-ip: [2001:4898:80e8:1::519]
x-ms-office365-filtering-correlation-id: ea16791e-f3b7-46dc-fee1-08d401c51920
x-microsoft-exchange-diagnostics: 1; CY1PR03MB2268; 7:hPh3NPQu8imxzlqEqq/TBs40h9lqj2bN2zrHr00BrqZ6rQvrUErdGiN8GBUqxeap7aC5CnG+XzpQnmM/FP5iv4MY3q7Lcbir+6Q0wuhzyHi11mTk/KEe3/xZBHnxSeoveHRuVXlR74tjnORH/liHY+qOTG+eMPwmDVSyq0cIkAXCtGrswjsuJWTV5ABjkExQEInEdXIVJ1g5XfNQCHAaUkBA0LHpOX7ZVwxhdEwrXvJ6+MZTMnWOF2VCMIRKE/nD/GKu91w11xMguhnthFHIaK20490Nb1Af6QixYSuLonqq/PlRG5EyCFSwWj7dcpB8fOfFLBv/dEsBEFLXqGXw3FdXasZ5jIDW4aMTOH4IeYdm+f2SRIPG7bAMrwoOa4Dm
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CY1PR03MB2268;
x-microsoft-antispam-prvs: <CY1PR03MB226863F1AB504F3182D33E76A3AE0@CY1PR03MB2268.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6040176)(6045074)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026)(61426038)(61427038)(6046074)(6072074); SRVR:CY1PR03MB2268; BCL:0; PCL:0; RULEID:; SRVR:CY1PR03MB2268;
x-forefront-prvs: 01128BA907
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(189002)(199003)(377454003)(13464003)(230783001)(10400500002)(10090500001)(9686002)(68736007)(87936001)(5005710100001)(99286002)(8936002)(105586002)(8990500004)(106116001)(106356001)(3660700001)(3280700002)(102836003)(6116002)(5002640100001)(586003)(19580405001)(19580395003)(2501003)(10290500002)(33656002)(305945005)(5001770100001)(189998001)(74316002)(101416001)(7846002)(7736002)(2900100001)(107886002)(8676002)(97736004)(50986999)(2950100002)(92566002)(2906002)(76176999)(54356999)(76576001)(81156014)(81166006)(86362001)(122556002)(86612001)(11100500001)(7696004)(2201001)(15975445007)(77096005)(5660300001)(491001); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR03MB2268; H:CY1PR03MB2265.namprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Oct 2016 19:35:40.6999 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR03MB2268
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-dir/cylGQCSnxr3ipJy4dUV-7w3waxc>
Subject: Re: [Int-dir] INT-DIR review of draft-ietf-6lo-privacy-considerations-03
X-BeenThere: int-dir@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "This list is for discussion between the members of the Internet Area directorate." <int-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-dir>, <mailto:int-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-dir/>
List-Post: <mailto:int-dir@ietf.org>
List-Help: <mailto:int-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-dir>, <mailto:int-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Oct 2016 19:36:16 -0000

It is true that the 6lo-specific parts are mainly in section 3.  The audience is people doing new foo-over-IPv6 protocols,
which today is primarily the 6lo WG, hence it was homed there and was tailored towards that audience.

I have no preference either way on whether the title should change, other than in my view the document is already 
quite short and it would not make sense to split the document or anything.   

If the title were to change (and abstract) then it could be something like:

	Privacy Considerations for IPv6 Adaptation Layer Mechanisms

With possible abstract

OLD:
   This document discusses how a number of privacy threats apply to
   technologies designed for IPv6 over networks of resource-constrained
   nodes, and provides advice to protocol designers on how to address
   such threats in adaptation layer specifications for IPv6 over such
   links.
NEW:
   This document discusses how a number of privacy threats apply to
   technologies designed for IPv6 over various link layer protocols,
   and provides advice to protocol designers on how to address
   such threats in adaptation layer specifications for IPv6 over such
   links.

I'll wait a couple hours in case the chairs or ADs have a preference.

Dave

-----Original Message-----
From: jinmei.tatuya@gmail.com [mailto:jinmei.tatuya@gmail.com] On Behalf Of ????
Sent: Monday, September 26, 2016 9:34 AM
To: <int-dir@ietf.org> <int-dir@ietf.org>; int-ads@tools.ietf.org; draft-ietf-6lo-privacy-considerations.all@ietf.org
Subject: INT-DIR review of draft-ietf-6lo-privacy-considerations-03

I am an assigned INT directorate reviewer for <https://tools.ietf.org/html/draft-ietf-6lo-privacy-considerations-03>.
These comments were written primarily for the benefit of the Internet Area Directors. Document editors and shepherd(s) should treat these comments just like they would treat comments from any other IETF contributors and resolve them along with any other Last Call comments that have been received. For more details on the INT Directorate, see http://www.ietf.org/iesg/directorate.html.

This document is very well written and looks useful.  I didn't find any obvious technical issues that may block publication.

One possible point that my warrant a discussion is that this document doesn't seem to be very specific to resource constrained nodes (as the title and abstract suggests).  I don't see anything tightly specific to such nodes except for some parts of Section 3.  Even in Section 3 most of the discussions seem generic.  I wonder whether such general privacy issues regarding IPv6 addresses are already covered by some existing documents.  If so, this document could be much shorter by just referring to such documents and focusing on a few points specific to 6lo nodes.  If not, we might rather consider publishing it as such a generic document.

--
JINMEI, Tatuya