
From nobody Fri Sep  1 06:55:50 2017
Return-Path: <housley@vigilsec.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C91D213328B; Fri,  1 Sep 2017 06:55:48 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Russ Housley <housley@vigilsec.com>
To: <gen-art@ietf.org>
Cc: curdle@ietf.org, draft-ietf-curdle-rsa-sha2.all@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.59.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150427414878.3237.4575033946525642940@ietfa.amsl.com>
Date: Fri, 01 Sep 2017 06:55:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/GdgpuvceSE7cQFDfQ_u1i-DcSzw>
Subject: [Gen-art] Genart last call review of draft-ietf-curdle-rsa-sha2-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Sep 2017 13:55:49 -0000

Reviewer: Russ Housley
Review result: Almost Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-curdle-rsa-sha2-10
Reviewer: Russ Housley
Review Date: 2017-09-01
IETF LC End Date: 2017-09-11
IESG Telechat date: unknown

Summary: Almost Ready

Major Concerns: None


Minor Concerns:

I think that a better title for this document would be:

   Use of RSA Keys with SHA-256 and SHA-512 in Secure Shell (SSH)

These are two of the hash function in the SHA2 family, and there is no
ambiguity about them being part of the SHA3 family.  Similarly, I think
that the Abstract and Section 1 should explicitly names these two hash
functions.  The current wording seems to include SHA-224 and SHA-384,
and that is not the intent of the author.

In Section 3, I suggest:
   s/using SHA-2 [SHS] as hash./using SHA-256 or SHA-512 [SHS] as hash./
   s/the hash used is SHA-2 256./the hash used is SHA-256./
   s/the hash used is SHA-2 512./the hash used is SHA-512./

Note:  I did not propose changing the strings in case people have already
implemented against this specification.  If no one has implemented yet,
then I would change those too.


Section 5.1 should be expanded to say that following the NIST advice on
key sizes and SHA-1 outside the US Government is prudent.


Nits: None



From nobody Fri Sep  1 14:46:25 2017
Return-Path: <David.Black@dell.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23EF31341D1; Fri,  1 Sep 2017 14:46:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.601
X-Spam-Level: 
X-Spam-Status: No, score=-3.601 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dell.com header.b=xiA0pmuk; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=emc.com header.b=hQx+FgXg
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 Yh5heAh3PwDo; Fri,  1 Sep 2017 14:46:06 -0700 (PDT)
Received: from esa1.dell-outbound.iphmx.com (esa1.dell-outbound.iphmx.com [68.232.153.90]) (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 4761E13465E; Fri,  1 Sep 2017 14:46:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dell.com; i=@dell.com; q=dns/txt; s=smtpout; t=1504301937; x=1535837937; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=V9A77kD36qa3KfOE5aQLmBAYyJNdeObN54luehsjoIY=; b=xiA0pmukMqc8xhh+TWNI33nPkIJNoOT9cKNF0ijBev+LRPfiOkwg9CUQ Qn4PNah2rPTtilm/Ra9BAYT/7qcJ1nnvmX6WOOUZBSq67tGDtqYRx9cvu NKKQhq5Ypws5X9BrTIi0VTMH+dX7TFXEoobU1cehpe2BNZ09fpThoD/cM Q=;
Received: from esa2.dell-outbound2.iphmx.com ([68.232.153.202]) by esa1.dell-outbound.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Sep 2017 16:38:53 -0500
From: "Black, David" <David.Black@dell.com>
Received: from mailuogwhop.emc.com ([168.159.213.141]) by esa2.dell-outbound2.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Sep 2017 03:38:51 +0600
Received: from maildlpprd06.lss.emc.com (maildlpprd06.lss.emc.com [10.253.24.38]) by mailuogwprd03.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id v81Lk00h014784 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 1 Sep 2017 17:46:00 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd03.lss.emc.com v81Lk00h014784
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1504302360; bh=y/44bVrTpQ2Lrj0+/Ao2pGKIwBQ=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=hQx+FgXggilm5dBknKY2SNq4Yxi12tO/qTG6Qey5YOpzM870O6nw2Nu9p+SRcswLS 6su2ri/xUTt6ZRH0pcfBHayEIYjJYI/TzM/w6ViG/WVt5CsfHz2P8GYtCQATseNMZH PyFJCZd7iFbPNQEHS7FBstIfm1iuc5x7aTGymRFM=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd03.lss.emc.com v81Lk00h014784
Received: from mailusrhubprd51.lss.emc.com (mailusrhubprd51.lss.emc.com [10.106.48.24]) by maildlpprd06.lss.emc.com (RSA Interceptor); Fri, 1 Sep 2017 17:44:56 -0400
Received: from MXHUB321.corp.emc.com (MXHUB321.corp.emc.com [10.146.3.99]) by mailusrhubprd51.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id v81LjiBt025824 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Fri, 1 Sep 2017 17:45:45 -0400
Received: from MX307CL04.corp.emc.com ([fe80::849f:5da2:11b:4385]) by MXHUB321.corp.emc.com ([10.146.3.99]) with mapi id 14.03.0352.000; Fri, 1 Sep 2017 17:45:44 -0400
To: Brian Carpenter <brian.e.carpenter@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-tsvwg-ecn-experimentation.all@ietf.org" <draft-ietf-tsvwg-ecn-experimentation.all@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: Genart telechat review of draft-ietf-tsvwg-ecn-experimentation-05
Thread-Index: AQHTIsZAf8GsSgkmu0q70NA4hkw3sKKgjxdg
Date: Fri, 1 Sep 2017 21:45:44 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949362FC30A29@MX307CL04.corp.emc.com>
References: <150423129417.4604.2689843099266054478@ietfa.amsl.com>
In-Reply-To: <150423129417.4604.2689843099266054478@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.44.126]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd51.lss.emc.com
X-RSA-Classifications: public
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/ru7i_G61nVbozQF_b9ZOOy_gjvc>
Subject: Re: [Gen-art] Genart telechat review of draft-ietf-tsvwg-ecn-experimentation-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Sep 2017 21:46:08 -0000

QnJpYW4sDQoNClRoYW5rcyBmb3IgdGhlIHByb21wdCByZXZpZXcuDQoNCj4gQ29tbWVudDogVmVy
eSBjbGVhciBmcm9tIHRoZSB0ZWNobmljYWwgc3RhbmRwb2ludC4gDQoNClRoYW5rIHlvdSENCg0K
PiBJIHVuZGVyc3RhbmQgdGhlIGRlc2lyZSBmb3IgYnJldml0eSwgYnV0IHRoaXMgYm90aGVycyBt
ZSBhIGJpdC4gV2hhdCBpcw0KPiB0aGUgcmVhZGVyIHRvIG1ha2Ugb2YgUkZDMzE2OCBTZWN0aW9u
IDIwLjIsIGZvciBleGFtcGxlPyBNeSBmZWVsaW5nIGlzDQo+IHRoYXQgYSBzaG9ydCBBcHBlbmRp
eCBvdXRsaW5pbmcgdGhlIHNwZWNpZmljIHVwZGF0ZXMgd291bGQgYmUgdXNlZnVsLg0KPiBUaGVy
ZSdzIGFscmVhZHkgdG9vIG11Y2ggc3BhZ2hldHRpIHRvIHVudGFuZ2xlLg0KDQpSRkMgMzE2OCBT
ZWN0aW9uIDIwLjIgaXMgdGhlIHJhdGlvbmFsZSBmb3IgdGhlIEVDTiBOb25jZSBhbmQgaGVuY2Ug
d291bGQgYmUNCmRlbGV0ZWQuIFJlcXVlc3Qgbm90ZWQsIEknbGwgY29uc3VsdCB3aXRoIHRoZSBk
cmFmdCBzaGVwaGVyZCBhbmQgcmVzcG9uc2libGUNCkFEIHRvIGZpZ3VyZSBvdXQgd2hldGhlciB0
byBkbyB0aGlzLg0KDQo+IEkgc2VlIG5vIHJlYXNvbiB3aHkgUkZDMzU0MCBhbmQgUkZDNTYyMiBu
ZWVkIHRvIGJlIG5vcm1hdGl2ZSByZWZlcmVuY2VzDQo+IChhbmQgdGhlcmVmb3JlIGRvd25yZWZz
KS4gVGhleSBhcmVuJ3QgcmVxdWlyZWQgcmVhZGluZyBpbiBvcmRlciB0bw0KPiB1bmRlcnN0YW5k
IHRoaXMgZHJhZnQuDQoNCk9UT0gsIGJvdGggYXJlIGFmZmVjdGVkIGJ5IHRoaXMgZHJhZnQ6DQoN
CkluIHJldmVyc2Ugb3JkZXIsIHRoaXMgZHJhZnQgdXBkYXRlcyBSRkMgNTYyMiAtIHRoYXQgc2Vl
bXMgdG8gbWVyaXQgYQ0Kbm9ybWF0aXZlIHJlZmVyZW5jZS4gICAgVGhpcyBkcmFmdCBhbHNvIHBy
b3ZpZGVzIHRoZSByYXRpb25hbGUgZm9yIHRoZQ0Kc3RhdHVzIGNoYW5nZSBvZiBSRkMgMzU0MCB0
byBIaXN0b3JpYywgd2hpY2ggYWxzbyBzZWVtcyB0byBtZXJpdCBhDQpub3JtYXRpdmUgcmVmZXJl
bmNlLg0KDQpUaGFua3MsIC0tRGF2aWQNCg0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0t
DQo+IEZyb206IEJyaWFuIENhcnBlbnRlciBbbWFpbHRvOmJyaWFuLmUuY2FycGVudGVyQGdtYWls
LmNvbV0NCj4gU2VudDogVGh1cnNkYXksIEF1Z3VzdCAzMSwgMjAxNyAxMDowMiBQTQ0KPiBUbzog
Z2VuLWFydEBpZXRmLm9yZw0KPiBDYzogZHJhZnQtaWV0Zi10c3Z3Zy1lY24tZXhwZXJpbWVudGF0
aW9uLmFsbEBpZXRmLm9yZzsgdHN2d2dAaWV0Zi5vcmcNCj4gU3ViamVjdDogR2VuYXJ0IHRlbGVj
aGF0IHJldmlldyBvZiBkcmFmdC1pZXRmLXRzdndnLWVjbi1leHBlcmltZW50YXRpb24tMDUNCj4g
DQo+IFJldmlld2VyOiBCcmlhbiBDYXJwZW50ZXINCj4gUmV2aWV3IHJlc3VsdDogUmVhZHkgd2l0
aCBJc3N1ZXMNCj4gDQo+IEdlbi1BUlQgTGFzdCBDYWxsIHJldmlldyBvZiBkcmFmdC1pZXRmLXRz
dndnLWVjbi1leHBlcmltZW50YXRpb24tMDUNCj4gDQo+IEkgYW0gdGhlIGFzc2lnbmVkIEdlbi1B
UlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIFRoZSBHZW5lcmFsIEFyZWENCj4gUmV2aWV3IFRl
YW0gKEdlbi1BUlQpIHJldmlld3MgYWxsIElFVEYgZG9jdW1lbnRzIGJlaW5nIHByb2Nlc3NlZA0K
PiBieSB0aGUgSUVTRyBmb3IgdGhlIElFVEYgQ2hhaXIuICBQbGVhc2UgdHJlYXQgdGhlc2UgY29t
bWVudHMganVzdA0KPiBsaWtlIGFueSBvdGhlciBsYXN0IGNhbGwgY29tbWVudHMuDQo+IA0KPiBG
b3IgbW9yZSBpbmZvcm1hdGlvbiwgcGxlYXNlIHNlZSB0aGUgRkFRIGF0DQo+IDxodHRwOi8vd2lr
aS50b29scy5pZXRmLm9yZy9hcmVhL2dlbi90cmFjL3dpa2kvR2VuQXJ0ZmFxPi4NCj4gDQo+IERv
Y3VtZW50OiBkcmFmdC1pZXRmLXRzdndnLWVjbi1leHBlcmltZW50YXRpb24tMDUudHh0DQo+IFJl
dmlld2VyOiBCcmlhbiBDYXJwZW50ZXINCj4gUmV2aWV3IERhdGU6IDIwMTctMDktMDENCj4gSUVU
RiBMQyBFbmQgRGF0ZTogMjAxNy0wOS0xNA0KPiBJRVNHIFRlbGVjaGF0IGRhdGU6IDIwMTctMDkt
MTQNCj4gDQo+IFN1bW1hcnk6IFJlYWR5IHdpdGggKG1pbm9yKSBpc3N1ZXMNCj4gLS0tLS0tLS0N
Cj4gDQo+IENvbW1lbnQ6IFZlcnkgY2xlYXIgZnJvbSB0aGUgdGVjaG5pY2FsIHN0YW5kcG9pbnQu
DQo+IC0tLS0tLS0tDQo+IA0KPiBNaW5vciBJc3N1ZXM6DQo+IC0tLS0tLS0tLS0tLS0NCj4gDQo+
ID4gMy4gIEVDTiBOb25jZSBhbmQgUkZDIDM1NDANCj4gLi4uDQo+ID4gbyAgVXBkYXRlcyBSRkMg
MzE2OCBbUkZDMzE2OF0gdG8gcmVtb3ZlIGRpc2N1c3Npb24gb2YgdGhlIEVDTiBOb25jZQ0KPiA+
ICAgIGFuZCB1c2Ugb2YgRUNUKDEpIGZvciB0aGF0IE5vbmNlLiAgVGhlIHNwZWNpZmljIHRleHQg
dXBkYXRlcyBhcmUNCj4gPiAgICBvbWl0dGVkIGZvciBicmV2aXR5Lg0KPiANCj4gSSB1bmRlcnN0
YW5kIHRoZSBkZXNpcmUgZm9yIGJyZXZpdHksIGJ1dCB0aGlzIGJvdGhlcnMgbWUgYSBiaXQuIFdo
YXQgaXMNCj4gdGhlIHJlYWRlciB0byBtYWtlIG9mIFJGQzMxNjggU2VjdGlvbiAyMC4yLCBmb3Ig
ZXhhbXBsZT8gTXkgZmVlbGluZyBpcw0KPiB0aGF0IGEgc2hvcnQgQXBwZW5kaXggb3V0bGluaW5n
IHRoZSBzcGVjaWZpYyB1cGRhdGVzIHdvdWxkIGJlIHVzZWZ1bC4NCj4gVGhlcmUncyBhbHJlYWR5
IHRvbyBtdWNoIHNwYWdoZXR0aSB0byB1bnRhbmdsZS4NCj4gDQo+IEkgc2VlIG5vIHJlYXNvbiB3
aHkgUkZDMzU0MCBhbmQgUkZDNTYyMiBuZWVkIHRvIGJlIG5vcm1hdGl2ZSByZWZlcmVuY2VzDQo+
IChhbmQgdGhlcmVmb3JlIGRvd25yZWZzKS4gVGhleSBhcmVuJ3QgcmVxdWlyZWQgcmVhZGluZyBp
biBvcmRlciB0bw0KPiB1bmRlcnN0YW5kIHRoaXMgZHJhZnQuDQo+IA0KPiAtLQ0KDQo=


From nobody Fri Sep  1 16:41:26 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BE8E13446A; Fri,  1 Sep 2017 16:41:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 5KfcNi2WnDgk; Fri,  1 Sep 2017 16:41:17 -0700 (PDT)
Received: from mail-pg0-x230.google.com (mail-pg0-x230.google.com [IPv6:2607:f8b0:400e:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77D741341EE; Fri,  1 Sep 2017 16:41:17 -0700 (PDT)
Received: by mail-pg0-x230.google.com with SMTP id r133so4371881pgr.3; Fri, 01 Sep 2017 16:41:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=hDCk0VMGGlkMiInDdnnyB5P+AHh4pvKg3x9PcZ0jeEI=; b=a/Bfa66OKH8JS7kUKzl/JkE/N+ixr0LZQwsri97MEaQbBsfrG4wo3ikktfniLELafP RAUrxykNDfeS8LWK/hpoiFf7uZCiETcI987U8URBIeqHPMJFuNszkp5UQ25HCJoE7f9g C4g7u6b2vJ34Uq9Mr/T1hwJWDFl+5VDqeui3iuOTgVUFiq8w6E/WGcV8mcRWFjv0z16q aeJuWRxTTl1Nn1qQo6UpyWcdEoeGM5IXaZs+UnBZq+q26d4xYbEjB2Q2vmXKCPSWwmFN jZiHktP3rOgQwe4m0sW6wt1TpElFOxdhChkZnZydWZzVMJp9teGU6+f3IZWVKE1rztsr /I9A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=hDCk0VMGGlkMiInDdnnyB5P+AHh4pvKg3x9PcZ0jeEI=; b=rBCeWf+jj5HyAY0WetIooSfvq+bpHuVG0tIN2A31vuLx6prEMy0jzVZ4nrsRmSfhEA YqF+GR25rnyUu1cDhJY83TLcpnypMf2X8kVeH6EvfWNXbxcR4H82siiTBR0OxmprCc3D OknE7lBplmr+HH8ed80Kiub/Wt+i/FfK007ywcC55/BozZKEZhDgwqvED/2MZOog/gIt bb4G9yU/QPdaM+S/uJ2yksi4VjErUq4bW5CHuta/nW6N/M/hfkMF8AOhRp+n5HgAIiFP 8tOoF2CmqWvNn9Jxv17c+du3jio8IHUmOEfAgVNV/AlPknAGnu/0lbv4m5jgVmRsEF1U XiLQ==
X-Gm-Message-State: AHPjjUg47/rd8Ru08W0RoRTNN+wan9YxJu0+J4eGSnXDB598zbeQlKmK g8PNnGo9p4CA7yMf
X-Google-Smtp-Source: ADKCNb7d13D/Sg5dFNXiu2uMObUUjITdW5g+u0sloZgWZLXJXPoh2ombo4vVjt57PWAUzKcLKMN8ig==
X-Received: by 10.98.75.2 with SMTP id y2mr4188047pfa.305.1504309276652; Fri, 01 Sep 2017 16:41:16 -0700 (PDT)
Received: from ?IPv6:2406:e007:57a7:1:28cc:dc4c:9703:6781? ([2406:e007:57a7:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id 27sm1507796pfk.91.2017.09.01.16.41.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Sep 2017 16:41:15 -0700 (PDT)
To: "Black, David" <David.Black@dell.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Cc: "draft-ietf-tsvwg-ecn-experimentation.all@ietf.org" <draft-ietf-tsvwg-ecn-experimentation.all@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
References: <150423129417.4604.2689843099266054478@ietfa.amsl.com> <CE03DB3D7B45C245BCA0D243277949362FC30A29@MX307CL04.corp.emc.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <6afe85ba-83c5-5945-fd37-dc313eb22162@gmail.com>
Date: Sat, 2 Sep 2017 11:41:23 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <CE03DB3D7B45C245BCA0D243277949362FC30A29@MX307CL04.corp.emc.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/wQqdOFMcT3uxD_uv7xrK1_aU1sY>
Subject: Re: [Gen-art] Genart telechat review of draft-ietf-tsvwg-ecn-experimentation-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Sep 2017 23:41:19 -0000

On 02/09/2017 09:45, Black, David wrote:
> Brian,
> 
> Thanks for the prompt review.
> 
>> Comment: Very clear from the technical standpoint. 
> 
> Thank you!
> 
>> I understand the desire for brevity, but this bothers me a bit. What is
>> the reader to make of RFC3168 Section 20.2, for example? My feeling is
>> that a short Appendix outlining the specific updates would be useful.
>> There's already too much spaghetti to untangle.
> 
> RFC 3168 Section 20.2 is the rationale for the ECN Nonce and hence would be
> deleted. Request noted, I'll consult with the draft shepherd and responsible
> AD to figure out whether to do this.

Thanks. It's not intended as a blocking issue.

> 
>> I see no reason why RFC3540 and RFC5622 need to be normative references
>> (and therefore downrefs). They aren't required reading in order to
>> understand this draft.
> 
> OTOH, both are affected by this draft:
> 
> In reverse order, this draft updates RFC 5622 - that seems to merit a
> normative reference.    This draft also provides the rationale for the
> status change of RFC 3540 to Historic, which also seems to merit a
> normative reference.

Well, my understanding is that a normative reference is needed only
when the citing document cannot be understood and implemented
without reading the cited document.

Again it's not a blocking comment - although there is a technical error
in the Last Call message: it flags the downref to 5622, but not that to 3540.
I don't know if that's a tool error or an AD error ;-).

    Brian

> 
> Thanks, --David
> 
> 
>> -----Original Message-----
>> From: Brian Carpenter [mailto:brian.e.carpenter@gmail.com]
>> Sent: Thursday, August 31, 2017 10:02 PM
>> To: gen-art@ietf.org
>> Cc: draft-ietf-tsvwg-ecn-experimentation.all@ietf.org; tsvwg@ietf.org
>> Subject: Genart telechat review of draft-ietf-tsvwg-ecn-experimentation-05
>>
>> Reviewer: Brian Carpenter
>> Review result: Ready with Issues
>>
>> Gen-ART Last Call review of draft-ietf-tsvwg-ecn-experimentation-05
>>
>> I am the assigned Gen-ART reviewer for this draft. The General Area
>> Review Team (Gen-ART) reviews all IETF documents being processed
>> by the IESG for the IETF Chair.  Please treat these comments just
>> like any other last call comments.
>>
>> For more information, please see the FAQ at
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>> Document: draft-ietf-tsvwg-ecn-experimentation-05.txt
>> Reviewer: Brian Carpenter
>> Review Date: 2017-09-01
>> IETF LC End Date: 2017-09-14
>> IESG Telechat date: 2017-09-14
>>
>> Summary: Ready with (minor) issues
>> --------
>>
>> Comment: Very clear from the technical standpoint.
>> --------
>>
>> Minor Issues:
>> -------------
>>
>>> 3.  ECN Nonce and RFC 3540
>> ...
>>> o  Updates RFC 3168 [RFC3168] to remove discussion of the ECN Nonce
>>>    and use of ECT(1) for that Nonce.  The specific text updates are
>>>    omitted for brevity.
>>
>> I understand the desire for brevity, but this bothers me a bit. What is
>> the reader to make of RFC3168 Section 20.2, for example? My feeling is
>> that a short Appendix outlining the specific updates would be useful.
>> There's already too much spaghetti to untangle.
>>
>> I see no reason why RFC3540 and RFC5622 need to be normative references
>> (and therefore downrefs). They aren't required reading in order to
>> understand this draft.
>>
>> --
> 


From nobody Fri Sep  1 18:14:52 2017
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 39065134633; Fri,  1 Sep 2017 18:14:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Peter Yee <peter@akayla.com>
To: <gen-art@ietf.org>
Cc: mpls@ietf.org, ietf@ietf.org, draft-ietf-mpls-ldp-mrt.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.59.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150431489114.6649.9807443646105756121@ietfa.amsl.com>
Date: Fri, 01 Sep 2017 18:14:51 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/EpgQGl0DkI2DIVzg1vrICflQltM>
Subject: [Gen-art] Genart last call review of draft-ietf-mpls-ldp-mrt-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Sep 2017 01:14:51 -0000

Reviewer: Peter Yee
Review result: Ready with Issues

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-mpls-ldp-mrt-06
Reviewer: Peter Yee
Review Date: 2017-09-01
IETF LC End Date: 2017-09-01
IESG Telechat date: 2017-09-14

Summary:  The draft is ready for publication after correcting some minor issues.

Major issues:  None

Minor issues:

Page 3, section 3, IBR definition: the definition give here appears to be a
duplicate of the one given for IN.  Copy the correct definition from RFC 7812
instead.

Nits/editorial comments:

Page 3, section 1, 2nd paragraph, 1st sentence: append a comma after "e.g.".

Page 8, section 4.4., 1st paragraph, 2nd sentence: delete duplicate "on".

Page 8, section 4.4, 2nd paragraph, 4th sentence: change comma after
"computations" to a period.

Page 9, section 5.1.1, 4th paragraph, 2nd sentence: the construction
"red(blue)" is used without defining what it means exactly.  From the context,
it isn't quite "red or blue".  An explanation of the meaning of this
construction should be given.  I'm assuming it means something like use "red"
in the sentence in all cases or use use "blue", but don't mix them.  There's
also red/blue used later in the document which muddies the point.

Page 10, 1st full paragraph, 2nd sentence: change "foll" to "follows:".

Page 11, section 5.2.2, 2nd paragraph, 1st sentence: delete the period after
"A.1.7".

Page 12, 1st paragraph, 1st sentence: consider deleting "how".

Page 13, 2nd paragraph after numbered list, 1st sentence: append "to" after
"respect".

Section titles for 5.2, 5.3, and 7: append a space after "RFC" to separate it
from the number.  The spaceless form should only be used for references
enclosed in brackets.


From nobody Sat Sep  2 01:28:01 2017
Return-Path: <denisbider.ietf@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1224132EC2; Sat,  2 Sep 2017 01:27:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 vVqjc5tZhT_n; Sat,  2 Sep 2017 01:27:57 -0700 (PDT)
Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 992D2132E5F; Sat,  2 Sep 2017 01:27:53 -0700 (PDT)
Received: by mail-lf0-x230.google.com with SMTP id a126so7258166lfa.0; Sat, 02 Sep 2017 01:27:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=H9l5RqPS8fC5xXB4YONQh8iqj2A1Cl+H/nqq9kMiMNg=; b=QyW1BQNq0STQpgIdhhmZmE5bwPf0tAvAzA5D4h0cxeMtvXeQz9qbnJsh4NDJ9HZPs3 RSdBS8uBCjBv9r9y3jMy6L6JWDlAI58FUgqT3XdMLjj6pAly4EWf0evee4qUbodCSnp2 LFT570LQKJ2jcmX8NKw7N3W5RVShf0Zx/9SJY1/mokDMP05r1k3wazAAhAxpsIHyNloA jJ16jotZbKyRrp/C8TVsKZ7s/Fp6x7+cdqUE5vxATrHBLpA3uic/mpariMYYL89LPKZC XRctTGhTOlBrrQPA1hFJ8tiSR0kWM63vsWpO36fR48XQImtYLVIEFW00ki6JNol1ecI1 Vgvw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=H9l5RqPS8fC5xXB4YONQh8iqj2A1Cl+H/nqq9kMiMNg=; b=A05ZrNnBwZ3dPXKZUVLo2ymMCZ3pyP+2v63ernrWtLsSNe4hOZwgNJe/znGRQBzWrd 7pynxzGwPWjgqPxolDWXWdi41CvQtV0mDAjUQuVEhQ0gLH8dEZvjxcWrNfvrhIaJke5Z N8ALGeW//7FWP6ueRLl3gHf7eNHRvTYpLiipfCIEKmQTkkeVtGgSQt3JgdQUPnpZE2WI ZtxjwkzctOhjxLssbPLZADJ4cs8treGzduk16ynqaWdvGbBVsVRlj3ImZeZ8Lrmzkb7n uwCAuSf1PT1j08FSkrTn0SSPTbMvW00KowE0NzjYYgKw2mipKTqFCPYAt/10bgAus7Bg k9GQ==
X-Gm-Message-State: AHPjjUgYjx33LhmMt01/6I+sjdbl+owGvageDhkWnWjkyf6ck49M4Btb /06NIHyJZQk4xXUZsnwjqPWZU2550FkC
X-Google-Smtp-Source: ADKCNb65AxuXQgiEdPfgwvsYp9ny4ebkj23Yza5C6bwD+K1vujZqeRXZRDqj+/TdE2OG98jFPYujCGXjlbgyX3Ts/H0=
X-Received: by 10.25.222.143 with SMTP id i15mr258450lfl.4.1504340871822; Sat, 02 Sep 2017 01:27:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.179.27.209 with HTTP; Sat, 2 Sep 2017 01:27:51 -0700 (PDT)
In-Reply-To: <150427414878.3237.4575033946525642940@ietfa.amsl.com>
References: <150427414878.3237.4575033946525642940@ietfa.amsl.com>
From: denis bider <denisbider.ietf@gmail.com>
Date: Sat, 2 Sep 2017 03:27:51 -0500
Message-ID: <CADPMZDBhLQ3ztEoL_Eg_hnZFihCTFpsachjZYgSr_gRO4WbiZw@mail.gmail.com>
To: Russ Housley <housley@vigilsec.com>
Cc: gen-art@ietf.org, curdle <curdle@ietf.org>,  draft-ietf-curdle-rsa-sha2.all@ietf.org, ietf@ietf.org
Content-Type: multipart/alternative; boundary="f403045fa78c494409055830a7fe"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/XNcdM-ijrsocAM4_RAw_nP7z-qs>
Subject: Re: [Gen-art] [Curdle] Genart last call review of draft-ietf-curdle-rsa-sha2-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Sep 2017 08:27:59 -0000

--f403045fa78c494409055830a7fe
Content-Type: text/plain; charset="UTF-8"

Hello Russ,

thank you for the review. Comments:


> I think that a better title for this document would be:
> Use of RSA Keys with SHA-256 and SHA-512 in Secure Shell (SSH)

I can make this change, but I should note this is not universally agreed
on. In a previous specification, which became RFC 6668:

https://www.ietf.org/rfc/rfc6668.txt

... the original draft called for e.g. "hmac-sha256", but there were
immediate concerns about ambiguity which led to "hmac-sha2-256" and
"hmac-sha2-512" being specified.


> The current wording seems to include SHA-224 and SHA-384,
> and that is not the intent of the author.

True, but in this case as well, I point out RFC 6668, where we have the
title:

"SHA-2 Data Integrity Verification for the Secure Shell (SSH) Transport
Layer Protocol"

... even though the document only specifies "hmac-sha2-256" and
"hmac-sha2-512".

It appears to me that it may not be necessary for a document to specify use
of all versions of SHA-2, in order to be accurately described as specifying
the use of SHA-2 in a context.


> I did not propose changing the strings in case people have
> already implemented against this specification.  If no one
> has implemented yet, then I would change those too.

This intuition is correct. It has been widely implemented and is deployed
on, very possibly, millions of systems. One can launch an off-the-shelf
Amazon instance that has a long-term-support edition of Ubuntu with a
version of OpenSSH that implements this.


> Section 5.1 should be expanded to say that following the NIST
> advice on key sizes and SHA-1 outside the US Government is
> prudent.

I can do this.


As instructed, I await instructions from the document shepherd.

denis



On Fri, Sep 1, 2017 at 8:55 AM, Russ Housley <housley@vigilsec.com> wrote:

> Reviewer: Russ Housley
> Review result: Almost Ready
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair. Please wait for direction from your
> document shepherd or AD before posting a new version of the draft.
>
> For more information, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Document: draft-ietf-curdle-rsa-sha2-10
> Reviewer: Russ Housley
> Review Date: 2017-09-01
> IETF LC End Date: 2017-09-11
> IESG Telechat date: unknown
>
> Summary: Almost Ready
>
> Major Concerns: None
>
>
> Minor Concerns:
>
> I think that a better title for this document would be:
>
>    Use of RSA Keys with SHA-256 and SHA-512 in Secure Shell (SSH)
>
> These are two of the hash function in the SHA2 family, and there is no
> ambiguity about them being part of the SHA3 family.  Similarly, I think
> that the Abstract and Section 1 should explicitly names these two hash
> functions.  The current wording seems to include SHA-224 and SHA-384,
> and that is not the intent of the author.
>
> In Section 3, I suggest:
>    s/using SHA-2 [SHS] as hash./using SHA-256 or SHA-512 [SHS] as hash./
>    s/the hash used is SHA-2 256./the hash used is SHA-256./
>    s/the hash used is SHA-2 512./the hash used is SHA-512./
>
> Note:  I did not propose changing the strings in case people have already
> implemented against this specification.  If no one has implemented yet,
> then I would change those too.
>
>
> Section 5.1 should be expanded to say that following the NIST advice on
> key sizes and SHA-1 outside the US Government is prudent.
>
>
> Nits: None
>
>
> _______________________________________________
> Curdle mailing list
> Curdle@ietf.org
> https://www.ietf.org/mailman/listinfo/curdle
>

--f403045fa78c494409055830a7fe
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello Russ,<div><br></div><div>thank you for the review. C=
omments:</div><div><br></div><div><br></div><div>&gt;=C2=A0<span style=3D"f=
ont-size:12.8px">I think that a better title for this document would be:</s=
pan></div><span style=3D"font-size:12.8px">&gt; Use of RSA Keys with SHA-25=
6 and SHA-512 in Secure Shell (SSH)</span><br style=3D"font-size:12.8px"><d=
iv><span style=3D"font-size:12.8px"><br></span></div><div><span style=3D"fo=
nt-size:12.8px">I can make this change, but I should note this is not unive=
rsally agreed on. In a previous specification, which became RFC 6668:</span=
></div><div><span style=3D"font-size:12.8px"><br></span></div><div><span st=
yle=3D"font-size:12.8px"><a href=3D"https://www.ietf.org/rfc/rfc6668.txt">h=
ttps://www.ietf.org/rfc/rfc6668.txt</a></span><br></div><div><span style=3D=
"font-size:12.8px"><br></span></div><div><span style=3D"font-size:12.8px">.=
.. the original draft called for e.g. &quot;hmac-sha256&quot;, but there we=
re immediate concerns about ambiguity which led to &quot;hmac-sha2-256&quot=
; and &quot;hmac-sha2-512&quot; being specified.</span></div><div><span sty=
le=3D"font-size:12.8px"><br></span></div><div><br></div><div><span style=3D=
"font-size:12.8px">&gt;=C2=A0</span><span style=3D"font-size:12.8px">The cu=
rrent wording seems to include SHA-224 and SHA-384,</span></div><span style=
=3D"font-size:12.8px">&gt; and that is not the intent of the author.</span>=
<br style=3D"font-size:12.8px"><div><span style=3D"font-size:12.8px"><br></=
span></div><div><span style=3D"font-size:12.8px">True, but in this case as =
well, I point out RFC 6668, where we have the title:</span></div><div><span=
 style=3D"font-size:12.8px"><br></span></div><div><span style=3D"font-size:=
12.8px">&quot;SHA-2 Data Integrity Verification for the Secure Shell (SSH) =
Transport Layer Protocol&quot;</span><br></div><div><span style=3D"font-siz=
e:12.8px"><br></span></div><div><span style=3D"font-size:12.8px">... even t=
hough the document only specifies &quot;hmac-sha2-256&quot; and &quot;hmac-=
sha2-512&quot;.</span></div><div><span style=3D"font-size:12.8px"><br></spa=
n></div><div><span style=3D"font-size:12.8px">It appears to me that it may =
not be necessary for a document to specify use of all versions of SHA-2, in=
 order to be accurately described as specifying the use of SHA-2 in a conte=
xt.</span></div><div><span style=3D"font-size:12.8px"><br></span></div><div=
><span style=3D"font-size:12.8px"><br></span></div><div><span style=3D"font=
-size:12.8px">&gt;=C2=A0</span><span style=3D"font-size:12.8px">I did not p=
ropose changing the strings in case people have</span></div><div><span styl=
e=3D"font-size:12.8px">&gt; already=C2=A0</span><span style=3D"font-size:12=
.8px">implemented against this specification.=C2=A0 If no one</span></div><=
div><span style=3D"font-size:12.8px">&gt; has implemented yet,=C2=A0</span>=
<span style=3D"font-size:12.8px">then I would change those too.</span></div=
><div><span style=3D"font-size:12.8px"><br></span></div><div><span style=3D=
"font-size:12.8px">This intuition is correct. It has been widely implemente=
d and is deployed on, very possibly, millions of systems. One can launch an=
 off-the-shelf Amazon instance that has a long-term-support edition of Ubun=
tu with a version of OpenSSH that implements this.</span></div><div><span s=
tyle=3D"font-size:12.8px"><br></span></div><div><span style=3D"font-size:12=
.8px"><br></span></div><div><span style=3D"font-size:12.8px">&gt;=C2=A0</sp=
an><span style=3D"font-size:12.8px">Section 5.1 should be expanded to say t=
hat following the NIST</span></div><div><span style=3D"font-size:12.8px">&g=
t; advice on=C2=A0</span><span style=3D"font-size:12.8px">key sizes and SHA=
-1 outside the US Government is</span></div><div><span style=3D"font-size:1=
2.8px">&gt; prudent.</span></div><div><span style=3D"font-size:12.8px"><br>=
</span></div><div><span style=3D"font-size:12.8px">I can do this.</span></d=
iv><div><span style=3D"font-size:12.8px"><br></span></div><div><span style=
=3D"font-size:12.8px"><br></span></div><div><span style=3D"font-size:12.8px=
">As instructed, I await instructions from the document shepherd.</span></d=
iv><div><span style=3D"font-size:12.8px"><br></span></div><div><span style=
=3D"font-size:12.8px">denis</span></div><div><span style=3D"font-size:12.8p=
x"><br></span></div><div><span style=3D"font-size:12.8px"><br></span></div>=
</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, Sep=
 1, 2017 at 8:55 AM, Russ Housley <span dir=3D"ltr">&lt;<a href=3D"mailto:h=
ousley@vigilsec.com" target=3D"_blank">housley@vigilsec.com</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">Reviewer: Russ Housley<br>
Review result: Almost Ready<br>
<br>
I am the assigned Gen-ART reviewer for this draft. The General Area<br>
Review Team (Gen-ART) reviews all IETF documents being processed<br>
by the IESG for the IETF Chair. Please wait for direction from your<br>
document shepherd or AD before posting a new version of the draft.<br>
<br>
For more information, please see the FAQ at<br>
&lt;<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" rel=
=3D"noreferrer" target=3D"_blank">http://wiki.tools.ietf.org/<wbr>area/gen/=
trac/wiki/GenArtfaq</a>&gt;.<br>
<br>
Document: draft-ietf-curdle-rsa-sha2-10<br>
Reviewer: Russ Housley<br>
Review Date: 2017-09-01<br>
IETF LC End Date: 2017-09-11<br>
IESG Telechat date: unknown<br>
<br>
Summary: Almost Ready<br>
<br>
Major Concerns: None<br>
<br>
<br>
Minor Concerns:<br>
<br>
I think that a better title for this document would be:<br>
<br>
=C2=A0 =C2=A0Use of RSA Keys with SHA-256 and SHA-512 in Secure Shell (SSH)=
<br>
<br>
These are two of the hash function in the SHA2 family, and there is no<br>
ambiguity about them being part of the SHA3 family.=C2=A0 Similarly, I thin=
k<br>
that the Abstract and Section 1 should explicitly names these two hash<br>
functions.=C2=A0 The current wording seems to include SHA-224 and SHA-384,<=
br>
and that is not the intent of the author.<br>
<br>
In Section 3, I suggest:<br>
=C2=A0 =C2=A0s/using SHA-2 [SHS] as hash./using SHA-256 or SHA-512 [SHS] as=
 hash./<br>
=C2=A0 =C2=A0s/the hash used is SHA-2 256./the hash used is SHA-256./<br>
=C2=A0 =C2=A0s/the hash used is SHA-2 512./the hash used is SHA-512./<br>
<br>
Note:=C2=A0 I did not propose changing the strings in case people have alre=
ady<br>
implemented against this specification.=C2=A0 If no one has implemented yet=
,<br>
then I would change those too.<br>
<br>
<br>
Section 5.1 should be expanded to say that following the NIST advice on<br>
key sizes and SHA-1 outside the US Government is prudent.<br>
<br>
<br>
Nits: None<br>
<br>
<br>
______________________________<wbr>_________________<br>
Curdle mailing list<br>
<a href=3D"mailto:Curdle@ietf.org">Curdle@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/curdle" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/curdle</a><br=
>
</blockquote></div><br></div>

--f403045fa78c494409055830a7fe--


From nobody Sat Sep  2 05:16:25 2017
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20655132E1A; Sat,  2 Sep 2017 05:16:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level: 
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 EJ_vOlM3y9p9; Sat,  2 Sep 2017 05:16:22 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (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 C7691132DFE; Sat,  2 Sep 2017 05:16:21 -0700 (PDT)
X-AuditID: c1b4fb30-597ff70000005897-b5-59aaa11368d7
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 60.83.22679.311AAA95; Sat,  2 Sep 2017 14:16:19 +0200 (CEST)
Received: from ESESSMB102.ericsson.se ([169.254.2.248]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0352.000; Sat, 2 Sep 2017 14:16:19 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-mboned-interdomain-peering-bcp.all@ietf.org" <draft-ietf-mboned-interdomain-peering-bcp.all@ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-mboned-interdomain-peering-bcp-10
Thread-Index: AdMj5GSgtiZKqgW1ThOTlEwwxRTw9Q==
Date: Sat, 2 Sep 2017 12:16:18 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B56273EEC@ESESSMB102.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.150]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B56273EECESESSMB102erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrDLMWRmVeSWpSXmKPExsUyM2K7tK7wwlWRBn92Gln8vdnCbHH11WcW ByaPJUt+MgUwRnHZpKTmZJalFunbJXBl/Jv1gKmgJbBi64UvrA2MDR5djJwcEgImEvdfvGXt YuTiEBI4wihx4vZERghnMaPE3bk7gRwODjYBC4nuf9ogcRGBBYwSv+6dZATpFhZwl9jX2sUK YosI+EhcWnqYBcLWk3j3/D1YDYuAisTKu8eZQWxeAV+J01OfsIPYjAJiEt9PrWECsZkFxCVu PZnPBHGRgMSSPeeZIWxRiZeP/7FC2EoSK7ZfYoSoz5d4dOkmE8RMQYmTM5+wTGAUnIVk1Cwk ZbOQlEHEdSQW7P7EBmFrSyxb+JoZxj5z4DETsvgCRvZVjKLFqcVJuelGRnqpRZnJxcX5eXp5 qSWbGIFxcHDLb4MdjC+fOx5iFOBgVOLhfTN7VaQQa2JZcWXuIUYJDmYlEV45kBBvSmJlVWpR fnxRaU5q8SFGaQ4WJXFex30XIoQE0hNLUrNTUwtSi2CyTBycUg2MGdmSLu9aLt+bMssvzd3e 0uf8+Sv/JmU4pu6VZvvMVGK/5OOFkz2Z5dsrnQ7flY9nObl0StSGxZu2nt3C++VV3o4Id7VI jcvSnhx5s5a5mt14ojp/raR7rURplpACw9XXjA9ZFlR6yDyZ923bZLU/n/7mrxHR3/lyccN9 XgMhpb8yU+1+qC8wVGIpzkg01GIuKk4EAB5WhJl/AgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/OWhMHrOOAVJ3OJl8LoibwYNESZ0>
Subject: [Gen-art] Gen-ART review of draft-ietf-mboned-interdomain-peering-bcp-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Sep 2017 12:16:24 -0000

--_000_7594FB04B1934943A5C02806D1A2204B56273EECESESSMB102erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/Gen=
Artfaq>



Document:                       draft-ietf-mboned-interdomain-peering-bcp-1=
0.txt

Reviewer:                         Christer Holmberg

Review Date:                   2 September 2017

IETF LC End Date:           23 August 2017

IETF Telechat Date:        N/A



Summary: The document is well written. However, there are a couple of issue=
s that I'd like the authors to address.


Major Issues: None



Minor Issues:



Q1: The Introduction talks about the growing usage of multicast, and the it=
 begins the list what the document does. But, what is the background and ne=
ed for the document? Is there a problem? Are there interoperability issues?=
 At the end of the section it is said that ways to improve are identified, =
but it is unclear exactly what needs to be improved. I think it would be go=
od to say a few words in the Introduction about the issues and problems.


Editorial Issues:

Q2: The title of section 4 is "Supporting Functionality". That seems a litt=
le strange in my eyes. Supporting functionality of what?



--_000_7594FB04B1934943A5C02806D1A2204B56273EECESESSMB102erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.apple-tab-span
	{mso-style-name:apple-tab-span;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">I am the assigned Gen-ART reviewer for =
this draft. For background on Gen-ART, please see the FAQ at &lt;</span><sp=
an style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sans-serif;col=
or:black"><a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfa=
q"><span style=3D"font-size:11.0pt;color:#954F72">http://wiki.tools.ietf.or=
g/area/gen/trac/wiki/GenArtfaq</span></a></span><span style=3D"font-size:11=
.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:black">&gt;</span><sp=
an style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sans-serif;col=
or:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoPlainText" style=3D"margin:0cm;margin-bottom:.0001pt"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:=
black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin:0cm;margin-bottom:.0001pt"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:=
black">Document: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp;&nbsp;</span><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,sans-serif">draft-ietf-mboned-interdomain-peering-bcp-1=
0.txt<span style=3D"color:black"><o:p></o:p></span></span></p>
<p class=3D"MsoPlainText" style=3D"margin:0cm;margin-bottom:.0001pt"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:=
black">Reviewer: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; Christer Holmberg&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin:0cm;margin-bottom:.0001pt"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:=
black">Review Date: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp;
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans=
-serif">2 September<span style=3D"color:black"> 2017&nbsp;<o:p></o:p></span=
></span></p>
<p class=3D"MsoPlainText" style=3D"margin:0cm;margin-bottom:.0001pt"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:=
black">IETF LC End Date: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2</span><span s=
tyle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">3<span=
 style=3D"color:black">
</span>August<span style=3D"color:black"> 2017&nbsp;<o:p></o:p></span></spa=
n></p>
<p class=3D"MsoPlainText" style=3D"margin:0cm;margin-bottom:.0001pt"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:=
black">IETF Telechat Date: &nbsp; &nbsp; &nbsp; &nbsp;N/A<o:p></o:p></span>=
</p>
<p class=3D"MsoPlainText" style=3D"margin:0cm;margin-bottom:.0001pt"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:=
black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin:0cm;margin-bottom:.0001pt"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:=
black">Summary: The document is well written. However,
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans=
-serif">there are a couple of issues that I&#8217;d like the authors to add=
ress.<span style=3D"color:black"><o:p></o:p></span></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoPlainText" style=3D"margin:0cm;margin-bottom:.0001pt"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:=
black">Major Issues: None<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin:0cm;margin-bottom:.0001pt"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:=
black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin:0cm;margin-bottom:.0001pt"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:=
black">Minor Issues:<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin:0cm;margin-bottom:.0001pt"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"><o:p>=
&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin:0cm;margin-bottom:.0001pt"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">Q1: T=
he Introduction talks about the growing usage of multicast, and the it begi=
ns the list what the document does. But, what is
 the background and need for the document? Is there a problem? Are there in=
teroperability issues? At the end of the section it is said that ways to im=
prove are identified, but it is unclear exactly what needs to be improved. =
I think it would be good to say
 a few words in the Introduction about the issues and problems.<o:p></o:p><=
/span></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<div>
<div>
<p class=3D"MsoPlainText" style=3D"margin:0cm;margin-bottom:.0001pt"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:=
black">Editorial Issues:<o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">Q</span><span style=3D"font-size:10.5pt=
;font-family:&quot;Calibri&quot;,sans-serif">2<span style=3D"color:black">:=
<span class=3D"apple-tab-span">
</span></span><span class=3D"apple-tab-span">The title of section 4 is &#82=
20;Supporting Functionality&#8221;. That seems a little strange in my eyes.=
 Supporting functionality of what?</span><span style=3D"color:black"><o:p><=
/o:p></span></span></p>
</div>
<div>
<div>
<div>
<p class=3D"MsoPlainText" style=3D"margin:0cm;margin-bottom:.0001pt"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:=
black"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B56273EECESESSMB102erics_--


From nobody Sat Sep  2 11:37:55 2017
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAEEC1321A2; Sat,  2 Sep 2017 11:37:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 zy2_AmAhR-GA; Sat,  2 Sep 2017 11:37:52 -0700 (PDT)
Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A68F132FE7; Sat,  2 Sep 2017 11:37:52 -0700 (PDT)
Received: by mail-yw0-x229.google.com with SMTP id h127so12366633ywf.3; Sat, 02 Sep 2017 11:37:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fB2cskDpRkosKDonYY+IczVRuUZ727D3nexbqCSh4N0=; b=CAUTjFSzZx6RAvAENGGnD7SG69NcCinWn/NILLy1Q1jMYNzz02cgmeHejk60kaFet5 LMK17OBknMPe/Udt1svuE9HhLBw+PPghTLNkvuER1Dkutcwd06RIma7ZJeTHk51XfnDd 6alMo1QJi2lP790O8/Gd5q5D75JaiAhzaY9FSYEDo8E6kYo+X2gKf+Ph0sSG+HTcFc8x xPUGcgos7zQqAtiBuHbluylk8edZgMwT8UwYS0pu/441AF1yo60Su5wOor0zsI0mwSFS T8qMY/izM3fE8OySjJAfrsKAgHwt6wSiRLqu1PwF0NqDKuDJphz0xnGt43EUCwrSmyeV KXaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=fB2cskDpRkosKDonYY+IczVRuUZ727D3nexbqCSh4N0=; b=sQhLXQFeYWANDbeQR1lfzodJFSY6LeXbwyW+tKCRJaPHWOemqmcFLYH20y9q0SGevV JJ0+P1TQ28vvQUX/GzMxl/+F/7T7+s2XRYPjSlcnGEpCyerZkIqnMgo52eVMk6KIshIM qw2ru4GJJT1dLk3jVQIjrdwaBrE1Tcso/P/YO1zyUZNMwoxtwviiXfWgNu/LWnFkykLh cAzoYGac2ZFYq7ZqXImESYZeuRuasxuIFcFEg2AHZ451LoAxURZiJ6bJYWFuF1OEC5VL sBeE7rBqucQ8brs1F4YcVUikKzwsEssxMHlf/fslAkYEyG0sQtKaZA9C5emAsysKF6RA fvOQ==
X-Gm-Message-State: AHPjjUgyLfrZgidepawt2F6VQSLZ0t418WhPDu8kggYCXhi1BpADNukQ 9G9ByM9QXrKLYV2k8CLMUw0nzRGQew==
X-Google-Smtp-Source: ADKCNb7NgNhpKNh+N+5eIJBAn5vcQHzZArnupRinBxr4/mAk7hGHeNSYYxltVw0trVbn6KLD/TMmjFX4ip113aBMUpE=
X-Received: by 10.37.88.86 with SMTP id m83mr5174211ybb.170.1504377471275; Sat, 02 Sep 2017 11:37:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.2.148 with HTTP; Sat, 2 Sep 2017 11:37:50 -0700 (PDT)
In-Reply-To: <6afe85ba-83c5-5945-fd37-dc313eb22162@gmail.com>
References: <150423129417.4604.2689843099266054478@ietfa.amsl.com> <CE03DB3D7B45C245BCA0D243277949362FC30A29@MX307CL04.corp.emc.com> <6afe85ba-83c5-5945-fd37-dc313eb22162@gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Sat, 2 Sep 2017 13:37:50 -0500
Message-ID: <CAKKJt-doFog1_LrDr6qTtUa3_wPAvVV888U-u392B7J+xsiLxA@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: "Black, David" <David.Black@dell.com>, "gen-art@ietf.org" <gen-art@ietf.org>,  "draft-ietf-tsvwg-ecn-experimentation.all@ietf.org" <draft-ietf-tsvwg-ecn-experimentation.all@ietf.org>,  "tsvwg@ietf.org" <tsvwg@ietf.org>
Content-Type: multipart/alternative; boundary="001a114166d4c898960558392c79"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/_hjTpyU2HqTmdb2Kz8eSPKsuYCo>
Subject: Re: [Gen-art] Genart telechat review of draft-ietf-tsvwg-ecn-experimentation-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Sep 2017 18:37:54 -0000

--001a114166d4c898960558392c79
Content-Type: text/plain; charset="UTF-8"

Hi, Brian,

On Fri, Sep 1, 2017 at 6:41 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 02/09/2017 09:45, Black, David wrote:
> > Brian,
> >
> > Thanks for the prompt review.
> >
> >> Comment: Very clear from the technical standpoint.
> >
> > Thank you!
> >
> >> I understand the desire for brevity, but this bothers me a bit. What is
> >> the reader to make of RFC3168 Section 20.2, for example? My feeling is
> >> that a short Appendix outlining the specific updates would be useful.
> >> There's already too much spaghetti to untangle.
> >
> > RFC 3168 Section 20.2 is the rationale for the ECN Nonce and hence would
> be
> > deleted. Request noted, I'll consult with the draft shepherd and
> responsible
> > AD to figure out whether to do this.
>
> Thanks. It's not intended as a blocking issue.
>
> >
> >> I see no reason why RFC3540 and RFC5622 need to be normative references
> >> (and therefore downrefs). They aren't required reading in order to
> >> understand this draft.
> >
> > OTOH, both are affected by this draft:
> >
> > In reverse order, this draft updates RFC 5622 - that seems to merit a
> > normative reference.    This draft also provides the rationale for the
> > status change of RFC 3540 to Historic, which also seems to merit a
> > normative reference.
>
> Well, my understanding is that a normative reference is needed only
> when the citing document cannot be understood and implemented
> without reading the cited document.
>
> Again it's not a blocking comment - although there is a technical error
> in the Last Call message: it flags the downref to 5622, but not that to
> 3540.
> I don't know if that's a tool error or an AD error ;-).


As Bran is too polite to say, the AD sees the generated Last Call
announcement before it's sent.

I just regenerated the Last Call announcement, and it's still only naming
one draft as a normative downref. But the AD didn't notice that, so blaming
the tools was the wrong answer :-)

It's a 3-day weekend in the US, so any updated Last Call announcement won't
go out until Tuesday, anyway.

So, let's talk about that.

I just re-read the draft, focusing on the places where it refers to RFC
3540.

This draft explains the ECN Nonce experiment inline, although it cites 3540
as its reference, and explains that the experiment required ECT(0) and
ECT(1), but the experiment is over, and hasn't been deployed on the
Internet in any significant way, so we want ECT(1) back, for other
experiments.

It also refers to 3540 when it changes a registration in the Transmission
Control Protocol (TCP) Header Flags registry, but I believe this draft
explains the IANA actions requested well enough that IANA wouldn't need to
read 3540 to carry out the requested action.

I could be convinced that this draft explains why we want ECT(1) back well
enough that it's not necessary to actually read 3540, and since we're
declaring 3540 Historic, we actually kinda hope no one reads it in the
future except archaeologists in cyberspace.

But unless that reference really is informational, it remains a normative
downref that was omitted from the Last Call announcement.

David, I don't mind re-issuing the Last Call announcement if you think
still think the reference is normative, but you might want to take a look
at the text in the draft, and see how badly it needs to be normative,
before letting me know.

Spencer

--001a114166d4c898960558392c79
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi, Brian,<div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On Fri, Sep 1, 2017 at 6:41 PM, Brian E Carpenter <span dir=3D"lt=
r">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">bri=
an.e.carpenter@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex"><span class=3D"gmail-">On 02/09/2017 09:45, Black,=
 David wrote:<br>
&gt; Brian,<br>
&gt;<br>
&gt; Thanks for the prompt review.<br>
&gt;<br>
&gt;&gt; Comment: Very clear from the technical standpoint.<br>
&gt;<br>
&gt; Thank you!<br>
&gt;<br>
&gt;&gt; I understand the desire for brevity, but this bothers me a bit. Wh=
at is<br>
&gt;&gt; the reader to make of RFC3168 Section 20.2, for example? My feelin=
g is<br>
&gt;&gt; that a short Appendix outlining the specific updates would be usef=
ul.<br>
&gt;&gt; There&#39;s already too much spaghetti to untangle.<br>
&gt;<br>
&gt; RFC 3168 Section 20.2 is the rationale for the ECN Nonce and hence wou=
ld be<br>
&gt; deleted. Request noted, I&#39;ll consult with the draft shepherd and r=
esponsible<br>
&gt; AD to figure out whether to do this.<br>
<br>
</span>Thanks. It&#39;s not intended as a blocking issue.<br>
<span class=3D"gmail-"><br>
&gt;<br>
&gt;&gt; I see no reason why RFC3540 and RFC5622 need to be normative refer=
ences<br>
&gt;&gt; (and therefore downrefs). They aren&#39;t required reading in orde=
r to<br>
&gt;&gt; understand this draft.<br>
&gt;<br>
&gt; OTOH, both are affected by this draft:<br>
&gt;<br>
&gt; In reverse order, this draft updates RFC 5622 - that seems to merit a<=
br>
&gt; normative reference.=C2=A0 =C2=A0 This draft also provides the rationa=
le for the<br>
&gt; status change of RFC 3540 to Historic, which also seems to merit a<br>
&gt; normative reference.<br>
<br>
</span>Well, my understanding is that a normative reference is needed only<=
br>
when the citing document cannot be understood and implemented<br>
without reading the cited document.<br>
<br>
Again it&#39;s not a blocking comment - although there is a technical error=
<br>
in the Last Call message: it flags the downref to 5622, but not that to 354=
0.<br>
I don&#39;t know if that&#39;s a tool error or an AD error ;-).</blockquote=
><div><br></div><div>As Bran is too polite to say, the AD sees the generate=
d Last Call announcement before it&#39;s sent.=C2=A0</div><div><br></div><d=
iv>I just regenerated the Last Call announcement, and it&#39;s still only n=
aming one draft as a normative downref. But the AD didn&#39;t notice that, =
so blaming the tools was the wrong answer :-)</div><div><br></div><div>It&#=
39;s a 3-day weekend in the US, so any updated Last Call announcement won&#=
39;t go out until Tuesday, anyway.=C2=A0</div><div><br></div><div>So, let&#=
39;s talk about that.</div><div><br></div><div>I just re-read the draft, fo=
cusing on the places where it refers to RFC 3540.=C2=A0</div><div><br></div=
><div>This draft explains the ECN Nonce experiment inline, although it cite=
s 3540 as its reference, and explains that the experiment required ECT(0) a=
nd ECT(1), but the experiment is over, and hasn&#39;t been deployed on the =
Internet in any significant way, so we want ECT(1) back, for other experime=
nts.</div><div><br></div><div>It also refers to 3540 when it changes a regi=
stration in the Transmission Control Protocol (TCP) Header Flags registry, =
but I believe this draft explains the IANA actions requested well enough th=
at IANA wouldn&#39;t need to read 3540 to carry out the requested action.=
=C2=A0</div><div><br></div><div>I could be convinced that this draft explai=
ns why we want ECT(1) back well enough that it&#39;s not necessary to actua=
lly read 3540, and since we&#39;re declaring 3540 Historic, we actually kin=
da hope no one reads it in the future except archaeologists in cyberspace.<=
/div><div><br></div><div>But unless that reference really is informational,=
 it remains a normative downref that was omitted from the Last Call announc=
ement.</div><div><br></div><div>David, I don&#39;t mind re-issuing the Last=
 Call announcement if you think still think the reference is normative, but=
 you might want to take a look at the text in the draft, and see how badly =
it needs to be normative, before letting me know.</div><div><br></div><div>=
Spencer</div></div></div></div>

--001a114166d4c898960558392c79--


From nobody Mon Sep  4 02:47:36 2017
Return-Path: <adrian@olddog.co.uk>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99E6213248B; Mon,  4 Sep 2017 02:47:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
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 7g_pMCOTh7ob; Mon,  4 Sep 2017 02:47:33 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5F41126B6E; Mon,  4 Sep 2017 02:47:32 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id v849lSEi001546; Mon, 4 Sep 2017 10:47:28 +0100
Received: from 950129200 (196.252.114.87.dyn.plus.net [87.114.252.196]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id v849lRIb001523 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Sep 2017 10:47:28 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Elwyn Davies'" <elwynd@dial.pipex.com>, <gen-art@ietf.org>
Cc: <draft-ietf-teas-pce-central-control.all@ietf.org>, <ietf@ietf.org>, <teas@ietf.org>
References: <150394826804.19875.11489576374495678242@ietfa.amsl.com>
In-Reply-To: <150394826804.19875.11489576374495678242@ietfa.amsl.com>
Date: Mon, 4 Sep 2017 10:47:25 +0100
Message-ID: <04bc01d32562$d1429220$73c7b660$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGKGKKrdjo4X1idSejwpVo6v2ubj6M2k29g
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-23302.006
X-TM-AS-Result: No--13.393-10.0-31-10
X-imss-scan-details: No--13.393-10.0-31-10
X-TMASE-MatchedRID: HXSqh3WYKfunykMun0J1wru9iqQJLR0vt3aeg7g/usAiFs20Vxq/wm49 qzHIwIdXjZ0K7EGsP6YXEaT5uhkwzL7JS94zlW+lbMGKOuLn5FWzWETBQPV38lP0F8diMVluHLI ml6S5nfclpVclvjJJDDHcJ6BoI/5LC2s6EMq6ZtKdVNZaI2n6/zIaJpKzSfrsxSZxKZrfThPoYz vlUu2YlJ5PSOMffyxBslhzcjn859Q6dvNUujrkrxzwnpmtY/+rfS0Ip2eEHny+qryzYw2E8M894 3oc3p3sq7rFUcuGp/EgBwKKRHe+r9/bCv1rzS3NpMUEeBeh7W0RiTtSp1zpJmMjrIr8gQiiERmc 8MHbBtw=
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/oGTUCqFVUtB6iTjkT8ittpFjxNg>
Subject: Re: [Gen-art] [Teas] Genart telechat review of draft-ietf-teas-pce-central-control-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 09:47:34 -0000

Thanks Elwyn,

Clarified in the next revision.

Adrian

> -----Original Message-----
> From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Elwyn Davies
> Sent: 28 August 2017 20:24
> To: gen-art@ietf.org
> Cc: draft-ietf-teas-pce-central-control.all@ietf.org; ietf@ietf.org;
teas@ietf.org
> Subject: [Teas] Genart telechat review of
draft-ietf-teas-pce-central-control-04
> 
> Reviewer: Elwyn Davies
> Review result: Ready with Nits
> 
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair. Please wait for direction from your
> document shepherd or AD before posting a new version of the draft.
> 
> For more information, please see the FAQ at
> 
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
> 
> Document: draft-ietf-teas-pce-central-control-04
> Reviewer: Elwyn Davies
> Review Date: 2017-08-28
> IETF LC End Date: 2017-08-24
> IESG Telechat date: 2017-08-31
> 
> Summary: Thanks for addressing my Last Call comments on -03.  The new version
> is ready with one introduced nit.  Also I am still of the abstract is somewhat
> overlong.
> 
> Nit:
> s6, para 2: The SDN term 'northbound' has appeared in the new version. Needs
> brief explanation.
> 
> Major issues:
> 
> Minor issues:
> 
> Nits/editorial comments:
> 
> 
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas


From nobody Mon Sep  4 03:21:12 2017
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE57A13291C for <gen-art@ietfa.amsl.com>; Mon,  4 Sep 2017 03:21:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
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 pCn6EtpfM60I for <gen-art@ietfa.amsl.com>; Mon,  4 Sep 2017 03:21:07 -0700 (PDT)
Received: from virgo01.ee.ethz.ch (virgo01.ee.ethz.ch [129.132.2.226]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 674B41241FC for <gen-art@ietf.org>; Mon,  4 Sep 2017 03:21:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by virgo01.ee.ethz.ch (Postfix) with ESMTP id 3xm5Ts54SNzMljg; Mon,  4 Sep 2017 12:21:05 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at virgo01.ee.ethz.ch
Received: from virgo01.ee.ethz.ch ([127.0.0.1]) by localhost (virgo01.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7VhvgPIhph-H; Mon,  4 Sep 2017 12:21:00 +0200 (CEST)
X-MtScore: NO score=0
Received: from [192.168.178.33] (pD9E11141.dip0.t-ipconnect.de [217.225.17.65]) by virgo01.ee.ethz.ch (Postfix) with ESMTPSA; Mon,  4 Sep 2017 12:21:00 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
In-Reply-To: <150100555089.26234.7716617823296361972@ietfa.amsl.com>
Date: Mon, 4 Sep 2017 12:21:03 +0200
Cc: gen-art <gen-art@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <07E40187-36E9-49C7-9A2F-AC20404C18D8@tik.ee.ethz.ch>
References: <150100555089.26234.7716617823296361972@ietfa.amsl.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/SqLC3lVaP_Sh2RqP8jr2rWcJeos>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-curdle-ssh-dh-group-exchange-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 10:21:10 -0000

Hi Pete,

thanks for the review. Will check about the pre-5378 boilerplate.

Mirja


> Am 25.07.2017 um 19:59 schrieb Pete Resnick <presnick@qti.qualcomm.com>:
> 
> Reviewer: Pete Resnick
> Review result: Ready
> 
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
> 
> For more information, please see the FAQ at
> 
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
> 
> Document: draft-ietf-curdle-ssh-dh-group-exchange-05
> Reviewer: Pete Resnick
> Review Date: 2017-07-25
> IETF LC End Date: 2017-07-30
> IESG Telechat date: Not scheduled for a telechat
> 
> Summary: Ready. No concerns.
> 
> Major issues: None.
> 
> Minor issues: None.
> 
> Nits/editorial comments: I am not convinced the pre-5378 boilerplate is
> necessary. You refer to, but have not incorporated, material from 4419.
> 
> 


From nobody Mon Sep  4 04:44:00 2017
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72F1712ECEC for <gen-art@ietfa.amsl.com>; Mon,  4 Sep 2017 04:43:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
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 jf7pfU4J3uhQ for <gen-art@ietfa.amsl.com>; Mon,  4 Sep 2017 04:43:56 -0700 (PDT)
Received: from virgo01.ee.ethz.ch (virgo01.ee.ethz.ch [129.132.2.226]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 376B8124E15 for <gen-art@ietf.org>; Mon,  4 Sep 2017 04:43:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by virgo01.ee.ethz.ch (Postfix) with ESMTP id 3xm7KQ65RYzMpCd; Mon,  4 Sep 2017 13:43:54 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at virgo01.ee.ethz.ch
Received: from virgo01.ee.ethz.ch ([127.0.0.1]) by localhost (virgo01.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OK4mEcctneRb; Mon,  4 Sep 2017 13:43:49 +0200 (CEST)
X-MtScore: NO score=0
Received: from [192.168.178.33] (pD9E11141.dip0.t-ipconnect.de [217.225.17.65]) by virgo01.ee.ethz.ch (Postfix) with ESMTPSA; Mon,  4 Sep 2017 13:43:49 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
In-Reply-To: <150147719452.17668.11130233205318099796@ietfa.amsl.com>
Date: Mon, 4 Sep 2017 13:43:52 +0200
Cc: gen-art <gen-art@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <DE019382-94BD-41A5-BD1D-C69D466156CF@tik.ee.ethz.ch>
References: <150147719452.17668.11130233205318099796@ietfa.amsl.com>
To: Orit Levin <oritl@microsoft.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/t4mNsvyoT_qCzUXXKOE-IBX-mag>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-curdle-ssh-modp-dh-sha2-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 11:43:58 -0000

Thanks for the review!

> Am 31.07.2017 um 06:59 schrieb Orit Levin <oritl@microsoft.com>:
> 
> Reviewer: Orit Levin
> Review result: Ready
> 
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
> 
> For more information, please see the FAQ at
> 
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
> 
> Document: draft-ietf-curdle-ssh-modp-dh-sha2-??
> Reviewer: Orit Levin
> Review Date: 2017-07-30
> IETF LC End Date: 2017-07-30
> IESG Telechat date: Not scheduled for a telechat
> 
> Summary: The document is ready. No issue observed.
> 
> Major issues:
> 
> Minor issues:
> 
> Nits/editorial comments: 
> 
> 


From nobody Mon Sep  4 05:19:42 2017
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA081124F57 for <gen-art@ietfa.amsl.com>; Mon,  4 Sep 2017 05:19:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
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 ecEYZnMTq71B for <gen-art@ietfa.amsl.com>; Mon,  4 Sep 2017 05:19:38 -0700 (PDT)
Received: from virgo01.ee.ethz.ch (virgo01.ee.ethz.ch [129.132.2.226]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1895D124E15 for <gen-art@ietf.org>; Mon,  4 Sep 2017 05:19:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by virgo01.ee.ethz.ch (Postfix) with ESMTP id 3xm86c6PcSzMpMY; Mon,  4 Sep 2017 14:19:36 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at virgo01.ee.ethz.ch
Received: from virgo01.ee.ethz.ch ([127.0.0.1]) by localhost (virgo01.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1vg7dPAN5r2D; Mon,  4 Sep 2017 14:19:31 +0200 (CEST)
X-MtScore: NO score=0
Received: from [192.168.178.33] (pD9E11141.dip0.t-ipconnect.de [217.225.17.65]) by virgo01.ee.ethz.ch (Postfix) with ESMTPSA; Mon,  4 Sep 2017 14:19:30 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
In-Reply-To: <150093015937.32021.12465797358778837950@ietfa.amsl.com>
Date: Mon, 4 Sep 2017 14:19:29 +0200
Cc: gen-art <gen-art@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1AB79C67-79FF-4EC8-95A3-06BE9CFF6929@tik.ee.ethz.ch>
References: <150093015937.32021.12465797358778837950@ietfa.amsl.com>
To: Matthew Miller <linuxwolf+ietf@outer-planes.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/gM8gbDNfei48KmfNoz77OpGlFMs>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-curdle-ssh-ext-info-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 12:19:41 -0000

Thanks for the review and follow up!

> Am 24.07.2017 um 23:02 schrieb Matthew Miller =
<linuxwolf+ietf@outer-planes.net>:
>=20
> Reviewer: Matthew Miller
> Review result: Ready with Issues
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-curdle-ssh-ext-info-10
> Reviewer: Matthew Miller
> Review Date: 2017-07-24
> IETF LC End Date: 2017-07-30
> IESG Telechat date: N/A
>=20
> Summary:
>=20
> This document is ready with an issue.
>=20
> I found this document very coherent and easy to follow.
>=20
> Major issues:
>=20
> Minor issues:
>=20
> My only issue borders on nit, but sided with nit as I can see it
> potentially causing confusion for an implementer in the future.
>=20
> Section 2.5. "Interpretation of Extension Names and Values" explicitly
> states in the second paragraph a condition where the relative order of
> extension-names in an EXT_INFO message is irrelevant.  However, the =
rest
> of the section seems to imply to me that relative order is not =
important;
> so to explicitly call out a scenario seems to imply that relative =
order
> *is* relevant/important, sometimes.  If relative order is expected to =
be
> important most of the time, I think it helpful to explicitly state =
that
> and give a rationale for it.
>=20
> Nits/editorial comments:
>=20
> * RFC 5226 is referenced by this document, but is obsoleted by RFC =
8126.
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Mon Sep  4 06:50:41 2017
Return-Path: <ietf@kuehlewind.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F093132191 for <gen-art@ietfa.amsl.com>; Mon,  4 Sep 2017 06:50:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.net
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 EvD4FAEpEz40 for <gen-art@ietfa.amsl.com>; Mon,  4 Sep 2017 06:50:38 -0700 (PDT)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B0C8132A05 for <gen-art@ietf.org>; Mon,  4 Sep 2017 06:50:37 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net;  b=iZBEUfC6HysGmj29Actcd83hoNXmUMO0t477ihBx0i0Yju8RMoo5JJnj94O6Y2RaCOa4kT+C3i+U10S/eMdeGa7IdpZVA75ATaujYIwxip6iTuoHO7Nu/ybtrGygOTFLIj1zGMlvDK77Q4qnoiHkAqkUKZOVT9F0ZRMHKF97UX4=; h=Received:Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 19713 invoked from network); 4 Sep 2017 15:50:35 +0200
Received: from pd9e11141.dip0.t-ipconnect.de (HELO ?192.168.178.33?) (217.225.17.65) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 4 Sep 2017 15:50:35 +0200
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <ABCAA4EF18F17B4FB619EA93DEF7939A4F5BA212@eusaamb107.ericsson.se>
Date: Mon, 4 Sep 2017 15:50:33 +0200
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E84F3FEF-509F-4332-8633-1A1904DC2D54@kuehlewind.net>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A4F5BA212@eusaamb107.ericsson.se>
To: Meral Shirazipour <meral.shirazipour@ericsson.com>
X-Mailer: Apple Mail (2.3273)
X-PPP-Message-ID: <20170904135035.19708.89856@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Oa5GUZDbso1l_Lw-GpmudpbsI8k>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-curdle-des-des-des-die-die-die-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 13:50:40 -0000

Thanks for the review!

> Am 31.07.2017 um 19:23 schrieb Meral Shirazipour =
<meral.shirazipour@ericsson.com>:
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area =
Review Team (Gen-ART) reviews all IETF documents being processed by the =
IESG for the IETF Chair.  Please treat these comments just like any =
other last call comments.
> =20
> For more information, please see the FAQ at =
<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
> =20
> Document: draft-ietf-curdle-des-des-des-die-die-die-04
> Reviewer: Meral Shirazipour
> Review Date: 2017-07-31
> IETF LC End Date: 2017-07-30
> IESG Telechat date: NA
> =20
> =20
> Summary: This draft is ready to be published as BCP RFC.
> =20
> Major issues:
> =20
> Minor issues:
> =20
> Nits/editorial comments:=20
> =20
> Best Regards,
> Meral
> ---
> Meral Shirazipour
> Ericsson
> Research
> www.ericsson.com
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Mon Sep  4 07:09:58 2017
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D270A132A8F; Mon,  4 Sep 2017 07:09:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level: 
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
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 UW0RmXng7v2Y; Mon,  4 Sep 2017 07:09:48 -0700 (PDT)
Received: from b-painless.mh.aa.net.uk (b-painless.mh.aa.net.uk [81.187.30.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF025132A8E; Mon,  4 Sep 2017 07:09:47 -0700 (PDT)
Received: from 153.107.2.81.in-addr.arpa ([81.2.107.153] helo=[192.168.0.134]) by b-painless.mh.aa.net.uk with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <elwynd@dial.pipex.com>) id 1dorhU-0002RF-SG; Mon, 04 Sep 2017 14:46:04 +0100
Date: Mon, 04 Sep 2017 14:45:53 +0100
Message-ID: <rfhekveodc5rfqnx7mjqh18i.1504532678414@email.android.com>
Importance: normal
From: Elwyn Davies <elwynd@dial.pipex.com>
To: adrian@olddog.co.uk, gen-art@ietf.org
Cc: draft-ietf-teas-pce-central-control.all@ietf.org, ietf@ietf.org, teas@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.samsung.android.email_920406988092210"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/ou3emNZM0qa9I2QHJHD8wY0rHLQ>
Subject: Re: [Gen-art] [Teas] Genart telechat review of draft-ietf-teas-pce-central-control-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 14:09:51 -0000

----_com.samsung.android.email_920406988092210
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

CkhpLCBBZHJpYW4uClR3byBwb2ludHM6LSBJIGRvbid0IHNlZSBhbiBleHBsYW5hdGlvbiBvZiBu
b3J0aGJvdW5kIGluIC0wNS4tIEluIHRoZSBuZXcgdGV4dCBhdCB0aGUgZW5kIG9mIHMyLjEuMiBz
L3dob2xlIHRoZSBjb250cm9sbGVycy93aGlsZSB0aGUgY29udHJvbGxlcnMvCk90aGVyd2lzZSwg
dGhlIGV4dHJhIHRleHQgYW5kIGNoYW5nZXMgbG9vayBoZWxwZnVsLgpCZXN0IHdzaGVzLEVsd3lu
CgpTZW50IGZyb20gU2Ftc3VuZyB0YWJsZXQuCi0tLS0tLS0tIE9yaWdpbmFsIG1lc3NhZ2UgLS0t
LS0tLS1Gcm9tOiBBZHJpYW4gRmFycmVsIDxhZHJpYW5Ab2xkZG9nLmNvLnVrPiBEYXRlOiAwNC8w
OS8yMDE3ICAxMDo0NyAgKEdNVCswMDowMCkgVG86ICdFbHd5biBEYXZpZXMnIDxlbHd5bmRAZGlh
bC5waXBleC5jb20+LCBnZW4tYXJ0QGlldGYub3JnIENjOiBkcmFmdC1pZXRmLXRlYXMtcGNlLWNl
bnRyYWwtY29udHJvbC5hbGxAaWV0Zi5vcmcsIGlldGZAaWV0Zi5vcmcsIHRlYXNAaWV0Zi5vcmcg
U3ViamVjdDogUkU6IFtUZWFzXSBHZW5hcnQgdGVsZWNoYXQgcmV2aWV3IG9mIGRyYWZ0LWlldGYt
dGVhcy1wY2UtY2VudHJhbC1jb250cm9sLTA0IApUaGFua3MgRWx3eW4sCgpDbGFyaWZpZWQgaW4g
dGhlIG5leHQgcmV2aXNpb24uCgpBZHJpYW4KCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0K
PiBGcm9tOiBUZWFzIFttYWlsdG86dGVhcy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2Yg
RWx3eW4gRGF2aWVzCj4gU2VudDogMjggQXVndXN0IDIwMTcgMjA6MjQKPiBUbzogZ2VuLWFydEBp
ZXRmLm9yZwo+IENjOiBkcmFmdC1pZXRmLXRlYXMtcGNlLWNlbnRyYWwtY29udHJvbC5hbGxAaWV0
Zi5vcmc7IGlldGZAaWV0Zi5vcmc7CnRlYXNAaWV0Zi5vcmcKPiBTdWJqZWN0OiBbVGVhc10gR2Vu
YXJ0IHRlbGVjaGF0IHJldmlldyBvZgpkcmFmdC1pZXRmLXRlYXMtcGNlLWNlbnRyYWwtY29udHJv
bC0wNAo+IAo+IFJldmlld2VyOiBFbHd5biBEYXZpZXMKPiBSZXZpZXcgcmVzdWx0OiBSZWFkeSB3
aXRoIE5pdHMKPiAKPiBJIGFtIHRoZSBhc3NpZ25lZCBHZW4tQVJUIHJldmlld2VyIGZvciB0aGlz
IGRyYWZ0LiBUaGUgR2VuZXJhbCBBcmVhCj4gUmV2aWV3IFRlYW0gKEdlbi1BUlQpIHJldmlld3Mg
YWxsIElFVEYgZG9jdW1lbnRzIGJlaW5nIHByb2Nlc3NlZAo+IGJ5IHRoZSBJRVNHIGZvciB0aGUg
SUVURiBDaGFpci4gUGxlYXNlIHdhaXQgZm9yIGRpcmVjdGlvbiBmcm9tIHlvdXIKPiBkb2N1bWVu
dCBzaGVwaGVyZCBvciBBRCBiZWZvcmUgcG9zdGluZyBhIG5ldyB2ZXJzaW9uIG9mIHRoZSBkcmFm
dC4KPiAKPiBGb3IgbW9yZSBpbmZvcm1hdGlvbiwgcGxlYXNlIHNlZSB0aGUgRkFRIGF0Cj4gCj4g
PGh0dHBzOi8vdHJhYy5pZXRmLm9yZy90cmFjL2dlbi93aWtpL0dlbkFydGZhcT4uCj4gCj4gRG9j
dW1lbnQ6IGRyYWZ0LWlldGYtdGVhcy1wY2UtY2VudHJhbC1jb250cm9sLTA0Cj4gUmV2aWV3ZXI6
IEVsd3luIERhdmllcwo+IFJldmlldyBEYXRlOiAyMDE3LTA4LTI4Cj4gSUVURiBMQyBFbmQgRGF0
ZTogMjAxNy0wOC0yNAo+IElFU0cgVGVsZWNoYXQgZGF0ZTogMjAxNy0wOC0zMQo+IAo+IFN1bW1h
cnk6IFRoYW5rcyBmb3IgYWRkcmVzc2luZyBteSBMYXN0IENhbGwgY29tbWVudHMgb24gLTAzLsKg
IFRoZSBuZXcgdmVyc2lvbgo+IGlzIHJlYWR5IHdpdGggb25lIGludHJvZHVjZWQgbml0LsKgIEFs
c28gSSBhbSBzdGlsbCBvZiB0aGUgYWJzdHJhY3QgaXMgc29tZXdoYXQKPiBvdmVybG9uZy4KPiAK
PiBOaXQ6Cj4gczYsIHBhcmEgMjogVGhlIFNETiB0ZXJtICdub3J0aGJvdW5kJyBoYXMgYXBwZWFy
ZWQgaW4gdGhlIG5ldyB2ZXJzaW9uLiBOZWVkcwo+IGJyaWVmIGV4cGxhbmF0aW9uLgo+IAo+IE1h
am9yIGlzc3VlczoKPiAKPiBNaW5vciBpc3N1ZXM6Cj4gCj4gTml0cy9lZGl0b3JpYWwgY29tbWVu
dHM6Cj4gCj4gCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X18KPiBUZWFzIG1haWxpbmcgbGlzdAo+IFRlYXNAaWV0Zi5vcmcKPiBodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3RlYXMKCg==

----_com.samsung.android.email_920406988092210
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0
L2h0bWw7IGNoYXJzZXQ9VVRGLTgiPjwvaGVhZD48Ym9keT48ZGl2Pjxicj48L2Rpdj48ZGl2Pkhp
LCBBZHJpYW4uPC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj5Ud28gcG9pbnRzOjwvZGl2PjxkaXY+
LSBJIGRvbid0IHNlZSBhbiBleHBsYW5hdGlvbiBvZiBub3J0aGJvdW5kIGluIC0wNS48L2Rpdj48
ZGl2Pi0gSW4gdGhlIG5ldyB0ZXh0IGF0IHRoZSBlbmQgb2YgczIuMS4yIHMvd2hvbGUgdGhlIGNv
bnRyb2xsZXJzL3doaWxlIHRoZSBjb250cm9sbGVycy88L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2
Pk90aGVyd2lzZSwgdGhlIGV4dHJhIHRleHQgYW5kIGNoYW5nZXMgbG9vayBoZWxwZnVsLjwvZGl2
PjxkaXY+PGJyPjwvZGl2PjxkaXY+QmVzdCB3c2hlcyw8L2Rpdj48ZGl2PkVsd3luPC9kaXY+PGRp
dj48YnI+PC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdiBpZD0iY29tcG9zZXJfc2lnbmF0dXJlIj48
ZGl2IHN0eWxlPSJmb250LXNpemU6ODUlO2NvbG9yOiM1NzU3NTciIGRpcj0iYXV0byI+U2VudCBm
cm9tIFNhbXN1bmcgdGFibGV0LjwvZGl2PjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXYgc3R5bGU9
ImZvbnQtc2l6ZToxMDAlO2NvbG9yOiMwMDAwMDAiPjwhLS0gb3JpZ2luYWxNZXNzYWdlIC0tPjxk
aXY+LS0tLS0tLS0gT3JpZ2luYWwgbWVzc2FnZSAtLS0tLS0tLTwvZGl2PjxkaXY+RnJvbTogQWRy
aWFuIEZhcnJlbCAmbHQ7YWRyaWFuQG9sZGRvZy5jby51ayZndDsgPC9kaXY+PGRpdj5EYXRlOiAw
NC8wOS8yMDE3ICAxMDo0NyAgKEdNVCswMDowMCkgPC9kaXY+PGRpdj5UbzogJ0Vsd3luIERhdmll
cycgJmx0O2Vsd3luZEBkaWFsLnBpcGV4LmNvbSZndDssIGdlbi1hcnRAaWV0Zi5vcmcgPC9kaXY+
PGRpdj5DYzogZHJhZnQtaWV0Zi10ZWFzLXBjZS1jZW50cmFsLWNvbnRyb2wuYWxsQGlldGYub3Jn
LCBpZXRmQGlldGYub3JnLCB0ZWFzQGlldGYub3JnIDwvZGl2PjxkaXY+U3ViamVjdDogUkU6IFtU
ZWFzXSBHZW5hcnQgdGVsZWNoYXQgcmV2aWV3IG9mIGRyYWZ0LWlldGYtdGVhcy1wY2UtY2VudHJh
bC1jb250cm9sLTA0IDwvZGl2PjxkaXY+PGJyPjwvZGl2PjwvZGl2PlRoYW5rcyBFbHd5biw8YnI+
PGJyPkNsYXJpZmllZCBpbiB0aGUgbmV4dCByZXZpc2lvbi48YnI+PGJyPkFkcmlhbjxicj48YnI+
Jmd0OyAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxicj4mZ3Q7IEZyb206IFRlYXMgW21haWx0
bzp0ZWFzLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBFbHd5biBEYXZpZXM8YnI+Jmd0
OyBTZW50OiAyOCBBdWd1c3QgMjAxNyAyMDoyNDxicj4mZ3Q7IFRvOiBnZW4tYXJ0QGlldGYub3Jn
PGJyPiZndDsgQ2M6IGRyYWZ0LWlldGYtdGVhcy1wY2UtY2VudHJhbC1jb250cm9sLmFsbEBpZXRm
Lm9yZzsgaWV0ZkBpZXRmLm9yZzs8YnI+dGVhc0BpZXRmLm9yZzxicj4mZ3Q7IFN1YmplY3Q6IFtU
ZWFzXSBHZW5hcnQgdGVsZWNoYXQgcmV2aWV3IG9mPGJyPmRyYWZ0LWlldGYtdGVhcy1wY2UtY2Vu
dHJhbC1jb250cm9sLTA0PGJyPiZndDsgPGJyPiZndDsgUmV2aWV3ZXI6IEVsd3luIERhdmllczxi
cj4mZ3Q7IFJldmlldyByZXN1bHQ6IFJlYWR5IHdpdGggTml0czxicj4mZ3Q7IDxicj4mZ3Q7IEkg
YW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIFRoZSBHZW5l
cmFsIEFyZWE8YnI+Jmd0OyBSZXZpZXcgVGVhbSAoR2VuLUFSVCkgcmV2aWV3cyBhbGwgSUVURiBk
b2N1bWVudHMgYmVpbmcgcHJvY2Vzc2VkPGJyPiZndDsgYnkgdGhlIElFU0cgZm9yIHRoZSBJRVRG
IENoYWlyLiBQbGVhc2Ugd2FpdCBmb3IgZGlyZWN0aW9uIGZyb20geW91cjxicj4mZ3Q7IGRvY3Vt
ZW50IHNoZXBoZXJkIG9yIEFEIGJlZm9yZSBwb3N0aW5nIGEgbmV3IHZlcnNpb24gb2YgdGhlIGRy
YWZ0Ljxicj4mZ3Q7IDxicj4mZ3Q7IEZvciBtb3JlIGluZm9ybWF0aW9uLCBwbGVhc2Ugc2VlIHRo
ZSBGQVEgYXQ8YnI+Jmd0OyA8YnI+Jmd0OyAmbHQ7aHR0cHM6Ly90cmFjLmlldGYub3JnL3RyYWMv
Z2VuL3dpa2kvR2VuQXJ0ZmFxJmd0Oy48YnI+Jmd0OyA8YnI+Jmd0OyBEb2N1bWVudDogZHJhZnQt
aWV0Zi10ZWFzLXBjZS1jZW50cmFsLWNvbnRyb2wtMDQ8YnI+Jmd0OyBSZXZpZXdlcjogRWx3eW4g
RGF2aWVzPGJyPiZndDsgUmV2aWV3IERhdGU6IDIwMTctMDgtMjg8YnI+Jmd0OyBJRVRGIExDIEVu
ZCBEYXRlOiAyMDE3LTA4LTI0PGJyPiZndDsgSUVTRyBUZWxlY2hhdCBkYXRlOiAyMDE3LTA4LTMx
PGJyPiZndDsgPGJyPiZndDsgU3VtbWFyeTogVGhhbmtzIGZvciBhZGRyZXNzaW5nIG15IExhc3Qg
Q2FsbCBjb21tZW50cyBvbiAtMDMuJm5ic3A7IFRoZSBuZXcgdmVyc2lvbjxicj4mZ3Q7IGlzIHJl
YWR5IHdpdGggb25lIGludHJvZHVjZWQgbml0LiZuYnNwOyBBbHNvIEkgYW0gc3RpbGwgb2YgdGhl
IGFic3RyYWN0IGlzIHNvbWV3aGF0PGJyPiZndDsgb3ZlcmxvbmcuPGJyPiZndDsgPGJyPiZndDsg
Tml0Ojxicj4mZ3Q7IHM2LCBwYXJhIDI6IFRoZSBTRE4gdGVybSAnbm9ydGhib3VuZCcgaGFzIGFw
cGVhcmVkIGluIHRoZSBuZXcgdmVyc2lvbi4gTmVlZHM8YnI+Jmd0OyBicmllZiBleHBsYW5hdGlv
bi48YnI+Jmd0OyA8YnI+Jmd0OyBNYWpvciBpc3N1ZXM6PGJyPiZndDsgPGJyPiZndDsgTWlub3Ig
aXNzdWVzOjxicj4mZ3Q7IDxicj4mZ3Q7IE5pdHMvZWRpdG9yaWFsIGNvbW1lbnRzOjxicj4mZ3Q7
IDxicj4mZ3Q7IDxicj4mZ3Q7IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fPGJyPiZndDsgVGVhcyBtYWlsaW5nIGxpc3Q8YnI+Jmd0OyBUZWFzQGlldGYub3Jn
PGJyPiZndDsgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby90ZWFzPGJyPjxi
cj48L2JvZHk+PC9odG1sPg==

----_com.samsung.android.email_920406988092210--


From nobody Mon Sep  4 09:59:37 2017
Return-Path: <adrian@olddog.co.uk>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B765126C19; Mon,  4 Sep 2017 09:59:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
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 mx0RBdqL7h_x; Mon,  4 Sep 2017 09:59:16 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7DFE132CE8; Mon,  4 Sep 2017 09:59:06 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id v84Gx3V0006330; Mon, 4 Sep 2017 17:59:03 +0100
Received: from 950129200 (196.252.114.87.dyn.plus.net [87.114.252.196]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id v84Gx1ph006283 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Sep 2017 17:59:02 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Elwyn Davies'" <elwynd@dial.pipex.com>, <gen-art@ietf.org>
Cc: <draft-ietf-teas-pce-central-control.all@ietf.org>, <ietf@ietf.org>, <teas@ietf.org>
References: <rfhekveodc5rfqnx7mjqh18i.1504532678414@email.android.com>
In-Reply-To: <rfhekveodc5rfqnx7mjqh18i.1504532678414@email.android.com>
Date: Mon, 4 Sep 2017 17:59:00 +0100
Message-ID: <055001d3259f$1b86e750$5294b5f0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0551_01D325A7.7D500A40"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFPQJ9uAfmyPpSzi7H2PguHhxmKOqOsuiuQ
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-23304.001
X-TM-AS-Result: No--39.197-10.0-31-10
X-imss-scan-details: No--39.197-10.0-31-10
X-TMASE-MatchedRID: 8HTFlOrbAtHtvMVN/9JMyhIMDPFEv6UxaL9g24i1ttV4sKInj/osm7+F 5bh4N9c/nwDcrOcCISvBudlKdl9AGu5BG6Mr3NWaknV2Dc7+QbHnFDhXm/j3I87QgtSUcDEy1WJ BvqhSgSkENLaL1ZQGAiFyczyoJ0RqiXDwRBge15rM1jffIgQXhso7mIWzSjiM6yKEyHG4lURMeA WHgRfLNB1uclAMPpFHa/qlTDFTzyPMM0KP1pISrWjZ8q/Oc1nAVQHOr6CvF1YM74Nf6tTB9i7sr eQJNnc7gMcbIURayq2sKEpNuJAwUPDZOKmFLlvIdFmXOeGyE+9imi8LvNfmr4aKwv8Fn/097hK9 01+mC+ARW3Fo+hK3sJbNfgtQUD+kR1vveBQPCRfBtFDYGmaWKrRfRjDbtW6i5DjmdW0+qbGuwVT xTDkELrK2YHb/kidP/PEgL0tqyq50bnu2kHqixLMsPmSZxbpkE7JInT4wddoTjfkO3pb+WD0msI gSyun3H/Z71HJDNaFacyhB9L1ar9+PZq+Z+KYzkdcpJKX5Jwr8BlbXy+O/WnKuL8SC59l3YCowK SvpI+95QzetarMsxEgF6uuiHQ769Z8q6rO+Ih6Ycl4BgqVyk3cF/0kiqyh4DxjBugJBzzwITux6 kRboK/Nt5XZU3wuLk1zNU0ainQZP5mzaUz6wQBD3+0w1DhqK3kR1SkDo278ML9Wb3Qh/ha0QmL2 wrxWPWU8XtC6NtyQqhZrv4f7cO34FjWYN+jMve5NWR5iixe05LRtPnepd1cO/l0Ny5PZ5mg+Op3 qhhyTwpvAauYPakRQAXi4Ga9GRHxPMjOKY7A+DGx/OQ1GV8mgVPcrOkeoTLL+82TohWm+nmxwsc wVeEzsAVzN+Ov/s51hhkcWdulLbz1hTXw72C1/6pS7IuoTZZVZHHJqxW835MQR4E76/Ig==
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/X26XpHUWnzSFsqzj9adN6aSGSpE>
Subject: Re: [Gen-art] [Teas] Genart telechat review of draft-ietf-teas-pce-central-control-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 16:59:20 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0551_01D325A7.7D500A40
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi Elwyn,
=20
-04 has
   Some of this will be the TED as is normal for a PCE and can be
  collected using the mechanisms already in place (such as listening to
   the IGPs, using BGP-LS [RFC7752], or northbound export of YANG-
   encoded data [I-D.ietf-teas-yang-te-topo]).
-05 has
   Some of this will be the TED as is normal for a PCE and can be
   collected using the mechanisms already in place (such as listening to
   the IGPs, using BGP-LS [RFC7752], or northbound export of YANG-
   encoded data [I-D.ietf-teas-yang-te-topo] from the network elements
   to the controller).
=20
I think that probably gives enough context.
=20
Yes, thanks for the typo in 2.1.2. I'll save it for Auth48.
=20
A
=20
From: Elwyn Davies [mailto:elwynd@dial.pipex.com]=20
Sent: 04 September 2017 14:46
To: adrian@olddog.co.uk; gen-art@ietf.org
Cc: draft-ietf-teas-pce-central-control.all@ietf.org; ietf@ietf.org; =
teas@ietf.org
Subject: RE: [Teas] Genart telechat review of =
draft-ietf-teas-pce-central-control-04
=20
=20
Hi, Adrian.
=20
Two points:
- I don't see an explanation of northbound in -05.
- In the new text at the end of s2.1.2 s/whole the controllers/while the =
controllers/
=20
Otherwise, the extra text and changes look helpful.
=20
Best wshes,
Elwyn
=20
=20
Sent from Samsung tablet.
=20
-------- Original message --------
From: Adrian Farrel <adrian@olddog.co.uk>=20
Date: 04/09/2017 10:47 (GMT+00:00)=20
To: 'Elwyn Davies' <elwynd@dial.pipex.com>, gen-art@ietf.org=20
Cc: draft-ietf-teas-pce-central-control.all@ietf.org, ietf@ietf.org, =
teas@ietf.org=20
Subject: RE: [Teas] Genart telechat review of =
draft-ietf-teas-pce-central-control-04=20
=20
Thanks Elwyn,

Clarified in the next revision.

Adrian

> -----Original Message-----
> From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Elwyn Davies
> Sent: 28 August 2017 20:24
> To: gen-art@ietf.org
> Cc: draft-ietf-teas-pce-central-control.all@ietf.org; ietf@ietf.org;
teas@ietf.org
> Subject: [Teas] Genart telechat review of
draft-ietf-teas-pce-central-control-04
>=20
> Reviewer: Elwyn Davies
> Review result: Ready with Nits
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair. Please wait for direction from your
> document shepherd or AD before posting a new version of the draft.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-teas-pce-central-control-04
> Reviewer: Elwyn Davies
> Review Date: 2017-08-28
> IETF LC End Date: 2017-08-24
> IESG Telechat date: 2017-08-31
>=20
> Summary: Thanks for addressing my Last Call comments on -03.  The new =
version
> is ready with one introduced nit.  Also I am still of the abstract is =
somewhat
> overlong.
>=20
> Nit:
> s6, para 2: The SDN term 'northbound' has appeared in the new version. =
Needs
> brief explanation.
>=20
> Major issues:
>=20
> Minor issues:
>=20
> Nits/editorial comments:
>=20
>=20
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas

------=_NextPart_000_0551_01D325A7.7D500A40
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DProgId content=3DWord.Document><meta name=3DGenerator =
content=3D"Microsoft Word 14"><meta name=3DOriginator =
content=3D"Microsoft Word 14"><link rel=3DFile-List =
href=3D"cid:filelist.xml@01D325A6.1C1DCBF0"><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:EnvelopeVis/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-GB</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:DoNotExpandShiftReturn/>
<w:BreakWrappedTables/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true" =
DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" =
LatentStyleCount=3D"267">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1073786111 1 0 415 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520081665 -1073717157 41 0 66047 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	mso-fareast-font-family:Calibri;}
a:link, span.MsoHyperlink
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-size:10.0pt;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
</style><![endif]--><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB link=3Dblue =
vlink=3Dpurple style=3D'tab-interval:36.0pt'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>Hi =
Elwyn,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>-04 =
has<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><span =
style=3D'mso-spacerun:yes'>=C2=A0=C2=A0 </span>Some of this will be the =
TED as is normal for a PCE and can be<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'> <span =
style=3D'mso-spacerun:yes'>=C2=A0=C2=A0</span>collected using the =
mechanisms already in place (such as listening =
to<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><span =
style=3D'mso-spacerun:yes'>=C2=A0=C2=A0 </span>the IGPs, using BGP-LS =
[RFC7752], or northbound export of YANG-<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><span =
style=3D'mso-spacerun:yes'>=C2=A0=C2=A0 </span>encoded data =
[I-D.ietf-teas-yang-te-topo]).<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>-05 =
has<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><span =
style=3D'mso-spacerun:yes'>=C2=A0=C2=A0 </span>Some of this will be the =
TED as is normal for a PCE and can be<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><span =
style=3D'mso-spacerun:yes'>=C2=A0=C2=A0 </span>collected using the =
mechanisms already in place (such as listening =
to<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><span =
style=3D'mso-spacerun:yes'>=C2=A0=C2=A0 </span>the IGPs, using BGP-LS =
[RFC7752], or northbound export of YANG-<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><span =
style=3D'mso-spacerun:yes'>=C2=A0=C2=A0 </span>encoded data =
[I-D.ietf-teas-yang-te-topo] from the network =
elements<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><span =
style=3D'mso-spacerun:yes'>=C2=A0=C2=A0 </span>to the =
controller).<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>I think that probably gives =
enough context.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>Yes, thanks for the typo in =
2.1.2. I'll save it for Auth48.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>A<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New =
Roman";mso-ansi-language:EN-US'>From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New Roman";mso-ansi-language:EN-US'> Elwyn Davies =
[mailto:elwynd@dial.pipex.com] <br><b>Sent:</b> 04 September 2017 =
14:46<br><b>To:</b> adrian@olddog.co.uk; gen-art@ietf.org<br><b>Cc:</b> =
draft-ietf-teas-pce-central-control.all@ietf.org; ietf@ietf.org; =
teas@ietf.org<br><b>Subject:</b> RE: [Teas] Genart telechat review of =
draft-ietf-teas-pce-central-control-04<o:p></o:p></span></p></div></div><=
p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal><span =
style=3D'mso-fareast-font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times New =
Roman"'>Hi, Adrian.<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times New =
Roman"'>Two points:<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times New =
Roman"'>- I don't see an explanation of northbound in =
-05.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'mso-fareast-font-family:"Times New Roman"'>- In the new text at =
the end of s2.1.2 s/whole the controllers/while the =
controllers/<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'mso-fareast-font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times New =
Roman"'>Otherwise, the extra text and changes look =
helpful.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'mso-fareast-font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times New =
Roman"'>Best wshes,<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times New =
Roman"'>Elwyn<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'mso-fareast-font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></p></div><div =
id=3D"composer_signature"><div><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;mso-fareast-font-family:"Times New =
Roman";color:#575757'>Sent from Samsung =
tablet.<o:p></o:p></span></p></div></div><div><p class=3DMsoNormal><span =
style=3D'mso-fareast-font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></p></div><div><div><p =
class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times New =
Roman";color:black'>-------- Original message =
--------<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'mso-fareast-font-family:"Times New Roman";color:black'>From: =
Adrian Farrel &lt;adrian@olddog.co.uk&gt; =
<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'mso-fareast-font-family:"Times New Roman";color:black'>Date: =
04/09/2017 10:47 (GMT+00:00) <o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times New =
Roman";color:black'>To: 'Elwyn Davies' &lt;elwynd@dial.pipex.com&gt;, =
gen-art@ietf.org <o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times New =
Roman";color:black'>Cc: =
draft-ietf-teas-pce-central-control.all@ietf.org, ietf@ietf.org, =
teas@ietf.org <o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times New =
Roman";color:black'>Subject: RE: [Teas] Genart telechat review of =
draft-ietf-teas-pce-central-control-04 =
<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'mso-fareast-font-family:"Times New =
Roman";color:black'><o:p>&nbsp;</o:p></span></p></div></div><p =
class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'mso-fareast-font-family:"Times New Roman"'>Thanks =
Elwyn,<br><br>Clarified in the next revision.<br><br>Adrian<br><br>&gt; =
-----Original Message-----<br>&gt; From: Teas =
[mailto:teas-bounces@ietf.org] On Behalf Of Elwyn Davies<br>&gt; Sent: =
28 August 2017 20:24<br>&gt; To: gen-art@ietf.org<br>&gt; Cc: =
draft-ietf-teas-pce-central-control.all@ietf.org; =
ietf@ietf.org;<br>teas@ietf.org<br>&gt; Subject: [Teas] Genart telechat =
review of<br>draft-ietf-teas-pce-central-control-04<br>&gt; <br>&gt; =
Reviewer: Elwyn Davies<br>&gt; Review result: Ready with Nits<br>&gt; =
<br>&gt; I am the assigned Gen-ART reviewer for this draft. The General =
Area<br>&gt; Review Team (Gen-ART) reviews all IETF documents being =
processed<br>&gt; by the IESG for the IETF Chair. Please wait for =
direction from your<br>&gt; document shepherd or AD before posting a new =
version of the draft.<br>&gt; <br>&gt; For more information, please see =
the FAQ at<br>&gt; <br>&gt; =
&lt;https://trac.ietf.org/trac/gen/wiki/GenArtfaq&gt;.<br>&gt; <br>&gt; =
Document: draft-ietf-teas-pce-central-control-04<br>&gt; Reviewer: Elwyn =
Davies<br>&gt; Review Date: 2017-08-28<br>&gt; IETF LC End Date: =
2017-08-24<br>&gt; IESG Telechat date: 2017-08-31<br>&gt; <br>&gt; =
Summary: Thanks for addressing my Last Call comments on -03.&nbsp; The =
new version<br>&gt; is ready with one introduced nit.&nbsp; Also I am =
still of the abstract is somewhat<br>&gt; overlong.<br>&gt; <br>&gt; =
Nit:<br>&gt; s6, para 2: The SDN term 'northbound' has appeared in the =
new version. Needs<br>&gt; brief explanation.<br>&gt; <br>&gt; Major =
issues:<br>&gt; <br>&gt; Minor issues:<br>&gt; <br>&gt; Nits/editorial =
comments:<br>&gt; <br>&gt; <br>&gt; =
_______________________________________________<br>&gt; Teas mailing =
list<br>&gt; Teas@ietf.org<br>&gt; =
https://www.ietf.org/mailman/listinfo/teas<o:p></o:p></span></p></div></d=
iv></body></html>
------=_NextPart_000_0551_01D325A7.7D500A40--


From nobody Mon Sep  4 14:01:13 2017
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 652911320CF; Mon,  4 Sep 2017 14:01:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.954
X-Spam-Level: 
X-Spam-Status: No, score=-1.954 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
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 HAk9ZtmhqgFV; Mon,  4 Sep 2017 14:01:03 -0700 (PDT)
Received: from a-painless.mh.aa.net.uk (a-painless.mh.aa.net.uk [81.187.30.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D9EB12426E; Mon,  4 Sep 2017 14:01:03 -0700 (PDT)
Received: from 153.107.2.81.in-addr.arpa ([81.2.107.153] helo=[192.168.0.134]) by a-painless.mh.aa.net.uk with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <elwynd@dial.pipex.com>) id 1doyNs-0001VZ-34; Mon, 04 Sep 2017 21:54:16 +0100
Date: Mon, 04 Sep 2017 21:54:14 +0100
Message-ID: <21r6makqd3wjckx8ptulkfkg.1504558193773@email.android.com>
Importance: normal
From: Elwyn Davies <elwynd@dial.pipex.com>
To: adrian@olddog.co.uk, gen-art@ietf.org
Cc: draft-ietf-teas-pce-central-control.all@ietf.org, ietf@ietf.org, teas@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.samsung.android.email_1049265487762570"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/QMOPlv36x_GQbIs3R6hIhR3gqXY>
Subject: Re: [Gen-art] [Teas] Genart telechat review of draft-ietf-teas-pce-central-control-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 21:01:06 -0000

----_com.samsung.android.email_1049265487762570
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

SGksIEFkcmlhbi4KT0ssIGl0J3MgYSBmYWlyIGNvcC4KQ2hlZXJzLEVsd3luCgoKU2VudCBmcm9t
IFNhbXN1bmcgdGFibGV0LgotLS0tLS0tLSBPcmlnaW5hbCBtZXNzYWdlIC0tLS0tLS0tRnJvbTog
QWRyaWFuIEZhcnJlbCA8YWRyaWFuQG9sZGRvZy5jby51az4gRGF0ZTogMDQvMDkvMjAxNyAgMTc6
NTkgIChHTVQrMDA6MDApIFRvOiAnRWx3eW4gRGF2aWVzJyA8ZWx3eW5kQGRpYWwucGlwZXguY29t
PiwgZ2VuLWFydEBpZXRmLm9yZyBDYzogZHJhZnQtaWV0Zi10ZWFzLXBjZS1jZW50cmFsLWNvbnRy
b2wuYWxsQGlldGYub3JnLCBpZXRmQGlldGYub3JnLCB0ZWFzQGlldGYub3JnIFN1YmplY3Q6IFJF
OiBbVGVhc10gR2VuYXJ0IHRlbGVjaGF0IHJldmlldyBvZiBkcmFmdC1pZXRmLXRlYXMtcGNlLWNl
bnRyYWwtY29udHJvbC0wNCAKSGkgRWx3eW4swqAtMDQgaGFzwqDCoCBTb21lIG9mIHRoaXMgd2ls
bCBiZSB0aGUgVEVEIGFzIGlzIG5vcm1hbCBmb3IgYSBQQ0UgYW5kIGNhbiBiZSDCoMKgY29sbGVj
dGVkIHVzaW5nIHRoZSBtZWNoYW5pc21zIGFscmVhZHkgaW4gcGxhY2UgKHN1Y2ggYXMgbGlzdGVu
aW5nIHRvwqDCoCB0aGUgSUdQcywgdXNpbmcgQkdQLUxTIFtSRkM3NzUyXSwgb3Igbm9ydGhib3Vu
ZCBleHBvcnQgb2YgWUFORy3CoMKgIGVuY29kZWQgZGF0YSBbSS1ELmlldGYtdGVhcy15YW5nLXRl
LXRvcG9dKS4tMDUgaGFzwqDCoCBTb21lIG9mIHRoaXMgd2lsbCBiZSB0aGUgVEVEIGFzIGlzIG5v
cm1hbCBmb3IgYSBQQ0UgYW5kIGNhbiBiZcKgwqAgY29sbGVjdGVkIHVzaW5nIHRoZSBtZWNoYW5p
c21zIGFscmVhZHkgaW4gcGxhY2UgKHN1Y2ggYXMgbGlzdGVuaW5nIHRvwqDCoCB0aGUgSUdQcywg
dXNpbmcgQkdQLUxTIFtSRkM3NzUyXSwgb3Igbm9ydGhib3VuZCBleHBvcnQgb2YgWUFORy3CoMKg
IGVuY29kZWQgZGF0YSBbSS1ELmlldGYtdGVhcy15YW5nLXRlLXRvcG9dIGZyb20gdGhlIG5ldHdv
cmsgZWxlbWVudHPCoMKgIHRvIHRoZSBjb250cm9sbGVyKS7CoEkgdGhpbmsgdGhhdCBwcm9iYWJs
eSBnaXZlcyBlbm91Z2ggY29udGV4dC7CoFllcywgdGhhbmtzIGZvciB0aGUgdHlwbyBpbiAyLjEu
Mi4gSSdsbCBzYXZlIGl0IGZvciBBdXRoNDguwqBBwqBGcm9tOiBFbHd5biBEYXZpZXMgW21haWx0
bzplbHd5bmRAZGlhbC5waXBleC5jb21dIApTZW50OiAwNCBTZXB0ZW1iZXIgMjAxNyAxNDo0NgpU
bzogYWRyaWFuQG9sZGRvZy5jby51azsgZ2VuLWFydEBpZXRmLm9yZwpDYzogZHJhZnQtaWV0Zi10
ZWFzLXBjZS1jZW50cmFsLWNvbnRyb2wuYWxsQGlldGYub3JnOyBpZXRmQGlldGYub3JnOyB0ZWFz
QGlldGYub3JnClN1YmplY3Q6IFJFOiBbVGVhc10gR2VuYXJ0IHRlbGVjaGF0IHJldmlldyBvZiBk
cmFmdC1pZXRmLXRlYXMtcGNlLWNlbnRyYWwtY29udHJvbC0wNMKgwqBIaSwgQWRyaWFuLsKgVHdv
IHBvaW50czotIEkgZG9uJ3Qgc2VlIGFuIGV4cGxhbmF0aW9uIG9mIG5vcnRoYm91bmQgaW4gLTA1
Li0gSW4gdGhlIG5ldyB0ZXh0IGF0IHRoZSBlbmQgb2YgczIuMS4yIHMvd2hvbGUgdGhlIGNvbnRy
b2xsZXJzL3doaWxlIHRoZSBjb250cm9sbGVycy/CoE90aGVyd2lzZSwgdGhlIGV4dHJhIHRleHQg
YW5kIGNoYW5nZXMgbG9vayBoZWxwZnVsLsKgQmVzdCB3c2hlcyxFbHd5bsKgwqBTZW50IGZyb20g
U2Ftc3VuZyB0YWJsZXQuwqAtLS0tLS0tLSBPcmlnaW5hbCBtZXNzYWdlIC0tLS0tLS0tRnJvbTog
QWRyaWFuIEZhcnJlbCA8YWRyaWFuQG9sZGRvZy5jby51az4gRGF0ZTogMDQvMDkvMjAxNyAxMDo0
NyAoR01UKzAwOjAwKSBUbzogJ0Vsd3luIERhdmllcycgPGVsd3luZEBkaWFsLnBpcGV4LmNvbT4s
IGdlbi1hcnRAaWV0Zi5vcmcgQ2M6IGRyYWZ0LWlldGYtdGVhcy1wY2UtY2VudHJhbC1jb250cm9s
LmFsbEBpZXRmLm9yZywgaWV0ZkBpZXRmLm9yZywgdGVhc0BpZXRmLm9yZyBTdWJqZWN0OiBSRTog
W1RlYXNdIEdlbmFydCB0ZWxlY2hhdCByZXZpZXcgb2YgZHJhZnQtaWV0Zi10ZWFzLXBjZS1jZW50
cmFsLWNvbnRyb2wtMDQgwqBUaGFua3MgRWx3eW4sCgpDbGFyaWZpZWQgaW4gdGhlIG5leHQgcmV2
aXNpb24uCgpBZHJpYW4KCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0KPiBGcm9tOiBUZWFz
IFttYWlsdG86dGVhcy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgRWx3eW4gRGF2aWVz
Cj4gU2VudDogMjggQXVndXN0IDIwMTcgMjA6MjQKPiBUbzogZ2VuLWFydEBpZXRmLm9yZwo+IENj
OiBkcmFmdC1pZXRmLXRlYXMtcGNlLWNlbnRyYWwtY29udHJvbC5hbGxAaWV0Zi5vcmc7IGlldGZA
aWV0Zi5vcmc7CnRlYXNAaWV0Zi5vcmcKPiBTdWJqZWN0OiBbVGVhc10gR2VuYXJ0IHRlbGVjaGF0
IHJldmlldyBvZgpkcmFmdC1pZXRmLXRlYXMtcGNlLWNlbnRyYWwtY29udHJvbC0wNAo+IAo+IFJl
dmlld2VyOiBFbHd5biBEYXZpZXMKPiBSZXZpZXcgcmVzdWx0OiBSZWFkeSB3aXRoIE5pdHMKPiAK
PiBJIGFtIHRoZSBhc3NpZ25lZCBHZW4tQVJUIHJldmlld2VyIGZvciB0aGlzIGRyYWZ0LiBUaGUg
R2VuZXJhbCBBcmVhCj4gUmV2aWV3IFRlYW0gKEdlbi1BUlQpIHJldmlld3MgYWxsIElFVEYgZG9j
dW1lbnRzIGJlaW5nIHByb2Nlc3NlZAo+IGJ5IHRoZSBJRVNHIGZvciB0aGUgSUVURiBDaGFpci4g
UGxlYXNlIHdhaXQgZm9yIGRpcmVjdGlvbiBmcm9tIHlvdXIKPiBkb2N1bWVudCBzaGVwaGVyZCBv
ciBBRCBiZWZvcmUgcG9zdGluZyBhIG5ldyB2ZXJzaW9uIG9mIHRoZSBkcmFmdC4KPiAKPiBGb3Ig
bW9yZSBpbmZvcm1hdGlvbiwgcGxlYXNlIHNlZSB0aGUgRkFRIGF0Cj4gCj4gPGh0dHBzOi8vdHJh
Yy5pZXRmLm9yZy90cmFjL2dlbi93aWtpL0dlbkFydGZhcT4uCj4gCj4gRG9jdW1lbnQ6IGRyYWZ0
LWlldGYtdGVhcy1wY2UtY2VudHJhbC1jb250cm9sLTA0Cj4gUmV2aWV3ZXI6IEVsd3luIERhdmll
cwo+IFJldmlldyBEYXRlOiAyMDE3LTA4LTI4Cj4gSUVURiBMQyBFbmQgRGF0ZTogMjAxNy0wOC0y
NAo+IElFU0cgVGVsZWNoYXQgZGF0ZTogMjAxNy0wOC0zMQo+IAo+IFN1bW1hcnk6IFRoYW5rcyBm
b3IgYWRkcmVzc2luZyBteSBMYXN0IENhbGwgY29tbWVudHMgb24gLTAzLsKgIFRoZSBuZXcgdmVy
c2lvbgo+IGlzIHJlYWR5IHdpdGggb25lIGludHJvZHVjZWQgbml0LsKgIEFsc28gSSBhbSBzdGls
bCBvZiB0aGUgYWJzdHJhY3QgaXMgc29tZXdoYXQKPiBvdmVybG9uZy4KPiAKPiBOaXQ6Cj4gczYs
IHBhcmEgMjogVGhlIFNETiB0ZXJtICdub3J0aGJvdW5kJyBoYXMgYXBwZWFyZWQgaW4gdGhlIG5l
dyB2ZXJzaW9uLiBOZWVkcwo+IGJyaWVmIGV4cGxhbmF0aW9uLgo+IAo+IE1ham9yIGlzc3VlczoK
PiAKPiBNaW5vciBpc3N1ZXM6Cj4gCj4gTml0cy9lZGl0b3JpYWwgY29tbWVudHM6Cj4gCj4gCj4g
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KPiBUZWFzIG1h
aWxpbmcgbGlzdAo+IFRlYXNAaWV0Zi5vcmcKPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL3RlYXM=

----_com.samsung.android.email_1049265487762570
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0
L2h0bWw7IGNoYXJzZXQ9VVRGLTgiPjwvaGVhZD48Ym9keT48ZGl2PkhpLCBBZHJpYW4uPC9kaXY+
PGRpdj48YnI+PC9kaXY+PGRpdj5PSywgaXQncyBhIGZhaXIgY29wLjwvZGl2PjxkaXY+PGJyPjwv
ZGl2PjxkaXY+Q2hlZXJzLDwvZGl2PjxkaXY+RWx3eW48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2
Pjxicj48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2IGlkPSJjb21wb3Nlcl9zaWduYXR1cmUiPjxk
aXYgc3R5bGU9ImZvbnQtc2l6ZTo4NSU7Y29sb3I6IzU3NTc1NyIgZGlyPSJhdXRvIj5TZW50IGZy
b20gU2Ftc3VuZyB0YWJsZXQuPC9kaXY+PC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdiBzdHlsZT0i
Zm9udC1zaXplOjEwMCU7Y29sb3I6IzAwMDAwMCI+PCEtLSBvcmlnaW5hbE1lc3NhZ2UgLS0+PGRp
dj4tLS0tLS0tLSBPcmlnaW5hbCBtZXNzYWdlIC0tLS0tLS0tPC9kaXY+PGRpdj5Gcm9tOiBBZHJp
YW4gRmFycmVsICZsdDthZHJpYW5Ab2xkZG9nLmNvLnVrJmd0OyA8L2Rpdj48ZGl2PkRhdGU6IDA0
LzA5LzIwMTcgIDE3OjU5ICAoR01UKzAwOjAwKSA8L2Rpdj48ZGl2PlRvOiAnRWx3eW4gRGF2aWVz
JyAmbHQ7ZWx3eW5kQGRpYWwucGlwZXguY29tJmd0OywgZ2VuLWFydEBpZXRmLm9yZyA8L2Rpdj48
ZGl2PkNjOiBkcmFmdC1pZXRmLXRlYXMtcGNlLWNlbnRyYWwtY29udHJvbC5hbGxAaWV0Zi5vcmcs
IGlldGZAaWV0Zi5vcmcsIHRlYXNAaWV0Zi5vcmcgPC9kaXY+PGRpdj5TdWJqZWN0OiBSRTogW1Rl
YXNdIEdlbmFydCB0ZWxlY2hhdCByZXZpZXcgb2YgZHJhZnQtaWV0Zi10ZWFzLXBjZS1jZW50cmFs
LWNvbnRyb2wtMDQgPC9kaXY+PGRpdj48YnI+PC9kaXY+PC9kaXY+PGRpdiBjbGFzcz0iV29yZFNl
Y3Rpb24xIj48cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7
bXNvLWJpZGktZm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7O2NvbG9yOiMx
RjQ5N0QiPkhpIEVsd3luLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7bXNvLWJpZGktZm9udC1mYW1pbHk6JnF1b3Q7
VGltZXMgTmV3IFJvbWFuJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD48cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7
bXNvLWJpZGktZm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7O2NvbG9yOiMx
RjQ5N0QiPi0wNCBoYXM8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O21zby1iaWRpLWZvbnQtZmFtaWx5OiZxdW90O1Rp
bWVzIE5ldyBSb21hbiZxdW90Oztjb2xvcjojMUY0OTdEIj48c3BhbiBzdHlsZT0ibXNvLXNwYWNl
cnVuOnllcyI+Jm5ic3A7Jm5ic3A7IDwvc3Bhbj5Tb21lIG9mIHRoaXMgd2lsbCBiZSB0aGUgVEVE
IGFzIGlzIG5vcm1hbCBmb3IgYSBQQ0UgYW5kIGNhbiBiZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD48
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7bXNvLWJpZGkt
Zm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiA8
c3BhbiBzdHlsZT0ibXNvLXNwYWNlcnVuOnllcyI+Jm5ic3A7Jm5ic3A7PC9zcGFuPmNvbGxlY3Rl
ZCB1c2luZyB0aGUgbWVjaGFuaXNtcyBhbHJlYWR5IGluIHBsYWNlIChzdWNoIGFzIGxpc3Rlbmlu
ZyB0bzxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDs7bXNvLWJpZGktZm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJv
bWFuJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxzcGFuIHN0eWxlPSJtc28tc3BhY2VydW46eWVzIj4m
bmJzcDsmbmJzcDsgPC9zcGFuPnRoZSBJR1BzLCB1c2luZyBCR1AtTFMgW1JGQzc3NTJdLCBvciBu
b3J0aGJvdW5kIGV4cG9ydCBvZiBZQU5HLTxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7bXNvLWJpZGktZm9udC1mYW1p
bHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxzcGFuIHN0eWxl
PSJtc28tc3BhY2VydW46eWVzIj4mbmJzcDsmbmJzcDsgPC9zcGFuPmVuY29kZWQgZGF0YSBbSS1E
LmlldGYtdGVhcy15YW5nLXRlLXRvcG9dKS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O21zby1iaWRpLWZvbnQtZmFt
aWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90Oztjb2xvcjojMUY0OTdEIj4tMDUgaGFzPG86
cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1z
ZXJpZiZxdW90Ozttc28tYmlkaS1mb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVv
dDs7Y29sb3I6IzFGNDk3RCI+PHNwYW4gc3R5bGU9Im1zby1zcGFjZXJ1bjp5ZXMiPiZuYnNwOyZu
YnNwOyA8L3NwYW4+U29tZSBvZiB0aGlzIHdpbGwgYmUgdGhlIFRFRCBhcyBpcyBub3JtYWwgZm9y
IGEgUENFIGFuZCBjYW4gYmU8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O21zby1iaWRpLWZvbnQtZmFtaWx5OiZxdW90
O1RpbWVzIE5ldyBSb21hbiZxdW90Oztjb2xvcjojMUY0OTdEIj48c3BhbiBzdHlsZT0ibXNvLXNw
YWNlcnVuOnllcyI+Jm5ic3A7Jm5ic3A7IDwvc3Bhbj5jb2xsZWN0ZWQgdXNpbmcgdGhlIG1lY2hh
bmlzbXMgYWxyZWFkeSBpbiBwbGFjZSAoc3VjaCBhcyBsaXN0ZW5pbmcgdG88bzpwPjwvbzpwPjwv
c3Bhbj48L3A+PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
O21zby1iaWRpLWZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90Oztjb2xvcjoj
MUY0OTdEIj48c3BhbiBzdHlsZT0ibXNvLXNwYWNlcnVuOnllcyI+Jm5ic3A7Jm5ic3A7IDwvc3Bh
bj50aGUgSUdQcywgdXNpbmcgQkdQLUxTIFtSRkM3NzUyXSwgb3Igbm9ydGhib3VuZCBleHBvcnQg
b2YgWUFORy08bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oywm
cXVvdDtzYW5zLXNlcmlmJnF1b3Q7O21zby1iaWRpLWZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5l
dyBSb21hbiZxdW90Oztjb2xvcjojMUY0OTdEIj48c3BhbiBzdHlsZT0ibXNvLXNwYWNlcnVuOnll
cyI+Jm5ic3A7Jm5ic3A7IDwvc3Bhbj5lbmNvZGVkIGRhdGEgW0ktRC5pZXRmLXRlYXMteWFuZy10
ZS10b3BvXSBmcm9tIHRoZSBuZXR3b3JrIGVsZW1lbnRzPG86cD48L286cD48L3NwYW4+PC9wPjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Ozttc28tYmlkaS1m
b250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDs7Y29sb3I6IzFGNDk3RCI+PHNw
YW4gc3R5bGU9Im1zby1zcGFjZXJ1bjp5ZXMiPiZuYnNwOyZuYnNwOyA8L3NwYW4+dG8gdGhlIGNv
bnRyb2xsZXIpLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7bXNvLWJpZGktZm9udC1mYW1pbHk6JnF1b3Q7VGltZXMg
TmV3IFJvbWFuJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD48cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7bXNvLWJp
ZGktZm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7O2NvbG9yOiMxRjQ5N0Qi
PkkgdGhpbmsgdGhhdCBwcm9iYWJseSBnaXZlcyBlbm91Z2ggY29udGV4dC48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
O21zby1iaWRpLWZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90Oztjb2xvcjoj
MUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O21zby1iaWRpLWZvbnQtZmFtaWx5OiZxdW90O1Rp
bWVzIE5ldyBSb21hbiZxdW90Oztjb2xvcjojMUY0OTdEIj5ZZXMsIHRoYW5rcyBmb3IgdGhlIHR5
cG8gaW4gMi4xLjIuIEknbGwgc2F2ZSBpdCBmb3IgQXV0aDQ4LjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD48cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7bXNvLWJp
ZGktZm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7O2NvbG9yOiMxRjQ5N0Qi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDs7bXNvLWJpZGktZm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3
IFJvbWFuJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkE8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O21zby1iaWRpLWZvbnQt
ZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+PGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6
c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0Ij48ZGl2PjxkaXYgc3R5
bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMu
MHB0IDBjbSAwY20gMGNtIj48cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7bXNvLWZhcmVhc3QtZm9udC1mYW1pbHk6JnF1b3Q7VGlt
ZXMgTmV3IFJvbWFuJnF1b3Q7O21zby1hbnNpLWxhbmd1YWdlOkVOLVVTIj5Gcm9tOjwvc3Bhbj48
L2I+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O21zby1mYXJlYXN0LWZv
bnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90Ozttc28tYW5zaS1sYW5ndWFnZTpF
Ti1VUyI+IEVsd3luIERhdmllcyBbbWFpbHRvOmVsd3luZEBkaWFsLnBpcGV4LmNvbV0gPGJyPjxi
PlNlbnQ6PC9iPiAwNCBTZXB0ZW1iZXIgMjAxNyAxNDo0Njxicj48Yj5Ubzo8L2I+IGFkcmlhbkBv
bGRkb2cuY28udWs7IGdlbi1hcnRAaWV0Zi5vcmc8YnI+PGI+Q2M6PC9iPiBkcmFmdC1pZXRmLXRl
YXMtcGNlLWNlbnRyYWwtY29udHJvbC5hbGxAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmc7IHRlYXNA
aWV0Zi5vcmc8YnI+PGI+U3ViamVjdDo8L2I+IFJFOiBbVGVhc10gR2VuYXJ0IHRlbGVjaGF0IHJl
dmlldyBvZiBkcmFmdC1pZXRmLXRlYXMtcGNlLWNlbnRyYWwtY29udHJvbC0wNDxvOnA+PC9vOnA+
PC9zcGFuPjwvcD48L2Rpdj48L2Rpdj48cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD48ZGl2PjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFz
dC1mb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD48L2Rpdj48ZGl2PjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJtc28tZmFyZWFzdC1mb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPkhp
LCBBZHJpYW4uPG86cD48L286cD48L3NwYW4+PC9wPjwvZGl2PjxkaXY+PHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5l
dyBSb21hbiZxdW90OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjwvZGl2PjxkaXY+PHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWZvbnQtZmFtaWx5OiZx
dW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+VHdvIHBvaW50czo8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+PC9kaXY+PGRpdj48cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWZhcmVh
c3QtZm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij4tIEkgZG9uJ3Qgc2Vl
IGFuIGV4cGxhbmF0aW9uIG9mIG5vcnRoYm91bmQgaW4gLTA1LjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD48L2Rpdj48ZGl2PjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFz
dC1mb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPi0gSW4gdGhlIG5ldyB0
ZXh0IGF0IHRoZSBlbmQgb2YgczIuMS4yIHMvd2hvbGUgdGhlIGNvbnRyb2xsZXJzL3doaWxlIHRo
ZSBjb250cm9sbGVycy88bzpwPjwvbzpwPjwvc3Bhbj48L3A+PC9kaXY+PGRpdj48cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtZm9udC1mYW1pbHk6JnF1b3Q7VGlt
ZXMgTmV3IFJvbWFuJnF1b3Q7Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PC9kaXY+PGRp
dj48cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtZm9udC1mYW1p
bHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij5PdGhlcndpc2UsIHRoZSBleHRyYSB0ZXh0
IGFuZCBjaGFuZ2VzIGxvb2sgaGVscGZ1bC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+PC9kaXY+PGRp
dj48cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtZm9udC1mYW1p
bHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+PC9kaXY+PGRpdj48cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWZhcmVh
c3QtZm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij5CZXN0IHdzaGVzLDxv
OnA+PC9vOnA+PC9zcGFuPjwvcD48L2Rpdj48ZGl2PjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJtc28tZmFyZWFzdC1mb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVv
dDsiPkVsd3luPG86cD48L286cD48L3NwYW4+PC9wPjwvZGl2PjxkaXY+PHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5l
dyBSb21hbiZxdW90OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjwvZGl2PjxkaXY+PHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWZvbnQtZmFtaWx5OiZx
dW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjwv
ZGl2PjxkaXYgaWQ9ImNvbXBvc2VyX3NpZ25hdHVyZSI+PGRpdj48cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDttc28tZmFyZWFzdC1mb250LWZhbWlseTom
cXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDs7Y29sb3I6IzU3NTc1NyI+U2VudCBmcm9tIFNhbXN1
bmcgdGFibGV0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48L2Rpdj48L2Rpdj48ZGl2PjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1mb250LWZhbWlseTomcXVvdDtU
aW1lcyBOZXcgUm9tYW4mcXVvdDsiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48L2Rpdj48
ZGl2PjxkaXY+PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWZv
bnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90Oztjb2xvcjpibGFjayI+LS0tLS0t
LS0gT3JpZ2luYWwgbWVzc2FnZSAtLS0tLS0tLTxvOnA+PC9vOnA+PC9zcGFuPjwvcD48L2Rpdj48
ZGl2PjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1mb250LWZh
bWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDs7Y29sb3I6YmxhY2siPkZyb206IEFkcmlh
biBGYXJyZWwgJmx0O2FkcmlhbkBvbGRkb2cuY28udWsmZ3Q7IDxvOnA+PC9vOnA+PC9zcGFuPjwv
cD48L2Rpdj48ZGl2PjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFz
dC1mb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDs7Y29sb3I6YmxhY2siPkRh
dGU6IDA0LzA5LzIwMTcgMTA6NDcgKEdNVCswMDowMCkgPG86cD48L286cD48L3NwYW4+PC9wPjwv
ZGl2PjxkaXY+PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWZv
bnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90Oztjb2xvcjpibGFjayI+VG86ICdF
bHd5biBEYXZpZXMnICZsdDtlbHd5bmRAZGlhbC5waXBleC5jb20mZ3Q7LCBnZW4tYXJ0QGlldGYu
b3JnIDxvOnA+PC9vOnA+PC9zcGFuPjwvcD48L2Rpdj48ZGl2PjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1mb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9t
YW4mcXVvdDs7Y29sb3I6YmxhY2siPkNjOiBkcmFmdC1pZXRmLXRlYXMtcGNlLWNlbnRyYWwtY29u
dHJvbC5hbGxAaWV0Zi5vcmcsIGlldGZAaWV0Zi5vcmcsIHRlYXNAaWV0Zi5vcmcgPG86cD48L286
cD48L3NwYW4+PC9wPjwvZGl2PjxkaXY+PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
Im1zby1mYXJlYXN0LWZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90Oztjb2xv
cjpibGFjayI+U3ViamVjdDogUkU6IFtUZWFzXSBHZW5hcnQgdGVsZWNoYXQgcmV2aWV3IG9mIGRy
YWZ0LWlldGYtdGVhcy1wY2UtY2VudHJhbC1jb250cm9sLTA0IDxvOnA+PC9vOnA+PC9zcGFuPjwv
cD48L2Rpdj48ZGl2PjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFz
dC1mb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDs7Y29sb3I6YmxhY2siPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48L2Rpdj48L2Rpdj48cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1m
b250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPlRoYW5rcyBFbHd5biw8YnI+
PGJyPkNsYXJpZmllZCBpbiB0aGUgbmV4dCByZXZpc2lvbi48YnI+PGJyPkFkcmlhbjxicj48YnI+
Jmd0OyAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxicj4mZ3Q7IEZyb206IFRlYXMgW21haWx0
bzp0ZWFzLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBFbHd5biBEYXZpZXM8YnI+Jmd0
OyBTZW50OiAyOCBBdWd1c3QgMjAxNyAyMDoyNDxicj4mZ3Q7IFRvOiBnZW4tYXJ0QGlldGYub3Jn
PGJyPiZndDsgQ2M6IGRyYWZ0LWlldGYtdGVhcy1wY2UtY2VudHJhbC1jb250cm9sLmFsbEBpZXRm
Lm9yZzsgaWV0ZkBpZXRmLm9yZzs8YnI+dGVhc0BpZXRmLm9yZzxicj4mZ3Q7IFN1YmplY3Q6IFtU
ZWFzXSBHZW5hcnQgdGVsZWNoYXQgcmV2aWV3IG9mPGJyPmRyYWZ0LWlldGYtdGVhcy1wY2UtY2Vu
dHJhbC1jb250cm9sLTA0PGJyPiZndDsgPGJyPiZndDsgUmV2aWV3ZXI6IEVsd3luIERhdmllczxi
cj4mZ3Q7IFJldmlldyByZXN1bHQ6IFJlYWR5IHdpdGggTml0czxicj4mZ3Q7IDxicj4mZ3Q7IEkg
YW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIFRoZSBHZW5l
cmFsIEFyZWE8YnI+Jmd0OyBSZXZpZXcgVGVhbSAoR2VuLUFSVCkgcmV2aWV3cyBhbGwgSUVURiBk
b2N1bWVudHMgYmVpbmcgcHJvY2Vzc2VkPGJyPiZndDsgYnkgdGhlIElFU0cgZm9yIHRoZSBJRVRG
IENoYWlyLiBQbGVhc2Ugd2FpdCBmb3IgZGlyZWN0aW9uIGZyb20geW91cjxicj4mZ3Q7IGRvY3Vt
ZW50IHNoZXBoZXJkIG9yIEFEIGJlZm9yZSBwb3N0aW5nIGEgbmV3IHZlcnNpb24gb2YgdGhlIGRy
YWZ0Ljxicj4mZ3Q7IDxicj4mZ3Q7IEZvciBtb3JlIGluZm9ybWF0aW9uLCBwbGVhc2Ugc2VlIHRo
ZSBGQVEgYXQ8YnI+Jmd0OyA8YnI+Jmd0OyAmbHQ7aHR0cHM6Ly90cmFjLmlldGYub3JnL3RyYWMv
Z2VuL3dpa2kvR2VuQXJ0ZmFxJmd0Oy48YnI+Jmd0OyA8YnI+Jmd0OyBEb2N1bWVudDogZHJhZnQt
aWV0Zi10ZWFzLXBjZS1jZW50cmFsLWNvbnRyb2wtMDQ8YnI+Jmd0OyBSZXZpZXdlcjogRWx3eW4g
RGF2aWVzPGJyPiZndDsgUmV2aWV3IERhdGU6IDIwMTctMDgtMjg8YnI+Jmd0OyBJRVRGIExDIEVu
ZCBEYXRlOiAyMDE3LTA4LTI0PGJyPiZndDsgSUVTRyBUZWxlY2hhdCBkYXRlOiAyMDE3LTA4LTMx
PGJyPiZndDsgPGJyPiZndDsgU3VtbWFyeTogVGhhbmtzIGZvciBhZGRyZXNzaW5nIG15IExhc3Qg
Q2FsbCBjb21tZW50cyBvbiAtMDMuJm5ic3A7IFRoZSBuZXcgdmVyc2lvbjxicj4mZ3Q7IGlzIHJl
YWR5IHdpdGggb25lIGludHJvZHVjZWQgbml0LiZuYnNwOyBBbHNvIEkgYW0gc3RpbGwgb2YgdGhl
IGFic3RyYWN0IGlzIHNvbWV3aGF0PGJyPiZndDsgb3ZlcmxvbmcuPGJyPiZndDsgPGJyPiZndDsg
Tml0Ojxicj4mZ3Q7IHM2LCBwYXJhIDI6IFRoZSBTRE4gdGVybSAnbm9ydGhib3VuZCcgaGFzIGFw
cGVhcmVkIGluIHRoZSBuZXcgdmVyc2lvbi4gTmVlZHM8YnI+Jmd0OyBicmllZiBleHBsYW5hdGlv
bi48YnI+Jmd0OyA8YnI+Jmd0OyBNYWpvciBpc3N1ZXM6PGJyPiZndDsgPGJyPiZndDsgTWlub3Ig
aXNzdWVzOjxicj4mZ3Q7IDxicj4mZ3Q7IE5pdHMvZWRpdG9yaWFsIGNvbW1lbnRzOjxicj4mZ3Q7
IDxicj4mZ3Q7IDxicj4mZ3Q7IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fPGJyPiZndDsgVGVhcyBtYWlsaW5nIGxpc3Q8YnI+Jmd0OyBUZWFzQGlldGYub3Jn
PGJyPiZndDsgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby90ZWFzPG86cD48
L286cD48L3NwYW4+PC9wPjwvZGl2PjwvZGl2PjwvYm9keT48L2h0bWw+

----_com.samsung.android.email_1049265487762570--


From nobody Mon Sep  4 18:25:43 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CBB391321A5; Mon,  4 Sep 2017 18:25:29 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern <jmh@joelhalpern.com>
To: <gen-art@ietf.org>
Cc: kitten@ietf.org, ietf@ietf.org, draft-ietf-kitten-rfc5653bis.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.59.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150457472979.28661.15542249793619015627@ietfa.amsl.com>
Date: Mon, 04 Sep 2017 18:25:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/uraFVNSEtv0D7G6BfmOYgoytGKY>
Subject: [Gen-art] Genart last call review of draft-ietf-kitten-rfc5653bis-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Sep 2017 01:25:30 -0000

Reviewer: Joel Halpern
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-kitten-rfc5653bis-05
Reviewer: Joel Halpern
Review Date: 2017-09-04
IETF LC End Date: 2017-09-11
IESG Telechat date: Not scheduled for a telechat

Summary: This document is ready for publication as a Proposed Standard RFC.

Reviewer note: The reviewer concentrated on the changes from the previous RFC,
and did not attempt to review the code.  The changes seem clear and
understandable.

Major issues: N/A

Minor issues: N/A

Nits/editorial comments:  N/A



From nobody Mon Sep  4 19:09:12 2017
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A41AA1321A6; Mon,  4 Sep 2017 19:09:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 fh_idjb2qMm3; Mon,  4 Sep 2017 19:09:09 -0700 (PDT)
Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 587A0126C19; Mon,  4 Sep 2017 19:09:09 -0700 (PDT)
Received: by mail-yw0-x22a.google.com with SMTP id w204so7690162ywg.3; Mon, 04 Sep 2017 19:09:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=J7Lr1tc9qlUUa0fpzxF0LpD0f2RQ2zpSTgiERB+3RBc=; b=BUFRW1SV2O6vnuQA74dsxt4U+PkkLgrS9j/c0xYlVsgmozgK3G5SYRUSGveMSxK23/ de08SGoybUqXeMVXHT7Y9OmYY3IEQDm7a3R6zqkPci/PYcwjugw3HYcOeQHmnCXbJttF sn9vr+bp4eqguPFwHToprfx3eZ1Ltb20D62nipLnroMtxq0xTEaA3DgS8hXI5+vzm/+B LBzFxeZ5C0jBuiyFNsAHY2CqH5lSp7SYwgvTO9Zba7h+NTPKuDinvnnO6LAxM4zZe0qE xrk0+OhYOTujDm0q2uCiLLdr2kPyOyTaAl0vfrFKnSaouvTBYVYC3w+kTTWKkBIuC5rt pPbA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=J7Lr1tc9qlUUa0fpzxF0LpD0f2RQ2zpSTgiERB+3RBc=; b=IGuDHgvarE+rKa9ytX6r62S+XpsX3YYmtCweB3cjyZWmn5ksLNN0JE6VnvxggKcuqH eFQFmN8/OzzPR+ITfy/K2MW7itn8jrndEHjNkuM67azsDD9CWGBG9rJ56Zh3AzLk18nN tzmju6PkTe93D0Tu5IrMOSpFExetGu48CQuO4QaDTNs6EeLWg6a9oGzFVLVjyHObo4os iogTkPCf5zNJmjVD0eiXfTkokgyAWY/cB58zqDNUuv/1HYWAP8vxc0lJn4c+NPSbK8Jy CDSAx9jMrPQVo1DUF8yijl7ci7UZvVxcb2g1KgjFSiOOTM+iUsO9lw1rDheu7qBZfd3X qijw==
X-Gm-Message-State: AHPjjUhVoj00Gyg0hSHqJLSqlDyVURTABE8CCBUPm/C+QXSQ+oOygV8Q gJd2P7CYPi2VsymvNNTS4vX0ns+R3A==
X-Google-Smtp-Source: ADKCNb6DSPwszHAOzNiSSQGfamORoKB80MvvVFksqC8RRdf+AhvD1W+Of7mnaPYXU0uZ8D5o1q3SpIWIStYQ0sHk+Ag=
X-Received: by 10.37.108.86 with SMTP id h83mr1937064ybc.211.1504577348505; Mon, 04 Sep 2017 19:09:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.2.148 with HTTP; Mon, 4 Sep 2017 19:09:08 -0700 (PDT)
Received: by 10.37.2.148 with HTTP; Mon, 4 Sep 2017 19:09:08 -0700 (PDT)
In-Reply-To: <CAKKJt-doFog1_LrDr6qTtUa3_wPAvVV888U-u392B7J+xsiLxA@mail.gmail.com>
References: <150423129417.4604.2689843099266054478@ietfa.amsl.com> <CE03DB3D7B45C245BCA0D243277949362FC30A29@MX307CL04.corp.emc.com> <6afe85ba-83c5-5945-fd37-dc313eb22162@gmail.com> <CAKKJt-doFog1_LrDr6qTtUa3_wPAvVV888U-u392B7J+xsiLxA@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 4 Sep 2017 21:09:08 -0500
Message-ID: <CAKKJt-f4MOqTy5bvm_O_4YCor8CiYeTFBW8qGi+2V1HiL3s=UA@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: "draft-ietf-tsvwg-ecn-experimentation.all@ietf.org" <draft-ietf-tsvwg-ecn-experimentation.all@ietf.org>,  "Black, David" <David.Black@dell.com>, "gen-art@ietf.org" <gen-art@ietf.org>,  "tsvwg@ietf.org" <tsvwg@ietf.org>
Content-Type: multipart/alternative; boundary="001a1148ac346517b7055867b6db"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/cQ_Rwqw_zFbG-kGUpCBFFa9twG0>
Subject: Re: [Gen-art] Genart telechat review of draft-ietf-tsvwg-ecn-experimentation-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Sep 2017 02:09:10 -0000

--001a1148ac346517b7055867b6db
Content-Type: text/plain; charset="UTF-8"

Just to end the suspense,

On Sep 2, 2017 13:37, "Spencer Dawkins at IETF" <
spencerdawkins.ietf@gmail.com> wrote:

Hi, Brian,

On Fri, Sep 1, 2017 at 6:41 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 02/09/2017 09:45, Black, David wrote:
> > Brian,
> >
> > Thanks for the prompt review.
> >
> >> Comment: Very clear from the technical standpoint.
> >
> > Thank you!
> >
> >> I understand the desire for brevity, but this bothers me a bit. What is
> >> the reader to make of RFC3168 Section 20.2, for example? My feeling is
> >> that a short Appendix outlining the specific updates would be useful.
> >> There's already too much spaghetti to untangle.
> >
> > RFC 3168 Section 20.2 is the rationale for the ECN Nonce and hence would
> be
> > deleted. Request noted, I'll consult with the draft shepherd and
> responsible
> > AD to figure out whether to do this.
>
> Thanks. It's not intended as a blocking issue.
>
> >
> >> I see no reason why RFC3540 and RFC5622 need to be normative references
> >> (and therefore downrefs). They aren't required reading in order to
> >> understand this draft.
> >
> > OTOH, both are affected by this draft:
> >
> > In reverse order, this draft updates RFC 5622 - that seems to merit a
> > normative reference.    This draft also provides the rationale for the
> > status change of RFC 3540 to Historic, which also seems to merit a
> > normative reference.
>
> Well, my understanding is that a normative reference is needed only
> when the citing document cannot be understood and implemented
> without reading the cited document.
>
> Again it's not a blocking comment - although there is a technical error
> in the Last Call message: it flags the downref to 5622, but not that to
> 3540.
> I don't know if that's a tool error or an AD error ;-).


As Bran is too polite to say, the AD sees the generated Last Call
announcement before it's sent.

I just regenerated the Last Call announcement, and it's still only naming
one draft as a normative downref. But the AD didn't notice that, so blaming
the tools was the wrong answer :-)

It's a 3-day weekend in the US, so any updated Last Call announcement won't
go out until Tuesday, anyway.

So, let's talk about that.

I just re-read the draft, focusing on the places where it refers to RFC
3540.

This draft explains the ECN Nonce experiment inline, although it cites 3540
as its reference, and explains that the experiment required ECT(0) and
ECT(1), but the experiment is over, and hasn't been deployed on the
Internet in any significant way, so we want ECT(1) back, for other
experiments.

It also refers to 3540 when it changes a registration in the Transmission
Control Protocol (TCP) Header Flags registry, but I believe this draft
explains the IANA actions requested well enough that IANA wouldn't need to
read 3540 to carry out the requested action.

I could be convinced that this draft explains why we want ECT(1) back well
enough that it's not necessary to actually read 3540, and since we're
declaring 3540 Historic, we actually kinda hope no one reads it in the
future except archaeologists in cyberspace.

But unless that reference really is informational, it remains a normative
downref that was omitted from the Last Call announcement.

David, I don't mind re-issuing the Last Call announcement if you think
still think the reference is normative, but you might want to take a look
at the text in the draft, and see how badly it needs to be normative,
before letting me know.

Spencer


Mirja and I talked this morning, and the score is

It's normative:2
It's informative:2

between me, Brian, David, and Mirja, so I took that as a sign that moving
that reference to Informative References isn't obviously ok.

I edited the Last Call text and re-issued the Last Call requests for both
the draft and the status change document, so they stay in sync.

The Secretariat was likely off today (US Labor Day), so it might take a day
for the Last Calls to pop out.

Thanks to everyone for your help.

Spencer

--001a1148ac346517b7055867b6db
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div>Just to end the suspense,<br><div class=3D"gmail_ext=
ra"><br><div class=3D"gmail_quote">On Sep 2, 2017 13:37, &quot;Spencer Dawk=
ins at IETF&quot; &lt;<a href=3D"mailto:spencerdawkins.ietf@gmail.com">spen=
cerdawkins.ietf@gmail.com</a>&gt; wrote:<br type=3D"attribution"><blockquot=
e class=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex"><div dir=3D"ltr">Hi, Brian,<div class=3D"gmail_extra"><br><d=
iv class=3D"gmail_quote"><div class=3D"elided-text">On Fri, Sep 1, 2017 at =
6:41 PM, Brian E Carpenter <span dir=3D"ltr">&lt;<a href=3D"mailto:brian.e.=
carpenter@gmail.com" target=3D"_blank">brian.e.carpenter@gmail.com</a>&gt;<=
/span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span cl=
ass=3D"m_8649521626021885577gmail-">On 02/09/2017 09:45, Black, David wrote=
:<br>
&gt; Brian,<br>
&gt;<br>
&gt; Thanks for the prompt review.<br>
&gt;<br>
&gt;&gt; Comment: Very clear from the technical standpoint.<br>
&gt;<br>
&gt; Thank you!<br>
&gt;<br>
&gt;&gt; I understand the desire for brevity, but this bothers me a bit. Wh=
at is<br>
&gt;&gt; the reader to make of RFC3168 Section 20.2, for example? My feelin=
g is<br>
&gt;&gt; that a short Appendix outlining the specific updates would be usef=
ul.<br>
&gt;&gt; There&#39;s already too much spaghetti to untangle.<br>
&gt;<br>
&gt; RFC 3168 Section 20.2 is the rationale for the ECN Nonce and hence wou=
ld be<br>
&gt; deleted. Request noted, I&#39;ll consult with the draft shepherd and r=
esponsible<br>
&gt; AD to figure out whether to do this.<br>
<br>
</span>Thanks. It&#39;s not intended as a blocking issue.<br>
<span class=3D"m_8649521626021885577gmail-"><br>
&gt;<br>
&gt;&gt; I see no reason why RFC3540 and RFC5622 need to be normative refer=
ences<br>
&gt;&gt; (and therefore downrefs). They aren&#39;t required reading in orde=
r to<br>
&gt;&gt; understand this draft.<br>
&gt;<br>
&gt; OTOH, both are affected by this draft:<br>
&gt;<br>
&gt; In reverse order, this draft updates RFC 5622 - that seems to merit a<=
br>
&gt; normative reference.=C2=A0 =C2=A0 This draft also provides the rationa=
le for the<br>
&gt; status change of RFC 3540 to Historic, which also seems to merit a<br>
&gt; normative reference.<br>
<br>
</span>Well, my understanding is that a normative reference is needed only<=
br>
when the citing document cannot be understood and implemented<br>
without reading the cited document.<br>
<br>
Again it&#39;s not a blocking comment - although there is a technical error=
<br>
in the Last Call message: it flags the downref to 5622, but not that to 354=
0.<br>
I don&#39;t know if that&#39;s a tool error or an AD error ;-).</blockquote=
><div><br></div></div><div>As Bran is too polite to say, the AD sees the ge=
nerated Last Call announcement before it&#39;s sent.=C2=A0</div><div><br></=
div><div>I just regenerated the Last Call announcement, and it&#39;s still =
only naming one draft as a normative downref. But the AD didn&#39;t notice =
that, so blaming the tools was the wrong answer :-)</div><div><br></div><di=
v>It&#39;s a 3-day weekend in the US, so any updated Last Call announcement=
 won&#39;t go out until Tuesday, anyway.=C2=A0</div><div><br></div><div>So,=
 let&#39;s talk about that.</div><div><br></div><div>I just re-read the dra=
ft, focusing on the places where it refers to RFC 3540.=C2=A0</div><div><br=
></div><div>This draft explains the ECN Nonce experiment inline, although i=
t cites 3540 as its reference, and explains that the experiment required EC=
T(0) and ECT(1), but the experiment is over, and hasn&#39;t been deployed o=
n the Internet in any significant way, so we want ECT(1) back, for other ex=
periments.</div><div><br></div><div>It also refers to 3540 when it changes =
a registration in the Transmission Control Protocol (TCP) Header Flags regi=
stry, but I believe this draft explains the IANA actions requested well eno=
ugh that IANA wouldn&#39;t need to read 3540 to carry out the requested act=
ion.=C2=A0</div><div><br></div><div>I could be convinced that this draft ex=
plains why we want ECT(1) back well enough that it&#39;s not necessary to a=
ctually read 3540, and since we&#39;re declaring 3540 Historic, we actually=
 kinda hope no one reads it in the future except archaeologists in cyberspa=
ce.</div><div><br></div><div>But unless that reference really is informatio=
nal, it remains a normative downref that was omitted from the Last Call ann=
ouncement.</div><div><br></div><div>David, I don&#39;t mind re-issuing the =
Last Call announcement if you think still think the reference is normative,=
 but you might want to take a look at the text in the draft, and see how ba=
dly it needs to be normative, before letting me know.</div><font color=3D"#=
888888"><div><br></div><div>Spencer</div></font></div></div></div>
</blockquote></div><br></div></div><div class=3D"gmail_extra" dir=3D"auto">=
Mirja and I talked this morning, and the score is=C2=A0</div><div class=3D"=
gmail_extra" dir=3D"auto"><br></div><div class=3D"gmail_extra" dir=3D"auto"=
>It&#39;s normative:2</div><div class=3D"gmail_extra" dir=3D"auto">It&#39;s=
 informative:2</div><div class=3D"gmail_extra" dir=3D"auto"><br></div><div =
class=3D"gmail_extra" dir=3D"auto">between me, Brian, David, and Mirja, so =
I took that as a sign that moving that reference to Informative References =
isn&#39;t obviously ok.</div><div class=3D"gmail_extra" dir=3D"auto"><br></=
div><div class=3D"gmail_extra" dir=3D"auto">I edited the Last Call text and=
 re-issued the Last Call requests for both the draft and the status change =
document, so they stay in sync.</div><div class=3D"gmail_extra" dir=3D"auto=
"><br></div><div class=3D"gmail_extra" dir=3D"auto">The Secretariat was lik=
ely off today (US Labor Day), so it might take a day for the Last Calls to =
pop out.</div><div class=3D"gmail_extra" dir=3D"auto"><br></div><div class=
=3D"gmail_extra" dir=3D"auto">Thanks to everyone for your help.</div><div c=
lass=3D"gmail_extra" dir=3D"auto"><br></div><div class=3D"gmail_extra" dir=
=3D"auto">Spencer</div></div>

--001a1148ac346517b7055867b6db--


From nobody Tue Sep  5 04:20:37 2017
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F276413293F; Tue,  5 Sep 2017 04:20:35 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Roni Even <ron.even.tlv@gmail.com>
To: <gen-art@ietf.org>
Cc: ietf@ietf.org, draft-ietf-taps-transports-usage.all@ietf.org, taps@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.59.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150461043596.28616.17788381104851881245@ietfa.amsl.com>
Date: Tue, 05 Sep 2017 04:20:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/9BY_S9U-bUiCfYix0l5nkW_FrCM>
Subject: [Gen-art] Genart telechat review of draft-ietf-taps-transports-usage-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Sep 2017 11:20:36 -0000

Reviewer: Roni Even
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-taps-transports-usage-??
Reviewer: Roni Even
Review Date: 2017-09-05
IETF LC End Date: 2017-09-14
IESG Telechat date: 2017-09-14

Summary: The document is ready with nits to be published as informational RFC

Major issues:

Minor issues:

Nits/editorial comments:
1. I think it will be better to have the introduction as section 1 and the
terminology as section 2 2.In section 3.1 in "open" I did not understand the
following sentence "more than TCP's maximum segment size (minus options used in
the SYN)" 3. in section 6 "The views expressed are solely those of the
author(s)" suggest removing the sentence since this document expresses the
views of the WG. 4. A general readability comment when describing primitives in
pass 2 the structure is
               PRIMITIVENAME.PROTOCOL:
                              Pass 1 primitive / event:
                               Parameters:
                                Returns:
                                Comments:
but it will be easier to read if there is for example a line space between the
paragraphs. look for example at CONNECT.TCP: it is difficult to see where
parameters finish and comment starts



From nobody Thu Sep  7 08:51:31 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E55AD132F84; Thu,  7 Sep 2017 08:51:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.878
X-Spam-Level: 
X-Spam-Status: No, score=-1.878 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 eALaR1njMpz2; Thu,  7 Sep 2017 08:51:26 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EDA813219F; Thu,  7 Sep 2017 08:51:25 -0700 (PDT)
Received: from unescapeable.local ([47.186.15.50]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v87FpKXH044717 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 7 Sep 2017 10:51:21 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [47.186.15.50] claimed to be unescapeable.local
To: Eliot Lear <lear@cisco.com>, gen-art@ietf.org
Cc: draft-ietf-opsawg-mud.all@ietf.org, opsawg@ietf.org, ietf@ietf.org
References: <150411366399.21627.17047458871931107094@ietfa.amsl.com> <0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <3570a07d-6786-3077-f1a7-4ec61a4bf9d0@nostrum.com>
Date: Thu, 7 Sep 2017 10:51:20 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com>
Content-Type: multipart/alternative; boundary="------------35768AF4B247EF2DF66EB037"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/3ucpk0B3iSbAnSs5li81Ag4JWOk>
Subject: Re: [Gen-art] Genart early review of draft-ietf-opsawg-mud-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 15:51:30 -0000

This is a multi-part message in MIME format.
--------------35768AF4B247EF2DF66EB037
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Apologies for being a little laggy -

Some comments inline.


On 8/31/17 2:07 PM, Eliot Lear wrote:
>
> Robert,
>
> As I wrote earlier, this was a great review.Â  Thanks for that. Please 
> see below.
>
>
> On 8/30/17 7:21 PM, Robert Sparks wrote:
>> Reviewer: Robert Sparks
>> Review result: Almost Ready
>>
>> This is an exciting concept, and the draft overall is approachable. I
>> have identified a few areas I think need more detail, and have a
>> longish list of nits (please don't take that to be negative).
>>
>> ==Issues==
>>
>> I find the structure of the introduction unclear. Please consider
>> reworking it.  I would suggest even more succinctly listing goals and
>> constraints, and then intended applicability (these things are in the
>> current text, but I think you can render them much more efficiently). In
>> particular, the argument that implementers of things are incented only to
>> provide the minimal amount of behavior to get their thingyness could be
>> more strongly highlighted.
>
> I've received conflicting reviews here.Â  Most like what's there and 
> while I'm open to specific textual changes, a full reorganization 
> would likely be destabilizing.
I disagree. I know it's work, but if you read this as an implementer, I 
think it would pay back.
This is a stylistic suggestion though, so take it only as my opinion.
>
>> The document proposes "reputation services". It needs more words about
>> whether those exist, and what scopes the architecture imagines (an
>> enterprise might have a different idea of a reputation service than a
>> residence). There is a notion of "decent web reputations" in the security
>> considerations section. Who determines that? The security considerations
>> section should talk about attacks against the reputation services.
>
> This is discussed in security considerations:
>> It may also be useful
>> to limit retrieval of MUD URLs to only those sites that are known to
>> have decent web reputations.
> What I am specifically talking about are web or domain reputation 
> services.Â  These are pretty commonplace today.Â  Your browser uses one, 
> and numerous companies offer them, including our own.Â  But to be 
> clearer, I propose to use the term "web or domain reputation 
> services", so that people know what I'm talking about.
I'll look at the diff.
>
>
>
>
>> In the first paragraph of Section 2, it's not clear if you are trying
>> to restrict the models to only those in the two documents in the list
>> following the paragraph.
>
> Right.Â  This was caught earlier, and I'll correct.
>
>> I am not a YANG doctor, so this may be in the weeds, but it feels like
>> there's a discrepancy between the diagram at the end of section 2 and the
>> element definitions in section 3. In particular 3.7 doesn't seem to align
>> with what the diagram or the example in Appendix B uses. Should you be
>> defining "from-device-policy" and "to-device-policy" instead of
>> "packet-direction"? (I'm wondering if 3.7 reflects an older design?)
>
> Yupper.Â  Fixed (I think).
>> At section 3.13, the description of my-controller is not quite right.
>> This bit signals to the mud controller to use a mapping that it knows
>> about or creates. Something else established that class (and maybe gave
>> it a name). I talked about this with Eliot and he has a better
>> description to use.
>
> Proposed text:
>
>> This null-valued node signals to the MUD controller to use whatever
>> mapping it has for this URL to a controller class".Â  This may require
>> prompting the administrator for class members.Â  Future work should
>> seek to automate membership management.
ack
>
>> It's not clear to me that this is a good use of .well-known. I suggest
>> getting an expert review on the proposed usage. (I had a quick
>> conversation with Mark Nottingham and got some initial feedback that
>> I'm passing along here. I'm sure there's more that an in-depth review
>> would identify.) Why wouldn't a URI template (RFC6570) do the job?
>> Rather than use RFC3986's query, consider pointing to HTML5 (which
>> would bring the more familiar key=value format).
>
> The key issue is that we want to externalize versioning AND hardcode 
> it in the URL so that it's independent of transport. Remember, there 
> is very little information exchange between the Thing and the network, 
> and I will claim that's a good thing.
Sure, and URL templates would _do_ that, no? But please take that 
argument up with folks like Mark.
>
>> The document needs to say more about how HTTP is used. I assume you only
>> intend to use GET, and that you expect redirects to be followed, and that
>> nothing special needs to be considered with caching? The document needs
>> to be explicit about it. Take a look at
>> <https://mnot.github.io/I-D/bcp56bis/>. (There's been some conversation
>> about it on the art list, so Eliot, at least, is already aware of it -
>> see<https://mailarchive.ietf.org/arch/search/?q=bcp56bis>)
>
> What we say today is the following;
>> Processing of this
>> URL occurs as specified in {{RFC2818}} and {{RFC3986}}.
> There is one aspect of caching semantics we should probably capture, 
> which is that the cache-validity period should exceed the HTTP cache 
> or expiry period as specified by max-age or Expires. Does that sound 
> about right to you?
Goes in the right direction. Do you expect POST to work with this?
>
>> I think there needs to be more discussion of the PKI used for signing MUD
>> files.
>
> We do have some discussion in Section 12.2.Â  I'm happy to add an 
> additional sentence or two, but would seek guidance on where you think 
> we're missing.
So, are you expecting to reuse the web PKI here? Will the MUD files be 
signed with the same credentials used by the HTTP server? I'm thinking 
you aren't, and are waving your hands at where trust lies with the 
recommendation that signers be validated directly etc. Either way, I 
think you need to be more explicit and that what you expect for 
establishing trust is going to take more than a couple of sentences.
>
>> Consider discussing whether the stacks used by typical things will let
>> them add DHCP options (or include bits in the other protocols being
>> enabled). If it's well known (I can't say) that these stacks typically
>> _won't_ provide that functionality, then you should punch up the
>> discussion of the controllers mapping other identifiers to MUD URLs on
>> behalf of the thing.
>
> I agree.Â  We allude to this in the draft.Â  We say, for instance:
>> It is possible that there may be other means for a MUD URL to be
>> learned by a network.Â  For instance, if a device has a serial number,
>> it may be possible for the MUD controller to perform a lookup of the
>> device, if it has some knowledge as to who the device manufacturer
>> is, and what its MUD file server is.Â  Such mechanisms are not
>> described in this memo, but are possible.
>
> The case we have in mind is LoRaWAN.Â  Should we go further?
I think explicitly acknowledging that some things stacks limit their 
behavior will pay back. It would be unfortunate if someone who started a 
MUD controller implementation made the assumption that the majority of 
things will hand them the DHCP option (etc.) and waited to bolt the 
complexity of the lookup above onto their initial design.
>
>
>> You suggest the DHCP Client (which is a thing) SHOULD log or report
>> improper acknowledgments from servers. That's asking a bit much from
>> a thing. I suspect the requirement is unrealistic and should be removed
>> or rewritten to acknowledge that things typically won't do that.
> I think there's a philosophical thing hiding here, though: what 
> expectations should we have of device.Â  As a SHOULD we're saying, if 
> you have good cause not to, ok.Â  But otherwise, for the sake of the 
> sanity of the customer, please log.
Why not acknowledge in the document that the expectation is that most 
won't be able to.
Painting as explicit and accurate picture as possible can only do good, no?
(Again, I'm not trying to _assert_ that the majority of things can't, 
but that's my suspicion. People who work with this things on a daily 
basis should weigh in.)
>
>> The security and deployment considerations sections talk about what the
>> need for coordination if control over the domain name used in the URL
>> changes. It should talk more about what happens if the new administration
>> of the domain is not interested in facilitating a transition (consider
>> the case of a young company with a few thousand start-up-ish things out
>> there that loses a suit over its name). Please discuss whether or not
>> suddenly losing the MUD assisted network configuration is expected to
>> leave the devices effectively cut-off.
>
> It should not, and here's why:
>
>   * Assuming the device has already been used, there is no reason to
>     simply delete the MUD file from one's cache.Â  The cache-validity
>     value is meant as a timer to keep implementations for harassing
>     the MUD file server, but there's the information is still useful,
>     even if it may not have been freshened.
>
Hrmm - there should be some description about using the information even 
if the cache has expired. That might have security ramifications (it at 
least enables an attacker to cause a set of devices to use old 
information by attacking the access to what might be newer information).
>
>   * In the case where the MUD file service is unavailable when the
>     device is first turned up, it's as if it had not included a
>     MUD-URL in the first place.Â  While this may be a downgrade attack,
>     there is, as I understand it, really no way to get around it,
>     other than for the MUD controller to log a problem.
>
Worth a short discussion in the text.
>
>  *
>
>
>> Right now, you leave the DHCP server (when it's used) responsible for
>> clearing state in the MUD controller. Please discuss what happens when
>> those are distinct elements (as you have in the end of section 9.2) and
>> the DHCP server reboots. Perhaps it would make sense for the DHCP server
>> to hand the length of the lease it has granted to the MUD controller and
>> let the MUD controller clean up on its own?
>
> See other response.
>
>> The document currently suggests that a piece of software inspect the
>> WHOIS database to see if registration ownership of a domain has changed.
>> Do you really mean software, or should this be advice to the
>> administrator of the controller instead?
>
> The controller.Â  The idea is to catch bad behavior and anomalies. And 
> the bigger idea is to reduce the number of decisions that the 
> administrator must make, while providing relevant information with 
> which to make the decisions.
I don't think this is a reasonable thing to do. It has the many of the 
same properties we complain about when someone suggest that code inspect 
an IANA registry.
>
>> ==Nits==
>>
>> I recommend an editorial pass focusing on simplifying sentences. Look
>> particularly where the word "therefore" is used and consider
>> restructuring the surrounds. (It is used non-sequitur in a couple of
>> places). Be careful to call out actors explicitly (I note the places
>> that particularly caught my eye below).
>
> ok.
>> Some specific nits:
>>
>> The abstract speaks only about properties of MUD but does not describe
>> what MUD _is_, or is good for. A few more words here would help.
> Right.Â  See response to Henk.
>> Next to last paragraph of section 1 (before 1.1): A means for _who_ to
>> retrieve the description? (Consider rendering the three list elements on
>> their own lines.)
> Right.Â  Fixed.
>> The last sentence of section 1 treats "enterprise networks" more
>> specially than it intends, I think. Why couldn't _any_ network do this?
>> Could the sentence be reworded to make it clear that enterprise networks
>> are an example?
>
> s/enterprise networks/local deployments/
>
> ?
Sure
>
>> First sentence of 1.1: Perhaps you mean "general purpose computing
>> devices" instead of "general computing"? "their" has an unclear
>> antecedent.
>
> Indeed.Â  fixed.
>
>> Last paragraph of 1.3: It's unclear what "such an approach" is intended
>> to point to. Would "a general solution that required capabilities their
>> particular device would not use" make more sense?
>
> Reworded.
>
>> First paragraph of 1.5: "might to allow" is probably meant to be "might
>> be to allow". What does it mean for a controller to "need to speak COAP".
>> Do you mean "controllers capable of speaking COAP"?
> Fixed.
>> Fourth paragraph of 1.5 at the discussion of time and effort: Consider
>> rephrasing this to focus on the result of the time and effort (high
>> quality) rather than the time and effort itself.
>
> Existence is good enough in this case ;-)
>
>> In the list of abstractions at the end of 1.5, you have three things you
>> describe as devices and one thing you describe as a class. You later talk
>> about the abstractions you've described as devices as classes. At this
>> point in the document what you mean by "class" has not been made as
>> explicit as it could be.
> I've tried to review all instances of class to be clear that it is 
> used consistently.Â  This is somewhat difficult given natural language, 
> but I hope I've gotten it right.
>
>> Section 1.8, item 3: the MUD file doesn't have hosts in it (it has
>> identifiers of some kind). Consider being more explicit about what
>> you mean by testing that against a reputation service.
>
> Actually, it can have hosts in it, but see above.
>
>> Section 3.1: You say "Which turn was taken". I think you meant
>> "Which, in turn, was taken". Consider deleting "for those keeping score".
>
> Awwww.Â  Just a bit of humor? ;-)
>
>> Section 3.3 is missing a word at "the location any MASA service"?
>
> Ok it's cleaned up.
>
>> I found the prose in the descriptions of the "manufacturer" and
>> "same-manufacturer" elements (3.8 and 3.9) very confusing. I think
>> additional prose introducing the concepts and maybe some examples would
>> be very useful.
>
> Added examples per your suggestion.
>
>> What do you mean by "matches" at 3.10. Do you mean "is"?
>
> All of this is applicable in the context of the matches statement in 
> the ACL model.Â  I've added some explanatory text at the beginning of 
> the chapeau.
>> The caution in the 2nd paragraph of 3.12 is not clear.
>
> Ok, I've cleaned that up and added an example.
>
>> At section 4, consider pointing out that you are not allowing
>> DHCP by default, and that devices that are expected to use DHCP
>> need to have an explicit allow in their MUD file.
>
> Hmm.Â  The issue here is that DHCP is an L2 protocol that isn't 
> forwarded.Â  Do you think it needs to be listed anyway?
Hmm indeed. You're right. That said, the thing that triggered the thought
was the ability of a MUD file to say whether or not something can talk to
other things in the local network. Maybe some reinforcement in the 
discussion
about what that rule would expand to would prevent someone from walling
off the device more than you intended (it would be a creative mistake to 
do so,
I agree)
>
>> The description of the manufacturer leaf in the MUD YANG model
>> could be made more useful.
>
> ALL the descriptions have been improved.
>> Provide a reference for "giaddr" when you use it in section 9.2.
>
> Cleaned up (that's defined in RFC 2131, already normatively 
> referenced, but I expanded).
>> Section 14, 2nd paragraph: additional segmentation of what?
>
> Make that "network segmentation".
>> Second paragraph of Section 15 - it would help to be more precise
>> with agency. _Who_ should review the class?
>
> Fixed.
>
>> In the security considerations section, when you get to the "if for some
>> reason it is not possible to determine whether ownership has changed",
>> _who_ are you suggesting conduct further review?
>
> It's always the network administrator.
>> ==Micro-nits==
>>
>> 1,$s/enorcement/enforcement/g
>
> Doh!
>
>> s/autjors/authors/
>>
>
> Fixed.
>
> Thanks again,
>
> Eliot
>


--------------35768AF4B247EF2DF66EB037
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Apologies for being a little laggy -<br>
    </p>
    <p>Some comments inline.<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 8/31/17 2:07 PM, Eliot Lear wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <p>Robert,</p>
      <p>As I wrote earlier, this was a great review.Â  Thanks for that.Â 
        Please see below.</p>
      <br>
      <div class="moz-cite-prefix">On 8/30/17 7:21 PM, Robert Sparks
        wrote:<br>
      </div>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">Reviewer: Robert Sparks
Review result: Almost Ready

This is an exciting concept, and the draft overall is approachable. I
have identified a few areas I think need more detail, and have a 
longish list of nits (please don't take that to be negative).

==Issues==

I find the structure of the introduction unclear. Please consider
reworking it.  I would suggest even more succinctly listing goals and
constraints, and then intended applicability (these things are in the
current text, but I think you can render them much more efficiently). In
particular, the argument that implementers of things are incented only to
provide the minimal amount of behavior to get their thingyness could be
more strongly highlighted.</pre>
      </blockquote>
      <br>
      I've received conflicting reviews here.Â  Most like what's there
      and while I'm open to specific textual changes, a full
      reorganization would likely be destabilizing.<br>
    </blockquote>
    I disagree. I know it's work, but if you read this as an
    implementer, I think it would pay back.<br>
    This is a stylistic suggestion though, so take it only as my
    opinion.<br>
    <blockquote type="cite"
      cite="mid:0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com"> <br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">The document proposes "reputation services". It needs more words about
whether those exist, and what scopes the architecture imagines (an
enterprise might have a different idea of a reputation service than a
residence). There is a notion of "decent web reputations" in the security
considerations section. Who determines that? The security considerations
section should talk about attacks against the reputation services.</pre>
      </blockquote>
      <br>
      This is discussed in security considerations:<br>
      <blockquote type="cite">It may also be useful<br>
        to limit retrieval of MUD URLs to only those sites that are
        known to<br>
        have decent web reputations.<br>
      </blockquote>
      What I am specifically talking about are web or domain reputation
      services.Â  These are pretty commonplace today.Â  Your browser uses
      one, and numerous companies offer them, including our own.Â  But to
      be clearer, I propose to use the term "web or domain reputation
      services", so that people know what I'm talking about.<br>
    </blockquote>
    I'll look at the diff.<br>
    <blockquote type="cite"
      cite="mid:0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com"> <br>
      <br>
      <br>
      <br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">In the first paragraph of Section 2, it's not clear if you are trying
to restrict the models to only those in the two documents in the list
following the paragraph. </pre>
      </blockquote>
      <br>
      Right.Â  This was caught earlier, and I'll correct.<br>
      <br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">I am not a YANG doctor, so this may be in the weeds, but it feels like
there's a discrepancy between the diagram at the end of section 2 and the
element definitions in section 3. In particular 3.7 doesn't seem to align
with what the diagram or the example in Appendix B uses. Should you be 
defining "from-device-policy" and "to-device-policy" instead of
"packet-direction"? (I'm wondering if 3.7 reflects an older design?)</pre>
      </blockquote>
      <br>
      Yupper.Â  Fixed (I think).<br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">At section 3.13, the description of my-controller is not quite right.
This bit signals to the mud controller to use a mapping that it knows
about or creates. Something else established that class (and maybe gave
it a name). I talked about this with Eliot and he has a better 
description to use.</pre>
      </blockquote>
      <br>
      Proposed text:<br>
      <br>
      <blockquote type="cite">This null-valued node signals to the MUD
        controller to use whatever<br>
        mapping it has for this URL to a controller class".Â  This may
        require<br>
        prompting the administrator for class members.Â  Future work
        should<br>
        seek to automate membership management.</blockquote>
    </blockquote>
    ack<br>
    <blockquote type="cite"
      cite="mid:0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com"> <br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">It's not clear to me that this is a good use of .well-known. I suggest
getting an expert review on the proposed usage. (I had a quick 
conversation with Mark Nottingham and got some initial feedback that 
I'm passing along here. I'm sure there's more that an in-depth review
would identify.) Why wouldn't a URI template (RFC6570) do the job? 
Rather than use RFC3986's query, consider pointing to HTML5 (which
would bring the more familiar key=value format). </pre>
      </blockquote>
      <br>
      The key issue is that we want to externalize versioning AND
      hardcode it in the URL so that it's independent of transport.Â 
      Remember, there is very little information exchange between the
      Thing and the network, and I will claim that's a good thing.<br>
    </blockquote>
    Sure, and URL templates would _do_ that, no? But please take that
    argument up with folks like Mark.<br>
    <blockquote type="cite"
      cite="mid:0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com"> <br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">The document needs to say more about how HTTP is used. I assume you only
intend to use GET, and that you expect redirects to be followed, and that
nothing special needs to be considered with caching? The document needs
to be explicit about it. Take a look at 
<a class="moz-txt-link-rfc2396E" href="https://mnot.github.io/I-D/bcp56bis/" moz-do-not-send="true">&lt;https://mnot.github.io/I-D/bcp56bis/&gt;</a>. (There's been some conversation
about it on the art list, so Eliot, at least, is already aware of it - 
see <a class="moz-txt-link-rfc2396E" href="https://mailarchive.ietf.org/arch/search/?q=bcp56bis" moz-do-not-send="true">&lt;https://mailarchive.ietf.org/arch/search/?q=bcp56bis&gt;</a>)</pre>
      </blockquote>
      <br>
      What we say today is the following;<br>
      <blockquote type="cite">Processing of this<br>
        URL occurs as specified in {{RFC2818}} and {{RFC3986}}.</blockquote>
      There is one aspect of caching semantics we should probably
      capture, which is that the cache-validity period should exceed the
      HTTP cache or expiry period as specified by max-age or Expires.Â 
      Does that sound about right to you?<br>
    </blockquote>
    Goes in the right direction. Do you expect POST to work with this? <br>
    <blockquote type="cite"
      cite="mid:0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com"> <br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">I think there needs to be more discussion of the PKI used for signing MUD
files.</pre>
      </blockquote>
      <br>
      We do have some discussion in Section 12.2.Â  I'm happy to add an
      additional sentence or two, but would seek guidance on where you
      think we're missing.<br>
    </blockquote>
    So, are you expecting to reuse the web PKI here? Will the MUD files
    be signed with the same credentials used by the HTTP server? I'm
    thinking you aren't, and are waving your hands at where trust lies
    with the recommendation that signers be validated directly etc.
    Either way, I think you need to be more explicit and that what you
    expect for establishing trust is going to take more than a couple of
    sentences.<br>
    <blockquote type="cite"
      cite="mid:0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com"> <br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">Consider discussing whether the stacks used by typical things will let
them add DHCP options (or include bits in the other protocols being 
enabled). If it's well known (I can't say) that these stacks typically
_won't_ provide that functionality, then you should punch up the
discussion of the controllers mapping other identifiers to MUD URLs on
behalf of the thing.</pre>
      </blockquote>
      <br>
      I agree.Â  We allude to this in the draft.Â  We say, for instance:<br>
      <blockquote type="cite">It is possible that there may be other
        means for a MUD URL to be<br>
        learned by a network.Â  For instance, if a device has a serial
        number,<br>
        it may be possible for the MUD controller to perform a lookup of
        the<br>
        device, if it has some knowledge as to who the device
        manufacturer<br>
        is, and what its MUD file server is.Â  Such mechanisms are not<br>
        described in this memo, but are possible.<br>
      </blockquote>
      <br>
      The case we have in mind is LoRaWAN.Â  Should we go further?<br>
    </blockquote>
    I think explicitly acknowledging that some things stacks limit their
    behavior will pay back. It would be unfortunate if someone who
    started a MUD controller implementation made the assumption that the
    majority of things will hand them the DHCP option (etc.) and waited
    to bolt the complexity of the lookup above onto their initial
    design.<br>
    <blockquote type="cite"
      cite="mid:0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com"> <br>
      <br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">You suggest the DHCP Client (which is a thing) SHOULD log or report 
improper acknowledgments from servers. That's asking a bit much from
a thing. I suspect the requirement is unrealistic and should be removed
or rewritten to acknowledge that things typically won't do that.</pre>
      </blockquote>
      I think there's a philosophical thing hiding here, though: what
      expectations should we have of device.Â  As a SHOULD we're saying,
      if you have good cause not to, ok.Â  But otherwise, for the sake of
      the sanity of the customer, please log.<br>
    </blockquote>
    Why not acknowledge in the document that the expectation is that
    most won't be able to.<br>
    Painting as explicit and accurate picture as possible can only do
    good, no?<br>
    (Again, I'm not trying to _assert_ that the majority of things
    can't, but that's my suspicion. People who work with this things on
    a daily basis should weigh in.)<br>
    <blockquote type="cite"
      cite="mid:0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com"> <br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">The security and deployment considerations sections talk about what the
need for coordination if control over the domain name used in the URL
changes. It should talk more about what happens if the new administration
of the domain is not interested in facilitating a transition (consider
the case of a young company with a few thousand start-up-ish things out
there that loses a suit over its name). Please discuss whether or not
suddenly losing the MUD assisted network configuration is expected to
leave the devices effectively cut-off. </pre>
      </blockquote>
      <br>
      It should not, and here's why:<br>
      <br>
      <ul>
        <li>Assuming the device has already been used, there is no
          reason to simply delete the MUD file from one's cache.Â  The
          cache-validity value is meant as a timer to keep
          implementations for harassing the MUD file server, but there's
          the information is still useful, even if it may not have been
          freshened.</li>
      </ul>
    </blockquote>
    Hrmm - there should be some description about using the information
    even if the cache has expired. That might have security
    ramifications (it at least enables an attacker to cause a set of
    devices to use old information by attacking the access to what might
    be newer information).<br>
    <blockquote type="cite"
      cite="mid:0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com">
      <ul>
        <li>In the case where the MUD file service is unavailable when
          the device is first turned up, it's as if it had not included
          a MUD-URL in the first place.Â  While this may be a downgrade
          attack, there is, as I understand it, really no way to get
          around it, other than for the MUD controller to log a problem.<br>
        </li>
      </ul>
    </blockquote>
    Worth a short discussion in the text.<br>
    <blockquote type="cite"
      cite="mid:0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com">
      <ul>
        <li> <br>
        </li>
      </ul>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">Right now, you leave the DHCP server (when it's used) responsible for
clearing state in the MUD controller. Please discuss what happens when
those are distinct elements (as you have in the end of section 9.2) and
the DHCP server reboots. Perhaps it would make sense for the DHCP server
to hand the length of the lease it has granted to the MUD controller and
let the MUD controller clean up on its own?</pre>
      </blockquote>
      <br>
      See other response.<br>
      <br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">The document currently suggests that a piece of software inspect the
WHOIS database to see if registration ownership of a domain has changed.
Do you really mean software, or should this be advice to the
administrator of the controller instead? </pre>
      </blockquote>
      <br>
      The controller.Â  The idea is to catch bad behavior and anomalies.Â 
      And the bigger idea is to reduce the number of decisions that the
      administrator must make, while providing relevant information with
      which to make the decisions.<br>
    </blockquote>
    I don't think this is a reasonable thing to do. It has the many of
    the same properties we complain about when someone suggest that code
    inspect an IANA registry.<br>
    <blockquote type="cite"
      cite="mid:0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com"> <br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">==Nits==

I recommend an editorial pass focusing on simplifying sentences. Look
particularly where the word "therefore" is used and consider
restructuring the surrounds. (It is used non-sequitur in a couple of
places). Be careful to call out actors explicitly (I note the places 
that particularly caught my eye below).</pre>
      </blockquote>
      <br>
      ok.<br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">Some specific nits:

The abstract speaks only about properties of MUD but does not describe
what MUD _is_, or is good for. A few more words here would help.</pre>
      </blockquote>
      Right.Â  See response to Henk.<br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">Next to last paragraph of section 1 (before 1.1): A means for _who_ to
retrieve the description? (Consider rendering the three list elements on
their own lines.)</pre>
      </blockquote>
      Right.Â  Fixed.<br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">The last sentence of section 1 treats "enterprise networks" more
specially than it intends, I think. Why couldn't _any_ network do this?
Could the sentence be reworded to make it clear that enterprise networks
are an example?</pre>
      </blockquote>
      <br>
      s/enterprise networks/local deployments/<br>
      <br>
      ?<br>
    </blockquote>
    Sure<br>
    <blockquote type="cite"
      cite="mid:0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com"> <br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">First sentence of 1.1: Perhaps you mean "general purpose computing
devices" instead of "general computing"? "their" has an unclear
antecedent.</pre>
      </blockquote>
      <br>
      Indeed.Â  fixed.<br>
      <br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">Last paragraph of 1.3: It's unclear what "such an approach" is intended
to point to. Would "a general solution that required capabilities their
particular device would not use" make more sense?</pre>
      </blockquote>
      <br>
      Reworded.<br>
      <br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">First paragraph of 1.5: "might to allow" is probably meant to be "might
be to allow". What does it mean for a controller to "need to speak COAP".
Do you mean "controllers capable of speaking COAP"?
</pre>
      </blockquote>
      Fixed.<br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">Fourth paragraph of 1.5 at the discussion of time and effort: Consider
rephrasing this to focus on the result of the time and effort (high
quality) rather than the time and effort itself.</pre>
      </blockquote>
      <br>
      Existence is good enough in this case ;-)<br>
      <br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">In the list of abstractions at the end of 1.5, you have three things you
describe as devices and one thing you describe as a class. You later talk
about the abstractions you've described as devices as classes. At this
point in the document what you mean by "class" has not been made as
explicit as it could be.</pre>
      </blockquote>
      I've tried to review all instances of class to be clear that it is
      used consistently.Â  This is somewhat difficult given natural
      language, but I hope I've gotten it right.<br>
      <br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">
Section 1.8, item 3: the MUD file doesn't have hosts in it (it has
identifiers of some kind). Consider being more explicit about what
you mean by testing that against a reputation service.</pre>
      </blockquote>
      <br>
      Actually, it can have hosts in it, but see above.<br>
      <br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">Section 3.1: You say "Which turn was taken". I think you meant
"Which, in turn, was taken". Consider deleting "for those keeping score".</pre>
      </blockquote>
      <br>
      Awwww.Â  Just a bit of humor? ;-)<br>
      <br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">
Section 3.3 is missing a word at "the location any MASA service"?</pre>
      </blockquote>
      <br>
      Ok it's cleaned up.<br>
      <br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">
I found the prose in the descriptions of the "manufacturer" and
"same-manufacturer" elements (3.8 and 3.9) very confusing. I think
additional prose introducing the concepts and maybe some examples would
be very useful.</pre>
      </blockquote>
      <br>
      Added examples per your suggestion.<br>
      <br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">
What do you mean by "matches" at 3.10. Do you mean "is"?</pre>
      </blockquote>
      <br>
      All of this is applicable in the context of the matches statement
      in the ACL model.Â  I've added some explanatory text at the
      beginning of the chapeau.<br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">
The caution in the 2nd paragraph of 3.12 is not clear.</pre>
      </blockquote>
      <br>
      Ok, I've cleaned that up and added an example.<br>
      <br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">
At section 4, consider pointing out that you are not allowing 
DHCP by default, and that devices that are expected to use DHCP
need to have an explicit allow in their MUD file. </pre>
      </blockquote>
      <br>
      Hmm.Â  The issue here is that DHCP is an L2 protocol that isn't
      forwarded.Â  Do you think it needs to be listed anyway?</blockquote>
    Hmm indeed. You're right. That said, the thing that triggered the
    thought<br>
    was the ability of a MUD file to say whether or not something can
    talk to<br>
    other things in the local network. Maybe some reinforcement in the
    discussion<br>
    about what that rule would expand to would prevent someone from
    walling<br>
    off the device more than you intended (it would be a creative
    mistake to do so,<br>
    I agree)<br>
    <blockquote type="cite"
      cite="mid:0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com"> <br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">
The description of the manufacturer leaf in the MUD YANG model
could be made more useful.</pre>
      </blockquote>
      <br>
      ALL the descriptions have been improved.<br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">
Provide a reference for "giaddr" when you use it in section 9.2.</pre>
      </blockquote>
      <br>
      Cleaned up (that's defined in RFC 2131, already normatively
      referenced, but I expanded).<br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">
Section 14, 2nd paragraph: additional segmentation of what?</pre>
      </blockquote>
      <br>
      Make that "network segmentation".<br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">
Second paragraph of Section 15 - it would help to be more precise
with agency. _Who_ should review the class?</pre>
      </blockquote>
      <br>
      Fixed.<br>
      <br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">
In the security considerations section, when you get to the "if for some
reason it is not possible to determine whether ownership has changed",
_who_ are you suggesting conduct further review?</pre>
      </blockquote>
      <br>
      It's always the network administrator.<br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">
==Micro-nits==

1,$s/enorcement/enforcement/g</pre>
      </blockquote>
      <br>
      Doh!<br>
      <br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
        <pre wrap="">
s/autjors/authors/

</pre>
      </blockquote>
      <br>
      Fixed.<br>
      <br>
      Thanks again,<br>
      <br>
      Eliot<br>
      <blockquote type="cite"
        cite="mid:150411366399.21627.17047458871931107094@ietfa.amsl.com">
      </blockquote>
      <br>
    </blockquote>
    <br>
  </body>
</html>

--------------35768AF4B247EF2DF66EB037--


From nobody Thu Sep  7 14:51:50 2017
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 837CD132C49 for <gen-art@ietf.org>; Thu,  7 Sep 2017 14:51:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jean Mahoney <mahoney@nostrum.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.60.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-to: mahoney@nostrum.com
Message-ID: <150482110953.7921.9518046336396099581.idtracker@ietfa.amsl.com>
Date: Thu, 07 Sep 2017 14:51:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/pRH3zT4FhFh6xzXNeR9Gewj4nC0>
Subject: [Gen-art] Review Assignments
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 21:51:49 -0000

Hi all,

The following reviewers have assignments:

For telechat 2017-09-14

Reviewer               Type      LC end     Draft
Francis Dupont         Telechat  2017-09-14 draft-ietf-taps-transports-usage-udp-06
Matthew Miller         Telechat  2017-07-30 draft-ietf-curdle-ssh-ext-info-12 *
Matthew Miller         Last Call 2017-08-28 draft-ietf-rmcat-coupled-cc-06
Dale Worley            Telechat  2017-08-09 draft-ietf-bess-evpn-etree-13 *

Last calls:

Reviewer               Type      LC end     Draft
Jari Arkko             Last Call 2017-09-13 draft-ietf-dcrup-dkim-usage-04
Stewart Bryant         Last Call 2017-09-27 draft-kille-ldap-xmpp-schema-01
Fernando Gont          Last Call 2017-08-24 draft-ietf-pals-p2mp-pw-03
Paul Kyzivat           Last Call 2017-09-14 draft-spinosa-urn-lex-11
Orit Levin             Last Call None       draft-ietf-v6ops-rfc6555bis-04
Meral Shirazipour      Last Call 2017-09-15 draft-ietf-6man-maxra-03
Robert Sparks          Last Call 2017-09-20 draft-ietf-opsawg-service-model-explained-03

* Other revision previously reviewed
** This revision already reviewed

Next in the reviewer rotation:

  Jari Arkko
  Stewart Bryant
  Brian Carpenter
  Elwyn Davies
  Linda Dunbar
  Francis Dupont
  Roni Even
  Fernando Gont
  Vijay Gurbani
  Wassim Haddad

The LC and Telechat review templates are included below:
-------------------------------------------------------

-- Begin LC Template --
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments: 

-- End LC Template --

-- Begin Telechat Template --
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

-- End Telechat Template --



From nobody Thu Sep  7 23:25:20 2017
Return-Path: <lear@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A1CA132D90; Thu,  7 Sep 2017 23:25:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level: 
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 WLtZAblJOb-l; Thu,  7 Sep 2017 23:25:10 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C22A81321ED; Thu,  7 Sep 2017 23:25:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=28232; q=dns/txt; s=iport; t=1504851909; x=1506061509; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=Gu73CRtWTElK6P8KDGN/nNhChMwwGigOIdoI/bGpUsA=; b=AyMte3A6OpwhXhuEW0mIIt8loaH3GVc1L+62UDbiVIvKHOdzL0SkmSEz 5fMufTq9WdcY/4rCm3VwvdhBCWRii4cGMxbMS98FaaIb/5cjkKIoYZcNI JVBiG1PaUuU21k5cvH8WXEHwdq/Z/pIZ8FLV6vXpIO7cKv2QCcd1DT9Xj k=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DyBAA7N7JZ/xbLJq1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgy2BEW6EHosVkHMJIpY2ggQHA4IDgzsChEYUAQIBAQEBAQEBayiFGQE?= =?us-ascii?q?EASNPBwULCw40AgJXBgEMCAEBiiUIqn6CJyeLEwEBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQ4PgyYEhTMrC4JyhE4BCgQCgymCYQWJfgEThxaBZ4UliECEOYIhhFuJHAK?= =?us-ascii?q?CEYVng1qHHZUrgTk2IVsyMiEIHBWFXAUcgWk+iBMBASQHghQBAQE?=
X-IronPort-AV: E=Sophos;i="5.42,360,1500940800";  d="asc'?scan'208,217";a="657313580"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Sep 2017 06:25:04 +0000
Received: from [10.61.194.216] ([10.61.194.216]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v886P4kw026034; Fri, 8 Sep 2017 06:25:04 GMT
To: Robert Sparks <rjsparks@nostrum.com>, gen-art@ietf.org
Cc: draft-ietf-opsawg-mud.all@ietf.org, opsawg@ietf.org, ietf@ietf.org
References: <150411366399.21627.17047458871931107094@ietfa.amsl.com> <0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com> <3570a07d-6786-3077-f1a7-4ec61a4bf9d0@nostrum.com>
From: Eliot Lear <lear@cisco.com>
Message-ID: <59951415-4f15-97da-fef0-be2686850b9d@cisco.com>
Date: Fri, 8 Sep 2017 08:25:09 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <3570a07d-6786-3077-f1a7-4ec61a4bf9d0@nostrum.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="G09gOSsONrln52186q8PjfU32srn0a7r1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/d69dzaCtN0fwG4fUY7O92w1czds>
Subject: Re: [Gen-art] Genart early review of draft-ietf-opsawg-mud-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 06:25:12 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--G09gOSsONrln52186q8PjfU32srn0a7r1
Content-Type: multipart/mixed; boundary="m1Rf2qkQejQRNEUanG9feDvMxoQF52C2G";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: Robert Sparks <rjsparks@nostrum.com>, gen-art@ietf.org
Cc: draft-ietf-opsawg-mud.all@ietf.org, opsawg@ietf.org, ietf@ietf.org
Message-ID: <59951415-4f15-97da-fef0-be2686850b9d@cisco.com>
Subject: Re: Genart early review of draft-ietf-opsawg-mud-08
References: <150411366399.21627.17047458871931107094@ietfa.amsl.com>
 <0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com>
 <3570a07d-6786-3077-f1a7-4ec61a4bf9d0@nostrum.com>
In-Reply-To: <3570a07d-6786-3077-f1a7-4ec61a4bf9d0@nostrum.com>

--m1Rf2qkQejQRNEUanG9feDvMxoQF52C2G
Content-Type: multipart/alternative;
 boundary="------------492D86A3EC36FAC886DF6A3D"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------492D86A3EC36FAC886DF6A3D
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Robert,

Thanks now for BOTH of your reviews.=C2=A0 I've a number of proposals bel=
ow.

On 9/7/17 5:51 PM, Robert Sparks wrote:

> There is one aspect of caching semantics we should probably capture,
> which is that the cache-validity period should exceed the HTTP cache
> or expiry period as specified by max-age or Expires.=C2=A0 Does that so=
und
> about right to you?
> Goes in the right direction. Do you expect POST to work with this?

There is no particular POST operation required, but if someone wanted to
POST a MUD file, so long as they also POST a signature file, it should
be fine.

>>
>>> I think there needs to be more discussion of the PKI used for signing=
 MUD
>>> files.
>>
>> We do have some discussion in Section 12.2.=C2=A0 I'm happy to add an
>> additional sentence or two, but would seek guidance on where you
>> think we're missing.
> So, are you expecting to reuse the web PKI here? Will the MUD files be
> signed with the same credentials used by the HTTP server? I'm thinking
> you aren't, and are waving your hands at where trust lies with the
> recommendation that signers be validated directly etc. Either way, I
> think you need to be more explicit and that what you expect for
> establishing trust is going to take more than a couple of sentences.

You're right.=C2=A0 I don't think we want to interlock the signature of t=
he
file with the cert used on the web server.=C2=A0 It *could* be that, but =
the
focus on trust has to be the signer of the file.=C2=A0 How about somethin=
g
like this:

    The purpose of the signature on the file is to assign accountability
    to an entity, whose reputation can be used to guide administrators
    on whether or not to accept a given MUD file.=C2=A0 It is already com=
mon
    place to check web=C2=A0 reputation on the location of a server on wh=
ich
    a file resides.=C2=A0 While it is likely that the manufacturer will b=
e
    the signer of the file, this is not strictly necessary, and may not
    be desirable.=C2=A0 For one thing, in some environments, integrators =
may
    install their own certificates.=C2=A0 For another, what is more impor=
tant
    is the accountability of the recommendation, and not the
    cryptographic relationship between the device and the file.=C2=A0


??

This follows the philosophy we've used previously in efforts like DKIM.


>>
>>> Consider discussing whether the stacks used by typical things will le=
t
>>> them add DHCP options (or include bits in the other protocols being=20
>>> enabled). If it's well known (I can't say) that these stacks typicall=
y
>>> _won't_ provide that functionality, then you should punch up the
>>> discussion of the controllers mapping other identifiers to MUD URLs o=
n
>>> behalf of the thing.
>>
>> I agree.=C2=A0 We allude to this in the draft.=C2=A0 We say, for insta=
nce:
>>> It is possible that there may be other means for a MUD URL to be
>>> learned by a network.=C2=A0 For instance, if a device has a serial nu=
mber,
>>> it may be possible for the MUD controller to perform a lookup of the
>>> device, if it has some knowledge as to who the device manufacturer
>>> is, and what its MUD file server is.=C2=A0 Such mechanisms are not
>>> described in this memo, but are possible.
>>
>> The case we have in mind is LoRaWAN.=C2=A0 Should we go further?
> I think explicitly acknowledging that some things stacks limit their
> behavior will pay back.=20

How about a replacement paragraph:

    It is possible that there may be other means for a MUD URL to be
    learned by a network.=C2=A0 For instance, some devices may already be=

    fielded or have very limited ability to communicate a MUD URL, and ye=
t
    can be identified through some means, such as a serial number or a
    public key.=C2=A0 In these cases, manufacturers may be able to map th=
ose
    identifies to particular MUD URLs (or even the files themselves).
    Similarly, there may be alternative resolution mechanisms available
    for situations where Internet connectivity is limited or does not
    exist.=C2=A0 Such mechanisms are not described in this memo, but are
    possible.=C2=A0 Implementors should allow for this sort of flexibilit=
y of
    how MUD URLs may be learned.

>
>>> You suggest the DHCP Client (which is a thing) SHOULD log or report=20
>>> improper acknowledgments from servers. That's asking a bit much from
>>> a thing. I suspect the requirement is unrealistic and should be remov=
ed
>>> or rewritten to acknowledge that things typically won't do that.
>> I think there's a philosophical thing hiding here, though: what
>> expectations should we have of device.=C2=A0 As a SHOULD we're saying,=
 if
>> you have good cause not to, ok.=C2=A0 But otherwise, for the sake of t=
he
>> sanity of the customer, please log.
> Why not acknowledge in the document that the expectation is that most
> won't be able to.
> Painting as explicit and accurate picture as possible can only do
> good, no?
> (Again, I'm not trying to _assert_ that the majority of things can't,
> but that's my suspicion. People who work with this things on a daily
> basis should weigh in.)

Obviously a Thing can be literally anything.=C2=A0 I agree we are setting=
 a
bit of a bar here, but I would rather not let implementors off the
hook.=C2=A0 From an implementation standpoint, the device is already awak=
e in
this case in order to process the packet, and so we're not talking about
excess power consumption.=C2=A0 In the case of really low power, DHCP isn=
't
going to be in the picture.
>>
>>> The security and deployment considerations sections talk about what t=
he
>>> need for coordination if control over the domain name used in the URL=

>>> changes. It should talk more about what happens if the new administra=
tion
>>> of the domain is not interested in facilitating a transition (conside=
r
>>> the case of a young company with a few thousand start-up-ish things o=
ut
>>> there that loses a suit over its name). Please discuss whether or not=

>>> suddenly losing the MUD assisted network configuration is expected to=

>>> leave the devices effectively cut-off.=20
>>
>> It should not, and here's why:
>>
>>   * Assuming the device has already been used, there is no reason to
>>     simply delete the MUD file from one's cache.=C2=A0 The cache-valid=
ity
>>     value is meant as a timer to keep implementations for harassing
>>     the MUD file server, but there's the information is still useful,
>>     even if it may not have been freshened.
>>
> Hrmm - there should be some description about using the information
> even if the cache has expired. That might have security ramifications
> (it at least enables an attacker to cause a set of devices to use old
> information by attacking the access to what might be newer information)=
=2E

It may be worth "logging and/or reporting".=C2=A0=C2=A0 I think we need
implementation experience to tell us exactly how long to wait before
doing so, however. See below.

>>   * In the case where the MUD file service is unavailable when the
>>     device is first turned up, it's as if it had not included a
>>     MUD-URL in the first place.=C2=A0 While this may be a downgrade
>>     attack, there is, as I understand it, really no way to get around
>>     it, other than for the MUD controller to log a problem.
>>
> Worth a short discussion in the text.

How about this:

    It may not be possible for a MUD controller to retrieve a MUD file at=

    any given time.=C2=A0 Should a MUD controller fail to retrieve a MUD =
file,
    it SHOULD consider the existing one safe to use, at least for a time.=

    After some period, it SHOULD log that it has been unable to retrieve
    the file.=C2=A0 There may be very good reasons for such failures, inc=
luding
    the possibility that the MUD controller is in an off-line environment=
,
    the local Internet connection has failed, or the remote Internet
    connection has failed.=C2=A0 It is also possible that an attacker is
    attempting to prevent onboarding of a device.=C2=A0 It is a local
    deployment decision as to whether or not devices may be onboarded in
    the face of such failures.



>>  *
>>
>>
>>
>>
>>> Right now, you leave the DHCP server (when it's used) responsible for=

>>> clearing state in the MUD controller. Please discuss what happens whe=
n
>>> those are distinct elements (as you have in the end of section 9.2) a=
nd
>>> the DHCP server reboots. Perhaps it would make sense for the DHCP ser=
ver
>>> to hand the length of the lease it has granted to the MUD controller =
and
>>> let the MUD controller clean up on its own?
>>
>> See other response.
>>
>>> The document currently suggests that a piece of software inspect the
>>> WHOIS database to see if registration ownership of a domain has chang=
ed.
>>> Do you really mean software, or should this be advice to the
>>> administrator of the controller instead?=20
>>
>> The controller.=C2=A0 The idea is to catch bad behavior and anomalies.=
=C2=A0
>> And the bigger idea is to reduce the number of decisions that the
>> administrator must make, while providing relevant information with
>> which to make the decisions.
> I don't think this is a reasonable thing to do. It has the many of the
> same properties we complain about when someone suggest that code
> inspect an IANA registry.

This is different.=C2=A0 The registries are REALLY static information and=
 do
not maintain any form of ownership.=C2=A0 Here, if there is an ownership
change, it's a good idea to spot it.=C2=A0 Note that such queries should =
be
infrequent.=C2=A0 They should only happen when a signer has changed, and =
when
DNS information has changed.

>>> At section 4, consider pointing out that you are not allowing=20
>>> DHCP by default, and that devices that are expected to use DHCP
>>> need to have an explicit allow in their MUD file.=20
>>
>> Hmm.=C2=A0 The issue here is that DHCP is an L2 protocol that isn't
>> forwarded.=C2=A0 Do you think it needs to be listed anyway?
> Hmm indeed. You're right. That said, the thing that triggered the thoug=
ht
> was the ability of a MUD file to say whether or not something can talk =
to
> other things in the local network. Maybe some reinforcement in the
> discussion
> about what that rule would expand to would prevent someone from walling=

> off the device more than you intended (it would be a creative mistake
> to do so,
> I agree)

I'd need a suggestion for that, but since it's a stretch I suggest we
let this one go for now.

Thanks again.

Eliot

--------------492D86A3EC36FAC886DF6A3D
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf=
-8">
  </head>
  <body text=3D"#000000" bgcolor=3D"#FFFFFF">
    <p>Hi Robert,</p>
    <p>Thanks now for BOTH of your reviews.=C2=A0 I've a number of propos=
als
      below.<br>
    </p>
    <div class=3D"moz-cite-prefix">On 9/7/17 5:51 PM, Robert Sparks wrote=
:<br>
    </div>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:3570a07d-6786-3077-f1a7-4ec61a4bf9d0@nostrum.com">There=

      is one aspect of caching semantics we should probably capture,
      which is that the cache-validity period should exceed the HTTP
      cache or expiry period as specified by max-age or Expires.=C2=A0 Do=
es
      that sound about right to you?<br>
      Goes in the right direction. Do you expect POST to work with this?
      <br>
    </blockquote>
    <br>
    There is no particular POST operation required, but if someone
    wanted to POST a MUD file, so long as they also POST a signature
    file, it should be fine.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:3570a07d-6786-3077-f1a7-4ec61a4bf9d0@nostrum.com">
      <blockquote type=3D"cite"
        cite=3D"mid:0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com"> <br>=

        <blockquote type=3D"cite"
          cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.=
com">
          <pre wrap=3D"">I think there needs to be more discussion of the=
 PKI used for signing MUD
files.</pre>
        </blockquote>
        <br>
        We do have some discussion in Section 12.2.=C2=A0 I'm happy to ad=
d an
        additional sentence or two, but would seek guidance on where you
        think we're missing.<br>
      </blockquote>
      So, are you expecting to reuse the web PKI here? Will the MUD
      files be signed with the same credentials used by the HTTP server?
      I'm thinking you aren't, and are waving your hands at where trust
      lies with the recommendation that signers be validated directly
      etc. Either way, I think you need to be more explicit and that
      what you expect for establishing trust is going to take more than
      a couple of sentences.<br>
    </blockquote>
    <br>
    You're right.=C2=A0 I don't think we want to interlock the signature =
of
    the file with the cert used on the web server.=C2=A0 It *could* be th=
at,
    but the focus on trust has to be the signer of the file.=C2=A0 How ab=
out
    something like this:<br>
    <br>
    <blockquote>The purpose of the signature on the file is to assign
      accountability to an entity, whose reputation can be used to guide
      administrators on whether or not to accept a given MUD file.=C2=A0 =
It
      is already common place to check web=C2=A0 reputation on the locati=
on
      of a server on which a file resides.=C2=A0 While it is likely that =
the
      manufacturer will be the signer of the file, this is not strictly
      necessary, and may not be desirable.=C2=A0 For one thing, in some
      environments, integrators may install their own certificates.=C2=A0=
 For
      another, what is more important is the accountability of the
      recommendation, and not the cryptographic relationship between the
      device and the file.=C2=A0 <br>
    </blockquote>
    <br>
    ??<br>
    <br>
    This follows the philosophy we've used previously in efforts like
    DKIM.<br>
    <br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:3570a07d-6786-3077-f1a7-4ec61a4bf9d0@nostrum.com">
      <blockquote type=3D"cite"
        cite=3D"mid:0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com"> <br>=

        <blockquote type=3D"cite"
          cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.=
com">
          <pre wrap=3D"">Consider discussing whether the stacks used by t=
ypical things will let
them add DHCP options (or include bits in the other protocols being=20
enabled). If it's well known (I can't say) that these stacks typically
_won't_ provide that functionality, then you should punch up the
discussion of the controllers mapping other identifiers to MUD URLs on
behalf of the thing.</pre>
        </blockquote>
        <br>
        I agree.=C2=A0 We allude to this in the draft.=C2=A0 We say, for =
instance:<br>
        <blockquote type=3D"cite">It is possible that there may be other
          means for a MUD URL to be<br>
          learned by a network.=C2=A0 For instance, if a device has a ser=
ial
          number,<br>
          it may be possible for the MUD controller to perform a lookup
          of the<br>
          device, if it has some knowledge as to who the device
          manufacturer<br>
          is, and what its MUD file server is.=C2=A0 Such mechanisms are =
not<br>
          described in this memo, but are possible.<br>
        </blockquote>
        <br>
        The case we have in mind is LoRaWAN.=C2=A0 Should we go further?<=
br>
      </blockquote>
      I think explicitly acknowledging that some things stacks limit
      their behavior will pay back. </blockquote>
    <br>
    How about a replacement paragraph:<br>
    <br>
    <blockquote>It is possible that there may be other means for a MUD
      URL to be<br>
      learned by a network.=C2=A0 For instance, some devices may already =
be<br>
      fielded or have very limited ability to communicate a MUD URL, and
      yet<br>
      can be identified through some means, such as a serial number or a<=
br>
      public key.=C2=A0 In these cases, manufacturers may be able to map
      those<br>
      identifies to particular MUD URLs (or even the files themselves).<b=
r>
      Similarly, there may be alternative resolution mechanisms
      available<br>
      for situations where Internet connectivity is limited or does not<b=
r>
      exist.=C2=A0 Such mechanisms are not described in this memo, but ar=
e<br>
      possible.=C2=A0 Implementors should allow for this sort of flexibil=
ity
      of<br>
      how MUD URLs may be learned.<br>
    </blockquote>
    <blockquote type=3D"cite"
      cite=3D"mid:3570a07d-6786-3077-f1a7-4ec61a4bf9d0@nostrum.com"><br>
      <blockquote type=3D"cite"
        cite=3D"mid:0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com">
        <blockquote type=3D"cite"
          cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.=
com">
          <pre wrap=3D"">You suggest the DHCP Client (which is a thing) S=
HOULD log or report=20
improper acknowledgments from servers. That's asking a bit much from
a thing. I suspect the requirement is unrealistic and should be removed
or rewritten to acknowledge that things typically won't do that.</pre>
        </blockquote>
        I think there's a philosophical thing hiding here, though: what
        expectations should we have of device.=C2=A0 As a SHOULD we're
        saying, if you have good cause not to, ok.=C2=A0 But otherwise, f=
or
        the sake of the sanity of the customer, please log.<br>
      </blockquote>
      Why not acknowledge in the document that the expectation is that
      most won't be able to.<br>
      Painting as explicit and accurate picture as possible can only do
      good, no?<br>
      (Again, I'm not trying to _assert_ that the majority of things
      can't, but that's my suspicion. People who work with this things
      on a daily basis should weigh in.)<br>
    </blockquote>
    <br>
    Obviously a Thing can be literally anything.=C2=A0 I agree we are set=
ting
    a bit of a bar here, but I would rather not let implementors off the
    hook.=C2=A0 From an implementation standpoint, the device is already
    awake in this case in order to process the packet, and so we're not
    talking about excess power consumption.=C2=A0 In the case of really l=
ow
    power, DHCP isn't going to be in the picture.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:3570a07d-6786-3077-f1a7-4ec61a4bf9d0@nostrum.com">
      <blockquote type=3D"cite"
        cite=3D"mid:0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com"> <br>=

        <blockquote type=3D"cite"
          cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.=
com">
          <pre wrap=3D"">The security and deployment considerations secti=
ons talk about what the
need for coordination if control over the domain name used in the URL
changes. It should talk more about what happens if the new administration=

of the domain is not interested in facilitating a transition (consider
the case of a young company with a few thousand start-up-ish things out
there that loses a suit over its name). Please discuss whether or not
suddenly losing the MUD assisted network configuration is expected to
leave the devices effectively cut-off. </pre>
        </blockquote>
        <br>
        It should not, and here's why:<br>
        <br>
        <ul>
          <li>Assuming the device has already been used, there is no
            reason to simply delete the MUD file from one's cache.=C2=A0 =
The
            cache-validity value is meant as a timer to keep
            implementations for harassing the MUD file server, but
            there's the information is still useful, even if it may not
            have been freshened.</li>
        </ul>
      </blockquote>
      Hrmm - there should be some description about using the
      information even if the cache has expired. That might have
      security ramifications (it at least enables an attacker to cause a
      set of devices to use old information by attacking the access to
      what might be newer information).<br>
    </blockquote>
    <br>
    It may be worth "logging and/or reporting".=C2=A0=C2=A0 I think we ne=
ed
    implementation experience to tell us exactly how long to wait before
    doing so, however. See below.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:3570a07d-6786-3077-f1a7-4ec61a4bf9d0@nostrum.com">
      <blockquote type=3D"cite"
        cite=3D"mid:0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com">
        <ul>
          <li>In the case where the MUD file service is unavailable when
            the device is first turned up, it's as if it had not
            included a MUD-URL in the first place.=C2=A0 While this may b=
e a
            downgrade attack, there is, as I understand it, really no
            way to get around it, other than for the MUD controller to
            log a problem.<br>
          </li>
        </ul>
      </blockquote>
      Worth a short discussion in the text.<br>
    </blockquote>
    <br>
    How about this:<br>
    <br>
    <blockquote>It may not be possible for a MUD controller to retrieve
      a MUD file at<br>
      any given time.=C2=A0 Should a MUD controller fail to retrieve a MU=
D
      file,<br>
      it SHOULD consider the existing one safe to use, at least for a
      time.<br>
      After some period, it SHOULD log that it has been unable to
      retrieve<br>
      the file.=C2=A0 There may be very good reasons for such failures,
      including<br>
      the possibility that the MUD controller is in an off-line
      environment,<br>
      the local Internet connection has failed, or the remote Internet<br=
>
      connection has failed.=C2=A0 It is also possible that an attacker i=
s<br>
      attempting to prevent onboarding of a device.=C2=A0 It is a local<b=
r>
      deployment decision as to whether or not devices may be onboarded
      in<br>
      the face of such failures.<br>
    </blockquote>
    <br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:3570a07d-6786-3077-f1a7-4ec61a4bf9d0@nostrum.com">
      <blockquote type=3D"cite"
        cite=3D"mid:0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com">
        <ul>
          <li> <br>
          </li>
        </ul>
        <blockquote type=3D"cite"
          cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.=
com">
          <pre wrap=3D"">Right now, you leave the DHCP server (when it's =
used) responsible for
clearing state in the MUD controller. Please discuss what happens when
those are distinct elements (as you have in the end of section 9.2) and
the DHCP server reboots. Perhaps it would make sense for the DHCP server
to hand the length of the lease it has granted to the MUD controller and
let the MUD controller clean up on its own?</pre>
        </blockquote>
        <br>
        See other response.<br>
        <br>
        <blockquote type=3D"cite"
          cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.=
com">
          <pre wrap=3D"">The document currently suggests that a piece of =
software inspect the
WHOIS database to see if registration ownership of a domain has changed.
Do you really mean software, or should this be advice to the
administrator of the controller instead? </pre>
        </blockquote>
        <br>
        The controller.=C2=A0 The idea is to catch bad behavior and
        anomalies.=C2=A0 And the bigger idea is to reduce the number of
        decisions that the administrator must make, while providing
        relevant information with which to make the decisions.<br>
      </blockquote>
      I don't think this is a reasonable thing to do. It has the many of
      the same properties we complain about when someone suggest that
      code inspect an IANA registry.<br>
    </blockquote>
    <br>
    This is different.=C2=A0 The registries are REALLY static information=
 and
    do not maintain any form of ownership.=C2=A0 Here, if there is an
    ownership change, it's a good idea to spot it.=C2=A0 Note that such
    queries should be infrequent.=C2=A0 They should only happen when a si=
gner
    has changed, and when DNS information has changed.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:3570a07d-6786-3077-f1a7-4ec61a4bf9d0@nostrum.com">
      <blockquote type=3D"cite"
        cite=3D"mid:0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com">
        <blockquote type=3D"cite"
          cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.=
com">
          <pre wrap=3D"">At section 4, consider pointing out that you are=
 not allowing=20
DHCP by default, and that devices that are expected to use DHCP
need to have an explicit allow in their MUD file. </pre>
        </blockquote>
        <br>
        Hmm.=C2=A0 The issue here is that DHCP is an L2 protocol that isn=
't
        forwarded.=C2=A0 Do you think it needs to be listed anyway?</bloc=
kquote>
      Hmm indeed. You're right. That said, the thing that triggered the
      thought<br>
      was the ability of a MUD file to say whether or not something can
      talk to<br>
      other things in the local network. Maybe some reinforcement in the
      discussion<br>
      about what that rule would expand to would prevent someone from
      walling<br>
      off the device more than you intended (it would be a creative
      mistake to do so,<br>
      I agree)<br>
    </blockquote>
    <br>
    I'd need a suggestion for that, but since it's a stretch I suggest
    we let this one go for now.<br>
    <br>
    Thanks again.<br>
    <br>
    Eliot<br>
  </body>
</html>

--------------492D86A3EC36FAC886DF6A3D--

--m1Rf2qkQejQRNEUanG9feDvMxoQF52C2G--

--G09gOSsONrln52186q8PjfU32srn0a7r1
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2

iQEcBAEBCAAGBQJZsjfFAAoJEIe2a0bZ0nozSr0IAIxMmojcFqthbfF4tdwqRp+f
ngYruBPVzxqm6Zl6BIHXBPeLOkZDjk4lfW7Ja/CasXIubN0XBgageSZfRvwHe63u
JjdLzei/lnJzl9i81qwg+0Ja0zuFp+gc+LAGGrX4fcRufzDR+LK3ALiIDCq6Q9uI
0gWOiQU7zMdXIi9772V3lv1IdUmnnb7Vi71UswQLt3Grjl4Nnw04+fEY+Ps4DgkP
hIEWFZcFLuGFyySam+0MvqFiByR1dYD8iVdMa/16bYMhODLRxQMU+fHuaCRevF92
YkiHSpAitdSmqrADK2nueGDgT6/uage5l4HeHiL/IKGlrMoc/TDylkgZQ1p4ldE=
=zGHT
-----END PGP SIGNATURE-----

--G09gOSsONrln52186q8PjfU32srn0a7r1--


From nobody Mon Sep 11 04:39:03 2017
Return-Path: <ietf@kuehlewind.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34174132D14 for <gen-art@ietfa.amsl.com>; Mon, 11 Sep 2017 04:39:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.net
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 dan5be-529pG for <gen-art@ietfa.amsl.com>; Mon, 11 Sep 2017 04:39:00 -0700 (PDT)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02EA1133049 for <gen-art@ietf.org>; Mon, 11 Sep 2017 04:38:59 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net;  b=Qjd3+N+TXPO5LG7hVKqPz25DHW0yPpchV5/v5dVhZfTO1xXVpW6op2IfBXsX0OF7uhve8RxLd0eY//18kOVYp7Gv3H1ggWvi5YeWZpKrojtrhvKCF5q5qau/RqmEZOJB4PCi8F73fBsiIXyU9eQlRxVZO1m5P0wPHhVUfj1N9zQ=; h=Received:Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 30396 invoked from network); 11 Sep 2017 13:38:58 +0200
Received: from pd9e11f83.dip0.t-ipconnect.de (HELO ?192.168.178.33?) (217.225.31.131) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 11 Sep 2017 13:38:58 +0200
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <150431489114.6649.9807443646105756121@ietfa.amsl.com>
Date: Mon, 11 Sep 2017 13:38:53 +0200
Cc: gen-art <gen-art@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <531E9DB4-8B3B-44A8-A33A-E86CFA6390BC@kuehlewind.net>
References: <150431489114.6649.9807443646105756121@ietfa.amsl.com>
To: Peter Yee <peter@akayla.com>
X-Mailer: Apple Mail (2.3273)
X-PPP-Message-ID: <20170911113858.30391.18276@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/dvmgzKUMr_dGx5IXZNpkaCwawEI>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-mpls-ldp-mrt-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 11:39:02 -0000

Thanks for the review and detailed read!

> Am 02.09.2017 um 03:14 schrieb Peter Yee <peter@akayla.com>:
>=20
> Reviewer: Peter Yee
> Review result: Ready with Issues
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-mpls-ldp-mrt-06
> Reviewer: Peter Yee
> Review Date: 2017-09-01
> IETF LC End Date: 2017-09-01
> IESG Telechat date: 2017-09-14
>=20
> Summary:  The draft is ready for publication after correcting some =
minor issues.
>=20
> Major issues:  None
>=20
> Minor issues:
>=20
> Page 3, section 3, IBR definition: the definition give here appears to =
be a
> duplicate of the one given for IN.  Copy the correct definition from =
RFC 7812
> instead.
>=20
> Nits/editorial comments:
>=20
> Page 3, section 1, 2nd paragraph, 1st sentence: append a comma after =
"e.g.".
>=20
> Page 8, section 4.4., 1st paragraph, 2nd sentence: delete duplicate =
"on".
>=20
> Page 8, section 4.4, 2nd paragraph, 4th sentence: change comma after
> "computations" to a period.
>=20
> Page 9, section 5.1.1, 4th paragraph, 2nd sentence: the construction
> "red(blue)" is used without defining what it means exactly.  =46rom =
the context,
> it isn't quite "red or blue".  An explanation of the meaning of this
> construction should be given.  I'm assuming it means something like =
use "red"
> in the sentence in all cases or use use "blue", but don't mix them.  =
There's
> also red/blue used later in the document which muddies the point.
>=20
> Page 10, 1st full paragraph, 2nd sentence: change "foll" to =
"follows:".
>=20
> Page 11, section 5.2.2, 2nd paragraph, 1st sentence: delete the period =
after
> "A.1.7".
>=20
> Page 12, 1st paragraph, 1st sentence: consider deleting "how".
>=20
> Page 13, 2nd paragraph after numbered list, 1st sentence: append "to" =
after
> "respect".
>=20
> Section titles for 5.2, 5.3, and 7: append a space after "RFC" to =
separate it
> from the number.  The spaceless form should only be used for =
references
> enclosed in brackets.
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Mon Sep 11 04:51:07 2017
Return-Path: <worley@ariadne.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 51B04133055; Mon, 11 Sep 2017 04:51:00 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Dale Worley <worley@ariadne.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-bess-evpn-etree.all@ietf.org, ietf@ietf.org, bess@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.60.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150513066026.9797.2035706342631240836@ietfa.amsl.com>
Date: Mon, 11 Sep 2017 04:51:00 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/QAyKe08r9KUvV7YWSkzUefHljZo>
Subject: [Gen-art] Genart telechat review of draft-ietf-bess-evpn-etree-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 11:51:00 -0000

Reviewer: Dale Worley
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft.  The General Area
Review Team (Gen-ART) reviews all IETF documents being processed by
the IESG for the IETF Chair.  Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document:  draft-ietf-bess-evpn-etree-13
Reviewer:  Dale R. Worley
Review Date:  2017-09-12
IETF LC End Date:  2017-08-09
IESG Telechat date:  2017-09-12

Summary:

This draft is basically ready for publication, but has nits that
should be fixed before publication.

There are a few matters that I would like to see amplified in the
Introduction to improve the exposition for readers who aren't familiar
with this area.

1.  Relationship to RFC 7432.  The Introduction now states "Since this
document specifies a solution based on [RFC7432], it requires the
readers to have the knowledge of [RFC7432] as prerequisite."  This is
a significant improvement, but I still find this unsatisfyingly vague
regarding the relationship between the two documents.  Is RFC 7432
only background knowledge, or is this document an
extension/modification of RFC 7432, in which case, some parts of the
technique described in this document are actually defined in RFC 7432?
It seems a minor change of wording of this sentence could make this
clear.

2.  Management:  The document doesn't describe how the EVPN structure
will be set up (e.g., how endpoints are added or deleted from the
structure, what MPLS labels will be used), nor how choice of the many
technology alternatives will be communicated (e.g., 2.1 vs. 2.2
vs. 2.3; approach A vs. approach B).  I suspect that this is normal
for documents defining VPN techniques, but it seems peculiar for me,
as the areas I'm familiar with (SIP and data-center networking) try to
minimize the amount of "configuration" that needs to be done.  It
might help the reader to list in the Introduction what aspects of
set-up are out of scope for the document, and conversely, what aspects
you've arranged for the control plane to handle automatically (which
are benefits of the technique).

3.  Efficiency:  The Abstract and the final paragraph of the
Introduction mention that this technique is more efficient than that
of RFC 7796, and of course that is a major motivation for this work.
But the nature of the improved efficiency is only detailed in section
3.1.  It would help the reader, I think, to mention the nature of the
improved efficiency in the Introduction, and perhaps to mention the
specific traffic patterns where this improved efficiency is
particularly effective.  This helps the reader know when reading the
document will be particularly valuable.

There are a few nits I noticed:

Abstract

   solution based on RFC7432, BGP MPLS Based Ethernet VPN (EVPN), with
   some extensions and how such a solution can offer a more efficient
   implementation of these functions than that of RFC7796, E-Tree
   Support in Virtual Private LAN Service (VPLS). This document makes

In the same way as you quote the title of RFC 76387, it would be more
readable if you quoted the titles of the other two RFCs.

1  Introduction

   Attachment Circuits (AC) (e.g., an Ethernet tag but may also be
   represented by a MAC address) is labeled as either a Root or a Leaf

I assume "tag" means 802.1q VLAN tag, but it would be helpful to spell
that out.

1.2  Terminology

   Ethernet Segment Identifier (ESI): A unique non-zero identifier that
   identifies an Ethernet segment is called an 'Ethernet Segment
   Identifier'.

What universe is the ESI is unique over?

[END]



From nobody Mon Sep 11 06:20:36 2017
Return-Path: <ietf@kuehlewind.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F770132716 for <gen-art@ietfa.amsl.com>; Mon, 11 Sep 2017 06:20:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.net
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 eA1vyxrLUi12 for <gen-art@ietfa.amsl.com>; Mon, 11 Sep 2017 06:20:28 -0700 (PDT)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FBA71326DF for <gen-art@ietf.org>; Mon, 11 Sep 2017 06:20:27 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net;  b=dvMigwnksKu/aWKHOX7NPTwcpDodDkmzo7emdt2heX8nmxALUYOwIzta4/ZztSW8f7cFYkll0cCogqKtUMpdGTsD39V41BLOgazG0eGAspG60LnxAD4rfTht/nKeSKkWvW2n+Dzze9cWL97YyqjYmXyHnpYXLfXvO2EA7sutvH0=; h=Received:Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 5687 invoked from network); 11 Sep 2017 15:20:25 +0200
Received: from pd9e11f83.dip0.t-ipconnect.de (HELO ?192.168.178.33?) (217.225.31.131) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 11 Sep 2017 15:20:25 +0200
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <150513066026.9797.2035706342631240836@ietfa.amsl.com>
Date: Mon, 11 Sep 2017 15:20:23 +0200
Cc: gen-art <gen-art@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5668A16D-C2FA-4103-9DBB-477EAC04FC9B@kuehlewind.net>
References: <150513066026.9797.2035706342631240836@ietfa.amsl.com>
To: Dale Worley <worley@ariadne.com>
X-Mailer: Apple Mail (2.3273)
X-PPP-Message-ID: <20170911132025.5682.60191@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/tgjb-Y_G25mnKafmVPqTULb1Rw8>
Subject: Re: [Gen-art] Genart telechat review of draft-ietf-bess-evpn-etree-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 13:20:34 -0000

Thanks for the review. I agree and updated my ballot to point to your =
review comments as well!

> Am 11.09.2017 um 13:51 schrieb Dale Worley <worley@ariadne.com>:
>=20
> Reviewer: Dale Worley
> Review result: Ready with Nits
>=20
> I am the assigned Gen-ART reviewer for this draft.  The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed by
> the IESG for the IETF Chair.  Please wait for direction from your
> document shepherd or AD before posting a new version of the draft.
>=20
> For more information, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Document:  draft-ietf-bess-evpn-etree-13
> Reviewer:  Dale R. Worley
> Review Date:  2017-09-12
> IETF LC End Date:  2017-08-09
> IESG Telechat date:  2017-09-12
>=20
> Summary:
>=20
> This draft is basically ready for publication, but has nits that
> should be fixed before publication.
>=20
> There are a few matters that I would like to see amplified in the
> Introduction to improve the exposition for readers who aren't familiar
> with this area.
>=20
> 1.  Relationship to RFC 7432.  The Introduction now states "Since this
> document specifies a solution based on [RFC7432], it requires the
> readers to have the knowledge of [RFC7432] as prerequisite."  This is
> a significant improvement, but I still find this unsatisfyingly vague
> regarding the relationship between the two documents.  Is RFC 7432
> only background knowledge, or is this document an
> extension/modification of RFC 7432, in which case, some parts of the
> technique described in this document are actually defined in RFC 7432?
> It seems a minor change of wording of this sentence could make this
> clear.
>=20
> 2.  Management:  The document doesn't describe how the EVPN structure
> will be set up (e.g., how endpoints are added or deleted from the
> structure, what MPLS labels will be used), nor how choice of the many
> technology alternatives will be communicated (e.g., 2.1 vs. 2.2
> vs. 2.3; approach A vs. approach B).  I suspect that this is normal
> for documents defining VPN techniques, but it seems peculiar for me,
> as the areas I'm familiar with (SIP and data-center networking) try to
> minimize the amount of "configuration" that needs to be done.  It
> might help the reader to list in the Introduction what aspects of
> set-up are out of scope for the document, and conversely, what aspects
> you've arranged for the control plane to handle automatically (which
> are benefits of the technique).
>=20
> 3.  Efficiency:  The Abstract and the final paragraph of the
> Introduction mention that this technique is more efficient than that
> of RFC 7796, and of course that is a major motivation for this work.
> But the nature of the improved efficiency is only detailed in section
> 3.1.  It would help the reader, I think, to mention the nature of the
> improved efficiency in the Introduction, and perhaps to mention the
> specific traffic patterns where this improved efficiency is
> particularly effective.  This helps the reader know when reading the
> document will be particularly valuable.
>=20
> There are a few nits I noticed:
>=20
> Abstract
>=20
>   solution based on RFC7432, BGP MPLS Based Ethernet VPN (EVPN), with
>   some extensions and how such a solution can offer a more efficient
>   implementation of these functions than that of RFC7796, E-Tree
>   Support in Virtual Private LAN Service (VPLS). This document makes
>=20
> In the same way as you quote the title of RFC 76387, it would be more
> readable if you quoted the titles of the other two RFCs.
>=20
> 1  Introduction
>=20
>   Attachment Circuits (AC) (e.g., an Ethernet tag but may also be
>   represented by a MAC address) is labeled as either a Root or a Leaf
>=20
> I assume "tag" means 802.1q VLAN tag, but it would be helpful to spell
> that out.
>=20
> 1.2  Terminology
>=20
>   Ethernet Segment Identifier (ESI): A unique non-zero identifier that
>   identifies an Ethernet segment is called an 'Ethernet Segment
>   Identifier'.
>=20
> What universe is the ESI is unique over?
>=20
> [END]
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Mon Sep 11 08:43:32 2017
Return-Path: <linuxwolf+ietf@outer-planes.net>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B6901326FE; Mon, 11 Sep 2017 08:43:24 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Matthew Miller <linuxwolf+ietf@outer-planes.net>
To: <gen-art@ietf.org>
Cc: rmcat@ietf.org, ietf@ietf.org, draft-ietf-rmcat-coupled-cc.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.60.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150514460458.9791.14186175950174051912@ietfa.amsl.com>
Date: Mon, 11 Sep 2017 08:43:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/ST_t9CPxPvFbsefpgdsmemXD1k8>
Subject: [Gen-art] Genart last call review of draft-ietf-rmcat-coupled-cc-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 15:43:25 -0000

Reviewer: Matthew Miller
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-rmcat-coupled-cc-06
Reviewer: Matthew A. Miller
Review Date:  2017-09-11
IETF LC End Date: 2017-08-28
IESG Telechat date: 2017-09-14

Summary:

This document is ready to be published as Experimental; I have some nits
below that addressing them would help with the readability.

Major issues:  NONE

Minor issues:  NONE

Nits/editorial comments:

* In Section 2. "Definitions", the second sentence detailing the term
"Flow" is awkward.  I think "or" can be added between "connection," and
"an RTP stream" to correct it?

  """
  It could, for example, be a transport layer connection, or an RTP
  stream [RFC7656], whether or not this RTP stream is multiplexed
  onto an RTP session with other RTP streams.
  """

* In Section 4. "Architectural overview", the last paragraph has an
awkwardly-phrased sentence.  I suggest the following sentence be changed from:
  """
  It does, for instance, not define how many bits must be used to represent
  FSIs, or in which way the entities communicate.
  """

  to the following:
  """
  It does not, for instance, define how many bits must be used to represent
  FSIs, or in which way the entities communicate.
  """



From nobody Mon Sep 11 08:50:32 2017
Return-Path: <linuxwolf+ietf@outer-planes.net>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A4202133147; Mon, 11 Sep 2017 08:50:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Matthew Miller <linuxwolf+ietf@outer-planes.net>
To: <gen-art@ietf.org>
Cc: curdle@ietf.org, ietf@ietf.org, draft-ietf-curdle-ssh-ext-info.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.60.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150514502563.9757.15916793470185466485@ietfa.amsl.com>
Date: Mon, 11 Sep 2017 08:50:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/z2sTB9X5qb1zKOP7yjsD9vD7ka0>
Subject: [Gen-art] Genart telechat review of draft-ietf-curdle-ssh-ext-info-12
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 15:50:26 -0000

Reviewer: Matthew Miller
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-curdle-ssh-ext-info-12
Reviewer: Matthew Miller
Review Date: 2017-09-11
IETF LC End Date: 2017-07-30
IESG Telechat date: 2017-09-14

Summary:

This document is ready to be published as Standards Track.  All of my
concerned from revision -10 are addressed in this revision (-12).

Major issues:  NONE

Minor issues: NONE

Nits/editorial comments: NONE



From nobody Mon Sep 11 08:56:59 2017
Return-Path: <ietf@kuehlewind.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5638133143 for <gen-art@ietfa.amsl.com>; Mon, 11 Sep 2017 08:56:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.net
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 952r7lBTq_MZ for <gen-art@ietfa.amsl.com>; Mon, 11 Sep 2017 08:56:56 -0700 (PDT)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4288513292D for <gen-art@ietf.org>; Mon, 11 Sep 2017 08:56:56 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net;  b=IXSWwSN1dssxxh8sIetGo32DLm44ZEeN+5JnqiuJDl8dA3t4cp0DYgkvF9ZeLl3jV93sLdHhPUqL1KDkQzeRWWN1yb4JXPKKUWOeFib8erdkJMvXdZllEvFL/a38hCX8cHR41h03JM/0z0AjTBtEyhLszAVvjNqYs6rweQhWVfs=; h=Received:Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 17479 invoked from network); 11 Sep 2017 17:50:12 +0200
Received: from pd9e11f83.dip0.t-ipconnect.de (HELO ?192.168.178.33?) (217.225.31.131) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 11 Sep 2017 17:50:11 +0200
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <150514460458.9791.14186175950174051912@ietfa.amsl.com>
Date: Mon, 11 Sep 2017 17:50:10 +0200
Cc: gen-art@ietf.org, rmcat@ietf.org, ietf@ietf.org, draft-ietf-rmcat-coupled-cc.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <DF196A30-C75D-4D00-A638-D5BFFAB73A5C@kuehlewind.net>
References: <150514460458.9791.14186175950174051912@ietfa.amsl.com>
To: Matthew Miller <linuxwolf+ietf@outer-planes.net>
X-Mailer: Apple Mail (2.3273)
X-PPP-Message-ID: <20170911155012.17471.98598@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Xchx1nIHZu76kPbIwCALP_cnsoI>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-rmcat-coupled-cc-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 15:56:58 -0000

Thanks for the review and the nit. We will address these in the next =
version or as editor comments!

Mirja


> Am 11.09.2017 um 17:43 schrieb Matthew Miller =
<linuxwolf+ietf@outer-planes.net>:
>=20
> Reviewer: Matthew Miller
> Review result: Ready with Nits
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-rmcat-coupled-cc-06
> Reviewer: Matthew A. Miller
> Review Date:  2017-09-11
> IETF LC End Date: 2017-08-28
> IESG Telechat date: 2017-09-14
>=20
> Summary:
>=20
> This document is ready to be published as Experimental; I have some =
nits
> below that addressing them would help with the readability.
>=20
> Major issues:  NONE
>=20
> Minor issues:  NONE
>=20
> Nits/editorial comments:
>=20
> * In Section 2. "Definitions", the second sentence detailing the term
> "Flow" is awkward.  I think "or" can be added between "connection," =
and
> "an RTP stream" to correct it?
>=20
>  """
>  It could, for example, be a transport layer connection, or an RTP
>  stream [RFC7656], whether or not this RTP stream is multiplexed
>  onto an RTP session with other RTP streams.
>  """
>=20
> * In Section 4. "Architectural overview", the last paragraph has an
> awkwardly-phrased sentence.  I suggest the following sentence be =
changed from:
>  """
>  It does, for instance, not define how many bits must be used to =
represent
>  FSIs, or in which way the entities communicate.
>  """
>=20
>  to the following:
>  """
>  It does not, for instance, define how many bits must be used to =
represent
>  FSIs, or in which way the entities communicate.
>  """
>=20
>=20


From nobody Mon Sep 11 11:02:29 2017
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CEA2132ED1 for <gen-art@ietfa.amsl.com>; Mon, 11 Sep 2017 11:02:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 g6uRUye_XQja for <gen-art@ietfa.amsl.com>; Mon, 11 Sep 2017 11:02:25 -0700 (PDT)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (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 6454012ECEC for <gen-art@ietf.org>; Mon, 11 Sep 2017 11:02:24 -0700 (PDT)
X-AuditID: c6180641-0f7ff70000002d27-15-59b6894b1aa1
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usplmg21.ericsson.net (Symantec Mail Security) with SMTP id 1E.C9.11559.C4986B95; Mon, 11 Sep 2017 15:02:04 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.03.0352.000; Mon, 11 Sep 2017 14:02:22 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-6man-maxra.all@tools.ietf.org" <draft-ietf-6man-maxra.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ietf-6man-maxra-03
Thread-Index: AdMrKAoIPq23NcdASwGY1cLqQS2y8g==
Date: Mon, 11 Sep 2017 18:02:22 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A4F5DE8CC@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.12]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A4F5DE8CCeusaamb107erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrMLMWRmVeSWpSXmKPExsUyuXRPgq5P57ZIg9VnxSwWtLtYXH31mcWB yWPJkp9MHl8uf2YLYIrisklJzcksSy3St0vgyli2VLBgu2rF+nedrA2MkxW7GDk5JARMJH5u mcXWxcjFISRwlFHi488fUM5yRok3314zg1SxCVhIbP/9nBUkISLQwigxd81ORpCEsICtxPm1 bewgtoiAk8Tf/ucsELaexK3DF8GaWQRUJZpWPwGzeQV8JeZPX8QEYjMKiEl8P7UGzGYWEJe4 9WQ+E8RJAhJL9pxnhrBFJV4+/scKYStJzHl9jRmiPl+ifc9LVoiZghInZz5hmcAoOAvJqFlI ymYhKYOI60gs2P2JDcLWlli28DUzjH3mwGMmZPEFjOyrGDlKiwtyctONDDcxAoP+mASb4w7G vb2ehxgFOBiVeHhXNW6LFGJNLCuuzD3EKMHBrCTC+30vUIg3JbGyKrUoP76oNCe1+BCjNAeL kjjvu/ILEUIC6YklqdmpqQWpRTBZJg5OqQZGhdaz+1wd551hrjltdzT5YUTIr8p7rNukCpNP 9unsiT19Vcp1yZTY/CkRXvwRnyOutqUn9U00KLAV3RGQ9V6dP2mnfcuiBBNJmZx9h5yz8q5F PbdSt3/u/a78CkObiZGH4YcVTMqmDFXfk69EvT7jJrlpdgz/hyPm0bUJCt4V73vE/PxPrlZi Kc5INNRiLipOBAD8TijRdgIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/VpO6ZJwW0Dp3LgjfqVjB7tqm58I>
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-6man-maxra-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 18:02:27 -0000

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A4F5DE8CCeusaamb107erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am the assigned Gen-ART reviewer for this draft. The General Area Review =
Team (Gen-ART) reviews all IETF documents being processed by the IESG for t=
he IETF Chair.  Please treat these comments just like any other last call c=
omments.

For more information, please see the FAQ at <https://trac.ietf.org/trac/gen=
/wiki/GenArtfaq>.

Document: draft-ietf-6man-maxra-03
Reviewer: Meral Shirazipour
Review Date: 2017-09-11
IETF LC End Date: 2017-09-15
IESG Telechat date: NA


Summary: This draft is ready to be published as Standards Track RFC.

Major issues:

Minor issues:

Nits/editorial comments:
-[Page 2], "relaxing the the"--typo-->"relaxing the"



Best Regards,
Meral
---
Meral Shirazipour
Ericsson
Research
www.ericsson.com

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A4F5DE8CCeusaamb107erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. T=
he General Area Review Team (Gen-ART) reviews all IETF documents being proc=
essed by the IESG for the IETF Chair.&nbsp; Please treat these comments jus=
t like any other last call comments.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">For more information, please see the FAQ at &lt;http=
s://trac.ietf.org/trac/gen/wiki/GenArtfaq&gt;.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ietf-6man-maxra-03<o:p></o:p></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2017-09-11<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date: 2017-09-15<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: NA<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary: This draft is ready to be published as Stan=
dards Track RFC.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Major issues:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Minor issues:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Nits/editorial comments: <o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 2], &quot;relaxing the the&quot;--typo--&gt;&=
quot;relaxing the&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson<o:p></o:p></p>
<p class=3D"MsoNormal">Research<o:p></o:p></p>
<p class=3D"MsoNormal">www.ericsson.com<o:p></o:p></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A4F5DE8CCeusaamb107erics_--


From nobody Wed Sep 13 11:34:11 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A19213207A; Wed, 13 Sep 2017 11:34:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jari Arkko <jari.arkko@piuha.net>
To: <gen-art@ietf.org>
Cc: dcrup@ietf.org, draft-ietf-dcrup-dkim-usage.all@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.61.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150532764947.30447.10287410957823560223@ietfa.amsl.com>
Date: Wed, 13 Sep 2017 11:34:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Kjo4tb5F2Wo_JS4--fu7eH2jEOA>
Subject: [Gen-art] Genart last call review of draft-ietf-dcrup-dkim-usage-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 18:34:09 -0000

Reviewer: Jari Arkko
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-dcrup-dkim-usage-??
Reviewer: Jari Arkko
Review Date: 2017-09-13
IETF LC End Date: 2017-09-13
IESG Telechat date: Not scheduled for a telechat

Summary:

This document defines modern day requirements for the cryptographic
algorithms used for DKIM.

The document is well written, short, and sets requirements that are
quite appropriate.

I have no comments beyond one small issue/question related to the
wording of the main requirement.

Major issues:

Minor issues:

The document says:

   Signers MUST sign using rsa-sha256.  Verifiers MUST verify
   using rsa-sha256. rsa-sha1 MUST NOT be used for signing or
   verifying.

I was slightly surprised by the wording of the middle requirement
about MUST verify using rsa-sha256.

Given that new algorithms may be defined in the future (and
indeed, draft-ietf-dcrup-dkim-crypto already defines some),
wouldn't a "MUST implement" type wording be more suitable?
Particularly when the third requirement prohibits the use of
weak algorithm. With the middle requirement, how could
any other, future stronger algorithm be used? Or is the idea
that the definition of those algorithms would update these
requirements? Or am I missing something?

Nits/editorial comments: 



From nobody Thu Sep 14 07:35:43 2017
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A8B513303B; Thu, 14 Sep 2017 07:35:23 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: <gen-art@ietf.org>
Cc: draft-ietf-taps-transports-usage-udp.all@ietf.org, ietf@ietf.org, taps@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.61.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150539972354.12573.3384960389295469266@ietfa.amsl.com>
Date: Thu, 14 Sep 2017 07:35:23 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/apKALRji992LIE--QlCD8fl2cqg>
Subject: [Gen-art] Genart telechat review of draft-ietf-taps-transports-usage-udp-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Sep 2017 14:35:24 -0000

Reviewer: Francis Dupont
Review result: On the Right Track

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-taps-transports-usage-udp-??
Reviewer: Francis Dupont
Review Date: 2017-09-14
IETF LC End Date: 2017-09-14
IESG Telechat date: 2017-09-14

Summary: On the Right Track

Major issues: None

Minor issues: soem technical details are wrong, for instanc SO_REUSEADDR and
SO_REUSEPORT descriptions.

Nits/editorial comments:
 I'll send a full review as soon as I get the time to type it.


From nobody Thu Sep 14 08:45:41 2017
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDE20132F3F for <gen-art@ietfa.amsl.com>; Thu, 14 Sep 2017 08:45:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
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 js-Zi1j9edio for <gen-art@ietfa.amsl.com>; Thu, 14 Sep 2017 08:45:38 -0700 (PDT)
Received: from resqmta-ch2-03v.sys.comcast.net (resqmta-ch2-03v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:35]) (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 3263113291C for <gen-art@ietf.org>; Thu, 14 Sep 2017 08:45:38 -0700 (PDT)
Received: from resomta-ch2-03v.sys.comcast.net ([69.252.207.99]) by resqmta-ch2-03v.sys.comcast.net with ESMTP id sWJoda99hZ53dsWKfdzR9p; Thu, 14 Sep 2017 15:45:37 +0000
Received: from PaulKyzivatsMBP.localdomain ([24.62.227.142]) by resomta-ch2-03v.sys.comcast.net with SMTP id sWKedQQ7pxDGQsWKedmVcr; Thu, 14 Sep 2017 15:45:37 +0000
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
To: draft-spinosa-urn-lex.all@ietf.org
Cc: General Area Review Team <gen-art@ietf.org>
Message-ID: <470a7b0a-ca03-f002-b427-8003e3f7f592@alum.mit.edu>
Date: Thu, 14 Sep 2017 11:45:36 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-CMAE-Envelope: MS4wfLGEdb6eYlMR0K5kCsdnI7TgAR42Qb7GJnO5HrJcddd64QjxblIR+9W0foqf7Q+8ulMoeikCxIM4WKKxclvb/9WCpVsoNNlTUFZ9M07/urY3cyuFDRYR P/UI9fapG1FkU/4Z+8g957rws1L07Z7+WHvsi1qrn4I9L2N1J7HDGksmUUdgGhcYP0sIQv53ekapi/4fenXlC4nkRfO5AxYhtds/eJrb7Z1N5obu7R9ueOSk
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/A9NBHgeHucLGHlIDgZvAaq7-RyU>
Subject: [Gen-art] Gen-ART Last Call review of draft-spinosa-urn-lex-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Sep 2017 15:45:40 -0000

I am the assigned Gen-ART reviewer for this draft. The General Area 
Review Team (Gen-ART) reviews all IETF documents being processed by the 
IESG for the IETF Chair. Please wait for direction from your document 
shepherd or AD before posting a new version of the draft. For more 
information, please see the FAQ at 
<â€‹http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-spinosa-urn-lex-11
Reviewer: Paul Kyzivat
Review Date: 2017-09-14
IETF LC End Date: 2017-09-14
IESG Telechat date: TBD

Summary:

This draft has serious issues, described in the review, and needs to be 
rethought.

General Comments:

I had great difficulty deciding how to approach this review. Rather that 
pick at lots of small points I have elected to focus on the the ones I 
find most notable.

As part of doing this review I investigated prior discussions of prior 
versions of this draft (by Barry Leiba, Patrik FÃ¤ltstrÃ¶m and Dale 
Worley), that have occurred over several *years*. I found some 
substantial issues raised that IMO were not adequately addressed. The 
following is a useful starting point into that discussion:

https://www.ietf.org/mail-archive/web/urn-nid/current/msg01270.html

I have borrowed some points from that discussion and from other 
information that Dale Worley sent privately to you.

Issues:

Major: 2
Minor: 5
Nits:  0

(1) MAJOR: Scope of the document

This document is nominally the specification of a URN. However the 
actual scope of the document is much broader - partially specifying a 
complete system for federating the naming and access to legal documents. 
Much of the contained information goes well beyond what is useful for 
defining the URN, and yet is frustratingly incomplete when it comes to 
defining the broader system.

It would be better to split this into multiple documents. One would 
cover solely the specification of the URN, while the other(s) would 
define the broader system in which the URN operates.

(2) MAJOR: Name or query?

A URN is by definition a *name*. Some parts of this document do focus on 
the lex URN as a name. But the document also proposes using the lex URN 
as a *query*. The following text from section 2 highlights this:

         "To cope with possible incomplete or inaccurate uniform names,
          the implementation of a catalogue, based on a relational-
          database, able to associate a URN to related URLs, is
          suggested, as it will lead to a higher flexibility in the
          resolution process. A resolver can provide names normalization,
          completion of inaccurate or incomplete names, and finally their
          resolution in network locations (see Section 8.2 and 8.3 for
          characteristics and behaviour of a catalogue for resolution)."

This behavior is inconsistent with the intent of URNs.

(3) MINOR: Jurisdiction identifiers:

URNs are required to remain valid indefinitely. But country codes are 
occasionally reassigned. The draft doesn't fully resolve this problem. 
Specifically, section 11.2 doesn't address the case where a request 
comes from a jurisdiction that corresponds to a country and the 
jurisdiction code is the same as a top level ccTLD, which *is* already 
registered for a different entity.

A solution could be to simply follow the rules for a multinational or 
international organization in this case.

The suggestion in section 11.2 to use names of the form '<name>.lex' in 
effect appropriates 'lex' as a TLD, even though it has not been so 
assigned. Or else it presumes that it never will be assigned. This is a 
bad assumption. Some other naming convention should be chosen for this case.

(4) MINOR: Full utility of this URN form as described in this document 
seems to require a browser extension for resolving lex urns, or for urns 
in general. It is not at all clear that such an extension will be widely 
deployed as part of standard browser distributions, limiting this 
function to users who extend their browser with a plugin. And browser 
support for plugins is decreasing. I would hope to see an explanation 
for using lex URNs without such a browser extension.

However, the mechanism for resolving URNs probably belongs in a 
companion document.

(5) MINOR: Use of Punycode

The document calls for use of %-encoding to handle non-ASCII characters. 
The inclusion of %-encoding within <alphanum> allows this widely. 
However, section 4.4 recommends that non-ASCII characters be handled by 
Punycode-encoding them. Because Punycode contains "-" it isn't valid 
according to the current syntax in the many fields that are defined as 
'alfanum *normal'.

The inclusion of Punycode appears to have been an afterthought. If it is 
to be supported then it needs much better specification.

(6) MINOR: Ambiguity between components and features

The syntax for <manifestation>:

               manifestation = format *(";" specification)
                               ":" editor *(";" specification)
                               [":" component *(";" specification)]
                               [":" feature *(";" specification)]

is syntactically ambiguous in that in a form like:

    urn:lex:it:stato:legge:2000-04-03;56
            $application-pdf;1.7:parlamento.it:xxx

it is not clear whether "xxx" is a "component" or a "feature".

(7) MINOR: Purpose of the Attachment D

There are no references to Attachment D within the body of the document, 
and it seems entirely unnecessary to the understanding of the document. 
This ought to be removed - perhaps incorporated into another document 
describing a proposed system for using and resolving lex URNs.


From nobody Thu Sep 14 09:21:55 2017
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23634132D47; Thu, 14 Sep 2017 09:21:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.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 AIwxUL9h0y1p; Thu, 14 Sep 2017 09:21:53 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 2A425127517; Thu, 14 Sep 2017 09:21:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1505406112; d=isode.com; s=june2016; i=@isode.com; bh=bL4cDKBAh5AUqv+7iGX0ziTQw16rTtYaqsunJHt6lYg=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=XpA3b4dk/K4viFIhRwO6a6T0hB5rg048EgxBMFdhLaiCBWcz74lGRQSkyTQ9Qvk80X3Cg1 z6v9T1kiWbeld01jQpt/BxpTISRyR1Mxg9wyuU0z063HLzu3eboKlf12jpCc662P8p12SE O4i3eCkjhkdk2r9uTak1WUO+cP7F5bg=;
Received: from [10.211.83.152] ((unknown) [85.255.232.5])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <WbqsnwBsZrLg@waldorf.isode.com>; Thu, 14 Sep 2017 17:21:52 +0100
X-SMTP-Protocol-Errors: NORDNS PIPELINING
From: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: iPhone Mail (13G35)
In-Reply-To: <470a7b0a-ca03-f002-b427-8003e3f7f592@alum.mit.edu>
Date: Thu, 14 Sep 2017 17:25:01 +0100
Cc: draft-spinosa-urn-lex.all@ietf.org, General Area Review Team <gen-art@ietf.org>
Message-Id: <B21F7E94-7E48-47F6-9109-693496BDED24@isode.com>
References: <470a7b0a-ca03-f002-b427-8003e3f7f592@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/cpDixO8Kk1l_-igYaMYKVyrumzc>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-spinosa-urn-lex-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Sep 2017 16:21:54 -0000

Hi Paul,
I am not an author, but let me disagree with one of your reported issues:

> On 14 Sep 2017, at 16:45, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>=20
> (2) MAJOR: Name or query?
>=20
> A URN is by definition a *name*. Some parts of this document do focus on t=
he lex URN as a name. But the document also proposes using the lex URN as a *=
query*. The following text from section 2 highlights this:
>=20
>        "To cope with possible incomplete or inaccurate uniform names,
>         the implementation of a catalogue, based on a relational-
>         database, able to associate a URN to related URLs, is
>         suggested, as it will lead to a higher flexibility in the
>         resolution process. A resolver can provide names normalization,
>         completion of inaccurate or incomplete names, and finally their
>         resolution in network locations (see Section 8.2 and 8.3 for
>         characteristics and behaviour of a catalogue for resolution)."
>=20
> This behavior is inconsistent with the intent of URNs.

I think the document is only talking about names. Association with URLs is t=
he result of URN resolution process, which is a part of URN architecture. If=
 this is not clear, I think it should be clarified (if authors agree that th=
is is the intent).

Best Regards,
Alexey


From nobody Thu Sep 14 10:04:12 2017
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97EEA1321AC; Thu, 14 Sep 2017 10:04:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 Jep1wq5hzRsZ; Thu, 14 Sep 2017 10:04:09 -0700 (PDT)
Received: from alum-mailsec-scanner-1.mit.edu (alum-mailsec-scanner-1.mit.edu [18.7.68.12]) by ietfa.amsl.com (Postfix) with ESMTP id 653BB126BF0;  Thu, 14 Sep 2017 10:04:09 -0700 (PDT)
X-AuditID: 1207440c-7e5ff7000000143e-0b-59bab68864bc
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by alum-mailsec-scanner-1.mit.edu (Symantec Messaging Gateway) with SMTP id 70.EC.05182.886BAB95; Thu, 14 Sep 2017 13:04:08 -0400 (EDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id v8EH47HH012309 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 14 Sep 2017 13:04:08 -0400
To: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: draft-spinosa-urn-lex.all@ietf.org, General Area Review Team <gen-art@ietf.org>
References: <470a7b0a-ca03-f002-b427-8003e3f7f592@alum.mit.edu> <B21F7E94-7E48-47F6-9109-693496BDED24@isode.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <d9bd361c-e080-ae30-c2cc-b1764b4887d3@alum.mit.edu>
Date: Thu, 14 Sep 2017 13:04:07 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <B21F7E94-7E48-47F6-9109-693496BDED24@isode.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpnleLIzCtJLcpLzFFi42IRYndR1O3YtivSYNE1Q4sZq4ssTq7vZre4 +uoziwOzx5IlP5k8TjUbBjBFcdmkpOZklqUW6dslcGU07LnJXPBAoOLV83nMDYxfeboYOTkk BEwk7l6/wNjFyMUhJLCDSWJP5wVWCOchk8S1C/vYuhg5OIQFHCVu7o0DaRAR0JdY/WoWC4jN LBAj0bZkETOILSRQJPHi+yJWEJtNQEtizqH/YDW8AvYSE+8uBathEVCVeNQwAywuKpAm8W/3 WUaIGkGJkzOfgMU5BWwlzizYyAox30xi3uaHzBC2uMStJ/OZIGx5ie1v5zBPYBSYhaR9FpKW WUhaZiFpWcDIsopRLjGnNFc3NzEzpzg1Wbc4OTEvL7VI11AvN7NELzWldBMjJIx5djB+Wydz iFGAg1GJh1dgwq5IIdbEsuLK3EOMkhxMSqK8e3V3RgrxJeWnVGYkFmfEF5XmpBYfYpTgYFYS 4TXaBFTOm5JYWZValA+TkuZgURLnVV2i7ickkJ5YkpqdmlqQWgSTleHgUJLg1d0K1ChYlJqe WpGWmVOCkGbi4AQZzgM0nB2khre4IDG3ODMdIn+KUZejp+fGHyYhlrz8vFQpoDUgRQIgRRml eXBzYOnnFaM40FvCvCogVTzA1AU36RXQEiagJWdO7wBZUpKIkJJqYCxwW20eESrPPnEDc/S/ //eKpweu3Ju+dhfX99wba6wuak4vU+bqXbub5U9I7NKmErmi+/PWJjBsnfnc4mM9W/qBbbUh F8MLQk3EjyjJFsx6sccrY9Hjy6UH43dHOvU+SiyUWVKScFD05dSrZ1d/KlPR/tvT5GXBkevd /GqbMYe5hYe64z1uJiWW4oxEQy3mouJEAJLjDscaAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/HpqiiQMAUez4EzfPH5cvelGhDhQ>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-spinosa-urn-lex-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Sep 2017 17:04:11 -0000

Hi Alexey,

On 9/14/17 12:25 PM, Alexey Melnikov wrote:
> Hi Paul,
> I am not an author, but let me disagree with one of your reported issues:
> 
>> On 14 Sep 2017, at 16:45, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>>
>> (2) MAJOR: Name or query?
>>
>> A URN is by definition a *name*. Some parts of this document do focus on the lex URN as a name. But the document also proposes using the lex URN as a *query*. The following text from section 2 highlights this:
>>
>>         "To cope with possible incomplete or inaccurate uniform names,
>>          the implementation of a catalogue, based on a relational-
>>          database, able to associate a URN to related URLs, is
>>          suggested, as it will lead to a higher flexibility in the
>>          resolution process. A resolver can provide names normalization,
>>          completion of inaccurate or incomplete names, and finally their
>>          resolution in network locations (see Section 8.2 and 8.3 for
>>          characteristics and behaviour of a catalogue for resolution)."
>>
>> This behavior is inconsistent with the intent of URNs.
> 
> I think the document is only talking about names. Association with URLs is the result of URN resolution process, which is a part of URN architecture. If this is not clear, I think it should be clarified (if authors agree that this is the intent).

I found it very difficult to sort out what was fundamental and normative 
regarding the URN from the parts that are aspirational about resolution 
and use. Hence my recommendation that this document be split. Such a 
split may well resolve this issue for me.

I only pointed to this one place, but there are other places that 
express an intention that it be possible to "guess" or recreate a lex 
URN based on metadata about the document. That only makes sense if then 
intent is that the resulting URN be resolvable to the document. But 
there are so many elements to chosen and used or not for a given 
document that reasonable people are likely to arrive at different forms 
of the URN. That ties in to the quote above.

	Thanks,
	Paul


From nobody Thu Sep 14 11:59:00 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E36BD132403; Thu, 14 Sep 2017 11:58:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
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 IR3rEpVMfEGl; Thu, 14 Sep 2017 11:58:57 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CCC01320D9; Thu, 14 Sep 2017 11:58:57 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 0B5F158C4AF; Thu, 14 Sep 2017 20:58:53 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id E82B3B0CBB7; Thu, 14 Sep 2017 20:58:52 +0200 (CEST)
Date: Thu, 14 Sep 2017 20:58:52 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-mboned-interdomain-peering-bcp.all@ietf.org" <draft-ietf-mboned-interdomain-peering-bcp.all@ietf.org>
Message-ID: <20170914185852.GA27398@faui40p.informatik.uni-erlangen.de>
References: <7594FB04B1934943A5C02806D1A2204B56273EEC@ESESSMB102.ericsson.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B56273EEC@ESESSMB102.ericsson.se>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/v-jphu6VO94ODi72eGCupCORaCA>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-mboned-interdomain-peering-bcp-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Sep 2017 18:58:59 -0000

On Sat, Sep 02, 2017 at 12:16:18PM +0000, Christer Holmberg wrote:
> 
> 
> I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq<https://urldefense.proofpoint.com/v2/url?u=http-3A__wiki.tools.ietf.org_area_gen_trac_wiki_GenArtfaq&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=4Z9x1ZAReZp_mJahI6h9bQ&m=iIo_51LYIireg4AnsuBoZIWVunRNL9x6ZXHqz5Q2CGc&s=peDTnfOaiDiT8_m4J-VWJr70Nt0m41lLVGq3yYls12k&e=>>
> 
> Minor Issues:
> 
> Q1: The Introduction talks about the growing usage of multicast, and the it begins the list what the document does. But, what is the background and need for the document? Is there a problem? Are there interoperability issues? At the end of the section it is said that ways to improve are identified, but it is unclear exactly what needs to be improved. I think it would be good to say a few words in the Introduction about the issues and problems.

I am a bit at a loss. This is a BCP, eg: it is meant to document current best practices.
It is not meant to suggest "improvements" for protocols or the like. The abstract and
intro do IMHO pretty well stsate the intent and purpose of the doc. 

Maybe its just surprising to you that there has so far been no document to describe how
to deploy IP multicast interdomain, especially with the inclusion of of options such
as GRE and AMT - and simplifying it by only using SSM ??

Or else: Do you have any text to propose ?

> Editorial Issues:
> 
> 
> 
> Q2: The title of section 4 is ?Supporting Functionality?. That seems a little strange in my eyes. Supporting functionality of what?
> 
All the subsections are called "<function-foobar> Guidlines", so how about wee call the whole section "Functional Guidelines" ?

Cheers
    Toerless

---
tte@cs.fau.de


From nobody Thu Sep 14 14:25:18 2017
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D1B22120724 for <gen-art@ietf.org>; Thu, 14 Sep 2017 14:25:16 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jean Mahoney <mahoney@nostrum.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.61.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-to: mahoney@nostrum.com
Message-ID: <150542431681.18982.14224199804569584827.idtracker@ietfa.amsl.com>
Date: Thu, 14 Sep 2017 14:25:16 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/tNcSyyPuNO4CpvpYjgeW1GA1Jls>
Subject: [Gen-art] Review Assignments
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Sep 2017 21:25:17 -0000

Hi all,

The following reviewers have assignments:

For telechat 2017-09-28

Reviewer               Type      LC end     Draft
Elwyn Davies           Last Call 2017-09-22 draft-ietf-teas-rsvp-te-scaling-rec-06
Paul Kyzivat           Telechat  2017-06-28 draft-baeuerle-netnews-cancel-lock-06 *
Dan Romascanu          Last Call 2017-09-20 draft-ietf-bier-architecture-08 *

Last calls:

Reviewer               Type      LC end     Draft
Jari Arkko             Last Call 2017-10-11 draft-wu-l3sm-rfc8049bis-04
Stewart Bryant         Last Call 2017-09-27 draft-kille-ldap-xmpp-schema-05
Brian Carpenter        Last Call 2017-09-25 draft-ietf-grow-bgp-session-culling-04
Linda Dunbar           Last Call 2017-09-28 draft-ietf-ippm-alt-mark-10
Orit Levin             Last Call 2017-09-26 draft-ietf-v6ops-rfc6555bis-04
Meral Shirazipour      Last Call 2017-09-15 draft-ietf-6man-maxra-03
Robert Sparks          Last Call 2017-09-20 draft-ietf-opsawg-service-model-explained-03

* Other revision previously reviewed
** This revision already reviewed

Next in the reviewer rotation:

  Francis Dupont
  Roni Even
  Fernando Gont
  Vijay Gurbani
  Wassim Haddad
  Joel Halpern
  Christer Holmberg
  Russ Housley
  Jouni Korhonen
  Paul Kyzivat

The LC and Telechat review templates are included below:
-------------------------------------------------------

-- Begin LC Template --
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments: 

-- End LC Template --

-- Begin Telechat Template --
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

-- End Telechat Template --



From nobody Fri Sep 15 06:37:24 2017
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 343251332CD; Fri, 15 Sep 2017 06:37:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 NFULKj_rpe7c; Fri, 15 Sep 2017 06:37:20 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DBC9133226; Fri, 15 Sep 2017 06:37:20 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [IPv6:::1]) by givry.fdupont.fr (8.14.7/8.14.7) with ESMTP id v8FDILVx076578; Fri, 15 Sep 2017 15:18:21 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201709151318.v8FDILVx076578@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Cc: draft-ietf-taps-transports-usage-udp.all@ietf.org
Date: Fri, 15 Sep 2017 15:18:21 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/reqcba916dmcBAMvxSN-jmhaovY>
Subject: [Gen-art] review of draft-ietf-taps-transports-usage-udp-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Sep 2017 13:37:23 -0000

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-taps-transports-usage-udp-06.txt
Reviewer: Francis Dupont
Review Date: 2017-09-14
IETF LC End Date: done
IESG Telechat date: 2017-09-14

Summary: In the Right Track

Major issues: None

Minor issues:
 - SO_REUSEADDR and SO_REUSEPORT descriptionss are incorrect (see below).
   BTW they are in the introduction so it is very minor but incorrect
   (or misinterpreted to stay polite) definition of SO_REUSEADDR made
   enough damage to want to stop it.

Nits/editorial comments:
 - TOC page 2 and 4 page 12: Acknowledgements -> Acknowledgements???
  (according to ispell with the US dict. I tried the GB one too
   and it gave less errors so now I assume you'd like to keep the
   spelling from this side of the ocean :-).

 - 1 page 2: The de facto standard: usually IEEE acts by delegation
  of the ISO so it can be in fact "de jure". I suggest to remove the
  "de facto" which can only bring useless (and unrelated) arguments...

 - 1 page 3: The SO_REUSEADDR description is fully wrong:
   this socket option is about conflicts (formal definition
   a conflict happens when a received packet matches more than one
   socket, in practice as CONNECT does an implicit (and conflict free)
   BIND it is only for BIND so local address *and* port with the same
   port, and equal addresses or an address being any/wildcard).
   Only the SO_REUSEADDR set to 0/no is really defined: the call
   to BIND by the second socket fails. The behavior on 1/yes is
   to fail if the conflict can't be solved (same addresses) in BSDs
   and derived system, and to never fail (i.e., the conflict detection
   is disabled) on Linux.
   I propose to change:
   o  SO_REUSEADDR specifies the rules for validating addresses supplied
      to bind() should allow reuse of local addresses.

   into

   o  SO_REUSEADDR specifies the rules for validating addresses supplied
      to bind() should allow conflicts on reuse of local addresses and
      ports.

  - 1 page 3: SO_REUSEPORT is a very different beast which unfortunately
    got a (far too) close name. I know at least 4 cases:
     * no defined in system headers
     * defined as being an alias of SO_REUSEADDR
     * defined but not supported (silly isn't it? but there is a popular
       system doing exactly this!)
     * defined using the original/BSD behavior: this socket option
    is for multicast applications and means received packets must be
    duplicated and delivered to all "matching" applications which
    must set to 1 the option (another difference with SO_REUSEADDR where
    the first application is not required to set it).

    I have no good proposal, perhaps the best is to move it to the
    multicast annex. BTW if you need a good reference (and a source
    of good text about SO_REUSE*) I highly recommend the Stevens book
    (not the API one by the "TCP/IP Illustrated volue 2", in my copy
    it is in PCB chapter page 720.

  - 1 page 3: I disagree about raw sockets: you must insist on
    the fact a raw socket bound to the known UDP protocol is able
    to *only* send packets, *never* to receive packets which are
    demultiplexed to the UDP protocol handler.

  - 1 page 3: insert a space in "in[I-D.ietf-taps-t...]"

  - 2 pages 3 and 4: I have a concern with the wording about
    the use of RFC 2119 words. In fact this document never uses
    directly these words but cites fragments of reference(d) RFCs
    which use them. So IMHO the "but does not itself define new terms."
    should be improved.

  - 3 page 4: "datagram services that preserve message boundaries."
    IMHO it is a pleonasm. I'd prefer to get connectionless in place
    of "preserve message boundaries" even it can be considered as
    a (common :-) pleonasm too. BTW the author of the "datagram" term
    is still on the Internet so you can ask him...

  - 3 page 4: summarizes -> summarises

  - 3.1 pages 5 and 8 (SET_DF, GET_MMS_S): packetization -> packetisation
    (and Packetization -> Packetisation)

  - 3.1 page 6: the LISTEN primitive is not defined for UDP. IMHO
    it is more a wording issue than a defect, i.e., you know (and state?)
    that the CONNECT primitive must be used instead (note I wrote must,
    not should, cf the question mark).

  - 3.1.1 page 9 (GET_TTL, SET_MIN_TTL) and A page 17 (IP_MULTICAST_TTL):
    Generalized -> Generalised

  - 3.1.1 page 11: I believe the GET_SRCADDR is excluded because it is
    available in the RECEIVE (recvfrom()/recvmsg()) primitive so
    no longer a primitive, isn't it?  

  - A page 19: you have twice MCAST_LEAVE_GROUP: this looks like
    a bad cut & paste, i.e., there is a missing SOURCE.

Two other points: I'll send your draft to my ISC colleagues as
the bind DNS server could be a significant source of UDP traffic over
the Internet. And if you have no Microsoft/Winsock person in
reviewers I recommend to contact one as if it is POSIX API it can have
interesting/to-notice difference.

Regards

Francis.Dupont@fdupont.fr


From nobody Fri Sep 15 11:27:36 2017
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EBE7133529; Fri, 15 Sep 2017 11:27:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 PZ7FdHKvIeZK; Fri, 15 Sep 2017 11:27:33 -0700 (PDT)
Received: from alum-mailsec-scanner-7.mit.edu (alum-mailsec-scanner-7.mit.edu [18.7.68.19]) by ietfa.amsl.com (Postfix) with ESMTP id 75262132D54;  Fri, 15 Sep 2017 11:27:33 -0700 (PDT)
X-AuditID: 12074413-3a3ff70000007929-a9-59bc1b94b2be
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by alum-mailsec-scanner-7.mit.edu (Symantec Messaging Gateway) with SMTP id A8.BE.31017.49B1CB95; Fri, 15 Sep 2017 14:27:32 -0400 (EDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id v8FIRUpZ025074 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 15 Sep 2017 14:27:31 -0400
To: Enrico Francesconi <enrico.francesconi@gmail.com>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, draft-spinosa-urn-lex.all@ietf.org, General Area Review Team <gen-art@ietf.org>
References: <470a7b0a-ca03-f002-b427-8003e3f7f592@alum.mit.edu> <B21F7E94-7E48-47F6-9109-693496BDED24@isode.com> <d9bd361c-e080-ae30-c2cc-b1764b4887d3@alum.mit.edu> <B3FC1E30-EF22-4A98-A902-3BDAB0534284@gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <d52b7940-3c69-02b7-e62a-bdb949e89f57@alum.mit.edu>
Date: Fri, 15 Sep 2017 14:27:30 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <B3FC1E30-EF22-4A98-A902-3BDAB0534284@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprMKsWRmVeSWpSXmKPExsUixO6iqDtFek+kwar3mhYzVhdZnFzfzW7R v/8Lm8XVV59ZHFg8ds66y+6xZMlPJo9TzYYBzFFcNimpOZllqUX6dglcGU1L/zAVnNGreHjr E0sD40+VLkZODgkBE4kJHevZuhi5OIQEdjBJLF72kxXCecgk0bLlPXMXIweHsICjxM29cSAN IgKmEm8mTmcHqWEWmMQocePMPyaIhtuMEuvmv2IEqWIT0JKYc+g/C4jNK2AvcXn5dSYQm0VA VeL41g52EFtUIE3i3+6zjBA1ghInZz4Bq+cUsJX43D6NGcRmFjCTmLf5IZQtLnHryXwmCFte onnrbOYJjAKzkLTPQtIyC0nLLCQtCxhZVjHKJeaU5urmJmbmFKcm6xYnJ+blpRbpmuvlZpbo paaUbmKEhLfwDsZdJ+UOMQpwMCrx8DZc3h0pxJpYVlyZe4hRkoNJSZS3TGpPpBBfUn5KZUZi cUZ8UWlOavEhRgkOZiUR3iRhoBxvSmJlVWpRPkxKmoNFSZxXbYm6n5BAemJJanZqakFqEUxW hoNDSYL3E8hQwaLU9NSKtMycEoQ0EwcnyHAeoOGzQWp4iwsSc4sz0yHypxh1OXp6bvxhEmLJ y89LlRLn3QZSJABSlFGaBzcHlpZeMYoDvSXM6wBMUkI8wJQGN+kV0BImoCVnTu8AWVKSiJCS amAsDtc13hsy+aH+9MJbGzo/pu/f2cT82lA8NSGkkHffvjKZaLM062UeC81aX25dExJ2qH4m 8/rHlVUnjR792CcX8Yv5WXZzm1/ebFcNSZXa18zVe3/oygX//BDpe4Dvp5jvH/PsrSlds8Pn Mb4KWLlEe/7fNWnaoc9enD58tsNY/7/BJ/vlhtOVWIozEg21mIuKEwHE2nApJgMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/qW9rTp_2KTKVC_bzejKm7dt8f2Q>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-spinosa-urn-lex-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Sep 2017 18:27:35 -0000

Enrico,

On 9/15/17 12:03 PM, Enrico Francesconi wrote:
> Dear Paul and Alexey,
>     thanks for your remarks. We are pleased to work with you to fix all the issues still remaining in the current urn:lex version.
> 
> As regards the quoted issue on names or queries, the urn:lex draft actually talks about names. As pointed out by Alexey, any reference to queries is meant to clarify the principles of the resolution process for urn:lex, moreover the section â€œresolutionâ€� is expected in the draft template.
> 
> As regards Paulâ€™s remarks on the possibility to arrive at different forms of urn:lex starting from document metadata, this is actually meant to facilitate interoperability. A typical example is the possibility to create equivalent urn:lex names in different languages. Moreover, the addressed flexibility is also meant to cope with promoting interoperability when, for example, it is necessary to link legal resources from incomplete textual citations. In this case the suggested behavior of the resolution system can facilitate the discovery of the target resource.

I still have trouble understanding this except as a form of query.

Let me try to explain. I'm drawing a distinction between two classes of 
users for these URNs:

1) The authority who is formally assigning lex URNs to documents. The 
authority can choose which of the various optional parts of the urn are 
applicable to a given document. A question is whether the goal of the 
authority should be to choose the "best" name for the document, or 
should attempt to assign every possible name that any reasonable person 
might guess to be the name of the document.

2) Someone interested in referencing the document. Some people may only 
be interested in obtaining a name to use to point at the document, but 
that always implies an assumption that someone will want to retrieve the 
document using that name, so I'll assume that the goal here is to 
retrieve the document.

2a) One possibility is that this person is given the name by someone who 
obtained it directly from (1), so that it is known to refer to a document.

2b) This person is aware of some metatdata about the document, and 
attempts to independently construct a URN identifying the document from 
this metatdata. (I take this to be an important use case from the point 
of view of the draft.) In this case, this person may get lucky and come 
up with an identical URN to one assigned by (1). On the other hand, 
given the number of possible optional fields, he may not be so lucky. 
His chances are better if (1) attempted to define every imaginable 
permutation, but that is a lot of work and I doubt one can count on this.

You imply an environment where such an undefined URN can be resolved by 
a smart resolver. But in this case the input URN is not actually a URN 
to the document in question - it is a query for some document. And that 
is my point.

ISTM that the definition of the URN should be concerned with (1) and 
(2a). But as I read the draft it certainly feels to me that it has a 
heavy concern for (2b).

	Thanks,
	Paul

> For the other issues raised, we will analyse them in details and get back to you soon.
> 
> Best regards
>     Pierluigi and Enrico
> 
> 
> 
> ---------------------------------------------------------
> Enrico Francesconi
> ITTIG - CNR
> Institute of Legal Information Theory and Techniques
> Italian National Research Council
> 
> Via de' Barucci 20
> 50127 Florence
> Italy
> 
> Tel: +39-055-4399-665
> Fax: +39-055-4399-605
> email: francesconi@ittig.cnr.it
> ---------------------------------------------------------
> 
>> On 14 set 2017, at 19:04, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>>
>> Hi Alexey,
>>
>> On 9/14/17 12:25 PM, Alexey Melnikov wrote:
>>> Hi Paul,
>>> I am not an author, but let me disagree with one of your reported issues:
>>>> On 14 Sep 2017, at 16:45, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>>>>
>>>> (2) MAJOR: Name or query?
>>>>
>>>> A URN is by definition a *name*. Some parts of this document do focus on the lex URN as a name. But the document also proposes using the lex URN as a *query*. The following text from section 2 highlights this:
>>>>
>>>>         "To cope with possible incomplete or inaccurate uniform names,
>>>>          the implementation of a catalogue, based on a relational-
>>>>          database, able to associate a URN to related URLs, is
>>>>          suggested, as it will lead to a higher flexibility in the
>>>>          resolution process. A resolver can provide names normalization,
>>>>          completion of inaccurate or incomplete names, and finally their
>>>>          resolution in network locations (see Section 8.2 and 8.3 for
>>>>          characteristics and behaviour of a catalogue for resolution)."
>>>>
>>>> This behavior is inconsistent with the intent of URNs.
>>> I think the document is only talking about names. Association with URLs is the result of URN resolution process, which is a part of URN architecture. If this is not clear, I think it should be clarified (if authors agree that this is the intent).
>>
>> I found it very difficult to sort out what was fundamental and normative regarding the URN from the parts that are aspirational about resolution and use. Hence my recommendation that this document be split. Such a split may well resolve this issue for me.
>>
>> I only pointed to this one place, but there are other places that express an intention that it be possible to "guess" or recreate a lex URN based on metadata about the document. That only makes sense if then intent is that the resulting URN be resolvable to the document. But there are so many elements to chosen and used or not for a given document that reasonable people are likely to arrive at different forms of the URN. That ties in to the quote above.
>>
>> 	Thanks,
>> 	Paul
> 
> 


From nobody Fri Sep 15 13:43:18 2017
Return-Path: <enrico.francesconi@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83766132D4B; Fri, 15 Sep 2017 09:03:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 CgKBFQ1HaL7t; Fri, 15 Sep 2017 09:03:18 -0700 (PDT)
Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B8441321A4; Fri, 15 Sep 2017 09:03:18 -0700 (PDT)
Received: by mail-wm0-x22a.google.com with SMTP id i189so9547290wmf.1; Fri, 15 Sep 2017 09:03:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=raZ7iBR8juxSdZeUTv8HThqIPjeRVrHMMk1jLZA/q48=; b=QuM64W1xTqdeiHA5YpWBSmYPzyQ9wx+6AHb5DVkSWPv7S8/ygrnUNYEn86XlwLNQOU tQ2NE53hQ+tDa4fbG1zL/FN3OD6ZTeu9OWOtWVJmWIgNd6YMMcRlmC6JZ9enZ8W5FAaw MIuXbdPFijfx7zi6aOnqKpDWhLiPBkum7j3FwJ6nG89i0cVr0dyqWej3Oz5BjjM0Q8ev 1qNodv9gN8MePpjS2lWIuIsoxPNGqm217Xu7U7xvK93NhSMYFCo4uql1+ARWjNak/flO +1rmNPVgbIwTNByzlJvsIm10G3DgGuFgMZBB6LVY4oyp76kaCipt0Mh9hNV6nKNqXxeO SETA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=raZ7iBR8juxSdZeUTv8HThqIPjeRVrHMMk1jLZA/q48=; b=ouiPn8v78mT1aSDqTA/FXkFNmww94IGYKiV7XIAabR09Kb1jdS1JgPunMuOOujWoL0 ZJbH9vcFcmnMKOnWELM18GJXXuKR2fOn2at4fCt9KnwRi8ig4r2wpwYUCREnKP68e+K4 9ChC8cLpEGCssB/Gao80xXsj91sqhukBmCcQnC+kPrxaNbDcfFZR/zwGQ1kxCE/ZGFla 1STzXR1x/ODgV/jvMcnblDiL7PjBjtZr6xxFW15ojUWjSDdCzPm+ph9kBEk8JuV/vzM6 YrPCHftHFUcIGp+Hp5n47KRc22e1YERwxeqyU7F1EgPTXALVGjoP95klwf26ZjGOokMg Av/g==
X-Gm-Message-State: AHPjjUi7FvIDxnZMt00l8/y7RILHEvWRBOsY012pHHR9eBiAQZoGmPwM 4qaXn4Kre9z75Fhav2Oge6c=
X-Google-Smtp-Source: AOwi7QDA4ftjhKBJn+OngiRQyf78DNJWPBng9EN4L2YKzzhIe217V7/Fe/HfYrzSRPR6tUAJiEoPBQ==
X-Received: by 10.28.232.138 with SMTP id f10mr187489wmi.130.1505491396635; Fri, 15 Sep 2017 09:03:16 -0700 (PDT)
Received: from air-di-enrico.homenet.telecomitalia.it (host136-125-dynamic.46-79-r.retail.telecomitalia.it. [79.46.125.136]) by smtp.gmail.com with ESMTPSA id y84sm861105wmg.43.2017.09.15.09.03.13 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 15 Sep 2017 09:03:13 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.0 \(3094\))
From: Enrico Francesconi <enrico.francesconi@gmail.com>
In-Reply-To: <d9bd361c-e080-ae30-c2cc-b1764b4887d3@alum.mit.edu>
Date: Fri, 15 Sep 2017 18:03:12 +0200
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, draft-spinosa-urn-lex.all@ietf.org, General Area Review Team <gen-art@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B3FC1E30-EF22-4A98-A902-3BDAB0534284@gmail.com>
References: <470a7b0a-ca03-f002-b427-8003e3f7f592@alum.mit.edu> <B21F7E94-7E48-47F6-9109-693496BDED24@isode.com> <d9bd361c-e080-ae30-c2cc-b1764b4887d3@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.3094)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/4knf2dUpDGLSRokcdQQr13fYS2o>
X-Mailman-Approved-At: Fri, 15 Sep 2017 13:43:16 -0700
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-spinosa-urn-lex-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Sep 2017 16:03:20 -0000

Dear Paul and Alexey,
   thanks for your remarks. We are pleased to work with you to fix all =
the issues still remaining in the current urn:lex version.

As regards the quoted issue on names or queries, the urn:lex draft =
actually talks about names. As pointed out by Alexey, any reference to =
queries is meant to clarify the principles of the resolution process for =
urn:lex, moreover the section =E2=80=9Cresolution=E2=80=9D is expected =
in the draft template.

As regards Paul=E2=80=99s remarks on the possibility to arrive at =
different forms of urn:lex starting from document metadata, this is =
actually meant to facilitate interoperability. A typical example is the =
possibility to create equivalent urn:lex names in different languages. =
Moreover, the addressed flexibility is also meant to cope with promoting =
interoperability when, for example, it is necessary to link legal =
resources from incomplete textual citations. In this case the suggested =
behavior of the resolution system can facilitate the discovery of the =
target resource.

For the other issues raised, we will analyse them in details and get =
back to you soon.

Best regards
   Pierluigi and Enrico



---------------------------------------------------------
Enrico Francesconi
ITTIG - CNR
Institute of Legal Information Theory and Techniques
Italian National Research Council

Via de' Barucci 20
50127 Florence
Italy

Tel: +39-055-4399-665
Fax: +39-055-4399-605
email: francesconi@ittig.cnr.it
---------------------------------------------------------

> On 14 set 2017, at 19:04, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>=20
> Hi Alexey,
>=20
> On 9/14/17 12:25 PM, Alexey Melnikov wrote:
>> Hi Paul,
>> I am not an author, but let me disagree with one of your reported =
issues:
>>> On 14 Sep 2017, at 16:45, Paul Kyzivat <pkyzivat@alum.mit.edu> =
wrote:
>>>=20
>>> (2) MAJOR: Name or query?
>>>=20
>>> A URN is by definition a *name*. Some parts of this document do =
focus on the lex URN as a name. But the document also proposes using the =
lex URN as a *query*. The following text from section 2 highlights this:
>>>=20
>>>        "To cope with possible incomplete or inaccurate uniform =
names,
>>>         the implementation of a catalogue, based on a relational-
>>>         database, able to associate a URN to related URLs, is
>>>         suggested, as it will lead to a higher flexibility in the
>>>         resolution process. A resolver can provide names =
normalization,
>>>         completion of inaccurate or incomplete names, and finally =
their
>>>         resolution in network locations (see Section 8.2 and 8.3 for
>>>         characteristics and behaviour of a catalogue for =
resolution)."
>>>=20
>>> This behavior is inconsistent with the intent of URNs.
>> I think the document is only talking about names. Association with =
URLs is the result of URN resolution process, which is a part of URN =
architecture. If this is not clear, I think it should be clarified (if =
authors agree that this is the intent).
>=20
> I found it very difficult to sort out what was fundamental and =
normative regarding the URN from the parts that are aspirational about =
resolution and use. Hence my recommendation that this document be split. =
Such a split may well resolve this issue for me.
>=20
> I only pointed to this one place, but there are other places that =
express an intention that it be possible to "guess" or recreate a lex =
URN based on metadata about the document. That only makes sense if then =
intent is that the resulting URN be resolvable to the document. But =
there are so many elements to chosen and used or not for a given =
document that reasonable people are likely to arrive at different forms =
of the URN. That ties in to the quote above.
>=20
> 	Thanks,
> 	Paul


From nobody Sun Sep 17 23:11:52 2017
Return-Path: <worley@alum.mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1154113306A for <gen-art@ietfa.amsl.com>; Sun, 17 Sep 2017 23:11:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level: 
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
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 cztZVsW2hTTz for <gen-art@ietfa.amsl.com>; Sun, 17 Sep 2017 23:11:50 -0700 (PDT)
Received: from resqmta-po-04v.sys.comcast.net (resqmta-po-04v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:163]) (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 0999A13305F for <gen-art@ietf.org>; Sun, 17 Sep 2017 23:11:50 -0700 (PDT)
Received: from resomta-po-16v.sys.comcast.net ([96.114.154.240]) by resqmta-po-04v.sys.comcast.net with ESMTP id tpHQdrqs0GK63tpHZdnVyB; Mon, 18 Sep 2017 06:11:49 +0000
Received: from hobgoblin.ariadne.com ([73.53.57.65]) by resomta-po-16v.sys.comcast.net with SMTP id tpHXdzV6nLKGOtpHYd9kP2; Mon, 18 Sep 2017 06:11:49 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v8I6Bl5U004786; Mon, 18 Sep 2017 02:11:47 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v8I6BkAS004776; Mon, 18 Sep 2017 02:11:46 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Cc: enrico.francesconi@gmail.com, draft-spinosa-urn-lex.all@ietf.org, gen-art@ietf.org
In-Reply-To: <d52b7940-3c69-02b7-e62a-bdb949e89f57@alum.mit.edu> (pkyzivat@alum.mit.edu)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Mon, 18 Sep 2017 02:11:46 -0400
Message-ID: <87zi9sedst.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfMPCHNLjc2ZUE6YpB8A/JTUj3pz2azvn9HEIHhUbFyiSQqMaIE5J0RVG+uZprAz6PmM2MxxJKFoQjocPiuh3ZzEXeSgaPgldhhICGyrf78aG21sgDhU8 Qs0wqETI0PeYgQY4/bYntKCpnu3CrBFi8AyzOUaJIlv0S7bk86HvF2U75b9cjguzGMsUPdQe5duu26GzsZ1IT6Zkexb2/+i7o2sRq8TktCQrWSJxfbYUx7MT qlOQ7IL41DteSVhlDHNhnU0pSPzyKGDQhXkanIOYfigQyNmXk91E+WtAofq8DTA8
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/-a7l6jxYfQTdIF-9FLYgcSxKK4g>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-spinosa-urn-lex-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Sep 2017 06:11:51 -0000

Let me speak in favor of draft-spinosa-urn-lex.

My understanding of the intention of the draft is essentially the
creation of a universal system for bibliographic citations of legal
works, using the syntax of URNs to express the citations.  This
understanding colors how I think about the namespace proposal.

The intention seems to be that every document is assigned one or more
URNs by a governing jurisdiction, or by a publisher of a version of the
document.  Note a point that I did not understand until recently, that
the uniqueness rule for URNs permits multiple URNs to refer to one same
resource.  As the authors note, one use of this is providing references
to a document which are based on multiple natural languages.

The resolution process for assigned URNs is a typical indirection
system, where the URN is looked up in a database.  However, the system
supports a usage that is much more like other library or bibliographic
systems -- the user can compose the information that he knows about the
document into an "approximate" URN which can be searched for in a
database using a "closest match" rule, which both converts the queried
URN into an assigned URN and provides information about the document
itself.  In this usage, the user-composed URNs are fundamentally
equivalent to queries.

The current draft does not clearly separate the information about the
query/resolution process.  It would be helpful if the resolution
information were in a separate section, as the registration template
format in RFC 8141 recommends.  It would also be helpful if there was a
clear distinction between the parts of the resolution process that are
well-defined and fixed, and (IIRC) some information which has not been
firmly fixed.

However, the messy part is the user-created "query" URNs.  To get these
within the formal rules for URN namespaces, we need to recognize them as
a special subclass whose definition does not come from assignment to a
document by an authority, but rather from the namespace definition
itself, in a clause somewhat like:

    A URN that is not assigned to a document is defined to represent a
    query into the universe of URNs that have been assigned to
    documents, whose resolution is current set of assigned URNs that
    most closely match the URN.

Clearly, there are some rough edges to that.  But the meaning of a URN
is time-invariant as a query, despite that the results of the query
depend on the time.  And when a URN is assigned to a document, the URN
is equivalently a query that returns just that one document (since it is
a perfect match to itself as an assigned URN).

Some of this reasoning is a stretch, but (a) I've written URN definitions
that aren't perfectly compatible with RFC 8141, and (b) this pattern of
definition and usage seems to be ideal for handling bibliographic
references.

So I think the overall concept is good and useful, though the
presentation needs to be cleaned up in the ways that we've been
discussing.

Dale


From nobody Mon Sep 18 14:15:20 2017
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22F75132D89; Mon, 18 Sep 2017 14:15:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 69GjxHg5fvxc; Mon, 18 Sep 2017 14:15:16 -0700 (PDT)
Received: from alum-mailsec-scanner-2.mit.edu (alum-mailsec-scanner-2.mit.edu [18.7.68.13]) by ietfa.amsl.com (Postfix) with ESMTP id 6B1BD132153;  Mon, 18 Sep 2017 14:15:16 -0700 (PDT)
X-AuditID: 1207440d-853ff70000000f42-17-59c0374ee5de
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by alum-mailsec-scanner-2.mit.edu (Symantec Messaging Gateway) with SMTP id E8.72.03906.E4730C95; Mon, 18 Sep 2017 17:14:54 -0400 (EDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id v8ILErKB007774 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 18 Sep 2017 17:14:54 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
To: draft-baeuerle-netnews-cancel-lock.all@ietf.org
References: <9be2e7af-b99d-4f86-6552-bfada936600d@alum.mit.edu> <20170707174750.487009ed@WStation4> <7452e826-62e9-0d6e-32b5-dcdefcb4c2ea@alum.mit.edu> <20170711203934.458e3b62@WStation4> <37001dcd-6551-78b4-18e7-75fbebaff761@alum.mit.edu>
Cc: General Area Review Team <gen-art@ietf.org>
Message-ID: <0147f247-2763-8017-f123-5cdd6ceb06b3@alum.mit.edu>
Date: Mon, 18 Sep 2017 17:14:53 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <37001dcd-6551-78b4-18e7-75fbebaff761@alum.mit.edu>
Content-Type: text/plain; charset=iso-8859-15; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrPIsWRmVeSWpSXmKPExsUixO6iqOtnfiDS4MNLM4v2FV+YLK6++szi wOSxZMlPpgDGKC6blNSczLLUIn27BK6MeweOMBf8DK748389WwPjHOcuRk4OCQETiYbp89i6 GLk4hAR2MEm8+jWVCcJ5yCSx9+dNJpAqNgEtiTmH/rN0MbJzCAu4SywpB4mKCBhLTDq6lQWi /DujxJZXIIM4OZgF9CX+PlkM1sorYC/xYfZPVhCbRUBV4sj3a2C2qECaxL/dZxkhagQlTs58 wgJicwo4SLQd7GKEmGMjcW7rcRYIW1zi1pP5TBC2vETz1tnMExgFZiFpn4WkZRaSlllIWhYw sqxilEvMKc3VzU3MzClOTdYtTk7My0st0jXSy80s0UtNKd3ECAlb3h2M/9fJHGIU4GBU4uEV uLY/Uog1say4MvcQoyQHk5Ior2gkUIgvKT+lMiOxOCO+qDQntfgQowQHs5IIb7L8gUgh3pTE yqrUonyYlDQHi5I4r9oSdT8hgfTEktTs1NSC1CKYrAwHh5IEr5IZUKNgUWp6akVaZk4JQpqJ gxNkOA/Q8P+mIMOLCxJzizPTIfKnGHU5enpu/GESYsnLz0uVEufVBxkkAFKUUZoHNweWbl4x igO9JczLD1LFA0xVcJNeAS1hAlrSsmMPyJKSRISUVAPjLPnDGel2r/Y0h9vFXD5fEajcHNRo JjWp6PQelai8gMVbZ4jfvfm1Q9jjS+1Rv7+OF85P9Dn32O3U3AMaRZV22TZJ/3UyJkrGim3Y fHTiXWMxT4F8xvYXrUdM9rwX/W72zkj8JZNizFQvrWcrIqbXx7zi4Mw4nF/Xe0TYRXKu6P19 /usZDqUpsRRnJBpqMRcVJwIAxKfpbxIDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/iNvnBFs0kzFeA1ugvHKjnW0a0RI>
Subject: Re: [Gen-art] draft-baeuerle-netnews-cancel-lock-06 and RFCs 5536 & 5322
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Sep 2017 21:15:19 -0000

I'm on tap to do the genart telechat review on 
draft-baeuerle-netnews-cancel-lock-06. I see that nothing has been done 
about the ABNF that was my primary concern in my prior wglc review of -05:

https://mailarchive.ietf.org/arch/msg/gen-art/wXKa5tadbo_xQbbUUCk9RZyB0w8

I'm told by the authors that Alexey asked that it be submitted this way, 
but the ABNF *is* wrong, and I can't see how a new draft can be allowed 
to be published with knowingly wrong ABNF. OTOH, the problem didn't 
originate with this draft. Rather the problem originated with RFC5536, 
and this draft has simply built on that mistake. Unfortunately the root 
of the problem is with RFC5322, since its ABNF is structured in a way 
that makes it really hard to define extensions such as those in RFC5536 
and this draft. So the cleanest solution I can see is to revise both 
5322 and 5536, and then this draft can build on those changes. That is a 
rather involved fix but I don't see any other reasonable way.

This prompted me to submit an erratum (#5116) on RFC5536 regarding this 
issue. But errata aren't often acted on quickly when they require 
revising RFCs.

The question is: in the meantime, what to do about this draft? By 
default I guess I will simply restate the issue in my genart telechat 
review and leave it for the IESG discuss it.

Anybody have a better idea?

	Thanks,
	Paul

On 7/14/17 12:58 PM, Paul Kyzivat wrote:
> Michael,
> 
> Please see further comments inline.
> 
> (Sorry - the indenting is getting deep, but I think we are pretty much 
> done.)
> 
> On 7/11/17 2:39 PM, Michael Bäuerle wrote:
>> Paul Kyzivat wrote:
>>> On 7/7/17 11:47 AM, Michael Bäuerle wrote:
>>>> Paul Kyzivat wrote:
>>>>>
>>>>> [...]
>>>>> General Comments:
>>>>>
>>>>> I have not attempted to validate the security properties of this
>>>>> document - leaving that to a security review.
>>>>>
>>>>> I have also not attempted to verify the operational suitability of 
>>>>> this
>>>>> mechanism because I don't have the experience needed to do so.
>>>>>
>>>>> Issues:
>>>>>
>>>>> Major: 1
>>>>> Minor: 3
>>>>> Nits:  0
>>>>>
>>>>> (1) MAJOR:
>>>>>
>>>>> [Problem with ABNF syntax of header fields]
>>>>
>>>> Hi Paul,
>>>>
>>>> Julien Élie has proposed a new syntax definition.
>>>
>>> I was copied on his mail proposing a change to RFC5536, and that is
>>> tentative. *This* document would of course require a similar change. Or
>>> else it could extend that change, via something like
>>>
>>>     news-fields =/ cancel-lock / cancel-key
>>>
>>> But that can only be done if there is actually a draft that revises 5536
>>> that can then be referenced. Bottom line is that it seems there needs to
>>> be some coordination of that fix with this draft.
>>
>> It's clear that the Cancel-Lock draft needs to be changed. My comment
>> was about the potential erratum for RFC 5536 and the question:
>> Is it (in general) possible to reference a modified ABNF definition in
>> an erratum?
> 
> I don't know of any way to do so. Perhaps somebody else can provide a 
> more definitive answer. You might try asking on rfc-interest.
> 
>> If this is possible, then the current:
>>
>>     fields =/ *( cancel-lock / cancel-key )
>>
>> can be changed to:
>>
>>     news-fields =/ cancel-lock / cancel-key
>>
>> and should then reference the new ABNF from the erratum.
>> If not, what about a less formal definition like this:
>>
>>     The Cancel-Lock and Cancel-Key header fields MUST be treated as
>>     though it were news header fields as defined in Section 3 of
>>     [RFC5536].
> 
> I'm not sure about that. It might fly, or not. Again, I think you need 
> to ask somebody more authoritative.
> 
>> Rewriting RFC 5322 and RFC 5536 should be avoided if possible.
> 
> I understand why you might not want to take on responsibility for that. 
> But it is the right thing to do. Question is whether it needs to be done 
> now.
> 
>>>>> (2) Minor:
>>>>>
>>>>> In Section 3.5, step 1 says to hash the key using the algorithm 
>>>>> from its
>>>>> scheme. But IIUC the scheme describes the algorithm that has already
>>>>> been used when constructing the Cancel-Key header.
>>>>
>>>> No. There are two different operations that use a hash function.
>>>>
>>>> The recommended algorithm described in Section 4 calculates:
>>>> |
>>>> | K = HMAC(uid+mid, sec)
>>>>
>>>> K is then used for <c-key-string> in the Cancel-Key header field only
>>>> with Base64 as transfer encoding (no further hash operation is used):
>>>>
>>>>      c-key-string = Base64(K)
>>>>
>>>> HMAC can be based on a different hash function than the one in <scheme>
>>>> (because a serving agent doesn't need to know how K was calculated for
>>>> the check algorithm defined in Section 3.5).
>>>>
>>>> A value of e.g. "sha256" for <scheme> in a Cancel-Key header field
>>>> doesn't mean that SHA256 was used to generate this field, but that the
>>>> corresponding Cancel-Lock header field (in the original article) 
>>>> contains
>>>> the value of <c-key-string> hashed with SHA256 (and finally Base64
>>>> encoded).
>>>>
>>>> The hash function defined by <scheme> is used to generate 
>>>> <c-lock-string>
>>>> elements for the Cancel-Lock header field:
>>>>
>>>>      c-lock-string = Base64(hash(c-key-string))
>>>>                             ^^^^
>>>> This hash function is the one specified with <scheme> (in both matching
>>>> elements <c-lock> and <c-key> in the Cancel-Lock and Cancel-Key header
>>>> fields of the two articles involved).
>>>>> IIUC the serving
>>>>> agent need not hash the provided key. Rather it only uses the 
>>>>> scheme to
>>>>> select the locks to compare the hash against.
>>>>
>>>> <scheme> is used for both purposes.
>>>>
>>>> Step 1 is defined in Section 3.5 as:
>>>> |
>>>> | 1. The <c-key-string> part of the <c-key> element is hashed using
>>>> |    the algorithm defined by its <scheme> part.
>>>>
>>>> This is the operation for <c-lock-string> listed above.
>>>> The hash operation is required here because if the elements from the
>>>> Cancel-Key header field would be directly comparable, everybody could
>>>> forge them (copy from the public original article).
>>>> The hijack/abuse attack against <c-key-string> elements on their way
>>>> through the network (as discussed for the review from David Mandelberg)
>>>> is not the same. The relevant difference is who can *create* valid
>>>> <c-key-string> elements.
>>>>
>>>> In Step 2 <scheme> is used again to skip <c-lock-string> elements that
>>>> were created using different hash functions. The compare operation from
>>>> Step 2 (with first operand from Step 1) is:
>>>>
>>>>      Base64(hash(c-key-string)) == c-lock-string
>>>>
>>>> The Base64 encode part is not explicitly noted in Step 1.
>>>> Base64 decoding the second operand instead would work too:
>>>>
>>>>      hash(c-key-string) == Base64_decode(c-lock-string)
>>>>
>>>> To be unambiguous and consistent with the definition of <c-lock-string>
>>>> from Section 2.1, the words for Step 1 in Section 3.5 maybe should
>>>> explicitly cover the Base64 encode operation. Suggestion:
>>>>
>>>>      1. The <c-key-string> part of the <c-key> element is hashed using
>>>>         the algorithm defined by its <scheme> part and then Base64
>>>>         encoded.
>>>
>>> Hmm. That wasn't so clear to me, though on rereading I can understand it
>>> that way.
>>>
>>> But in that case, what is the point of passing the scheme around at all?
>>
>> The <scheme> part of <c-key> elements serve the following purposes:
>> - Backward compatibility
>>    Existing implementations use it this way since many years
>> - Define the hash algorithm to apply on <c-key-string> elements
>> - Select corresponding <c-lock-string> elements to compare against
>>
>>> IIUC doing so doesn't add any additional security or privacy. You could
>>> simply pass the hashed value in cancel-key. Then the verifying agent
>>> wouldn't do any hashing.
>>
>> In this case the creator of the Cancel-Key header field would not prove
>> that he really knows K.
>>
>>> This would mean that the cancel-key would be
>>> checked against locks that used a different hash, but that shouldn't
>>> hurt anything.
>>
>> Yes, it is unlikely that comparing against <c-lock-string> elements,
>> that used a different hash algorithm, will hurt.
>>
>> But changing the general syntax of the header fields would break
>> backward compatibility to existing implementations. This should be
>> avoided with highest priority.
> 
> I studied the draft further. I finally get that it is simpler than I was 
> expecting it to be. So really it is just that the lock contains 
> hash(password) while the key contains the password. (The key is just an 
> algorithmically generated password.) I couldn't believe you would really 
> be passing the password in the clear, since that would expose it to 
> on-path attack. But I guess your assumption is that this is really a 
> one-time password, and that if it is correct then it will immediately be 
> invalidated, and if it is wrong then it doesn't matter.
> 
> So I'll withdraw my concerns on this section, except that maybe it could 
> be clearer. Specifically, section 3 could be more explicit about what 
> each distinct actor (poster, posting agent, moderator or injecting 
> agent) does.
> 
>>> [...]
>>> I didn't see a response from you on (4).
>>
>> Sorry for the delay, I was busy.
>>
>> | (4) Minor:
>> |
>> | In Section 8.1/8.2 the syntax/semantics of the Owner/Change
>> | controller is unspecified. But IANA is charged with 
>> allowing/rejecting change
>> | requests only from the "same" owner. How is IANA expected to verify
>> | this?
>>
>> If it is an experimental algorithm, I see no need for strong 
>> authentication
>> of external contributors.
>>
>> For the algorithms on the standards track, the IESG is defined as owner
>> (may authenticate itself to IANA with a signature).
>>
>> | What if a change is required but the original owner is no longer
>> | available?
>> | E.g., the owner might be specified by email address. Later the mail
>> | server for that email address may no longer exist.
>>
>> In this case the part "[...] where the owner of the registration [...]
>> has moved out of contact [...]" can be applied.
> 
> I won't belabor this point because it will clearly be an infrequent event.
> 
>      Thanks,
>      Paul
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art
> 



From nobody Mon Sep 18 21:45:06 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EA44E1342C0; Mon, 18 Sep 2017 21:44:58 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Brian Carpenter <brian.e.carpenter@gmail.com>
To: <gen-art@ietf.org>
Cc: grow@ietf.org, draft-ietf-grow-bgp-session-culling.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.62.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150579629891.15651.17244647188709040958@ietfa.amsl.com>
Date: Mon, 18 Sep 2017 21:44:58 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/XKDyjuUlp7S0E3_d4eQwd00wGdo>
Subject: [Gen-art] Genart last call review of draft-ietf-grow-bgp-session-culling-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Sep 2017 04:44:59 -0000

Reviewer: Brian Carpenter
Review result: Ready with Issues

Gen-ART Last Call review of draft-ietf-grow-bgp-session-culling-04

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-grow-bgp-session-culling-04.txt
Reviewer: Brian Carpenter
Review Date: 2017-09-19
IETF LC End Date: 2017-09-25
IESG Telechat date: 

Summary: Ready with issues
--------

Minor Issues:
-------------

> 3.1.1.  Maintenance Considerations
>
>  Initiators of the administrative shutdown could consider using
>  Graceful Shutdown [I-D.ietf-grow-bgp-gshut] to facilitate smooth
>  drainage of traffic prior to session tear down, and the Shutdown
>  Communication [I-D.ietf-idr-shutdown]...

This strikes me as vague. "Could consider"? Surely if this is
a BCP, they MUST use some mechanisms and perhaps SHOULD use these
particular mechanisms. Otherwise the document doesn't specify
anything much at all for this case.

> 3.2.  Involuntary BGP Session Teardown Recommendations
...
>  In the absence notifications from the lower layer (e.g. ethernet link
>  down) consistent with the planned maintenance activities in a
>  switched layer-2 fabric, the Caretaker of the fabric could choose to
>  cull BGP sessions on behalf of the Operators connected to the fabric.

This seems incomplete. Firstly, I'm assuming that it should start
"In the absence of notifications...". Secondly, if there are no
fault indications, what causes the Caretaker to cull sessions?
What's the trigger? Is the Caretaker supposed to know by magic
that layer 2 maintenance is planned?
...
>  In this scenario, BGP Session Culling is accomplished through the
>  application of a combined layer-3 and layer-4 packet filter deployed
>  in the switched fabric itself.

Please add "as described in the next sub-section" because otherwise
the reader can easily be confused.

> 3.2.1.  Packet Filter Considerations
>
>  The following considerations apply to the packet filter design:
>
>  o  The packet filter MUST only affect BGP traffic specific to the
>     layer-2 fabric, i.e. forming part of the control plane of the
>     system described, rather than multihop BGP traffic which merely
>     transits

That's a goal, but it doesn't tell me how to achieve the goal.
What packet signature tells me which packets are specific to the
fabric? I suspect this might overlap with the last bullet - if so,
you might consider re-ordering the bullets.
...
>  o  The packet filter MUST affect all relevant Address Family
>     Identifiers

Define "relevant". And in Appendix A, explain precisely how
the example prefixes are used: what makes them relevant? Are they
normally announced by BGP to all the IXP's BGP peers?

--


From nobody Mon Sep 18 21:53:19 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B50E132A89; Mon, 18 Sep 2017 21:53:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 tgjGZfHgFqcT; Mon, 18 Sep 2017 21:53:15 -0700 (PDT)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 227E21326DF; Mon, 18 Sep 2017 21:53:15 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id h66so7192342ioh.11; Mon, 18 Sep 2017 21:53:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=O18I0bVeebuTzelGQHK9Zb4uzjziqcuiDPDHVJ8POkA=; b=U4WmgI9v2YIWVGTetiYa2IMp1nX87K/Lz95KfEBofWDFCEFh6SzQPrbM90I/unt2bK LYPIr4jlnTO+uOf7AcUY8WjQPj3Wn/KwBq/yT7VSdenPdS619mdRpK3tdkGKe483qzV9 jtwX+0cWXdSEn1OYHmLWmnOL2j2C52wT3Zuy86OO3Q4EJ40vXHiZW8O5SlXDlNZud70P j+xv+ZWBHj5WNkb39fJrs19o8VUo6nubiPjwZZMTZ2pmsyTYhDibtcJW0fpA4rRZ7xcQ 3nfZTg8e3fq6d0/DJSSlOeh/UFtC879ja5qz1gbfkcfeT1SjEdL6stQgpb2HCuJXv5la skRQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=O18I0bVeebuTzelGQHK9Zb4uzjziqcuiDPDHVJ8POkA=; b=EopNuOXJJopik7NBbc2CuAmrWvJ+5N0KVYfxBdOBynRxi9hPbeDVOE2BioHZYxjqmO U8UMkZ0Ai6pl9tRvKgW8v3B3LAGedUpBgxk53ZAFiReQPGS1G/n+A4Yq3pwoISF80jFX ReadcMoX1BFcvVMUlE1pWi30iaaXhlLUildEkTCYFVuivjibaBj6wKRKja47Y+jOC9vq uovrqFtBxMla1b5ZJj/jsmeKF1g5eZ/Xi1qIDGoS9oxu9LbPndXEmsa98+bln5DsEamX mk1Ez3GUuvrez6XakCYzM9sTPQq9jGdQhKWVGl3YaQgbD3j+NiJc14X7yZ4qT8H2WPmv okuA==
X-Gm-Message-State: AHPjjUjy64e0GpC0B+Gw2WnZQfAMKH/e/3VTn45IUVcrbzRHeLWsGhdP 8D8ydU64Jp3wm2e4wd6SJC2ttg==
X-Google-Smtp-Source: AOwi7QBPKEcXrSo/t776ijmqjMCYwPAOFDvtJj/UhsMjNLuwaG11HBT6ZVAoDpz8q/xJZhk06IQAfw==
X-Received: by 10.107.46.163 with SMTP id u35mr188061iou.276.1505796792839; Mon, 18 Sep 2017 21:53:12 -0700 (PDT)
Received: from ?IPv6:2406:e007:57a7:1:28cc:dc4c:9703:6781? ([2406:e007:57a7:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id q19sm4417986iod.42.2017.09.18.21.53.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Sep 2017 21:53:11 -0700 (PDT)
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, draft-baeuerle-netnews-cancel-lock.all@ietf.org
Cc: General Area Review Team <gen-art@ietf.org>
References: <9be2e7af-b99d-4f86-6552-bfada936600d@alum.mit.edu> <20170707174750.487009ed@WStation4> <7452e826-62e9-0d6e-32b5-dcdefcb4c2ea@alum.mit.edu> <20170711203934.458e3b62@WStation4> <37001dcd-6551-78b4-18e7-75fbebaff761@alum.mit.edu> <0147f247-2763-8017-f123-5cdd6ceb06b3@alum.mit.edu>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <640fa8b4-0a91-fba9-0649-8cb2bb14ad61@gmail.com>
Date: Tue, 19 Sep 2017 16:53:10 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <0147f247-2763-8017-f123-5cdd6ceb06b3@alum.mit.edu>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/EYQw0h_fqwc6yAuFSREdqQIDOHg>
Subject: Re: [Gen-art] draft-baeuerle-netnews-cancel-lock-06 and RFCs 5536 & 5322
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Sep 2017 04:53:18 -0000

> The question is: in the meantime, what to do about this draft? By=20
> default I guess I will simply restate the issue in my genart telechat=20
> review and leave it for the IESG discuss it.

That's about all you can do. Of course if the IESG approves it anyway
you can appeal that decision. I'm not aware of any case where a Gen-ART
reviewer has needed to do that, but there's a first time for everything,
and the plenaries are boring if there are no appeals to rehash ;-)

Regards
   Brian

On 19/09/2017 09:14, Paul Kyzivat wrote:
> I'm on tap to do the genart telechat review on=20
> draft-baeuerle-netnews-cancel-lock-06. I see that nothing has been done=
=20
> about the ABNF that was my primary concern in my prior wglc review of -=
05:
>=20
> https://mailarchive.ietf.org/arch/msg/gen-art/wXKa5tadbo_xQbbUUCk9RZyB0=
w8
>=20
> I'm told by the authors that Alexey asked that it be submitted this way=
,=20
> but the ABNF *is* wrong, and I can't see how a new draft can be allowed=
=20
> to be published with knowingly wrong ABNF. OTOH, the problem didn't=20
> originate with this draft. Rather the problem originated with RFC5536, =

> and this draft has simply built on that mistake. Unfortunately the root=
=20
> of the problem is with RFC5322, since its ABNF is structured in a way=20
> that makes it really hard to define extensions such as those in RFC5536=
=20
> and this draft. So the cleanest solution I can see is to revise both=20
> 5322 and 5536, and then this draft can build on those changes. That is =
a=20
> rather involved fix but I don't see any other reasonable way.
>=20
> This prompted me to submit an erratum (#5116) on RFC5536 regarding this=
=20
> issue. But errata aren't often acted on quickly when they require=20
> revising RFCs.
>=20
> The question is: in the meantime, what to do about this draft? By=20
> default I guess I will simply restate the issue in my genart telechat=20
> review and leave it for the IESG discuss it.
>=20
> Anybody have a better idea?
>=20
> 	Thanks,
> 	Paul
>=20
> On 7/14/17 12:58 PM, Paul Kyzivat wrote:
>> Michael,
>>
>> Please see further comments inline.
>>
>> (Sorry - the indenting is getting deep, but I think we are pretty much=
=20
>> done.)
>>
>> On 7/11/17 2:39 PM, Michael B=C3=A4uerle wrote:
>>> Paul Kyzivat wrote:
>>>> On 7/7/17 11:47 AM, Michael B=C3=A4uerle wrote:
>>>>> Paul Kyzivat wrote:
>>>>>>
>>>>>> [...]
>>>>>> General Comments:
>>>>>>
>>>>>> I have not attempted to validate the security properties of this
>>>>>> document - leaving that to a security review.
>>>>>>
>>>>>> I have also not attempted to verify the operational suitability of=
=20
>>>>>> this
>>>>>> mechanism because I don't have the experience needed to do so.
>>>>>>
>>>>>> Issues:
>>>>>>
>>>>>> Major: 1
>>>>>> Minor: 3
>>>>>> Nits:=C2=A0 0
>>>>>>
>>>>>> (1) MAJOR:
>>>>>>
>>>>>> [Problem with ABNF syntax of header fields]
>>>>>
>>>>> Hi Paul,
>>>>>
>>>>> Julien =C3=89lie has proposed a new syntax definition.
>>>>
>>>> I was copied on his mail proposing a change to RFC5536, and that is
>>>> tentative. *This* document would of course require a similar change.=
 Or
>>>> else it could extend that change, via something like
>>>>
>>>> =C2=A0=C2=A0=C2=A0=C2=A0news-fields =3D/ cancel-lock / cancel-key
>>>>
>>>> But that can only be done if there is actually a draft that revises =
5536
>>>> that can then be referenced. Bottom line is that it seems there need=
s to
>>>> be some coordination of that fix with this draft.
>>>
>>> It's clear that the Cancel-Lock draft needs to be changed. My comment=

>>> was about the potential erratum for RFC 5536 and the question:
>>> Is it (in general) possible to reference a modified ABNF definition i=
n
>>> an erratum?
>>
>> I don't know of any way to do so. Perhaps somebody else can provide a =

>> more definitive answer. You might try asking on rfc-interest.
>>
>>> If this is possible, then the current:
>>>
>>> =C2=A0=C2=A0=C2=A0 fields =3D/ *( cancel-lock / cancel-key )
>>>
>>> can be changed to:
>>>
>>> =C2=A0=C2=A0=C2=A0 news-fields =3D/ cancel-lock / cancel-key
>>>
>>> and should then reference the new ABNF from the erratum.
>>> If not, what about a less formal definition like this:
>>>
>>> =C2=A0=C2=A0=C2=A0 The Cancel-Lock and Cancel-Key header fields MUST =
be treated as
>>> =C2=A0=C2=A0=C2=A0 though it were news header fields as defined in Se=
ction 3 of
>>> =C2=A0=C2=A0=C2=A0 [RFC5536].
>>
>> I'm not sure about that. It might fly, or not. Again, I think you need=
=20
>> to ask somebody more authoritative.
>>
>>> Rewriting RFC 5322 and RFC 5536 should be avoided if possible.
>>
>> I understand why you might not want to take on responsibility for that=
=2E=20
>> But it is the right thing to do. Question is whether it needs to be do=
ne=20
>> now.
>>
>>>>>> (2) Minor:
>>>>>>
>>>>>> In Section 3.5, step 1 says to hash the key using the algorithm=20
>>>>>> from its
>>>>>> scheme. But IIUC the scheme describes the algorithm that has alrea=
dy
>>>>>> been used when constructing the Cancel-Key header.
>>>>>
>>>>> No. There are two different operations that use a hash function.
>>>>>
>>>>> The recommended algorithm described in Section 4 calculates:
>>>>> |
>>>>> | K =3D HMAC(uid+mid, sec)
>>>>>
>>>>> K is then used for <c-key-string> in the Cancel-Key header field on=
ly
>>>>> with Base64 as transfer encoding (no further hash operation is used=
):
>>>>>
>>>>> =C2=A0=C2=A0=C2=A0=C2=A0 c-key-string =3D Base64(K)
>>>>>
>>>>> HMAC can be based on a different hash function than the one in <sch=
eme>
>>>>> (because a serving agent doesn't need to know how K was calculated =
for
>>>>> the check algorithm defined in Section 3.5).
>>>>>
>>>>> A value of e.g. "sha256" for <scheme> in a Cancel-Key header field
>>>>> doesn't mean that SHA256 was used to generate this field, but that =
the
>>>>> corresponding Cancel-Lock header field (in the original article)=20
>>>>> contains
>>>>> the value of <c-key-string> hashed with SHA256 (and finally Base64
>>>>> encoded).
>>>>>
>>>>> The hash function defined by <scheme> is used to generate=20
>>>>> <c-lock-string>
>>>>> elements for the Cancel-Lock header field:
>>>>>
>>>>> =C2=A0=C2=A0=C2=A0=C2=A0 c-lock-string =3D Base64(hash(c-key-string=
))
>>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 ^^^^
>>>>> This hash function is the one specified with <scheme> (in both matc=
hing
>>>>> elements <c-lock> and <c-key> in the Cancel-Lock and Cancel-Key hea=
der
>>>>> fields of the two articles involved).
>>>>>> IIUC the serving
>>>>>> agent need not hash the provided key. Rather it only uses the=20
>>>>>> scheme to
>>>>>> select the locks to compare the hash against.
>>>>>
>>>>> <scheme> is used for both purposes.
>>>>>
>>>>> Step 1 is defined in Section 3.5 as:
>>>>> |
>>>>> | 1. The <c-key-string> part of the <c-key> element is hashed using=

>>>>> |=C2=A0=C2=A0=C2=A0 the algorithm defined by its <scheme> part.
>>>>>
>>>>> This is the operation for <c-lock-string> listed above.
>>>>> The hash operation is required here because if the elements from th=
e
>>>>> Cancel-Key header field would be directly comparable, everybody cou=
ld
>>>>> forge them (copy from the public original article).
>>>>> The hijack/abuse attack against <c-key-string> elements on their wa=
y
>>>>> through the network (as discussed for the review from David Mandelb=
erg)
>>>>> is not the same. The relevant difference is who can *create* valid
>>>>> <c-key-string> elements.
>>>>>
>>>>> In Step 2 <scheme> is used again to skip <c-lock-string> elements t=
hat
>>>>> were created using different hash functions. The compare operation =
from
>>>>> Step 2 (with first operand from Step 1) is:
>>>>>
>>>>> =C2=A0=C2=A0=C2=A0=C2=A0 Base64(hash(c-key-string)) =3D=3D c-lock-s=
tring
>>>>>
>>>>> The Base64 encode part is not explicitly noted in Step 1.
>>>>> Base64 decoding the second operand instead would work too:
>>>>>
>>>>> =C2=A0=C2=A0=C2=A0=C2=A0 hash(c-key-string) =3D=3D Base64_decode(c-=
lock-string)
>>>>>
>>>>> To be unambiguous and consistent with the definition of <c-lock-str=
ing>
>>>>> from Section 2.1, the words for Step 1 in Section 3.5 maybe should
>>>>> explicitly cover the Base64 encode operation. Suggestion:
>>>>>
>>>>> =C2=A0=C2=A0=C2=A0=C2=A0 1. The <c-key-string> part of the <c-key> =
element is hashed using
>>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 the algorithm defined by=
 its <scheme> part and then Base64
>>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 encoded.
>>>>
>>>> Hmm. That wasn't so clear to me, though on rereading I can understan=
d it
>>>> that way.
>>>>
>>>> But in that case, what is the point of passing the scheme around at =
all?
>>>
>>> The <scheme> part of <c-key> elements serve the following purposes:
>>> - Backward compatibility
>>> =C2=A0=C2=A0 Existing implementations use it this way since many year=
s
>>> - Define the hash algorithm to apply on <c-key-string> elements
>>> - Select corresponding <c-lock-string> elements to compare against
>>>
>>>> IIUC doing so doesn't add any additional security or privacy. You co=
uld
>>>> simply pass the hashed value in cancel-key. Then the verifying agent=

>>>> wouldn't do any hashing.
>>>
>>> In this case the creator of the Cancel-Key header field would not pro=
ve
>>> that he really knows K.
>>>
>>>> This would mean that the cancel-key would be
>>>> checked against locks that used a different hash, but that shouldn't=

>>>> hurt anything.
>>>
>>> Yes, it is unlikely that comparing against <c-lock-string> elements,
>>> that used a different hash algorithm, will hurt.
>>>
>>> But changing the general syntax of the header fields would break
>>> backward compatibility to existing implementations. This should be
>>> avoided with highest priority.
>>
>> I studied the draft further. I finally get that it is simpler than I w=
as=20
>> expecting it to be. So really it is just that the lock contains=20
>> hash(password) while the key contains the password. (The key is just a=
n=20
>> algorithmically generated password.) I couldn't believe you would real=
ly=20
>> be passing the password in the clear, since that would expose it to=20
>> on-path attack. But I guess your assumption is that this is really a=20
>> one-time password, and that if it is correct then it will immediately =
be=20
>> invalidated, and if it is wrong then it doesn't matter.
>>
>> So I'll withdraw my concerns on this section, except that maybe it cou=
ld=20
>> be clearer. Specifically, section 3 could be more explicit about what =

>> each distinct actor (poster, posting agent, moderator or injecting=20
>> agent) does.
>>
>>>> [...]
>>>> I didn't see a response from you on (4).
>>>
>>> Sorry for the delay, I was busy.
>>>
>>> | (4) Minor:
>>> |
>>> | In Section 8.1/8.2 the syntax/semantics of the Owner/Change
>>> | controller is unspecified. But IANA is charged with=20
>>> allowing/rejecting change
>>> | requests only from the "same" owner. How is IANA expected to verify=

>>> | this?
>>>
>>> If it is an experimental algorithm, I see no need for strong=20
>>> authentication
>>> of external contributors.
>>>
>>> For the algorithms on the standards track, the IESG is defined as own=
er
>>> (may authenticate itself to IANA with a signature).
>>>
>>> | What if a change is required but the original owner is no longer
>>> | available?
>>> | E.g., the owner might be specified by email address. Later the mail=

>>> | server for that email address may no longer exist.
>>>
>>> In this case the part "[...] where the owner of the registration [...=
]
>>> has moved out of contact [...]" can be applied.
>>
>> I won't belabor this point because it will clearly be an infrequent ev=
ent.
>>
>>  =C2=A0=C2=A0=C2=A0=C2=A0Thanks,
>>  =C2=A0=C2=A0=C2=A0=C2=A0Paul
>>
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art
>>
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art
>=20


From nobody Tue Sep 19 02:06:25 2017
Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08CE0126DFE; Tue, 19 Sep 2017 02:06:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level: 
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.fm header.b=sm7n5Mol; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=etXlWKFj
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 Gj6Le7mZWJHn; Tue, 19 Sep 2017 02:06:16 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38774126B7E; Tue, 19 Sep 2017 02:06:16 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 3655D20A52; Tue, 19 Sep 2017 05:06:15 -0400 (EDT)
Received: from web5 ([10.202.2.215]) by compute7.internal (MEProxy); Tue, 19 Sep 2017 05:06:15 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=fs1c0EjdaXP8R4wrLDv93CHJ86RhG Yi5bgr9D2JODwM=; b=sm7n5MolVVnYTcHN5wW0PX65FVfX/CExUEzWP9+7uUVgC z5rBWvBagr8rWpMDcN6Y5VVvSEaYUbtjbvn+HqsloeZeIf19daz8ozi1l74iatbW 43u1Vp6h7XPI/0bp8h4vNSduINl1kMGwrKlanE2SaKfrqF6wEJs5aVnIRgmEJy9b 0S3ZZQcVK06Glw89i9TmldF9g/tkYcPtSe8rn3PA/vjO0skmAX7I+FWQrRyhfN3W zqZ9b6ylIwhGnMf4mLOKKHd1cyxOoWSxjIyK0g5fOqEH5P0JvbKC/FHlQFgbzDAn J3YPV7X+E6npxzuJH7NdL8ytQHQUhTDBIq7LGBmuA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=fs1c0E jdaXP8R4wrLDv93CHJ86RhGYi5bgr9D2JODwM=; b=etXlWKFj8lTS0+MC+QbAqJ lNbVB978X6+0RMj+Eq2I7XUM/MZ09+T/b5CIto/vrbVF7XeCkY1gVWNitoXkROeR mq2ScXR8CJeyUf/VLji4ncOFqEqJbNTGzxIzdbg2DLAAPRstZqDla2cmHDL7x6/Q fib7JrYSaRx0jSNuca5JGfUfksP5dYDhlwow/4/dQOdKfDa/AMvUGNShLD84nJOD h1/xxsF7ZjsPatN2Gq1STdeThNmZFPS5o+UcVO3ltlQGDxrk6Ks6N4tD1kggc8Fq HvO+fkq+Ae7eKrnRDunqzv0o1k44XOFITSJRo1lYgkybWcLYlgftgbi9tUEee/EQ ==
X-ME-Sender: <xms:B97AWaNNs_s7wwA9Jk9GyVV1jsv-xu_B3OCkVFfYjTr0hisH6MXlDA>
Received: by mailuser.nyi.internal (Postfix, from userid 99) id 028E69E2E0; Tue, 19 Sep 2017 05:06:14 -0400 (EDT)
Message-Id: <1505811974.1510044.1110862800.6711A3E0@webmail.messagingengine.com>
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, draft-baeuerle-netnews-cancel-lock.all@ietf.org
Cc: General Area Review Team <gen-art@ietf.org>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-64b08692
In-Reply-To: <0147f247-2763-8017-f123-5cdd6ceb06b3@alum.mit.edu>
References: <9be2e7af-b99d-4f86-6552-bfada936600d@alum.mit.edu> <20170707174750.487009ed@WStation4> <7452e826-62e9-0d6e-32b5-dcdefcb4c2ea@alum.mit.edu> <20170711203934.458e3b62@WStation4> <37001dcd-6551-78b4-18e7-75fbebaff761@alum.mit.edu> <0147f247-2763-8017-f123-5cdd6ceb06b3@alum.mit.edu>
Date: Tue, 19 Sep 2017 10:06:14 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/7nPf6NA-LL7ULDlhu72mKoU_8F8>
Subject: Re: [Gen-art] draft-baeuerle-netnews-cancel-lock-06 and RFCs 5536 & 5322
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Sep 2017 09:06:23 -0000

Paul,

On Mon, Sep 18, 2017, at 10:14 PM, Paul Kyzivat wrote:
> I'm on tap to do the genart telechat review on=20
> draft-baeuerle-netnews-cancel-lock-06. I see that nothing has been done=20
> about the ABNF that was my primary concern in my prior wglc review of
> -05:
>=20
> https://mailarchive.ietf.org/arch/msg/gen-art/wXKa5tadbo_xQbbUUCk9RZyB0w8
>=20
> I'm told by the authors that Alexey asked that it be submitted this way,=
=20
> but the ABNF *is* wrong, and I can't see how a new draft can be allowed=20
> to be published with knowingly wrong ABNF. OTOH, the problem didn't=20
> originate with this draft. Rather the problem originated with RFC5536,=20
> and this draft has simply built on that mistake. Unfortunately the root=20
> of the problem is with RFC5322, since its ABNF is structured in a way=20
> that makes it really hard to define extensions such as those in RFC5536=20
> and this draft. So the cleanest solution I can see is to revise both=20
> 5322 and 5536, and then this draft can build on those changes. That is a=
=20
> rather involved fix but I don't see any other reasonable way.
>=20
> This prompted me to submit an erratum (#5116) on RFC5536 regarding this=20
> issue. But errata aren't often acted on quickly when they require=20
> revising RFCs.
>=20
> The question is: in the meantime, what to do about this draft? By=20
> default I guess I will simply restate the issue in my genart telechat=20
> review and leave it for the IESG discuss it.
>=20
> Anybody have a better idea?

It is on my to do list *before* the telechat. I contacted Pete Resnick
and he suggested a slightly better fix to your erratum. This is just
taking time on my part.

Best Regards,
Alexey

> 	Thanks,
> 	Paul
>=20
> On 7/14/17 12:58 PM, Paul Kyzivat wrote:
> > Michael,
> >=20
> > Please see further comments inline.
> >=20
> > (Sorry - the indenting is getting deep, but I think we are pretty much=
=20
> > done.)
> >=20
> > On 7/11/17 2:39 PM, Michael B=C3=A4uerle wrote:
> >> Paul Kyzivat wrote:
> >>> On 7/7/17 11:47 AM, Michael B=C3=A4uerle wrote:
> >>>> Paul Kyzivat wrote:
> >>>>>
> >>>>> [...]
> >>>>> General Comments:
> >>>>>
> >>>>> I have not attempted to validate the security properties of this
> >>>>> document - leaving that to a security review.
> >>>>>
> >>>>> I have also not attempted to verify the operational suitability of=
=20
> >>>>> this
> >>>>> mechanism because I don't have the experience needed to do so.
> >>>>>
> >>>>> Issues:
> >>>>>
> >>>>> Major: 1
> >>>>> Minor: 3
> >>>>> Nits:=C2=A0 0
> >>>>>
> >>>>> (1) MAJOR:
> >>>>>
> >>>>> [Problem with ABNF syntax of header fields]
> >>>>
> >>>> Hi Paul,
> >>>>
> >>>> Julien =C3=89lie has proposed a new syntax definition.
> >>>
> >>> I was copied on his mail proposing a change to RFC5536, and that is
> >>> tentative. *This* document would of course require a similar change. =
Or
> >>> else it could extend that change, via something like
> >>>
> >>> =C2=A0=C2=A0=C2=A0=C2=A0news-fields =3D/ cancel-lock / cancel-key
> >>>
> >>> But that can only be done if there is actually a draft that revises 5=
536
> >>> that can then be referenced. Bottom line is that it seems there needs=
 to
> >>> be some coordination of that fix with this draft.
> >>
> >> It's clear that the Cancel-Lock draft needs to be changed. My comment
> >> was about the potential erratum for RFC 5536 and the question:
> >> Is it (in general) possible to reference a modified ABNF definition in
> >> an erratum?
> >=20
> > I don't know of any way to do so. Perhaps somebody else can provide a=20
> > more definitive answer. You might try asking on rfc-interest.
> >=20
> >> If this is possible, then the current:
> >>
> >> =C2=A0=C2=A0=C2=A0 fields =3D/ *( cancel-lock / cancel-key )
> >>
> >> can be changed to:
> >>
> >> =C2=A0=C2=A0=C2=A0 news-fields =3D/ cancel-lock / cancel-key
> >>
> >> and should then reference the new ABNF from the erratum.
> >> If not, what about a less formal definition like this:
> >>
> >> =C2=A0=C2=A0=C2=A0 The Cancel-Lock and Cancel-Key header fields MUST b=
e treated as
> >> =C2=A0=C2=A0=C2=A0 though it were news header fields as defined in Sec=
tion 3 of
> >> =C2=A0=C2=A0=C2=A0 [RFC5536].
> >=20
> > I'm not sure about that. It might fly, or not. Again, I think you need=
=20
> > to ask somebody more authoritative.
> >=20
> >> Rewriting RFC 5322 and RFC 5536 should be avoided if possible.
> >=20
> > I understand why you might not want to take on responsibility for that.=
=20
> > But it is the right thing to do. Question is whether it needs to be don=
e=20
> > now.
> >=20
> >>>>> (2) Minor:
> >>>>>
> >>>>> In Section 3.5, step 1 says to hash the key using the algorithm=20
> >>>>> from its
> >>>>> scheme. But IIUC the scheme describes the algorithm that has already
> >>>>> been used when constructing the Cancel-Key header.
> >>>>
> >>>> No. There are two different operations that use a hash function.
> >>>>
> >>>> The recommended algorithm described in Section 4 calculates:
> >>>> |
> >>>> | K =3D HMAC(uid+mid, sec)
> >>>>
> >>>> K is then used for <c-key-string> in the Cancel-Key header field only
> >>>> with Base64 as transfer encoding (no further hash operation is used):
> >>>>
> >>>> =C2=A0=C2=A0=C2=A0=C2=A0 c-key-string =3D Base64(K)
> >>>>
> >>>> HMAC can be based on a different hash function than the one in <sche=
me>
> >>>> (because a serving agent doesn't need to know how K was calculated f=
or
> >>>> the check algorithm defined in Section 3.5).
> >>>>
> >>>> A value of e.g. "sha256" for <scheme> in a Cancel-Key header field
> >>>> doesn't mean that SHA256 was used to generate this field, but that t=
he
> >>>> corresponding Cancel-Lock header field (in the original article)=20
> >>>> contains
> >>>> the value of <c-key-string> hashed with SHA256 (and finally Base64
> >>>> encoded).
> >>>>
> >>>> The hash function defined by <scheme> is used to generate=20
> >>>> <c-lock-string>
> >>>> elements for the Cancel-Lock header field:
> >>>>
> >>>> =C2=A0=C2=A0=C2=A0=C2=A0 c-lock-string =3D Base64(hash(c-key-string))
> >>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 ^^^^
> >>>> This hash function is the one specified with <scheme> (in both match=
ing
> >>>> elements <c-lock> and <c-key> in the Cancel-Lock and Cancel-Key head=
er
> >>>> fields of the two articles involved).
> >>>>> IIUC the serving
> >>>>> agent need not hash the provided key. Rather it only uses the=20
> >>>>> scheme to
> >>>>> select the locks to compare the hash against.
> >>>>
> >>>> <scheme> is used for both purposes.
> >>>>
> >>>> Step 1 is defined in Section 3.5 as:
> >>>> |
> >>>> | 1. The <c-key-string> part of the <c-key> element is hashed using
> >>>> |=C2=A0=C2=A0=C2=A0 the algorithm defined by its <scheme> part.
> >>>>
> >>>> This is the operation for <c-lock-string> listed above.
> >>>> The hash operation is required here because if the elements from the
> >>>> Cancel-Key header field would be directly comparable, everybody could
> >>>> forge them (copy from the public original article).
> >>>> The hijack/abuse attack against <c-key-string> elements on their way
> >>>> through the network (as discussed for the review from David Mandelbe=
rg)
> >>>> is not the same. The relevant difference is who can *create* valid
> >>>> <c-key-string> elements.
> >>>>
> >>>> In Step 2 <scheme> is used again to skip <c-lock-string> elements th=
at
> >>>> were created using different hash functions. The compare operation f=
rom
> >>>> Step 2 (with first operand from Step 1) is:
> >>>>
> >>>> =C2=A0=C2=A0=C2=A0=C2=A0 Base64(hash(c-key-string)) =3D=3D c-lock-st=
ring
> >>>>
> >>>> The Base64 encode part is not explicitly noted in Step 1.
> >>>> Base64 decoding the second operand instead would work too:
> >>>>
> >>>> =C2=A0=C2=A0=C2=A0=C2=A0 hash(c-key-string) =3D=3D Base64_decode(c-l=
ock-string)
> >>>>
> >>>> To be unambiguous and consistent with the definition of <c-lock-stri=
ng>
> >>>> from Section 2.1, the words for Step 1 in Section 3.5 maybe should
> >>>> explicitly cover the Base64 encode operation. Suggestion:
> >>>>
> >>>> =C2=A0=C2=A0=C2=A0=C2=A0 1. The <c-key-string> part of the <c-key> e=
lement is hashed using
> >>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 the algorithm defined by =
its <scheme> part and then Base64
> >>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 encoded.
> >>>
> >>> Hmm. That wasn't so clear to me, though on rereading I can understand=
 it
> >>> that way.
> >>>
> >>> But in that case, what is the point of passing the scheme around at a=
ll?
> >>
> >> The <scheme> part of <c-key> elements serve the following purposes:
> >> - Backward compatibility
> >> =C2=A0=C2=A0 Existing implementations use it this way since many years
> >> - Define the hash algorithm to apply on <c-key-string> elements
> >> - Select corresponding <c-lock-string> elements to compare against
> >>
> >>> IIUC doing so doesn't add any additional security or privacy. You cou=
ld
> >>> simply pass the hashed value in cancel-key. Then the verifying agent
> >>> wouldn't do any hashing.
> >>
> >> In this case the creator of the Cancel-Key header field would not prove
> >> that he really knows K.
> >>
> >>> This would mean that the cancel-key would be
> >>> checked against locks that used a different hash, but that shouldn't
> >>> hurt anything.
> >>
> >> Yes, it is unlikely that comparing against <c-lock-string> elements,
> >> that used a different hash algorithm, will hurt.
> >>
> >> But changing the general syntax of the header fields would break
> >> backward compatibility to existing implementations. This should be
> >> avoided with highest priority.
> >=20
> > I studied the draft further. I finally get that it is simpler than I wa=
s=20
> > expecting it to be. So really it is just that the lock contains=20
> > hash(password) while the key contains the password. (The key is just an=
=20
> > algorithmically generated password.) I couldn't believe you would reall=
y=20
> > be passing the password in the clear, since that would expose it to=20
> > on-path attack. But I guess your assumption is that this is really a=20
> > one-time password, and that if it is correct then it will immediately b=
e=20
> > invalidated, and if it is wrong then it doesn't matter.
> >=20
> > So I'll withdraw my concerns on this section, except that maybe it coul=
d=20
> > be clearer. Specifically, section 3 could be more explicit about what=20
> > each distinct actor (poster, posting agent, moderator or injecting=20
> > agent) does.
> >=20
> >>> [...]
> >>> I didn't see a response from you on (4).
> >>
> >> Sorry for the delay, I was busy.
> >>
> >> | (4) Minor:
> >> |
> >> | In Section 8.1/8.2 the syntax/semantics of the Owner/Change
> >> | controller is unspecified. But IANA is charged with=20
> >> allowing/rejecting change
> >> | requests only from the "same" owner. How is IANA expected to verify
> >> | this?
> >>
> >> If it is an experimental algorithm, I see no need for strong=20
> >> authentication
> >> of external contributors.
> >>
> >> For the algorithms on the standards track, the IESG is defined as owner
> >> (may authenticate itself to IANA with a signature).
> >>
> >> | What if a change is required but the original owner is no longer
> >> | available?
> >> | E.g., the owner might be specified by email address. Later the mail
> >> | server for that email address may no longer exist.
> >>
> >> In this case the part "[...] where the owner of the registration [...]
> >> has moved out of contact [...]" can be applied.
> >=20
> > I won't belabor this point because it will clearly be an infrequent eve=
nt.
> >=20
> >  =C2=A0=C2=A0=C2=A0=C2=A0Thanks,
> >  =C2=A0=C2=A0=C2=A0=C2=A0Paul
> >=20
> > _______________________________________________
> > Gen-art mailing list
> > Gen-art@ietf.org
> > https://www.ietf.org/mailman/listinfo/gen-art
> >=20
>=20
>=20


From nobody Tue Sep 19 02:42:51 2017
Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C03AD126BF0; Tue, 19 Sep 2017 02:42:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level: 
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.fm header.b=glk27n7i; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Ra++uAtg
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 9Z91llITYmgo; Tue, 19 Sep 2017 02:42:46 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 385C91241F3; Tue, 19 Sep 2017 02:42:46 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id A00E4209BF; Tue, 19 Sep 2017 05:42:45 -0400 (EDT)
Received: from web5 ([10.202.2.215]) by compute7.internal (MEProxy); Tue, 19 Sep 2017 05:42:45 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=MsqUwTGbgScQBIdm8Cjhdz9NQBgiY 90UdD+x846kE1s=; b=glk27n7ipNrYrGWJj5Vg6g7HaKdlFs5jh0pStdJ2GOnK/ QGKtgQ1J9sLXhHRM4wxHTd8DgpQ80/bZDu+OZ3Nwt/K9LnrWD0Wh0xi98YUfK0c4 9JYMsGHxHBlh0HrhcKe5dpD18aMTroLvrVsKBp1VM15Jp3B85hAojYyGHQJjPIwe ATVwoPXk8IpE70eFFljySIrsg6YluHmK9xwk8f8/u6KY2ytp3NEMwCrieaql/tDo bjWf0pJkWhWpCWeyXlZN2ScghhuGZyb+O2hevzeVDOUUFR1/MHYhucgbyWQANpiI Azwxr0mslNEYzmJsDXDtF6N4aHPHKRtoqWAVFyNwQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=MsqUwT GbgScQBIdm8Cjhdz9NQBgiY90UdD+x846kE1s=; b=Ra++uAtgTXJuhq/Aa+ilOl Hk79tlFY6yoS7N9DfP1y5UyX0egUdQwin9qes6oIHQTA5nu8Ev8YSpwxPiEso9Up M4pZlnG8ESlFop6SVdt2x72v6T85mjBJaeyPlLy0CUtelYPo1smfUky08nt1lYl8 27nw9Xk5Q+91/B5h6ZrQKrfgzzePx76OABwxQnfkN4BD0MopSeDdkBC0oaaCsGab Awn2pjoGI0gO8iH59wAtRXrAfTH9vQlat6fAR8dx8G+CV8Hc7jQUWYhno4hPojT7 ygbp2Q8XoAyQGyLhlVhknnrQfYWishTovwEqzNB87wBi0gYiUF2fgN4z3tYQxWqA ==
X-ME-Sender: <xms:lebAWf5gA-5IeLNT0eNW7Lqb93Gte2A10ycoFWwm3dc70FuZV2HvOQ>
Received: by mailuser.nyi.internal (Postfix, from userid 99) id 7BFA09E2E0; Tue, 19 Sep 2017 05:42:45 -0400 (EDT)
Message-Id: <1505814165.1516258.1110891352.7E7D795F@webmail.messagingengine.com>
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, draft-baeuerle-netnews-cancel-lock.all@ietf.org, Pete Resnick <presnick@qti.qualcomm.com>
Cc: General Area Review Team <gen-art@ietf.org>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-64b08692
In-Reply-To: <0147f247-2763-8017-f123-5cdd6ceb06b3@alum.mit.edu>
References: <9be2e7af-b99d-4f86-6552-bfada936600d@alum.mit.edu> <20170707174750.487009ed@WStation4> <7452e826-62e9-0d6e-32b5-dcdefcb4c2ea@alum.mit.edu> <20170711203934.458e3b62@WStation4> <37001dcd-6551-78b4-18e7-75fbebaff761@alum.mit.edu> <0147f247-2763-8017-f123-5cdd6ceb06b3@alum.mit.edu>
Date: Tue, 19 Sep 2017 10:42:45 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/0Vw28yGDxSoagHbTJZTmKF_wJZA>
Subject: Re: [Gen-art] draft-baeuerle-netnews-cancel-lock-06 and RFCs 5536 & 5322
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Sep 2017 09:42:49 -0000

Hi Paul,

On Mon, Sep 18, 2017, at 10:14 PM, Paul Kyzivat wrote:
> I'm on tap to do the genart telechat review on=20
> draft-baeuerle-netnews-cancel-lock-06. I see that nothing has been done=20
> about the ABNF that was my primary concern in my prior wglc review of
> -05:
>=20
> https://mailarchive.ietf.org/arch/msg/gen-art/wXKa5tadbo_xQbbUUCk9RZyB0w8
>=20
> I'm told by the authors that Alexey asked that it be submitted this way,

I asked the editor to submit a new version addressing all other
concerns. I wanted to see how the rest of the draft looks.
=20
> but the ABNF *is* wrong, and I can't see how a new draft can be allowed=20
> to be published with knowingly wrong ABNF. OTOH, the problem didn't=20
> originate with this draft. Rather the problem originated with RFC5536,=20
> and this draft has simply built on that mistake.

I was looking at your comment and it was very hard to figure out how big
of a deal it was. You are right that ABNF by itself will cause the
ordering issue that you reported. However, section 3.6 of RFC 5322 says
(ignoring for the moment trace header fields, that have some ordering):

   It is important to note that the header fields are not guaranteed to
   be in a particular order.  They may appear in any order, and they
   have been known to be reordered occasionally when transported over
   the Internet.  However, for the purposes of this specification,
   header fields SHOULD NOT be reordered when a message is transported
   or transformed.  More importantly, the trace header fields and resent
   header fields MUST NOT be reordered, and SHOULD be kept in blocks
   prepended to the message.  See sections 3.6.6 and 3.6.7 for more
   information.

So I think this already clear that header fields other than trace or
resent can appear in any order. This is effectively provides an extra
level of flexibility not covered by the ABNF from RFC 5322. As far as I
remember, none of the new header fields defined for Netnews articles are
trace or resent header fields.

> Unfortunately the root=20
> of the problem is with RFC5322, since its ABNF is structured in a way=20
> that makes it really hard to define extensions such as those in RFC5536=20
> and this draft. So the cleanest solution I can see is to revise both=20
> 5322 and 5536, and then this draft can build on those changes. That is a=
=20
> rather involved fix but I don't see any other reasonable way.

I think I agree with you that RFC 5322 could have introduced a few extra
ABNF productions to make extensibility easier.

However in short term, I think we should go with the easiest fix. Pete
suggested:

Section 3 of RFC 5536:

Original Text:

    fields          =3D/ *( approved /
                          archive /
                          control /
                          distribution /
                          expires /
                          followup-to /
                          injection-date /
                          injection-info /
                          lines /
                          newsgroups /
                          organization /
                          path /
                          summary /
                          supersedes /
                          user-agent /
                          xref )

Corrected Text:

    optional-field  =3D/ *( approved /
                          archive /
                          control /
                          distribution /
                          expires /
                          followup-to /
                          injection-date /
                          injection-info /
                          lines /
                          newsgroups /
                          organization /
                          path /
                          summary /
                          supersedes /
                          user-agent /
                          xref )

The name optional-field is a bit unfortunate, but it was always intended
for extensibility. So I think doing this change and adding a note saying
that some of Netnews header fields are mandatory (despite
"optional-field" production name) would be the best way forward.

> This prompted me to submit an erratum (#5116) on RFC5536 regarding this=20
> issue. But errata aren't often acted on quickly when they require=20
> revising RFCs.

Thank you for the erratum. Unless there is a better proposal, I will
edit resolution based on Pete's feedback and I will approve it.

> The question is: in the meantime, what to do about this draft? By=20
> default I guess I will simply restate the issue in my genart telechat=20
> review and leave it for the IESG discuss it.

As per my comments above, I think we should acknowledge that there is a
subtle issue with ABNF in RFC 5536. I think the best way forward is to
approve some fix to your erratum and let
draft-baeuerle-netnews-cancel-lock be reviewed by IESG. At this moment
it is not clear to me that work on RFC 5536 will happen any time soon,
so I don't think we should hold this draft hostage.

Best Regards,
Alexey

> Anybody have a better idea?
>=20
> 	Thanks,
> 	Paul
>=20
> On 7/14/17 12:58 PM, Paul Kyzivat wrote:
> > Michael,
> >=20
> > Please see further comments inline.
> >=20
> > (Sorry - the indenting is getting deep, but I think we are pretty much=
=20
> > done.)
> >=20
> > On 7/11/17 2:39 PM, Michael B=C3=A4uerle wrote:
> >> Paul Kyzivat wrote:
> >>> On 7/7/17 11:47 AM, Michael B=C3=A4uerle wrote:
> >>>> Paul Kyzivat wrote:
> >>>>>
> >>>>> [...]
> >>>>> General Comments:
> >>>>>
> >>>>> I have not attempted to validate the security properties of this
> >>>>> document - leaving that to a security review.
> >>>>>
> >>>>> I have also not attempted to verify the operational suitability of=
=20
> >>>>> this
> >>>>> mechanism because I don't have the experience needed to do so.
> >>>>>
> >>>>> Issues:
> >>>>>
> >>>>> Major: 1
> >>>>> Minor: 3
> >>>>> Nits:=C2=A0 0
> >>>>>
> >>>>> (1) MAJOR:
> >>>>>
> >>>>> [Problem with ABNF syntax of header fields]
> >>>>
> >>>> Hi Paul,
> >>>>
> >>>> Julien =C3=89lie has proposed a new syntax definition.
> >>>
> >>> I was copied on his mail proposing a change to RFC5536, and that is
> >>> tentative. *This* document would of course require a similar change. =
Or
> >>> else it could extend that change, via something like
> >>>
> >>> =C2=A0=C2=A0=C2=A0=C2=A0news-fields =3D/ cancel-lock / cancel-key
> >>>
> >>> But that can only be done if there is actually a draft that revises 5=
536
> >>> that can then be referenced. Bottom line is that it seems there needs=
 to
> >>> be some coordination of that fix with this draft.
> >>
> >> It's clear that the Cancel-Lock draft needs to be changed. My comment
> >> was about the potential erratum for RFC 5536 and the question:
> >> Is it (in general) possible to reference a modified ABNF definition in
> >> an erratum?
> >=20
> > I don't know of any way to do so. Perhaps somebody else can provide a=20
> > more definitive answer. You might try asking on rfc-interest.
> >=20
> >> If this is possible, then the current:
> >>
> >> =C2=A0=C2=A0=C2=A0 fields =3D/ *( cancel-lock / cancel-key )
> >>
> >> can be changed to:
> >>
> >> =C2=A0=C2=A0=C2=A0 news-fields =3D/ cancel-lock / cancel-key
> >>
> >> and should then reference the new ABNF from the erratum.
> >> If not, what about a less formal definition like this:
> >>
> >> =C2=A0=C2=A0=C2=A0 The Cancel-Lock and Cancel-Key header fields MUST b=
e treated as
> >> =C2=A0=C2=A0=C2=A0 though it were news header fields as defined in Sec=
tion 3 of
> >> =C2=A0=C2=A0=C2=A0 [RFC5536].
> >=20
> > I'm not sure about that. It might fly, or not. Again, I think you need=
=20
> > to ask somebody more authoritative.
> >=20
> >> Rewriting RFC 5322 and RFC 5536 should be avoided if possible.
> >=20
> > I understand why you might not want to take on responsibility for that.=
=20
> > But it is the right thing to do. Question is whether it needs to be don=
e=20
> > now.
> >=20
> >>>>> (2) Minor:
> >>>>>
> >>>>> In Section 3.5, step 1 says to hash the key using the algorithm=20
> >>>>> from its
> >>>>> scheme. But IIUC the scheme describes the algorithm that has already
> >>>>> been used when constructing the Cancel-Key header.
> >>>>
> >>>> No. There are two different operations that use a hash function.
> >>>>
> >>>> The recommended algorithm described in Section 4 calculates:
> >>>> |
> >>>> | K =3D HMAC(uid+mid, sec)
> >>>>
> >>>> K is then used for <c-key-string> in the Cancel-Key header field only
> >>>> with Base64 as transfer encoding (no further hash operation is used):
> >>>>
> >>>> =C2=A0=C2=A0=C2=A0=C2=A0 c-key-string =3D Base64(K)
> >>>>
> >>>> HMAC can be based on a different hash function than the one in <sche=
me>
> >>>> (because a serving agent doesn't need to know how K was calculated f=
or
> >>>> the check algorithm defined in Section 3.5).
> >>>>
> >>>> A value of e.g. "sha256" for <scheme> in a Cancel-Key header field
> >>>> doesn't mean that SHA256 was used to generate this field, but that t=
he
> >>>> corresponding Cancel-Lock header field (in the original article)=20
> >>>> contains
> >>>> the value of <c-key-string> hashed with SHA256 (and finally Base64
> >>>> encoded).
> >>>>
> >>>> The hash function defined by <scheme> is used to generate=20
> >>>> <c-lock-string>
> >>>> elements for the Cancel-Lock header field:
> >>>>
> >>>> =C2=A0=C2=A0=C2=A0=C2=A0 c-lock-string =3D Base64(hash(c-key-string))
> >>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 ^^^^
> >>>> This hash function is the one specified with <scheme> (in both match=
ing
> >>>> elements <c-lock> and <c-key> in the Cancel-Lock and Cancel-Key head=
er
> >>>> fields of the two articles involved).
> >>>>> IIUC the serving
> >>>>> agent need not hash the provided key. Rather it only uses the=20
> >>>>> scheme to
> >>>>> select the locks to compare the hash against.
> >>>>
> >>>> <scheme> is used for both purposes.
> >>>>
> >>>> Step 1 is defined in Section 3.5 as:
> >>>> |
> >>>> | 1. The <c-key-string> part of the <c-key> element is hashed using
> >>>> |=C2=A0=C2=A0=C2=A0 the algorithm defined by its <scheme> part.
> >>>>
> >>>> This is the operation for <c-lock-string> listed above.
> >>>> The hash operation is required here because if the elements from the
> >>>> Cancel-Key header field would be directly comparable, everybody could
> >>>> forge them (copy from the public original article).
> >>>> The hijack/abuse attack against <c-key-string> elements on their way
> >>>> through the network (as discussed for the review from David Mandelbe=
rg)
> >>>> is not the same. The relevant difference is who can *create* valid
> >>>> <c-key-string> elements.
> >>>>
> >>>> In Step 2 <scheme> is used again to skip <c-lock-string> elements th=
at
> >>>> were created using different hash functions. The compare operation f=
rom
> >>>> Step 2 (with first operand from Step 1) is:
> >>>>
> >>>> =C2=A0=C2=A0=C2=A0=C2=A0 Base64(hash(c-key-string)) =3D=3D c-lock-st=
ring
> >>>>
> >>>> The Base64 encode part is not explicitly noted in Step 1.
> >>>> Base64 decoding the second operand instead would work too:
> >>>>
> >>>> =C2=A0=C2=A0=C2=A0=C2=A0 hash(c-key-string) =3D=3D Base64_decode(c-l=
ock-string)
> >>>>
> >>>> To be unambiguous and consistent with the definition of <c-lock-stri=
ng>
> >>>> from Section 2.1, the words for Step 1 in Section 3.5 maybe should
> >>>> explicitly cover the Base64 encode operation. Suggestion:
> >>>>
> >>>> =C2=A0=C2=A0=C2=A0=C2=A0 1. The <c-key-string> part of the <c-key> e=
lement is hashed using
> >>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 the algorithm defined by =
its <scheme> part and then Base64
> >>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 encoded.
> >>>
> >>> Hmm. That wasn't so clear to me, though on rereading I can understand=
 it
> >>> that way.
> >>>
> >>> But in that case, what is the point of passing the scheme around at a=
ll?
> >>
> >> The <scheme> part of <c-key> elements serve the following purposes:
> >> - Backward compatibility
> >> =C2=A0=C2=A0 Existing implementations use it this way since many years
> >> - Define the hash algorithm to apply on <c-key-string> elements
> >> - Select corresponding <c-lock-string> elements to compare against
> >>
> >>> IIUC doing so doesn't add any additional security or privacy. You cou=
ld
> >>> simply pass the hashed value in cancel-key. Then the verifying agent
> >>> wouldn't do any hashing.
> >>
> >> In this case the creator of the Cancel-Key header field would not prove
> >> that he really knows K.
> >>
> >>> This would mean that the cancel-key would be
> >>> checked against locks that used a different hash, but that shouldn't
> >>> hurt anything.
> >>
> >> Yes, it is unlikely that comparing against <c-lock-string> elements,
> >> that used a different hash algorithm, will hurt.
> >>
> >> But changing the general syntax of the header fields would break
> >> backward compatibility to existing implementations. This should be
> >> avoided with highest priority.
> >=20
> > I studied the draft further. I finally get that it is simpler than I wa=
s=20
> > expecting it to be. So really it is just that the lock contains=20
> > hash(password) while the key contains the password. (The key is just an=
=20
> > algorithmically generated password.) I couldn't believe you would reall=
y=20
> > be passing the password in the clear, since that would expose it to=20
> > on-path attack. But I guess your assumption is that this is really a=20
> > one-time password, and that if it is correct then it will immediately b=
e=20
> > invalidated, and if it is wrong then it doesn't matter.
> >=20
> > So I'll withdraw my concerns on this section, except that maybe it coul=
d=20
> > be clearer. Specifically, section 3 could be more explicit about what=20
> > each distinct actor (poster, posting agent, moderator or injecting=20
> > agent) does.
> >=20
> >>> [...]
> >>> I didn't see a response from you on (4).
> >>
> >> Sorry for the delay, I was busy.
> >>
> >> | (4) Minor:
> >> |
> >> | In Section 8.1/8.2 the syntax/semantics of the Owner/Change
> >> | controller is unspecified. But IANA is charged with=20
> >> allowing/rejecting change
> >> | requests only from the "same" owner. How is IANA expected to verify
> >> | this?
> >>
> >> If it is an experimental algorithm, I see no need for strong=20
> >> authentication
> >> of external contributors.
> >>
> >> For the algorithms on the standards track, the IESG is defined as owner
> >> (may authenticate itself to IANA with a signature).
> >>
> >> | What if a change is required but the original owner is no longer
> >> | available?
> >> | E.g., the owner might be specified by email address. Later the mail
> >> | server for that email address may no longer exist.
> >>
> >> In this case the part "[...] where the owner of the registration [...]
> >> has moved out of contact [...]" can be applied.
> >=20
> > I won't belabor this point because it will clearly be an infrequent eve=
nt.
> >=20
> >  =C2=A0=C2=A0=C2=A0=C2=A0Thanks,
> >  =C2=A0=C2=A0=C2=A0=C2=A0Paul
> >=20
> > _______________________________________________
> > Gen-art mailing list
> > Gen-art@ietf.org
> > https://www.ietf.org/mailman/listinfo/gen-art
> >=20
>=20
>=20


From nobody Tue Sep 19 05:13:46 2017
Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03A4713420B; Tue, 19 Sep 2017 05:13:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level: 
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.fm header.b=MFcU1OTS; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ZisQaElM
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 V0pYU7BU3Y9C; Tue, 19 Sep 2017 05:13:42 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FD52132193; Tue, 19 Sep 2017 05:13:42 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id CA0E720854; Tue, 19 Sep 2017 08:13:41 -0400 (EDT)
Received: from web5 ([10.202.2.215]) by compute7.internal (MEProxy); Tue, 19 Sep 2017 08:13:41 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=OG4M6OEqRntpLvCEbrQIkfGm/1oJV jZSyjva5iCa4i4=; b=MFcU1OTSOWCXJQWLAbUSgQwI4SME6YYsXFG1Cx5wq8SJo LU2iRuRQZrpUbEXScsLkzg0gmCQaNV+OWzVOng/PBDYP8KbmQee87wIfVr3J73+/ VPGPHrElrx2ptXNIU+cbzGTEUKCoJ2kd7DIkWPi04u5ZCzkiVQZPEm4IwTPb4OA+ 366xoeIGYjJCvXcAQf1Zo3Mwa2OGDhNHz0Co3jcF2Tp6l7qkIxKM6c99F/0HT9Yv skIDW57rcpTy+LI16SWxVEmW5LInwI3cVdDlrpa2gcKjE6ZoMk0svwdP5klk7RuU J63pdGav4szHa6eN1bPaCRxru1H1ibAMDF1sidEiw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=OG4M6O EqRntpLvCEbrQIkfGm/1oJVjZSyjva5iCa4i4=; b=ZisQaElMD6MM67pTQG9MEn Taw4qb+ZNq/MLdpR9uEIh/thxtfq0UvTTx+0BTdJk1Otle6dRGfFNgm58ga1aifP F35w6TI/MlV/fLy+deeZ8ykqZmT5VqQVRdkw8OHuaY37Kohqcj3zmY/+0lbCrB6W Ah04jSOXmwBHjlcKzS94Rx+QqiVySxeAHSvFwDX+5zwfllCwrhLEPfAoqaRPLN7g h0aLeJhl+bdxm+Pe62Q8iYZu9VZKjmpCajmFtyx1fp698pfk7Mzj5THvoIsrheeL yRkD+V7x98PNX86I70QA2je+v+cAY2LMNs1vwiVglXg42AqEGdl8TWc2NQIX8Dqg ==
X-ME-Sender: <xms:9QnBWbID9DMr1qDpmRzhDk6hhVld1dgrbZjDC9H6Hm-aDqfMXjOheA>
Received: by mailuser.nyi.internal (Postfix, from userid 99) id A4DF09E2E0; Tue, 19 Sep 2017 08:13:41 -0400 (EDT)
Message-Id: <1505823221.2181948.1111036680.2C045859@webmail.messagingengine.com>
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, draft-baeuerle-netnews-cancel-lock.all@ietf.org, Pete Resnick <presnick@qti.qualcomm.com>
Cc: General Area Review Team <gen-art@ietf.org>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-64b08692
Date: Tue, 19 Sep 2017 13:13:41 +0100
In-Reply-To: <1505814165.1516258.1110891352.7E7D795F@webmail.messagingengine.com>
References: <9be2e7af-b99d-4f86-6552-bfada936600d@alum.mit.edu> <20170707174750.487009ed@WStation4> <7452e826-62e9-0d6e-32b5-dcdefcb4c2ea@alum.mit.edu> <20170711203934.458e3b62@WStation4> <37001dcd-6551-78b4-18e7-75fbebaff761@alum.mit.edu> <0147f247-2763-8017-f123-5cdd6ceb06b3@alum.mit.edu> <1505814165.1516258.1110891352.7E7D795F@webmail.messagingengine.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/KQr1UNAvc76A05Sj4o3OiXtiOjY>
Subject: Re: [Gen-art] draft-baeuerle-netnews-cancel-lock-06 and RFCs 5536 & 5322
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Sep 2017 12:13:45 -0000

On Tue, Sep 19, 2017, at 10:42 AM, Alexey Melnikov wrote:
> Hi Paul,
>=20
> On Mon, Sep 18, 2017, at 10:14 PM, Paul Kyzivat wrote:
> > I'm on tap to do the genart telechat review on=20
> > draft-baeuerle-netnews-cancel-lock-06. I see that nothing has been done=
=20
> > about the ABNF that was my primary concern in my prior wglc review of
> > -05:
> >=20
> > https://mailarchive.ietf.org/arch/msg/gen-art/wXKa5tadbo_xQbbUUCk9RZyB0=
w8
> >=20
> > I'm told by the authors that Alexey asked that it be submitted this way,
>=20
> I asked the editor to submit a new version addressing all other
> concerns. I wanted to see how the rest of the draft looks.
>=20=20
> > but the ABNF *is* wrong, and I can't see how a new draft can be allowed=
=20
> > to be published with knowingly wrong ABNF. OTOH, the problem didn't=20
> > originate with this draft. Rather the problem originated with RFC5536,=
=20
> > and this draft has simply built on that mistake.
>=20
> I was looking at your comment and it was very hard to figure out how big
> of a deal it was. You are right that ABNF by itself will cause the
> ordering issue that you reported. However, section 3.6 of RFC 5322 says
> (ignoring for the moment trace header fields, that have some ordering):
>=20
>    It is important to note that the header fields are not guaranteed to
>    be in a particular order.  They may appear in any order, and they
>    have been known to be reordered occasionally when transported over
>    the Internet.  However, for the purposes of this specification,
>    header fields SHOULD NOT be reordered when a message is transported
>    or transformed.  More importantly, the trace header fields and resent
>    header fields MUST NOT be reordered, and SHOULD be kept in blocks
>    prepended to the message.  See sections 3.6.6 and 3.6.7 for more
>    information.
>=20
> So I think this already clear that header fields other than trace or
> resent can appear in any order. This is effectively provides an extra
> level of flexibility not covered by the ABNF from RFC 5322. As far as I
> remember, none of the new header fields defined for Netnews articles are
> trace or resent header fields.
>=20
> > Unfortunately the root=20
> > of the problem is with RFC5322, since its ABNF is structured in a way=20
> > that makes it really hard to define extensions such as those in RFC5536=
=20
> > and this draft. So the cleanest solution I can see is to revise both=20
> > 5322 and 5536, and then this draft can build on those changes. That is =
a=20
> > rather involved fix but I don't see any other reasonable way.
>=20
> I think I agree with you that RFC 5322 could have introduced a few extra
> ABNF productions to make extensibility easier.
>=20
> However in short term, I think we should go with the easiest fix. Pete
> suggested:
>=20
> Section 3 of RFC 5536:
>=20
> Original Text:
>=20
>     fields          =3D/ *( approved /
>                           archive /
>                           control /
>                           distribution /
>                           expires /
>                           followup-to /
>                           injection-date /
>                           injection-info /
>                           lines /
>                           newsgroups /
>                           organization /
>                           path /
>                           summary /
>                           supersedes /
>                           user-agent /
>                           xref )
>=20
> Corrected Text:
>=20
>     optional-field  =3D/ *( approved /

Just to clarify: optional-field is defined in RFC 5322 and is
specifically designed for extensibility.

We can also drop "*" in front of "(approved", as this field is already
allowed multiple times in an RFC 5322 message.

>                           archive /
>                           control /
>                           distribution /
>                           expires /
>                           followup-to /
>                           injection-date /
>                           injection-info /
>                           lines /
>                           newsgroups /
>                           organization /
>                           path /
>                           summary /
>                           supersedes /
>                           user-agent /
>                           xref )
>=20
> The name optional-field is a bit unfortunate, but it was always intended
> for extensibility. So I think doing this change and adding a note saying
> that some of Netnews header fields are mandatory (despite
> "optional-field" production name) would be the best way forward.
>=20
> > This prompted me to submit an erratum (#5116) on RFC5536 regarding this=
=20
> > issue. But errata aren't often acted on quickly when they require=20
> > revising RFCs.
>=20
> Thank you for the erratum. Unless there is a better proposal, I will
> edit resolution based on Pete's feedback and I will approve it.
>=20
> > The question is: in the meantime, what to do about this draft? By=20
> > default I guess I will simply restate the issue in my genart telechat=20
> > review and leave it for the IESG discuss it.
>=20
> As per my comments above, I think we should acknowledge that there is a
> subtle issue with ABNF in RFC 5536. I think the best way forward is to
> approve some fix to your erratum and let
> draft-baeuerle-netnews-cancel-lock be reviewed by IESG. At this moment
> it is not clear to me that work on RFC 5536 will happen any time soon,
> so I don't think we should hold this draft hostage.
>=20
> Best Regards,
> Alexey
>=20
> > Anybody have a better idea?
> >=20
> > 	Thanks,
> > 	Paul
> >=20
> > On 7/14/17 12:58 PM, Paul Kyzivat wrote:
> > > Michael,
> > >=20
> > > Please see further comments inline.
> > >=20
> > > (Sorry - the indenting is getting deep, but I think we are pretty muc=
h=20
> > > done.)
> > >=20
> > > On 7/11/17 2:39 PM, Michael B=C3=A4uerle wrote:
> > >> Paul Kyzivat wrote:
> > >>> On 7/7/17 11:47 AM, Michael B=C3=A4uerle wrote:
> > >>>> Paul Kyzivat wrote:
> > >>>>>
> > >>>>> [...]
> > >>>>> General Comments:
> > >>>>>
> > >>>>> I have not attempted to validate the security properties of this
> > >>>>> document - leaving that to a security review.
> > >>>>>
> > >>>>> I have also not attempted to verify the operational suitability o=
f=20
> > >>>>> this
> > >>>>> mechanism because I don't have the experience needed to do so.
> > >>>>>
> > >>>>> Issues:
> > >>>>>
> > >>>>> Major: 1
> > >>>>> Minor: 3
> > >>>>> Nits:=C2=A0 0
> > >>>>>
> > >>>>> (1) MAJOR:
> > >>>>>
> > >>>>> [Problem with ABNF syntax of header fields]
> > >>>>
> > >>>> Hi Paul,
> > >>>>
> > >>>> Julien =C3=89lie has proposed a new syntax definition.
> > >>>
> > >>> I was copied on his mail proposing a change to RFC5536, and that is
> > >>> tentative. *This* document would of course require a similar change=
. Or
> > >>> else it could extend that change, via something like
> > >>>
> > >>> =C2=A0=C2=A0=C2=A0=C2=A0news-fields =3D/ cancel-lock / cancel-key
> > >>>
> > >>> But that can only be done if there is actually a draft that revises=
 5536
> > >>> that can then be referenced. Bottom line is that it seems there nee=
ds to
> > >>> be some coordination of that fix with this draft.
> > >>
> > >> It's clear that the Cancel-Lock draft needs to be changed. My comment
> > >> was about the potential erratum for RFC 5536 and the question:
> > >> Is it (in general) possible to reference a modified ABNF definition =
in
> > >> an erratum?
> > >=20
> > > I don't know of any way to do so. Perhaps somebody else can provide a=
=20
> > > more definitive answer. You might try asking on rfc-interest.
> > >=20
> > >> If this is possible, then the current:
> > >>
> > >> =C2=A0=C2=A0=C2=A0 fields =3D/ *( cancel-lock / cancel-key )
> > >>
> > >> can be changed to:
> > >>
> > >> =C2=A0=C2=A0=C2=A0 news-fields =3D/ cancel-lock / cancel-key
> > >>
> > >> and should then reference the new ABNF from the erratum.
> > >> If not, what about a less formal definition like this:
> > >>
> > >> =C2=A0=C2=A0=C2=A0 The Cancel-Lock and Cancel-Key header fields MUST=
 be treated as
> > >> =C2=A0=C2=A0=C2=A0 though it were news header fields as defined in S=
ection 3 of
> > >> =C2=A0=C2=A0=C2=A0 [RFC5536].
> > >=20
> > > I'm not sure about that. It might fly, or not. Again, I think you nee=
d=20
> > > to ask somebody more authoritative.
> > >=20
> > >> Rewriting RFC 5322 and RFC 5536 should be avoided if possible.
> > >=20
> > > I understand why you might not want to take on responsibility for tha=
t.=20
> > > But it is the right thing to do. Question is whether it needs to be d=
one=20
> > > now.
> > >=20
> > >>>>> (2) Minor:
> > >>>>>
> > >>>>> In Section 3.5, step 1 says to hash the key using the algorithm=20
> > >>>>> from its
> > >>>>> scheme. But IIUC the scheme describes the algorithm that has alre=
ady
> > >>>>> been used when constructing the Cancel-Key header.
> > >>>>
> > >>>> No. There are two different operations that use a hash function.
> > >>>>
> > >>>> The recommended algorithm described in Section 4 calculates:
> > >>>> |
> > >>>> | K =3D HMAC(uid+mid, sec)
> > >>>>
> > >>>> K is then used for <c-key-string> in the Cancel-Key header field o=
nly
> > >>>> with Base64 as transfer encoding (no further hash operation is use=
d):
> > >>>>
> > >>>> =C2=A0=C2=A0=C2=A0=C2=A0 c-key-string =3D Base64(K)
> > >>>>
> > >>>> HMAC can be based on a different hash function than the one in <sc=
heme>
> > >>>> (because a serving agent doesn't need to know how K was calculated=
 for
> > >>>> the check algorithm defined in Section 3.5).
> > >>>>
> > >>>> A value of e.g. "sha256" for <scheme> in a Cancel-Key header field
> > >>>> doesn't mean that SHA256 was used to generate this field, but that=
 the
> > >>>> corresponding Cancel-Lock header field (in the original article)=20
> > >>>> contains
> > >>>> the value of <c-key-string> hashed with SHA256 (and finally Base64
> > >>>> encoded).
> > >>>>
> > >>>> The hash function defined by <scheme> is used to generate=20
> > >>>> <c-lock-string>
> > >>>> elements for the Cancel-Lock header field:
> > >>>>
> > >>>> =C2=A0=C2=A0=C2=A0=C2=A0 c-lock-string =3D Base64(hash(c-key-strin=
g))
> > >>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 ^^^^
> > >>>> This hash function is the one specified with <scheme> (in both mat=
ching
> > >>>> elements <c-lock> and <c-key> in the Cancel-Lock and Cancel-Key he=
ader
> > >>>> fields of the two articles involved).
> > >>>>> IIUC the serving
> > >>>>> agent need not hash the provided key. Rather it only uses the=20
> > >>>>> scheme to
> > >>>>> select the locks to compare the hash against.
> > >>>>
> > >>>> <scheme> is used for both purposes.
> > >>>>
> > >>>> Step 1 is defined in Section 3.5 as:
> > >>>> |
> > >>>> | 1. The <c-key-string> part of the <c-key> element is hashed using
> > >>>> |=C2=A0=C2=A0=C2=A0 the algorithm defined by its <scheme> part.
> > >>>>
> > >>>> This is the operation for <c-lock-string> listed above.
> > >>>> The hash operation is required here because if the elements from t=
he
> > >>>> Cancel-Key header field would be directly comparable, everybody co=
uld
> > >>>> forge them (copy from the public original article).
> > >>>> The hijack/abuse attack against <c-key-string> elements on their w=
ay
> > >>>> through the network (as discussed for the review from David Mandel=
berg)
> > >>>> is not the same. The relevant difference is who can *create* valid
> > >>>> <c-key-string> elements.
> > >>>>
> > >>>> In Step 2 <scheme> is used again to skip <c-lock-string> elements =
that
> > >>>> were created using different hash functions. The compare operation=
 from
> > >>>> Step 2 (with first operand from Step 1) is:
> > >>>>
> > >>>> =C2=A0=C2=A0=C2=A0=C2=A0 Base64(hash(c-key-string)) =3D=3D c-lock-=
string
> > >>>>
> > >>>> The Base64 encode part is not explicitly noted in Step 1.
> > >>>> Base64 decoding the second operand instead would work too:
> > >>>>
> > >>>> =C2=A0=C2=A0=C2=A0=C2=A0 hash(c-key-string) =3D=3D Base64_decode(c=
-lock-string)
> > >>>>
> > >>>> To be unambiguous and consistent with the definition of <c-lock-st=
ring>
> > >>>> from Section 2.1, the words for Step 1 in Section 3.5 maybe should
> > >>>> explicitly cover the Base64 encode operation. Suggestion:
> > >>>>
> > >>>> =C2=A0=C2=A0=C2=A0=C2=A0 1. The <c-key-string> part of the <c-key>=
 element is hashed using
> > >>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 the algorithm defined b=
y its <scheme> part and then Base64
> > >>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 encoded.
> > >>>
> > >>> Hmm. That wasn't so clear to me, though on rereading I can understa=
nd it
> > >>> that way.
> > >>>
> > >>> But in that case, what is the point of passing the scheme around at=
 all?
> > >>
> > >> The <scheme> part of <c-key> elements serve the following purposes:
> > >> - Backward compatibility
> > >> =C2=A0=C2=A0 Existing implementations use it this way since many yea=
rs
> > >> - Define the hash algorithm to apply on <c-key-string> elements
> > >> - Select corresponding <c-lock-string> elements to compare against
> > >>
> > >>> IIUC doing so doesn't add any additional security or privacy. You c=
ould
> > >>> simply pass the hashed value in cancel-key. Then the verifying agent
> > >>> wouldn't do any hashing.
> > >>
> > >> In this case the creator of the Cancel-Key header field would not pr=
ove
> > >> that he really knows K.
> > >>
> > >>> This would mean that the cancel-key would be
> > >>> checked against locks that used a different hash, but that shouldn't
> > >>> hurt anything.
> > >>
> > >> Yes, it is unlikely that comparing against <c-lock-string> elements,
> > >> that used a different hash algorithm, will hurt.
> > >>
> > >> But changing the general syntax of the header fields would break
> > >> backward compatibility to existing implementations. This should be
> > >> avoided with highest priority.
> > >=20
> > > I studied the draft further. I finally get that it is simpler than I =
was=20
> > > expecting it to be. So really it is just that the lock contains=20
> > > hash(password) while the key contains the password. (The key is just =
an=20
> > > algorithmically generated password.) I couldn't believe you would rea=
lly=20
> > > be passing the password in the clear, since that would expose it to=20
> > > on-path attack. But I guess your assumption is that this is really a=
=20
> > > one-time password, and that if it is correct then it will immediately=
 be=20
> > > invalidated, and if it is wrong then it doesn't matter.
> > >=20
> > > So I'll withdraw my concerns on this section, except that maybe it co=
uld=20
> > > be clearer. Specifically, section 3 could be more explicit about what=
=20
> > > each distinct actor (poster, posting agent, moderator or injecting=20
> > > agent) does.
> > >=20
> > >>> [...]
> > >>> I didn't see a response from you on (4).
> > >>
> > >> Sorry for the delay, I was busy.
> > >>
> > >> | (4) Minor:
> > >> |
> > >> | In Section 8.1/8.2 the syntax/semantics of the Owner/Change
> > >> | controller is unspecified. But IANA is charged with=20
> > >> allowing/rejecting change
> > >> | requests only from the "same" owner. How is IANA expected to verify
> > >> | this?
> > >>
> > >> If it is an experimental algorithm, I see no need for strong=20
> > >> authentication
> > >> of external contributors.
> > >>
> > >> For the algorithms on the standards track, the IESG is defined as ow=
ner
> > >> (may authenticate itself to IANA with a signature).
> > >>
> > >> | What if a change is required but the original owner is no longer
> > >> | available?
> > >> | E.g., the owner might be specified by email address. Later the mail
> > >> | server for that email address may no longer exist.
> > >>
> > >> In this case the part "[...] where the owner of the registration [..=
.]
> > >> has moved out of contact [...]" can be applied.
> > >=20
> > > I won't belabor this point because it will clearly be an infrequent e=
vent.
> > >=20
> > >  =C2=A0=C2=A0=C2=A0=C2=A0Thanks,
> > >  =C2=A0=C2=A0=C2=A0=C2=A0Paul
> > >=20
> > > _______________________________________________
> > > Gen-art mailing list
> > > Gen-art@ietf.org
> > > https://www.ietf.org/mailman/listinfo/gen-art
> > >=20
> >=20
> >=20


From nobody Tue Sep 19 07:00:49 2017
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3BC813432F; Tue, 19 Sep 2017 07:00:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 pnVFKo8vM_Q6; Tue, 19 Sep 2017 07:00:44 -0700 (PDT)
Received: from alum-mailsec-scanner-5.mit.edu (alum-mailsec-scanner-5.mit.edu [18.7.68.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7831213423D;  Tue, 19 Sep 2017 07:00:44 -0700 (PDT)
X-AuditID: 12074411-f95ff70000007f0a-8c-59c12307cd4a
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by alum-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP id F3.8C.32522.70321C95; Tue, 19 Sep 2017 10:00:39 -0400 (EDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id v8JE0cG6023883 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 19 Sep 2017 10:00:38 -0400
To: Alexey Melnikov <aamelnikov@fastmail.fm>, draft-baeuerle-netnews-cancel-lock.all@ietf.org, Pete Resnick <presnick@qti.qualcomm.com>
Cc: General Area Review Team <gen-art@ietf.org>
References: <9be2e7af-b99d-4f86-6552-bfada936600d@alum.mit.edu> <20170707174750.487009ed@WStation4> <7452e826-62e9-0d6e-32b5-dcdefcb4c2ea@alum.mit.edu> <20170711203934.458e3b62@WStation4> <37001dcd-6551-78b4-18e7-75fbebaff761@alum.mit.edu> <0147f247-2763-8017-f123-5cdd6ceb06b3@alum.mit.edu> <1505814165.1516258.1110891352.7E7D795F@webmail.messagingengine.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <38d90b33-4edf-8bba-9bfe-9b5f5a0890d3@alum.mit.edu>
Date: Tue, 19 Sep 2017 10:00:38 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <1505814165.1516258.1110891352.7E7D795F@webmail.messagingengine.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCKsWRmVeSWpSXmKPExsUixO6iqMupfDDSYOE7a4v97w8xWbSv+MJk cfXVZxaLK1dbmB1YPHaeOsDmsWTJTyaPRVOfMQYwR3HZpKTmZJalFunbJXBl3Djzh7VgVg9j xau/L5kaGPdkdDFyckgImEicf7WSCcQWEtjBJNHVU9rFyAVkP2SS6L68mLWLkZ1DWMBdYkk5 SFhEYCajxMJJx9lB6pkF9CX+PlnMBFH/hUli59TdrCAJNgEtiTmH/rOA2LwC9hK7rj5lBrFZ BFQlXk3YBWaLCqRJ/Nt9lhGiRlDi5MwnYPWcAoESy85+YYJYYCYxb/NDZghbXOLWk/lQcXmJ 5q2zmScwCsxC0j4LScssJC2zkLQsYGRZxSiXmFOaq5ubmJlTnJqsW5ycmJeXWqRrqpebWaKX mlK6iRES4II7GGeclDvEKMDBqMTDK3Btf6QQa2JZcWXuIUZJDiYlUV5lhYORQnxJ+SmVGYnF GfFFpTmpxYcYJTiYlUR4tWSBcrwpiZVVqUX5MClpDhYlcV6+Jep+QgLpiSWp2ampBalFMFkZ Dg4lCd7JikCNgkWp6akVaZk5JQhpJg5OkOE8QMNngNTwFhck5hZnpkPkTzHqcvT03PjDJMSS l5+XKiXOawpSJABSlFGaBzcHlpheMYoDvSXMOw2kigeY1OAmvQJawgS0JHvDAZAlJYkIKakG xplV5ydGHJn843jpl5U2XNVL5iXMPKAR+TSnw2h+xeftTGoHQ5esYNmQdHjioTCDvu11nrfm ah01WaiQuer/pEM79f5q/H/7Yv25aDPlt+axcpw8O3+me6z7u+709FCrMwwrPdSSnyuYBYmL WtiZ29X6BMrYcG7hVk1z79nxyWP2UTepjsVMnUosxRmJhlrMRcWJABfFeVknAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/4LdNwZbt7hdmEh9aa_6lbZbZJpg>
Subject: Re: [Gen-art] draft-baeuerle-netnews-cancel-lock-06 and RFCs 5536 & 5322
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Sep 2017 14:00:48 -0000

Hi Alexey,

On 9/19/17 5:42 AM, Alexey Melnikov wrote:
> Hi Paul,
> 
> On Mon, Sep 18, 2017, at 10:14 PM, Paul Kyzivat wrote:
>> I'm on tap to do the genart telechat review on
>> draft-baeuerle-netnews-cancel-lock-06. I see that nothing has been done
>> about the ABNF that was my primary concern in my prior wglc review of
>> -05:
>>
>> https://mailarchive.ietf.org/arch/msg/gen-art/wXKa5tadbo_xQbbUUCk9RZyB0w8
>>
>> I'm told by the authors that Alexey asked that it be submitted this way,
> 
> I asked the editor to submit a new version addressing all other
> concerns. I wanted to see how the rest of the draft looks.
>   
>> but the ABNF *is* wrong, and I can't see how a new draft can be allowed
>> to be published with knowingly wrong ABNF. OTOH, the problem didn't
>> originate with this draft. Rather the problem originated with RFC5536,
>> and this draft has simply built on that mistake.
> 
> I was looking at your comment and it was very hard to figure out how big
> of a deal it was. You are right that ABNF by itself will cause the
> ordering issue that you reported. However, section 3.6 of RFC 5322 says
> (ignoring for the moment trace header fields, that have some ordering):
> 
>     It is important to note that the header fields are not guaranteed to
>     be in a particular order.  They may appear in any order, and they
>     have been known to be reordered occasionally when transported over
>     the Internet.  However, for the purposes of this specification,
>     header fields SHOULD NOT be reordered when a message is transported
>     or transformed.  More importantly, the trace header fields and resent
>     header fields MUST NOT be reordered, and SHOULD be kept in blocks
>     prepended to the message.  See sections 3.6.6 and 3.6.7 for more
>     information.
> 
> So I think this already clear that header fields other than trace or
> resent can appear in any order. This is effectively provides an extra
> level of flexibility not covered by the ABNF from RFC 5322. As far as I
> remember, none of the new header fields defined for Netnews articles are
> trace or resent header fields.

I guess this can be read as providing some wiggle room, though in the 
context of the existing 5322 text this statement seems *consistent* with 
the ABNF, and so might not be read as providing extra latitude.

>> Unfortunately the root
>> of the problem is with RFC5322, since its ABNF is structured in a way
>> that makes it really hard to define extensions such as those in RFC5536
>> and this draft. So the cleanest solution I can see is to revise both
>> 5322 and 5536, and then this draft can build on those changes. That is a
>> rather involved fix but I don't see any other reasonable way.
> 
> I think I agree with you that RFC 5322 could have introduced a few extra
> ABNF productions to make extensibility easier.
> 
> However in short term, I think we should go with the easiest fix. Pete
> suggested:
> 
> Section 3 of RFC 5536:
> 
> Original Text:
> 
>      fields          =/ *( approved /
>                            archive /
>                            control /
>                            distribution /
>                            expires /
>                            followup-to /
>                            injection-date /
>                            injection-info /
>                            lines /
>                            newsgroups /
>                            organization /
>                            path /
>                            summary /
>                            supersedes /
>                            user-agent /
>                            xref )
> 
> Corrected Text:
> 
>      optional-field  =/ *( approved /
>                            archive /
>                            control /
>                            distribution /
>                            expires /
>                            followup-to /
>                            injection-date /
>                            injection-info /
>                            lines /
>                            newsgroups /
>                            organization /
>                            path /
>                            summary /
>                            supersedes /
>                            user-agent /
>                            xref )

I see one issue with the above. <optional-field> appears *twice* in the 
definition of <fields> in 5322. I don't understand what the intent was 
there - whether it was a mistake or was trying to express something that 
I am missing. This really needs some further discussion. (E.g., should 
the valid values for <optional-field> as used with trace be distinct 
from those in its later appearance? This needs to be thrashed out with 
mail experts before this fix is finalized. I don't know what forum is 
appropriate for that.

Ignoring that, I agree this change to 5536 would achieve the goal 
without requiring a change in 5322, which is progress. However I think a 
tweak to the above would be be a bit cleaner:

     optional-field  =/    approved /
                           archive /
                           control /
                           distribution /
                           expires /
                           followup-to /
                           injection-date /
                           injection-info /
                           lines /
                           newsgroups /
                           organization /
                           path /
                           summary /
                           supersedes /
                           user-agent /
                           xref

This is definitely a better fix than I was suggesting. (Thank you Pete!)


> The name optional-field is a bit unfortunate, but it was always intended
> for extensibility. So I think doing this change and adding a note saying
> that some of Netnews header fields are mandatory (despite
> "optional-field" production name) would be the best way forward.

Even as it is currently written the *intent* of the current ABNF in 5536 
is that all of the netnews header fields be optional. And syntactically 
it allows them to be repeated multiple times but specifically forbids 
that in text. Section 3.1 uses text to specify that certain of those 
fields are actually mandatory. (Writing ABNF that allows fields to be in 
any order while making some at-most-once and some entirely optional is 
not practical.) So I don't think any new text is needed for this.

>> This prompted me to submit an erratum (#5116) on RFC5536 regarding this
>> issue. But errata aren't often acted on quickly when they require
>> revising RFCs.
> 
> Thank you for the erratum. Unless there is a better proposal, I will
> edit resolution based on Pete's feedback and I will approve it.
> 
>> The question is: in the meantime, what to do about this draft? By
>> default I guess I will simply restate the issue in my genart telechat
>> review and leave it for the IESG discuss it.
> 
> As per my comments above, I think we should acknowledge that there is a
> subtle issue with ABNF in RFC 5536. I think the best way forward is to
> approve some fix to your erratum and let
> draft-baeuerle-netnews-cancel-lock be reviewed by IESG. At this moment
> it is not clear to me that work on RFC 5536 will happen any time soon,
> so I don't think we should hold this draft hostage.

I don't see any reason to hold it hostage if there is a path forward 
that gets everything fixed. The work-around above can be used 
independently in 5536 and draft-baeuerle-netnews-cancel-lock, so they 
can proceed independently.

I will update my erratum to include the fix above, and write my genart 
telechat review to recommend the same fix.

	Thanks,
	Paul

> Best Regards,
> Alexey
> 
>> Anybody have a better idea?
>>
>> 	Thanks,
>> 	Paul
>>
>> On 7/14/17 12:58 PM, Paul Kyzivat wrote:
>>> Michael,
>>>
>>> Please see further comments inline.
>>>
>>> (Sorry - the indenting is getting deep, but I think we are pretty much
>>> done.)
>>>
>>> On 7/11/17 2:39 PM, Michael BÃ¤uerle wrote:
>>>> Paul Kyzivat wrote:
>>>>> On 7/7/17 11:47 AM, Michael BÃ¤uerle wrote:
>>>>>> Paul Kyzivat wrote:
>>>>>>>
>>>>>>> [...]
>>>>>>> General Comments:
>>>>>>>
>>>>>>> I have not attempted to validate the security properties of this
>>>>>>> document - leaving that to a security review.
>>>>>>>
>>>>>>> I have also not attempted to verify the operational suitability of
>>>>>>> this
>>>>>>> mechanism because I don't have the experience needed to do so.
>>>>>>>
>>>>>>> Issues:
>>>>>>>
>>>>>>> Major: 1
>>>>>>> Minor: 3
>>>>>>> Nits:Â  0
>>>>>>>
>>>>>>> (1) MAJOR:
>>>>>>>
>>>>>>> [Problem with ABNF syntax of header fields]
>>>>>>
>>>>>> Hi Paul,
>>>>>>
>>>>>> Julien Ã‰lie has proposed a new syntax definition.
>>>>>
>>>>> I was copied on his mail proposing a change to RFC5536, and that is
>>>>> tentative. *This* document would of course require a similar change. Or
>>>>> else it could extend that change, via something like
>>>>>
>>>>>  Â Â Â Â news-fields =/ cancel-lock / cancel-key
>>>>>
>>>>> But that can only be done if there is actually a draft that revises 5536
>>>>> that can then be referenced. Bottom line is that it seems there needs to
>>>>> be some coordination of that fix with this draft.
>>>>
>>>> It's clear that the Cancel-Lock draft needs to be changed. My comment
>>>> was about the potential erratum for RFC 5536 and the question:
>>>> Is it (in general) possible to reference a modified ABNF definition in
>>>> an erratum?
>>>
>>> I don't know of any way to do so. Perhaps somebody else can provide a
>>> more definitive answer. You might try asking on rfc-interest.
>>>
>>>> If this is possible, then the current:
>>>>
>>>>  Â Â Â  fields =/ *( cancel-lock / cancel-key )
>>>>
>>>> can be changed to:
>>>>
>>>>  Â Â Â  news-fields =/ cancel-lock / cancel-key
>>>>
>>>> and should then reference the new ABNF from the erratum.
>>>> If not, what about a less formal definition like this:
>>>>
>>>>  Â Â Â  The Cancel-Lock and Cancel-Key header fields MUST be treated as
>>>>  Â Â Â  though it were news header fields as defined in Section 3 of
>>>>  Â Â Â  [RFC5536].
>>>
>>> I'm not sure about that. It might fly, or not. Again, I think you need
>>> to ask somebody more authoritative.
>>>
>>>> Rewriting RFC 5322 and RFC 5536 should be avoided if possible.
>>>
>>> I understand why you might not want to take on responsibility for that.
>>> But it is the right thing to do. Question is whether it needs to be done
>>> now.
>>>
>>>>>>> (2) Minor:
>>>>>>>
>>>>>>> In Section 3.5, step 1 says to hash the key using the algorithm
>>>>>>> from its
>>>>>>> scheme. But IIUC the scheme describes the algorithm that has already
>>>>>>> been used when constructing the Cancel-Key header.
>>>>>>
>>>>>> No. There are two different operations that use a hash function.
>>>>>>
>>>>>> The recommended algorithm described in Section 4 calculates:
>>>>>> |
>>>>>> | K = HMAC(uid+mid, sec)
>>>>>>
>>>>>> K is then used for <c-key-string> in the Cancel-Key header field only
>>>>>> with Base64 as transfer encoding (no further hash operation is used):
>>>>>>
>>>>>>  Â Â Â Â  c-key-string = Base64(K)
>>>>>>
>>>>>> HMAC can be based on a different hash function than the one in <scheme>
>>>>>> (because a serving agent doesn't need to know how K was calculated for
>>>>>> the check algorithm defined in Section 3.5).
>>>>>>
>>>>>> A value of e.g. "sha256" for <scheme> in a Cancel-Key header field
>>>>>> doesn't mean that SHA256 was used to generate this field, but that the
>>>>>> corresponding Cancel-Lock header field (in the original article)
>>>>>> contains
>>>>>> the value of <c-key-string> hashed with SHA256 (and finally Base64
>>>>>> encoded).
>>>>>>
>>>>>> The hash function defined by <scheme> is used to generate
>>>>>> <c-lock-string>
>>>>>> elements for the Cancel-Lock header field:
>>>>>>
>>>>>>  Â Â Â Â  c-lock-string = Base64(hash(c-key-string))
>>>>>>  Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  ^^^^
>>>>>> This hash function is the one specified with <scheme> (in both matching
>>>>>> elements <c-lock> and <c-key> in the Cancel-Lock and Cancel-Key header
>>>>>> fields of the two articles involved).
>>>>>>> IIUC the serving
>>>>>>> agent need not hash the provided key. Rather it only uses the
>>>>>>> scheme to
>>>>>>> select the locks to compare the hash against.
>>>>>>
>>>>>> <scheme> is used for both purposes.
>>>>>>
>>>>>> Step 1 is defined in Section 3.5 as:
>>>>>> |
>>>>>> | 1. The <c-key-string> part of the <c-key> element is hashed using
>>>>>> |Â Â Â  the algorithm defined by its <scheme> part.
>>>>>>
>>>>>> This is the operation for <c-lock-string> listed above.
>>>>>> The hash operation is required here because if the elements from the
>>>>>> Cancel-Key header field would be directly comparable, everybody could
>>>>>> forge them (copy from the public original article).
>>>>>> The hijack/abuse attack against <c-key-string> elements on their way
>>>>>> through the network (as discussed for the review from David Mandelberg)
>>>>>> is not the same. The relevant difference is who can *create* valid
>>>>>> <c-key-string> elements.
>>>>>>
>>>>>> In Step 2 <scheme> is used again to skip <c-lock-string> elements that
>>>>>> were created using different hash functions. The compare operation from
>>>>>> Step 2 (with first operand from Step 1) is:
>>>>>>
>>>>>>  Â Â Â Â  Base64(hash(c-key-string)) == c-lock-string
>>>>>>
>>>>>> The Base64 encode part is not explicitly noted in Step 1.
>>>>>> Base64 decoding the second operand instead would work too:
>>>>>>
>>>>>>  Â Â Â Â  hash(c-key-string) == Base64_decode(c-lock-string)
>>>>>>
>>>>>> To be unambiguous and consistent with the definition of <c-lock-string>
>>>>>> from Section 2.1, the words for Step 1 in Section 3.5 maybe should
>>>>>> explicitly cover the Base64 encode operation. Suggestion:
>>>>>>
>>>>>>  Â Â Â Â  1. The <c-key-string> part of the <c-key> element is hashed using
>>>>>>  Â Â Â Â Â Â Â  the algorithm defined by its <scheme> part and then Base64
>>>>>>  Â Â Â Â Â Â Â  encoded.
>>>>>
>>>>> Hmm. That wasn't so clear to me, though on rereading I can understand it
>>>>> that way.
>>>>>
>>>>> But in that case, what is the point of passing the scheme around at all?
>>>>
>>>> The <scheme> part of <c-key> elements serve the following purposes:
>>>> - Backward compatibility
>>>>  Â Â  Existing implementations use it this way since many years
>>>> - Define the hash algorithm to apply on <c-key-string> elements
>>>> - Select corresponding <c-lock-string> elements to compare against
>>>>
>>>>> IIUC doing so doesn't add any additional security or privacy. You could
>>>>> simply pass the hashed value in cancel-key. Then the verifying agent
>>>>> wouldn't do any hashing.
>>>>
>>>> In this case the creator of the Cancel-Key header field would not prove
>>>> that he really knows K.
>>>>
>>>>> This would mean that the cancel-key would be
>>>>> checked against locks that used a different hash, but that shouldn't
>>>>> hurt anything.
>>>>
>>>> Yes, it is unlikely that comparing against <c-lock-string> elements,
>>>> that used a different hash algorithm, will hurt.
>>>>
>>>> But changing the general syntax of the header fields would break
>>>> backward compatibility to existing implementations. This should be
>>>> avoided with highest priority.
>>>
>>> I studied the draft further. I finally get that it is simpler than I was
>>> expecting it to be. So really it is just that the lock contains
>>> hash(password) while the key contains the password. (The key is just an
>>> algorithmically generated password.) I couldn't believe you would really
>>> be passing the password in the clear, since that would expose it to
>>> on-path attack. But I guess your assumption is that this is really a
>>> one-time password, and that if it is correct then it will immediately be
>>> invalidated, and if it is wrong then it doesn't matter.
>>>
>>> So I'll withdraw my concerns on this section, except that maybe it could
>>> be clearer. Specifically, section 3 could be more explicit about what
>>> each distinct actor (poster, posting agent, moderator or injecting
>>> agent) does.
>>>
>>>>> [...]
>>>>> I didn't see a response from you on (4).
>>>>
>>>> Sorry for the delay, I was busy.
>>>>
>>>> | (4) Minor:
>>>> |
>>>> | In Section 8.1/8.2 the syntax/semantics of the Owner/Change
>>>> | controller is unspecified. But IANA is charged with
>>>> allowing/rejecting change
>>>> | requests only from the "same" owner. How is IANA expected to verify
>>>> | this?
>>>>
>>>> If it is an experimental algorithm, I see no need for strong
>>>> authentication
>>>> of external contributors.
>>>>
>>>> For the algorithms on the standards track, the IESG is defined as owner
>>>> (may authenticate itself to IANA with a signature).
>>>>
>>>> | What if a change is required but the original owner is no longer
>>>> | available?
>>>> | E.g., the owner might be specified by email address. Later the mail
>>>> | server for that email address may no longer exist.
>>>>
>>>> In this case the part "[...] where the owner of the registration [...]
>>>> has moved out of contact [...]" can be applied.
>>>
>>> I won't belabor this point because it will clearly be an infrequent event.
>>>
>>>   Â Â Â Â Thanks,
>>>   Â Â Â Â Paul
>>>
>>> _______________________________________________
>>> Gen-art mailing list
>>> Gen-art@ietf.org
>>> https://www.ietf.org/mailman/listinfo/gen-art
>>>
>>
>>
> 


From nobody Tue Sep 19 07:03:06 2017
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 639C1134334; Tue, 19 Sep 2017 07:03:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 p8BR_dGtNCWi; Tue, 19 Sep 2017 07:03:04 -0700 (PDT)
Received: from alum-mailsec-scanner-1.mit.edu (alum-mailsec-scanner-1.mit.edu [18.7.68.12]) by ietfa.amsl.com (Postfix) with ESMTP id 2CB3C134330;  Tue, 19 Sep 2017 07:03:04 -0700 (PDT)
X-AuditID: 1207440c-7e5ff7000000143e-a6-59c1239786fa
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by alum-mailsec-scanner-1.mit.edu (Symantec Messaging Gateway) with SMTP id FC.E4.05182.79321C95; Tue, 19 Sep 2017 10:03:03 -0400 (EDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id v8JE32KX023994 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 19 Sep 2017 10:03:03 -0400
To: Alexey Melnikov <aamelnikov@fastmail.fm>, draft-baeuerle-netnews-cancel-lock.all@ietf.org, Pete Resnick <presnick@qti.qualcomm.com>
Cc: General Area Review Team <gen-art@ietf.org>
References: <9be2e7af-b99d-4f86-6552-bfada936600d@alum.mit.edu> <20170707174750.487009ed@WStation4> <7452e826-62e9-0d6e-32b5-dcdefcb4c2ea@alum.mit.edu> <20170711203934.458e3b62@WStation4> <37001dcd-6551-78b4-18e7-75fbebaff761@alum.mit.edu> <0147f247-2763-8017-f123-5cdd6ceb06b3@alum.mit.edu> <1505814165.1516258.1110891352.7E7D795F@webmail.messagingengine.com> <1505823221.2181948.1111036680.2C045859@webmail.messagingengine.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <94f86248-b094-0e65-e4e8-0097ba050a27@alum.mit.edu>
Date: Tue, 19 Sep 2017 10:03:02 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <1505823221.2181948.1111036680.2C045859@webmail.messagingengine.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprFKsWRmVeSWpSXmKPExsUixO6iqDtd+WCkwY0Pahb73x9ismhf8YXJ 4uqrzywWV662MDuweOw8dYDNY8mSn0wei6Y+YwxgjuKySUnNySxLLdK3S+DKWLhqJWvBNvaK 75NWMzUwzmfuYuTkkBAwkWiePZ+1i5GLQ0hgB5PEk45z7BDOQyaJCTfagDLsHMIC7hJLykHC IgIzGSUWTjrODtLMLKAv8ffJYiaI+t3MEpO+rQNLsAloScw59J8FxOYVsJf4+7ELLM4ioCqx +f48JhBbVCBN4t/us4wQNYISJ2c+AavnFAiUOPzzCtQCM4l5mx8yQ9jiEreezGeCsOUltr+d wzyBUWAWkvZZSFpmIWmZhaRlASPLKka5xJzSXN3cxMyc4tRk3eLkxLy81CJdQ73czBK91JTS TYyQAOfZwfhtncwhRgEORiUeXoFr+yOFWBPLiitzDzFKcjApifIqKxyMFOJLyk+pzEgszogv Ks1JLT7EKMHBrCTCqyULlONNSaysSi3Kh0lJc7AoifOqLlH3ExJITyxJzU5NLUgtgsnKcHAo SfC2KgE1ChalpqdWpGXmlCCkmTg4QYbzAA2foQgyvLggMbc4Mx0if4rRmOPGw+t/mDh6em78 YRJiycvPS5US5zUFGScAUppRmgc3DZakXjGKAz0nzOsPUsUDTHBw814BrWICWpW94QDIqpJE hJRUAyOvbP0ZQWcH85v79JItt30LWScaqvV74+5++9QjvAo8Jq4xNSsDl+5g5kycz/NuYmED Vwqj9GzG0KcnTC7bOaxcw8PQkPM5JLz2T0pX6v2giUtuqhpcjP+WJ9Cd91aGy0kv0bDy7aJu /x7elNn11hFKsj0TlWwY+09H6Vrfbj64a6Ff7w5dJZbijERDLeai4kQAOTNeDC0DAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/-9LVUFvjYmNKFpMDnU259huu8CI>
Subject: Re: [Gen-art] draft-baeuerle-netnews-cancel-lock-06 and RFCs 5536 & 5322
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Sep 2017 14:03:05 -0000

On 9/19/17 8:13 AM, Alexey Melnikov wrote:

> We can also drop "*" in front of "(approved", as this field is already
> allowed multiple times in an RFC 5322 message.
> 
>>                            archive /
>>                            control /
>>                            distribution /
>>                            expires /
>>                            followup-to /
>>                            injection-date /
>>                            injection-info /
>>                            lines /
>>                            newsgroups /
>>                            organization /
>>                            path /
>>                            summary /
>>                            supersedes /
>>                            user-agent /
>>                            xref )

Oops. I replied to your earlier mail before reading this one thoroughly. 
We arrived at the same conclusion.

	Thanks,
	Paul


From nobody Tue Sep 19 07:24:00 2017
Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA5191331D9; Tue, 19 Sep 2017 07:23:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level: 
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.fm header.b=QUbp2Qzg; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=pZBUPM9y
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 pMxRw4EJzEIW; Tue, 19 Sep 2017 07:23:55 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B25713219B; Tue, 19 Sep 2017 07:23:55 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id B528820DFF; Tue, 19 Sep 2017 10:23:54 -0400 (EDT)
Received: from web5 ([10.202.2.215]) by compute7.internal (MEProxy); Tue, 19 Sep 2017 10:23:54 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=Nd4NDNpjBHdMwUj6sA0RcdLfo/1Jv yJRFC2HDJe8o54=; b=QUbp2QzgHFqEdgMrAe6CWurVGmk5RbT8axCM94LPOUA6Z YabIhE9Y0vidNeNqQr3TDPYKzXIaAoUWye0D/SsMpArmiI/DeV/dUe0QXmpOIz/W KsuRRsR/z4YPHylwM2bSvWtnfWpv/jex7VKR1853aYI8NZIhWO+lAiXnD5ROyxNm DvrnL/qGCb/sbtkUHJDpONPL0CkUqg1XKY5HOGxonOIsZckjGqnp8D0R46JvOHzJ rAvnduRtGSiedKtnEqZ1V6WH3zjANCu+n0sa50DpDFDsRy7w5KR7byZ7HRWSjkKJ mFnx7kKDLyP7+OfPjqe5SewsI/itdWEppJN7AMQiQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=Nd4NDN pjBHdMwUj6sA0RcdLfo/1JvyJRFC2HDJe8o54=; b=pZBUPM9y3mttBnSLMy4YLk vIsxve46eZ+7/JTkquITjxiXV3mvanfUiw8G4zbCFeef9mSJl1lReVGc+sX0v8nt owhmEIZFobzASPltb/LT3+7Ct8wweTrvYAbj7P52j7IIbz+jELLdhEbhNzYApEbV +ZN7xQKugQVgpR4QZsCrNrfSAEfAj6zxh+iRoyVIHnOmOpi7gyjcbirVDfnHctol OG1Jp3ltkT8d1/k3uwGG+KlG/lCC8rG8s/SrX8xDB3ShgAz0unpdHydgT+I/GSkK bkzunZxlNwz5RB2n+80KjvR6fMjWRxLMhOPfjq7uHLoy4vvitdR1NF5izdgjxMGQ ==
X-ME-Sender: <xms:eijBWd-wC5j-hWPM9kRrCGI_Nxhm3JTHnLQ32UYE1IPYqxdPaqFacg>
Received: by mailuser.nyi.internal (Postfix, from userid 99) id 8CDCD9E2E0; Tue, 19 Sep 2017 10:23:54 -0400 (EDT)
Message-Id: <1505831034.2210395.1111181888.051F2D85@webmail.messagingengine.com>
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, draft-baeuerle-netnews-cancel-lock.all@ietf.org, Pete Resnick <presnick@qti.qualcomm.com>
Cc: General Area Review Team <gen-art@ietf.org>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-64b08692
Date: Tue, 19 Sep 2017 15:23:54 +0100
References: <9be2e7af-b99d-4f86-6552-bfada936600d@alum.mit.edu> <20170707174750.487009ed@WStation4> <7452e826-62e9-0d6e-32b5-dcdefcb4c2ea@alum.mit.edu> <20170711203934.458e3b62@WStation4> <37001dcd-6551-78b4-18e7-75fbebaff761@alum.mit.edu> <0147f247-2763-8017-f123-5cdd6ceb06b3@alum.mit.edu> <1505814165.1516258.1110891352.7E7D795F@webmail.messagingengine.com> <38d90b33-4edf-8bba-9bfe-9b5f5a0890d3@alum.mit.edu>
In-Reply-To: <38d90b33-4edf-8bba-9bfe-9b5f5a0890d3@alum.mit.edu>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/FMXq0ZVaiBnUQxZIvRtDe2XDooY>
Subject: Re: [Gen-art] draft-baeuerle-netnews-cancel-lock-06 and RFCs 5536 & 5322
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Sep 2017 14:23:58 -0000

Hi Paul,

On Tue, Sep 19, 2017, at 03:00 PM, Paul Kyzivat wrote:
> Hi Alexey,
>=20
> On 9/19/17 5:42 AM, Alexey Melnikov wrote:
> > Hi Paul,
> >=20
> > On Mon, Sep 18, 2017, at 10:14 PM, Paul Kyzivat wrote:
> >> I'm on tap to do the genart telechat review on
> >> draft-baeuerle-netnews-cancel-lock-06. I see that nothing has been done
> >> about the ABNF that was my primary concern in my prior wglc review of
> >> -05:
> >>
> >> https://mailarchive.ietf.org/arch/msg/gen-art/wXKa5tadbo_xQbbUUCk9RZyB=
0w8
> >>
> >> I'm told by the authors that Alexey asked that it be submitted this wa=
y,
> >=20
> > I asked the editor to submit a new version addressing all other
> > concerns. I wanted to see how the rest of the draft looks.
> >=20=20=20
> >> but the ABNF *is* wrong, and I can't see how a new draft can be allowed
> >> to be published with knowingly wrong ABNF. OTOH, the problem didn't
> >> originate with this draft. Rather the problem originated with RFC5536,
> >> and this draft has simply built on that mistake.
> >=20
> > I was looking at your comment and it was very hard to figure out how big
> > of a deal it was. You are right that ABNF by itself will cause the
> > ordering issue that you reported. However, section 3.6 of RFC 5322 says
> > (ignoring for the moment trace header fields, that have some ordering):
> >=20
> >     It is important to note that the header fields are not guaranteed to
> >     be in a particular order.  They may appear in any order, and they
> >     have been known to be reordered occasionally when transported over
> >     the Internet.  However, for the purposes of this specification,
> >     header fields SHOULD NOT be reordered when a message is transported
> >     or transformed.  More importantly, the trace header fields and rese=
nt
> >     header fields MUST NOT be reordered, and SHOULD be kept in blocks
> >     prepended to the message.  See sections 3.6.6 and 3.6.7 for more
> >     information.
> >=20
> > So I think this already clear that header fields other than trace or
> > resent can appear in any order. This is effectively provides an extra
> > level of flexibility not covered by the ABNF from RFC 5322. As far as I
> > remember, none of the new header fields defined for Netnews articles are
> > trace or resent header fields.
>=20
> I guess this can be read as providing some wiggle room, though in the=20
> context of the existing 5322 text this statement seems *consistent* with=
=20
> the ABNF, and so might not be read as providing extra latitude.
>=20
> >> Unfortunately the root
> >> of the problem is with RFC5322, since its ABNF is structured in a way
> >> that makes it really hard to define extensions such as those in RFC5536
> >> and this draft. So the cleanest solution I can see is to revise both
> >> 5322 and 5536, and then this draft can build on those changes. That is=
 a
> >> rather involved fix but I don't see any other reasonable way.
> >=20
> > I think I agree with you that RFC 5322 could have introduced a few extra
> > ABNF productions to make extensibility easier.
> >=20
> > However in short term, I think we should go with the easiest fix. Pete
> > suggested:
> >=20
> > Section 3 of RFC 5536:
> >=20
> > Original Text:
> >=20
> >      fields          =3D/ *( approved /
> >                            archive /
> >                            control /
> >                            distribution /
> >                            expires /
> >                            followup-to /
> >                            injection-date /
> >                            injection-info /
> >                            lines /
> >                            newsgroups /
> >                            organization /
> >                            path /
> >                            summary /
> >                            supersedes /
> >                            user-agent /
> >                            xref )
> >=20
> > Corrected Text:
> >=20
> >      optional-field  =3D/ *( approved /
> >                            archive /
> >                            control /
> >                            distribution /
> >                            expires /
> >                            followup-to /
> >                            injection-date /
> >                            injection-info /
> >                            lines /
> >                            newsgroups /
> >                            organization /
> >                            path /
> >                            summary /
> >                            supersedes /
> >                            user-agent /
> >                            xref )
>=20
> I see one issue with the above. <optional-field> appears *twice* in the=20
> definition of <fields> in 5322. I don't understand what the intent was=20
> there - whether it was a mistake or was trying to express something that=
=20
> I am missing.

I believe it was entirely intentional. The first instance allows to add
new trace header fields (which should be kept together in groups), the
second allows adding other types of header fields.

> This really needs some further discussion. (E.g., should=20
> the valid values for <optional-field> as used with trace be distinct=20
> from those in its later appearance?

Yes. It would have been better to have 2 separate productions, like
trace-optional-field and other-optional-field, but what Pete did seems
to be Ok.

> This needs to be thrashed out with=20
> mail experts before this fix is finalized. I don't know what forum is=20
> appropriate for that.

I am not sure. Pete?

> Ignoring that, I agree this change to 5536 would achieve the goal=20
> without requiring a change in 5322, which is progress. However I think a=
=20
> tweak to the above would be be a bit cleaner:
>=20
>      optional-field  =3D/    approved /
>                            archive /
>                            control /
>                            distribution /
>                            expires /
>                            followup-to /
>                            injection-date /
>                            injection-info /
>                            lines /
>                            newsgroups /
>                            organization /
>                            path /
>                            summary /
>                            supersedes /
>                            user-agent /
>                            xref
>=20
> This is definitely a better fix than I was suggesting. (Thank you Pete!)

Good.

> > The name optional-field is a bit unfortunate, but it was always intended
> > for extensibility. So I think doing this change and adding a note saying
> > that some of Netnews header fields are mandatory (despite
> > "optional-field" production name) would be the best way forward.
>=20
> Even as it is currently written the *intent* of the current ABNF in 5536=
=20
> is that all of the netnews header fields be optional. And syntactically=20
> it allows them to be repeated multiple times but specifically forbids=20
> that in text. Section 3.1 uses text to specify that certain of those=20
> fields are actually mandatory. (Writing ABNF that allows fields to be in=
=20
> any order while making some at-most-once and some entirely optional is=20
> not practical.) So I don't think any new text is needed for this.

I doesn't hurt to point out, that some header fields are required to be
in Netnews articles. Maybe a pointer to the section where extra
restrictions are specified.

> >> This prompted me to submit an erratum (#5116) on RFC5536 regarding this
> >> issue. But errata aren't often acted on quickly when they require
> >> revising RFCs.
> >=20
> > Thank you for the erratum. Unless there is a better proposal, I will
> > edit resolution based on Pete's feedback and I will approve it.
> >=20
> >> The question is: in the meantime, what to do about this draft? By
> >> default I guess I will simply restate the issue in my genart telechat
> >> review and leave it for the IESG discuss it.
> >=20
> > As per my comments above, I think we should acknowledge that there is a
> > subtle issue with ABNF in RFC 5536. I think the best way forward is to
> > approve some fix to your erratum and let
> > draft-baeuerle-netnews-cancel-lock be reviewed by IESG. At this moment
> > it is not clear to me that work on RFC 5536 will happen any time soon,
> > so I don't think we should hold this draft hostage.
>=20
> I don't see any reason to hold it hostage if there is a path forward=20
> that gets everything fixed. The work-around above can be used=20
> independently in 5536 and draft-baeuerle-netnews-cancel-lock, so they=20
> can proceed independently.
>=20
> I will update my erratum to include the fix above, and write my genart=20
> telechat review to recommend the same fix.

If you can't do that, I can edit the erratum.

Thank you for raising the issue and for the followup discussion.

Best Regards,
Alexey

> 	Thanks,
> 	Paul
>=20
> > Best Regards,
> > Alexey
> >=20
> >> Anybody have a better idea?
> >>
> >> 	Thanks,
> >> 	Paul
> >>
> >> On 7/14/17 12:58 PM, Paul Kyzivat wrote:
> >>> Michael,
> >>>
> >>> Please see further comments inline.
> >>>
> >>> (Sorry - the indenting is getting deep, but I think we are pretty much
> >>> done.)
> >>>
> >>> On 7/11/17 2:39 PM, Michael B=C3=A4uerle wrote:
> >>>> Paul Kyzivat wrote:
> >>>>> On 7/7/17 11:47 AM, Michael B=C3=A4uerle wrote:
> >>>>>> Paul Kyzivat wrote:
> >>>>>>>
> >>>>>>> [...]
> >>>>>>> General Comments:
> >>>>>>>
> >>>>>>> I have not attempted to validate the security properties of this
> >>>>>>> document - leaving that to a security review.
> >>>>>>>
> >>>>>>> I have also not attempted to verify the operational suitability of
> >>>>>>> this
> >>>>>>> mechanism because I don't have the experience needed to do so.
> >>>>>>>
> >>>>>>> Issues:
> >>>>>>>
> >>>>>>> Major: 1
> >>>>>>> Minor: 3
> >>>>>>> Nits:=C2=A0 0
> >>>>>>>
> >>>>>>> (1) MAJOR:
> >>>>>>>
> >>>>>>> [Problem with ABNF syntax of header fields]
> >>>>>>
> >>>>>> Hi Paul,
> >>>>>>
> >>>>>> Julien =C3=89lie has proposed a new syntax definition.
> >>>>>
> >>>>> I was copied on his mail proposing a change to RFC5536, and that is
> >>>>> tentative. *This* document would of course require a similar change=
. Or
> >>>>> else it could extend that change, via something like
> >>>>>
> >>>>>  =C2=A0=C2=A0=C2=A0=C2=A0news-fields =3D/ cancel-lock / cancel-key
> >>>>>
> >>>>> But that can only be done if there is actually a draft that revises=
 5536
> >>>>> that can then be referenced. Bottom line is that it seems there nee=
ds to
> >>>>> be some coordination of that fix with this draft.
> >>>>
> >>>> It's clear that the Cancel-Lock draft needs to be changed. My comment
> >>>> was about the potential erratum for RFC 5536 and the question:
> >>>> Is it (in general) possible to reference a modified ABNF definition =
in
> >>>> an erratum?
> >>>
> >>> I don't know of any way to do so. Perhaps somebody else can provide a
> >>> more definitive answer. You might try asking on rfc-interest.
> >>>
> >>>> If this is possible, then the current:
> >>>>
> >>>>  =C2=A0=C2=A0=C2=A0 fields =3D/ *( cancel-lock / cancel-key )
> >>>>
> >>>> can be changed to:
> >>>>
> >>>>  =C2=A0=C2=A0=C2=A0 news-fields =3D/ cancel-lock / cancel-key
> >>>>
> >>>> and should then reference the new ABNF from the erratum.
> >>>> If not, what about a less formal definition like this:
> >>>>
> >>>>  =C2=A0=C2=A0=C2=A0 The Cancel-Lock and Cancel-Key header fields MUS=
T be treated as
> >>>>  =C2=A0=C2=A0=C2=A0 though it were news header fields as defined in =
Section 3 of
> >>>>  =C2=A0=C2=A0=C2=A0 [RFC5536].
> >>>
> >>> I'm not sure about that. It might fly, or not. Again, I think you need
> >>> to ask somebody more authoritative.
> >>>
> >>>> Rewriting RFC 5322 and RFC 5536 should be avoided if possible.
> >>>
> >>> I understand why you might not want to take on responsibility for tha=
t.
> >>> But it is the right thing to do. Question is whether it needs to be d=
one
> >>> now.
> >>>
> >>>>>>> (2) Minor:
> >>>>>>>
> >>>>>>> In Section 3.5, step 1 says to hash the key using the algorithm
> >>>>>>> from its
> >>>>>>> scheme. But IIUC the scheme describes the algorithm that has alre=
ady
> >>>>>>> been used when constructing the Cancel-Key header.
> >>>>>>
> >>>>>> No. There are two different operations that use a hash function.
> >>>>>>
> >>>>>> The recommended algorithm described in Section 4 calculates:
> >>>>>> |
> >>>>>> | K =3D HMAC(uid+mid, sec)
> >>>>>>
> >>>>>> K is then used for <c-key-string> in the Cancel-Key header field o=
nly
> >>>>>> with Base64 as transfer encoding (no further hash operation is use=
d):
> >>>>>>
> >>>>>>  =C2=A0=C2=A0=C2=A0=C2=A0 c-key-string =3D Base64(K)
> >>>>>>
> >>>>>> HMAC can be based on a different hash function than the one in <sc=
heme>
> >>>>>> (because a serving agent doesn't need to know how K was calculated=
 for
> >>>>>> the check algorithm defined in Section 3.5).
> >>>>>>
> >>>>>> A value of e.g. "sha256" for <scheme> in a Cancel-Key header field
> >>>>>> doesn't mean that SHA256 was used to generate this field, but that=
 the
> >>>>>> corresponding Cancel-Lock header field (in the original article)
> >>>>>> contains
> >>>>>> the value of <c-key-string> hashed with SHA256 (and finally Base64
> >>>>>> encoded).
> >>>>>>
> >>>>>> The hash function defined by <scheme> is used to generate
> >>>>>> <c-lock-string>
> >>>>>> elements for the Cancel-Lock header field:
> >>>>>>
> >>>>>>  =C2=A0=C2=A0=C2=A0=C2=A0 c-lock-string =3D Base64(hash(c-key-stri=
ng))
> >>>>>>  =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 ^^^^
> >>>>>> This hash function is the one specified with <scheme> (in both mat=
ching
> >>>>>> elements <c-lock> and <c-key> in the Cancel-Lock and Cancel-Key he=
ader
> >>>>>> fields of the two articles involved).
> >>>>>>> IIUC the serving
> >>>>>>> agent need not hash the provided key. Rather it only uses the
> >>>>>>> scheme to
> >>>>>>> select the locks to compare the hash against.
> >>>>>>
> >>>>>> <scheme> is used for both purposes.
> >>>>>>
> >>>>>> Step 1 is defined in Section 3.5 as:
> >>>>>> |
> >>>>>> | 1. The <c-key-string> part of the <c-key> element is hashed using
> >>>>>> |=C2=A0=C2=A0=C2=A0 the algorithm defined by its <scheme> part.
> >>>>>>
> >>>>>> This is the operation for <c-lock-string> listed above.
> >>>>>> The hash operation is required here because if the elements from t=
he
> >>>>>> Cancel-Key header field would be directly comparable, everybody co=
uld
> >>>>>> forge them (copy from the public original article).
> >>>>>> The hijack/abuse attack against <c-key-string> elements on their w=
ay
> >>>>>> through the network (as discussed for the review from David Mandel=
berg)
> >>>>>> is not the same. The relevant difference is who can *create* valid
> >>>>>> <c-key-string> elements.
> >>>>>>
> >>>>>> In Step 2 <scheme> is used again to skip <c-lock-string> elements =
that
> >>>>>> were created using different hash functions. The compare operation=
 from
> >>>>>> Step 2 (with first operand from Step 1) is:
> >>>>>>
> >>>>>>  =C2=A0=C2=A0=C2=A0=C2=A0 Base64(hash(c-key-string)) =3D=3D c-lock=
-string
> >>>>>>
> >>>>>> The Base64 encode part is not explicitly noted in Step 1.
> >>>>>> Base64 decoding the second operand instead would work too:
> >>>>>>
> >>>>>>  =C2=A0=C2=A0=C2=A0=C2=A0 hash(c-key-string) =3D=3D Base64_decode(=
c-lock-string)
> >>>>>>
> >>>>>> To be unambiguous and consistent with the definition of <c-lock-st=
ring>
> >>>>>> from Section 2.1, the words for Step 1 in Section 3.5 maybe should
> >>>>>> explicitly cover the Base64 encode operation. Suggestion:
> >>>>>>
> >>>>>>  =C2=A0=C2=A0=C2=A0=C2=A0 1. The <c-key-string> part of the <c-key=
> element is hashed using
> >>>>>>  =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 the algorithm defined =
by its <scheme> part and then Base64
> >>>>>>  =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 encoded.
> >>>>>
> >>>>> Hmm. That wasn't so clear to me, though on rereading I can understa=
nd it
> >>>>> that way.
> >>>>>
> >>>>> But in that case, what is the point of passing the scheme around at=
 all?
> >>>>
> >>>> The <scheme> part of <c-key> elements serve the following purposes:
> >>>> - Backward compatibility
> >>>>  =C2=A0=C2=A0 Existing implementations use it this way since many ye=
ars
> >>>> - Define the hash algorithm to apply on <c-key-string> elements
> >>>> - Select corresponding <c-lock-string> elements to compare against
> >>>>
> >>>>> IIUC doing so doesn't add any additional security or privacy. You c=
ould
> >>>>> simply pass the hashed value in cancel-key. Then the verifying agent
> >>>>> wouldn't do any hashing.
> >>>>
> >>>> In this case the creator of the Cancel-Key header field would not pr=
ove
> >>>> that he really knows K.
> >>>>
> >>>>> This would mean that the cancel-key would be
> >>>>> checked against locks that used a different hash, but that shouldn't
> >>>>> hurt anything.
> >>>>
> >>>> Yes, it is unlikely that comparing against <c-lock-string> elements,
> >>>> that used a different hash algorithm, will hurt.
> >>>>
> >>>> But changing the general syntax of the header fields would break
> >>>> backward compatibility to existing implementations. This should be
> >>>> avoided with highest priority.
> >>>
> >>> I studied the draft further. I finally get that it is simpler than I =
was
> >>> expecting it to be. So really it is just that the lock contains
> >>> hash(password) while the key contains the password. (The key is just =
an
> >>> algorithmically generated password.) I couldn't believe you would rea=
lly
> >>> be passing the password in the clear, since that would expose it to
> >>> on-path attack. But I guess your assumption is that this is really a
> >>> one-time password, and that if it is correct then it will immediately=
 be
> >>> invalidated, and if it is wrong then it doesn't matter.
> >>>
> >>> So I'll withdraw my concerns on this section, except that maybe it co=
uld
> >>> be clearer. Specifically, section 3 could be more explicit about what
> >>> each distinct actor (poster, posting agent, moderator or injecting
> >>> agent) does.
> >>>
> >>>>> [...]
> >>>>> I didn't see a response from you on (4).
> >>>>
> >>>> Sorry for the delay, I was busy.
> >>>>
> >>>> | (4) Minor:
> >>>> |
> >>>> | In Section 8.1/8.2 the syntax/semantics of the Owner/Change
> >>>> | controller is unspecified. But IANA is charged with
> >>>> allowing/rejecting change
> >>>> | requests only from the "same" owner. How is IANA expected to verify
> >>>> | this?
> >>>>
> >>>> If it is an experimental algorithm, I see no need for strong
> >>>> authentication
> >>>> of external contributors.
> >>>>
> >>>> For the algorithms on the standards track, the IESG is defined as ow=
ner
> >>>> (may authenticate itself to IANA with a signature).
> >>>>
> >>>> | What if a change is required but the original owner is no longer
> >>>> | available?
> >>>> | E.g., the owner might be specified by email address. Later the mail
> >>>> | server for that email address may no longer exist.
> >>>>
> >>>> In this case the part "[...] where the owner of the registration [..=
.]
> >>>> has moved out of contact [...]" can be applied.
> >>>
> >>> I won't belabor this point because it will clearly be an infrequent e=
vent.
> >>>
> >>>   =C2=A0=C2=A0=C2=A0=C2=A0Thanks,
> >>>   =C2=A0=C2=A0=C2=A0=C2=A0Paul
> >>>
> >>> _______________________________________________
> >>> Gen-art mailing list
> >>> Gen-art@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/gen-art
> >>>
> >>
> >>
> >=20
>=20


From nobody Tue Sep 19 09:42:48 2017
Return-Path: <dromasca@gmail.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 77AC5134286; Tue, 19 Sep 2017 09:42:46 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Dan Romascanu <dromasca@gmail.com>
To: <gen-art@ietf.org>
Cc: bier@ietf.org, ietf@ietf.org, draft-ietf-bier-architecture.all@ietf.org, dromasca@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 6.62.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150583936645.11787.3653434949933737592@ietfa.amsl.com>
Date: Tue, 19 Sep 2017 09:42:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Vj7K6Ym05WsC29ij5kEvz2N1WzE>
Subject: [Gen-art] Genart last call review of draft-ietf-bier-architecture-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Sep 2017 16:42:46 -0000

Reviewer: Dan Romascanu
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-bier-architecture-08
Reviewer: Dan Romascanu
Review Date: 2017-09-19
IETF LC End Date: 2017-09-20
IESG Telechat date: 2017-09-28

Summary:

This document is Ready. I have reviewed the previous version (07) and the
resulting discussions with the authors and the edits for the current version
(08) addressed most of the issues raised in the previous review. One single
issue remains open, it is minor, and concerns more the charter scope. However,
as it is related to the Experimental status of the document, I am mentioning it
again. I do not believe it was clarified in the revision or the discussions.

Major issues:

Minor issues:

1. As the document is targeting 'Experimental' it would be useful to mention
what is the scope of the experiment. The charter actually says:

' The scope of the experiment will be
documented in the output of the Working Group.'

Would not the Architecture document be the right place for this? If not, is
there another document that deals or is planned to define the scope of the
experiment?

Nits/editorial comments:



From nobody Tue Sep 19 09:46:50 2017
Return-Path: <akatlas@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6805D12895E; Tue, 19 Sep 2017 09:46:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 RWloRMq8ZcgN; Tue, 19 Sep 2017 09:46:34 -0700 (PDT)
Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 307E41331C1; Tue, 19 Sep 2017 09:46:31 -0700 (PDT)
Received: by mail-wr0-x232.google.com with SMTP id l39so148570wrl.12; Tue, 19 Sep 2017 09:46:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=pmk3swYPWjsudG1z+OLB2vlgtAinCrYg6pD62qod39E=; b=FZkYArILZ7DskZTFEx3uA3otadM+R2pNEe8ZLjgYPhad2HoZW/J/qAAdeRM1f11JpD zo2gHeSvlICFAEwfcPQJlS8URs0iAdE+oWXx4bNsNBeBn0RCoAUOv8U9cBVI0M+Ago6J jydU4I5X6RmomZpNBd1hq9VgCJAwMVq0Q6HCekegDWywrIAM32KFPs+poiHDGo7K6XNj ZVycafU8DEvQgDM6yyyBV7ZXFchSJiJTMP4N5L+34fmwBPf6F9MYwD0BcnySMeUwPxem 3m8COc3yICFxSMN7Z9NZZ2AvA8tPVwY9eE3bBNt7bez3NPAoTNlJS6q650YpgGga3kKk lFdw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=pmk3swYPWjsudG1z+OLB2vlgtAinCrYg6pD62qod39E=; b=CG+Hfk6oHMO/8SKBgd97DrxbFzGScfWiup3qUVpZ/JlVxVPCXGvKWrInnf0ywGXQmm hgQzfnpdvpy3WlhN7S1zGkQbtFQODG6cDtmXhL546GuKN4OxMoq+5Rxa4v9ZYLU7ggr6 2jXHm2rTkVf0O0w7wqMsV/Rn6LFJoL9Td1RuKay2hAlyG05W8gm3EQIWTkBTcwu1aEkT mWOX67bps2it4OQC8dAKmwpGW6JUZazWm2RKoHO4E3yJ6FFQFuTBVDwYMzVgygcbOu6N uQjaXUjUtAdbWGa1aIZUAvED7MQ1NtdJ45PRI8X6VpKI2Y8iNHC1cC+L3CQmzns3qBZh LiCw==
X-Gm-Message-State: AHPjjUjXnAmeSNLrXZprvlR1aWVRdTuBV2H1Hobj8pNTk0ctO2QHmgei 4pW+1eZTQHpS3TMUQbUg1NwjJWHEvXiph1Y7kYU9YA==
X-Google-Smtp-Source: AOwi7QA9/mtIFdIp2pd4/I9iYbyMADIlJr7Dram3cfndPnQP3LhSaq43GTk+KLwc7mAjvlCE4dG/k/tppRWAIhuhG9k=
X-Received: by 10.223.169.51 with SMTP id u48mr2010278wrc.270.1505839589502; Tue, 19 Sep 2017 09:46:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.136.153 with HTTP; Tue, 19 Sep 2017 09:46:28 -0700 (PDT)
In-Reply-To: <150583936645.11787.3653434949933737592@ietfa.amsl.com>
References: <150583936645.11787.3653434949933737592@ietfa.amsl.com>
From: Alia Atlas <akatlas@gmail.com>
Date: Tue, 19 Sep 2017 12:46:28 -0400
Message-ID: <CAG4d1rfG3JiCoxvHGKcPMHwn1vCsCV_VhYb0BoWz-fcjViy3cg@mail.gmail.com>
To: Dan Romascanu <dromasca@gmail.com>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "bier@ietf.org" <bier@ietf.org>,  IETF Discussion Mailing List <ietf@ietf.org>, draft-ietf-bier-architecture.all@ietf.org
Content-Type: multipart/alternative; boundary="f403045cf4dad248e005598d99c1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/KIXTCMSBTCIhImX9L0Mxo_Kxiog>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-bier-architecture-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Sep 2017 16:46:36 -0000

--f403045cf4dad248e005598d99c1
Content-Type: text/plain; charset="UTF-8"

Hi Dan,

On Tue, Sep 19, 2017 at 12:42 PM, Dan Romascanu <dromasca@gmail.com> wrote:

> Reviewer: Dan Romascanu
> Review result: Ready
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-ietf-bier-architecture-08
> Reviewer: Dan Romascanu
> Review Date: 2017-09-19
> IETF LC End Date: 2017-09-20
> IESG Telechat date: 2017-09-28
>
> Summary:
>
> This document is Ready. I have reviewed the previous version (07) and the
> resulting discussions with the authors and the edits for the current
> version
> (08) addressed most of the issues raised in the previous review. One single
> issue remains open, it is minor, and concerns more the charter scope.
> However,
> as it is related to the Experimental status of the document, I am
> mentioning it
> again. I do not believe it was clarified in the revision or the
> discussions.
>
> Major issues:
>
> Minor issues:
>
> 1. As the document is targeting 'Experimental' it would be useful to
> mention
> what is the scope of the experiment. The charter actually says:
>
> ' The scope of the experiment will be
> documented in the output of the Working Group.'
>
> Would not the Architecture document be the right place for this? If not, is
> there another document that deals or is planned to define the scope of the
> experiment?
>

Thanks for the review!  The charter has an item (#9, I believe) for
describing
the results to progress to standards track.

Regards,
Alia

--f403045cf4dad248e005598d99c1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Dan,<div class=3D"gmail_extra"><br><div class=3D"gmail_=
quote">On Tue, Sep 19, 2017 at 12:42 PM, Dan Romascanu <span dir=3D"ltr">&l=
t;<a href=3D"mailto:dromasca@gmail.com" target=3D"_blank">dromasca@gmail.co=
m</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Reviewer: Dan Rom=
ascanu<br>
Review result: Ready<br>
<br>
I am the assigned Gen-ART reviewer for this draft. The General Area<br>
Review Team (Gen-ART) reviews all IETF documents being processed<br>
by the IESG for the IETF Chair.=C2=A0 Please treat these comments just<br>
like any other last call comments.<br>
<br>
For more information, please see the FAQ at<br>
<br>
&lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/GenArtfaq" rel=3D"norefe=
rrer" target=3D"_blank">https://trac.ietf.org/trac/<wbr>gen/wiki/GenArtfaq<=
/a>&gt;.<br>
<br>
Document: draft-ietf-bier-architecture-<wbr>08<br>
Reviewer: Dan Romascanu<br>
Review Date: 2017-09-19<br>
IETF LC End Date: 2017-09-20<br>
IESG Telechat date: 2017-09-28<br>
<br>
Summary:<br>
<br>
This document is Ready. I have reviewed the previous version (07) and the<b=
r>
resulting discussions with the authors and the edits for the current versio=
n<br>
(08) addressed most of the issues raised in the previous review. One single=
<br>
issue remains open, it is minor, and concerns more the charter scope. Howev=
er,<br>
as it is related to the Experimental status of the document, I am mentionin=
g it<br>
again. I do not believe it was clarified in the revision or the discussions=
.<br>
<br>
Major issues:<br>
<br>
Minor issues:<br>
<br>
1. As the document is targeting &#39;Experimental&#39; it would be useful t=
o mention<br>
what is the scope of the experiment. The charter actually says:<br>
<br>
&#39; The scope of the experiment will be<br>
documented in the output of the Working Group.&#39;<br>
<br>
Would not the Architecture document be the right place for this? If not, is=
<br>
there another document that deals or is planned to define the scope of the<=
br>
experiment?<br></blockquote><div><br></div><div>Thanks for the review!=C2=
=A0 The charter has an item (#9, I believe) for describing</div><div>the re=
sults to progress to standards track.</div><div><br></div><div>Regards,</di=
v><div>Alia=C2=A0</div></div></div></div>

--f403045cf4dad248e005598d99c1--


From nobody Tue Sep 19 09:56:50 2017
Return-Path: <dromasca@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63629134296; Tue, 19 Sep 2017 09:56:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Rz7ThZGdqrbK; Tue, 19 Sep 2017 09:56:40 -0700 (PDT)
Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 58D70134295; Tue, 19 Sep 2017 09:56:40 -0700 (PDT)
Received: by mail-qk0-x235.google.com with SMTP id b23so256989qkg.1; Tue, 19 Sep 2017 09:56:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=c9mDwRqmvwuAdaD1EkGhf+khyehDFl3+dlvIU1UNRlg=; b=HFTVgRHBA3mwVpJmPde5gMjlMb78MN4YUIZjmmrbPpYYpopQ42c47rcnsJU2GTxq1M SpDNA38et5lSORLV0DPumbhwCGe2d5TdArfTmKaqONksMRMcs42GDakBnmxBIa9Ktndt iNXMPKH0pno3R2RP3/va5Ga3AWBejVdzLIfiKKqbWh1YIBbbPWCxB7O5l0RKIWkiNDO6 WeH1HOwjqXRDFDA97Gw1rFSMXpHMasdCJwfAKz5C+GASulZ2xaD+5nbOoqW/D3E1ddoF UJs9G+KQZMHXh50Q9W2WIu1gtdgR8IK2EXRySLrOE2+lRWUJ0Mb6jvytGvG1J5te1S/s SplQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=c9mDwRqmvwuAdaD1EkGhf+khyehDFl3+dlvIU1UNRlg=; b=QdB2B4tFKELiOxZxJw5dxhNOtWDv5695tci2BBw54f0jcshqNvZuK8GvFOk/B2FVkj 4IgPsh1e6usODrmILjKobltNTAuS51EXxnWZkdVdkXmhP6mJgB8gBPkk9gMZCLo0jIPf Uo9DBhxEMUXJ+a/9R/Q18067M5/FCEmrJyfalwiTCnoKJxzCDHTVsVG8x3AAmh6JVXdv 5kz794lEC9oILs4r6YqKAN9OW6OevuGJnQGWIwvy6bk0xUuOHjK+gt5W+Xgy5IulvuV4 ZHSjQOlp2AwwkNaoGZaKMxkEHh6omsKweS3oD3g2wgJmCiTcG+Fw5PrnvuwACcwUZMZT H9Hw==
X-Gm-Message-State: AHPjjUjARv4hX2914MenzIfZTN0DrTRwpbTNEKLDW297yA9BN5t0/UX4 bFGNXuZC5KdjliCLj5QLPOMkDeAggo+l+zcI46E=
X-Google-Smtp-Source: AOwi7QBnxSAWXuyiqUyNQzWr7ZE4f0Qif4hFz/3GhhNsG1wsktrGFIWkiL/0NHQ26Lo2HFWxykAsc00PGz2N7tVJI8I=
X-Received: by 10.55.19.75 with SMTP id d72mr2737735qkh.266.1505840198508; Tue, 19 Sep 2017 09:56:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.19.206 with HTTP; Tue, 19 Sep 2017 09:56:37 -0700 (PDT)
In-Reply-To: <CAG4d1rfG3JiCoxvHGKcPMHwn1vCsCV_VhYb0BoWz-fcjViy3cg@mail.gmail.com>
References: <150583936645.11787.3653434949933737592@ietfa.amsl.com> <CAG4d1rfG3JiCoxvHGKcPMHwn1vCsCV_VhYb0BoWz-fcjViy3cg@mail.gmail.com>
From: Dan Romascanu <dromasca@gmail.com>
Date: Tue, 19 Sep 2017 19:56:37 +0300
Message-ID: <CAFgnS4V96Lvyx9D-jAsA367D9Dv=0541zZGELZQSkzHcYrPecg@mail.gmail.com>
To: Alia Atlas <akatlas@gmail.com>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "bier@ietf.org" <bier@ietf.org>,  IETF Discussion Mailing List <ietf@ietf.org>, draft-ietf-bier-architecture.all@ietf.org
Content-Type: multipart/alternative; boundary="001a113fffb81ee32f05598dbef5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/vwVNq84n6kemEcDj5FGoGdG3qlQ>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-bier-architecture-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Sep 2017 16:56:42 -0000

--001a113fffb81ee32f05598dbef5
Content-Type: text/plain; charset="UTF-8"

Hi Alia,

Yes, I am aware about this. Yet, there is this little sentence in the WG
charter which does not seem to be answered by now :-)

'The scope of the experiment will be documented in the output of the
Working Group.'

Regards,

Dan


On Tue, Sep 19, 2017 at 7:46 PM, Alia Atlas <akatlas@gmail.com> wrote:

> Hi Dan,
>
> On Tue, Sep 19, 2017 at 12:42 PM, Dan Romascanu <dromasca@gmail.com>
> wrote:
>
>> Reviewer: Dan Romascanu
>> Review result: Ready
>>
>> I am the assigned Gen-ART reviewer for this draft. The General Area
>> Review Team (Gen-ART) reviews all IETF documents being processed
>> by the IESG for the IETF Chair.  Please treat these comments just
>> like any other last call comments.
>>
>> For more information, please see the FAQ at
>>
>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>
>> Document: draft-ietf-bier-architecture-08
>> Reviewer: Dan Romascanu
>> Review Date: 2017-09-19
>> IETF LC End Date: 2017-09-20
>> IESG Telechat date: 2017-09-28
>>
>> Summary:
>>
>> This document is Ready. I have reviewed the previous version (07) and the
>> resulting discussions with the authors and the edits for the current
>> version
>> (08) addressed most of the issues raised in the previous review. One
>> single
>> issue remains open, it is minor, and concerns more the charter scope.
>> However,
>> as it is related to the Experimental status of the document, I am
>> mentioning it
>> again. I do not believe it was clarified in the revision or the
>> discussions.
>>
>> Major issues:
>>
>> Minor issues:
>>
>> 1. As the document is targeting 'Experimental' it would be useful to
>> mention
>> what is the scope of the experiment. The charter actually says:
>>
>> ' The scope of the experiment will be
>> documented in the output of the Working Group.'
>>
>> Would not the Architecture document be the right place for this? If not,
>> is
>> there another document that deals or is planned to define the scope of the
>> experiment?
>>
>
> Thanks for the review!  The charter has an item (#9, I believe) for
> describing
> the results to progress to standards track.
>
> Regards,
> Alia
>

--001a113fffb81ee32f05598dbef5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div>Hi Alia, <br><br></div>Yes, I am aware abou=
t this. Yet, there is this little sentence in the WG charter which does not=
 seem to be answered by now :-) <br><br>&#39;The scope of the experiment wi=
ll be documented in the output of the Working Group.&#39;</div><div><br></d=
iv>Regards,<br><br></div>Dan<br><br></div><div class=3D"gmail_extra"><br><d=
iv class=3D"gmail_quote">On Tue, Sep 19, 2017 at 7:46 PM, Alia Atlas <span =
dir=3D"ltr">&lt;<a href=3D"mailto:akatlas@gmail.com" target=3D"_blank">akat=
las@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div =
dir=3D"ltr">Hi Dan,<div class=3D"gmail_extra"><br><div class=3D"gmail_quote=
"><div><div class=3D"h5">On Tue, Sep 19, 2017 at 12:42 PM, Dan Romascanu <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:dromasca@gmail.com" target=3D"_blank"=
>dromasca@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>Reviewer: Dan Romascanu<br>
Review result: Ready<br>
<br>
I am the assigned Gen-ART reviewer for this draft. The General Area<br>
Review Team (Gen-ART) reviews all IETF documents being processed<br>
by the IESG for the IETF Chair.=C2=A0 Please treat these comments just<br>
like any other last call comments.<br>
<br>
For more information, please see the FAQ at<br>
<br>
&lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/GenArtfaq" rel=3D"norefe=
rrer" target=3D"_blank">https://trac.ietf.org/trac/ge<wbr>n/wiki/GenArtfaq<=
/a>&gt;.<br>
<br>
Document: draft-ietf-bier-architecture-0<wbr>8<br>
Reviewer: Dan Romascanu<br>
Review Date: 2017-09-19<br>
IETF LC End Date: 2017-09-20<br>
IESG Telechat date: 2017-09-28<br>
<br>
Summary:<br>
<br>
This document is Ready. I have reviewed the previous version (07) and the<b=
r>
resulting discussions with the authors and the edits for the current versio=
n<br>
(08) addressed most of the issues raised in the previous review. One single=
<br>
issue remains open, it is minor, and concerns more the charter scope. Howev=
er,<br>
as it is related to the Experimental status of the document, I am mentionin=
g it<br>
again. I do not believe it was clarified in the revision or the discussions=
.<br>
<br>
Major issues:<br>
<br>
Minor issues:<br>
<br>
1. As the document is targeting &#39;Experimental&#39; it would be useful t=
o mention<br>
what is the scope of the experiment. The charter actually says:<br>
<br>
&#39; The scope of the experiment will be<br>
documented in the output of the Working Group.&#39;<br>
<br>
Would not the Architecture document be the right place for this? If not, is=
<br>
there another document that deals or is planned to define the scope of the<=
br>
experiment?<br></blockquote><div><br></div></div></div><div>Thanks for the =
review!=C2=A0 The charter has an item (#9, I believe) for describing</div><=
div>the results to progress to standards track.</div><div><br></div><div>Re=
gards,</div><div>Alia=C2=A0</div></div></div></div>
</blockquote></div><br></div>

--001a113fffb81ee32f05598dbef5--


From nobody Tue Sep 19 10:12:19 2017
Return-Path: <gjshep@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C12FB13304E; Tue, 19 Sep 2017 10:12:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 HVRL7nGX5yPI; Tue, 19 Sep 2017 10:12:14 -0700 (PDT)
Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFE95124207; Tue, 19 Sep 2017 10:12:14 -0700 (PDT)
Received: by mail-it0-x236.google.com with SMTP id c195so324341itb.1; Tue, 19 Sep 2017 10:12:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc; bh=jjEiGf5cvMHqULcCv1h7YQfxchjJjH6p30sJ3zcPsEU=; b=vb6Go+7v79TviP8er3hphOYKyZRzhgzcb+plKTaMGAAcMp0P5C+kww+KBp98DtMqx5 JdGzDB2jkSmA9ctXWEXNVWsLVKDBr1KxUErs3aMF7NJZWzqaLXf5g2WbwmQb2f1kGUiA gB8HhUevYtO0kY50WJHV2Kmrk+U9WbefjkhwDD/ygglMT8PzCKpl82lZrjXWaFbNlopP vR290aE8O/a+XITKpswt786pXBzhBXJnR5J9UyWrt4tZou1924j9W15vNJG3VawV+2Q2 tyOYCH+2dM5lAJTx9IE2N0/l32I3HS6dFHsJzc4uvdJTMT9qetUxQ448PCdxNtKvYJW1 YEgA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=jjEiGf5cvMHqULcCv1h7YQfxchjJjH6p30sJ3zcPsEU=; b=JDYfvNOVrGokhdlaHCZXxEslLdLlo7reB+W6r5FFNdt6dEsymAtlU7fMJ8sc0L4WJh 1fpiGfuIKxjIyLqGElMHQt4yp019CsglubsYKQa5ZtQ/5ocOoctN1kiP3qW33peP5U+W vpBuBPkVPAWSX+uTVVDOXOsqrZFNQwQmIuY4IoGYulMbu8pctjnR85KByWhFnurjd2ZG a5O8foRCbiPWiKLR/jpqubYXecjVp0klKmnxCZghG5jZoG4YYg4fTmjGe/Yt7zcHgCKr xrreY7mnULyJJAbjHjsIntT7Ov5WLGXaEggdLygsFwF0NYCg/SLdqtvtriQEwSeqPfSw iTQQ==
X-Gm-Message-State: AHPjjUjBiY9luiLHmzfmL8cLp4pI0o0dXrKRERb0c3h0a31L06yWEgAH i/nAyU1LKW7N4mAkAp8N6UOVu7d+YpN+ZxY01Vg=
X-Google-Smtp-Source: AOwi7QAyCWRH/HZ9U/fcO1nQIOpgPPbPE7zGkmsiR5jXn3SRpTAlPGgMVLpk6Pnhoc8nOTqwAOQ51VmVareeJeTkfeY=
X-Received: by 10.36.14.87 with SMTP id 84mr2557938ite.71.1505841134062; Tue, 19 Sep 2017 10:12:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.2.137.156 with HTTP; Tue, 19 Sep 2017 10:12:13 -0700 (PDT)
Reply-To: gjshep@gmail.com
In-Reply-To: <CAFgnS4V96Lvyx9D-jAsA367D9Dv=0541zZGELZQSkzHcYrPecg@mail.gmail.com>
References: <150583936645.11787.3653434949933737592@ietfa.amsl.com> <CAG4d1rfG3JiCoxvHGKcPMHwn1vCsCV_VhYb0BoWz-fcjViy3cg@mail.gmail.com> <CAFgnS4V96Lvyx9D-jAsA367D9Dv=0541zZGELZQSkzHcYrPecg@mail.gmail.com>
From: Greg Shepherd <gjshep@gmail.com>
Date: Tue, 19 Sep 2017 10:12:13 -0700
Message-ID: <CABFReBovkfCXAbdhXy9d7_VTosjPqacy+yPwYH7=Du8bgPNrzQ@mail.gmail.com>
To: Dan Romascanu <dromasca@gmail.com>
Cc: Alia Atlas <akatlas@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "bier@ietf.org" <bier@ietf.org>,  IETF Discussion Mailing List <ietf@ietf.org>, draft-ietf-bier-architecture.all@ietf.org
Content-Type: multipart/alternative; boundary="001a11437264e254aa05598df553"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/13HWRHfXaeLhIzvCQAkpFbe4Oe4>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-bier-architecture-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Sep 2017 17:12:17 -0000

--001a11437264e254aa05598df553
Content-Type: text/plain; charset="UTF-8"

The intent is for the WG to author a results draft with or without
justification for moving the work to Standards track.

Greg

On Tue, Sep 19, 2017 at 9:56 AM, Dan Romascanu <dromasca@gmail.com> wrote:

> Hi Alia,
>
> Yes, I am aware about this. Yet, there is this little sentence in the WG
> charter which does not seem to be answered by now :-)
>
> 'The scope of the experiment will be documented in the output of the
> Working Group.'
>
> Regards,
>
> Dan
>
>
> On Tue, Sep 19, 2017 at 7:46 PM, Alia Atlas <akatlas@gmail.com> wrote:
>
>> Hi Dan,
>>
>> On Tue, Sep 19, 2017 at 12:42 PM, Dan Romascanu <dromasca@gmail.com>
>> wrote:
>>
>>> Reviewer: Dan Romascanu
>>> Review result: Ready
>>>
>>> I am the assigned Gen-ART reviewer for this draft. The General Area
>>> Review Team (Gen-ART) reviews all IETF documents being processed
>>> by the IESG for the IETF Chair.  Please treat these comments just
>>> like any other last call comments.
>>>
>>> For more information, please see the FAQ at
>>>
>>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>>
>>> Document: draft-ietf-bier-architecture-08
>>> Reviewer: Dan Romascanu
>>> Review Date: 2017-09-19
>>> IETF LC End Date: 2017-09-20
>>> IESG Telechat date: 2017-09-28
>>>
>>> Summary:
>>>
>>> This document is Ready. I have reviewed the previous version (07) and the
>>> resulting discussions with the authors and the edits for the current
>>> version
>>> (08) addressed most of the issues raised in the previous review. One
>>> single
>>> issue remains open, it is minor, and concerns more the charter scope.
>>> However,
>>> as it is related to the Experimental status of the document, I am
>>> mentioning it
>>> again. I do not believe it was clarified in the revision or the
>>> discussions.
>>>
>>> Major issues:
>>>
>>> Minor issues:
>>>
>>> 1. As the document is targeting 'Experimental' it would be useful to
>>> mention
>>> what is the scope of the experiment. The charter actually says:
>>>
>>> ' The scope of the experiment will be
>>> documented in the output of the Working Group.'
>>>
>>> Would not the Architecture document be the right place for this? If not,
>>> is
>>> there another document that deals or is planned to define the scope of
>>> the
>>> experiment?
>>>
>>
>> Thanks for the review!  The charter has an item (#9, I believe) for
>> describing
>> the results to progress to standards track.
>>
>> Regards,
>> Alia
>>
>
>

--001a11437264e254aa05598df553
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">The intent is for the WG to author a results draft with or=
 without justification for moving the work to Standards track.<div><br></di=
v><div>Greg</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_q=
uote">On Tue, Sep 19, 2017 at 9:56 AM, Dan Romascanu <span dir=3D"ltr">&lt;=
<a href=3D"mailto:dromasca@gmail.com" target=3D"_blank">dromasca@gmail.com<=
/a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><d=
iv><div><div>Hi Alia, <br><br></div>Yes, I am aware about this. Yet, there =
is this little sentence in the WG charter which does not seem to be answere=
d by now :-) <br><br>&#39;The scope of the experiment will be documented in=
 the output of the Working Group.&#39;</div><div><br></div>Regards,<br><br>=
</div>Dan<br><br></div><div class=3D"HOEnZb"><div class=3D"h5"><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Sep 19, 2017 at 7:4=
6 PM, Alia Atlas <span dir=3D"ltr">&lt;<a href=3D"mailto:akatlas@gmail.com"=
 target=3D"_blank">akatlas@gmail.com</a>&gt;</span> wrote:<br><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex"><div dir=3D"ltr">Hi Dan,<div class=3D"gmail_extra"><br><d=
iv class=3D"gmail_quote"><div><div class=3D"m_-3206273730285109299h5">On Tu=
e, Sep 19, 2017 at 12:42 PM, Dan Romascanu <span dir=3D"ltr">&lt;<a href=3D=
"mailto:dromasca@gmail.com" target=3D"_blank">dromasca@gmail.com</a>&gt;</s=
pan> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">Reviewer: Dan Romascanu<br>
Review result: Ready<br>
<br>
I am the assigned Gen-ART reviewer for this draft. The General Area<br>
Review Team (Gen-ART) reviews all IETF documents being processed<br>
by the IESG for the IETF Chair.=C2=A0 Please treat these comments just<br>
like any other last call comments.<br>
<br>
For more information, please see the FAQ at<br>
<br>
&lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/GenArtfaq" rel=3D"norefe=
rrer" target=3D"_blank">https://trac.ietf.org/trac/ge<wbr>n/wiki/GenArtfaq<=
/a>&gt;.<br>
<br>
Document: draft-ietf-bier-architecture-0<wbr>8<br>
Reviewer: Dan Romascanu<br>
Review Date: 2017-09-19<br>
IETF LC End Date: 2017-09-20<br>
IESG Telechat date: 2017-09-28<br>
<br>
Summary:<br>
<br>
This document is Ready. I have reviewed the previous version (07) and the<b=
r>
resulting discussions with the authors and the edits for the current versio=
n<br>
(08) addressed most of the issues raised in the previous review. One single=
<br>
issue remains open, it is minor, and concerns more the charter scope. Howev=
er,<br>
as it is related to the Experimental status of the document, I am mentionin=
g it<br>
again. I do not believe it was clarified in the revision or the discussions=
.<br>
<br>
Major issues:<br>
<br>
Minor issues:<br>
<br>
1. As the document is targeting &#39;Experimental&#39; it would be useful t=
o mention<br>
what is the scope of the experiment. The charter actually says:<br>
<br>
&#39; The scope of the experiment will be<br>
documented in the output of the Working Group.&#39;<br>
<br>
Would not the Architecture document be the right place for this? If not, is=
<br>
there another document that deals or is planned to define the scope of the<=
br>
experiment?<br></blockquote><div><br></div></div></div><div>Thanks for the =
review!=C2=A0 The charter has an item (#9, I believe) for describing</div><=
div>the results to progress to standards track.</div><div><br></div><div>Re=
gards,</div><div>Alia=C2=A0</div></div></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>

--001a11437264e254aa05598df553--


From nobody Tue Sep 19 11:41:41 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29BE7134349; Tue, 19 Sep 2017 11:41:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.999
X-Spam-Level: 
X-Spam-Status: No, score=-6.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.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 J7aR_7BOcg-s; Tue, 19 Sep 2017 11:41:38 -0700 (PDT)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 345BE134350; Tue, 19 Sep 2017 11:41:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1505846498; x=1537382498; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=h+3nHlwjwWaEqLNz/iBwPWJBmX51mjtsih18Ra0DArY=; b=K7ByXZ4ugNXi6QqdcmwBidbd/L0agpmey+IVdpCdSxFOGFpCgQC0Y4GH DFNt6+SRELptCt8uCdmhpfr1fsjeU11RhJEXV4sefPC34LwkGHrLs0Sfb 3jVjQZh9JTQmGYvqAUoMayPQ6WsHEWwwaAUjjQ4viAkuW3lR+gBfFk9Cr A=;
X-IronPort-AV: E=Sophos;i="5.42,418,1500966000";  d="scan'208,217";a="115130684"
Received: from unknown (HELO Ironmsg04-L.qualcomm.com) ([10.53.140.111]) by sabertooth01.qualcomm.com with ESMTP; 19 Sep 2017 11:41:37 -0700
X-IronPort-AV: E=McAfee;i="5900,7806,8659"; a="1425740628"
X-MGA-submission: =?us-ascii?q?MDEZwbQ3YSs6HY7gUoMeVtPpLjjbibwQBxKsF8?= =?us-ascii?q?5yyyuRav4Up+jelfTJtWxczeEmP24nIs0YzpXiewaZsHxPsjHpGVBeF+?= =?us-ascii?q?TBWjuCB/yDyq8KxSQa/hP8d6NPulQqrl5f/aeGUAZsxrOvV8MSMRlKvG?= =?us-ascii?q?DZ?=
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/AES256-SHA; 19 Sep 2017 11:41:37 -0700
Received: from [10.110.24.18] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Tue, 19 Sep 2017 11:41:36 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
CC: Paul Kyzivat <pkyzivat@alum.mit.edu>, <draft-baeuerle-netnews-cancel-lock.all@ietf.org>, General Area Review Team <gen-art@ietf.org>
Date: Tue, 19 Sep 2017 13:41:35 -0500
Message-ID: <D0DEE08D-531E-4CD5-8C65-52B008B7CB02@qti.qualcomm.com>
In-Reply-To: <1505831034.2210395.1111181888.051F2D85@webmail.messagingengine.com>
References: <9be2e7af-b99d-4f86-6552-bfada936600d@alum.mit.edu> <20170707174750.487009ed@WStation4> <7452e826-62e9-0d6e-32b5-dcdefcb4c2ea@alum.mit.edu> <20170711203934.458e3b62@WStation4> <37001dcd-6551-78b4-18e7-75fbebaff761@alum.mit.edu> <0147f247-2763-8017-f123-5cdd6ceb06b3@alum.mit.edu> <1505814165.1516258.1110891352.7E7D795F@webmail.messagingengine.com> <38d90b33-4edf-8bba-9bfe-9b5f5a0890d3@alum.mit.edu> <1505831034.2210395.1111181888.051F2D85@webmail.messagingengine.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_38D57B4E-4690-47F5-A1D0-BECA94C1C233_="
X-Mailer: MailMate (1.9.7r5412)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01B.na.qualcomm.com (10.85.0.82) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/jgBiSPIATc66ZVOQKa7w0OzMgW0>
Subject: Re: [Gen-art] draft-baeuerle-netnews-cancel-lock-06 and RFCs 5536 & 5322
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Sep 2017 18:41:40 -0000

--=_MailMate_38D57B4E-4690-47F5-A1D0-BECA94C1C233_=
Content-Type: text/plain; format=flowed

On 19 Sep 2017, at 9:23, Alexey Melnikov wrote:

>>>      optional-field  =/ *( approved /
>>>                            archive /
>>>                            control /
>>>                            distribution /
>>>                            expires /
>>>                            followup-to /
>>>                            injection-date /
>>>                            injection-info /
>>>                            lines /
>>>                            newsgroups /
>>>                            organization /
>>>                            path /
>>>                            summary /
>>>                            supersedes /
>>>                            user-agent /
>>>                            xref )
>>
>> I see one issue with the above. <optional-field> appears *twice* in 
>> the
>> definition of <fields> in 5322. I don't understand what the intent 
>> was
>> there - whether it was a mistake or was trying to express something 
>> that
>> I am missing.
>
> I believe it was entirely intentional. The first instance allows to 
> add
> new trace header fields (which should be kept together in groups), the
> second allows adding other types of header fields.

Correct, that was the intention. In 5322, optional-field is a catchall 
for any new header field, so you need one for new trace fields and one 
for other fields. Otherwise, there's no way to put a new field between 
two trace fields. This was a fix in 5322 from 2822.

>> This really needs some further discussion. (E.g., should
>> the valid values for <optional-field> as used with trace be distinct
>> from those in its later appearance?
>
> Yes. It would have been better to have 2 separate productions, like
> trace-optional-field and other-optional-field, but what Pete did seems
> to be Ok.

Yes, that might have been nice, but putting extensibility syntax 
throughout the grammar starts to get ugly. (Imagine 
resent-optional-field, originator-optional-field, etc.) I think just one 
is fine.

>> This needs to be thrashed out with
>> mail experts before this fix is finalized. I don't know what forum is
>> appropriate for that.
>
> I am not sure. Pete?

Probably ietf-822, but (a) I personally haven't read the list in a very 
long time, and (b) I don't think there's anything terribly controversial 
about the change.

>> Ignoring that, I agree this change to 5536 would achieve the goal
>> without requiring a change in 5322, which is progress. However I 
>> think a
>> tweak to the above would be be a bit cleaner:
>>
>>      optional-field  =/    approved /
>>                            archive /
>>                            control /
>>                            distribution /
>>                            expires /
>>                            followup-to /
>>                            injection-date /
>>                            injection-info /
>>                            lines /
>>                            newsgroups /
>>                            organization /
>>                            path /
>>                            summary /
>>                            supersedes /
>>                            user-agent /
>>                            xref
>>
>> This is definitely a better fix than I was suggesting. (Thank you 
>> Pete!)
>
> Good.

You're very welcome. I am equally fine with Alexey and Julien's version:

      optional-field  = <see RFC 5322 Section 3.6.8>

      news-fields     =     approved /
                            archive /
                            control /
                            distribution /
                            expires /
                            followup-to /
                            injection-date /
                            injection-info /
                            lines /
                            newsgroups /
                            organization /
                            path /
                            summary /
                            supersedes /
                            user-agent /
                            xref

      optional-field  /=    newsfields


pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478

--=_MailMate_38D57B4E-4690-47F5-A1D0-BECA94C1C233_=
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">On 19 Sep 2017, at 9:23, Alexey Melnikov wrote:</p>

</div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><blockquote style=
=3D"border-left:2px solid #777; color:#999; margin:0 0 5px; padding-left:=
5px; border-left-color:#999"><blockquote style=3D"border-left:2px solid #=
777; color:#BBB; margin:0 0 5px; padding-left:5px; border-left-color:#BBB=
"><p dir=3D"auto">     optional-field  =3D/ *( approved /<br>
                           archive /<br>
                           control /<br>
                           distribution /<br>
                           expires /<br>
                           followup-to /<br>
                           injection-date /<br>
                           injection-info /<br>
                           lines /<br>
                           newsgroups /<br>
                           organization /<br>
                           path /<br>
                           summary /<br>
                           supersedes /<br>
                           user-agent /<br>
                           xref )</p>
</blockquote><p dir=3D"auto">I see one issue with the above. &lt;optional=
-field&gt; appears *twice* in the<br>
definition of &lt;fields&gt; in 5322. I don't understand what the intent =
was<br>
there - whether it was a mistake or was trying to express something that<=
br>
I am missing.</p>
</blockquote><p dir=3D"auto">I believe it was entirely intentional. The f=
irst instance allows to add<br>
new trace header fields (which should be kept together in groups), the<br=
>
second allows adding other types of header fields.</p>
</blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">Correct, that was the intention. In 5322, optional-field =
is a catchall for any new header field, so you need one for new trace fie=
lds and one for other fields. Otherwise, there's no way to put a new fiel=
d between two trace fields. This was a fix in 5322 from 2822.</p>

</div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><blockquote style=
=3D"border-left:2px solid #777; color:#999; margin:0 0 5px; padding-left:=
5px; border-left-color:#999"><p dir=3D"auto">This really needs some furth=
er discussion. (E.g., should<br>
the valid values for &lt;optional-field&gt; as used with trace be distinc=
t<br>
from those in its later appearance?</p>
</blockquote><p dir=3D"auto">Yes. It would have been better to have 2 sep=
arate productions, like<br>
trace-optional-field and other-optional-field, but what Pete did seems<br=
>
to be Ok.</p>
</blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">Yes, that might have been nice, but putting extensibility=
 syntax throughout the grammar starts to get ugly. (Imagine resent-option=
al-field, originator-optional-field, etc.) I think just one is fine.</p>

</div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><blockquote style=
=3D"border-left:2px solid #777; color:#999; margin:0 0 5px; padding-left:=
5px; border-left-color:#999"><p dir=3D"auto">This needs to be thrashed ou=
t with<br>
mail experts before this fix is finalized. I don't know what forum is<br>=

appropriate for that.</p>
</blockquote><p dir=3D"auto">I am not sure. Pete?</p>
</blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">Probably ietf-822, but (a) I personally haven't read the =
list in a very long time, and (b) I don't think there's anything terribly=
 controversial about the change.</p>

</div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><blockquote style=
=3D"border-left:2px solid #777; color:#999; margin:0 0 5px; padding-left:=
5px; border-left-color:#999"><p dir=3D"auto">Ignoring that, I agree this =
change to 5536 would achieve the goal<br>
without requiring a change in 5322, which is progress. However I think a<=
br>
tweak to the above would be be a bit cleaner:<br>
<br>
     optional-field  =3D/    approved /<br>
                           archive /<br>
                           control /<br>
                           distribution /<br>
                           expires /<br>
                           followup-to /<br>
                           injection-date /<br>
                           injection-info /<br>
                           lines /<br>
                           newsgroups /<br>
                           organization /<br>
                           path /<br>
                           summary /<br>
                           supersedes /<br>
                           user-agent /<br>
                           xref<br>
<br>
This is definitely a better fix than I was suggesting. (Thank you Pete!)<=
/p>
</blockquote><p dir=3D"auto">Good.</p>
</blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">You're very welcome. I am equally fine with Alexey and Ju=
lien's version:</p>

<pre style=3D"background-color:#F7F7F7; border-radius:5px 5px 5px 5px; ma=
rgin-left:15px; margin-right:15px; max-width:90vw; overflow-x:auto; paddi=
ng:5px" bgcolor=3D"#F7F7F7"><code style=3D"background-color:#F7F7F7; bord=
er-radius:3px; margin:0; padding:0" bgcolor=3D"#F7F7F7"> optional-field  =
=3D &lt;see RFC 5322 Section 3.6.8&gt;

 news-fields     =3D     approved /
                       archive /
                       control /
                       distribution /
                       expires /
                       followup-to /
                       injection-date /
                       injection-info /
                       lines /
                       newsgroups /
                       organization /
                       path /
                       summary /
                       supersedes /
                       user-agent /
                       xref

 optional-field  /=3D    newsfields
</code></pre>

<p dir=3D"auto">pr<br>
-- <br>
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/" style=3D"co=
lor:#3983C4">http://www.qualcomm.com/~presnick/</a><br>
Qualcomm Technologies, Inc. - +1 (858)651-4478</p>
</div>
</div>
</body>
</html>

--=_MailMate_38D57B4E-4690-47F5-A1D0-BECA94C1C233_=--


From nobody Tue Sep 19 12:19:14 2017
Return-Path: <julien@trigofacile.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F074134379 for <gen-art@ietfa.amsl.com>; Tue, 19 Sep 2017 12:19:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.421
X-Spam-Level: 
X-Spam-Status: No, score=-3.421 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_NEUTRAL=0.779] autolearn=ham autolearn_force=no
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 0kMhpkDlGtwX for <gen-art@ietfa.amsl.com>; Tue, 19 Sep 2017 12:19:10 -0700 (PDT)
Received: from smtp.smtpout.orange.fr (smtp08.smtpout.orange.fr [80.12.242.130]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55BEC13437E for <gen-art@ietf.org>; Tue, 19 Sep 2017 12:19:10 -0700 (PDT)
Received: from mbpdejulienelie.home ([90.3.207.21]) by mwinf5d67 with ME id BXK41w00c0UDvf603XK5R0; Tue, 19 Sep 2017 21:19:08 +0200
X-ME-Helo: mbpdejulienelie.home
X-ME-Auth: anVsaWVuLmVsaWU0ODdAd2FuYWRvby5mcg==
X-ME-Date: Tue, 19 Sep 2017 21:19:08 +0200
X-ME-IP: 90.3.207.21
To: Pete Resnick <presnick@qti.qualcomm.com>
Cc: Alexey Melnikov <aamelnikov@fastmail.fm>, Paul Kyzivat <pkyzivat@alum.mit.edu>, draft-baeuerle-netnews-cancel-lock.all@ietf.org, General Area Review Team <gen-art@ietf.org>
References: <9be2e7af-b99d-4f86-6552-bfada936600d@alum.mit.edu> <20170707174750.487009ed@WStation4> <7452e826-62e9-0d6e-32b5-dcdefcb4c2ea@alum.mit.edu> <20170711203934.458e3b62@WStation4> <37001dcd-6551-78b4-18e7-75fbebaff761@alum.mit.edu> <0147f247-2763-8017-f123-5cdd6ceb06b3@alum.mit.edu> <1505814165.1516258.1110891352.7E7D795F@webmail.messagingengine.com> <38d90b33-4edf-8bba-9bfe-9b5f5a0890d3@alum.mit.edu> <1505831034.2210395.1111181888.051F2D85@webmail.messagingengine.com> <D0DEE08D-531E-4CD5-8C65-52B008B7CB02@qti.qualcomm.com>
From: =?UTF-8?Q?Julien_=c3=89LIE?= <julien@trigofacile.com>
Organization: TrigoFACILE -- http://www.trigofacile.com/
Message-ID: <751abb6b-a5a2-d13b-ca30-d9fd9c7a95b8@trigofacile.com>
Date: Tue, 19 Sep 2017 21:19:04 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <D0DEE08D-531E-4CD5-8C65-52B008B7CB02@qti.qualcomm.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/8ERNMbtBUi3mXGxZxmNcxlzI9O4>
Subject: Re: [Gen-art] draft-baeuerle-netnews-cancel-lock-06 and RFCs 5536 & 5322
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Sep 2017 19:19:13 -0000

Hi all,

 > optional-field  = <see RFC 5322 Section 3.6.8>
 >
 > news-fields     =     approved /
 >                       archive /
 >                       control /
 >                       distribution /
 >                       expires /
 >                       followup-to /
 >                       injection-date /
 >                       injection-info /
 >                       lines /
 >                       newsgroups /
 >                       organization /
 >                       path /
 >                       summary /
 >                       supersedes /
 >                       user-agent /
 >                       xref
 >
 > optional-field  /=    news-fields

This change looks great (with typo fixed for "news-fields" instead of 
"newsfields").

Please note that the first line about <optional-field> updates Section 
1.4 of RFC 5536 (the line defining <fields> is changed to the line 
defining <optional-field>).

The other lines update Section 3 of RFC 5536.  The introduction of 
Section 3 should also refer to Section 3.6.8 of RFC 5322 instead of 
Section 3.6.

-- 
Julien Ã‰LIE

Â«Â Vanitas uanitatum et omnia uanitas.Â Â» (EcclÃ©siaste)


From nobody Tue Sep 19 12:30:29 2017
Return-Path: <julien@trigofacile.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01F7D13437E for <gen-art@ietfa.amsl.com>; Tue, 19 Sep 2017 12:30:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.42
X-Spam-Level: 
X-Spam-Status: No, score=-3.42 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 Do396s2W_yyo for <gen-art@ietfa.amsl.com>; Tue, 19 Sep 2017 12:30:23 -0700 (PDT)
Received: from smtp.smtpout.orange.fr (smtp08.smtpout.orange.fr [80.12.242.130]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BB37134379 for <gen-art@ietf.org>; Tue, 19 Sep 2017 12:30:23 -0700 (PDT)
Received: from mbpdejulienelie.home ([90.3.207.21]) by mwinf5d67 with ME id BXWM1w0030UDvf603XWMc2; Tue, 19 Sep 2017 21:30:21 +0200
X-ME-Helo: mbpdejulienelie.home
X-ME-Auth: anVsaWVuLmVsaWU0ODdAd2FuYWRvby5mcg==
X-ME-Date: Tue, 19 Sep 2017 21:30:21 +0200
X-ME-IP: 90.3.207.21
To: Alexey Melnikov <aamelnikov@fastmail.fm>, Paul Kyzivat <pkyzivat@alum.mit.edu>, draft-baeuerle-netnews-cancel-lock.all@ietf.org, Pete Resnick <presnick@qti.qualcomm.com>
Cc: General Area Review Team <gen-art@ietf.org>
References: <9be2e7af-b99d-4f86-6552-bfada936600d@alum.mit.edu> <20170707174750.487009ed@WStation4> <7452e826-62e9-0d6e-32b5-dcdefcb4c2ea@alum.mit.edu> <20170711203934.458e3b62@WStation4> <37001dcd-6551-78b4-18e7-75fbebaff761@alum.mit.edu> <0147f247-2763-8017-f123-5cdd6ceb06b3@alum.mit.edu> <1505814165.1516258.1110891352.7E7D795F@webmail.messagingengine.com>
From: =?UTF-8?Q?Julien_=c3=89LIE?= <julien@trigofacile.com>
Organization: TrigoFACILE -- http://www.trigofacile.com/
Message-ID: <74196156-9558-b3f4-30d7-208400c08606@trigofacile.com>
Date: Tue, 19 Sep 2017 21:30:21 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <1505814165.1516258.1110891352.7E7D795F@webmail.messagingengine.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/zBK2It3AwlSV5XZhwHlJkpPoCx4>
Subject: Re: [Gen-art] draft-baeuerle-netnews-cancel-lock-06 and RFCs 5536 & 5322
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Sep 2017 19:30:27 -0000

Hi Alexey,

>> The question is: in the meantime, what to do about this draft? By
>> default I guess I will simply restate the issue in my genart telechat
>> review and leave it for the IESG discuss it.
> 
> As per my comments above, I think we should acknowledge that there is a
> subtle issue with ABNF in RFC 5536. I think the best way forward is to
> approve some fix to your erratum and let
> draft-baeuerle-netnews-cancel-lock be reviewed by IESG. At this moment
> it is not clear to me that work on RFC 5536 will happen any time soon,
> so I don't think we should hold this draft hostage.

No work on RFC 5536 is scheduled in a near future.
The next revision will probably be when we deal with Netnews 
internationalization (UTF-8 newsgroup names, UTF-8 distributions...). 
It may be in a separate RFC or in a rewrite of RFC 5536 (in case RFC 
5322 is also rewritten).
Also, the USEFOR WG began a BCP for Netnews but the WG concluded before 
the task finished.  That is the next consequent work to do.
   https://datatracker.ietf.org/doc/draft-ietf-usefor-useage/

-- 
Julien Ã‰LIE

Â«Â De mourir, Ã§a ne me fait rien. Mais Ã§a me fait peine de quitter la
   vie.Â Â» (Marcel Pagnol)


From nobody Tue Sep 19 13:02:17 2017
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6931B13438D for <gen-art@ietfa.amsl.com>; Tue, 19 Sep 2017 13:02:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level: 
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 B7JCNP-HU0lP for <gen-art@ietfa.amsl.com>; Tue, 19 Sep 2017 13:02:15 -0700 (PDT)
Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) (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 34890134299 for <gen-art@ietf.org>; Tue, 19 Sep 2017 13:02:15 -0700 (PDT)
Received: from resomta-ch2-19v.sys.comcast.net ([69.252.207.115]) by resqmta-ch2-08v.sys.comcast.net with ESMTP id uOi0d0WIMkjYruOikdQU7Z; Tue, 19 Sep 2017 20:02:14 +0000
Received: from PaulKyzivatsMBP.localdomain ([24.62.227.142]) by resomta-ch2-19v.sys.comcast.net with SMTP id uOijdIiDctwaXuOijdmoHx; Tue, 19 Sep 2017 20:02:14 +0000
To: Pete Resnick <presnick@qti.qualcomm.com>, Alexey Melnikov <aamelnikov@fastmail.fm>
Cc: draft-baeuerle-netnews-cancel-lock.all@ietf.org, General Area Review Team <gen-art@ietf.org>
References: <9be2e7af-b99d-4f86-6552-bfada936600d@alum.mit.edu> <20170707174750.487009ed@WStation4> <7452e826-62e9-0d6e-32b5-dcdefcb4c2ea@alum.mit.edu> <20170711203934.458e3b62@WStation4> <37001dcd-6551-78b4-18e7-75fbebaff761@alum.mit.edu> <0147f247-2763-8017-f123-5cdd6ceb06b3@alum.mit.edu> <1505814165.1516258.1110891352.7E7D795F@webmail.messagingengine.com> <38d90b33-4edf-8bba-9bfe-9b5f5a0890d3@alum.mit.edu> <1505831034.2210395.1111181888.051F2D85@webmail.messagingengine.com> <D0DEE08D-531E-4CD5-8C65-52B008B7CB02@qti.qualcomm.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <2761ff34-eec8-d326-18c1-7f126155593f@alum.mit.edu>
Date: Tue, 19 Sep 2017 16:02:12 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <D0DEE08D-531E-4CD5-8C65-52B008B7CB02@qti.qualcomm.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfHs9HN2FJ0qHAcG1/GAbpVD/ybcF0/xuYh7wUPKgO5J5DiLoRaYuU/8GVG9zdSBsDqXSsagGhu5pmDPN6H5YhajzUghIDyQrPWEEstF/FZJHgllPD1XY M90bwYn98zwS3M6Jh2TJ2xQCtXkvTLI2cuE53E4+Y9xkgKhF4HWwAeiUkxuamHDBlU1NyYDx4N/fFIpflL5veQs6IfjVIICBlUJav3CUfIg6c8Dq8vvT/pQF 2vzTY91quRofke0mKiXYtcYx6I2oxgruVVD+nw/0QwYcc8YkMbzAw/6YCIVoW8NSvTRjxjOHYiclM8YfVVUndYFK3J1Sg8XZXSeu/tPOADU=
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/eXGpl6Zt8LNmlQopi5nkeUD4udg>
Subject: Re: [Gen-art] draft-baeuerle-netnews-cancel-lock-06 and RFCs 5536 & 5322
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Sep 2017 20:02:16 -0000

On 9/19/17 2:41 PM, Pete Resnick wrote:
> On 19 Sep 2017, at 9:23, Alexey Melnikov wrote:
> 
>             optional-field =/ *( approved /
>             archive /
>             control /
>             distribution /
>             expires /
>             followup-to /
>             injection-date /
>             injection-info /
>             lines /
>             newsgroups /
>             organization /
>             path /
>             summary /
>             supersedes /
>             user-agent /
>             xref )
> 
>         I see one issue with the above. <optional-field> appears *twice*
>         in the
>         definition of <fields> in 5322. I don't understand what the
>         intent was
>         there - whether it was a mistake or was trying to express
>         something that
>         I am missing.
> 
>     I believe it was entirely intentional. The first instance allows to add
>     new trace header fields (which should be kept together in groups), the
>     second allows adding other types of header fields.
> 
> Correct, that was the intention. In 5322, optional-field is a catchall 
> for any new header field, so you need one for new trace fields and one 
> for other fields. Otherwise, there's no way to put a new field between 
> two trace fields. This was a fix in 5322 from 2822.
> 
>         This really needs some further discussion. (E.g., should
>         the valid values for <optional-field> as used with trace be distinct
>         from those in its later appearance?
> 
>     Yes. It would have been better to have 2 separate productions, like
>     trace-optional-field and other-optional-field, but what Pete did seems
>     to be Ok.

This probably wasn't *too* bad as long as <optional-field> was simply 
defined as:

    optional-field  =   field-name ":" unstructured CRLF

Even then, ideally there should have been some words to indicate that 
the <field-name>s used as extensions for trace be disjoint from those 
used as non-trace extension headers.

It gets more ugly when we start to extends <optional-field> 
syntactically via =/. Now, when the syntax is evaluated the new header 
fields we are defining show up as explicitly syntactically valid in both 
places. :-(

> Yes, that might have been nice, but putting extensibility syntax 
> throughout the grammar starts to get ugly. (Imagine 
> resent-optional-field, originator-optional-field, etc.) I think just one 
> is fine.

Since there is an IANA registry, another possibility would be to not 
attempt to revise the syntax from 5322 at all. Instead, simply rely on 
the the extensibility already there via <optional-field> and register 
all the new header fields in the IANA registry. (Use ABNF to define the 
syntax of the individual new headers but not their linkage into the 
message.)

Then use text to specify conditions about where they may appear in a 
message.

	Thanks,
	Paul

>         This needs to be thrashed out with
>         mail experts before this fix is finalized. I don't know what
>         forum is
>         appropriate for that.
> 
>     I am not sure. Pete?
> 
> Probably ietf-822, but (a) I personally haven't read the list in a very 
> long time, and (b) I don't think there's anything terribly controversial 
> about the change.
> 
>         Ignoring that, I agree this change to 5536 would achieve the goal
>         without requiring a change in 5322, which is progress. However I
>         think a
>         tweak to the above would be be a bit cleaner:
> 
>         optional-field =/ approved /
>         archive /
>         control /
>         distribution /
>         expires /
>         followup-to /
>         injection-date /
>         injection-info /
>         lines /
>         newsgroups /
>         organization /
>         path /
>         summary /
>         supersedes /
>         user-agent /
>         xref
> 
>         This is definitely a better fix than I was suggesting. (Thank
>         you Pete!)
> 
>     Good.
> 
> You're very welcome. I am equally fine with Alexey and Julien's version:
> 
> |optional-field = <see RFC 5322 Section 3.6.8> news-fields = approved / 
> archive / control / distribution / expires / followup-to / 
> injection-date / injection-info / lines / newsgroups / organization / 
> path / summary / supersedes / user-agent / xref optional-field /= 
> newsfields |
> 
> pr
> -- 
> Pete Resnick http://www.qualcomm.com/~presnick/ 
> <http://www.qualcomm.com/%7Epresnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
> 


From nobody Tue Sep 19 13:17:58 2017
Return-Path: <julien@trigofacile.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FC0C1343A9 for <gen-art@ietfa.amsl.com>; Tue, 19 Sep 2017 13:17:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.421
X-Spam-Level: 
X-Spam-Status: No, score=-3.421 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_NEUTRAL=0.779] autolearn=unavailable autolearn_force=no
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 1G3EYuA0NyVw for <gen-art@ietfa.amsl.com>; Tue, 19 Sep 2017 13:17:54 -0700 (PDT)
Received: from smtp.smtpout.orange.fr (smtp08.smtpout.orange.fr [80.12.242.130]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B22141343A6 for <gen-art@ietf.org>; Tue, 19 Sep 2017 13:17:52 -0700 (PDT)
Received: from mbpdejulienelie.home ([90.3.207.21]) by mwinf5d67 with ME id BYHq1w0070UDvf603YHqHy; Tue, 19 Sep 2017 22:17:51 +0200
X-ME-Helo: mbpdejulienelie.home
X-ME-Auth: anVsaWVuLmVsaWU0ODdAd2FuYWRvby5mcg==
X-ME-Date: Tue, 19 Sep 2017 22:17:51 +0200
X-ME-IP: 90.3.207.21
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Pete Resnick <presnick@qti.qualcomm.com>, Alexey Melnikov <aamelnikov@fastmail.fm>
Cc: draft-baeuerle-netnews-cancel-lock.all@ietf.org, General Area Review Team <gen-art@ietf.org>
References: <9be2e7af-b99d-4f86-6552-bfada936600d@alum.mit.edu> <20170707174750.487009ed@WStation4> <7452e826-62e9-0d6e-32b5-dcdefcb4c2ea@alum.mit.edu> <20170711203934.458e3b62@WStation4> <37001dcd-6551-78b4-18e7-75fbebaff761@alum.mit.edu> <0147f247-2763-8017-f123-5cdd6ceb06b3@alum.mit.edu> <1505814165.1516258.1110891352.7E7D795F@webmail.messagingengine.com> <38d90b33-4edf-8bba-9bfe-9b5f5a0890d3@alum.mit.edu> <1505831034.2210395.1111181888.051F2D85@webmail.messagingengine.com> <D0DEE08D-531E-4CD5-8C65-52B008B7CB02@qti.qualcomm.com> <2761ff34-eec8-d326-18c1-7f126155593f@alum.mit.edu>
From: =?UTF-8?Q?Julien_=c3=89LIE?= <julien@trigofacile.com>
Organization: TrigoFACILE -- http://www.trigofacile.com/
Message-ID: <286bef73-b254-b032-e160-7af4abc5333b@trigofacile.com>
Date: Tue, 19 Sep 2017 22:17:50 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <2761ff34-eec8-d326-18c1-7f126155593f@alum.mit.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/NX48Y0HA_Rww5n4Ni_FCJk8PGzI>
Subject: Re: [Gen-art] draft-baeuerle-netnews-cancel-lock-06 and RFCs 5536 & 5322
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Sep 2017 20:17:57 -0000

Hi Paul,

> Even then, ideally there should have been some words to indicate that 
> the <field-name>s used as extensions for trace be disjoint from those 
> used as non-trace extension headers.
> 
> It gets more ugly when we start to extends <optional-field> 
> syntactically via =/. Now, when the syntax is evaluated the new header 
> fields we are defining show up as explicitly syntactically valid in both 
> places. :-(

In the erratum for RFC 5536, a sentence may be added to say that news 
header fields defined by this document are not trace header fields, in 
the terminology of RFC 5322.

-- 
Julien Ã‰LIE

Â« You know it's love when all you want is that person to be happy;
   even if you're not part of their happiness. Â»


From nobody Tue Sep 19 15:23:30 2017
Return-Path: <linda.dunbar@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB033132944; Tue, 19 Sep 2017 15:23:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 kdoJ_mItu6fI; Tue, 19 Sep 2017 15:23:27 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1DDE13219C; Tue, 19 Sep 2017 15:23:26 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DOX90720; Tue, 19 Sep 2017 22:23:24 +0000 (GMT)
Received: from SJCEML703-CHM.china.huawei.com (10.208.112.39) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.301.0; Tue, 19 Sep 2017 23:23:23 +0100
Received: from SJCEML702-CHM.china.huawei.com ([169.254.4.207]) by SJCEML703-CHM.china.huawei.com ([169.254.5.15]) with mapi id 14.03.0301.000; Tue, 19 Sep 2017 15:23:18 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-ippm-alt-mark@ietf.org" <draft-ietf-ippm-alt-mark@ietf.org>
Thread-Topic: [Gen-art] Gen-art last call review of draft-ietf-ippm-alt-mark-10
Thread-Index: AdMxlA/z+MMHihMVRSm0VRqWZ2baoQ==
Date: Tue, 19 Sep 2017 22:23:17 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F65949B9D5@SJCEML702-CHM.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.192.11.78]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090206.59C198DD.0012, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.4.207, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: ce8b428e370d5bdb7494f43eb123aa1e
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/kyGtpNzzVfEXGFDupIwPClectSU>
Subject: [Gen-art] Gen-art last call review of draft-ietf-ippm-alt-mark-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Sep 2017 22:23:29 -0000

Reviewer: Linda Dunbar
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area Review =
Team (Gen-ART) reviews all IETF documents being processed by the IESG for t=
he IETF Chair.  Please treat these comments just like any other last call c=
omments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-ippm-alt-mark-10=20
Reviewer: Linda Dunbar
Review Date: 2017-09-19
IETF LC End Date: 2017-09-28
IESG Telechat date: ??

Summary:

This document is written very clear and comprehensive. It is Ready.=20
One single question remains open, it is minor.

Major issues: None

Minor issues:

Section 3.1.1, second paragraph states ".. every node along the path must b=
e able to identify unambiguously the colored packets".=20

I think the scheme should work even if some intermediate nodes don't suppor=
t the proposed scheme. If every node supports the scheme, using Link based =
method, there shouldn't be any disorder of packets. Correct?

Section 3.1.1 last paragraph also states that the "how to choose the markin=
g field ... is out of the scope". Besides the DSCP field, what other option=
s there could be? Just curious.=20

Nits/editorial comments:

Thanks, Linda Dunbar
_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Sep 20 02:19:00 2017
Return-Path: <giuseppe.fioccola@telecomitalia.it>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC0ED13336A; Wed, 20 Sep 2017 02:18:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 uchNpPJtQBkS; Wed, 20 Sep 2017 02:18:50 -0700 (PDT)
Received: from mx01.telecomitalia.it (mx01.telecomitalia.it [217.169.121.10]) (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 B307E1332E4; Wed, 20 Sep 2017 02:18:47 -0700 (PDT)
X-AuditID: d9a9790a-4ddff70000008134-9f-59c232751e3b
Received: from TELMBXB02RM001.telecomitalia.local ( [10.14.252.27]) (using TLS with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by mx01.telecomitalia.it () with SMTP id 77.4D.33076.57232C95; Wed, 20 Sep 2017 11:18:45 +0200 (CEST)
From: Fioccola Giuseppe <giuseppe.fioccola@telecomitalia.it>
To: Linda Dunbar <linda.dunbar@huawei.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-ippm-alt-mark@ietf.org" <draft-ietf-ippm-alt-mark@ietf.org>
Thread-Topic: [Gen-art] Gen-art last call review of draft-ietf-ippm-alt-mark-10
Thread-Index: AdMxlA/z+MMHihMVRSm0VRqWZ2baoQAW8YEw
Date: Wed, 20 Sep 2017 09:18:44 +0000
Message-ID: <2d02340a25c1498d981ced328d217577@TELMBXB02RM001.telecomitalia.local>
References: <4A95BA014132FF49AE685FAB4B9F17F65949B9D5@SJCEML702-CHM.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F65949B9D5@SJCEML702-CHM.china.huawei.com>
Accept-Language: it-IT, en-US
Content-Language: it-IT
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.14.252.238]
x-ti-disclaimer: Disclaimer1
Content-Type: text/plain; charset="iso-8859-1"
content-transfer-encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrFKsWRmVeSWpSXmKPExsXCxfdHWrfU6FCkwcoXEhZtayczWlx99ZnF 4tnG+SwWd1smMjmweLQcecvqsWTJT6YApqgGRpvEvLz8ksSSVIWU1OJkWyWXzOLknMTM3NQi hZDUnNTk/FwlhcwUWyVjJYWCnMTk1NzUvBJbpcSCgtS8FCU7LgUMYANUlpmnkJqXnJ+SmZdu q+QZ7K9rYWFqqWuoZBdYmlpckq+Qm1pcnJienpmvkJqwXjCjccIs5oKFEhVXmpcwNjA2i3Qx cnJICJhI7F74nL2LkYtDSGAqk8TxO+sZQRJsAjYSB1+dYAOxRQSCJVY9fQUWZxbIk7i8ei8T iC0s4Cvx/s9OJoiaQImz0zawdDFyANlGEnNO2IKEWQRUJZo6DoK18gKVnNq+iR3EFhIIlThz 7xBYK6dAmMS2nTPA4owCshITdi+CWiUu8WL6CXaIOwUkluw5zwxhi0q8fPyPFcI2kNi6dB8L hK0o8fH8ZkYIW0Zi4ZHJrBBz9CRuTJ3CBmFrSyxb+JoZ4h5BiZMzn7BMYBSbhWTdLCQts5C0 zELSsoCRZRWjaG6FgaFeCST6MksSczIT9TJLNjECE8jNlZVcOxhfr3I+xCjAwajEw7s58WCk EGtiWXFl7iFGCQ5mJRFeX8NDkUK8KYmVValF+fFFpTmpxYcYfYAhNpFZSjQ5H5jc8kriDU0s LA2NLSyMDC3MTHEIK4nzhmkBzRJIB6av7NTUgtQimHFMHJxSDYxyCq+P/bha+Ozjzry8sKC0 2NdbjhyQMZf697E25uW73xNOKnyMiVNICYptmBp2PvfTUfP5ThyrYqblVgkJbH/g2vbEeo32 j/AvU5/MLFLj76sIO3z19Y+U0vVdlfcWbzlQyfJeMkeqbl6PWkTip7qGW/N0Pura8rw5uIOz V559dcRO5ywbe3klluKMREMt5qLiRAAmreysTQMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/nRV4h6Zyet_zHV2qOFcQETmgOWA>
Subject: [Gen-art] R: Gen-art last call review of draft-ietf-ippm-alt-mark-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Sep 2017 09:18:53 -0000

Hi Linda,
Thank you for your considerations.
Please see my answers inline tagged as [GF].

Best Regards,

Giuseppe

-----Messaggio originale-----
Da: Linda Dunbar [mailto:linda.dunbar@huawei.com] 
Inviato: mercoled=EC 20 settembre 2017 00:23
A: gen-art@ietf.org
Cc: ietf@ietf.org; draft-ietf-ippm-alt-mark@ietf.org
Oggetto: [Gen-art] Gen-art last call review of draft-ietf-ippm-alt-mark-10



Reviewer: Linda Dunbar
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area Review T=
eam (Gen-ART) reviews all IETF documents being processed by the IESG for the=
 IETF Chair.  Please treat these comments just like any other last call comm=
ents.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-ippm-alt-mark-10 
Reviewer: Linda Dunbar
Review Date: 2017-09-19
IETF LC End Date: 2017-09-28
IESG Telechat date: ??

Summary:

This document is written very clear and comprehensive. It is Ready. 
One single question remains open, it is minor.

Major issues: None

Minor issues:

Section 3.1.1, second paragraph states ".. every node along the path must be=
 able to identify unambiguously the colored packets". 

I think the scheme should work even if some intermediate nodes don't support=
 the proposed scheme. If every node supports the scheme, using Link based me=
thod, there shouldn't be any disorder of packets. Correct?

[GF]: You are right, the scheme will work even if some intermediate nodes ar=
e not able to identify unambiguously the colored packets. I could change thi=
s sentence because I meant that ".. every node that is designated as a measu=
rement point should be able to identify unambiguously the colored packets".=
 The out of order issue could be avoided in any case by taking the counter d=
uring the available counting interval (as described in section 3.2) that con=
siders the interval we need to wait to avoid out of order because of network=
 delay and clock error between network devices.

Section 3.1.1 last paragraph also states that the "how to choose the marking=
 field ... is out of the scope". Besides the DSCP field, what other options=
 there could be? Just curious. 

[GF]: Besides the DSCP field in the IPv4 Header, draft-chen-ippm-coloring-ba=
sed-ipfpm-framework suggests to use the "evil bit" (unused bit in the IPv4 F=
lags field) to perform marking (the IPFPM use case is mentioned in section 5=
.2). In addition, regarding MPLS, Synonymous Flow Label can be used for mark=
ing as reported in section 5.4 (draft-ietf-mpls-rfc6374-sfl). Regarding BIER=
, two OAM bits from BIER Header are reserved for the passive performance mea=
surement marking method (draft-ietf-bier-pmmm-oam). There are also new propo=
sals in NVO3 (draft-fmm-nvo3-pm-alt-mark) and SFC (draft-mirsky-sfc-pmamm).=
 

Nits/editorial comments:

Thanks, Linda Dunbar
_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle pers=
one indicate. La diffusione, copia o qualsiasi altra azione derivante dalla=
 conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbia=
te ricevuto questo documento per errore siete cortesemente pregati di darne=
 immediata comunicazione al mittente e di provvedere alla sua distruzione, G=
razie. 

This e-mail and any attachments is confidential and may contain privileged i=
nformation intended for the addressee(s) only. Dissemination, copying, print=
ing or use by anybody else is unauthorised. If you are not the intended reci=
pient, please delete this message and any attachments and advise the sender=
 by return e-mail, Thanks. 

Rispetta l'ambiente. Non stampare questa mail se non =E8 necessario.


From nobody Wed Sep 20 02:54:04 2017
Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9A04134292; Wed, 20 Sep 2017 02:54:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.fm header.b=avOWE/sc; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=OX57kuk7
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 n71_yus28iFE; Wed, 20 Sep 2017 02:54:00 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6A2F134237; Wed, 20 Sep 2017 02:54:00 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 0D0C220CF3; Wed, 20 Sep 2017 05:54:00 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Wed, 20 Sep 2017 05:54:00 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=xALKHcc+9bEtTLqmh1 Lmp0e348WkhFMl7IrN6LuIdlg=; b=avOWE/scTq89lqtaUPtWq/T281PNeHAxEz +idQpC9u4xdM4/2UnT+oezlSe9l7LNEENGpxuwBTZICQug+rpLAaNLnhQ20aTiXY uOYCmwUg2DB1wOI6PxiwwG//F/elIXDl5XJzrjY/3Q0QspR9i0fOxt24Rk9Q2uxP hju3/vgrW0OJ46sWzhO5c22v2xkyCTvN8/0HICBI+FhV1nq6EClJPw9ZfZEA4F3b XLQYe0kry+//qdmFefeZvN+ctpjfLU97IIqs2n8NrdsAySfKRLBOCGuchYuaMuFE 92kQzq7NtvOf2UfzUANFGNq9mZoGXn9yHsjzGc+iR01oagaI0y5w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=xALKHcc+9bEtTLqmh1Lmp0e348WkhFMl7IrN6LuIdlg=; b=OX57kuk7 vgZwMJLInwxAVQEm1pVIuRWgUSL+k+4G6pAGJctD9+2GQrhpbcTaLo3U6JqJqrs8 lVHRAT9lNfby3ycdMcq2axyDNa7Wjk7lmcBGyh5yrkBbUqWZsbOFuzPY5tsTxxOG shPW9czkc1yD7otYdgN6m+QBbyBlJdBd6k34nc9mramMCJKcic89s4/yZYQ5AZey PogFSbkLpZ0I+wiXNdCd3bAjtFJ13+1YJ91B2dSxHwPWHcqvOfmNu22d3UQdgg5E zhQ8X+EnLaTnh6hF5q8FnnejrCTkmIRbZ5NMxqY3OyiPcGlt4Rpki1Kh/5gqSneY H1EqRvXjGV7+UQ==
X-ME-Sender: <xms:tzrCWehvBiUa-pzoLaUEHjo9G3w3trhY-IgBykzlA8G1DdGH3487Bg>
X-Sasl-enc: sJ6AqaxUTK+EpYS5uknx1O492x863UV8rA+RTOuqZk8w 1505901239
Received: from [10.4.40.8] (unknown [85.255.237.23]) by mail.messagingengine.com (Postfix) with ESMTPA id 7EA7E7F94C; Wed, 20 Sep 2017 05:53:59 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: iPhone Mail (13G35)
In-Reply-To: <2761ff34-eec8-d326-18c1-7f126155593f@alum.mit.edu>
Date: Wed, 20 Sep 2017 10:57:29 +0100
Cc: Pete Resnick <presnick@qti.qualcomm.com>, draft-baeuerle-netnews-cancel-lock.all@ietf.org, General Area Review Team <gen-art@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E06A5BFE-8232-43D7-8F39-CF441B90720A@fastmail.fm>
References: <9be2e7af-b99d-4f86-6552-bfada936600d@alum.mit.edu> <20170707174750.487009ed@WStation4> <7452e826-62e9-0d6e-32b5-dcdefcb4c2ea@alum.mit.edu> <20170711203934.458e3b62@WStation4> <37001dcd-6551-78b4-18e7-75fbebaff761@alum.mit.edu> <0147f247-2763-8017-f123-5cdd6ceb06b3@alum.mit.edu> <1505814165.1516258.1110891352.7E7D795F@webmail.messagingengine.com> <38d90b33-4edf-8bba-9bfe-9b5f5a0890d3@alum.mit.edu> <1505831034.2210395.1111181888.051F2D85@webmail.messagingengine.com> <D0DEE08D-531E-4CD5-8C65-52B008B7CB02@qti.qualcomm.com> <2761ff34-eec8-d326-18c1-7f126155593f@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/SD-QWitBITTfVWZxVs8IZWj4rb0>
Subject: Re: [Gen-art] draft-baeuerle-netnews-cancel-lock-06 and RFCs 5536 & 5322
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Sep 2017 09:54:02 -0000

Hi Paul,

> On 19 Sep 2017, at 21:02, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>=20
>> On 9/19/17 2:41 PM, Pete Resnick wrote:
>> On 19 Sep 2017, at 9:23, Alexey Melnikov wrote:
>>            optional-field =3D/ *( approved /
>>            archive /
>>            control /
>>            distribution /
>>            expires /
>>            followup-to /
>>            injection-date /
>>            injection-info /
>>            lines /
>>            newsgroups /
>>            organization /
>>            path /
>>            summary /
>>            supersedes /
>>            user-agent /
>>            xref )
>>        I see one issue with the above. <optional-field> appears *twice*
>>        in the
>>        definition of <fields> in 5322. I don't understand what the
>>        intent was
>>        there - whether it was a mistake or was trying to express
>>        something that
>>        I am missing.
>>    I believe it was entirely intentional. The first instance allows to ad=
d
>>    new trace header fields (which should be kept together in groups), the=

>>    second allows adding other types of header fields.
>> Correct, that was the intention. In 5322, optional-field is a catchall fo=
r any new header field, so you need one for new trace fields and one for oth=
er fields. Otherwise, there's no way to put a new field between two trace fi=
elds. This was a fix in 5322 from 2822.
>>        This really needs some further discussion. (E.g., should
>>        the valid values for <optional-field> as used with trace be distin=
ct
>>        from those in its later appearance?
>>    Yes. It would have been better to have 2 separate productions, like
>>    trace-optional-field and other-optional-field, but what Pete did seems=

>>    to be Ok.
>=20
> This probably wasn't *too* bad as long as <optional-field> was simply defi=
ned as:
>=20
>   optional-field  =3D   field-name ":" unstructured CRLF
>=20
> Even then, ideally there should have been some words to indicate that the <=
field-name>s used as extensions for trace be disjoint from those used as non=
-trace extension headers.
>=20
> It gets more ugly when we start to extends <optional-field> syntactically v=
ia =3D/. Now, when the syntax is evaluated the new header fields we are defi=
ning show up as explicitly syntactically valid in both places. :-(
>=20
>> Yes, that might have been nice, but putting extensibility syntax througho=
ut the grammar starts to get ugly. (Imagine resent-optional-field, originato=
r-optional-field, etc.) I think just one is fine.
>=20
> Since there is an IANA registry, another possibility would be to not attem=
pt to revise the syntax from 5322 at all.

On my memory most of new header fields are defined without extending "option=
al-field" production. So people are already doing what you propose.

> Instead, simply rely on the the extensibility already there via <optional-=
field> and register all the new header fields in the IANA registry. (Use ABN=
F to define the syntax of the individual new headers but not their linkage i=
nto the message.)
>=20
> Then use text to specify conditions about where they may appear in a messa=
ge.

Right.

>    Thanks,
>    Paul
>=20
>>        This needs to be thrashed out with
>>        mail experts before this fix is finalized. I don't know what
>>        forum is
>>        appropriate for that.
>>    I am not sure. Pete?
>> Probably ietf-822, but (a) I personally haven't read the list in a very l=
ong time, and (b) I don't think there's anything terribly controversial abou=
t the change.
>>        Ignoring that, I agree this change to 5536 would achieve the goal
>>        without requiring a change in 5322, which is progress. However I
>>        think a
>>        tweak to the above would be be a bit cleaner:
>>        optional-field =3D/ approved /
>>        archive /
>>        control /
>>        distribution /
>>        expires /
>>        followup-to /
>>        injection-date /
>>        injection-info /
>>        lines /
>>        newsgroups /
>>        organization /
>>        path /
>>        summary /
>>        supersedes /
>>        user-agent /
>>        xref
>>        This is definitely a better fix than I was suggesting. (Thank
>>        you Pete!)
>>    Good.
>> You're very welcome. I am equally fine with Alexey and Julien's version:
>> |optional-field =3D <see RFC 5322 Section 3.6.8> news-fields =3D approved=
 / archive / control / distribution / expires / followup-to / injection-date=
 / injection-info / lines / newsgroups / organization / path / summary / sup=
ersedes / user-agent / xref optional-field /=3D newsfields |
>> pr
>> --=20
>> Pete Resnick http://www.qualcomm.com/~presnick/ <http://www.qualcomm.com/=
%7Epresnick/>
>> Qualcomm Technologies, Inc. - +1 (858)651-4478
>=20


From nobody Wed Sep 20 03:56:21 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7756E126C0F; Wed, 20 Sep 2017 03:56:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stewart Bryant <stewart.bryant@gmail.com>
To: <gen-art@ietf.org>
Cc: draft-kille-ldap-xmpp-schema.all@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.62.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150590497937.29233.14546248725198048319@ietfa.amsl.com>
Date: Wed, 20 Sep 2017 03:56:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/gSFy5fF3fYo3T3jK7H4JcTSyxMc>
Subject: [Gen-art] Genart last call review of draft-kille-ldap-xmpp-schema-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Sep 2017 10:56:19 -0000

Reviewer: Stewart Bryant
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-kille-ldap-xmpp-schema-05
Reviewer: Stewart Bryant
Review Date: 2017-09-20
IETF LC End Date: 2017-09-27
IESG Telechat date: Not scheduled for a telechat

Summary: A well written document, however it uses an example email address that
might be allocated in the future, rather than one for the example range.

Major issues: None

Minor issues:

"romeo@shakespeare.lit representing a user) "

That is a really cool example! However I can imagine .lit eventually being
allocated so we ought to use one of the RFC6761 example TLDs.

Nits/editorial comments:  None



From nobody Wed Sep 20 06:39:53 2017
Return-Path: <steve.kille@isode.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1655D133053; Wed, 20 Sep 2017 06:39:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.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 hJTte-ZhkllG; Wed, 20 Sep 2017 06:39:44 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 0050B13422C; Wed, 20 Sep 2017 06:39:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1505914777; d=isode.com; s=june2016; i=@isode.com; bh=UlKiLcFc98RaqISkdw5NBtUJ7q1GDIcUymR0u/ra3A4=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=qK1OdEerktZpYUgq/BJOh3hMf6MiN/uKfshEPJOH3GOgQQgSvVpWA+DcUeGGreAAMBxOOl mDt0XoptdC40EtiLQWatGyvmeA5v3ddI1UbKnwqwsK7D7Cwj8n1JGsIoPQiY9o+1U1fUde X+uVjoWWy4joQHxsYV0Kkc4ay5e4b90=;
Received: from MonteRosa ((unknown) [62.232.206.186])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <WcJvmQBsZgLO@waldorf.isode.com>; Wed, 20 Sep 2017 14:39:37 +0100
X-SMTP-Protocol-Errors: NORDNS
From: "Steve Kille" <steve.kille@isode.com>
To: "'Stewart Bryant'" <stewart.bryant@gmail.com>, <gen-art@ietf.org>
Cc: <draft-kille-ldap-xmpp-schema.all@ietf.org>, <ietf@ietf.org>
References: <150590497937.29233.14546248725198048319@ietfa.amsl.com>
In-Reply-To: <150590497937.29233.14546248725198048319@ietfa.amsl.com>
Date: Wed, 20 Sep 2017 14:39:35 +0100
Message-ID: <04c201d33215$e5eec990$b1cc5cb0$@isode.com>
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKEgQn09NW4Xt7wx2nBbgql5QM3I6FbKP5w
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/UFOVsPfz2aFgTrgRtKf5GgSJO84>
Subject: Re: [Gen-art] Genart last call review of draft-kille-ldap-xmpp-schema-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Sep 2017 13:39:51 -0000

Stewart,

These Shakespearean style addresses are conventionally used in XMPP =
XEPs, and I followed that style here.

I've discussed with XMPP colleagues, and we agree that although the =
convention is cool, you are right that a safe address should be used.

I have fixed this in 06, which I just submitted


Regards


Steve=20

> -----Original Message-----
> From: Stewart Bryant [mailto:stewart.bryant@gmail.com]
> Sent: 20 September 2017 11:56
> To: gen-art@ietf.org
> Cc: draft-kille-ldap-xmpp-schema.all@ietf.org; ietf@ietf.org
> Subject: Genart last call review of draft-kille-ldap-xmpp-schema-05
>=20
> Reviewer: Stewart Bryant
> Review result: Ready with Nits
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area =
Review
> Team (Gen-ART) reviews all IETF documents being processed by the IESG =
for
> the IETF Chair.  Please treat these comments just like any other last =
call
> comments.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-kille-ldap-xmpp-schema-05
> Reviewer: Stewart Bryant
> Review Date: 2017-09-20
> IETF LC End Date: 2017-09-27
> IESG Telechat date: Not scheduled for a telechat
>=20
> Summary: A well written document, however it uses an example email
> address that might be allocated in the future, rather than one for the
> example range.
>=20
> Major issues: None
>=20
> Minor issues:
>=20
> "romeo@shakespeare.lit representing a user) "
>=20
> That is a really cool example! However I can imagine .lit eventually =
being
> allocated so we ought to use one of the RFC6761 example TLDs.
>=20
> Nits/editorial comments:  None
>=20



From nobody Wed Sep 20 07:00:38 2017
Return-Path: <dave@cridland.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 607BB1331E7 for <gen-art@ietfa.amsl.com>; Wed, 20 Sep 2017 07:00:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cridland.net
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 lNL-1GRCBuTz for <gen-art@ietfa.amsl.com>; Wed, 20 Sep 2017 07:00:31 -0700 (PDT)
Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85B1B133052 for <gen-art@ietf.org>; Wed, 20 Sep 2017 07:00:28 -0700 (PDT)
Received: by mail-lf0-x230.google.com with SMTP id u21so2779707lfk.12 for <gen-art@ietf.org>; Wed, 20 Sep 2017 07:00:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=i4y9cvr0H0T2FsDMoGNsdzbRMkHKSOzvEc9RrfXmfQM=; b=IwNEh9J9QLVEWNznHvDyIqPnWitQ533Yo1c1mRNU0HN5YrgtJNcoEgr2JH0HQKZavV aqlLvzhKOudLQILu3QGJ6hd84KTdpsn5VuAIYTNm0MBcSpXMFHKD82M9SoDEd9ak7PVr wKV/G/73aHpr7GGpdHu1oU7z8NMXBTxHSi8UQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=i4y9cvr0H0T2FsDMoGNsdzbRMkHKSOzvEc9RrfXmfQM=; b=GUssgrJ3/57IhHe7U7Y0u8NmxADbTxyCe9vtAEsMrXEBlBS1dDxNwmSWf3hUM4kInP JamQ81mzJnutBatF3reQ6bCw1J6N4ozHgcDMZNx1tlkZBIkpJkadFFUwZAdnUw0MYnbA k87dN538pVzLkjvheGyttOWS9uP5/egck3l1zcXi6a4YyWxNW2o6fmTvo2UNy0MgT+mi KFjPzEs7kFk0dL8zXPrEvMO3j97KWALu6o4m9kH+xZAtKnVo/wJyamQVRpIukCQx2jbj venwlDdAgj5yAugI+DIJfDGBwzsUCOaVvrCHfZExZz/tt8ocTHd4mbzViCa0dDTzkGaM 5ujg==
X-Gm-Message-State: AHPjjUiBQ4EKVsKd4EI3ederQxrQvBTLbPpPaHSuMEAWs1pnejckgLmk veQ5aGMyqcHyh/I9xbiibeKTQkDaVZ8nFYsgYbpOuw==
X-Google-Smtp-Source: AOwi7QCUFLyjMBoIUqZdpfNTybJ0lfZJMYVOtK9klIkfykUm6nKRHJ+zYGrllgWE/Xcjjsi3q6DxM45lxGsYQamUH9o=
X-Received: by 10.46.84.74 with SMTP id y10mr2549052ljd.89.1505916026647; Wed, 20 Sep 2017 07:00:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.179.75.138 with HTTP; Wed, 20 Sep 2017 07:00:26 -0700 (PDT)
Received: by 10.179.75.138 with HTTP; Wed, 20 Sep 2017 07:00:26 -0700 (PDT)
In-Reply-To: <04c201d33215$e5eec990$b1cc5cb0$@isode.com>
References: <150590497937.29233.14546248725198048319@ietfa.amsl.com> <04c201d33215$e5eec990$b1cc5cb0$@isode.com>
From: Dave Cridland <dave@cridland.net>
Date: Wed, 20 Sep 2017 15:00:26 +0100
Message-ID: <CAKHUCzw-g-xb4hPaLqyiqK3yLebS5EG_P57fCPA4PpnCDR_F_Q@mail.gmail.com>
To: Steve Kille <steve.kille@isode.com>
Cc: "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>, "ietf@ietf.org Discussion" <ietf@ietf.org>,  draft-kille-ldap-xmpp-schema.all@ietf.org,  Stewart Bryant <stewart.bryant@gmail.com>
Content-Type: multipart/alternative; boundary="f403045fb4ced4991c05599f6581"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/ZexYbnaYaYSqS7DpmMRGQxEDjGQ>
Subject: Re: [Gen-art] Genart last call review of draft-kille-ldap-xmpp-schema-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Sep 2017 14:00:33 -0000

--f403045fb4ced4991c05599f6581
Content-Type: text/plain; charset="UTF-8"

shakespeare.example is a fine domain to use - the XMPP community (mostly
due to Peter Saint-Andre) has used these inventive domains to express
examples with more clarity - montague.lit, capulet.lit, and so on provide
usefully recognisable domains. But .example is just as good as .lit, and
just as clear.

On 20 Sep 2017 14:39, "Steve Kille" <steve.kille@isode.com> wrote:

Stewart,

These Shakespearean style addresses are conventionally used in XMPP XEPs,
and I followed that style here.

I've discussed with XMPP colleagues, and we agree that although the
convention is cool, you are right that a safe address should be used.

I have fixed this in 06, which I just submitted


Regards


Steve

> -----Original Message-----
> From: Stewart Bryant [mailto:stewart.bryant@gmail.com]
> Sent: 20 September 2017 11:56
> To: gen-art@ietf.org
> Cc: draft-kille-ldap-xmpp-schema.all@ietf.org; ietf@ietf.org
> Subject: Genart last call review of draft-kille-ldap-xmpp-schema-05
>
> Reviewer: Stewart Bryant
> Review result: Ready with Nits
>
> I am the assigned Gen-ART reviewer for this draft. The General Area Review
> Team (Gen-ART) reviews all IETF documents being processed by the IESG for
> the IETF Chair.  Please treat these comments just like any other last call
> comments.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-kille-ldap-xmpp-schema-05
> Reviewer: Stewart Bryant
> Review Date: 2017-09-20
> IETF LC End Date: 2017-09-27
> IESG Telechat date: Not scheduled for a telechat
>
> Summary: A well written document, however it uses an example email
> address that might be allocated in the future, rather than one for the
> example range.
>
> Major issues: None
>
> Minor issues:
>
> "romeo@shakespeare.lit representing a user) "
>
> That is a really cool example! However I can imagine .lit eventually being
> allocated so we ought to use one of the RFC6761 example TLDs.
>
> Nits/editorial comments:  None
>

--f403045fb4ced4991c05599f6581
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div>shakespeare.example is a fine domain to use - the XM=
PP community (mostly due to Peter Saint-Andre) has used these inventive dom=
ains to express examples with more clarity - montague.lit, capulet.lit, and=
 so on provide usefully recognisable domains. But .example is just as good =
as .lit, and just as clear.<br><div class=3D"gmail_extra"><br><div class=3D=
"gmail_quote">On 20 Sep 2017 14:39, &quot;Steve Kille&quot; &lt;<a href=3D"=
mailto:steve.kille@isode.com">steve.kille@isode.com</a>&gt; wrote:<br type=
=3D"attribution"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex">Stewart,<br>
<br>
These Shakespearean style addresses are conventionally used in XMPP XEPs, a=
nd I followed that style here.<br>
<br>
I&#39;ve discussed with XMPP colleagues, and we agree that although the con=
vention is cool, you are right that a safe address should be used.<br>
<br>
I have fixed this in 06, which I just submitted<br>
<br>
<br>
Regards<br>
<font color=3D"#888888"><br>
<br>
Steve<br>
</font><div class=3D"elided-text"><br>
&gt; -----Original Message-----<br>
&gt; From: Stewart Bryant [mailto:<a href=3D"mailto:stewart.bryant@gmail.co=
m">stewart.bryant@gmail.<wbr>com</a>]<br>
&gt; Sent: 20 September 2017 11:56<br>
&gt; To: <a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br>
&gt; Cc: <a href=3D"mailto:draft-kille-ldap-xmpp-schema.all@ietf.org">draft=
-kille-ldap-xmpp-schema.<wbr>all@ietf.org</a>; <a href=3D"mailto:ietf@ietf.=
org">ietf@ietf.org</a><br>
&gt; Subject: Genart last call review of draft-kille-ldap-xmpp-schema-<wbr>=
05<br>
&gt;<br>
&gt; Reviewer: Stewart Bryant<br>
&gt; Review result: Ready with Nits<br>
&gt;<br>
&gt; I am the assigned Gen-ART reviewer for this draft. The General Area Re=
view<br>
&gt; Team (Gen-ART) reviews all IETF documents being processed by the IESG =
for<br>
&gt; the IETF Chair.=C2=A0 Please treat these comments just like any other =
last call<br>
&gt; comments.<br>
&gt;<br>
&gt; For more information, please see the FAQ at<br>
&gt;<br>
&gt; &lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/GenArtfaq" rel=3D"n=
oreferrer" target=3D"_blank">https://trac.ietf.org/trac/<wbr>gen/wiki/GenAr=
tfaq</a>&gt;.<br>
&gt;<br>
&gt; Document: draft-kille-ldap-xmpp-schema-<wbr>05<br>
&gt; Reviewer: Stewart Bryant<br>
&gt; Review Date: 2017-09-20<br>
&gt; IETF LC End Date: 2017-09-27<br>
&gt; IESG Telechat date: Not scheduled for a telechat<br>
&gt;<br>
&gt; Summary: A well written document, however it uses an example email<br>
&gt; address that might be allocated in the future, rather than one for the=
<br>
&gt; example range.<br>
&gt;<br>
&gt; Major issues: None<br>
&gt;<br>
&gt; Minor issues:<br>
&gt;<br>
&gt; &quot;romeo@shakespeare.lit representing a user) &quot;<br>
&gt;<br>
&gt; That is a really cool example! However I can imagine .lit eventually b=
eing<br>
&gt; allocated so we ought to use one of the RFC6761 example TLDs.<br>
&gt;<br>
&gt; Nits/editorial comments:=C2=A0 None<br>
&gt;<br>
<br>
<br>
</div></blockquote></div><br></div></div></div>

--f403045fb4ced4991c05599f6581--


From nobody Wed Sep 20 07:26:24 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B51713293A; Wed, 20 Sep 2017 07:26:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 LRyXV4uZh0ak; Wed, 20 Sep 2017 07:26:20 -0700 (PDT)
Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69A7E13217D; Wed, 20 Sep 2017 07:26:18 -0700 (PDT)
Received: by mail-wr0-x232.google.com with SMTP id k20so2323817wre.4; Wed, 20 Sep 2017 07:26:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=6fb6abX6CMWGzUUVKA5PhxzigSGD6oh3mpwVwrwjsbY=; b=nq6HlK9GKtlLVG+aewEgvGtj9OlUA/09NIFerikb37P9nlIGkpjo5ODlh1mXqFDbSJ g4Q/yvQko4kGXL2BkmKyu0iMEsbiZ2AJIMnT5ruSoKVHtGDXRoAX6AYEymLrZyFP2i37 cUjgAxoCaLmbz+rezSlgB+F3S/txKLx/LVTy6u7uqzt1TAXEHqurdkx8HV8dYCG3f05M 90MoqEPp9zfeVH99KrS73y7lvepM1PULIuPEc188zh8j+O80qAC29rPcQ3MdIvMt71wn 7ZkF5XzSWF7+yv75GqM2LuWWEVmpRq4NFp8/m2vCNH+tVoMFacRhp9OIMW24opA9CcNi BOmA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=6fb6abX6CMWGzUUVKA5PhxzigSGD6oh3mpwVwrwjsbY=; b=dndwuzo/6GtAUQMFm8/QLBrjA/XyqnvNrXJ255COE2p6/WJ6pT588yEZrkZCjX9vlj Y1d7oIcgf81MTpdw8XE2I42PvVgCCKqy+g/VOzDXJybOzOjfEPd6qU+oZrGOZeqgwwzK +1rqwHcZfp2/q9CdN9BxXk5TF3slIaShxjFk7I2jFXpZd4W43boyMeBJfBKkf5iNPfd1 35/VKylYs20/yI5hpl+rFZqFEzrMYTbOKmel+JdKdbPvG3BuU3w7IJ+e+TpnC1lAF3Ot 1AGvnioglBy5XXg8UB5+HlZLBAuQeXkMeUzKUM84nSrD1jt8Z7eWKUKKR4m9tiYklZ0r PI/Q==
X-Gm-Message-State: AHPjjUiejfyVFvZzdF4NHhE4UQ/xn/7ItLOx4yBkQhw+H3bBxHnUpW0a MvyxIvw6tW13XZmp4t8k/DfEqSk8
X-Google-Smtp-Source: AOwi7QAFJSoXYsGv+2nt80ZV94YgiN0Vm0KS5c9TZ5HxPQLwxE0f2Tcheu+4Is7Rwn/HjeOp5PbpnA==
X-Received: by 10.223.153.106 with SMTP id x97mr4677985wrb.107.1505917576514;  Wed, 20 Sep 2017 07:26:16 -0700 (PDT)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id m19sm1797519wmd.16.2017.09.20.07.26.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Sep 2017 07:26:15 -0700 (PDT)
To: Dave Cridland <dave@cridland.net>, Steve Kille <steve.kille@isode.com>
Cc: "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>, "ietf@ietf.org Discussion" <ietf@ietf.org>, draft-kille-ldap-xmpp-schema.all@ietf.org
References: <150590497937.29233.14546248725198048319@ietfa.amsl.com> <04c201d33215$e5eec990$b1cc5cb0$@isode.com> <CAKHUCzw-g-xb4hPaLqyiqK3yLebS5EG_P57fCPA4PpnCDR_F_Q@mail.gmail.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <2262cd3e-6483-609e-9354-fe0616ac6656@gmail.com>
Date: Wed, 20 Sep 2017 15:26:14 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <CAKHUCzw-g-xb4hPaLqyiqK3yLebS5EG_P57fCPA4PpnCDR_F_Q@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------E76D2F3D45D717414225E76E"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/-05oALbgSC3nkl116543O9st6fw>
Subject: Re: [Gen-art] Genart last call review of draft-kille-ldap-xmpp-schema-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Sep 2017 14:26:23 -0000

This is a multi-part message in MIME format.
--------------E76D2F3D45D717414225E76E
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Thanks for doing the update.

- Stewart


On 20/09/2017 15:00, Dave Cridland wrote:
> shakespeare.example is a fine domain to use - the XMPP community 
> (mostly due to Peter Saint-Andre) has used these inventive domains to 
> express examples with more clarity - montague.lit, capulet.lit, and so 
> on provide usefully recognisable domains. But .example is just as good 
> as .lit, and just as clear.
>
> On 20 Sep 2017 14:39, "Steve Kille" <steve.kille@isode.com 
> <mailto:steve.kille@isode.com>> wrote:
>
>     Stewart,
>
>     These Shakespearean style addresses are conventionally used in
>     XMPP XEPs, and I followed that style here.
>
>     I've discussed with XMPP colleagues, and we agree that although
>     the convention is cool, you are right that a safe address should
>     be used.
>
>     I have fixed this in 06, which I just submitted
>
>
>     Regards
>
>
>     Steve
>
>     > -----Original Message-----
>     > From: Stewart Bryant [mailto:stewart.bryant@gmail.com
>     <mailto:stewart.bryant@gmail.com>]
>     > Sent: 20 September 2017 11:56
>     > To: gen-art@ietf.org <mailto:gen-art@ietf.org>
>     > Cc: draft-kille-ldap-xmpp-schema.all@ietf.org
>     <mailto:draft-kille-ldap-xmpp-schema.all@ietf.org>; ietf@ietf.org
>     <mailto:ietf@ietf.org>
>     > Subject: Genart last call review of draft-kille-ldap-xmpp-schema-05
>     >
>     > Reviewer: Stewart Bryant
>     > Review result: Ready with Nits
>     >
>     > I am the assigned Gen-ART reviewer for this draft. The General
>     Area Review
>     > Team (Gen-ART) reviews all IETF documents being processed by the
>     IESG for
>     > the IETF Chair.Â  Please treat these comments just like any other
>     last call
>     > comments.
>     >
>     > For more information, please see the FAQ at
>     >
>     > <https://trac.ietf.org/trac/gen/wiki/GenArtfaq
>     <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>>.
>     >
>     > Document: draft-kille-ldap-xmpp-schema-05
>     > Reviewer: Stewart Bryant
>     > Review Date: 2017-09-20
>     > IETF LC End Date: 2017-09-27
>     > IESG Telechat date: Not scheduled for a telechat
>     >
>     > Summary: A well written document, however it uses an example email
>     > address that might be allocated in the future, rather than one
>     for the
>     > example range.
>     >
>     > Major issues: None
>     >
>     > Minor issues:
>     >
>     > "romeo@shakespeare.lit representing a user) "
>     >
>     > That is a really cool example! However I can imagine .lit
>     eventually being
>     > allocated so we ought to use one of the RFC6761 example TLDs.
>     >
>     > Nits/editorial comments:Â  None
>     >
>
>
>


--------------E76D2F3D45D717414225E76E
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Thanks for doing the update.</p>
    <p>- Stewart<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 20/09/2017 15:00, Dave Cridland
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAKHUCzw-g-xb4hPaLqyiqK3yLebS5EG_P57fCPA4PpnCDR_F_Q@mail.gmail.com">
      <div dir="auto">
        <div>shakespeare.example is a fine domain to use - the XMPP
          community (mostly due to Peter Saint-Andre) has used these
          inventive domains to express examples with more clarity -
          montague.lit, capulet.lit, and so on provide usefully
          recognisable domains. But .example is just as good as .lit,
          and just as clear.<br>
          <div class="gmail_extra"><br>
            <div class="gmail_quote">On 20 Sep 2017 14:39, "Steve Kille"
              &lt;<a href="mailto:steve.kille@isode.com"
                moz-do-not-send="true">steve.kille@isode.com</a>&gt;
              wrote:<br type="attribution">
              <blockquote class="quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">Stewart,<br>
                <br>
                These Shakespearean style addresses are conventionally
                used in XMPP XEPs, and I followed that style here.<br>
                <br>
                I've discussed with XMPP colleagues, and we agree that
                although the convention is cool, you are right that a
                safe address should be used.<br>
                <br>
                I have fixed this in 06, which I just submitted<br>
                <br>
                <br>
                Regards<br>
                <font color="#888888"><br>
                  <br>
                  Steve<br>
                </font>
                <div class="elided-text"><br>
                  &gt; -----Original Message-----<br>
                  &gt; From: Stewart Bryant [mailto:<a
                    href="mailto:stewart.bryant@gmail.com"
                    moz-do-not-send="true">stewart.bryant@gmail.<wbr>com</a>]<br>
                  &gt; Sent: 20 September 2017 11:56<br>
                  &gt; To: <a href="mailto:gen-art@ietf.org"
                    moz-do-not-send="true">gen-art@ietf.org</a><br>
                  &gt; Cc: <a
                    href="mailto:draft-kille-ldap-xmpp-schema.all@ietf.org"
                    moz-do-not-send="true">draft-kille-ldap-xmpp-schema.<wbr>all@ietf.org</a>;
                  <a href="mailto:ietf@ietf.org" moz-do-not-send="true">ietf@ietf.org</a><br>
                  &gt; Subject: Genart last call review of
                  draft-kille-ldap-xmpp-schema-<wbr>05<br>
                  &gt;<br>
                  &gt; Reviewer: Stewart Bryant<br>
                  &gt; Review result: Ready with Nits<br>
                  &gt;<br>
                  &gt; I am the assigned Gen-ART reviewer for this
                  draft. The General Area Review<br>
                  &gt; Team (Gen-ART) reviews all IETF documents being
                  processed by the IESG for<br>
                  &gt; the IETF Chair.Â  Please treat these comments just
                  like any other last call<br>
                  &gt; comments.<br>
                  &gt;<br>
                  &gt; For more information, please see the FAQ at<br>
                  &gt;<br>
                  &gt; &lt;<a
                    href="https://trac.ietf.org/trac/gen/wiki/GenArtfaq"
                    rel="noreferrer" target="_blank"
                    moz-do-not-send="true">https://trac.ietf.org/trac/<wbr>gen/wiki/GenArtfaq</a>&gt;.<br>
                  &gt;<br>
                  &gt; Document: draft-kille-ldap-xmpp-schema-<wbr>05<br>
                  &gt; Reviewer: Stewart Bryant<br>
                  &gt; Review Date: 2017-09-20<br>
                  &gt; IETF LC End Date: 2017-09-27<br>
                  &gt; IESG Telechat date: Not scheduled for a telechat<br>
                  &gt;<br>
                  &gt; Summary: A well written document, however it uses
                  an example email<br>
                  &gt; address that might be allocated in the future,
                  rather than one for the<br>
                  &gt; example range.<br>
                  &gt;<br>
                  &gt; Major issues: None<br>
                  &gt;<br>
                  &gt; Minor issues:<br>
                  &gt;<br>
                  &gt; <a class="moz-txt-link-rfc2396E" href="mailto:romeo@shakespeare.litrepresentingauser)">"romeo@shakespeare.lit representing a user) "</a><br>
                  &gt;<br>
                  &gt; That is a really cool example! However I can
                  imagine .lit eventually being<br>
                  &gt; allocated so we ought to use one of the RFC6761
                  example TLDs.<br>
                  &gt;<br>
                  &gt; Nits/editorial comments:Â  None<br>
                  &gt;<br>
                  <br>
                  <br>
                </div>
              </blockquote>
            </div>
            <br>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------E76D2F3D45D717414225E76E--


From nobody Wed Sep 20 08:07:13 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 325011331C2; Wed, 20 Sep 2017 08:07:08 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: <gen-art@ietf.org>
Cc: opsawg@ietf.org, ietf@ietf.org, draft-ietf-opsawg-service-model-explained.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.62.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150592002817.29335.8762036344417909160@ietfa.amsl.com>
Date: Wed, 20 Sep 2017 08:07:08 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/9mKc7moNYfNLjZyoICb7LjuoT3k>
Subject: [Gen-art] Genart last call review of draft-ietf-opsawg-service-model-explained-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Sep 2017 15:07:08 -0000

Reviewer: Robert Sparks
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-opsawg-service-model-explained-03

Reviewer: Robert Sparks
Review Date: 2017-09-20
IETF LC End Date: 2017-09-20
IESG Telechat date: Not scheduled for a telechat

Summary: Ready for publication as an Informational RFC

This is well written. Hopefully it will help avoid, or at least shorten, rehash
of arguments about choosing the right level of abstraction for service models.

I don't have text to suggest, but please look at the first bullet of section 5.
The explanation here was less helpful than the other bullets. Demonstrating the
confusion due to the reuse of the word "service" doesn't help clarify the
confusion. I wonder if there's more conversation that hasn't been captured that
this paragraph is alluding to.

(nit) I also suggest raising the level of abstraction in the security
consideration section where it currently lists authorization, authentication,
and encryption by speaking initially to what, and calling the how out as a
detail.


From nobody Wed Sep 20 08:22:49 2017
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 728C513301F for <gen-art@ietfa.amsl.com>; Wed, 20 Sep 2017 08:22:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
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 0x9gfQAvrOYZ for <gen-art@ietfa.amsl.com>; Wed, 20 Sep 2017 08:22:47 -0700 (PDT)
Received: from resqmta-ch2-04v.sys.comcast.net (resqmta-ch2-04v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:36]) (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 1DACF1331D9 for <gen-art@ietf.org>; Wed, 20 Sep 2017 08:22:40 -0700 (PDT)
Received: from resomta-ch2-10v.sys.comcast.net ([69.252.207.106]) by resqmta-ch2-04v.sys.comcast.net with ESMTP id ugpUdd7t7kqLNugpjdNIaA; Wed, 20 Sep 2017 15:22:39 +0000
Received: from PaulKyzivatsMBP.localdomain ([24.62.227.142]) by resomta-ch2-10v.sys.comcast.net with SMTP id ugphdD24XhHTKugpidFM6u; Wed, 20 Sep 2017 15:22:39 +0000
To: Alexey Melnikov <aamelnikov@fastmail.fm>
Cc: Pete Resnick <presnick@qti.qualcomm.com>, draft-baeuerle-netnews-cancel-lock.all@ietf.org, General Area Review Team <gen-art@ietf.org>
References: <9be2e7af-b99d-4f86-6552-bfada936600d@alum.mit.edu> <20170707174750.487009ed@WStation4> <7452e826-62e9-0d6e-32b5-dcdefcb4c2ea@alum.mit.edu> <20170711203934.458e3b62@WStation4> <37001dcd-6551-78b4-18e7-75fbebaff761@alum.mit.edu> <0147f247-2763-8017-f123-5cdd6ceb06b3@alum.mit.edu> <1505814165.1516258.1110891352.7E7D795F@webmail.messagingengine.com> <38d90b33-4edf-8bba-9bfe-9b5f5a0890d3@alum.mit.edu> <1505831034.2210395.1111181888.051F2D85@webmail.messagingengine.com> <D0DEE08D-531E-4CD5-8C65-52B008B7CB02@qti.qualcomm.com> <2761ff34-eec8-d326-18c1-7f126155593f@alum.mit.edu> <E06A5BFE-8232-43D7-8F39-CF441B90720A@fastmail.fm>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <ae382a2c-f966-bfe7-667f-0fa632f2d413@alum.mit.edu>
Date: Wed, 20 Sep 2017 11:22:37 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <E06A5BFE-8232-43D7-8F39-CF441B90720A@fastmail.fm>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfPVvX1xPNx5X7gx3bz2U1CqgiMHw8ezJVoAbXVRt8PuW1oOtlrdH0vu7Tf/dB746t+8m8IMbHwc4+Z/r0al7+fFLBjpJlsJEaT7qeZYk73qLHGIaw3Rd lIwtSQjLjYGpYvoJ4YTH6545La6aKmg8zw2vUcqhnrD7kHmmESUxChwe6o4okatzr0rKTOk6ra0uFIlxCNzV0YOVYcNnjZjx9Khs3aVFBO350YZY2JPbPsCC wHbZ71pTaGekg+mv8cehMCSfx98MvZCkW4iSk8IuIskxMPECtqSw7IGW8SGbxaEtVCzlQIYv3eUMO4/UstYF+yQinlykyM6HFTs6M72ISTA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/l6eJ21-5OQASXJGffELafyI_Ci8>
Subject: Re: [Gen-art] draft-baeuerle-netnews-cancel-lock-06 and RFCs 5536 & 5322
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Sep 2017 15:22:48 -0000

On 9/20/17 5:57 AM, Alexey Melnikov wrote:

>> Since there is an IANA registry, another possibility would be to not attempt to revise the syntax from 5322 at all.
> 
> On my memory most of new header fields are defined without extending "optional-field" production. So people are already doing what you propose.
> 
>> Instead, simply rely on the the extensibility already there via <optional-field> and register all the new header fields in the IANA registry. (Use ABNF to define the syntax of the individual new headers but not their linkage into the message.)
>>
>> Then use text to specify conditions about where they may appear in a message.
> 
> Right.

OK. Barring further comments to the contrary I will revise my review 
(and the erratum) to recommend this approach.

	Thanks,
	Paul


From nobody Wed Sep 20 12:48:57 2017
Return-Path: <enrico.francesconi@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CAB91331C1; Wed, 20 Sep 2017 10:55:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 7eOUleaWok0I; Wed, 20 Sep 2017 10:55:57 -0700 (PDT)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F40F613232C; Wed, 20 Sep 2017 10:55:56 -0700 (PDT)
Received: by mail-wm0-x22e.google.com with SMTP id 13so9406983wmq.2; Wed, 20 Sep 2017 10:55:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=sender:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=aqngQyirtA2EG/EO8SnOT+R8n+JCaJXrlPKC8d76o60=; b=u7I34cGn2KLKIsIB4+oy6vGU/F6IZlk7/hR7kFn+P/Uqr1Xws1s6r4pEgfoUCC1x5s lev2hcat7IJfQYF5RNjadgF3hmjA2Jtmb9pkHcJvC8dUF9BD0lxLoGWIAlN5vQNRROi9 iqFyMDVLLGZSeTXlEh3bkM/Tk3Y2HLQlZSiRai6NkAwRyCDogvA9QQbAcdOLdkv0YiVH G7UPs0JiXbJmjuCA9bCVW4T2x9glvjyRMuoyTw9zjafO2ODRKALHRIBJwCS4CJceQW8U ABgnQWg+A5AIzCoYQw3Dv2v0MnnDmDUXngXj94zTLIHONxqb94t2mBOPwCl+yi2lMyE3 8Y5w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:mime-version:subject:from:in-reply-to :date:cc:content-transfer-encoding:message-id:references:to; bh=aqngQyirtA2EG/EO8SnOT+R8n+JCaJXrlPKC8d76o60=; b=MzUQa0xNI7PeD9vkTqoiPKlnXRzpKxdKXVS5swzUzZC7VjVpL101QU5sPXHF0yd5UR jJ31zEEmLBbN3ocDYnnQLXlGwQVW+tJjJucktGtD9/tuPMSrY8BHttwkrYVm7q/4VzoZ qrTip7v9pyAI24HIEDjuBPEFETAupyWi0Vu6m4KOBB7s5qwMdvEmXDuy2nfKV81joTeF 16EvQkH21sdN8qud/x00AyJ7zdcQEUVV2MZQZryVtd5KRmR/3/b0s8RohO9j+CzOkKxd GLYwP+McQXodFCMZqApBGurqv2xikCB935cSnNfqMY60wZ/uJYFZyHvYWxfGYfeWzyY5 4PeQ==
X-Gm-Message-State: AHPjjUizuwTk/XKKpj5v2yjjLv12M1/IHp02s34M+96E8F0dwaMeSbFN VtctEcHcZNOn/i2Xoc2PwH4=
X-Google-Smtp-Source: AOwi7QDS0SLu2EBxu6dre446URrNlCR6Hmvh0Y5hZJ3SKTrFgm7HD/Tj41AW0xbZsdejraZCY6GfeQ==
X-Received: by 10.80.186.58 with SMTP id g55mr5254589edc.139.1505930155201; Wed, 20 Sep 2017 10:55:55 -0700 (PDT)
Received: from [192.168.0.3] ([94.103.212.185]) by smtp.gmail.com with ESMTPSA id d2sm1395344eda.71.2017.09.20.10.55.53 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 20 Sep 2017 10:55:53 -0700 (PDT)
Sender: Enrico Francesconi <enrico.francesconi@gmail.com>
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.0 \(3094\))
From: Enrico Francesconi <francesconi@ittig.cnr.it>
In-Reply-To: <87zi9sedst.fsf@hobgoblin.ariadne.com>
Date: Wed, 20 Sep 2017 19:55:52 +0200
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, draft-spinosa-urn-lex.all@ietf.org,  gen-art@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <42ECF75A-E097-4AD8-9B48-7D680003AEB8@ittig.cnr.it>
References: <87zi9sedst.fsf@hobgoblin.ariadne.com>
To: "Dale R. Worley" <worley@ariadne.com>
X-Mailer: Apple Mail (2.3094)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/ehRdK2FuaVn3TDLl00jl-FIloiA>
X-Mailman-Approved-At: Wed, 20 Sep 2017 12:48:56 -0700
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-spinosa-urn-lex-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Sep 2017 17:55:59 -0000

Dear Dale,
  thanks for your remarks. As they are very sensitive in the on-going =
discussion, we send you and the other reviewers some considerations =
about them, in order to clarify our approach in the URN:LEX proposal.=20

URN:LEX has been conceived to cope with two main objectives:
- sources of law identification
- facilitate sources of law accessibility from references usually =
present in different types of documents (other sources of law =
(legislation, case law or administrative acts) was well as newspapers, =
legal doctrine, etc.)

In this respect the URN:LEX proposal distinguishes two aspects:

1) sources of law URNs creation and attribution
	a) always complete and unequivocal;
	b) generated through a complex set of metadata, which =
nevertheless is able to guarantee uniqueness of document identification =
(among versions, languages, formats, within a federated system =
characterized by different issuing authorities and publishers)
	c) assigned by an issuing authority or publisher

2) sources of law references
They can be present in any document, even non legal.=20
Legal references are often incomplete or inaccurate, therefore the URN =
derived from a reference will be incomplete as well, either generated by =
a human or by a software tool (a parser).
Since the aim of the approach is to facilitate document retrieval, an =
intelligent resolver can use the derived, even incomplete, URN to =
retrieve the best matching documents. Then, the user will be able to =
choose, among the results, the document matching his requirements.
This mechanism exploits the possibility to detect metadata within a =
textual reference expressed in natural language and create an even =
incomplete URN, rather than forcing a user to search for the exact URN =
within an remote database.

In the legal domain the access to the last version of a law is typically =
required. Since the information expressed in references correspond =
usually to metadata at the FRBR Work level, the URN that can be derived =
is not complete (it lacks information at Expression and Manifestation =
levels; ex: Regulation (EU) No 1308/2013 of the European Parliament and =
of the Council of 17 December 2013).

Moreover, a part from references expressing amending actions which are =
typically static (they make reference to a specific version of a target =
act or partition at the moment of their modification), legal references =
are typically dynamic (they make reference to the version of the target =
act or partition =E2=80=9Cin-force=E2=80=9D today). Therefore, =
describing a reference by a complete URN is wrong even from a conceptual =
point of view.

An effective URN resolver has to be able to provide all the URNs at Work =
level matching the incomplete one derived from the reference.
Then, the user can choose the desired URN and the resolver can provide =
the different versions associated to that Work (in case highlighting the =
=E2=80=9Cin-force=E2=80=9D version). Then, chosen a version, the =
resolver can provide all the possible manifestations among which the =
user can choose the required document.
Such resolver behavior is actually made easy by the hierarchical =
structure of URN:LEX (work, expression and manifestation levels clearly =
separated by @ and $ characters).

In the URN-LEX proposal we followed such principles, with the aim to =
distinguish between these two aspects (sources of law naming and sources =
of law referencing). Obviously we are available to modify the URN:LEX =
draft so that these principles can be more clear.

We are also analyzing the other remarks of the reviewers; shortly we =
will send you some proposals to solve the issues raised.=20

Thanks!
Best regards
  Pierluigi and Enrico


---------------------------------------------------------
Enrico Francesconi
ITTIG - CNR
Institute of Legal Information Theory and Techniques
Italian National Research Council

Via de' Barucci 20
50127 Florence
Italy

Tel: +39-055-4399-665
Fax: +39-055-4399-605
email: francesconi@ittig.cnr.it
---------------------------------------------------------

> On 18 set 2017, at 08:11, Dale R. Worley <worley@ariadne.com> wrote:
>=20
> Let me speak in favor of draft-spinosa-urn-lex.
>=20
> My understanding of the intention of the draft is essentially the
> creation of a universal system for bibliographic citations of legal
> works, using the syntax of URNs to express the citations.  This
> understanding colors how I think about the namespace proposal.
>=20
> The intention seems to be that every document is assigned one or more
> URNs by a governing jurisdiction, or by a publisher of a version of =
the
> document.  Note a point that I did not understand until recently, that
> the uniqueness rule for URNs permits multiple URNs to refer to one =
same
> resource.  As the authors note, one use of this is providing =
references
> to a document which are based on multiple natural languages.
>=20
> The resolution process for assigned URNs is a typical indirection
> system, where the URN is looked up in a database.  However, the system
> supports a usage that is much more like other library or bibliographic
> systems -- the user can compose the information that he knows about =
the
> document into an "approximate" URN which can be searched for in a
> database using a "closest match" rule, which both converts the queried
> URN into an assigned URN and provides information about the document
> itself.  In this usage, the user-composed URNs are fundamentally
> equivalent to queries.
>=20
> The current draft does not clearly separate the information about the
> query/resolution process.  It would be helpful if the resolution
> information were in a separate section, as the registration template
> format in RFC 8141 recommends.  It would also be helpful if there was =
a
> clear distinction between the parts of the resolution process that are
> well-defined and fixed, and (IIRC) some information which has not been
> firmly fixed.
>=20
> However, the messy part is the user-created "query" URNs.  To get =
these
> within the formal rules for URN namespaces, we need to recognize them =
as
> a special subclass whose definition does not come from assignment to a
> document by an authority, but rather from the namespace definition
> itself, in a clause somewhat like:
>=20
>    A URN that is not assigned to a document is defined to represent a
>    query into the universe of URNs that have been assigned to
>    documents, whose resolution is current set of assigned URNs that
>    most closely match the URN.
>=20
> Clearly, there are some rough edges to that.  But the meaning of a URN
> is time-invariant as a query, despite that the results of the query
> depend on the time.  And when a URN is assigned to a document, the URN
> is equivalently a query that returns just that one document (since it =
is
> a perfect match to itself as an assigned URN).
>=20
> Some of this reasoning is a stretch, but (a) I've written URN =
definitions
> that aren't perfectly compatible with RFC 8141, and (b) this pattern =
of
> definition and usage seems to be ideal for handling bibliographic
> references.
>=20
> So I think the overall concept is good and useful, though the
> presentation needs to be cleaned up in the ways that we've been
> discussing.
>=20
> Dale


From nobody Wed Sep 20 15:45:55 2017
Return-Path: <David.Black@dell.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B348D13433D; Wed, 20 Sep 2017 15:45:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.001
X-Spam-Level: 
X-Spam-Status: No, score=-5.001 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_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dell.com header.b=aO4pRPkQ; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=emc.com header.b=OtCsTiXK
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 6bS1vAnEM7nV; Wed, 20 Sep 2017 15:45:43 -0700 (PDT)
Received: from esa1.dell-outbound.iphmx.com (esa1.dell-outbound.iphmx.com [68.232.153.90]) (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 28584134300; Wed, 20 Sep 2017 15:45:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dell.com; i=@dell.com; q=dns/txt; s=smtpout; t=1505947388; x=1537483388; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=+WyOzOfyo8dWQ2rYgIwHCfc8UKMwgyiZj4y81Phs/k8=; b=aO4pRPkQT/pNvqewJR2APi9gaskBw8LdP5K4Kg8aNqkxcHFBl2RQBonn j7NDrGmLTb8zpDWkfjxzVNoyNj9nKf7ExDg8kKcHkkgcDOag9ep22HSCL pUSAGeosgk134JbHIudsiDhBGFUKTDMiCn+TLMEqxPsRwA5n2R9T+iiI9 I=;
Received: from esa5.dell-outbound2.iphmx.com ([68.232.153.203]) by esa1.dell-outbound.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Sep 2017 17:43:07 -0500
From: "Black, David" <David.Black@dell.com>
Received: from mailuogwdur.emc.com ([128.221.224.79]) by esa5.dell-outbound2.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Sep 2017 04:36:29 +0600
Received: from maildlpprd55.lss.emc.com (maildlpprd55.lss.emc.com [10.106.48.159]) by mailuogwprd54.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id v8KMjZfY025488 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 20 Sep 2017 18:45:40 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com v8KMjZfY025488
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1505947540; bh=X95SPHqFzN8+HYMWVaTZSXIACzY=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=OtCsTiXKqZbajYj6cZW0YKX2oYCgsazVPV6P/w0v5tSP56zePv+S7XzWEuuM9kZoo FkDy8W+ZJS1ifPQWHiq7Ujbr6gyYJ/jtJbNnrM89BuY8bmTr+JfPZXKrw0P44IHxXX 3VGr08LgFfY2V650GmhpevUuu5XJTxmGVlZPExVk=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com v8KMjZfY025488
Received: from mailusrhubprd02.lss.emc.com (mailusrhubprd02.lss.emc.com [10.253.24.20]) by maildlpprd55.lss.emc.com (RSA Interceptor); Wed, 20 Sep 2017 18:44:40 -0400
Received: from MXHUB309.corp.emc.com (MXHUB309.corp.emc.com [10.146.3.35]) by mailusrhubprd02.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id v8KMjEQ8024949 (version=TLSv1.2 cipher=AES128-SHA256 bits=128 verify=FAIL); Wed, 20 Sep 2017 18:45:14 -0400
Received: from MX307CL04.corp.emc.com ([fe80::849f:5da2:11b:4385]) by MXHUB309.corp.emc.com ([10.146.3.35]) with mapi id 14.03.0352.000; Wed, 20 Sep 2017 18:45:14 -0400
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-tsvwg-ecn-experimentation.all@ietf.org" <draft-ietf-tsvwg-ecn-experimentation.all@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: Genart telechat review of draft-ietf-tsvwg-ecn-experimentation-05
Thread-Index: AQHTIsZAf8GsSgkmu0q70NA4hkw3sKKgjxdggABmDoCAHYckYA==
Date: Wed, 20 Sep 2017 22:45:13 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949362FC628DA@MX307CL04.corp.emc.com>
References: <150423129417.4604.2689843099266054478@ietfa.amsl.com> <CE03DB3D7B45C245BCA0D243277949362FC30A29@MX307CL04.corp.emc.com> <6afe85ba-83c5-5945-fd37-dc313eb22162@gmail.com>
In-Reply-To: <6afe85ba-83c5-5945-fd37-dc313eb22162@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.105.8.135]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd02.lss.emc.com
X-RSA-Classifications: public
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/p01A7nfQdLeJXncg04lIaOWmcPQ>
Subject: Re: [Gen-art] Genart telechat review of draft-ietf-tsvwg-ecn-experimentation-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Sep 2017 22:45:46 -0000

QnJpYW4sDQoNCkknbSBhYm91dCB0byBwb3N0IHRoZSAtMDYgdmVyc2lvbiBvZiB0aGlzIGRyYWZ0
LiAgIFRoZSBjb25jZXJuIG9uIFJGQyAzMTY4IGltcGFjdCBvZiB0aGUgRUNOIG5vbmNlIHJlbW92
YWwgd2FzIHJlc29sdmVkIGJ5IGxpc3RpbmcgdGhlIGZvdXIgbWFqb3IgY2hhbmdlcyAoYW5kIHlv
dSB3ZXJlIGNvcnJlY3QgdGhhdCB0aGUgY2hhbmdlIHRvIFNlY3Rpb24gMjAuMiBpcyBzdWJ0bGUg
LSBJIGdvdCBpdCB3cm9uZyBvbiBteSBmaXJzdCBhdHRlbXB0IGluIHJlc3BvbmRpbmcgdG8geW91
ciBlbWFpbCkuICBIZXJlJ3MgdGhlIHNwZWNpZmljIHRleHQgdGhhdCBJJ3ZlIGFkZGVkIHRvIFNl
Y3Rpb24gMyBvZiB0aGUgZHJhZnQ6DQoNCiAgIFRoZSBmb3VyIHByaW1hcnkgdXBkYXRlcyB0byBS
RkMgMzE2OCB0aGF0IHJlbW92ZSBkaXNjdXNzaW9uIG9mIHRoZQ0KICAgRUNOIG5vbmNlIGFuZCB1
c2Ugb2YgRUNUKDEpIGZvciB0aGF0IG5vbmNlIGFyZToNCg0KICAgMS4gIFJlbW92ZSB0aGUgcGFy
YWdyYXBoIGluIFNlY3Rpb24gNSB0aGF0IGltbWVkaWF0ZWx5IGZvbGxvd3MNCiAgICAgICBGaWd1
cmUgMTsgdGhpcyBwYXJhZ3JhcGggZGlzY3Vzc2VzIHRoZSBFQ04gbm9uY2UgYXMgdGhlDQogICAg
ICAgbW90aXZhdGlvbiBmb3IgdHdvIEVDVCBjb2RlcG9pbnRzLg0KDQogICAyLiAgUmVtb3ZlIFNl
Y3Rpb24gMTEuMiAiQSBEaXNjdXNzaW9uIG9mIHRoZSBFQ04gbm9uY2UuIiBpbiBpdHMNCiAgICAg
ICBlbnRpcmV0eS4NCg0KICAgMy4gIFJlbW92ZSB0aGUgbGFzdCBwYXJhZ3JhcGggb2YgU2VjdGlv
biAxMiwgd2hpY2ggc3RhdGVzIHRoYXQgRUNUKDEpDQogICAgICAgbWF5IGJlIHVzZWQgYXMgcGFy
dCBvZiB0aGUgaW1wbGVtZW50YXRpb24gb2YgdGhlIEVDTiBub25jZS4NCg0KICAgNC4gIFJlbW92
ZSB0aGUgZmlyc3QgdHdvIHBhcmFncmFwaHMgb2YgU2VjdGlvbiAyMC4yLCB3aGljaCBkaXNjdXNz
DQogICAgICAgdGhlIEVDTiBub25jZSBhbmQgYWx0ZXJuYXRpdmVzLiAgTm8gY2hhbmdlcyBhcmUg
bWFkZSB0byB0aGUgcmVzdA0KICAgICAgIG9mIFNlY3Rpb24gMjAuMiwgd2hpY2ggZGlzY3Vzc2Vz
IGFsdGVybmF0ZSB1c2VzIGZvciB0aGUgZm91cnRoDQogICAgICAgRUNOIGNvZGVwb2ludC4NCg0K
ICAgQWRkaXRpb25hbCBtaW5vciBjaGFuZ2VzIHJlbW92ZSBvdGhlciBtZW50aW9ucyBvZiB0aGUg
RUNOIG5vbmNlIGFuZA0KICAgaW1wbGljYXRpb25zIHRoYXQgRUNUKDEpIGlzIGludGVuZGVkIGZv
ciB1c2UgYnkgdGhlIEVDTiBub25jZTsgdGhlDQogICBzcGVjaWZpYyB0ZXh0IHVwZGF0ZXMgYXJl
IG9taXR0ZWQgZm9yIGJyZXZpdHkuDQoNClRoZSBwcm92ZXJiaWFsICJyZXN0IG9mIHRoZSBzdG9y
eSIgaXMgdGhhdCBhbiBSRkMgMzE2OGJpcyBlZmZvcnQgYXBwZWFycyB0byBiZSBhIGdvb2QgaWRl
YSwgZS5nLiwgYXMgUkZDIDYwNDAgaGFzIGFscmVhZHkgbWFkZSBzb21lIHZpc2libGUgY2hhbmdl
cy4gVGhlIHByZWZlcnJlZCAzMTY4YmlzIHRpbWluZyBhcHBlYXJzIHRvIGJlIGFmdGVyIHdlIHVu
ZGVyc3RhbmQgdGhlIG91dGNvbWVzIG9mIHRoZSBjdXJyZW50IHByb3Bvc2VkIG9mIGV4cGVyaW1l
bnRzLCBhcyB0aGV5J3JlIGxpa2VseSB0byByZXN1bHQgaW4gYW5vdGhlciByb3VuZCBvZiBjaGFu
Z2VzIHRvIFJGQyAzMTY4Lg0KDQpNYW55IHRoYW5rcywgYW5kIGNoYWxrIHRoaXMgdXAgYXMgb25l
IG1vcmUgaW5zdGFuY2Ugd2hlcmUgYSBHZW5BUlQgcmV2aWV3IGhhcyB2aXNpYmx5IGltcHJvdmVk
IHRoZSBxdWFsaXR5IG9mIGEgZHJhZnQsICAtLURhdmlkDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0NCj4gRnJvbTogQnJpYW4gRSBDYXJwZW50ZXIgW21haWx0bzpicmlhbi5lLmNhcnBl
bnRlckBnbWFpbC5jb21dDQo+IFNlbnQ6IEZyaWRheSwgU2VwdGVtYmVyIDEsIDIwMTcgNzo0MSBQ
TQ0KPiBUbzogQmxhY2ssIERhdmlkIDxkYXZpZC5ibGFja0BlbWMuY29tPjsgZ2VuLWFydEBpZXRm
Lm9yZw0KPiBDYzogZHJhZnQtaWV0Zi10c3Z3Zy1lY24tZXhwZXJpbWVudGF0aW9uLmFsbEBpZXRm
Lm9yZzsgdHN2d2dAaWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6IEdlbmFydCB0ZWxlY2hhdCByZXZp
ZXcgb2YgZHJhZnQtaWV0Zi10c3Z3Zy1lY24tDQo+IGV4cGVyaW1lbnRhdGlvbi0wNQ0KPiANCj4g
T24gMDIvMDkvMjAxNyAwOTo0NSwgQmxhY2ssIERhdmlkIHdyb3RlOg0KPiA+IEJyaWFuLA0KPiA+
DQo+ID4gVGhhbmtzIGZvciB0aGUgcHJvbXB0IHJldmlldy4NCj4gPg0KPiA+PiBDb21tZW50OiBW
ZXJ5IGNsZWFyIGZyb20gdGhlIHRlY2huaWNhbCBzdGFuZHBvaW50Lg0KPiA+DQo+ID4gVGhhbmsg
eW91IQ0KPiA+DQo+ID4+IEkgdW5kZXJzdGFuZCB0aGUgZGVzaXJlIGZvciBicmV2aXR5LCBidXQg
dGhpcyBib3RoZXJzIG1lIGEgYml0LiBXaGF0IGlzDQo+ID4+IHRoZSByZWFkZXIgdG8gbWFrZSBv
ZiBSRkMzMTY4IFNlY3Rpb24gMjAuMiwgZm9yIGV4YW1wbGU/IE15IGZlZWxpbmcgaXMNCj4gPj4g
dGhhdCBhIHNob3J0IEFwcGVuZGl4IG91dGxpbmluZyB0aGUgc3BlY2lmaWMgdXBkYXRlcyB3b3Vs
ZCBiZSB1c2VmdWwuDQo+ID4+IFRoZXJlJ3MgYWxyZWFkeSB0b28gbXVjaCBzcGFnaGV0dGkgdG8g
dW50YW5nbGUuDQo+ID4NCj4gPiBSRkMgMzE2OCBTZWN0aW9uIDIwLjIgaXMgdGhlIHJhdGlvbmFs
ZSBmb3IgdGhlIEVDTiBOb25jZSBhbmQgaGVuY2Ugd291bGQNCj4gYmUNCj4gPiBkZWxldGVkLiBS
ZXF1ZXN0IG5vdGVkLCBJJ2xsIGNvbnN1bHQgd2l0aCB0aGUgZHJhZnQgc2hlcGhlcmQgYW5kDQo+
IHJlc3BvbnNpYmxlDQo+ID4gQUQgdG8gZmlndXJlIG91dCB3aGV0aGVyIHRvIGRvIHRoaXMuDQo+
IA0KPiBUaGFua3MuIEl0J3Mgbm90IGludGVuZGVkIGFzIGEgYmxvY2tpbmcgaXNzdWUuDQo+IA0K
PiA+DQo+ID4+IEkgc2VlIG5vIHJlYXNvbiB3aHkgUkZDMzU0MCBhbmQgUkZDNTYyMiBuZWVkIHRv
IGJlIG5vcm1hdGl2ZQ0KPiByZWZlcmVuY2VzDQo+ID4+IChhbmQgdGhlcmVmb3JlIGRvd25yZWZz
KS4gVGhleSBhcmVuJ3QgcmVxdWlyZWQgcmVhZGluZyBpbiBvcmRlciB0bw0KPiA+PiB1bmRlcnN0
YW5kIHRoaXMgZHJhZnQuDQo+ID4NCj4gPiBPVE9ILCBib3RoIGFyZSBhZmZlY3RlZCBieSB0aGlz
IGRyYWZ0Og0KPiA+DQo+ID4gSW4gcmV2ZXJzZSBvcmRlciwgdGhpcyBkcmFmdCB1cGRhdGVzIFJG
QyA1NjIyIC0gdGhhdCBzZWVtcyB0byBtZXJpdCBhDQo+ID4gbm9ybWF0aXZlIHJlZmVyZW5jZS4g
ICAgVGhpcyBkcmFmdCBhbHNvIHByb3ZpZGVzIHRoZSByYXRpb25hbGUgZm9yIHRoZQ0KPiA+IHN0
YXR1cyBjaGFuZ2Ugb2YgUkZDIDM1NDAgdG8gSGlzdG9yaWMsIHdoaWNoIGFsc28gc2VlbXMgdG8g
bWVyaXQgYQ0KPiA+IG5vcm1hdGl2ZSByZWZlcmVuY2UuDQo+IA0KPiBXZWxsLCBteSB1bmRlcnN0
YW5kaW5nIGlzIHRoYXQgYSBub3JtYXRpdmUgcmVmZXJlbmNlIGlzIG5lZWRlZCBvbmx5DQo+IHdo
ZW4gdGhlIGNpdGluZyBkb2N1bWVudCBjYW5ub3QgYmUgdW5kZXJzdG9vZCBhbmQgaW1wbGVtZW50
ZWQNCj4gd2l0aG91dCByZWFkaW5nIHRoZSBjaXRlZCBkb2N1bWVudC4NCj4gDQo+IEFnYWluIGl0
J3Mgbm90IGEgYmxvY2tpbmcgY29tbWVudCAtIGFsdGhvdWdoIHRoZXJlIGlzIGEgdGVjaG5pY2Fs
IGVycm9yDQo+IGluIHRoZSBMYXN0IENhbGwgbWVzc2FnZTogaXQgZmxhZ3MgdGhlIGRvd25yZWYg
dG8gNTYyMiwgYnV0IG5vdCB0aGF0IHRvIDM1NDAuDQo+IEkgZG9uJ3Qga25vdyBpZiB0aGF0J3Mg
YSB0b29sIGVycm9yIG9yIGFuIEFEIGVycm9yIDstKS4NCj4gDQo+ICAgICBCcmlhbg0KPiANCj4g
Pg0KPiA+IFRoYW5rcywgLS1EYXZpZA0KPiA+DQo+ID4NCj4gPj4gLS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0NCj4gPj4gRnJvbTogQnJpYW4gQ2FycGVudGVyIFttYWlsdG86YnJpYW4uZS5jYXJw
ZW50ZXJAZ21haWwuY29tXQ0KPiA+PiBTZW50OiBUaHVyc2RheSwgQXVndXN0IDMxLCAyMDE3IDEw
OjAyIFBNDQo+ID4+IFRvOiBnZW4tYXJ0QGlldGYub3JnDQo+ID4+IENjOiBkcmFmdC1pZXRmLXRz
dndnLWVjbi1leHBlcmltZW50YXRpb24uYWxsQGlldGYub3JnOyB0c3Z3Z0BpZXRmLm9yZw0KPiA+
PiBTdWJqZWN0OiBHZW5hcnQgdGVsZWNoYXQgcmV2aWV3IG9mIGRyYWZ0LWlldGYtdHN2d2ctZWNu
LWV4cGVyaW1lbnRhdGlvbi0NCj4gMDUNCj4gPj4NCj4gPj4gUmV2aWV3ZXI6IEJyaWFuIENhcnBl
bnRlcg0KPiA+PiBSZXZpZXcgcmVzdWx0OiBSZWFkeSB3aXRoIElzc3Vlcw0KPiA+Pg0KPiA+PiBH
ZW4tQVJUIExhc3QgQ2FsbCByZXZpZXcgb2YgZHJhZnQtaWV0Zi10c3Z3Zy1lY24tZXhwZXJpbWVu
dGF0aW9uLTA1DQo+ID4+DQo+ID4+IEkgYW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIg
Zm9yIHRoaXMgZHJhZnQuIFRoZSBHZW5lcmFsIEFyZWENCj4gPj4gUmV2aWV3IFRlYW0gKEdlbi1B
UlQpIHJldmlld3MgYWxsIElFVEYgZG9jdW1lbnRzIGJlaW5nIHByb2Nlc3NlZA0KPiA+PiBieSB0
aGUgSUVTRyBmb3IgdGhlIElFVEYgQ2hhaXIuICBQbGVhc2UgdHJlYXQgdGhlc2UgY29tbWVudHMg
anVzdA0KPiA+PiBsaWtlIGFueSBvdGhlciBsYXN0IGNhbGwgY29tbWVudHMuDQo+ID4+DQo+ID4+
IEZvciBtb3JlIGluZm9ybWF0aW9uLCBwbGVhc2Ugc2VlIHRoZSBGQVEgYXQNCj4gPj4gPGh0dHA6
Ly93aWtpLnRvb2xzLmlldGYub3JnL2FyZWEvZ2VuL3RyYWMvd2lraS9HZW5BcnRmYXE+Lg0KPiA+
Pg0KPiA+PiBEb2N1bWVudDogZHJhZnQtaWV0Zi10c3Z3Zy1lY24tZXhwZXJpbWVudGF0aW9uLTA1
LnR4dA0KPiA+PiBSZXZpZXdlcjogQnJpYW4gQ2FycGVudGVyDQo+ID4+IFJldmlldyBEYXRlOiAy
MDE3LTA5LTAxDQo+ID4+IElFVEYgTEMgRW5kIERhdGU6IDIwMTctMDktMTQNCj4gPj4gSUVTRyBU
ZWxlY2hhdCBkYXRlOiAyMDE3LTA5LTE0DQo+ID4+DQo+ID4+IFN1bW1hcnk6IFJlYWR5IHdpdGgg
KG1pbm9yKSBpc3N1ZXMNCj4gPj4gLS0tLS0tLS0NCj4gPj4NCj4gPj4gQ29tbWVudDogVmVyeSBj
bGVhciBmcm9tIHRoZSB0ZWNobmljYWwgc3RhbmRwb2ludC4NCj4gPj4gLS0tLS0tLS0NCj4gPj4N
Cj4gPj4gTWlub3IgSXNzdWVzOg0KPiA+PiAtLS0tLS0tLS0tLS0tDQo+ID4+DQo+ID4+PiAzLiAg
RUNOIE5vbmNlIGFuZCBSRkMgMzU0MA0KPiA+PiAuLi4NCj4gPj4+IG8gIFVwZGF0ZXMgUkZDIDMx
NjggW1JGQzMxNjhdIHRvIHJlbW92ZSBkaXNjdXNzaW9uIG9mIHRoZSBFQ04gTm9uY2UNCj4gPj4+
ICAgIGFuZCB1c2Ugb2YgRUNUKDEpIGZvciB0aGF0IE5vbmNlLiAgVGhlIHNwZWNpZmljIHRleHQg
dXBkYXRlcyBhcmUNCj4gPj4+ICAgIG9taXR0ZWQgZm9yIGJyZXZpdHkuDQo+ID4+DQo+ID4+IEkg
dW5kZXJzdGFuZCB0aGUgZGVzaXJlIGZvciBicmV2aXR5LCBidXQgdGhpcyBib3RoZXJzIG1lIGEg
Yml0LiBXaGF0IGlzDQo+ID4+IHRoZSByZWFkZXIgdG8gbWFrZSBvZiBSRkMzMTY4IFNlY3Rpb24g
MjAuMiwgZm9yIGV4YW1wbGU/IE15IGZlZWxpbmcgaXMNCj4gPj4gdGhhdCBhIHNob3J0IEFwcGVu
ZGl4IG91dGxpbmluZyB0aGUgc3BlY2lmaWMgdXBkYXRlcyB3b3VsZCBiZSB1c2VmdWwuDQo+ID4+
IFRoZXJlJ3MgYWxyZWFkeSB0b28gbXVjaCBzcGFnaGV0dGkgdG8gdW50YW5nbGUuDQo+ID4+DQo+
ID4+IEkgc2VlIG5vIHJlYXNvbiB3aHkgUkZDMzU0MCBhbmQgUkZDNTYyMiBuZWVkIHRvIGJlIG5v
cm1hdGl2ZQ0KPiByZWZlcmVuY2VzDQo+ID4+IChhbmQgdGhlcmVmb3JlIGRvd25yZWZzKS4gVGhl
eSBhcmVuJ3QgcmVxdWlyZWQgcmVhZGluZyBpbiBvcmRlciB0bw0KPiA+PiB1bmRlcnN0YW5kIHRo
aXMgZHJhZnQuDQo+ID4+DQo+ID4+IC0tDQo+ID4NCg==


From nobody Wed Sep 20 17:14:00 2017
Return-Path: <grizz@20c.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A0AF1321BB for <gen-art@ietfa.amsl.com>; Wed, 20 Sep 2017 17:13:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=20c-com.20150623.gappssmtp.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 4b0j915KTgeF for <gen-art@ietfa.amsl.com>; Wed, 20 Sep 2017 17:13:56 -0700 (PDT)
Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 770AA13209C for <gen-art@ietf.org>; Wed, 20 Sep 2017 17:13:56 -0700 (PDT)
Received: by mail-it0-x22a.google.com with SMTP id r131so3546422itc.1 for <gen-art@ietf.org>; Wed, 20 Sep 2017 17:13:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=20c-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=7SzDpcE+iE8X9sHsZeJRlOvg0xO5+9Zwx5kvjSQGcUM=; b=lcFfXLYHq19mZHihvnq0RL7gMgi6WNEuHR+SoSWp7VMjIryJUhGmJ2/fTBbhdTB1Ao /ru9EfTKAFl7rdcmhjIRGtSpUfkkEDCQlSkrnQbMPHvq4SBebuQpp/IFKafr6roERh3q 8jKNtezb7iCsnswJTdec0YCtWHMKhaJ+VQJhHvssP6olaKBeEx2RhHpn+W7NL0SSLXkm oHpfXGJ1eMrkz31XYnsyWIQk/dT4w9zQISjY/vqxy7eEJPEx7F42xqNYPrupltgMHNjr Pa+t/OT9fM/VAiMJqKtzCjr6FdF3FExl4HgMuHzMoXLd1tR3I6DVnl2S5WYckvcZiWOC Gmxw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=7SzDpcE+iE8X9sHsZeJRlOvg0xO5+9Zwx5kvjSQGcUM=; b=nBaaZxGtY5brrtgRbxSiVrVQbtrZL3H/LSomy2Cj2NX5azU9WmCzvttpixEBNEqsce eFwS6TmK6tQTmE1v71SdwwHU67M2zWj65uUZkp9KV6o2dloZSuP5ZzqrEvWC1IgXyfKo 8Ysc/gD1xMm4vN8doNkZijOgp/ryhGf1hNIMekyNAQCSUpr1pCVEU1ltEJfj8i1e+W7h lXKafrE+JRGEhH4o+w9dWcEj2ze8Z/rYQy5ZnLTDF0/1snvbnCfTmagc9CkGL+BCSvWq Wy3aKJ0Ul/G95nGA0X9nSFEVv2mDS6BYqN3PvMana2OAJd3WgexyK8NUuedDz4RmsFAk aTRg==
X-Gm-Message-State: AHPjjUjFvJ3yVL7QKmM1f/N/ix/1yx5KqpGB77PiYuopgByJe6oj5kuC KLtmU0hWJq13EQgR1tfuZbZf4Q==
X-Google-Smtp-Source: AOwi7QDl1x1+St/yjb6ux68GUCrUcJg98PF/kAww6MKr+FTb+ZAEgzwD0UF0n/5tfQfxCJpYFJi7Kw==
X-Received: by 10.36.84.82 with SMTP id t79mr5769018ita.98.1505952835688; Wed, 20 Sep 2017 17:13:55 -0700 (PDT)
Received: from x0r (97-83-204-249.dhcp.eucl.wi.charter.com. [97.83.204.249]) by smtp.gmail.com with ESMTPSA id n67sm75751ion.64.2017.09.20.17.13.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Sep 2017 17:13:54 -0700 (PDT)
Date: Thu, 21 Sep 2017 00:13:53 +0000
From: Matt Griswold <grizz@20c.com>
To: Brian Carpenter <brian.e.carpenter@gmail.com>
Cc: <gen-art@ietf.org>, grow@ietf.org, draft-ietf-grow-bgp-session-culling.all@ietf.org
Message-ID: <20170921001353.260a3439@x0r>
In-Reply-To: <150579629891.15651.17244647188709040958@ietfa.amsl.com>
References: <150579629891.15651.17244647188709040958@ietfa.amsl.com>
X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.28; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/LNevqMVPqD0gPuYZEsFn5owIh6k>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-grow-bgp-session-culling-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 00:13:58 -0000

* Brian Carpenter <brian.e.carpenter@gmail.com> [170918 21:44 -0700]:
> Minor Issues:
> -------------
> 
> > 3.1.1.  Maintenance Considerations
> >
> >  Initiators of the administrative shutdown could consider using
> >  Graceful Shutdown [I-D.ietf-grow-bgp-gshut] to facilitate smooth
> >  drainage of traffic prior to session tear down, and the Shutdown
> >  Communication [I-D.ietf-idr-shutdown]...  
> 
> This strikes me as vague. "Could consider"? Surely if this is
> a BCP, they MUST use some mechanisms and perhaps SHOULD use these
> particular mechanisms. Otherwise the document doesn't specify
> anything much at all for this case.

Graceful Shutdown is just one of multiple ways an Operator can
accomplish that.

> > 3.2.  Involuntary BGP Session Teardown Recommendations  
> ...
> >  In the absence notifications from the lower layer (e.g. ethernet
> >   link down) consistent with the planned maintenance activities in a
> >  switched layer-2 fabric, the Caretaker of the fabric could choose
> >   to cull BGP sessions on behalf of the Operators connected to the
> >   fabric.  
> 
> This seems incomplete. Firstly, I'm assuming that it should start
> "In the absence of notifications...".

Fixed!

> Secondly, if there are no fault indications, what causes the
> Caretaker to cull sessions? What's the trigger? Is the Caretaker
> supposed to know by magic that layer 2 maintenance is planned?

The Caretaker controls the layer 2 network, so yes, would do this as
part of the maintenance process.

> ...
> >  In this scenario, BGP Session Culling is accomplished through the
> >  application of a combined layer-3 and layer-4 packet filter
> >   deployed in the switched fabric itself.  
> 
> Please add "as described in the next sub-section" because otherwise
> the reader can easily be confused.

Added.

> > 3.2.1.  Packet Filter Considerations
> >
> >  The following considerations apply to the packet filter design:
> >
> >  o  The packet filter MUST only affect BGP traffic specific to the
> >     layer-2 fabric, i.e. forming part of the control plane of the
> >     system described, rather than multihop BGP traffic which merely
> >     transits  
> 
> That's a goal, but it doesn't tell me how to achieve the goal.
> What packet signature tells me which packets are specific to the
> fabric? I suspect this might overlap with the last bullet - if so,
> you might consider re-ordering the bullets.
> ...
> >  o  The packet filter MUST affect all relevant Address Family
> >     Identifiers  
> 
> Define "relevant".

Removed "relevant".

> And in Appendix A, explain precisely how the example prefixes are
> used: what makes them relevant? Are they normally announced by BGP to
> all the IXP's BGP peers?

They are the IXP LAN addresses, as explained above the examples.

Thanks for your review!


From nobody Wed Sep 20 19:03:30 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D6581320DC; Wed, 20 Sep 2017 19:03:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 d4G3HZiQaGRh; Wed, 20 Sep 2017 19:03:27 -0700 (PDT)
Received: from mail-pg0-x22f.google.com (mail-pg0-x22f.google.com [IPv6:2607:f8b0:400e:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CAC21252BA; Wed, 20 Sep 2017 19:03:27 -0700 (PDT)
Received: by mail-pg0-x22f.google.com with SMTP id b11so2702389pgn.12; Wed, 20 Sep 2017 19:03:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=0XnJndgfewHE3yVyAxePqpTE8GN/GmGNZNIjcxBDWgw=; b=LHYS9ylDWjL/ln7niCGJDUYV/o9r5aonJO0JoLhdWN+0AEKrMY0aWjoNjdsy1KZCjB PvMxprb6u9IBfEqfj68Co6cjicqDdymq3eQJdPDx+/vd4KkvUjPLiL6gZaQMFpbFNgPu U5Mh5f0tVhVU+AuIhOHBgrP8opfuzFWKmbw9X+Tlfb0Wv1v40hLpi0Ek1cuwupa+qOXI Qy9yfvPKRvBKBPSFrePSyqs+FRftO/pFhi3kEU93sc97ajlwkv3xwOvDGoeZHstupGXJ LcaXyytmxUdcXMV55bOT+l8lcNYw9cNK7rv3um2zuNfuukFWnllZa2+oFQ0M9A0au8qr 7ZVg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=0XnJndgfewHE3yVyAxePqpTE8GN/GmGNZNIjcxBDWgw=; b=Q9/iF8tX3e+chS7QttWQbXSqumRv875S0I4qnJJI0WGUOVP/vSlTUrwB1ro0SLm/w6 oUMNwiGTAZHTCeoIx728Aiwm1xpj3pL/jl7OKVgu1hzsKJWpTY0x9K3aZiwvlJWfrAYx YUAkrTth2w78O2UUYj0jRGayQxEICYRs41dDROIKjHslAvxWjrXgz3MEgZiJmo/SUuo8 IG8vEDxLZqieHTwmzke27XgFYxXdlgGmZ9ovWDmp1+YwdvlERHAKvTPCp7FHAjyE529s I9XFXbRBCZgZ+450tkVR1mJx8OHgQPFkk/ZNJK11HJCjpiczwyT7VeDbsFyxMMFAt/Xi tucQ==
X-Gm-Message-State: AHPjjUjCmd3CDAiPF34hSTMEMTfIXzxiI38XmNgMamUHkPrCUNUSWPBn 9nE0V2mFlQIzAplnkC7V9iBgTA==
X-Google-Smtp-Source: AOwi7QA7QGP4WflYvQDPah0Nuacm6TfsEgPfguRVLo25F/fVB7PS3qLmGLvIPNlucHTvKmRkOfp3Bg==
X-Received: by 10.99.180.65 with SMTP id n1mr4164977pgu.313.1505959404851; Wed, 20 Sep 2017 19:03:24 -0700 (PDT)
Received: from ?IPv6:2406:e001:3f51:1:28cc:dc4c:9703:6781? ([2406:e001:3f51:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id s76sm308990pfj.119.2017.09.20.19.03.21 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Sep 2017 19:03:23 -0700 (PDT)
To: "Black, David" <David.Black@dell.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Cc: "draft-ietf-tsvwg-ecn-experimentation.all@ietf.org" <draft-ietf-tsvwg-ecn-experimentation.all@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
References: <150423129417.4604.2689843099266054478@ietfa.amsl.com> <CE03DB3D7B45C245BCA0D243277949362FC30A29@MX307CL04.corp.emc.com> <6afe85ba-83c5-5945-fd37-dc313eb22162@gmail.com> <CE03DB3D7B45C245BCA0D243277949362FC628DA@MX307CL04.corp.emc.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <dd49e1c9-edcb-4702-e0bc-4a0cd9a3ef8b@gmail.com>
Date: Thu, 21 Sep 2017 14:03:27 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <CE03DB3D7B45C245BCA0D243277949362FC628DA@MX307CL04.corp.emc.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/DWimWZcSLAZwMF4MTYSNwekZA4M>
Subject: Re: [Gen-art] Genart telechat review of draft-ietf-tsvwg-ecn-experimentation-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 02:03:29 -0000

Thanks David. That completely responds to my comments.

Regards
   Brian

On 21/09/2017 10:45, Black, David wrote:
> Brian,
> 
> I'm about to post the -06 version of this draft.   The concern on RFC 3168 impact of the ECN nonce removal was resolved by listing the four major changes (and you were correct that the change to Section 20.2 is subtle - I got it wrong on my first attempt in responding to your email).  Here's the specific text that I've added to Section 3 of the draft:
> 
>    The four primary updates to RFC 3168 that remove discussion of the
>    ECN nonce and use of ECT(1) for that nonce are:
> 
>    1.  Remove the paragraph in Section 5 that immediately follows
>        Figure 1; this paragraph discusses the ECN nonce as the
>        motivation for two ECT codepoints.
> 
>    2.  Remove Section 11.2 "A Discussion of the ECN nonce." in its
>        entirety.
> 
>    3.  Remove the last paragraph of Section 12, which states that ECT(1)
>        may be used as part of the implementation of the ECN nonce.
> 
>    4.  Remove the first two paragraphs of Section 20.2, which discuss
>        the ECN nonce and alternatives.  No changes are made to the rest
>        of Section 20.2, which discusses alternate uses for the fourth
>        ECN codepoint.
> 
>    Additional minor changes remove other mentions of the ECN nonce and
>    implications that ECT(1) is intended for use by the ECN nonce; the
>    specific text updates are omitted for brevity.
> 
> The proverbial "rest of the story" is that an RFC 3168bis effort appears to be a good idea, e.g., as RFC 6040 has already made some visible changes. The preferred 3168bis timing appears to be after we understand the outcomes of the current proposed of experiments, as they're likely to result in another round of changes to RFC 3168.
> 
> Many thanks, and chalk this up as one more instance where a GenART review has visibly improved the quality of a draft,  --David
> 
>> -----Original Message-----
>> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
>> Sent: Friday, September 1, 2017 7:41 PM
>> To: Black, David <david.black@emc.com>; gen-art@ietf.org
>> Cc: draft-ietf-tsvwg-ecn-experimentation.all@ietf.org; tsvwg@ietf.org
>> Subject: Re: Genart telechat review of draft-ietf-tsvwg-ecn-
>> experimentation-05
>>
>> On 02/09/2017 09:45, Black, David wrote:
>>> Brian,
>>>
>>> Thanks for the prompt review.
>>>
>>>> Comment: Very clear from the technical standpoint.
>>>
>>> Thank you!
>>>
>>>> I understand the desire for brevity, but this bothers me a bit. What is
>>>> the reader to make of RFC3168 Section 20.2, for example? My feeling is
>>>> that a short Appendix outlining the specific updates would be useful.
>>>> There's already too much spaghetti to untangle.
>>>
>>> RFC 3168 Section 20.2 is the rationale for the ECN Nonce and hence would
>> be
>>> deleted. Request noted, I'll consult with the draft shepherd and
>> responsible
>>> AD to figure out whether to do this.
>>
>> Thanks. It's not intended as a blocking issue.
>>
>>>
>>>> I see no reason why RFC3540 and RFC5622 need to be normative
>> references
>>>> (and therefore downrefs). They aren't required reading in order to
>>>> understand this draft.
>>>
>>> OTOH, both are affected by this draft:
>>>
>>> In reverse order, this draft updates RFC 5622 - that seems to merit a
>>> normative reference.    This draft also provides the rationale for the
>>> status change of RFC 3540 to Historic, which also seems to merit a
>>> normative reference.
>>
>> Well, my understanding is that a normative reference is needed only
>> when the citing document cannot be understood and implemented
>> without reading the cited document.
>>
>> Again it's not a blocking comment - although there is a technical error
>> in the Last Call message: it flags the downref to 5622, but not that to 3540.
>> I don't know if that's a tool error or an AD error ;-).
>>
>>     Brian
>>
>>>
>>> Thanks, --David
>>>
>>>
>>>> -----Original Message-----
>>>> From: Brian Carpenter [mailto:brian.e.carpenter@gmail.com]
>>>> Sent: Thursday, August 31, 2017 10:02 PM
>>>> To: gen-art@ietf.org
>>>> Cc: draft-ietf-tsvwg-ecn-experimentation.all@ietf.org; tsvwg@ietf.org
>>>> Subject: Genart telechat review of draft-ietf-tsvwg-ecn-experimentation-
>> 05
>>>>
>>>> Reviewer: Brian Carpenter
>>>> Review result: Ready with Issues
>>>>
>>>> Gen-ART Last Call review of draft-ietf-tsvwg-ecn-experimentation-05
>>>>
>>>> I am the assigned Gen-ART reviewer for this draft. The General Area
>>>> Review Team (Gen-ART) reviews all IETF documents being processed
>>>> by the IESG for the IETF Chair.  Please treat these comments just
>>>> like any other last call comments.
>>>>
>>>> For more information, please see the FAQ at
>>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>>
>>>> Document: draft-ietf-tsvwg-ecn-experimentation-05.txt
>>>> Reviewer: Brian Carpenter
>>>> Review Date: 2017-09-01
>>>> IETF LC End Date: 2017-09-14
>>>> IESG Telechat date: 2017-09-14
>>>>
>>>> Summary: Ready with (minor) issues
>>>> --------
>>>>
>>>> Comment: Very clear from the technical standpoint.
>>>> --------
>>>>
>>>> Minor Issues:
>>>> -------------
>>>>
>>>>> 3.  ECN Nonce and RFC 3540
>>>> ...
>>>>> o  Updates RFC 3168 [RFC3168] to remove discussion of the ECN Nonce
>>>>>    and use of ECT(1) for that Nonce.  The specific text updates are
>>>>>    omitted for brevity.
>>>>
>>>> I understand the desire for brevity, but this bothers me a bit. What is
>>>> the reader to make of RFC3168 Section 20.2, for example? My feeling is
>>>> that a short Appendix outlining the specific updates would be useful.
>>>> There's already too much spaghetti to untangle.
>>>>
>>>> I see no reason why RFC3540 and RFC5622 need to be normative
>> references
>>>> (and therefore downrefs). They aren't required reading in order to
>>>> understand this draft.
>>>>
>>>> --
>>>


From nobody Wed Sep 20 19:19:37 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04FD6132944; Wed, 20 Sep 2017 19:19:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 PNdK1CyBoCra; Wed, 20 Sep 2017 19:19:27 -0700 (PDT)
Received: from mail-pg0-x236.google.com (mail-pg0-x236.google.com [IPv6:2607:f8b0:400e:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1FA3B1320DC; Wed, 20 Sep 2017 19:19:27 -0700 (PDT)
Received: by mail-pg0-x236.google.com with SMTP id b11so2722331pgn.12; Wed, 20 Sep 2017 19:19:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Az3sqUpHtSeRUo/Igh2nKvcadMxQQstZHY4DqXORPUo=; b=pza8daQNUi+lGhgoaR6qrQq7fvM8/iRJLBFJkesOlutWhpttuv46H4Fj4LcGYPH7o9 rWjjKwHaM41VgBDfIMPU2w5YXP8lMt6/zfOFR13JeYk+j64wi0lWUmSkBaJFPB0H3yxa O02nVcgH/wkyoCQ5EQeoNlwiK48mXsdSMVeILcxLlT3mD5go8zPdgmnrYeFHxyfpzITA C1WZyKKPMqfMe9iVVFPjy1FHbTcABcMrN0KXW1MixuRZK8qcj4E7cno7BTk/mOMsPxfc XiIdhmVMhlwSUMi3zK5HhJGl0ix3a2hMDosoK9xZq1D/fhGIfbIID1nCVatzWyMhYf/x EqYw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=Az3sqUpHtSeRUo/Igh2nKvcadMxQQstZHY4DqXORPUo=; b=Soa9nV6gLWBPYToMbJ2VGrCQnaNz0GT7AwqI9a/mxToEt+qD9lFnDC2pREf2wiekTP q+GMwIwgUJfccglw18c5mw6Jm13ciFxpzhrbe/XeF8ZSNlYBIOfQKrQWs9LrzuhF668R rz8+09RQO5z15+3zeeEEhBXpvkgH64bZjf9ixdj2/lDRQdJuevHnP1P0n40WxdEqy4B9 e39jj31SH2pKwafyqR4QTdH0DpDBpWVZvz4fOxUJRS0abLuA0FlCACBwGRH7C6J+oAOo 49BRE59ECrDyriJFdMRHueyjw3ygoK7EMjaDf6dIhzHP5h1/XFlyNt9Eb3iQJOCpWnRJ d/ZQ==
X-Gm-Message-State: AHPjjUgOM/l14ofqrAmw8edKePYrYgnhLfVb5azEWr5Gx9b0M6vhgzYu 8E4vvOub4YZ4aPVyv8dtIK274g==
X-Google-Smtp-Source: AOwi7QAnRf1Y4tMSU0pzEx+a7Rw9mlsMP+8BDfVumZIU975geATwzvarCRjHnPqRi1DmJYob1rmc6Q==
X-Received: by 10.101.70.203 with SMTP id n11mr4091125pgr.197.1505960366329; Wed, 20 Sep 2017 19:19:26 -0700 (PDT)
Received: from ?IPv6:2406:e001:3f51:1:28cc:dc4c:9703:6781? ([2406:e001:3f51:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id c82sm305741pfe.172.2017.09.20.19.19.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Sep 2017 19:19:25 -0700 (PDT)
To: Matt Griswold <grizz@20c.com>
Cc: gen-art@ietf.org, grow@ietf.org, draft-ietf-grow-bgp-session-culling.all@ietf.org
References: <150579629891.15651.17244647188709040958@ietfa.amsl.com> <20170921001353.260a3439@x0r>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <5aedafdd-8cc6-8d25-e702-26b4beac15ea@gmail.com>
Date: Thu, 21 Sep 2017 14:19:29 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <20170921001353.260a3439@x0r>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/SJUsBxO3JWFHU82JsxabXEICBig>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-grow-bgp-session-culling-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 02:19:29 -0000

On 21/09/2017 12:13, Matt Griswold wrote:
> * Brian Carpenter <brian.e.carpenter@gmail.com> [170918 21:44 -0700]:
>> Minor Issues:
>> -------------
>>
>>> 3.1.1.  Maintenance Considerations
>>>
>>>  Initiators of the administrative shutdown could consider using
>>>  Graceful Shutdown [I-D.ietf-grow-bgp-gshut] to facilitate smooth
>>>  drainage of traffic prior to session tear down, and the Shutdown
>>>  Communication [I-D.ietf-idr-shutdown]...  
>>
>> This strikes me as vague. "Could consider"? Surely if this is
>> a BCP, they MUST use some mechanisms and perhaps SHOULD use these
>> particular mechanisms. Otherwise the document doesn't specify
>> anything much at all for this case.
> 
> Graceful Shutdown is just one of multiple ways an Operator can
> accomplish that.

Understood, so perhaps it's a MAY not a SHOULD, but the text still
really only seems to say "do the right thing" without saying what
that is. To be honest the whole document is a bit like that - written
for members of the club who know how to run BGP, rather than for a
newcomer who wants to know how to run BGP.

> 
>>> 3.2.  Involuntary BGP Session Teardown Recommendations  
>> ...
>>>  In the absence notifications from the lower layer (e.g. ethernet
>>>   link down) consistent with the planned maintenance activities in a
>>>  switched layer-2 fabric, the Caretaker of the fabric could choose
>>>   to cull BGP sessions on behalf of the Operators connected to the
>>>   fabric.  
>>
>> This seems incomplete. Firstly, I'm assuming that it should start
>> "In the absence of notifications...".
> 
> Fixed!
> 
>> Secondly, if there are no fault indications, what causes the
>> Caretaker to cull sessions? What's the trigger? Is the Caretaker
>> supposed to know by magic that layer 2 maintenance is planned?
> 
> The Caretaker controls the layer 2 network, so yes, would do this as
> part of the maintenance process.

Again: not clear to a newcomer. 

>> ...
>>>  In this scenario, BGP Session Culling is accomplished through the
>>>  application of a combined layer-3 and layer-4 packet filter
>>>   deployed in the switched fabric itself.  
>>
>> Please add "as described in the next sub-section" because otherwise
>> the reader can easily be confused.
> 
> Added.
> 
>>> 3.2.1.  Packet Filter Considerations
>>>
>>>  The following considerations apply to the packet filter design:
>>>
>>>  o  The packet filter MUST only affect BGP traffic specific to the
>>>     layer-2 fabric, i.e. forming part of the control plane of the
>>>     system described, rather than multihop BGP traffic which merely
>>>     transits  
>>
>> That's a goal, but it doesn't tell me how to achieve the goal.
>> What packet signature tells me which packets are specific to the
>> fabric? I suspect this might overlap with the last bullet - if so,
>> you might consider re-ordering the bullets.
>> ...
>>>  o  The packet filter MUST affect all relevant Address Family
>>>     Identifiers  
>>
>> Define "relevant".
> 
> Removed "relevant".
> 
>> And in Appendix A, explain precisely how the example prefixes are
>> used: what makes them relevant? Are they normally announced by BGP to
>> all the IXP's BGP peers?
> 
> They are the IXP LAN addresses, as explained above the examples.

Yes, I realise that, but again you're assuming that the reader has
a complete picture in her mind. Maybe there's actually a need for
a scenario description in the Introduction, or at least a reminder
that in normal operation, paths through the fabric in question may be
known throughout the BGP realm, and the objective is to delete
those paths before starting maintenance.

> Thanks for your review!

You're welcome,
    Brian


From nobody Thu Sep 21 10:04:19 2017
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED1261286C7; Thu, 21 Sep 2017 10:04:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 fSvtyf9zem0c; Thu, 21 Sep 2017 10:04:16 -0700 (PDT)
Received: from alum-mailsec-scanner-5.mit.edu (alum-mailsec-scanner-5.mit.edu [18.7.68.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0D23912008A;  Thu, 21 Sep 2017 10:04:15 -0700 (PDT)
X-AuditID: 12074411-f7dff70000007f0a-90-59c3f10e4520
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by alum-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP id B6.DA.32522.E01F3C95; Thu, 21 Sep 2017 13:04:14 -0400 (EDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id v8LH4De8015847 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 21 Sep 2017 13:04:13 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
To: draft-baeuerle-netnews-cancel-lock.all@ietf.org
Cc: General Area Review Team <gen-art@ietf.org>
Message-ID: <e350cd4f-126d-c4f9-b817-d941c15c21f9@alum.mit.edu>
Date: Thu, 21 Sep 2017 13:04:13 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLIsWRmVeSWpSXmKPExsUixO6iqMv38XCkwcc1UhbtK74wWVx99ZnF gcljyZKfTAGMUVw2Kak5mWWpRfp2CVwZ7248Zin4KFex8Mcj1gbGa4JdjBwcEgImEt2LJLsY uTiEBHYwSXzqeckK4Txkknh09Q97FyMnB5uAlsScQ/9ZQGxhAS+Jp5MXMoLYIgLGEpOObgWL MwvoS/x9spgJxOYVsJdYsGcSmM0ioCpx/nMXWI2oQJrEv91nGSFqBCVOznwC1WsmMW/zQ2YI W1zi1pP5TBC2vETz1tnMExj5ZiFpmYWkZRaSlllIWhYwsqxilEvMKc3VzU3MzClOTdYtTk7M y0st0jXVy80s0UtNKd3ECAlDwR2MM07KHWIU4GBU4uE1OHg4Uog1say4MvcQoyQHk5Io74Gn QCG+pPyUyozE4oz4otKc1OJDjBIczEoivMfeAuV4UxIrq1KL8mFS0hwsSuK8fEvU/YQE0hNL UrNTUwtSi2CyMhwcShK8K98DNQoWpaanVqRl5pQgpJk4OEGG8wANZ/sAMry4IDG3ODMdIn+K 0Zijp+fGHyaOHTfv/mESYsnLz0uVEuf1BSkVACnNKM2DmwZLJa8YxYGeE+b9ALKUB5iG4Oa9 AlrFBLQqe8MBkFUliQgpqQZG7jPz4mI8puj2HDIMD4uzmDwpT6rz9dLb7Id9ckzmzcgTbzro foZ9y8L0Jk/j6ZuP/sjbtT+wUv/2mc4F8Ro7lux6yf/H/74kW+HPImmnNVnOB5brP24/wHLo M5P5I5+/DQmFjxXP9PuvVF4kK7miV3a74nRNd7EFHdtd1x89NueJ19S+IpdsJZbijERDLeai 4kQAAhW74gADAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/OQC5Oscvpwo331cobORN6QLzM5g>
Subject: [Gen-art] Gen-ART Last Call review of draft-baeuerle-netnews-cancel-lock-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 17:04:18 -0000

I am the assigned Gen-ART reviewer for this draft. The General Area 
Review Team (Gen-ART) reviews all IETF documents being processed by the 
IESG for the IETF Chair. Please wait for direction from your document 
shepherd or AD before posting a new version of the draft. For more 
information, please see the FAQ at 
<â€‹http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-baeuerle-netnews-cancel-lock-06
Reviewer: Paul Kyzivat
Review Date: 2017-09-21
IETF LC End Date: 2017-06-28
IESG Telechat date: 2017-09-26

Summary:

This draft is on the right track but has open issues, described in the 
review.

General Comments:

I have not attempted to validate the security properties of this 
document - leaving that to a security review.

I have also not attempted to verify the operational suitability of this 
mechanism because I don't have the experience needed to do so.

Issues:

Major: 1
Minor: 0
Nits:  0

(1) MAJOR:

In Section 2, the ABNF syntax provided does not do what you want it to. 
You supply:

        fields =/ *( cancel-lock / cancel-key )

as an extension to the definition in RFC5536:

     fields          =/ *( approved /
                           archive /
                           control /
                           distribution /
                           expires /
                           followup-to /
                           injection-date /
                           injection-info /
                           lines /
                           newsgroups /
                           organization /
                           path /
                           summary /
                           supersedes /
                           user-agent /
                           xref )

and that in turn extends RFC5322:

     fields          =   *(trace
                           *optional-field /
                           *(resent-date /
                            resent-from /
                            resent-sender /
                            resent-to /
                            resent-cc /
                            resent-bcc /
                            resent-msg-id))
                         *(orig-date /
                         from /
                         sender /
                         reply-to /
                         to /
                         cc /
                         bcc /
                         message-id /
                         in-reply-to /
                         references /
                         subject /
                         comments /
                         keywords /
                         optional-field)

     message         =   (fields / obs-fields)
                         [CRLF body]

RFC5536 got this wrong, and the new draft continues the mistake. The 
problem is with the way things are grouped. Let me give a simpler example:

     foo = *("a" / "b") / *("c" / "d")

This means the following are valid: ab aabb bab cd ccdd dcd
But the following are not: abcd ac

The latter is what you want, for which the syntax would be:

     foo = *("a" / "b" / "c" / "d")

It isn't easy to do a valid syntax extension like this because of way 
the ABNF of RFC5322 is structured. However, after offline discussion, we 
realized that RFC5322 already has an extension point for new headers via 
the <optional-field> rule. Along with that, RFC3864 established a 
process for registering header fields with IANA.

So, my recommendation is that to fix this, remove from section 2 the 
extension of the <fields> rule:

       fields =/ *( cancel-lock / cancel-key )

Instead, simply rely on the text to specify the newly defined header 
fields, and the IANA registration to link them to RFC5322. This will 
probably require some minor tweaking of the text. I won't try to do the 
wordsmithing here.


From nobody Thu Sep 21 12:09:04 2017
Return-Path: <grizz@20c.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDB10132F65 for <gen-art@ietfa.amsl.com>; Thu, 21 Sep 2017 12:09:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=20c-com.20150623.gappssmtp.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 50J9UOIS8fqw for <gen-art@ietfa.amsl.com>; Thu, 21 Sep 2017 12:08:59 -0700 (PDT)
Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C46B6132D54 for <gen-art@ietf.org>; Thu, 21 Sep 2017 12:08:59 -0700 (PDT)
Received: by mail-io0-x234.google.com with SMTP id l15so13149268iol.8 for <gen-art@ietf.org>; Thu, 21 Sep 2017 12:08:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=20c-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=ajY+IoGbpz70jvGBLnqSu+a9imlBvp4KbffcvxrT5qI=; b=RugmZYcUnPPhHK16xOGm4YGGBiBpbEv/ToH+vZBQ5adACxHLH6mWOEki633OO18SC2 deAQz51D02YukX5K9nPJteJt+eCkAYeH+wiwdTmZQotX3MvTh1vvc+NiT5/DcDs2Z1bT U83PeAdn3Nrdgf8kKXmlGDiSmQg3AbXIvhYmJ+8nYgcoEJEGDMwwi2i07wXMarvpECGU iXHPhoCi5zYY+IAl1AQiIDRUSrhJJuEJsi3k8i/5G461WoqijHoKWCCfO1CTn200ix6h 5Qtda6brefKO+l5qs/MvuettKFnuig7FFvE8exqQtlD/a71c4yKMgvjnVchyX4nubtDK 9FFg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=ajY+IoGbpz70jvGBLnqSu+a9imlBvp4KbffcvxrT5qI=; b=ULdhHsmmL1nwjbCjaDoXU9E2S+wF/Yx/JYjEyTmF94t0ngkUe3LM8MIC3Lzz3vaeNp t8DM6Kw6rU7XbmImuO92aKCkiji/pwR7FmVv8dZzrauyqpsvXOoO/WVBeSqFIkUVSUkZ F6suQ0P0waA/Llx9OcrzhwBT+06Vq9GrxZ8eVPQmnhNaVlAZ6T1VcHn/PA2kJGlQz1xj S5vydGwQ3l7OgPOqdo5eNxcUElenyX56jSbvPF2GgtnOWoUMxuaqKFV29gyHLAOg7pbx cmJFFUHTATSpK+fnyipgoZBky4kPHOoOqHsHu5pphwUOaQy9YYAa60btV9gsCVS72GLF YEpg==
X-Gm-Message-State: AHPjjUjmNlh+gD4mPXUmcB8RYfzft+UfAi4insvsMbWK60UCeprxq5Di gYJCf0h9M9I+RfKOzJV2KVJiQQ==
X-Google-Smtp-Source: AOwi7QABrz1ZnnNqmMum3LizFLzkdG0dk1pw4AkFh/HDINNhF5+mGP9ZDe0G7IyDDnc2MPgUDeP9Uw==
X-Received: by 10.107.29.149 with SMTP id d143mr4679842iod.201.1506020938883;  Thu, 21 Sep 2017 12:08:58 -0700 (PDT)
Received: from x0r (97-83-204-249.dhcp.eucl.wi.charter.com. [97.83.204.249]) by smtp.gmail.com with ESMTPSA id 193sm1138094ion.83.2017.09.21.12.08.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 Sep 2017 12:08:57 -0700 (PDT)
Date: Thu, 21 Sep 2017 19:08:55 +0000
From: Matt Griswold <grizz@20c.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: gen-art@ietf.org, grow@ietf.org, draft-ietf-grow-bgp-session-culling.all@ietf.org
Message-ID: <20170921190855.303addad@x0r>
In-Reply-To: <5aedafdd-8cc6-8d25-e702-26b4beac15ea@gmail.com>
References: <150579629891.15651.17244647188709040958@ietfa.amsl.com> <20170921001353.260a3439@x0r> <5aedafdd-8cc6-8d25-e702-26b4beac15ea@gmail.com>
X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.28; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/6Vo9pdrzH7oeSeSOk-tG_4FZZeY>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-grow-bgp-session-culling-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 19:09:02 -0000

* Brian E Carpenter <brian.e.carpenter@gmail.com> [170921 14:19 +1200]:
> On 21/09/2017 12:13, Matt Griswold wrote:
> > * Brian Carpenter <brian.e.carpenter@gmail.com> [170918 21:44
> >   -0700]:  
> >> Minor Issues:
> >> -------------
> >>  
> >>> 3.1.1.  Maintenance Considerations
> >>>
> >>>  Initiators of the administrative shutdown could consider using
> >>>  Graceful Shutdown [I-D.ietf-grow-bgp-gshut] to facilitate smooth
> >>>  drainage of traffic prior to session tear down, and the Shutdown
> >>>  Communication [I-D.ietf-idr-shutdown]...    
> >>
> >> This strikes me as vague. "Could consider"? Surely if this is
> >> a BCP, they MUST use some mechanisms and perhaps SHOULD use these
> >> particular mechanisms. Otherwise the document doesn't specify
> >> anything much at all for this case.  
> > 
> > Graceful Shutdown is just one of multiple ways an Operator can
> > accomplish that.  
> 
> Understood, so perhaps it's a MAY not a SHOULD

You're right, I will update it to MAY.

> but the text still really only seems to say "do the right thing"
> without saying what that is. To be honest the whole document is a bit
> like that - written for members of the club who know how to run BGP,
> rather than for a newcomer who wants to know how to run BGP.

That's really by design, the document is for people who know and run
BGP, I think putting too much basic BGP knowledge would make it
monotonous. Any ideas on how to meet in the middle?

> >> Secondly, if there are no fault indications, what causes the
> >> Caretaker to cull sessions? What's the trigger? Is the Caretaker
> >> supposed to know by magic that layer 2 maintenance is planned?  
> > 
> > The Caretaker controls the layer 2 network, so yes, would do this as
> > part of the maintenance process.  
> 
> Again: not clear to a newcomer.

The updated language is:

  Throughout this document the "Caretaker" is defined to be in control
  of the lower layer network, while "Operators" directly administrate
  the BGP speakers.

I think that clears it up?

> >> And in Appendix A, explain precisely how the example prefixes are
> >> used: what makes them relevant? Are they normally announced by BGP
> >>   to all the IXP's BGP peers?  
> > 
> > They are the IXP LAN addresses, as explained above the examples.  
> 
> Yes, I realise that, but again you're assuming that the reader has
> a complete picture in her mind. Maybe there's actually a need for
> a scenario description in the Introduction, or at least a reminder
> that in normal operation, paths through the fabric in question may be
> known throughout the BGP realm, and the objective is to delete
> those paths before starting maintenance.

Again, that section is for IXP Caretakers so I don't think we need to
go into IXP operational details too much. Adding a brief scenario
paragraph should work, I'll write something up.

Thanks


From nobody Thu Sep 21 13:23:52 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 556251330C1; Thu, 21 Sep 2017 13:23:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 sqVpf7HMb805; Thu, 21 Sep 2017 13:23:46 -0700 (PDT)
Received: from mail-pg0-x231.google.com (mail-pg0-x231.google.com [IPv6:2607:f8b0:400e:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C99313308A; Thu, 21 Sep 2017 13:23:46 -0700 (PDT)
Received: by mail-pg0-x231.google.com with SMTP id c137so4109722pga.11; Thu, 21 Sep 2017 13:23:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=l04loXUgwaXiYt/lFsTNLrXDEMbTFith7rAZe6UDAdg=; b=GQUHpIvEGg5g4Aq6EPK6wUDiZoZ7Sr//khVKKb8r/HEMr7rWVUrCI5P4yMCltXrozx 7HFtfOoK80dxPn01NSN6tMEvzqWnxXbtcyWn8jK0DEkvAZ4Z0U0DJXTgQpoB9Vumfzuj 9d9+OZZOsSMNBg3FKRA6QEJvjJbF1e543pPHg3jlrcUGMyckIu6vvLM244dPLAIgr0O/ E4tm4PL2bwGH0xe2TMaZIMj6aYXN0ULnY9gxTVPMUEnrnzqSgTFja65KjD+t59DOAW3V 0RojFWJtk5M5Gvq+Pifxbsv7hjk30L9r58/T2kfg1SGschlhl9EkmATYYFB/kcqXGGj6 luDg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=l04loXUgwaXiYt/lFsTNLrXDEMbTFith7rAZe6UDAdg=; b=tC36zW1akLedm2NEJLHWEXshdZU2YNjktSgFKPurFuzKKkty8nLelEMmKnSIY8Q4sh Yyo6AuPLLYEuz2LW74ei0p+wvWlsSsztic5II3aN1rFFRy8pAA9RFNt4qmcKN+ZLaJzC zR2OoYlr4vEazyqogodZO0ln4kqMzyRCwDp/RWbWXi5CJNBRzzV1YtaroJIB+V8wsVj/ rUVBZqiuNh+e2wIiprPCC9vQgxIzrKIn6APPkubjaDNgdcWCjF3AMgAL6U8ZuEeOQ3jZ FNFPi/Xepej8t2wSCz3neIt0X3Ouu+joNtN5/XUHqSSSZgi7KNZWNmsecJYl6fWVqRUR fePQ==
X-Gm-Message-State: AHPjjUi9QgiLtA9+Ltp4gMO1LZg56xrtIaCOeuiVSxoCVxVnnwt9BaDJ RZbZrPO1U8/gKBDQ/ka3xs3cIA==
X-Google-Smtp-Source: AOwi7QCKPJiOA+BykOfOaim+AcGJgFT8ZwCAGuKWf68GQqOuSEVa4PdugIWskllToOTTikcr5lTrIg==
X-Received: by 10.84.197.69 with SMTP id m63mr6619022pld.226.1506025425628; Thu, 21 Sep 2017 13:23:45 -0700 (PDT)
Received: from ?IPv6:2406:e001:3f51:1:28cc:dc4c:9703:6781? ([2406:e001:3f51:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id k13sm3439783pgo.51.2017.09.21.13.23.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 Sep 2017 13:23:43 -0700 (PDT)
To: Matt Griswold <grizz@20c.com>
Cc: gen-art@ietf.org, grow@ietf.org, draft-ietf-grow-bgp-session-culling.all@ietf.org
References: <150579629891.15651.17244647188709040958@ietfa.amsl.com> <20170921001353.260a3439@x0r> <5aedafdd-8cc6-8d25-e702-26b4beac15ea@gmail.com> <20170921190855.303addad@x0r>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <c0f179f2-c712-9579-f6ae-b458a9e5bbbd@gmail.com>
Date: Fri, 22 Sep 2017 08:23:48 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <20170921190855.303addad@x0r>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/WkV2IuU70UWVlm-P-NJYN3753LA>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-grow-bgp-session-culling-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 20:23:50 -0000

Hi Matt,
On 22/09/2017 07:08, Matt Griswold wrote:
> * Brian E Carpenter <brian.e.carpenter@gmail.com> [170921 14:19 +1200]:
>> On 21/09/2017 12:13, Matt Griswold wrote:
>>> * Brian Carpenter <brian.e.carpenter@gmail.com> [170918 21:44
>>>   -0700]:  
>>>> Minor Issues:
>>>> -------------
>>>>  
>>>>> 3.1.1.  Maintenance Considerations
>>>>>
>>>>>  Initiators of the administrative shutdown could consider using
>>>>>  Graceful Shutdown [I-D.ietf-grow-bgp-gshut] to facilitate smooth
>>>>>  drainage of traffic prior to session tear down, and the Shutdown
>>>>>  Communication [I-D.ietf-idr-shutdown]...    
>>>>
>>>> This strikes me as vague. "Could consider"? Surely if this is
>>>> a BCP, they MUST use some mechanisms and perhaps SHOULD use these
>>>> particular mechanisms. Otherwise the document doesn't specify
>>>> anything much at all for this case.  
>>>
>>> Graceful Shutdown is just one of multiple ways an Operator can
>>> accomplish that.  
>>
>> Understood, so perhaps it's a MAY not a SHOULD
> 
> You're right, I will update it to MAY.
> 
>> but the text still really only seems to say "do the right thing"
>> without saying what that is. To be honest the whole document is a bit
>> like that - written for members of the club who know how to run BGP,
>> rather than for a newcomer who wants to know how to run BGP.
> 
> That's really by design, the document is for people who know and run
> BGP, I think putting too much basic BGP knowledge would make it
> monotonous. Any ideas on how to meet in the middle?

Your suggestion below "Adding a brief scenario paragraph should work,
I'll write something up." would do it, I think. (I should add that my
perspective is that of someone who understands in theory how BGP is supposed
to work but has never personally practiced it - I'm not suggesting you
need to cover everything, just supply a few clues.)

> 
>>>> Secondly, if there are no fault indications, what causes the
>>>> Caretaker to cull sessions? What's the trigger? Is the Caretaker
>>>> supposed to know by magic that layer 2 maintenance is planned?  
>>>
>>> The Caretaker controls the layer 2 network, so yes, would do this as
>>> part of the maintenance process.  
>>
>> Again: not clear to a newcomer.
> 
> The updated language is:
> 
>   Throughout this document the "Caretaker" is defined to be in control
>   of the lower layer network, while "Operators" directly administrate
>   the BGP speakers.
> 
> I think that clears it up?

Yes.

> 
>>>> And in Appendix A, explain precisely how the example prefixes are
>>>> used: what makes them relevant? Are they normally announced by BGP
>>>>   to all the IXP's BGP peers?  
>>>
>>> They are the IXP LAN addresses, as explained above the examples.  
>>
>> Yes, I realise that, but again you're assuming that the reader has
>> a complete picture in her mind. Maybe there's actually a need for
>> a scenario description in the Introduction, or at least a reminder
>> that in normal operation, paths through the fabric in question may be
>> known throughout the BGP realm, and the objective is to delete
>> those paths before starting maintenance.
> 
> Again, that section is for IXP Caretakers so I don't think we need to
> go into IXP operational details too much. Adding a brief scenario
> paragraph should work, I'll write something up.

Great.

    Brian


From nobody Thu Sep 21 14:19:29 2017
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C394D13263F for <gen-art@ietf.org>; Thu, 21 Sep 2017 14:19:27 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jean Mahoney <mahoney@nostrum.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.62.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-to: mahoney@nostrum.com
Message-ID: <150602876779.10460.9266813328359882394.idtracker@ietfa.amsl.com>
Date: Thu, 21 Sep 2017 14:19:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/50Hrad3s69_gMBF0p9TOa5eXqjA>
Subject: [Gen-art] Review Assignments
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 21:19:28 -0000

Hi all,

The following reviewers have assignments:

For telechat 2017-09-28

Reviewer               Type      LC end     Draft
Brian Carpenter        Telechat  2017-09-19 draft-ietf-tsvwg-ecn-experimentation-06 *
Elwyn Davies           Last Call 2017-09-22 draft-ietf-teas-rsvp-te-scaling-rec-06
Paul Kyzivat           Telechat  2017-06-28 draft-baeuerle-netnews-cancel-lock-06 *

For telechat 2017-10-12

Reviewer               Type      LC end     Draft
Roni Even              Last Call 2017-10-04 draft-ietf-rtgwg-uloop-delay-06
Vijay Gurbani          Last Call 2017-10-03 draft-ietf-rtgwg-routing-types-14
Joel Halpern           Last Call 2017-10-02 draft-ietf-tcpm-cubic-06
Christer Holmberg      Last Call 2017-10-02 draft-ietf-nvo3-mcast-framework-09
Pete Resnick           Last Call 2017-10-04 draft-ietf-lisp-sec-13

Last calls:

Reviewer               Type      LC end     Draft
Jari Arkko             Last Call 2017-10-11 draft-wu-l3sm-rfc8049bis-05
Linda Dunbar           Last Call 2017-09-28 draft-ietf-ippm-alt-mark-10
Francis Dupont         Last Call 2017-10-16 draft-dawkins-iesg-nomcom-advisor-iaoc-03
Orit Levin             Last Call 2017-09-26 draft-ietf-v6ops-rfc6555bis-04

* Other revision previously reviewed
** This revision already reviewed

Next in the reviewer rotation:

  Fernando Gont
  Vijay Gurbani
  Wassim Haddad
  Joel Halpern
  Christer Holmberg
  Russ Housley
  Jouni Korhonen
  Paul Kyzivat
  Orit Levin
  Matthew Miller

The LC and Telechat review templates are included below:
-------------------------------------------------------

-- Begin LC Template --
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments: 

-- End LC Template --

-- Begin Telechat Template --
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

-- End Telechat Template --



From nobody Fri Sep 22 12:01:32 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8ED811345AB; Fri, 22 Sep 2017 12:01:24 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern <jmh@joelhalpern.com>
To: <gen-art@ietf.org>
Cc: tcpm@ietf.org, ietf@ietf.org, draft-ietf-tcpm-cubic.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.62.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150610688453.16831.3652838434219802004@ietfa.amsl.com>
Date: Fri, 22 Sep 2017 12:01:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/7H5cKJFmmuTEo48o_DXAmdFyUQg>
Subject: [Gen-art] Genart last call review of draft-ietf-tcpm-cubic-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Sep 2017 19:01:25 -0000

Reviewer: Joel Halpern
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-tcpm-cubic-06
Reviewer: Joel Halpern
Review Date: 2017-09-22
IETF LC End Date: 2017-10-02
IESG Telechat date: 2017-10-12

Summary: This Document is ready for publication as an Informational RFC.

Major issues: N/A

Minor issues: N/A

Nits/editorial comments:  N/A



From nobody Fri Sep 22 14:12:48 2017
Return-Path: <worley@alum.mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A17FE13303A for <gen-art@ietfa.amsl.com>; Fri, 22 Sep 2017 14:12:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level: 
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
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 CRXSY16GTV81 for <gen-art@ietfa.amsl.com>; Fri, 22 Sep 2017 14:12:45 -0700 (PDT)
Received: from resqmta-ch2-09v.sys.comcast.net (resqmta-ch2-09v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:41]) (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 8399D13219B for <gen-art@ietf.org>; Fri, 22 Sep 2017 14:12:45 -0700 (PDT)
Received: from resomta-ch2-01v.sys.comcast.net ([69.252.207.97]) by resqmta-ch2-09v.sys.comcast.net with ESMTP id vVFbdxpOTeT1FvVFcdflqJ; Fri, 22 Sep 2017 21:12:44 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-01v.sys.comcast.net with SMTP id vVFadCtZVqsElvVFbd0gVP; Fri, 22 Sep 2017 21:12:43 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v8MLCgmd006134; Fri, 22 Sep 2017 17:12:42 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v8MLCg11006131; Fri, 22 Sep 2017 17:12:42 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Matt Griswold <grizz@20c.com>
Cc: brian.e.carpenter@gmail.com, gen-art@ietf.org, draft-ietf-grow-bgp-session-culling.all@ietf.org, grow@ietf.org
In-Reply-To: <20170921190855.303addad@x0r> (grizz@20c.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Fri, 22 Sep 2017 17:12:41 -0400
Message-ID: <87a81mcu9i.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfJ5HeEo689/VRmtCUGIspm9kmlfBo4oyeyctP+PiTVjqf5hIVUWbLnyB44ScQfn1W2dR80lRn5KQBACID2Iif5vg6eXkKQIogKkreYMBWC0cVZk2JyLd VUUzCZ1RNvlAPW1s5T758OfLf3cpYADCd9l4UqsXuNkYY5Lz7MGLWz10Nu3yiF0+JG96ArbwDaZwiTLM3rZKWxy30dkVGUHQbNg1Ug16czterdY3Rpi2MwH9 n700BSEJoLED5pchGgDZCV4lB8rlTqkjJTzBO7PzwIeBWFvwNM+RNbqjUgkvOVIl7/uV2QNVwJKHg5bwFAgYmg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/ll52CPagZNHuIdOcugg8AVMkUUM>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-grow-bgp-session-culling-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Sep 2017 21:12:47 -0000

Matt Griswold <grizz@20c.com> writes:
>> >>> 3.1.1.  Maintenance Considerations
>> >>>
>> >>>  Initiators of the administrative shutdown could consider using
>> >>>  Graceful Shutdown [I-D.ietf-grow-bgp-gshut] to facilitate smooth
>> >>>  drainage of traffic prior to session tear down, and the Shutdown
>> >>>  Communication [I-D.ietf-idr-shutdown]...    
>> >>
>> >> This strikes me as vague. "Could consider"? Surely if this is
>> >> a BCP, they MUST use some mechanisms and perhaps SHOULD use these
>> >> particular mechanisms. Otherwise the document doesn't specify
>> >> anything much at all for this case.  
>> > 
>> > Graceful Shutdown is just one of multiple ways an Operator can
>> > accomplish that.  
>> 
>> Understood, so perhaps it's a MAY not a SHOULD
>
> You're right, I will update it to MAY.
>
>> but the text still really only seems to say "do the right thing"
>> without saying what that is. To be honest the whole document is a bit
>> like that - written for members of the club who know how to run BGP,
>> rather than for a newcomer who wants to know how to run BGP.
>
> That's really by design, the document is for people who know and run
> BGP, I think putting too much basic BGP knowledge would make it
> monotonous. Any ideas on how to meet in the middle?

Section 3.1.1 seems to be uniquely short.  I would favor adding a list
of the "multiple ways an Operator can accomplish that."  Even just
listing the *names* of the methods that might be used is a useful guide
-- a novice operator can use search engines to find tutorial information
regarding the various methods.

Dale


From nobody Fri Sep 22 15:06:35 2017
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 32235133053; Fri, 22 Sep 2017 15:06:33 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Elwyn Davies <elwynd@dial.pipex.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-teas-rsvp-te-scaling-rec.all@ietf.org, ietf@ietf.org, teas@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.62.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150611799315.22445.6055168230107378983@ietfa.amsl.com>
Date: Fri, 22 Sep 2017 15:06:33 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/VVTHjcKvCI-5CD0mjIswTkZ4fk0>
Subject: [Gen-art] Genart last call review of draft-ietf-teas-rsvp-te-scaling-rec-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Sep 2017 22:06:33 -0000

Reviewer: Elwyn Davies
Review result: Not Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-teas-rsvp-te-scaling-rec-06
Reviewer: Elwyn Davies
Review Date: 2017-09-22
IETF LC End Date: 2017-09-22
IESG Telechat date: 2017-09-28

Summary: Not ready, primarily because the title and presentation give the
impression that the content is really a BCP when it isn't.  This conceals the
considerable amount of tweaking of RFC 2961 functionality and addition of new
RSVP Capabilities described in the document.  There are also a couple of minor
issues that need to be sorted out.

Major issues:
Title and way proposals are presented:  The document defines two new
'capabilities' for RSVP-TE and is indeed (as specified in the document header)
correctly intended for Standards Track status.  However the title and the whole
of the meat of the document in Section 2 presents the proposals as
'recommendations' which says to me that I am expecting a BCP where a profile of
available options from existing standards is recommended as the best choice for
implementation and deployment.  In my opinion, the title would be better as
something like "Additional Capabilities Designed to Improve the Scalability of
RSVP-TE Deployments".  Whilst the proposals are based on the techniques in RFC
2961, the document *requires* the implementor to conform to rules that were
optional and constrains configurable values to different ranges in order to be
able to deliver the capabilities defined in the document as well as defining
new RSVP extensions modifying some of the behaviour defined in RFC 2961.  Thus
although some of the rules could be met by choosing particular values within
the RFC 2961 set, the use of MUST, tweaking of functionality and variation of
ranges takes it well beyond a set of recommendations for RFC 2961 options
selections.  In view of this Section 1 needs to be written as an introduction
to the definitions of the new capabilities rather than advocacy for selection
of RFC 2961 options and the implication that the techniques mentioned in the
last paragraph of s1 are just a matter of selecting a profile of option values.
 In actuality new protocol values are introduced and ss2.2 and 2.3 define novel
extensions to RSVP beyond what is available for RFC 2961 and requiring
modification to basic RFC 2961 functionality..

Minor issues:
Interaction with RFC 5063:  The document does not explicitly state that an
implementation would need to support (at least) the extra capability obect
defined in s4.2 of RFC 5063.  Some words about interaction with RFC 5063 are
probably required in that s4.2.1 of RFC 5063 rather assumes that if there is a
capability object, by default its S bit will be set.

Behaviour if a node stops setting Refresh-Reduction-Capable bit:  The last para
of s2 in RFC 2961 discusses behaviour if a node stops setting this bit in
messages.  What would happen with the extensions defined in this document if
this happened while either of the extensions is in use?  As a matter of
interest, if a peer offers the capabilities defined in this draft, is it
possible or sensible for it to stop setting the Refresh-Reduction-Capable bit
without stopping offering the extensions?

s2.1.3, para 2: As specified, it appears that the 'slower timer' transmission
of Path and Resv messages can go on indefinitely if no ack arrives.  What puts
an end to this repetition?  [It may be that I have forgotten how basic RSVP
works, but since this is altering the behaviour it would be good to explain how
it terminates, and whether this requires any additional modification to timers.]

Nits/editorial comments:
Abstract: RSVP-TE is not a 'well-known' abbreviation: s/RSVP-TE/RSVP Traffic
Engineering (RSVP-TE)/

Abstract and s1, first para:  This para is not future proof.  Suggest:
OLD:
   The scale at which RSVP-TE [RFC3209] Label Switched Paths (LSPs) get
   deployed is growing continually and there is considerable onus on
   RSVP-TE implementations across the board to keep up with this
   increasing demand in scale.
NEW:
   At the time of writing, networks which utilise RSVP Traffic Engineering
   (RSVP-TE) [RFC3209] Label Switched Paths (LSPs) are encountering limitations
   in the ability of implementations to support the growth in the number of LSPs
   deployed.  This document defines two additional RSVP-TE extensions that
   are intended to reduce the number of messages needed to maintain RSVP-TE
   soft state in routers and hence allow implementations to support larger
   scale deployments.
ENDS
Note:  Omit reference from Abstract.

s1, para 2: s/under certain/beyond a certain/

s1, para 3: s/makes a set of concrete implementation recommendations/defines
two extensions/; s/- push higher/by increasing/; s/maintain LSP state./maintain
LSP state by reducing the number of messages needed./

Abstract, para 2 and s1, last para:  [Omit reference from Abstract]
OLD:
   This document advocates the use of a couple of techniques - "Refresh-
   Interval Independent RSVP (RI-RSVP)" and "Per-Peer Flow-Control" -
   for significantly cutting down the amount of processing cycles
   required to maintain LSP state.
NEW:
   This document defines two RSVP Capabilities [RFC5063] "Refresh-
   Interval Independent RSVP (RI-RSVP)" and "Per-Peer Flow-Control"
   that will cut down the number of messsages and processing cycles
   required to maintain LSP state.
ENDS

s1, last para: Add new penultimate sentence:
   Note that the "Per-Peer Flow-Control" capability requires the "RI-RSVP"
   capability as a prerequisite.

s1, last para: s/RECOMMENDED/recommended/ - this isn't a recommendation about
the protocol on the wire.

Subdivision of s2:  The issues regarding the nature of the document would be
helped by altering s2 into four top level sections, thus: s2: Requirement for
RFC 2961 Refresh Overhead Reduction Support and Specific Option Choices (from
s2.1) s3: Requirement for RFC 5063 Capability Object support (see Minor Issues
above) s4: Refresh-Interval Independent RSVP Capability (from s2.3) s5:
Per-Peer RSVP Flow Control Capability (from s2.4) Subsequent major sections
then renumbered as s6 onwards. References to s2.x will need to be updated
throughout.

s2.1 (would be introduction of new s2):
OLD:
   The implementation recommendations discussed in this section are
   based on the proposals made in [RFC2961] and act as prerequisites for
   implementing the techniques discussed in Sections 2.2 and 2.3.

NEW:
   The Capabilities defined in Sections 4 and 5 of this document are based on
   proposals made in [RFC2961].  Implementations of these Capabilities will
   need to support the RSVP messages and techniques defined in [RFC2961] as set
   out in Section 2.1 [was 2.1.1] with
   some minor modifications and alterations to recommended time intervals and
   iteration counts as defined in the remainder of this section.
ENDS

s2.1.1, title and para 1 [will be s2.1]:
OLD:
2.1.1.  Basic Prerequisites

   An implementation that supports the techniques discussed in Sections
   2.2 and 2.3 must meet certain basic prerequisites.
NEW:
2.1.  Required Functionality from RFC 2961 to be Implemented

   An implementation that supports the capabiities discussed in Sections
   4 and 5 must provide a large subset of the functionality described
   in [RFC2961] as follows:
ENDS

s2.1.2, para 2 [will be s2.2]: s/techniques discussed in Sections 2.2 and
2.3/Capabilities defined in Sections 4 and 5/

s2.1.2, para 2: s/MESSAGE ID/MESSAGE_ID/

s2.2, para 1: s/improvement on transmission overhead/improvement of
transmission overhead/

s2.2, para 1: s/proposes sufficient recommendations/sets out additional
requirements/

s2.2, last bullet: Add a reference to the proposed new Section 3 that discusses
the Capability object.

s2.2.1, last para: s/set Refresh-Reduction-Capable bit in common header/set the
Refresh-Reduction-Capable bit in the common header/

s2.3, para 1: s/set of recommendations/functionality/; s/provide/provides/;
s/RSVP-TE control plane congestion/a significant portion of the RSVP-TE control
message load/

s2.3.2: s/MESSAGE ID/MESSAGE_ID/



From nobody Sun Sep 24 17:10:05 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BB36132992; Sun, 24 Sep 2017 17:10:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Brian Carpenter <brian.e.carpenter@gmail.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-tsvwg-ecn-experimentation.all@ietf.org, tsvwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.62.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150629820260.5004.13229146476923387593@ietfa.amsl.com>
Date: Sun, 24 Sep 2017 17:10:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/tX6tlp4632Ta2l9rBBT72MvhqQ0>
Subject: [Gen-art] Genart telechat review of draft-ietf-tsvwg-ecn-experimentation-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Sep 2017 00:10:03 -0000

Reviewer: Brian Carpenter
Review result: Ready

Gen-ART telechat review of draft-ietf-tsvwg-ecn-experimentation-06

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-tsvwg-ecn-experimentation-06.txt
Reviewer: Brian Carpenter
Review Date: 2017-09-25
IETF LC End Date: 2017-09-19
IESG Telechat date: 2017-09-28

Summary: Ready
--------

Comment:
--------

Thanks for handling my Last Call comments.



From nobody Mon Sep 25 03:14:09 2017
Return-Path: <nick@foobar.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAB6F1332DA; Mon, 25 Sep 2017 03:14:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 ESL9fdV3F5eT; Mon, 25 Sep 2017 03:14:01 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC48E13420F; Mon, 25 Sep 2017 03:14:00 -0700 (PDT)
X-Envelope-To: grow@ietf.org
Received: from cupcake.local (089-101-195156.ntlworld.ie [89.101.195.156] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id v8P9DXXS045929 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 25 Sep 2017 10:13:34 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-195156.ntlworld.ie [89.101.195.156] (may be forged) claimed to be cupcake.local
Message-ID: <59C8D6D9.7030508@foobar.org>
Date: Mon, 25 Sep 2017 11:13:45 +0100
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.19 (Macintosh/20170908)
MIME-Version: 1.0
To: "Dale R. Worley" <worley@ariadne.com>
CC: Matt Griswold <grizz@20c.com>, gen-art@ietf.org, draft-ietf-grow-bgp-session-culling.all@ietf.org, grow@ietf.org, brian.e.carpenter@gmail.com
References: <87a81mcu9i.fsf@hobgoblin.ariadne.com>
In-Reply-To: <87a81mcu9i.fsf@hobgoblin.ariadne.com>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/vMZt0PjPcI-FtLS9gQ1ErIwxJtc>
Subject: Re: [Gen-art] [GROW] Genart last call review of draft-ietf-grow-bgp-session-culling-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Sep 2017 10:14:03 -0000

Dale R. Worley wrote:
> Section 3.1.1 seems to be uniquely short.  I would favor adding a list
> of the "multiple ways an Operator can accomplish that."  Even just
> listing the *names* of the methods that might be used is a useful guide
> -- a novice operator can use search engines to find tutorial information
> regarding the various methods.

Hi Dale,

At an IXP, it's fine for a client network operator to voluntarily shut
down their bgp sessions, as noted in section 3.1, and let traffic drain
off an interface.  This is the standard operational practice.

Graceful shutdown and Shutdown Communication could be used, but they're
new and are arguably overkill in many situations because for the most
part, network flaps are a part of life and people aren't interested in
what's going on in other peoples' networks unless it affects their own.

The point of the ID is that it's about session culling / involuntary
session drops initiated by the IXP Caretaker, and I think we need to
stay on topic in the draft, rather than get bogged down in tangential stuff.

Nick


From nobody Tue Sep 26 10:25:12 2017
Return-Path: <ietf@kuehlewind.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40167132D51 for <gen-art@ietfa.amsl.com>; Tue, 26 Sep 2017 10:25:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.net
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 dJ_m8wsX-kaM for <gen-art@ietfa.amsl.com>; Tue, 26 Sep 2017 10:25:09 -0700 (PDT)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7F6E13334E for <gen-art@ietf.org>; Tue, 26 Sep 2017 10:25:07 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net;  b=BgMMlksCkri+xt59bBYdOSapSjNSkjRZ6YFbZFfRdiORBwfIxRIzo8MVI26ej4Bm8tOxkE158sD29lBKjhZ6UvrywH4apqCFztYDjF1FvMAfZUJj0BwGVjDoUzlzEKIYOq6OP9CZpdsxyKdbrjlnAA3t3k+WT04wbFRmfuhs8lM=; h=Received:Received:Subject:To:References:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language:Content-Transfer-Encoding:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 5937 invoked from network); 26 Sep 2017 19:25:04 +0200
Received: from nb-10510.ethz.ch (HELO ?82.130.103.143?) (82.130.103.143) by kuehlewind.net with ESMTPSA (DHE-RSA-AES128-SHA encrypted, authenticated); 26 Sep 2017 19:25:04 +0200
To: Jari Arkko <jari.arkko@piuha.net>, gen-art@ietf.org
References: <150532764947.30447.10287410957823560223@ietfa.amsl.com>
From: =?UTF-8?Q?Mirja_K=c3=bchlewind?= <ietf@kuehlewind.net>
Message-ID: <7ad84677-2af5-ad4a-b009-77eca6594bfb@kuehlewind.net>
Date: Tue, 26 Sep 2017 19:25:03 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <150532764947.30447.10287410957823560223@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-PPP-Message-ID: <20170926172504.5932.32560@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/zD1E4bJkqniqNtmfGF_bxFoCfas>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-dcrup-dkim-usage-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Sep 2017 17:25:11 -0000

Thanks Jari! I point to your review in my ballot comment because I would also 
like to see a reply!

Mirja


On 13.09.2017 20:34, Jari Arkko wrote:
> Reviewer: Jari Arkko
> Review result: Ready
> 
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
> 
> For more information, please see the FAQ at
> 
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
> 
> Document: draft-ietf-dcrup-dkim-usage-??
> Reviewer: Jari Arkko
> Review Date: 2017-09-13
> IETF LC End Date: 2017-09-13
> IESG Telechat date: Not scheduled for a telechat
> 
> Summary:
> 
> This document defines modern day requirements for the cryptographic
> algorithms used for DKIM.
> 
> The document is well written, short, and sets requirements that are
> quite appropriate.
> 
> I have no comments beyond one small issue/question related to the
> wording of the main requirement.
> 
> Major issues:
> 
> Minor issues:
> 
> The document says:
> 
>     Signers MUST sign using rsa-sha256.  Verifiers MUST verify
>     using rsa-sha256. rsa-sha1 MUST NOT be used for signing or
>     verifying.
> 
> I was slightly surprised by the wording of the middle requirement
> about MUST verify using rsa-sha256.
> 
> Given that new algorithms may be defined in the future (and
> indeed, draft-ietf-dcrup-dkim-crypto already defines some),
> wouldn't a "MUST implement" type wording be more suitable?
> Particularly when the third requirement prohibits the use of
> weak algorithm. With the middle requirement, how could
> any other, future stronger algorithm be used? Or is the idea
> that the definition of those algorithms would update these
> requirements? Or am I missing something?
> 
> Nits/editorial comments:
> 
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art
> 


From nobody Tue Sep 26 11:03:22 2017
Return-Path: <ietf@kuehlewind.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 896941330AE for <gen-art@ietfa.amsl.com>; Tue, 26 Sep 2017 11:03:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.net
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 A2nz-qwEO_3n for <gen-art@ietfa.amsl.com>; Tue, 26 Sep 2017 11:03:18 -0700 (PDT)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2A87132D51 for <gen-art@ietf.org>; Tue, 26 Sep 2017 11:03:17 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net;  b=T0HN9I4+c2y/SQWKEn0vF6+/v69WxkUG0Yqogr+LZxO+SoC0QMv+qtQHmfraN1MAXzps0mATGldizNafspvRO0U8bYs3M6Fxj6C/7v7YHApQFykc41Uru6uAEMHyDT0xkf4VUOfqJ+Ya8dYsEIgAoGfE3Gv/sjDr03c/ThB7/Dg=; h=Received:Received:Subject:To:References:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language:Content-Transfer-Encoding:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 7811 invoked from network); 26 Sep 2017 20:03:15 +0200
Received: from nb-10510.ethz.ch (HELO ?82.130.103.143?) (82.130.103.143) by kuehlewind.net with ESMTPSA (DHE-RSA-AES128-SHA encrypted, authenticated); 26 Sep 2017 20:03:15 +0200
To: Elwyn Davies <elwynd@dial.pipex.com>, gen-art@ietf.org
References: <150611799315.22445.6055168230107378983@ietfa.amsl.com>
From: =?UTF-8?Q?Mirja_K=c3=bchlewind?= <ietf@kuehlewind.net>
Message-ID: <cce7c9c4-9904-43a5-4b28-62117e60201b@kuehlewind.net>
Date: Tue, 26 Sep 2017 20:03:14 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <150611799315.22445.6055168230107378983@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-PPP-Message-ID: <20170926180315.7806.31386@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/jykH8sy-dM6DeR4vHpr7hwDCezQ>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-teas-rsvp-te-scaling-rec-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Sep 2017 18:03:20 -0000

Hi Elwyn,

thanks a lot for the detailed review! I fully agree and have mentioned your 
review in my ballot comments. I really hope they will address it and rewrite 
large parts respectively!

Mirja



On 23.09.2017 00:06, Elwyn Davies wrote:
> Reviewer: Elwyn Davies
> Review result: Not Ready
> 
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
> 
> For more information, please see the FAQ at
> 
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
> 
> Document: draft-ietf-teas-rsvp-te-scaling-rec-06
> Reviewer: Elwyn Davies
> Review Date: 2017-09-22
> IETF LC End Date: 2017-09-22
> IESG Telechat date: 2017-09-28
> 
> Summary: Not ready, primarily because the title and presentation give the
> impression that the content is really a BCP when it isn't.  This conceals the
> considerable amount of tweaking of RFC 2961 functionality and addition of new
> RSVP Capabilities described in the document.  There are also a couple of minor
> issues that need to be sorted out.
> 
> Major issues:
> Title and way proposals are presented:  The document defines two new
> 'capabilities' for RSVP-TE and is indeed (as specified in the document header)
> correctly intended for Standards Track status.  However the title and the whole
> of the meat of the document in Section 2 presents the proposals as
> 'recommendations' which says to me that I am expecting a BCP where a profile of
> available options from existing standards is recommended as the best choice for
> implementation and deployment.  In my opinion, the title would be better as
> something like "Additional Capabilities Designed to Improve the Scalability of
> RSVP-TE Deployments".  Whilst the proposals are based on the techniques in RFC
> 2961, the document *requires* the implementor to conform to rules that were
> optional and constrains configurable values to different ranges in order to be
> able to deliver the capabilities defined in the document as well as defining
> new RSVP extensions modifying some of the behaviour defined in RFC 2961.  Thus
> although some of the rules could be met by choosing particular values within
> the RFC 2961 set, the use of MUST, tweaking of functionality and variation of
> ranges takes it well beyond a set of recommendations for RFC 2961 options
> selections.  In view of this Section 1 needs to be written as an introduction
> to the definitions of the new capabilities rather than advocacy for selection
> of RFC 2961 options and the implication that the techniques mentioned in the
> last paragraph of s1 are just a matter of selecting a profile of option values.
>   In actuality new protocol values are introduced and ss2.2 and 2.3 define novel
> extensions to RSVP beyond what is available for RFC 2961 and requiring
> modification to basic RFC 2961 functionality..
> 
> Minor issues:
> Interaction with RFC 5063:  The document does not explicitly state that an
> implementation would need to support (at least) the extra capability obect
> defined in s4.2 of RFC 5063.  Some words about interaction with RFC 5063 are
> probably required in that s4.2.1 of RFC 5063 rather assumes that if there is a
> capability object, by default its S bit will be set.
> 
> Behaviour if a node stops setting Refresh-Reduction-Capable bit:  The last para
> of s2 in RFC 2961 discusses behaviour if a node stops setting this bit in
> messages.  What would happen with the extensions defined in this document if
> this happened while either of the extensions is in use?  As a matter of
> interest, if a peer offers the capabilities defined in this draft, is it
> possible or sensible for it to stop setting the Refresh-Reduction-Capable bit
> without stopping offering the extensions?
> 
> s2.1.3, para 2: As specified, it appears that the 'slower timer' transmission
> of Path and Resv messages can go on indefinitely if no ack arrives.  What puts
> an end to this repetition?  [It may be that I have forgotten how basic RSVP
> works, but since this is altering the behaviour it would be good to explain how
> it terminates, and whether this requires any additional modification to timers.]
> 
> Nits/editorial comments:
> Abstract: RSVP-TE is not a 'well-known' abbreviation: s/RSVP-TE/RSVP Traffic
> Engineering (RSVP-TE)/
> 
> Abstract and s1, first para:  This para is not future proof.  Suggest:
> OLD:
>     The scale at which RSVP-TE [RFC3209] Label Switched Paths (LSPs) get
>     deployed is growing continually and there is considerable onus on
>     RSVP-TE implementations across the board to keep up with this
>     increasing demand in scale.
> NEW:
>     At the time of writing, networks which utilise RSVP Traffic Engineering
>     (RSVP-TE) [RFC3209] Label Switched Paths (LSPs) are encountering limitations
>     in the ability of implementations to support the growth in the number of LSPs
>     deployed.  This document defines two additional RSVP-TE extensions that
>     are intended to reduce the number of messages needed to maintain RSVP-TE
>     soft state in routers and hence allow implementations to support larger
>     scale deployments.
> ENDS
> Note:  Omit reference from Abstract.
> 
> s1, para 2: s/under certain/beyond a certain/
> 
> s1, para 3: s/makes a set of concrete implementation recommendations/defines
> two extensions/; s/- push higher/by increasing/; s/maintain LSP state./maintain
> LSP state by reducing the number of messages needed./
> 
> Abstract, para 2 and s1, last para:  [Omit reference from Abstract]
> OLD:
>     This document advocates the use of a couple of techniques - "Refresh-
>     Interval Independent RSVP (RI-RSVP)" and "Per-Peer Flow-Control" -
>     for significantly cutting down the amount of processing cycles
>     required to maintain LSP state.
> NEW:
>     This document defines two RSVP Capabilities [RFC5063] "Refresh-
>     Interval Independent RSVP (RI-RSVP)" and "Per-Peer Flow-Control"
>     that will cut down the number of messsages and processing cycles
>     required to maintain LSP state.
> ENDS
> 
> s1, last para: Add new penultimate sentence:
>     Note that the "Per-Peer Flow-Control" capability requires the "RI-RSVP"
>     capability as a prerequisite.
> 
> s1, last para: s/RECOMMENDED/recommended/ - this isn't a recommendation about
> the protocol on the wire.
> 
> Subdivision of s2:  The issues regarding the nature of the document would be
> helped by altering s2 into four top level sections, thus: s2: Requirement for
> RFC 2961 Refresh Overhead Reduction Support and Specific Option Choices (from
> s2.1) s3: Requirement for RFC 5063 Capability Object support (see Minor Issues
> above) s4: Refresh-Interval Independent RSVP Capability (from s2.3) s5:
> Per-Peer RSVP Flow Control Capability (from s2.4) Subsequent major sections
> then renumbered as s6 onwards. References to s2.x will need to be updated
> throughout.
> 
> s2.1 (would be introduction of new s2):
> OLD:
>     The implementation recommendations discussed in this section are
>     based on the proposals made in [RFC2961] and act as prerequisites for
>     implementing the techniques discussed in Sections 2.2 and 2.3.
> 
> NEW:
>     The Capabilities defined in Sections 4 and 5 of this document are based on
>     proposals made in [RFC2961].  Implementations of these Capabilities will
>     need to support the RSVP messages and techniques defined in [RFC2961] as set
>     out in Section 2.1 [was 2.1.1] with
>     some minor modifications and alterations to recommended time intervals and
>     iteration counts as defined in the remainder of this section.
> ENDS
> 
> s2.1.1, title and para 1 [will be s2.1]:
> OLD:
> 2.1.1.  Basic Prerequisites
> 
>     An implementation that supports the techniques discussed in Sections
>     2.2 and 2.3 must meet certain basic prerequisites.
> NEW:
> 2.1.  Required Functionality from RFC 2961 to be Implemented
> 
>     An implementation that supports the capabiities discussed in Sections
>     4 and 5 must provide a large subset of the functionality described
>     in [RFC2961] as follows:
> ENDS
> 
> s2.1.2, para 2 [will be s2.2]: s/techniques discussed in Sections 2.2 and
> 2.3/Capabilities defined in Sections 4 and 5/
> 
> s2.1.2, para 2: s/MESSAGE ID/MESSAGE_ID/
> 
> s2.2, para 1: s/improvement on transmission overhead/improvement of
> transmission overhead/
> 
> s2.2, para 1: s/proposes sufficient recommendations/sets out additional
> requirements/
> 
> s2.2, last bullet: Add a reference to the proposed new Section 3 that discusses
> the Capability object.
> 
> s2.2.1, last para: s/set Refresh-Reduction-Capable bit in common header/set the
> Refresh-Reduction-Capable bit in the common header/
> 
> s2.3, para 1: s/set of recommendations/functionality/; s/provide/provides/;
> s/RSVP-TE control plane congestion/a significant portion of the RSVP-TE control
> message load/
> 
> s2.3.2: s/MESSAGE ID/MESSAGE_ID/
> 
> 


From nobody Tue Sep 26 11:26:19 2017
Return-Path: <ietf@kuehlewind.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4ECCE134302 for <gen-art@ietfa.amsl.com>; Tue, 26 Sep 2017 11:26:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.net
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 F5FmkPcg1LMi for <gen-art@ietfa.amsl.com>; Tue, 26 Sep 2017 11:26:17 -0700 (PDT)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD5A01342DD for <gen-art@ietf.org>; Tue, 26 Sep 2017 11:26:16 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net;  b=lh0PezXVXha0XyHXvhIQHu9PHjXjRShTzlUeUOQ7ZK9aMMK16nN8I+00g2nkyO9RCVbekbFCjS6asoeRoD+1ZcedlsEqgnnl3+tZKVQy4HQk9eNsMXBbOPqWCLEk+CkRQK6hkDnzXedrY3L59EhPclnaC9RfcOwVRja1W4LoMFs=; h=Received:Received:Subject:To:References:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language:Content-Transfer-Encoding:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 9320 invoked from network); 26 Sep 2017 20:26:14 +0200
Received: from nb-10510.ethz.ch (HELO ?82.130.103.143?) (82.130.103.143) by kuehlewind.net with ESMTPSA (DHE-RSA-AES128-SHA encrypted, authenticated); 26 Sep 2017 20:26:14 +0200
To: Stewart Bryant <stewart.bryant@gmail.com>, gen-art@ietf.org
References: <150590497937.29233.14546248725198048319@ietfa.amsl.com>
From: =?UTF-8?Q?Mirja_K=c3=bchlewind?= <ietf@kuehlewind.net>
Message-ID: <df646798-11d6-74c9-0ec9-8df32992ed8f@kuehlewind.net>
Date: Tue, 26 Sep 2017 20:26:14 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <150590497937.29233.14546248725198048319@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-PPP-Message-ID: <20170926182614.9315.74230@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Q_sjmIwmB8-67pLcLsGBv5u9TtU>
Subject: Re: [Gen-art] Genart last call review of draft-kille-ldap-xmpp-schema-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Sep 2017 18:26:18 -0000

Thanks for the review!


On 20.09.2017 12:56, Stewart Bryant wrote:
> Reviewer: Stewart Bryant
> Review result: Ready with Nits
> 
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
> 
> For more information, please see the FAQ at
> 
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
> 
> Document: draft-kille-ldap-xmpp-schema-05
> Reviewer: Stewart Bryant
> Review Date: 2017-09-20
> IETF LC End Date: 2017-09-27
> IESG Telechat date: Not scheduled for a telechat
> 
> Summary: A well written document, however it uses an example email address that
> might be allocated in the future, rather than one for the example range.
> 
> Major issues: None
> 
> Minor issues:
> 
> "romeo@shakespeare.lit representing a user)"
> 
> That is a really cool example! However I can imagine .lit eventually being
> allocated so we ought to use one of the RFC6761 example TLDs.
> 
> Nits/editorial comments:  None
> 
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art
> 


From nobody Wed Sep 27 01:59:47 2017
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C9891347F1; Wed, 27 Sep 2017 01:59:46 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Roni Even <ron.even.tlv@gmail.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-rtgwg-uloop-delay.all@ietf.org, ietf@ietf.org, rtgwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.62.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150650278635.25015.9033751036427955769@ietfa.amsl.com>
Date: Wed, 27 Sep 2017 01:59:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/preRR4LzBvOvI_nVKKQcQ4_DDMA>
Subject: [Gen-art] Genart last call review of draft-ietf-rtgwg-uloop-delay-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Sep 2017 08:59:46 -0000

Reviewer: Roni Even
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-rtgwg-uloop-delay-??
Reviewer: Roni Even
Review Date: 2017-09-27
IETF LC End Date: 2017-10-04
IESG Telechat date: 2017-10-12

Summary:
The document is ready for publication as a standard track RFC with nits

Major issues:

Minor issues:

Nits/editorial comments:

1. Abbreviation like RIB and FIB are not expanded
2. In section 9.1 "more simple" should be "simpler"
3. In section 9.1 " does not enough provide enough bandwidth"  to " does not
provide enough bandwidth" 4. In section 9.2 "a mechanism where the convergence
of the  network upon a topology change is made ordered to prevent transient
forwarding loops"  is difficult to read maybe "a mechanism where the
convergence of the network upon a topology change is ordered in order to
prevent transient forwarding loops"



From nobody Wed Sep 27 03:34:36 2017
Return-Path: <adrian@olddog.co.uk>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D67C8134684; Wed, 27 Sep 2017 03:34:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
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 ifrivET-MZVn; Wed, 27 Sep 2017 03:34:32 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE5171345AE; Wed, 27 Sep 2017 03:34:31 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id v8RAYSW3009724; Wed, 27 Sep 2017 11:34:29 +0100
Received: from 950129200 (218.122.115.87.dyn.plus.net [87.115.122.218]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id v8RAYPZJ009629 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Sep 2017 11:34:28 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Robert Sparks'" <rjsparks@nostrum.com>, <gen-art@ietf.org>
Cc: <opsawg@ietf.org>, <ietf@ietf.org>, <draft-ietf-opsawg-service-model-explained.all@ietf.org>
References: <150592002817.29335.8762036344417909160@ietfa.amsl.com>
In-Reply-To: <150592002817.29335.8762036344417909160@ietfa.amsl.com>
Date: Wed, 27 Sep 2017 11:34:21 +0100
Message-ID: <040501d3377c$2fc5c940$8f515bc0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQF4nlKXHvtRoZ3nBAUKfDu5BedhnKN9r7SA
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-23354.005
X-TM-AS-Result: No--8.837-10.0-31-10
X-imss-scan-details: No--8.837-10.0-31-10
X-TMASE-MatchedRID: VPleTT1nwdSnykMun0J1wvHkpkyUphL9IfyQNHR2naZXPwnnY5XL5IrJ LtnzLZWOGB47tH/7BLfyXH6dEQg1mv9/CfUC4LZKU+OjsPhIWDj4uJ1REX4MHSgMxnfFXjiIK93 7aFdF5XOoqk9quFGZe5KnBNxYrreWsEBAuoaUqK/5wpfrIJDXe3xKrqNquhWx3ZqGWCMdqrdyE1 VHvQXnDiOP5gi3f9kCkZOl7WKIImq0P2qkGU0XygtuKBGekqUpbGVEmIfjf3vkrMJ0jtvZ6OKyA ydaH0Qo4IM8agKIeKhmvPOgYj6uP3SjCqt066pw
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/v_hr3hcbyytq3UM0_6gLnF4xWd0>
Subject: Re: [Gen-art] [OPSAWG] Genart last call review of draft-ietf-opsawg-service-model-explained-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Sep 2017 10:34:34 -0000

Thanks Robert,

> I don't have text to suggest, but please look at the first bullet of section
5.
> The explanation here was less helpful than the other bullets. Demonstrating
the
> confusion due to the reuse of the word "service" doesn't help clarify the
> confusion. I wonder if there's more conversation that hasn't been captured
that
> this paragraph is alluding to.

Yes, the paragraph is not as clear as it could be. We were trying to distinguish
between different uses of the word "service" where we are primarily interested
in connectivity services achieved by manipulating the network resources, and not
value-added services provided using other resources (compute, storage, ...) that
are reachable over the network.

I have tried to make this a bit clearer.

> (nit) I also suggest raising the level of abstraction in the security
> consideration section where it currently lists authorization, authentication,
> and encryption by speaking initially to what, and calling the how out as a
> detail.

OK

Adrian


From nobody Wed Sep 27 05:26:34 2017
Return-Path: <ietf@kuehlewind.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00098134A5A for <gen-art@ietfa.amsl.com>; Wed, 27 Sep 2017 05:26:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.net
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 4flo4-i2vIRg for <gen-art@ietfa.amsl.com>; Wed, 27 Sep 2017 05:26:31 -0700 (PDT)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 146E51349FA for <gen-art@ietf.org>; Wed, 27 Sep 2017 05:26:30 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net;  b=I2y751+YYTUX8ugZEJ/LiEik0NJbf7Qyncebd9sYWYdBi4I1x3NEw1xbuHxphztcfNxLU/ffT0A8HdktDJ8da+T1Zz2CAxadY2ZXacK2n3AP3jsdkrwxAP8MMrZIb4viIGSyrGTZtJrrZOIHa6nYCC334L6hRE4xYiVPUkOguFw=; h=Received:Received:Subject:To:References:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language:Content-Transfer-Encoding:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 24495 invoked from network); 27 Sep 2017 14:26:28 +0200
Received: from nb-10510.ethz.ch (HELO ?82.130.103.143?) (82.130.103.143) by kuehlewind.net with ESMTPSA (DHE-RSA-AES128-SHA encrypted, authenticated); 27 Sep 2017 14:26:28 +0200
To: Dan Romascanu <dromasca@gmail.com>, gen-art@ietf.org
References: <150583936645.11787.3653434949933737592@ietfa.amsl.com>
From: =?UTF-8?Q?Mirja_K=c3=bchlewind?= <ietf@kuehlewind.net>
Message-ID: <da5fe240-60d0-9fa8-9b76-fe4c78d3cc2f@kuehlewind.net>
Date: Wed, 27 Sep 2017 14:26:28 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <150583936645.11787.3653434949933737592@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-PPP-Message-ID: <20170927122628.24490.24108@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Pakl4McWhmV_gChZAqaN6Tumyy8>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-bier-architecture-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Sep 2017 12:26:33 -0000

Thanks for the review. While the wg is only charter to produce exp RFCs, i 
agree that could be explained in the document as well. Haven commented on 
this in an updated ballot.

Mirja


On 19.09.2017 18:42, Dan Romascanu wrote:
> Reviewer: Dan Romascanu
> Review result: Ready
> 
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
> 
> For more information, please see the FAQ at
> 
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
> 
> Document: draft-ietf-bier-architecture-08
> Reviewer: Dan Romascanu
> Review Date: 2017-09-19
> IETF LC End Date: 2017-09-20
> IESG Telechat date: 2017-09-28
> 
> Summary:
> 
> This document is Ready. I have reviewed the previous version (07) and the
> resulting discussions with the authors and the edits for the current version
> (08) addressed most of the issues raised in the previous review. One single
> issue remains open, it is minor, and concerns more the charter scope. However,
> as it is related to the Experimental status of the document, I am mentioning it
> again. I do not believe it was clarified in the revision or the discussions.
> 
> Major issues:
> 
> Minor issues:
> 
> 1. As the document is targeting 'Experimental' it would be useful to mention
> what is the scope of the experiment. The charter actually says:
> 
> ' The scope of the experiment will be
> documented in the output of the Working Group.'
> 
> Would not the Architecture document be the right place for this? If not, is
> there another document that deals or is planned to define the scope of the
> experiment?
> 
> Nits/editorial comments:
> 
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art
> 


From nobody Wed Sep 27 06:12:26 2017
Return-Path: <stephane.litkowski@orange.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8C07134B8B; Wed, 27 Sep 2017 06:12:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.399
X-Spam-Level: 
X-Spam-Status: No, score=-5.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
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 VimGJk3DYu3R; Wed, 27 Sep 2017 06:12:13 -0700 (PDT)
Received: from relais-inet.orange.com (mta135.mail.business.static.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 873F5134BAD; Wed, 27 Sep 2017 06:09:50 -0700 (PDT)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) by opfednr21.francetelecom.fr (ESMTP service) with ESMTP id AC1D1C06FC; Wed, 27 Sep 2017 15:09:48 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.72]) by opfednr04.francetelecom.fr (ESMTP service) with ESMTP id 7F45B40070; Wed, 27 Sep 2017 15:09:48 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541%19]) with mapi id 14.03.0361.001; Wed, 27 Sep 2017 15:09:48 +0200
From: <stephane.litkowski@orange.com>
To: Roni Even <ron.even.tlv@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-rtgwg-uloop-delay.all@ietf.org" <draft-ietf-rtgwg-uloop-delay.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>,  "rtgwg@ietf.org" <rtgwg@ietf.org>
Thread-Topic: Genart last call review of draft-ietf-rtgwg-uloop-delay-06
Thread-Index: AQHTN275FLcT4GuiukaArZcj5dduU6LItNgg
Date: Wed, 27 Sep 2017 13:09:47 +0000
Message-ID: <15706_1506517788_59CBA31C_15706_105_1_9E32478DFA9976438E7A22F69B08FF921EA8172D@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <150650278635.25015.9033751036427955769@ietfa.amsl.com>
In-Reply-To: <150650278635.25015.9033751036427955769@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.3]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/PDiLD9AKC51iIqoSis69RVLJnZ4>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-rtgwg-uloop-delay-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Sep 2017 13:12:20 -0000

VGhhbmtzIEkgd2lsbCBmaXggaXQgaW4gdGhlIG5leHQgcmV2aXNpb24NCg0KDQotLS0tLU9yaWdp
bmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogUm9uaSBFdmVuIFttYWlsdG86cm9uLmV2ZW4udGx2QGdt
YWlsLmNvbV0gDQpTZW50OiBXZWRuZXNkYXksIFNlcHRlbWJlciAyNywgMjAxNyAxMTowMA0KVG86
IGdlbi1hcnRAaWV0Zi5vcmcNCkNjOiBkcmFmdC1pZXRmLXJ0Z3dnLXVsb29wLWRlbGF5LmFsbEBp
ZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZzsgcnRnd2dAaWV0Zi5vcmcNClN1YmplY3Q6IEdlbmFydCBs
YXN0IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtcnRnd2ctdWxvb3AtZGVsYXktMDYNCg0KUmV2
aWV3ZXI6IFJvbmkgRXZlbg0KUmV2aWV3IHJlc3VsdDogUmVhZHkgd2l0aCBOaXRzDQoNCkkgYW0g
dGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIFRoZSBHZW5lcmFs
IEFyZWEgUmV2aWV3IFRlYW0gKEdlbi1BUlQpIHJldmlld3MgYWxsIElFVEYgZG9jdW1lbnRzIGJl
aW5nIHByb2Nlc3NlZCBieSB0aGUgSUVTRyBmb3IgdGhlIElFVEYgQ2hhaXIuICBQbGVhc2UgdHJl
YXQgdGhlc2UgY29tbWVudHMganVzdCBsaWtlIGFueSBvdGhlciBsYXN0IGNhbGwgY29tbWVudHMu
DQoNCkZvciBtb3JlIGluZm9ybWF0aW9uLCBwbGVhc2Ugc2VlIHRoZSBGQVEgYXQNCg0KPGh0dHBz
Oi8vdHJhYy5pZXRmLm9yZy90cmFjL2dlbi93aWtpL0dlbkFydGZhcT4uDQoNCkRvY3VtZW50OiBk
cmFmdC1pZXRmLXJ0Z3dnLXVsb29wLWRlbGF5LT8/DQpSZXZpZXdlcjogUm9uaSBFdmVuDQpSZXZp
ZXcgRGF0ZTogMjAxNy0wOS0yNw0KSUVURiBMQyBFbmQgRGF0ZTogMjAxNy0xMC0wNA0KSUVTRyBU
ZWxlY2hhdCBkYXRlOiAyMDE3LTEwLTEyDQoNClN1bW1hcnk6DQpUaGUgZG9jdW1lbnQgaXMgcmVh
ZHkgZm9yIHB1YmxpY2F0aW9uIGFzIGEgc3RhbmRhcmQgdHJhY2sgUkZDIHdpdGggbml0cw0KDQpN
YWpvciBpc3N1ZXM6DQoNCk1pbm9yIGlzc3VlczoNCg0KTml0cy9lZGl0b3JpYWwgY29tbWVudHM6
DQoNCjEuIEFiYnJldmlhdGlvbiBsaWtlIFJJQiBhbmQgRklCIGFyZSBub3QgZXhwYW5kZWQgMi4g
SW4gc2VjdGlvbiA5LjEgIm1vcmUgc2ltcGxlIiBzaG91bGQgYmUgInNpbXBsZXIiDQozLiBJbiBz
ZWN0aW9uIDkuMSAiIGRvZXMgbm90IGVub3VnaCBwcm92aWRlIGVub3VnaCBiYW5kd2lkdGgiICB0
byAiIGRvZXMgbm90IHByb3ZpZGUgZW5vdWdoIGJhbmR3aWR0aCIgNC4gSW4gc2VjdGlvbiA5LjIg
ImEgbWVjaGFuaXNtIHdoZXJlIHRoZSBjb252ZXJnZW5jZSBvZiB0aGUgIG5ldHdvcmsgdXBvbiBh
IHRvcG9sb2d5IGNoYW5nZSBpcyBtYWRlIG9yZGVyZWQgdG8gcHJldmVudCB0cmFuc2llbnQgZm9y
d2FyZGluZyBsb29wcyIgIGlzIGRpZmZpY3VsdCB0byByZWFkIG1heWJlICJhIG1lY2hhbmlzbSB3
aGVyZSB0aGUgY29udmVyZ2VuY2Ugb2YgdGhlIG5ldHdvcmsgdXBvbiBhIHRvcG9sb2d5IGNoYW5n
ZSBpcyBvcmRlcmVkIGluIG9yZGVyIHRvIHByZXZlbnQgdHJhbnNpZW50IGZvcndhcmRpbmcgbG9v
cHMiDQoNCg0KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18KCkNlIG1lc3NhZ2UgZXQgc2VzIHBpZWNlcyBqb2ludGVzIHBldXZl
bnQgY29udGVuaXIgZGVzIGluZm9ybWF0aW9ucyBjb25maWRlbnRpZWxsZXMgb3UgcHJpdmlsZWdp
ZWVzIGV0IG5lIGRvaXZlbnQgZG9uYwpwYXMgZXRyZSBkaWZmdXNlcywgZXhwbG9pdGVzIG91IGNv
cGllcyBzYW5zIGF1dG9yaXNhdGlvbi4gU2kgdm91cyBhdmV6IHJlY3UgY2UgbWVzc2FnZSBwYXIg
ZXJyZXVyLCB2ZXVpbGxleiBsZSBzaWduYWxlcgphIGwnZXhwZWRpdGV1ciBldCBsZSBkZXRydWly
ZSBhaW5zaSBxdWUgbGVzIHBpZWNlcyBqb2ludGVzLiBMZXMgbWVzc2FnZXMgZWxlY3Ryb25pcXVl
cyBldGFudCBzdXNjZXB0aWJsZXMgZCdhbHRlcmF0aW9uLApPcmFuZ2UgZGVjbGluZSB0b3V0ZSBy
ZXNwb25zYWJpbGl0ZSBzaSBjZSBtZXNzYWdlIGEgZXRlIGFsdGVyZSwgZGVmb3JtZSBvdSBmYWxz
aWZpZS4gTWVyY2kuCgpUaGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cyBtYXkgY29udGFp
biBjb25maWRlbnRpYWwgb3IgcHJpdmlsZWdlZCBpbmZvcm1hdGlvbiB0aGF0IG1heSBiZSBwcm90
ZWN0ZWQgYnkgbGF3Owp0aGV5IHNob3VsZCBub3QgYmUgZGlzdHJpYnV0ZWQsIHVzZWQgb3IgY29w
aWVkIHdpdGhvdXQgYXV0aG9yaXNhdGlvbi4KSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlbWFp
bCBpbiBlcnJvciwgcGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGFuZCBkZWxldGUgdGhpcyBtZXNz
YWdlIGFuZCBpdHMgYXR0YWNobWVudHMuCkFzIGVtYWlscyBtYXkgYmUgYWx0ZXJlZCwgT3Jhbmdl
IGlzIG5vdCBsaWFibGUgZm9yIG1lc3NhZ2VzIHRoYXQgaGF2ZSBiZWVuIG1vZGlmaWVkLCBjaGFu
Z2VkIG9yIGZhbHNpZmllZC4KVGhhbmsgeW91LgoK


From nobody Wed Sep 27 10:04:01 2017
Return-Path: <ietf@kuehlewind.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96367134E57 for <gen-art@ietfa.amsl.com>; Wed, 27 Sep 2017 10:03:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.net
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 kIDgff1EHPqS for <gen-art@ietfa.amsl.com>; Wed, 27 Sep 2017 10:03:57 -0700 (PDT)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1323E134E52 for <gen-art@ietf.org>; Wed, 27 Sep 2017 10:03:56 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net;  b=WLXqCGeEM9fJ9uu5KcmkiDqwfZjb2uT4MR3IOeok2E7OAAXIDEhMw6a+n0x5LizI9h1POBQbaPUSsgasvtZt3km0fCwSm1uzX81e1F6MqQURtD7qQY2ES0hotS/9yXnZusBHtMJx9UGsB9nwC6btJwo5xD4NBXGMRKO5NBKkVmA=; h=Received:Received:Subject:To:References:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language:Content-Transfer-Encoding:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 5890 invoked from network); 27 Sep 2017 19:03:55 +0200
Received: from nb-10510.ethz.ch (HELO ?82.130.103.143?) (82.130.103.143) by kuehlewind.net with ESMTPSA (DHE-RSA-AES128-SHA encrypted, authenticated); 27 Sep 2017 19:03:54 +0200
To: Dan Romascanu <dromasca@gmail.com>, gen-art@ietf.org
References: <150341604132.6021.14134855950693780483@ietfa.amsl.com>
From: =?UTF-8?Q?Mirja_K=c3=bchlewind?= <ietf@kuehlewind.net>
Message-ID: <20dae0e0-10db-570b-8b1f-0802a566d6ec@kuehlewind.net>
Date: Wed, 27 Sep 2017 19:03:54 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <150341604132.6021.14134855950693780483@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-PPP-Message-ID: <20170927170355.5885.93178@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/oCG9RJRXMH-9TEbKR537nEkE5aY>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-sfc-nsh-19
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Sep 2017 17:03:59 -0000

Hi Dan,

thanks for the review! My understanding is that your comments have all been 
addressed in the mean time, so I didn't note any thing further in my ballot 
position.

Mirja



On 22.08.2017 17:34, Dan Romascanu wrote:
> Reviewer: Dan Romascanu
> Review result: Almost Ready
> 
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
> 
> For more information, please see the FAQ at
> 
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
> 
> Document: draft-ietf-sfc-nsh-19
> Reviewer: Dan Romascanu
> Review Date: 2017-08-22
> IETF LC End Date: 2017-08-25
> IESG Telechat date: 2017-09-14
> 
> Summary:
> 
> This document describes the header (called Network Service Header - NSH) to be
> inserted in packets and frames in order to create packets and frames that
> realize service functions described by other SFC documents. It needs to be read
> in conjunction with RFC 7665 and other documents as the SFC control plane I-D
> in order to make sense of the required functionality. This part of the SFC
> solution seems almost ready, but a few issues mentioned below need in my
> opinion clarification before the document is approved.
> 
> Major issues:
> 
> 1. Section 11.1 claims: 'An IEEE EtherType, 0x894F, has been allocated for
> NSH'. I could not find this value in the tables displayed by the IEEE
> Registration Authority (RAC) - for example at
> http://standards-oui.ieee.org/ethertype/eth.txt. Neither does IANA at
> https://www.iana.org/assignments/ieee-802-numbers/ieee-802-numbers.xhtml (which
> would not be in any case the authoritative source). Can you please indicate the
> source that this is indeed a confirmed IEEE EtherType registration.
> 
> 2. Section 5 refers to ietf-rtgwg-dt-encap which is expired. If I understand
> correctly the status of this work, there is a design team in place in the
> Routing Area created to look at common issues for the different data plane
> encapsulations being discussed in various WGs including SFC. This leaves the
> issue unsettled at this stage and this may be a problem for a standards track
> document. I suggest that first the reference to the expired document is
> removed, second that the issue is marked as 'open' and subject for future work.
> 
> Minor issues:
> 
> 1.  Two values 'Experiment 1' and 'Experiment 2' are defined in section 2.2 and
> 11.2.5 for the Next Protocol. This seems a little odd. Why 2? Why are they
> defined at the end of the range? Maybe there is an explanation for those who
> know the history but for an un-initiated reader or a future implementer this
> seems odd.
> 
> 2. In Section 2.2 I see:
> 
>> All other flag fields, marked U, are unassigned and available for
>     future use, see Section 11.2.1.  Unassigned bits MUST be set to zero
>     upon origination, and MUST be ignored and preserved unmodified by
>     other NSH supporting elements.  Elements which do not understand the
>     meaning of any of these bits MUST NOT modify their actions based on
>     those unknown bits.
> 
> The way the last sentence is written it seems to open the path for elements
> that claim to 'understand' the meaning of some Unassigned bit to modify its
> behavior based upon it. This does not seem good, as at transmission all
> Unassigned bits MUST be set to zero. I would suggest to make the statement
> simpler and just say that at reception all elements MUST NOT modify their
> actions based on these bits.
> 
> 3. In Section 2.2 I see:
> 
>> 0xF - This value is reserved for experimentation and testing, as per
>     [RFC3692].  Implementations not explicitly configured to be part of
>     an experiment SHOULD silently discard packets with MD Type 0xF.
> 
> Why is this a SHOULD and not a MUST?
> 
> 4. I believe that  [I-D.ietf-sfc-control-plane] needs to be a Normative
> Reference. There are several places in the document (e.g. in Section 2.3) where
> this document is referred to describe behavior or actions related to the fields
> of the header.
> 
> 5. The version number has only two bits assigned. Moreover, this document
> reserves already two values without any explanation why (only 00 is mandatory
> to use, as far as I understand). This needs to be explained (maybe 'historical'
> reasons - but unclear for future readers and users) and may be a limitation as
> the protocol develops.
> 
> Nits/editorial comments:
> 
> 1. Please make sure that acronyms are expanded at first occurrence (e.g. ECMP)
> and if necessary appropriate references are being provided.
> 
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art
> 


From nobody Wed Sep 27 14:34:17 2017
Return-Path: <dromasca@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E7D3135105 for <gen-art@ietfa.amsl.com>; Wed, 27 Sep 2017 14:34:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 KNb3rq3DZSjs for <gen-art@ietfa.amsl.com>; Wed, 27 Sep 2017 14:34:13 -0700 (PDT)
Received: from mail-qt0-x234.google.com (mail-qt0-x234.google.com [IPv6:2607:f8b0:400d:c0d::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27A0D135102 for <gen-art@ietf.org>; Wed, 27 Sep 2017 14:34:13 -0700 (PDT)
Received: by mail-qt0-x234.google.com with SMTP id o13so15175970qtf.1 for <gen-art@ietf.org>; Wed, 27 Sep 2017 14:34:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=6rNwEQZ9ELqRzCDYLmWcmK3pIoyo3d1h2ggd4wAKJ8U=; b=EtWKgfgf5DeTknsJm0PLZ4pCw5MKur+qk0o+gThS9kTn5S11lvDftVxcJBq4/CCRUB aAbr+wY3J90xzzNEVwJoZIKW9WbJyLbLEJbS7KC0dR9CkOczk4ravZVVBjrcgB/gj/Be cydRcmnlL0MS5UTMpLq5YLkuQC+s3wSCrKo8JQmXqNzOGu9nqiTr9aT3NH+OB6BYDpdf mf1lyEsjB9mGMIiYyha2bTEvcAakpDS/qSjX+L+0NxjqgLRLk13E38tGXENC3AMxgEdn 6dQR7adjMZsA5zQM6nQ7ycSDZewapdcy3yeRTs7OanaotFzJ0UfXlk995n/8GzWae0JV zheQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=6rNwEQZ9ELqRzCDYLmWcmK3pIoyo3d1h2ggd4wAKJ8U=; b=XpCLIXpyCcnAqo+HxUsO14pknholZ/5/6fm3nIcrLQY/io9moaexqSVXtsXIkUwvSn CUh50kP2ECxkyz7MD482I0uTrG3QldjAW6xsJhz4FoTRRHWPvbKq+Ypsgw5o03e185oS G4z6yxYQHMSpTdwRSbkLN2qbOwhGLF/9NA5hgqc6EHXiYafurRZQRc2NzvgiuonX0i0W +bBiqg+4ya5JfbUk9xXUtri+qrzdaQhXKOgLoDXB2rI3ro++g+zZIx1K4yf/IqRfNeSh Dv7i9dW5bGmYtY3l11cuX4WtfBtMP/vs/Pu4Vv9knHrpzt1zCDs0MLLY0UWIeD1G4+e0 bKdQ==
X-Gm-Message-State: AHPjjUjLaRR5lYVFjBQpFOvCLfm7xTF4iVsZogwu33sewd+L/JH1zEHT FvVguS2z/KAQp00djhu43WRRFeJEUzQYrwKqoos=
X-Google-Smtp-Source: AOwi7QCe9ogeFGS4VJJxIskQJ6+BIwTbng3lBMYtLz3NMBf/CYAylT7jWNOfeBmwcpCXCtvcoyHjRQptDnJEa/2rNnU=
X-Received: by 10.200.34.28 with SMTP id o28mr4197058qto.184.1506548052288; Wed, 27 Sep 2017 14:34:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.35.242 with HTTP; Wed, 27 Sep 2017 14:34:11 -0700 (PDT)
In-Reply-To: <20dae0e0-10db-570b-8b1f-0802a566d6ec@kuehlewind.net>
References: <150341604132.6021.14134855950693780483@ietfa.amsl.com> <20dae0e0-10db-570b-8b1f-0802a566d6ec@kuehlewind.net>
From: Dan Romascanu <dromasca@gmail.com>
Date: Thu, 28 Sep 2017 00:34:11 +0300
Message-ID: <CAFgnS4WxgaFpG+YtDNuebfZ-zwt7VOaHXvL8v_jnA6pBNedhiA@mail.gmail.com>
To: =?UTF-8?Q?Mirja_K=C3=BChlewind?= <ietf@kuehlewind.net>
Cc: gen-art <gen-art@ietf.org>
Content-Type: multipart/alternative; boundary="001a1140f04c7e6b3b055a328d19"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/vV5qr98aP9YuXHzlfvO-WQl4Vw0>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-sfc-nsh-19
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Sep 2017 21:34:16 -0000

--001a1140f04c7e6b3b055a328d19
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Mirja,

Indeed, my concerns were addressed.

Thanks and Regards,

Dan


On Wed, Sep 27, 2017 at 8:03 PM, Mirja K=C3=BChlewind <ietf@kuehlewind.net>
wrote:

> Hi Dan,
>
> thanks for the review! My understanding is that your comments have all
> been addressed in the mean time, so I didn't note any thing further in my
> ballot position.
>
> Mirja
>
>
>
>
> On 22.08.2017 17:34, Dan Romascanu wrote:
>
>> Reviewer: Dan Romascanu
>> Review result: Almost Ready
>>
>> I am the assigned Gen-ART reviewer for this draft. The General Area
>> Review Team (Gen-ART) reviews all IETF documents being processed
>> by the IESG for the IETF Chair.  Please treat these comments just
>> like any other last call comments.
>>
>> For more information, please see the FAQ at
>>
>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>
>> Document: draft-ietf-sfc-nsh-19
>> Reviewer: Dan Romascanu
>> Review Date: 2017-08-22
>> IETF LC End Date: 2017-08-25
>> IESG Telechat date: 2017-09-14
>>
>> Summary:
>>
>> This document describes the header (called Network Service Header - NSH)
>> to be
>> inserted in packets and frames in order to create packets and frames tha=
t
>> realize service functions described by other SFC documents. It needs to
>> be read
>> in conjunction with RFC 7665 and other documents as the SFC control plan=
e
>> I-D
>> in order to make sense of the required functionality. This part of the S=
FC
>> solution seems almost ready, but a few issues mentioned below need in my
>> opinion clarification before the document is approved.
>>
>> Major issues:
>>
>> 1. Section 11.1 claims: 'An IEEE EtherType, 0x894F, has been allocated f=
or
>> NSH'. I could not find this value in the tables displayed by the IEEE
>> Registration Authority (RAC) - for example at
>> http://standards-oui.ieee.org/ethertype/eth.txt. Neither does IANA at
>> https://www.iana.org/assignments/ieee-802-numbers/ieee-802-numbers.xhtml
>> (which
>> would not be in any case the authoritative source). Can you please
>> indicate the
>> source that this is indeed a confirmed IEEE EtherType registration.
>>
>> 2. Section 5 refers to ietf-rtgwg-dt-encap which is expired. If I
>> understand
>> correctly the status of this work, there is a design team in place in th=
e
>> Routing Area created to look at common issues for the different data pla=
ne
>> encapsulations being discussed in various WGs including SFC. This leaves
>> the
>> issue unsettled at this stage and this may be a problem for a standards
>> track
>> document. I suggest that first the reference to the expired document is
>> removed, second that the issue is marked as 'open' and subject for futur=
e
>> work.
>>
>> Minor issues:
>>
>> 1.  Two values 'Experiment 1' and 'Experiment 2' are defined in section
>> 2.2 and
>> 11.2.5 for the Next Protocol. This seems a little odd. Why 2? Why are th=
ey
>> defined at the end of the range? Maybe there is an explanation for those
>> who
>> know the history but for an un-initiated reader or a future implementer
>> this
>> seems odd.
>>
>> 2. In Section 2.2 I see:
>>
>> All other flag fields, marked U, are unassigned and available for
>>>
>>     future use, see Section 11.2.1.  Unassigned bits MUST be set to zero
>>     upon origination, and MUST be ignored and preserved unmodified by
>>     other NSH supporting elements.  Elements which do not understand the
>>     meaning of any of these bits MUST NOT modify their actions based on
>>     those unknown bits.
>>
>> The way the last sentence is written it seems to open the path for
>> elements
>> that claim to 'understand' the meaning of some Unassigned bit to modify
>> its
>> behavior based upon it. This does not seem good, as at transmission all
>> Unassigned bits MUST be set to zero. I would suggest to make the stateme=
nt
>> simpler and just say that at reception all elements MUST NOT modify thei=
r
>> actions based on these bits.
>>
>> 3. In Section 2.2 I see:
>>
>> 0xF - This value is reserved for experimentation and testing, as per
>>>
>>     [RFC3692].  Implementations not explicitly configured to be part of
>>     an experiment SHOULD silently discard packets with MD Type 0xF.
>>
>> Why is this a SHOULD and not a MUST?
>>
>> 4. I believe that  [I-D.ietf-sfc-control-plane] needs to be a Normative
>> Reference. There are several places in the document (e.g. in Section 2.3=
)
>> where
>> this document is referred to describe behavior or actions related to the
>> fields
>> of the header.
>>
>> 5. The version number has only two bits assigned. Moreover, this documen=
t
>> reserves already two values without any explanation why (only 00 is
>> mandatory
>> to use, as far as I understand). This needs to be explained (maybe
>> 'historical'
>> reasons - but unclear for future readers and users) and may be a
>> limitation as
>> the protocol develops.
>>
>> Nits/editorial comments:
>>
>> 1. Please make sure that acronyms are expanded at first occurrence (e.g.
>> ECMP)
>> and if necessary appropriate references are being provided.
>>
>>
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art
>>
>>

--001a1140f04c7e6b3b055a328d19
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div>Hi Mirja,<br><br></div>Indeed, my concerns =
were addressed. <br><br></div>Thanks and Regards,<br><br></div>Dan<br><br><=
/div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Sep =
27, 2017 at 8:03 PM, Mirja K=C3=BChlewind <span dir=3D"ltr">&lt;<a href=3D"=
mailto:ietf@kuehlewind.net" target=3D"_blank">ietf@kuehlewind.net</a>&gt;</=
span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">Hi Dan,<br>
<br>
thanks for the review! My understanding is that your comments have all been=
 addressed in the mean time, so I didn&#39;t note any thing further in my b=
allot position.<br>
<br>
Mirja<div><div class=3D"h5"><br>
<br>
<br>
<br>
On <a href=3D"tel:22.08.2017%2017" value=3D"+12208201717" target=3D"_blank"=
>22.08.2017 17</a>:34, Dan Romascanu wrote:<br>
</div></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><div><div class=3D"h5">
Reviewer: Dan Romascanu<br>
Review result: Almost Ready<br>
<br>
I am the assigned Gen-ART reviewer for this draft. The General Area<br>
Review Team (Gen-ART) reviews all IETF documents being processed<br>
by the IESG for the IETF Chair.=C2=A0 Please treat these comments just<br>
like any other last call comments.<br>
<br>
For more information, please see the FAQ at<br>
<br>
&lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/GenArtfaq" rel=3D"norefe=
rrer" target=3D"_blank">https://trac.ietf.org/trac/ge<wbr>n/wiki/GenArtfaq<=
/a>&gt;.<br>
<br>
Document: draft-ietf-sfc-nsh-19<br>
Reviewer: Dan Romascanu<br>
Review Date: 2017-08-22<br>
IETF LC End Date: 2017-08-25<br>
IESG Telechat date: 2017-09-14<br>
<br>
Summary:<br>
<br>
This document describes the header (called Network Service Header - NSH) to=
 be<br>
inserted in packets and frames in order to create packets and frames that<b=
r>
realize service functions described by other SFC documents. It needs to be =
read<br>
in conjunction with RFC 7665 and other documents as the SFC control plane I=
-D<br>
in order to make sense of the required functionality. This part of the SFC<=
br>
solution seems almost ready, but a few issues mentioned below need in my<br=
>
opinion clarification before the document is approved.<br>
<br>
Major issues:<br>
<br>
1. Section 11.1 claims: &#39;An IEEE EtherType, 0x894F, has been allocated =
for<br>
NSH&#39;. I could not find this value in the tables displayed by the IEEE<b=
r>
Registration Authority (RAC) - for example at<br>
<a href=3D"http://standards-oui.ieee.org/ethertype/eth.txt" rel=3D"noreferr=
er" target=3D"_blank">http://standards-oui.ieee.org/<wbr>ethertype/eth.txt<=
/a>. Neither does IANA at<br>
<a href=3D"https://www.iana.org/assignments/ieee-802-numbers/ieee-802-numbe=
rs.xhtml" rel=3D"noreferrer" target=3D"_blank">https://www.iana.org/assignm=
en<wbr>ts/ieee-802-numbers/ieee-802-<wbr>numbers.xhtml</a> (which<br>
would not be in any case the authoritative source). Can you please indicate=
 the<br>
source that this is indeed a confirmed IEEE EtherType registration.<br>
<br>
2. Section 5 refers to ietf-rtgwg-dt-encap which is expired. If I understan=
d<br>
correctly the status of this work, there is a design team in place in the<b=
r>
Routing Area created to look at common issues for the different data plane<=
br>
encapsulations being discussed in various WGs including SFC. This leaves th=
e<br>
issue unsettled at this stage and this may be a problem for a standards tra=
ck<br>
document. I suggest that first the reference to the expired document is<br>
removed, second that the issue is marked as &#39;open&#39; and subject for =
future work.<br>
<br>
Minor issues:<br>
<br>
1.=C2=A0 Two values &#39;Experiment 1&#39; and &#39;Experiment 2&#39; are d=
efined in section 2.2 and<br>
11.2.5 for the Next Protocol. This seems a little odd. Why 2? Why are they<=
br>
defined at the end of the range? Maybe there is an explanation for those wh=
o<br>
know the history but for an un-initiated reader or a future implementer thi=
s<br>
seems odd.<br>
<br>
2. In Section 2.2 I see:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
All other flag fields, marked U, are unassigned and available for<br>
</blockquote>
=C2=A0 =C2=A0 future use, see Section 11.2.1.=C2=A0 Unassigned bits MUST be=
 set to zero<br>
=C2=A0 =C2=A0 upon origination, and MUST be ignored and preserved unmodifie=
d by<br>
=C2=A0 =C2=A0 other NSH supporting elements.=C2=A0 Elements which do not un=
derstand the<br>
=C2=A0 =C2=A0 meaning of any of these bits MUST NOT modify their actions ba=
sed on<br>
=C2=A0 =C2=A0 those unknown bits.<br>
<br>
The way the last sentence is written it seems to open the path for elements=
<br>
that claim to &#39;understand&#39; the meaning of some Unassigned bit to mo=
dify its<br>
behavior based upon it. This does not seem good, as at transmission all<br>
Unassigned bits MUST be set to zero. I would suggest to make the statement<=
br>
simpler and just say that at reception all elements MUST NOT modify their<b=
r>
actions based on these bits.<br>
<br>
3. In Section 2.2 I see:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
0xF - This value is reserved for experimentation and testing, as per<br>
</blockquote>
=C2=A0 =C2=A0 [RFC3692].=C2=A0 Implementations not explicitly configured to=
 be part of<br>
=C2=A0 =C2=A0 an experiment SHOULD silently discard packets with MD Type 0x=
F.<br>
<br>
Why is this a SHOULD and not a MUST?<br>
<br>
4. I believe that=C2=A0 [I-D.ietf-sfc-control-plane] needs to be a Normativ=
e<br>
Reference. There are several places in the document (e.g. in Section 2.3) w=
here<br>
this document is referred to describe behavior or actions related to the fi=
elds<br>
of the header.<br>
<br>
5. The version number has only two bits assigned. Moreover, this document<b=
r>
reserves already two values without any explanation why (only 00 is mandato=
ry<br>
to use, as far as I understand). This needs to be explained (maybe &#39;his=
torical&#39;<br>
reasons - but unclear for future readers and users) and may be a limitation=
 as<br>
the protocol develops.<br>
<br>
Nits/editorial comments:<br>
<br>
1. Please make sure that acronyms are expanded at first occurrence (e.g. EC=
MP)<br>
and if necessary appropriate references are being provided.<br>
<br>
<br></div></div>
______________________________<wbr>_________________<br>
Gen-art mailing list<br>
<a href=3D"mailto:Gen-art@ietf.org" target=3D"_blank">Gen-art@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/gen-art" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/gen-art</a><=
br>
<br>
</blockquote>
</blockquote></div><br></div>

--001a1140f04c7e6b3b055a328d19--


From nobody Wed Sep 27 19:49:06 2017
Return-Path: <vishnupavan@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91361135269; Wed, 27 Sep 2017 19:48:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 LfGOq7gAvQPe; Wed, 27 Sep 2017 19:48:51 -0700 (PDT)
Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CE421344EC; Wed, 27 Sep 2017 19:48:51 -0700 (PDT)
Received: by mail-it0-x231.google.com with SMTP id c195so600257itb.1; Wed, 27 Sep 2017 19:48:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=DKx5gw3lfrER7aud3O5s2UkbQcte/bGtnceDwoAOqjo=; b=hM7QyxwEbMQ5C8NODsnScSTcajFHRcxORj14WIVxg8sCE3177z+ohzRdjEWwDufRIe 6f6vkRfVk7hOGFITmTlzSSg9x972mT5FatjeljcebdKpKKKBInIUgMOrZCQQrT2rstsT +TA9PRZcTgw/LKp3R+rZTm1v8SiquZGmwt7w+xU+fps95J5iufcPEw+SNC2wWKYp4y7S fTwkGnWiAIyn1BcCumIY64Fz+ShMQYlWYr+lDQh9X6c8AvX1mfZgavhnV7XxfB8ANw93 SzDSs9kl51s5M8dtERg3csmnsK5c/sN9U9LaXakvVqVCiV/dykhMLGaQpl8Y1w3y/oxK YjKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=DKx5gw3lfrER7aud3O5s2UkbQcte/bGtnceDwoAOqjo=; b=fsENiA9l/NozOU0BBuRIJtJS9iTPAB60+ujLYTGvRzNGkgOIIWUpM6nOmVlP4cED3S P5VuNPXSKFKKFr5WAHaUkMlVGgiwB/jbcc0a7JpGFahzi0WpXV1i9ng6AOhlP4Nh82U1 Ps11rcku/wcrT/eytb2YVjoLrOZy8njEeP9SvQZBKGzSeq/BTK8USFbaNhtPLo0TKq+q 0Vin+ikFA+t9AgNT7z3IZeplcxvidAGMieEBoyFWjgICj8Cf7Pf97Ix7BTaX5GdgSQhn 7eIjwiuT8vFWT9UqGK2GWr8KYjirVei0gAzP/G6qeHkC3llOC59GP6y9FkJ8AVUFPGSt hZBQ==
X-Gm-Message-State: AHPjjUhsLzl26ZHJ4ypdX/koQQ5f3s41ujF6YilqUKI0yiIbvqqpf2Oe +xdqECpLz6E/7jkDE47KDysdR6BWvLP2jFl9blg=
X-Google-Smtp-Source: AOwi7QAKOvTL3TrMieWyMqV5XcyXdymMP6fIGHcM4oLFs1iYWrDDMUje2c4ee56S1uB0MeqymHJt5pRHyLZljRXRAPw=
X-Received: by 10.36.140.77 with SMTP id j74mr3593801itd.95.1506566930885; Wed, 27 Sep 2017 19:48:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.7.216 with HTTP; Wed, 27 Sep 2017 19:48:50 -0700 (PDT)
In-Reply-To: <150611799315.22445.6055168230107378983@ietfa.amsl.com>
References: <150611799315.22445.6055168230107378983@ietfa.amsl.com>
From: Vishnu Pavan Beeram <vishnupavan@gmail.com>
Date: Wed, 27 Sep 2017 22:48:50 -0400
Message-ID: <CA+YzgTsbRe7k94WXy6ony_z50=dmQjSK_E-Lmfw4rLTm8BUBHg@mail.gmail.com>
To: Elwyn Davies <elwynd@dial.pipex.com>
Cc: gen-art@ietf.org, draft-ietf-teas-rsvp-te-scaling-rec.all@ietf.org,  ietf <ietf@ietf.org>, "teas@ietf.org" <teas@ietf.org>
Content-Type: multipart/alternative; boundary="001a1145eee8bef9d3055a36f233"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/w-x_Jjd7ABmpZ7TKiTMIaLz9fks>
Subject: Re: [Gen-art] [Teas] Genart last call review of draft-ietf-teas-rsvp-te-scaling-rec-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Sep 2017 02:48:55 -0000

--001a1145eee8bef9d3055a36f233
Content-Type: text/plain; charset="UTF-8"

Elwyn, Hi!

Thanks for the detailed review and the text suggestions. We just posted a
new revision (-07) to address the concerns listed below. Please go through
the new diffs (
https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-rsvp-te-scaling-rec-07)
and let us know if additional changes are required.

Please see inline for further responses (prefixed VPB).

Regards,
-Pavan

On Fri, Sep 22, 2017 at 6:06 PM, Elwyn Davies <elwynd@dial.pipex.com> wrote:

> Reviewer: Elwyn Davies
> Review result: Not Ready
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-ietf-teas-rsvp-te-scaling-rec-06
> Reviewer: Elwyn Davies
> Review Date: 2017-09-22
> IETF LC End Date: 2017-09-22
> IESG Telechat date: 2017-09-28
>
> Summary: Not ready, primarily because the title and presentation give the
> impression that the content is really a BCP when it isn't.  This conceals
> the
> considerable amount of tweaking of RFC 2961 functionality and addition of
> new
> RSVP Capabilities described in the document.  There are also a couple of
> minor
> issues that need to be sorted out.
>
> Major issues:
> Title and way proposals are presented:  The document defines two new
> 'capabilities' for RSVP-TE and is indeed (as specified in the document
> header)
> correctly intended for Standards Track status.  However the title and the
> whole
> of the meat of the document in Section 2 presents the proposals as
> 'recommendations' which says to me that I am expecting a BCP where a
> profile of
> available options from existing standards is recommended as the best
> choice for
> implementation and deployment.  In my opinion, the title would be better as
> something like "Additional Capabilities Designed to Improve the
> Scalability of
> RSVP-TE Deployments".  Whilst the proposals are based on the techniques in
> RFC
> 2961, the document *requires* the implementor to conform to rules that were
> optional and constrains configurable values to different ranges in order
> to be
> able to deliver the capabilities defined in the document as well as
> defining
> new RSVP extensions modifying some of the behaviour defined in RFC 2961.
> Thus
> although some of the rules could be met by choosing particular values
> within
> the RFC 2961 set, the use of MUST, tweaking of functionality and variation
> of
> ranges takes it well beyond a set of recommendations for RFC 2961 options
> selections.  In view of this Section 1 needs to be written as an
> introduction
> to the definitions of the new capabilities rather than advocacy for
> selection
> of RFC 2961 options and the implication that the techniques mentioned in
> the
> last paragraph of s1 are just a matter of selecting a profile of option
> values.
>  In actuality new protocol values are introduced and ss2.2 and 2.3 define
> novel
> extensions to RSVP beyond what is available for RFC 2961 and requiring
> modification to basic RFC 2961 functionality..
>
>
[VPB] We changed the title to "Techniques to Improve the Scalability of
RSVP-TE Deployments". We also tweaked the text in the introduction section
as suggested. Please see if the new set of diffs address the comment above.

Minor issues:
> Interaction with RFC 5063:  The document does not explicitly state that an
> implementation would need to support (at least) the extra capability obect
> defined in s4.2 of RFC 5063.  Some words about interaction with RFC 5063
> are
> probably required in that s4.2.1 of RFC 5063 rather assumes that if there
> is a
> capability object, by default its S bit will be set.
>

[VPB] The CAPABILITY object in RFC5063 is meant for generic use and can be
used even when there are no Graceful Restart extensions in play (even when
no GR flags are set). As far as we can tell, there is nothing in RFC5063
that precludes this. We added a reference to RFC5063 when the new
Capability flags are introduced. Would this be sufficient to address this
concern?


>
> Behaviour if a node stops setting Refresh-Reduction-Capable bit:  The last
> para
> of s2 in RFC 2961 discusses behaviour if a node stops setting this bit in
> messages.  What would happen with the extensions defined in this document
> if
> this happened while either of the extensions is in use?  As a matter of
> interest, if a peer offers the capabilities defined in this draft, is it
> possible or sensible for it to stop setting the Refresh-Reduction-Capable
> bit
> without stopping offering the extensions?
>

[VPB]  If a peer sets the I or F bit in the CAPABILITY object but does not
set the Refresh-Reduction-capable bit, then the corresponding functionality
("RI-RSVP" or "Per-Peer Flow-Control") is not activated for that peer. In
other words, resetting the Refresh-Reduction-Capable bit immediately makes
the node incapable of supporting the two capabilities discussed in this
document. This is covered in Sections 3.1 and 4.1 ( -07 version).


> s2.1.3, para 2: As specified, it appears that the 'slower timer'
> transmission
> of Path and Resv messages can go on indefinitely if no ack arrives.  What
> puts
> an end to this repetition?  [It may be that I have forgotten how basic RSVP
> works, but since this is altering the behaviour it would be good to
> explain how
> it terminates, and whether this requires any additional modification to
> timers.]
>

[VPB]  There is nothing new about Path and Resv messages getting
transmitted indefinitely (this is normal soft-state signaling behavior) --
all that this section does is discuss how these transmissions are paced in
the absence of an ack. The slower timer transmission will go on until
either an ack is received (at which point the regular "refresh interval"
comes into play) or the corresponding LSP instance state is torn down.


> Nits/editorial comments:
> Abstract: RSVP-TE is not a 'well-known' abbreviation: s/RSVP-TE/RSVP
> Traffic
> Engineering (RSVP-TE)/
>

> Abstract and s1, first para:  This para is not future proof.  Suggest:
> OLD:
>    The scale at which RSVP-TE [RFC3209] Label Switched Paths (LSPs) get
>    deployed is growing continually and there is considerable onus on
>    RSVP-TE implementations across the board to keep up with this
>    increasing demand in scale.
> NEW:
>    At the time of writing, networks which utilise RSVP Traffic Engineering
>    (RSVP-TE) [RFC3209] Label Switched Paths (LSPs) are encountering
> limitations
>    in the ability of implementations to support the growth in the number
> of LSPs
>    deployed.  This document defines two additional RSVP-TE extensions that
>    are intended to reduce the number of messages needed to maintain RSVP-TE
>    soft state in routers and hence allow implementations to support larger
>    scale deployments.
> ENDS
> Note:  Omit reference from Abstract.
>
>
[VPB] Fixed in -07

s1, para 2: s/under certain/beyond a certain/
>

[VPB] Fixed in -07


> s1, para 3: s/makes a set of concrete implementation
> recommendations/defines
> two extensions/; s/- push higher/by increasing/; s/maintain LSP
> state./maintain
> LSP state by reducing the number of messages needed./
>
> Abstract, para 2 and s1, last para:  [Omit reference from Abstract]
> OLD:
>    This document advocates the use of a couple of techniques - "Refresh-
>    Interval Independent RSVP (RI-RSVP)" and "Per-Peer Flow-Control" -
>    for significantly cutting down the amount of processing cycles
>    required to maintain LSP state.
> NEW:
>    This document defines two RSVP Capabilities [RFC5063] "Refresh-
>    Interval Independent RSVP (RI-RSVP)" and "Per-Peer Flow-Control"
>    that will cut down the number of messsages and processing cycles
>    required to maintain LSP state.
> ENDS
>

[VPB] Fixed in -07


> s1, last para: Add new penultimate sentence:
>    Note that the "Per-Peer Flow-Control" capability requires the "RI-RSVP"
>    capability as a prerequisite.
>

[VPB] Fixed in -07


> s1, last para: s/RECOMMENDED/recommended/ - this isn't a recommendation
> about
> the protocol on the wire.
>

[VPB] Fixed in -07


> Subdivision of s2:  The issues regarding the nature of the document would
> be
> helped by altering s2 into four top level sections, thus: s2: Requirement
> for
> RFC 2961 Refresh Overhead Reduction Support and Specific Option Choices
> (from
> s2.1) s3: Requirement for RFC 5063 Capability Object support (see Minor
> Issues
> above) s4: Refresh-Interval Independent RSVP Capability (from s2.3) s5:
> Per-Peer RSVP Flow Control Capability (from s2.4) Subsequent major sections
> then renumbered as s6 onwards. References to s2.x will need to be updated
> throughout.
>

[VPB] We subdivided s2 into 3 top level sections. We did not add a separate
section for discussing RFC5063 Capability Object support.


> s2.1 (would be introduction of new s2):
> OLD:
>    The implementation recommendations discussed in this section are
>    based on the proposals made in [RFC2961] and act as prerequisites for
>    implementing the techniques discussed in Sections 2.2 and 2.3.
>
> NEW:
>    The Capabilities defined in Sections 4 and 5 of this document are based
> on
>    proposals made in [RFC2961].  Implementations of these Capabilities will
>    need to support the RSVP messages and techniques defined in [RFC2961]
> as set
>    out in Section 2.1 [was 2.1.1] with
>    some minor modifications and alterations to recommended time intervals
> and
>    iteration counts as defined in the remainder of this section.
> ENDS
>
>
[VPB] Fixed in -07

s2.1.1, title and para 1 [will be s2.1]:
> OLD:
> 2.1.1.  Basic Prerequisites
>
>    An implementation that supports the techniques discussed in Sections
>    2.2 and 2.3 must meet certain basic prerequisites.
> NEW:
> 2.1.  Required Functionality from RFC 2961 to be Implemented
>
>    An implementation that supports the capabiities discussed in Sections
>    4 and 5 must provide a large subset of the functionality described
>    in [RFC2961] as follows:
> ENDS
>

[VPB] Fixed in -07


> s2.1.2, para 2 [will be s2.2]: s/techniques discussed in Sections 2.2 and
> 2.3/Capabilities defined in Sections 4 and 5/
>

[VPB] Fixed in -07


> s2.1.2, para 2: s/MESSAGE ID/MESSAGE_ID/
>

[VPB] Fixed in -07


> s2.2, para 1: s/improvement on transmission overhead/improvement of
> transmission overhead/
>

[VPB] Fixed in -07


> s2.2, para 1: s/proposes sufficient recommendations/sets out additional
> requirements/
>

[VPB] Fixed in -07


> s2.2, last bullet: Add a reference to the proposed new Section 3 that
> discusses
> the Capability object.
>

[VPB] Added a direct reference to RFC5063


> s2.2.1, last para: s/set Refresh-Reduction-Capable bit in common
> header/set the
> Refresh-Reduction-Capable bit in the common header/
>

[VPB] Fixed in -07


> s2.3, para 1: s/set of recommendations/functionality/;
> s/provide/provides/;
> s/RSVP-TE control plane congestion/a significant portion of the RSVP-TE
> control
> message load/
>

[VPB] Fixed in -07


> s2.3.2: s/MESSAGE ID/MESSAGE_ID/
>

[VPB] Fixed in -07


>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>

--001a1145eee8bef9d3055a36f233
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>Elwyn, Hi!</div><div><br></div><div>Thanks for t=
he detailed review and the text suggestions. We just posted a new revision =
(-07) to address the concerns listed below. Please go through the new diffs=
 (<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-teas-rsvp-te-sc=
aling-rec-07">https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-teas-rsvp-te-s=
caling-rec-07</a>) and let us know if additional changes are required.</div=
><div><br></div><div>Please see inline for further responses (prefixed VPB)=
.<br><br></div>Regards,<br></div>-Pavan<br><div class=3D"gmail_extra"><br><=
div class=3D"gmail_quote">On Fri, Sep 22, 2017 at 6:06 PM, Elwyn Davies <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:elwynd@dial.pipex.com" target=3D"_blan=
k">elwynd@dial.pipex.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex">Reviewer: Elwyn Davies<br>
Review result: Not Ready<br>
<br>
I am the assigned Gen-ART reviewer for this draft. The General Area<br>
Review Team (Gen-ART) reviews all IETF documents being processed<br>
by the IESG for the IETF Chair.=C2=A0 Please treat these comments just<br>
like any other last call comments.<br>
<br>
For more information, please see the FAQ at<br>
<br>
&lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/GenArtfaq" rel=3D"norefe=
rrer" target=3D"_blank">https://trac.ietf.org/trac/ge<wbr>n/wiki/GenArtfaq<=
/a>&gt;.<br>
<br>
Document: draft-ietf-teas-rsvp-te-scalin<wbr>g-rec-06<br>
Reviewer: Elwyn Davies<br>
Review Date: 2017-09-22<br>
IETF LC End Date: 2017-09-22<br>
IESG Telechat date: 2017-09-28<br>
<br>
Summary: Not ready, primarily because the title and presentation give the<b=
r>
impression that the content is really a BCP when it isn&#39;t.=C2=A0 This c=
onceals the<br>
considerable amount of tweaking of RFC 2961 functionality and addition of n=
ew<br>
RSVP Capabilities described in the document.=C2=A0 There are also a couple =
of minor<br>
issues that need to be sorted out.<br>
<br>
Major issues:<br>
Title and way proposals are presented:=C2=A0 The document defines two new<b=
r>
&#39;capabilities&#39; for RSVP-TE and is indeed (as specified in the docum=
ent header)<br>
correctly intended for Standards Track status.=C2=A0 However the title and =
the whole<br>
of the meat of the document in Section 2 presents the proposals as<br>
&#39;recommendations&#39; which says to me that I am expecting a BCP where =
a profile of<br>
available options from existing standards is recommended as the best choice=
 for<br>
implementation and deployment.=C2=A0 In my opinion, the title would be bett=
er as<br>
something like &quot;Additional Capabilities Designed to Improve the Scalab=
ility of<br>
RSVP-TE Deployments&quot;.=C2=A0 Whilst the proposals are based on the tech=
niques in RFC<br>
2961, the document *requires* the implementor to conform to rules that were=
<br>
optional and constrains configurable values to different ranges in order to=
 be<br>
able to deliver the capabilities defined in the document as well as definin=
g<br>
new RSVP extensions modifying some of the behaviour defined in RFC 2961.=C2=
=A0 Thus<br>
although some of the rules could be met by choosing particular values withi=
n<br>
the RFC 2961 set, the use of MUST, tweaking of functionality and variation =
of<br>
ranges takes it well beyond a set of recommendations for RFC 2961 options<b=
r>
selections.=C2=A0 In view of this Section 1 needs to be written as an intro=
duction<br>
to the definitions of the new capabilities rather than advocacy for selecti=
on<br>
of RFC 2961 options and the implication that the techniques mentioned in th=
e<br>
last paragraph of s1 are just a matter of selecting a profile of option val=
ues.<br>
=C2=A0In actuality new protocol values are introduced and ss2.2 and 2.3 def=
ine novel<br>
extensions to RSVP beyond what is available for RFC 2961 and requiring<br>
modification to basic RFC 2961 functionality..<br>
<br></blockquote><div><br></div><div>[VPB] We changed the title to &quot;Te=
chniques to Improve the Scalability of RSVP-TE Deployments&quot;. We also t=
weaked the text in the introduction section as suggested. Please see if the=
 new set of diffs address the comment above.<br></div><div> <br></div><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:=
1px solid rgb(204,204,204);padding-left:1ex">
Minor issues:<br>
Interaction with RFC 5063:=C2=A0 The document does not explicitly state tha=
t an<br>
implementation would need to support (at least) the extra capability obect<=
br>
defined in s4.2 of RFC 5063.=C2=A0 Some words about interaction with RFC 50=
63 are<br>
probably required in that s4.2.1 of RFC 5063 rather assumes that if there i=
s a<br>
capability object, by default its S bit will be set.<br></blockquote><div><=
br></div><div>[VPB] The CAPABILITY object in RFC5063 is meant for generic u=
se and can be used even when there are no Graceful Restart extensions in pl=
ay (even when no GR flags are set). As far as we can tell, there is nothing=
 in RFC5063 that precludes this. We added a reference to RFC5063 when the n=
ew Capability flags are introduced. Would this be sufficient to address thi=
s concern?<br></div><div>=C2=A0<br></div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex">
<br>
Behaviour if a node stops setting Refresh-Reduction-Capable bit:=C2=A0 The =
last para<br>
of s2 in RFC 2961 discusses behaviour if a node stops setting this bit in<b=
r>
messages.=C2=A0 What would happen with the extensions defined in this docum=
ent if<br>
this happened while either of the extensions is in use?=C2=A0 As a matter o=
f<br>
interest, if a peer offers the capabilities defined in this draft, is it<br=
>
possible or sensible for it to stop setting the Refresh-Reduction-Capable b=
it<br>
without stopping offering the extensions?<br></blockquote><div><br></div><d=
iv>[VPB]=C2=A0 If a peer sets the I or F bit in the CAPABILITY object but d=
oes not set the Refresh-Reduction-capable bit, then the corresponding funct=
ionality (&quot;RI-RSVP&quot; or &quot;Per-Peer Flow-Control&quot;) is not =
activated for that peer. In other words, resetting the Refresh-Reduction-Ca=
pable bit immediately makes the node incapable of supporting the two capabi=
lities discussed in this document. This is covered in Sections 3.1 and 4.1 =
( -07 version). <br></div><div><br></div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex">
<br>
s2.1.3, para 2: As specified, it appears that the &#39;slower timer&#39; tr=
ansmission<br>
of Path and Resv messages can go on indefinitely if no ack arrives.=C2=A0 W=
hat puts<br>
an end to this repetition?=C2=A0 [It may be that I have forgotten how basic=
 RSVP<br>
works, but since this is altering the behaviour it would be good to explain=
 how<br>
it terminates, and whether this requires any additional modification to tim=
ers.]<br></blockquote><div><br></div><div>[VPB]=C2=A0 There is nothing new =
about Path and Resv messages getting transmitted indefinitely (this is norm=
al soft-state signaling behavior) -- all that this section does is discuss =
how these transmissions are paced in the absence of an ack. The slower time=
r transmission will go on until either an ack is received (at which point t=
he regular &quot;refresh interval&quot; comes into play) or the correspondi=
ng LSP instance state is torn down. <br></div><div><br></div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid=
 rgb(204,204,204);padding-left:1ex">
<br>
Nits/editorial comments:<br>
Abstract: RSVP-TE is not a &#39;well-known&#39; abbreviation: s/RSVP-TE/RSV=
P Traffic<br>
Engineering (RSVP-TE)/<br></blockquote><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex">
<br>
Abstract and s1, first para:=C2=A0 This para is not future proof.=C2=A0 Sug=
gest:<br>
OLD:<br>
=C2=A0 =C2=A0The scale at which RSVP-TE [RFC3209] Label Switched Paths (LSP=
s) get<br>
=C2=A0 =C2=A0deployed is growing continually and there is considerable onus=
 on<br>
=C2=A0 =C2=A0RSVP-TE implementations across the board to keep up with this<=
br>
=C2=A0 =C2=A0increasing demand in scale.<br>
NEW:<br>
=C2=A0 =C2=A0At the time of writing, networks which utilise RSVP Traffic En=
gineering<br>
=C2=A0 =C2=A0(RSVP-TE) [RFC3209] Label Switched Paths (LSPs) are encounteri=
ng limitations<br>
=C2=A0 =C2=A0in the ability of implementations to support the growth in the=
 number of LSPs<br>
=C2=A0 =C2=A0deployed.=C2=A0 This document defines two additional RSVP-TE e=
xtensions that<br>
=C2=A0 =C2=A0are intended to reduce the number of messages needed to mainta=
in RSVP-TE<br>
=C2=A0 =C2=A0soft state in routers and hence allow implementations to suppo=
rt larger<br>
=C2=A0 =C2=A0scale deployments.<br>
ENDS<br>
Note:=C2=A0 Omit reference from Abstract.<br>
<br></blockquote><div><br></div><div>[VPB] Fixed in -07</div><div> <br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex">
s1, para 2: s/under certain/beyond a certain/<br></blockquote><div><br></di=
v><div>[VPB] Fixed in -07<br></div><div> <br></div><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2=
04,204);padding-left:1ex">
<br>
s1, para 3: s/makes a set of concrete implementation recommendations/define=
s<br>
two extensions/; s/- push higher/by increasing/; s/maintain LSP state./main=
tain<br>
LSP state by reducing the number of messages needed./<br>
<br>
Abstract, para 2 and s1, last para:=C2=A0 [Omit reference from Abstract]<br=
>
OLD:<br>
=C2=A0 =C2=A0This document advocates the use of a couple of techniques - &q=
uot;Refresh-<br>
=C2=A0 =C2=A0Interval Independent RSVP (RI-RSVP)&quot; and &quot;Per-Peer F=
low-Control&quot; -<br>
=C2=A0 =C2=A0for significantly cutting down the amount of processing cycles=
<br>
=C2=A0 =C2=A0required to maintain LSP state.<br>
NEW:<br>
=C2=A0 =C2=A0This document defines two RSVP Capabilities [RFC5063] &quot;Re=
fresh-<br>
=C2=A0 =C2=A0Interval Independent RSVP (RI-RSVP)&quot; and &quot;Per-Peer F=
low-Control&quot;<br>
=C2=A0 =C2=A0that will cut down the number of messsages and processing cycl=
es<br>
=C2=A0 =C2=A0required to maintain LSP state.<br>
ENDS<br></blockquote><div><br></div><div>[VPB] Fixed in -07<br></div><div> =
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
s1, last para: Add new penultimate sentence:<br>
=C2=A0 =C2=A0Note that the &quot;Per-Peer Flow-Control&quot; capability req=
uires the &quot;RI-RSVP&quot;<br>
=C2=A0 =C2=A0capability as a prerequisite.<br></blockquote><div><br></div><=
div>[VPB] Fixed in -07<br></div><div> <br></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex">
<br>
s1, last para: s/RECOMMENDED/recommended/ - this isn&#39;t a recommendation=
 about<br>
the protocol on the wire.<br></blockquote><div>=C2=A0</div><div>[VPB] Fixed=
 in -07</div><div> <br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex">
<br>
Subdivision of s2:=C2=A0 The issues regarding the nature of the document wo=
uld be<br>
helped by altering s2 into four top level sections, thus: s2: Requirement f=
or<br>
RFC 2961 Refresh Overhead Reduction Support and Specific Option Choices (fr=
om<br>
s2.1) s3: Requirement for RFC 5063 Capability Object support (see Minor Iss=
ues<br>
above) s4: Refresh-Interval Independent RSVP Capability (from s2.3) s5:<br>
Per-Peer RSVP Flow Control Capability (from s2.4) Subsequent major sections=
<br>
then renumbered as s6 onwards. References to s2.x will need to be updated<b=
r>
throughout.<br></blockquote><div><br></div><div>[VPB] We subdivided s2 into=
 3 top level sections. We did not add a separate section for discussing RFC=
5063 Capability Object support.</div><div><br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex">
<br>
s2.1 (would be introduction of new s2):<br>
OLD:<br>
=C2=A0 =C2=A0The implementation recommendations discussed in this section a=
re<br>
=C2=A0 =C2=A0based on the proposals made in [RFC2961] and act as prerequisi=
tes for<br>
=C2=A0 =C2=A0implementing the techniques discussed in Sections 2.2 and 2.3.=
<br>
<br>
NEW:<br>
=C2=A0 =C2=A0The Capabilities defined in Sections 4 and 5 of this document =
are based on<br>
=C2=A0 =C2=A0proposals made in [RFC2961].=C2=A0 Implementations of these Ca=
pabilities will<br>
=C2=A0 =C2=A0need to support the RSVP messages and techniques defined in [R=
FC2961] as set<br>
=C2=A0 =C2=A0out in Section 2.1 [was 2.1.1] with<br>
=C2=A0 =C2=A0some minor modifications and alterations to recommended time i=
ntervals and<br>
=C2=A0 =C2=A0iteration counts as defined in the remainder of this section.<=
br>
ENDS<br>
<br></blockquote><div><br></div><div>[VPB] Fixed in -07<br></div><div> <br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex">
s2.1.1, title and para 1 [will be s2.1]:<br>
OLD:<br>
2.1.1.=C2=A0 Basic Prerequisites<br>
<br>
=C2=A0 =C2=A0An implementation that supports the techniques discussed in Se=
ctions<br>
=C2=A0 =C2=A02.2 and 2.3 must meet certain basic prerequisites.<br>
NEW:<br>
2.1.=C2=A0 Required Functionality from RFC 2961 to be Implemented<br>
<br>
=C2=A0 =C2=A0An implementation that supports the capabiities discussed in S=
ections<br>
=C2=A0 =C2=A04 and 5 must provide a large subset of the functionality descr=
ibed<br>
=C2=A0 =C2=A0in [RFC2961] as follows:<br>
ENDS<br></blockquote><div><br></div><div>[VPB] Fixed in -07<br></div><div> =
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
s2.1.2, para 2 [will be s2.2]: s/techniques discussed in Sections 2.2 and<b=
r>
2.3/Capabilities defined in Sections 4 and 5/<br></blockquote><div><br></di=
v><div>[VPB] Fixed in -07<br></div><div> <br></div><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2=
04,204);padding-left:1ex">
<br>
s2.1.2, para 2: s/MESSAGE ID/MESSAGE_ID/<br></blockquote><div><br></div><di=
v>[VPB] Fixed in -07<br></div><div> <br></div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20=
4);padding-left:1ex">
<br>
s2.2, para 1: s/improvement on transmission overhead/improvement of<br>
transmission overhead/<br></blockquote><div><br></div><div>[VPB] Fixed in -=
07<br></div><div> <br></div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x">
<br>
s2.2, para 1: s/proposes sufficient recommendations/sets out additional<br>
requirements/<br></blockquote><div><br></div><div>[VPB] Fixed in -07<br></d=
iv><div> <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
s2.2, last bullet: Add a reference to the proposed new Section 3 that discu=
sses<br>
the Capability object.<br></blockquote><div>=C2=A0</div><div>[VPB] Added a =
direct reference to RFC5063</div><div> <br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex">
<br>
s2.2.1, last para: s/set Refresh-Reduction-Capable bit in common header/set=
 the<br>
Refresh-Reduction-Capable bit in the common header/<br></blockquote><div><b=
r></div><div>[VPB] Fixed in -07<br></div><div> <br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">
<br>
s2.3, para 1: s/set of recommendations/functionality/<wbr>; s/provide/provi=
des/;<br>
s/RSVP-TE control plane congestion/a significant portion of the RSVP-TE con=
trol<br>
message load/<br></blockquote><div><br></div><div>[VPB] Fixed in -07<br></d=
iv><div> <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
s2.3.2: s/MESSAGE ID/MESSAGE_ID/<br></blockquote><div><br></div><div>[VPB] =
Fixed in -07<br></div><div> <br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">
<br>
<br>
______________________________<wbr>_________________<br>
Teas mailing list<br>
<a href=3D"mailto:Teas@ietf.org" target=3D"_blank">Teas@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/teas" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/teas</a><br>
</blockquote></div><br></div></div>

--001a1145eee8bef9d3055a36f233--


From nobody Thu Sep 28 13:24:50 2017
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0860412426E for <gen-art@ietf.org>; Thu, 28 Sep 2017 13:24:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jean Mahoney <mahoney@nostrum.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-to: mahoney@nostrum.com
Message-ID: <150663028902.27697.4573542332026542635.idtracker@ietfa.amsl.com>
Date: Thu, 28 Sep 2017 13:24:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/jwXRtcGJC-ymm3chckjshHMXl4M>
Subject: [Gen-art] Review Assignments
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Sep 2017 20:24:49 -0000

Hi all,

The following reviewers have assignments:

For telechat 2017-10-12

Reviewer               Type      LC end     Draft
Vijay Gurbani          Last Call 2017-10-03 draft-ietf-rtgwg-routing-types-14
Wassim Haddad          Last Call 2017-10-06 draft-ietf-mpls-spring-lsp-ping-11
Joel Halpern           Telechat  2017-07-25 draft-ietf-lamps-rfc5280-i18n-update-03 *
Christer Holmberg      Last Call 2017-10-02 draft-ietf-nvo3-mcast-framework-09
Jouni Korhonen         Telechat  2016-10-24 draft-ietf-ccamp-ospf-availability-extension-10 *
Jouni Korhonen         Telechat  2017-07-25 draft-ietf-curdle-cms-eddsa-signatures-07 *
Pete Resnick           Last Call 2017-10-04 draft-ietf-lisp-sec-13

For telechat 2017-10-26

Reviewer               Type      LC end     Draft
Jari Arkko             Last Call 2017-10-11 draft-wu-l3sm-rfc8049bis-05
Meral Shirazipour      Telechat  None       draft-ietf-mile-rolie-09
Dale Worley            Telechat  None       draft-ietf-acme-acme-07
Peter Yee              Telechat  None       draft-ietf-bier-mpls-encapsulation-09

Last calls:

Reviewer               Type      LC end     Draft
Stewart Bryant         Last Call 2017-10-09 draft-ietf-lamps-eai-addresses-15 *
Brian Carpenter        Last Call 2017-10-09 draft-ietf-oauth-discovery-07
Francis Dupont         Last Call 2017-10-16 draft-dawkins-iesg-nomcom-advisor-iaoc-03
Francis Dupont         Last Call 2017-10-09 draft-ietf-curdle-pkix-06
Roni Even              Last Call 2017-10-09 draft-ietf-tsvwg-ieee-802-11-09
Fernando Gont          Last Call 2017-10-12 draft-ietf-sunset4-ipv6-ietf-01
Joel Halpern           Last Call 2017-10-12 draft-ietf-dnssd-hybrid-07
Russ Housley           Last Call 2017-10-12 draft-ietf-anima-voucher-05
Orit Levin             Last Call 2017-09-26 draft-ietf-v6ops-rfc6555bis-04
Matthew Miller         Last Call 2017-10-11 draft-ietf-grow-bgp-gshut-11
Dan Romascanu          Last Call 2017-10-12 draft-ietf-anima-prefix-management-05

* Other revision previously reviewed
** This revision already reviewed

Next in the reviewer rotation:

  Robert Sparks
  Dale Worley
  Peter Yee
  Jari Arkko
  Stewart Bryant
  Brian Carpenter
  Elwyn Davies
  Linda Dunbar
  Francis Dupont
  Roni Even

The LC and Telechat review templates are included below:
-------------------------------------------------------

-- Begin LC Template --
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments: 

-- End LC Template --

-- Begin Telechat Template --
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

-- End Telechat Template --



From nobody Thu Sep 28 13:25:36 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8264212426E; Thu, 28 Sep 2017 13:25:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern <jmh@joelhalpern.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-lamps-rfc5280-i18n-update.all@ietf.org, spasm@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150663032250.27722.15835601633819810120@ietfa.amsl.com>
Date: Thu, 28 Sep 2017 13:25:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Zl1GiMIHZCCukqkg8zXtuCWbY3s>
Subject: [Gen-art] Genart telechat review of draft-ietf-lamps-rfc5280-i18n-update-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Sep 2017 20:25:23 -0000

Reviewer: Joel Halpern
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-lamps-rfc5280-i18n-update-03
Reviewer: Joel Halpern
Review Date: 2017-09-28
IETF LC End Date: 2017-07-25
IESG Telechat date: 2017-10-12

Summary: This document is still ready for publication as a Proposed Standard

Major issues: N/A

Minor issues: N/A

Nits/editorial comments:  N/A



From nobody Fri Sep 29 06:00:53 2017
Return-Path: <pt5947@att.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 663C313292F; Fri, 29 Sep 2017 06:00:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.401
X-Spam-Level: 
X-Spam-Status: No, score=-5.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 6hDEk7pUcAzv; Fri, 29 Sep 2017 06:00:43 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (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 84C9E1344F7; Fri, 29 Sep 2017 06:00:39 -0700 (PDT)
Received: from pps.filterd (m0083689.ppops.net [127.0.0.1]) by m0083689.ppops.net-00191d01. (8.16.0.21/8.16.0.21) with SMTP id v8TCt4uL030100; Fri, 29 Sep 2017 09:00:27 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0083689.ppops.net-00191d01. with ESMTP id 2d9cbbc3tq-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 29 Sep 2017 09:00:27 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v8TD0QIa029816; Fri, 29 Sep 2017 09:00:26 -0400
Received: from mlpi407.sfdc.sbc.com (mlpi407.sfdc.sbc.com [130.9.128.239]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v8TD0GQw029653 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 29 Sep 2017 09:00:22 -0400
Received: from MISOUT7MSGHUBAC.ITServices.sbc.com (MISOUT7MSGHUBAC.itservices.sbc.com [130.9.129.147]) by mlpi407.sfdc.sbc.com (RSA Interceptor); Fri, 29 Sep 2017 13:00:01 GMT
Received: from MISOUT7MSGUSRDG.ITServices.sbc.com ([169.254.7.116]) by MISOUT7MSGHUBAC.ITServices.sbc.com ([130.9.129.147]) with mapi id 14.03.0361.001; Fri, 29 Sep 2017 09:00:00 -0400
From: "TARAPORE, PERCY S" <pt5947@att.com>
To: Toerless Eckert <tte@cs.fau.de>, Christer Holmberg <christer.holmberg@ericsson.com>
CC: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-mboned-interdomain-peering-bcp.all@ietf.org" <draft-ietf-mboned-interdomain-peering-bcp.all@ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-mboned-interdomain-peering-bcp-10
Thread-Index: AQHTLYuJG4rdVgdVy0WnzxTPwflVZKLL6bnw
Date: Fri, 29 Sep 2017 13:00:00 +0000
Message-ID: <ACC789373DA69C4285B9678D0CEBF86F13036B0B@MISOUT7MSGUSRDG.ITServices.sbc.com>
References: <7594FB04B1934943A5C02806D1A2204B56273EEC@ESESSMB102.ericsson.se> <20170914185852.GA27398@faui40p.informatik.uni-erlangen.de>
In-Reply-To: <20170914185852.GA27398@faui40p.informatik.uni-erlangen.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.10.181.234]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-09-29_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1709290185
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/KfvcbE3bNA1PQaT-i6r0FKS-gw4>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-mboned-interdomain-peering-bcp-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Sep 2017 13:00:50 -0000

Hi Christer,

We discussed your first comment and we agree with Toerless's response. We b=
elieve that the intro does express the intent and purpose of this BCP adequ=
ately. Based on your second comment, we have changed the title of Section 4=
 to "Functional Guidelines". The new version has been uploaded.

Thanks for taking the time and effort to read this BCP.

Best wishes,

Percy

-----Original Message-----
From: Toerless Eckert [mailto:tte@cs.fau.de]=20
Sent: Thursday, September 14, 2017 2:59 PM
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: gen-art@ietf.org; draft-ietf-mboned-interdomain-peering-bcp.all@ietf.or=
g
Subject: Re: Gen-ART review of draft-ietf-mboned-interdomain-peering-bcp-10

On Sat, Sep 02, 2017 at 12:16:18PM +0000, Christer Holmberg wrote:
>=20
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on=20
> Gen-ART, please see the FAQ at=20
> <https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__wiki.tools.ietf.o
> rg_area_gen_trac_wiki_GenArtfaq&d=3DDwIBAg&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=
=3D4Z
> 9x1ZAReZp_mJahI6h9bQ&m=3DYk2i9Ji8MOfUjKFN0Jp-3wS1nKYQtvqPqcyy5j0Rc2o&s=3D=
D
> GgoHGkoQq2XyywjloPLLrHgVKLzBLrEJ8qSkNxKa3I&e=3D=20
> <https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__wiki.tools.ietf.o
> rg_area_gen_trac_wiki_GenArtfaq&d=3DDwMFAg&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=
=3D4Z
> 9x1ZAReZp_mJahI6h9bQ&m=3DiIo_51LYIireg4AnsuBoZIWVunRNL9x6ZXHqz5Q2CGc&s=3D=
p
> eDTnfOaiDiT8_m4J-VWJr70Nt0m41lLVGq3yYls12k&e=3D>>
>=20
> Minor Issues:
>=20
> Q1: The Introduction talks about the growing usage of multicast, and the =
it begins the list what the document does. But, what is the background and =
need for the document? Is there a problem? Are there interoperability issue=
s? At the end of the section it is said that ways to improve are identified=
, but it is unclear exactly what needs to be improved. I think it would be =
good to say a few words in the Introduction about the issues and problems.

I am a bit at a loss. This is a BCP, eg: it is meant to document current be=
st practices.
It is not meant to suggest "improvements" for protocols or the like. The ab=
stract and intro do IMHO pretty well stsate the intent and purpose of the d=
oc.=20

Maybe its just surprising to you that there has so far been no document to =
describe how to deploy IP multicast interdomain, especially with the inclus=
ion of of options such as GRE and AMT - and simplifying it by only using SS=
M ??

Or else: Do you have any text to propose ?

> Editorial Issues:
>=20
>=20
>=20
> Q2: The title of section 4 is ?Supporting Functionality?. That seems a li=
ttle strange in my eyes. Supporting functionality of what?
>=20
All the subsections are called "<function-foobar> Guidlines", so how about =
wee call the whole section "Functional Guidelines" ?

Cheers
    Toerless

---
tte@cs.fau.de


From nobody Fri Sep 29 06:25:10 2017
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E95D7134527; Fri, 29 Sep 2017 06:25:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 1YLd8JCCy88Q; Fri, 29 Sep 2017 06:25:07 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (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 9919F132D79; Fri, 29 Sep 2017 06:25:06 -0700 (PDT)
X-AuditID: c1b4fb30-e87ff7000000155f-06-59ce49b0a6cf
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.183.78]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 0C.05.05471.0B94EC95; Fri, 29 Sep 2017 15:25:04 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.6]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.03.0352.000; Fri, 29 Sep 2017 15:25:03 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "TARAPORE, PERCY S" <pt5947@att.com>, Toerless Eckert <tte@cs.fau.de>
CC: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-mboned-interdomain-peering-bcp.all@ietf.org" <draft-ietf-mboned-interdomain-peering-bcp.all@ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-mboned-interdomain-peering-bcp-10
Thread-Index: AdMj5GSgtiZKqgW1ThOTlEwwxRTw9QJlllQAAuXWiAAAB11MAA==
Date: Fri, 29 Sep 2017 13:25:03 +0000
Message-ID: <D5F4259C.22FAB%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B56273EEC@ESESSMB102.ericsson.se> <20170914185852.GA27398@faui40p.informatik.uni-erlangen.de> <ACC789373DA69C4285B9678D0CEBF86F13036B0B@MISOUT7MSGUSRDG.ITServices.sbc.com>
In-Reply-To: <ACC789373DA69C4285B9678D0CEBF86F13036B0B@MISOUT7MSGUSRDG.ITServices.sbc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.7.170905
x-originating-ip: [153.88.183.19]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <102CAB3F97DC2848BFAE8A6E10553BBA@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrIIsWRmVeSWpSXmKPExsUyM2K7n+4Gz3ORBtM261n8vdnCbHH11WcW ix9TV7FZnLv+m9mBxeNl/xxGj5kb3zJ6LFnykymAOYrLJiU1J7MstUjfLoErY/OHe2wFV8Qq Oua8Z21g/CfUxcjJISFgIrH6+i/GLkYuDiGBI4wST+ceYINwFjFK9M3bx9TFyMHBJmAh0f1P G6RBRMBTYsHLtawgNcwCCxgl3u1+wwySEBbwlni2eCUzRJGPxKWlh1kgbCeJI1/+MYLYLAKq Eg9mPwCzeQWsJSZ3drFCLLvNKHF5wmSwBk6BKIk1W6aCFTEKiEl8P7WGCcRmFhCXuPVkPhPE 2QISS/acZ4awRSVePv7HCmKLCuhJbDhxmx0irijR/rSBEaJXR2LB7k9sELa1xMGlLVBxbYll C18zQxwkKHFy5hOWCYzis5Csm4WkfRaS9llI2mchaV/AyLqKUbQ4tTgpN93ISC+1KDO5uDg/ Ty8vtWQTIzAiD275bbCD8eVzx0OMAhyMSjy8Uy3PRQqxJpYVV+YeYpTgYFYS4e12AwrxpiRW VqUW5ccXleakFh9ilOZgURLnddx3IUJIID2xJDU7NbUgtQgmy8TBKdXAGJxjIvdy56XkB/bM 51aEWWfzaXSnBC2IPPQ38/zGwuMzH950coyTvbJ3qmf1O/kcowCznwV7pqvMe+GmdjfhtE54 2ZxMJuZXcue2/EiZeWBXneu63Kmtd3oq5281eav/z0B9AUfehJn5u2XWqR62frcjiT/v3hpG 7uqkf8a8Sjcr2CtUuSoTlViKMxINtZiLihMB4hddusQCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/2AiAWU8_FPwGnZg8DjYmlDgtuRA>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-mboned-interdomain-peering-bcp-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Sep 2017 13:25:10 -0000

Hi,

>We discussed your first comment and we agree with Toerless's response. We
>believe that the intro does express the intent and purpose of this BCP
>adequately. Based on your second comment, we have changed the title of
>Section 4 to "Functional Guidelines". The new version has been uploaded.

Ok. Thanks!

Regards,

Christer


>-----Original Message-----
>From: Toerless Eckert [mailto:tte@cs.fau.de]
>Sent: Thursday, September 14, 2017 2:59 PM
>To: Christer Holmberg <christer.holmberg@ericsson.com>
>Cc: gen-art@ietf.org;
>draft-ietf-mboned-interdomain-peering-bcp.all@ietf.org
>Subject: Re: Gen-ART review of
>draft-ietf-mboned-interdomain-peering-bcp-10
>
>On Sat, Sep 02, 2017 at 12:16:18PM +0000, Christer Holmberg wrote:
>>=20
>>=20
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>> <https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__wiki.tools.ietf.o
>> rg_area_gen_trac_wiki_GenArtfaq&d=3DDwIBAg&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=
=3D4Z
>> 9x1ZAReZp_mJahI6h9bQ&m=3DYk2i9Ji8MOfUjKFN0Jp-3wS1nKYQtvqPqcyy5j0Rc2o&s=
=3DD
>> GgoHGkoQq2XyywjloPLLrHgVKLzBLrEJ8qSkNxKa3I&e=3D
>> <https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__wiki.tools.ietf.o
>> rg_area_gen_trac_wiki_GenArtfaq&d=3DDwMFAg&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=
=3D4Z
>> 9x1ZAReZp_mJahI6h9bQ&m=3DiIo_51LYIireg4AnsuBoZIWVunRNL9x6ZXHqz5Q2CGc&s=
=3Dp
>> eDTnfOaiDiT8_m4J-VWJr70Nt0m41lLVGq3yYls12k&e=3D>>
>>=20
>> Minor Issues:
>>=20
>> Q1: The Introduction talks about the growing usage of multicast, and
>>the it begins the list what the document does. But, what is the
>>background and need for the document? Is there a problem? Are there
>>interoperability issues? At the end of the section it is said that ways
>>to improve are identified, but it is unclear exactly what needs to be
>>improved. I think it would be good to say a few words in the
>>Introduction about the issues and problems.
>
>I am a bit at a loss. This is a BCP, eg: it is meant to document current
>best practices.
>It is not meant to suggest "improvements" for protocols or the like. The
>abstract and intro do IMHO pretty well stsate the intent and purpose of
>the doc.=20
>
>Maybe its just surprising to you that there has so far been no document
>to describe how to deploy IP multicast interdomain, especially with the
>inclusion of of options such as GRE and AMT - and simplifying it by only
>using SSM ??
>
>Or else: Do you have any text to propose ?
>
>> Editorial Issues:
>>=20
>>=20
>>=20
>> Q2: The title of section 4 is ?Supporting Functionality?. That seems a
>>little strange in my eyes. Supporting functionality of what?
>>=20
>All the subsections are called "<function-foobar> Guidlines", so how
>about wee call the whole section "Functional Guidelines" ?
>
>Cheers
>    Toerless
>
>---
>tte@cs.fau.de


From nobody Fri Sep 29 10:50:47 2017
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53D0213337F; Fri, 29 Sep 2017 10:50:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level: 
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
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 ZNP7slYlcV8Y; Fri, 29 Sep 2017 10:50:31 -0700 (PDT)
Received: from a-painless.mh.aa.net.uk (a-painless.mh.aa.net.uk [81.187.30.51]) (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 56775128D0D; Fri, 29 Sep 2017 10:50:31 -0700 (PDT)
Received: from 153.107.2.81.in-addr.arpa ([81.2.107.153] helo=[192.168.0.128]) by a-painless.mh.aa.net.uk with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from <elwynd@dial.pipex.com>) id 1dxzB3-0004et-T6; Fri, 29 Sep 2017 18:34:21 +0100
Date: Fri, 29 Sep 2017 18:34:09 +0100
Message-ID: <8wh65ldo8qkrghsf29x4nukb.1506702288623@email.android.com>
Importance: normal
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Vishnu Pavan Beeram <vishnupavan@gmail.com>
Cc: gen-art@ietf.org, draft-ietf-teas-rsvp-te-scaling-rec.all@ietf.org, ietf <ietf@ietf.org>, "teas@ietf.org" <teas@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.samsung.android.email_154488561075070"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/nBLz6Vy73fupR-WioiFohkY2HmI>
Subject: Re: [Gen-art] [Teas] Genart last call review of draft-ietf-teas-rsvp-te-scaling-rec-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Sep 2017 17:50:39 -0000

----_com.samsung.android.email_154488561075070
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

CgpIaSwgUGF2YW4uCkkndmUgY2hlY2tlZCB0aHJvdWdoIHRoZSBjaGFuZ2VzIGluIC0wNyBhbmQg
SSB0aGluayBhbGwgaXMgZ29vZCBhcyByZWdhcmRzIGZpeGluZyB0aGUgJ21ham9yIGlzc3VlJywg
cmVzdHVjdHVyaW5nIHMyIGFuZCBmaXhpbmcgdGhlIG5pdHMgLSB0aGFua3MuCkxvb2tpbmcgYXQg
dGhlIElFU0cgY29tbWVudHMgSSB0aGluayB5b3UgaGF2ZSBjb3ZlcmVkIG1vc3Qgb2YgdGhlbcKg
IGV4Y2VwdCBpdCB3b3VsZCBiZSBnb29kIHRvIHB1dCBhIHBvaW50ZXIgdG8gQXBwZW5kaXggQSBp
bnRvIHRoZSBpbnRybyBvZiBzMi7CoApXaXRoIHJlZmVyZW5jZSB0byBBcHBlbmRpeCBBKGQpLCBp
dCB3b3VsZCBiZSBoZWxwZnVsIHRvIHMvcGVyaW9kaWMgcmV0cmFuc21pc3Npb24gaW50ZXJ2YWwv
UGVyaW9kaWMgUmV0cmFuc21pc3Npb24gSW50ZXJ2YWwvIGFuZCBwb3NzaWJseSBnaXZlIGl0IGEg
bmFtZSAoUnByaSBvciBzb21lIHN1Y2gpwqAgaW4gczIuMyBhbmQgQXBwZW5kaXggQShkKS7CoCBB
ZGRpbmcgdGhlIG5hbWUgb2YgdGhlIGludGVydmFsIGFmdGVyICJyZXRyYW5zbWlzc2lvbiBvZiB0
aGVzZSBvbiBhIHNsb3dlciB0aW1lciIgbWlndCBtYWsgaXQgY2xlYXJlciBhbHNvLgpIb3dldmVy
LMKgIEkgdGhpbmsgeW91IHN0aWxsIG5lZWQgdG8gYWRkcmVzcyBhbGwgdGhyZWUgb2YgdGhlIG1p
bm9yIGlzc3VlczotIENhcGFiaWxpdHkgb2JqZWN0OsKgIEEgJ2Jhc2ljJyBpbXBsZW1lbnRhdGlv
biBvZiBSRkMgMjIwOS9SRkMzMjA5IHdpbGwgbm90IGluY2x1ZGUgdGhlIFJGQzUwNjMgZXh0ZW5z
aW9ucy7CoCBJIHRoaW5rIHlvdSBzaG91bGQgdGhlcmVmb3JlIG1ha2UgaXQgZXhwbGljaXQgdGhh
dCBhIHByZXJlcXVpc2l0ZSBmb3IgeW91ciBleHRlbnNpb25zIGlzIGFuIGltcGxlbWVudGF0aW9u
IG9mIHRoZSBDYXBhYmlsaXR5IG9iamVjdCBhcyBzcGVjaWZpZWQgaW4gUkZDNTA2MyAobXkgcHJv
cG9zYWwgZm9yIHMzKSAsIG1ha2luZyBpdCBjbGVhciB0aGF0IHRoaXMgZG9lcyBub3QgcmVxdWly
ZSBhbnkgb2YgdGhlIG90aGVyIGZ1bmN0aW9uYWxpdHkgb2YgUkZDIDUwNjMsIGVzcGVjaWFsbHkg
bm8gc3VwcG9ydCBmb3IgdGhlIFMgYml0IGluIHRoZSBDYXBhYmlsaXRpZXMuLcKgIFlvdXIgcmVz
cG9uc2UgcmVnYXJkaW5nIHdoYXQgaGFwcGVucyBpZiBhIHBlZXIgaW5pdGlhbGx5IGFja25vd2xl
ZGdlcyB0aGF0IGl0IHN1cHBvcnRzIHRoZSBuZXcgY2FwYWJpbGl0aWVzIGJ5IHNldHRpbmcgdGhl
IEkvRiBiaXRzIGluIHRoZSBDYXBhYmlsaXR5IGFuZCBzZW5kcyBzb21lIG1lc3NhZ2VzIHdpdGgg
dGhlIFJlZnJlc2gtUmVkdWN0aW9uLUNhcGFibGUgYml0IHNldCwgYnV0IHRoZW4gc3RvcHMgc2V0
dGluZyB0aGUgUmVmcmVzaC1SZWR1Y3Rpb24tQ2FwYWJsZSBiaXQgZG9lc24ndCByZWFsbHkgYWRk
cmVzcyB0aGUgcHJvYmxlbS7CoCDCoFdvdWxkIHRoaXMgbWVhbiB0aGF0IHRoZSByZWNlaXZlciBz
aG91bGQgYXNzdW1lIHRoYXQgdGhlIHBlZXIgY2FuIG5vIGxvbmdlciBzdXBwb3J0IHRoZSBleHRl
bnNpb25zP8KgIElzIHRoaXMgYSBwZXJtYW5lbnQgc3RhdGUgb3IgY291bGQgdGhlIHBlZXIgc3Rh
cnQgc2V0dGluZyB0aGUgUmVmcmVzaC1SZWR1Y3Rpb24tQ2FwYWJsZSBiaXQgYWdhaW4gYW5kIHJl
c3RvcmUgaW5pdGlhbCBmdW5jdGlvbmFsaXR5IC0gb3Igc2hvdWxkIHRoaXMganVzdCBub3QgYmUg
YWxsb3dlZC4gSSB0aGluayB5b3UgbmVlZCB0byB0aGluayB0aHJvdWdoIHdoYXQgaGFwcGVzIGlu
IHRoZSB2YXJpb3VzIHBvc3NpYmxlIGNhc2VzIGFuZCBleHBsYWluIHdoYXQgYW4gaW1wbGVtZW50
YXRpb24gc2hvdWxkIGRvIGluIGVhY2ggY2FzZS4tIFNvLCBJIGhhdmUgZG9uZSBteSBob21ld29y
ayBhbmQgY2hlY2tlZCBiYWNrIG9uIHdoYXQgaGFwcGVucyB3aGVuIHRoZXJlIGlzIG5vIGFja25v
d2xlZGdlbWVudCBvZiByZWZyZXNoZXMuIFRoZSByZWxldmFudCBwYXJhbWV0ZXIgaXMgdGhlIGNs
ZWFudXAgdGltZS7CoCBIb3dldmVyLCB0aGlzIGxlYXZlcyB1cyB3aXRoIGEgcHJvYmxlbS4uIHRo
ZSBjbGVhbnVwIHRpbWUgaXMgdHlwaWNhbGx5IHNldCBhcyBhIG11bHRpcGxlIG9mIHRoZSByZWZy
ZXNoIGludGVydmFsICg5IHRpbWVzIHNlZW1zIHRvIGJlIHRoZSBkZWZhdWx0KSAtIGluZGVlZCBJ
IHNlZSB0aGF0IHRoZSBpbnRlcmZhY2UgY29uZmlndXJhdGlvbiBvbiBhIEp1bmlwZXIgcm91dGVy
ICghKSBhY3R1YWxseSBzZXRzIGl0IGJ5IGFza2luZyBmb3IgdGhlIG11bHRpcGxlIHJhdGhlciB0
aGFuIGFuIGFic29sdXRlIHZhbHVlLsKgIFd0aCB0aGUgbmV3IGRpc3BlbnNhdGlvbiBpbiB0aHMg
ZG9jdW1lbnQsIHRoZXJlIGFyZSB0d28gdGltZSBwZXJpb2RzIGludm9sdmVkOsKgIEkgdGhpbmsg
eW91IGRvIG5lZWQgdG8gcmVzcGVjaWZ5IGhvdyB0byBjYWxjdWxhdGUgYSBzZW5zaWJsZSBjbGVh
bnVwIGludGVydmFsLCBhbmQgbm90ZSB0aGF0IHRoZSByZXRyYW5zbWlzc2lvbnMgd2lsbCB0aGVu
IGhhbHQgYWZ0ZXIgdGhpcyBpbnRlcnZhbC4KRG9lcyB0aGlzIGxhc3QgbW9kaWZpY2F0aW9uIGNv
bnN0aXR1dGUgYW4gdXBkYXRlIG9mIFJGQyAyMjA5P8KgIEkgYW0gbm90IHN1cmUgLWNvbnN1bHQg
eW91ciBBRCEKUmVnYXJkcyxFbHd5bsKgClNlbnQgZnJvbSBTYW1zdW5nIHRhYmxldC4KLS0tLS0t
LS0gT3JpZ2luYWwgbWVzc2FnZSAtLS0tLS0tLUZyb206IFZpc2hudSBQYXZhbiBCZWVyYW0gPHZp
c2hudXBhdmFuQGdtYWlsLmNvbT4gRGF0ZTogMjgvMDkvMjAxNyAgMDM6NDggIChHTVQrMDA6MDAp
IFRvOiBFbHd5biBEYXZpZXMgPGVsd3luZEBkaWFsLnBpcGV4LmNvbT4gQ2M6IGdlbi1hcnRAaWV0
Zi5vcmcsIGRyYWZ0LWlldGYtdGVhcy1yc3ZwLXRlLXNjYWxpbmctcmVjLmFsbEBpZXRmLm9yZywg
aWV0ZiA8aWV0ZkBpZXRmLm9yZz4sIHRlYXNAaWV0Zi5vcmcgU3ViamVjdDogUmU6IFtUZWFzXSBH
ZW5hcnQgbGFzdCBjYWxsIHJldmlldyBvZiBkcmFmdC1pZXRmLXRlYXMtcnN2cC10ZS1zY2FsaW5n
LXJlYy0wNiAKRWx3eW4sIEhpIQpUaGFua3MgZm9yIHRoZSBkZXRhaWxlZCByZXZpZXcgYW5kIHRo
ZSB0ZXh0IHN1Z2dlc3Rpb25zLiBXZSBqdXN0IHBvc3RlZCBhIG5ldyByZXZpc2lvbiAoLTA3KSB0
byBhZGRyZXNzIHRoZSBjb25jZXJucyBsaXN0ZWQgYmVsb3cuIFBsZWFzZSBnbyB0aHJvdWdoIHRo
ZSBuZXcgZGlmZnMgKGh0dHBzOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1pZXRm
LXRlYXMtcnN2cC10ZS1zY2FsaW5nLXJlYy0wNykgYW5kIGxldCB1cyBrbm93IGlmIGFkZGl0aW9u
YWwgY2hhbmdlcyBhcmUgcmVxdWlyZWQuClBsZWFzZSBzZWUgaW5saW5lIGZvciBmdXJ0aGVyIHJl
c3BvbnNlcyAocHJlZml4ZWQgVlBCKS4KClJlZ2FyZHMsCi1QYXZhbgoKT24gRnJpLCBTZXAgMjIs
IDIwMTcgYXQgNjowNiBQTSwgRWx3eW4gRGF2aWVzIDxlbHd5bmRAZGlhbC5waXBleC5jb20+IHdy
b3RlOgpSZXZpZXdlcjogRWx3eW4gRGF2aWVzCgpSZXZpZXcgcmVzdWx0OiBOb3QgUmVhZHkKCgoK
SSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gVGhlIEdl
bmVyYWwgQXJlYQoKUmV2aWV3IFRlYW0gKEdlbi1BUlQpIHJldmlld3MgYWxsIElFVEYgZG9jdW1l
bnRzIGJlaW5nIHByb2Nlc3NlZAoKYnkgdGhlIElFU0cgZm9yIHRoZSBJRVRGIENoYWlyLsKgIFBs
ZWFzZSB0cmVhdCB0aGVzZSBjb21tZW50cyBqdXN0CgpsaWtlIGFueSBvdGhlciBsYXN0IGNhbGwg
Y29tbWVudHMuCgoKCkZvciBtb3JlIGluZm9ybWF0aW9uLCBwbGVhc2Ugc2VlIHRoZSBGQVEgYXQK
CgoKPGh0dHBzOi8vdHJhYy5pZXRmLm9yZy90cmFjL2dlbi93aWtpL0dlbkFydGZhcT4uCgoKCkRv
Y3VtZW50OiBkcmFmdC1pZXRmLXRlYXMtcnN2cC10ZS1zY2FsaW5nLXJlYy0wNgoKUmV2aWV3ZXI6
IEVsd3luIERhdmllcwoKUmV2aWV3IERhdGU6IDIwMTctMDktMjIKCklFVEYgTEMgRW5kIERhdGU6
IDIwMTctMDktMjIKCklFU0cgVGVsZWNoYXQgZGF0ZTogMjAxNy0wOS0yOAoKCgpTdW1tYXJ5OiBO
b3QgcmVhZHksIHByaW1hcmlseSBiZWNhdXNlIHRoZSB0aXRsZSBhbmQgcHJlc2VudGF0aW9uIGdp
dmUgdGhlCgppbXByZXNzaW9uIHRoYXQgdGhlIGNvbnRlbnQgaXMgcmVhbGx5IGEgQkNQIHdoZW4g
aXQgaXNuJ3QuwqAgVGhpcyBjb25jZWFscyB0aGUKCmNvbnNpZGVyYWJsZSBhbW91bnQgb2YgdHdl
YWtpbmcgb2YgUkZDIDI5NjEgZnVuY3Rpb25hbGl0eSBhbmQgYWRkaXRpb24gb2YgbmV3CgpSU1ZQ
IENhcGFiaWxpdGllcyBkZXNjcmliZWQgaW4gdGhlIGRvY3VtZW50LsKgIFRoZXJlIGFyZSBhbHNv
IGEgY291cGxlIG9mIG1pbm9yCgppc3N1ZXMgdGhhdCBuZWVkIHRvIGJlIHNvcnRlZCBvdXQuCgoK
Ck1ham9yIGlzc3VlczoKClRpdGxlIGFuZCB3YXkgcHJvcG9zYWxzIGFyZSBwcmVzZW50ZWQ6wqAg
VGhlIGRvY3VtZW50IGRlZmluZXMgdHdvIG5ldwoKJ2NhcGFiaWxpdGllcycgZm9yIFJTVlAtVEUg
YW5kIGlzIGluZGVlZCAoYXMgc3BlY2lmaWVkIGluIHRoZSBkb2N1bWVudCBoZWFkZXIpCgpjb3Jy
ZWN0bHkgaW50ZW5kZWQgZm9yIFN0YW5kYXJkcyBUcmFjayBzdGF0dXMuwqAgSG93ZXZlciB0aGUg
dGl0bGUgYW5kIHRoZSB3aG9sZQoKb2YgdGhlIG1lYXQgb2YgdGhlIGRvY3VtZW50IGluIFNlY3Rp
b24gMiBwcmVzZW50cyB0aGUgcHJvcG9zYWxzIGFzCgoncmVjb21tZW5kYXRpb25zJyB3aGljaCBz
YXlzIHRvIG1lIHRoYXQgSSBhbSBleHBlY3RpbmcgYSBCQ1Agd2hlcmUgYSBwcm9maWxlIG9mCgph
dmFpbGFibGUgb3B0aW9ucyBmcm9tIGV4aXN0aW5nIHN0YW5kYXJkcyBpcyByZWNvbW1lbmRlZCBh
cyB0aGUgYmVzdCBjaG9pY2UgZm9yCgppbXBsZW1lbnRhdGlvbiBhbmQgZGVwbG95bWVudC7CoCBJ
biBteSBvcGluaW9uLCB0aGUgdGl0bGUgd291bGQgYmUgYmV0dGVyIGFzCgpzb21ldGhpbmcgbGlr
ZSAiQWRkaXRpb25hbCBDYXBhYmlsaXRpZXMgRGVzaWduZWQgdG8gSW1wcm92ZSB0aGUgU2NhbGFi
aWxpdHkgb2YKClJTVlAtVEUgRGVwbG95bWVudHMiLsKgIFdoaWxzdCB0aGUgcHJvcG9zYWxzIGFy
ZSBiYXNlZCBvbiB0aGUgdGVjaG5pcXVlcyBpbiBSRkMKCjI5NjEsIHRoZSBkb2N1bWVudCAqcmVx
dWlyZXMqIHRoZSBpbXBsZW1lbnRvciB0byBjb25mb3JtIHRvIHJ1bGVzIHRoYXQgd2VyZQoKb3B0
aW9uYWwgYW5kIGNvbnN0cmFpbnMgY29uZmlndXJhYmxlIHZhbHVlcyB0byBkaWZmZXJlbnQgcmFu
Z2VzIGluIG9yZGVyIHRvIGJlCgphYmxlIHRvIGRlbGl2ZXIgdGhlIGNhcGFiaWxpdGllcyBkZWZp
bmVkIGluIHRoZSBkb2N1bWVudCBhcyB3ZWxsIGFzIGRlZmluaW5nCgpuZXcgUlNWUCBleHRlbnNp
b25zIG1vZGlmeWluZyBzb21lIG9mIHRoZSBiZWhhdmlvdXIgZGVmaW5lZCBpbiBSRkMgMjk2MS7C
oCBUaHVzCgphbHRob3VnaCBzb21lIG9mIHRoZSBydWxlcyBjb3VsZCBiZSBtZXQgYnkgY2hvb3Np
bmcgcGFydGljdWxhciB2YWx1ZXMgd2l0aGluCgp0aGUgUkZDIDI5NjEgc2V0LCB0aGUgdXNlIG9m
IE1VU1QsIHR3ZWFraW5nIG9mIGZ1bmN0aW9uYWxpdHkgYW5kIHZhcmlhdGlvbiBvZgoKcmFuZ2Vz
IHRha2VzIGl0IHdlbGwgYmV5b25kIGEgc2V0IG9mIHJlY29tbWVuZGF0aW9ucyBmb3IgUkZDIDI5
NjEgb3B0aW9ucwoKc2VsZWN0aW9ucy7CoCBJbiB2aWV3IG9mIHRoaXMgU2VjdGlvbiAxIG5lZWRz
IHRvIGJlIHdyaXR0ZW4gYXMgYW4gaW50cm9kdWN0aW9uCgp0byB0aGUgZGVmaW5pdGlvbnMgb2Yg
dGhlIG5ldyBjYXBhYmlsaXRpZXMgcmF0aGVyIHRoYW4gYWR2b2NhY3kgZm9yIHNlbGVjdGlvbgoK
b2YgUkZDIDI5NjEgb3B0aW9ucyBhbmQgdGhlIGltcGxpY2F0aW9uIHRoYXQgdGhlIHRlY2huaXF1
ZXMgbWVudGlvbmVkIGluIHRoZQoKbGFzdCBwYXJhZ3JhcGggb2YgczEgYXJlIGp1c3QgYSBtYXR0
ZXIgb2Ygc2VsZWN0aW5nIGEgcHJvZmlsZSBvZiBvcHRpb24gdmFsdWVzLgoKwqBJbiBhY3R1YWxp
dHkgbmV3IHByb3RvY29sIHZhbHVlcyBhcmUgaW50cm9kdWNlZCBhbmQgc3MyLjIgYW5kIDIuMyBk
ZWZpbmUgbm92ZWwKCmV4dGVuc2lvbnMgdG8gUlNWUCBiZXlvbmQgd2hhdCBpcyBhdmFpbGFibGUg
Zm9yIFJGQyAyOTYxIGFuZCByZXF1aXJpbmcKCm1vZGlmaWNhdGlvbiB0byBiYXNpYyBSRkMgMjk2
MSBmdW5jdGlvbmFsaXR5Li4KCgoKW1ZQQl0gV2UgY2hhbmdlZCB0aGUgdGl0bGUgdG8gIlRlY2hu
aXF1ZXMgdG8gSW1wcm92ZSB0aGUgU2NhbGFiaWxpdHkgb2YgUlNWUC1URSBEZXBsb3ltZW50cyIu
IFdlIGFsc28gdHdlYWtlZCB0aGUgdGV4dCBpbiB0aGUgaW50cm9kdWN0aW9uIHNlY3Rpb24gYXMg
c3VnZ2VzdGVkLiBQbGVhc2Ugc2VlIGlmIHRoZSBuZXcgc2V0IG9mIGRpZmZzIGFkZHJlc3MgdGhl
IGNvbW1lbnQgYWJvdmUuCiAKCk1pbm9yIGlzc3VlczoKCkludGVyYWN0aW9uIHdpdGggUkZDIDUw
NjM6wqAgVGhlIGRvY3VtZW50IGRvZXMgbm90IGV4cGxpY2l0bHkgc3RhdGUgdGhhdCBhbgoKaW1w
bGVtZW50YXRpb24gd291bGQgbmVlZCB0byBzdXBwb3J0IChhdCBsZWFzdCkgdGhlIGV4dHJhIGNh
cGFiaWxpdHkgb2JlY3QKCmRlZmluZWQgaW4gczQuMiBvZiBSRkMgNTA2My7CoCBTb21lIHdvcmRz
IGFib3V0IGludGVyYWN0aW9uIHdpdGggUkZDIDUwNjMgYXJlCgpwcm9iYWJseSByZXF1aXJlZCBp
biB0aGF0IHM0LjIuMSBvZiBSRkMgNTA2MyByYXRoZXIgYXNzdW1lcyB0aGF0IGlmIHRoZXJlIGlz
IGEKCmNhcGFiaWxpdHkgb2JqZWN0LCBieSBkZWZhdWx0IGl0cyBTIGJpdCB3aWxsIGJlIHNldC4K
CltWUEJdIFRoZSBDQVBBQklMSVRZIG9iamVjdCBpbiBSRkM1MDYzIGlzIG1lYW50IGZvciBnZW5l
cmljIHVzZSBhbmQgY2FuIGJlIHVzZWQgZXZlbiB3aGVuIHRoZXJlIGFyZSBubyBHcmFjZWZ1bCBS
ZXN0YXJ0IGV4dGVuc2lvbnMgaW4gcGxheSAoZXZlbiB3aGVuIG5vIEdSIGZsYWdzIGFyZSBzZXQp
LiBBcyBmYXIgYXMgd2UgY2FuIHRlbGwsIHRoZXJlIGlzIG5vdGhpbmcgaW4gUkZDNTA2MyB0aGF0
IHByZWNsdWRlcyB0aGlzLiBXZSBhZGRlZCBhIHJlZmVyZW5jZSB0byBSRkM1MDYzIHdoZW4gdGhl
IG5ldyBDYXBhYmlsaXR5IGZsYWdzIGFyZSBpbnRyb2R1Y2VkLiBXb3VsZCB0aGlzIGJlIHN1ZmZp
Y2llbnQgdG8gYWRkcmVzcyB0aGlzIGNvbmNlcm4/CsKgCgoKCkJlaGF2aW91ciBpZiBhIG5vZGUg
c3RvcHMgc2V0dGluZyBSZWZyZXNoLVJlZHVjdGlvbi1DYXBhYmxlIGJpdDrCoCBUaGUgbGFzdCBw
YXJhCgpvZiBzMiBpbiBSRkMgMjk2MSBkaXNjdXNzZXMgYmVoYXZpb3VyIGlmIGEgbm9kZSBzdG9w
cyBzZXR0aW5nIHRoaXMgYml0IGluCgptZXNzYWdlcy7CoCBXaGF0IHdvdWxkIGhhcHBlbiB3aXRo
IHRoZSBleHRlbnNpb25zIGRlZmluZWQgaW4gdGhpcyBkb2N1bWVudCBpZgoKdGhpcyBoYXBwZW5l
ZCB3aGlsZSBlaXRoZXIgb2YgdGhlIGV4dGVuc2lvbnMgaXMgaW4gdXNlP8KgIEFzIGEgbWF0dGVy
IG9mCgppbnRlcmVzdCwgaWYgYSBwZWVyIG9mZmVycyB0aGUgY2FwYWJpbGl0aWVzIGRlZmluZWQg
aW4gdGhpcyBkcmFmdCwgaXMgaXQKCnBvc3NpYmxlIG9yIHNlbnNpYmxlIGZvciBpdCB0byBzdG9w
IHNldHRpbmcgdGhlIFJlZnJlc2gtUmVkdWN0aW9uLUNhcGFibGUgYml0Cgp3aXRob3V0IHN0b3Bw
aW5nIG9mZmVyaW5nIHRoZSBleHRlbnNpb25zPwoKW1ZQQl3CoCBJZiBhIHBlZXIgc2V0cyB0aGUg
SSBvciBGIGJpdCBpbiB0aGUgQ0FQQUJJTElUWSBvYmplY3QgYnV0IGRvZXMgbm90IHNldCB0aGUg
UmVmcmVzaC1SZWR1Y3Rpb24tY2FwYWJsZSBiaXQsIHRoZW4gdGhlIGNvcnJlc3BvbmRpbmcgZnVu
Y3Rpb25hbGl0eSAoIlJJLVJTVlAiIG9yICJQZXItUGVlciBGbG93LUNvbnRyb2wiKSBpcyBub3Qg
YWN0aXZhdGVkIGZvciB0aGF0IHBlZXIuIEluIG90aGVyIHdvcmRzLCByZXNldHRpbmcgdGhlIFJl
ZnJlc2gtUmVkdWN0aW9uLUNhcGFibGUgYml0IGltbWVkaWF0ZWx5IG1ha2VzIHRoZSBub2RlIGlu
Y2FwYWJsZSBvZiBzdXBwb3J0aW5nIHRoZSB0d28gY2FwYWJpbGl0aWVzIGRpc2N1c3NlZCBpbiB0
aGlzIGRvY3VtZW50LiBUaGlzIGlzIGNvdmVyZWQgaW4gU2VjdGlvbnMgMy4xIGFuZCA0LjEgKCAt
MDcgdmVyc2lvbikuIAoKCgoKczIuMS4zLCBwYXJhIDI6IEFzIHNwZWNpZmllZCwgaXQgYXBwZWFy
cyB0aGF0IHRoZSAnc2xvd2VyIHRpbWVyJyB0cmFuc21pc3Npb24KCm9mIFBhdGggYW5kIFJlc3Yg
bWVzc2FnZXMgY2FuIGdvIG9uIGluZGVmaW5pdGVseSBpZiBubyBhY2sgYXJyaXZlcy7CoCBXaGF0
IHB1dHMKCmFuIGVuZCB0byB0aGlzIHJlcGV0aXRpb24/wqAgW0l0IG1heSBiZSB0aGF0IEkgaGF2
ZSBmb3Jnb3R0ZW4gaG93IGJhc2ljIFJTVlAKCndvcmtzLCBidXQgc2luY2UgdGhpcyBpcyBhbHRl
cmluZyB0aGUgYmVoYXZpb3VyIGl0IHdvdWxkIGJlIGdvb2QgdG8gZXhwbGFpbiBob3cKCml0IHRl
cm1pbmF0ZXMsIGFuZCB3aGV0aGVyIHRoaXMgcmVxdWlyZXMgYW55IGFkZGl0aW9uYWwgbW9kaWZp
Y2F0aW9uIHRvIHRpbWVycy5dCgpbVlBCXcKgIFRoZXJlIGlzIG5vdGhpbmcgbmV3IGFib3V0IFBh
dGggYW5kIFJlc3YgbWVzc2FnZXMgZ2V0dGluZyB0cmFuc21pdHRlZCBpbmRlZmluaXRlbHkgKHRo
aXMgaXMgbm9ybWFsIHNvZnQtc3RhdGUgc2lnbmFsaW5nIGJlaGF2aW9yKSAtLSBhbGwgdGhhdCB0
aGlzIHNlY3Rpb24gZG9lcyBpcyBkaXNjdXNzIGhvdyB0aGVzZSB0cmFuc21pc3Npb25zIGFyZSBw
YWNlZCBpbiB0aGUgYWJzZW5jZSBvZiBhbiBhY2suIFRoZSBzbG93ZXIgdGltZXIgdHJhbnNtaXNz
aW9uIHdpbGwgZ28gb24gdW50aWwgZWl0aGVyIGFuIGFjayBpcyByZWNlaXZlZCAoYXQgd2hpY2gg
cG9pbnQgdGhlIHJlZ3VsYXIgInJlZnJlc2ggaW50ZXJ2YWwiIGNvbWVzIGludG8gcGxheSkgb3Ig
dGhlIGNvcnJlc3BvbmRpbmcgTFNQIGluc3RhbmNlIHN0YXRlIGlzIHRvcm4gZG93bi4gCgoKCgpO
aXRzL2VkaXRvcmlhbCBjb21tZW50czoKCkFic3RyYWN0OiBSU1ZQLVRFIGlzIG5vdCBhICd3ZWxs
LWtub3duJyBhYmJyZXZpYXRpb246IHMvUlNWUC1URS9SU1ZQIFRyYWZmaWMKCkVuZ2luZWVyaW5n
IChSU1ZQLVRFKS8KCgoKQWJzdHJhY3QgYW5kIHMxLCBmaXJzdCBwYXJhOsKgIFRoaXMgcGFyYSBp
cyBub3QgZnV0dXJlIHByb29mLsKgIFN1Z2dlc3Q6CgpPTEQ6CgrCoCDCoFRoZSBzY2FsZSBhdCB3
aGljaCBSU1ZQLVRFIFtSRkMzMjA5XSBMYWJlbCBTd2l0Y2hlZCBQYXRocyAoTFNQcykgZ2V0CgrC
oCDCoGRlcGxveWVkIGlzIGdyb3dpbmcgY29udGludWFsbHkgYW5kIHRoZXJlIGlzIGNvbnNpZGVy
YWJsZSBvbnVzIG9uCgrCoCDCoFJTVlAtVEUgaW1wbGVtZW50YXRpb25zIGFjcm9zcyB0aGUgYm9h
cmQgdG8ga2VlcCB1cCB3aXRoIHRoaXMKCsKgIMKgaW5jcmVhc2luZyBkZW1hbmQgaW4gc2NhbGUu
CgpORVc6CgrCoCDCoEF0IHRoZSB0aW1lIG9mIHdyaXRpbmcsIG5ldHdvcmtzIHdoaWNoIHV0aWxp
c2UgUlNWUCBUcmFmZmljIEVuZ2luZWVyaW5nCgrCoCDCoChSU1ZQLVRFKSBbUkZDMzIwOV0gTGFi
ZWwgU3dpdGNoZWQgUGF0aHMgKExTUHMpIGFyZSBlbmNvdW50ZXJpbmcgbGltaXRhdGlvbnMKCsKg
IMKgaW4gdGhlIGFiaWxpdHkgb2YgaW1wbGVtZW50YXRpb25zIHRvIHN1cHBvcnQgdGhlIGdyb3d0
aCBpbiB0aGUgbnVtYmVyIG9mIExTUHMKCsKgIMKgZGVwbG95ZWQuwqAgVGhpcyBkb2N1bWVudCBk
ZWZpbmVzIHR3byBhZGRpdGlvbmFsIFJTVlAtVEUgZXh0ZW5zaW9ucyB0aGF0CgrCoCDCoGFyZSBp
bnRlbmRlZCB0byByZWR1Y2UgdGhlIG51bWJlciBvZiBtZXNzYWdlcyBuZWVkZWQgdG8gbWFpbnRh
aW4gUlNWUC1URQoKwqAgwqBzb2Z0IHN0YXRlIGluIHJvdXRlcnMgYW5kIGhlbmNlIGFsbG93IGlt
cGxlbWVudGF0aW9ucyB0byBzdXBwb3J0IGxhcmdlcgoKwqAgwqBzY2FsZSBkZXBsb3ltZW50cy4K
CkVORFMKCk5vdGU6wqAgT21pdCByZWZlcmVuY2UgZnJvbSBBYnN0cmFjdC4KCgoKW1ZQQl0gRml4
ZWQgaW4gLTA3IAoKczEsIHBhcmEgMjogcy91bmRlciBjZXJ0YWluL2JleW9uZCBhIGNlcnRhaW4v
CgpbVlBCXSBGaXhlZCBpbiAtMDcKIAoKCgpzMSwgcGFyYSAzOiBzL21ha2VzIGEgc2V0IG9mIGNv
bmNyZXRlIGltcGxlbWVudGF0aW9uIHJlY29tbWVuZGF0aW9ucy9kZWZpbmVzCgp0d28gZXh0ZW5z
aW9ucy87IHMvLSBwdXNoIGhpZ2hlci9ieSBpbmNyZWFzaW5nLzsgcy9tYWludGFpbiBMU1Agc3Rh
dGUuL21haW50YWluCgpMU1Agc3RhdGUgYnkgcmVkdWNpbmcgdGhlIG51bWJlciBvZiBtZXNzYWdl
cyBuZWVkZWQuLwoKCgpBYnN0cmFjdCwgcGFyYSAyIGFuZCBzMSwgbGFzdCBwYXJhOsKgIFtPbWl0
IHJlZmVyZW5jZSBmcm9tIEFic3RyYWN0XQoKT0xEOgoKwqAgwqBUaGlzIGRvY3VtZW50IGFkdm9j
YXRlcyB0aGUgdXNlIG9mIGEgY291cGxlIG9mIHRlY2huaXF1ZXMgLSAiUmVmcmVzaC0KCsKgIMKg
SW50ZXJ2YWwgSW5kZXBlbmRlbnQgUlNWUCAoUkktUlNWUCkiIGFuZCAiUGVyLVBlZXIgRmxvdy1D
b250cm9sIiAtCgrCoCDCoGZvciBzaWduaWZpY2FudGx5IGN1dHRpbmcgZG93biB0aGUgYW1vdW50
IG9mIHByb2Nlc3NpbmcgY3ljbGVzCgrCoCDCoHJlcXVpcmVkIHRvIG1haW50YWluIExTUCBzdGF0
ZS4KCk5FVzoKCsKgIMKgVGhpcyBkb2N1bWVudCBkZWZpbmVzIHR3byBSU1ZQIENhcGFiaWxpdGll
cyBbUkZDNTA2M10gIlJlZnJlc2gtCgrCoCDCoEludGVydmFsIEluZGVwZW5kZW50IFJTVlAgKFJJ
LVJTVlApIiBhbmQgIlBlci1QZWVyIEZsb3ctQ29udHJvbCIKCsKgIMKgdGhhdCB3aWxsIGN1dCBk
b3duIHRoZSBudW1iZXIgb2YgbWVzc3NhZ2VzIGFuZCBwcm9jZXNzaW5nIGN5Y2xlcwoKwqAgwqBy
ZXF1aXJlZCB0byBtYWludGFpbiBMU1Agc3RhdGUuCgpFTkRTCgpbVlBCXSBGaXhlZCBpbiAtMDcK
IAoKCgpzMSwgbGFzdCBwYXJhOiBBZGQgbmV3IHBlbnVsdGltYXRlIHNlbnRlbmNlOgoKwqAgwqBO
b3RlIHRoYXQgdGhlICJQZXItUGVlciBGbG93LUNvbnRyb2wiIGNhcGFiaWxpdHkgcmVxdWlyZXMg
dGhlICJSSS1SU1ZQIgoKwqAgwqBjYXBhYmlsaXR5IGFzIGEgcHJlcmVxdWlzaXRlLgoKW1ZQQl0g
Rml4ZWQgaW4gLTA3CiAKCgoKczEsIGxhc3QgcGFyYTogcy9SRUNPTU1FTkRFRC9yZWNvbW1lbmRl
ZC8gLSB0aGlzIGlzbid0IGEgcmVjb21tZW5kYXRpb24gYWJvdXQKCnRoZSBwcm90b2NvbCBvbiB0
aGUgd2lyZS4KwqBbVlBCXSBGaXhlZCBpbiAtMDcgCgoKClN1YmRpdmlzaW9uIG9mIHMyOsKgIFRo
ZSBpc3N1ZXMgcmVnYXJkaW5nIHRoZSBuYXR1cmUgb2YgdGhlIGRvY3VtZW50IHdvdWxkIGJlCgpo
ZWxwZWQgYnkgYWx0ZXJpbmcgczIgaW50byBmb3VyIHRvcCBsZXZlbCBzZWN0aW9ucywgdGh1czog
czI6IFJlcXVpcmVtZW50IGZvcgoKUkZDIDI5NjEgUmVmcmVzaCBPdmVyaGVhZCBSZWR1Y3Rpb24g
U3VwcG9ydCBhbmQgU3BlY2lmaWMgT3B0aW9uIENob2ljZXMgKGZyb20KCnMyLjEpIHMzOiBSZXF1
aXJlbWVudCBmb3IgUkZDIDUwNjMgQ2FwYWJpbGl0eSBPYmplY3Qgc3VwcG9ydCAoc2VlIE1pbm9y
IElzc3VlcwoKYWJvdmUpIHM0OiBSZWZyZXNoLUludGVydmFsIEluZGVwZW5kZW50IFJTVlAgQ2Fw
YWJpbGl0eSAoZnJvbSBzMi4zKSBzNToKClBlci1QZWVyIFJTVlAgRmxvdyBDb250cm9sIENhcGFi
aWxpdHkgKGZyb20gczIuNCkgU3Vic2VxdWVudCBtYWpvciBzZWN0aW9ucwoKdGhlbiByZW51bWJl
cmVkIGFzIHM2IG9ud2FyZHMuIFJlZmVyZW5jZXMgdG8gczIueCB3aWxsIG5lZWQgdG8gYmUgdXBk
YXRlZAoKdGhyb3VnaG91dC4KCltWUEJdIFdlIHN1YmRpdmlkZWQgczIgaW50byAzIHRvcCBsZXZl
bCBzZWN0aW9ucy4gV2UgZGlkIG5vdCBhZGQgYSBzZXBhcmF0ZSBzZWN0aW9uIGZvciBkaXNjdXNz
aW5nIFJGQzUwNjMgQ2FwYWJpbGl0eSBPYmplY3Qgc3VwcG9ydC4KCgoKczIuMSAod291bGQgYmUg
aW50cm9kdWN0aW9uIG9mIG5ldyBzMik6CgpPTEQ6CgrCoCDCoFRoZSBpbXBsZW1lbnRhdGlvbiBy
ZWNvbW1lbmRhdGlvbnMgZGlzY3Vzc2VkIGluIHRoaXMgc2VjdGlvbiBhcmUKCsKgIMKgYmFzZWQg
b24gdGhlIHByb3Bvc2FscyBtYWRlIGluIFtSRkMyOTYxXSBhbmQgYWN0IGFzIHByZXJlcXVpc2l0
ZXMgZm9yCgrCoCDCoGltcGxlbWVudGluZyB0aGUgdGVjaG5pcXVlcyBkaXNjdXNzZWQgaW4gU2Vj
dGlvbnMgMi4yIGFuZCAyLjMuCgoKCk5FVzoKCsKgIMKgVGhlIENhcGFiaWxpdGllcyBkZWZpbmVk
IGluIFNlY3Rpb25zIDQgYW5kIDUgb2YgdGhpcyBkb2N1bWVudCBhcmUgYmFzZWQgb24KCsKgIMKg
cHJvcG9zYWxzIG1hZGUgaW4gW1JGQzI5NjFdLsKgIEltcGxlbWVudGF0aW9ucyBvZiB0aGVzZSBD
YXBhYmlsaXRpZXMgd2lsbAoKwqAgwqBuZWVkIHRvIHN1cHBvcnQgdGhlIFJTVlAgbWVzc2FnZXMg
YW5kIHRlY2huaXF1ZXMgZGVmaW5lZCBpbiBbUkZDMjk2MV0gYXMgc2V0CgrCoCDCoG91dCBpbiBT
ZWN0aW9uIDIuMSBbd2FzIDIuMS4xXSB3aXRoCgrCoCDCoHNvbWUgbWlub3IgbW9kaWZpY2F0aW9u
cyBhbmQgYWx0ZXJhdGlvbnMgdG8gcmVjb21tZW5kZWQgdGltZSBpbnRlcnZhbHMgYW5kCgrCoCDC
oGl0ZXJhdGlvbiBjb3VudHMgYXMgZGVmaW5lZCBpbiB0aGUgcmVtYWluZGVyIG9mIHRoaXMgc2Vj
dGlvbi4KCkVORFMKCgoKW1ZQQl0gRml4ZWQgaW4gLTA3CiAKCnMyLjEuMSwgdGl0bGUgYW5kIHBh
cmEgMSBbd2lsbCBiZSBzMi4xXToKCk9MRDoKCjIuMS4xLsKgIEJhc2ljIFByZXJlcXVpc2l0ZXMK
CgoKwqAgwqBBbiBpbXBsZW1lbnRhdGlvbiB0aGF0IHN1cHBvcnRzIHRoZSB0ZWNobmlxdWVzIGRp
c2N1c3NlZCBpbiBTZWN0aW9ucwoKwqAgwqAyLjIgYW5kIDIuMyBtdXN0IG1lZXQgY2VydGFpbiBi
YXNpYyBwcmVyZXF1aXNpdGVzLgoKTkVXOgoKMi4xLsKgIFJlcXVpcmVkIEZ1bmN0aW9uYWxpdHkg
ZnJvbSBSRkMgMjk2MSB0byBiZSBJbXBsZW1lbnRlZAoKCgrCoCDCoEFuIGltcGxlbWVudGF0aW9u
IHRoYXQgc3VwcG9ydHMgdGhlIGNhcGFiaWl0aWVzIGRpc2N1c3NlZCBpbiBTZWN0aW9ucwoKwqAg
wqA0IGFuZCA1IG11c3QgcHJvdmlkZSBhIGxhcmdlIHN1YnNldCBvZiB0aGUgZnVuY3Rpb25hbGl0
eSBkZXNjcmliZWQKCsKgIMKgaW4gW1JGQzI5NjFdIGFzIGZvbGxvd3M6CgpFTkRTCgpbVlBCXSBG
aXhlZCBpbiAtMDcKIAoKCgpzMi4xLjIsIHBhcmEgMiBbd2lsbCBiZSBzMi4yXTogcy90ZWNobmlx
dWVzIGRpc2N1c3NlZCBpbiBTZWN0aW9ucyAyLjIgYW5kCgoyLjMvQ2FwYWJpbGl0aWVzIGRlZmlu
ZWQgaW4gU2VjdGlvbnMgNCBhbmQgNS8KCltWUEJdIEZpeGVkIGluIC0wNwogCgoKCnMyLjEuMiwg
cGFyYSAyOiBzL01FU1NBR0UgSUQvTUVTU0FHRV9JRC8KCltWUEJdIEZpeGVkIGluIC0wNwogCgoK
CnMyLjIsIHBhcmEgMTogcy9pbXByb3ZlbWVudCBvbiB0cmFuc21pc3Npb24gb3ZlcmhlYWQvaW1w
cm92ZW1lbnQgb2YKCnRyYW5zbWlzc2lvbiBvdmVyaGVhZC8KCltWUEJdIEZpeGVkIGluIC0wNwog
CgoKCnMyLjIsIHBhcmEgMTogcy9wcm9wb3NlcyBzdWZmaWNpZW50IHJlY29tbWVuZGF0aW9ucy9z
ZXRzIG91dCBhZGRpdGlvbmFsCgpyZXF1aXJlbWVudHMvCgpbVlBCXSBGaXhlZCBpbiAtMDcKIAoK
CgpzMi4yLCBsYXN0IGJ1bGxldDogQWRkIGEgcmVmZXJlbmNlIHRvIHRoZSBwcm9wb3NlZCBuZXcg
U2VjdGlvbiAzIHRoYXQgZGlzY3Vzc2VzCgp0aGUgQ2FwYWJpbGl0eSBvYmplY3QuCsKgW1ZQQl0g
QWRkZWQgYSBkaXJlY3QgcmVmZXJlbmNlIHRvIFJGQzUwNjMgCgoKCnMyLjIuMSwgbGFzdCBwYXJh
OiBzL3NldCBSZWZyZXNoLVJlZHVjdGlvbi1DYXBhYmxlIGJpdCBpbiBjb21tb24gaGVhZGVyL3Nl
dCB0aGUKClJlZnJlc2gtUmVkdWN0aW9uLUNhcGFibGUgYml0IGluIHRoZSBjb21tb24gaGVhZGVy
LwoKW1ZQQl0gRml4ZWQgaW4gLTA3CiAKCgoKczIuMywgcGFyYSAxOiBzL3NldCBvZiByZWNvbW1l
bmRhdGlvbnMvZnVuY3Rpb25hbGl0eS87IHMvcHJvdmlkZS9wcm92aWRlcy87CgpzL1JTVlAtVEUg
Y29udHJvbCBwbGFuZSBjb25nZXN0aW9uL2Egc2lnbmlmaWNhbnQgcG9ydGlvbiBvZiB0aGUgUlNW
UC1URSBjb250cm9sCgptZXNzYWdlIGxvYWQvCgpbVlBCXSBGaXhlZCBpbiAtMDcKIAoKCgpzMi4z
LjI6IHMvTUVTU0FHRSBJRC9NRVNTQUdFX0lELwoKW1ZQQl0gRml4ZWQgaW4gLTA3CiAKCgoKCgpf
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwoKVGVhcyBtYWls
aW5nIGxpc3QKClRlYXNAaWV0Zi5vcmcKCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vdGVhcwoKCgo=

----_com.samsung.android.email_154488561075070
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0
L2h0bWw7IGNoYXJzZXQ9VVRGLTgiPjwvaGVhZD48Ym9keT48ZGl2Pjxicj48L2Rpdj48ZGl2Pjxi
cj48L2Rpdj48ZGl2PkhpLCBQYXZhbi48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2PkkndmUgY2hl
Y2tlZCB0aHJvdWdoIHRoZSBjaGFuZ2VzIGluIC0wNyBhbmQgSSB0aGluayBhbGwgaXMgZ29vZCBh
cyByZWdhcmRzIGZpeGluZyB0aGUgJ21ham9yIGlzc3VlJywgcmVzdHVjdHVyaW5nIHMyIGFuZCBm
aXhpbmcgdGhlIG5pdHMgLSB0aGFua3MuPC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj5Mb29raW5n
IGF0IHRoZSBJRVNHIGNvbW1lbnRzIEkgdGhpbmsgeW91IGhhdmUgY292ZXJlZCBtb3N0IG9mIHRo
ZW0mbmJzcDsgZXhjZXB0IGl0IHdvdWxkIGJlIGdvb2QgdG8gcHV0IGEgcG9pbnRlciB0byBBcHBl
bmRpeCBBIGludG8gdGhlIGludHJvIG9mIHMyLiZuYnNwOzwvZGl2PjxkaXY+PGJyPjwvZGl2Pjxk
aXY+V2l0aCByZWZlcmVuY2UgdG8gQXBwZW5kaXggQShkKSwgaXQgd291bGQgYmUgaGVscGZ1bCB0
byBzL3BlcmlvZGljIHJldHJhbnNtaXNzaW9uIGludGVydmFsL1BlcmlvZGljIFJldHJhbnNtaXNz
aW9uIEludGVydmFsLyBhbmQgcG9zc2libHkgZ2l2ZSBpdCBhIG5hbWUgKFJwcmkgb3Igc29tZSBz
dWNoKSZuYnNwOyBpbiBzMi4zIGFuZCBBcHBlbmRpeCBBKGQpLiZuYnNwOyBBZGRpbmcgdGhlIG5h
bWUgb2YgdGhlIGludGVydmFsIGFmdGVyICJyZXRyYW5zbWlzc2lvbiBvZiB0aGVzZSBvbiBhIHNs
b3dlciB0aW1lciIgbWlndCBtYWsgaXQgY2xlYXJlciBhbHNvLjwvZGl2PjxkaXY+PGJyPjwvZGl2
PjxkaXY+SG93ZXZlciwmbmJzcDsgSSB0aGluayB5b3Ugc3RpbGwgbmVlZCB0byBhZGRyZXNzIGFs
bCB0aHJlZSBvZiB0aGUgbWlub3IgaXNzdWVzOjwvZGl2PjxkaXY+LSBDYXBhYmlsaXR5IG9iamVj
dDombmJzcDsgQSAnYmFzaWMnIGltcGxlbWVudGF0aW9uIG9mIFJGQyAyMjA5L1JGQzMyMDkgd2ls
bCBub3QgaW5jbHVkZSB0aGUgUkZDNTA2MyBleHRlbnNpb25zLiZuYnNwOyBJIHRoaW5rIHlvdSBz
aG91bGQgdGhlcmVmb3JlIG1ha2UgaXQgZXhwbGljaXQgdGhhdCBhIHByZXJlcXVpc2l0ZSBmb3Ig
eW91ciBleHRlbnNpb25zIGlzIGFuIGltcGxlbWVudGF0aW9uIG9mIHRoZSBDYXBhYmlsaXR5IG9i
amVjdCBhcyBzcGVjaWZpZWQgaW4gUkZDNTA2MyAobXkgcHJvcG9zYWwgZm9yIHMzKSAsIG1ha2lu
ZyBpdCBjbGVhciB0aGF0IHRoaXMgZG9lcyBub3QgcmVxdWlyZSBhbnkgb2YgdGhlIG90aGVyIGZ1
bmN0aW9uYWxpdHkgb2YgUkZDIDUwNjMsIGVzcGVjaWFsbHkgbm8gc3VwcG9ydCBmb3IgdGhlIFMg
Yml0IGluIHRoZSBDYXBhYmlsaXRpZXMuPC9kaXY+PGRpdj4tJm5ic3A7IFlvdXIgcmVzcG9uc2Ug
cmVnYXJkaW5nIHdoYXQgaGFwcGVucyBpZiBhIHBlZXIgaW5pdGlhbGx5IGFja25vd2xlZGdlcyB0
aGF0IGl0IHN1cHBvcnRzIHRoZSBuZXcgY2FwYWJpbGl0aWVzIGJ5IHNldHRpbmcgdGhlIEkvRiBi
aXRzIGluIHRoZSBDYXBhYmlsaXR5IGFuZCBzZW5kcyBzb21lIG1lc3NhZ2VzIHdpdGggdGhlIFJl
ZnJlc2gtUmVkdWN0aW9uLUNhcGFibGUgYml0IHNldCwgYnV0IHRoZW4gc3RvcHMgc2V0dGluZyB0
aGUgUmVmcmVzaC1SZWR1Y3Rpb24tQ2FwYWJsZSBiaXQgZG9lc24ndCByZWFsbHkgYWRkcmVzcyB0
aGUgcHJvYmxlbS4mbmJzcDsgJm5ic3A7V291bGQgdGhpcyBtZWFuIHRoYXQgdGhlIHJlY2VpdmVy
IHNob3VsZCBhc3N1bWUgdGhhdCB0aGUgcGVlciBjYW4gbm8gbG9uZ2VyIHN1cHBvcnQgdGhlIGV4
dGVuc2lvbnM/Jm5ic3A7IElzIHRoaXMgYSBwZXJtYW5lbnQgc3RhdGUgb3IgY291bGQgdGhlIHBl
ZXIgc3RhcnQgc2V0dGluZyB0aGUgUmVmcmVzaC1SZWR1Y3Rpb24tQ2FwYWJsZSBiaXQgYWdhaW4g
YW5kIHJlc3RvcmUgaW5pdGlhbCBmdW5jdGlvbmFsaXR5IC0gb3Igc2hvdWxkIHRoaXMganVzdCBu
b3QgYmUgYWxsb3dlZC4gSSB0aGluayB5b3UgbmVlZCB0byB0aGluayB0aHJvdWdoIHdoYXQgaGFw
cGVzIGluIHRoZSB2YXJpb3VzIHBvc3NpYmxlIGNhc2VzIGFuZCBleHBsYWluIHdoYXQgYW4gaW1w
bGVtZW50YXRpb24gc2hvdWxkIGRvIGluIGVhY2ggY2FzZS48L2Rpdj48ZGl2Pi0gU28sIEkgaGF2
ZSBkb25lIG15IGhvbWV3b3JrIGFuZCBjaGVja2VkIGJhY2sgb24gd2hhdCBoYXBwZW5zIHdoZW4g
dGhlcmUgaXMgbm8gYWNrbm93bGVkZ2VtZW50IG9mIHJlZnJlc2hlcy4gVGhlIHJlbGV2YW50IHBh
cmFtZXRlciBpcyB0aGUgY2xlYW51cCB0aW1lLiZuYnNwOyBIb3dldmVyLCB0aGlzIGxlYXZlcyB1
cyB3aXRoIGEgcHJvYmxlbS4uIHRoZSBjbGVhbnVwIHRpbWUgaXMgdHlwaWNhbGx5IHNldCBhcyBh
IG11bHRpcGxlIG9mIHRoZSByZWZyZXNoIGludGVydmFsICg5IHRpbWVzIHNlZW1zIHRvIGJlIHRo
ZSBkZWZhdWx0KSAtIGluZGVlZCBJIHNlZSB0aGF0IHRoZSBpbnRlcmZhY2UgY29uZmlndXJhdGlv
biBvbiBhIEp1bmlwZXIgcm91dGVyICghKSBhY3R1YWxseSBzZXRzIGl0IGJ5IGFza2luZyBmb3Ig
dGhlIG11bHRpcGxlIHJhdGhlciB0aGFuIGFuIGFic29sdXRlIHZhbHVlLiZuYnNwOyBXdGggdGhl
IG5ldyBkaXNwZW5zYXRpb24gaW4gdGhzIGRvY3VtZW50LCB0aGVyZSBhcmUgdHdvIHRpbWUgcGVy
aW9kcyBpbnZvbHZlZDombmJzcDsgSSB0aGluayB5b3UgZG8gbmVlZCB0byByZXNwZWNpZnkgaG93
IHRvIGNhbGN1bGF0ZSBhIHNlbnNpYmxlIGNsZWFudXAgaW50ZXJ2YWwsIGFuZCBub3RlIHRoYXQg
dGhlIHJldHJhbnNtaXNzaW9ucyB3aWxsIHRoZW4gaGFsdCBhZnRlciB0aGlzIGludGVydmFsLjwv
ZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+RG9lcyB0aGlzIGxhc3QgbW9kaWZpY2F0aW9uIGNvbnN0
aXR1dGUgYW4gdXBkYXRlIG9mIFJGQyAyMjA5PyZuYnNwOyBJIGFtIG5vdCBzdXJlIC1jb25zdWx0
IHlvdXIgQUQhPC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj5SZWdhcmRzLDwvZGl2PjxkaXY+RWx3
eW4mbmJzcDs8L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2IGlkPSJjb21wb3Nlcl9zaWduYXR1cmUi
PjxkaXYgc3R5bGU9ImZvbnQtc2l6ZTo4NSU7Y29sb3I6IzU3NTc1NyIgZGlyPSJhdXRvIj5TZW50
IGZyb20gU2Ftc3VuZyB0YWJsZXQuPC9kaXY+PC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdiBzdHls
ZT0iZm9udC1zaXplOjEwMCU7Y29sb3I6IzAwMDAwMCI+PCEtLSBvcmlnaW5hbE1lc3NhZ2UgLS0+
PGRpdj4tLS0tLS0tLSBPcmlnaW5hbCBtZXNzYWdlIC0tLS0tLS0tPC9kaXY+PGRpdj5Gcm9tOiBW
aXNobnUgUGF2YW4gQmVlcmFtICZsdDt2aXNobnVwYXZhbkBnbWFpbC5jb20mZ3Q7IDwvZGl2Pjxk
aXY+RGF0ZTogMjgvMDkvMjAxNyAgMDM6NDggIChHTVQrMDA6MDApIDwvZGl2PjxkaXY+VG86IEVs
d3luIERhdmllcyAmbHQ7ZWx3eW5kQGRpYWwucGlwZXguY29tJmd0OyA8L2Rpdj48ZGl2PkNjOiBn
ZW4tYXJ0QGlldGYub3JnLCBkcmFmdC1pZXRmLXRlYXMtcnN2cC10ZS1zY2FsaW5nLXJlYy5hbGxA
aWV0Zi5vcmcsIGlldGYgJmx0O2lldGZAaWV0Zi5vcmcmZ3Q7LCB0ZWFzQGlldGYub3JnIDwvZGl2
PjxkaXY+U3ViamVjdDogUmU6IFtUZWFzXSBHZW5hcnQgbGFzdCBjYWxsIHJldmlldyBvZiBkcmFm
dC1pZXRmLXRlYXMtcnN2cC10ZS1zY2FsaW5nLXJlYy0wNiA8L2Rpdj48ZGl2Pjxicj48L2Rpdj48
L2Rpdj48ZGl2IGRpcj0ibHRyIj48ZGl2PjxkaXY+RWx3eW4sIEhpITwvZGl2PjxkaXY+PGJyPjwv
ZGl2PjxkaXY+VGhhbmtzIGZvciB0aGUgZGV0YWlsZWQgcmV2aWV3IGFuZCB0aGUgdGV4dCBzdWdn
ZXN0aW9ucy4gV2UganVzdCBwb3N0ZWQgYSBuZXcgcmV2aXNpb24gKC0wNykgdG8gYWRkcmVzcyB0
aGUgY29uY2VybnMgbGlzdGVkIGJlbG93LiBQbGVhc2UgZ28gdGhyb3VnaCB0aGUgbmV3IGRpZmZz
ICg8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9yZmNkaWZmP3VybDI9ZHJhZnQtaWV0Zi10
ZWFzLXJzdnAtdGUtc2NhbGluZy1yZWMtMDciPmh0dHBzOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/
dXJsMj1kcmFmdC1pZXRmLXRlYXMtcnN2cC10ZS1zY2FsaW5nLXJlYy0wNzwvYT4pIGFuZCBsZXQg
dXMga25vdyBpZiBhZGRpdGlvbmFsIGNoYW5nZXMgYXJlIHJlcXVpcmVkLjwvZGl2PjxkaXY+PGJy
PjwvZGl2PjxkaXY+UGxlYXNlIHNlZSBpbmxpbmUgZm9yIGZ1cnRoZXIgcmVzcG9uc2VzIChwcmVm
aXhlZCBWUEIpLjxicj48YnI+PC9kaXY+UmVnYXJkcyw8YnI+PC9kaXY+LVBhdmFuPGJyPjxkaXYg
Y2xhc3M9ImdtYWlsX2V4dHJhIj48YnI+PGRpdiBjbGFzcz0iZ21haWxfcXVvdGUiPk9uIEZyaSwg
U2VwIDIyLCAyMDE3IGF0IDY6MDYgUE0sIEVsd3luIERhdmllcyA8c3BhbiBkaXI9Imx0ciI+Jmx0
OzxhIGhyZWY9Im1haWx0bzplbHd5bmRAZGlhbC5waXBleC5jb20iIHRhcmdldD0iX2JsYW5rIj5l
bHd5bmRAZGlhbC5waXBleC5jb208L2E+Jmd0Ozwvc3Bhbj4gd3JvdGU6PGJyPjxibG9ja3F1b3Rl
IGNsYXNzPSJnbWFpbF9xdW90ZSIgc3R5bGU9Im1hcmdpbjowcHggMHB4IDBweCAwLjhleDtib3Jk
ZXItbGVmdDoxcHggc29saWQgcmdiKDIwNCwyMDQsMjA0KTtwYWRkaW5nLWxlZnQ6MWV4Ij5SZXZp
ZXdlcjogRWx3eW4gRGF2aWVzPGJyPgpSZXZpZXcgcmVzdWx0OiBOb3QgUmVhZHk8YnI+Cjxicj4K
SSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gVGhlIEdl
bmVyYWwgQXJlYTxicj4KUmV2aWV3IFRlYW0gKEdlbi1BUlQpIHJldmlld3MgYWxsIElFVEYgZG9j
dW1lbnRzIGJlaW5nIHByb2Nlc3NlZDxicj4KYnkgdGhlIElFU0cgZm9yIHRoZSBJRVRGIENoYWly
LiZuYnNwOyBQbGVhc2UgdHJlYXQgdGhlc2UgY29tbWVudHMganVzdDxicj4KbGlrZSBhbnkgb3Ro
ZXIgbGFzdCBjYWxsIGNvbW1lbnRzLjxicj4KPGJyPgpGb3IgbW9yZSBpbmZvcm1hdGlvbiwgcGxl
YXNlIHNlZSB0aGUgRkFRIGF0PGJyPgo8YnI+CiZsdDs8YSBocmVmPSJodHRwczovL3RyYWMuaWV0
Zi5vcmcvdHJhYy9nZW4vd2lraS9HZW5BcnRmYXEiIHJlbD0ibm9yZWZlcnJlciIgdGFyZ2V0PSJf
YmxhbmsiPmh0dHBzOi8vdHJhYy5pZXRmLm9yZy90cmFjL2dlPHdicj5uL3dpa2kvR2VuQXJ0ZmFx
PC9hPiZndDsuPGJyPgo8YnI+CkRvY3VtZW50OiBkcmFmdC1pZXRmLXRlYXMtcnN2cC10ZS1zY2Fs
aW48d2JyPmctcmVjLTA2PGJyPgpSZXZpZXdlcjogRWx3eW4gRGF2aWVzPGJyPgpSZXZpZXcgRGF0
ZTogMjAxNy0wOS0yMjxicj4KSUVURiBMQyBFbmQgRGF0ZTogMjAxNy0wOS0yMjxicj4KSUVTRyBU
ZWxlY2hhdCBkYXRlOiAyMDE3LTA5LTI4PGJyPgo8YnI+ClN1bW1hcnk6IE5vdCByZWFkeSwgcHJp
bWFyaWx5IGJlY2F1c2UgdGhlIHRpdGxlIGFuZCBwcmVzZW50YXRpb24gZ2l2ZSB0aGU8YnI+Cmlt
cHJlc3Npb24gdGhhdCB0aGUgY29udGVudCBpcyByZWFsbHkgYSBCQ1Agd2hlbiBpdCBpc24ndC4m
bmJzcDsgVGhpcyBjb25jZWFscyB0aGU8YnI+CmNvbnNpZGVyYWJsZSBhbW91bnQgb2YgdHdlYWtp
bmcgb2YgUkZDIDI5NjEgZnVuY3Rpb25hbGl0eSBhbmQgYWRkaXRpb24gb2YgbmV3PGJyPgpSU1ZQ
IENhcGFiaWxpdGllcyBkZXNjcmliZWQgaW4gdGhlIGRvY3VtZW50LiZuYnNwOyBUaGVyZSBhcmUg
YWxzbyBhIGNvdXBsZSBvZiBtaW5vcjxicj4KaXNzdWVzIHRoYXQgbmVlZCB0byBiZSBzb3J0ZWQg
b3V0Ljxicj4KPGJyPgpNYWpvciBpc3N1ZXM6PGJyPgpUaXRsZSBhbmQgd2F5IHByb3Bvc2FscyBh
cmUgcHJlc2VudGVkOiZuYnNwOyBUaGUgZG9jdW1lbnQgZGVmaW5lcyB0d28gbmV3PGJyPgonY2Fw
YWJpbGl0aWVzJyBmb3IgUlNWUC1URSBhbmQgaXMgaW5kZWVkIChhcyBzcGVjaWZpZWQgaW4gdGhl
IGRvY3VtZW50IGhlYWRlcik8YnI+CmNvcnJlY3RseSBpbnRlbmRlZCBmb3IgU3RhbmRhcmRzIFRy
YWNrIHN0YXR1cy4mbmJzcDsgSG93ZXZlciB0aGUgdGl0bGUgYW5kIHRoZSB3aG9sZTxicj4Kb2Yg
dGhlIG1lYXQgb2YgdGhlIGRvY3VtZW50IGluIFNlY3Rpb24gMiBwcmVzZW50cyB0aGUgcHJvcG9z
YWxzIGFzPGJyPgoncmVjb21tZW5kYXRpb25zJyB3aGljaCBzYXlzIHRvIG1lIHRoYXQgSSBhbSBl
eHBlY3RpbmcgYSBCQ1Agd2hlcmUgYSBwcm9maWxlIG9mPGJyPgphdmFpbGFibGUgb3B0aW9ucyBm
cm9tIGV4aXN0aW5nIHN0YW5kYXJkcyBpcyByZWNvbW1lbmRlZCBhcyB0aGUgYmVzdCBjaG9pY2Ug
Zm9yPGJyPgppbXBsZW1lbnRhdGlvbiBhbmQgZGVwbG95bWVudC4mbmJzcDsgSW4gbXkgb3Bpbmlv
biwgdGhlIHRpdGxlIHdvdWxkIGJlIGJldHRlciBhczxicj4Kc29tZXRoaW5nIGxpa2UgIkFkZGl0
aW9uYWwgQ2FwYWJpbGl0aWVzIERlc2lnbmVkIHRvIEltcHJvdmUgdGhlIFNjYWxhYmlsaXR5IG9m
PGJyPgpSU1ZQLVRFIERlcGxveW1lbnRzIi4mbmJzcDsgV2hpbHN0IHRoZSBwcm9wb3NhbHMgYXJl
IGJhc2VkIG9uIHRoZSB0ZWNobmlxdWVzIGluIFJGQzxicj4KMjk2MSwgdGhlIGRvY3VtZW50ICpy
ZXF1aXJlcyogdGhlIGltcGxlbWVudG9yIHRvIGNvbmZvcm0gdG8gcnVsZXMgdGhhdCB3ZXJlPGJy
PgpvcHRpb25hbCBhbmQgY29uc3RyYWlucyBjb25maWd1cmFibGUgdmFsdWVzIHRvIGRpZmZlcmVu
dCByYW5nZXMgaW4gb3JkZXIgdG8gYmU8YnI+CmFibGUgdG8gZGVsaXZlciB0aGUgY2FwYWJpbGl0
aWVzIGRlZmluZWQgaW4gdGhlIGRvY3VtZW50IGFzIHdlbGwgYXMgZGVmaW5pbmc8YnI+Cm5ldyBS
U1ZQIGV4dGVuc2lvbnMgbW9kaWZ5aW5nIHNvbWUgb2YgdGhlIGJlaGF2aW91ciBkZWZpbmVkIGlu
IFJGQyAyOTYxLiZuYnNwOyBUaHVzPGJyPgphbHRob3VnaCBzb21lIG9mIHRoZSBydWxlcyBjb3Vs
ZCBiZSBtZXQgYnkgY2hvb3NpbmcgcGFydGljdWxhciB2YWx1ZXMgd2l0aGluPGJyPgp0aGUgUkZD
IDI5NjEgc2V0LCB0aGUgdXNlIG9mIE1VU1QsIHR3ZWFraW5nIG9mIGZ1bmN0aW9uYWxpdHkgYW5k
IHZhcmlhdGlvbiBvZjxicj4KcmFuZ2VzIHRha2VzIGl0IHdlbGwgYmV5b25kIGEgc2V0IG9mIHJl
Y29tbWVuZGF0aW9ucyBmb3IgUkZDIDI5NjEgb3B0aW9uczxicj4Kc2VsZWN0aW9ucy4mbmJzcDsg
SW4gdmlldyBvZiB0aGlzIFNlY3Rpb24gMSBuZWVkcyB0byBiZSB3cml0dGVuIGFzIGFuIGludHJv
ZHVjdGlvbjxicj4KdG8gdGhlIGRlZmluaXRpb25zIG9mIHRoZSBuZXcgY2FwYWJpbGl0aWVzIHJh
dGhlciB0aGFuIGFkdm9jYWN5IGZvciBzZWxlY3Rpb248YnI+Cm9mIFJGQyAyOTYxIG9wdGlvbnMg
YW5kIHRoZSBpbXBsaWNhdGlvbiB0aGF0IHRoZSB0ZWNobmlxdWVzIG1lbnRpb25lZCBpbiB0aGU8
YnI+Cmxhc3QgcGFyYWdyYXBoIG9mIHMxIGFyZSBqdXN0IGEgbWF0dGVyIG9mIHNlbGVjdGluZyBh
IHByb2ZpbGUgb2Ygb3B0aW9uIHZhbHVlcy48YnI+CiZuYnNwO0luIGFjdHVhbGl0eSBuZXcgcHJv
dG9jb2wgdmFsdWVzIGFyZSBpbnRyb2R1Y2VkIGFuZCBzczIuMiBhbmQgMi4zIGRlZmluZSBub3Zl
bDxicj4KZXh0ZW5zaW9ucyB0byBSU1ZQIGJleW9uZCB3aGF0IGlzIGF2YWlsYWJsZSBmb3IgUkZD
IDI5NjEgYW5kIHJlcXVpcmluZzxicj4KbW9kaWZpY2F0aW9uIHRvIGJhc2ljIFJGQyAyOTYxIGZ1
bmN0aW9uYWxpdHkuLjxicj4KPGJyPjwvYmxvY2txdW90ZT48ZGl2Pjxicj48L2Rpdj48ZGl2PltW
UEJdIFdlIGNoYW5nZWQgdGhlIHRpdGxlIHRvICJUZWNobmlxdWVzIHRvIEltcHJvdmUgdGhlIFNj
YWxhYmlsaXR5IG9mIFJTVlAtVEUgRGVwbG95bWVudHMiLiBXZSBhbHNvIHR3ZWFrZWQgdGhlIHRl
eHQgaW4gdGhlIGludHJvZHVjdGlvbiBzZWN0aW9uIGFzIHN1Z2dlc3RlZC4gUGxlYXNlIHNlZSBp
ZiB0aGUgbmV3IHNldCBvZiBkaWZmcyBhZGRyZXNzIHRoZSBjb21tZW50IGFib3ZlLjxicj48L2Rp
dj48ZGl2PiA8YnI+PC9kaXY+PGJsb2NrcXVvdGUgY2xhc3M9ImdtYWlsX3F1b3RlIiBzdHlsZT0i
bWFyZ2luOjBweCAwcHggMHB4IDAuOGV4O2JvcmRlci1sZWZ0OjFweCBzb2xpZCByZ2IoMjA0LDIw
NCwyMDQpO3BhZGRpbmctbGVmdDoxZXgiPgpNaW5vciBpc3N1ZXM6PGJyPgpJbnRlcmFjdGlvbiB3
aXRoIFJGQyA1MDYzOiZuYnNwOyBUaGUgZG9jdW1lbnQgZG9lcyBub3QgZXhwbGljaXRseSBzdGF0
ZSB0aGF0IGFuPGJyPgppbXBsZW1lbnRhdGlvbiB3b3VsZCBuZWVkIHRvIHN1cHBvcnQgKGF0IGxl
YXN0KSB0aGUgZXh0cmEgY2FwYWJpbGl0eSBvYmVjdDxicj4KZGVmaW5lZCBpbiBzNC4yIG9mIFJG
QyA1MDYzLiZuYnNwOyBTb21lIHdvcmRzIGFib3V0IGludGVyYWN0aW9uIHdpdGggUkZDIDUwNjMg
YXJlPGJyPgpwcm9iYWJseSByZXF1aXJlZCBpbiB0aGF0IHM0LjIuMSBvZiBSRkMgNTA2MyByYXRo
ZXIgYXNzdW1lcyB0aGF0IGlmIHRoZXJlIGlzIGE8YnI+CmNhcGFiaWxpdHkgb2JqZWN0LCBieSBk
ZWZhdWx0IGl0cyBTIGJpdCB3aWxsIGJlIHNldC48YnI+PC9ibG9ja3F1b3RlPjxkaXY+PGJyPjwv
ZGl2PjxkaXY+W1ZQQl0gVGhlIENBUEFCSUxJVFkgb2JqZWN0IGluIFJGQzUwNjMgaXMgbWVhbnQg
Zm9yIGdlbmVyaWMgdXNlIGFuZCBjYW4gYmUgdXNlZCBldmVuIHdoZW4gdGhlcmUgYXJlIG5vIEdy
YWNlZnVsIFJlc3RhcnQgZXh0ZW5zaW9ucyBpbiBwbGF5IChldmVuIHdoZW4gbm8gR1IgZmxhZ3Mg
YXJlIHNldCkuIEFzIGZhciBhcyB3ZSBjYW4gdGVsbCwgdGhlcmUgaXMgbm90aGluZyBpbiBSRkM1
MDYzIHRoYXQgcHJlY2x1ZGVzIHRoaXMuIFdlIGFkZGVkIGEgcmVmZXJlbmNlIHRvIFJGQzUwNjMg
d2hlbiB0aGUgbmV3IENhcGFiaWxpdHkgZmxhZ3MgYXJlIGludHJvZHVjZWQuIFdvdWxkIHRoaXMg
YmUgc3VmZmljaWVudCB0byBhZGRyZXNzIHRoaXMgY29uY2Vybj88YnI+PC9kaXY+PGRpdj4mbmJz
cDs8YnI+PC9kaXY+PGJsb2NrcXVvdGUgY2xhc3M9ImdtYWlsX3F1b3RlIiBzdHlsZT0ibWFyZ2lu
OjBweCAwcHggMHB4IDAuOGV4O2JvcmRlci1sZWZ0OjFweCBzb2xpZCByZ2IoMjA0LDIwNCwyMDQp
O3BhZGRpbmctbGVmdDoxZXgiPgo8YnI+CkJlaGF2aW91ciBpZiBhIG5vZGUgc3RvcHMgc2V0dGlu
ZyBSZWZyZXNoLVJlZHVjdGlvbi1DYXBhYmxlIGJpdDombmJzcDsgVGhlIGxhc3QgcGFyYTxicj4K
b2YgczIgaW4gUkZDIDI5NjEgZGlzY3Vzc2VzIGJlaGF2aW91ciBpZiBhIG5vZGUgc3RvcHMgc2V0
dGluZyB0aGlzIGJpdCBpbjxicj4KbWVzc2FnZXMuJm5ic3A7IFdoYXQgd291bGQgaGFwcGVuIHdp
dGggdGhlIGV4dGVuc2lvbnMgZGVmaW5lZCBpbiB0aGlzIGRvY3VtZW50IGlmPGJyPgp0aGlzIGhh
cHBlbmVkIHdoaWxlIGVpdGhlciBvZiB0aGUgZXh0ZW5zaW9ucyBpcyBpbiB1c2U/Jm5ic3A7IEFz
IGEgbWF0dGVyIG9mPGJyPgppbnRlcmVzdCwgaWYgYSBwZWVyIG9mZmVycyB0aGUgY2FwYWJpbGl0
aWVzIGRlZmluZWQgaW4gdGhpcyBkcmFmdCwgaXMgaXQ8YnI+CnBvc3NpYmxlIG9yIHNlbnNpYmxl
IGZvciBpdCB0byBzdG9wIHNldHRpbmcgdGhlIFJlZnJlc2gtUmVkdWN0aW9uLUNhcGFibGUgYml0
PGJyPgp3aXRob3V0IHN0b3BwaW5nIG9mZmVyaW5nIHRoZSBleHRlbnNpb25zPzxicj48L2Jsb2Nr
cXVvdGU+PGRpdj48YnI+PC9kaXY+PGRpdj5bVlBCXSZuYnNwOyBJZiBhIHBlZXIgc2V0cyB0aGUg
SSBvciBGIGJpdCBpbiB0aGUgQ0FQQUJJTElUWSBvYmplY3QgYnV0IGRvZXMgbm90IHNldCB0aGUg
UmVmcmVzaC1SZWR1Y3Rpb24tY2FwYWJsZSBiaXQsIHRoZW4gdGhlIGNvcnJlc3BvbmRpbmcgZnVu
Y3Rpb25hbGl0eSAoIlJJLVJTVlAiIG9yICJQZXItUGVlciBGbG93LUNvbnRyb2wiKSBpcyBub3Qg
YWN0aXZhdGVkIGZvciB0aGF0IHBlZXIuIEluIG90aGVyIHdvcmRzLCByZXNldHRpbmcgdGhlIFJl
ZnJlc2gtUmVkdWN0aW9uLUNhcGFibGUgYml0IGltbWVkaWF0ZWx5IG1ha2VzIHRoZSBub2RlIGlu
Y2FwYWJsZSBvZiBzdXBwb3J0aW5nIHRoZSB0d28gY2FwYWJpbGl0aWVzIGRpc2N1c3NlZCBpbiB0
aGlzIGRvY3VtZW50LiBUaGlzIGlzIGNvdmVyZWQgaW4gU2VjdGlvbnMgMy4xIGFuZCA0LjEgKCAt
MDcgdmVyc2lvbikuIDxicj48L2Rpdj48ZGl2Pjxicj48L2Rpdj48YmxvY2txdW90ZSBjbGFzcz0i
Z21haWxfcXVvdGUiIHN0eWxlPSJtYXJnaW46MHB4IDBweCAwcHggMC44ZXg7Ym9yZGVyLWxlZnQ6
MXB4IHNvbGlkIHJnYigyMDQsMjA0LDIwNCk7cGFkZGluZy1sZWZ0OjFleCI+Cjxicj4KczIuMS4z
LCBwYXJhIDI6IEFzIHNwZWNpZmllZCwgaXQgYXBwZWFycyB0aGF0IHRoZSAnc2xvd2VyIHRpbWVy
JyB0cmFuc21pc3Npb248YnI+Cm9mIFBhdGggYW5kIFJlc3YgbWVzc2FnZXMgY2FuIGdvIG9uIGlu
ZGVmaW5pdGVseSBpZiBubyBhY2sgYXJyaXZlcy4mbmJzcDsgV2hhdCBwdXRzPGJyPgphbiBlbmQg
dG8gdGhpcyByZXBldGl0aW9uPyZuYnNwOyBbSXQgbWF5IGJlIHRoYXQgSSBoYXZlIGZvcmdvdHRl
biBob3cgYmFzaWMgUlNWUDxicj4Kd29ya3MsIGJ1dCBzaW5jZSB0aGlzIGlzIGFsdGVyaW5nIHRo
ZSBiZWhhdmlvdXIgaXQgd291bGQgYmUgZ29vZCB0byBleHBsYWluIGhvdzxicj4KaXQgdGVybWlu
YXRlcywgYW5kIHdoZXRoZXIgdGhpcyByZXF1aXJlcyBhbnkgYWRkaXRpb25hbCBtb2RpZmljYXRp
b24gdG8gdGltZXJzLl08YnI+PC9ibG9ja3F1b3RlPjxkaXY+PGJyPjwvZGl2PjxkaXY+W1ZQQl0m
bmJzcDsgVGhlcmUgaXMgbm90aGluZyBuZXcgYWJvdXQgUGF0aCBhbmQgUmVzdiBtZXNzYWdlcyBn
ZXR0aW5nIHRyYW5zbWl0dGVkIGluZGVmaW5pdGVseSAodGhpcyBpcyBub3JtYWwgc29mdC1zdGF0
ZSBzaWduYWxpbmcgYmVoYXZpb3IpIC0tIGFsbCB0aGF0IHRoaXMgc2VjdGlvbiBkb2VzIGlzIGRp
c2N1c3MgaG93IHRoZXNlIHRyYW5zbWlzc2lvbnMgYXJlIHBhY2VkIGluIHRoZSBhYnNlbmNlIG9m
IGFuIGFjay4gVGhlIHNsb3dlciB0aW1lciB0cmFuc21pc3Npb24gd2lsbCBnbyBvbiB1bnRpbCBl
aXRoZXIgYW4gYWNrIGlzIHJlY2VpdmVkIChhdCB3aGljaCBwb2ludCB0aGUgcmVndWxhciAicmVm
cmVzaCBpbnRlcnZhbCIgY29tZXMgaW50byBwbGF5KSBvciB0aGUgY29ycmVzcG9uZGluZyBMU1Ag
aW5zdGFuY2Ugc3RhdGUgaXMgdG9ybiBkb3duLiA8YnI+PC9kaXY+PGRpdj48YnI+PC9kaXY+PGJs
b2NrcXVvdGUgY2xhc3M9ImdtYWlsX3F1b3RlIiBzdHlsZT0ibWFyZ2luOjBweCAwcHggMHB4IDAu
OGV4O2JvcmRlci1sZWZ0OjFweCBzb2xpZCByZ2IoMjA0LDIwNCwyMDQpO3BhZGRpbmctbGVmdDox
ZXgiPgo8YnI+Ck5pdHMvZWRpdG9yaWFsIGNvbW1lbnRzOjxicj4KQWJzdHJhY3Q6IFJTVlAtVEUg
aXMgbm90IGEgJ3dlbGwta25vd24nIGFiYnJldmlhdGlvbjogcy9SU1ZQLVRFL1JTVlAgVHJhZmZp
Yzxicj4KRW5naW5lZXJpbmcgKFJTVlAtVEUpLzxicj48L2Jsb2NrcXVvdGU+PGJsb2NrcXVvdGUg
Y2xhc3M9ImdtYWlsX3F1b3RlIiBzdHlsZT0ibWFyZ2luOjBweCAwcHggMHB4IDAuOGV4O2JvcmRl
ci1sZWZ0OjFweCBzb2xpZCByZ2IoMjA0LDIwNCwyMDQpO3BhZGRpbmctbGVmdDoxZXgiPgo8YnI+
CkFic3RyYWN0IGFuZCBzMSwgZmlyc3QgcGFyYTombmJzcDsgVGhpcyBwYXJhIGlzIG5vdCBmdXR1
cmUgcHJvb2YuJm5ic3A7IFN1Z2dlc3Q6PGJyPgpPTEQ6PGJyPgombmJzcDsgJm5ic3A7VGhlIHNj
YWxlIGF0IHdoaWNoIFJTVlAtVEUgW1JGQzMyMDldIExhYmVsIFN3aXRjaGVkIFBhdGhzIChMU1Bz
KSBnZXQ8YnI+CiZuYnNwOyAmbmJzcDtkZXBsb3llZCBpcyBncm93aW5nIGNvbnRpbnVhbGx5IGFu
ZCB0aGVyZSBpcyBjb25zaWRlcmFibGUgb251cyBvbjxicj4KJm5ic3A7ICZuYnNwO1JTVlAtVEUg
aW1wbGVtZW50YXRpb25zIGFjcm9zcyB0aGUgYm9hcmQgdG8ga2VlcCB1cCB3aXRoIHRoaXM8YnI+
CiZuYnNwOyAmbmJzcDtpbmNyZWFzaW5nIGRlbWFuZCBpbiBzY2FsZS48YnI+Ck5FVzo8YnI+CiZu
YnNwOyAmbmJzcDtBdCB0aGUgdGltZSBvZiB3cml0aW5nLCBuZXR3b3JrcyB3aGljaCB1dGlsaXNl
IFJTVlAgVHJhZmZpYyBFbmdpbmVlcmluZzxicj4KJm5ic3A7ICZuYnNwOyhSU1ZQLVRFKSBbUkZD
MzIwOV0gTGFiZWwgU3dpdGNoZWQgUGF0aHMgKExTUHMpIGFyZSBlbmNvdW50ZXJpbmcgbGltaXRh
dGlvbnM8YnI+CiZuYnNwOyAmbmJzcDtpbiB0aGUgYWJpbGl0eSBvZiBpbXBsZW1lbnRhdGlvbnMg
dG8gc3VwcG9ydCB0aGUgZ3Jvd3RoIGluIHRoZSBudW1iZXIgb2YgTFNQczxicj4KJm5ic3A7ICZu
YnNwO2RlcGxveWVkLiZuYnNwOyBUaGlzIGRvY3VtZW50IGRlZmluZXMgdHdvIGFkZGl0aW9uYWwg
UlNWUC1URSBleHRlbnNpb25zIHRoYXQ8YnI+CiZuYnNwOyAmbmJzcDthcmUgaW50ZW5kZWQgdG8g
cmVkdWNlIHRoZSBudW1iZXIgb2YgbWVzc2FnZXMgbmVlZGVkIHRvIG1haW50YWluIFJTVlAtVEU8
YnI+CiZuYnNwOyAmbmJzcDtzb2Z0IHN0YXRlIGluIHJvdXRlcnMgYW5kIGhlbmNlIGFsbG93IGlt
cGxlbWVudGF0aW9ucyB0byBzdXBwb3J0IGxhcmdlcjxicj4KJm5ic3A7ICZuYnNwO3NjYWxlIGRl
cGxveW1lbnRzLjxicj4KRU5EUzxicj4KTm90ZTombmJzcDsgT21pdCByZWZlcmVuY2UgZnJvbSBB
YnN0cmFjdC48YnI+Cjxicj48L2Jsb2NrcXVvdGU+PGRpdj48YnI+PC9kaXY+PGRpdj5bVlBCXSBG
aXhlZCBpbiAtMDc8L2Rpdj48ZGl2PiA8YnI+PC9kaXY+PGJsb2NrcXVvdGUgY2xhc3M9ImdtYWls
X3F1b3RlIiBzdHlsZT0ibWFyZ2luOjBweCAwcHggMHB4IDAuOGV4O2JvcmRlci1sZWZ0OjFweCBz
b2xpZCByZ2IoMjA0LDIwNCwyMDQpO3BhZGRpbmctbGVmdDoxZXgiPgpzMSwgcGFyYSAyOiBzL3Vu
ZGVyIGNlcnRhaW4vYmV5b25kIGEgY2VydGFpbi88YnI+PC9ibG9ja3F1b3RlPjxkaXY+PGJyPjwv
ZGl2PjxkaXY+W1ZQQl0gRml4ZWQgaW4gLTA3PGJyPjwvZGl2PjxkaXY+IDxicj48L2Rpdj48Ymxv
Y2txdW90ZSBjbGFzcz0iZ21haWxfcXVvdGUiIHN0eWxlPSJtYXJnaW46MHB4IDBweCAwcHggMC44
ZXg7Ym9yZGVyLWxlZnQ6MXB4IHNvbGlkIHJnYigyMDQsMjA0LDIwNCk7cGFkZGluZy1sZWZ0OjFl
eCI+Cjxicj4KczEsIHBhcmEgMzogcy9tYWtlcyBhIHNldCBvZiBjb25jcmV0ZSBpbXBsZW1lbnRh
dGlvbiByZWNvbW1lbmRhdGlvbnMvZGVmaW5lczxicj4KdHdvIGV4dGVuc2lvbnMvOyBzLy0gcHVz
aCBoaWdoZXIvYnkgaW5jcmVhc2luZy87IHMvbWFpbnRhaW4gTFNQIHN0YXRlLi9tYWludGFpbjxi
cj4KTFNQIHN0YXRlIGJ5IHJlZHVjaW5nIHRoZSBudW1iZXIgb2YgbWVzc2FnZXMgbmVlZGVkLi88
YnI+Cjxicj4KQWJzdHJhY3QsIHBhcmEgMiBhbmQgczEsIGxhc3QgcGFyYTombmJzcDsgW09taXQg
cmVmZXJlbmNlIGZyb20gQWJzdHJhY3RdPGJyPgpPTEQ6PGJyPgombmJzcDsgJm5ic3A7VGhpcyBk
b2N1bWVudCBhZHZvY2F0ZXMgdGhlIHVzZSBvZiBhIGNvdXBsZSBvZiB0ZWNobmlxdWVzIC0gIlJl
ZnJlc2gtPGJyPgombmJzcDsgJm5ic3A7SW50ZXJ2YWwgSW5kZXBlbmRlbnQgUlNWUCAoUkktUlNW
UCkiIGFuZCAiUGVyLVBlZXIgRmxvdy1Db250cm9sIiAtPGJyPgombmJzcDsgJm5ic3A7Zm9yIHNp
Z25pZmljYW50bHkgY3V0dGluZyBkb3duIHRoZSBhbW91bnQgb2YgcHJvY2Vzc2luZyBjeWNsZXM8
YnI+CiZuYnNwOyAmbmJzcDtyZXF1aXJlZCB0byBtYWludGFpbiBMU1Agc3RhdGUuPGJyPgpORVc6
PGJyPgombmJzcDsgJm5ic3A7VGhpcyBkb2N1bWVudCBkZWZpbmVzIHR3byBSU1ZQIENhcGFiaWxp
dGllcyBbUkZDNTA2M10gIlJlZnJlc2gtPGJyPgombmJzcDsgJm5ic3A7SW50ZXJ2YWwgSW5kZXBl
bmRlbnQgUlNWUCAoUkktUlNWUCkiIGFuZCAiUGVyLVBlZXIgRmxvdy1Db250cm9sIjxicj4KJm5i
c3A7ICZuYnNwO3RoYXQgd2lsbCBjdXQgZG93biB0aGUgbnVtYmVyIG9mIG1lc3NzYWdlcyBhbmQg
cHJvY2Vzc2luZyBjeWNsZXM8YnI+CiZuYnNwOyAmbmJzcDtyZXF1aXJlZCB0byBtYWludGFpbiBM
U1Agc3RhdGUuPGJyPgpFTkRTPGJyPjwvYmxvY2txdW90ZT48ZGl2Pjxicj48L2Rpdj48ZGl2PltW
UEJdIEZpeGVkIGluIC0wNzxicj48L2Rpdj48ZGl2PiA8YnI+PC9kaXY+PGJsb2NrcXVvdGUgY2xh
c3M9ImdtYWlsX3F1b3RlIiBzdHlsZT0ibWFyZ2luOjBweCAwcHggMHB4IDAuOGV4O2JvcmRlci1s
ZWZ0OjFweCBzb2xpZCByZ2IoMjA0LDIwNCwyMDQpO3BhZGRpbmctbGVmdDoxZXgiPgo8YnI+CnMx
LCBsYXN0IHBhcmE6IEFkZCBuZXcgcGVudWx0aW1hdGUgc2VudGVuY2U6PGJyPgombmJzcDsgJm5i
c3A7Tm90ZSB0aGF0IHRoZSAiUGVyLVBlZXIgRmxvdy1Db250cm9sIiBjYXBhYmlsaXR5IHJlcXVp
cmVzIHRoZSAiUkktUlNWUCI8YnI+CiZuYnNwOyAmbmJzcDtjYXBhYmlsaXR5IGFzIGEgcHJlcmVx
dWlzaXRlLjxicj48L2Jsb2NrcXVvdGU+PGRpdj48YnI+PC9kaXY+PGRpdj5bVlBCXSBGaXhlZCBp
biAtMDc8YnI+PC9kaXY+PGRpdj4gPGJyPjwvZGl2PjxibG9ja3F1b3RlIGNsYXNzPSJnbWFpbF9x
dW90ZSIgc3R5bGU9Im1hcmdpbjowcHggMHB4IDBweCAwLjhleDtib3JkZXItbGVmdDoxcHggc29s
aWQgcmdiKDIwNCwyMDQsMjA0KTtwYWRkaW5nLWxlZnQ6MWV4Ij4KPGJyPgpzMSwgbGFzdCBwYXJh
OiBzL1JFQ09NTUVOREVEL3JlY29tbWVuZGVkLyAtIHRoaXMgaXNuJ3QgYSByZWNvbW1lbmRhdGlv
biBhYm91dDxicj4KdGhlIHByb3RvY29sIG9uIHRoZSB3aXJlLjxicj48L2Jsb2NrcXVvdGU+PGRp
dj4mbmJzcDs8L2Rpdj48ZGl2PltWUEJdIEZpeGVkIGluIC0wNzwvZGl2PjxkaXY+IDxicj48L2Rp
dj48YmxvY2txdW90ZSBjbGFzcz0iZ21haWxfcXVvdGUiIHN0eWxlPSJtYXJnaW46MHB4IDBweCAw
cHggMC44ZXg7Ym9yZGVyLWxlZnQ6MXB4IHNvbGlkIHJnYigyMDQsMjA0LDIwNCk7cGFkZGluZy1s
ZWZ0OjFleCI+Cjxicj4KU3ViZGl2aXNpb24gb2YgczI6Jm5ic3A7IFRoZSBpc3N1ZXMgcmVnYXJk
aW5nIHRoZSBuYXR1cmUgb2YgdGhlIGRvY3VtZW50IHdvdWxkIGJlPGJyPgpoZWxwZWQgYnkgYWx0
ZXJpbmcgczIgaW50byBmb3VyIHRvcCBsZXZlbCBzZWN0aW9ucywgdGh1czogczI6IFJlcXVpcmVt
ZW50IGZvcjxicj4KUkZDIDI5NjEgUmVmcmVzaCBPdmVyaGVhZCBSZWR1Y3Rpb24gU3VwcG9ydCBh
bmQgU3BlY2lmaWMgT3B0aW9uIENob2ljZXMgKGZyb208YnI+CnMyLjEpIHMzOiBSZXF1aXJlbWVu
dCBmb3IgUkZDIDUwNjMgQ2FwYWJpbGl0eSBPYmplY3Qgc3VwcG9ydCAoc2VlIE1pbm9yIElzc3Vl
czxicj4KYWJvdmUpIHM0OiBSZWZyZXNoLUludGVydmFsIEluZGVwZW5kZW50IFJTVlAgQ2FwYWJp
bGl0eSAoZnJvbSBzMi4zKSBzNTo8YnI+ClBlci1QZWVyIFJTVlAgRmxvdyBDb250cm9sIENhcGFi
aWxpdHkgKGZyb20gczIuNCkgU3Vic2VxdWVudCBtYWpvciBzZWN0aW9uczxicj4KdGhlbiByZW51
bWJlcmVkIGFzIHM2IG9ud2FyZHMuIFJlZmVyZW5jZXMgdG8gczIueCB3aWxsIG5lZWQgdG8gYmUg
dXBkYXRlZDxicj4KdGhyb3VnaG91dC48YnI+PC9ibG9ja3F1b3RlPjxkaXY+PGJyPjwvZGl2Pjxk
aXY+W1ZQQl0gV2Ugc3ViZGl2aWRlZCBzMiBpbnRvIDMgdG9wIGxldmVsIHNlY3Rpb25zLiBXZSBk
aWQgbm90IGFkZCBhIHNlcGFyYXRlIHNlY3Rpb24gZm9yIGRpc2N1c3NpbmcgUkZDNTA2MyBDYXBh
YmlsaXR5IE9iamVjdCBzdXBwb3J0LjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxibG9ja3F1b3RlIGNs
YXNzPSJnbWFpbF9xdW90ZSIgc3R5bGU9Im1hcmdpbjowcHggMHB4IDBweCAwLjhleDtib3JkZXIt
bGVmdDoxcHggc29saWQgcmdiKDIwNCwyMDQsMjA0KTtwYWRkaW5nLWxlZnQ6MWV4Ij4KPGJyPgpz
Mi4xICh3b3VsZCBiZSBpbnRyb2R1Y3Rpb24gb2YgbmV3IHMyKTo8YnI+Ck9MRDo8YnI+CiZuYnNw
OyAmbmJzcDtUaGUgaW1wbGVtZW50YXRpb24gcmVjb21tZW5kYXRpb25zIGRpc2N1c3NlZCBpbiB0
aGlzIHNlY3Rpb24gYXJlPGJyPgombmJzcDsgJm5ic3A7YmFzZWQgb24gdGhlIHByb3Bvc2FscyBt
YWRlIGluIFtSRkMyOTYxXSBhbmQgYWN0IGFzIHByZXJlcXVpc2l0ZXMgZm9yPGJyPgombmJzcDsg
Jm5ic3A7aW1wbGVtZW50aW5nIHRoZSB0ZWNobmlxdWVzIGRpc2N1c3NlZCBpbiBTZWN0aW9ucyAy
LjIgYW5kIDIuMy48YnI+Cjxicj4KTkVXOjxicj4KJm5ic3A7ICZuYnNwO1RoZSBDYXBhYmlsaXRp
ZXMgZGVmaW5lZCBpbiBTZWN0aW9ucyA0IGFuZCA1IG9mIHRoaXMgZG9jdW1lbnQgYXJlIGJhc2Vk
IG9uPGJyPgombmJzcDsgJm5ic3A7cHJvcG9zYWxzIG1hZGUgaW4gW1JGQzI5NjFdLiZuYnNwOyBJ
bXBsZW1lbnRhdGlvbnMgb2YgdGhlc2UgQ2FwYWJpbGl0aWVzIHdpbGw8YnI+CiZuYnNwOyAmbmJz
cDtuZWVkIHRvIHN1cHBvcnQgdGhlIFJTVlAgbWVzc2FnZXMgYW5kIHRlY2huaXF1ZXMgZGVmaW5l
ZCBpbiBbUkZDMjk2MV0gYXMgc2V0PGJyPgombmJzcDsgJm5ic3A7b3V0IGluIFNlY3Rpb24gMi4x
IFt3YXMgMi4xLjFdIHdpdGg8YnI+CiZuYnNwOyAmbmJzcDtzb21lIG1pbm9yIG1vZGlmaWNhdGlv
bnMgYW5kIGFsdGVyYXRpb25zIHRvIHJlY29tbWVuZGVkIHRpbWUgaW50ZXJ2YWxzIGFuZDxicj4K
Jm5ic3A7ICZuYnNwO2l0ZXJhdGlvbiBjb3VudHMgYXMgZGVmaW5lZCBpbiB0aGUgcmVtYWluZGVy
IG9mIHRoaXMgc2VjdGlvbi48YnI+CkVORFM8YnI+Cjxicj48L2Jsb2NrcXVvdGU+PGRpdj48YnI+
PC9kaXY+PGRpdj5bVlBCXSBGaXhlZCBpbiAtMDc8YnI+PC9kaXY+PGRpdj4gPGJyPjwvZGl2Pjxi
bG9ja3F1b3RlIGNsYXNzPSJnbWFpbF9xdW90ZSIgc3R5bGU9Im1hcmdpbjowcHggMHB4IDBweCAw
LjhleDtib3JkZXItbGVmdDoxcHggc29saWQgcmdiKDIwNCwyMDQsMjA0KTtwYWRkaW5nLWxlZnQ6
MWV4Ij4KczIuMS4xLCB0aXRsZSBhbmQgcGFyYSAxIFt3aWxsIGJlIHMyLjFdOjxicj4KT0xEOjxi
cj4KMi4xLjEuJm5ic3A7IEJhc2ljIFByZXJlcXVpc2l0ZXM8YnI+Cjxicj4KJm5ic3A7ICZuYnNw
O0FuIGltcGxlbWVudGF0aW9uIHRoYXQgc3VwcG9ydHMgdGhlIHRlY2huaXF1ZXMgZGlzY3Vzc2Vk
IGluIFNlY3Rpb25zPGJyPgombmJzcDsgJm5ic3A7Mi4yIGFuZCAyLjMgbXVzdCBtZWV0IGNlcnRh
aW4gYmFzaWMgcHJlcmVxdWlzaXRlcy48YnI+Ck5FVzo8YnI+CjIuMS4mbmJzcDsgUmVxdWlyZWQg
RnVuY3Rpb25hbGl0eSBmcm9tIFJGQyAyOTYxIHRvIGJlIEltcGxlbWVudGVkPGJyPgo8YnI+CiZu
YnNwOyAmbmJzcDtBbiBpbXBsZW1lbnRhdGlvbiB0aGF0IHN1cHBvcnRzIHRoZSBjYXBhYmlpdGll
cyBkaXNjdXNzZWQgaW4gU2VjdGlvbnM8YnI+CiZuYnNwOyAmbmJzcDs0IGFuZCA1IG11c3QgcHJv
dmlkZSBhIGxhcmdlIHN1YnNldCBvZiB0aGUgZnVuY3Rpb25hbGl0eSBkZXNjcmliZWQ8YnI+CiZu
YnNwOyAmbmJzcDtpbiBbUkZDMjk2MV0gYXMgZm9sbG93czo8YnI+CkVORFM8YnI+PC9ibG9ja3F1
b3RlPjxkaXY+PGJyPjwvZGl2PjxkaXY+W1ZQQl0gRml4ZWQgaW4gLTA3PGJyPjwvZGl2PjxkaXY+
IDxicj48L2Rpdj48YmxvY2txdW90ZSBjbGFzcz0iZ21haWxfcXVvdGUiIHN0eWxlPSJtYXJnaW46
MHB4IDBweCAwcHggMC44ZXg7Ym9yZGVyLWxlZnQ6MXB4IHNvbGlkIHJnYigyMDQsMjA0LDIwNCk7
cGFkZGluZy1sZWZ0OjFleCI+Cjxicj4KczIuMS4yLCBwYXJhIDIgW3dpbGwgYmUgczIuMl06IHMv
dGVjaG5pcXVlcyBkaXNjdXNzZWQgaW4gU2VjdGlvbnMgMi4yIGFuZDxicj4KMi4zL0NhcGFiaWxp
dGllcyBkZWZpbmVkIGluIFNlY3Rpb25zIDQgYW5kIDUvPGJyPjwvYmxvY2txdW90ZT48ZGl2Pjxi
cj48L2Rpdj48ZGl2PltWUEJdIEZpeGVkIGluIC0wNzxicj48L2Rpdj48ZGl2PiA8YnI+PC9kaXY+
PGJsb2NrcXVvdGUgY2xhc3M9ImdtYWlsX3F1b3RlIiBzdHlsZT0ibWFyZ2luOjBweCAwcHggMHB4
IDAuOGV4O2JvcmRlci1sZWZ0OjFweCBzb2xpZCByZ2IoMjA0LDIwNCwyMDQpO3BhZGRpbmctbGVm
dDoxZXgiPgo8YnI+CnMyLjEuMiwgcGFyYSAyOiBzL01FU1NBR0UgSUQvTUVTU0FHRV9JRC88YnI+
PC9ibG9ja3F1b3RlPjxkaXY+PGJyPjwvZGl2PjxkaXY+W1ZQQl0gRml4ZWQgaW4gLTA3PGJyPjwv
ZGl2PjxkaXY+IDxicj48L2Rpdj48YmxvY2txdW90ZSBjbGFzcz0iZ21haWxfcXVvdGUiIHN0eWxl
PSJtYXJnaW46MHB4IDBweCAwcHggMC44ZXg7Ym9yZGVyLWxlZnQ6MXB4IHNvbGlkIHJnYigyMDQs
MjA0LDIwNCk7cGFkZGluZy1sZWZ0OjFleCI+Cjxicj4KczIuMiwgcGFyYSAxOiBzL2ltcHJvdmVt
ZW50IG9uIHRyYW5zbWlzc2lvbiBvdmVyaGVhZC9pbXByb3ZlbWVudCBvZjxicj4KdHJhbnNtaXNz
aW9uIG92ZXJoZWFkLzxicj48L2Jsb2NrcXVvdGU+PGRpdj48YnI+PC9kaXY+PGRpdj5bVlBCXSBG
aXhlZCBpbiAtMDc8YnI+PC9kaXY+PGRpdj4gPGJyPjwvZGl2PjxibG9ja3F1b3RlIGNsYXNzPSJn
bWFpbF9xdW90ZSIgc3R5bGU9Im1hcmdpbjowcHggMHB4IDBweCAwLjhleDtib3JkZXItbGVmdDox
cHggc29saWQgcmdiKDIwNCwyMDQsMjA0KTtwYWRkaW5nLWxlZnQ6MWV4Ij4KPGJyPgpzMi4yLCBw
YXJhIDE6IHMvcHJvcG9zZXMgc3VmZmljaWVudCByZWNvbW1lbmRhdGlvbnMvc2V0cyBvdXQgYWRk
aXRpb25hbDxicj4KcmVxdWlyZW1lbnRzLzxicj48L2Jsb2NrcXVvdGU+PGRpdj48YnI+PC9kaXY+
PGRpdj5bVlBCXSBGaXhlZCBpbiAtMDc8YnI+PC9kaXY+PGRpdj4gPGJyPjwvZGl2PjxibG9ja3F1
b3RlIGNsYXNzPSJnbWFpbF9xdW90ZSIgc3R5bGU9Im1hcmdpbjowcHggMHB4IDBweCAwLjhleDti
b3JkZXItbGVmdDoxcHggc29saWQgcmdiKDIwNCwyMDQsMjA0KTtwYWRkaW5nLWxlZnQ6MWV4Ij4K
PGJyPgpzMi4yLCBsYXN0IGJ1bGxldDogQWRkIGEgcmVmZXJlbmNlIHRvIHRoZSBwcm9wb3NlZCBu
ZXcgU2VjdGlvbiAzIHRoYXQgZGlzY3Vzc2VzPGJyPgp0aGUgQ2FwYWJpbGl0eSBvYmplY3QuPGJy
PjwvYmxvY2txdW90ZT48ZGl2PiZuYnNwOzwvZGl2PjxkaXY+W1ZQQl0gQWRkZWQgYSBkaXJlY3Qg
cmVmZXJlbmNlIHRvIFJGQzUwNjM8L2Rpdj48ZGl2PiA8YnI+PC9kaXY+PGJsb2NrcXVvdGUgY2xh
c3M9ImdtYWlsX3F1b3RlIiBzdHlsZT0ibWFyZ2luOjBweCAwcHggMHB4IDAuOGV4O2JvcmRlci1s
ZWZ0OjFweCBzb2xpZCByZ2IoMjA0LDIwNCwyMDQpO3BhZGRpbmctbGVmdDoxZXgiPgo8YnI+CnMy
LjIuMSwgbGFzdCBwYXJhOiBzL3NldCBSZWZyZXNoLVJlZHVjdGlvbi1DYXBhYmxlIGJpdCBpbiBj
b21tb24gaGVhZGVyL3NldCB0aGU8YnI+ClJlZnJlc2gtUmVkdWN0aW9uLUNhcGFibGUgYml0IGlu
IHRoZSBjb21tb24gaGVhZGVyLzxicj48L2Jsb2NrcXVvdGU+PGRpdj48YnI+PC9kaXY+PGRpdj5b
VlBCXSBGaXhlZCBpbiAtMDc8YnI+PC9kaXY+PGRpdj4gPGJyPjwvZGl2PjxibG9ja3F1b3RlIGNs
YXNzPSJnbWFpbF9xdW90ZSIgc3R5bGU9Im1hcmdpbjowcHggMHB4IDBweCAwLjhleDtib3JkZXIt
bGVmdDoxcHggc29saWQgcmdiKDIwNCwyMDQsMjA0KTtwYWRkaW5nLWxlZnQ6MWV4Ij4KPGJyPgpz
Mi4zLCBwYXJhIDE6IHMvc2V0IG9mIHJlY29tbWVuZGF0aW9ucy9mdW5jdGlvbmFsaXR5Lzx3YnI+
OyBzL3Byb3ZpZGUvcHJvdmlkZXMvOzxicj4Kcy9SU1ZQLVRFIGNvbnRyb2wgcGxhbmUgY29uZ2Vz
dGlvbi9hIHNpZ25pZmljYW50IHBvcnRpb24gb2YgdGhlIFJTVlAtVEUgY29udHJvbDxicj4KbWVz
c2FnZSBsb2FkLzxicj48L2Jsb2NrcXVvdGU+PGRpdj48YnI+PC9kaXY+PGRpdj5bVlBCXSBGaXhl
ZCBpbiAtMDc8YnI+PC9kaXY+PGRpdj4gPGJyPjwvZGl2PjxibG9ja3F1b3RlIGNsYXNzPSJnbWFp
bF9xdW90ZSIgc3R5bGU9Im1hcmdpbjowcHggMHB4IDBweCAwLjhleDtib3JkZXItbGVmdDoxcHgg
c29saWQgcmdiKDIwNCwyMDQsMjA0KTtwYWRkaW5nLWxlZnQ6MWV4Ij4KPGJyPgpzMi4zLjI6IHMv
TUVTU0FHRSBJRC9NRVNTQUdFX0lELzxicj48L2Jsb2NrcXVvdGU+PGRpdj48YnI+PC9kaXY+PGRp
dj5bVlBCXSBGaXhlZCBpbiAtMDc8YnI+PC9kaXY+PGRpdj4gPGJyPjwvZGl2PjxibG9ja3F1b3Rl
IGNsYXNzPSJnbWFpbF9xdW90ZSIgc3R5bGU9Im1hcmdpbjowcHggMHB4IDBweCAwLjhleDtib3Jk
ZXItbGVmdDoxcHggc29saWQgcmdiKDIwNCwyMDQsMjA0KTtwYWRkaW5nLWxlZnQ6MWV4Ij4KPGJy
Pgo8YnI+Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzx3YnI+X19fX19fX19fX19fX19f
X188YnI+ClRlYXMgbWFpbGluZyBsaXN0PGJyPgo8YSBocmVmPSJtYWlsdG86VGVhc0BpZXRmLm9y
ZyIgdGFyZ2V0PSJfYmxhbmsiPlRlYXNAaWV0Zi5vcmc8L2E+PGJyPgo8YSBocmVmPSJodHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3RlYXMiIHJlbD0ibm9yZWZlcnJlciIgdGFy
Z2V0PSJfYmxhbmsiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbDx3YnI+aXN0aW5mby90
ZWFzPC9hPjxicj4KPC9ibG9ja3F1b3RlPjwvZGl2Pjxicj48L2Rpdj48L2Rpdj4KPC9ib2R5Pjwv
aHRtbD4=

----_com.samsung.android.email_154488561075070--


