
From nobody Sat Jul  1 07:54:00 2017
Return-Path: <David.Black@dell.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 339A1128BC8; Sat,  1 Jul 2017 07:53:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.5
X-Spam-Level: 
X-Spam-Status: No, score=-5.5 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, 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=dell.com header.b=dGs3BT0g; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=emc.com header.b=GGA9IuUs
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 v3aQQyH4PxPV; Sat,  1 Jul 2017 07:53:41 -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 C0A6F127180; Sat,  1 Jul 2017 07:53:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dell.com; i=@dell.com; q=dns/txt; s=smtpout; t=1498920482; x=1530456482; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=tOYUwwUkY2e9/jKtJgENIjVUb0YoJH7mujKOsyHFIoM=; b=dGs3BT0gZtKrnf3Cn/QcIk2kUPJTJApEs0cp+SpO9iErnc4wK3q/X1a9 zq7+HjnLoRxgGQzXil2/CYMbwHNLEoa/gmK9y13XVj6eWFQHgLXSO8lOt PTcnjDme9m9n6PT3BCVAMjoMsvP+IfK7jSiklIavFGsCDxSEG+W2ezXjd k=;
Received: from esa1.dell-outbound2.iphmx.com ([68.232.153.201]) by esa1.dell-outbound.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Jul 2017 09:47:59 -0500
From: "Black, David" <David.Black@dell.com>
Received: from mailuogwdur.emc.com ([128.221.224.79]) by esa1.dell-outbound2.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Jul 2017 20:48:28 +0600
Received: from maildlpprd53.lss.emc.com (maildlpprd53.lss.emc.com [10.106.48.157]) by mailuogwprd52.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id v61ErYiP013098 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 1 Jul 2017 10:53:35 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com v61ErYiP013098
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1498920815; bh=Ykwf0xoaRMa8qYDBCgz0fvPavOc=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=GGA9IuUskNWMoEuEzOYJK/AGlgywt0ZlRWvFxBi3pW3W128+lTToD/CBMDtfTmiLY 04t6diKSkZvUvF2jrnkfPdek6r9ZgpYl953kJDqWz5E6EVwlF00jmCV6oAYHfCscrp 9Sio0OUwsXipYFsuHC2gASiRWGyqj6w7MZFBw8/0=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com v61ErYiP013098
Received: from mailusrhubprd54.lss.emc.com (mailusrhubprd54.lss.emc.com [10.106.48.19]) by maildlpprd53.lss.emc.com (RSA Interceptor); Sat, 1 Jul 2017 10:53:19 -0400
Received: from MXHUB304.corp.emc.com (MXHUB304.corp.emc.com [10.146.3.30]) by mailusrhubprd54.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id v61ErJsN004413 (version=TLSv1.2 cipher=AES128-SHA256 bits=128 verify=FAIL); Sat, 1 Jul 2017 10:53:19 -0400
Received: from MX307CL04.corp.emc.com ([fe80::849f:5da2:11b:4385]) by MXHUB304.corp.emc.com ([10.146.3.30]) with mapi id 14.03.0352.000; Sat, 1 Jul 2017 10:53:16 -0400
To: Donald Eastlake <d3e3e3@gmail.com>
CC: Magnus Westerlund <magnus.westerlund@ericsson.com>, "tsv-art@ietf.org" <tsv-art@ietf.org>, "draft-ietf-trill-over-ip.all@ietf.org" <draft-ietf-trill-over-ip.all@ietf.org>, IETF Discussion <ietf@ietf.org>, "trill@ietf.org" <trill@ietf.org>
Subject: RE: [Tsv-art] Tsvart early review of draft-ietf-trill-over-ip-10 - ECN & DSCP considerations
Thread-Topic: [Tsv-art] Tsvart early review of draft-ietf-trill-over-ip-10 - ECN & DSCP considerations
Thread-Index: AdLurvO3SYOqL32fRKuavuJggYEWYwDffoiAABLbSJA=
Date: Sat, 1 Jul 2017 14:53:15 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949362FB59E00@MX307CL04.corp.emc.com>
References: <CE03DB3D7B45C245BCA0D243277949362FB4DF88@MX307CL04.corp.emc.com> <CAF4+nEFUmB=eMO6rvK6-YiL+3Adp_t1QVqgMDBHZFn73_JxEfw@mail.gmail.com>
In-Reply-To: <CAF4+nEFUmB=eMO6rvK6-YiL+3Adp_t1QVqgMDBHZFn73_JxEfw@mail.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: mailusrhubprd54.lss.emc.com
X-RSA-Classifications: public
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/S8IStsNa5lGhC2cqPWEah8crL7g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Jul 2017 14:53:45 -0000

QWxzbywgYXMgbm90ZWQgZWFybGllciBpbiB0aGlzIGRpc2N1c3Npb24sIFJGQyA3NjU3IGV4cGxp
Y2l0bHkgZGlzY291cmFnZXMgdXNlIG9mIG11bHRpcGxlIERTQ1BzIGluIGEgc2luZ2xlIFRDUCBj
b25uZWN0aW9uLiAgVGhhdCBuZWVkcyB0byBiZSByZWZsZWN0ZWQgaW4gdGhlIFRDUCBlbmNhcHN1
bGF0aW9uIHRleHQgaW4gdGhlIHRyaWxsLW92ZXItaXAgZHJhZnQgLSBpbiBwYXJ0aWN1bGFyLCB0
aGUgY3VycmVudCB0ZXh0IGluIFNlY3Rpb24gNC4zIG9uIG1hcHBpbmcgdG8gRFNDUHMgZnJvbSBU
UklMTCBwcmlvcml0eSBhbmQgREVJIGRvZXMgbm90IGFwcGVhciB0byBiZSBjb25zaXN0ZW50IHdp
dGggUkZDIDc2NTcgZm9yIFRDUC1iYXNlZCBlbmNhcHN1bGF0aW9uLg0KDQpUaGFua3MsIC0tRGF2
aWQNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBEb25hbGQgRWFzdGxh
a2UgW21haWx0bzpkM2UzZTNAZ21haWwuY29tXQ0KPiBTZW50OiBGcmlkYXksIEp1bmUgMzAsIDIw
MTcgOTo0MyBQTQ0KPiBUbzogQmxhY2ssIERhdmlkIDxkYXZpZC5ibGFja0BlbWMuY29tPg0KPiBD
YzogTWFnbnVzIFdlc3Rlcmx1bmQgPG1hZ251cy53ZXN0ZXJsdW5kQGVyaWNzc29uLmNvbT47IHRz
di0NCj4gYXJ0QGlldGYub3JnOyBkcmFmdC1pZXRmLXRyaWxsLW92ZXItaXAuYWxsQGlldGYub3Jn
OyBJRVRGIERpc2N1c3Npb24NCj4gPGlldGZAaWV0Zi5vcmc+OyB0cmlsbEBpZXRmLm9yZw0KPiBT
dWJqZWN0OiBSZTogW1Rzdi1hcnRdIFRzdmFydCBlYXJseSByZXZpZXcgb2YgZHJhZnQtaWV0Zi10
cmlsbC1vdmVyLWlwLTEwIC0gRUNOICYNCj4gRFNDUCBjb25zaWRlcmF0aW9ucw0KPiANCj4gSGkg
RGF2aWQsDQo+IA0KPiBPbiBNb24sIEp1biAyNiwgMjAxNyBhdCAzOjA0IFBNLCBCbGFjaywgRGF2
aWQgPERhdmlkLkJsYWNrQGRlbGwuY29tPg0KPiB3cm90ZToNCj4gPiBBZGRpbmcgc29tZSBjb21t
ZW50cyBvbiBFQ04gYW5kIERTQ1AgLi4uDQo+ID4NCj4gPj4gPiBTZWN0aW9uIDQuMzoNCj4gPj4g
Pg0KPiA+PiA+ICAgIFRSSUxMIG92ZXIgSVAgaW1wbGVtZW50YXRpb25zIE1VU1Qgc3VwcG9ydCBz
ZXR0aW5nIHRoZSBEU0NQIHZhbHVlIGluDQo+ID4+ID4gICAgdGhlIG91dGVyIElQIEhlYWRlciBv
ZiBUUklMTCBwYWNrZXRzIHRoZXkgc2VuZCBieSBtYXBwaW5nIHRoZSBUUklMTA0KPiA+PiA+ICAg
IHByaW9yaXR5IGFuZCBERUkgdG8gdGhlIERTQ1AuIFRoZXkgTUFZIHN1cHBvcnQsIGZvciBhIFRS
SUxMIERhdGENCj4gPj4gPiAgICBwYWNrZXQgd2hlcmUgdGhlIG5hdGl2ZSBmcmFtZSBwYXlsb2Fk
IGlzIGFuIElQIHBhY2tldCwgbWFwcGluZyB0aGUNCj4gPj4gPiAgICBEU0NQIGluIHRoaXMgaW5u
ZXIgSVAgcGFja2V0IHRvIHRoZSBvdXRlciBJUCBIZWFkZXIgd2l0aCB0aGUgZGVmYXVsdA0KPiA+
PiA+ICAgIGZvciB0aGF0IG1hcHBpbmcgYmVpbmcgdG8gY29weSB0aGUgRFNDUCB3aXRob3V0IGNo
YW5nZS4NCj4gPj4gPg0KPiA+PiA+IEkgdGhpbmsgaXQgaXMgZmluZSB0byByZXF1aXJlIHRoYXQg
aW1wbGVtZW50YXRpb25zIGFyZSBjYXBhYmxlIG9mIHNldHRpbmcNCj4gPj4gPiBEU0NQIHZhbHVl
cyBvbiB0aGUgb3V0ZXIgSVAgaGVhZGVyLiBIb3dldmVyLCBJIGZhaWwgdG8gc2VlIGFueSBkaXNj
dXNzaW9uIG9mDQo+ID4+ID4gdGhlIHBvdGVudGlhbCBpc3N1ZXMgd2l0aCBhY3R1YWxseSBzZXR0
aW5nIHRoZSBEU0NQIHZhbHVlcy4gSXQgaXMgb25lIHRoaW5nIHRvDQo+ID4+ID4gZG8gdGhpcyBp
biBhbiBJUCBiYWNrIGJvbmUgdXNlIGNhc2Ugd2hlcmUgb25lIGNhbiBrbm93IGFuZCBoYXZlIGNv
bnRyb2wNCj4gPj4gPiBvdmVyIHRoZSBQSEIgdGhhdCB0aGUgRFNDUCB2YWx1ZXMgbWFwcyB0by4g
QnV0IG90aGVyd2lzZSwgb3ZlciBnZW5lcmFsIGludGVybmV0IHRoZQ0KPiA+PiA+IGJlaGF2aW9y
IGlzIG5vdCB0aGF0IHByZWRpY3RhYmxlLiBPbmUgY2FuIGVhc2lseSBiZSBzdWJqZWN0IHRvIHBv
bGljZXJzIG9yDQo+ID4+ID4gcmVtYXBwaW5nLiBBbHNvIGFzIHRoZSBhY3R1YWwgRFNDUCBjb2Rl
IHBvaW50IHVzYWdlIGlzIGRvbWFpbiBzcGVjaWZpYyB0aGlzIGlzDQo+ID4+ID4gZGlmZmljdWx0
LiBQcmlvcml0eSByZXZlcnNhbCBpcyBsaWtlbHkgdGhlIGxlYXN0IG9mIHRoZSBwcm9ibGVtcyB0
aGF0IHRoaXMgY2FuDQo+ID4+ID4gcnVuIGludG8gb3ZlciBnZW5lcmFsIEludGVybmV0Lg0KPiA+
Pg0KPiA+PiBJdCBzb3VuZHMgbGlrZSBhcHByb3ByaWF0ZSBkaXNjdXNzaW9uIGFuZCB3YXJuaW5n
cyBhYm91dCB0aGVzZSBpc3N1ZXMNCj4gPj4gd291bGQgcmVzb2x2ZSB0aGUgYWJvdmUgY29tbWVu
dC4NCj4gPg0KPiA+IEZvciBFQ04sIHNlZSBSRkMgNjA0MCBhbmQgZHJhZnQtaWV0Zi10c3Z3Zy1y
ZmM2MDQwdXBkYXRlLXNoaW0uICBJbiBwYXJ0aWN1bGFyLA0KPiA+IGNvcHlpbmcgdGhlIGlubmVy
IEVDTiBjb2RlcG9pbnQgdG8gdGhlIG91dGVyIElQIGhlYWRlciBlbmNhcHN1bGF0aW9uIHdpdGhv
dXQNCj4gPiByZXF1aXJpbmcgZGVjYXBzdWxhdGlvbiBwcm9jZXNzaW5nIGFzIHNwZWNpZmllZCBp
biBSRkMgNjA0MCBvciB0aGUgNjA0MHVwZGF0ZS1zaGltDQo+ID4gZHJhZnQgY2FuIGxvc2UgY29u
Z2VzdGlvbiBpbmRpY2F0aW9ucyBmcm9tIHRoZSBuZXR3b3JrIGFuZCBoZW5jZSBpcyB3cm9uZw0K
PiA+IChpdCdzIGFsc28gd3Jvbmcgd3J0IFJGQyAzMTY4LCBidXQgUkZDIDYwNDAgYW5kIHRoZSA2
MDQwdXBkYXRlLXNoaW0gZHJhZnRzIGFyZQ0KPiA+IGJldHRlciBhbmQgbW9yZSBjdXJyZW50IHJl
ZmVyZW5jZXMpLg0KPiANCj4gVGhhdCdzIGEgZ29vZCBwb2ludC4NCj4gDQo+ID4gRm9yIERTQ1Bz
LCBzdGFydCB3aXRoIFJGQyAyOTgzIC0gdGhpbmtpbmcgYWJvdXQgdGhlIHZhbGlkaXR5IChvciBs
aWtlbHkgdmFsaWRpdHkpDQo+ID4gb2YgdGhlIG91dGVyIERTQ1AgYXQgdGhlIGRlY2Fwc3VsYXRv
ciBtYXkgaGVscCBpbiBjaG9vc2luZyB3aGV0aGVyIHRvDQo+ID4gcmVjb21tZW5kIGEgdW5pZm9y
bSBtb2RlbCAoZS5nLiwgY29weSBEU0NQIG91dCBhdCBpbmdyZXNzLCBjb3B5IGJhY2sgaW4gYXQN
Cj4gPiBlZ3Jlc3MpIG9yIGEgcGlwZSBtb2RlbCAoZS5nLiwgZG8gc29tZXRoaW5nIHJlYXNvbmFi
bGUgZm9yIG91dGVyIERTQ1AgYXQNCj4gPiBpbmdyZXNzLCBpZ25vcmUgaXQgb24gZWdyZXNzKSBh
cyB0aGUgaW1wbGVtZW50YXRpb24gZGVmYXVsdC4NCj4gDQo+IEkgYmVsaWV2ZSB0aGUgZGVmYXVs
dCBiZWhhdmlvciBpbiB0aGUgY3VycmVudCBkcmFmdCBpcyB0aGUgYmVzdA0KPiBkZWZhdWx0LiBU
aGF0IHNldHMgRFNDUCBiYXNlZCBvbiB0aGUgc2FtZSBUUklMTCBIZWFkZXIgaW5kaWNpYSB0aGF0
DQo+IGNvbnRyb2xzIGRlZmF1bHQgUW9TIG9uIG5vbi1JUCBsaW5rcy4NCj4gDQo+ID4gLS0gRFND
UCBtYXBwaW5nIHRvL2Zyb20gVFJJTEwvRXRoZXJuZXQgcHJpb3JpdGllcw0KPiA+DQo+ID4+IFRo
ZSBpbnRlbnQgaW4gdGhlIGRyYWZ0IGlzIHRvIHJlZmxlY3QgdGhlIGRlZmF1bHQgcmVsYXRpdmUg
cHJpb3JpdHkgb2YNCj4gPj4gdGhlIGRpZmZlcmVudCBwcmlvcml0eSBjb2RlIHBvaW50cyBpbiBJ
RUVFIFN0ZCA4MDIuMVEgd2hlcmUgcHJpb3JpdHkgMQ0KPiA+PiBpcyBsb3dlciB0aGFuIHByaW9y
aXR5IDAuIEF0IGEgcXVpY2sgbG9vaywgaXQgYXBwZWFycyB0byBtZSB0aGF0IFJGQw0KPiA+PiAy
NDc0IHJlcXVpcmVzIHRoYXQgMHgwMDEwMDAgYmUgaGFuZGxlZCBhcyBiZWluZyBvZiBhIHByaW9y
aXR5IG5vdA0KPiA+PiBsb3dlciB0aGFuIHRoZSBwcmlvcml0eSB3aXRoIHdoaWNoIDB4MDAwMDAw
IGlzIGhhbmRsZWQuIFlldCBSRkMgMzY2MiwNCj4gPj4gd2hpY2ggeW91IHBvaW50IHRvLCBzZWVt
cyB0byBzdWdnZXN0IHVzaW5nIDB4MDAxMDAwIGFzIGEgbG93ZXINCj4gPj4gcHJpb3JpdHkgY29k
ZSBwb2ludCB0aGFuIDB4MDAwMDAwLiBHaXZlbiB0aGF0IDM2NjIgbm90IG9ubHkgZG9lcyBub3QN
Cj4gPj4gdXBkYXRlIDI0NzQgYnV0IGlzIG9ubHkgSW5mb3JtYXRpb25hbCB3aGlsZSAyNDc0IGlz
IFN0YW5kYXJkcyBUcmFjaywgSQ0KPiA+PiB3b3VsZCBzYXkgdGhhdCAyNDc0IGRvbWluYXRlcyBh
bmQgdGhhdCB0aGlzIGRyYWZ0IG1ha2VzIHRoZSBiZXN0DQo+ID4+IGFzc3VtcHRpb25zIGl0IGNh
biBhYm91dCBkZWZhdWx0IGJlaGF2aW9yLi4uDQo+ID4NCj4gPiBXZWxsIC4uLiB0aGF0J3MgYSBk
aXNjdXNzaW9uIGFib3V0IHRleHQgaW4gUkZDcyB0aGF0IGFyZSB3ZWxsIG92ZXIgYSBkZWNhZGUN
Cj4gPiBvbGQsIGFuZCBpbiBhbiBhcmVhIChsZXNzLXRoYW4tYmVzdC1lZmZvcnQgc2VydmljZSkg
d2hlcmUgdGhlIGFzcGlyYXRpb25zDQo+ID4gb2YgYXQgbGVhc3QgUkZDIDM2NjIgd2VyZW4ndCBy
ZWFsaXplZCAuLi4gYnV0IHRoYXQgUkZDIGlzIG5vdCBzYWZlIHRvIGlnbm9yZSwNCj4gPiBlaXRo
ZXIuDQo+ID4NCj4gPiBJbiBwcmFjdGljZSwgdGhlIHNwZWNpZmljYXRpb24gb2YgQ1MxIGZvciBs
ZXNzLXRoYW4tYmVzdC1lZmZvcnQgc2VydmljZSBoYXMNCj4gPiBiZWVuIHByb211bGdhdGVkIGJ5
IFJGQyA0NTk0IHJhdGhlciB0aGFuIFJGQyAzNjYyLCBhbmQgUkZDIDQ1OTQgaGFzDQo+ID4gaGFk
IHNpZ25pZmljYW50ICJydW5uaW5nIGNvZGUiIGltcGFjdCBvbiBuZXR3b3JrIGRlc2lnbiBhbmQg
b3BlcmF0aW9uLg0KPiA+DQo+ID4gQXMgTWFnbnVzIG1lbnRpb25lZCBSRkM3NjU3LCBJIHN0cm9u
Z2x5IHN1Z2dlc3Qgc3RhcnRpbmcgZnJvbSB0aGUNCj4gPiBSRkMgNzY1NyBkaXNjdXNzaW9uIG9m
IHRoaXMgdG9waWMgaW4gb3JkZXIgdG8gZmlndXJlIG91dCB3aGF0IHRvIGRvLiAgSSdtDQo+ID4g
bm90IHN1cmUgd2hhdCB0byByZWNvbW1lbmQsIGJ1dCBJIGRvIHRoaW5rIHRoYXQgc3RhcnRpbmcg
ZnJvbQ0KPiA+IFJGQyA3NjU3IChyYXRoZXIgdGhhbiBSRkMgMjQ3NCBhbmQgUkZDIDM2NjIpIGlz
IHRoZSBiZXR0ZXIgYXBwcm9hY2guDQo+IA0KPiBPSy4NCj4gDQo+ID4gRldJVywgdGhlIFRTVldH
IFdHIGlzIGluIHRoZSBwcm9jZXNzIG9mIGZpZ3VyaW5nIG91dCB3aGljaCBEU0NQDQo+ID4gdG8g
cmVjb21tZW5kIGZvciBsZXNzLXRoYW4tYmVzdC1lZmZvcnQtc2VydmljZSBpbiBwbGFjZSBvZiBD
UzEgLSB0aGF0J3MNCj4gPiBsaWtlbHkgdG8gYmUgYW4gYWN0aXZlIHRvcGljIG9mIGRpc2N1c3Np
b24gaW4gUHJhZ3VlLg0KPiANCj4gSSdsbCB0cnkgdG8gYXR0ZW5kIHRoYXQgc2Vzc2lvbi4NCj4g
DQo+IFRoYW5rcywNCj4gRG9uYWxkDQo+ID09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0N
Cj4gIERvbmFsZCBFLiBFYXN0bGFrZSAzcmQgICArMS01MDgtMzMzLTIyNzAgKGNlbGwpDQo+ICAx
NTUgQmVhdmVyIFN0cmVldCwgTWlsZm9yZCwgTUEgMDE3NTcgVVNBDQo+ICBkM2UzZTNAZ21haWwu
Y29tDQo+IA0KPiA+IFRoYW5rcywgLS1EYXZpZA0KPiA+DQo+ID4+IC0tLS0tT3JpZ2luYWwgTWVz
c2FnZS0tLS0tDQo+ID4+IEZyb206IFRzdi1hcnQgW21haWx0bzp0c3YtYXJ0LWJvdW5jZXNAaWV0
Zi5vcmddIE9uIEJlaGFsZiBPZiBEb25hbGQNCj4gPj4gRWFzdGxha2UNCj4gPj4gU2VudDogU3Vu
ZGF5LCBKdW5lIDI1LCAyMDE3IDg6MDcgUE0NCj4gPj4gVG86IE1hZ251cyBXZXN0ZXJsdW5kIDxt
YWdudXMud2VzdGVybHVuZEBlcmljc3Nvbi5jb20+DQo+ID4+IENjOiB0c3YtYXJ0QGlldGYub3Jn
OyBkcmFmdC1pZXRmLXRyaWxsLW92ZXItaXAuYWxsQGlldGYub3JnOyBJRVRGIERpc2N1c3Npb24N
Cj4gPj4gPGlldGZAaWV0Zi5vcmc+OyB0cmlsbEBpZXRmLm9yZw0KPiA+PiBTdWJqZWN0OiBSZTog
W1Rzdi1hcnRdIFRzdmFydCBlYXJseSByZXZpZXcgb2YgZHJhZnQtaWV0Zi10cmlsbC1vdmVyLWlw
LTEwDQo+ID4+DQo+ID4+IEhpIE1hZ251cywNCj4gPj4NCj4gPj4gVGhhbmtzIGZvciB0aGUgZXh0
ZW5zaXZlIHJldmlldy4gU2VlIG15IHJlc3BvbnNlcyBiZWxvdy4NCj4gPj4NCj4gPj4gT24gVGh1
LCBKdW4gMTUsIDIwMTcgYXQgMTozMiBQTSwgTWFnbnVzIFdlc3Rlcmx1bmQNCj4gPj4gPG1hZ251
cy53ZXN0ZXJsdW5kQGVyaWNzc29uLmNvbT4gd3JvdGU6DQo+ID4+ID4NCj4gPj4gPiBSZXZpZXdl
cjogTWFnbnVzIFdlc3Rlcmx1bmQNCj4gPj4gPiBSZXZpZXcgcmVzdWx0OiBOb3QgUmVhZHkNCj4g
Pj4gPg0KPiA+PiA+IEVhcmx5IHJldmlldyBvZiBkcmFmdC1pZXRmLXRyaWxsLW92ZXItaXAtMTAN
Cj4gPj4gPiBSZXZpZXdlcjogTWFnbnVzIFdlc3Rlcmx1bmQNCj4gPj4gPiBSZXZpZXcgcmVzdWx0
OiBOb3QgUmVhZHkNCj4gPj4gPg0KPiA+PiA+IFRTVi1BUlQgcmV2aWV3IGNvbW1lbnRzOg0KPiA+
PiA+DQo+ID4+ID4gSSBoYXZlIHNldCB0aGlzIHRvIG5vdCByZWFkeSBhcyB0aGVyZSBhcmUgc2V2
ZXJhbCBpc3N1ZXMsIHNvbWUgc2lnbmlmaWNhbnQNCj4gdGhhdA0KPiA+PiA+IGNvdWxkIGFmZmVj
dCB0aGUgcHJvdG9jb2wgcmVhbGl6YXRpb24gc2lnbmlmaWNhbnRseS4gU29tZSBtYXkgYmUgbWUN
Cj4gbWlzc2luZw0KPiA+PiA+IHRoaW5ncyBpbiBUUklMTCwgSSB3YXMgbm90IHRoYXQgZmFtaWxp
YXIgd2l0aCBpdCBiZWZvcmUgdGhpcyByZXZpZXcgYW5kIEkgaGF2ZQ0KPiA+PiA+IG9ubHkgdHJp
ZWQgbG9va2luZyB1cCB0aGluZ3MsIG5vdCByZWFkaW5nIHRoZSB3aG9sZSBlYXJsaWVyIHNwZWNp
ZmljYXRpb25zLg0KPiBTbw0KPiA+PiA+IGRvbid0IGhlc2l0YXRlIHRvIHB1c2ggYmFjayBhbmQg
cHJvdmlkZSBwb2ludGVycyB0byB0aGluZ3MgdGhhdCBjYW4NCj4gcmVzb2x2ZQ0KPiA+PiA+IGlz
c3Vlcy4gVGhlIGF1dGhvcnMgYW5kIHRoZSBXRyBjbGVhcmx5IGhhdmUgdGhvdWdodCBhYm91dCBh
IGxvdCBvZiBpc3N1ZXMNCj4gPj4gYW5kDQo+ID4+ID4gZGVhbHQgd2l0aCBtdWNoIGFscmVhZHku
DQo+ID4+DQo+ID4+IE9LLiBIb3BlZnVsbHkgd2UgY2FuIHJlc29sdmUgdGhlc2Ugb25lIHdheSBv
ciB0aGUgb3RoZXIuDQo+ID4+DQo+ID4+ID4gRGlmZnNlcnYgdXNhZ2UNCj4gPj4gPiAtLS0tLS0t
LS0tLS0tLQ0KPiA+PiA+DQo+ID4+ID4gU2VjdGlvbiA0LjM6DQo+ID4+ID4NCj4gPj4gPiAgICBU
UklMTCBvdmVyIElQIGltcGxlbWVudGF0aW9ucyBNVVNUIHN1cHBvcnQgc2V0dGluZyB0aGUgRFND
UCB2YWx1ZSBpbg0KPiA+PiA+ICAgIHRoZSBvdXRlciBJUCBIZWFkZXIgb2YgVFJJTEwgcGFja2V0
cyB0aGV5IHNlbmQgYnkgbWFwcGluZyB0aGUgVFJJTEwNCj4gPj4gPiAgICBwcmlvcml0eSBhbmQg
REVJIHRvIHRoZSBEU0NQLiBUaGV5IE1BWSBzdXBwb3J0LCBmb3IgYSBUUklMTCBEYXRhDQo+ID4+
ID4gICAgcGFja2V0IHdoZXJlIHRoZSBuYXRpdmUgZnJhbWUgcGF5bG9hZCBpcyBhbiBJUCBwYWNr
ZXQsIG1hcHBpbmcgdGhlDQo+ID4+ID4gICAgRFNDUCBpbiB0aGlzIGlubmVyIElQIHBhY2tldCB0
byB0aGUgb3V0ZXIgSVAgSGVhZGVyIHdpdGggdGhlIGRlZmF1bHQNCj4gPj4gPiAgICBmb3IgdGhh
dCBtYXBwaW5nIGJlaW5nIHRvIGNvcHkgdGhlIERTQ1Agd2l0aG91dCBjaGFuZ2UuDQo+ID4+ID4N
Cj4gPj4gPiBJIHRoaW5rIGl0IGlzIGZpbmUgdG8gcmVxdWlyZSB0aGF0IGltcGxlbWVudGF0aW9u
cyBhcmUgY2FwYWJsZSAgb2Ygc2V0dGluZw0KPiA+PiA+IERTQ1AgdmFsdWVzIG9uIHRoZSBvdXRl
ciBJUCBoZWFkZXIuIEhvd2V2ZXIsIEkgZmFpbCB0byBzZWUgYW55IGRpc2N1c3Npb24NCj4gb2YN
Cj4gPj4gPiB0aGUgcG90ZW50aWFsIGlzc3VlcyB3aXRoIGFjdHVhbGx5IHNldHRpbmcgdGhlIERT
Q1AgdmFsdWVzLiBJdCBpcyBvbmUgdGhpbmcNCj4gdG8NCj4gPj4gPiBkbyB0aGlzIGluIGFuIElQ
IGJhY2sgYm9uZSB1c2UgY2FzZSB3aGVyZSBvbmUgY2FuIGtub3cgYW5kIGhhdmUgY29udHJvbA0K
PiA+PiBvdmVyDQo+ID4+ID4gdGhlIFBIQiB0aGF0IHRoZSBEU0NQIHZhbHVlcyBtYXBzIHRvLiBC
dXQgb3RoZXJ3aXNlLCBvdmVyIGdlbmVyYWwNCj4gPj4gaW50ZXJuZXQgdGhlDQo+ID4+ID4gYmVo
YXZpb3IgaXMgbm90IHRoYXQgcHJlZGljdGFibGUuIE9uZSBjYW4gZWFzaWx5IGJlIHN1YmplY3Qg
dG8gcG9saWNlcnMgb3INCj4gPj4gPiByZW1hcHBpbmcuIEFsc28gYXMgdGhlIGFjdHVhbCBEU0NQ
IGNvZGUgcG9pbnQgdXNhZ2UgaXMgZG9tYWluIHNwZWNpZmljDQo+IHRoaXMNCj4gPj4gaXMNCj4g
Pj4gPiBkaWZmaWN1bHQuIFByaW9yaXR5IHJldmVyc2FsIGlzIGxpa2VseSB0aGUgbGVhc3Qgb2Yg
dGhlIHByb2JsZW1zIHRoYXQgdGhpcyBjYW4NCj4gPj4gPiBydW4gaW50byBvdmVyIGdlbmVyYWwg
SW50ZXJuZXQuDQo+ID4+DQo+ID4+IEl0IHNvdW5kcyBsaWtlIGFwcHJvcHJpYXRlIGRpc2N1c3Np
b24gYW5kIHdhcm5pbmdzIGFib3V0IHRoZXNlIGlzc3Vlcw0KPiA+PiB3b3VsZCByZXNvbHZlIHRo
ZSBhYm92ZSBjb21tZW50Lg0KPiA+Pg0KPiA+PiA+IFNlY3Rpb24gNC4zOg0KPiA+PiA+DQo+ID4+
ID4gICAgVGhlIGRlZmF1bHQgVFJJTEwgcHJpb3JpdHkgYW5kIERFSSB0byBEU0NQIG1hcHBpbmcs
IHdoaWNoIG1heSBiZQ0KPiA+PiA+ICAgIGNvbmZpZ3VyZWQgcGVyIFRSSUxMIG92ZXIgSVAgcG9y
dCwgaXMgYW4gZm9sbG93cy4gTm90ZSB0aGF0IHRoZSBERUkNCj4gPj4gPiAgICB2YWx1ZSBkb2Vz
IG5vdCBhZmZlY3QgdGhlIGRlZmF1bHQgbWFwcGluZyBhbmQsIHRvIHByb3ZpZGUgYQ0KPiA+PiA+
ICAgIHBvdGVudGlhbGx5IGxvd2VyIHByaW9yaXR5IHNlcnZpY2UgdGhhbiB0aGUgZGVmYXVsdCBw
cmlvcml0eSAwLA0KPiA+PiA+ICAgIHByaW9yaXR5IDEgaXMgY29uc2lkZXJlZCBsb3dlciBwcmlv
cml0eSB0aGFuIDAuIFNvIHRoZSBwcmlvcml0eQ0KPiA+PiA+ICAgIHNlcXVlbmNlIGZyb20gbG93
ZXIgdG8gaGlnaGVyIHByaW9yaXR5IGlzIDEsIDAsIDIsIDMsIDQsIDUsIDYsIDcuDQo+ID4+ID4N
Cj4gPj4gPiAgICAgICBUUklMTCBQcmlvcml0eSAgREVJICBEU0NQIEZpZWxkIChCaW5hcnkvZGVj
aW1hbCkNCj4gPj4gPiAgICAgICAtLS0tLS0tLS0tLS0tLSAgLS0tICAtLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLQ0KPiA+PiA+ICAgICAgICAgICAgICAgICAgIDAgICAwLzEgIDAwMTAwMCAv
IDgNCj4gPj4gPiAgICAgICAgICAgICAgICAgICAxICAgMC8xICAwMDAwMDAgLyAwDQo+ID4+ID4g
ICAgICAgICAgICAgICAgICAgMiAgIDAvMSAgMDEwMDAwIC8gMTYNCj4gPj4gPiAgICAgICAgICAg
ICAgICAgICAzICAgMC8xICAwMTEwMDAgLyAyNA0KPiA+PiA+ICAgICAgICAgICAgICAgICAgIDQg
ICAwLzEgIDEwMDAwMCAvIDMyDQo+ID4+ID4gICAgICAgICAgICAgICAgICAgNSAgIDAvMSAgMTAx
MDAwIC8gNDANCj4gPj4gPiAgICAgICAgICAgICAgICAgICA2ICAgMC8xICAxMTAwMDAgLyA0OA0K
PiA+PiA+ICAgICAgICAgICAgICAgICAgIDcgICAwLzEgIDExMTAwMCAvIDU2DQo+ID4+ID4NCj4g
Pj4gPiBUaGlzIGFwcGVhciB0byBiZSBhbiBwcm9ibGVtYXRpYyBtYXBwaW5nLiBBdCBsZWFzdCBm
b3IgcHJpbyAwIGFuZCAxLiBBcw0KPiA+PiA+IHByaW9yaXR5IDEgYXBwZWFycyB0byBiZSBpbnRl
bmRlZCB0byBiZSBoaWdoZXIgdGhhbiBwcmlvcml0eSAwLCBpdCBpcw0KPiA+PiA+IGludGVyZXN0
aW5nIHRoYXQgaXQgaXMgbWFwcGVkIHRvIENTMSwgd2hpY2ggdG8gcXVvdGUNCj4gPj4gPiBodHRw
czovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9yZmM3NjU3LzoNCj4gPj4gPg0KPiA+PiA+IENT
MSAoJzAwMTAwMCcpIHdhcyBzdWJzZXF1ZW50bHkgZGVzaWduYXRlZCBhcyB0aGUgcmVjb21tZW5k
ZWQNCj4gPj4gPiAgICAgICBjb2RlcG9pbnQgZm9yIHRoZSBMb3dlciBFZmZvcnQgKExFKSBQSEIg
W1JGQzM2NjJdLg0KPiA+PiA+DQo+ID4+ID4gU28gd2hhdCBpcyBwcm9wb3NlZCBjYW4gaW4gYSBu
ZXR3b3JrIHVzaW5nIGRlZmF1bHQgbWFwcGluZywgcmVzdWx0IGluDQo+IHRoYXQNCj4gPj4geW91
DQo+ID4+ID4gZ2V0IHByaW9yaXR5IDAgdG8gYmUgbG93ZXIgcHJpb3JpdHkgdGhhbiAxLiBQbHVz
IHRoYXQgaW4gc29tZSBuZXR3b3JrcyB0aGlzDQo+IGNhbg0KPiA+PiA+IGFsc28gcmVzdWx0cyBp
biBzdHJhbmdlIHJlbWFwcGluZyB0aGF0IHJlc3VsdHMgaW4gYSBkaWZmZXJlbnQgUEhCIGZvciBD
UzENCj4gPj4gdGhhbi4NCj4gPj4NCj4gPj4gVGhlIGludGVudCBpbiB0aGUgZHJhZnQgaXMgdG8g
cmVmbGVjdCB0aGUgZGVmYXVsdCByZWxhdGl2ZSBwcmlvcml0eSBvZg0KPiA+PiB0aGUgZGlmZmVy
ZW50IHByaW9yaXR5IGNvZGUgcG9pbnRzIGluIElFRUUgU3RkIDgwMi4xUSB3aGVyZSBwcmlvcml0
eSAxDQo+ID4+IGlzIGxvd2VyIHRoYW4gcHJpb3JpdHkgMC4gQXQgYSBxdWljayBsb29rLCBpdCBh
cHBlYXJzIHRvIG1lIHRoYXQgUkZDDQo+ID4+IDI0NzQgcmVxdWlyZXMgdGhhdCAweDAwMTAwMCBi
ZSBoYW5kbGVkIGFzIGJlaW5nIG9mIGEgcHJpb3JpdHkgbm90DQo+ID4+IGxvd2VyIHRoYW4gdGhl
IHByaW9yaXR5IHdpdGggd2hpY2ggMHgwMDAwMDAgaXMgaGFuZGxlZC4gWWV0IFJGQyAzNjYyLA0K
PiA+PiB3aGljaCB5b3UgcG9pbnQgdG8sIHNlZW1zIHRvIHN1Z2dlc3QgdXNpbmcgMHgwMDEwMDAg
YXMgYSBsb3dlcg0KPiA+PiBwcmlvcml0eSBjb2RlIHBvaW50IHRoYW4gMHgwMDAwMDAuIEdpdmVu
IHRoYXQgMzY2MiBub3Qgb25seSBkb2VzIG5vdA0KPiA+PiB1cGRhdGUgMjQ3NCBidXQgaXMgb25s
eSBJbmZvcm1hdGlvbmFsIHdoaWxlIDI0NzQgaXMgU3RhbmRhcmRzIFRyYWNrLCBJDQo+ID4+IHdv
dWxkIHNheSB0aGF0IDI0NzQgZG9taW5hdGVzIGFuZCB0aGF0IHRoaXMgZHJhZnQgbWFrZXMgdGhl
IGJlc3QNCj4gPj4gYXNzdW1wdGlvbnMgaXQgY2FuIGFib3V0IGRlZmF1bHQgYmVoYXZpb3IuLi4N
Cj4gPj4NCj4gPj4gPiBNVFUgYW5kIEZyYWdtZW50YXRpb24NCj4gPj4gPiAtLS0tLS0tLS0tLS0t
LS0tLS0tLS0NCj4gPj4gPg0KPiA+PiA+IEkgdGhpbmsgdGhlcmUgYXJlIHR3byBtYWluIGlzc3Vl
IGhlcmUuIFRoZSBmaXJzdCBvbmUgaXMgTVRVRCBkaXNjb3ZlcnkNCj4gPj4gPiBvZiB0aGUgYWN0
dWFsIElQIHBhdGggTVRVIGJldHdlZW4gdGhlIHBvcnRzLiBUaGF0IHdpbGwgYmUgbmVlZGVkIHRv
DQo+ID4+IHByZXZlbnQNCj4gPj4gPiBhIGxvdCBvZiB0cmFmZmljIGdvaW5nIGludG8gTVRVIGJs
YWNrIGhvbGVzLiBFc3BlY2lhbGx5IGFzIFRSSUxMIHJlcXVyaWVzDQo+ID4+ID4gMTQ3MCBieXRl
IHN1cHBvcnQgd2hpY2ggaXMgbGlrZXkgYWJvdmUgYSBsb3Qgb2YgcGF0aHMuDQo+ID4+DQo+ID4+
IFNlZW1zIGxpa2UgaXQgd291bGQgZGVwZW5kIG9uIHRoZSBlbnZpcm9ubWVudHMgd2hlcmUgVFJJ
TEwgd2FzIHVzZWQuDQo+ID4+IEZvciBleGFtcGxlLCBJIGRvIG5vdCB0aGluayAxNDcwIHdvdWxk
IGJlIGEgcHJvYmxlbSBpbiBtb3N0IERhdGENCj4gPj4gQ2VudGVyIG9yIEludGVybmV0IEV4Y2hh
bmdlIHBvaW50IHVzZXMsIGZvciBleGFtcGxlLiBEYXRhIENlbnRlcnMNCj4gPj4gc29tZXRpbWVz
IHN1cHBvcnQgOUsganVtYm8gZnJhbWVzIGFuZCB0aGUgbGlrZS4NCj4gPj4NCj4gPj4gSW4gZmFj
dCwgaXQgaXMgcHJvYmFibHkgYmFkIHRvIGZvY3VzIHRvbyBtdWNoIG9uIDE0NzAgLS0gdGhhdCBp
cyBhDQo+ID4+IHJlcXVpcmVkIG1pbmltdW0gdG8gYmUgc3VyZSB0aGF0IHJlYXNvbmFibGUgc2l6
ZSBsaW5rIHN0YXRlIFBEVXMgY2FuDQo+ID4+IGJlIHN1Y2Nlc3NmdWxseSBmbG9vZGVkIHRocm91
Z2ggdGhlIFRSSUxMIGNhbXB1cyBzbyB0aGF0IHJvdXRpbmcgd2lsbA0KPiA+PiB3b3JrLiBIb3dl
dmVyLCBpdCB3b3VsZCBjb21tb25seSBiZSB0aGUgY2FzZSB0aGF0LCBmb3IgdGhlIFRSSUxMDQo+
ID4+IGNhbXB1cyB0byBiZSB1c2VmdWwgaW4gYSBwYXJ0aWN1bGFyIGNhc2UsIGxpbmtzIG5lZWQg
dG8gYmUgYWJsZSB0bw0KPiA+PiBjYXJyeSB0aGUgZXhwZWN0ZWQgc2l6ZSBUUklMTCBEYXRhIHBh
Y2tldHMuIEZvciBleGFtcGxlLCBpZiB0aGVyZSB3ZXJlDQo+ID4+IHR3byBwYXJ0cyBvZiBhIFRS
SUxMIGNhbXB1cyBjb25uZWN0ZWQgYnkgb25lIG9yIGEgZmV3IFRSSUxMIG92ZXIgSVANCj4gPj4g
bGlua3MgYW5kIHRoZSBlbmQgc3RhdGlvbnMgaW4gZWFjaCBwYXJ0IHdlcmUgYXNzdW1pbmcgdGhl
eSBjb3VsZCB1c2UNCj4gPj4gMTUwMCBieXRlIEV0aGVybmV0IHBhY2tldHMsIHRoZW4gdGhlIFRS
SUxMIG92ZXIgSVAgbGlua3Mgd291bGQgbmVlZCB0bw0KPiA+PiBzdXBwb3J0IGFuIE1UVSBiYXNl
ZCBvbiAxNTAwICsgVFJJTEwgSGVhZGVyICsgSVAgYW5kIFRSSUxMIG92ZXIgSVANCj4gPj4gZW5j
YXBzdWxhdGlvbi4gQW5kIG1vcmUgaWYgc2VjdXJpdHkgd2FzIGJlaW5nIHVzZWQgb3IgdGhlcmUg
d2VyZSBhbnkNCj4gPj4gb3RoZXIgcmVhc29ucyBmb3IgYWRkaXRpb25hbCBoZWFkZXJzL2VuY2Fw
c3VsYXRpb24uLi4NCj4gPj4NCj4gPj4gPiBTZWN0aW9uIDguNDoNCj4gPj4gPg0KPiA+PiA+ICAg
IFBhdGggTVRVIGRpc2NvdmVyeSBbUkZDNDgyMV0gc2hvdWxkIGJlIHVzZWZ1bA0KPiA+PiA+ICAg
IGluIGRldGVybWluaW5nIHRoZSBJUCBNVFUgYmV0d2VlbiBhIHBhaXIgb2YgUkJyaWRnZSBwb3J0
cyB3aXRoIElQDQo+ID4+ID4gICAgY29ubmVjdGl2aXR5Lg0KPiA+PiA+DQo+ID4+ID4gVGhlIGlz
c3VlIHdpdGggUkZDNDgyMSBpcyB0aGF0IGl0IGhhcyByZXF1aXJlbWVudHMgb24gdGhlIHBhY2tl
dGl6YXRpb24NCj4gPj4gbGF5ZXIuDQo+ID4+ID4gVHJpbGwgYXBwZWFycyB0byBoYXZlIHNldmVy
YWwgY29tcG9uZW50cyB0aGF0IGFyZSB1c2VmdWwuIEhvd2V2ZXIsIGl0IHdpbGwNCj4gPj4gPiBy
ZXF1aXJlIGEgc3BlY2lmaWNhdGlvbiBvZiB0aGUgcHJvY2VkdXJlIHRvIHJlc3VsdCBpbiBhIHVz
ZWZ1bCB0b29sLg0KPiA+Pg0KPiA+PiBTZWUgYmVsb3cuDQo+ID4+DQo+ID4+ID4gU2VjdGlvbiA4
LjQ6DQo+ID4+ID4NCj4gPj4gPiAgICBUUklMTCBJUy1JUyBNVFUgUERVcywgYXMgc3BlY2lmaWVk
IGluIFNlY3Rpb24gNSBvZiBbUkZDNjMyNV0gYW5kIGluDQo+ID4+ID4gICAgW1JGQzcxNzddLCBj
YW4gYmUgdXNlZCB0byBvYnRhaW4gYWRkZWQgYXNzdXJhbmNlIG9mIHRoZSBNVFUgb2YgYQ0KPiA+
PiA+ICAgIGxpbmsuDQo+ID4+ID4NCj4gPj4gPiBZZXMsIHRoYXQgY2FuIGNvbmZpcm0gd29ya2lu
ZyBNVFVzIHRoYXQgYXJlIGF0IDE0NzAgb3IgYWJvdmUsIGJ1dA0KPiBhcHBlYXJzDQo+ID4+ID4g
cHJldmVudGVkIGZyb20gd29ya2luZyBiZWxvdyAxNDcwPw0KPiA+Pg0KPiA+PiBXaGlsZSB0aGVy
ZSBpcyBhIG1pbmltdW0gc2l6ZSBmb3IgVFJJTEwgSVMtSVMgTVRVIFBEVXMsIGRldGVybWluZWQg
YnkNCj4gPj4gaGVhZGVyIHNpemUsIGl0IGlzIHdlbGwgYmVsb3cgMTQ3MCwgcHJvYmFibHkgKGRl
cGVuZGluZyBvbiB3aGV0aGVyDQo+ID4+IHNlY3VpcnR5IGlzIGluIHVzZSwgZXRjLikgYmVsb3cg
MTUwIGJ5dGVzLg0KPiA+Pg0KPiA+PiA+IFRodXMsIGl0IGFwcGVhcnMgdGhhdCB0aGVyZSBpcyBh
IGxhY2sgb2YgbWVjaGFuaXNtIGhlcmUgdG8gYWN0dWFsbHkgZ2V0IGENCj4gdmFsaWQNCj4gPj4g
PiBhbmQgZnVuY3Rpb25hbCBNVFUgZnJvbSBUUklMTCBpbiB0aGUgY2FzZXMgd2hlcmUgdGhlIFBh
dGggTVRVIGlzIGJlbG93DQo+ID4+IDE0NzAuIElmDQo+ID4+ID4gSSBhbSB3cm9uZyBnb29kLCBi
dXQgSSB0aGluayB0aGlzIGlzIGFuIGltcG9ydGFudCBwaWVjZSBmb3IgaG93IHRvIGhhbmRsZQ0K
PiA+PiB0aGUNCj4gPj4gPiBuZXh0IG1haW4gaXNzdWUuDQo+ID4+DQo+ID4+IEhvdyBhYm91dCBy
ZWZlcmVuY2luZyBTZWN0aW9uIDMgb2YNCj4gPj4gaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1s
L2RyYWZ0LWlldGYtdHJpbGwtbXR1LW5lZ290aWF0aW9uLTA1DQo+ID4+IHdoaWNoIGlzIGN1cnJl
bnRseSBpbiBJRVRGIExhc3QgQ2FsbD8gKFRoZSB3b3JkaW5nIG9mIHRoYXQgc2VjdGlvbiBpcw0K
PiA+PiBwcm9iYWJseSBnb2luZyB0byBiZSBpbXByb3ZlZCBiYXNlZCBvbiBhbiBPUFMgcmV2aWV3
IGJ5IEJyaWFuDQo+ID4+IENhcnBlbnRlci4pDQo+ID4+DQo+ID4+ID4gVURQIGVuY2Fwc3VsYXRp
b24gYW5kIElQIGZyYWdtZW50cy4NCj4gPj4gICAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tDQo+ID4+ID4gSSBzZWUgaXQgYXMgYSBiaWcgaXNzdWUgdGhhdCBVRFAgZW5jYXBzdWxh
dGlvbiBpcyB0aGUgbmF0aXZlIG9uZSwgYW5kIHRoYXQNCj4gPj4gPiByZWxpZXMgb24gSVAgZnJh
Z21lbnRhdGlvbiBkZXNwaXRlIHRoZSBuZWVkIGZvciByZWxpYWJsZSBmcmFnbWVudGF0aW9uLg0K
PiA+PiBXaXRoDQo+ID4+ID4gdGhlIHNldHVwIG9mIGhhdmluZyB0byBzdXBwb3J0IDE0NzAgTVRV
IG9uIFRSSUxMIGxldmVsIHNvbWUgcGFja2V0cyB3aWxsDQo+ID4+IGJlDQo+ID4+ID4gZnJhZ21l
bnRlZCBpbiBtYW55IGVudmlyb25tZW50cy4gVGhhdCB3aWxsIGxlYWQgdG8gYSBsb3Qgb2YgbG9z
c2VzLCBhbmQgYXMNCj4gPj4gPiBkaXNjdXNzZWQgYmVsb3cgYSB2ZXJ5IGJpZyBwcm9ibGVtIHdp
dGggbWlkZGxlYm94ZXMuIFRoZSBtYWluIHByb2JsZW0NCj4gPj4gaGVyZSBpcw0KPiA+PiA+IHRo
YXQgaWYgb25lIHRyaWVzIHRvIHJlbHkgb24gSVAgZnJhZ21lbnRzIG9uZSB3aWxsIGhhdmUgaXNz
dWVzIHdpdGggcGFja2V0cw0KPiA+PiA+IGVuZGluZyB1cCBpbiBibGFjayBob2xlcy4gQW5kIGRp
ZmZlcmVudCBwcm9ibGVtcyBkZXBlbmRpbmcgb24gSVB2NCBvcg0KPiA+PiBJUHY2Lg0KPiA+PiA+
IElQdjYgaXMgbGlsa2VseSB0aGUgbGVzc2VyIHByb2JsZW0gYXNzdW1pbmcgdGhhdCBvbmUgaGF2
ZSB3b3JraW5nDQo+IFBNVFVELg0KPiA+PiA+DQo+ID4+ID4gVGhlcmUgYXJlIHNldmVyYWwgd2F5
cyBvdXQgb2YgdGhpcy4NCj4gPj4gPg0KPiA+PiA+IDEuIERldGVjdCBpc3N1ZXMgYW5kIHVzZSBU
Q1AgZW5jYXBzdWxhdGlvbiB3aXRoIGNvcnJlY3RseSBzZXQgTVNTIHRvIG5vdA0KPiA+PiBnZXQg
SVANCj4gPj4gPiBmcmFnZW1lbnRzIDIuIERldGVybWluZSBNVFUgYW5kIGltcGxlbWVudCBhbiBm
cmFnbWVudGF0aW9uDQo+ID4+IG1lY2hhbmlzbSBvbiB0b3Agb2YNCj4gPj4gPiBVRFAuDQo+ID4+
DQo+ID4+IFNvLCBJIGRvbid0IHNlZSB0aGF0IG11Y2ggcHJvYmxlbSB3aXRoIFVEUCBiZWluZyB0
aGUgZ2VuZXJhbCBkZWZhdWx0DQo+ID4+IGNvbnNpc3RlbnQgd2l0aCB0aGUgVFJJTEwgcGhpbG9z
b3BoeSBvZiBkZWZhdWx0aW5nIHRvIG5lZWQgemVybyBvcg0KPiA+PiBtaW5pbWFsIGNvbmZpZ3Vy
YXRpb24uIFRoZSBkZWZhdWx0IHNob3VsZCBiZSB0byB1c2UgbXVsdGljYXN0IEhlbGxvcw0KPiA+
PiBmb3IgZGlzY292ZXJ5IG9mIG5laWdoYm9ycyB3aGljaCBzdXJlIHBvaW50cyBhdCBVRFAgdG8g
bWUuIEhhdmluZyB0bw0KPiA+PiB0cmF2ZXJzZSBhIE5BVCBzaG91bGQgYmUgYSByYXJlIGNhc2Uu
IFNpbmNlLCBpbiB0aGUgTkFUIGNhc2UsIHlvdSBoYXZlDQo+ID4+IHRvIGNvbmZpZ3VyZSB0aGlu
Z3MgcmVsYXRlZCB0byB0aGUgc3RhdGljIGJpbmRpbmcgYW5kIHRoZSBJUA0KPiA+PiBhZGRyZXNz
KGVzKSBvZiBwZWVyKHMpIGFueXdheSB5b3UgY2FuIGFsc28gY29uZmlndXJlIHRvIHVzZSBhDQo+
ID4+IGRpZmZlcmVudCBlbmNhcHN1bGF0aW9uIHRoYW4gVURQLCBzdWNoIGFzIFRDUCwgYXQgdGhl
IHNhbWUgdGltZS4gSQ0KPiA+PiBkb24ndCBzZWUgaXQgYXMgbXVjaCBvZiBhIHByb2JsZW0gaWYs
IGJ5IGRlZmF1bHQsIFRSSUxMIHdvbid0IG9wZXJhdGUNCj4gPj4gdGhyb3VnaCBhIE5BVC4gSWYg
eW91IGFyZSB1c2luZyBVRFAgYW5kIGl0IGZyYWdtZW50cyBhbmQgZnJhZ21lbnRzIGFyZQ0KPiA+
PiBkcm9wcGVkIGF0IGEgTkFULCBwcm9iYWJseSB5b3UgY2FuJ3QgZXhjaGFuZ2UgSGVsbG9zIHNv
IHlvdSB3aWxsIG5vdA0KPiA+PiBmb3JtIGFuIGFkamFjZW5jeSBhbmQgYW55dGhpbmcgb24gdGhl
IG90aGVyIHNpZGUgb2YgdGhlIE5BVCB3aWxsIG5vdA0KPiA+PiBiZSB2aXNpYmxlLg0KPiA+Pg0K
PiA+PiA+IFplcm8gQ2hlY2tzdW06DQo+ID4+ID4gLS0tLS0tLS0tLS0tLS0NCj4gPj4gPg0KPiA+
PiA+IFNlY3Rpb24gNS40Og0KPiA+PiA+DQo+ID4+ID4gVURQIENoZWNrc3VtIC0gYXMgc3BlY2lm
aWVkIGluIFtSRkMwNzY4XQ0KPiA+PiA+DQo+ID4+ID4gQ29uc2lkZXJpbmcgdGhlIGZhc3QgcGF0
aCBlbmNhcHN1bGF0aW9uIGRlc2lyZSwgSSBhbSBzdXJwcmlzZWQgdG8gbm90IHNlZQ0KPiA+PiBh
bnkNCj4gPj4gPiBtZW50aW9uaW5nIG9mIHVzZSBvZiB6ZXJvIGNoZWNrc3VtIGhlcmUuIFJhaXNp
bmcgdGhlIHplcm8gY2hlY2tzdW0gYW5kDQo+ID4+IGZvcndhcmQNCj4gPj4gPiByZWZlcmVuY2Ug
d291bGQgYmUgZ29vZCBJIHRoaW5rLg0KPiA+PiA+DQo+ID4+ID4gQW5kIHRoZW4gU2VjdGlvbiA4
LjU6DQo+ID4+ID4NCj4gPj4gPiAgICBUaGUgcmVxdWlyZW1lbnRzIGZvciB0aGUgdXNhZ2Ugb2Yg
dGhlIHplcm8gVURQIENoZWNrc3VtIGluIGEgVURQDQo+ID4+ID4gICAgdHVubmVsIHByb3RvY29s
IGFyZSBkZXRhaWxlZCBpbiBbUkZDNjkzNl0uIFRoZXNlIHJlcXVpcmVtZW50cyBhcHBseQ0KPiA+
PiA+ICAgIHRvIHRoZSBVRFAgYmFzZWQgVFJJTEwgb3ZlciBJUCBlbmNhcHN1bGF0aW9ucyBzcGVj
aWZpZWQgaGVyZWluDQo+ID4+ID4gICAgKG5hdGl2ZSBhbmQgVlhMQU4pLCB3aGljaCBhcmUgYXBw
bGljYXRpb25zIG9mIFVEUCB0dW5uZWwuDQo+ID4+ID4NCj4gPj4gPiBJZiB5b3UgYWN0dWFsbHkg
aW50ZW5kZWQgdG8gYWxsb3cgemVybyBjaGVja3N1bSwgdGhlbiB5b3UgYWN0dWFsbHkgc2hvdWxk
DQo+ID4+ID4gZG9jdW1lbnQgdGhhdCBUcmlsbCBmdWxmaWxscyB0aGUgcmVxdWlyZW1lbnRzIHRo
YXQgdGhlIGFwcGxpY2FiaWxpdHkNCj4gc3RhdGVtZW50DQo+ID4+ID4gcmFpc2VzLiBJIGhhdmUg
bm90IGFuYWx5emVkIGhvdyB3ZWxsIGl0IG1lZXRzIHRoZXNlIHJlcXVpcmVtZW50cy4NCj4gPj4g
Pg0KPiA+PiA+IFBsZWFzZSByZXZpZXcgU2VjdGlvbiA2LjIgb2YgUkZDIDgwODYgZm9yIGV4YW1w
bGUgaG93IHRoYXQgY2FuIGJlIGRvbmUuDQo+ID4+DQo+ID4+IE9LLiBXZSdsbCBsb29rIGludG8g
aXQuDQo+ID4+DQo+ID4+ID4gVENQIEVuY2Fwc3VsYXRpb24gaXNzdWUNCj4gPj4gPiAtLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLQ0KPiA+PiA+DQo+ID4+ID4gU2VjdGlvbiA1LjY6DQo+ID4+ID4NCj4g
Pj4gPiBUaGUgVENQIGVuY2Fwc3VsYXRpb24gYXBwZWFyIHRvIGJlIG1pc3NpbmcgYW4gZGVsaW1p
dGVyIGZvcm1hdCBhbGxvd2luZw0KPiA+PiBlYWNoDQo+ID4+ID4gaW5kaXZpZHVhbCBUUklMTCBw
YWNrZXQvcGF5bG9hZCB0byBiZSByZWFkIG91dCBvZiB0aGUgVENQJ3MgYnl0ZSBzdHJlYW0uDQo+
IEluDQo+ID4+ID4gb3RoZXIgd29yZHMsIGEgbm9ybWFsIGltcGxlbWVudGF0aW9uIGhhcyBubyB3
YXkgb2YgZW5zdXJpbmcgdGhhdCB0aGUNCj4gVENQDQo+ID4+ID4gcGF5bG9hZCBzdGFydHMgd2l0
aCB0aGUgc3RhcnQgb2YgYSBuZXcgVFJJTEwgcGF5bG9hZC4gTXVsdGlwbGUgc21hbGwgVFJJTEwN
Cj4gPj4gPiBwYXlsb2FkcyBtYXkgYmUgaW5jbHVkZWQgaW4gdGhlIHNhbWUgVENQIHBheWxvYWQs
IGFuZCBhbHNvIG9ubHkgcGFydHMNCj4gYXMNCj4gPj4gVENQIGlzDQo+ID4+ID4gb25lIHdheSBv
ZiBkZWFsaW5nIHdpdGggVFJJTEwgcGFja2V0cyB0aGF0IGFyZSBsYXJnZXIgdGhhbiB0aGUNCj4g
Pj4gSVArRW5jYXBzdWxhdGlvbg0KPiA+PiA+IE1UVSB0aGF0IGFjdHVhbGx5IHdpbGwgd29yay4N
Cj4gPj4gPg0KPiA+PiA+IFRoaXMgY29tbWVudCBpcyBiYXNlZCBvbiB0aGF0IHRoZXJlIGFwcGVh
ciB0byBiZSBubyBsZW5ndGggZmllbGRzDQo+IGluY2x1ZGVkDQo+ID4+IGluDQo+ID4+ID4gdGhl
IFRSSUxMIGhlYWRlci4gVGhlIG1vc3Qgc3RyYWlnaHQgZm9yd2FyZCBkZWxpbWl0ZXIgaXMgYSAy
LWJ5dGUgbGVuZ3RoDQo+ID4+IGZpZWxkDQo+ID4+ID4gZm9yIHRoZSBUUklMTCBwYXlsb2FkIHRv
IGJlIGVuY2Fwc3VsYXRlZC4NCj4gPj4NCj4gPj4gUmlnaHQuIEl0IG1pZ2h0IGFsc28gYmUgdXNl
ZnVsIHRvIGluY2x1ZGUgc29tZSBzb3J0IG9mIGNoZWNrIGZpZWxkLCBhcw0KPiA+PiBpcyBkb25l
IGluIEJHUCwgdG8gZGV0ZWN0IGlmIHlvdSBhcmUgb3V0IG9mIHN5bmMgaW4gcGFyc2luZyB0aGUg
VENQDQo+ID4+IHN0cmVhbS4NCj4gPj4NCj4gPj4gQW5vdGhlciBwb2ludCBpcyB0aGF0LCB3aGls
ZSB3aXRoIFVEUCBpdCBzZWVtcyBmaW5lIHRvIHNlbmQgcGFja2V0cw0KPiA+PiB3aXRoIGFzc29y
dGVkIFFvUywgeW91IGRvbid0IHdhbnQgdG8gZW5jb3VyYWdlIHJlLW9yZGVyaW5nIG9mIFRDUA0K
PiA+PiBwYWNrZXRzIGluIGEgc3RyZWFtLiBTbyBpZiBUQ1AgZW5jYXBzdWxhdGlvbiBpcyBiZWlu
ZyB1c2VkLCB5b3Ugd2FudA0KPiA+PiB0byB1c2UgdGhlIHNhbWUgRFNDUCB2YWx1ZSBmb3IgdGhl
IHBhY2tldHMgaW4gYSBwYXJ0aWN1bGFyIFRDUCBzdHJlYW0uDQo+ID4+IFNvLCBnZW5lcmFsbHks
IHlvdSBuZWVkIHRvIGhhdmUgYSBUQ1AgY29ubmVjdGlvbiBwZXIgcHJpb3JpdHkgaGFuZGxpbmcN
Cj4gPj4gY2F0ZWdvcnkuIE1hcHBpbmcgdGhlIDggcHJpb3JpdHkgbGV2ZWxzIGludG8gYSBzbWFs
bGVyIG51bWJlciBvZg0KPiA+PiBoYW5kbGluZyBjYXRlZ29yaWVzIGlzIGEgbm9ybWFsIHRoaW5n
IHRvIGRvIHNvIHlvdSBjZXJ0YWlubHkgZG9uJ3QNCj4gPj4gbmVjZXNzYXJpbHkgbmVlZCA4IFRD
UCBjb25uZWN0aW9ucy4gQWRkaW5nIG1hdGVyaWFsIG9uIHRoaXMgc2hvdWxkIG5vdA0KPiA+PiBi
ZSB0b28gaGFyZC4NCj4gPj4NCj4gPj4gPiBTZWN0aW9uIDUuNjoNCj4gPj4gPg0KPiA+PiA+IFRD
UCBlbmRwb2ludCByZXF1aXJlbWVudHMuIEkgZG8gd29uZGVyIGlmIGFuIGFwcGxpY2F0aW9uIGxp
a2UgVFJJTEwgYWN0dWFsDQo+ID4+ID4gd291bGQgbmVlZCB0byBkaXNjdXNzIHBlcmZvcm1hbmNl
IGltcGFjdGluZyBpbXBsZW1lbnRhdGlvbiBjaG9pY2VzIG9yDQo+ID4+ID4gbGltaXRhdGlvbnMu
IEZvciBleGFtcGxlIHVzZSBvZiBOQUdMRSwgdGhlIHJlcXVpcmVtZW50cyBvbiBidWZmZXIgc2l6
ZXMNCj4gaW4NCj4gPj4gPiByZWxhdGlvbiB0byBCYW5kd2lkdGggZGVsYXkgcHJvZHVjdHMsIGFz
IGJ1ZmZlciBtZW1vcnkgaW4gYSBSQnJpZGdlIHdpbGwNCj4gPj4gaW1wYWN0DQo+ID4+ID4gcGVy
Zm9ybWFuY2UuDQo+ID4+DQo+ID4+IFdlbGwsIEknbSBub3Qgc3VyZSBob3cgZGVlcGx5IHRoaXMg
ZG9jdW1lbnQgc2hvdWxkIGdldCBpbnRvIHN1Y2gNCj4gPj4gcGVyZm9ybWFuY2UgaXNzdWVzLiBX
aGF0IGFib3V0IGp1c3Qgc2F5aW5nIHNvbWV0aGluZyBhYm91dA0KPiA+PiBjb25zaWRlcmF0aW9u
IGJlaW5nIGdpdmVuIHRvIHR1bmluZyBUQ1AgZm9yIHBlcmZvcm1hbmNlIGFuZCBwb2ludGluZw0K
PiA+PiB0byBvbmUgb3IgYSBmZXcgb3RoZXIgUkZDcyB0aGF0IHRhbGsgYWJvdXQgdGhpcz8NCj4g
Pj4NCj4gPj4gPiBDb25nZXN0aW9uIENvbnRyb2wNCj4gPj4gPiAtLS0tLS0tLS0tLS0tLS0tLS0N
Cj4gPj4gPiBGaXJzdCB0aGFua3MgZm9yIHRoZSBlZmZvcnQgaGVyZS4NCj4gPj4NCj4gPj4gWW91
J3JlIHdlbGNvbWUuDQo+ID4+DQo+ID4+ID4gOC4xLjIgSW4gT3RoZXIgRW52aXJvbm1lbnRzDQo+
ID4+ID4NCj4gPj4gPiAgICBXaGVyZSBVRFAgYmFzZWQgZW5jYXBzdWxhdGlvbiBoZWFkZXJzIGFy
ZSB1c2VkIGluIFRSSUxMIG92ZXIgSVAgaW4NCj4gPj4gPiAgICBlbnZpcm9ubWVudHMgb3RoZXIg
dGhhbiB0aG9zZSBkaXNjdXNzZWQgaW4gU2VjdGlvbiA4LjEuMSwgc3BlY2lmaWMNCj4gPj4gPiAg
ICBjb25nZXN0aW9uIGNvbnRyb2wgbWVjaGFuaXNtcyBhcmUgY29tbW9ubHkgbmVlZGVkLiAgSG93
ZXZlciwgaWYgdGhlDQo+ID4+ID4gICAgdHJhZmZpYyBiZWluZyBjYXJyaWVkIGJ5IHRoZSBUUklM
TCBvdmVyIElQIGxpbmsgaXMgYWxyZWFkeSBjb25nZXN0aW9uDQo+ID4+ID4gICAgY29udHJvbGxl
ZCBhbmQgdGhlIHNpemUgYW5kIHZvbGF0aWxpdHkgb2YgdGhlIFRSSUxMIElTLUlTIGxpbmsgc3Rh
dGUNCj4gPj4gPiAgICBkYXRhYmFzZSBpcyBsaW1pdGVkLCB0aGVuIHNwZWNpZmljIGNvbmdlc3Rp
b24gY29udHJvbCBtYXkgbm90IGJlDQo+ID4+ID4gICAgbmVlZGVkLiBTZWUgW1JGQzgwODVdIFNl
Y3Rpb24gMy4xLjExIGZvciBmdXJ0aGVyIGd1aWRhbmNlLg0KPiA+PiA+DQo+ID4+ID4gVGhpcyBp
cyBjb3JyZWN0LCBob3dldmVyIG15IHF1ZXN0aW9uIGlzIGlmIHRoZSBSQnJpZGdlcyBoYXZlIGFu
eSB3YXkgb2YNCj4gPj4ga25vd2luZw0KPiA+PiA+IHdoaWNoIHRyYWZmaWMgaXMgYWN0dWFsbHkg
Y29uZ2VzdGlvbiBjb250cm9sbGVkLCBjb25zaWRlcmluZyB0aGF0IFRSSUxMDQo+ID4+IHByb3Zp
ZGVzDQo+ID4+ID4gYW4gbGF5ZXIgMiBhYnN0cmFjdGlvbi4gSSB3b25kZXIgaWYgdGhlcmUgc2hv
dWxkIGJlIGFueSB0eXBlIG9mIHdoaXRlIGxpc3Qgb2YNCj4gPj4gPiB0aGUgdHlwZXMgb2YgbGF5
ZXIgMiBwYXlsb2FkcyB0aGF0IGNhbiBiZSBhc3N1bWVkIHRvIGJlIGNvbmdlc3Rpb24NCj4gPj4g
Y29udHJvbGxlZCwNCj4gPj4gPiBhbmQgdGh1cyBva2F5IHRvIGZvcndhcmQgb3ZlciBJUCBwYXRo
cz8gSSBhbSB3b3JyaWVkIHRoYXQgd2l0aG91dCBhbnkNCj4gPj4gPiByZWNvbW1lbmRhdGlvbiB0
byBwcmV2ZW50IHRyYWZmaWMgdGhhdCBpcyBub3QgY29udHJvbGxlZCB0byBiZSBmb3J3YXJkZWQs
DQo+ID4+IGNhbg0KPiA+PiA+IGxlYWQgdG8gY29uZ2VzdGlvbiBpc3N1ZXMuDQo+ID4+ID4NCj4g
Pj4gPiBUaGUgb3RoZXIgaXNzdWUgSSB0aGluayBtYXkgZXhpc3QgaXMgdGhlIGlzc3VlIHNlcmlh
bCB1bmljYXN0IGVtdWxhdGlvbiBvZg0KPiA+PiA+IGJyb2FkY2FzdC9tdWx0aWNhc3QgY3JlYXRl
cy4gQXMgdGhpcyBhbXBsaWZpZXMgdGhlIG91dGdvaW5nIHBhY2tldCByYXRlDQo+IHdpdGgNCj4g
Pj4gPiBhIGZhY3RvciBvZiBob3cgbWFueSBhZGRyZXNzZXMgYXJlIGNvbmZpZ3VyZWQgZm9yIHNl
cmlhbCB1bmljYXN0IHRoaXMgY2FuDQo+ID4+ID4gYmUgc2lnbmlmaWNhbnQgdHJhZmZpYyBleHBh
bnNpb24uIFRodXMsIEkgdGhpbmsgYWRkaXRpb25hbCBjb25zaWRlcmF0aW9ucyBhcmUNCj4gPj4g
PiBuZWVkZWQgaGVyZSwgYW5kIG1heWJlIHJhdGUgbGltaXRpbmcgb2YgdGhlIGFtb3VudCBvZiB0
cmFmZmljIHRvIGJlDQo+ID4+IG11bHRpY2FzdGVkLg0KPiA+Pg0KPiA+PiBPSy4gV2UgY2FuIHRo
aW5rIGFib3V0IHRob3NlIGlzc3Vlcy4NCj4gPj4NCj4gPj4gPiBGbG93IGFuZCBFQ01QDQo+ID4+
ID4gLS0tLS0tLS0tLS0tLQ0KPiA+PiA+DQo+ID4+ID4gU2VjdGlvbiA4LjM6DQo+ID4+ID4NCj4g
Pj4gPiBGb3IgZXhhbXBsZSwgZm9yIFRSSUxMDQo+ID4+ID4gICAgRGF0YSwgdGhpcyBlbnRyb3B5
IGZpZWxkIGNvdWxkIGJlIGJhc2VkIG9uIHNvbWUgaGFzaCBvZiB0aGUNCj4gPj4gPiAgICBJbm5l
ci5NYWNEQSwgSW5uZXIuTWFjU0EsIGFuZCBJbm5lci5WTEFOIG9yIElubmVyLkZHTC4NCj4gPj4g
Pg0KPiA+PiA+IEkgd291bGQgYXBwcmVjaWF0ZSBjbGVhcmVyIHJlZmVyZW5jZXMgdG8gd2hhdCB0
aGVzZSBmaWVsZHMgYXJlLg0KPiA+Pg0KPiA+PiBJbiBhIFRSSUxMIERhdGEgcGFja2V0LCB0aGUg
cGF5bG9hZCBhZnRlciB0aGUgVFJJTEwgSGVhZGVyIGxvb2tzIGxpa2UNCj4gPj4gYW4gRXRoZXJu
ZXQgZnJhbWUgZXhjZXB0IHRoYXQgdGhlcmUgaXMgYWx3YXlzIGVpdGhlciBhIFZMQU4gdGFnIG9y
LA0KPiA+PiBhbHRlcm5hdGl2ZWx5LCB3aGVyZSB0aGUgVkxBTiB0YWcgd291bGQgYmUsIGEgRmlu
ZSBHcmFpbmVkIExhYmVsDQo+ID4+IFtSRkM3MTcyXS4gKFRoZSBwcmVjZWRpbmcgaXMgdGhlIHZp
ZXcgaW4gdGhlIFRSSUxMIFJGQ3MsIGJ1dCB0aGVyZSBpcw0KPiA+PiBhbiBlcXVpdmFsZW50IGFu
ZCBlcXVhbGx5IHZhbGlkIHZpZXcgaW4gd2hpY2ggYWxsIHRoZSBmaWVsZHMgdGhyb3VnaA0KPiA+
PiBhbmQgaW5jbHVkaW5nIHRoZSBWTEFOIG9yIEZHTCB0YWcgYXJlIHBhcnQgb2YgdGhlIFRSSUxM
IEhlYWRlci4pIFRoZQ0KPiA+PiBUUklMTCBiYXNlIHByb3RvY29sIHNwZWNpZmljYXRpb24gZm9j
dXNlcyBvbiBFdGhlcm5ldCBhcyBhIGxpbmsNCj4gPj4gdGVjaG5vbG9neSBiZXR3ZWVuIFRSSUxM
IHN3aXRjaGVzLCBpbiB3aGljaCBjYXNlIHRoZXJlIHdpbGwgYmUgYSBsaW5rDQo+ID4+IGhlYWRl
ciBpbmNsdWRpbmcgYW4gT3V0ZXIuTWFjREEgYW5kIE91dGVyLk1hY1NBIGZpZWxkcyBhbmQgcG9z
c2libHkgYW4NCj4gPj4gT3V0ZXIuVkxBTiwgYWxsIGJlZm9yZSB0aGUgVFJJTEwgSGVhZGVyLiBT
ZWUgRmlndXJlIDEgYW5kIEZpZ3VyZSAyIGluDQo+ID4+IFJGQyA3MTcyLg0KPiA+Pg0KPiA+PiBT
b21lIG9mIHRoZSBhYm92ZSBjb3VsZCBiZSBhZGRlZCB0byB0aGUgZHJhZnQgZm9yIGNsYXJpdHku
DQo+ID4+DQo+ID4+ID4gSWYgSSB1bmRlcnN0YW5kIHRoaXMgY29ycmVjdGx5LCB0aGUgaWRlYSBo
ZXJlIGlzIHRvIGxvb2sgaW50byB0aGUgaW5uZXINCj4gPj4gPiBsYXllciAyIGZyYW1lcywgYW5k
IHVzZSB0aGUgZmxvdyBlcXVpdmFsZW50cyB0aGF0IGV4aXN0cyBvbiB0aGF0IGxldmVsIGFuZA0K
PiA+PiA+IGhhc2ggdGhhdCBpbnRvIHZhbHVlIHRoYXQgbWFwcyB0aGUgZmxvd3Mgb250byB0aGUg
c291cmNlIHBvcnQgcmFuZ2UuDQo+ID4+DQo+ID4+IFllcy4NCj4gPj4NCj4gPj4gPiBJIHRoaW5r
IHRoaXMgdGV4dCBzaG91bGQgaW5jbHVkZSBhIHN1bW1hcnkgb2YgdGhlIHByaW5jaXBsZSBhbmQg
ZW5zdXJlIHRvDQo+ID4+ID4gbm90ZSB0aGUgaW1wb3J0YW50IHJlcXVpcmVtZW50IHRoYXQgd2hh
dCBpcyBjb25zaWRlcmVkIGZsb3dzIGluIHRoZQ0KPiBpbm5lcg0KPiA+PiA+IG11c3Qgbm90IHJl
c3VsdCBpbiBiZWluZyBzdHJpcGVkIG92ZXIgbXVsdGlwbGUgc291cmNlIHBvcnRzIGFzIHRoaXMg
bWF5DQo+IGxlYWQNCj4gPj4gdG8NCj4gPj4gPiByZW9yZGVyaW5nIGlzc3VlcyBkdWUgdG8gcGFj
a2V0cyB0YWtpbmcgZGlmZmVyZW50IHBhdGhzLg0KPiA+Pg0KPiA+PiBXZWxsLCB3ZSBjYW4gYWRk
IHNvbWUgdGV4dC4gQnV0IHdoZW4gd291bGQgdGhlIHJlbGF0aXZlIG9yZGVyaW5nDQo+ID4+IG1h
dHRlciBmb3IgdHdvIFRSSUxMIERhdGEgcGFja2V0cyB3aGVyZSB0aGUgdHdvIGlubmVyIG5hdGl2
ZSBwYXlsb2Fkcw0KPiA+PiBoYXZlIGRpZmZlcmVudCB2YWx1ZXMgZm9yIGFueSBvbmUgb3IgbW9y
ZSBvZiB0aGVzZSB0aHJlZSBmaWVsZHMNCj4gPj4gKElubmVyLk1hY0RBLCBJbm5lci5NYWNTQSwg
YW5kIGlubmVyIFZMQU4vRkdMIHRhZykgPyBJZiBhbnkgb2YgdGhvc2UNCj4gPj4gZmllbGRzIGFy
ZSBkaWZmZXJlbnQsIHlvdSBhcmUgdGFsa2luZyBhYm91dCBkaWZmZXJlbnQgc3RyZWFtcy4NCj4g
Pj4NCj4gPj4gPiBOQVQgYW5kIFRSSUxMIG92ZXIgSVA6DQo+ID4+ID4gU2VjdGlvbiA4LjU6DQo+
ID4+ID4NCj4gPj4gPiBJZiBvbmUgbGlrZSB0byB1c2UgVFJJTEwgb3ZlciBJUCB0aHJvdWdoIGEg
TkFULCB0aGVuIHRoZXJlIGFyZSBzb21lIHZlcnkNCj4gPj4gPiBpbXBvcnRhbnQgY29uc2lkZXJh
dGlvbnMgdGhhdCBhcmUgbWlzc2luZy4gRmlyc3QgdGhlIG5lZWQgZm9yIHN0YXRpYw0KPiBiaW5k
aW5nDQo+ID4+ID4gY29uZmlndXJhdGlvbnMgb3IgdGhlIG5lZWQgZm9yIGRldGVybWluaW5nIG9u
ZXMgZXh0ZXJuYWwgYWRkcmVzcyhlcykgYW5kDQo+ID4+IGJlDQo+ID4+ID4gYWJsZSB0byBjb21t
dW5pY2F0ZSB0aGF0IHRvIHRoZSBwZWVyIFJCcmlkZ2VzLCBhbmQgaW4gYWRkaXRpb24gZW5zdXJl
DQo+IHRoYXQNCj4gPj4gb25lDQo+ID4+ID4gaGFzIGtlZXAtYWxpdmVzIHRvIHRoYXQgdGhlIE5B
VCBiaW5kaW5nIG5ldmVyIHRpbWVzIG91dC4NCj4gPj4NCj4gPj4gSSB0aGluayB0aG9zZSBhcmUg
Z29vZCBwb2ludHMuIFRoZXJlIGlzIGFuIGFkZGl0aW9uYWwgcHJvYmxlbSB0aGF0DQo+ID4+IFRS
SUxMIEhlbGxvcyBkZXRlY3QgbmVpZ2hib3JzIHdpdGggd2hpY2ggdGhleSBoYXZlIDItd2F5IGNv
bm5lY3Rpdml0eQ0KPiA+PiBieSBpbmRpY2F0aW5nLCBpbnNpZGUgdGhlIEhlbGxvcyB0aGF0IGFy
ZSBzZW50LCBmcm9tIHdoYXQgbmVpZ2hib3JzDQo+ID4+IEhlbGxvcyBoYXZlIGJlZW4gcmVjZWl2
ZWQgb24gdGhhdCBwb3J0LiBJZiBhIE5BVCBpcyBpbnZvbHZlZCwgdGhlc2UNCj4gPj4gbmVpZ2hi
b3IgYWRkcmVzc2VzIGluc2lkZSBIZWxsb3MgbmVlZCB0byBiZSBtYXBwZWQuDQo+ID4+DQo+ID4+
ID4gTmV4dCBpcyB0aGUgaXNzdWUgdGhhdCB0aGVyZSBpcyBhbG1vc3QgemVybyBjaGFuY2Ugb2Yg
Z2V0dGluZyBhIElQL1VEUA0KPiA+PiA+IGVuY2Fwc3VsYXRpb24gVFJJTEwgcGF5bG9hZCB0aHJv
dWdoIHRoZSBOQVQgaWYgaXQgcmVzdWx0cyBpbiBJUA0KPiA+PiBmcmFnbWVudGF0aW9uLA0KPiA+
PiA+IGFzIE5BVHMgZG9uJ3QgZG8gZGVmcmFnbWVudCBhbmQgcmVmcmFnbWVudGVkIG9uIHRoZSBp
bnRlcm5hbCBzaWRlLCBhbmQNCj4gPj4gYW4gSVANCj4gPj4gPiBmcmFnbWVudCBsYWNrcyBVRFAg
cG9ydCBhbmQgdGh1cyBjYW4ndCBiZSBtYXRjaGVkIHRvIGJpbmRpbmcuDQo+ID4+DQo+ID4+IFNv
IHBlcmhhcHMgdGhlIHJlY29tbWVuZGF0aW9uIHNob3VsZCBiZSB0byBjb25maWd1cmUgdGhlIHBv
cnQgdG8gdXNlDQo+ID4+IFRDUCBpZiB0aGVyZSB3aWxsIGJlIGZyYWdtZW50YXRpb24uDQo+ID4+
DQo+ID4+ID4gQWxzbyBpZiB5b3UgbGlrZSB0byBydW4gSVAvRVNQIHRocm91Z2ggYSBOQVQsIHRo
ZW4geW91IG1vc3QgbGlrZWx5IG5lZWQgdGhlDQo+ID4+ID4gSVAvVURQL0VTUCBlbmNhcHN1bGF0
aW9uIChodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjMzk0OCkuIE5vdGUNCj4gdGhhdA0K
PiA+PiB0aGlzDQo+ID4+ID4gd2lsbCByZXN0cmljdCB0aGUgTVRVIGV2ZW4gZnVydGhlciBhbmQg
dGh1cyBlbnN1cmUgdGhhdCB0aGUgMTQ3MA0KPiA+PiByZXF1aXJlbWVudA0KPiA+PiA+IGNhbm5v
dCBiZSBmdWxmaWxsZWQgZXZlbiB3aXRob3V0IGFkZGl0aW9uYWwgdHVubmVscyBvdmVyIGFuIDE1
MDAgYnl0ZXMNCj4gTVRVDQo+ID4+ID4gRXRoZXJuZXQgaW5mcmFzdHJ1Y3R1cmUuDQo+ID4+ID4N
Cj4gPj4gPiBJIHdvdWxkIG5vdGUgdGhhdCBhbHNvIGZpcmV3YWxscyBsaWtlbHkgaGF2ZSBpc3N1
ZXMgd2l0aCBJUCBmcmFnbWVudHMgZm9yDQo+IHRoZQ0KPiA+PiA+IHNhbWUgcmVhc29uLCB0aGV5
IHJlcXVpcmUgc2lnbmlmaWNhbnQgYW1vdW50IG9mIHN0YXRlIHRvIGJlIHZlcmlmaWVkIGlmDQo+
IHRoZXkNCj4gPj4gPiBzaG91bGQgYmUgbGV0IHRocm91Z2guDQo+ID4+ID4NCj4gPj4gPiBJbiBn
ZW5lcmFsIEkgdGhpbmsgeW91IHNob3VsZCBjcmVhdGUgYSBjb25maWd1cmF0aW9uIHRoYXQgaGFz
IGNoYW5jZSB0bw0KPiB3b3JrDQo+ID4+ID4gdGhyb3VnaCBtb3N0IG1pZGRsZWJveGVzLCBidXQg
SSB0aGluayB5b3Ugc2hvdWxkIHJlcXVpcmUgc3RhdGljIGJpbmRpbmdzLg0KPiBJDQo+ID4+ID4g
dGhpbmsgdGhhdCBjb25maWd1cmF0aW9uIGlzLCBhbmQgZG9uJ3QgbGF1Z2ggbm93LCBidXQNCj4g
Pj4gSVAvVURQL0VTUC9UQ1AvVFJJTEwsDQo+ID4+ID4gb3RoZXJ3aXNlIHlvdSB3aWxsIG5vdCBi
ZSBhYmxlIHRvIGhhdmUgYm90aCBzZWN1cml0eSBhbmQgcmVsaWFibGUNCj4gPj4gZnJhZ21lbnRh
dGlvbg0KPiA+PiA+IG9mIFRSSUxMIHBhY2tldHMuDQo+ID4+DQo+ID4+IE9LLiBUaGFua3MgYWdh
aW4gZm9yIHRoaXMgcmV2aWV3LiBJdCBoYXMgcG9pbnRlZCBvdXQgYSBudW1iZXIgb2YNCj4gPj4g
cHJvYmxlbXMgYW5kIGluIHRoaW5raW5nIGFib3V0IHRob3NlLCBJIGJlbGlldmUgYSBjb3VwbGUg
b2YgZnVydGhlcg0KPiA+PiBwcm9ibGVtcyBoYXZlIGNvbWUgdG8gbWluZCB0aGF0IEkgbWVudGlv
bmVkIGFib3ZlLiBXZSdsbCB3b3JrIG9uIGENCj4gPj4gcmV2aXNlZCBkcmFmdC4NCj4gPj4NCj4g
Pj4gVGhhbmtzLA0KPiA+PiBEb25hbGQNCj4gPj4gPT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PQ0KPiA+PiAgRG9uYWxkIEUuIEVhc3RsYWtlIDNyZCAgICsxLTUwOC0zMzMtMjI3MCAoY2Vs
bCkNCj4gPj4gIDE1NSBCZWF2ZXIgU3RyZWV0LCBNaWxmb3JkLCBNQSAwMTc1NyBVU0ENCj4gPj4g
IGQzZTNlM0BnbWFpbC5jb20NCj4gPj4NCj4gPj4gPiBDaGVlcnMNCj4gPj4gPg0KPiA+PiA+IE1h
Z251cyBXZXN0ZXJsdW5kDQo+ID4+DQo+ID4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fDQo+ID4+IFRzdi1hcnQgbWFpbGluZyBsaXN0DQo+ID4+IFRzdi1h
cnRAaWV0Zi5vcmcNCj4gPj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby90
c3YtYXJ0DQo=


From nobody Sat Jul  1 11:04:23 2017
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 752E1127342; Sat,  1 Jul 2017 11:04:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, 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 nNj-w13x68mL; Sat,  1 Jul 2017 11:03:57 -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 888171201F8; Sat,  1 Jul 2017 11:03:57 -0700 (PDT)
Received: by mail-it0-x22a.google.com with SMTP id m84so39271311ita.0; Sat, 01 Jul 2017 11:03:57 -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:content-transfer-encoding; bh=YPY4SuaFP+9Psn09VAzrOc9z7ISAZ0GTqP2XcK3eHKc=; b=QQvvMQno0aEgsR8P8W/qc0w9Bvt5yxKp2YQ63okbMtbo0TG40PdBaJGwGVVDMnhmei o5aj0T3DTOh3YSmnO9y8C5iOM8IH5V2j8eLXpwELH32nuLA0Mt0WDMjFfl9mskHFt8M9 wHqcuIzgNO80MqR7Snb2k8CK34i1Vyya20lBnvT8Qa+6Lf5xmUwzentQYE75v4RJFABZ fCuKWpusQQRg5bCAac5QQCOF1NSzHp+rJFkF2Nzlfdb/ULBuUkTqOWnKvYvVBH0jSqMy 3UgwZMcajg3ddFbPS9w/dikl46KpKpWzIS/NFxFA165E5/vC37NMlwCgujSq45N0zjww gTAQ==
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:content-transfer-encoding; bh=YPY4SuaFP+9Psn09VAzrOc9z7ISAZ0GTqP2XcK3eHKc=; b=CKElRv+89mhxLXsykn6vodblAo/nmFY4BoaG3OPPUO5XzyNdBmBgQVGsML57OKKKdN eQZzNn0RhRmu0y73uwQBalf5AzxH5jIKGvc8SSFqcgLQJay9cj0IqCw3J9LP6+S7JdIB 6jm2R/u5KW4OkJesqiK9AVSjs6hikQv+Eh+/WJSsrGvk7sp6etT86D63S1Ef8uaBDMk1 Y4Zs4tM4vRWcqPrrtjh2amqMS/Qsxz8eNtk1Q4kiDcmwGf4OAI4dJdzg95I8DmWIuxDI ZYCG2kXmeKnmzlzaIpOiqHMCXixyUeBIvpcmTIZx+LYlDh1VgmnXqXNfW8SdCXmrAZUJ dBLA==
X-Gm-Message-State: AIVw112Cw6FkKya6PqJ/nQSLsDe2oe/nlt6r03GtXTLMQ491wyWqRiZD Es54B9jMj+4UfF9AxV+PWbIuEqiRWA==
X-Received: by 10.36.3.11 with SMTP id e11mr1848026ite.79.1498932236595; Sat, 01 Jul 2017 11:03:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.17.221 with HTTP; Sat, 1 Jul 2017 11:03:41 -0700 (PDT)
In-Reply-To: <CE03DB3D7B45C245BCA0D243277949362FB59E00@MX307CL04.corp.emc.com>
References: <CE03DB3D7B45C245BCA0D243277949362FB4DF88@MX307CL04.corp.emc.com> <CAF4+nEFUmB=eMO6rvK6-YiL+3Adp_t1QVqgMDBHZFn73_JxEfw@mail.gmail.com> <CE03DB3D7B45C245BCA0D243277949362FB59E00@MX307CL04.corp.emc.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sat, 1 Jul 2017 14:03:41 -0400
Message-ID: <CAF4+nEEdv8XRSKmpffe1fU+4wRpikeixzX-49g1ocQSJBaqgSg@mail.gmail.com>
Subject: Re: [Tsv-art] Tsvart early review of draft-ietf-trill-over-ip-10 - ECN & DSCP considerations
To: "Black, David" <David.Black@dell.com>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "tsv-art@ietf.org" <tsv-art@ietf.org>,  "draft-ietf-trill-over-ip.all@ietf.org" <draft-ietf-trill-over-ip.all@ietf.org>, IETF Discussion <ietf@ietf.org>,  "trill@ietf.org" <trill@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/erBNdAvn8ijGAUwRwBvcE2HxpUk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Jul 2017 18:04:00 -0000

On Sat, Jul 1, 2017 at 10:53 AM, Black, David <David.Black@dell.com> wrote:
> Also, as noted earlier in this discussion, RFC 7657 explicitly discourage=
s use of multiple DSCPs in a single TCP connection.  That needs to be refle=
cted in the TCP encapsulation text in the trill-over-ip draft - in particul=
ar, the current text in Section 4.3 on mapping to DSCPs from TRILL priority=
 and DEI does not appear to be consistent with RFC 7657 for TCP-based encap=
sulation.

I'm surprised it only "discourages" rather than "prohibits"...

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> Thanks, --David
>
>> -----Original Message-----
>> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
>> Sent: Friday, June 30, 2017 9:43 PM
>> To: Black, David <david.black@emc.com>
>> Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>; tsv-
>> art@ietf.org; draft-ietf-trill-over-ip.all@ietf.org; IETF Discussion
>> <ietf@ietf.org>; trill@ietf.org
>> Subject: Re: [Tsv-art] Tsvart early review of draft-ietf-trill-over-ip-1=
0 - ECN &
>> DSCP considerations
>>
>> Hi David,
>>
>> On Mon, Jun 26, 2017 at 3:04 PM, Black, David <David.Black@dell.com>
>> wrote:
>> > Adding some comments on ECN and DSCP ...
>> >
>> >> > Section 4.3:
>> >> >
>> >> >    TRILL over IP implementations MUST support setting the DSCP valu=
e in
>> >> >    the outer IP Header of TRILL packets they send by mapping the TR=
ILL
>> >> >    priority and DEI to the DSCP. They MAY support, for a TRILL Data
>> >> >    packet where the native frame payload is an IP packet, mapping t=
he
>> >> >    DSCP in this inner IP packet to the outer IP Header with the def=
ault
>> >> >    for that mapping being to copy the DSCP without change.
>> >> >
>> >> > I think it is fine to require that implementations are capable of s=
etting
>> >> > DSCP values on the outer IP header. However, I fail to see any disc=
ussion of
>> >> > the potential issues with actually setting the DSCP values. It is o=
ne thing to
>> >> > do this in an IP back bone use case where one can know and have con=
trol
>> >> > over the PHB that the DSCP values maps to. But otherwise, over gene=
ral internet the
>> >> > behavior is not that predictable. One can easily be subject to poli=
cers or
>> >> > remapping. Also as the actual DSCP code point usage is domain speci=
fic this is
>> >> > difficult. Priority reversal is likely the least of the problems th=
at this can
>> >> > run into over general Internet.
>> >>
>> >> It sounds like appropriate discussion and warnings about these issues
>> >> would resolve the above comment.
>> >
>> > For ECN, see RFC 6040 and draft-ietf-tsvwg-rfc6040update-shim.  In par=
ticular,
>> > copying the inner ECN codepoint to the outer IP header encapsulation w=
ithout
>> > requiring decapsulation processing as specified in RFC 6040 or the 604=
0update-shim
>> > draft can lose congestion indications from the network and hence is wr=
ong
>> > (it's also wrong wrt RFC 3168, but RFC 6040 and the 6040update-shim dr=
afts are
>> > better and more current references).
>>
>> That's a good point.
>>
>> > For DSCPs, start with RFC 2983 - thinking about the validity (or likel=
y validity)
>> > of the outer DSCP at the decapsulator may help in choosing whether to
>> > recommend a uniform model (e.g., copy DSCP out at ingress, copy back i=
n at
>> > egress) or a pipe model (e.g., do something reasonable for outer DSCP =
at
>> > ingress, ignore it on egress) as the implementation default.
>>
>> I believe the default behavior in the current draft is the best
>> default. That sets DSCP based on the same TRILL Header indicia that
>> controls default QoS on non-IP links.
>>
>> > -- DSCP mapping to/from TRILL/Ethernet priorities
>> >
>> >> The intent in the draft is to reflect the default relative priority o=
f
>> >> the different priority code points in IEEE Std 802.1Q where priority =
1
>> >> is lower than priority 0. At a quick look, it appears to me that RFC
>> >> 2474 requires that 0x001000 be handled as being of a priority not
>> >> lower than the priority with which 0x000000 is handled. Yet RFC 3662,
>> >> which you point to, seems to suggest using 0x001000 as a lower
>> >> priority code point than 0x000000. Given that 3662 not only does not
>> >> update 2474 but is only Informational while 2474 is Standards Track, =
I
>> >> would say that 2474 dominates and that this draft makes the best
>> >> assumptions it can about default behavior...
>> >
>> > Well ... that's a discussion about text in RFCs that are well over a d=
ecade
>> > old, and in an area (less-than-best-effort service) where the aspirati=
ons
>> > of at least RFC 3662 weren't realized ... but that RFC is not safe to =
ignore,
>> > either.
>> >
>> > In practice, the specification of CS1 for less-than-best-effort servic=
e has
>> > been promulgated by RFC 4594 rather than RFC 3662, and RFC 4594 has
>> > had significant "running code" impact on network design and operation.
>> >
>> > As Magnus mentioned RFC7657, I strongly suggest starting from the
>> > RFC 7657 discussion of this topic in order to figure out what to do.  =
I'm
>> > not sure what to recommend, but I do think that starting from
>> > RFC 7657 (rather than RFC 2474 and RFC 3662) is the better approach.
>>
>> OK.
>>
>> > FWIW, the TSVWG WG is in the process of figuring out which DSCP
>> > to recommend for less-than-best-effort-service in place of CS1 - that'=
s
>> > likely to be an active topic of discussion in Prague.
>>
>> I'll try to attend that session.
>>
>> Thanks,
>> Donald
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D
>>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>>  155 Beaver Street, Milford, MA 01757 USA
>>  d3e3e3@gmail.com
>>
>> > Thanks, --David
>> >
>> >> -----Original Message-----
>> >> From: Tsv-art [mailto:tsv-art-bounces@ietf.org] On Behalf Of Donald
>> >> Eastlake
>> >> Sent: Sunday, June 25, 2017 8:07 PM
>> >> To: Magnus Westerlund <magnus.westerlund@ericsson.com>
>> >> Cc: tsv-art@ietf.org; draft-ietf-trill-over-ip.all@ietf.org; IETF Dis=
cussion
>> >> <ietf@ietf.org>; trill@ietf.org
>> >> Subject: Re: [Tsv-art] Tsvart early review of draft-ietf-trill-over-i=
p-10
>> >>
>> >> Hi Magnus,
>> >>
>> >> Thanks for the extensive review. See my responses below.
>> >>
>> >> On Thu, Jun 15, 2017 at 1:32 PM, Magnus Westerlund
>> >> <magnus.westerlund@ericsson.com> wrote:
>> >> >
>> >> > Reviewer: Magnus Westerlund
>> >> > Review result: Not Ready
>> >> >
>> >> > Early review of draft-ietf-trill-over-ip-10
>> >> > Reviewer: Magnus Westerlund
>> >> > Review result: Not Ready
>> >> >
>> >> > TSV-ART review comments:
>> >> >
>> >> > I have set this to not ready as there are several issues, some sign=
ificant
>> that
>> >> > could affect the protocol realization significantly. Some may be me
>> missing
>> >> > things in TRILL, I was not that familiar with it before this review=
 and I have
>> >> > only tried looking up things, not reading the whole earlier specifi=
cations.
>> So
>> >> > don't hesitate to push back and provide pointers to things that can
>> resolve
>> >> > issues. The authors and the WG clearly have thought about a lot of =
issues
>> >> and
>> >> > dealt with much already.
>> >>
>> >> OK. Hopefully we can resolve these one way or the other.
>> >>
>> >> > Diffserv usage
>> >> > --------------
>> >> >
>> >> > Section 4.3:
>> >> >
>> >> >    TRILL over IP implementations MUST support setting the DSCP valu=
e in
>> >> >    the outer IP Header of TRILL packets they send by mapping the TR=
ILL
>> >> >    priority and DEI to the DSCP. They MAY support, for a TRILL Data
>> >> >    packet where the native frame payload is an IP packet, mapping t=
he
>> >> >    DSCP in this inner IP packet to the outer IP Header with the def=
ault
>> >> >    for that mapping being to copy the DSCP without change.
>> >> >
>> >> > I think it is fine to require that implementations are capable  of =
setting
>> >> > DSCP values on the outer IP header. However, I fail to see any disc=
ussion
>> of
>> >> > the potential issues with actually setting the DSCP values. It is o=
ne thing
>> to
>> >> > do this in an IP back bone use case where one can know and have con=
trol
>> >> over
>> >> > the PHB that the DSCP values maps to. But otherwise, over general
>> >> internet the
>> >> > behavior is not that predictable. One can easily be subject to poli=
cers or
>> >> > remapping. Also as the actual DSCP code point usage is domain speci=
fic
>> this
>> >> is
>> >> > difficult. Priority reversal is likely the least of the problems th=
at this can
>> >> > run into over general Internet.
>> >>
>> >> It sounds like appropriate discussion and warnings about these issues
>> >> would resolve the above comment.
>> >>
>> >> > Section 4.3:
>> >> >
>> >> >    The default TRILL priority and DEI to DSCP mapping, which may be
>> >> >    configured per TRILL over IP port, is an follows. Note that the =
DEI
>> >> >    value does not affect the default mapping and, to provide a
>> >> >    potentially lower priority service than the default priority 0,
>> >> >    priority 1 is considered lower priority than 0. So the priority
>> >> >    sequence from lower to higher priority is 1, 0, 2, 3, 4, 5, 6, 7=
.
>> >> >
>> >> >       TRILL Priority  DEI  DSCP Field (Binary/decimal)
>> >> >       --------------  ---  -----------------------------
>> >> >                   0   0/1  001000 / 8
>> >> >                   1   0/1  000000 / 0
>> >> >                   2   0/1  010000 / 16
>> >> >                   3   0/1  011000 / 24
>> >> >                   4   0/1  100000 / 32
>> >> >                   5   0/1  101000 / 40
>> >> >                   6   0/1  110000 / 48
>> >> >                   7   0/1  111000 / 56
>> >> >
>> >> > This appear to be an problematic mapping. At least for prio 0 and 1=
. As
>> >> > priority 1 appears to be intended to be higher than priority 0, it =
is
>> >> > interesting that it is mapped to CS1, which to quote
>> >> > https://datatracker.ietf.org/doc/rfc7657/:
>> >> >
>> >> > CS1 ('001000') was subsequently designated as the recommended
>> >> >       codepoint for the Lower Effort (LE) PHB [RFC3662].
>> >> >
>> >> > So what is proposed can in a network using default mapping, result =
in
>> that
>> >> you
>> >> > get priority 0 to be lower priority than 1. Plus that in some netwo=
rks this
>> can
>> >> > also results in strange remapping that results in a different PHB f=
or CS1
>> >> than.
>> >>
>> >> The intent in the draft is to reflect the default relative priority o=
f
>> >> the different priority code points in IEEE Std 802.1Q where priority =
1
>> >> is lower than priority 0. At a quick look, it appears to me that RFC
>> >> 2474 requires that 0x001000 be handled as being of a priority not
>> >> lower than the priority with which 0x000000 is handled. Yet RFC 3662,
>> >> which you point to, seems to suggest using 0x001000 as a lower
>> >> priority code point than 0x000000. Given that 3662 not only does not
>> >> update 2474 but is only Informational while 2474 is Standards Track, =
I
>> >> would say that 2474 dominates and that this draft makes the best
>> >> assumptions it can about default behavior...
>> >>
>> >> > MTU and Fragmentation
>> >> > ---------------------
>> >> >
>> >> > I think there are two main issue here. The first one is MTUD discov=
ery
>> >> > of the actual IP path MTU between the ports. That will be needed to
>> >> prevent
>> >> > a lot of traffic going into MTU black holes. Especially as TRILL re=
quries
>> >> > 1470 byte support which is likey above a lot of paths.
>> >>
>> >> Seems like it would depend on the environments where TRILL was used.
>> >> For example, I do not think 1470 would be a problem in most Data
>> >> Center or Internet Exchange point uses, for example. Data Centers
>> >> sometimes support 9K jumbo frames and the like.
>> >>
>> >> In fact, it is probably bad to focus too much on 1470 -- that is a
>> >> required minimum to be sure that reasonable size link state PDUs can
>> >> be successfully flooded through the TRILL campus so that routing will
>> >> work. However, it would commonly be the case that, for the TRILL
>> >> campus to be useful in a particular case, links need to be able to
>> >> carry the expected size TRILL Data packets. For example, if there wer=
e
>> >> two parts of a TRILL campus connected by one or a few TRILL over IP
>> >> links and the end stations in each part were assuming they could use
>> >> 1500 byte Ethernet packets, then the TRILL over IP links would need t=
o
>> >> support an MTU based on 1500 + TRILL Header + IP and TRILL over IP
>> >> encapsulation. And more if security was being used or there were any
>> >> other reasons for additional headers/encapsulation...
>> >>
>> >> > Section 8.4:
>> >> >
>> >> >    Path MTU discovery [RFC4821] should be useful
>> >> >    in determining the IP MTU between a pair of RBridge ports with I=
P
>> >> >    connectivity.
>> >> >
>> >> > The issue with RFC4821 is that it has requirements on the packetiza=
tion
>> >> layer.
>> >> > Trill appears to have several components that are useful. However, =
it will
>> >> > require a specification of the procedure to result in a useful tool=
.
>> >>
>> >> See below.
>> >>
>> >> > Section 8.4:
>> >> >
>> >> >    TRILL IS-IS MTU PDUs, as specified in Section 5 of [RFC6325] and=
 in
>> >> >    [RFC7177], can be used to obtain added assurance of the MTU of a
>> >> >    link.
>> >> >
>> >> > Yes, that can confirm working MTUs that are at 1470 or above, but
>> appears
>> >> > prevented from working below 1470?
>> >>
>> >> While there is a minimum size for TRILL IS-IS MTU PDUs, determined by
>> >> header size, it is well below 1470, probably (depending on whether
>> >> secuirty is in use, etc.) below 150 bytes.
>> >>
>> >> > Thus, it appears that there is a lack of mechanism here to actually=
 get a
>> valid
>> >> > and functional MTU from TRILL in the cases where the Path MTU is be=
low
>> >> 1470. If
>> >> > I am wrong good, but I think this is an important piece for how to =
handle
>> >> the
>> >> > next main issue.
>> >>
>> >> How about referencing Section 3 of
>> >> https://tools.ietf.org/html/draft-ietf-trill-mtu-negotiation-05
>> >> which is currently in IETF Last Call? (The wording of that section is
>> >> probably going to be improved based on an OPS review by Brian
>> >> Carpenter.)
>> >>
>> >> > UDP encapsulation and IP fragments.
>> >>   ----------------------------------
>> >> > I see it as a big issue that UDP encapsulation is the native one, a=
nd that
>> >> > relies on IP fragmentation despite the need for reliable fragmentat=
ion.
>> >> With
>> >> > the setup of having to support 1470 MTU on TRILL level some packets=
 will
>> >> be
>> >> > fragmented in many environments. That will lead to a lot of losses,=
 and as
>> >> > discussed below a very big problem with middleboxes. The main probl=
em
>> >> here is
>> >> > that if one tries to rely on IP fragments one will have issues with=
 packets
>> >> > ending up in black holes. And different problems depending on IPv4 =
or
>> >> IPv6.
>> >> > IPv6 is lilkely the lesser problem assuming that one have working
>> PMTUD.
>> >> >
>> >> > There are several ways out of this.
>> >> >
>> >> > 1. Detect issues and use TCP encapsulation with correctly set MSS t=
o not
>> >> get IP
>> >> > fragements 2. Determine MTU and implement an fragmentation
>> >> mechanism on top of
>> >> > UDP.
>> >>
>> >> So, I don't see that much problem with UDP being the general default
>> >> consistent with the TRILL philosophy of defaulting to need zero or
>> >> minimal configuration. The default should be to use multicast Hellos
>> >> for discovery of neighbors which sure points at UDP to me. Having to
>> >> traverse a NAT should be a rare case. Since, in the NAT case, you hav=
e
>> >> to configure things related to the static binding and the IP
>> >> address(es) of peer(s) anyway you can also configure to use a
>> >> different encapsulation than UDP, such as TCP, at the same time. I
>> >> don't see it as much of a problem if, by default, TRILL won't operate
>> >> through a NAT. If you are using UDP and it fragments and fragments ar=
e
>> >> dropped at a NAT, probably you can't exchange Hellos so you will not
>> >> form an adjacency and anything on the other side of the NAT will not
>> >> be visible.
>> >>
>> >> > Zero Checksum:
>> >> > --------------
>> >> >
>> >> > Section 5.4:
>> >> >
>> >> > UDP Checksum - as specified in [RFC0768]
>> >> >
>> >> > Considering the fast path encapsulation desire, I am surprised to n=
ot see
>> >> any
>> >> > mentioning of use of zero checksum here. Raising the zero checksum =
and
>> >> forward
>> >> > reference would be good I think.
>> >> >
>> >> > And then Section 8.5:
>> >> >
>> >> >    The requirements for the usage of the zero UDP Checksum in a UDP
>> >> >    tunnel protocol are detailed in [RFC6936]. These requirements ap=
ply
>> >> >    to the UDP based TRILL over IP encapsulations specified herein
>> >> >    (native and VXLAN), which are applications of UDP tunnel.
>> >> >
>> >> > If you actually intended to allow zero checksum, then you actually =
should
>> >> > document that Trill fulfills the requirements that the applicabilit=
y
>> statement
>> >> > raises. I have not analyzed how well it meets these requirements.
>> >> >
>> >> > Please review Section 6.2 of RFC 8086 for example how that can be d=
one.
>> >>
>> >> OK. We'll look into it.
>> >>
>> >> > TCP Encapsulation issue
>> >> > -----------------------
>> >> >
>> >> > Section 5.6:
>> >> >
>> >> > The TCP encapsulation appear to be missing an delimiter format allo=
wing
>> >> each
>> >> > individual TRILL packet/payload to be read out of the TCP's byte st=
ream.
>> In
>> >> > other words, a normal implementation has no way of ensuring that th=
e
>> TCP
>> >> > payload starts with the start of a new TRILL payload. Multiple smal=
l TRILL
>> >> > payloads may be included in the same TCP payload, and also only par=
ts
>> as
>> >> TCP is
>> >> > one way of dealing with TRILL packets that are larger than the
>> >> IP+Encapsulation
>> >> > MTU that actually will work.
>> >> >
>> >> > This comment is based on that there appear to be no length fields
>> included
>> >> in
>> >> > the TRILL header. The most straight forward delimiter is a 2-byte l=
ength
>> >> field
>> >> > for the TRILL payload to be encapsulated.
>> >>
>> >> Right. It might also be useful to include some sort of check field, a=
s
>> >> is done in BGP, to detect if you are out of sync in parsing the TCP
>> >> stream.
>> >>
>> >> Another point is that, while with UDP it seems fine to send packets
>> >> with assorted QoS, you don't want to encourage re-ordering of TCP
>> >> packets in a stream. So if TCP encapsulation is being used, you want
>> >> to use the same DSCP value for the packets in a particular TCP stream=
.
>> >> So, generally, you need to have a TCP connection per priority handlin=
g
>> >> category. Mapping the 8 priority levels into a smaller number of
>> >> handling categories is a normal thing to do so you certainly don't
>> >> necessarily need 8 TCP connections. Adding material on this should no=
t
>> >> be too hard.
>> >>
>> >> > Section 5.6:
>> >> >
>> >> > TCP endpoint requirements. I do wonder if an application like TRILL=
 actual
>> >> > would need to discuss performance impacting implementation choices =
or
>> >> > limitations. For example use of NAGLE, the requirements on buffer s=
izes
>> in
>> >> > relation to Bandwidth delay products, as buffer memory in a RBridge=
 will
>> >> impact
>> >> > performance.
>> >>
>> >> Well, I'm not sure how deeply this document should get into such
>> >> performance issues. What about just saying something about
>> >> consideration being given to tuning TCP for performance and pointing
>> >> to one or a few other RFCs that talk about this?
>> >>
>> >> > Congestion Control
>> >> > ------------------
>> >> > First thanks for the effort here.
>> >>
>> >> You're welcome.
>> >>
>> >> > 8.1.2 In Other Environments
>> >> >
>> >> >    Where UDP based encapsulation headers are used in TRILL over IP =
in
>> >> >    environments other than those discussed in Section 8.1.1, specif=
ic
>> >> >    congestion control mechanisms are commonly needed.  However, if =
the
>> >> >    traffic being carried by the TRILL over IP link is already conge=
stion
>> >> >    controlled and the size and volatility of the TRILL IS-IS link s=
tate
>> >> >    database is limited, then specific congestion control may not be
>> >> >    needed. See [RFC8085] Section 3.1.11 for further guidance.
>> >> >
>> >> > This is correct, however my question is if the RBridges have any wa=
y of
>> >> knowing
>> >> > which traffic is actually congestion controlled, considering that T=
RILL
>> >> provides
>> >> > an layer 2 abstraction. I wonder if there should be any type of whi=
te list of
>> >> > the types of layer 2 payloads that can be assumed to be congestion
>> >> controlled,
>> >> > and thus okay to forward over IP paths? I am worried that without a=
ny
>> >> > recommendation to prevent traffic that is not controlled to be forw=
arded,
>> >> can
>> >> > lead to congestion issues.
>> >> >
>> >> > The other issue I think may exist is the issue serial unicast emula=
tion of
>> >> > broadcast/multicast creates. As this amplifies the outgoing packet =
rate
>> with
>> >> > a factor of how many addresses are configured for serial unicast th=
is can
>> >> > be significant traffic expansion. Thus, I think additional consider=
ations are
>> >> > needed here, and maybe rate limiting of the amount of traffic to be
>> >> multicasted.
>> >>
>> >> OK. We can think about those issues.
>> >>
>> >> > Flow and ECMP
>> >> > -------------
>> >> >
>> >> > Section 8.3:
>> >> >
>> >> > For example, for TRILL
>> >> >    Data, this entropy field could be based on some hash of the
>> >> >    Inner.MacDA, Inner.MacSA, and Inner.VLAN or Inner.FGL.
>> >> >
>> >> > I would appreciate clearer references to what these fields are.
>> >>
>> >> In a TRILL Data packet, the payload after the TRILL Header looks like
>> >> an Ethernet frame except that there is always either a VLAN tag or,
>> >> alternatively, where the VLAN tag would be, a Fine Grained Label
>> >> [RFC7172]. (The preceding is the view in the TRILL RFCs, but there is
>> >> an equivalent and equally valid view in which all the fields through
>> >> and including the VLAN or FGL tag are part of the TRILL Header.) The
>> >> TRILL base protocol specification focuses on Ethernet as a link
>> >> technology between TRILL switches, in which case there will be a link
>> >> header including an Outer.MacDA and Outer.MacSA fields and possibly a=
n
>> >> Outer.VLAN, all before the TRILL Header. See Figure 1 and Figure 2 in
>> >> RFC 7172.
>> >>
>> >> Some of the above could be added to the draft for clarity.
>> >>
>> >> > If I understand this correctly, the idea here is to look into the i=
nner
>> >> > layer 2 frames, and use the flow equivalents that exists on that le=
vel and
>> >> > hash that into value that maps the flows onto the source port range=
.
>> >>
>> >> Yes.
>> >>
>> >> > I think this text should include a summary of the principle and ens=
ure to
>> >> > note the important requirement that what is considered flows in the
>> inner
>> >> > must not result in being striped over multiple source ports as this=
 may
>> lead
>> >> to
>> >> > reordering issues due to packets taking different paths.
>> >>
>> >> Well, we can add some text. But when would the relative ordering
>> >> matter for two TRILL Data packets where the two inner native payloads
>> >> have different values for any one or more of these three fields
>> >> (Inner.MacDA, Inner.MacSA, and inner VLAN/FGL tag) ? If any of those
>> >> fields are different, you are talking about different streams.
>> >>
>> >> > NAT and TRILL over IP:
>> >> > Section 8.5:
>> >> >
>> >> > If one like to use TRILL over IP through a NAT, then there are some=
 very
>> >> > important considerations that are missing. First the need for stati=
c
>> binding
>> >> > configurations or the need for determining ones external address(es=
) and
>> >> be
>> >> > able to communicate that to the peer RBridges, and in addition ensu=
re
>> that
>> >> one
>> >> > has keep-alives to that the NAT binding never times out.
>> >>
>> >> I think those are good points. There is an additional problem that
>> >> TRILL Hellos detect neighbors with which they have 2-way connectivity
>> >> by indicating, inside the Hellos that are sent, from what neighbors
>> >> Hellos have been received on that port. If a NAT is involved, these
>> >> neighbor addresses inside Hellos need to be mapped.
>> >>
>> >> > Next is the issue that there is almost zero chance of getting a IP/=
UDP
>> >> > encapsulation TRILL payload through the NAT if it results in IP
>> >> fragmentation,
>> >> > as NATs don't do defragment and refragmented on the internal side, =
and
>> >> an IP
>> >> > fragment lacks UDP port and thus can't be matched to binding.
>> >>
>> >> So perhaps the recommendation should be to configure the port to use
>> >> TCP if there will be fragmentation.
>> >>
>> >> > Also if you like to run IP/ESP through a NAT, then you most likely =
need the
>> >> > IP/UDP/ESP encapsulation (https://tools.ietf.org/html/rfc3948). Not=
e
>> that
>> >> this
>> >> > will restrict the MTU even further and thus ensure that the 1470
>> >> requirement
>> >> > cannot be fulfilled even without additional tunnels over an 1500 by=
tes
>> MTU
>> >> > Ethernet infrastructure.
>> >> >
>> >> > I would note that also firewalls likely have issues with IP fragmen=
ts for
>> the
>> >> > same reason, they require significant amount of state to be verifie=
d if
>> they
>> >> > should be let through.
>> >> >
>> >> > In general I think you should create a configuration that has chanc=
e to
>> work
>> >> > through most middleboxes, but I think you should require static bin=
dings.
>> I
>> >> > think that configuration is, and don't laugh now, but
>> >> IP/UDP/ESP/TCP/TRILL,
>> >> > otherwise you will not be able to have both security and reliable
>> >> fragmentation
>> >> > of TRILL packets.
>> >>
>> >> OK. Thanks again for this review. It has pointed out a number of
>> >> problems and in thinking about those, I believe a couple of further
>> >> problems have come to mind that I mentioned above. We'll work on a
>> >> revised draft.
>> >>
>> >> Thanks,
>> >> Donald
>> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
>> >>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>> >>  155 Beaver Street, Milford, MA 01757 USA
>> >>  d3e3e3@gmail.com
>> >>
>> >> > Cheers
>> >> >
>> >> > Magnus Westerlund
>> >>
>> >> _______________________________________________
>> >> Tsv-art mailing list
>> >> Tsv-art@ietf.org
>> >> https://www.ietf.org/mailman/listinfo/tsv-art


From nobody Sat Jul  1 13:52:35 2017
Return-Path: <cpignata@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56912129AD3; Sat,  1 Jul 2017 13:52:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level: 
X-Spam-Status: No, score=-14.521 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 hV3108t04Vah; Sat,  1 Jul 2017 13:52:32 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E19A7129AEA; Sat,  1 Jul 2017 13:52:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13820; q=dns/txt; s=iport; t=1498942352; x=1500151952; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=K6WG6hFKIWZp+9v5nMZMa8j5Iy21KNL592HCmBqynbs=; b=hqRws3pN0NaKS9LEo/sbdmiHAPgVwcMlCftAvzy7WgoEQETjJSswgtQU XuxSmXOBUuhAEb9sj46+rF+d/hHtsGrU5/PFjuxbmJsLEMnkYyviy+eEu zVW3jaPDJy/ezE0o6q6nw3dJ2E1ETJxH501sURGapkl1BBTTHWCCLsn22 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AqAQBoClhZ/4sNJK1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBg1mBcQeDZYoZoj6FK4IRhhwCGoJ/PxgBAgEBAQEBAQFrKIUZBiNWEAI?= =?us-ascii?q?BCD8DAgICMBQRAgQOBYlLZLIggiaLUAEBAQEBAQEBAQEBAQEBAQEBAQEBAR2DJ?= =?us-ascii?q?4NMgWErgnmHfTCCMQWJT4hWjFoCk3+CDIVKikeVLwEfOIEKdRVbAYUAHIFmdog?= =?us-ascii?q?+gQ0BAQE?=
X-IronPort-AV: E=Sophos;i="5.40,294,1496102400";  d="scan'208,217";a="448178266"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 01 Jul 2017 20:52:31 +0000
Received: from XCH-RTP-018.cisco.com (xch-rtp-018.cisco.com [64.101.220.158]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id v61KqUVQ025136 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 1 Jul 2017 20:52:30 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-018.cisco.com (64.101.220.158) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sat, 1 Jul 2017 16:52:30 -0400
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1210.000; Sat, 1 Jul 2017 16:52:29 -0400
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
CC: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "spring@ietf.org" <spring@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-spring-oam-usecase.all@ietf.org" <draft-ietf-spring-oam-usecase.all@ietf.org>
Subject: Re: Rtgdir last call review of draft-ietf-spring-oam-usecase-06
Thread-Topic: Rtgdir last call review of draft-ietf-spring-oam-usecase-06
Thread-Index: AQHS61uWxVbWnw4SLk2wgKSt4LG4WKI/xD6A
Date: Sat, 1 Jul 2017 20:52:29 +0000
Message-ID: <6B35D999-331B-4DB3-A9F1-C2BEF4EC0944@cisco.com>
References: <149813817013.30481.17524594111387704082@ietfa.amsl.com>
In-Reply-To: <149813817013.30481.17524594111387704082@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.116.131]
Content-Type: multipart/alternative; boundary="_000_6B35D999331B4DB3A9F1C2BEF4EC0944ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5k-3uP7FDtvGdJdxpAf1z0JieqA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Jul 2017 20:52:34 -0000

--_000_6B35D999331B4DB3A9F1C2BEF4EC0944ciscocom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

VGhhbmtzIGZvciB5b3VyIHJldmlldywgSm9lbCENCg0KUmV2aXNpb24gLTA3LCBqdXN0IHN1Ym1p
dHRlZCwgc2hvdWxkIGFkZHJlc3MgYWxsIHlvdXIgY29uY2VybnMgYW5kIHN1Z2dlc3Rpb25zLiBQ
bGVhc2UgbGV0IHVzIGtub3cgb3RoZXJ3aXNlLg0KDQpUaGFua3MsDQoNCuKAlCBDYXJsb3MuDQoN
Ck9uIEp1biAyMiwgMjAxNywgYXQgOToyOSBBTSwgSm9lbCBIYWxwZXJuIDxqbWhAam9lbGhhbHBl
cm4uY29tPG1haWx0bzpqbWhAam9lbGhhbHBlcm4uY29tPj4gd3JvdGU6DQoNClJldmlld2VyOiBK
b2VsIEhhbHBlcm4NClJldmlldyByZXN1bHQ6IEhhcyBOaXRzDQoNClRoaXMgaXMgYSBydGctZGly
IHJlcXVlc3RlZCByZXZpZXcuDQoNClN1bW1hcnk6IFJlYWR5IGZvciBwdWJsaWNhdGlvbiBhcyBh
biBJbmZvcm1hdGlvbmFsIFJGQyB3aXRoIHNvbWUgbWlub3IgaXRlbXMNCnRoYXQgc2hvdWxkIGJl
IGNvbnNpZGVyZWQuDQoNCk1ham9yOiBOL0ENCg0KTWlub3I6DQogICBUaGUgaW50cm9kdWN0aW9u
IHRyZWF0cyBoYXZpbmcgYSBzaW5nbGUgY2VudHJhbGl6ZWQgbW9uaXRvcmluZyBzeXN0ZW0gYXMg
YW4NCiAgIHVuYWxsb3llZCBwb3NpdGl2ZS4gIFRvIHNldCBjb250ZXh0IHByb3Blcmx5LCBpdCB3
b3VsZCBzZWVtIG1vcmUNCiAgIGFwcHJvcHJpYXRlIHRvIG5vdGUgdGhhdCBtYW55IG9wZXJhdG9y
cyBmaW5kIHN1Y2ggY2VudHJhbCBzeXN0ZW1zIHVzZWZ1bCwNCiAgIGFuZCB0aGUgYXBwcm9hY2gg
ZGVzY3JpYmVkIGhlcmUgZW5hYmxlcyB0aGF0IHdoZW4gZGVzaXJlZC4NCg0KICAgVGhlIHJlZmVy
ZW5jZSBpbiB0aGUgaW50cm9kdWN0aW9uIHRvIElHUCB0b3BvbG9neSBkaXNjb3ZlcnkgaXMgdmVy
eQ0KICAgY29uZnVzaW5nLiAiQWRkaW5nIE1QTFMgdG9wb2xvZ3kgYXdhcmVuZXNzIHRvIGFuIElH
UCBzcGVha2luZyBkZXZpY2UgaGVuY2UNCiAgIGVuYWJsZXMgYSBzaW1wbGUgYW5kIHNjYWxhYmxl
IGRhdGEgcGxhbmUgYmFzZWQgbW9uaXRvcmluZyBtZWNoYW5pc20uIiAgQXMNCiAgIG5vdGVkIGxh
dGVyIGluIHRoZSBkb2N1bWVudCwgbGluay1zdGF0ZSBJR1BzIHByb3ZpZGUgdG9wb2xvZ3kgYXdh
cmVuZXNzLg0KICAgU28gd2hhdCBpcyB0aGlzIHBhcnQgb2YgdGhlIGludHJvZHVjdGlvbiB0cnlp
bmcgdG8gc2F5PyAgKFNpZGUtbm90ZSwgbm90DQogICBhbGwgSUdQcyBhcmUgbGluayBzdGF0ZSwg
YWx0aG91Z2ggdGhlIGFwcGxpY2FiaWxpdHkgb2YgQmFiZWwgb3IgUklQIHRvIE1QTFMNCiAgIFNl
Z21lbnQgUm91dGluZyBpcyBjbGVhcmx5IG91dHNpZGUgdGhlIHNjb3BlIG9mIHRoaXMgZG9jdW1l
bnQuKQ0KDQogICBJbiBzZWN0aW9uIDUuMSBpbiBkaXNjdXNzaW5nIHBhdGggdHJhY2UgdGhlIHJl
ZmVyZW5jZSBpcyB0byBSRkMgNDM3OSB3aGljaA0KICAgaXMgYSBjbGVhciBzb3VyY2UgZm9yIHBh
dGggdHJhY2UuICBIb3dldmVyLCB0aGUgdGV4dCByZWZlcnMgdG8gInRyZWUNCiAgIHRyYWNlIi4g
IFdoaWxlIHRoYXQgbWF5IGhhdmUgYmVjb21lIGEgY29tbW9uIHBocmFzZSBmb3IgdGhlIHVzYWdl
LCBpdCBpcw0KICAgbm90IHVzZWQgaW4gUkZDIDQzNzkuICBUaGUgdGVybSBzaG91bGQgZWl0aGVy
IGJlIGV4cGxhaW4sIGluY2x1ZGUgYQ0KICAgc3VpdGFibGUgcmVmZXJlbmNlLCBvciBub3QgYmUg
dXNlZC4NCg0KICBJbiBzZWN0aW9uIDUuMyBvbiBmYXVsdCBpc29sYXRpb24sIHRoZSB0ZXh0IG5v
dGVzIHRoYXQgdGhlIG9ubHkgZGlmZmVyZW5jZQ0KICBiZXR3ZWVuIHRoZSB0ZXN0IHdoaWNoIHN1
Y2NlZWRzIGFuZCB0aGF0IHdoaWNoIGZhaWxzIGlzIHRoZSBkaWZmZXJlbmNlIHRoZQ0KICB0aGUg
YWRqYWNlbmN5IFNJRC4gIFRoZSB0ZXh0IHRoZW4gZ29lcyBvbiB0byBzYXkgIkFzc3VtaW5nIHRo
ZSBzZWNvbmQgcHJvYmUNCiAgaGFzIGJlZW4gcm91dGVkIGNvcnJlY3RseSwgdGhlIGZhdWx0IG11
c3QgaGF2ZSBiZWVuIG9jY3VycmluZyBpbiBSMiB3aGljaA0KICBkaWRuJ3QgZm9yd2FyZCB0aGUg
cGFja2V0IHRvIHRoZSBpbnRlcmZhY2UgaWRlbnRpZmllZCBieSBpdHMgQWRqYWNlbmN5IFNJRA0K
ICA2NjMuIiAgVGhhdCBkb2VzIG5vdCBmb2xsb3cuICBJZiB0aGUgbGluayBhcyBmYWlsZWQgaW4g
YW4gdW5kZXRlY3RlZCBmYXNoaW9uDQogIChlaXRoZXIgaW4gb25lIGRpcmVjdGlvbiBvciBib3Ro
KSwgUjIgd291bGQgYmUgZnVuY3Rpb25pbmcgZmluZSBhbmQgdGhlDQogIHN5bXB0b20gd291bGQg
YmUgdGhlIHNhbWUuICBSZW1vdGVseSBkZXRlY3RpbmcgdGhlIGRpZmZlcmVuY2UgYmV0d2VlbiBS
Mg0KICBmYWlsaW5nIHRvIGZvcndhcmQgYW5kIHRoZSBsaW5rIG5vdCB3b3JraW5nIHNlZW1zIGEg
bXVjaCBoYXJkZXIgdGFzay4NCg0KICAgVGhlIGNsYWltIHRoYXQgdGhlIFBNUyBjYW4gLyBzaG91
bGQgKGludGVudCBpcyBhbWJpZ3VvdXMpIG5vdGlmeSB0aGUgcm91dGVyDQogICB3aGVuIGl0IGRl
dGVjdHMgYSBwYXRoIGZhaWx1cmUgcmFpc2VzIGEgbnVtYmVyIG9mIGlzc3Vlcy4gICBJdCBpcyBu
b3QgYXQNCiAgIGFsbCBjbGVhciB3aGF0IHRoZSByb3V0ZXIgd291bGQgZG8gd2l0aCB0aGUgbm90
aWZpY2F0aW9uLiAgKGUuZy4gSWYgaXQNCiAgIHJlbW92ZWQgdGhlIGxpbmsgZnJvbSBzZXJ2aWNl
LCB0aGVuIGZ1dHVyZSBtb25pdG9yaW5nIHdvdWxkIG5vdCBiZSBhYmxlIHRvDQogICBkZXRlY3Qg
dGhhdCB0aGUgbGluayB3YXMgd29ya2luZy4pICBFaXRoZXIgdGhpcyBuZWVkcyB0byBiZWNvbWUg
YQ0KICAgc2lnbmlmaWNhbnRseSBsYXJnZXIgc2VjdGlvbiwgb3IgKG1vcmUgbGlrZWx5KSB0aGUg
dGV4dCBuZWVkcyB0byBiZSByZW1vdmVkLg0KDQpFZGl0b3JpYWw6DQogICBDaGFwdGVyIDcgaXMg
dGl0bGVkIGRlYWxpbmcgd2l0aCBub24tU1IgZW52aXJvbm1lbnRzLiAgV2hpY2ggbWFrZXMgc2Vu
c2UuDQogICBUaGUgdGV4dCB0aGVuIHN3aXRjaGVzIHRvIHVzaW5nICJwcmUtU1IiIGluc3RlYWQg
b2YgIm5vbi1TUiIuICBJIHdvdWxkDQogICByZWNvbW1lbmQgdGhhdCBhbGwgdXNlcyBvZiAicHJl
LVNSIiBiZSBjaGFuZ2VkIHRvICJub24tU1IiLg0KDQoNCuKAlA0KQ2FybG9zIFBpZ25hdGFybywg
Y2FybG9zQGNpc2NvLmNvbTxtYWlsdG86Y2FybG9zQGNpc2NvLmNvbT4NCg0K4oCcU29tZXRpbWVz
IEkgdXNlIGJpZyB3b3JkcyB0aGF0IEkgZG8gbm90IGZ1bGx5IHVuZGVyc3RhbmQsIHRvIG1ha2Ug
bXlzZWxmIHNvdW5kIG1vcmUgcGhvdG9zeW50aGVzaXMuIg0KDQo=

--_000_6B35D999331B4DB3A9F1C2BEF4EC0944ciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <373CD0989D13A848AC179573BDD1D29F@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KVGhhbmtzIGZvciB5b3VyIHJldmll
dywgSm9lbCEmbmJzcDsNCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2
IGNsYXNzPSIiPlJldmlzaW9uIC0wNywganVzdCBzdWJtaXR0ZWQsIHNob3VsZCBhZGRyZXNzIGFs
bCB5b3VyIGNvbmNlcm5zIGFuZCBzdWdnZXN0aW9ucy4gUGxlYXNlIGxldCB1cyBrbm93IG90aGVy
d2lzZS48L2Rpdj4NCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNs
YXNzPSIiPlRoYW5rcyw8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+
DQo8ZGl2IGNsYXNzPSIiPuKAlCBDYXJsb3MuPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFz
cz0iIj4NCjxkaXY+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj4NCjxkaXYgY2xh
c3M9IiI+T24gSnVuIDIyLCAyMDE3LCBhdCA5OjI5IEFNLCBKb2VsIEhhbHBlcm4gJmx0OzxhIGhy
ZWY9Im1haWx0bzpqbWhAam9lbGhhbHBlcm4uY29tIiBjbGFzcz0iIj5qbWhAam9lbGhhbHBlcm4u
Y29tPC9hPiZndDsgd3JvdGU6PC9kaXY+DQo8YnIgY2xhc3M9IkFwcGxlLWludGVyY2hhbmdlLW5l
d2xpbmUiPg0KPGRpdiBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+UmV2aWV3ZXI6IEpvZWwgSGFs
cGVybjxiciBjbGFzcz0iIj4NClJldmlldyByZXN1bHQ6IEhhcyBOaXRzPGJyIGNsYXNzPSIiPg0K
PGJyIGNsYXNzPSIiPg0KVGhpcyBpcyBhIHJ0Zy1kaXIgcmVxdWVzdGVkIHJldmlldy48YnIgY2xh
c3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpTdW1tYXJ5OiBSZWFkeSBmb3IgcHVibGljYXRpb24gYXMg
YW4gSW5mb3JtYXRpb25hbCBSRkMgd2l0aCBzb21lIG1pbm9yIGl0ZW1zPGJyIGNsYXNzPSIiPg0K
dGhhdCBzaG91bGQgYmUgY29uc2lkZXJlZC48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpN
YWpvcjogTi9BPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KTWlub3I6PGJyIGNsYXNzPSIi
Pg0KJm5ic3A7Jm5ic3A7Jm5ic3A7VGhlIGludHJvZHVjdGlvbiB0cmVhdHMgaGF2aW5nIGEgc2lu
Z2xlIGNlbnRyYWxpemVkIG1vbml0b3Jpbmcgc3lzdGVtIGFzIGFuPGJyIGNsYXNzPSIiPg0KJm5i
c3A7Jm5ic3A7Jm5ic3A7dW5hbGxveWVkIHBvc2l0aXZlLiAmbmJzcDtUbyBzZXQgY29udGV4dCBw
cm9wZXJseSwgaXQgd291bGQgc2VlbSBtb3JlPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Jm5i
c3A7YXBwcm9wcmlhdGUgdG8gbm90ZSB0aGF0IG1hbnkgb3BlcmF0b3JzIGZpbmQgc3VjaCBjZW50
cmFsIHN5c3RlbXMgdXNlZnVsLDxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwOyZuYnNwO2FuZCB0
aGUgYXBwcm9hY2ggZGVzY3JpYmVkIGhlcmUgZW5hYmxlcyB0aGF0IHdoZW4gZGVzaXJlZC48YnIg
Y2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDsmbmJzcDtUaGUgcmVmZXJlbmNl
IGluIHRoZSBpbnRyb2R1Y3Rpb24gdG8gSUdQIHRvcG9sb2d5IGRpc2NvdmVyeSBpcyB2ZXJ5PGJy
IGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Y29uZnVzaW5nLiAmcXVvdDtBZGRpbmcgTVBM
UyB0b3BvbG9neSBhd2FyZW5lc3MgdG8gYW4gSUdQIHNwZWFraW5nIGRldmljZSBoZW5jZTxiciBj
bGFzcz0iIj4NCiZuYnNwOyZuYnNwOyZuYnNwO2VuYWJsZXMgYSBzaW1wbGUgYW5kIHNjYWxhYmxl
IGRhdGEgcGxhbmUgYmFzZWQgbW9uaXRvcmluZyBtZWNoYW5pc20uJnF1b3Q7ICZuYnNwO0FzPGJy
IGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7bm90ZWQgbGF0ZXIgaW4gdGhlIGRvY3VtZW50
LCBsaW5rLXN0YXRlIElHUHMgcHJvdmlkZSB0b3BvbG9neSBhd2FyZW5lc3MuIDxiciBjbGFzcz0i
Ij4NCiZuYnNwOyZuYnNwOyZuYnNwO1NvIHdoYXQgaXMgdGhpcyBwYXJ0IG9mIHRoZSBpbnRyb2R1
Y3Rpb24gdHJ5aW5nIHRvIHNheT8gJm5ic3A7KFNpZGUtbm90ZSwgbm90PGJyIGNsYXNzPSIiPg0K
Jm5ic3A7Jm5ic3A7Jm5ic3A7YWxsIElHUHMgYXJlIGxpbmsgc3RhdGUsIGFsdGhvdWdoIHRoZSBh
cHBsaWNhYmlsaXR5IG9mIEJhYmVsIG9yIFJJUCB0byBNUExTPGJyIGNsYXNzPSIiPg0KJm5ic3A7
Jm5ic3A7Jm5ic3A7U2VnbWVudCBSb3V0aW5nIGlzIGNsZWFybHkgb3V0c2lkZSB0aGUgc2NvcGUg
b2YgdGhpcyBkb2N1bWVudC4pPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5i
c3A7Jm5ic3A7SW4gc2VjdGlvbiA1LjEgaW4gZGlzY3Vzc2luZyBwYXRoIHRyYWNlIHRoZSByZWZl
cmVuY2UgaXMgdG8gUkZDIDQzNzkgd2hpY2g8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDsmbmJz
cDtpcyBhIGNsZWFyIHNvdXJjZSBmb3IgcGF0aCB0cmFjZS4gJm5ic3A7SG93ZXZlciwgdGhlIHRl
eHQgcmVmZXJzIHRvICZxdW90O3RyZWU8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDsmbmJzcDt0
cmFjZSZxdW90Oy4gJm5ic3A7V2hpbGUgdGhhdCBtYXkgaGF2ZSBiZWNvbWUgYSBjb21tb24gcGhy
YXNlIGZvciB0aGUgdXNhZ2UsIGl0IGlzPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7
bm90IHVzZWQgaW4gUkZDIDQzNzkuICZuYnNwO1RoZSB0ZXJtIHNob3VsZCBlaXRoZXIgYmUgZXhw
bGFpbiwgaW5jbHVkZSBhPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7c3VpdGFibGUg
cmVmZXJlbmNlLCBvciBub3QgYmUgdXNlZC48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQom
bmJzcDsmbmJzcDtJbiBzZWN0aW9uIDUuMyBvbiBmYXVsdCBpc29sYXRpb24sIHRoZSB0ZXh0IG5v
dGVzIHRoYXQgdGhlIG9ubHkgZGlmZmVyZW5jZTxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO2Jl
dHdlZW4gdGhlIHRlc3Qgd2hpY2ggc3VjY2VlZHMgYW5kIHRoYXQgd2hpY2ggZmFpbHMgaXMgdGhl
IGRpZmZlcmVuY2UgdGhlPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7dGhlIGFkamFjZW5jeSBT
SUQuICZuYnNwO1RoZSB0ZXh0IHRoZW4gZ29lcyBvbiB0byBzYXkgJnF1b3Q7QXNzdW1pbmcgdGhl
IHNlY29uZCBwcm9iZTxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO2hhcyBiZWVuIHJvdXRlZCBj
b3JyZWN0bHksIHRoZSBmYXVsdCBtdXN0IGhhdmUgYmVlbiBvY2N1cnJpbmcgaW4gUjIgd2hpY2g8
YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDtkaWRuJ3QgZm9yd2FyZCB0aGUgcGFja2V0IHRvIHRo
ZSBpbnRlcmZhY2UgaWRlbnRpZmllZCBieSBpdHMgQWRqYWNlbmN5IFNJRDxiciBjbGFzcz0iIj4N
CiZuYnNwOyZuYnNwOzY2My4mcXVvdDsgJm5ic3A7VGhhdCBkb2VzIG5vdCBmb2xsb3cuICZuYnNw
O0lmIHRoZSBsaW5rIGFzIGZhaWxlZCBpbiBhbiB1bmRldGVjdGVkIGZhc2hpb248YnIgY2xhc3M9
IiI+DQombmJzcDsmbmJzcDsoZWl0aGVyIGluIG9uZSBkaXJlY3Rpb24gb3IgYm90aCksIFIyIHdv
dWxkIGJlIGZ1bmN0aW9uaW5nIGZpbmUgYW5kIHRoZTxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNw
O3N5bXB0b20gd291bGQgYmUgdGhlIHNhbWUuICZuYnNwO1JlbW90ZWx5IGRldGVjdGluZyB0aGUg
ZGlmZmVyZW5jZSBiZXR3ZWVuIFIyPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7ZmFpbGluZyB0
byBmb3J3YXJkIGFuZCB0aGUgbGluayBub3Qgd29ya2luZyBzZWVtcyBhIG11Y2ggaGFyZGVyIHRh
c2suPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7VGhlIGNs
YWltIHRoYXQgdGhlIFBNUyBjYW4gLyBzaG91bGQgKGludGVudCBpcyBhbWJpZ3VvdXMpIG5vdGlm
eSB0aGUgcm91dGVyPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7d2hlbiBpdCBkZXRl
Y3RzIGEgcGF0aCBmYWlsdXJlIHJhaXNlcyBhIG51bWJlciBvZiBpc3N1ZXMuICZuYnNwOyZuYnNw
O0l0IGlzIG5vdCBhdDxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwOyZuYnNwO2FsbCBjbGVhciB3
aGF0IHRoZSByb3V0ZXIgd291bGQgZG8gd2l0aCB0aGUgbm90aWZpY2F0aW9uLiAmbmJzcDsoZS5n
LiBJZiBpdDxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwOyZuYnNwO3JlbW92ZWQgdGhlIGxpbmsg
ZnJvbSBzZXJ2aWNlLCB0aGVuIGZ1dHVyZSBtb25pdG9yaW5nIHdvdWxkIG5vdCBiZSBhYmxlIHRv
PGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7ZGV0ZWN0IHRoYXQgdGhlIGxpbmsgd2Fz
IHdvcmtpbmcuKSAmbmJzcDtFaXRoZXIgdGhpcyBuZWVkcyB0byBiZWNvbWUgYTxiciBjbGFzcz0i
Ij4NCiZuYnNwOyZuYnNwOyZuYnNwO3NpZ25pZmljYW50bHkgbGFyZ2VyIHNlY3Rpb24sIG9yICht
b3JlIGxpa2VseSkgdGhlIHRleHQgbmVlZHMgdG8gYmUgcmVtb3ZlZC48YnIgY2xhc3M9IiI+DQo8
YnIgY2xhc3M9IiI+DQpFZGl0b3JpYWw6PGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7
Q2hhcHRlciA3IGlzIHRpdGxlZCBkZWFsaW5nIHdpdGggbm9uLVNSIGVudmlyb25tZW50cy4gJm5i
c3A7V2hpY2ggbWFrZXMgc2Vuc2UuIDxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwOyZuYnNwO1Ro
ZSB0ZXh0IHRoZW4gc3dpdGNoZXMgdG8gdXNpbmcgJnF1b3Q7cHJlLVNSJnF1b3Q7IGluc3RlYWQg
b2YgJnF1b3Q7bm9uLVNSJnF1b3Q7LiAmbmJzcDtJIHdvdWxkPGJyIGNsYXNzPSIiPg0KJm5ic3A7
Jm5ic3A7Jm5ic3A7cmVjb21tZW5kIHRoYXQgYWxsIHVzZXMgb2YgJnF1b3Q7cHJlLVNSJnF1b3Q7
IGJlIGNoYW5nZWQgdG8gJnF1b3Q7bm9uLVNSJnF1b3Q7LjxiciBjbGFzcz0iIj4NCjxiciBjbGFz
cz0iIj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxiciBjbGFzcz0i
Ij4NCjxkaXYgY2xhc3M9IiI+DQo8ZGl2IHN0eWxlPSJjb2xvcjogcmdiKDAsIDAsIDApOyBsZXR0
ZXItc3BhY2luZzogbm9ybWFsOyBvcnBoYW5zOiBhdXRvOyB0ZXh0LWFsaWduOiBzdGFydDsgdGV4
dC1pbmRlbnQ6IDBweDsgdGV4dC10cmFuc2Zvcm06IG5vbmU7IHdoaXRlLXNwYWNlOiBub3JtYWw7
IHdpZG93czogYXV0bzsgd29yZC1zcGFjaW5nOiAwcHg7IC13ZWJraXQtdGV4dC1zdHJva2Utd2lk
dGg6IDBweDsgd29yZC13cmFwOiBicmVhay13b3JkOyAtd2Via2l0LW5ic3AtbW9kZTogc3BhY2U7
IC13ZWJraXQtbGluZS1icmVhazogYWZ0ZXItd2hpdGUtc3BhY2U7IiBjbGFzcz0iIj4NCjxkaXYg
c3R5bGU9ImNvbG9yOiByZ2IoMCwgMCwgMCk7IGxldHRlci1zcGFjaW5nOiBub3JtYWw7IG9ycGhh
bnM6IGF1dG87IHRleHQtYWxpZ246IHN0YXJ0OyB0ZXh0LWluZGVudDogMHB4OyB0ZXh0LXRyYW5z
Zm9ybTogbm9uZTsgd2hpdGUtc3BhY2U6IG5vcm1hbDsgd2lkb3dzOiBhdXRvOyB3b3JkLXNwYWNp
bmc6IDBweDsgLXdlYmtpdC10ZXh0LXN0cm9rZS13aWR0aDogMHB4OyB3b3JkLXdyYXA6IGJyZWFr
LXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJyZWFrOiBhZnRl
ci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KPGRpdiBzdHlsZT0iY29sb3I6IHJnYigwLCAwLCAw
KTsgbGV0dGVyLXNwYWNpbmc6IG5vcm1hbDsgb3JwaGFuczogYXV0bzsgdGV4dC1hbGlnbjogc3Rh
cnQ7IHRleHQtaW5kZW50OiAwcHg7IHRleHQtdHJhbnNmb3JtOiBub25lOyB3aGl0ZS1zcGFjZTog
bm9ybWFsOyB3aWRvd3M6IGF1dG87IHdvcmQtc3BhY2luZzogMHB4OyAtd2Via2l0LXRleHQtc3Ry
b2tlLXdpZHRoOiAwcHg7IHdvcmQtd3JhcDogYnJlYWstd29yZDsgLXdlYmtpdC1uYnNwLW1vZGU6
IHNwYWNlOyAtd2Via2l0LWxpbmUtYnJlYWs6IGFmdGVyLXdoaXRlLXNwYWNlOyIgY2xhc3M9IiI+
DQrigJQ8L2Rpdj4NCjxkaXYgc3R5bGU9ImNvbG9yOiByZ2IoMCwgMCwgMCk7IGxldHRlci1zcGFj
aW5nOiBub3JtYWw7IG9ycGhhbnM6IGF1dG87IHRleHQtYWxpZ246IHN0YXJ0OyB0ZXh0LWluZGVu
dDogMHB4OyB0ZXh0LXRyYW5zZm9ybTogbm9uZTsgd2hpdGUtc3BhY2U6IG5vcm1hbDsgd2lkb3dz
OiBhdXRvOyB3b3JkLXNwYWNpbmc6IDBweDsgLXdlYmtpdC10ZXh0LXN0cm9rZS13aWR0aDogMHB4
OyB3b3JkLXdyYXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtp
dC1saW5lLWJyZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KQ2FybG9zIFBpZ25h
dGFybywmbmJzcDs8YSBocmVmPSJtYWlsdG86Y2FybG9zQGNpc2NvLmNvbSIgY2xhc3M9IiI+Y2Fy
bG9zQGNpc2NvLmNvbTwvYT48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQo8aSBjbGFzcz0i
Ij7igJxTb21ldGltZXMgSSB1c2UgYmlnIHdvcmRzIHRoYXQgSSBkbyBub3QgZnVsbHkgdW5kZXJz
dGFuZCwgdG8gbWFrZSBteXNlbGYgc291bmQgbW9yZSZuYnNwO3Bob3Rvc3ludGhlc2lzLiZxdW90
OzwvaT48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxiciBj
bGFzcz0iIj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_6B35D999331B4DB3A9F1C2BEF4EC0944ciscocom_--


From nobody Sat Jul  1 13:56:16 2017
Return-Path: <cpignata@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DA88129AE8; Sat,  1 Jul 2017 13:56:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 WFwFqW8VHtDE; Sat,  1 Jul 2017 13:56:13 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19091129ADE; Sat,  1 Jul 2017 13:56:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3954; q=dns/txt; s=iport; t=1498942573; x=1500152173; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=H8FmzOAMin7hgl4Eso7WTjxJ3lldqGb72FYbBrR/Elc=; b=A3NMuGKq5a1dbSGwDIl3IuMCwrvNj8LfEBPJuxFHk5baLc4kTSw88Dox 5Xi7IIwt92zlKTah+pXfrNxDEYwhGmLoxirkTZOzTmuYnt3h55IXVSp6h 6nTDRIOXAWpf9DZ6sZqR/ehdjFIcRJzAaOVihZp+yB/E6M1Sth/SILn3I 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DFAAC7C1hZ/5BdJa1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1mBcQeDZYoZkWyVfYIRhhwCGoJ/PxgBAgEBAQEBAQFrKIUYAQE?= =?us-ascii?q?BAQIBIxFFBQsCAQgYAgImAgICMBUQAgQOBYonCLIlgiaLUAEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAR2BC4Icg0yBYSuCeYd9MIIxBZcoh1cCiwiId4IMhUqKR5UvAR8?= =?us-ascii?q?4gQp1FVsBhwJ2iD6BDQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.40,294,1496102400"; d="scan'208";a="264805731"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Jul 2017 20:56:12 +0000
Received: from XCH-RTP-019.cisco.com (xch-rtp-019.cisco.com [64.101.220.159]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id v61KuBf6010282 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 1 Jul 2017 20:56:12 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-019.cisco.com (64.101.220.159) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sat, 1 Jul 2017 16:56:11 -0400
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1210.000; Sat, 1 Jul 2017 16:56:11 -0400
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Joel Jaeggli <joelja@bogus.com>
CC: "ops-dir@ietf.org" <ops-dir@ietf.org>, "spring@ietf.org" <spring@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-spring-oam-usecase.all@ietf.org" <draft-ietf-spring-oam-usecase.all@ietf.org>
Subject: Re: Opsdir last call review of draft-ietf-spring-oam-usecase-06
Thread-Topic: Opsdir last call review of draft-ietf-spring-oam-usecase-06
Thread-Index: AQHS8asSheiuQD9TpUafQQQDEffqE6I/uKYA
Date: Sat, 1 Jul 2017 20:56:11 +0000
Message-ID: <25E86852-0B40-43C4-BFF2-C83088F34B5D@cisco.com>
References: <149883201392.4666.499169365560986574@ietfa.amsl.com>
In-Reply-To: <149883201392.4666.499169365560986574@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.116.131]
Content-Type: text/plain; charset="utf-8"
Content-ID: <F0860E84A666634CBC18CA347A02504B@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/y5zzlpOBcxiE_NtekmrR2S7-SM8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Jul 2017 20:56:15 -0000

SGksIEpvZWwsDQoNCk1hbnkgdGhhbmtzIGZvciB5b3VyIHJldmlldyEgUGxlYXNlIHNlZSBpbmxp
bmUuDQoNCj4gT24gSnVuIDMwLCAyMDE3LCBhdCAxMDoxMyBBTSwgSm9lbCBKYWVnZ2xpIDxqb2Vs
amFAYm9ndXMuY29tPiB3cm90ZToNCj4gDQo+IFJldmlld2VyOiBKb2VsIEphZWdnbGkNCj4gUmV2
aWV3IHJlc3VsdDogSGFzIE5pdHMNCj4gDQo+IEkgaGF2ZSByZXZpZXdlZA0KPiANCj4gZHJhZnQt
aWV0Zi1zcHJpbmctb2FtLXVzZWNhc2UtMDYgYXMgcGFyIG9mIHRoZSBPUFMgZGlyZWN0b3JhdGUg
cmV2aWV3IGN5Y2xlDQo+IGZvcklFVEYgbGFzdCBjYWxsLg0KPiANCj4gSW4gZ2VuZXJhbCBJIHRo
aW5rIHRoaXMgZG9jdW1lbnQgaXMgcmVhZHkgdG8gZ28gaG93ZXZlciBJIGhhdmUgYSBjb3VwbGUg
b2YNCj4gY29uY2VybnMgdGhhdCBzaG91bGQgcHJvYmFibHkgYXQgbGVhc3QgYmUgZGlzY3Vzc2Vk
IHByaW9yIHRvIElFU0cgcmV2aWV3Lg0KPiANCj4+IEZyb20gbXkgdmFudGFnZSBwb2ludCB0aGUg
ZG9jdW1lbnQgaXMgbm90IHNvIG11Y2ggYSBkZXNjcmlwdGlvbiBvZiBhIHVzZSBjYXNlDQo+IG9y
IHJlcXVpcmVtZW50cyBhcyBpdCBpcyB0aGUgYXJjaGl0ZWN0dXJhbCB3cmFwcGVyIGFyb3VuZA0K
PiBkcmFmdC1pZXRmLW1wbHMtc3ByaW5nLWxzcC1waW5nLiBJdCdzIG1vc3QgaGVscGZ1bCBpbiBt
eSBvcGluaW9uIHRvIHJldmlldyB0aGlzDQo+IG9uZSBhcyB0aG91Z2ggdGhlIG90aGVyIG9uZSB3
YXMgdGhlIGNvbXBhbmlvbiBkb2N1bWVudCwgZnJvbSB0aGlzIHZhbnRhZ2UgcG9pbnQNCj4gSSB0
aGluayB0aGUgbGF0ZXIgZG9jdW1lbnQgaXMgZWZmZWN0aXZlbHkgbm9ybWF0aXZlbHkgcmVmZXJl
bmNlZC4gU2ltaWxhcmx5IHRoZQ0KPiByZWFkaW5lc3Mgb2YgdGhlIGxhdGVyIGRvY3VtZW50ICh3
aGljaCBpcyBhIGJpdCBlYXJsaWVyIGluIGl0J3MgbGlmZWN5Y2xlKQ0KPiByYWlzZXMgdGhlIHF1
ZXN0aW9uIG9mIHdoZXRoZXIgdGhpcyBvbmUgaXMgcmVhZHkgdG8gZ28uDQo+IA0KDQpJIGFncmVl
IHRoYXQgdGhpcyBpcyBub3Qgc28gbXVjaCBhIHVzZS1jYXNlIGRvY3VtZW50IOKAlCBob3dldmVy
LCBJIHdvdWxkIG5vdCBjaGFyYWN0ZXJpemUgdGhpcyBkb2N1bWVudCBhcyBzdGFuZGluZyBhdG9w
IGRyYWZ0LWlldGYtbXBscy1zcHJpbmctbHNwLXBpbmcuIEluIGZhY3QsIHRoZSBtb25pdG9yaW5n
IHN5c3RlbSBkZXNjcmliZWQsIGFzIHRoZSB0ZXh0IGFscmVhZHkgc2hvd3MsIGNhbiB1c2Ugb3Ro
ZXIgT0FNIHByb3RvY29scyBhbmQgZm9ybWF0cy4gVGhhdCBpcywgaWYgdGhlIFBNUyB1c2VzIGZv
ciBleGFtcGxlIEJGRCwgYW5kIHRoZXJlZm9yZSBpdCBkb2VzIG5vdCB1c2UgUkZDIDgwMjksIHRo
ZW4gaXQgY2Fubm90IHVzZSBkcmFmdC1pZXRmLW1wbHMtc3ByaW5nLWxzcC1waW5nIChiZWNhdXNl
IHRob3NlIGFyZSBleHRlbnNpb25zIG9mIE1QTFMgTFNQIFBpbmcpLiBGdXJ0aGVyLCB0aGUgUE1T
IGNhbiBwZXJmZWN0bHkgd2VsbCAoYXMgYWxyZWFkeSBkZXNjcmliZWQpIGZ1bmN0aW9uIHdpdGgg
UkZDIDgwMjkgYW5kIHdpdGhvdXQgZHJhZnQtaWV0Zi1tcGxzLXNwcmluZy1sc3AtcGluZy4gZHJh
ZnQtaWV0Zi1tcGxzLXNwcmluZy1sc3AtcGluZyBwcm92aWRlcyB2ZXJ5IHVzZWZ1bCBlbmhhbmNl
bWVudHMgdGhhdCB0aGUgc3lzdGVtIGNhbiBsZXZlcmFnZSwgYnV0IHRoZSBzeXN0ZW0gaXMgbm90
IHdyYXBwZWQgYXJvdW5kIHRoZSBzcGVjaWZpY2F0aW9uIG9mIGRyYWZ0LWlldGYtbXBscy1zcHJp
bmctbHNwLXBpbmcuDQoNCldlIHRyaWVkIHRvIGNsYXJpZnkgdGhpcyBhIGJpdCBpbiB0aGUgdmVy
c2lvbiBqdXN0IHN1Ym1pdHRlZC4NCg0KPiBpbiB0aGUgc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMg
c2VjdGlvbiB0aGUgZG9jdW1lbnQgbm90ZXM6DQo+IA0KPiAgIEFzIG1lbnRpb25lZCBpbiB0aGUg
aW50cm9kdWN0aW9uLCBhIFBNUyBtb25pdG9yaW5nIHBhY2tldCBzaG91bGQNCj4gICBuZXZlciBs
ZWF2ZSB0aGUgZG9tYWluIHdoZXJlIGl0IG9yaWdpbmF0ZWQuICBJdCB0aGVyZWZvcmUgc2hvdWxk
DQo+ICAgbmV2ZXIgdXNlIHN0YWxlIE1QTFMgb3IgSUdQIHJvdXRpbmcgaW5mb3JtYXRpb24uDQo+
IA0KPiBJIHRoaW5rIGlzIGlzIG1vcmUgYWNjdXJhdGUgdG8gc2F5Og0KPiANCj4gVXNlIG9mIHN0
YWxlIE1QTFMgb3IgSUdQIHJvdXRpbmcgaW5mb3JtYXRpb24gY291bGQgY2F1c2UgYSBQTVMgbW9u
aXRvcmluZw0KPiBwYWNrZXQgdG8gbGVhdmUgdGhlIGRvbWFpbiB3aGVyZSBpdCBvcmlnaW5hdGVk
LiBQTVMgbW9uaXRvcmluZyBwYWNrZXRzIHNob3VsZA0KPiBub3QgYmUgc2VudCB1c2luZyBzdGFs
ZSBNUExTIG9yIElHUCByb3V0aW5nIGluZm9ybWF0aW9uLg0KPiANCj4gQXMgaXQgaXMgbmVjZXNz
YXJ5IHRvIGtub3cgdGhhdCB0aGUgaW5mb3JtYXRpb24gaXMgc3RhbGUgaXMgb3JkZXIgdG8gZm9s
bG93IHRoZQ0KPiBpbnN0cnVjdGlvbiwgYXMgaXMgdGhlIGNhc2Ugd2l0aCBmb3IgZXhhbXBsZSBj
b252ZXJnZW5jZSBldmVudHMgdGhhdCBtYXkgYmUNCj4gb25nb2luZyBhdCB0aGUgdGltZSBvZiBk
aWFnbm9zdGljIG1lYXN1cmVtZW50Lg0KPiANCg0KDQpBZ3JlZWQuIFdlIGFkZGVkIHRoaXMgdGV4
dC4gTm90ZSBwbGVhc2UgdGhhdCBhZGRpdGlvbmFsbHksIHdlIHNpZ25pZmljYW50bHkgcmV2YW1w
ZWQgdGhlIFNlY3VyaXR5IENvbnNpZGVyYXRpb25zIHNlY3Rpb24uDQoNClRoYW5rcyENCg0KPiAN
Cg0K4oCUDQpDYXJsb3MgUGlnbmF0YXJvLCBjYXJsb3NAY2lzY28uY29tDQoNCuKAnFNvbWV0aW1l
cyBJIHVzZSBiaWcgd29yZHMgdGhhdCBJIGRvIG5vdCBmdWxseSB1bmRlcnN0YW5kLCB0byBtYWtl
IG15c2VsZiBzb3VuZCBtb3JlIHBob3Rvc3ludGhlc2lzLiINCg0K


From nobody Sat Jul  1 14:07:22 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 144BC124D6C; Sat,  1 Jul 2017 14:07:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, SPF_HELO_PASS=-0.001, 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=joelhalpern.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 eujk0Bfw9d9V; Sat,  1 Jul 2017 14:07:03 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 5126A127735; Sat,  1 Jul 2017 14:07:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 37F78403E92; Sat,  1 Jul 2017 14:07:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1498943223; bh=tBtXPxa3iFZjZJnN7u20NQFekBiq7+tQIy/QTv72YYY=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=N7xYccuFND3s7jkyMhEXmrtM7leqFofy83jtl6JYUpFLO8ePUCy20LK2eL+TonW7d 5J7wB+x6JTtWOm/u4dkAxQVEme/X25wM2J3nAGq3i/1T98FM4tt/G0zo4xyKc/ikHm hwTXwy7ZcPXIrTsCvq8nZFMOfxBYU3oMfQmnCZpw=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (unknown [50.225.209.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 3F6661C0049; Sat,  1 Jul 2017 14:07:02 -0700 (PDT)
Subject: Re: Rtgdir last call review of draft-ietf-spring-oam-usecase-06
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Cc: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "spring@ietf.org" <spring@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-spring-oam-usecase.all@ietf.org" <draft-ietf-spring-oam-usecase.all@ietf.org>
References: <149813817013.30481.17524594111387704082@ietfa.amsl.com> <6B35D999-331B-4DB3-A9F1-C2BEF4EC0944@cisco.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <d8fbfd80-f30a-5d60-5dae-f140e00f152a@joelhalpern.com>
Date: Sat, 1 Jul 2017 17:07:01 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <6B35D999-331B-4DB3-A9F1-C2BEF4EC0944@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3PtHgUIoTzmHAUWGBXK0PyEH_Ag>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Jul 2017 21:07:05 -0000

Almost.
I believe the earlier email had agreed to replace pre-SR with non-SR. 
There are two uses of pre-SR stil in the document.

Otherwise, yes, these address my comments.

Yours,
Joel

On 7/1/17 4:52 PM, Carlos Pignataro (cpignata) wrote:
> Thanks for your review, Joel!
> 
> Revision -07, just submitted, should address all your concerns and 
> suggestions. Please let us know otherwise.
> 
> Thanks,
> 
> — Carlos.
> 
>> On Jun 22, 2017, at 9:29 AM, Joel Halpern <jmh@joelhalpern.com 
>> <mailto:jmh@joelhalpern.com>> wrote:
>>
>> Reviewer: Joel Halpern
>> Review result: Has Nits
>>
>> This is a rtg-dir requested review.
>>
>> Summary: Ready for publication as an Informational RFC with some minor 
>> items
>> that should be considered.
>>
>> Major: N/A
>>
>> Minor:
>>    The introduction treats having a single centralized monitoring 
>> system as an
>>    unalloyed positive.  To set context properly, it would seem more
>>    appropriate to note that many operators find such central systems 
>> useful,
>>    and the approach described here enables that when desired.
>>
>>    The reference in the introduction to IGP topology discovery is very
>>    confusing. "Adding MPLS topology awareness to an IGP speaking 
>> device hence
>>    enables a simple and scalable data plane based monitoring 
>> mechanism."  As
>>    noted later in the document, link-state IGPs provide topology 
>> awareness.
>>    So what is this part of the introduction trying to say? 
>>  (Side-note, not
>>    all IGPs are link state, although the applicability of Babel or RIP 
>> to MPLS
>>    Segment Routing is clearly outside the scope of this document.)
>>
>>    In section 5.1 in discussing path trace the reference is to RFC 
>> 4379 which
>>    is a clear source for path trace.  However, the text refers to "tree
>>    trace".  While that may have become a common phrase for the usage, 
>> it is
>>    not used in RFC 4379.  The term should either be explain, include a
>>    suitable reference, or not be used.
>>
>>   In section 5.3 on fault isolation, the text notes that the only 
>> difference
>>   between the test which succeeds and that which fails is the 
>> difference the
>>   the adjacency SID.  The text then goes on to say "Assuming the 
>> second probe
>>   has been routed correctly, the fault must have been occurring in R2 
>> which
>>   didn't forward the packet to the interface identified by its 
>> Adjacency SID
>>   663."  That does not follow.  If the link as failed in an undetected 
>> fashion
>>   (either in one direction or both), R2 would be functioning fine and the
>>   symptom would be the same.  Remotely detecting the difference between R2
>>   failing to forward and the link not working seems a much harder task.
>>
>>    The claim that the PMS can / should (intent is ambiguous) notify 
>> the router
>>    when it detects a path failure raises a number of issues.   It is 
>> not at
>>    all clear what the router would do with the notification.  (e.g. If it
>>    removed the link from service, then future monitoring would not be 
>> able to
>>    detect that the link was working.)  Either this needs to become a
>>    significantly larger section, or (more likely) the text needs to be 
>> removed.
>>
>> Editorial:
>>    Chapter 7 is titled dealing with non-SR environments.  Which makes 
>> sense.
>>    The text then switches to using "pre-SR" instead of "non-SR".  I would
>>    recommend that all uses of "pre-SR" be changed to "non-SR".
>>
> 
> —
> Carlos Pignataro, carlos@cisco.com <mailto:carlos@cisco.com>
> 
> /“Sometimes I use big words that I do not fully understand, to make 
> myself sound more photosynthesis."/
> 


From nobody Sat Jul  1 19:43:13 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1F4F129AF1 for <ietf@ietfa.amsl.com>; Sat,  1 Jul 2017 19:43:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 bW5iOoy-n2SP for <ietf@ietfa.amsl.com>; Sat,  1 Jul 2017 19:43:09 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5565012702E for <ietf@ietf.org>; Sat,  1 Jul 2017 19:43:09 -0700 (PDT)
Received: (qmail 89632 invoked from network); 2 Jul 2017 02:43:08 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 2 Jul 2017 02:43:08 -0000
Date: 2 Jul 2017 02:42:46 -0000
Message-ID: <20170702024246.55844.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: 
In-Reply-To: <CAF4+nEE5+nF_biteqsbEThU8tSeN7SwuCZLun3MHuJYVGvn0rQ@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ddlD0zp3iisAZpEYx55ucp8Y4IM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Jul 2017 02:43:11 -0000

In article <CAF4+nEE5+nF_biteqsbEThU8tSeN7SwuCZLun3MHuJYVGvn0rQ@mail.gmail.com> you write:
>> a three letter code that already exists as a gTLD. Afaik there are no
>> clashes right now, but past results are not a guarantee for the future.
>
>COM is the three letter code for the Comoros Islands. I believe it is
>also used by a few entities as their TLD :-)

That is the only name in the alpha-3 3166 list that's delegated as a
TLD, but I will admit that it could be problematic.  Fun fact: there
are enough names in .com to give 200 names to every resident of the
Comoros.

I have seen the arguments about reserving alpha-3 3166 codes and have
never seen any plausible explanation of what problem it is supposed to
solve.  Every place with a three letter code has a two letter code,
and the argument that the three letter codes are somehow more mnemonic
or better known is ridiculous.  (Quick, what are BES, COD, and TLS?)

R's,
John


From nobody Sun Jul  2 12:11:36 2017
Return-Path: <cpignata@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FEF3124BE8; Sun,  2 Jul 2017 12:11:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 SS7-utQEhPxL; Sun,  2 Jul 2017 12:11:16 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3937127599; Sun,  2 Jul 2017 12:11:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16034; q=dns/txt; s=iport; t=1499022676; x=1500232276; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=xOhnQoX6eRJoo3rSyRPgihqvUgxksSfN0AXJEQENux0=; b=ey0wMdnkogUHEJkEaZJqsxekTap5V76FrkFkG/yAWT9X0S9qxWo/x2Bl T4DGxXW6hgZu/f5Z4r4vp44rIS8hbZjEtT2J964Mh2MTg37OfDzgzLovl VjFUHnWfYAS1fZbsmdfu1+ZnSnVuKincNjN4IS1bRXoGCxPmrAReoiZSI 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A5AQCbRFlZ/5RdJa1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1mBcQeNfpFGkHSFK4IRhhwCGoJ/PxgBAgEBAQEBAQFrKIUZBiN?= =?us-ascii?q?WEAIBCD8DAgICMBQRAgQOBYlLZLFUgiaLSAEBAQEBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?R2DJ4NMgWErC4JuhDsSAYMvMIIxBYlPiFaFA4dXApN/ggyFSopHlS8BHzh/C3U?= =?us-ascii?q?VWwGFAByBZnaGUIEjgQ0BAQE?=
X-IronPort-AV: E=Sophos;i="5.40,299,1496102400";  d="scan'208,217";a="448511865"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Jul 2017 19:11:15 +0000
Received: from XCH-RTP-016.cisco.com (xch-rtp-016.cisco.com [64.101.220.156]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id v62JBEkp008581 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 2 Jul 2017 19:11:14 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-016.cisco.com (64.101.220.156) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sun, 2 Jul 2017 15:11:13 -0400
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1210.000; Sun, 2 Jul 2017 15:11:13 -0400
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
CC: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "spring@ietf.org" <spring@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-spring-oam-usecase.all@ietf.org" <draft-ietf-spring-oam-usecase.all@ietf.org>
Subject: Re: Rtgdir last call review of draft-ietf-spring-oam-usecase-06
Thread-Topic: Rtgdir last call review of draft-ietf-spring-oam-usecase-06
Thread-Index: AQHS61uWxVbWnw4SLk2wgKSt4LG4WKI/xD6AgAAED4CAAXH7gA==
Date: Sun, 2 Jul 2017 19:11:13 +0000
Message-ID: <6B1007C6-4AE8-4244-89D6-392922984AE7@cisco.com>
References: <149813817013.30481.17524594111387704082@ietfa.amsl.com> <6B35D999-331B-4DB3-A9F1-C2BEF4EC0944@cisco.com> <d8fbfd80-f30a-5d60-5dae-f140e00f152a@joelhalpern.com>
In-Reply-To: <d8fbfd80-f30a-5d60-5dae-f140e00f152a@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.116.131]
Content-Type: multipart/alternative; boundary="_000_6B1007C64AE8424489D6392922984AE7ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/p4_3pyFQnMykqw1p2wtGSt3Xffk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Jul 2017 19:11:18 -0000

--_000_6B1007C64AE8424489D6392922984AE7ciscocom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

VGhhbmsgeW91LCBKb2VsLCB3ZWxsIHNwb3R0ZWQuIEFwb2xvZ2llcyB3ZSBjaGFuZ2VkIGFsbCBp
bnN0YW5jZXMgZXhjZXB0IGZvciB0d28uIFRoaXMgaXMgbm93IGZpeGVkIGluIC0wOC4NCg0KVGhh
bmtzIQ0KDQrigJQgQ2FybG9zLg0KDQpPbiBKdWwgMSwgMjAxNywgYXQgNTowNyBQTSwgSm9lbCBN
LiBIYWxwZXJuIDxqbWhAam9lbGhhbHBlcm4uY29tPG1haWx0bzpqbWhAam9lbGhhbHBlcm4uY29t
Pj4gd3JvdGU6DQoNCkFsbW9zdC4NCkkgYmVsaWV2ZSB0aGUgZWFybGllciBlbWFpbCBoYWQgYWdy
ZWVkIHRvIHJlcGxhY2UgcHJlLVNSIHdpdGggbm9uLVNSLiBUaGVyZSBhcmUgdHdvIHVzZXMgb2Yg
cHJlLVNSIHN0aWwgaW4gdGhlIGRvY3VtZW50Lg0KDQpPdGhlcndpc2UsIHllcywgdGhlc2UgYWRk
cmVzcyBteSBjb21tZW50cy4NCg0KWW91cnMsDQpKb2VsDQoNCk9uIDcvMS8xNyA0OjUyIFBNLCBD
YXJsb3MgUGlnbmF0YXJvIChjcGlnbmF0YSkgd3JvdGU6DQpUaGFua3MgZm9yIHlvdXIgcmV2aWV3
LCBKb2VsIQ0KUmV2aXNpb24gLTA3LCBqdXN0IHN1Ym1pdHRlZCwgc2hvdWxkIGFkZHJlc3MgYWxs
IHlvdXIgY29uY2VybnMgYW5kIHN1Z2dlc3Rpb25zLiBQbGVhc2UgbGV0IHVzIGtub3cgb3RoZXJ3
aXNlLg0KVGhhbmtzLA0K4oCUIENhcmxvcy4NCk9uIEp1biAyMiwgMjAxNywgYXQgOToyOSBBTSwg
Sm9lbCBIYWxwZXJuIDxqbWhAam9lbGhhbHBlcm4uY29tPG1haWx0bzpqbWhAam9lbGhhbHBlcm4u
Y29tPiA8bWFpbHRvOmptaEBqb2VsaGFscGVybi5jb20+PiB3cm90ZToNCg0KUmV2aWV3ZXI6IEpv
ZWwgSGFscGVybg0KUmV2aWV3IHJlc3VsdDogSGFzIE5pdHMNCg0KVGhpcyBpcyBhIHJ0Zy1kaXIg
cmVxdWVzdGVkIHJldmlldy4NCg0KU3VtbWFyeTogUmVhZHkgZm9yIHB1YmxpY2F0aW9uIGFzIGFu
IEluZm9ybWF0aW9uYWwgUkZDIHdpdGggc29tZSBtaW5vciBpdGVtcw0KdGhhdCBzaG91bGQgYmUg
Y29uc2lkZXJlZC4NCg0KTWFqb3I6IE4vQQ0KDQpNaW5vcjoNCiAgVGhlIGludHJvZHVjdGlvbiB0
cmVhdHMgaGF2aW5nIGEgc2luZ2xlIGNlbnRyYWxpemVkIG1vbml0b3Jpbmcgc3lzdGVtIGFzIGFu
DQogIHVuYWxsb3llZCBwb3NpdGl2ZS4gIFRvIHNldCBjb250ZXh0IHByb3Blcmx5LCBpdCB3b3Vs
ZCBzZWVtIG1vcmUNCiAgYXBwcm9wcmlhdGUgdG8gbm90ZSB0aGF0IG1hbnkgb3BlcmF0b3JzIGZp
bmQgc3VjaCBjZW50cmFsIHN5c3RlbXMgdXNlZnVsLA0KICBhbmQgdGhlIGFwcHJvYWNoIGRlc2Ny
aWJlZCBoZXJlIGVuYWJsZXMgdGhhdCB3aGVuIGRlc2lyZWQuDQoNCiAgVGhlIHJlZmVyZW5jZSBp
biB0aGUgaW50cm9kdWN0aW9uIHRvIElHUCB0b3BvbG9neSBkaXNjb3ZlcnkgaXMgdmVyeQ0KICBj
b25mdXNpbmcuICJBZGRpbmcgTVBMUyB0b3BvbG9neSBhd2FyZW5lc3MgdG8gYW4gSUdQIHNwZWFr
aW5nIGRldmljZSBoZW5jZQ0KICBlbmFibGVzIGEgc2ltcGxlIGFuZCBzY2FsYWJsZSBkYXRhIHBs
YW5lIGJhc2VkIG1vbml0b3JpbmcgbWVjaGFuaXNtLiIgIEFzDQogIG5vdGVkIGxhdGVyIGluIHRo
ZSBkb2N1bWVudCwgbGluay1zdGF0ZSBJR1BzIHByb3ZpZGUgdG9wb2xvZ3kgYXdhcmVuZXNzLg0K
ICBTbyB3aGF0IGlzIHRoaXMgcGFydCBvZiB0aGUgaW50cm9kdWN0aW9uIHRyeWluZyB0byBzYXk/
ICAoU2lkZS1ub3RlLCBub3QNCiAgYWxsIElHUHMgYXJlIGxpbmsgc3RhdGUsIGFsdGhvdWdoIHRo
ZSBhcHBsaWNhYmlsaXR5IG9mIEJhYmVsIG9yIFJJUCB0byBNUExTDQogIFNlZ21lbnQgUm91dGlu
ZyBpcyBjbGVhcmx5IG91dHNpZGUgdGhlIHNjb3BlIG9mIHRoaXMgZG9jdW1lbnQuKQ0KDQogIElu
IHNlY3Rpb24gNS4xIGluIGRpc2N1c3NpbmcgcGF0aCB0cmFjZSB0aGUgcmVmZXJlbmNlIGlzIHRv
IFJGQyA0Mzc5IHdoaWNoDQogIGlzIGEgY2xlYXIgc291cmNlIGZvciBwYXRoIHRyYWNlLiAgSG93
ZXZlciwgdGhlIHRleHQgcmVmZXJzIHRvICJ0cmVlDQogIHRyYWNlIi4gIFdoaWxlIHRoYXQgbWF5
IGhhdmUgYmVjb21lIGEgY29tbW9uIHBocmFzZSBmb3IgdGhlIHVzYWdlLCBpdCBpcw0KICBub3Qg
dXNlZCBpbiBSRkMgNDM3OS4gIFRoZSB0ZXJtIHNob3VsZCBlaXRoZXIgYmUgZXhwbGFpbiwgaW5j
bHVkZSBhDQogIHN1aXRhYmxlIHJlZmVyZW5jZSwgb3Igbm90IGJlIHVzZWQuDQoNCiBJbiBzZWN0
aW9uIDUuMyBvbiBmYXVsdCBpc29sYXRpb24sIHRoZSB0ZXh0IG5vdGVzIHRoYXQgdGhlIG9ubHkg
ZGlmZmVyZW5jZQ0KIGJldHdlZW4gdGhlIHRlc3Qgd2hpY2ggc3VjY2VlZHMgYW5kIHRoYXQgd2hp
Y2ggZmFpbHMgaXMgdGhlIGRpZmZlcmVuY2UgdGhlDQogdGhlIGFkamFjZW5jeSBTSUQuICBUaGUg
dGV4dCB0aGVuIGdvZXMgb24gdG8gc2F5ICJBc3N1bWluZyB0aGUgc2Vjb25kIHByb2JlDQogaGFz
IGJlZW4gcm91dGVkIGNvcnJlY3RseSwgdGhlIGZhdWx0IG11c3QgaGF2ZSBiZWVuIG9jY3Vycmlu
ZyBpbiBSMiB3aGljaA0KIGRpZG4ndCBmb3J3YXJkIHRoZSBwYWNrZXQgdG8gdGhlIGludGVyZmFj
ZSBpZGVudGlmaWVkIGJ5IGl0cyBBZGphY2VuY3kgU0lEDQogNjYzLiIgIFRoYXQgZG9lcyBub3Qg
Zm9sbG93LiAgSWYgdGhlIGxpbmsgYXMgZmFpbGVkIGluIGFuIHVuZGV0ZWN0ZWQgZmFzaGlvbg0K
IChlaXRoZXIgaW4gb25lIGRpcmVjdGlvbiBvciBib3RoKSwgUjIgd291bGQgYmUgZnVuY3Rpb25p
bmcgZmluZSBhbmQgdGhlDQogc3ltcHRvbSB3b3VsZCBiZSB0aGUgc2FtZS4gIFJlbW90ZWx5IGRl
dGVjdGluZyB0aGUgZGlmZmVyZW5jZSBiZXR3ZWVuIFIyDQogZmFpbGluZyB0byBmb3J3YXJkIGFu
ZCB0aGUgbGluayBub3Qgd29ya2luZyBzZWVtcyBhIG11Y2ggaGFyZGVyIHRhc2suDQoNCiAgVGhl
IGNsYWltIHRoYXQgdGhlIFBNUyBjYW4gLyBzaG91bGQgKGludGVudCBpcyBhbWJpZ3VvdXMpIG5v
dGlmeSB0aGUgcm91dGVyDQogIHdoZW4gaXQgZGV0ZWN0cyBhIHBhdGggZmFpbHVyZSByYWlzZXMg
YSBudW1iZXIgb2YgaXNzdWVzLiAgIEl0IGlzIG5vdCBhdA0KICBhbGwgY2xlYXIgd2hhdCB0aGUg
cm91dGVyIHdvdWxkIGRvIHdpdGggdGhlIG5vdGlmaWNhdGlvbi4gIChlLmcuIElmIGl0DQogIHJl
bW92ZWQgdGhlIGxpbmsgZnJvbSBzZXJ2aWNlLCB0aGVuIGZ1dHVyZSBtb25pdG9yaW5nIHdvdWxk
IG5vdCBiZSBhYmxlIHRvDQogIGRldGVjdCB0aGF0IHRoZSBsaW5rIHdhcyB3b3JraW5nLikgIEVp
dGhlciB0aGlzIG5lZWRzIHRvIGJlY29tZSBhDQogIHNpZ25pZmljYW50bHkgbGFyZ2VyIHNlY3Rp
b24sIG9yIChtb3JlIGxpa2VseSkgdGhlIHRleHQgbmVlZHMgdG8gYmUgcmVtb3ZlZC4NCg0KRWRp
dG9yaWFsOg0KICBDaGFwdGVyIDcgaXMgdGl0bGVkIGRlYWxpbmcgd2l0aCBub24tU1IgZW52aXJv
bm1lbnRzLiAgV2hpY2ggbWFrZXMgc2Vuc2UuDQogIFRoZSB0ZXh0IHRoZW4gc3dpdGNoZXMgdG8g
dXNpbmcgInByZS1TUiIgaW5zdGVhZCBvZiAibm9uLVNSIi4gIEkgd291bGQNCiAgcmVjb21tZW5k
IHRoYXQgYWxsIHVzZXMgb2YgInByZS1TUiIgYmUgY2hhbmdlZCB0byAibm9uLVNSIi4NCg0K4oCU
DQpDYXJsb3MgUGlnbmF0YXJvLCBjYXJsb3NAY2lzY28uY29tPG1haWx0bzpjYXJsb3NAY2lzY28u
Y29tPiA8bWFpbHRvOmNhcmxvc0BjaXNjby5jb20+DQov4oCcU29tZXRpbWVzIEkgdXNlIGJpZyB3
b3JkcyB0aGF0IEkgZG8gbm90IGZ1bGx5IHVuZGVyc3RhbmQsIHRvIG1ha2UgbXlzZWxmIHNvdW5k
IG1vcmUgcGhvdG9zeW50aGVzaXMuIi8NCg0K4oCUDQpDYXJsb3MgUGlnbmF0YXJvLCBjYXJsb3NA
Y2lzY28uY29tPG1haWx0bzpjYXJsb3NAY2lzY28uY29tPg0KDQrigJxTb21ldGltZXMgSSB1c2Ug
YmlnIHdvcmRzIHRoYXQgSSBkbyBub3QgZnVsbHkgdW5kZXJzdGFuZCwgdG8gbWFrZSBteXNlbGYg
c291bmQgbW9yZSBwaG90b3N5bnRoZXNpcy4iDQoNCg==

--_000_6B1007C64AE8424489D6392922984AE7ciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <362EA5C4B14AD84FB8EF340BAAB1854D@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KVGhhbmsgeW91LCBKb2VsLCB3ZWxs
IHNwb3R0ZWQuIEFwb2xvZ2llcyB3ZSBjaGFuZ2VkIGFsbCBpbnN0YW5jZXMgZXhjZXB0IGZvciB0
d28uIFRoaXMgaXMgbm93IGZpeGVkIGluIC0wOC4NCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIi
Pg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPlRoYW5rcyE8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+PGJy
IGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPuKAlCBDYXJsb3MuPC9kaXY+DQo8ZGl2
IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjxkaXY+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBj
bGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+T24gSnVsIDEsIDIwMTcsIGF0IDU6MDcgUE0sIEpvZWwg
TS4gSGFscGVybiAmbHQ7PGEgaHJlZj0ibWFpbHRvOmptaEBqb2VsaGFscGVybi5jb20iIGNsYXNz
PSIiPmptaEBqb2VsaGFscGVybi5jb208L2E+Jmd0OyB3cm90ZTo8L2Rpdj4NCjxiciBjbGFzcz0i
QXBwbGUtaW50ZXJjaGFuZ2UtbmV3bGluZSI+DQo8ZGl2IGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0i
Ij5BbG1vc3QuPGJyIGNsYXNzPSIiPg0KSSBiZWxpZXZlIHRoZSBlYXJsaWVyIGVtYWlsIGhhZCBh
Z3JlZWQgdG8gcmVwbGFjZSBwcmUtU1Igd2l0aCBub24tU1IuIFRoZXJlIGFyZSB0d28gdXNlcyBv
ZiBwcmUtU1Igc3RpbCBpbiB0aGUgZG9jdW1lbnQuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIi
Pg0KT3RoZXJ3aXNlLCB5ZXMsIHRoZXNlIGFkZHJlc3MgbXkgY29tbWVudHMuPGJyIGNsYXNzPSIi
Pg0KPGJyIGNsYXNzPSIiPg0KWW91cnMsPGJyIGNsYXNzPSIiPg0KSm9lbDxiciBjbGFzcz0iIj4N
CjxiciBjbGFzcz0iIj4NCk9uIDcvMS8xNyA0OjUyIFBNLCBDYXJsb3MgUGlnbmF0YXJvIChjcGln
bmF0YSkgd3JvdGU6PGJyIGNsYXNzPSIiPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9
IiI+VGhhbmtzIGZvciB5b3VyIHJldmlldywgSm9lbCE8YnIgY2xhc3M9IiI+DQpSZXZpc2lvbiAt
MDcsIGp1c3Qgc3VibWl0dGVkLCBzaG91bGQgYWRkcmVzcyBhbGwgeW91ciBjb25jZXJucyBhbmQg
c3VnZ2VzdGlvbnMuIFBsZWFzZSBsZXQgdXMga25vdyBvdGhlcndpc2UuPGJyIGNsYXNzPSIiPg0K
VGhhbmtzLDxiciBjbGFzcz0iIj4NCuKAlCBDYXJsb3MuPGJyIGNsYXNzPSIiPg0KPGJsb2NrcXVv
dGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+T24gSnVuIDIyLCAyMDE3LCBhdCA5OjI5IEFNLCBKb2Vs
IEhhbHBlcm4gJmx0OzxhIGhyZWY9Im1haWx0bzpqbWhAam9lbGhhbHBlcm4uY29tIiBjbGFzcz0i
Ij5qbWhAam9lbGhhbHBlcm4uY29tPC9hPiAmbHQ7PGEgaHJlZj0ibWFpbHRvOmptaEBqb2VsaGFs
cGVybi5jb20iIGNsYXNzPSIiPm1haWx0bzpqbWhAam9lbGhhbHBlcm4uY29tPC9hPiZndDsmZ3Q7
IHdyb3RlOjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NClJldmlld2VyOiBKb2VsIEhhbHBl
cm48YnIgY2xhc3M9IiI+DQpSZXZpZXcgcmVzdWx0OiBIYXMgTml0czxiciBjbGFzcz0iIj4NCjxi
ciBjbGFzcz0iIj4NClRoaXMgaXMgYSBydGctZGlyIHJlcXVlc3RlZCByZXZpZXcuPGJyIGNsYXNz
PSIiPg0KPGJyIGNsYXNzPSIiPg0KU3VtbWFyeTogUmVhZHkgZm9yIHB1YmxpY2F0aW9uIGFzIGFu
IEluZm9ybWF0aW9uYWwgUkZDIHdpdGggc29tZSBtaW5vciBpdGVtczxiciBjbGFzcz0iIj4NCnRo
YXQgc2hvdWxkIGJlIGNvbnNpZGVyZWQuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KTWFq
b3I6IE4vQTxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCk1pbm9yOjxiciBjbGFzcz0iIj4N
CiZuYnNwOyZuYnNwO1RoZSBpbnRyb2R1Y3Rpb24gdHJlYXRzIGhhdmluZyBhIHNpbmdsZSBjZW50
cmFsaXplZCBtb25pdG9yaW5nIHN5c3RlbSBhcyBhbjxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNw
O3VuYWxsb3llZCBwb3NpdGl2ZS4gJm5ic3A7VG8gc2V0IGNvbnRleHQgcHJvcGVybHksIGl0IHdv
dWxkIHNlZW0gbW9yZTxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO2FwcHJvcHJpYXRlIHRvIG5v
dGUgdGhhdCBtYW55IG9wZXJhdG9ycyBmaW5kIHN1Y2ggY2VudHJhbCBzeXN0ZW1zIHVzZWZ1bCw8
YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDthbmQgdGhlIGFwcHJvYWNoIGRlc2NyaWJlZCBoZXJl
IGVuYWJsZXMgdGhhdCB3aGVuIGRlc2lyZWQuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0K
Jm5ic3A7Jm5ic3A7VGhlIHJlZmVyZW5jZSBpbiB0aGUgaW50cm9kdWN0aW9uIHRvIElHUCB0b3Bv
bG9neSBkaXNjb3ZlcnkgaXMgdmVyeTxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO2NvbmZ1c2lu
Zy4gJnF1b3Q7QWRkaW5nIE1QTFMgdG9wb2xvZ3kgYXdhcmVuZXNzIHRvIGFuIElHUCBzcGVha2lu
ZyBkZXZpY2UgaGVuY2U8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDtlbmFibGVzIGEgc2ltcGxl
IGFuZCBzY2FsYWJsZSBkYXRhIHBsYW5lIGJhc2VkIG1vbml0b3JpbmcgbWVjaGFuaXNtLiZxdW90
OyAmbmJzcDtBczxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO25vdGVkIGxhdGVyIGluIHRoZSBk
b2N1bWVudCwgbGluay1zdGF0ZSBJR1BzIHByb3ZpZGUgdG9wb2xvZ3kgYXdhcmVuZXNzLjxiciBj
bGFzcz0iIj4NCiZuYnNwOyZuYnNwO1NvIHdoYXQgaXMgdGhpcyBwYXJ0IG9mIHRoZSBpbnRyb2R1
Y3Rpb24gdHJ5aW5nIHRvIHNheT8gJm5ic3A7KFNpZGUtbm90ZSwgbm90PGJyIGNsYXNzPSIiPg0K
Jm5ic3A7Jm5ic3A7YWxsIElHUHMgYXJlIGxpbmsgc3RhdGUsIGFsdGhvdWdoIHRoZSBhcHBsaWNh
YmlsaXR5IG9mIEJhYmVsIG9yIFJJUCB0byBNUExTPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7
U2VnbWVudCBSb3V0aW5nIGlzIGNsZWFybHkgb3V0c2lkZSB0aGUgc2NvcGUgb2YgdGhpcyBkb2N1
bWVudC4pPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7SW4gc2VjdGlv
biA1LjEgaW4gZGlzY3Vzc2luZyBwYXRoIHRyYWNlIHRoZSByZWZlcmVuY2UgaXMgdG8gUkZDIDQz
Nzkgd2hpY2g8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDtpcyBhIGNsZWFyIHNvdXJjZSBmb3Ig
cGF0aCB0cmFjZS4gJm5ic3A7SG93ZXZlciwgdGhlIHRleHQgcmVmZXJzIHRvICZxdW90O3RyZWU8
YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDt0cmFjZSZxdW90Oy4gJm5ic3A7V2hpbGUgdGhhdCBt
YXkgaGF2ZSBiZWNvbWUgYSBjb21tb24gcGhyYXNlIGZvciB0aGUgdXNhZ2UsIGl0IGlzPGJyIGNs
YXNzPSIiPg0KJm5ic3A7Jm5ic3A7bm90IHVzZWQgaW4gUkZDIDQzNzkuICZuYnNwO1RoZSB0ZXJt
IHNob3VsZCBlaXRoZXIgYmUgZXhwbGFpbiwgaW5jbHVkZSBhPGJyIGNsYXNzPSIiPg0KJm5ic3A7
Jm5ic3A7c3VpdGFibGUgcmVmZXJlbmNlLCBvciBub3QgYmUgdXNlZC48YnIgY2xhc3M9IiI+DQo8
YnIgY2xhc3M9IiI+DQombmJzcDtJbiBzZWN0aW9uIDUuMyBvbiBmYXVsdCBpc29sYXRpb24sIHRo
ZSB0ZXh0IG5vdGVzIHRoYXQgdGhlIG9ubHkgZGlmZmVyZW5jZTxiciBjbGFzcz0iIj4NCiZuYnNw
O2JldHdlZW4gdGhlIHRlc3Qgd2hpY2ggc3VjY2VlZHMgYW5kIHRoYXQgd2hpY2ggZmFpbHMgaXMg
dGhlIGRpZmZlcmVuY2UgdGhlPGJyIGNsYXNzPSIiPg0KJm5ic3A7dGhlIGFkamFjZW5jeSBTSUQu
ICZuYnNwO1RoZSB0ZXh0IHRoZW4gZ29lcyBvbiB0byBzYXkgJnF1b3Q7QXNzdW1pbmcgdGhlIHNl
Y29uZCBwcm9iZTxiciBjbGFzcz0iIj4NCiZuYnNwO2hhcyBiZWVuIHJvdXRlZCBjb3JyZWN0bHks
IHRoZSBmYXVsdCBtdXN0IGhhdmUgYmVlbiBvY2N1cnJpbmcgaW4gUjIgd2hpY2g8YnIgY2xhc3M9
IiI+DQombmJzcDtkaWRuJ3QgZm9yd2FyZCB0aGUgcGFja2V0IHRvIHRoZSBpbnRlcmZhY2UgaWRl
bnRpZmllZCBieSBpdHMgQWRqYWNlbmN5IFNJRDxiciBjbGFzcz0iIj4NCiZuYnNwOzY2My4mcXVv
dDsgJm5ic3A7VGhhdCBkb2VzIG5vdCBmb2xsb3cuICZuYnNwO0lmIHRoZSBsaW5rIGFzIGZhaWxl
ZCBpbiBhbiB1bmRldGVjdGVkIGZhc2hpb248YnIgY2xhc3M9IiI+DQombmJzcDsoZWl0aGVyIGlu
IG9uZSBkaXJlY3Rpb24gb3IgYm90aCksIFIyIHdvdWxkIGJlIGZ1bmN0aW9uaW5nIGZpbmUgYW5k
IHRoZTxiciBjbGFzcz0iIj4NCiZuYnNwO3N5bXB0b20gd291bGQgYmUgdGhlIHNhbWUuICZuYnNw
O1JlbW90ZWx5IGRldGVjdGluZyB0aGUgZGlmZmVyZW5jZSBiZXR3ZWVuIFIyPGJyIGNsYXNzPSIi
Pg0KJm5ic3A7ZmFpbGluZyB0byBmb3J3YXJkIGFuZCB0aGUgbGluayBub3Qgd29ya2luZyBzZWVt
cyBhIG11Y2ggaGFyZGVyIHRhc2suPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KJm5ic3A7
Jm5ic3A7VGhlIGNsYWltIHRoYXQgdGhlIFBNUyBjYW4gLyBzaG91bGQgKGludGVudCBpcyBhbWJp
Z3VvdXMpIG5vdGlmeSB0aGUgcm91dGVyPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7d2hlbiBp
dCBkZXRlY3RzIGEgcGF0aCBmYWlsdXJlIHJhaXNlcyBhIG51bWJlciBvZiBpc3N1ZXMuICZuYnNw
OyZuYnNwO0l0IGlzIG5vdCBhdDxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO2FsbCBjbGVhciB3
aGF0IHRoZSByb3V0ZXIgd291bGQgZG8gd2l0aCB0aGUgbm90aWZpY2F0aW9uLiAmbmJzcDsoZS5n
LiBJZiBpdDxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO3JlbW92ZWQgdGhlIGxpbmsgZnJvbSBz
ZXJ2aWNlLCB0aGVuIGZ1dHVyZSBtb25pdG9yaW5nIHdvdWxkIG5vdCBiZSBhYmxlIHRvPGJyIGNs
YXNzPSIiPg0KJm5ic3A7Jm5ic3A7ZGV0ZWN0IHRoYXQgdGhlIGxpbmsgd2FzIHdvcmtpbmcuKSAm
bmJzcDtFaXRoZXIgdGhpcyBuZWVkcyB0byBiZWNvbWUgYTxiciBjbGFzcz0iIj4NCiZuYnNwOyZu
YnNwO3NpZ25pZmljYW50bHkgbGFyZ2VyIHNlY3Rpb24sIG9yIChtb3JlIGxpa2VseSkgdGhlIHRl
eHQgbmVlZHMgdG8gYmUgcmVtb3ZlZC48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpFZGl0
b3JpYWw6PGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Q2hhcHRlciA3IGlzIHRpdGxlZCBkZWFs
aW5nIHdpdGggbm9uLVNSIGVudmlyb25tZW50cy4gJm5ic3A7V2hpY2ggbWFrZXMgc2Vuc2UuPGJy
IGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7VGhlIHRleHQgdGhlbiBzd2l0Y2hlcyB0byB1c2luZyAm
cXVvdDtwcmUtU1ImcXVvdDsgaW5zdGVhZCBvZiAmcXVvdDtub24tU1ImcXVvdDsuICZuYnNwO0kg
d291bGQ8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDtyZWNvbW1lbmQgdGhhdCBhbGwgdXNlcyBv
ZiAmcXVvdDtwcmUtU1ImcXVvdDsgYmUgY2hhbmdlZCB0byAmcXVvdDtub24tU1ImcXVvdDsuPGJy
IGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KPC9ibG9ja3F1b3RlPg0K4oCUPGJyIGNsYXNzPSIi
Pg0KQ2FybG9zIFBpZ25hdGFybywgPGEgaHJlZj0ibWFpbHRvOmNhcmxvc0BjaXNjby5jb20iIGNs
YXNzPSIiPmNhcmxvc0BjaXNjby5jb208L2E+ICZsdDs8YSBocmVmPSJtYWlsdG86Y2FybG9zQGNp
c2NvLmNvbSIgY2xhc3M9IiI+bWFpbHRvOmNhcmxvc0BjaXNjby5jb208L2E+Jmd0OzxiciBjbGFz
cz0iIj4NCi/igJxTb21ldGltZXMgSSB1c2UgYmlnIHdvcmRzIHRoYXQgSSBkbyBub3QgZnVsbHkg
dW5kZXJzdGFuZCwgdG8gbWFrZSBteXNlbGYgc291bmQgbW9yZSBwaG90b3N5bnRoZXNpcy4mcXVv
dDsvPGJyIGNsYXNzPSIiPg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2tx
dW90ZT4NCjwvZGl2Pg0KPGJyIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj4NCjxkaXYgc3R5bGU9
ImNvbG9yOiByZ2IoMCwgMCwgMCk7IGxldHRlci1zcGFjaW5nOiBub3JtYWw7IG9ycGhhbnM6IGF1
dG87IHRleHQtYWxpZ246IHN0YXJ0OyB0ZXh0LWluZGVudDogMHB4OyB0ZXh0LXRyYW5zZm9ybTog
bm9uZTsgd2hpdGUtc3BhY2U6IG5vcm1hbDsgd2lkb3dzOiBhdXRvOyB3b3JkLXNwYWNpbmc6IDBw
eDsgLXdlYmtpdC10ZXh0LXN0cm9rZS13aWR0aDogMHB4OyB3b3JkLXdyYXA6IGJyZWFrLXdvcmQ7
IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJyZWFrOiBhZnRlci13aGl0
ZS1zcGFjZTsiIGNsYXNzPSIiPg0KPGRpdiBzdHlsZT0iY29sb3I6IHJnYigwLCAwLCAwKTsgbGV0
dGVyLXNwYWNpbmc6IG5vcm1hbDsgb3JwaGFuczogYXV0bzsgdGV4dC1hbGlnbjogc3RhcnQ7IHRl
eHQtaW5kZW50OiAwcHg7IHRleHQtdHJhbnNmb3JtOiBub25lOyB3aGl0ZS1zcGFjZTogbm9ybWFs
OyB3aWRvd3M6IGF1dG87IHdvcmQtc3BhY2luZzogMHB4OyAtd2Via2l0LXRleHQtc3Ryb2tlLXdp
ZHRoOiAwcHg7IHdvcmQtd3JhcDogYnJlYWstd29yZDsgLXdlYmtpdC1uYnNwLW1vZGU6IHNwYWNl
OyAtd2Via2l0LWxpbmUtYnJlYWs6IGFmdGVyLXdoaXRlLXNwYWNlOyIgY2xhc3M9IiI+DQo8ZGl2
IHN0eWxlPSJjb2xvcjogcmdiKDAsIDAsIDApOyBsZXR0ZXItc3BhY2luZzogbm9ybWFsOyBvcnBo
YW5zOiBhdXRvOyB0ZXh0LWFsaWduOiBzdGFydDsgdGV4dC1pbmRlbnQ6IDBweDsgdGV4dC10cmFu
c2Zvcm06IG5vbmU7IHdoaXRlLXNwYWNlOiBub3JtYWw7IHdpZG93czogYXV0bzsgd29yZC1zcGFj
aW5nOiAwcHg7IC13ZWJraXQtdGV4dC1zdHJva2Utd2lkdGg6IDBweDsgd29yZC13cmFwOiBicmVh
ay13b3JkOyAtd2Via2l0LW5ic3AtbW9kZTogc3BhY2U7IC13ZWJraXQtbGluZS1icmVhazogYWZ0
ZXItd2hpdGUtc3BhY2U7IiBjbGFzcz0iIj4NCuKAlDwvZGl2Pg0KPGRpdiBzdHlsZT0iY29sb3I6
IHJnYigwLCAwLCAwKTsgbGV0dGVyLXNwYWNpbmc6IG5vcm1hbDsgb3JwaGFuczogYXV0bzsgdGV4
dC1hbGlnbjogc3RhcnQ7IHRleHQtaW5kZW50OiAwcHg7IHRleHQtdHJhbnNmb3JtOiBub25lOyB3
aGl0ZS1zcGFjZTogbm9ybWFsOyB3aWRvd3M6IGF1dG87IHdvcmQtc3BhY2luZzogMHB4OyAtd2Vi
a2l0LXRleHQtc3Ryb2tlLXdpZHRoOiAwcHg7IHdvcmQtd3JhcDogYnJlYWstd29yZDsgLXdlYmtp
dC1uYnNwLW1vZGU6IHNwYWNlOyAtd2Via2l0LWxpbmUtYnJlYWs6IGFmdGVyLXdoaXRlLXNwYWNl
OyIgY2xhc3M9IiI+DQpDYXJsb3MgUGlnbmF0YXJvLCZuYnNwOzxhIGhyZWY9Im1haWx0bzpjYXJs
b3NAY2lzY28uY29tIiBjbGFzcz0iIj5jYXJsb3NAY2lzY28uY29tPC9hPjxiciBjbGFzcz0iIj4N
CjxiciBjbGFzcz0iIj4NCjxpIGNsYXNzPSIiPuKAnFNvbWV0aW1lcyBJIHVzZSBiaWcgd29yZHMg
dGhhdCBJIGRvIG5vdCBmdWxseSB1bmRlcnN0YW5kLCB0byBtYWtlIG15c2VsZiBzb3VuZCBtb3Jl
Jm5ic3A7cGhvdG9zeW50aGVzaXMuJnF1b3Q7PC9pPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0
bWw+DQo=

--_000_6B1007C64AE8424489D6392922984AE7ciscocom_--


From nobody Sun Jul  2 13:14:49 2017
Return-Path: <cpignata@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FB0E127867; Sun,  2 Jul 2017 13:14:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 7qpxMJUMceCp; Sun,  2 Jul 2017 13:14:40 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED09E126B72; Sun,  2 Jul 2017 13:14:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7424; q=dns/txt; s=iport; t=1499026480; x=1500236080; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=h5MY+zUcSfVXBpEr6VM9/QColp2+UV1VySd8aZYd1wQ=; b=AK9pkKAl61LoBsMNKzCmC+TcIdHSuPFU5xnpoYej9eQIGhIzhOkzqLaF Oz2omRPQ8pwDZfaaOkt3ZE21wYE/sFP7NQETxwc2ujBOkrpyOAdX/aL09 DMf+AJOBqoP9G0zFc/RrTPBraqZRQrmY+3uwCQUesr4PRc7I4RwrwJIqe c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0C6AADiU1lZ/4gNJK1WBhkBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYMsLWOBDgeNfpFGIpV9ghEshXACGoJ/PxgBAgEBAQEBAQFrKIU?= =?us-ascii?q?YAQEBAQIBIxE3DgULAgEGAg4GBAICJgICAjAVEAIEDgUbigwIEJN4nWOCJotIA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBAQEBGAWBC4Icg0yBYSsLgm6EXIMhMIIxBZ5/Aod?= =?us-ascii?q?FgnqJQIIMhUqDcYZWlS8BHziBCnUVWwGFAByBZnaHc4ENAQEB?=
X-IronPort-AV: E=Sophos;i="5.40,299,1496102400"; d="scan'208";a="263247295"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 02 Jul 2017 20:14:30 +0000
Received: from XCH-RTP-019.cisco.com (xch-rtp-019.cisco.com [64.101.220.159]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v62KETLU015124 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 2 Jul 2017 20:14:30 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-019.cisco.com (64.101.220.159) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sun, 2 Jul 2017 16:14:29 -0400
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1210.000; Sun, 2 Jul 2017 16:14:29 -0400
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
CC: "gen-art@ietf.org" <gen-art@ietf.org>, "spring@ietf.org" <spring@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-spring-oam-usecase.all@ietf.org" <draft-ietf-spring-oam-usecase.all@ietf.org>
Subject: Re: Genart last call review of draft-ietf-spring-oam-usecase-06
Thread-Topic: Genart last call review of draft-ietf-spring-oam-usecase-06
Thread-Index: AQHS8DzDWIhR6rTu8UG+oA8joThdh6JBQjKA
Date: Sun, 2 Jul 2017 20:14:29 +0000
Message-ID: <FFB75186-880F-4288-9DCB-19CF1D666939@cisco.com>
References: <149867468440.7527.6305996146978005032@ietfa.amsl.com>
In-Reply-To: <149867468440.7527.6305996146978005032@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.116.131]
Content-Type: text/plain; charset="utf-8"
Content-ID: <15DAEEE9C75F9D4DBBAC78E11FC52853@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tqFKOQkcbhs-w0ciTkQzmyTUsas>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Jul 2017 20:14:42 -0000

SGksIFBldGUsDQoNCk1hbnkgdGhhbmtzIGZvciB0aGUgdGltZSB0byByZWFkIGFuZCByZXZpZXcg
dGhpcyBkb2N1bWVudCENCg0KTGlrZSBSdWVkaWdlciwgSSB3aWxsIGxldCB0aGUgc2hlcGhlcmQs
IGNoYWlycywgYW5kIEFEIHdlaWdodCBpbiDigJQgYnV0IGluIHRoZSBtZWFudGltZSwgSSB3YW50
ZWQgdG8gb2ZmZXIgYSBjb3VwbGUgb2Ygb2JzZXJ2YXRpb25zIGZvciBjb25zaWRlcmF0aW9uLiBQ
bGVhc2Ugc2VlIGlubGluZS4NCg0KDQo+IE9uIEp1biAyOCwgMjAxNywgYXQgMjozMSBQTSwgUGV0
ZSBSZXNuaWNrIDxwcmVzbmlja0BxdGkucXVhbGNvbW0uY29tPiB3cm90ZToNCj4gDQo+IFJldmll
d2VyOiBQZXRlIFJlc25pY2sNCj4gUmV2aWV3IHJlc3VsdDogTm90IFJlYWR5DQo+IA0KPiBJIGFt
IHRoZSBhc3NpZ25lZCBHZW4tQVJUIHJldmlld2VyIGZvciB0aGlzIGRyYWZ0LiBUaGUgR2VuZXJh
bCBBcmVhDQo+IFJldmlldyBUZWFtIChHZW4tQVJUKSByZXZpZXdzIGFsbCBJRVRGIGRvY3VtZW50
cyBiZWluZyBwcm9jZXNzZWQNCj4gYnkgdGhlIElFU0cgZm9yIHRoZSBJRVRGIENoYWlyLiAgUGxl
YXNlIHRyZWF0IHRoZXNlIGNvbW1lbnRzIGp1c3QNCj4gbGlrZSBhbnkgb3RoZXIgbGFzdCBjYWxs
IGNvbW1lbnRzLg0KPiANCj4gRm9yIG1vcmUgaW5mb3JtYXRpb24sIHBsZWFzZSBzZWUgdGhlIEZB
USBhdA0KPiANCj4gPGh0dHBzOi8vdHJhYy5pZXRmLm9yZy90cmFjL2dlbi93aWtpL0dlbkFydGZh
cT4uDQo+IA0KPiBEb2N1bWVudDogZHJhZnQtaWV0Zi1zcHJpbmctb2FtLXVzZWNhc2UtMDYNCj4g
UmV2aWV3ZXI6IFBldGUgUmVzbmljaw0KPiBSZXZpZXcgRGF0ZTogMjAxNy0wNi0yOA0KPiBJRVRG
IExDIEVuZCBEYXRlOiAyMDE3LTA2LTMwDQo+IElFU0cgVGVsZWNoYXQgZGF0ZTogTm90IHNjaGVk
dWxlZCBmb3IgYSB0ZWxlY2hhdA0KPiANCj4gU3VtbWFyeTogTm90IFJlYWR5IGZvciBwdWJsaWNh
dGlvbiBhcyBJbmZvcm1hdGlvbmFsLCBidXQgbWlnaHQgYmUgUmVhZHkgZm9yDQo+IHB1YmxpY2F0
aW9uIGFzIFByb3Bvc2VkIFN0YW5kYXJkDQo+IA0KPiBNYWpvciBpc3N1ZXM6DQo+IA0KPiBUaGlz
IGlzIGFuIGFkbWl0dGVkbHkgdW51c3VhbCByZXZpZXcuIEkgaGF2ZSByZWFkIHRocm91Z2ggdGhl
IGVudGlyZSBkb2N1bWVudCwNCj4gYW5kIHRoZSB0ZWNobmljYWwgd29yayBzZWVtcyBmaW5lLCBi
dXQgaXMgd2VsbCBiZXlvbmQgbXkgdGVjaG5pY2FsIGV4cGVydGlzZSwNCj4gc28gSSBjYW4ndCBy
ZWFsbHkgY29tbWVudCBvbiB0aGUgdGVjaG5pY2FsIGNvcnJlY3RuZXNzLiBIb3dldmVyLCBpdCBp
cw0KPiBhYnNvbHV0ZWx5IGNsZWFyIHRvIG1lIHRoYXQgdGhpcyBpcyAqbm90KiBhICJ1c2UgY2Fz
ZSIgZG9jdW1lbnQgYXQgYWxsDQoNCkkgYWdyZWUgd2l0aCB0aGUgYXNzZXNzbWVudCB0aGF0IHRo
aXMgaXMgbm90IGEg4oCcdXNlLWNhc2XigJ0gZG9jdW1lbnQgKGluIGEgc3RyaWN0IG9yIHRyYWRp
dGlvbmFsIHNlbnNlKTsgdGhpcyBkb2N1bWVudCBkZXNjcmliZXMgYSBkZXBsb3ltZW50IGNhc2Ug
YW5kIGEgc29sdXRpb24gdG8gYSB1c2UgY2FzZSwgdXNpbmcgZXhpc3RpbmcgdGVjaG5vbG9neSBi
bG9ja3MuIEl0IGRvZXMgbm90IGRlZmluZSBuZXcgcHJvdG9jb2wgbm9yIChtb3JlIGltcG9ydGFu
dGx5KSBjcmVhdGVzIGludGVyb3BlcmFiaWxpdHkgY29uc2lkZXJhdGlvbnMuIA0KDQo+IGFuZCBJ
DQo+IGRvbid0IHRoaW5rIGl0J3MgYXBwcm9wcmlhdGUgYXMgYW4gSW5mb3JtYXRpb25hbCBkb2N1
bWVudC4NCg0KTm93LCByZWdhcmRpbmcgdGhlIG1vc3QgYXBwcm9wcmlhdGUgaW50ZW5kZWQgc3Rh
dHVzLCBJIGNvdWxkIHBlcnNvbmFsbHkgYXJndWUgYm90aCBzaWRlcywgYW5kIGZyYW5rbHksIEkg
ZG8gbm90IGhhdmUgYSBzdHJvbmcgcHJlZmVyZW5jZSBvciBjb25jZXJuIGVpdGhlciB3YXkuIA0K
DQpUaGUgbmV0IG9mIGl0IGlzIHRoYXQgdGhpcyAoaW5mb3JtYXRpb25hbC9zcGVjaWZpY2F0aW9u
KSBkb2N1bWVudCBkb2VzIG5vdCBjcmVhdGUgcmVxdWlyZW1lbnRzIGZvciBTUFJJTkcgbm9kZXMs
IGNoYW5nZXMgaW4gU1BSSU5HLCBub3IgZXhwb3NlcyBpbnRlcm9wZXJhYmlsaXR5IGlzc3Vlcy4g
SXQgYmFzaWNhbGx5IGxldmVyYWdlcyBhcy1pcyB0aGUgdW5kZXJseWluZyBjYXBhYmlsaXRpZXMg
Y3JlYXRlZCB3aXRoIFNQUklORy4gRnJvbSB0aGF0IGFuZ2xlLCBJbmZvcm1hdGlvbmFsIGlzIGEg
dmVyeSBhcHByb3ByaWF0ZSBmaXQuIE9uIHRoZSBvdGhlciBoYW5kLCBJIGRvIG5vdCBkaXNhZ3Jl
ZSB3aXRoIHRoaXMgZG9jdW1lbnQgc3BlY2lmeWluZyBhIHN5c3RlbSwgYW5kIHRoZSBwbGF5LW9m
LXdvcmRzIHRoYXQgcmVzdWx0cyBpbiBzdGFuZGFyZHMtdHJhY2sg4oCUIHNvIGl0IGlzIGEgc3Bl
YyBmb3IgdGhlIHBhdGggbW9uaXRvcmluZyBzeXN0ZW0sIGJ1dCBwcm92aWRlcyBpbmZvcm1hdGlv
biB0byB0aGUgbmV0d29yayBhbmQgdG8gU1BSSU5HIHNwZWNzIG9uIGhvdyB0aGUgbmV3IHRlY2gg
Y2FuIGJlIHVzZWQuDQoNCk5ldC1uZXQsIEkgc2VlIEluZm9ybWF0aW9uYWwgYnV0IGNhbiB1bmRl
cnN0YW5kIHlvdXIgcmF0aW9uYWxlLg0KDQpJbiBhbnkgY2FzZSwgd2hhdCBkb2VzIGNvbmNlcm4g
bWUgbW9yZSBpcyB3aGV0aGVyIGEgcG90ZW50aWFsIGNoYW5nZSBvZiBpbnRlbmRlZCBzdGF0dXMg
d291bGQgYWRkIHNpZ25pZmljYW50IGRlbGF5IGFuZCByZXNldCBwcm9jZXNzIHRpbWVycyBvbiBh
IHRpbWVsaW5lIHRoYXQgaXMgYWxyZWFkeSBvdmVyc3RyZXRjaGVkIGFuZCBhIHZlcnkgc2xvdyBw
cm9ncmVzc+KApg0KDQo+IFRoaXMgaXMgY2xlYXJseSBhDQo+ICpzcGVjaWZpY2F0aW9uKiBvZiBh
IHBhdGggbW9uaXRvcmluZyBzeXN0ZW0uIEl0IGdpdmVzIGd1aWRhbmNlcyBhcyB0byByZXF1aXJl
ZCwNCj4gcmVjb21tZW5kZWQsIGFuZCBvcHRpb25hbCBwYXJhbWV0ZXJzLCBhbmQgc3BlY2lmaWVz
IGhvdyB0byB1c2UgZGlmZmVyZW50DQo+IHByb3RvY29sIHBpZWNlcy4gSXQgaXMgYXQgdGhlIHZl
cnkgbGVhc3Qgd2hhdCBSRkMgMjAyNiByZWZlcnMgdG8gYXMgYW4NCj4gIkFwcGxpY2FiaWxpdHkg
U3RhdGVtZW50IChBUykiIChzZWUgUkZDIDIwMjYsIHNlYy4gMy4yKS4gSXQgKm1pZ2h0KiBiZSBh
IEJDUCwNCj4gYnV0IGl0IGlzIG5vdCBzdHJpY3RseSBnaXZpbmcgImNvbW1vbiBndWlkZWxpbmVz
IGZvciBwb2xpY2llcyBhbmQgb3BlcmF0aW9ucyINCj4gKDIwMjYsIHNlYy4gNSksIHNvIEkgZG9u
J3QgcmVhbGx5IHRoaW5rIHRoYXQncyByaWdodCwgYW5kIGluc3RlYWQgdGhpcyBzaG91bGQNCj4g
YmUgb2ZmZXJlZCBmb3IgUHJvcG9zZWQgU3RhbmRhcmQuIEVpdGhlciB3YXksIEkgdGhpbmsgSW5m
b3JtYXRpb25hbCBpcyBub3QNCj4gY29ycmVjdC4gSW1wb3J0YW50bHksIEkgdGhpbmsgdGhlcmUg
aXMgYSBnb29kIGxpa2VsaWhvb2QgdGhhdCB0aGlzIGRvY3VtZW50IGhhcw0KPiBub3QgcmVjZWl2
ZWQgdGhlIGFwcHJvcHJpYXRlIGFtb3VudCBvZiByZXZpZXc7IHBlb3BsZSB0ZW5kIHRvIGlnbm9y
ZQ0KPiBJbmZvcm1hdGlvbmFsICJ1c2UgY2FzZSIgZG9jdW1lbnRzLA0KDQpUaGlzLCBob3dldmVy
LCBJIHRoaW5rIGlzIGFuIGluYXBwcm9wcmlhdGUgZXh0cmFwb2xhdGlvbi4gQWx0aG91Z2ggdGhl
IHNoZXBoZXJkLCBXRyBhbmQgY2hhaXJzIGFscmVhZHkgY29uc2lkZXJlZCB0aGUgaW50ZW5kZWQg
c3RhdHVzLCBJIHRoaW5rIGl0IGlzIGltcG9ydGFudCB0byByZS10aGluayB3aGF04oCZcyBiZXN0
IGZvciB0aGlzIGRvY3VtZW50IGluIHRoZSBjb250ZXh0IG9mIHRoZSBtZXJpdHMsIHN0cnVjdHVy
ZSBhbmQgZ29hbHMuIEJ1dCBqdXN0aWZ5aW5nIGl0IG5vdCBiZWluZyBpbmZvcm1hdGlvbmFsIGJl
Y2F1c2Ug4oCccGVvcGxlIHRlbmQgdG8gaWdub3JlIFvigKZd4oCdIHNlZW1zIGEgcmVkIGhlcnJp
bmcuIA0KDQo+IGFuZCB0aGVyZSBoYXZlIGJlZW4gbm8gTGFzdCBDYWxsIGNvbW1lbnRzDQo+IGJl
eW9uZCBKb2VsJ3MgUlRHIEFyZWEgUmV2aWV3Lg0KDQpXaXRoaW4gU1BSSU5HLCB0aGlzIGRvY3Vt
ZW50IGRhdGVzIHRoZSBvcmlnaW5zIG9mIHRoZSBXRy4gSXQgd2FzIHByZXNlbnRlZCBpbiBtYW55
IFdHcyBudW1lcm91cyB0aW1lcyBhbmQgaXRlcmF0ZWQgdGhyb3VnaCBtYW55IHZlcnNpb25zICh3
aXRoaW4gdGhyZWUgZmlsZW5hbWVzKSBhcyB2YXJpb3VzIHJldmlld3MgY2FtZSBpbi4gSeKAmWQg
cmVjb21tZW5kIHlvdSBhbHNvIGdvIGJhY2sgYW5kIGNoZWNrIHRoZSB0aW1lbGluZS4gSSB3b3Vs
ZCBub3QgYWxzbyBtYWtlIGhhcmQgY29uY2x1c2lvbnMgYmFzZWQgb24gTEMgdHJhZmZpYy4NCg0K
PiBFdmVuIGluIElFU0cgcmV2aWV3LCBhbiBJbmZvcm1hdGlvbmFsIGRvY3VtZW50DQo+IG9ubHkg
dGFrZXMgdGhlIHNwb25zb3JpbmcgQUQgdG8gYXBwcm92ZTsgZXZlcnkgb3RoZXIgQUQgY2FuIHN1
bW1hcmlseSBpZ25vcmUNCj4gdGhlIGRvY3VtZW50LCBvciBldmVuIGJhbGxvdCBBQlNUQUlOLCBh
bmQgdGhlIGRvY3VtZW50IHdpbGwgc3RpbGwgYmUgcHVibGlzaGVkDQo+ICh0aG91Z2ggdGhhdCBk
b2VzIG5vdCBub3JtYWxseSBoYXBwZW4pLiBUaGlzIGRvY3VtZW50IHNob3VsZCBoYXZlIG11Y2gg
bW9yZQ0KPiB0aGFuIHRoYXQgbGV2ZWwgb2YgcmV2aWV3LiBJIHN0cm9uZ2x5IHJlY29tbWVuZCB0
byB0aGUgV0cgYW5kIEFEIHRoYXQgdGhpcw0KPiBkb2N1bWVudCBiZSB3aXRoZHJhd24gYXMgYW4g
SW5mb3JtYXRpb25hbCBkb2N1bWVudCBhbmQgcmVzdWJtaXR0ZWQgZm9yIFByb3Bvc2VkDQo+IFN0
YW5kYXJkIGFuZCBoYXZlIHRoYXQgbGV2ZWwgb2YgcmV2aWV3IGFuZCBzY3J1dGlueSBhcHBsaWVk
IHRvIGl0Lg0KDQpBcyBJIHNhaWQsIEkgYW0gaGFwcHkgd2l0aCBlaXRoZXIgc3RhdHVzIGFuZCBj
YW4gc2VlIGFyZ3VtZW50cyBib3RoIHdheXMuIEkgd291bGQgbm90IG9iamVjdCB0byBhIGNoYW5n
ZS4gDQoNCkhvd2V2ZXIsIHBlcnNvbmFsbHksIEkgZG8gbm90IHNlZSB0aGUgbmVlZC4NCg0KPiAN
Cj4gTWlub3IgaXNzdWVzOg0KPiANCj4gTm9uZS4NCj4gDQo+IE5pdHMvZWRpdG9yaWFsIGNvbW1l
bnRzOg0KPiANCj4gVGhpcyBkb2N1bWVudCByZWZlcnMgdG8gUkZDIDQzNzksIHdoaWNoIGhhcyBi
ZWVuIG9ic29sZXRlZCBieSBSRkMgODAyOS4gSXQNCj4gc2VlbXMgbGlrZSB0aGUgcmVmZXJlbmNl
cyBzaG91bGQgYmUgdXBkYXRlZC4NCj4gDQo+IA0KDQpJbmRlZWQuIERvbmUgaW4gLTA3IGFuZCAt
MDguDQoNClRoYW5rcyBhZ2FpbiwgUGV0ZSENCg0K4oCUDQpDYXJsb3MgUGlnbmF0YXJvLCBjYXJs
b3NAY2lzY28uY29tDQoNCuKAnFNvbWV0aW1lcyBJIHVzZSBiaWcgd29yZHMgdGhhdCBJIGRvIG5v
dCBmdWxseSB1bmRlcnN0YW5kLCB0byBtYWtlIG15c2VsZiBzb3VuZCBtb3JlIHBob3Rvc3ludGhl
c2lzLiINCg0K


From nobody Sun Jul  2 14:43:09 2017
Return-Path: <xufeng.liu.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2226127076; Sun,  2 Jul 2017 14:42:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.689
X-Spam-Level: 
X-Spam-Status: No, score=-2.689 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, T_KAM_HTML_FONT_INVALID=0.01] 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 aqu-UJqYwa0H; Sun,  2 Jul 2017 14:42:39 -0700 (PDT)
Received: from mail-oi0-x242.google.com (mail-oi0-x242.google.com [IPv6:2607:f8b0:4003:c06::242]) (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 ED844129ADF; Sun,  2 Jul 2017 14:42:38 -0700 (PDT)
Received: by mail-oi0-x242.google.com with SMTP id n2so10356075oig.3; Sun, 02 Jul 2017 14:42:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:thread-index:content-language; bh=7wn2ZdbvCT7vb7lFFwezh+KdQta67VdbifyBmsyw5fg=; b=SbbV8lyWc7nc2RU/adRmkQ4mJAaYNouRm2xuQIvjPPp2dWONsOHiiB2ZKSdCnczduC 6nIAglOkplftXy5jr8qQjawbQxoWBf3Pgy6hkS4nSx3vvyQ6Fbrp3qgzsVMkXltxSiOv SzTd9/6/TqDUVLsdX1RddFwtqGiEQxmu5hzvbeanH5ikBL33HiOqiORCGMb0Mdrum7Ba XEoQR3u6ogYBF54lq6TgNth/C8uruJvOXtCeTTVtLbLOlQ14QTCzB5lhdQsKnAb/WMIE YK19uFn0BlTZMCPNG33AuyK0PAJBq6TUHaNDT//gdtkVmjQRVD6IGB4IsOdae7Nw2lnU 8I2Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=7wn2ZdbvCT7vb7lFFwezh+KdQta67VdbifyBmsyw5fg=; b=c05HvACF/wPzd9l+zQuUnjDgoonGoUmsBGmh7kvKbdFlMOyPI/B5b/3H8iFP4L6GNI LOlL4wwoOlQxXmD60yTleM0Oy8ph432jhngZdqts9xxOL1eG16Ci31ZCemEZZMKwMqC/ TBnPy2g/Kw83plpoHuv64DAExMzc9J3ldqtaLlZWtiBHJ8ivtaBO9mdn3KPGRVm2/KUF pMdJ73iJxVvxQ4G3MCsFnCTTQuNLWa6BSAPxS483o/XnvGchLnCM88mxPu5yullvKIs3 nNuqrfX/D4j1bFGP49YuKi1IgDakwRz6F8mMVCUhtoYOWCIiTFp+Y1ynmaCfYoOUd/RA yKtQ==
X-Gm-Message-State: AKS2vOz+LIKaKT27xdKmd9Rn1FViUBLIg+0RIn46jskNpHA9Xdfx98CE +UXToOxyrsp9ng==
X-Received: by 10.202.213.2 with SMTP id m2mr21471867oig.17.1499031758265; Sun, 02 Jul 2017 14:42:38 -0700 (PDT)
Received: from xliuus (ip72-209-195-86.dc.dc.cox.net. [72.209.195.86]) by smtp.gmail.com with ESMTPSA id t130sm24644026oig.3.2017.07.02.14.42.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 02 Jul 2017 14:42:37 -0700 (PDT)
From: "Xufeng Liu" <xufeng.liu.ietf@gmail.com>
To: "'Benoit Claise'" <bclaise@cisco.com>, "'Xufeng Liu'" <Xufeng_Liu@jabil.com>, "'Robert Wilton'" <rwilton@cisco.com>, "'Mahesh Jethanandani'" <mjethanandani@gmail.com>, <yang-doctors@ietf.org>
Cc: <ietf@ietf.org>, <teas@ietf.org>, <draft-ietf-teas-yang-te-topo.all@ietf.org>
References: <149564066257.28529.12761629961042171907@ietfa.amsl.com> <BN3PR0201MB08670E55FFB5470F338E998DF1CD0@BN3PR0201MB0867.namprd02.prod.outlook.com> <5d4541d3-9426-787d-e02b-9c2dbc3a5400@cisco.com> <BN3PR0201MB0867315F3E88577B9EEF6584F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com> <3a1c319f-0255-b8ee-ecbd-739568c1dc7f@cisco.com> <1ab3a0d8-de3e-1d7c-2967-97b74b1c68a5@cisco.com> <BN3PR0201MB0867664CBDA460C283DC8043F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com> <04b933e2-189a-6fe2-5d24-310167f91b69@cisco.com>
In-Reply-To: <04b933e2-189a-6fe2-5d24-310167f91b69@cisco.com>
Subject: RE: [Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-08
Date: Sun, 2 Jul 2017 17:42:42 -0400
Message-ID: <00d001d2f37c$22d3dd10$687b9730$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00D1_01D2F35A.9BC52340"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQGOEtHVR4X43lNLh7rZd88C0w0DvAIP54n+AmHbMQEB8+cVUAKUyOUBAjMgSAcBQqeaTwEuF5NGol3XSiA=
Content-Language: en-us
x-dg-ref: PG1ldGE+PGF0IG5tPSJib2R5Lmh0bWwiIHA9ImM6XHVzZXJzXHhsaXVcYXBwZGF0YVxyb2FtaW5nXDA5ZDg0OWI2LTMyZDMtNGE0MC04NWVlLTZiODRiYTI5ZTM1Ylxtc2dzXG1zZy01ZjM1YjAwNy01ZjZmLTExZTctOWMxOS0xODVlMGZlM2M0NWNcYW1lLXRlc3RcNWYzNWIwMDgtNWY2Zi0xMWU3LTljMTktMTg1ZTBmZTNjNDVjYm9keS5odG1sIiBzej0iMjI5NzYiIHQ9IjEzMTQzNTA1MzYxNzE4NjExNSIgaD0iM0VZc21LV0t5bGZuZk1zWEdwZFFQZ3NOejNBPSIgaWQ9IiIgYmw9IjAiIGJvPSIxIi8+PC9tZXRhPg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PHnltWMBrjxuRJDue-ZinWoGPXg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Jul 2017 21:42:43 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00D1_01D2F35A.9BC52340
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

An updated revision of the TE topology model has been posted at =
https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-10.

=20

This new revision now contains the NMDA compliant module and a companion =
=E2=80=9C-state=E2=80=9D module, after the I2RS topology model that we =
augment has been update with a =E2=80=9C-state=E2=80=9D module.

=20

Now that this issue has been solved, the authors and contributors think =
that the draft is ready for the last call.

=20

Thanks,

- Xufeng

=20

P.S. Because of the structure changes of the TE topology model, all =
augmenting models need to be updated. Sorry for the short notice.

=20

From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Benoit Claise
Sent: Monday, June 26, 2017 6:46 AM
To: Xufeng Liu <Xufeng_Liu@jabil.com>; Robert Wilton =
<rwilton@cisco.com>; Mahesh Jethanandani <mjethanandani@gmail.com>; =
yang-doctors@ietf.org
Cc: Benoit Claise <bclaise@cisco.com>; ietf@ietf.org; teas@ietf.org; =
draft-ietf-teas-yang-te-topo.all@ietf.org
Subject: Re: [Teas] Yangdoctors last call review of =
draft-ietf-teas-yang-te-topo-08

=20

Hi Xufeng,

Hi Benoit,
=20

-----Original Message-----
From: Benoit Claise [mailto:bclaise@cisco.com]
Sent: Thursday, June 22, 2017 6:12 AM
To: Robert Wilton  <mailto:rwilton@cisco.com> <rwilton@cisco.com>; =
Xufeng Liu  <mailto:Xufeng_Liu@jabil.com> <Xufeng_Liu@jabil.com>;
Mahesh Jethanandani  <mailto:mjethanandani@gmail.com> =
<mjethanandani@gmail.com>; yang-doctors@ietf.org =
<mailto:yang-doctors@ietf.org>=20
Cc: ietf@ietf.org <mailto:ietf@ietf.org> ; teas@ietf.org =
<mailto:teas@ietf.org> ; draft-ietf-teas-yang-te-topo.all@ietf.org =
<mailto:draft-ietf-teas-yang-te-topo.all@ietf.org>=20
Subject: Re: [Teas] Yangdoctors last call review of =
draft-ietf-teas-yang-te-topo-
08
=20
Dear draft-ietf-teas-yang-te-topo authors,

Hi Xufeng,
=20
OK, by tooling, I don't mean the pyang plugins that I have been
working on to convert between different types of models.  As you
aware, the TE YANG models can easily be converted to NMDA style since
I have already done it
(https://github.com/rgwilton/ietf-models-to-combined).
=20
My comment actually relates to the fact the structure used by TE YANG
modules don't match any other YANG modules - they are using their own
unique style of structure.

This is an important issue to resolve.

=20
Today, there are three common styles of modules:
(1) IETF style split config/state trees (e.g. ietf-interfaces).
(2) IETF NMDA style combined config/state trees (i.e. where all IETF
modules are heading to).
(3) OpenConfig style modules with the config/state containers
immediately above the config leaves.
=20
Tooling is likely to be optimized to work with these model structures,
but the TE modules do not fit into any of the three styles above.
They are a yet another OpenConfig-like style, but that is different
enough that tooling that is designed to work with OpenConfig style
YANG modules would likely not work with the TE YANG modules.
=20
Specifically, for clients that expecting to work with an OpenConfig
style YANG module, then if it knows the path to config leaf X, then
they would expect the applied config value to be available at the path
"../state/X".  But, this doesn't hold for the structure being used in
the TE YANG models.
=20
I believe strongly that the models being produced by organizations
should be structures in a consistent way, hence why I think that the
published standard version of the TE YANG modules should immediately
align to the NMDA style.

Agreed.
Here is the OPS and RTG AD message:
https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html
=20
I understand that the I2RS topology YANG modules will be improved to the
NMDA style.

[Xufeng] The I2RS topology model is already NMDA style, but the NMDA =
models are not immediately implementable without NETCONF/RESTCONF =
protocol update. We will need the "-state" module for the I2RS topology =
model (and for all the top-level models) for now.=20

Adding -state to the Appendix is a possibility.
"In all cases, the NMDA and non-NMDA modules SHOULD be published in the =
same document, with NMDA modules in the document main body and the =
non-NMDA modules in an Appendix."
See https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html



While the NMDA is nice, the NMDA discussions have already significantly =
delayed publishing new models, and doing NMDA without staging will =
further delay the process.

This is not solving the important issue brought up by Rob Witlon:

My comment actually relates to the fact the structure used by TE YANG =
modules don't match any other YANG modules - they are using their own =
unique style of structure.

Regards, B.



=20
Thanks,  Xufeng

=20
Regards, Benoit

=20
Thanks,
Rob
=20
=20
On 22/06/2017 04:16, Xufeng Liu wrote:

Hi Rob,
=20
While the tooling is very nice to have, especially for writing new
models or converting models, we do not have to use it for every
model. It seems not necessary to use the tooling on this model for
now. We already know that we can manually convert it to NMDA style if
needed.
=20
Thanks,
- Xufeng
=20

-----Original Message-----
From: Robert Wilton [mailto:rwilton@cisco.com]
Sent: Wednesday, June 21, 2017 5:34 AM
To: Xufeng Liu  <mailto:Xufeng_Liu@jabil.com> <Xufeng_Liu@jabil.com>; =
Mahesh Jethanandani
 <mailto:mjethanandani@gmail.com> <mjethanandani@gmail.com>; =
yang-doctors@ietf.org <mailto:yang-doctors@ietf.org>=20
Cc: ietf@ietf.org <mailto:ietf@ietf.org> ; teas@ietf.org =
<mailto:teas@ietf.org> ;
draft-ietf-teas-yang-te-topo.all@ietf.org =
<mailto:draft-ietf-teas-yang-te-topo.all@ietf.org>=20
Subject: Re: [Teas] Yangdoctors last call review of
draft-ietf-teas-yang-te-topo-
08
=20
Hi Xufeng,
=20
On 12/06/2017 22:28, Xufeng Liu wrote:

Hi Mahesh,
=20
Thank you much for the review. We have submitted an updated draft

(https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09) to
address these issues. More detailed explanations are put below
inline.

If the responses and updates are satisfactory, we are ready for the
last call.
=20
Best regards,
- Xufeng
=20

-----Original Message-----
From: Mahesh Jethanandani [mailto:mjethanandani@gmail.com]
Sent: Wednesday, May 24, 2017 11:44 AM
To: yang-doctors@ietf.org <mailto:yang-doctors@ietf.org>=20
Cc: ietf@ietf.org <mailto:ietf@ietf.org> ; teas@ietf.org =
<mailto:teas@ietf.org> ;
draft-ietf-teas-yang-te-topo.all@ietf.org =
<mailto:draft-ietf-teas-yang-te-topo.all@ietf.org>=20
Subject: Yangdoctors last call review of
draft-ietf-teas-yang-te-topo-08
=20
Reviewer: Mahesh Jethanandani
Review result: Ready with Issues
=20
Document reviewed: draft-ietf-teas-yang-te-topo-08
=20
Status: Ready with Issues
=20
I am not an expert in Traffic Engineering. This review is looking
at the draft from a YANG perspective. With that said, I have
marked it as =E2=80=9CReady

with Issues=E2=80=9D

because of some of the points discussed below.
=20
Summary:
=20
This document defines a YANG data model for representing,
retrieving and manipulating TE Topologies. The model serves as a
base model that other technology specific TE Topology models can

augment.

=20
Comments:
=20
Almost all the containers in the model are presence containers. Is
there a reason why they have to be presence containers? Note, that
presence containers are containers whose existence itself
represents configuration data. What particular configuration data
is each container

representing in itself?

[Xufeng] Containers that use =E2=80=9Cpresence=E2=80=9D are:
    - Container =E2=80=9Cunderlay=E2=80=9D
      o  We have changed 13 occurrences of such containers to be
not

presence container.

    - Container =E2=80=9Cte=E2=80=9D under augmentation
      o  To indicate that =E2=80=9CTE=E2=80=9D is enabled (configuration =
data)
      o  Also used to do augmentation. The =E2=80=9Cpresence=E2=80=9D =
statement can

prevent the mandatory child from affecting augmented base model.

    - /nw:networks/nw:network/nw:network-types/te-topology!
      o  A mechanism required by I2RS topology model to specify the

topology type.

It is difficult to co-relate the diagram with the model itself
because of different terms being used to define different parts of
the model.
There is =E2=80=9CTE Topology Model=E2=80=9D and then there is =
=E2=80=9CGeneric TE
Topology

Model=E2=80=9D.

Are these one and the same models? If so, a common term for both
of them would be helpful.

[Xufeng] Yes. These two terms are the same. Figure 12, Figure 13,
and relevant

descriptions have been updated to make the document consistent.

There is extensive use of groupings in the document. However, not
all instances of groupings are used multiple number of times.
Where they are not being repeated, it would be better to move the
grouping directly where the uses statement resides. Case in point
the grouping

connectivity-label-restriction-list.

[Xufeng] We have removed the following groupings
      te-link-augment
      te-node-augment
      te-termination-point-augment
      te-topologies-augment
      te-topology-augment
      te-link-state-underlay-attributes
      te-node-state-derived-notification
      te-topology-type
=20
The remaining groupings have been kept so that we can:
    - Share the groupings in this model
    - Prepare to be shared by a model augmenting this model
    - Prevent a grouping or configuration section from being too long
    - Improve readability
=20

The split between config and state containers does not seem to
follow any particular pattern.

[Xufeng] The pattern is clear:
For each manageable entity (object), there is a config container
and state

container. The configurable properties go into the config container
and state properties go into the state container. Such objects are
identified by a list item or a presence container so that the
=E2=80=9Ccreate=E2=80=9D, =E2=80=9Cdelete=E2=80=9D, and =
=E2=80=9Cmodify=E2=80=9D
operations
can be performed on them. The non-presence containers do not
represent configuration data so they do not introduce such objects.

It is neither a top level split, as is the case with existing IETF
models,

[Xufeng] We could not do top level split because the base I2RS
network

topology model
(https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo-
12) that we augment does not have the top-level split (for its own
reasons).

nor do they follow the OpenConfig style of splitting config and
state under each relevant leaf,

[Xufeng] The pattern is consistent with this style in principle,
with some

adjustments to fit to our multiple levels of hierarchy.
This is effectively a new forth style of YANG models that is not
consistent with any of the three existing styles, i.e.:
   - Current IETF config/state split model style
   - NMDA combined config/state tree
   - OpenConfig split config/state containers immediately above the
config true leaves.
=20
Tooling that it designed to work with OpenConfig models will need
customization to work with these TE models because the config/state
containers will not be where the tooling expects them to be.
=20
Thanks,
Rob

=20
.
=20

=20

=20


------=_NextPart_000_00D1_01D2F35A.9BC52340
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=3DGenerator 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:DengXian;
	panose-1:3 0 5 9 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@DengXian";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	color:black;}
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";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle21
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri",sans-serif;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@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 bgcolor=3Dwhite =
lang=3DEN-US link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoPlainText>An updated revision of the TE topology model has =
been posted at <a =
href=3D"https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-10">http=
s://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-10</a>.<o:p></o:p></=
p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>This new revision now contains the NMDA compliant =
module and a companion =E2=80=9C-state=E2=80=9D module, after the I2RS =
topology model that we augment has been update with a =
=E2=80=9C-state=E2=80=9D module.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Now =
that this issue has been solved, the authors and contributors think that =
the draft is ready for the last call.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Thanks,<o:p></o:p></p><p class=3DMsoPlainText>- =
Xufeng<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>P.S. Because of the structure changes of the TE =
topology model, all augmenting models need to be updated. Sorry for the =
short notice.<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:windowtext'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #E1E1E1 =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'color:windowtext'>From:</span></b><span =
style=3D'color:windowtext'> Teas [mailto:teas-bounces@ietf.org] <b>On =
Behalf Of </b>Benoit Claise<br><b>Sent:</b> Monday, June 26, 2017 6:46 =
AM<br><b>To:</b> Xufeng Liu &lt;Xufeng_Liu@jabil.com&gt;; Robert Wilton =
&lt;rwilton@cisco.com&gt;; Mahesh Jethanandani =
&lt;mjethanandani@gmail.com&gt;; yang-doctors@ietf.org<br><b>Cc:</b> =
Benoit Claise &lt;bclaise@cisco.com&gt;; ietf@ietf.org; teas@ietf.org; =
draft-ietf-teas-yang-te-topo.all@ietf.org<br><b>Subject:</b> Re: [Teas] =
Yangdoctors last call review of =
draft-ietf-teas-yang-te-topo-08<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>Hi =
Xufeng,<o:p></o:p></p></div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>Hi =
Benoit,<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>-----Original =
Message-----<o:p></o:p></pre><pre>From: Benoit Claise [<a =
href=3D"mailto:bclaise@cisco.com">mailto:bclaise@cisco.com</a>]<o:p></o:p=
></pre><pre>Sent: Thursday, June 22, 2017 6:12 =
AM<o:p></o:p></pre><pre>To: Robert Wilton <a =
href=3D"mailto:rwilton@cisco.com">&lt;rwilton@cisco.com&gt;</a>; Xufeng =
Liu <a =
href=3D"mailto:Xufeng_Liu@jabil.com">&lt;Xufeng_Liu@jabil.com&gt;</a>;<o:=
p></o:p></pre><pre>Mahesh Jethanandani <a =
href=3D"mailto:mjethanandani@gmail.com">&lt;mjethanandani@gmail.com&gt;</=
a>; <a =
href=3D"mailto:yang-doctors@ietf.org">yang-doctors@ietf.org</a><o:p></o:p=
></pre><pre>Cc: <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:teas@ietf.org">teas@ietf.org</a>; <a =
href=3D"mailto:draft-ietf-teas-yang-te-topo.all@ietf.org">draft-ietf-teas=
-yang-te-topo.all@ietf.org</a><o:p></o:p></pre><pre>Subject: Re: [Teas] =
Yangdoctors last call review of =
draft-ietf-teas-yang-te-topo-<o:p></o:p></pre><pre>08<o:p></o:p></pre><pr=
e><o:p>&nbsp;</o:p></pre><pre>Dear draft-ietf-teas-yang-te-topo =
authors,<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>Hi =
Xufeng,<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>OK, by tooling, =
I don't mean the pyang plugins that I have =
been<o:p></o:p></pre><pre>working on to convert between different types =
of models.=C2=A0 As you<o:p></o:p></pre><pre>aware, the TE YANG models =
can easily be converted to NMDA style since<o:p></o:p></pre><pre>I have =
already done it<o:p></o:p></pre><pre>(<a =
href=3D"https://github.com/rgwilton/ietf-models-to-combined">https://gith=
ub.com/rgwilton/ietf-models-to-combined</a>).<o:p></o:p></pre><pre><o:p>&=
nbsp;</o:p></pre><pre>My comment actually relates to the fact the =
structure used by TE YANG<o:p></o:p></pre><pre>modules don't match any =
other YANG modules - they are using their =
own<o:p></o:p></pre><pre>unique style of =
structure.<o:p></o:p></pre></blockquote><pre>This is an important issue =
to resolve.<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre><o:p>&nbsp;</o:p></pr=
e><pre>Today, there are three common styles of =
modules:<o:p></o:p></pre><pre>(1) IETF style split config/state trees =
(e.g. ietf-interfaces).<o:p></o:p></pre><pre>(2) IETF NMDA style =
combined config/state trees (i.e. where all =
IETF<o:p></o:p></pre><pre>modules are heading =
to).<o:p></o:p></pre><pre>(3) OpenConfig style modules with the =
config/state containers<o:p></o:p></pre><pre>immediately above the =
config leaves.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Tooling =
is likely to be optimized to work with these model =
structures,<o:p></o:p></pre><pre>but the TE modules do not fit into any =
of the three styles above.<o:p></o:p></pre><pre>They are a yet another =
OpenConfig-like style, but that is different<o:p></o:p></pre><pre>enough =
that tooling that is designed to work with OpenConfig =
style<o:p></o:p></pre><pre>YANG modules would likely not work with the =
TE YANG =
modules.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Specifically, =
for clients that expecting to work with an =
OpenConfig<o:p></o:p></pre><pre>style YANG module, then if it knows the =
path to config leaf X, then<o:p></o:p></pre><pre>they would expect the =
applied config value to be available at the =
path<o:p></o:p></pre><pre>&quot;../state/X&quot;.=C2=A0 But, this =
doesn't hold for the structure being used in<o:p></o:p></pre><pre>the TE =
YANG models.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>I believe =
strongly that the models being produced by =
organizations<o:p></o:p></pre><pre>should be structures in a consistent =
way, hence why I think that the<o:p></o:p></pre><pre>published standard =
version of the TE YANG modules should =
immediately<o:p></o:p></pre><pre>align to the NMDA =
style.<o:p></o:p></pre></blockquote><pre>Agreed.<o:p></o:p></pre><pre>Her=
e is the OPS and RTG AD message:<o:p></o:p></pre><pre><a =
href=3D"https://www.ietf.org/mail-archive/web/netmod/current/msg18252.htm=
l">https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html</a>=
<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>I understand that the =
I2RS topology YANG modules will be improved to =
the<o:p></o:p></pre><pre>NMDA =
style.<o:p></o:p></pre></blockquote><pre>[Xufeng] The I2RS topology =
model is already NMDA style, but the NMDA models are not immediately =
implementable without NETCONF/RESTCONF protocol update. We will need the =
&quot;-state&quot; module for the I2RS topology model (and for all the =
top-level models) for now. <o:p></o:p></pre></blockquote><p =
class=3DMsoNormal>Adding -state to the Appendix is a =
possibility.<br>&quot;In all cases, the NMDA and non-NMDA modules SHOULD =
be published in the same document, with NMDA modules in the document =
main body and the non-NMDA modules in an Appendix.&quot;<br>See <a =
href=3D"https://www.ietf.org/mail-archive/web/netmod/current/msg18252.htm=
l">https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html</a>=
<br><br><o:p></o:p></p><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>While the NMDA is =
nice, the NMDA discussions have already significantly delayed publishing =
new models, and doing NMDA without staging will further delay the =
process.<o:p></o:p></pre></blockquote><p class=3DMsoNormal>This is not =
solving the important issue brought up by Rob =
Witlon:<o:p></o:p></p><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p class=3DMsoNormal>My =
comment actually relates to the fact the structure used by TE YANG =
modules don't match any other YANG modules - they are using their own =
unique style of structure.<o:p></o:p></p></blockquote><p =
class=3DMsoNormal>Regards, B.<br><br><o:p></o:p></p><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre><o:p>&nbsp;</o:p></pr=
e><pre>Thanks,=C2=A0 Xufeng<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre><o:p>&nbsp;</o:p></pr=
e><pre>Regards, Benoit<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre><o:p>&nbsp;</o:p></pr=
e><pre>Thanks,<o:p></o:p></pre><pre>Rob<o:p></o:p></pre><pre><o:p>&nbsp;<=
/o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>On 22/06/2017 04:16, Xufeng =
Liu wrote:<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>Hi =
Rob,<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>While the tooling =
is very nice to have, especially for writing =
new<o:p></o:p></pre><pre>models or converting models, we do not have to =
use it for every<o:p></o:p></pre><pre>model. It seems not necessary to =
use the tooling on this model for<o:p></o:p></pre><pre>now. We already =
know that we can manually convert it to NMDA style =
if<o:p></o:p></pre><pre>needed.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></p=
re><pre>Thanks,<o:p></o:p></pre><pre>- =
Xufeng<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>-----Original =
Message-----<o:p></o:p></pre><pre>From: Robert Wilton [<a =
href=3D"mailto:rwilton@cisco.com">mailto:rwilton@cisco.com</a>]<o:p></o:p=
></pre><pre>Sent: Wednesday, June 21, 2017 5:34 =
AM<o:p></o:p></pre><pre>To: Xufeng Liu <a =
href=3D"mailto:Xufeng_Liu@jabil.com">&lt;Xufeng_Liu@jabil.com&gt;</a>; =
Mahesh Jethanandani<o:p></o:p></pre><pre><a =
href=3D"mailto:mjethanandani@gmail.com">&lt;mjethanandani@gmail.com&gt;</=
a>; <a =
href=3D"mailto:yang-doctors@ietf.org">yang-doctors@ietf.org</a><o:p></o:p=
></pre><pre>Cc: <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:teas@ietf.org">teas@ietf.org</a>;<o:p></o:p></pre><pre><a =
href=3D"mailto:draft-ietf-teas-yang-te-topo.all@ietf.org">draft-ietf-teas=
-yang-te-topo.all@ietf.org</a><o:p></o:p></pre><pre>Subject: Re: [Teas] =
Yangdoctors last call review =
of<o:p></o:p></pre><pre>draft-ietf-teas-yang-te-topo-<o:p></o:p></pre><pr=
e>08<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Hi =
Xufeng,<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>On 12/06/2017 =
22:28, Xufeng Liu wrote:<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>Hi =
Mahesh,<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Thank you much =
for the review. We have submitted an updated =
draft<o:p></o:p></pre></blockquote><pre>(<a =
href=3D"https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09">http=
s://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09</a>) =
to<o:p></o:p></pre><pre>address these issues. More detailed explanations =
are put below<o:p></o:p></pre><pre>inline.<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>If the responses and =
updates are satisfactory, we are ready for the<o:p></o:p></pre><pre>last =
call.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Best =
regards,<o:p></o:p></pre><pre>- =
Xufeng<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>-----Original =
Message-----<o:p></o:p></pre><pre>From: Mahesh Jethanandani [<a =
href=3D"mailto:mjethanandani@gmail.com">mailto:mjethanandani@gmail.com</a=
>]<o:p></o:p></pre><pre>Sent: Wednesday, May 24, 2017 11:44 =
AM<o:p></o:p></pre><pre>To: <a =
href=3D"mailto:yang-doctors@ietf.org">yang-doctors@ietf.org</a><o:p></o:p=
></pre><pre>Cc: <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:teas@ietf.org">teas@ietf.org</a>;<o:p></o:p></pre><pre><a =
href=3D"mailto:draft-ietf-teas-yang-te-topo.all@ietf.org">draft-ietf-teas=
-yang-te-topo.all@ietf.org</a><o:p></o:p></pre><pre>Subject: Yangdoctors =
last call review =
of<o:p></o:p></pre><pre>draft-ietf-teas-yang-te-topo-08<o:p></o:p></pre><=
pre><o:p>&nbsp;</o:p></pre><pre>Reviewer: Mahesh =
Jethanandani<o:p></o:p></pre><pre>Review result: Ready with =
Issues<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Document =
reviewed: =
draft-ietf-teas-yang-te-topo-08<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></p=
re><pre>Status: Ready with =
Issues<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>I am not an =
expert in Traffic Engineering. This review is =
looking<o:p></o:p></pre><pre>at the draft from a YANG perspective. With =
that said, I have<o:p></o:p></pre><pre>marked it as =
=E2=80=9CReady<o:p></o:p></pre></blockquote></blockquote><pre>with =
Issues=E2=80=9D<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>because of some of =
the points discussed =
below.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Summary:<o:p></o:=
p></pre><pre><o:p>&nbsp;</o:p></pre><pre>This document defines a YANG =
data model for representing,<o:p></o:p></pre><pre>retrieving and =
manipulating TE Topologies. The model serves as =
a<o:p></o:p></pre><pre>base model that other technology specific TE =
Topology models =
can<o:p></o:p></pre></blockquote></blockquote></blockquote></blockquote><=
/blockquote><pre>augment.<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre><o:p>&nbsp;</o:p></pr=
e><pre>Comments:<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Almost =
all the containers in the model are presence containers. =
Is<o:p></o:p></pre><pre>there a reason why they have to be presence =
containers? Note, that<o:p></o:p></pre><pre>presence containers are =
containers whose existence itself<o:p></o:p></pre><pre>represents =
configuration data. What particular configuration =
data<o:p></o:p></pre><pre>is each =
container<o:p></o:p></pre></blockquote></blockquote><pre>representing in =
itself?<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>[Xufeng] Containers =
that use =E2=80=9Cpresence=E2=80=9D =
are:<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 - Container =
=E2=80=9Cunderlay=E2=80=9D<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 o=C2=A0 We have changed 13 occurrences of such containers to =
be<o:p></o:p></pre><pre>not<o:p></o:p></pre></blockquote><pre>presence =
container.<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>=C2=A0=C2=A0=C2=A0 - =
Container =E2=80=9Cte=E2=80=9D under =
augmentation<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 o=C2=A0 =
To indicate that =E2=80=9CTE=E2=80=9D is enabled (configuration =
data)<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 o=C2=A0 Also =
used to do augmentation. The =E2=80=9Cpresence=E2=80=9D statement =
can<o:p></o:p></pre></blockquote><pre>prevent the mandatory child from =
affecting augmented base model.<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>=C2=A0=C2=A0=C2=A0 - =
/nw:networks/nw:network/nw:network-types/te-topology!<o:p></o:p></pre><pr=
e>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 o=C2=A0 A mechanism required by I2RS =
topology model to specify the<o:p></o:p></pre></blockquote><pre>topology =
type.<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>It is difficult to =
co-relate the diagram with the model itself<o:p></o:p></pre><pre>because =
of different terms being used to define different parts =
of<o:p></o:p></pre><pre>the model.<o:p></o:p></pre><pre>There is =
=E2=80=9CTE Topology Model=E2=80=9D and then there is =E2=80=9CGeneric =
TE<o:p></o:p></pre><pre>Topology<o:p></o:p></pre></blockquote></blockquot=
e><pre>Model=E2=80=9D.<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>Are these one and =
the same models? If so, a common term for both<o:p></o:p></pre><pre>of =
them would be helpful.<o:p></o:p></pre></blockquote><pre>[Xufeng] Yes. =
These two terms are the same. Figure 12, Figure =
13,<o:p></o:p></pre><pre>and =
relevant<o:p></o:p></pre></blockquote><pre>descriptions have been =
updated to make the document consistent.<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>There is extensive =
use of groupings in the document. However, not<o:p></o:p></pre><pre>all =
instances of groupings are used multiple number of =
times.<o:p></o:p></pre><pre>Where they are not being repeated, it would =
be better to move the<o:p></o:p></pre><pre>grouping directly where the =
uses statement resides. Case in point<o:p></o:p></pre><pre>the =
grouping<o:p></o:p></pre></blockquote></blockquote><pre>connectivity-labe=
l-restriction-list.<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>[Xufeng] We have =
removed the following =
groupings<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
te-link-augment<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
te-node-augment<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
te-termination-point-augment<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 =
te-topologies-augment<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
 te-topology-augment<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
te-link-state-underlay-attributes<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 =
te-node-state-derived-notification<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0=
=C2=A0 =
=C2=A0te-topology-type<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>T=
he remaining groupings have been kept so that we =
can:<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 - Share the groupings in =
this model<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 - Prepare to be =
shared by a model augmenting this =
model<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 - Prevent a grouping or =
configuration section from being too =
long<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 - Improve =
readability<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>The split between =
config and state containers does not seem to<o:p></o:p></pre><pre>follow =
any particular pattern.<o:p></o:p></pre></blockquote><pre>[Xufeng] The =
pattern is clear:<o:p></o:p></pre><pre>For each manageable entity =
(object), there is a config container<o:p></o:p></pre><pre>and =
state<o:p></o:p></pre></blockquote><pre>container. The configurable =
properties go into the config container<o:p></o:p></pre><pre>and state =
properties go into the state container. Such objects =
are<o:p></o:p></pre><pre>identified by a list item or a presence =
container so that the<o:p></o:p></pre><pre>=E2=80=9Ccreate=E2=80=9D, =
=E2=80=9Cdelete=E2=80=9D, and =
=E2=80=9Cmodify=E2=80=9D<o:p></o:p></pre><pre>operations<o:p></o:p></pre>=
<pre>can be performed on them. The non-presence containers do =
not<o:p></o:p></pre><pre>represent configuration data so they do not =
introduce such objects.<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>It is neither a top =
level split, as is the case with existing =
IETF<o:p></o:p></pre><pre>models,<o:p></o:p></pre></blockquote><pre>[Xufe=
ng] We could not do top level split because the base =
I2RS<o:p></o:p></pre><pre>network<o:p></o:p></pre></blockquote><pre>topol=
ogy model<o:p></o:p></pre><pre>(<a =
href=3D"https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo">ht=
tps://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo</a>-<o:p></o:=
p></pre><pre>12) that we augment does not have the top-level split (for =
its own<o:p></o:p></pre><pre>reasons).<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>nor do they follow =
the OpenConfig style of splitting config and<o:p></o:p></pre><pre>state =
under each relevant leaf,<o:p></o:p></pre></blockquote><pre>[Xufeng] The =
pattern is consistent with this style in =
principle,<o:p></o:p></pre><pre>with =
some<o:p></o:p></pre></blockquote><pre>adjustments to fit to our =
multiple levels of hierarchy.<o:p></o:p></pre><pre>This is effectively a =
new forth style of YANG models that is =
not<o:p></o:p></pre><pre>consistent with any of the three existing =
styles, i.e.:<o:p></o:p></pre><pre>=C2=A0=C2=A0 - Current IETF =
config/state split model style<o:p></o:p></pre><pre>=C2=A0=C2=A0 - NMDA =
combined config/state tree<o:p></o:p></pre><pre>=C2=A0=C2=A0 - =
OpenConfig split config/state containers immediately above =
the<o:p></o:p></pre><pre>config true =
leaves.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Tooling that it =
designed to work with OpenConfig models will =
need<o:p></o:p></pre><pre>customization to work with these TE models =
because the config/state<o:p></o:p></pre><pre>containers will not be =
where the tooling expects them to =
be.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Thanks,<o:p></o:p></=
pre><pre>Rob<o:p></o:p></pre></blockquote></blockquote><pre><o:p>&nbsp;</=
o:p></pre><pre>.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre></blockquote=
></blockquote><pre><o:p>&nbsp;</o:p></pre></blockquote><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_00D1_01D2F35A.9BC52340--



From nobody Sun Jul  2 21:48:17 2017
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BDE8130141; Sun,  2 Jul 2017 21:48:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 NN3zuFMAsdo3; Sun,  2 Jul 2017 21:48:11 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 4225C1293D6; Sun,  2 Jul 2017 21:48:11 -0700 (PDT)
Received: from mb.local (c-73-96-132-59.hsd1.or.comcast.net [73.96.132.59]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id v634m9lv046833 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Mon, 3 Jul 2017 04:48:09 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host c-73-96-132-59.hsd1.or.comcast.net [73.96.132.59] claimed to be mb.local
Subject: Re: PechaKucha presenters for Prague?
To: Aaron Falk <aaron.falk@gmail.com>, ietf@ietf.org, "99attendees@ietf.org" <99attendees@ietf.org>
References: <D53C2422-8C47-4E42-B5AF-9A263FB89730@gmail.com> <DDE016E1-C9B5-4980-9A5D-36D05DBB9736@gmail.com>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <fe378c1c-ebdd-36c4-5325-2bf4d14ec451@bogus.com>
Date: Sun, 2 Jul 2017 21:48:03 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:54.0) Gecko/20100101 Thunderbird/54.0
MIME-Version: 1.0
In-Reply-To: <DDE016E1-C9B5-4980-9A5D-36D05DBB9736@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4d7q65wknaVEBegIv98GJfvAAttJ3Shbc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gjF6MgL7-tysys16UxSh_mgW5LY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jul 2017 04:48:13 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--4d7q65wknaVEBegIv98GJfvAAttJ3Shbc
Content-Type: multipart/mixed; boundary="fuO2rV0eeG74DfNw1Jp3Lx1Tnc5DvVOEK";
 protected-headers="v1"
From: joel jaeggli <joelja@bogus.com>
To: Aaron Falk <aaron.falk@gmail.com>, ietf@ietf.org,
 "99attendees@ietf.org" <99attendees@ietf.org>
Message-ID: <fe378c1c-ebdd-36c4-5325-2bf4d14ec451@bogus.com>
Subject: Re: PechaKucha presenters for Prague?
References: <D53C2422-8C47-4E42-B5AF-9A263FB89730@gmail.com>
 <DDE016E1-C9B5-4980-9A5D-36D05DBB9736@gmail.com>
In-Reply-To: <DDE016E1-C9B5-4980-9A5D-36D05DBB9736@gmail.com>

--fuO2rV0eeG74DfNw1Jp3Lx1Tnc5DvVOEK
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

joelja@bogus.com "IPv6 flow label hashing, threat or menace?"

On 6/29/17 1:42 PM, Aaron Falk wrote:
> I=E2=80=99ve heard from three people, which isn=E2=80=99t sufficient. U=
nless a few more
> people show interest, I=E2=80=99m canceling for Prague.
>=20
> =E2=80=94aaron
>=20
> On 21 Jun 2017, at 18:09, Aaron Falk wrote:
>=20
>     This is a poll for folks who are interested in presenting at a
>     PechaKucha in Prague. The number of folks presenting has declined
>     slightly and I=E2=80=99m contemplating whether holding a session at=
 every
>     IETF meeting is too frequent. If I don=E2=80=99t hear from enough f=
olks
>     we=E2=80=99ll wait until Singapore to do the next one. In other wor=
ds, if
>     you want to give a talk, please send me a note ASAP.
>=20
>     Standard invitation and background info below.
>=20
>     Thanks!
>=20
>     =E2=80=94aaron
>=20
>     -------------------------------------------------------------------=
-----
>=20
>     A Pecha Kucha is a lightning-talk presentation format, originating
>     in Japan, where a speaker presents 20 image-only slides that are
>     each on the screen for 20 seconds and advance automatically. With
>     each talk lasting for 6:40, it has the feature of forcing
>     presentations -- good or bad -- to be focused and brief. This is an=

>     unofficial event. Topics are encouraged to be a IETF-related and
>     satirical or controversial in some way, although not mean-spirited.=

>     Anyone can participate in this social event. Video from the Berlin,=

>     Seoul, and Chicago PKs can be found here <http://snaggletooth.akam.=
ai>.
>=20
>     Format Details:
>=20
>       * Presentation slots are open to all, assigned first come, first
>         served.
>       * To reserve a presentation slot, send a name and title to
>         aaron.falk@gmail.com <mailto:aaron.falk@gmail.com> and receive
>         confirmation.
>       * Presenters must agree to adhere to the Pecha Kucha format (20
>         slides, primarily image-only, automatically advancing every 20
>         seconds).
>       * There are lots of online tutorials and suggestions for how to
>         make a good Pecha Kucha. Here are a few: [1
>         <http://www.pechakucha.org/>], [2
>         <http://blog.indezine.com/2012/05/10-tips-to-create-and-present=
-pecha.html>],
>         [3 <https://catherinecronin.wordpress.com/2012/06/13/pecha-kuch=
a/>].
>=20



--fuO2rV0eeG74DfNw1Jp3Lx1Tnc5DvVOEK--

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

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAllZzIQACgkQ8AA1q7Z/VrKqxwCeJXZlduSoElulQpMG43phj8xf
qGsAn3hvysc2D+ekgt0cLBZivWjMCN0F
=2ZCY
-----END PGP SIGNATURE-----

--4d7q65wknaVEBegIv98GJfvAAttJ3Shbc--


From nobody Mon Jul  3 00:51:27 2017
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B74FC12702E; Mon,  3 Jul 2017 00:51:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.491
X-Spam-Level: 
X-Spam-Status: No, score=-14.491 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=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 NvIaXWO_ZiJO; Mon,  3 Jul 2017 00:51:20 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29AA9129B66; Mon,  3 Jul 2017 00:51:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=48295; q=dns/txt; s=iport; t=1499068279; x=1500277879; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=BFrxjyeKGLOZ4tej5RJYY1JlCJ2XIVWWQG2THDaZYD4=; b=nDdwCI/QATVr9L0cQ1Wjz0aivi7ejQkQbcLlwmdojp/AjcNQ+aHcamV5 0r9xsz3ur4yoUirpDK85ZZqXQSN8aml6udk1+lT3JgdwtHKRQ6wU0uuwK FxBNaD34O/wMqKTNw4Gqu1soePwOBMVkHv17N7Fa2Jd1bNnB6GD49dvDb E=;
X-IronPort-AV: E=Sophos;i="5.40,301,1496102400";  d="scan'208,217";a="654011997"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Jul 2017 07:51:17 +0000
Received: from [10.55.221.37] (ams-bclaise-nitro4.cisco.com [10.55.221.37]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v637pGj5006738; Mon, 3 Jul 2017 07:51:16 GMT
Subject: Re: [Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-08
To: Xufeng Liu <xufeng.liu.ietf@gmail.com>, "'Xufeng Liu'" <Xufeng_Liu@jabil.com>, "'Robert Wilton'" <rwilton@cisco.com>, "'Mahesh Jethanandani'" <mjethanandani@gmail.com>, yang-doctors@ietf.org
Cc: ietf@ietf.org, teas@ietf.org, draft-ietf-teas-yang-te-topo.all@ietf.org
References: <149564066257.28529.12761629961042171907@ietfa.amsl.com> <BN3PR0201MB08670E55FFB5470F338E998DF1CD0@BN3PR0201MB0867.namprd02.prod.outlook.com> <5d4541d3-9426-787d-e02b-9c2dbc3a5400@cisco.com> <BN3PR0201MB0867315F3E88577B9EEF6584F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com> <3a1c319f-0255-b8ee-ecbd-739568c1dc7f@cisco.com> <1ab3a0d8-de3e-1d7c-2967-97b74b1c68a5@cisco.com> <BN3PR0201MB0867664CBDA460C283DC8043F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com> <04b933e2-189a-6fe2-5d24-310167f91b69@cisco.com> <00d001d2f37c$22d3dd10$687b9730$@gmail.com>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <33750275-7900-e3c3-f03f-b516b1f3eaac@cisco.com>
Date: Mon, 3 Jul 2017 09:51:03 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <00d001d2f37c$22d3dd10$687b9730$@gmail.com>
Content-Type: multipart/alternative; boundary="------------29FFFA2DABFAB3113B36E23C"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/v8GAKAtyglYQTX66VDplmQCkKW4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jul 2017 07:51:25 -0000

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

Thank you Xufeng.

Regards, Benoit
>
> An updated revision of the TE topology model has been posted at 
> https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-10.
>
> This new revision now contains the NMDA compliant module and a 
> companion “-state” module, after the I2RS topology model that we 
> augment has been update with a “-state” module.
>
> Now that this issue has been solved, the authors and contributors 
> think that the draft is ready for the last call.
>
> Thanks,
>
> - Xufeng
>
> P.S. Because of the structure changes of the TE topology model, all 
> augmenting models need to be updated. Sorry for the short notice.
>
> *From:*Teas [mailto:teas-bounces@ietf.org] *On Behalf Of *Benoit Claise
> *Sent:* Monday, June 26, 2017 6:46 AM
> *To:* Xufeng Liu <Xufeng_Liu@jabil.com>; Robert Wilton 
> <rwilton@cisco.com>; Mahesh Jethanandani <mjethanandani@gmail.com>; 
> yang-doctors@ietf.org
> *Cc:* Benoit Claise <bclaise@cisco.com>; ietf@ietf.org; teas@ietf.org; 
> draft-ietf-teas-yang-te-topo.all@ietf.org
> *Subject:* Re: [Teas] Yangdoctors last call review of 
> draft-ietf-teas-yang-te-topo-08
>
> Hi Xufeng,
>
>     Hi Benoit,
>
>         -----Original Message-----
>
>         From: Benoit Claise [mailto:bclaise@cisco.com]
>
>         Sent: Thursday, June 22, 2017 6:12 AM
>
>         To: Robert Wilton<rwilton@cisco.com> <mailto:rwilton@cisco.com>; Xufeng Liu<Xufeng_Liu@jabil.com> <mailto:Xufeng_Liu@jabil.com>;
>
>         Mahesh Jethanandani<mjethanandani@gmail.com> <mailto:mjethanandani@gmail.com>;yang-doctors@ietf.org <mailto:yang-doctors@ietf.org>
>
>         Cc:ietf@ietf.org <mailto:ietf@ietf.org>;teas@ietf.org <mailto:teas@ietf.org>;draft-ietf-teas-yang-te-topo.all@ietf.org
>         <mailto:draft-ietf-teas-yang-te-topo.all@ietf.org>
>
>         Subject: Re: [Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-
>
>         08
>
>         Dear draft-ietf-teas-yang-te-topo authors,
>
>             Hi Xufeng,
>
>             OK, by tooling, I don't mean the pyang plugins that I have been
>
>             working on to convert between different types of models.  As you
>
>             aware, the TE YANG models can easily be converted to NMDA style since
>
>             I have already done it
>
>             (https://github.com/rgwilton/ietf-models-to-combined).
>
>             My comment actually relates to the fact the structure used by TE YANG
>
>             modules don't match any other YANG modules - they are using their own
>
>             unique style of structure.
>
>         This is an important issue to resolve.
>
>             Today, there are three common styles of modules:
>
>             (1) IETF style split config/state trees (e.g. ietf-interfaces).
>
>             (2) IETF NMDA style combined config/state trees (i.e. where all IETF
>
>             modules are heading to).
>
>             (3) OpenConfig style modules with the config/state containers
>
>             immediately above the config leaves.
>
>             Tooling is likely to be optimized to work with these model structures,
>
>             but the TE modules do not fit into any of the three styles above.
>
>             They are a yet another OpenConfig-like style, but that is different
>
>             enough that tooling that is designed to work with OpenConfig style
>
>             YANG modules would likely not work with the TE YANG modules.
>
>             Specifically, for clients that expecting to work with an OpenConfig
>
>             style YANG module, then if it knows the path to config leaf X, then
>
>             they would expect the applied config value to be available at the path
>
>             "../state/X".  But, this doesn't hold for the structure being used in
>
>             the TE YANG models.
>
>             I believe strongly that the models being produced by organizations
>
>             should be structures in a consistent way, hence why I think that the
>
>             published standard version of the TE YANG modules should immediately
>
>             align to the NMDA style.
>
>         Agreed.
>
>         Here is the OPS and RTG AD message:
>
>         https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html
>
>         I understand that the I2RS topology YANG modules will be improved to the
>
>         NMDA style.
>
>     [Xufeng] The I2RS topology model is already NMDA style, but the NMDA models are not immediately implementable without NETCONF/RESTCONF protocol update. We will need the "-state" module for the I2RS topology model (and for all the top-level models) for now.
>
> Adding -state to the Appendix is a possibility.
> "In all cases, the NMDA and non-NMDA modules SHOULD be published in 
> the same document, with NMDA modules in the document main body and the 
> non-NMDA modules in an Appendix."
> See https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html
>
>     While the NMDA is nice, the NMDA discussions have already significantly delayed publishing new models, and doing NMDA without staging will further delay the process.
>
> This is not solving the important issue brought up by Rob Witlon:
>
>     My comment actually relates to the fact the structure used by TE
>     YANG modules don't match any other YANG modules - they are using
>     their own unique style of structure.
>
> Regards, B.
>
>     Thanks,  Xufeng
>
>         Regards, Benoit
>
>             Thanks,
>
>             Rob
>
>             On 22/06/2017 04:16, Xufeng Liu wrote:
>
>                 Hi Rob,
>
>                 While the tooling is very nice to have, especially for writing new
>
>                 models or converting models, we do not have to use it for every
>
>                 model. It seems not necessary to use the tooling on this model for
>
>                 now. We already know that we can manually convert it to NMDA style if
>
>                 needed.
>
>                 Thanks,
>
>                 - Xufeng
>
>                     -----Original Message-----
>
>                     From: Robert Wilton [mailto:rwilton@cisco.com]
>
>                     Sent: Wednesday, June 21, 2017 5:34 AM
>
>                     To: Xufeng Liu<Xufeng_Liu@jabil.com> <mailto:Xufeng_Liu@jabil.com>; Mahesh Jethanandani
>
>                     <mjethanandani@gmail.com>
>                     <mailto:mjethanandani@gmail.com>;yang-doctors@ietf.org <mailto:yang-doctors@ietf.org>
>
>                     Cc:ietf@ietf.org <mailto:ietf@ietf.org>;teas@ietf.org <mailto:teas@ietf.org>;
>
>                     draft-ietf-teas-yang-te-topo.all@ietf.org
>                     <mailto:draft-ietf-teas-yang-te-topo.all@ietf.org>
>
>                     Subject: Re: [Teas] Yangdoctors last call review of
>
>                     draft-ietf-teas-yang-te-topo-
>
>                     08
>
>                     Hi Xufeng,
>
>                     On 12/06/2017 22:28, Xufeng Liu wrote:
>
>                         Hi Mahesh,
>
>                         Thank you much for the review. We have submitted an updated draft
>
>                     (https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09) to
>
>                     address these issues. More detailed explanations are put below
>
>                     inline.
>
>                         If the responses and updates are satisfactory, we are ready for the
>
>                         last call.
>
>                         Best regards,
>
>                         - Xufeng
>
>                             -----Original Message-----
>
>                             From: Mahesh Jethanandani [mailto:mjethanandani@gmail.com]
>
>                             Sent: Wednesday, May 24, 2017 11:44 AM
>
>                             To:yang-doctors@ietf.org
>                             <mailto:yang-doctors@ietf.org>
>
>                             Cc:ietf@ietf.org <mailto:ietf@ietf.org>;teas@ietf.org <mailto:teas@ietf.org>;
>
>                             draft-ietf-teas-yang-te-topo.all@ietf.org
>                             <mailto:draft-ietf-teas-yang-te-topo.all@ietf.org>
>
>                             Subject: Yangdoctors last call review of
>
>                             draft-ietf-teas-yang-te-topo-08
>
>                             Reviewer: Mahesh Jethanandani
>
>                             Review result: Ready with Issues
>
>                             Document reviewed: draft-ietf-teas-yang-te-topo-08
>
>                             Status: Ready with Issues
>
>                             I am not an expert in Traffic Engineering. This review is looking
>
>                             at the draft from a YANG perspective. With that said, I have
>
>                             marked it as “Ready
>
>                     with Issues”
>
>                             because of some of the points discussed below.
>
>                             Summary:
>
>                             This document defines a YANG data model for representing,
>
>                             retrieving and manipulating TE Topologies. The model serves as a
>
>                             base model that other technology specific TE Topology models can
>
>         augment.
>
>                             Comments:
>
>                             Almost all the containers in the model are presence containers. Is
>
>                             there a reason why they have to be presence containers? Note, that
>
>                             presence containers are containers whose existence itself
>
>                             represents configuration data. What particular configuration data
>
>                             is each container
>
>                     representing in itself?
>
>                         [Xufeng] Containers that use “presence” are:
>
>                              - Container “underlay”
>
>                                o  We have changed 13 occurrences of such containers to be
>
>                         not
>
>                     presence container.
>
>                              - Container “te” under augmentation
>
>                                o  To indicate that “TE” is enabled (configuration data)
>
>                                o  Also used to do augmentation. The “presence” statement can
>
>                     prevent the mandatory child from affecting augmented base model.
>
>                              - /nw:networks/nw:network/nw:network-types/te-topology!
>
>                                o  A mechanism required by I2RS topology model to specify the
>
>                     topology type.
>
>                             It is difficult to co-relate the diagram with the model itself
>
>                             because of different terms being used to define different parts of
>
>                             the model.
>
>                             There is “TE Topology Model” and then there is “Generic TE
>
>                             Topology
>
>                     Model”.
>
>                             Are these one and the same models? If so, a common term for both
>
>                             of them would be helpful.
>
>                         [Xufeng] Yes. These two terms are the same. Figure 12, Figure 13,
>
>                         and relevant
>
>                     descriptions have been updated to make the document consistent.
>
>                             There is extensive use of groupings in the document. However, not
>
>                             all instances of groupings are used multiple number of times.
>
>                             Where they are not being repeated, it would be better to move the
>
>                             grouping directly where the uses statement resides. Case in point
>
>                             the grouping
>
>                     connectivity-label-restriction-list.
>
>                         [Xufeng] We have removed the following groupings
>
>                                te-link-augment
>
>                                te-node-augment
>
>                                te-termination-point-augment
>
>                                te-topologies-augment
>
>                                te-topology-augment
>
>                                te-link-state-underlay-attributes
>
>                                te-node-state-derived-notification
>
>                                te-topology-type
>
>                         The remaining groupings have been kept so that we can:
>
>                              - Share the groupings in this model
>
>                              - Prepare to be shared by a model augmenting this model
>
>                              - Prevent a grouping or configuration section from being too long
>
>                              - Improve readability
>
>                             The split between config and state containers does not seem to
>
>                             follow any particular pattern.
>
>                         [Xufeng] The pattern is clear:
>
>                         For each manageable entity (object), there is a config container
>
>                         and state
>
>                     container. The configurable properties go into the config container
>
>                     and state properties go into the state container. Such objects are
>
>                     identified by a list item or a presence container so that the
>
>                     “create”, “delete”, and “modify”
>
>                     operations
>
>                     can be performed on them. The non-presence containers do not
>
>                     represent configuration data so they do not introduce such objects.
>
>                             It is neither a top level split, as is the case with existing IETF
>
>                             models,
>
>                         [Xufeng] We could not do top level split because the base I2RS
>
>                         network
>
>                     topology model
>
>                     (https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo-
>
>                     12) that we augment does not have the top-level split (for its own
>
>                     reasons).
>
>                             nor do they follow the OpenConfig style of splitting config and
>
>                             state under each relevant leaf,
>
>                         [Xufeng] The pattern is consistent with this style in principle,
>
>                         with some
>
>                     adjustments to fit to our multiple levels of hierarchy.
>
>                     This is effectively a new forth style of YANG models that is not
>
>                     consistent with any of the three existing styles, i.e.:
>
>                         - Current IETF config/state split model style
>
>                         - NMDA combined config/state tree
>
>                         - OpenConfig split config/state containers immediately above the
>
>                     config true leaves.
>
>                     Tooling that it designed to work with OpenConfig models will need
>
>                     customization to work with these TE models because the config/state
>
>                     containers will not be where the tooling expects them to be.
>
>                     Thanks,
>
>                     Rob
>
>             .
>


--------------29FFFA2DABFAB3113B36E23C
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">
    <div class="moz-cite-prefix">Thank you Xufeng.<br>
      <br>
      Regards, Benoit<br>
    </div>
    <blockquote type="cite"
      cite="mid:00d001d2f37c$22d3dd10$687b9730$@gmail.com">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <meta name="Generator" content="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:DengXian;
	panose-1:3 0 5 9 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@DengXian";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	color:black;}
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";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle21
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri",sans-serif;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@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="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoPlainText">An updated revision of the TE topology
          model has been posted at <a
            href="https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-10"
            moz-do-not-send="true">https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-10</a>.<o:p></o:p></p>
        <p class="MsoPlainText"><o:p> </o:p></p>
        <p class="MsoPlainText">This new revision now contains the NMDA
          compliant module and a companion “-state” module, after the
          I2RS topology model that we augment has been update with a
          “-state” module.<o:p></o:p></p>
        <p class="MsoPlainText"><o:p> </o:p></p>
        <p class="MsoPlainText">Now that this issue has been solved, the
          authors and contributors think that the draft is ready for the
          last call.<o:p></o:p></p>
        <p class="MsoPlainText"><o:p> </o:p></p>
        <p class="MsoPlainText">Thanks,<o:p></o:p></p>
        <p class="MsoPlainText">- Xufeng<o:p></o:p></p>
        <p class="MsoPlainText"><o:p> </o:p></p>
        <p class="MsoPlainText">P.S. Because of the structure changes of
          the TE topology model, all augmenting models need to be
          updated. Sorry for the short notice.<o:p></o:p></p>
        <p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
        <div style="border:none;border-left:solid blue 1.5pt;padding:0in
          0in 0in 4.0pt">
          <div>
            <div style="border:none;border-top:solid #E1E1E1
              1.0pt;padding:3.0pt 0in 0in 0in">
              <p class="MsoNormal"><b><span style="color:windowtext">From:</span></b><span
                  style="color:windowtext"> Teas
                  [<a class="moz-txt-link-freetext" href="mailto:teas-bounces@ietf.org">mailto:teas-bounces@ietf.org</a>] <b>On Behalf Of </b>Benoit
                  Claise<br>
                  <b>Sent:</b> Monday, June 26, 2017 6:46 AM<br>
                  <b>To:</b> Xufeng Liu <a class="moz-txt-link-rfc2396E" href="mailto:Xufeng_Liu@jabil.com">&lt;Xufeng_Liu@jabil.com&gt;</a>;
                  Robert Wilton <a class="moz-txt-link-rfc2396E" href="mailto:rwilton@cisco.com">&lt;rwilton@cisco.com&gt;</a>; Mahesh
                  Jethanandani <a class="moz-txt-link-rfc2396E" href="mailto:mjethanandani@gmail.com">&lt;mjethanandani@gmail.com&gt;</a>;
                  <a class="moz-txt-link-abbreviated" href="mailto:yang-doctors@ietf.org">yang-doctors@ietf.org</a><br>
                  <b>Cc:</b> Benoit Claise <a class="moz-txt-link-rfc2396E" href="mailto:bclaise@cisco.com">&lt;bclaise@cisco.com&gt;</a>;
                  <a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:teas@ietf.org">teas@ietf.org</a>;
                  <a class="moz-txt-link-abbreviated" href="mailto:draft-ietf-teas-yang-te-topo.all@ietf.org">draft-ietf-teas-yang-te-topo.all@ietf.org</a><br>
                  <b>Subject:</b> Re: [Teas] Yangdoctors last call
                  review of draft-ietf-teas-yang-te-topo-08<o:p></o:p></span></p>
            </div>
          </div>
          <p class="MsoNormal"><o:p> </o:p></p>
          <div>
            <p class="MsoNormal">Hi Xufeng,<o:p></o:p></p>
          </div>
          <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
            <pre>Hi Benoit,<o:p></o:p></pre>
            <pre><o:p> </o:p></pre>
            <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
              <pre>-----Original Message-----<o:p></o:p></pre>
              <pre>From: Benoit Claise [<a href="mailto:bclaise@cisco.com" moz-do-not-send="true">mailto:bclaise@cisco.com</a>]<o:p></o:p></pre>
              <pre>Sent: Thursday, June 22, 2017 6:12 AM<o:p></o:p></pre>
              <pre>To: Robert Wilton <a href="mailto:rwilton@cisco.com" moz-do-not-send="true">&lt;rwilton@cisco.com&gt;</a>; Xufeng Liu <a href="mailto:Xufeng_Liu@jabil.com" moz-do-not-send="true">&lt;Xufeng_Liu@jabil.com&gt;</a>;<o:p></o:p></pre>
              <pre>Mahesh Jethanandani <a href="mailto:mjethanandani@gmail.com" moz-do-not-send="true">&lt;mjethanandani@gmail.com&gt;</a>; <a href="mailto:yang-doctors@ietf.org" moz-do-not-send="true">yang-doctors@ietf.org</a><o:p></o:p></pre>
              <pre>Cc: <a href="mailto:ietf@ietf.org" moz-do-not-send="true">ietf@ietf.org</a>; <a href="mailto:teas@ietf.org" moz-do-not-send="true">teas@ietf.org</a>; <a href="mailto:draft-ietf-teas-yang-te-topo.all@ietf.org" moz-do-not-send="true">draft-ietf-teas-yang-te-topo.all@ietf.org</a><o:p></o:p></pre>
              <pre>Subject: Re: [Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-<o:p></o:p></pre>
              <pre>08<o:p></o:p></pre>
              <pre><o:p> </o:p></pre>
              <pre>Dear draft-ietf-teas-yang-te-topo authors,<o:p></o:p></pre>
              <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
                <pre>Hi Xufeng,<o:p></o:p></pre>
                <pre><o:p> </o:p></pre>
                <pre>OK, by tooling, I don't mean the pyang plugins that I have been<o:p></o:p></pre>
                <pre>working on to convert between different types of models.  As you<o:p></o:p></pre>
                <pre>aware, the TE YANG models can easily be converted to NMDA style since<o:p></o:p></pre>
                <pre>I have already done it<o:p></o:p></pre>
                <pre>(<a href="https://github.com/rgwilton/ietf-models-to-combined" moz-do-not-send="true">https://github.com/rgwilton/ietf-models-to-combined</a>).<o:p></o:p></pre>
                <pre><o:p> </o:p></pre>
                <pre>My comment actually relates to the fact the structure used by TE YANG<o:p></o:p></pre>
                <pre>modules don't match any other YANG modules - they are using their own<o:p></o:p></pre>
                <pre>unique style of structure.<o:p></o:p></pre>
              </blockquote>
              <pre>This is an important issue to resolve.<o:p></o:p></pre>
              <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
                <pre><o:p> </o:p></pre>
                <pre>Today, there are three common styles of modules:<o:p></o:p></pre>
                <pre>(1) IETF style split config/state trees (e.g. ietf-interfaces).<o:p></o:p></pre>
                <pre>(2) IETF NMDA style combined config/state trees (i.e. where all IETF<o:p></o:p></pre>
                <pre>modules are heading to).<o:p></o:p></pre>
                <pre>(3) OpenConfig style modules with the config/state containers<o:p></o:p></pre>
                <pre>immediately above the config leaves.<o:p></o:p></pre>
                <pre><o:p> </o:p></pre>
                <pre>Tooling is likely to be optimized to work with these model structures,<o:p></o:p></pre>
                <pre>but the TE modules do not fit into any of the three styles above.<o:p></o:p></pre>
                <pre>They are a yet another OpenConfig-like style, but that is different<o:p></o:p></pre>
                <pre>enough that tooling that is designed to work with OpenConfig style<o:p></o:p></pre>
                <pre>YANG modules would likely not work with the TE YANG modules.<o:p></o:p></pre>
                <pre><o:p> </o:p></pre>
                <pre>Specifically, for clients that expecting to work with an OpenConfig<o:p></o:p></pre>
                <pre>style YANG module, then if it knows the path to config leaf X, then<o:p></o:p></pre>
                <pre>they would expect the applied config value to be available at the path<o:p></o:p></pre>
                <pre>"../state/X".  But, this doesn't hold for the structure being used in<o:p></o:p></pre>
                <pre>the TE YANG models.<o:p></o:p></pre>
                <pre><o:p> </o:p></pre>
                <pre>I believe strongly that the models being produced by organizations<o:p></o:p></pre>
                <pre>should be structures in a consistent way, hence why I think that the<o:p></o:p></pre>
                <pre>published standard version of the TE YANG modules should immediately<o:p></o:p></pre>
                <pre>align to the NMDA style.<o:p></o:p></pre>
              </blockquote>
              <pre>Agreed.<o:p></o:p></pre>
              <pre>Here is the OPS and RTG AD message:<o:p></o:p></pre>
              <pre><a href="https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html" moz-do-not-send="true">https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html</a><o:p></o:p></pre>
              <pre><o:p> </o:p></pre>
              <pre>I understand that the I2RS topology YANG modules will be improved to the<o:p></o:p></pre>
              <pre>NMDA style.<o:p></o:p></pre>
            </blockquote>
            <pre>[Xufeng] The I2RS topology model is already NMDA style, but the NMDA models are not immediately implementable without NETCONF/RESTCONF protocol update. We will need the "-state" module for the I2RS topology model (and for all the top-level models) for now. <o:p></o:p></pre>
          </blockquote>
          <p class="MsoNormal">Adding -state to the Appendix is a
            possibility.<br>
            "In all cases, the NMDA and non-NMDA modules SHOULD be
            published in the same document, with NMDA modules in the
            document main body and the non-NMDA modules in an Appendix."<br>
            See <a
href="https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html"
              moz-do-not-send="true">https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html</a><br>
            <br>
            <o:p></o:p></p>
          <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
            <pre>While the NMDA is nice, the NMDA discussions have already significantly delayed publishing new models, and doing NMDA without staging will further delay the process.<o:p></o:p></pre>
          </blockquote>
          <p class="MsoNormal">This is not solving the important issue
            brought up by Rob Witlon:<o:p></o:p></p>
          <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
            <p class="MsoNormal">My comment actually relates to the fact
              the structure used by TE YANG modules don't match any
              other YANG modules - they are using their own unique style
              of structure.<o:p></o:p></p>
          </blockquote>
          <p class="MsoNormal">Regards, B.<br>
            <br>
            <o:p></o:p></p>
          <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
            <pre><o:p> </o:p></pre>
            <pre>Thanks,  Xufeng<o:p></o:p></pre>
            <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
              <pre><o:p> </o:p></pre>
              <pre>Regards, Benoit<o:p></o:p></pre>
              <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
                <pre><o:p> </o:p></pre>
                <pre>Thanks,<o:p></o:p></pre>
                <pre>Rob<o:p></o:p></pre>
                <pre><o:p> </o:p></pre>
                <pre><o:p> </o:p></pre>
                <pre>On 22/06/2017 04:16, Xufeng Liu wrote:<o:p></o:p></pre>
                <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
                  <pre>Hi Rob,<o:p></o:p></pre>
                  <pre><o:p> </o:p></pre>
                  <pre>While the tooling is very nice to have, especially for writing new<o:p></o:p></pre>
                  <pre>models or converting models, we do not have to use it for every<o:p></o:p></pre>
                  <pre>model. It seems not necessary to use the tooling on this model for<o:p></o:p></pre>
                  <pre>now. We already know that we can manually convert it to NMDA style if<o:p></o:p></pre>
                  <pre>needed.<o:p></o:p></pre>
                  <pre><o:p> </o:p></pre>
                  <pre>Thanks,<o:p></o:p></pre>
                  <pre>- Xufeng<o:p></o:p></pre>
                  <pre><o:p> </o:p></pre>
                  <blockquote
                    style="margin-top:5.0pt;margin-bottom:5.0pt">
                    <pre>-----Original Message-----<o:p></o:p></pre>
                    <pre>From: Robert Wilton [<a href="mailto:rwilton@cisco.com" moz-do-not-send="true">mailto:rwilton@cisco.com</a>]<o:p></o:p></pre>
                    <pre>Sent: Wednesday, June 21, 2017 5:34 AM<o:p></o:p></pre>
                    <pre>To: Xufeng Liu <a href="mailto:Xufeng_Liu@jabil.com" moz-do-not-send="true">&lt;Xufeng_Liu@jabil.com&gt;</a>; Mahesh Jethanandani<o:p></o:p></pre>
                    <pre><a href="mailto:mjethanandani@gmail.com" moz-do-not-send="true">&lt;mjethanandani@gmail.com&gt;</a>; <a href="mailto:yang-doctors@ietf.org" moz-do-not-send="true">yang-doctors@ietf.org</a><o:p></o:p></pre>
                    <pre>Cc: <a href="mailto:ietf@ietf.org" moz-do-not-send="true">ietf@ietf.org</a>; <a href="mailto:teas@ietf.org" moz-do-not-send="true">teas@ietf.org</a>;<o:p></o:p></pre>
                    <pre><a href="mailto:draft-ietf-teas-yang-te-topo.all@ietf.org" moz-do-not-send="true">draft-ietf-teas-yang-te-topo.all@ietf.org</a><o:p></o:p></pre>
                    <pre>Subject: Re: [Teas] Yangdoctors last call review of<o:p></o:p></pre>
                    <pre>draft-ietf-teas-yang-te-topo-<o:p></o:p></pre>
                    <pre>08<o:p></o:p></pre>
                    <pre><o:p> </o:p></pre>
                    <pre>Hi Xufeng,<o:p></o:p></pre>
                    <pre><o:p> </o:p></pre>
                    <pre>On 12/06/2017 22:28, Xufeng Liu wrote:<o:p></o:p></pre>
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <pre>Hi Mahesh,<o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <pre>Thank you much for the review. We have submitted an updated draft<o:p></o:p></pre>
                    </blockquote>
                    <pre>(<a href="https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09" moz-do-not-send="true">https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09</a>) to<o:p></o:p></pre>
                    <pre>address these issues. More detailed explanations are put below<o:p></o:p></pre>
                    <pre>inline.<o:p></o:p></pre>
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <pre>If the responses and updates are satisfactory, we are ready for the<o:p></o:p></pre>
                      <pre>last call.<o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <pre>Best regards,<o:p></o:p></pre>
                      <pre>- Xufeng<o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <blockquote
                        style="margin-top:5.0pt;margin-bottom:5.0pt">
                        <pre>-----Original Message-----<o:p></o:p></pre>
                        <pre>From: Mahesh Jethanandani [<a href="mailto:mjethanandani@gmail.com" moz-do-not-send="true">mailto:mjethanandani@gmail.com</a>]<o:p></o:p></pre>
                        <pre>Sent: Wednesday, May 24, 2017 11:44 AM<o:p></o:p></pre>
                        <pre>To: <a href="mailto:yang-doctors@ietf.org" moz-do-not-send="true">yang-doctors@ietf.org</a><o:p></o:p></pre>
                        <pre>Cc: <a href="mailto:ietf@ietf.org" moz-do-not-send="true">ietf@ietf.org</a>; <a href="mailto:teas@ietf.org" moz-do-not-send="true">teas@ietf.org</a>;<o:p></o:p></pre>
                        <pre><a href="mailto:draft-ietf-teas-yang-te-topo.all@ietf.org" moz-do-not-send="true">draft-ietf-teas-yang-te-topo.all@ietf.org</a><o:p></o:p></pre>
                        <pre>Subject: Yangdoctors last call review of<o:p></o:p></pre>
                        <pre>draft-ietf-teas-yang-te-topo-08<o:p></o:p></pre>
                        <pre><o:p> </o:p></pre>
                        <pre>Reviewer: Mahesh Jethanandani<o:p></o:p></pre>
                        <pre>Review result: Ready with Issues<o:p></o:p></pre>
                        <pre><o:p> </o:p></pre>
                        <pre>Document reviewed: draft-ietf-teas-yang-te-topo-08<o:p></o:p></pre>
                        <pre><o:p> </o:p></pre>
                        <pre>Status: Ready with Issues<o:p></o:p></pre>
                        <pre><o:p> </o:p></pre>
                        <pre>I am not an expert in Traffic Engineering. This review is looking<o:p></o:p></pre>
                        <pre>at the draft from a YANG perspective. With that said, I have<o:p></o:p></pre>
                        <pre>marked it as “Ready<o:p></o:p></pre>
                      </blockquote>
                    </blockquote>
                    <pre>with Issues”<o:p></o:p></pre>
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <blockquote
                        style="margin-top:5.0pt;margin-bottom:5.0pt">
                        <pre>because of some of the points discussed below.<o:p></o:p></pre>
                        <pre><o:p> </o:p></pre>
                        <pre>Summary:<o:p></o:p></pre>
                        <pre><o:p> </o:p></pre>
                        <pre>This document defines a YANG data model for representing,<o:p></o:p></pre>
                        <pre>retrieving and manipulating TE Topologies. The model serves as a<o:p></o:p></pre>
                        <pre>base model that other technology specific TE Topology models can<o:p></o:p></pre>
                      </blockquote>
                    </blockquote>
                  </blockquote>
                </blockquote>
              </blockquote>
              <pre>augment.<o:p></o:p></pre>
              <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
                <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
                  <blockquote
                    style="margin-top:5.0pt;margin-bottom:5.0pt">
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <blockquote
                        style="margin-top:5.0pt;margin-bottom:5.0pt">
                        <pre><o:p> </o:p></pre>
                        <pre>Comments:<o:p></o:p></pre>
                        <pre><o:p> </o:p></pre>
                        <pre>Almost all the containers in the model are presence containers. Is<o:p></o:p></pre>
                        <pre>there a reason why they have to be presence containers? Note, that<o:p></o:p></pre>
                        <pre>presence containers are containers whose existence itself<o:p></o:p></pre>
                        <pre>represents configuration data. What particular configuration data<o:p></o:p></pre>
                        <pre>is each container<o:p></o:p></pre>
                      </blockquote>
                    </blockquote>
                    <pre>representing in itself?<o:p></o:p></pre>
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <pre>[Xufeng] Containers that use “presence” are:<o:p></o:p></pre>
                      <pre>    - Container “underlay”<o:p></o:p></pre>
                      <pre>      o  We have changed 13 occurrences of such containers to be<o:p></o:p></pre>
                      <pre>not<o:p></o:p></pre>
                    </blockquote>
                    <pre>presence container.<o:p></o:p></pre>
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <pre>    - Container “te” under augmentation<o:p></o:p></pre>
                      <pre>      o  To indicate that “TE” is enabled (configuration data)<o:p></o:p></pre>
                      <pre>      o  Also used to do augmentation. The “presence” statement can<o:p></o:p></pre>
                    </blockquote>
                    <pre>prevent the mandatory child from affecting augmented base model.<o:p></o:p></pre>
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <pre>    - /nw:networks/nw:network/nw:network-types/te-topology!<o:p></o:p></pre>
                      <pre>      o  A mechanism required by I2RS topology model to specify the<o:p></o:p></pre>
                    </blockquote>
                    <pre>topology type.<o:p></o:p></pre>
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <blockquote
                        style="margin-top:5.0pt;margin-bottom:5.0pt">
                        <pre>It is difficult to co-relate the diagram with the model itself<o:p></o:p></pre>
                        <pre>because of different terms being used to define different parts of<o:p></o:p></pre>
                        <pre>the model.<o:p></o:p></pre>
                        <pre>There is “TE Topology Model” and then there is “Generic TE<o:p></o:p></pre>
                        <pre>Topology<o:p></o:p></pre>
                      </blockquote>
                    </blockquote>
                    <pre>Model”.<o:p></o:p></pre>
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <blockquote
                        style="margin-top:5.0pt;margin-bottom:5.0pt">
                        <pre>Are these one and the same models? If so, a common term for both<o:p></o:p></pre>
                        <pre>of them would be helpful.<o:p></o:p></pre>
                      </blockquote>
                      <pre>[Xufeng] Yes. These two terms are the same. Figure 12, Figure 13,<o:p></o:p></pre>
                      <pre>and relevant<o:p></o:p></pre>
                    </blockquote>
                    <pre>descriptions have been updated to make the document consistent.<o:p></o:p></pre>
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <blockquote
                        style="margin-top:5.0pt;margin-bottom:5.0pt">
                        <pre>There is extensive use of groupings in the document. However, not<o:p></o:p></pre>
                        <pre>all instances of groupings are used multiple number of times.<o:p></o:p></pre>
                        <pre>Where they are not being repeated, it would be better to move the<o:p></o:p></pre>
                        <pre>grouping directly where the uses statement resides. Case in point<o:p></o:p></pre>
                        <pre>the grouping<o:p></o:p></pre>
                      </blockquote>
                    </blockquote>
                    <pre>connectivity-label-restriction-list.<o:p></o:p></pre>
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <pre>[Xufeng] We have removed the following groupings<o:p></o:p></pre>
                      <pre>      te-link-augment<o:p></o:p></pre>
                      <pre>      te-node-augment<o:p></o:p></pre>
                      <pre>      te-termination-point-augment<o:p></o:p></pre>
                      <pre>      te-topologies-augment<o:p></o:p></pre>
                      <pre>      te-topology-augment<o:p></o:p></pre>
                      <pre>      te-link-state-underlay-attributes<o:p></o:p></pre>
                      <pre>      te-node-state-derived-notification<o:p></o:p></pre>
                      <pre>      te-topology-type<o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <pre>The remaining groupings have been kept so that we can:<o:p></o:p></pre>
                      <pre>    - Share the groupings in this model<o:p></o:p></pre>
                      <pre>    - Prepare to be shared by a model augmenting this model<o:p></o:p></pre>
                      <pre>    - Prevent a grouping or configuration section from being too long<o:p></o:p></pre>
                      <pre>    - Improve readability<o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <blockquote
                        style="margin-top:5.0pt;margin-bottom:5.0pt">
                        <pre>The split between config and state containers does not seem to<o:p></o:p></pre>
                        <pre>follow any particular pattern.<o:p></o:p></pre>
                      </blockquote>
                      <pre>[Xufeng] The pattern is clear:<o:p></o:p></pre>
                      <pre>For each manageable entity (object), there is a config container<o:p></o:p></pre>
                      <pre>and state<o:p></o:p></pre>
                    </blockquote>
                    <pre>container. The configurable properties go into the config container<o:p></o:p></pre>
                    <pre>and state properties go into the state container. Such objects are<o:p></o:p></pre>
                    <pre>identified by a list item or a presence container so that the<o:p></o:p></pre>
                    <pre>“create”, “delete”, and “modify”<o:p></o:p></pre>
                    <pre>operations<o:p></o:p></pre>
                    <pre>can be performed on them. The non-presence containers do not<o:p></o:p></pre>
                    <pre>represent configuration data so they do not introduce such objects.<o:p></o:p></pre>
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <blockquote
                        style="margin-top:5.0pt;margin-bottom:5.0pt">
                        <pre>It is neither a top level split, as is the case with existing IETF<o:p></o:p></pre>
                        <pre>models,<o:p></o:p></pre>
                      </blockquote>
                      <pre>[Xufeng] We could not do top level split because the base I2RS<o:p></o:p></pre>
                      <pre>network<o:p></o:p></pre>
                    </blockquote>
                    <pre>topology model<o:p></o:p></pre>
                    <pre>(<a href="https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo" moz-do-not-send="true">https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo</a>-<o:p></o:p></pre>
                    <pre>12) that we augment does not have the top-level split (for its own<o:p></o:p></pre>
                    <pre>reasons).<o:p></o:p></pre>
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <blockquote
                        style="margin-top:5.0pt;margin-bottom:5.0pt">
                        <pre>nor do they follow the OpenConfig style of splitting config and<o:p></o:p></pre>
                        <pre>state under each relevant leaf,<o:p></o:p></pre>
                      </blockquote>
                      <pre>[Xufeng] The pattern is consistent with this style in principle,<o:p></o:p></pre>
                      <pre>with some<o:p></o:p></pre>
                    </blockquote>
                    <pre>adjustments to fit to our multiple levels of hierarchy.<o:p></o:p></pre>
                    <pre>This is effectively a new forth style of YANG models that is not<o:p></o:p></pre>
                    <pre>consistent with any of the three existing styles, i.e.:<o:p></o:p></pre>
                    <pre>   - Current IETF config/state split model style<o:p></o:p></pre>
                    <pre>   - NMDA combined config/state tree<o:p></o:p></pre>
                    <pre>   - OpenConfig split config/state containers immediately above the<o:p></o:p></pre>
                    <pre>config true leaves.<o:p></o:p></pre>
                    <pre><o:p> </o:p></pre>
                    <pre>Tooling that it designed to work with OpenConfig models will need<o:p></o:p></pre>
                    <pre>customization to work with these TE models because the config/state<o:p></o:p></pre>
                    <pre>containers will not be where the tooling expects them to be.<o:p></o:p></pre>
                    <pre><o:p> </o:p></pre>
                    <pre>Thanks,<o:p></o:p></pre>
                    <pre>Rob<o:p></o:p></pre>
                  </blockquote>
                </blockquote>
                <pre><o:p> </o:p></pre>
                <pre>.<o:p></o:p></pre>
                <pre><o:p> </o:p></pre>
              </blockquote>
            </blockquote>
            <pre><o:p> </o:p></pre>
          </blockquote>
          <p class="MsoNormal"><o:p> </o:p></p>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------29FFFA2DABFAB3113B36E23C--


From nobody Mon Jul  3 02:13:09 2017
Return-Path: <rwilton@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82447131467; Mon,  3 Jul 2017 02:13:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.491
X-Spam-Level: 
X-Spam-Status: No, score=-14.491 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=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 4FPgvPO3ljjV; Mon,  3 Jul 2017 02:12:58 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7F7012EC15; Mon,  3 Jul 2017 02:12:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=49424; q=dns/txt; s=iport; t=1499073177; x=1500282777; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=o6kD3fgfGKb+4UYxLggaU+qMJL4A7iHb+ylzYPtNsho=; b=WIJ8MRqJcmPFt7va+ppR51PFvXjmC+seL6nDLKZyp7isLLUb7PlGbSNW XKohsIvNGlTotIVox3UPuo7JZnQ81ryfsybOleDymivx2kBs+zibq/UJ+ sT8RbtnuiFTK90SOzadX84vpY7VyPgUlJbmVWxhPanz+oVxf30pbB9/Xi c=;
X-IronPort-AV: E=Sophos;i="5.40,302,1496102400";  d="scan'208,217";a="695558047"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Jul 2017 09:12:54 +0000
Received: from [10.63.23.55] (dhcp-ensft1-uk-vla370-10-63-23-55.cisco.com [10.63.23.55]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v639CsOo006580; Mon, 3 Jul 2017 09:12:54 GMT
Subject: Re: [Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-08
To: Xufeng Liu <xufeng.liu.ietf@gmail.com>, "'Benoit Claise'" <bclaise@cisco.com>, "'Xufeng Liu'" <Xufeng_Liu@jabil.com>, "'Mahesh Jethanandani'" <mjethanandani@gmail.com>, yang-doctors@ietf.org
References: <149564066257.28529.12761629961042171907@ietfa.amsl.com> <BN3PR0201MB08670E55FFB5470F338E998DF1CD0@BN3PR0201MB0867.namprd02.prod.outlook.com> <5d4541d3-9426-787d-e02b-9c2dbc3a5400@cisco.com> <BN3PR0201MB0867315F3E88577B9EEF6584F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com> <3a1c319f-0255-b8ee-ecbd-739568c1dc7f@cisco.com> <1ab3a0d8-de3e-1d7c-2967-97b74b1c68a5@cisco.com> <BN3PR0201MB0867664CBDA460C283DC8043F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com> <04b933e2-189a-6fe2-5d24-310167f91b69@cisco.com> <00d001d2f37c$22d3dd10$687b9730$@gmail.com>
Cc: ietf@ietf.org, teas@ietf.org, draft-ietf-teas-yang-te-topo.all@ietf.org
From: Robert Wilton <rwilton@cisco.com>
Message-ID: <a83f8acd-2c14-2d28-f196-96b5fd7833a9@cisco.com>
Date: Mon, 3 Jul 2017 10:12:54 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <00d001d2f37c$22d3dd10$687b9730$@gmail.com>
Content-Type: multipart/alternative; boundary="------------383B54D0E68C2CD834EE07C9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qDrxItg6ZuFgg-oPE6SRxIcC0jI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jul 2017 09:13:03 -0000

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

Hi Xufeng,

Thanks for updating the modules to be NMDA compliant.  I think that 
getting structural consistency across the IETF YANG modules will make 
them far more compelling as a solution.

I noticed that some of the snippets of YANG tree output in the draft 
still illustrate using the "split oc-style config/state structure" and 
hence also need to be updated.  Probably this could be done as part of 
the WG LC.

To find the instances, just search the draft for "rw config" and "ro state".

Thanks,
Rob


On 02/07/2017 22:42, Xufeng Liu wrote:
>
> An updated revision of the TE topology model has been posted at 
> https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-10.
>
> This new revision now contains the NMDA compliant module and a 
> companion “-state” module, after the I2RS topology model that we 
> augment has been update with a “-state” module.
>
> Now that this issue has been solved, the authors and contributors 
> think that the draft is ready for the last call.
>
> Thanks,
>
> - Xufeng
>
> P.S. Because of the structure changes of the TE topology model, all 
> augmenting models need to be updated. Sorry for the short notice.
>
> *From:*Teas [mailto:teas-bounces@ietf.org] *On Behalf Of *Benoit Claise
> *Sent:* Monday, June 26, 2017 6:46 AM
> *To:* Xufeng Liu <Xufeng_Liu@jabil.com>; Robert Wilton 
> <rwilton@cisco.com>; Mahesh Jethanandani <mjethanandani@gmail.com>; 
> yang-doctors@ietf.org
> *Cc:* Benoit Claise <bclaise@cisco.com>; ietf@ietf.org; teas@ietf.org; 
> draft-ietf-teas-yang-te-topo.all@ietf.org
> *Subject:* Re: [Teas] Yangdoctors last call review of 
> draft-ietf-teas-yang-te-topo-08
>
> Hi Xufeng,
>
>     Hi Benoit,
>
>         -----Original Message-----
>
>         From: Benoit Claise [mailto:bclaise@cisco.com]
>
>         Sent: Thursday, June 22, 2017 6:12 AM
>
>         To: Robert Wilton<rwilton@cisco.com> <mailto:rwilton@cisco.com>; Xufeng Liu<Xufeng_Liu@jabil.com> <mailto:Xufeng_Liu@jabil.com>;
>
>         Mahesh Jethanandani<mjethanandani@gmail.com> <mailto:mjethanandani@gmail.com>;yang-doctors@ietf.org <mailto:yang-doctors@ietf.org>
>
>         Cc:ietf@ietf.org <mailto:ietf@ietf.org>;teas@ietf.org <mailto:teas@ietf.org>;draft-ietf-teas-yang-te-topo.all@ietf.org
>         <mailto:draft-ietf-teas-yang-te-topo.all@ietf.org>
>
>         Subject: Re: [Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-
>
>         08
>
>         Dear draft-ietf-teas-yang-te-topo authors,
>
>             Hi Xufeng,
>
>             OK, by tooling, I don't mean the pyang plugins that I have been
>
>             working on to convert between different types of models.  As you
>
>             aware, the TE YANG models can easily be converted to NMDA style since
>
>             I have already done it
>
>             (https://github.com/rgwilton/ietf-models-to-combined).
>
>             My comment actually relates to the fact the structure used by TE YANG
>
>             modules don't match any other YANG modules - they are using their own
>
>             unique style of structure.
>
>         This is an important issue to resolve.
>
>             Today, there are three common styles of modules:
>
>             (1) IETF style split config/state trees (e.g. ietf-interfaces).
>
>             (2) IETF NMDA style combined config/state trees (i.e. where all IETF
>
>             modules are heading to).
>
>             (3) OpenConfig style modules with the config/state containers
>
>             immediately above the config leaves.
>
>             Tooling is likely to be optimized to work with these model structures,
>
>             but the TE modules do not fit into any of the three styles above.
>
>             They are a yet another OpenConfig-like style, but that is different
>
>             enough that tooling that is designed to work with OpenConfig style
>
>             YANG modules would likely not work with the TE YANG modules.
>
>             Specifically, for clients that expecting to work with an OpenConfig
>
>             style YANG module, then if it knows the path to config leaf X, then
>
>             they would expect the applied config value to be available at the path
>
>             "../state/X".  But, this doesn't hold for the structure being used in
>
>             the TE YANG models.
>
>             I believe strongly that the models being produced by organizations
>
>             should be structures in a consistent way, hence why I think that the
>
>             published standard version of the TE YANG modules should immediately
>
>             align to the NMDA style.
>
>         Agreed.
>
>         Here is the OPS and RTG AD message:
>
>         https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html
>
>         I understand that the I2RS topology YANG modules will be improved to the
>
>         NMDA style.
>
>     [Xufeng] The I2RS topology model is already NMDA style, but the NMDA models are not immediately implementable without NETCONF/RESTCONF protocol update. We will need the "-state" module for the I2RS topology model (and for all the top-level models) for now.
>
> Adding -state to the Appendix is a possibility.
> "In all cases, the NMDA and non-NMDA modules SHOULD be published in 
> the same document, with NMDA modules in the document main body and the 
> non-NMDA modules in an Appendix."
> See https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html
>
>     While the NMDA is nice, the NMDA discussions have already significantly delayed publishing new models, and doing NMDA without staging will further delay the process.
>
> This is not solving the important issue brought up by Rob Witlon:
>
>     My comment actually relates to the fact the structure used by TE
>     YANG modules don't match any other YANG modules - they are using
>     their own unique style of structure.
>
> Regards, B.
>
>     Thanks,  Xufeng
>
>         Regards, Benoit
>
>             Thanks,
>
>             Rob
>
>             On 22/06/2017 04:16, Xufeng Liu wrote:
>
>                 Hi Rob,
>
>                 While the tooling is very nice to have, especially for writing new
>
>                 models or converting models, we do not have to use it for every
>
>                 model. It seems not necessary to use the tooling on this model for
>
>                 now. We already know that we can manually convert it to NMDA style if
>
>                 needed.
>
>                 Thanks,
>
>                 - Xufeng
>
>                     -----Original Message-----
>
>                     From: Robert Wilton [mailto:rwilton@cisco.com]
>
>                     Sent: Wednesday, June 21, 2017 5:34 AM
>
>                     To: Xufeng Liu<Xufeng_Liu@jabil.com> <mailto:Xufeng_Liu@jabil.com>; Mahesh Jethanandani
>
>                     <mjethanandani@gmail.com>
>                     <mailto:mjethanandani@gmail.com>;yang-doctors@ietf.org <mailto:yang-doctors@ietf.org>
>
>                     Cc:ietf@ietf.org <mailto:ietf@ietf.org>;teas@ietf.org <mailto:teas@ietf.org>;
>
>                     draft-ietf-teas-yang-te-topo.all@ietf.org
>                     <mailto:draft-ietf-teas-yang-te-topo.all@ietf.org>
>
>                     Subject: Re: [Teas] Yangdoctors last call review of
>
>                     draft-ietf-teas-yang-te-topo-
>
>                     08
>
>                     Hi Xufeng,
>
>                     On 12/06/2017 22:28, Xufeng Liu wrote:
>
>                         Hi Mahesh,
>
>                         Thank you much for the review. We have submitted an updated draft
>
>                     (https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09) to
>
>                     address these issues. More detailed explanations are put below
>
>                     inline.
>
>                         If the responses and updates are satisfactory, we are ready for the
>
>                         last call.
>
>                         Best regards,
>
>                         - Xufeng
>
>                             -----Original Message-----
>
>                             From: Mahesh Jethanandani [mailto:mjethanandani@gmail.com]
>
>                             Sent: Wednesday, May 24, 2017 11:44 AM
>
>                             To:yang-doctors@ietf.org
>                             <mailto:yang-doctors@ietf.org>
>
>                             Cc:ietf@ietf.org <mailto:ietf@ietf.org>;teas@ietf.org <mailto:teas@ietf.org>;
>
>                             draft-ietf-teas-yang-te-topo.all@ietf.org
>                             <mailto:draft-ietf-teas-yang-te-topo.all@ietf.org>
>
>                             Subject: Yangdoctors last call review of
>
>                             draft-ietf-teas-yang-te-topo-08
>
>                             Reviewer: Mahesh Jethanandani
>
>                             Review result: Ready with Issues
>
>                             Document reviewed: draft-ietf-teas-yang-te-topo-08
>
>                             Status: Ready with Issues
>
>                             I am not an expert in Traffic Engineering. This review is looking
>
>                             at the draft from a YANG perspective. With that said, I have
>
>                             marked it as “Ready
>
>                     with Issues”
>
>                             because of some of the points discussed below.
>
>                             Summary:
>
>                             This document defines a YANG data model for representing,
>
>                             retrieving and manipulating TE Topologies. The model serves as a
>
>                             base model that other technology specific TE Topology models can
>
>         augment.
>
>                             Comments:
>
>                             Almost all the containers in the model are presence containers. Is
>
>                             there a reason why they have to be presence containers? Note, that
>
>                             presence containers are containers whose existence itself
>
>                             represents configuration data. What particular configuration data
>
>                             is each container
>
>                     representing in itself?
>
>                         [Xufeng] Containers that use “presence” are:
>
>                              - Container “underlay”
>
>                                o  We have changed 13 occurrences of such containers to be
>
>                         not
>
>                     presence container.
>
>                              - Container “te” under augmentation
>
>                                o  To indicate that “TE” is enabled (configuration data)
>
>                                o  Also used to do augmentation. The “presence” statement can
>
>                     prevent the mandatory child from affecting augmented base model.
>
>                              - /nw:networks/nw:network/nw:network-types/te-topology!
>
>                                o  A mechanism required by I2RS topology model to specify the
>
>                     topology type.
>
>                             It is difficult to co-relate the diagram with the model itself
>
>                             because of different terms being used to define different parts of
>
>                             the model.
>
>                             There is “TE Topology Model” and then there is “Generic TE
>
>                             Topology
>
>                     Model”.
>
>                             Are these one and the same models? If so, a common term for both
>
>                             of them would be helpful.
>
>                         [Xufeng] Yes. These two terms are the same. Figure 12, Figure 13,
>
>                         and relevant
>
>                     descriptions have been updated to make the document consistent.
>
>                             There is extensive use of groupings in the document. However, not
>
>                             all instances of groupings are used multiple number of times.
>
>                             Where they are not being repeated, it would be better to move the
>
>                             grouping directly where the uses statement resides. Case in point
>
>                             the grouping
>
>                     connectivity-label-restriction-list.
>
>                         [Xufeng] We have removed the following groupings
>
>                                te-link-augment
>
>                                te-node-augment
>
>                                te-termination-point-augment
>
>                                te-topologies-augment
>
>                                te-topology-augment
>
>                                te-link-state-underlay-attributes
>
>                                te-node-state-derived-notification
>
>                                te-topology-type
>
>                         The remaining groupings have been kept so that we can:
>
>                              - Share the groupings in this model
>
>                              - Prepare to be shared by a model augmenting this model
>
>                              - Prevent a grouping or configuration section from being too long
>
>                              - Improve readability
>
>                             The split between config and state containers does not seem to
>
>                             follow any particular pattern.
>
>                         [Xufeng] The pattern is clear:
>
>                         For each manageable entity (object), there is a config container
>
>                         and state
>
>                     container. The configurable properties go into the config container
>
>                     and state properties go into the state container. Such objects are
>
>                     identified by a list item or a presence container so that the
>
>                     “create”, “delete”, and “modify”
>
>                     operations
>
>                     can be performed on them. The non-presence containers do not
>
>                     represent configuration data so they do not introduce such objects.
>
>                             It is neither a top level split, as is the case with existing IETF
>
>                             models,
>
>                         [Xufeng] We could not do top level split because the base I2RS
>
>                         network
>
>                     topology model
>
>                     (https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo-
>
>                     12) that we augment does not have the top-level split (for its own
>
>                     reasons).
>
>                             nor do they follow the OpenConfig style of splitting config and
>
>                             state under each relevant leaf,
>
>                         [Xufeng] The pattern is consistent with this style in principle,
>
>                         with some
>
>                     adjustments to fit to our multiple levels of hierarchy.
>
>                     This is effectively a new forth style of YANG models that is not
>
>                     consistent with any of the three existing styles, i.e.:
>
>                         - Current IETF config/state split model style
>
>                         - NMDA combined config/state tree
>
>                         - OpenConfig split config/state containers immediately above the
>
>                     config true leaves.
>
>                     Tooling that it designed to work with OpenConfig models will need
>
>                     customization to work with these TE models because the config/state
>
>                     containers will not be where the tooling expects them to be.
>
>                     Thanks,
>
>                     Rob
>
>             .
>


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

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>Hi Xufeng,</p>
    <p>Thanks for updating the modules to be NMDA compliant.  I think
      that getting structural consistency across the IETF YANG modules
      will make them far more compelling as a solution.<br>
    </p>
    <p>I noticed that some of the snippets of YANG tree output in the
      draft still illustrate using the "split oc-style config/state
      structure" and hence also need to be updated.  Probably this could
      be done as part of the WG LC.</p>
    <p>To find the instances, just search the draft for "rw config" and
      "ro state".</p>
    <p>Thanks,<br>
      Rob<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 02/07/2017 22:42, Xufeng Liu wrote:<br>
    </div>
    <blockquote cite="mid:00d001d2f37c$22d3dd10$687b9730$@gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <meta name="Generator" content="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:DengXian;
	panose-1:3 0 5 9 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@DengXian";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	color:black;}
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";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle21
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri",sans-serif;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@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="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoPlainText">An updated revision of the TE topology
          model has been posted at <a moz-do-not-send="true"
            href="https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-10">https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-10</a>.<o:p></o:p></p>
        <p class="MsoPlainText"><o:p> </o:p></p>
        <p class="MsoPlainText">This new revision now contains the NMDA
          compliant module and a companion “-state” module, after the
          I2RS topology model that we augment has been update with a
          “-state” module.<o:p></o:p></p>
        <p class="MsoPlainText"><o:p> </o:p></p>
        <p class="MsoPlainText">Now that this issue has been solved, the
          authors and contributors think that the draft is ready for the
          last call.<o:p></o:p></p>
        <p class="MsoPlainText"><o:p> </o:p></p>
        <p class="MsoPlainText">Thanks,<o:p></o:p></p>
        <p class="MsoPlainText">- Xufeng<o:p></o:p></p>
        <p class="MsoPlainText"><o:p> </o:p></p>
        <p class="MsoPlainText">P.S. Because of the structure changes of
          the TE topology model, all augmenting models need to be
          updated. Sorry for the short notice.<o:p></o:p></p>
        <p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
        <div style="border:none;border-left:solid blue 1.5pt;padding:0in
          0in 0in 4.0pt">
          <div>
            <div style="border:none;border-top:solid #E1E1E1
              1.0pt;padding:3.0pt 0in 0in 0in">
              <p class="MsoNormal"><b><span style="color:windowtext">From:</span></b><span
                  style="color:windowtext"> Teas
                  [<a class="moz-txt-link-freetext" href="mailto:teas-bounces@ietf.org">mailto:teas-bounces@ietf.org</a>] <b>On Behalf Of </b>Benoit
                  Claise<br>
                  <b>Sent:</b> Monday, June 26, 2017 6:46 AM<br>
                  <b>To:</b> Xufeng Liu <a class="moz-txt-link-rfc2396E" href="mailto:Xufeng_Liu@jabil.com">&lt;Xufeng_Liu@jabil.com&gt;</a>;
                  Robert Wilton <a class="moz-txt-link-rfc2396E" href="mailto:rwilton@cisco.com">&lt;rwilton@cisco.com&gt;</a>; Mahesh
                  Jethanandani <a class="moz-txt-link-rfc2396E" href="mailto:mjethanandani@gmail.com">&lt;mjethanandani@gmail.com&gt;</a>;
                  <a class="moz-txt-link-abbreviated" href="mailto:yang-doctors@ietf.org">yang-doctors@ietf.org</a><br>
                  <b>Cc:</b> Benoit Claise <a class="moz-txt-link-rfc2396E" href="mailto:bclaise@cisco.com">&lt;bclaise@cisco.com&gt;</a>;
                  <a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:teas@ietf.org">teas@ietf.org</a>;
                  <a class="moz-txt-link-abbreviated" href="mailto:draft-ietf-teas-yang-te-topo.all@ietf.org">draft-ietf-teas-yang-te-topo.all@ietf.org</a><br>
                  <b>Subject:</b> Re: [Teas] Yangdoctors last call
                  review of draft-ietf-teas-yang-te-topo-08<o:p></o:p></span></p>
            </div>
          </div>
          <p class="MsoNormal"><o:p> </o:p></p>
          <div>
            <p class="MsoNormal">Hi Xufeng,<o:p></o:p></p>
          </div>
          <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
            <pre>Hi Benoit,<o:p></o:p></pre>
            <pre><o:p> </o:p></pre>
            <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
              <pre>-----Original Message-----<o:p></o:p></pre>
              <pre>From: Benoit Claise [<a moz-do-not-send="true" href="mailto:bclaise@cisco.com">mailto:bclaise@cisco.com</a>]<o:p></o:p></pre>
              <pre>Sent: Thursday, June 22, 2017 6:12 AM<o:p></o:p></pre>
              <pre>To: Robert Wilton <a moz-do-not-send="true" href="mailto:rwilton@cisco.com">&lt;rwilton@cisco.com&gt;</a>; Xufeng Liu <a moz-do-not-send="true" href="mailto:Xufeng_Liu@jabil.com">&lt;Xufeng_Liu@jabil.com&gt;</a>;<o:p></o:p></pre>
              <pre>Mahesh Jethanandani <a moz-do-not-send="true" href="mailto:mjethanandani@gmail.com">&lt;mjethanandani@gmail.com&gt;</a>; <a moz-do-not-send="true" href="mailto:yang-doctors@ietf.org">yang-doctors@ietf.org</a><o:p></o:p></pre>
              <pre>Cc: <a moz-do-not-send="true" href="mailto:ietf@ietf.org">ietf@ietf.org</a>; <a moz-do-not-send="true" href="mailto:teas@ietf.org">teas@ietf.org</a>; <a moz-do-not-send="true" href="mailto:draft-ietf-teas-yang-te-topo.all@ietf.org">draft-ietf-teas-yang-te-topo.all@ietf.org</a><o:p></o:p></pre>
              <pre>Subject: Re: [Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-<o:p></o:p></pre>
              <pre>08<o:p></o:p></pre>
              <pre><o:p> </o:p></pre>
              <pre>Dear draft-ietf-teas-yang-te-topo authors,<o:p></o:p></pre>
              <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
                <pre>Hi Xufeng,<o:p></o:p></pre>
                <pre><o:p> </o:p></pre>
                <pre>OK, by tooling, I don't mean the pyang plugins that I have been<o:p></o:p></pre>
                <pre>working on to convert between different types of models.  As you<o:p></o:p></pre>
                <pre>aware, the TE YANG models can easily be converted to NMDA style since<o:p></o:p></pre>
                <pre>I have already done it<o:p></o:p></pre>
                <pre>(<a moz-do-not-send="true" href="https://github.com/rgwilton/ietf-models-to-combined">https://github.com/rgwilton/ietf-models-to-combined</a>).<o:p></o:p></pre>
                <pre><o:p> </o:p></pre>
                <pre>My comment actually relates to the fact the structure used by TE YANG<o:p></o:p></pre>
                <pre>modules don't match any other YANG modules - they are using their own<o:p></o:p></pre>
                <pre>unique style of structure.<o:p></o:p></pre>
              </blockquote>
              <pre>This is an important issue to resolve.<o:p></o:p></pre>
              <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
                <pre><o:p> </o:p></pre>
                <pre>Today, there are three common styles of modules:<o:p></o:p></pre>
                <pre>(1) IETF style split config/state trees (e.g. ietf-interfaces).<o:p></o:p></pre>
                <pre>(2) IETF NMDA style combined config/state trees (i.e. where all IETF<o:p></o:p></pre>
                <pre>modules are heading to).<o:p></o:p></pre>
                <pre>(3) OpenConfig style modules with the config/state containers<o:p></o:p></pre>
                <pre>immediately above the config leaves.<o:p></o:p></pre>
                <pre><o:p> </o:p></pre>
                <pre>Tooling is likely to be optimized to work with these model structures,<o:p></o:p></pre>
                <pre>but the TE modules do not fit into any of the three styles above.<o:p></o:p></pre>
                <pre>They are a yet another OpenConfig-like style, but that is different<o:p></o:p></pre>
                <pre>enough that tooling that is designed to work with OpenConfig style<o:p></o:p></pre>
                <pre>YANG modules would likely not work with the TE YANG modules.<o:p></o:p></pre>
                <pre><o:p> </o:p></pre>
                <pre>Specifically, for clients that expecting to work with an OpenConfig<o:p></o:p></pre>
                <pre>style YANG module, then if it knows the path to config leaf X, then<o:p></o:p></pre>
                <pre>they would expect the applied config value to be available at the path<o:p></o:p></pre>
                <pre>"../state/X".  But, this doesn't hold for the structure being used in<o:p></o:p></pre>
                <pre>the TE YANG models.<o:p></o:p></pre>
                <pre><o:p> </o:p></pre>
                <pre>I believe strongly that the models being produced by organizations<o:p></o:p></pre>
                <pre>should be structures in a consistent way, hence why I think that the<o:p></o:p></pre>
                <pre>published standard version of the TE YANG modules should immediately<o:p></o:p></pre>
                <pre>align to the NMDA style.<o:p></o:p></pre>
              </blockquote>
              <pre>Agreed.<o:p></o:p></pre>
              <pre>Here is the OPS and RTG AD message:<o:p></o:p></pre>
              <pre><a moz-do-not-send="true" href="https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html">https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html</a><o:p></o:p></pre>
              <pre><o:p> </o:p></pre>
              <pre>I understand that the I2RS topology YANG modules will be improved to the<o:p></o:p></pre>
              <pre>NMDA style.<o:p></o:p></pre>
            </blockquote>
            <pre>[Xufeng] The I2RS topology model is already NMDA style, but the NMDA models are not immediately implementable without NETCONF/RESTCONF protocol update. We will need the "-state" module for the I2RS topology model (and for all the top-level models) for now. <o:p></o:p></pre>
          </blockquote>
          <p class="MsoNormal">Adding -state to the Appendix is a
            possibility.<br>
            "In all cases, the NMDA and non-NMDA modules SHOULD be
            published in the same document, with NMDA modules in the
            document main body and the non-NMDA modules in an Appendix."<br>
            See <a moz-do-not-send="true"
href="https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html">https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html</a><br>
            <br>
            <o:p></o:p></p>
          <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
            <pre>While the NMDA is nice, the NMDA discussions have already significantly delayed publishing new models, and doing NMDA without staging will further delay the process.<o:p></o:p></pre>
          </blockquote>
          <p class="MsoNormal">This is not solving the important issue
            brought up by Rob Witlon:<o:p></o:p></p>
          <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
            <p class="MsoNormal">My comment actually relates to the fact
              the structure used by TE YANG modules don't match any
              other YANG modules - they are using their own unique style
              of structure.<o:p></o:p></p>
          </blockquote>
          <p class="MsoNormal">Regards, B.<br>
            <br>
            <o:p></o:p></p>
          <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
            <pre><o:p> </o:p></pre>
            <pre>Thanks,  Xufeng<o:p></o:p></pre>
            <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
              <pre><o:p> </o:p></pre>
              <pre>Regards, Benoit<o:p></o:p></pre>
              <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
                <pre><o:p> </o:p></pre>
                <pre>Thanks,<o:p></o:p></pre>
                <pre>Rob<o:p></o:p></pre>
                <pre><o:p> </o:p></pre>
                <pre><o:p> </o:p></pre>
                <pre>On 22/06/2017 04:16, Xufeng Liu wrote:<o:p></o:p></pre>
                <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
                  <pre>Hi Rob,<o:p></o:p></pre>
                  <pre><o:p> </o:p></pre>
                  <pre>While the tooling is very nice to have, especially for writing new<o:p></o:p></pre>
                  <pre>models or converting models, we do not have to use it for every<o:p></o:p></pre>
                  <pre>model. It seems not necessary to use the tooling on this model for<o:p></o:p></pre>
                  <pre>now. We already know that we can manually convert it to NMDA style if<o:p></o:p></pre>
                  <pre>needed.<o:p></o:p></pre>
                  <pre><o:p> </o:p></pre>
                  <pre>Thanks,<o:p></o:p></pre>
                  <pre>- Xufeng<o:p></o:p></pre>
                  <pre><o:p> </o:p></pre>
                  <blockquote
                    style="margin-top:5.0pt;margin-bottom:5.0pt">
                    <pre>-----Original Message-----<o:p></o:p></pre>
                    <pre>From: Robert Wilton [<a moz-do-not-send="true" href="mailto:rwilton@cisco.com">mailto:rwilton@cisco.com</a>]<o:p></o:p></pre>
                    <pre>Sent: Wednesday, June 21, 2017 5:34 AM<o:p></o:p></pre>
                    <pre>To: Xufeng Liu <a moz-do-not-send="true" href="mailto:Xufeng_Liu@jabil.com">&lt;Xufeng_Liu@jabil.com&gt;</a>; Mahesh Jethanandani<o:p></o:p></pre>
                    <pre><a moz-do-not-send="true" href="mailto:mjethanandani@gmail.com">&lt;mjethanandani@gmail.com&gt;</a>; <a moz-do-not-send="true" href="mailto:yang-doctors@ietf.org">yang-doctors@ietf.org</a><o:p></o:p></pre>
                    <pre>Cc: <a moz-do-not-send="true" href="mailto:ietf@ietf.org">ietf@ietf.org</a>; <a moz-do-not-send="true" href="mailto:teas@ietf.org">teas@ietf.org</a>;<o:p></o:p></pre>
                    <pre><a moz-do-not-send="true" href="mailto:draft-ietf-teas-yang-te-topo.all@ietf.org">draft-ietf-teas-yang-te-topo.all@ietf.org</a><o:p></o:p></pre>
                    <pre>Subject: Re: [Teas] Yangdoctors last call review of<o:p></o:p></pre>
                    <pre>draft-ietf-teas-yang-te-topo-<o:p></o:p></pre>
                    <pre>08<o:p></o:p></pre>
                    <pre><o:p> </o:p></pre>
                    <pre>Hi Xufeng,<o:p></o:p></pre>
                    <pre><o:p> </o:p></pre>
                    <pre>On 12/06/2017 22:28, Xufeng Liu wrote:<o:p></o:p></pre>
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <pre>Hi Mahesh,<o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <pre>Thank you much for the review. We have submitted an updated draft<o:p></o:p></pre>
                    </blockquote>
                    <pre>(<a moz-do-not-send="true" href="https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09">https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09</a>) to<o:p></o:p></pre>
                    <pre>address these issues. More detailed explanations are put below<o:p></o:p></pre>
                    <pre>inline.<o:p></o:p></pre>
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <pre>If the responses and updates are satisfactory, we are ready for the<o:p></o:p></pre>
                      <pre>last call.<o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <pre>Best regards,<o:p></o:p></pre>
                      <pre>- Xufeng<o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <blockquote
                        style="margin-top:5.0pt;margin-bottom:5.0pt">
                        <pre>-----Original Message-----<o:p></o:p></pre>
                        <pre>From: Mahesh Jethanandani [<a moz-do-not-send="true" href="mailto:mjethanandani@gmail.com">mailto:mjethanandani@gmail.com</a>]<o:p></o:p></pre>
                        <pre>Sent: Wednesday, May 24, 2017 11:44 AM<o:p></o:p></pre>
                        <pre>To: <a moz-do-not-send="true" href="mailto:yang-doctors@ietf.org">yang-doctors@ietf.org</a><o:p></o:p></pre>
                        <pre>Cc: <a moz-do-not-send="true" href="mailto:ietf@ietf.org">ietf@ietf.org</a>; <a moz-do-not-send="true" href="mailto:teas@ietf.org">teas@ietf.org</a>;<o:p></o:p></pre>
                        <pre><a moz-do-not-send="true" href="mailto:draft-ietf-teas-yang-te-topo.all@ietf.org">draft-ietf-teas-yang-te-topo.all@ietf.org</a><o:p></o:p></pre>
                        <pre>Subject: Yangdoctors last call review of<o:p></o:p></pre>
                        <pre>draft-ietf-teas-yang-te-topo-08<o:p></o:p></pre>
                        <pre><o:p> </o:p></pre>
                        <pre>Reviewer: Mahesh Jethanandani<o:p></o:p></pre>
                        <pre>Review result: Ready with Issues<o:p></o:p></pre>
                        <pre><o:p> </o:p></pre>
                        <pre>Document reviewed: draft-ietf-teas-yang-te-topo-08<o:p></o:p></pre>
                        <pre><o:p> </o:p></pre>
                        <pre>Status: Ready with Issues<o:p></o:p></pre>
                        <pre><o:p> </o:p></pre>
                        <pre>I am not an expert in Traffic Engineering. This review is looking<o:p></o:p></pre>
                        <pre>at the draft from a YANG perspective. With that said, I have<o:p></o:p></pre>
                        <pre>marked it as “Ready<o:p></o:p></pre>
                      </blockquote>
                    </blockquote>
                    <pre>with Issues”<o:p></o:p></pre>
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <blockquote
                        style="margin-top:5.0pt;margin-bottom:5.0pt">
                        <pre>because of some of the points discussed below.<o:p></o:p></pre>
                        <pre><o:p> </o:p></pre>
                        <pre>Summary:<o:p></o:p></pre>
                        <pre><o:p> </o:p></pre>
                        <pre>This document defines a YANG data model for representing,<o:p></o:p></pre>
                        <pre>retrieving and manipulating TE Topologies. The model serves as a<o:p></o:p></pre>
                        <pre>base model that other technology specific TE Topology models can<o:p></o:p></pre>
                      </blockquote>
                    </blockquote>
                  </blockquote>
                </blockquote>
              </blockquote>
              <pre>augment.<o:p></o:p></pre>
              <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
                <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
                  <blockquote
                    style="margin-top:5.0pt;margin-bottom:5.0pt">
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <blockquote
                        style="margin-top:5.0pt;margin-bottom:5.0pt">
                        <pre><o:p> </o:p></pre>
                        <pre>Comments:<o:p></o:p></pre>
                        <pre><o:p> </o:p></pre>
                        <pre>Almost all the containers in the model are presence containers. Is<o:p></o:p></pre>
                        <pre>there a reason why they have to be presence containers? Note, that<o:p></o:p></pre>
                        <pre>presence containers are containers whose existence itself<o:p></o:p></pre>
                        <pre>represents configuration data. What particular configuration data<o:p></o:p></pre>
                        <pre>is each container<o:p></o:p></pre>
                      </blockquote>
                    </blockquote>
                    <pre>representing in itself?<o:p></o:p></pre>
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <pre>[Xufeng] Containers that use “presence” are:<o:p></o:p></pre>
                      <pre>    - Container “underlay”<o:p></o:p></pre>
                      <pre>      o  We have changed 13 occurrences of such containers to be<o:p></o:p></pre>
                      <pre>not<o:p></o:p></pre>
                    </blockquote>
                    <pre>presence container.<o:p></o:p></pre>
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <pre>    - Container “te” under augmentation<o:p></o:p></pre>
                      <pre>      o  To indicate that “TE” is enabled (configuration data)<o:p></o:p></pre>
                      <pre>      o  Also used to do augmentation. The “presence” statement can<o:p></o:p></pre>
                    </blockquote>
                    <pre>prevent the mandatory child from affecting augmented base model.<o:p></o:p></pre>
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <pre>    - /nw:networks/nw:network/nw:network-types/te-topology!<o:p></o:p></pre>
                      <pre>      o  A mechanism required by I2RS topology model to specify the<o:p></o:p></pre>
                    </blockquote>
                    <pre>topology type.<o:p></o:p></pre>
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <blockquote
                        style="margin-top:5.0pt;margin-bottom:5.0pt">
                        <pre>It is difficult to co-relate the diagram with the model itself<o:p></o:p></pre>
                        <pre>because of different terms being used to define different parts of<o:p></o:p></pre>
                        <pre>the model.<o:p></o:p></pre>
                        <pre>There is “TE Topology Model” and then there is “Generic TE<o:p></o:p></pre>
                        <pre>Topology<o:p></o:p></pre>
                      </blockquote>
                    </blockquote>
                    <pre>Model”.<o:p></o:p></pre>
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <blockquote
                        style="margin-top:5.0pt;margin-bottom:5.0pt">
                        <pre>Are these one and the same models? If so, a common term for both<o:p></o:p></pre>
                        <pre>of them would be helpful.<o:p></o:p></pre>
                      </blockquote>
                      <pre>[Xufeng] Yes. These two terms are the same. Figure 12, Figure 13,<o:p></o:p></pre>
                      <pre>and relevant<o:p></o:p></pre>
                    </blockquote>
                    <pre>descriptions have been updated to make the document consistent.<o:p></o:p></pre>
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <blockquote
                        style="margin-top:5.0pt;margin-bottom:5.0pt">
                        <pre>There is extensive use of groupings in the document. However, not<o:p></o:p></pre>
                        <pre>all instances of groupings are used multiple number of times.<o:p></o:p></pre>
                        <pre>Where they are not being repeated, it would be better to move the<o:p></o:p></pre>
                        <pre>grouping directly where the uses statement resides. Case in point<o:p></o:p></pre>
                        <pre>the grouping<o:p></o:p></pre>
                      </blockquote>
                    </blockquote>
                    <pre>connectivity-label-restriction-list.<o:p></o:p></pre>
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <pre>[Xufeng] We have removed the following groupings<o:p></o:p></pre>
                      <pre>      te-link-augment<o:p></o:p></pre>
                      <pre>      te-node-augment<o:p></o:p></pre>
                      <pre>      te-termination-point-augment<o:p></o:p></pre>
                      <pre>      te-topologies-augment<o:p></o:p></pre>
                      <pre>      te-topology-augment<o:p></o:p></pre>
                      <pre>      te-link-state-underlay-attributes<o:p></o:p></pre>
                      <pre>      te-node-state-derived-notification<o:p></o:p></pre>
                      <pre>      te-topology-type<o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <pre>The remaining groupings have been kept so that we can:<o:p></o:p></pre>
                      <pre>    - Share the groupings in this model<o:p></o:p></pre>
                      <pre>    - Prepare to be shared by a model augmenting this model<o:p></o:p></pre>
                      <pre>    - Prevent a grouping or configuration section from being too long<o:p></o:p></pre>
                      <pre>    - Improve readability<o:p></o:p></pre>
                      <pre><o:p> </o:p></pre>
                      <blockquote
                        style="margin-top:5.0pt;margin-bottom:5.0pt">
                        <pre>The split between config and state containers does not seem to<o:p></o:p></pre>
                        <pre>follow any particular pattern.<o:p></o:p></pre>
                      </blockquote>
                      <pre>[Xufeng] The pattern is clear:<o:p></o:p></pre>
                      <pre>For each manageable entity (object), there is a config container<o:p></o:p></pre>
                      <pre>and state<o:p></o:p></pre>
                    </blockquote>
                    <pre>container. The configurable properties go into the config container<o:p></o:p></pre>
                    <pre>and state properties go into the state container. Such objects are<o:p></o:p></pre>
                    <pre>identified by a list item or a presence container so that the<o:p></o:p></pre>
                    <pre>“create”, “delete”, and “modify”<o:p></o:p></pre>
                    <pre>operations<o:p></o:p></pre>
                    <pre>can be performed on them. The non-presence containers do not<o:p></o:p></pre>
                    <pre>represent configuration data so they do not introduce such objects.<o:p></o:p></pre>
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <blockquote
                        style="margin-top:5.0pt;margin-bottom:5.0pt">
                        <pre>It is neither a top level split, as is the case with existing IETF<o:p></o:p></pre>
                        <pre>models,<o:p></o:p></pre>
                      </blockquote>
                      <pre>[Xufeng] We could not do top level split because the base I2RS<o:p></o:p></pre>
                      <pre>network<o:p></o:p></pre>
                    </blockquote>
                    <pre>topology model<o:p></o:p></pre>
                    <pre>(<a moz-do-not-send="true" href="https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo">https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo</a>-<o:p></o:p></pre>
                    <pre>12) that we augment does not have the top-level split (for its own<o:p></o:p></pre>
                    <pre>reasons).<o:p></o:p></pre>
                    <blockquote
                      style="margin-top:5.0pt;margin-bottom:5.0pt">
                      <blockquote
                        style="margin-top:5.0pt;margin-bottom:5.0pt">
                        <pre>nor do they follow the OpenConfig style of splitting config and<o:p></o:p></pre>
                        <pre>state under each relevant leaf,<o:p></o:p></pre>
                      </blockquote>
                      <pre>[Xufeng] The pattern is consistent with this style in principle,<o:p></o:p></pre>
                      <pre>with some<o:p></o:p></pre>
                    </blockquote>
                    <pre>adjustments to fit to our multiple levels of hierarchy.<o:p></o:p></pre>
                    <pre>This is effectively a new forth style of YANG models that is not<o:p></o:p></pre>
                    <pre>consistent with any of the three existing styles, i.e.:<o:p></o:p></pre>
                    <pre>   - Current IETF config/state split model style<o:p></o:p></pre>
                    <pre>   - NMDA combined config/state tree<o:p></o:p></pre>
                    <pre>   - OpenConfig split config/state containers immediately above the<o:p></o:p></pre>
                    <pre>config true leaves.<o:p></o:p></pre>
                    <pre><o:p> </o:p></pre>
                    <pre>Tooling that it designed to work with OpenConfig models will need<o:p></o:p></pre>
                    <pre>customization to work with these TE models because the config/state<o:p></o:p></pre>
                    <pre>containers will not be where the tooling expects them to be.<o:p></o:p></pre>
                    <pre><o:p> </o:p></pre>
                    <pre>Thanks,<o:p></o:p></pre>
                    <pre>Rob<o:p></o:p></pre>
                  </blockquote>
                </blockquote>
                <pre><o:p> </o:p></pre>
                <pre>.<o:p></o:p></pre>
                <pre><o:p> </o:p></pre>
              </blockquote>
            </blockquote>
            <pre><o:p> </o:p></pre>
          </blockquote>
          <p class="MsoNormal"><o:p> </o:p></p>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------383B54D0E68C2CD834EE07C9--


From nobody Mon Jul  3 05:45:23 2017
Return-Path: <tjw.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F0DB1315F6; Mon,  3 Jul 2017 05:45:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level: 
X-Spam-Status: No, score=-1.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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 PU_upijtiOa3; Mon,  3 Jul 2017 05:45:20 -0700 (PDT)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::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 80C001315F7; Mon,  3 Jul 2017 05:45:19 -0700 (PDT)
Received: by mail-wm0-x22f.google.com with SMTP id f67so53703204wmh.1; Mon, 03 Jul 2017 05:45:19 -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=ME4ckjWUC1dhAtGK8hDRCq1ZF1WeXoEuFYbSHbjB3zE=; b=CLNam3Gdz/+YQTlmMiNUvTPCpztqqjwrP6ijhsA3RbNY/bUStYQM1sb0FJaruCtI3m +Zun24sga2Ml+ZpxnBlhbfygPh4SXDJGv/KZUI3rR4KsHieDk7JEw6A3+pLd1a3x3HhJ UiKmQ1TfeqoKqeFomIPeLyjvTW8Wiqj4ziWXNII3cBmJqPOcujoHgp1AkYqUVecpdw3G YeMSA+c3B6bS1rhfV+N4EsL4AKie3twJR1rZ8SPJzfiF2eZ08o1zXNgdQsy9bMSfkCQ3 AgM4YYucm2HPHjjqg83SwUGa0pvhXxmDU1NuV+oi3OT3WUyoSwUeZcLVo8GKbMREGwHu NEjw==
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=ME4ckjWUC1dhAtGK8hDRCq1ZF1WeXoEuFYbSHbjB3zE=; b=oENYuPm2mNeoMg9Mo0VTKPNK7rMDZusjMqIysLtFBRbwUssYqtbs+JsDl6KsLSv4Yj ulMtvhfELA/EK6ubjdM4XzH+eOhfMjFCjtIt5G8NKDr7S4giTpI2qMDaBAU1BrfzFcYN TW/fU6ptaDacw3DxW19OqV3eH//69FYe7IUefusb+XPIUCOyQPgmsy0JOW4QgibRl69u wF9o9EIy8e22fYn1DOnbadIWx/S5bTSw3XJ4zQNRbpvP/ht7fUF30MZugpJdahYIACkL Kw2siPIiuQ22qiAEVgc86hRK22amBKT5+eP03dIq/ZWd18cK8KXU8l8sDnJwZ5Ma1ffn DKRA==
X-Gm-Message-State: AKS2vOzgomESbKtMESAjWevROd7QA65yFs7XzM1N5vGu4qBXAMIcnH4G uQbGXdVJ7iD+nbpilOg1X2KLcf+3PA==
X-Received: by 10.28.35.201 with SMTP id j192mr15596660wmj.103.1499085917216;  Mon, 03 Jul 2017 05:45:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.170.152 with HTTP; Mon, 3 Jul 2017 05:45:16 -0700 (PDT)
In-Reply-To: <fe378c1c-ebdd-36c4-5325-2bf4d14ec451@bogus.com>
References: <D53C2422-8C47-4E42-B5AF-9A263FB89730@gmail.com> <DDE016E1-C9B5-4980-9A5D-36D05DBB9736@gmail.com> <fe378c1c-ebdd-36c4-5325-2bf4d14ec451@bogus.com>
From: tjw ietf <tjw.ietf@gmail.com>
Date: Mon, 3 Jul 2017 08:45:16 -0400
Message-ID: <CADyWQ+G3zG4XV867EY-KoDXYwJWF2P_V2_2pQD6=C2FHQCgQaA@mail.gmail.com>
Subject: Re: PechaKucha presenters for Prague?
To: joel jaeggli <joelja@bogus.com>
Cc: Aaron Falk <aaron.falk@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>,  "99attendees@ietf.org" <99attendees@ietf.org>
Content-Type: multipart/alternative; boundary="001a113eab429566c205536923b0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bGv8rWFx9ovQQDgQXeIuSI7jQFE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jul 2017 12:45:21 -0000

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

"My Time on the I=C3=87ANN NomCom - Greatest Time or The Greatest Time?"



On Mon, Jul 3, 2017 at 12:48 AM, joel jaeggli <joelja@bogus.com> wrote:

> joelja@bogus.com "IPv6 flow label hashing, threat or menace?"
>
> On 6/29/17 1:42 PM, Aaron Falk wrote:
> > I=E2=80=99ve heard from three people, which isn=E2=80=99t sufficient. U=
nless a few more
> > people show interest, I=E2=80=99m canceling for Prague.
> >
> > =E2=80=94aaron
> >
> > On 21 Jun 2017, at 18:09, Aaron Falk wrote:
> >
> >     This is a poll for folks who are interested in presenting at a
> >     PechaKucha in Prague. The number of folks presenting has declined
> >     slightly and I=E2=80=99m contemplating whether holding a session at=
 every
> >     IETF meeting is too frequent. If I don=E2=80=99t hear from enough f=
olks
> >     we=E2=80=99ll wait until Singapore to do the next one. In other wor=
ds, if
> >     you want to give a talk, please send me a note ASAP.
> >
> >     Standard invitation and background info below.
> >
> >     Thanks!
> >
> >     =E2=80=94aaron
> >
> >     ------------------------------------------------------------
> ------------
> >
> >     A Pecha Kucha is a lightning-talk presentation format, originating
> >     in Japan, where a speaker presents 20 image-only slides that are
> >     each on the screen for 20 seconds and advance automatically. With
> >     each talk lasting for 6:40, it has the feature of forcing
> >     presentations -- good or bad -- to be focused and brief. This is an
> >     unofficial event. Topics are encouraged to be a IETF-related and
> >     satirical or controversial in some way, although not mean-spirited.
> >     Anyone can participate in this social event. Video from the Berlin,
> >     Seoul, and Chicago PKs can be found here <
> http://snaggletooth.akam.ai>.
> >
> >     Format Details:
> >
> >       * Presentation slots are open to all, assigned first come, first
> >         served.
> >       * To reserve a presentation slot, send a name and title to
> >         aaron.falk@gmail.com <mailto:aaron.falk@gmail.com> and receive
> >         confirmation.
> >       * Presenters must agree to adhere to the Pecha Kucha format (20
> >         slides, primarily image-only, automatically advancing every 20
> >         seconds).
> >       * There are lots of online tutorials and suggestions for how to
> >         make a good Pecha Kucha. Here are a few: [1
> >         <http://www.pechakucha.org/>], [2
> >         <http://blog.indezine.com/2012/05/10-tips-to-create-and-
> present-pecha.html>],
> >         [3 <https://catherinecronin.wordpress.com/2012/06/13/
> pecha-kucha/>].
> >
>
>
>

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

<div dir=3D"ltr">&quot;My Time on the I=C3=87ANN NomCom - Greatest Time or =
The Greatest Time?&quot;<div><br></div><div><br></div></div><div class=3D"g=
mail_extra"><br><div class=3D"gmail_quote">On Mon, Jul 3, 2017 at 12:48 AM,=
 joel jaeggli <span dir=3D"ltr">&lt;<a href=3D"mailto:joelja@bogus.com" tar=
get=3D"_blank">joelja@bogus.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><a href=3D"mailto:joelja@bogus.com">joelja@bogus.com</a> &quo=
t;IPv6 flow label hashing, threat or menace?&quot;<br>
<br>
On 6/29/17 1:42 PM, Aaron Falk wrote:<br>
&gt; I=E2=80=99ve heard from three people, which isn=E2=80=99t sufficient. =
Unless a few more<br>
&gt; people show interest, I=E2=80=99m canceling for Prague.<br>
&gt;<br>
&gt; =E2=80=94aaron<br>
&gt;<br>
&gt; On 21 Jun 2017, at 18:09, Aaron Falk wrote:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0This is a poll for folks who are interested in pres=
enting at a<br>
&gt;=C2=A0 =C2=A0 =C2=A0PechaKucha in Prague. The number of folks presentin=
g has declined<br>
&gt;=C2=A0 =C2=A0 =C2=A0slightly and I=E2=80=99m contemplating whether hold=
ing a session at every<br>
&gt;=C2=A0 =C2=A0 =C2=A0IETF meeting is too frequent. If I don=E2=80=99t he=
ar from enough folks<br>
&gt;=C2=A0 =C2=A0 =C2=A0we=E2=80=99ll wait until Singapore to do the next o=
ne. In other words, if<br>
&gt;=C2=A0 =C2=A0 =C2=A0you want to give a talk, please send me a note ASAP=
.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Standard invitation and background info below.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Thanks!<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0=E2=80=94aaron<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0------------------------------<wbr>----------------=
--------------<wbr>------------<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0A Pecha Kucha is a lightning-talk presentation form=
at, originating<br>
&gt;=C2=A0 =C2=A0 =C2=A0in Japan, where a speaker presents 20 image-only sl=
ides that are<br>
&gt;=C2=A0 =C2=A0 =C2=A0each on the screen for 20 seconds and advance autom=
atically. With<br>
&gt;=C2=A0 =C2=A0 =C2=A0each talk lasting for 6:40, it has the feature of f=
orcing<br>
&gt;=C2=A0 =C2=A0 =C2=A0presentations -- good or bad -- to be focused and b=
rief. This is an<br>
&gt;=C2=A0 =C2=A0 =C2=A0unofficial event. Topics are encouraged to be a IET=
F-related and<br>
&gt;=C2=A0 =C2=A0 =C2=A0satirical or controversial in some way, although no=
t mean-spirited.<br>
&gt;=C2=A0 =C2=A0 =C2=A0Anyone can participate in this social event. Video =
from the Berlin,<br>
&gt;=C2=A0 =C2=A0 =C2=A0Seoul, and Chicago PKs can be found here &lt;<a hre=
f=3D"http://snaggletooth.akam.ai" rel=3D"noreferrer" target=3D"_blank">http=
://snaggletooth.akam.ai</a>&gt;.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Format Details:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0* Presentation slots are open to all, assign=
ed first come, first<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0served.<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0* To reserve a presentation slot, send a nam=
e and title to<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"mailto:aaron.falk@gmail.co=
m">aaron.falk@gmail.com</a> &lt;mailto:<a href=3D"mailto:aaron.falk@gmail.c=
om">aaron.falk@gmail.com</a>&gt; and receive<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0confirmation.<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0* Presenters must agree to adhere to the Pec=
ha Kucha format (20<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0slides, primarily image-only, automat=
ically advancing every 20<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0seconds).<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0* There are lots of online tutorials and sug=
gestions for how to<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0make a good Pecha Kucha. Here are a f=
ew: [1<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;<a href=3D"http://www.pechakucha.=
org/" rel=3D"noreferrer" target=3D"_blank">http://www.pechakucha.org/</a>&g=
t;], [2<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;<a href=3D"http://blog.indezine.c=
om/2012/05/10-tips-to-create-and-present-pecha.html" rel=3D"noreferrer" tar=
get=3D"_blank">http://blog.indezine.com/<wbr>2012/05/10-tips-to-create-and-=
<wbr>present-pecha.html</a>&gt;],<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[3 &lt;<a href=3D"https://catherinecr=
onin.wordpress.com/2012/06/13/pecha-kucha/" rel=3D"noreferrer" target=3D"_b=
lank">https://catherinecronin.<wbr>wordpress.com/2012/06/13/<wbr>pecha-kuch=
a/</a>&gt;].<br>
&gt;<br>
<br>
<br>
</blockquote></div><br></div>

--001a113eab429566c205536923b0--


From nobody Mon Jul  3 08:57:37 2017
Return-Path: <stefan.winter@restena.lu>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C2D713169F; Mon,  3 Jul 2017 08:57:28 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Stefan Winter <stefan.winter@restena.lu>
To: <ops-dir@ietf.org>
Cc: webpush@ietf.org, ietf@ietf.org, draft-ietf-webpush-vapid.all@ietf.org
Subject: Opsdir last call review of draft-ietf-webpush-vapid-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149909744835.22804.5791695515985213782@ietfa.amsl.com>
Date: Mon, 03 Jul 2017 08:57:28 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ph9nVnjnBb2iO523TD2kYgGnPvA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jul 2017 15:57:29 -0000

Reviewer: Stefan Winter
Review result: Has Issues

Cryptographic agility is ensured by requiring an all-new protocol in case a
different algorithm is used, or any other protocol property is changed (the
newly defined auth scheme "vapid" is hard-wired to ECDSA NIST P-256, and there
is no version field in the JWT token). Considering that the JWT header and JWK
fields describe their signing method, making it cryptographically agile,
pinning the algorithm appears to be a strange choice (see the example in 2.4).

The last paragraph of Security Considerations remains a mystery to me. What is
a "gradual migration"? With no key rollover, any change of key simply breaks
all clients with using that key. The last sentence implies that such a hard
failure is acceptable. That's a rather simplistic protocol design.

The example in 2.4 does not appear to be correct. I cannot decode "t":

> base64 --decode
eyJ0eXAiOiJKV1QiLCJhbGciOiJFUzI1NiJ9.eyJhdWQiOiJodHRwczovL3B1c2guZXhhbXBsZS5uZXQiLCJleHAiOjE0NTM1MjM3NjgsInN1YiI6Im1haWx0bzpwdXNoQGV4YW1wbGUuY29tIn0.i3CYb7t4xfxCDquptFOepC9GAu_HLGkMlMuCGSK2rpiUfnK9ojFwDXb1JrErtmysazNjjvW2L9OkSSHzvoD1oA
{"typ":"JWT","alg":"ES256"}base64: ungültige Eingabe



From nobody Mon Jul  3 09:30:56 2017
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 817ED13144E for <ietf@ietfa.amsl.com>; Mon,  3 Jul 2017 09:30:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.411
X-Spam-Level: 
X-Spam-Status: No, score=0.411 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FORGED_MUA_MOZILLA=2.309, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 DFogLOjquhiZ for <ietf@ietfa.amsl.com>; Mon,  3 Jul 2017 09:30:47 -0700 (PDT)
Received: from sonic319-29.consmr.mail.gq1.yahoo.com (sonic319-29.consmr.mail.gq1.yahoo.com [98.137.66.210]) (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 4CB39130154 for <ietf@ietf.org>; Mon,  3 Jul 2017 09:30:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1499099444; bh=6gFFqDAV36u9U1l1qCrrVg/hOBJuYTA1VVEEsO7xeTU=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=br/0PVYD0L27fX+/CMimCcywCmx2AkLatQFvGMddJYQxWn6FZYDU51RylECzB/80O4zOeHLJlMhVw1Nnq/dNnoKFzrom53Hdyzr6C/R2td3NCSzpEwk16mk8HQIbilRZFbn2Q9wXHBSbyJMOPieudOLzQ5rGz0j3+3rZq3hBKL9yucPT6Zo4IvG3lMGSULUff0UIkZAhGIMIQRmqUfaYfH4EctzqpND5q1zselGQ5vkonnv59iIJpgMjd42HxCxJeVyRG1CDaMnD1ZFoQUxp03Lt+A/HhG0yknGS0b+wVFCByT91Slnp2NtXQbvk8kVcN0hYL9ZP+G6evsnFZrHAdA==
X-YMail-OSG: bBWjZN4VM1mFQjtdaZatUFcbfxKq_cXnCMmGhhMb.3WVYp0i2Yw4urDEHlcCKCV 0cG..tkcpHWYUODwZfYFfItagSu51xGrZ81MloAhmgOhlvtwpjjccaLDer1i5OC2eYzbZE90mmBD hAkBS4QaBjGV5aZBtqWXQEPuRAH0l5FR.3UYagPtkMpfMXj1UNbbnOq68xW9Gc071V9NW71G94DH nBVtKhfGucs1r25WY60rJdGDGiewKXCFHjX6N1lCBYanaWhhUXGC77tSzoYTFc7FRhbq4HxVxIhH N1QXJ7q6O2OymkQc.pXGIouu9.jVvSn0dG4biGn9cRnmJDIqSnlf.Z1S0DurFbtoCp5nzx.wqozI 3zQxSEkeNiPnrgYtsfs2LVCVzL21SQjPRKWN9yeOAyOV0AKlVcE3SKvmMl7BqwU8cP98U44m7_dO glU4Gb3GGMzXWe8_nvmcBMicHY.HV0O.hUoNSJX5gndP3vYvkas697H8DlJeFzZTo9QSVUwPCeuE .3skfd_BMMDHCbqdhUY9LosoI4spHsvinXpeyQFFt3KG1Bfj40jwOqnniGrbnaMn0zzsarkn5gvG LShTdh4sYnECrAPKM0M8V
Received: from sonic.gate.mail.ne1.yahoo.com by sonic319.consmr.mail.gq1.yahoo.com with HTTP; Mon, 3 Jul 2017 16:30:44 +0000
Date: Mon, 3 Jul 2017 16:30:40 +0000 (UTC)
From: Nalini J Elkins <nalini.elkins@insidethestack.com>
Reply-To: Nalini J Elkins <nalini.elkins@insidethestack.com>
To: Vmeet <vmeet@ietf.org>, IETF Discussion <ietf@ietf.org>
Message-ID: <630362149.3463015.1499099440791@mail.yahoo.com>
In-Reply-To: <149909932539.22853.11929058514143665265.idtracker@ietfa.amsl.com>
References: <149909932539.22853.11929058514143665265.idtracker@ietfa.amsl.com>
Subject: Fw: New Version Notification for draft-elkins-ietf-remote-viewing-hubs-00.txt
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_3463014_942460272.1499099440788"
X-Mailer: WebService/1.1.9978 YahooMailNeo Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vkOEnWv0irP3Hwa8ffasAkb9--8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jul 2017 16:30:50 -0000

------=_Part_3463014_942460272.1499099440788
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

All,
We have posted a draft on Remote Viewing Hubs (may be used for outreach).
Please comment on the vmeet email list.=C2=A0Thank you all for your comment=
s and interest in this topic.

Nalini Elkins
CEO and Founder
Inside Products, Inc.
www.insidethestack.com
(831) 659-8360

    =20
----- Forwarded Message -----
 From: "internet-drafts@ietf.org" <internet-drafts@ietf.org>
 To: Nalini Elkins <nalini.elkins@insidethestack.com>; Harish Chowdhary <ha=
rish@nixi.in>; "harish@nixi.in" <harish@nixi.in>=20
 Sent: Monday, July 3, 2017 9:28 AM
 Subject: New Version Notification for draft-elkins-ietf-remote-viewing-hub=
s-00.txt
  =20

A new version of I-D, draft-elkins-ietf-remote-viewing-hubs-00.txt
has been successfully submitted by Nalini Elkins and posted to the
IETF repository.

Name:=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 draft-elkins-ietf-remote-viewing=
-hubs
Revision:=C2=A0=C2=A0=C2=A0 00
Title:=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 Remote Viewing Hubs
Document date:=C2=A0=C2=A0=C2=A0 2017-07-03
Group:=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 Individual Submission
Pages:=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 11
URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 https://www.ietf.org/internet=
-drafts/draft-elkins-ietf-remote-viewing-hubs-00.txt
Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://datatracker.ietf.org/doc/draft-e=
lkins-ietf-remote-viewing-hubs/
Htmlized:=C2=A0 =C2=A0 =C2=A0 https://tools.ietf.org/html/draft-elkins-ietf=
-remote-viewing-hubs-00
Htmlized:=C2=A0 =C2=A0 =C2=A0 https://datatracker.ietf.org/doc/html/draft-e=
lkins-ietf-remote-viewing-hubs-00


Abstract:
For many reasons, remote participation in IETF meetings has increased.
As the Internet grows, so does the participation by engineers worldwide.
Remote participation with more than one person is considered a hub.

Three types of remote hubs are defined.=C2=A0 Some exist today; other types
may exist in the future.=C2=A0 Each has its own characteristics.

=C2=A0 - Remote Participation Hubs (future)
=C2=A0 - Remote Viewing Hubs (today)
=C2=A0 - Enduring Local Meetups (today)

This document defines a Remote Viewing Hub (RVH).=C2=A0 Other documents
define the other types of hubs.=C2=A0 A common structure of sections will b=
e
used as far as possible for all hub types.

=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 =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=20


Please note that it may take a couple of minutes from the time of submissio=
n
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat



  =20
------=_Part_3463014_942460272.1499099440788
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body><div style=3D"color:#000; background-color:#fff; f=
ont-family:Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font=
-size:16px"><div id=3D"yui_3_16_0_ym19_1_1499099316554_10266"><span>All,</s=
pan></div><div id=3D"yui_3_16_0_ym19_1_1499099316554_10266"><span><br></spa=
n></div><div id=3D"yui_3_16_0_ym19_1_1499099316554_10266"><span id=3D"yui_3=
_16_0_ym19_1_1499099316554_10462">We have posted a draft on Remote Viewing =
Hubs (may be used for outreach).</span></div><div id=3D"yui_3_16_0_ym19_1_1=
499099316554_10266"><span><br></span></div><div id=3D"yui_3_16_0_ym19_1_149=
9099316554_10266"><span>Please comment on the vmeet email list.</span></div=
><div></div><div id=3D"yui_3_16_0_ym19_1_1499099316554_10265">&nbsp;</div><=
div class=3D"signature" id=3D"yui_3_16_0_ym19_1_1499099316554_10184">Thank =
you all for your comments and interest in this topic.<br><br>Nalini Elkins<=
br>CEO and Founder<br>Inside Products, Inc.<br>www.insidethestack.com<br>(8=
31) 659-8360</div><div class=3D"qtdSeparateBR"><br><br></div><div class=3D"=
yahoo_quoted" id=3D"yui_3_16_0_ym19_1_1499099316554_10310" style=3D"display=
: block;">  <div style=3D"font-family: Helvetica Neue, Helvetica, Arial, Lu=
cida Grande, sans-serif; font-size: 16px;" id=3D"yui_3_16_0_ym19_1_14990993=
16554_10309"> <div style=3D"font-family: HelveticaNeue, Helvetica Neue, Hel=
vetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id=3D"yui_3_16_=
0_ym19_1_1499099316554_10308"> <div dir=3D"ltr" id=3D"yui_3_16_0_ym19_1_149=
9099316554_10307"> <font size=3D"2" face=3D"Arial" id=3D"yui_3_16_0_ym19_1_=
1499099316554_10467"> <br>----- Forwarded Message -----<br> <b><span style=
=3D"font-weight:bold;">From:</span></b> "internet-drafts@ietf.org" &lt;inte=
rnet-drafts@ietf.org&gt;<br> <b><span style=3D"font-weight: bold;">To:</spa=
n></b> Nalini Elkins &lt;nalini.elkins@insidethestack.com&gt;; Harish Chowd=
hary &lt;harish@nixi.in&gt;; "harish@nixi.in" &lt;harish@nixi.in&gt; <br> <=
b><span style=3D"font-weight: bold;">Sent:</span></b> Monday, July 3, 2017 =
9:28 AM<br> <b><span style=3D"font-weight: bold;">Subject:</span></b> New V=
ersion Notification for draft-elkins-ietf-remote-viewing-hubs-00.txt<br> </=
font> </div> <div class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_1499099=
316554_10312"><br><div dir=3D"ltr" id=3D"yui_3_16_0_ym19_1_1499099316554_10=
468"><br></div><div dir=3D"ltr" id=3D"yui_3_16_0_ym19_1_1499099316554_10311=
">A new version of I-D, draft-elkins-ietf-remote-viewing-hubs-00.txt<br></d=
iv><div dir=3D"ltr" id=3D"yui_3_16_0_ym19_1_1499099316554_10469">has been s=
uccessfully submitted by Nalini Elkins and posted to the<br></div><div dir=
=3D"ltr" id=3D"yui_3_16_0_ym19_1_1499099316554_10313">IETF repository.<br><=
/div><div dir=3D"ltr"><br></div><div dir=3D"ltr">Name:&nbsp;&nbsp;&nbsp; &n=
bsp;&nbsp;&nbsp; draft-elkins-ietf-remote-viewing-hubs<br></div><div dir=3D=
"ltr">Revision:&nbsp;&nbsp;&nbsp; 00<br></div><div dir=3D"ltr">Title:&nbsp;=
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Remote Viewing Hubs<br></div><div dir=3D"lt=
r">Document date:&nbsp;&nbsp;&nbsp; 2017-07-03<br></div><div dir=3D"ltr">Gr=
oup:&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Individual Submission<br></div><d=
iv dir=3D"ltr">Pages:&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 11<br></div><div=
 dir=3D"ltr">URL:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <a href=3D"https=
://www.ietf.org/internet-drafts/draft-elkins-ietf-remote-viewing-hubs-00.tx=
t" target=3D"_blank">https://www.ietf.org/internet-drafts/draft-elkins-ietf=
-remote-viewing-hubs-00.txt</a><br></div><div dir=3D"ltr">Status:&nbsp; &nb=
sp; &nbsp; &nbsp;  <a href=3D"https://datatracker.ietf.org/doc/draft-elkins=
-ietf-remote-viewing-hubs/" target=3D"_blank">https://datatracker.ietf.org/=
doc/draft-elkins-ietf-remote-viewing-hubs/</a><br></div><div dir=3D"ltr">Ht=
mlized:&nbsp; &nbsp; &nbsp;  <a href=3D"https://tools.ietf.org/html/draft-e=
lkins-ietf-remote-viewing-hubs-00" target=3D"_blank">https://tools.ietf.org=
/html/draft-elkins-ietf-remote-viewing-hubs-00</a><br></div><div dir=3D"ltr=
">Htmlized:&nbsp; &nbsp; &nbsp;  <a href=3D"https://datatracker.ietf.org/do=
c/html/draft-elkins-ietf-remote-viewing-hubs-00" target=3D"_blank">https://=
datatracker.ietf.org/doc/html/draft-elkins-ietf-remote-viewing-hubs-00</a><=
br></div><div dir=3D"ltr"><br></div><div dir=3D"ltr"><br></div><div dir=3D"=
ltr">Abstract:<br></div><div dir=3D"ltr">For many reasons, remote participa=
tion in IETF meetings has increased.<br></div><div dir=3D"ltr">As the Inter=
net grows, so does the participation by engineers worldwide.<br></div><div =
dir=3D"ltr">Remote participation with more than one person is considered a =
hub.<br></div><div dir=3D"ltr"><br></div><div dir=3D"ltr">Three types of re=
mote hubs are defined.&nbsp;  Some exist today; other types<br></div><div d=
ir=3D"ltr">may exist in the future.&nbsp;  Each has its own characteristics=
.<br></div><div dir=3D"ltr"><br></div><div dir=3D"ltr">&nbsp;  - Remote Par=
ticipation Hubs (future)<br></div><div dir=3D"ltr">&nbsp;  - Remote Viewing=
 Hubs (today)<br></div><div dir=3D"ltr">&nbsp;  - Enduring Local Meetups (t=
oday)<br></div><div dir=3D"ltr"><br></div><div dir=3D"ltr">This document de=
fines a Remote Viewing Hub (RVH).&nbsp; Other documents<br></div><div dir=
=3D"ltr">define the other types of hubs.&nbsp; A common structure of sectio=
ns will be<br></div><div dir=3D"ltr">used as far as possible for all hub ty=
pes.<br></div><div dir=3D"ltr"><br></div><div dir=3D"ltr">&nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br></div><div dir=3D"ltr"><br=
></div><div dir=3D"ltr"><br></div><div dir=3D"ltr">Please note that it may =
take a couple of minutes from the time of submission<br></div><div dir=3D"l=
tr">until the htmlized version and diff are available at tools.ietf.org.<br=
></div><div dir=3D"ltr"><br></div><div dir=3D"ltr">The IETF Secretariat<br>=
</div><div dir=3D"ltr"><br></div><br><br></div> </div> </div>  </div></div>=
</body></html>
------=_Part_3463014_942460272.1499099440788--


From nobody Mon Jul  3 10:32:02 2017
Return-Path: <adam@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF9DF129B77; Mon,  3 Jul 2017 10:31:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.881
X-Spam-Level: 
X-Spam-Status: No, score=-1.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 G_XdMFONWs4P; Mon,  3 Jul 2017 10:31:41 -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 7D2CA1316EA; Mon,  3 Jul 2017 10:31:23 -0700 (PDT)
Received: from Orochi.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v63HVKjS097633 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 3 Jul 2017 12:31:21 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Orochi.local
Subject: Re: Opsdir last call review of draft-ietf-webpush-vapid-03
To: Stefan Winter <stefan.winter@restena.lu>, ops-dir@ietf.org
Cc: webpush@ietf.org, ietf@ietf.org, draft-ietf-webpush-vapid.all@ietf.org
References: <149909744835.22804.5791695515985213782@ietfa.amsl.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <bb3631d2-f5b5-d6b0-958f-ac9c10aaddec@nostrum.com>
Date: Mon, 3 Jul 2017 12:31:15 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <149909744835.22804.5791695515985213782@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pis6v5b1COYSNZs5EpmxGU12-sU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jul 2017 17:31:47 -0000

On 7/3/17 10:57, Stefan Winter wrote:
> The example in 2.4 does not appear to be correct. I cannot decode "t":
>
>> base64 --decode
> eyJ0eXAiOiJKV1QiLCJhbGciOiJFUzI1NiJ9.eyJhdWQiOiJodHRwczovL3B1c2guZXhhbXBsZS5uZXQiLCJleHAiOjE0NTM1MjM3NjgsInN1YiI6Im1haWx0bzpwdXNoQGV4YW1wbGUuY29tIn0.i3CYb7t4xfxCDquptFOepC9GAu_HLGkMlMuCGSK2rpiUfnK9ojFwDXb1JrErtmysazNjjvW2L9OkSSHzvoD1oA
> {"typ":"JWT","alg":"ES256"}base64: ungültige Eingabe
>
>

I'll let the authors respond to your other points; but, as this is 
simply a mechanical issue, I'll try to clarify the intended syntax (NOTE 
TO AUTHORS: THERE IS STILL AN ERROR THAT NEEDS FIXING).

"t" contains a JWT, which consists of three separate base64 encoded 
fields, delimited by a "." character: a header, a body, and a signature. 
The signature, naturally, does not render as something readable when 
decoded. Thus:

# echo eyJ0eXAiOiJKV1QiLCJhbGciOiJFUzI1NiJ9 | base64 --decode

{"typ":"JWT","alg":"ES256"}


# echo 
eyJhdWQiOiJodHRwczovL3B1c2guZXhhbXBsZS5uZXQiLCJleHAiOjE0NTM1MjM3NjgsInN1YiI6Im1haWx0bzpwdXNoQGV4YW1wbGUuY29tIn0 
| base64 --decode

{"aud":"https://push.example.net","exp":1453523768,"sub":"mailto:push@example.com


# echo 
i3CYb7t4xfxCDquptFOepC9GAu_HLGkMlMuCGSK2rpiUfnK9ojFwDXb1JrErtmysazNjjvW2L9OkSSHzvoD1oA 
| base64 --decode | od -tx1

0000000    8b  70  98  6f  bb  78  c5  fc  42  0e  ab  a9  b4 53  9e  a4
0000020    2f  46  02  ef  c7  2c  69  0c  94  cb  82  19  22  b6 ae  98
0000040    94  7e  72  bd  a2  31  70  0d  76  f5  26  b1  2b  b6 6c  ac
0000060    6b  33  63  8e  f5  b6  2f  d3  a4  49  21  f3  be  80 f5
0000077

So, there is an error, inasmuch as the body is missing a closing 
quotation mark and a closing brace; but the base64 encoding is otherwise 
okay.

/a


From nobody Mon Jul  3 11:06:53 2017
Return-Path: <aaron.falk@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3FE512EC52; Mon,  3 Jul 2017 11:06:45 -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 7yXfOUz-lmFu; Mon,  3 Jul 2017 11:06:43 -0700 (PDT)
Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::22d]) (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 8757C129A97; Mon,  3 Jul 2017 11:06:43 -0700 (PDT)
Received: by mail-qt0-x22d.google.com with SMTP id b40so40724555qtb.2; Mon, 03 Jul 2017 11:06:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:subject:date:message-id:in-reply-to:references:mime-version;  bh=6odCQ1KfPkZ1hmep0svPENtKCwu0NKfWuW5dcjStwdE=; b=Z9PfvEzm4XseWzC5/8ZW9c2Tg5y5eI+9zGlprquIRdw7UkibvafoYbdTMpNkFYHKjB pFk9TPEj7zsmmJf4h3N498JCnOQP60j1afReyhQHAaoho8oTipkpoiN2Ipmp3jZilO+J GlGxXcYbd6/9sMcjwt27Z2TPYwn/N8sc51aggg0oUVPYnHbEezjOcOcVY9XmpVDrLJD7 fK6a1WbmFwsCMi7/Paf7PDrfRB5hS9Vai4/Prr3dIjv96k6gCg00QdDeiLiM7D65jGv1 HBSPeWf0GXYKcjIhQxybI4brA3mXi8Y1z6GvftHSy56aD3XA13emTeKAB203IbEu45h0 1gSA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:in-reply-to :references:mime-version; bh=6odCQ1KfPkZ1hmep0svPENtKCwu0NKfWuW5dcjStwdE=; b=PHCR2kiH8nhBByQ/+srE6RkoYU+vWNED24OBqZi3oDLJDVSpR0oz/IGiAqZf7ryNip yyT8zPKEk6zW11Mt5+LrWV0Gt0EJFlTyX816gC4a/Al8uK0UroICkCHR8VNABrayFAjv mium57QTjaG5cwx2wq4ue+MGVJ7tcrRTaWu2E+Ez3UE3Qlv0dNFtcwk7Xk4BtuBL99pO pJh4LaKDlFfC5WToqKOCZgSNCwNdRMT5lMZnZgM8pJMIKF8mCbz9lCuXF+sadg++/dVo N+QI9J3Y95SwjFNSzxZC34QLPknbx9tfmkLV24rlkyd9fi0o2x4PQqrmhsJd5yA7j0MI /TdA==
X-Gm-Message-State: AKS2vOxtrhc6c1od0NjjevYE6ObxIAQItVMKlNxkn5n4NSNgMhxtOY8u 71MCj6+XSc1aaOFJzYk=
X-Received: by 10.200.52.71 with SMTP id v7mr42310281qtb.214.1499105202544; Mon, 03 Jul 2017 11:06:42 -0700 (PDT)
Received: from [172.19.43.43] ([2601:184:4980:a321:a10d:f2b3:e4ed:e94c]) by smtp.gmail.com with ESMTPSA id c26sm13976056qte.63.2017.07.03.11.06.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 03 Jul 2017 11:06:42 -0700 (PDT)
From: "Aaron Falk" <aaron.falk@gmail.com>
To: ietf@ietf.org, "99attendees@ietf.org" <99attendees@ietf.org>
Subject: Re: PechaKucha presenters for Prague?
Date: Mon, 03 Jul 2017 14:06:57 -0400
Message-ID: <F11AED30-9781-409D-89BD-BB676BB2E371@gmail.com>
In-Reply-To: <D53C2422-8C47-4E42-B5AF-9A263FB89730@gmail.com>
References: <D53C2422-8C47-4E42-B5AF-9A263FB89730@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_28BF074E-4088-49A4-AD70-51CAE15A9113_="
X-Mailer: MailMate (1.9.6r5356)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/y2GKJTGV2xqBScLin1JxUCeyMb0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jul 2017 18:06:46 -0000

--=_MailMate_28BF074E-4088-49A4-AD70-51CAE15A9113_=
Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown
Content-Transfer-Encoding: quoted-printable

I have five folks signed up.  IMO, that seems to be right on the cusp of =

making it worth the effort to hold the event.  Anyone else want to step =

up?

On 21 Jun 2017, at 18:09, Aaron Falk wrote:

> This is a poll for folks who are interested in presenting at a =

> PechaKucha in Prague.  The number of folks presenting has declined =

> slightly and I=E2=80=99m contemplating whether holding a session at eve=
ry =

> IETF meeting is too frequent.  If I don=E2=80=99t hear from enough folk=
s =

> we=E2=80=99ll wait until Singapore to do the next one.  In other words,=
 if =

> you want to give a talk, please send me a note ASAP.
>
> Standard invitation and background info below.
>
> Thanks!
>
> =E2=80=94aaron
>
> ____
>
> A Pecha Kucha is a lightning-talk presentation format, originating in =

> Japan, where a speaker presents 20 image-only slides that are each on =

> the screen for 20 seconds and advance automatically.  With each talk =

> lasting for 6:40, it has the feature of forcing presentations -- good =

> or bad -- to be focused and brief.  This is an unofficial event. =

> Topics are encouraged to be a IETF-related and satirical or =

> controversial in some way, although not mean-spirited.  Anyone can =

> participate in this social event.  Video from the Berlin, Seoul, and =

> Chicago PKs can be found [here](http://snaggletooth.akam.ai).
>
> Format Details:
>
> * Presentation slots are open to all, assigned first come, first =

> served.
> * To reserve a presentation slot, send a name and title to =

> aaron.falk@gmail.com and receive confirmation.
> * Presenters must agree to adhere to the Pecha Kucha format (20 =

> slides, primarily image-only, automatically advancing every 20 =

> seconds).
> * There are lots of online tutorials and suggestions for how to make a =

> good Pecha Kucha.  Here are a few: [[1](http://www.pechakucha.org/)], =

> [[2](http://blog.indezine.com/2012/05/10-tips-to-create-and-present-pec=
ha.html)], =

> [[3](https://catherinecronin.wordpress.com/2012/06/13/pecha-kucha/)].

--=_MailMate_28BF074E-4088-49A4-AD70-51CAE15A9113_=
Content-Type: text/html; charset=utf-8
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">I have five folks signed up.  IMO, that seems to be right=
 on the cusp of making it worth the effort to hold the event.  Anyone els=
e want to step up?</p>

<p dir=3D"auto">On 21 Jun 2017, at 18:09, Aaron Falk wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<p dir=3D"auto">This is a poll for folks who are interested in presenting=
 at a PechaKucha in Prague.  The number of folks presenting has declined =
slightly and I=E2=80=99m contemplating whether holding a session at every=
 IETF meeting is too frequent.  If I don=E2=80=99t hear from enough folks=
 we=E2=80=99ll wait until Singapore to do the next one.  In other words, =
if you want to give a talk, please send me a note ASAP.</p>

<p dir=3D"auto">Standard invitation and background info below.</p>

<p dir=3D"auto">Thanks!</p>

<p dir=3D"auto">=E2=80=94aaron</p>

<hr style=3D"background:#333; background-image:linear-gradient(to right, =
#ccc, #333, #ccc); border:0; height:1px" height=3D"1">

<p dir=3D"auto">A Pecha Kucha is a lightning-talk presentation format, or=
iginating in Japan, where a speaker presents 20 image-only slides that ar=
e each on the screen for 20 seconds and advance automatically.  With each=
 talk lasting for 6:40, it has the feature of forcing presentations -- go=
od or bad -- to be focused and brief.  This is an unofficial event. Topic=
s are encouraged to be a IETF-related and satirical or controversial in s=
ome way, although not mean-spirited.  Anyone can participate in this soci=
al event.  Video from the Berlin, Seoul, and Chicago PKs can be found <a =
href=3D"http://snaggletooth.akam.ai" style=3D"color:#777">here</a>.</p>

<p dir=3D"auto">Format Details:</p>

<ul>
<li>Presentation slots are open to all, assigned first come, first served=
=2E</li>
<li>To reserve a presentation slot, send a name and title to <a href=3D"m=
ailto:aaron.falk@gmail.com" style=3D"color:#777">aaron.falk@gmail.com</a>=
 and receive confirmation.</li>
<li>Presenters must agree to adhere to the Pecha Kucha format (20 slides,=
 primarily image-only, automatically advancing every 20 seconds).</li>
<li>There are lots of online tutorials and suggestions for how to make a =
good Pecha Kucha.  Here are a few: [<a href=3D"http://www.pechakucha.org/=
" style=3D"color:#777">1</a>], [<a href=3D"http://blog.indezine.com/2012/=
05/10-tips-to-create-and-present-pecha.html" style=3D"color:#777">2</a>],=
 [<a href=3D"https://catherinecronin.wordpress.com/2012/06/13/pecha-kucha=
/" style=3D"color:#777">3</a>].</li>
</ul>
</blockquote>
</div>
</div>
</body>
</html>

--=_MailMate_28BF074E-4088-49A4-AD70-51CAE15A9113_=--


From nobody Mon Jul  3 14:14:10 2017
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47ED112EC01 for <ietf@ietfa.amsl.com>; Mon,  3 Jul 2017 14:14:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.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 LbFCY6NXQbtM for <ietf@ietfa.amsl.com>; Mon,  3 Jul 2017 14:14:00 -0700 (PDT)
Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com [IPv6:2607:f8b0:400c:c05::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 63C0912EA6A for <ietf@ietf.org>; Mon,  3 Jul 2017 14:14:00 -0700 (PDT)
Received: by mail-vk0-x234.google.com with SMTP id 191so101328435vko.2 for <ietf@ietf.org>; Mon, 03 Jul 2017 14:14:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=0zU62tE4zlq6N5aCr/wQOYzCUnUltCd7Vg6z4La+w5k=; b=uvkIOODumUX2210FA5rQpEUpV9zWnYcxItLh6gNRNnsZ2UVod5XWmhktyTUVioUvlE OZnxQUyv+LI6yn2UwUwrGXgdtXrDBjbMsMVlfjnN78t1H5nr5PJAYiYzqfJ319015vdd q+6kETYfK/u6G6cwcuPvNtSxfMvUzPu+QeUCvZc98/F29MR985S3vyzOc+epq3hb+p66 iZqyP8LaXppOkfW4JzBNE/CvLAWdD2lYeSDuCYkgTfuO09AqdZio37YRD+7/elWQCE6/ peHm3HhKEwXiPCQ0sEy1VA/E+SayCImXPR75ONGH2tc4KhP4P2Dxk7MahB2oVnWmHWTh 2mlA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=0zU62tE4zlq6N5aCr/wQOYzCUnUltCd7Vg6z4La+w5k=; b=Hb59j8yUjysxCIXBJ5JFVAAmG/Rdf4x0uMrtOyGM4cjtvKd3k93dWTgFkD6Yxbl5v4 gXWYHzSapyaKP744V0/DULP1ay0LlWxAJY23wVo0Lx7W3ANANxsFHz74O6bMaaRcBNmY wFnB1ZieBSaP4GoC8iVnqUROhsoLNfBeejjcRKrAYGtDAQHFcWWhkVbxIlq6hXFtolh9 Ub3OMONTxI9f+OmtPD6S4zZAduWHIT23TZBuzuZKvSiN1hZP6xSsvueOBLxeUXIuPOXd FpAkl5J8OKbtekfDhkq7rv8BkyvxxCQ47Q24BJueY/xVkdKUlKyfLcyhEYhRP6/vloqY HTbA==
X-Gm-Message-State: AKS2vOwdtdVCDTIu/rC6pEp8002SQiIYkQvXxW6fh3Qq0CAv3Rzi1Tm/ Ola9ajXBZDLfYyt/E/rPxMWg2HIdFBgQ
X-Received: by 10.31.65.87 with SMTP id o84mr20109731vka.7.1499116439368; Mon, 03 Jul 2017 14:13:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.39.165 with HTTP; Mon, 3 Jul 2017 14:13:19 -0700 (PDT)
From: Warren Kumari <warren@kumari.net>
Date: Mon, 3 Jul 2017 17:13:19 -0400
Message-ID: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com>
Subject: Minor editorial change to draft-ietf-dnsop-sutld-ps
To: dnsop@ietf.org
Cc: IETF Discuss <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WnLBJTrePYmCxu2NNrHKQhc8jeo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jul 2017 21:14:03 -0000

Hi all,

The Special-Use Domain Names Problem Statement document unsurprisingly
contains a list of problems.

This was an unordered list of 21 problems, including descriptions and
sub-bullets.

While trying to write another draft referring to specific problems it
became clear that it would be much better to have this as a *numbered*
list, so that one can refer to specific problems and say thing like
"This helps address problem #17" instead of "This helps address the
problem in the list which begins with the text "foo bar baz"...

I have checked with my co-authors, the DNSOP chairs, IESG and
responsible AD, and have updated the document changing the list from
unordered to numbered (and adding "This is not an ordered list, it is
numbered merely to facilitate referencing specific problems:").

The consensus was that this is a purely editorial change, but please
scream if you disagree -- the document is on Thursday's telechat, and
Benoit is the responsible AD.

W


On Mon, Jul 3, 2017 at 2:56 PM, <internet-drafts@ietf.org> wrote:
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Domain Name System Operations of the IETF.
>
>         Title           : Special-Use Domain Names Problem Statement
>         Authors         : Ted Lemon
>                           Ralph Droms
>                           Warren Kumari
>         Filename        : draft-ietf-dnsop-sutld-ps-07.txt
>         Pages           : 29
>         Date            : 2017-07-03
>
> Abstract:
>    The Special-Use Domain Names IANA registry policy defined in RFC 6761
>    has been shown through experience to present unanticipated
>    challenges.  This memo presents a list, intended to be comprehensive,
>    of the problems that have been identified.  In addition it reviews
>    the history of Domain Names and summarizes current IETF publications
>    and some publications from other organizations relating to Special-
>    Use Domain Names.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-sutld-ps/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-dnsop-sutld-ps-07
> https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-sutld-ps-07
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-sutld-ps-07
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop




-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf


From nobody Mon Jul  3 15:25:41 2017
Return-Path: <xufeng.liu.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE87A12EC15; Mon,  3 Jul 2017 15:25:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.988
X-Spam-Level: 
X-Spam-Status: No, score=-1.988 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, T_KAM_HTML_FONT_INVALID=0.01, 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 bhU6AyGKZKXZ; Mon,  3 Jul 2017 15:25:35 -0700 (PDT)
Received: from mail-wm0-x242.google.com (mail-wm0-x242.google.com [IPv6:2a00:1450:400c:c09::242]) (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 3BB2E131640; Mon,  3 Jul 2017 15:25:31 -0700 (PDT)
Received: by mail-wm0-x242.google.com with SMTP id y5so22895848wmh.3; Mon, 03 Jul 2017 15:25:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:thread-index:content-language; bh=hubpHwPYpYLMlIiXg/qfbo3ZUHMPEuUdTo/3/5bBrH8=; b=Vah7mi8duIvB7ChMOUMWVYEv3xOrb91hwwCI7tXV/xqMf82+MfScwwom7Sej9b/0Li tAkdCdVEJatqIvtA4HcU5H61FhdusdwAdbmSfhXuK6Lo0U8QKyd4+Pvm3iNfqZUHAK7c KF7beevfHnzo7iZ42YJWlPBIL625d6giRQggLyY7+JshZQPaLfX8TCKBRqAEqOECEYK5 x/687BuGWTPFoFpo7xXJ8qQEB4gg+oHHljMCBu763p06CrLVfwL6Pq1RgtCaIEYDYPsf QNhqM/vk6Wztkrne8P3xye6AfRT/8QpiG8wHCzqAV+xZvzXqp/EjKf1jhPPRNMCsW8aH XNpg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=hubpHwPYpYLMlIiXg/qfbo3ZUHMPEuUdTo/3/5bBrH8=; b=f8GUtFTOE2yenPB2HhFqcaABCFWXjbQyk3d1/q+0dgaxpyi5nnSVAMooGjHpiu+OlB dipCcKlIQHWT26nrU4SQ4M+7V4dACLXAdWDW2z6OkaUuwt+b+aC3zDMHd2icM+fmDhNT O326wvFiFnOgOKy9l3YXKT6WUT9YebcNRFYT7dlGDSnW5CvLyxfDqxTeIMkPhxSn9vDr 0dc/sSxQjK/t9Hs803Pz4bCQ/lvp5SiCD9F7HLSyQajzPRKU5kaQdqtFwkIa2WoGZWnT 1YG8RKpa2ZBqNMQbktmRO0AxrwBEPM6v7/fc9xOEUCdVdlW5Wcv7EirVvXthRq9m9A+r jS+A==
X-Gm-Message-State: AIVw1121a8ijS5kTvdk8HW1UVlVY26TQGuJ0AnFjwx+Xy4J8+Uo0n0Cp iSM2nsXTGcnjUW2gZpP6lQ==
X-Received: by 10.28.66.67 with SMTP id p64mr9166569wma.93.1499120729626; Mon, 03 Jul 2017 15:25:29 -0700 (PDT)
Received: from xliuus (wsip-98-191-72-170.dc.dc.cox.net. [98.191.72.170]) by smtp.gmail.com with ESMTPSA id v102sm4601315wrc.53.2017.07.03.15.25.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 03 Jul 2017 15:25:29 -0700 (PDT)
From: "Xufeng Liu" <xufeng.liu.ietf@gmail.com>
To: "'Robert Wilton'" <rwilton@cisco.com>, "'Benoit Claise'" <bclaise@cisco.com>, "'Xufeng Liu'" <Xufeng_Liu@jabil.com>, "'Mahesh Jethanandani'" <mjethanandani@gmail.com>, <yang-doctors@ietf.org>
Cc: <ietf@ietf.org>, <teas@ietf.org>, <draft-ietf-teas-yang-te-topo.all@ietf.org>
References: <149564066257.28529.12761629961042171907@ietfa.amsl.com> <BN3PR0201MB08670E55FFB5470F338E998DF1CD0@BN3PR0201MB0867.namprd02.prod.outlook.com> <5d4541d3-9426-787d-e02b-9c2dbc3a5400@cisco.com> <BN3PR0201MB0867315F3E88577B9EEF6584F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com> <3a1c319f-0255-b8ee-ecbd-739568c1dc7f@cisco.com> <1ab3a0d8-de3e-1d7c-2967-97b74b1c68a5@cisco.com> <BN3PR0201MB0867664CBDA460C283DC8043F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com> <04b933e2-189a-6fe2-5d24-310167f91b69@cisco.com> <00d001d2f37c$22d3dd10$687b9730$@gmail.com> <a83f8acd-2c14-2d28-f196-96b5fd7833a9@cisco.com>
In-Reply-To: <a83f8acd-2c14-2d28-f196-96b5fd7833a9@cisco.com>
Subject: RE: [Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-08
Date: Mon, 3 Jul 2017 18:25:25 -0400
Message-ID: <024a01d2f44b$465229c0$d2f67d40$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_024B_01D2F429.BF43E520"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQGOEtHVR4X43lNLh7rZd88C0w0DvAIP54n+AmHbMQEB8+cVUAKUyOUBAjMgSAcBQqeaTwEuF5NGAlap3FoCL/2/hKI7SIxw
Content-Language: en-us
x-dg-ref: PG1ldGE+PGF0IG5tPSJib2R5Lmh0bWwiIHA9ImM6XHVzZXJzXHhsaXVcYXBwZGF0YVxyb2FtaW5nXDA5ZDg0OWI2LTMyZDMtNGE0MC04NWVlLTZiODRiYTI5ZTM1Ylxtc2dzXG1zZy04MWYzZTFkYi02MDNlLTExZTctOWMxOS0xODVlMGZlM2M0NWNcYW1lLXRlc3RcODFmM2UxZGQtNjAzZS0xMWU3LTljMTktMTg1ZTBmZTNjNDVjYm9keS5odG1sIiBzej0iMjY2NjgiIHQ9IjEzMTQzNTk0MzI1NTczMTg1OCIgaD0iZlJwVmt2Tll3QU91bGVUbUVCYVJxMlhnck5BPSIgaWQ9IiIgYmw9IjAiIGJvPSIxIi8+PC9tZXRhPg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hJpNdeTeIdrZVRJgj8Z8ByTAV1Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jul 2017 22:25:38 -0000

This is a multipart message in MIME format.

------=_NextPart_000_024B_01D2F429.BF43E520
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

HI Rob,

=20

Just posted =
https://datatracker.ietf.org/doc/draft-ietf-teas-yang-te-topo/  to fix =
the snippets, along with a missing IANA entry.

=20

Thanks,

- Xufeng

=20

From: Robert Wilton [mailto:rwilton@cisco.com]=20
Sent: Monday, July 3, 2017 5:13 AM
To: Xufeng Liu <xufeng.liu.ietf@gmail.com>; 'Benoit Claise' =
<bclaise@cisco.com>; 'Xufeng Liu' <Xufeng_Liu@jabil.com>; 'Mahesh =
Jethanandani' <mjethanandani@gmail.com>; yang-doctors@ietf.org
Cc: ietf@ietf.org; teas@ietf.org; =
draft-ietf-teas-yang-te-topo.all@ietf.org
Subject: Re: [Teas] Yangdoctors last call review of =
draft-ietf-teas-yang-te-topo-08

=20

Hi Xufeng,

Thanks for updating the modules to be NMDA compliant.  I think that =
getting structural consistency across the IETF YANG modules will make =
them far more compelling as a solution.

I noticed that some of the snippets of YANG tree output in the draft =
still illustrate using the "split oc-style config/state structure" and =
hence also need to be updated.  Probably this could be done as part of =
the WG LC.

To find the instances, just search the draft for "rw config" and "ro =
state".

Thanks,
Rob

=20

On 02/07/2017 22:42, Xufeng Liu wrote:

An updated revision of the TE topology model has been posted at =
https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-10.

=20

This new revision now contains the NMDA compliant module and a companion =
=E2=80=9C-state=E2=80=9D module, after the I2RS topology model that we =
augment has been update with a =E2=80=9C-state=E2=80=9D module.

=20

Now that this issue has been solved, the authors and contributors think =
that the draft is ready for the last call.

=20

Thanks,

- Xufeng

=20

P.S. Because of the structure changes of the TE topology model, all =
augmenting models need to be updated. Sorry for the short notice.

=20

From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Benoit Claise
Sent: Monday, June 26, 2017 6:46 AM
To: Xufeng Liu  <mailto:Xufeng_Liu@jabil.com> <Xufeng_Liu@jabil.com>; =
Robert Wilton  <mailto:rwilton@cisco.com> <rwilton@cisco.com>; Mahesh =
Jethanandani  <mailto:mjethanandani@gmail.com> =
<mjethanandani@gmail.com>; yang-doctors@ietf.org =
<mailto:yang-doctors@ietf.org>=20
Cc: Benoit Claise  <mailto:bclaise@cisco.com> <bclaise@cisco.com>; =
ietf@ietf.org <mailto:ietf@ietf.org> ; teas@ietf.org =
<mailto:teas@ietf.org> ; draft-ietf-teas-yang-te-topo.all@ietf.org =
<mailto:draft-ietf-teas-yang-te-topo.all@ietf.org>=20
Subject: Re: [Teas] Yangdoctors last call review of =
draft-ietf-teas-yang-te-topo-08

=20

Hi Xufeng,

Hi Benoit,
=20

-----Original Message-----
From: Benoit Claise [mailto:bclaise@cisco.com]
Sent: Thursday, June 22, 2017 6:12 AM
To: Robert Wilton  <mailto:rwilton@cisco.com> <rwilton@cisco.com>; =
Xufeng Liu  <mailto:Xufeng_Liu@jabil.com> <Xufeng_Liu@jabil.com>;
Mahesh Jethanandani  <mailto:mjethanandani@gmail.com> =
<mjethanandani@gmail.com>; yang-doctors@ietf.org =
<mailto:yang-doctors@ietf.org>=20
Cc: ietf@ietf.org <mailto:ietf@ietf.org> ; teas@ietf.org =
<mailto:teas@ietf.org> ; draft-ietf-teas-yang-te-topo.all@ietf.org =
<mailto:draft-ietf-teas-yang-te-topo.all@ietf.org>=20
Subject: Re: [Teas] Yangdoctors last call review of =
draft-ietf-teas-yang-te-topo-
08
=20
Dear draft-ietf-teas-yang-te-topo authors,

Hi Xufeng,
=20
OK, by tooling, I don't mean the pyang plugins that I have been
working on to convert between different types of models.  As you
aware, the TE YANG models can easily be converted to NMDA style since
I have already done it
(https://github.com/rgwilton/ietf-models-to-combined).
=20
My comment actually relates to the fact the structure used by TE YANG
modules don't match any other YANG modules - they are using their own
unique style of structure.

This is an important issue to resolve.

=20
Today, there are three common styles of modules:
(1) IETF style split config/state trees (e.g. ietf-interfaces).
(2) IETF NMDA style combined config/state trees (i.e. where all IETF
modules are heading to).
(3) OpenConfig style modules with the config/state containers
immediately above the config leaves.
=20
Tooling is likely to be optimized to work with these model structures,
but the TE modules do not fit into any of the three styles above.
They are a yet another OpenConfig-like style, but that is different
enough that tooling that is designed to work with OpenConfig style
YANG modules would likely not work with the TE YANG modules.
=20
Specifically, for clients that expecting to work with an OpenConfig
style YANG module, then if it knows the path to config leaf X, then
they would expect the applied config value to be available at the path
"../state/X".  But, this doesn't hold for the structure being used in
the TE YANG models.
=20
I believe strongly that the models being produced by organizations
should be structures in a consistent way, hence why I think that the
published standard version of the TE YANG modules should immediately
align to the NMDA style.

Agreed.
Here is the OPS and RTG AD message:
https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html
=20
I understand that the I2RS topology YANG modules will be improved to the
NMDA style.

[Xufeng] The I2RS topology model is already NMDA style, but the NMDA =
models are not immediately implementable without NETCONF/RESTCONF =
protocol update. We will need the "-state" module for the I2RS topology =
model (and for all the top-level models) for now.=20

Adding -state to the Appendix is a possibility.
"In all cases, the NMDA and non-NMDA modules SHOULD be published in the =
same document, with NMDA modules in the document main body and the =
non-NMDA modules in an Appendix."
See https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html




While the NMDA is nice, the NMDA discussions have already significantly =
delayed publishing new models, and doing NMDA without staging will =
further delay the process.

This is not solving the important issue brought up by Rob Witlon:

My comment actually relates to the fact the structure used by TE YANG =
modules don't match any other YANG modules - they are using their own =
unique style of structure.

Regards, B.




=20
Thanks,  Xufeng

=20
Regards, Benoit

=20
Thanks,
Rob
=20
=20
On 22/06/2017 04:16, Xufeng Liu wrote:

Hi Rob,
=20
While the tooling is very nice to have, especially for writing new
models or converting models, we do not have to use it for every
model. It seems not necessary to use the tooling on this model for
now. We already know that we can manually convert it to NMDA style if
needed.
=20
Thanks,
- Xufeng
=20

-----Original Message-----
From: Robert Wilton [mailto:rwilton@cisco.com]
Sent: Wednesday, June 21, 2017 5:34 AM
To: Xufeng Liu  <mailto:Xufeng_Liu@jabil.com> <Xufeng_Liu@jabil.com>; =
Mahesh Jethanandani
 <mailto:mjethanandani@gmail.com> <mjethanandani@gmail.com>; =
yang-doctors@ietf.org <mailto:yang-doctors@ietf.org>=20
Cc: ietf@ietf.org <mailto:ietf@ietf.org> ; teas@ietf.org =
<mailto:teas@ietf.org> ;
draft-ietf-teas-yang-te-topo.all@ietf.org =
<mailto:draft-ietf-teas-yang-te-topo.all@ietf.org>=20
Subject: Re: [Teas] Yangdoctors last call review of
draft-ietf-teas-yang-te-topo-
08
=20
Hi Xufeng,
=20
On 12/06/2017 22:28, Xufeng Liu wrote:

Hi Mahesh,
=20
Thank you much for the review. We have submitted an updated draft

(https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09) to
address these issues. More detailed explanations are put below
inline.

If the responses and updates are satisfactory, we are ready for the
last call.
=20
Best regards,
- Xufeng
=20

-----Original Message-----
From: Mahesh Jethanandani [mailto:mjethanandani@gmail.com]
Sent: Wednesday, May 24, 2017 11:44 AM
To: yang-doctors@ietf.org <mailto:yang-doctors@ietf.org>=20
Cc: ietf@ietf.org <mailto:ietf@ietf.org> ; teas@ietf.org =
<mailto:teas@ietf.org> ;
draft-ietf-teas-yang-te-topo.all@ietf.org =
<mailto:draft-ietf-teas-yang-te-topo.all@ietf.org>=20
Subject: Yangdoctors last call review of
draft-ietf-teas-yang-te-topo-08
=20
Reviewer: Mahesh Jethanandani
Review result: Ready with Issues
=20
Document reviewed: draft-ietf-teas-yang-te-topo-08
=20
Status: Ready with Issues
=20
I am not an expert in Traffic Engineering. This review is looking
at the draft from a YANG perspective. With that said, I have
marked it as =E2=80=9CReady

with Issues=E2=80=9D

because of some of the points discussed below.
=20
Summary:
=20
This document defines a YANG data model for representing,
retrieving and manipulating TE Topologies. The model serves as a
base model that other technology specific TE Topology models can

augment.

=20
Comments:
=20
Almost all the containers in the model are presence containers. Is
there a reason why they have to be presence containers? Note, that
presence containers are containers whose existence itself
represents configuration data. What particular configuration data
is each container

representing in itself?

[Xufeng] Containers that use =E2=80=9Cpresence=E2=80=9D are:
    - Container =E2=80=9Cunderlay=E2=80=9D
      o  We have changed 13 occurrences of such containers to be
not

presence container.

    - Container =E2=80=9Cte=E2=80=9D under augmentation
      o  To indicate that =E2=80=9CTE=E2=80=9D is enabled (configuration =
data)
      o  Also used to do augmentation. The =E2=80=9Cpresence=E2=80=9D =
statement can

prevent the mandatory child from affecting augmented base model.

    - /nw:networks/nw:network/nw:network-types/te-topology!
      o  A mechanism required by I2RS topology model to specify the

topology type.

It is difficult to co-relate the diagram with the model itself
because of different terms being used to define different parts of
the model.
There is =E2=80=9CTE Topology Model=E2=80=9D and then there is =
=E2=80=9CGeneric TE
Topology

Model=E2=80=9D.

Are these one and the same models? If so, a common term for both
of them would be helpful.

[Xufeng] Yes. These two terms are the same. Figure 12, Figure 13,
and relevant

descriptions have been updated to make the document consistent.

There is extensive use of groupings in the document. However, not
all instances of groupings are used multiple number of times.
Where they are not being repeated, it would be better to move the
grouping directly where the uses statement resides. Case in point
the grouping

connectivity-label-restriction-list.

[Xufeng] We have removed the following groupings
      te-link-augment
      te-node-augment
      te-termination-point-augment
      te-topologies-augment
      te-topology-augment
      te-link-state-underlay-attributes
      te-node-state-derived-notification
      te-topology-type
=20
The remaining groupings have been kept so that we can:
    - Share the groupings in this model
    - Prepare to be shared by a model augmenting this model
    - Prevent a grouping or configuration section from being too long
    - Improve readability
=20

The split between config and state containers does not seem to
follow any particular pattern.

[Xufeng] The pattern is clear:
For each manageable entity (object), there is a config container
and state

container. The configurable properties go into the config container
and state properties go into the state container. Such objects are
identified by a list item or a presence container so that the
=E2=80=9Ccreate=E2=80=9D, =E2=80=9Cdelete=E2=80=9D, and =
=E2=80=9Cmodify=E2=80=9D
operations
can be performed on them. The non-presence containers do not
represent configuration data so they do not introduce such objects.

It is neither a top level split, as is the case with existing IETF
models,

[Xufeng] We could not do top level split because the base I2RS
network

topology model
(https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo-
12) that we augment does not have the top-level split (for its own
reasons).

nor do they follow the OpenConfig style of splitting config and
state under each relevant leaf,

[Xufeng] The pattern is consistent with this style in principle,
with some

adjustments to fit to our multiple levels of hierarchy.
This is effectively a new forth style of YANG models that is not
consistent with any of the three existing styles, i.e.:
   - Current IETF config/state split model style
   - NMDA combined config/state tree
   - OpenConfig split config/state containers immediately above the
config true leaves.
=20
Tooling that it designed to work with OpenConfig models will need
customization to work with these TE models because the config/state
containers will not be where the tooling expects them to be.
=20
Thanks,
Rob

=20
.
=20

=20

=20

=20


------=_NextPart_000_024B_01D2F429.BF43E520
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=3DGenerator 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:DengXian;
	panose-1:3 0 5 9 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@DengXian";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	color:black;}
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";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	color:black;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri",sans-serif;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle25
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@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 bgcolor=3Dwhite =
lang=3DEN-US link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal><span style=3D'color:windowtext'>HI =
Rob,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:windowtext'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal>Just posted <a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-teas-yang-te-topo/">h=
ttps://datatracker.ietf.org/doc/draft-ietf-teas-yang-te-topo/</a> =
=C2=A0to fix the snippets, along with a missing IANA entry.<span =
style=3D'color:windowtext'><o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:windowtext'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:windowtext'>Thanks,<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:windowtext'>- =
Xufeng<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:windowtext'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #E1E1E1 =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'color:windowtext'>From:</span></b><span =
style=3D'color:windowtext'> Robert Wilton [mailto:rwilton@cisco.com] =
<br><b>Sent:</b> Monday, July 3, 2017 5:13 AM<br><b>To:</b> Xufeng Liu =
&lt;xufeng.liu.ietf@gmail.com&gt;; 'Benoit Claise' =
&lt;bclaise@cisco.com&gt;; 'Xufeng Liu' &lt;Xufeng_Liu@jabil.com&gt;; =
'Mahesh Jethanandani' &lt;mjethanandani@gmail.com&gt;; =
yang-doctors@ietf.org<br><b>Cc:</b> ietf@ietf.org; teas@ietf.org; =
draft-ietf-teas-yang-te-topo.all@ietf.org<br><b>Subject:</b> Re: [Teas] =
Yangdoctors last call review of =
draft-ietf-teas-yang-te-topo-08<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p>Hi =
Xufeng,<o:p></o:p></p><p>Thanks for updating the modules to be NMDA =
compliant.&nbsp; I think that getting structural consistency across the =
IETF YANG modules will make them far more compelling as a =
solution.<o:p></o:p></p><p>I noticed that some of the snippets of YANG =
tree output in the draft still illustrate using the &quot;split oc-style =
config/state structure&quot; and hence also need to be updated.&nbsp; =
Probably this could be done as part of the WG LC.<o:p></o:p></p><p>To =
find the instances, just search the draft for &quot;rw config&quot; and =
&quot;ro state&quot;.<o:p></o:p></p><p>Thanks,<br>Rob<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>On =
02/07/2017 22:42, Xufeng Liu wrote:<o:p></o:p></p></div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoPlainText>An updated revision of the TE topology model has =
been posted at <a =
href=3D"https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-10">http=
s://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-10</a>.<o:p></o:p></=
p><p class=3DMsoPlainText>&nbsp;<o:p></o:p></p><p =
class=3DMsoPlainText>This new revision now contains the NMDA compliant =
module and a companion =E2=80=9C-state=E2=80=9D module, after the I2RS =
topology model that we augment has been update with a =
=E2=80=9C-state=E2=80=9D module.<o:p></o:p></p><p =
class=3DMsoPlainText>&nbsp;<o:p></o:p></p><p class=3DMsoPlainText>Now =
that this issue has been solved, the authors and contributors think that =
the draft is ready for the last call.<o:p></o:p></p><p =
class=3DMsoPlainText>&nbsp;<o:p></o:p></p><p =
class=3DMsoPlainText>Thanks,<o:p></o:p></p><p class=3DMsoPlainText>- =
Xufeng<o:p></o:p></p><p class=3DMsoPlainText>&nbsp;<o:p></o:p></p><p =
class=3DMsoPlainText>P.S. Because of the structure changes of the TE =
topology model, all augmenting models need to be updated. Sorry for the =
short notice.<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:windowtext'>&nbsp;</span><o:p></o:p></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #E1E1E1 =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'color:windowtext'>From:</span></b><span =
style=3D'color:windowtext'> Teas [<a =
href=3D"mailto:teas-bounces@ietf.org">mailto:teas-bounces@ietf.org</a>] =
<b>On Behalf Of </b>Benoit Claise<br><b>Sent:</b> Monday, June 26, 2017 =
6:46 AM<br><b>To:</b> Xufeng Liu <a =
href=3D"mailto:Xufeng_Liu@jabil.com">&lt;Xufeng_Liu@jabil.com&gt;</a>; =
Robert Wilton <a =
href=3D"mailto:rwilton@cisco.com">&lt;rwilton@cisco.com&gt;</a>; Mahesh =
Jethanandani <a =
href=3D"mailto:mjethanandani@gmail.com">&lt;mjethanandani@gmail.com&gt;</=
a>; <a =
href=3D"mailto:yang-doctors@ietf.org">yang-doctors@ietf.org</a><br><b>Cc:=
</b> Benoit Claise <a =
href=3D"mailto:bclaise@cisco.com">&lt;bclaise@cisco.com&gt;</a>; <a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:teas@ietf.org">teas@ietf.org</a>; <a =
href=3D"mailto:draft-ietf-teas-yang-te-topo.all@ietf.org">draft-ietf-teas=
-yang-te-topo.all@ietf.org</a><br><b>Subject:</b> Re: [Teas] Yangdoctors =
last call review of =
draft-ietf-teas-yang-te-topo-08</span><o:p></o:p></p></div></div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p><div><p class=3DMsoNormal>Hi =
Xufeng,<o:p></o:p></p></div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>Hi =
Benoit,<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>-----Original =
Message-----<o:p></o:p></pre><pre>From: Benoit Claise [<a =
href=3D"mailto:bclaise@cisco.com">mailto:bclaise@cisco.com</a>]<o:p></o:p=
></pre><pre>Sent: Thursday, June 22, 2017 6:12 =
AM<o:p></o:p></pre><pre>To: Robert Wilton <a =
href=3D"mailto:rwilton@cisco.com">&lt;rwilton@cisco.com&gt;</a>; Xufeng =
Liu <a =
href=3D"mailto:Xufeng_Liu@jabil.com">&lt;Xufeng_Liu@jabil.com&gt;</a>;<o:=
p></o:p></pre><pre>Mahesh Jethanandani <a =
href=3D"mailto:mjethanandani@gmail.com">&lt;mjethanandani@gmail.com&gt;</=
a>; <a =
href=3D"mailto:yang-doctors@ietf.org">yang-doctors@ietf.org</a><o:p></o:p=
></pre><pre>Cc: <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:teas@ietf.org">teas@ietf.org</a>; <a =
href=3D"mailto:draft-ietf-teas-yang-te-topo.all@ietf.org">draft-ietf-teas=
-yang-te-topo.all@ietf.org</a><o:p></o:p></pre><pre>Subject: Re: [Teas] =
Yangdoctors last call review of =
draft-ietf-teas-yang-te-topo-<o:p></o:p></pre><pre>08<o:p></o:p></pre><pr=
e>&nbsp;<o:p></o:p></pre><pre>Dear draft-ietf-teas-yang-te-topo =
authors,<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>Hi =
Xufeng,<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>OK, by tooling, =
I don't mean the pyang plugins that I have =
been<o:p></o:p></pre><pre>working on to convert between different types =
of models.&nbsp; As you<o:p></o:p></pre><pre>aware, the TE YANG models =
can easily be converted to NMDA style since<o:p></o:p></pre><pre>I have =
already done it<o:p></o:p></pre><pre>(<a =
href=3D"https://github.com/rgwilton/ietf-models-to-combined">https://gith=
ub.com/rgwilton/ietf-models-to-combined</a>).<o:p></o:p></pre><pre>&nbsp;=
<o:p></o:p></pre><pre>My comment actually relates to the fact the =
structure used by TE YANG<o:p></o:p></pre><pre>modules don't match any =
other YANG modules - they are using their =
own<o:p></o:p></pre><pre>unique style of =
structure.<o:p></o:p></pre></blockquote><pre>This is an important issue =
to resolve.<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>&nbsp;<o:p></o:p></pr=
e><pre>Today, there are three common styles of =
modules:<o:p></o:p></pre><pre>(1) IETF style split config/state trees =
(e.g. ietf-interfaces).<o:p></o:p></pre><pre>(2) IETF NMDA style =
combined config/state trees (i.e. where all =
IETF<o:p></o:p></pre><pre>modules are heading =
to).<o:p></o:p></pre><pre>(3) OpenConfig style modules with the =
config/state containers<o:p></o:p></pre><pre>immediately above the =
config leaves.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Tooling =
is likely to be optimized to work with these model =
structures,<o:p></o:p></pre><pre>but the TE modules do not fit into any =
of the three styles above.<o:p></o:p></pre><pre>They are a yet another =
OpenConfig-like style, but that is different<o:p></o:p></pre><pre>enough =
that tooling that is designed to work with OpenConfig =
style<o:p></o:p></pre><pre>YANG modules would likely not work with the =
TE YANG =
modules.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Specifically, =
for clients that expecting to work with an =
OpenConfig<o:p></o:p></pre><pre>style YANG module, then if it knows the =
path to config leaf X, then<o:p></o:p></pre><pre>they would expect the =
applied config value to be available at the =
path<o:p></o:p></pre><pre>&quot;../state/X&quot;.&nbsp; But, this =
doesn't hold for the structure being used in<o:p></o:p></pre><pre>the TE =
YANG models.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>I believe =
strongly that the models being produced by =
organizations<o:p></o:p></pre><pre>should be structures in a consistent =
way, hence why I think that the<o:p></o:p></pre><pre>published standard =
version of the TE YANG modules should =
immediately<o:p></o:p></pre><pre>align to the NMDA =
style.<o:p></o:p></pre></blockquote><pre>Agreed.<o:p></o:p></pre><pre>Her=
e is the OPS and RTG AD message:<o:p></o:p></pre><pre><a =
href=3D"https://www.ietf.org/mail-archive/web/netmod/current/msg18252.htm=
l">https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html</a>=
<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>I understand that the =
I2RS topology YANG modules will be improved to =
the<o:p></o:p></pre><pre>NMDA =
style.<o:p></o:p></pre></blockquote><pre>[Xufeng] The I2RS topology =
model is already NMDA style, but the NMDA models are not immediately =
implementable without NETCONF/RESTCONF protocol update. We will need the =
&quot;-state&quot; module for the I2RS topology model (and for all the =
top-level models) for now. <o:p></o:p></pre></blockquote><p =
class=3DMsoNormal>Adding -state to the Appendix is a =
possibility.<br>&quot;In all cases, the NMDA and non-NMDA modules SHOULD =
be published in the same document, with NMDA modules in the document =
main body and the non-NMDA modules in an Appendix.&quot;<br>See <a =
href=3D"https://www.ietf.org/mail-archive/web/netmod/current/msg18252.htm=
l">https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html</a>=
<br><br><br><o:p></o:p></p><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>While the NMDA is =
nice, the NMDA discussions have already significantly delayed publishing =
new models, and doing NMDA without staging will further delay the =
process.<o:p></o:p></pre></blockquote><p class=3DMsoNormal>This is not =
solving the important issue brought up by Rob =
Witlon:<o:p></o:p></p><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p class=3DMsoNormal>My =
comment actually relates to the fact the structure used by TE YANG =
modules don't match any other YANG modules - they are using their own =
unique style of structure.<o:p></o:p></p></blockquote><p =
class=3DMsoNormal>Regards, B.<br><br><br><o:p></o:p></p><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>&nbsp;<o:p></o:p></pr=
e><pre>Thanks,&nbsp; Xufeng<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>&nbsp;<o:p></o:p></pr=
e><pre>Regards, Benoit<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>&nbsp;<o:p></o:p></pr=
e><pre>Thanks,<o:p></o:p></pre><pre>Rob<o:p></o:p></pre><pre>&nbsp;<o:p><=
/o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>On 22/06/2017 04:16, Xufeng =
Liu wrote:<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>Hi =
Rob,<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>While the tooling =
is very nice to have, especially for writing =
new<o:p></o:p></pre><pre>models or converting models, we do not have to =
use it for every<o:p></o:p></pre><pre>model. It seems not necessary to =
use the tooling on this model for<o:p></o:p></pre><pre>now. We already =
know that we can manually convert it to NMDA style =
if<o:p></o:p></pre><pre>needed.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></p=
re><pre>Thanks,<o:p></o:p></pre><pre>- =
Xufeng<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>-----Original =
Message-----<o:p></o:p></pre><pre>From: Robert Wilton [<a =
href=3D"mailto:rwilton@cisco.com">mailto:rwilton@cisco.com</a>]<o:p></o:p=
></pre><pre>Sent: Wednesday, June 21, 2017 5:34 =
AM<o:p></o:p></pre><pre>To: Xufeng Liu <a =
href=3D"mailto:Xufeng_Liu@jabil.com">&lt;Xufeng_Liu@jabil.com&gt;</a>; =
Mahesh Jethanandani<o:p></o:p></pre><pre><a =
href=3D"mailto:mjethanandani@gmail.com">&lt;mjethanandani@gmail.com&gt;</=
a>; <a =
href=3D"mailto:yang-doctors@ietf.org">yang-doctors@ietf.org</a><o:p></o:p=
></pre><pre>Cc: <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:teas@ietf.org">teas@ietf.org</a>;<o:p></o:p></pre><pre><a =
href=3D"mailto:draft-ietf-teas-yang-te-topo.all@ietf.org">draft-ietf-teas=
-yang-te-topo.all@ietf.org</a><o:p></o:p></pre><pre>Subject: Re: [Teas] =
Yangdoctors last call review =
of<o:p></o:p></pre><pre>draft-ietf-teas-yang-te-topo-<o:p></o:p></pre><pr=
e>08<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Hi =
Xufeng,<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>On 12/06/2017 =
22:28, Xufeng Liu wrote:<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>Hi =
Mahesh,<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Thank you much =
for the review. We have submitted an updated =
draft<o:p></o:p></pre></blockquote><pre>(<a =
href=3D"https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09">http=
s://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09</a>) =
to<o:p></o:p></pre><pre>address these issues. More detailed explanations =
are put below<o:p></o:p></pre><pre>inline.<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>If the responses and =
updates are satisfactory, we are ready for the<o:p></o:p></pre><pre>last =
call.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Best =
regards,<o:p></o:p></pre><pre>- =
Xufeng<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>-----Original =
Message-----<o:p></o:p></pre><pre>From: Mahesh Jethanandani [<a =
href=3D"mailto:mjethanandani@gmail.com">mailto:mjethanandani@gmail.com</a=
>]<o:p></o:p></pre><pre>Sent: Wednesday, May 24, 2017 11:44 =
AM<o:p></o:p></pre><pre>To: <a =
href=3D"mailto:yang-doctors@ietf.org">yang-doctors@ietf.org</a><o:p></o:p=
></pre><pre>Cc: <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:teas@ietf.org">teas@ietf.org</a>;<o:p></o:p></pre><pre><a =
href=3D"mailto:draft-ietf-teas-yang-te-topo.all@ietf.org">draft-ietf-teas=
-yang-te-topo.all@ietf.org</a><o:p></o:p></pre><pre>Subject: Yangdoctors =
last call review =
of<o:p></o:p></pre><pre>draft-ietf-teas-yang-te-topo-08<o:p></o:p></pre><=
pre>&nbsp;<o:p></o:p></pre><pre>Reviewer: Mahesh =
Jethanandani<o:p></o:p></pre><pre>Review result: Ready with =
Issues<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Document =
reviewed: =
draft-ietf-teas-yang-te-topo-08<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></p=
re><pre>Status: Ready with =
Issues<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>I am not an =
expert in Traffic Engineering. This review is =
looking<o:p></o:p></pre><pre>at the draft from a YANG perspective. With =
that said, I have<o:p></o:p></pre><pre>marked it as =
=E2=80=9CReady<o:p></o:p></pre></blockquote></blockquote><pre>with =
Issues=E2=80=9D<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>because of some of =
the points discussed =
below.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Summary:<o:p></o:=
p></pre><pre>&nbsp;<o:p></o:p></pre><pre>This document defines a YANG =
data model for representing,<o:p></o:p></pre><pre>retrieving and =
manipulating TE Topologies. The model serves as =
a<o:p></o:p></pre><pre>base model that other technology specific TE =
Topology models =
can<o:p></o:p></pre></blockquote></blockquote></blockquote></blockquote><=
/blockquote><pre>augment.<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>&nbsp;<o:p></o:p></pr=
e><pre>Comments:<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Almost =
all the containers in the model are presence containers. =
Is<o:p></o:p></pre><pre>there a reason why they have to be presence =
containers? Note, that<o:p></o:p></pre><pre>presence containers are =
containers whose existence itself<o:p></o:p></pre><pre>represents =
configuration data. What particular configuration =
data<o:p></o:p></pre><pre>is each =
container<o:p></o:p></pre></blockquote></blockquote><pre>representing in =
itself?<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>[Xufeng] Containers =
that use =E2=80=9Cpresence=E2=80=9D =
are:<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp; - Container =
=E2=80=9Cunderlay=E2=80=9D<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; o&nbsp; We have changed 13 occurrences of such containers to =
be<o:p></o:p></pre><pre>not<o:p></o:p></pre></blockquote><pre>presence =
container.<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>&nbsp;&nbsp;&nbsp; - =
Container =E2=80=9Cte=E2=80=9D under =
augmentation<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; o&nbsp; =
To indicate that =E2=80=9CTE=E2=80=9D is enabled (configuration =
data)<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; o&nbsp; Also =
used to do augmentation. The =E2=80=9Cpresence=E2=80=9D statement =
can<o:p></o:p></pre></blockquote><pre>prevent the mandatory child from =
affecting augmented base model.<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>&nbsp;&nbsp;&nbsp; - =
/nw:networks/nw:network/nw:network-types/te-topology!<o:p></o:p></pre><pr=
e>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; o&nbsp; A mechanism required by I2RS =
topology model to specify the<o:p></o:p></pre></blockquote><pre>topology =
type.<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>It is difficult to =
co-relate the diagram with the model itself<o:p></o:p></pre><pre>because =
of different terms being used to define different parts =
of<o:p></o:p></pre><pre>the model.<o:p></o:p></pre><pre>There is =
=E2=80=9CTE Topology Model=E2=80=9D and then there is =E2=80=9CGeneric =
TE<o:p></o:p></pre><pre>Topology<o:p></o:p></pre></blockquote></blockquot=
e><pre>Model=E2=80=9D.<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>Are these one and =
the same models? If so, a common term for both<o:p></o:p></pre><pre>of =
them would be helpful.<o:p></o:p></pre></blockquote><pre>[Xufeng] Yes. =
These two terms are the same. Figure 12, Figure =
13,<o:p></o:p></pre><pre>and =
relevant<o:p></o:p></pre></blockquote><pre>descriptions have been =
updated to make the document consistent.<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>There is extensive =
use of groupings in the document. However, not<o:p></o:p></pre><pre>all =
instances of groupings are used multiple number of =
times.<o:p></o:p></pre><pre>Where they are not being repeated, it would =
be better to move the<o:p></o:p></pre><pre>grouping directly where the =
uses statement resides. Case in point<o:p></o:p></pre><pre>the =
grouping<o:p></o:p></pre></blockquote></blockquote><pre>connectivity-labe=
l-restriction-list.<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>[Xufeng] We have =
removed the following =
groupings<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
te-link-augment<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
te-node-augment<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
te-termination-point-augment<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; =
te-topologies-augment<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 te-topology-augment<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
te-link-state-underlay-attributes<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; =
te-node-state-derived-notification<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp=
;&nbsp; =
&nbsp;te-topology-type<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>T=
he remaining groupings have been kept so that we =
can:<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp; - Share the groupings in =
this model<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp; - Prepare to be =
shared by a model augmenting this =
model<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp; - Prevent a grouping or =
configuration section from being too =
long<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp; - Improve =
readability<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>The split between =
config and state containers does not seem to<o:p></o:p></pre><pre>follow =
any particular pattern.<o:p></o:p></pre></blockquote><pre>[Xufeng] The =
pattern is clear:<o:p></o:p></pre><pre>For each manageable entity =
(object), there is a config container<o:p></o:p></pre><pre>and =
state<o:p></o:p></pre></blockquote><pre>container. The configurable =
properties go into the config container<o:p></o:p></pre><pre>and state =
properties go into the state container. Such objects =
are<o:p></o:p></pre><pre>identified by a list item or a presence =
container so that the<o:p></o:p></pre><pre>=E2=80=9Ccreate=E2=80=9D, =
=E2=80=9Cdelete=E2=80=9D, and =
=E2=80=9Cmodify=E2=80=9D<o:p></o:p></pre><pre>operations<o:p></o:p></pre>=
<pre>can be performed on them. The non-presence containers do =
not<o:p></o:p></pre><pre>represent configuration data so they do not =
introduce such objects.<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>It is neither a top =
level split, as is the case with existing =
IETF<o:p></o:p></pre><pre>models,<o:p></o:p></pre></blockquote><pre>[Xufe=
ng] We could not do top level split because the base =
I2RS<o:p></o:p></pre><pre>network<o:p></o:p></pre></blockquote><pre>topol=
ogy model<o:p></o:p></pre><pre>(<a =
href=3D"https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo">ht=
tps://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo</a>-<o:p></o:=
p></pre><pre>12) that we augment does not have the top-level split (for =
its own<o:p></o:p></pre><pre>reasons).<o:p></o:p></pre><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>nor do they follow =
the OpenConfig style of splitting config and<o:p></o:p></pre><pre>state =
under each relevant leaf,<o:p></o:p></pre></blockquote><pre>[Xufeng] The =
pattern is consistent with this style in =
principle,<o:p></o:p></pre><pre>with =
some<o:p></o:p></pre></blockquote><pre>adjustments to fit to our =
multiple levels of hierarchy.<o:p></o:p></pre><pre>This is effectively a =
new forth style of YANG models that is =
not<o:p></o:p></pre><pre>consistent with any of the three existing =
styles, i.e.:<o:p></o:p></pre><pre>&nbsp;&nbsp; - Current IETF =
config/state split model style<o:p></o:p></pre><pre>&nbsp;&nbsp; - NMDA =
combined config/state tree<o:p></o:p></pre><pre>&nbsp;&nbsp; - =
OpenConfig split config/state containers immediately above =
the<o:p></o:p></pre><pre>config true =
leaves.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Tooling that it =
designed to work with OpenConfig models will =
need<o:p></o:p></pre><pre>customization to work with these TE models =
because the config/state<o:p></o:p></pre><pre>containers will not be =
where the tooling expects them to =
be.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Thanks,<o:p></o:p></=
pre><pre>Rob<o:p></o:p></pre></blockquote></blockquote><pre>&nbsp;<o:p></=
o:p></pre><pre>.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre></blockquote=
></blockquote><pre>&nbsp;<o:p></o:p></pre></blockquote><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div></blockquote><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_024B_01D2F429.BF43E520--



From nobody Mon Jul  3 17:14:11 2017
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 398221317FF; Mon,  3 Jul 2017 17:14:09 -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 h1MA8cOlZKDS; Mon,  3 Jul 2017 17:14:07 -0700 (PDT)
Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::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 4EECE1317AE; Mon,  3 Jul 2017 17:14:07 -0700 (PDT)
Received: by mail-lf0-x22a.google.com with SMTP id t72so528247lff.1; Mon, 03 Jul 2017 17:14:07 -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=LURtEY7WlNeKhgLd435kgVoHEAVVrCBiG6fcdmvoCAI=; b=Dz1CCSZIMV2y4PnfvhA0v4jP/OUR3UFOXjXI5h4eXgvTsjw+LdWPTjQp3VlVlUxbOE yskpmHvvm94hgRnOksPPrMg9OQ2FNX3fbIB0b3to+2rmL+AUJwuzEUS3jsHktFK3zRHA Q0wgic5ndt2BZzcNsmZW47n4JV2lczzVQDIxU8DmZ1NLIftNfiERBsjCf5qO3oPilxdA i1Ei5Kk2gK8V5yevKz3ylrRrRYcgGtvqUh/YwHaiOyXOukkUu66rVhHIhjlrkzeRnywa 4PvWB48/Y+QF4sGolpDQrgMBXTxMRttNAsZ+lzyrXcXnhNCQlqX+hII24HtY042oR+XX qfsA==
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=LURtEY7WlNeKhgLd435kgVoHEAVVrCBiG6fcdmvoCAI=; b=GuOAh0hO/+67+5UcDSDO47pSgxu4xLfdK2eSUprx9Ko0aGeUkoSrrcZoYvMepsFtdj wE3t2uJIH7Xz+xZ4i79RkPmhslM0isYfAWvsWF8Mc1SKi8R7wTedJ0t3IVPONIJlDkmz Yhu/MuVa2l+JqA7MKbj/Nrf2czqiFmL+QF97hrITsUXgPDXbg2pFUAWg/Ez+yD+S0BIB /6nKiurhRBXbe5jSCMDruGxE854RwaVLi1xBuboHLz3E0gT//0QDk8nn5PXeVHuWB2e2 /oGArRWZtSuETPlC2T7K7u/hcGOM9X5QS8GOrQOQvLAMlOcon5gl8oY1bsw+KY4pUw9K LMxQ==
X-Gm-Message-State: AIVw1130br6GVDRHirDbonhHxp/zWxYfv41OaAbPiUxfWF+fljNQriTG ssIB/f/ANXQmUZzeJQVvWRA8Dcxw1rev9sE=
X-Received: by 10.46.83.7 with SMTP id h7mr1877217ljb.22.1499127245540; Mon, 03 Jul 2017 17:14:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.69.84 with HTTP; Mon, 3 Jul 2017 17:14:04 -0700 (PDT)
In-Reply-To: <bb3631d2-f5b5-d6b0-958f-ac9c10aaddec@nostrum.com>
References: <149909744835.22804.5791695515985213782@ietfa.amsl.com> <bb3631d2-f5b5-d6b0-958f-ac9c10aaddec@nostrum.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 4 Jul 2017 10:14:04 +1000
Message-ID: <CABkgnnUXMiMYYvmT2tV3=V_J3JGc2Cqvyo0R30nY27vL52t7eA@mail.gmail.com>
Subject: Re: Opsdir last call review of draft-ietf-webpush-vapid-03
To: Adam Roach <adam@nostrum.com>
Cc: Stefan Winter <stefan.winter@restena.lu>, "ops-dir@ietf.org" <ops-dir@ietf.org>,  "webpush@ietf.org" <webpush@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, draft-ietf-webpush-vapid.all@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RRVaHPkZ9Ag8XfcDcK0rgk-Eabs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 00:14:09 -0000

On 4 July 2017 at 03:31, Adam Roach <adam@nostrum.com> wrote:
> # echo
> eyJhdWQiOiJodHRwczovL3B1c2guZXhhbXBsZS5uZXQiLCJleHAiOjE0NTM1MjM3NjgsInN1YiI6Im1haWx0bzpwdXNoQGV4YW1wbGUuY29tIn0
> | base64 --decode
>
> {"aud":"https://push.example.net","exp":1453523768,"sub":"mailto:push@example.com

I get this:

$ echo eyJhdWQiOiJodHRwczovL3B1c2guZXhhbXBsZS5uZXQiLCJleHAiOjE0NTM1MjM3NjgsInN1YiI6Im1haWx0bzpwdXNoQGV4YW1wbGUuY29tIn0
| base64 --decode
{"aud":"https://push.example.net","exp":1453523768,"sub":"mailto:push@example.com"}base64:
invalid input

Which fills me with confidence in the base64 tool.  You'll note that
the trailing quote and curly brace are present here, but there is an
inexplicable error that adding the -i option doesn't remove.

I built this using my own implementation and verified it, but you will
see that this works too:

$ npm install base64url;node -e
'console.log(require("base64url").decode("eyJhdWQiOiJodHRwczovL3B1c2guZXhhbXBsZS5uZXQiLCJleHAiOjE0NTM1MjM3NjgsInN1YiI6Im1haWx0bzpwdXNoQGV4YW1wbGUuY29tIn0"))'
{"aud":"https://push.example.net","exp":1453523768,"sub":"mailto:push@example.com"}

(note that running this leaves a node_modules lying around).

https://www.base64decode.org/ also agrees.


From nobody Mon Jul  3 17:20:37 2017
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8320612F28E; Mon,  3 Jul 2017 17:20:35 -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, RCVD_IN_DNSWL_MED=-2.3, 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 vqMgph1vKhhs; Mon,  3 Jul 2017 17:20:30 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 AACFE1317AE; Mon,  3 Jul 2017 17:20:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v640KPVk002870; Tue, 4 Jul 2017 02:20:25 +0200 (CEST)
Received: from [192.168.217.124] (p5DC7F3A7.dip0.t-ipconnect.de [93.199.243.167]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3x1l5P1TRGz3ZH7; Tue,  4 Jul 2017 02:20:25 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Opsdir last call review of draft-ietf-webpush-vapid-03
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CABkgnnUXMiMYYvmT2tV3=V_J3JGc2Cqvyo0R30nY27vL52t7eA@mail.gmail.com>
Date: Tue, 4 Jul 2017 02:20:23 +0200
Cc: Adam Roach <adam@nostrum.com>, Stefan Winter <stefan.winter@restena.lu>, "ops-dir@ietf.org" <ops-dir@ietf.org>, draft-ietf-webpush-vapid.all@ietf.org, "ietf@ietf.org" <ietf@ietf.org>, "webpush@ietf.org" <webpush@ietf.org>
X-Mao-Original-Outgoing-Id: 520820422.828225-aaad11f0fde59b23389472456d56b79e
Content-Transfer-Encoding: quoted-printable
Message-Id: <93C3F14F-A6B9-4682-9173-7BE10D1A8EA2@tzi.org>
References: <149909744835.22804.5791695515985213782@ietfa.amsl.com> <bb3631d2-f5b5-d6b0-958f-ac9c10aaddec@nostrum.com> <CABkgnnUXMiMYYvmT2tV3=V_J3JGc2Cqvyo0R30nY27vL52t7eA@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/skOKxzMPGrkJ3xDibfoOCQOdF84>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 00:20:35 -0000

base64 classic seems to need padding and reacts differently on different =
versions when that is missing.

(I=E2=80=99d like to meet someone who can explain what they were =
thinking when they invented padding.)

Gr=C3=BC=C3=9Fe, Carsten


> On Jul 4, 2017, at 02:14, Martin Thomson <martin.thomson@gmail.com> =
wrote:
>=20
> On 4 July 2017 at 03:31, Adam Roach <adam@nostrum.com> wrote:
>> # echo
>> =
eyJhdWQiOiJodHRwczovL3B1c2guZXhhbXBsZS5uZXQiLCJleHAiOjE0NTM1MjM3NjgsInN1Yi=
I6Im1haWx0bzpwdXNoQGV4YW1wbGUuY29tIn0
>> | base64 --decode
>>=20
>> =
{"aud":"https://push.example.net","exp":1453523768,"sub":"mailto:push@exam=
ple.com
>=20
> I get this:
>=20
> $ echo =
eyJhdWQiOiJodHRwczovL3B1c2guZXhhbXBsZS5uZXQiLCJleHAiOjE0NTM1MjM3NjgsInN1Yi=
I6Im1haWx0bzpwdXNoQGV4YW1wbGUuY29tIn0
> | base64 --decode
> =
{"aud":"https://push.example.net","exp":1453523768,"sub":"mailto:push@exam=
ple.com"}base64:
> invalid input
>=20
> Which fills me with confidence in the base64 tool.  You'll note that
> the trailing quote and curly brace are present here, but there is an
> inexplicable error that adding the -i option doesn't remove.
>=20
> I built this using my own implementation and verified it, but you will
> see that this works too:
>=20
> $ npm install base64url;node -e
> =
'console.log(require("base64url").decode("eyJhdWQiOiJodHRwczovL3B1c2guZXhh=
bXBsZS5uZXQiLCJleHAiOjE0NTM1MjM3NjgsInN1YiI6Im1haWx0bzpwdXNoQGV4YW1wbGUuY2=
9tIn0"))'
> =
{"aud":"https://push.example.net","exp":1453523768,"sub":"mailto:push@exam=
ple.com"}
>=20
> (note that running this leaves a node_modules lying around).
>=20
> https://www.base64decode.org/ also agrees.
>=20
>=20


From nobody Mon Jul  3 17:25:16 2017
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8F4E13181B; Mon,  3 Jul 2017 17:25:11 -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, FREEMAIL_FROM=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 3t2UMHmqy5uI; Mon,  3 Jul 2017 17:25:08 -0700 (PDT)
Received: from mail-lf0-x231.google.com (mail-lf0-x231.google.com [IPv6:2a00:1450:4010:c07::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 F16E0131814; Mon,  3 Jul 2017 17:25:03 -0700 (PDT)
Received: by mail-lf0-x231.google.com with SMTP id b207so110140455lfg.2; Mon, 03 Jul 2017 17:25:03 -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=wLztgpu0/8eTvKnxPAhVAwWpPckYX8N5LsjBQKIOT9A=; b=EJ54BPlgin4ePYYYl7G5pRZ2GDUFRbtXJvxhD3WWhRL9+uLiRmG0TnRr9/NRJw72hS b9I6k13G2nPKkuvElJ3m/0RUyykKbpW1acBHThxzXfM+YQ91IPnoHraXA1kAQnqu0KQx RCqEAenyBC6zlXTR5vPmATqfQJyinre3jFr7qT9V5EdwHALLg1Dewcspnc7LptH08nnL 3FcjXJtxzuac0WqTjdXHVD3ERXBUged1PolLa4R4l32or7k/H7dEGmNNobXQlh/TkpDt DE7zC1bX3j9NvbY0PuPjfele4IbyiaXP9SV2thbLjcWDWQOvMY+XrpffU8RjZ3QFZ/vX yWtA==
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=wLztgpu0/8eTvKnxPAhVAwWpPckYX8N5LsjBQKIOT9A=; b=DJcyk6NTDwXgB8hhJu46WkY0VdLgyHB/G40bVIbTLzILdoU6/qnr93E/pimuEuKgCG arouiUsepA1h9Fhz2KACBb8MVewrehnESgepFpk7yQPe0eiKO6lEpZupDwY8EHo2p/g5 xU/LfTFt96tJe+YZvI5cxQOJ5RN2SPdBRk/ZH+Toy6doOShSX1DzuW3+gqnF7OljuGk7 3QeB+wjATT9xN80+BU9bJMHO0sqQFK6cD/BHs5Nabk95GP3eCy90O3e0DZMoDUsWaPhM 5wUuW+vNVgPNQYbXzl0/m0kz2u0cf2uVF9GkDONYu/Rd81Rq/Mn0X1uuGdmRPk9d5KSB /e8A==
X-Gm-Message-State: AKS2vOw8qBBHoX57I1MJ1WzYmoDXXj0LKXl5G4X34vixyZvKgNXG4iK+ qZy6f5MWXwkANMsFzrlrzdpRSr1wFQ==
X-Received: by 10.46.77.70 with SMTP id a67mr11843344ljb.103.1499127902275; Mon, 03 Jul 2017 17:25:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.69.84 with HTTP; Mon, 3 Jul 2017 17:25:01 -0700 (PDT)
In-Reply-To: <93C3F14F-A6B9-4682-9173-7BE10D1A8EA2@tzi.org>
References: <149909744835.22804.5791695515985213782@ietfa.amsl.com> <bb3631d2-f5b5-d6b0-958f-ac9c10aaddec@nostrum.com> <CABkgnnUXMiMYYvmT2tV3=V_J3JGc2Cqvyo0R30nY27vL52t7eA@mail.gmail.com> <93C3F14F-A6B9-4682-9173-7BE10D1A8EA2@tzi.org>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 4 Jul 2017 10:25:01 +1000
Message-ID: <CABkgnnWvQHPe0VPjZq372NisukW3aOuk6wv+EK43r+d67RQe2w@mail.gmail.com>
Subject: Re: Opsdir last call review of draft-ietf-webpush-vapid-03
To: Carsten Bormann <cabo@tzi.org>
Cc: Adam Roach <adam@nostrum.com>, Stefan Winter <stefan.winter@restena.lu>,  "ops-dir@ietf.org" <ops-dir@ietf.org>, draft-ietf-webpush-vapid.all@ietf.org,  "ietf@ietf.org" <ietf@ietf.org>, "webpush@ietf.org" <webpush@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/netXySBJE4jP0wiDS3Ge8jNRPoo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 00:25:12 -0000

On 4 July 2017 at 10:20, Carsten Bormann <cabo@tzi.org> wrote:
> base64 classic seems to need padding and reacts differently on different versions when that is missing.

Ahh, another example of insufficient application of Postel's Maxim.
Adding "=" fixes this particular problem.


From nobody Mon Jul  3 19:32:42 2017
Return-Path: <terry.manderson@icann.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACB72131614 for <ietf@ietfa.amsl.com>; Mon,  3 Jul 2017 19:32:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level: 
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 fIoQeGFyAcmg for <ietf@ietfa.amsl.com>; Mon,  3 Jul 2017 19:32:38 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-1.pexch112.icann.org [64.78.40.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E429E129413 for <ietf@ietf.org>; Mon,  3 Jul 2017 19:32:38 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Mon, 3 Jul 2017 19:32:36 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1178.000; Mon, 3 Jul 2017 19:32:36 -0700
From: Terry Manderson <terry.manderson@icann.org>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: FW: [homenet] Ray and Mark are stepping down - Call for chair nominations
Thread-Topic: [homenet] Ray and Mark are stepping down - Call for chair nominations
Thread-Index: AQHS9G3LpQy6tzTy3024HEMs3xsi/g==
Date: Tue, 4 Jul 2017 02:32:35 +0000
Message-ID: <CD0F900B-893D-4151-832A-DB8FAB5DDBE2@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.20.0.170309
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3582016353_427003176"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Kpt7RdYu_BCMk3EdcZw_BkKkq_w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 02:32:41 -0000

--B_3582016353_427003176
Content-type: multipart/mixed;
	boundary="B_3582016353_413892854"


--B_3582016353_413892854
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: 7bit

All,

I'm reposting this here for your awareness and interest.

Please email me directly (and offlist) if you are interested in a co-chair role in HOMENET and you would might the criteria as below.

Cheers,
Terry

On 21/06/2017, 10:37 AM, "homenet on behalf of Terry Manderson" <homenet-bounces@ietf.org on behalf of terry.manderson@icann.org> wrote:

    Dear HOMENET WG,
    
    Both Ray and Mark (your WG Chairs) have expressed a desire to step down from the chair role. The HOMENET WG has had quite a tumultuous history and both Ray and Mark have seen it though with professionalism and a commitment to the Workgroup and the technology. For that they have my sincere thanks as Internet Area Director. Buying them a beer when next you see them in the bar would be a fine gesture as they certainly put in a significant effort for the WG! :)
    
    With that, the job of HOMENET is not yet over - there are milestones to be achieved and contributions yet to be put forward. Therefore, this is a call for (self) nominations for two new HOMENET chairs. Please email your expression of interest (detailing your IETF and Standards experience) directly to me by the 10th of July (UTC).
    
    There are some expertise qualities I am looking for in the new chairs; awareness of DNS, naming systems, service discovery, security, and privacy. A candidate does not necessarily need to cover all of these facets, however my goal would be that between the two new chairs, this expertise is present. Naturally, I'm looking for candidates who are great communicators, understand the need for cross area dialog, and have shown that they embrace the IETF consensus process. Experience in an IETF leadership role is desired, but not mandatory.  
    
    After the 10th of July Ray, Mark, and I will review the expressions of interest and create a shortlist. I will then have a discussion with shortlisted candidates in Prague and the chairs will be seated soon after the Prague meeting.
    
    Ray has kindly offered to be a 3rd chair to help with chair-transition in between Prague and Singapore, so for a few months HOMNET will have the attention of 3 chairs.
    
    Cheers
    Terry
    


--B_3582016353_413892854
Content-type: application/pkcs7-signature; name="smime.p7s"
Content-ID: <F13A44A9BFF32149AF695C13751AC440@pexch112.icann.org>
Content-disposition: attachment;
	filename="smime.p7s"
Content-transfer-encoding: base64


MIIYwwYJKoZIhvcNAQcCoIIYtDCCGLACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
FowwggV0MIIEXKADAgECAhAJ0fxYYYV36W1njUywVtW8MA0GCSqGSIb3DQEBCwUAMGUxCzAJ
BgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2Vy
dC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IFNIQTIgQXNzdXJlZCBJRCBDQTAeFw0xNTAzMjYw
MDAwMDBaFw0xODAzMjYxMjAwMDBaMIGQMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZv
cm5pYTEUMBIGA1UEBxMLTG9zIEFuZ2VsZXMxPDA6BgNVBAoTM0ludGVybmV0IENvcnBvcmF0
aW9uIGZvciBBc3NpZ25lZCBOYW1lcyBhbmQgTnVtYmVyczEYMBYGA1UEAxMPVGVycnkgTWFu
ZGVyc29uMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwTImt0Ol/9dOAbnm4lby
4RG1iQEnHVB5UJTYqwX8kqEhA5NPFHbMX22ChnP7M/zIlY+OP2TfKcwfdF5DJN4ybt4gFGzE
9ksigMe365F0uA2Q4+CskwqWo2fGIqrhgb0C68bg6EnZxj73KlJ0mvbQqzLBY8fVwr8srWpB
BexjbYSeXp/+0W41ZOJPcdii59TDXRBGuziWjp+rd7yh8KCzKcj/Px1TzAE5U/TftZOfigYi
h6KTTDZBGnN+4DDaaCnZ93rveayavI3hd4agqiIWe/gB78+0vHyk5DFoe6HkwuL0qJVaBW57
KIt8AYq+p0P+igNhiQoHkPx3VvS7ZViGdQIDAQABo4IB8jCCAe4wHwYDVR0jBBgwFoAU5wIj
gABP2Ne8lAvZP3Q5STI8inkwHQYDVR0OBBYEFIXwv/ZX+K34v+mCL8g1Coo9c6lMMAwGA1Ud
EwEB/wQCMAAwJAYDVR0RBB0wG4EZdGVycnkubWFuZGVyc29uQGljYW5uLm9yZzAOBgNVHQ8B
Af8EBAMCBaAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMEMGA1UdIAQ8MDowOAYK
YIZIAYb9bAQBAjAqMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy5kaWdpY2VydC5jb20vQ1BT
MIGIBgNVHR8EgYAwfjA9oDugOYY3aHR0cDovL2NybDMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0
U0hBMkFzc3VyZWRJRENBLWcxLmNybDA9oDugOYY3aHR0cDovL2NybDQuZGlnaWNlcnQuY29t
L0RpZ2lDZXJ0U0hBMkFzc3VyZWRJRENBLWcxLmNybDB5BggrBgEFBQcBAQRtMGswJAYIKwYB
BQUHMAGGGGh0dHA6Ly9vY3NwLmRpZ2ljZXJ0LmNvbTBDBggrBgEFBQcwAoY3aHR0cDovL2Nh
Y2VydHMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0U0hBMkFzc3VyZWRJRENBLmNydDANBgkqhkiG
9w0BAQsFAAOCAQEAH1Dvq3r4yh4+zU4t+5Rg3EzwMpSPxApBivVcW/KPq9uwdlu3yGBPJlG9
j4BXOT7fEUEGpCfyfRhBzTReyc2zask73fDRTzNFl5U3gqzOre5+Xtzv0qHyZGZ2EGcPTFv9
oaAVTug//Z6ZSr4dtDphV/7uSA4Hj1riFh5yxHErwUfrbCneIspVqwSVJqjkKWGID6W0YB0D
cYJZGlyAH0FP/4+TMDxXOti2ypQrsZpNSfvc4TGC1p13Lyp4XEY+UysVtcypAgersTBN6gCb
7ueBt5KPTj9pH4w4C0lNO6rRIc6AGtJIuXHYyiy9CXUTOT5xLToXLZCyPXd+HFuWwdD9lzCC
Bk4wggU2oAMCAQICEASueWBmZpAaucV/pmxb3M0wDQYJKoZIhvcNAQELBQAwZTELMAkGA1UE
BhMCVVMxFTATBgNVBAoTDERpZ2lDZXJ0IEluYzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNv
bTEkMCIGA1UEAxMbRGlnaUNlcnQgQXNzdXJlZCBJRCBSb290IENBMB4XDTEzMTEwNTEyMDAw
MFoXDTI4MTEwNTEyMDAwMFowZTELMAkGA1UEBhMCVVMxFTATBgNVBAoTDERpZ2lDZXJ0IElu
YzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNvbTEkMCIGA1UEAxMbRGlnaUNlcnQgU0hBMiBB
c3N1cmVkIElEIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3PgRIz9qte/A
J3kbLQWHohBDMd8O1BUbT3ekIs4+jHDwvgeO3ScqvAEdtiwKyt1pWB9B7WoFH9pjeFkeIiwr
+Lp+yTU7VvEffEJ+JbAjGcZFONc9RPkgfGCuHLBaGAS+jzv3qfCUmqYMY0m2QRdTQDK9T+ZQ
elAfJUXo8Ymvzf9e/1Dz8BcR/73FifW9YrnY+45FBIVtmc3FSE39JqsCNkXqNtdfauIagkEK
3OnZ9ZEXjsYhrTg8E+Yef2ac1U3ZRtr2z1KnfTskw7TBUTXGm+vU737kewPhRL16CzfgT8uC
ig1xGOSm4IksG/OyczzBsJKeGH29q33FfQihLMKfcwIDAQABo4IC+DCCAvQwEgYDVR0TAQH/
BAgwBgEB/wIBADAOBgNVHQ8BAf8EBAMCAYYwNAYIKwYBBQUHAQEEKDAmMCQGCCsGAQUFBzAB
hhhodHRwOi8vb2NzcC5kaWdpY2VydC5jb20wgYEGA1UdHwR6MHgwOqA4oDaGNGh0dHA6Ly9j
cmw0LmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRFJvb3RDQS5jcmwwOqA4oDaGNGh0
dHA6Ly9jcmwzLmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRFJvb3RDQS5jcmwwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMIIBswYDVR0gBIIBqjCCAaYwggGiBgpghkgB
hv1sAAIEMIIBkjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cuZGlnaWNlcnQuY29tL0NQUzCC
AWQGCCsGAQUFBwICMIIBVh6CAVIAQQBuAHkAIAB1AHMAZQAgAG8AZgAgAHQAaABpAHMAIABD
AGUAcgB0AGkAZgBpAGMAYQB0AGUAIABjAG8AbgBzAHQAaQB0AHUAdABlAHMAIABhAGMAYwBl
AHAAdABhAG4AYwBlACAAbwBmACAAdABoAGUAIABEAGkAZwBpAEMAZQByAHQAIABDAFAALwBD
AFAAUwAgAGEAbgBkACAAdABoAGUAIABSAGUAbAB5AGkAbgBnACAAUABhAHIAdAB5ACAAQQBn
AHIAZQBlAG0AZQBuAHQAIAB3AGgAaQBjAGgAIABsAGkAbQBpAHQAIABsAGkAYQBiAGkAbABp
AHQAeQAgAGEAbgBkACAAYQByAGUAIABpAG4AYwBvAHIAcABvAHIAYQB0AGUAZAAgAGgAZQBy
AGUAaQBuACAAYgB5ACAAcgBlAGYAZQByAGUAbgBjAGUALjAdBgNVHQ4EFgQU5wIjgABP2Ne8
lAvZP3Q5STI8inkwHwYDVR0jBBgwFoAUReuir/SSy4IxLVGLp6chnfNtyA8wDQYJKoZIhvcN
AQELBQADggEBAE7UiSe5/R2Hd34PKAWQ8QovyTs+vZOckMav+pFRhzJUa+jKwXFRXJmOtfrg
YhmZpgeafBMn2+UCooQS2RX2CkRXxDSPbXMfOtagAT3e44LkRWuy6yX9gF4dOZC+W0L2zpFg
4/mgVgxIEM4zaHvNk6vwastPWA+5e10bBIGepyLiV0kn7pKTCL5pCFMCOi5dyBn0UIBOAtmw
XZG0k4f5lpaBVUCOZu2C2LsoX+1MYe0GWCgZUxFEvEcgKbIEbNiJVJk7ddtneCweknjGVT1Y
EhEybr1DDE0023vGQtvsvqubYUwGkuOO3yEqUFcEwGCiNdUknmY3CUnP1fhls+DibsIwggO3
MIICn6ADAgECAhAM5+DlF9hG/o/lYPwb8DA5MA0GCSqGSIb3DQEBBQUAMGUxCzAJBgNVBAYT
AlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2VydC5jb20x
JDAiBgNVBAMTG0RpZ2lDZXJ0IEFzc3VyZWQgSUQgUm9vdCBDQTAeFw0wNjExMTAwMDAwMDBa
Fw0zMTExMTAwMDAwMDBaMGUxCzAJBgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMx
GTAXBgNVBAsTEHd3dy5kaWdpY2VydC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IEFzc3VyZWQg
SUQgUm9vdCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAK0OFc7kQ4BcsYfz
t2D5cRKlrtwmlIiq9M71IDkoWGAM+IDaqRWVMmE8tbEohIqK3J8KDIMXeo+QrIrneVNcMYQq
9g+YMjZ2zN7dPKii72r7IfJSYd+fINcf4rHZ/hhk0hJbX/lYGDW8R82hNvlrf9SwOD7BG8OM
M9nYLxj+KA+zp4PWw25EwGE1lhb+WZyLdm3X8aJLDSv/C3LanmDQjpA1xnhVhyChz+VtCshJ
fDGYM2wi6YfQMlqiuhOCEe05F52ZOnKh5vqk2dUXMXWuhX0irj8BRob2KHnIsdrkVxfEfhwO
sLSSplazvbKX7aqn8LfFqD+VFtD/oZbrCF8Yd08CAwEAAaNjMGEwDgYDVR0PAQH/BAQDAgGG
MA8GA1UdEwEB/wQFMAMBAf8wHQYDVR0OBBYEFEXroq/0ksuCMS1Ri6enIZ3zbcgPMB8GA1Ud
IwQYMBaAFEXroq/0ksuCMS1Ri6enIZ3zbcgPMA0GCSqGSIb3DQEBBQUAA4IBAQCiDrzf4u3w
43JzemSUv/dyZtgy5EJ1Yq6H6/LV2d5Ws5/MzhQouQ2XYFwSTFjk0z2DSUVYlzVpGqhH6lbG
easS2GeBhN9/CTyU5rgmLCC9PbMoifdf/yLil4Qf6WXvh+DfwWdJs13rsgkq6ybteL59Pyvz
tyY1bV+JAbZJW58BBZurPSXBzLZ/wvFvhsb6ZGjrgS2U60K3+owe3WLxvlBnt2y98/Efaww2
BxZ/N3ypW2168RJGYIPXJwS+S86XvsNnKmgR34DnDDNmvxMNFG7zfx9jEB76jRslbWyPpbdh
AbHSoyahEHGdreLD+cOZUbcrBwjOLuZQsqf6CkUvovDyMIIHAzCCBeugAwIBAgIQD89pSVGb
AJQ9+ZeKCcX9BTANBgkqhkiG9w0BAQUFADBiMQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGln
aUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGlnaWNlcnQuY29tMSEwHwYDVQQDExhEaWdpQ2Vy
dCBBc3N1cmVkIElEIENBLTEwHhcNMTIwMzI3MDAwMDAwWhcNMTUwMzI3MTIwMDAwWjCBrDEL
MAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExFzAVBgNVBAcTDk1hcmluYSBkZWwg
UmV5MTwwOgYDVQQKEzNJbnRlcm5ldCBDb3Jwb3JhdGlvbiBmb3IgQXNzaWduZWQgTmFtZXMg
YW5kIE51bWJlcnMxFzAVBgNVBAsTDkROUyBPcGVyYXRpb25zMRgwFgYDVQQDEw9UZXJyeSBN
YW5kZXJzb24wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCkYWeFt1OjJ30tsKGB
BQiMjfoNTDSC6JG1CpPj05eZpit0LVkMU0jrtrHczcRzMuqdkaE/QTBjmprbRatlrMEq7uv+
yU9U35crRmjx3yuZDD/6SOO4ZnMFBJvWdevSOWq+8wU4hAEANOnBirYCfF4oixVCBy1bkat1
hsY5xUx5QB12OpnYA0/57QJ6BL7z1ZuF6lJ4yYmU0qI88q9atkahb8l7Nm5TgEbpg6ryyN98
ixnFLmhC/gPoYKHczP3y+JHaMveuJl75hHq6ZuHeH2PyX20VFsXNBKJrvZ8BhTZOoozuNapP
jiG6HLdqngPuTz3JVyTTR2FX809nclnxoMWjAgMBAAGjggNoMIIDZDAfBgNVHSMEGDAWgBQV
ABIrE5iymQftHt+ivlcNK2cCzTAdBgNVHQ4EFgQUs8L0dmF6T/V40vXJJzF+YNyzNo0wJAYD
VR0RBB0wG4EZdGVycnkubWFuZGVyc29uQGljYW5uLm9yZzAOBgNVHQ8BAf8EBAMCBaAwHQYD
VR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMCMH0GA1UdHwR2MHQwOKA2oDSGMmh0dHA6Ly9j
cmwzLmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRENBLTEuY3JsMDigNqA0hjJodHRw
Oi8vY3JsNC5kaWdpY2VydC5jb20vRGlnaUNlcnRBc3N1cmVkSURDQS0xLmNybDCCAcUGA1Ud
IASCAbwwggG4MIIBtAYKYIZIAYb9bAQBAjCCAaQwOgYIKwYBBQUHAgEWLmh0dHA6Ly93d3cu
ZGlnaWNlcnQuY29tL3NzbC1jcHMtcmVwb3NpdG9yeS5odG0wggFkBggrBgEFBQcCAjCCAVYe
ggFSAEEAbgB5ACAAdQBzAGUAIABvAGYAIAB0AGgAaQBzACAAQwBlAHIAdABpAGYAaQBjAGEA
dABlACAAYwBvAG4AcwB0AGkAdAB1AHQAZQBzACAAYQBjAGMAZQBwAHQAYQBuAGMAZQAgAG8A
ZgAgAHQAaABlACAARABpAGcAaQBDAGUAcgB0ACAAQwBQAC8AQwBQAFMAIABhAG4AZAAgAHQA
aABlACAAUgBlAGwAeQBpAG4AZwAgAFAAYQByAHQAeQAgAEEAZwByAGUAZQBtAGUAbgB0ACAA
dwBoAGkAYwBoACAAbABpAG0AaQB0ACAAbABpAGEAYgBpAGwAaQB0AHkAIABhAG4AZAAgAGEA
cgBlACAAaQBuAGMAbwByAHAAbwByAGEAdABlAGQAIABoAGUAcgBlAGkAbgAgAGIAeQAgAHIA
ZQBmAGUAcgBlAG4AYwBlAC4wdwYIKwYBBQUHAQEEazBpMCQGCCsGAQUFBzABhhhodHRwOi8v
b2NzcC5kaWdpY2VydC5jb20wQQYIKwYBBQUHMAKGNWh0dHA6Ly9jYWNlcnRzLmRpZ2ljZXJ0
LmNvbS9EaWdpQ2VydEFzc3VyZWRJRENBLTEuY3J0MAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcN
AQEFBQADggEBAGKcMSvyr3YW8kKqyqdspTEKTc6lR6H6OITyC056f6PlMmFZ+nWlkopWlflz
QcxOUZv3+5rNogNcwczrxr+eaSx9J+pYCEU3rgBs3yiLDwsD72EJJDAD1x84fQOOJtfYb4oE
4Djzco83Dk4h6sMAiUg0xGcdewhJK80D6tb3xtS75PgFoxLcQrBprLghx2mY8EPErBiO1uXA
NWOEU3EH+kvXiKUrDsFyGHQ4FqvVIYv2plu68ltOmBh+wR2oraoJpt9jGbond1MyVFOvi48e
7hgPRXupNbjxB4Wl0wKKGz0qT3ToBpp8VAkULtjiO/iPLx4knuwwvy5sRAwuZAfpVE4xggH/
MIIB+wIBATB5MGUxCzAJBgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNV
BAsTEHd3dy5kaWdpY2VydC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IFNIQTIgQXNzdXJlZCBJ
RCBDQQIQCdH8WGGFd+ltZ41MsFbVvDAJBgUrDgMCGgUAoF0wIwYJKoZIhvcNAQkEMRYEFOQ+
jgreDfQmvlJo8LAxDo6T0hswMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN
AQkFMQ8XDTE3MDYyMTAwMzc0OVowDQYJKoZIhvcNAQEBBQAEggEAZxnlfom+klYOZvw5YN3F
aJkj9bFMJeyVtHpmup0MzpKfYGbdvkTvmi2+qNlMx+BVfAD5YoQdntxJ35lq3sMswebu54uE
aLdEE6pN3bwiLtOQy+7C+WkeKi4n7AGelRrgViEuFzCRjrbDiIy+Q+roLKqaQoJYAAdGq6yy
geb7zh59aYaAYyLBkrLOFGKzmmAfuJsmpS4EwTRmpDaDO+HEc0j/R6HqbduxjKxhp8UU5vXq
bH6b+V+jvjUYXG793XBcc/SJHh0P6MQ9F9CDVxaoD/7r1BRM6KVi//ise0KkxGMZRSxzMr0w
+LjymMmsmlJMFa7PzvFIEDGAtPfVgV3vpA==
--B_3582016353_413892854
Content-type: text/plain; name="ATT00001.txt"
Content-ID: <35C98084B82CEB4EBCB5DD5519568AC1@pexch112.icann.org>
Content-disposition: attachment;
	filename="ATT00001.txt"
Content-transfer-encoding: base64


X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCmhvbWVu
ZXQgbWFpbGluZyBsaXN0DQpob21lbmV0QGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL2hvbWVuZXQNCg==
--B_3582016353_413892854--

--B_3582016353_427003176
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIYwwYJKoZIhvcNAQcCoIIYtDCCGLACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
FowwggV0MIIEXKADAgECAhAJ0fxYYYV36W1njUywVtW8MA0GCSqGSIb3DQEBCwUAMGUxCzAJ
BgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2Vy
dC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IFNIQTIgQXNzdXJlZCBJRCBDQTAeFw0xNTAzMjYw
MDAwMDBaFw0xODAzMjYxMjAwMDBaMIGQMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZv
cm5pYTEUMBIGA1UEBxMLTG9zIEFuZ2VsZXMxPDA6BgNVBAoTM0ludGVybmV0IENvcnBvcmF0
aW9uIGZvciBBc3NpZ25lZCBOYW1lcyBhbmQgTnVtYmVyczEYMBYGA1UEAxMPVGVycnkgTWFu
ZGVyc29uMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwTImt0Ol/9dOAbnm4lby
4RG1iQEnHVB5UJTYqwX8kqEhA5NPFHbMX22ChnP7M/zIlY+OP2TfKcwfdF5DJN4ybt4gFGzE
9ksigMe365F0uA2Q4+CskwqWo2fGIqrhgb0C68bg6EnZxj73KlJ0mvbQqzLBY8fVwr8srWpB
BexjbYSeXp/+0W41ZOJPcdii59TDXRBGuziWjp+rd7yh8KCzKcj/Px1TzAE5U/TftZOfigYi
h6KTTDZBGnN+4DDaaCnZ93rveayavI3hd4agqiIWe/gB78+0vHyk5DFoe6HkwuL0qJVaBW57
KIt8AYq+p0P+igNhiQoHkPx3VvS7ZViGdQIDAQABo4IB8jCCAe4wHwYDVR0jBBgwFoAU5wIj
gABP2Ne8lAvZP3Q5STI8inkwHQYDVR0OBBYEFIXwv/ZX+K34v+mCL8g1Coo9c6lMMAwGA1Ud
EwEB/wQCMAAwJAYDVR0RBB0wG4EZdGVycnkubWFuZGVyc29uQGljYW5uLm9yZzAOBgNVHQ8B
Af8EBAMCBaAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMEMGA1UdIAQ8MDowOAYK
YIZIAYb9bAQBAjAqMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy5kaWdpY2VydC5jb20vQ1BT
MIGIBgNVHR8EgYAwfjA9oDugOYY3aHR0cDovL2NybDMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0
U0hBMkFzc3VyZWRJRENBLWcxLmNybDA9oDugOYY3aHR0cDovL2NybDQuZGlnaWNlcnQuY29t
L0RpZ2lDZXJ0U0hBMkFzc3VyZWRJRENBLWcxLmNybDB5BggrBgEFBQcBAQRtMGswJAYIKwYB
BQUHMAGGGGh0dHA6Ly9vY3NwLmRpZ2ljZXJ0LmNvbTBDBggrBgEFBQcwAoY3aHR0cDovL2Nh
Y2VydHMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0U0hBMkFzc3VyZWRJRENBLmNydDANBgkqhkiG
9w0BAQsFAAOCAQEAH1Dvq3r4yh4+zU4t+5Rg3EzwMpSPxApBivVcW/KPq9uwdlu3yGBPJlG9
j4BXOT7fEUEGpCfyfRhBzTReyc2zask73fDRTzNFl5U3gqzOre5+Xtzv0qHyZGZ2EGcPTFv9
oaAVTug//Z6ZSr4dtDphV/7uSA4Hj1riFh5yxHErwUfrbCneIspVqwSVJqjkKWGID6W0YB0D
cYJZGlyAH0FP/4+TMDxXOti2ypQrsZpNSfvc4TGC1p13Lyp4XEY+UysVtcypAgersTBN6gCb
7ueBt5KPTj9pH4w4C0lNO6rRIc6AGtJIuXHYyiy9CXUTOT5xLToXLZCyPXd+HFuWwdD9lzCC
Bk4wggU2oAMCAQICEASueWBmZpAaucV/pmxb3M0wDQYJKoZIhvcNAQELBQAwZTELMAkGA1UE
BhMCVVMxFTATBgNVBAoTDERpZ2lDZXJ0IEluYzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNv
bTEkMCIGA1UEAxMbRGlnaUNlcnQgQXNzdXJlZCBJRCBSb290IENBMB4XDTEzMTEwNTEyMDAw
MFoXDTI4MTEwNTEyMDAwMFowZTELMAkGA1UEBhMCVVMxFTATBgNVBAoTDERpZ2lDZXJ0IElu
YzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNvbTEkMCIGA1UEAxMbRGlnaUNlcnQgU0hBMiBB
c3N1cmVkIElEIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3PgRIz9qte/A
J3kbLQWHohBDMd8O1BUbT3ekIs4+jHDwvgeO3ScqvAEdtiwKyt1pWB9B7WoFH9pjeFkeIiwr
+Lp+yTU7VvEffEJ+JbAjGcZFONc9RPkgfGCuHLBaGAS+jzv3qfCUmqYMY0m2QRdTQDK9T+ZQ
elAfJUXo8Ymvzf9e/1Dz8BcR/73FifW9YrnY+45FBIVtmc3FSE39JqsCNkXqNtdfauIagkEK
3OnZ9ZEXjsYhrTg8E+Yef2ac1U3ZRtr2z1KnfTskw7TBUTXGm+vU737kewPhRL16CzfgT8uC
ig1xGOSm4IksG/OyczzBsJKeGH29q33FfQihLMKfcwIDAQABo4IC+DCCAvQwEgYDVR0TAQH/
BAgwBgEB/wIBADAOBgNVHQ8BAf8EBAMCAYYwNAYIKwYBBQUHAQEEKDAmMCQGCCsGAQUFBzAB
hhhodHRwOi8vb2NzcC5kaWdpY2VydC5jb20wgYEGA1UdHwR6MHgwOqA4oDaGNGh0dHA6Ly9j
cmw0LmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRFJvb3RDQS5jcmwwOqA4oDaGNGh0
dHA6Ly9jcmwzLmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRFJvb3RDQS5jcmwwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMIIBswYDVR0gBIIBqjCCAaYwggGiBgpghkgB
hv1sAAIEMIIBkjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cuZGlnaWNlcnQuY29tL0NQUzCC
AWQGCCsGAQUFBwICMIIBVh6CAVIAQQBuAHkAIAB1AHMAZQAgAG8AZgAgAHQAaABpAHMAIABD
AGUAcgB0AGkAZgBpAGMAYQB0AGUAIABjAG8AbgBzAHQAaQB0AHUAdABlAHMAIABhAGMAYwBl
AHAAdABhAG4AYwBlACAAbwBmACAAdABoAGUAIABEAGkAZwBpAEMAZQByAHQAIABDAFAALwBD
AFAAUwAgAGEAbgBkACAAdABoAGUAIABSAGUAbAB5AGkAbgBnACAAUABhAHIAdAB5ACAAQQBn
AHIAZQBlAG0AZQBuAHQAIAB3AGgAaQBjAGgAIABsAGkAbQBpAHQAIABsAGkAYQBiAGkAbABp
AHQAeQAgAGEAbgBkACAAYQByAGUAIABpAG4AYwBvAHIAcABvAHIAYQB0AGUAZAAgAGgAZQBy
AGUAaQBuACAAYgB5ACAAcgBlAGYAZQByAGUAbgBjAGUALjAdBgNVHQ4EFgQU5wIjgABP2Ne8
lAvZP3Q5STI8inkwHwYDVR0jBBgwFoAUReuir/SSy4IxLVGLp6chnfNtyA8wDQYJKoZIhvcN
AQELBQADggEBAE7UiSe5/R2Hd34PKAWQ8QovyTs+vZOckMav+pFRhzJUa+jKwXFRXJmOtfrg
YhmZpgeafBMn2+UCooQS2RX2CkRXxDSPbXMfOtagAT3e44LkRWuy6yX9gF4dOZC+W0L2zpFg
4/mgVgxIEM4zaHvNk6vwastPWA+5e10bBIGepyLiV0kn7pKTCL5pCFMCOi5dyBn0UIBOAtmw
XZG0k4f5lpaBVUCOZu2C2LsoX+1MYe0GWCgZUxFEvEcgKbIEbNiJVJk7ddtneCweknjGVT1Y
EhEybr1DDE0023vGQtvsvqubYUwGkuOO3yEqUFcEwGCiNdUknmY3CUnP1fhls+DibsIwggO3
MIICn6ADAgECAhAM5+DlF9hG/o/lYPwb8DA5MA0GCSqGSIb3DQEBBQUAMGUxCzAJBgNVBAYT
AlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2VydC5jb20x
JDAiBgNVBAMTG0RpZ2lDZXJ0IEFzc3VyZWQgSUQgUm9vdCBDQTAeFw0wNjExMTAwMDAwMDBa
Fw0zMTExMTAwMDAwMDBaMGUxCzAJBgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMx
GTAXBgNVBAsTEHd3dy5kaWdpY2VydC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IEFzc3VyZWQg
SUQgUm9vdCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAK0OFc7kQ4BcsYfz
t2D5cRKlrtwmlIiq9M71IDkoWGAM+IDaqRWVMmE8tbEohIqK3J8KDIMXeo+QrIrneVNcMYQq
9g+YMjZ2zN7dPKii72r7IfJSYd+fINcf4rHZ/hhk0hJbX/lYGDW8R82hNvlrf9SwOD7BG8OM
M9nYLxj+KA+zp4PWw25EwGE1lhb+WZyLdm3X8aJLDSv/C3LanmDQjpA1xnhVhyChz+VtCshJ
fDGYM2wi6YfQMlqiuhOCEe05F52ZOnKh5vqk2dUXMXWuhX0irj8BRob2KHnIsdrkVxfEfhwO
sLSSplazvbKX7aqn8LfFqD+VFtD/oZbrCF8Yd08CAwEAAaNjMGEwDgYDVR0PAQH/BAQDAgGG
MA8GA1UdEwEB/wQFMAMBAf8wHQYDVR0OBBYEFEXroq/0ksuCMS1Ri6enIZ3zbcgPMB8GA1Ud
IwQYMBaAFEXroq/0ksuCMS1Ri6enIZ3zbcgPMA0GCSqGSIb3DQEBBQUAA4IBAQCiDrzf4u3w
43JzemSUv/dyZtgy5EJ1Yq6H6/LV2d5Ws5/MzhQouQ2XYFwSTFjk0z2DSUVYlzVpGqhH6lbG
easS2GeBhN9/CTyU5rgmLCC9PbMoifdf/yLil4Qf6WXvh+DfwWdJs13rsgkq6ybteL59Pyvz
tyY1bV+JAbZJW58BBZurPSXBzLZ/wvFvhsb6ZGjrgS2U60K3+owe3WLxvlBnt2y98/Efaww2
BxZ/N3ypW2168RJGYIPXJwS+S86XvsNnKmgR34DnDDNmvxMNFG7zfx9jEB76jRslbWyPpbdh
AbHSoyahEHGdreLD+cOZUbcrBwjOLuZQsqf6CkUvovDyMIIHAzCCBeugAwIBAgIQD89pSVGb
AJQ9+ZeKCcX9BTANBgkqhkiG9w0BAQUFADBiMQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGln
aUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGlnaWNlcnQuY29tMSEwHwYDVQQDExhEaWdpQ2Vy
dCBBc3N1cmVkIElEIENBLTEwHhcNMTIwMzI3MDAwMDAwWhcNMTUwMzI3MTIwMDAwWjCBrDEL
MAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExFzAVBgNVBAcTDk1hcmluYSBkZWwg
UmV5MTwwOgYDVQQKEzNJbnRlcm5ldCBDb3Jwb3JhdGlvbiBmb3IgQXNzaWduZWQgTmFtZXMg
YW5kIE51bWJlcnMxFzAVBgNVBAsTDkROUyBPcGVyYXRpb25zMRgwFgYDVQQDEw9UZXJyeSBN
YW5kZXJzb24wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCkYWeFt1OjJ30tsKGB
BQiMjfoNTDSC6JG1CpPj05eZpit0LVkMU0jrtrHczcRzMuqdkaE/QTBjmprbRatlrMEq7uv+
yU9U35crRmjx3yuZDD/6SOO4ZnMFBJvWdevSOWq+8wU4hAEANOnBirYCfF4oixVCBy1bkat1
hsY5xUx5QB12OpnYA0/57QJ6BL7z1ZuF6lJ4yYmU0qI88q9atkahb8l7Nm5TgEbpg6ryyN98
ixnFLmhC/gPoYKHczP3y+JHaMveuJl75hHq6ZuHeH2PyX20VFsXNBKJrvZ8BhTZOoozuNapP
jiG6HLdqngPuTz3JVyTTR2FX809nclnxoMWjAgMBAAGjggNoMIIDZDAfBgNVHSMEGDAWgBQV
ABIrE5iymQftHt+ivlcNK2cCzTAdBgNVHQ4EFgQUs8L0dmF6T/V40vXJJzF+YNyzNo0wJAYD
VR0RBB0wG4EZdGVycnkubWFuZGVyc29uQGljYW5uLm9yZzAOBgNVHQ8BAf8EBAMCBaAwHQYD
VR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMCMH0GA1UdHwR2MHQwOKA2oDSGMmh0dHA6Ly9j
cmwzLmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRENBLTEuY3JsMDigNqA0hjJodHRw
Oi8vY3JsNC5kaWdpY2VydC5jb20vRGlnaUNlcnRBc3N1cmVkSURDQS0xLmNybDCCAcUGA1Ud
IASCAbwwggG4MIIBtAYKYIZIAYb9bAQBAjCCAaQwOgYIKwYBBQUHAgEWLmh0dHA6Ly93d3cu
ZGlnaWNlcnQuY29tL3NzbC1jcHMtcmVwb3NpdG9yeS5odG0wggFkBggrBgEFBQcCAjCCAVYe
ggFSAEEAbgB5ACAAdQBzAGUAIABvAGYAIAB0AGgAaQBzACAAQwBlAHIAdABpAGYAaQBjAGEA
dABlACAAYwBvAG4AcwB0AGkAdAB1AHQAZQBzACAAYQBjAGMAZQBwAHQAYQBuAGMAZQAgAG8A
ZgAgAHQAaABlACAARABpAGcAaQBDAGUAcgB0ACAAQwBQAC8AQwBQAFMAIABhAG4AZAAgAHQA
aABlACAAUgBlAGwAeQBpAG4AZwAgAFAAYQByAHQAeQAgAEEAZwByAGUAZQBtAGUAbgB0ACAA
dwBoAGkAYwBoACAAbABpAG0AaQB0ACAAbABpAGEAYgBpAGwAaQB0AHkAIABhAG4AZAAgAGEA
cgBlACAAaQBuAGMAbwByAHAAbwByAGEAdABlAGQAIABoAGUAcgBlAGkAbgAgAGIAeQAgAHIA
ZQBmAGUAcgBlAG4AYwBlAC4wdwYIKwYBBQUHAQEEazBpMCQGCCsGAQUFBzABhhhodHRwOi8v
b2NzcC5kaWdpY2VydC5jb20wQQYIKwYBBQUHMAKGNWh0dHA6Ly9jYWNlcnRzLmRpZ2ljZXJ0
LmNvbS9EaWdpQ2VydEFzc3VyZWRJRENBLTEuY3J0MAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcN
AQEFBQADggEBAGKcMSvyr3YW8kKqyqdspTEKTc6lR6H6OITyC056f6PlMmFZ+nWlkopWlflz
QcxOUZv3+5rNogNcwczrxr+eaSx9J+pYCEU3rgBs3yiLDwsD72EJJDAD1x84fQOOJtfYb4oE
4Djzco83Dk4h6sMAiUg0xGcdewhJK80D6tb3xtS75PgFoxLcQrBprLghx2mY8EPErBiO1uXA
NWOEU3EH+kvXiKUrDsFyGHQ4FqvVIYv2plu68ltOmBh+wR2oraoJpt9jGbond1MyVFOvi48e
7hgPRXupNbjxB4Wl0wKKGz0qT3ToBpp8VAkULtjiO/iPLx4knuwwvy5sRAwuZAfpVE4xggH/
MIIB+wIBATB5MGUxCzAJBgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNV
BAsTEHd3dy5kaWdpY2VydC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IFNIQTIgQXNzdXJlZCBJ
RCBDQQIQCdH8WGGFd+ltZ41MsFbVvDAJBgUrDgMCGgUAoF0wIwYJKoZIhvcNAQkEMRYEFNMe
3C0cu1NI5YB7cwKsHmlunoWDMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN
AQkFMQ8XDTE3MDcwNDAyMzIzM1owDQYJKoZIhvcNAQEBBQAEggEAL0C5NC+fdShfuNDzlasN
Vv0JuNJHfSZo2ppKsGX8PL5FLIj3tjjyaNpZngJDsAEnBgOI7x8eOfAffPOMkUwnoB5QWr94
x8iKLFDY8+46QviLYV5Mg5CU32zaCfdOD2FxyoHUvxMN/OubgFGgIx99bRwJzXL+pzXS0ZUN
gtr9B9m7ogjQ5FPxcXqKPQqGGtdK85v3NPF0JC5Ni8LY65ah8bgqOQwwJfo0qzofQih1wYAL
nrLDp/YUsVrsMLLL94JLPbKtmTxumZN/9jTmRCZGVhnQbmg+1bGhjeSIQS35tiWpTWFaDyf0
bGIDOO2e6P2wAadKPK3BNzhOFOmCia/Q6A==

--B_3582016353_427003176--


From nobody Tue Jul  4 00:39:32 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D4DD131A71; Tue,  4 Jul 2017 00:39:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 PhiCM8mtJoOp; Tue,  4 Jul 2017 00:39:28 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 DB74D131A70; Tue,  4 Jul 2017 00:39:28 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dSIQg-0004ev-IN; Tue, 04 Jul 2017 07:39:26 +0000
Date: Tue, 04 Jul 2017 09:39:25 +0200
Message-ID: <m2a84kzm4y.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Warren Kumari <warren@kumari.net>
Cc: dnsop@ietf.org, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: Minor editorial change to draft-ietf-dnsop-sutld-ps
In-Reply-To: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TgkoSnB8H_nHBe06V-CdkW53Hi0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 07:39:30 -0000

> The Special-Use Domain Names Problem Statement document unsurprisingly
> contains a list of problems.

is there a companion document with the list of benefits/advantages?  or
is thins just one of those ietf documents from on high meant to kill
something?

randy, who does not have a dog in this fight, just smells dog poop


From nobody Tue Jul  4 02:44:10 2017
Return-Path: <chris.dearlove@baesystems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCC82131CB7 for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 02:44:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.126
X-Spam-Level: 
X-Spam-Status: No, score=-6.126 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RDNS_NONE=0.793] 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 P8PprDWilY-Q for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 02:44:06 -0700 (PDT)
Received: from ukmta1.baesystems.com (unknown [20.133.0.55]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18FB6131CC1 for <ietf@ietf.org>; Tue,  4 Jul 2017 02:44:05 -0700 (PDT)
X-IronPort-AV: E=Sophos; i="5.40,307,1496098800"; d="scan'208,217"; a="10187027"
Received: from unknown (HELO baemasmds016.greenlnk.net) ([10.15.207.101]) by ukmta1.baesystems.com with ESMTP; 04 Jul 2017 10:44:04 +0100
X-IronPort-AV: E=Sophos;i="5.40,307,1496098800"; d="scan'208,217";a="8567616"
Received: from glkxh0004v.greenlnk.net ([10.109.2.35]) by baemasmds016.greenlnk.net with ESMTP; 04 Jul 2017 10:44:04 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.118]) by GLKXH0004V.GREENLNK.net ([10.109.2.35]) with mapi id 14.03.0248.002; Tue, 4 Jul 2017 10:44:04 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Internet Draft block on post-IETF LC IDs
Thread-Topic: Internet Draft block on post-IETF LC IDs
Thread-Index: AdL0qhBRiqQLJKOfTlOGMW4pLUJgHg==
Date: Tue, 4 Jul 2017 09:44:04 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6386604@GLKXM0002V.GREENLNK.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: multipart/alternative; boundary="_000_B31EEDDDB8ED7E4A93FDF12A4EECD30DE6386604GLKXM0002VGREEN_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DcOGjifO2SRi5ud-BHAdRyus9G0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 09:44:09 -0000

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30DE6386604GLKXM0002VGREEN_
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

I (and co-authors) have an Internet Draft that's reached the IESG stage. It=
's due an update. In fact we have a specific request from our AD to update =
it before telechat this week.  Done that update but can't submit due to  pr=
e-meeting block. There are reasons for that, but they really don't apply to=
 anything post-IETF LC stage, specifically IESG review.

Of course I've sent a copy to the AD, and he may be able to bypass. But I'd=
 actually like to keep his load down - and I expect another update soon (po=
ssibly after telechat, hence not waiting to do both together).

Is it worth considering if/how this can be allowed? More work to create the=
 capability I appreciate (and having to make sure interface makes it clear =
that only such IDs will work). But aiming to take a bit of work off one of =
the most critically loaded part of the system.

--
Christopher Dearlove
Senior Principal Engineer
BAE Systems Applied Intelligence Laboratories
__________________________________________________________________________

T:  +44 3300 467500  |  E: chris.dearlove@baesystems.com<mailto:chris.dearl=
ove@baesystems.com>

BAE Systems Applied Intelligence, Chelmsford Technology Park, Great Baddow,=
 Chelmsford, Essex CM2 8HN.
www.baesystems.com/ai<http://www.baesystems.com/ai>
BAE Systems Applied Intelligence Limited
Registered in England & Wales No: 01337451
Registered Office: Surrey Research Park, Guildford, Surrey, GU2 7YP

********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30DE6386604GLKXM0002VGREEN_
Content-Type: text/html; charset="us-ascii"
MIME-Version: 1.0
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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
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;}
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";
	mso-fareast-language:EN-US;}
@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">I (and co-authors) have an Internet Draft that&#8217=
;s reached the IESG stage. It&#8217;s due an update. In fact we have a spec=
ific request from our AD to update it before telechat this week. &nbsp;Done=
 that update but can&#8217;t submit due to&nbsp; pre-meeting block.
 There are reasons for that, but they really don&#8217;t apply to anything =
post-IETF LC stage, specifically IESG review.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Of course I&#8217;ve sent a copy to the AD, and he m=
ay be able to bypass. But I&#8217;d actually like to keep his load down - a=
nd I expect another update soon (possibly after telechat, hence not waiting=
 to do both together).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Is it worth considering if/how this can be allowed? =
More work to create the capability I appreciate (and having to make sure in=
terface makes it clear that only such IDs will work). But aiming to take a =
bit of work off one of the most critically
 loaded part of the system.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><b><span style=3D"fon=
t-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#0=
07E7E;mso-fareast-language:EN-GB">--
<o:p></o:p></span></b></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><b><span style=3D"fon=
t-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#0=
07E7E;mso-fareast-language:EN-GB">Christopher Dearlove<br>
Senior Principal Engineer<br>
BAE Systems Applied Intelligence Laboratories<br>
</span></b><b><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif=
&quot;;color:#BEBEBE;mso-fareast-language:EN-GB">__________________________=
________________________________________________<br>
</span></b><span style=3D"font-size:8.0pt;font-family:&quot;Arial&quot;,&qu=
ot;sans-serif&quot;;color:#00007E;mso-fareast-language:EN-GB"><br>
</span><b><span style=3D"font-size:8.0pt;font-family:&quot;Arial&quot;,&quo=
t;sans-serif&quot;;color:#7D7D7D;mso-fareast-language:EN-GB">T</span></b><s=
pan style=3D"font-size:8.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif=
&quot;;color:#7D7D7D;mso-fareast-language:EN-GB">: &nbsp;&#43;44 3300 46750=
0 &nbsp;| &nbsp;<b>E:
</b><a href=3D"mailto:chris.dearlove@baesystems.com"><span style=3D"color:b=
lue">chris.dearlove@baesystems.com</span></a><br>
</span><span style=3D"font-size:8.0pt;font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;;color:#00007E;mso-fareast-language:EN-GB"><br>
</span><span style=3D"font-size:8.0pt;font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;;color:#3A8B92;mso-fareast-language:EN-GB">BAE Systems Appli=
ed Intelligence, Chelmsford Technology Park, Great Baddow, Chelmsford, Esse=
x CM2 8HN.<br>
<a href=3D"http://www.baesystems.com/ai"><span style=3D"color:#3A8B92">www.=
baesystems.com/ai</span></a><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:8.0pt;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;;color:#3A8B92;mso-fareast-language:EN-GB">B=
AE Systems Applied Intelligence Limited<br>
Registered in England &amp; Wales No: 01337451<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:8.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#3A8B9=
2;mso-fareast-language:EN-GB">Registered Office: Surrey Research Park, Guil=
dford, Surrey, GU2 7YP<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p>********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************</p></b=
ody>
</html>

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30DE6386604GLKXM0002VGREEN_--


From nobody Tue Jul  4 02:57:49 2017
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A1EF131D2E; Tue,  4 Jul 2017 02:57:34 -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-sipcore-content-id.all@ietf.org, sipcore@ietf.org, ietf@ietf.org
Subject: Genart telechat review of draft-ietf-sipcore-content-id-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149916225425.16088.10318703158229973440@ietfa.amsl.com>
Date: Tue, 04 Jul 2017 02:57:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nXeVXXVhk40AwxsbDDyan6-noyU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 09:57:34 -0000

Reviewer: Elwyn Davies
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-sipcore-content-id-07
Reviewer: Elwyn Davies
Review Date: 2017-07-04
IETF LC End Date: 2017-06-27
IESG Telechat date: 2017-07-06

Summary:
Ready.  Thank you for addressing the comments in my last call review.

Major issues:

Minor issues:

Nits/editorial comments:
The references to RFC 5368 and RFC 6442 are informative rather than normative -
you don't need the details to implement this update.


From nobody Tue Jul  4 04:27:40 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C8CE129A9F for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 04:27:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 ZNVUdY6W8yA9 for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 04:27:37 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:1829::130]) by ietfa.amsl.com (Postfix) with ESMTP id B71FD131574 for <ietf@ietf.org>; Tue,  4 Jul 2017 04:27:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 0EF942CFB2; Tue,  4 Jul 2017 14:27:34 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P12BIez6iWgZ; Tue,  4 Jul 2017 14:27:33 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:1829::130]) by p130.piuha.net (Postfix) with ESMTP id 949122CEE4; Tue,  4 Jul 2017 14:27:33 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Subject: Re: Internet Draft block on post-IETF LC IDs
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_C64CA32D-B36F-4ADF-97A9-C169C8CEEAAA"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6386604@GLKXM0002V.GREENLNK.net>
Date: Tue, 4 Jul 2017 14:27:32 +0300
Cc: "ietf@ietf.org" <ietf@ietf.org>
Message-Id: <3E469A47-95F5-4403-8004-F7A97CE6DC1C@piuha.net>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6386604@GLKXM0002V.GREENLNK.net>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QL1E6EsxclnxXKkOCHNc7IroXdk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 11:27:39 -0000

--Apple-Mail=_C64CA32D-B36F-4ADF-97A9-C169C8CEEAAA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

ADs regularly grant such requests, and you have a very good reason.

The question is if code should be added to not have a submission block
when tracker state is past WG process (e.g., Waiting for Writeup,  =
Waiting
or AD Go-Ahead, IESG Evaluation, IESG Evaluation - Defer, or
Approved-announcement to be sent).

Maybe. (But it is also not a big load on the ADs, and they=92d probably
still want to make exceptions on case-by-case basis.)

Personally, I think there are a lot of cases where updates should just
be allowed. For instance, you published a big update in time for the
meeting and for your topic to get on the WG agenda; you should be
allowed to fix bugs that people report to you as they prepare for the
meeting. Then again, many people are doing this on github anyway,
so the importance of a particular draft version is diminishing a bit,
along with the significance of the blocking period.

Jari


--Apple-Mail=_C64CA32D-B36F-4ADF-97A9-C169C8CEEAAA
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJZW3ulAAoJEM80gCTQU46qoRIQAMShg5tiNJ/IVRJRHVIpIkhq
oFnZSqFYl+rNufukEM+1pKnrqsh5pFreu0juxHZwX7Lb+Tz2NF11m4zWJksufBUq
FCZR5E6KVz1Ai/VxykiKMmwfRaheMg5qg34/dv41O4C7H77afQOzyAQqyi0cFI68
+EoFqWM79UJJ2u6+U8pjMdPw6b4M/Fw1ZEcRuBaMqKebu2H9Dozly2/MthNm1K7X
T2y7ABBt/w3awcPsB+TAoh5GhgrD5VLvg445YaCSu1StiW/LJQOFLM06gImGkUfO
j8EEKIfohhsxBIB/GNWYRqTrunilV7Udms/zqpT1aJ/hrhAHYqf1TsGPpQcnxJjN
ms6hJHTp5IM6+0chotMNLlDsqhO2jEn+Xg1MqfgqChrYmbZ2xue4DDApoq8w9yhn
DUovtLV8AaZgg9GgRKEeqVkihNQz3CUhqdshEObYx6EpHS5/2ENrHYgFQCMlwyZC
02XSXbxd9iCDV8o34jOQVOaCd7jYMwPu+MmplBfYEgs5MKAAyeb0u3YUa0SKvBqd
2MUW5YVHK2InI7IFtoCqf+bZuwx2TblTWWFXQsJRBZ24+FEy2scZjvdD9IB0tX8M
AXVnWQK+tQGpTN/klMxsuB0h/Lz+imJ0bPs4sTU5y3/s1SMf4PXYaDgfHZXw2Fu0
ftT0slz6e8PYuVwSidFe
=1/R0
-----END PGP SIGNATURE-----

--Apple-Mail=_C64CA32D-B36F-4ADF-97A9-C169C8CEEAAA--


From nobody Tue Jul  4 04:28:20 2017
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD7B9129A9F; Tue,  4 Jul 2017 04:28:19 -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, FREEMAIL_FROM=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 lv-vrrkWPZuD; Tue,  4 Jul 2017 04:28:18 -0700 (PDT)
Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (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 71D51131F1D; Tue,  4 Jul 2017 04:28:17 -0700 (PDT)
Received: by mail-qk0-x233.google.com with SMTP id v143so81884048qkb.0; Tue, 04 Jul 2017 04:28:17 -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=217Qkbjcosa32WFONDm+lfqdU0/1E3brVKetZdus0FQ=; b=JjaqZeHvZOEB3vpzNbr/UITI6XYMXjC6Pxr1LKR8L3kvxNw4zkL8Uf5hyZHH7LE8nx hZJSuPS33b6iNrILlPyC0jHNnPk+z6x+I0e/hbUpUvkltIqGDIeeTevbumKZtCGwfTKS fkl40QqNlk/OLhCIDS2C+xciM4oZv7a7M3gbarFoBekm4n9gtE0inAIXT1pxzXTNATNU lz6heg5OAphUe9GeyDeqKjOul6N8Ybu3/HzfawVP6Yuw6eGwQF3BHkTpd1iV8TmfNzsE /c1q024DXSVXOQI2GeIZrGFPhcT/AnpjbDBlaDQUf7e5tDtmv80bDTuj55IDyhnmoz5L VC4w==
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=217Qkbjcosa32WFONDm+lfqdU0/1E3brVKetZdus0FQ=; b=uLHnQ9piPIaxjZCaDMUUPvDyNghMwhrWtmqamPEfwkj6RjNiS45eyGKAH6e/zaItMb 14bOgQEzXjdRAUCIsN/EPz8GO61Ye2xWb3RW+I5SbMHb9VZWV7OVAuCpLU4Oe0myBwii 5rYebA4fT7wihpZlGmbRTJobuKcDFaOBLiBHQl+i83zaauC0TwWrvm6Qd3i1jRMHiG7c XOtbV+KcTAWB6U1dWOgFu36T9IRD6M0m5mUAbktla8yyN0revpmmqsLNhCYVHALY1WWV vZoIcUEcWE6kvy29am9fHemAXeq5+6bdHU2iVvVKedMLliEGqwfFbuzkm17hzQDPBg1I 2vWg==
X-Gm-Message-State: AKS2vOzBDF1cq+IE6zSDHDj5IZbDh1jrkZRSYK6FAXJ7AF27y3vigoZE 54pd9mEe5xMyUcre9VY=
X-Received: by 10.55.204.133 with SMTP id n5mr48238073qkl.135.1499167696654; Tue, 04 Jul 2017 04:28:16 -0700 (PDT)
Received: from ?IPv6:2601:18f:801:600:4488:ee:f477:1020? ([2601:18f:801:600:4488:ee:f477:1020]) by smtp.gmail.com with ESMTPSA id t11sm15523737qtt.47.2017.07.04.04.28.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Jul 2017 04:28:16 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Minor editorial change to draft-ietf-dnsop-sutld-ps
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <m2a84kzm4y.wl-randy@psg.com>
Date: Tue, 4 Jul 2017 07:28:12 -0400
Cc: Warren Kumari <warren@kumari.net>, dnsop@ietf.org, IETF Rinse Repeat <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C77F491C-E69C-4A24-8DDD-A233489D52AF@gmail.com>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wA2mAMF3GBEKQgyeiRUhKw5_tHI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 11:28:20 -0000

> On Jul 4, 2017, at 3:39 AM, Randy Bush <randy@psg.com> wrote:
>=20
>> The Special-Use Domain Names Problem Statement document =
unsurprisingly
>> contains a list of problems.
>=20
> is there a companion document with the list of benefits/advantages?

It's a list of problems, not solutions, so there aren't benefits and/or =
advantages.

>  or
> is thins just one of those ietf documents from on high meant to kill
> something?

It's not intended as a dead-end, either.  It is intended as a reference =
document for solution documents to point at.  Warren add numbering to =
the list so the problems could be referenced more easily by solutions =
documents, such as draft-ietf-dnsop-alt-tld-08=20

>=20
> randy, who does not have a dog in this fight, just smells dog poop
>=20

- Ralph



From nobody Tue Jul  4 05:14:48 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EF5A131FE5; Tue,  4 Jul 2017 05:14:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 CPnIGDvARHKu; Tue,  4 Jul 2017 05:14:38 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 B6B22131FE3; Tue,  4 Jul 2017 05:14:38 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dSMix-0005p6-Kq; Tue, 04 Jul 2017 12:14:35 +0000
Date: Tue, 04 Jul 2017 14:14:34 +0200
Message-ID: <m2zickxutx.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Cc: Warren Kumari <warren@kumari.net>, dnsop@ietf.org, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: Minor editorial change to draft-ietf-dnsop-sutld-ps
In-Reply-To: <C77F491C-E69C-4A24-8DDD-A233489D52AF@gmail.com>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <C77F491C-E69C-4A24-8DDD-A233489D52AF@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fplwp9oZGTw9f8JLsKiD-x7TBBE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 12:14:40 -0000

>>> The Special-Use Domain Names Problem Statement document unsurprisingly
>>> contains a list of problems.
>> 
>> is there a companion document with the list of benefits/advantages?
> 
> It's a list of problems, not solutions, so there aren't benefits
> and/or advantages.

so there are no advntages to special use domain spaces.  got it.

>> or is thins just one of those ietf documents from on high meant to
>> kill something?

i guess so, eh?

randy


From nobody Tue Jul  4 06:23:43 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E9AF13146A for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 06:23:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 3Yv1MW3GCDta for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 06:23:39 -0700 (PDT)
Received: from mail-qt0-x22a.google.com (mail-qt0-x22a.google.com [IPv6:2607:f8b0:400d:c0d::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 A1D34131441 for <ietf@ietf.org>; Tue,  4 Jul 2017 06:23:39 -0700 (PDT)
Received: by mail-qt0-x22a.google.com with SMTP id b40so56748625qtb.2 for <ietf@ietf.org>; Tue, 04 Jul 2017 06:23:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ou7b3m34UhCdE18S0bqD1OlTy4/NP2PQg/oUQVl3xxk=; b=1TohnQB2C+AACdtEua6w4WE97ExxTZdUAKIvqEm6MpIcPfnAw7ERd/Afg0N6YfKKpE fHCIh4962spgUYvh7xzHEjrzYm7gm/V1/1nW3n++JG/5Jg2T+N+N8DfPtzZMJxk18vMh jyy9NebhvLnt2LS09Vm+DoSpRsLnps/hiuA2btAfLUJhModduqF2F5JyA6DkWbBRQUpj qUsAcpltQlyCSx0B3sH7vTOcfMuGX1I5Km7OubqtzYsz2RH/VeMm0VsLkKsOqLtNDt25 rLczHgZ93GmaWSVjnOZJoCuZHgQNdpRyIUkMK/E0Bc1mePdvXQ0++A00g7eWGiahCekv BaKA==
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=ou7b3m34UhCdE18S0bqD1OlTy4/NP2PQg/oUQVl3xxk=; b=YvAlK+X/xTUIP0DCN9zUkWVtVQTVlYvXchQUubxObwI+jkFPDaureqTL+DyQv6G2BW SIff4eTSCW2YlE645X5WAfUvzg7Un9xfNMJhUgLGNvHTOOZXzFrPcA8G7obxFCXEO9TM hbCxnMU/2QcrEIem3NO5RYPg8aDh0HrbyC+ccNzifQObaF2ayMV/Cb38eA7Cxqs8CwTO HraR6fbSSTg65od7MM+ADIDZkf4AGN9GUCNOvcOa1xy6FEQi+1rLrmdOzUAqFo/oog7z QERf9j50N9dlkv9xoU/QTxgJRcI/YSSCPR9w6jCyrloCCnXkHgyZys+rgPcfZX5if/y8 UCAg==
X-Gm-Message-State: AKS2vOx2B2Y+eMThwn9rx5Uq1TFy8pjIVFEMU7N6zNoLojxQIpXaL+Cc 2fPts1vstS1aRUKM
X-Received: by 10.237.34.196 with SMTP id q4mr40864807qtc.39.1499174618803; Tue, 04 Jul 2017 06:23:38 -0700 (PDT)
Received: from [10.0.30.114] (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id f29sm15771305qtc.13.2017.07.04.06.23.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Jul 2017 06:23:38 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
Subject: Re: Minor editorial change to draft-ietf-dnsop-sutld-ps
From: Ted Lemon <mellon@fugue.com>
X-Mailer: iPad Mail (15A5304i)
In-Reply-To: <m2a84kzm4y.wl-randy@psg.com>
Date: Tue, 4 Jul 2017 09:23:37 -0400
Cc: Warren Kumari <warren@kumari.net>, dnsop@ietf.org, IETF Rinse Repeat <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rknF6FPpSRLZZ0IVDSr8kh6vCQw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 13:23:41 -0000

On Jul 4, 2017, at 3:39 AM, Randy Bush <randy@psg.com> wrote:
> is there a companion document with the list of benefits/advantages?  or
> is thins just one of those ietf documents from on high meant to kill
> something?

This is a very good question. We weren=E2=80=99t asked to answer that questi=
on, so we didn=E2=80=99t.  It is assumed throughout the document that variou=
s proponents of special use domains have good reasons for wanting them, and f=
urther that it is already accepted in principle that if their reason for wan=
ting them is valid, they can have them (modulo technical constraints like de=
legation). So we didn=E2=80=99t delve into that. But perhaps we should have.=
=20=


From nobody Tue Jul  4 06:37:09 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 204DD13160E; Tue,  4 Jul 2017 06:37:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 IU8FRxGzJfDA; Tue,  4 Jul 2017 06:37:06 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 2FC7C131613; Tue,  4 Jul 2017 06:37:06 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dSO0l-0000hd-5t; Tue, 04 Jul 2017 13:37:03 +0000
Date: Tue, 04 Jul 2017 15:37:02 +0200
Message-ID: <m2shicxr0h.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ted Lemon <mellon@fugue.com>
Cc: Warren Kumari <warren@kumari.net>, dnsop@ietf.org, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: Minor editorial change to draft-ietf-dnsop-sutld-ps
In-Reply-To: <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=ISO-8859-7
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PZtX0hyqi6nvect3bUjWm2ZbzLA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 13:37:08 -0000

>> is there a companion document with the list of benefits/advantages?
>> or is thins just one of those ietf documents from on high meant to
>> kill something?
>=20
> This is a very good question.  We weren=A2t asked to answer that
> question, so we didn=A2t.

how depressing.  one obvious curiousity is who asked the one-sided
question?  otoh, maybe i don't want to know.  but i wish you had
perceived a wider responsibility to the community.

randy


From nobody Tue Jul  4 06:42:18 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A633F1315FE for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 06:42:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-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 Cm68z2CjGSpv for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 06:42:10 -0700 (PDT)
Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::22b]) (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 23E9413189B for <ietf@ietf.org>; Tue,  4 Jul 2017 06:42:10 -0700 (PDT)
Received: by mail-qt0-x22b.google.com with SMTP id i2so165585330qta.3 for <ietf@ietf.org>; Tue, 04 Jul 2017 06:42:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=bFtdKImyVeWgMcWbEVh+l51Oz8dDVKMn9yJXspDRaik=; b=o4ffzbXpnQNnWcPwkCozdShAFN0x+GvaMOzFegL5CiMU4ehb51Zr+PtBeek+nMtIlo zdIzJ0HRg7udTHRk/I/FcefHXCR8hNaeY3QzcC1HO7zsu1D6eY1IYAATNtbM/H6Pv6mb y/X99aVN0G4fL/7/iS68kzMxNdz1J0eeoNS3b+uNWc2NNSLpK3wB1JVvRDZCS+aw4SQa O8u+v5C9C2Mgs3BPHM65nno+21AcXNuN2xHexn1lKx2esZePRt43le7IVB60/LAUDz2B e0K6BfY9qgYVLHms5HC0CeM7haptoR7CoZJolSb0Nadj33Co+fyvrt8p1MKGnNA6Ti0P 4gUQ==
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=bFtdKImyVeWgMcWbEVh+l51Oz8dDVKMn9yJXspDRaik=; b=q1T+Yb41vqC6VsuZ6lpNkz0DKX0RXZDJVmnHEoqy1vlxDH/m2whphaEwrR/hA9oOHA 3+iO+cQaG5aTqYhSAr5NdnVJ64zCr21MNx4xXVnQ/HPTUv+4geP/9b5dbBhH7q3vC1ne Jq+eL+PwPLUrwF9Zo+TBxdeBdhxDDgX+wR4/ewzvYij+qm6m6JnF08Cazafm2IIz/d4J Kzz99ZnW4z6VUrOhXKuC3w6Sk+lp7cHVi0iUAJnhgLGQ/bUkITPM/XkALOK06YtrVU8C mC38u4T2kDE+HJ+XmRdLxQONbh8fBMxuGKUGgiK1Fb7rILEblZnKpaGFoKZ5U/alllj1 C9dg==
X-Gm-Message-State: AIVw112lSDFy0MbvBKeCVkpQ0a7pjkBW3WmXWh/pEj8jlSUHIrRXplan P+NcdEHbeobUrZ9r
X-Received: by 10.237.48.225 with SMTP id 88mr17839861qtf.17.1499175729237; Tue, 04 Jul 2017 06:42:09 -0700 (PDT)
Received: from [10.0.30.114] (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id j75sm13632154qke.34.2017.07.04.06.42.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Jul 2017 06:42:08 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-C7F39176-8C3A-4238-8F80-116006D97642
Mime-Version: 1.0 (1.0)
Subject: Re: Minor editorial change to draft-ietf-dnsop-sutld-ps
From: Ted Lemon <mellon@fugue.com>
X-Mailer: iPad Mail (15A5304i)
In-Reply-To: <m2shicxr0h.wl-randy@psg.com>
Date: Tue, 4 Jul 2017 09:42:07 -0400
Cc: Warren Kumari <warren@kumari.net>, dnsop@ietf.org, IETF Rinse Repeat <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8-fhF3elQ2eElqbCy5b2pOnnms4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 13:42:12 -0000

--Apple-Mail-C7F39176-8C3A-4238-8F80-116006D97642
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Jul 4, 2017, at 9:37 AM, Randy Bush <randy@psg.com> wrote:
> how depressing.  one obvious curiousity is who asked the one-sided
> question?  otoh, maybe i don't want to know.  but i wish you had
> perceived a wider responsibility to the community.

It was discussed at length in the working group, so I would say that you cou=
ld In principle have raised this concern sooner. However, I will admit that i=
t didn=E2=80=99t occur to me to do so either. In any case, it really is a se=
parate issue from that covered by this draft, and so there=E2=80=99s no reas=
on why we can=E2=80=99t do this work if you think it=E2=80=99s worth doing. G=
iven the situation with ICANN and GTLD, it may be moot, but I wouldn=E2=80=99=
t mind writing it down.=20=

--Apple-Mail-C7F39176-8C3A-4238-8F80-116006D97642
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=3D=
utf-8"></head><body dir=3D"auto"><div></div><div>On Jul 4, 2017, at 9:37 AM,=
 Randy Bush &lt;<a href=3D"mailto:randy@psg.com">randy@psg.com</a>&gt; wrote=
:</div><blockquote type=3D"cite"><div><span>how depressing. &nbsp;one obviou=
s curiousity is who asked the one-sided</span><br><span>question? &nbsp;otoh=
, maybe i don't want to know. &nbsp;but i wish you had</span><br><span>perce=
ived a wider responsibility to the community.</span></div></blockquote><br><=
div>It was discussed <i>at length</i>&nbsp;in the working group, so I would s=
ay that you could In principle have raised this concern sooner. However, I w=
ill admit that it didn=E2=80=99t occur to me to do so either. In any case, i=
t really is a separate issue from that covered by this draft, and so there=E2=
=80=99s no reason why we can=E2=80=99t do this work if you think it=E2=80=99=
s worth doing. Given the situation with ICANN and GTLD, it may be moot, but I=
 wouldn=E2=80=99t mind writing it down.&nbsp;</div></body></html>=

--Apple-Mail-C7F39176-8C3A-4238-8F80-116006D97642--


From nobody Tue Jul  4 06:53:29 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4B02131490; Tue,  4 Jul 2017 06:53:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 MAustTeXrJ3c; Tue,  4 Jul 2017 06:53:26 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 854B013148B; Tue,  4 Jul 2017 06:53:26 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dSOGa-0000kc-Pe; Tue, 04 Jul 2017 13:53:24 +0000
Date: Tue, 04 Jul 2017 15:53:24 +0200
Message-ID: <m2podgxq97.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ted Lemon <mellon@fugue.com>
Cc: Warren Kumari <warren@kumari.net>, dnsop@ietf.org, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: Minor editorial change to draft-ietf-dnsop-sutld-ps
In-Reply-To: <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=ISO-8859-7
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Av_s0_RRy-wYz4BuIJjcT8Zq8G8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 13:53:28 -0000

>> how depressing.  one obvious curiousity is who asked the one-sided
>> question?  otoh, maybe i don't want to know.  but i wish you had
>> perceived a wider responsibility to the community.
>=20
> It was discussed at length in the working group, so I would say that
> you could In principle have raised this concern sooner.  However, I
> will admit that it didn=A2t occur to me to do so either. In any case, it
> really is a separate issue from that covered by this draft, and so
> there=A2s no reason why we can=A2t do this work if you think it=A2s worth
> doing. Given the situation with ICANN and GTLD, it may be moot, but I
> wouldn=A2t mind writing it down.

we really should not cover our eyes when we send in the assassins.

i would offer to put my keyboard where my mouth is.  but i fear that, at
the bottom, i would have the unreasonable desire for dns classes to
support these kinds of things.  i.e. i don't think we have a clean fix.
but it would be nice to document the good with the bad.

randy


From nobody Tue Jul  4 07:01:28 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FC9513160C for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 07:01:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 Uo0zHLtOrsm2 for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 07:01:25 -0700 (PDT)
Received: from mail-qt0-x231.google.com (mail-qt0-x231.google.com [IPv6:2607:f8b0:400d:c0d::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 EFF8E129459 for <ietf@ietf.org>; Tue,  4 Jul 2017 07:01:24 -0700 (PDT)
Received: by mail-qt0-x231.google.com with SMTP id b40so57529836qtb.2 for <ietf@ietf.org>; Tue, 04 Jul 2017 07:01:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=qqDIJrAAbRttRwWVLjKPD1QDEqnQh818CMDMsLr+Gfk=; b=xd21q5juZyMUWYfs3J+eyvvOo2Y0WfZG4Q4ujCC2voJPJ46ir7g8IOjh6AfTRcqTQh hpdmR44kbXBpCMHckDU6NDTEoU47u9tr2ILzbedSuY+/eMpWa1GPCofdFoph9w353x+5 7mBn1LJZbz+Il5XyLEreTCyY1zpGOkUsQpeZ6LQOCAIyCSuiDe9GDoaxdW+VHutBZQBD 60pIovL58crfICwToujpmnOnAfLm5n4npuK4yfMtNuiG7h8rDZEXSGoZ3UBrjwq1wTMa ziL3lvCDGBCt2DbG6lCdh+wqcrCuy2BthPW7/2RBq2cgHdxr8FpyR1TtL+F/QLtSkg7z oOZA==
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=qqDIJrAAbRttRwWVLjKPD1QDEqnQh818CMDMsLr+Gfk=; b=aUfNH2JGwibxsQEKZpdyADSTrEqTAdtasAq0RuwZOMKZgh9i8UqxikhvNjQlu5e9gL Ya20hFinLvjuMv8okV8KfBo2EHSr1savyyfzBn9aTkC+pAKRsaydEo1E/CwLe4O4bWBs HF9Z2XIDa7M2Tn1/P0mcpDfdhr/XuuBopp7mHZOfPnXGwSPCOqyzwulnIMFGvSekAYrL DqeVmAtW+xFVupDJkpr+zyhMsN+8/D5ekA3G92vBxgBRtG2BeNDb2A48dPP4iIjvvnaz wsTgEdCNiWb6w7zlgEcAON+dsevrHT8Ljs0UkyqX/i8sF7xNfRbJAzXZt0GxFf1Vrky8 ba2Q==
X-Gm-Message-State: AKS2vOwJMC2xGeb6SPAoehZb7L/wvcCYuUQOTgW5Neesr4urpISTK11w bIHicdJLPDQjI0E1sMqTmA==
X-Received: by 10.200.53.11 with SMTP id y11mr46176003qtb.98.1499176883861; Tue, 04 Jul 2017 07:01:23 -0700 (PDT)
Received: from [10.0.30.114] (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id a6sm14737541qtc.54.2017.07.04.07.01.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Jul 2017 07:01:23 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
Subject: Re: Minor editorial change to draft-ietf-dnsop-sutld-ps
From: Ted Lemon <mellon@fugue.com>
X-Mailer: iPad Mail (15A5304i)
In-Reply-To: <m2podgxq97.wl-randy@psg.com>
Date: Tue, 4 Jul 2017 10:01:21 -0400
Cc: Warren Kumari <warren@kumari.net>, dnsop@ietf.org, IETF Rinse Repeat <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/l_X74DDmFp_mI9TjqoZrqVhXgZo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 14:01:27 -0000

On Jul 4, 2017, at 9:53 AM, Randy Bush <randy@psg.com> wrote:
> i would offer to put my keyboard where my mouth is.  but i fear that, at
> the bottom, i would have the unreasonable desire for dns classes to
> support these kinds of things.  i.e. i don't think we have a clean fix.
> but it would be nice to document the good with the bad.

That sounds like a solution, not a motivation. That is, you care about the p=
roblem hypothetically, and have a hypothetical solution. In practice when we=
=E2=80=99ve talked about using dns classes to solve problems that have motiv=
ated rfc6761 allocations, it hasn=E2=80=99t really helped, because the infra=
structure required to use them this way is not present, and this isn=E2=80=99=
t how they were originally intended to be used.

For example, is ICANN.org with a different class not a subdomain of the .org=
 TLD? Would ICANN not object to us designating it for use by someone else?  I=
 suspect yes, and I wouldn=E2=80=99t blame them.=20=


From nobody Tue Jul  4 07:03:41 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80E5912EB21; Tue,  4 Jul 2017 07:03:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 g6yEsN2BvBSD; Tue,  4 Jul 2017 07:03:38 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 3A5A0129459; Tue,  4 Jul 2017 07:03:38 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dSOQS-0000mg-Ib; Tue, 04 Jul 2017 14:03:36 +0000
Date: Tue, 04 Jul 2017 16:03:35 +0200
Message-ID: <m2o9t0xps8.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ted Lemon <mellon@fugue.com>
Cc: Warren Kumari <warren@kumari.net>, dnsop@ietf.org, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: Minor editorial change to draft-ietf-dnsop-sutld-ps
In-Reply-To: <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=ISO-8859-7
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fAtMEwHavhj0KlaJ-S1mfehCZE8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 14:03:39 -0000

>> i would offer to put my keyboard where my mouth is.  but i fear that,
>> at the bottom, i would have the unreasonable desire for dns classes
>> to support these kinds of things.  i.e. i don't think we have a clean
>> fix.  but it would be nice to document the good with the bad.
>=20
> That sounds like a solution, not a motivation. That is, you care about
> the problem hypothetically, and have a hypothetical solution. In
> practice when we=A2ve talked about using dns classes to solve problems
> that have motivated rfc6761 allocations, it hasn=A2t really helped,
> because the infrastructure required to use them this way is not
> present, and this isn=A2t how they were originally intended to be used.
>=20
> For example, is ICANN.org with a different class not a subdomain of
> the .org TLD? Would ICANN not object to us designating it for use by
> someone else?  I suspect yes, and I wouldn=A2t blame them.

sorry.  maybe it would have helped if i had put UNREASONABLE DESIRE in
upper case.

randy


From nobody Tue Jul  4 07:05:58 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0FB41320AE for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 07:05:56 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 yVZ9m8PfiYeN for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 07:05:55 -0700 (PDT)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d: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 3DBAB1314F3 for <ietf@ietf.org>; Tue,  4 Jul 2017 07:05:55 -0700 (PDT)
Received: by mail-qk0-x22e.google.com with SMTP id p21so169255811qke.3 for <ietf@ietf.org>; Tue, 04 Jul 2017 07:05:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=84hX1flnV8x3PibXq/MhOrbKDKCqUUhditv1DONSdVg=; b=ig1A/6qHG7loInofDahBCojzsidvouEelO+80WWf//y2aNQVN+vI+fyKPdUfr/ANIs yC8suDAnuDCQ/zkhmQhRX9TTFwetBTRN7D5r8NM1JJT+KQ3o0LkLtbDPv2QUxIILDwfI uiO2ajj8H2ph56KFllvn4GzZSxOj5JHRb09R5eCVLubXxx8nXVOyWb2uVMz4XlXG0pW8 omVEMqbj5xHLTY+RWR3PqcuSHRjsCwDUepggY3BktUzDBpSnstXJSz0qhI3HOUSdRUkL SI2YyOQdzrVpPFAJXF081WIH2WR8Xt223txMr27mZOY5MqobkiTbrrUEL2B+DXF8oHx3 oCng==
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=84hX1flnV8x3PibXq/MhOrbKDKCqUUhditv1DONSdVg=; b=dkI2DDRe7y/OV74nT4rib1KrU1Vq2mvxXaAuMIDPClhpvPFx5x5QJIQVqvPke0DdD4 +EbhCbpwErJBBGpKoB2K10Cg9t/5lDpXnYDc0AoQ3GY9A9wL77fNsFDiotb8Bkp+e3Mv TCMXq14zRXd2YvOn/x5dSOyW8Mp/efT2FY2Q2WPu+vrMk/ThSjyXmEzE/9V6o2HPtQw9 OQmbanQrYdHhp+wHkyDKqjagVddFuEeya1khXq0mMK35ss6m5Y9lZ79CuS/FaTdDYGkY P/JG1FFDMCMt/gucALxQmaBnEqdogG19OsOvqm8/EZPAmlvTpLwQE1ijEuIJD1WE9uvF L1QQ==
X-Gm-Message-State: AIVw113qy/iSHrjO5KXwllzL/83jAOnaw5vCpZWnh82NysFM4+Xfxqwe uDU8aUQrR8kthLEv
X-Received: by 10.55.52.202 with SMTP id b193mr29012005qka.220.1499177154349;  Tue, 04 Jul 2017 07:05:54 -0700 (PDT)
Received: from [10.0.30.114] (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id b64sm13510753qkc.32.2017.07.04.07.05.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Jul 2017 07:05:53 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
Subject: Re: Minor editorial change to draft-ietf-dnsop-sutld-ps
From: Ted Lemon <mellon@fugue.com>
X-Mailer: iPad Mail (15A5304i)
In-Reply-To: <m2o9t0xps8.wl-randy@psg.com>
Date: Tue, 4 Jul 2017 10:05:53 -0400
Cc: Warren Kumari <warren@kumari.net>, dnsop@ietf.org, IETF Rinse Repeat <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <4165F4C5-6A4E-4993-8517-A7AD50AA67B3@fugue.com>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <m2o9t0xps8.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5O2kJ74EAaXOZJ8P6aktgvUfSlY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 14:05:57 -0000

On Jul 4, 2017, at 10:03 AM, Randy Bush <randy@psg.com> wrote:
> maybe it would have helped if i had put UNREASONABLE DESIRE in
> upper case.

My point was just that this wouldn=E2=80=99t be a description of what we mig=
ht want to accomplish with special-use names.=20=


From nobody Tue Jul  4 07:52:35 2017
Return-Path: <prvs=1358f35f7c=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 250E7131943 for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 07:52:33 -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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
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 yNk_Tf0P4YgU for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 07:52:31 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9FDE131540 for <ietf@ietf.org>; Tue,  4 Jul 2017 07:52:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1499179948; x=1499784748; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=ypzC8Luq6GkoRUUE5kT+7Zkqc y2aRX9ktQEtKjD2HC4=; b=logAevgqYS6pHYsJCRIHixaK3ZC5WuC2K3W+y2mbI yXPQgsDYR0idzicILwH0Mqi1T0UYXNa8YPR41VUWIlFCNiAMa6xPtYsr0SzrsI89 STlftc2XEtaQRJR30c5gvLVPpKvP3E7CPQeZq/PQs4v1tPtDBlx6o6nHI4aTVu5U q4=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=AlDZD+u72ZhNkcdFQRCtWmVb46Un+pcEGsp+OVovF3i+tTSW8oY+YQbxjLV5 cYTTaRuwFChMxP38mmQc6EEURv/Uu3b9jSb6p5QMHswYTY6KO4Q2ImUcc EJaWKDvLUx0/zRWJuMN3PI6cX8qEYmfSCz+qNJtHet3wwo0XOOpPGo=;
X-MDAV-Processed: mail.consulintel.es, Tue, 04 Jul 2017 16:52:28 +0200
X-Spam-Processed: mail.consulintel.es, Tue, 04 Jul 2017 16:52:28 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005465363.msg for <ietf@ietf.org>; Tue, 04 Jul 2017 16:52:27 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170704:md50005465363::z0vH8c5L8k0ZJmJY:00001BHS
X-Return-Path: prvs=1358f35f7c=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.21.0.170409
Date: Tue, 04 Jul 2017 16:52:23 +0200
Subject: Re: [99attendees] Mentors needed: TSV-SEC / SIP-APPs
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <99attendees@ietf.org>, IETF Discussion <ietf@ietf.org>
Message-ID: <6386E4AD-F2F5-4159-B317-1DBD68D5FC7B@consulintel.es>
Thread-Topic: [99attendees] Mentors needed: TSV-SEC / SIP-APPs
References: <1470252945.3502775.1499103278492.ref@mail.yahoo.com> <1470252945.3502775.1499103278492@mail.yahoo.com> <000601d2f4d0$3c6b8520$b5428f60$@gm>
In-Reply-To: <000601d2f4d0$3c6b8520$b5428f60$@gm>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lzm_0eIYH32YjlEqBbt5607Qo9E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 14:52:33 -0000

I guess it has been said already by others, but just in case =E2=80=A6

https://www.schengenvisainfo.com/

A visa for any of the countries in the Schengen area should be valid for th=
e others as well, so you have probably other 25 choices for embassies for p=
rocessing it if the CZ one is not available nearby you.

I think this info should be clearly available *always* for any IETF meeting=
 hosted in any of those countries =E2=80=A6 even in the registration email.

Could the secretariat take note of that or even include now this info in th=
e relevant web pages?

Regards,
Jordi
=20

-----Mensaje original-----
De: 99attendees <99attendees-bounces@ietf.org> en nombre de Alieu Touray <t=
ouraya@qanet.gm>
Responder a: <touraya@qanet.gm>
Fecha: martes, 4 de julio de 2017, 16:17
Para: 'Nalini J Elkins' <nalini.elkins@insidethestack.com>, <99attendees@ie=
tf.org>
Asunto: Re: [99attendees] Mentors needed: TSV-SEC / SIP-APPs

    Hello Everyone
    =20
    I wish to join the IEFT 99 but I couldn=E2=80=99t a visa as my country =
the Gambia has no Czech Republic Embassy. I also check with Senegal but the=
y refer me to Ghana but am little far from Ghana and beside I don=E2=80=99t=
 have the finance to travel to Ghana. If anyone can help please reply me UN=
ICAST.!!
    =20
    From: 99attendees [mailto:99attendees-bounces@ietf.org] On Behalf Of Na=
lini J Elkins
    Sent: Monday, July 03, 2017 10:35 AM
    To: 99attendees@ietf.org
    Subject: [99attendees] Mentors needed: TSV-SEC / SIP-APPs
   =20
   =20
    =20
    Potential Mentors,
   =20
    =20
   =20
    I need the following:
   =20
    =20
   =20
    1.   From a premier technical university in the U.S.  Interested in tsv=
wg, intarea, dots, hip, dmm, tls, ipsecme, ice, so-brandy.  First IETF.  En=
glish fine.
   =20
    =20
   =20
    2.  From a German company.  Interested in VoIP, SIP, IMS core, webpush,=
 appsawg, sipcore.  First IETF.   English OK.
   =20
    =20
   =20
    Please let me know unicast if you can help.
   =20
    =20
   =20
   =20
    Thanks,
   =20
    Nalini Elkins
   =20
    IETF Mentoring Program Lead
   =20
   =20
    CEO and Founder
    Inside Products, Inc.
    www.insidethestack.com <http://www.insidethestack.com>
    (831) 659-8360
   =20
   =20
   =20
    _______________________________________________
    99attendees mailing list
    99attendees@ietf.org
    https://www.ietf.org/mailman/listinfo/99attendees
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Tue Jul  4 07:56:57 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C53813163C for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 07:56:55 -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] 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 jTn-TlaghsH6 for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 07:56:53 -0700 (PDT)
Received: from bsa3.jck.com (static-65-175-133-137.cpe.metrocast.net [65.175.133.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 600FB131634 for <ietf@ietf.org>; Tue,  4 Jul 2017 07:56:53 -0700 (PDT)
Received: from hp5.int.jck.com ([198.252.137.153] helo=JcK-HP5.jck.com) by bsa3.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dSPFx-00053A-4l; Tue, 04 Jul 2017 10:56:49 -0400
Date: Tue, 04 Jul 2017 10:56:44 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>, ietf@ietf.org
Subject: Re: Internet Draft block on post-IETF LC IDs
Message-ID: <D42C259F293B1C4AF75DD857@JcK-HP5.jck.com>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6386604@GLKXM0002V.GREENLNK.net>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6386604@GLKXM0002V.GREENLNK.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/akQUBmxurU80vI7xOh9Y5fnSzYo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 14:56:55 -0000

--On Tuesday, July 04, 2017 9:44 AM +0000 "Dearlove, Christopher
(UK)" <chris.dearlove@baesystems.com> wrote:

> I (and co-authors) have an Internet Draft that's reached the
> IESG stage. It's due an update. In fact we have a specific
> request from our AD to update it before telechat this week.
> Done that update but can't submit due to  pre-meeting block.
> There are reasons for that, but they really don't apply to
> anything post-IETF LC stage, specifically IESG review.
> 
> Of course I've sent a copy to the AD, and he may be able to
> bypass. But I'd actually like to keep his load down - and I
> expect another update soon (possibly after telechat, hence not
> waiting to do both together).
> 
> Is it worth considering if/how this can be allowed? More work
> to create the capability I appreciate (and having to make sure
> interface makes it clear that only such IDs will work). But
> aiming to take a bit of work off one of the most critically
> loaded part of the system.

Hi.  One addition to Jari's comments, with which I agree.  

There is always a danger when documents are updated/ replaced
after IETF Last Call, which is that the changes might turn out
to be significant enough that the document a WG submitted and on
which the IETF reached consensus (or at least had a discussion)
might be different in some substantive way from what the IESG
ends up reviewing.  That has happened although all of the cases
I'm aware of have been mistakes, not an attempt to work around
the system.  I assume the relatively recent requirement for AD
signoff on changes made at AUTH48 were dictated by similar
concerns.

So, with or without the posting deadline, I would prefer that
there be explicit AD signoff on _any_ I-D revision during or
after IETF Last Call.  Such permission means that the AD has
reviewed the document and found that the changes are
insufficiently important to justify reopening the Last Call (or
a heads-up to reopen the Last Call if needed).  

Certainly that is an inconvenience for the AD and the author(s),
but it seems to me to protect the consensus process and to be
far less of an inconvenience than an appeal about the IESG
approving something the community had not reviewed (or even a
discussion about whether such an appeal is necessary).
Similarly, wrt AD workload, the workload for signing off on a
late posting (and maybe entering a note in the tracker as to why
it was approved) is almost certainly less than the effort that
would be required if someone, especially another AD, questions
the changes.

The suggestion to provide automatic permission falls, IMO, into
the "be careful what you wish for" category.

best,
    john


From nobody Tue Jul  4 10:09:36 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51366132427 for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 10:09:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 vAFt7S82cEN1 for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 10:09:33 -0700 (PDT)
Received: from miucha.iecc.com (w6.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A469E132426 for <ietf@ietf.org>; Tue,  4 Jul 2017 10:09:33 -0700 (PDT)
Received: (qmail 30187 invoked from network); 4 Jul 2017 17:09:32 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 4 Jul 2017 17:09:32 -0000
Date: 4 Jul 2017 17:09:10 -0000
Message-ID: <20170704170910.66459.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Minor philosophical update to draft-ietf-dnsop-sutld-ps
In-Reply-To: <m2podgxq97.wl-randy@psg.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/I--fYQ7ipHb9zKlj_Mrp6GTCdn0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 17:09:35 -0000

>i would offer to put my keyboard where my mouth is.  but i fear that, at
>the bottom, i would have the unreasonable desire for dns classes to
>support these kinds of things.  i.e. i don't think we have a clean fix.
>but it would be nice to document the good with the bad.

Special use TLDs are the North Korea of the IETF.  Everyone agrees
they're a problem, but there's no agreement about what to do, with
attitudes ranging from resigned acceptance to aggressive
countermeasures.

The countermeasures all have problems.  Some make implausible
assumptions like knowing in advance where all the missile launchers,
er, stunt resolvers are.  Others would take strong action that would
produce a toxic rain of collateral damage on their allies.

So welcome to the Land of Lousy Options.

R's,
John


From nobody Tue Jul  4 10:15:36 2017
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0C561324A0; Tue,  4 Jul 2017 10:15:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=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 LJAaTZXs6tmi; Tue,  4 Jul 2017 10:15:31 -0700 (PDT)
Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::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 091391319A0; Tue,  4 Jul 2017 10:15:17 -0700 (PDT)
Received: by mail-it0-x232.google.com with SMTP id m84so74564184ita.0; Tue, 04 Jul 2017 10:15:16 -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=ZdqMSF2jgye0iI7TNi+hoWSe1yF+bbp4lI7+2FUntJo=; b=BoOf/WQFWpvliUFSn2Mi8XV/Q78LlmFaQlb+VsPfvJcUiX/5IELem7kFqhOsvNe2om bVHWORU6hhV/mh+bZrMuLvicrY6+2rQ1gAMJkWIIBc8jCPgmBmptoP/fFCue/5gwsgRT EJD4Hmb75M9qO4CXs/jTuhPESDTfiVDLltvspLmCiMBw+fOzZDvUNyshi4oppii8D4hP ONNpW1Yx+mYerjEHeMTWPfJClKrAickRMmYlQnnDfX2Vvwchth4J8+jSczax/KYMW/6o V/HxugALcie13E8IvNpL8vWaOgZit/jKCtVukNQ33rY7tP0F6pZDPZR8HB1Tk6tB1R5o cQDQ==
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=ZdqMSF2jgye0iI7TNi+hoWSe1yF+bbp4lI7+2FUntJo=; b=jP+Z4nleYqmHFsXczjRU6ONK3/6cBLNjdC5htBJEwUHpi/ybWi9599BGZpiCSXnNMf AmCcC9QjS4j1lGrKa0wOQqNarzMnosgwOztJHUggnTDSCWhL9VQv/eqMn9jZAqkKnc4F vY52RLZaKb7P6J7QW9vn/40OwzlVAu3SDrkh94NKOo7TOS8knuzQOlIDXGs8sBYZbnRr EVb/LGOpt2oZzv87NzENDnZVlOZURFDX1g8HSJ5/x4ataH4T5njPrVeNFfRI2JSTEXJm 35S+MfoXJUdPFp6WIAtmVQ6tavYSEhYmGFqUwUmN+0wWadpojfFKNVAWmUMzwFTCi65+ 6ggg==
X-Gm-Message-State: AIVw111IXuIqQdU9zYu777/leXrRF4ahRLD+Rtetac9ChOazVUfs8cUK zauMVfuc20B1ZSbug6nosHQb051UWmuY
X-Received: by 10.36.3.11 with SMTP id e11mr14611724ite.79.1499188516171; Tue, 04 Jul 2017 10:15:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.17.221 with HTTP; Tue, 4 Jul 2017 10:15:00 -0700 (PDT)
In-Reply-To: <149870371689.6498.12830215563460223064@ietfa.amsl.com>
References: <149870371689.6498.12830215563460223064@ietfa.amsl.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 4 Jul 2017 13:15:00 -0400
Message-ID: <CAF4+nEE9A==y5f-vsO3vWnPSKkssdi5o1V7cAYakKOH3SZ96Jw@mail.gmail.com>
Subject: Re: Genart last call review of draft-ietf-trill-arp-optimization-08
To: Dale Worley <worley@ariadne.com>
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, draft-ietf-trill-arp-optimization.all@ietf.org,  IETF Discussion <ietf@ietf.org>, "trill@ietf.org" <trill@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fM_lFQ3PEYo5o3s-iirIYJUPk6E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 17:15:35 -0000

Hi Dale,

Thanks for the review. See below.

On Wed, Jun 28, 2017 at 10:35 PM, Dale Worley <worley@ariadne.com> wrote:
> 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 treat these comments just
> like any other last call comments.
>
> Document:  draft-ietf-trill-arp-optimization-08
> Reviewer:  Dale R. Worley
> Review Date:  2017-06-28
> IETF LC End Date:  2017-06-29
> IESG Telechat date:  unknown
>
> Summary:
>
>        This draft is basically ready for publication, but has nits
>        that should be fixed before publication.
>
>    Abstract
>
>    This document describes mechanisms to optimize the ARP (Address
>    Resolution Protocol) and ND (Neighbor Discovery) traffic in TRILL
>    campus.
>
> s/in TRILL campus/in a TRILL campus/

OK.

> Perhaps summarize what the optimizations are:
>
>    Each edge RBridge maintains a cache of IP/MAC address/Data Label
>    bindings that are learned from ARP/ND requests and responses that
>    pass through it.  This cache allows it to avoid flooding an ARP/ND
>    request by either responding to it directly or by encapsulating it
>    and unicasting it to the location where it is in use.

Wording along those lines sounds like a good addition.

>    2 ARP/ND Optimization Requirement and Solution
>
>    (including DHCP or gratuitous ARP_messages).
>
> s/_//

I think the underscore should be replaced by a space rather than the
null string.

>    and should allow an end station to
>    detect duplicate IP addresses.
>
> Unless this is a well-known phrase, it would be best if it was clear
> whether the end station is detecting that its own IP address is
> duplicated, or whether it is detecting that some other station's IP
> address is duplicated.

This is talking about the end station doing normal DAD by probing for
its own IP address.
"detect duplicate IP addresses" -> "detect duplication of its IP address".

>    TRILL already provides an option to disable data-plane learning from
>    the source MAC address of end-station frames on a per port basis (see
>    Section 5.3 of [RFC6325]).
>
> Given how this section is written, shouldn't this option be considered
> an option to *enable* data-plane learning?  And in particular, doesn't
> that imply that TRILL already includes a solution to suppress ARP
> flooding?

By default RBridges learn the source MAC addresses of the Ethernet
frames they receive from attached end stations in a way similar to
such data plane learning by bridges. A change in that default, to not
learn such MAC addresses requires optional configuration. I don't
think just learning MAC addresses is useful for the types of ARP
flooding suppression talked about in this document.

> Also, what is the meaning of "learning from the source MAC address"?
> It seems like you'd want to specify what the learning is *of*, and
> then perhaps what it is learned *from*.
>
> Or is this particular learning of MAC addresses alone, and not of
> IP/MAC bindings?  If so, then isn't this feature orthogonal to ARP/ND
> optimization?

As per RFC 6325, RBridge default to data plane learning of MAC
addresses but not IP addresses. Although TRILL has ways of arbitrating
between conflicting addressing information learned through different
paths, it may be useful to disable data plane MAC address learning
when a directory is being used or the like.

> As a design matter, I'm curious why an RBridge can't learn IP/MAC
> bindings by snooping data packets, and only by snooping ARP packets.
> I suspect there are good reasons for it, but the naive reader (me) is
> left wondering...

You can get miscellaneous data packets at line speed so MAC address
learning is frequently implemented in hardware. While there is no
reason you couldn't do that for IP addresses, if you don't want to
require hardware changes from that in most existing implementations,
you would learn from ARP/ND in software which is generally practical
as they are not normally received that frequently.

>    4.1 SEND Considerations
>
>    Secure SEND messages require knowledge of cryptographic keys. Methods
>    of communicating such keys to RBridges for use in SEND are beyond the
>    scope of this document. Thus, using the optimizations in this
>    document, RBridges do not attempt to construct SEND messages and are
>    generally transparent to them. RBridges only construct ARP, RARP, or
>    insecure ND messages, as appropriate.
>
> This doesn't flow quite correctly.  The second sentence suggests that
> there are known mechanisms for distributing keys to RBridges, but that
> this document doesn't describe them.

I disagree. Saying "X is beyond the scope of this document" means what
it says: that the topic is not further touched on in this document. I
do not think it implies that techniques to do X do or do not exist.

>                                                                  The reader then expects that the
> third sentence will say that if RBridges are provisioned with keys in
> an environment, they can generate SEND responses.  But instead, the
> real meaning of the second sentence seems to be that there are no such
> ways of distributing keys to RBridges and therefore they can't
> generate SEND responses.  That suggests that the second sentence
> should be rephrased:

I disagree. I don't think the typical reader would have such an
expectation. Even if there were standardized or deployed ways to put
such keys on edge RBridges, having said they were out of scope, I
would expect that further mechanisms built on such keys would also be
out of scope and not covered by the document.

>     There are no methods of communicating such keys to RBridges for
>     use in SEND, and thus RBridges cannot construct SEND messages and
>     must be generally transparent to them.

The existing wording goes as far as I think it should. I don't see any
reason to make it stronger and more restrictive.

> Or perhaps "SEND forbids communicating such keys to RBridges, and
> thus...".

I don't think SEND says anything about communicating such keys and it
seems like a bad idea for a TRILL document to be putting words in
SEND's mouth. If there is such a provision in the SEND specification
could you point it out to me?

>    4.3 Get Sender's IP/MAC Mapping Information for Non-zero IP
>
> What is "non-zero IP"?  Is this the case discussed in section 4.4 item
> (d)?  (If so, it also includes "a Neighbor Solicitation for DAD
> ... which has the unspecified source address".)  Perhaps the property
> being described is "Get Sender's IP/MAC Mapping Information from
> Non-Address Probe ARP/ND Queries".

This is section is talking about getting and handling the IP/MAC
mapping information for a local end station by an edge RBridge. An
ARP/ND from such a local end station might show a zero source IP
address if the end station does not have one or is probing for
duplicates.

Perhaps the title for the Section should be something like

   4.3 Extracting Local End Station IP/MAC Mapping Information

and a new first paragraph could be added something like

   Edge RBridges extract and use information about the correspondence
between local end station IP and MAC addresses from the ARP/ND
messages those end stations send as described below. An apparent zero
source IP address means that the end station is probing for duplicate
IP addresses and messages with such a zero source IP address are not
used for the extraction of IP/MAC address mapping information.

>    4.4 Determine How to Reply to ARP/ND
>
>    It is not essential that all RBridges use the same strategy for which
>    option to select for a particular ARP/ND query. It is up to the
>    implementation.
>
> It appears that the division between options (a), (b), (c), and (d)
> are fixed by the draft, so this statement is rather confusing.  Also,
> "It is up to the implementation." is a bit awkward.  Perhaps:
>
>    Within each item, it is an implementation decision which strategies
>    to use for any particular ARP/ND query falling under that item.

OK except "strategy" should be singular.

> --
>
>      Because the edge RBridge might not have an IPv6 address, the
>      source IP address for such an ND response MUST be that of the
>      target end station.
>
> Wouldn't the source IP address for such an ARP response also be that
> of the target end station, given that it is a simulated ARP response
> from the target end station?  That is, why is this MUST specific to
> IPv6?

ARP messages are not IP messages. They are link local layer 2
messages. Perhaps it could suggest that the source MAC address for an
ARP be that of the end station that would normally have sent the ARP
but all the information needed is inside the ARP message so there is
no need for an ARP implementation to look at any outer addressing of
an ARP message, such as MAC addresses on an Ethernet link, and I do
not think such implementations look at such outer addresses.
Furthermore, when this draft was previously considered by the IESG, we
were asked to specify the source IPv6 addresses for ND messages but
nothing along those lines was said about ARP messages.

Item a.5: "/ND/SEND" -> "ARP/ND/SEND"

>      b.3. Drop the message if the directory mechanism is used and you
>      know there should be no response (query based on an non-existent IP
>      address for example).
>
> It would be better to phrase this:
>
>      b.3. Drop the message if the directory server gives authoritative
>      information that the IP address is non-existent.

OK.

>    4.5 Determine How to Handle the ARP/ND Response
>
>    the target's egress RBridge R2 as discussed in subsection 3.2 item a)
>
> Really, it's subsection 3.2 item a.2.

Yes.

>    or to flood the request as per [RFC6325]
>
> Isn't this item a.5?

Yes.

>    When/if the target responds,
>
> Probably better as "If and when the target responds,".

OK.

>    5 Handling RARP (Reverse Address Resolution Protocol) Messages
>
> The title of section 5 starts "Handling" whereas the titles of
> sections 6 and 7 start "Handling of".  It's probably worth making the
> three consistent.

OK.

>    Its use is similar to
>
> Shouldn't this be "Its processing is similar to"

OK.

>    Normally, it is used to
>    look up a MAC address to find the corresponding IP address.
>
> Doesn't this duplicate the third sentence of this paragraph?

Yes, that sentence should probably be deleted.

>    7 Handling of Duplicate IP Addresses
>
>    Duplicate IP addresses can be detected when an existing active
>    IP1/MAC1 mapping gets modified.
>
> Should "IP1/MAC1" be "IP/MAC"?  Neither "IP1" nor "MAC1" is used
> elsewhere in the document.

OK.

>    Also an edge RBridge may send a query
>    to the former owner of IP called a DAD-query (Duplicate Address
>    Detection query).
>
> This is a bit ambiguous -- is it the query or the former owner that is
> called a DAD-query?  Better "may send a query called a DAD-query (...)
> to the former owner of the IP".

OK.

> However the following discussion does not specify how the DAD-query is
> addressed to the "former owner", and so doesn't specify if the former
> owner is defined by the MAC address previously associated with the IP
> address or what.  The protocol logic seems to require that the
> destination MAC is the one previously associated with the IP address
> and the queried-for IP must be the IP in question.  This should be
> spelled out, since the source addressing is specified.

OK.

>    In the case where the former owner replies, a Duplicate Address has
>    been detected. In this case the querying RBridge SHOULD log the
>    duplicate so that the network administrator can take appropriate
>    action.
>
> What action should the querying RBridge take in regard to its cache?

There is no inherent right answer that TRILL can specify when you have
duplicate IP assignments. (If there is a directory controlled by an
omniscient orchestration system, then the directory should be assumed
to be correct and conflicting IP assignments should be ignored.)

>    9 Security Considerations
>
> s/as provide in/as provided in/ (two instances)

OK.

>    12.1 Normative References
>
>    [DirMech] Dunbar, L., Eastlake 3rd, D., Perlman, R., I. Gashinsky.
>               and Li Y., TRILL: Edge Directory Assist Mechanisms",
>               draft-ietf-trill-directory-assist-mechanisms, work in
>               progress.
>
> There are unbalanced double-quotes here.

That draft has issue as RFC 8171 so the reference should be updated.

Thanks again for the review. Although I think a few of your comments
are off the mark, most of them will result in improved wording and
clarity.

Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com


From nobody Tue Jul  4 10:33:10 2017
Return-Path: <chinese.apricot@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DB671319B0; Tue,  4 Jul 2017 10:33:02 -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 azdrRrwCM5fS; Tue,  4 Jul 2017 10:33:00 -0700 (PDT)
Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::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 D50551325B2; Tue,  4 Jul 2017 10:32:59 -0700 (PDT)
Received: by mail-io0-x236.google.com with SMTP id h64so74502921iod.0; Tue, 04 Jul 2017 10:32:59 -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=u9R+FPH+CbDy52TpOQuT4IozacrJVOeMrm+FLvBugsM=; b=pYgYMR7wQk26OgfH6EKW3nOCUd3XD56ARmik5E4huIS38A/YiWrFnL5d2XSkNRjq5I 41T50wQnGE3aedzTMRCyXPaCYgO41ySLBoSskapP2La+FGFMWqu0DVsJkg5wTDnSNyEC 8Z/5CJhcO2GpxBfLWSmNvRNVzYsnmDY7MyzFIAHwvGP3Kc9a5AOc3+n/xlO619JWwvs7 hmLOORnGNGUaIJ25w4I0ajJbXQTSFcmvv1RC8cVhWkaveTSnjfzeincl4DONfnh+ntiU yF3W3jtuWS096rACyICoia+Y+rEBlrhafSoYqN5I4jCb9pQ09azEET8BUPqKXOxHtEQg Yq2w==
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=u9R+FPH+CbDy52TpOQuT4IozacrJVOeMrm+FLvBugsM=; b=Q6oJe7Pncg6mrsjJjnjfWUEzox1BEk4vHgxXuqaZzzLAF4tDVG/a4lDTGYmY4v04W2 C3DaD4kI0AR2mMWEGy0SNLIV9QOXbdVwCb7h8Aunkv2OtxLEVYAq7XYD37/WHspEuG9f DHLOPyIFTLRjNQQpLdfEZJjZ/+O9LYzZubXJuw4yetRLsiwZg7u/qhskTReWDtE7MJRq K4jzbi4rLPa6/0sWpG50ojOnYBLO97wJtzoNYeMrSTzclzYI45bCPyEa15igHUQwP61c DRmIBMJ7SzU04Qz/hgx2rogxFtLE1/gJag2weRwlaQOUwAvrdkd3Mq5aBsYyrmLOA3GG 1xQw==
X-Gm-Message-State: AKS2vOwpbeHeWj3JabBn/sHexa4zqFItuLW7iO+gbaEv11OeK/zZqYMO gZcDh7sE321Qxrru0kiTPuVdTDWAXw==
X-Received: by 10.107.184.8 with SMTP id i8mr40003825iof.153.1499189579236; Tue, 04 Jul 2017 10:32:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.18.170 with HTTP; Tue, 4 Jul 2017 10:32:58 -0700 (PDT)
In-Reply-To: <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com>
From: william manning <chinese.apricot@gmail.com>
Date: Tue, 4 Jul 2017 10:32:58 -0700
Message-ID: <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com>
Subject: Re: [DNSOP] Minor editorial change to draft-ietf-dnsop-sutld-ps
To: Ted Lemon <mellon@fugue.com>
Cc: Randy Bush <randy@psg.com>, dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c07712a525b2f05538146c4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/E5uezC9uvIJMEIbzT2ZWmSZqd7g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 17:33:02 -0000

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

I find Randys line of discussion mirroring my own thoughts.
And to answer your question above, technically, the TLD  org.  is a member
of the IN class, so in the OF class, it is credible to posit the existence
of  a org. TLD.   TLDs are per class... :)

/Wm

On Tue, Jul 4, 2017 at 7:01 AM, Ted Lemon <mellon@fugue.com> wrote:

> On Jul 4, 2017, at 9:53 AM, Randy Bush <randy@psg.com> wrote:
> > i would offer to put my keyboard where my mouth is.  but i fear that, a=
t
> > the bottom, i would have the unreasonable desire for dns classes to
> > support these kinds of things.  i.e. i don't think we have a clean fix.
> > but it would be nice to document the good with the bad.
>
> That sounds like a solution, not a motivation. That is, you care about th=
e
> problem hypothetically, and have a hypothetical solution. In practice whe=
n
> we=E2=80=99ve talked about using dns classes to solve problems that have =
motivated
> rfc6761 allocations, it hasn=E2=80=99t really helped, because the infrast=
ructure
> required to use them this way is not present, and this isn=E2=80=99t how =
they were
> originally intended to be used.
>
> For example, is ICANN.org with a different class not a subdomain of the
> .org TLD? Would ICANN not object to us designating it for use by someone
> else?  I suspect yes, and I wouldn=E2=80=99t blame them.
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>

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

<div dir=3D"ltr">I find Randys line of discussion mirroring my own thoughts=
.<div>And to answer your question above, technically, the TLD =C2=A0org. =
=C2=A0is a member of the IN class, so in the OF class, it is credible to po=
sit the existence of =C2=A0a org. TLD. =C2=A0 TLDs are per class... :)</div=
><div><br></div><div>/Wm</div></div><div class=3D"gmail_extra"><br><div cla=
ss=3D"gmail_quote">On Tue, Jul 4, 2017 at 7:01 AM, Ted Lemon <span dir=3D"l=
tr">&lt;<a href=3D"mailto:mellon@fugue.com" target=3D"_blank">mellon@fugue.=
com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"=
">On Jul 4, 2017, at 9:53 AM, Randy Bush &lt;<a href=3D"mailto:randy@psg.co=
m">randy@psg.com</a>&gt; wrote:<br>
&gt; i would offer to put my keyboard where my mouth is.=C2=A0 but i fear t=
hat, at<br>
&gt; the bottom, i would have the unreasonable desire for dns classes to<br=
>
&gt; support these kinds of things.=C2=A0 i.e. i don&#39;t think we have a =
clean fix.<br>
&gt; but it would be nice to document the good with the bad.<br>
<br>
</span>That sounds like a solution, not a motivation. That is, you care abo=
ut the problem hypothetically, and have a hypothetical solution. In practic=
e when we=E2=80=99ve talked about using dns classes to solve problems that =
have motivated rfc6761 allocations, it hasn=E2=80=99t really helped, becaus=
e the infrastructure required to use them this way is not present, and this=
 isn=E2=80=99t how they were originally intended to be used.<br>
<br>
For example, is ICANN.org with a different class not a subdomain of the .or=
g TLD? Would ICANN not object to us designating it for use by someone else?=
=C2=A0 I suspect yes, and I wouldn=E2=80=99t blame them.<br>
<div class=3D"HOEnZb"><div class=3D"h5">______________________________<wbr>=
_________________<br>
DNSOP mailing list<br>
<a href=3D"mailto:DNSOP@ietf.org">DNSOP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/dnsop</a><br>
</div></div></blockquote></div><br></div>

--94eb2c07712a525b2f05538146c4--


From nobody Tue Jul  4 10:40:05 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92D251325DE for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 10:39:58 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-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 BIFVUmEzELUc for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 10:39:57 -0700 (PDT)
Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::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 3761A1325F3 for <ietf@ietf.org>; Tue,  4 Jul 2017 10:39:56 -0700 (PDT)
Received: by mail-qk0-x234.google.com with SMTP id d78so172606328qkb.1 for <ietf@ietf.org>; Tue, 04 Jul 2017 10:39:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=pRlYSSgOyURP5PuBxxe9IKT2XRNk5KXildLC8fmDj4Q=; b=tAqTfpShFgFY1AAYAYkp8N9u1JXsMO2TR/5SXiVte9VanIF3xYfmhknluCAaJ1dB1n +3yQ09sc41xKTMIS5UDeazIe2nSh8WcE7JEImYAc0YaeX8yM4tDXMw6IPjUP0FZnlhbE a5DYdVjEEELG75CgzQPSNy18eFGV3/ulEP0jdVa8xMf+JzfCgopD4o20TiJjFd360Iwj EPpFErzRCAThCAVyQ5WrBFf4QzOCBoC2WFVejIoFzabqLK8ZmcYaBw63kUDxVzpcZAVW XHPPO8tbk2u/eWSNJc5ftMn1lQDLXs+dpnMRdaai5YGRXn5XaVNk39sfg1PC8Msv4vUI 2zAw==
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=pRlYSSgOyURP5PuBxxe9IKT2XRNk5KXildLC8fmDj4Q=; b=AG88iszG9XiZTDxzjA89nFKMMO1MK3lTcnzTMREgt2AirlIgf0H1w2n5pfWsfSvIe4 JgBPzEpKyzYGNenKZNffnVbFvICnDsE/Daf2qBQPUWkCsxlfPDTMdh1pgbTqsaZkGIUV tagC0d4MaotyvM3Jjfpb9VBt3e1PNsrooiweScK9nRw8lpxDN2CoOK7NJaWwJNMKp5Dy fZabh4D/UXbmoSzwKooOdSvA858yd1OqfpLLGNgHUy3AZRwZoI32c0yKSb8QBVvnehm5 ZqY7zFQKJnW1xXrrecTvurIQqfJVKcqPucfYNi4h+ayMqWNJ7ZY+8BVLkvGIcLVtYR4n sYiQ==
X-Gm-Message-State: AKS2vOxCy09Sa+jdbT+11/EO7XBNGbZwn1jqHRXVfj7XWRxs/yoihcFe q6VnATtz3ulzPg27
X-Received: by 10.55.71.136 with SMTP id u130mr37057018qka.66.1499189995339; Tue, 04 Jul 2017 10:39:55 -0700 (PDT)
Received: from [10.0.30.114] (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id 82sm16308392qkz.16.2017.07.04.10.39.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Jul 2017 10:39:54 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
Subject: Re: [DNSOP] Minor editorial change to draft-ietf-dnsop-sutld-ps
From: Ted Lemon <mellon@fugue.com>
X-Mailer: iPad Mail (15A5304i)
In-Reply-To: <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com>
Date: Tue, 4 Jul 2017 13:39:53 -0400
Cc: Randy Bush <randy@psg.com>, dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com>
To: william manning <chinese.apricot@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/C6n2_wk1IjQr1Io2kSMdFddLZc8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 17:39:58 -0000

On Jul 4, 2017, at 1:32 PM, william manning <chinese.apricot@gmail.com> wrot=
e:
> I find Randys line of discussion mirroring my own thoughts.
> And to answer your question above, technically, the TLD  org.  is a member=
 of the IN class, so in the OF class, it is credible to posit the existence o=
f  a org. TLD.   TLDs are per class... :)

Technically, yes. Would ICANN object?  I=E2=80=99d be astonished if they did=
 not. Is there any practical value in an alternative class hierarchy?  No. S=
o it=E2=80=99s moot.=20=


From nobody Tue Jul  4 10:50:04 2017
Return-Path: <paul@redbarn.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3FE9132616; Tue,  4 Jul 2017 10:49:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, 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 6d35VTTAy3FQ; Tue,  4 Jul 2017 10:49:53 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA879132614; Tue,  4 Jul 2017 10:49:53 -0700 (PDT)
Received: from [IPv6:2001:559:8000:c9:dc3:59e3:1fa5:69dc] (unknown [IPv6:2001:559:8000:c9:dc3:59e3:1fa5:69dc]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id B0F2261FF3; Tue,  4 Jul 2017 17:49:53 +0000 (UTC)
Message-ID: <595BD53E.60701@redbarn.org>
Date: Tue, 04 Jul 2017 10:49:50 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.15 (Windows/20170609)
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>
CC: william manning <chinese.apricot@gmail.com>, Randy Bush <randy@psg.com>, dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: [DNSOP] Minor editorial change to draft-ietf-dnsop-sutld-ps
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com>
In-Reply-To: <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/g9oK0_VBKGdDCM8uLqyKwn8_yhY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 17:49:56 -0000

Ted Lemon wrote:
> On Jul 4, 2017, at 1:32 PM, william
> manning<chinese.apricot@gmail.com>  wrote:
>> I find Randys line of discussion mirroring my own thoughts. And to
>> answer your question above, technically, the TLD  org.  is a member
>> of the IN class, so in the OF class, it is credible to posit the
>> existence of  a org. TLD.   TLDs are per class... :)
>
> Technically, yes. Would ICANN object?  I’d be astonished if they did
> not. Is there any practical value in an alternative class hierarchy?
> No. So it’s moot.

while IETF governs the protocol, ICANN only governs the IN class. i 
expect that there will be other classes some day, in order to avoid some 
aspect of ICANN. but this is not that.

-- 
P Vixie


From nobody Tue Jul  4 10:53:43 2017
Return-Path: <jim@rfc1035.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 861FC132616; Tue,  4 Jul 2017 10:53:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 093ASE5-B0VT; Tue,  4 Jul 2017 10:53:41 -0700 (PDT)
Received: from shaun.rfc1035.com (smtp.v6.rfc1035.com [IPv6:2001:4b10:100:7::25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4073B13260E; Tue,  4 Jul 2017 10:53:41 -0700 (PDT)
Received: from gromit.rfc1035.com (gromit.rfc1035.com [195.54.233.69]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 305982421519; Tue,  4 Jul 2017 17:53:39 +0000 (UTC)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: new DNS classes
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <595BD53E.60701@redbarn.org>
Date: Tue, 4 Jul 2017 18:53:38 +0100
Cc: Ted Lemon <mellon@fugue.com>, Randy Bush <randy@psg.com>, dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>, william manning <chinese.apricot@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org>
To: Paul Vixie <paul@redbarn.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8HYfIliyuX-EMdTExL1HnoV8u0U>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 17:53:42 -0000

> On 4 Jul 2017, at 18:49, Paul Vixie <paul@redbarn.org> wrote:
>=20
> while IETF governs the protocol, ICANN only governs the IN class. i =
expect that there will be other classes some day, in order to avoid some =
aspect of ICANN.

Attempts have already been made to do just that. It would be nice not to =
have to put out those fires all over again.


From nobody Tue Jul  4 10:58:40 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C92B132630 for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 10:58:38 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 SGzcQm7RMTvu for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 10:58:32 -0700 (PDT)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d: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 D467B13262D for <ietf@ietf.org>; Tue,  4 Jul 2017 10:58:31 -0700 (PDT)
Received: by mail-qk0-x22e.google.com with SMTP id p21so173528766qke.3 for <ietf@ietf.org>; Tue, 04 Jul 2017 10:58:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=4qn8CsmUp3VsJv1LXuhDtWSBYCrAZ0i8c5lergRSQ8U=; b=CBoJg9y19WxiAtNSE10Gsan7axBKZTvGcLOf3MBk7LTxERKUxZS5bWiBfLSrCmehcb bWXnCgtKXVzTIdOBU2C79Nwf3/M7mC5muEkig1NA2ezyS1b+etatndPDQPEy78pG0AcH mYZ6ZES8Zploe+AmU4n6xxbEZMWXbrWutpmpCADojNZXFyewXYmZB33BRsu0SxWhJI13 tW97fvSZTJ1/v2NjOcx86eQ9NtxWQofeNBwul3Sn5/qTJRbrpB5Wb2nFGjkf5nC3bEG6 rTYb1XukEQYN6z2/B/1O+smtnIkcpnxlh04HPIlyFUncNf7Q22Yih4qCRLJdhPamM1XI EBgQ==
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=4qn8CsmUp3VsJv1LXuhDtWSBYCrAZ0i8c5lergRSQ8U=; b=C1i73tUp0oOj4V25iDWZiHV5MPwAY/C4c5kBSvIPtT5HXFMtpXXPKJzbVKTQdVwtag gm+AWibUCiNr/9n7y40U7OmmGM0FjlvC6uIUaVUX2tgxEN5QNT3cHo3/0DiqmrLaWzKp 5YDSdMDzseF259DcZW7m9NdBd0fo+sLiAd74jLVgEf070jMf5wCyZrP9FjcZNcMZuLxy hYIXhMPediMweraq0BfhXPIhCkIP5qsIAAxFwFsTZAnNP9xoXTnI0Btydy0wLzEeTEgc NsHLTzfSz/q8JjlPbCu2E4CDbsWmjbpTguibLnypJFy8a3XkGx728bwy1ccPT1F5su+S xoNg==
X-Gm-Message-State: AIVw112X1GMEIzCbKkIdEAZQF8HGCfwIhpstZR9lnJJI4nwVneHKbqxI mC+8HAQ0eBVgFONJ
X-Received: by 10.55.145.6 with SMTP id t6mr17575675qkd.101.1499191111009; Tue, 04 Jul 2017 10:58:31 -0700 (PDT)
Received: from [10.0.30.114] (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id o23sm15406937qko.67.2017.07.04.10.58.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Jul 2017 10:58:30 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
Subject: Re: new DNS classes
From: Ted Lemon <mellon@fugue.com>
X-Mailer: iPad Mail (15A5304i)
In-Reply-To: <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com>
Date: Tue, 4 Jul 2017 13:58:29 -0400
Cc: Paul Vixie <paul@redbarn.org>, Randy Bush <randy@psg.com>, dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>, william manning <chinese.apricot@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <0E91DDA9-EFF5-4682-972D-95491A3DC22B@fugue.com>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com>
To: Jim Reid <jim@rfc1035.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/X0rqlm5Y1nwWCG80lFowlrH6iVU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 17:58:38 -0000

On Jul 4, 2017, at 1:53 PM, Jim Reid <jim@rfc1035.com> wrote:
> Attempts have already been made to do just that. It would be nice not to h=
ave to put out those fires all over again.

Realistically, at some point the damage the ICANN process has done will have=
 to get fixed, just like the damage the itu did got sort of fixed.  Like tha=
t case, the results will be messy. But we=E2=80=99ll all be gone by then, I s=
uspect.=20=


From nobody Tue Jul  4 10:59:33 2017
Return-Path: <paul@redbarn.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BF0D132638; Tue,  4 Jul 2017 10:59:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, 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 14UUa0-_O9uC; Tue,  4 Jul 2017 10:59:23 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B58E4132630; Tue,  4 Jul 2017 10:59:18 -0700 (PDT)
Received: from [IPv6:2001:559:8000:c9:dc3:59e3:1fa5:69dc] (unknown [IPv6:2001:559:8000:c9:dc3:59e3:1fa5:69dc]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 970FF61FF3; Tue,  4 Jul 2017 17:59:18 +0000 (UTC)
Message-ID: <595BD773.8050502@redbarn.org>
Date: Tue, 04 Jul 2017 10:59:15 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.15 (Windows/20170609)
MIME-Version: 1.0
To: Jim Reid <jim@rfc1035.com>
CC: Randy Bush <randy@psg.com>, dnsop <dnsop@ietf.org>,  Ted Lemon <mellon@fugue.com>, IETF Rinse Repeat <ietf@ietf.org>,  william manning <chinese.apricot@gmail.com>
Subject: Re: [DNSOP] new DNS classes
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com>
In-Reply-To: <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vYos1C94oH03eBus-iefzfNEPMg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 17:59:24 -0000

Jim Reid wrote:
>> On 4 Jul 2017, at 18:49, Paul Vixie<paul@redbarn.org>  wrote:
>>
>> while IETF governs the protocol, ICANN only governs the IN class. i
>> expect that there will be other classes some day, in order to avoid
>> some aspect of ICANN.
>
> Attempts have already been made to do just that. It would be nice not
> to have to put out those fires all over again.

nobody ever got a bonus for making things simpler. so, look for growth, 
and look for it in complexity.

-- 
P Vixie


From nobody Tue Jul  4 11:12:13 2017
Return-Path: <drc@virtualized.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3328D1326F8 for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 11:12:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=virtualized-org.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 Jb4J4c0W7tkk for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 11:12:06 -0700 (PDT)
Received: from mail-pg0-x22c.google.com (mail-pg0-x22c.google.com [IPv6:2607:f8b0:400e:c05::22c]) (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 37914132702 for <ietf@ietf.org>; Tue,  4 Jul 2017 11:12:05 -0700 (PDT)
Received: by mail-pg0-x22c.google.com with SMTP id k14so37357990pgr.0 for <ietf@ietf.org>; Tue, 04 Jul 2017 11:12:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=virtualized-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version; bh=Jexy41v/+ZGD/RsRqU2r1QcdaAAVQO273l/x2IdhIMI=; b=Myj3Fqigmn4hi3uTCqHoYSFcWobukSeh+J1KW0y5gXEzNbMwMvZt61qYNBKKDtjLCD /9Z5fxmMNp3Mxy0hdYIO46lTAezRDIpPAayi6AzI9J3j0CrU4AOkF/5poq24J9mQEA/q SkpCVsaXDa9UcbGQ2dQr4LlfR7h+4m7WakSou+x35aWVITbkr1r27lvRXG2F4R9TdpCc FY952cCgMvRHqFhLi02LXODiCUWNz8rhCXm51lCz80bbnTNuSv03Jdva0dCAZn9BV0JB yiqsYk7HMmn5cgHn1H+3S/ru/YsWZ0XGtX5lulvRaRtnjbkmsUI2Rz134vbvr9GzS8v2 oQBw==
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:message-id:in-reply-to :references:subject:mime-version; bh=Jexy41v/+ZGD/RsRqU2r1QcdaAAVQO273l/x2IdhIMI=; b=X7A/Ptf4FONLsv2HUpRMjiN3J5B6MrhS6VuTrgk/Ii3v/+G0D1KTzcOf3dvBRGlCtD 2gLbX7iHcus0xaoOwmkFHfjZkRRT8NUhu8TfduyEhJIAHYhGKYj6goDeE/ajrhUi7pWN oFnw4B3h5DySz2+R+8MHEKAaVI5gtu3bw8OCqF/xCAXgTnPTZ4ChXBtTfVfowLhkLiC7 a7ec/U4xNE+rtCWzo2HL+6xD6PeyFX3JwEuF4lFLMkQtezAkDymjhEN5mewofUV2nWKl 7GympqBwY+KVKRg4tcFNQcdmA8fPe2lG88OBgFe4qThWoAAe6ovp3d2xtgEkeltIqOK/ reMw==
X-Gm-Message-State: AIVw110D25bhu4ch/UuFr8zZLhtdnSB9JPy2sDMe6BJv2ZSGmQVugksd 6+9uTS0kZeEonjDe
X-Received: by 10.84.132.39 with SMTP id 36mr17555043ple.237.1499191924881; Tue, 04 Jul 2017 11:12:04 -0700 (PDT)
Received: from [192.168.7.50] (c-24-6-172-77.hsd1.ca.comcast.net. [24.6.172.77]) by smtp.gmail.com with ESMTPSA id l22sm42659218pfb.55.2017.07.04.11.12.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Jul 2017 11:12:04 -0700 (PDT)
Date: Tue, 4 Jul 2017 11:07:30 -0700
From: David Conrad <drc@virtualized.org>
To: Jim Reid <jim@rfc1035.com>, Paul Vixie <paul@redbarn.org>
Cc: Randy Bush <randy@psg.com>, dnsop <dnsop@ietf.org>, Ted Lemon <mellon@fugue.com>, IETF Rinse Repeat <ietf@ietf.org>, william manning <chinese.apricot@gmail.com>
Message-ID: <5156fc17-9db9-4ddb-8e6f-4210243d8550@Spark>
In-Reply-To: <595BD773.8050502@redbarn.org>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <595BD773.8050502@redbarn.org>
Subject: Re: [DNSOP] new DNS classes
X-Readdle-Message-ID: 5156fc17-9db9-4ddb-8e6f-4210243d8550@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="595bda71_643c9869_da49"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/U_3nVsOqLQY0IgBMJpPkH4AwQU8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 18:12:07 -0000

--595bda71_643c9869_da49
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Paul,

On Jul 4, 2017, 10:59 AM -0700, Paul Vixie <paul=40redbarn.org>, wrote:

> > > On 4 Jul 2017, at 18:49, Paul Vixie<paul=40redbarn.org> wrote:
> > > while IET=46 governs the protocol, ICANN only governs the IN class.=


Sorry, could you point me to anything that documents this=3F =C2=A0My imp=
ression has always been that ICANN governs (I'd prefer the term coordinat=
es myself) what =22the community=22 feels it should coordinate. I don't r=
ecall this being limited to a particular DNS class, but I might have miss=
ed it.

> nobody ever got a bonus for making things simpler.

Oh sure they have.

Thanks,
-drc


--595bda71_643c9869_da49
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<html xmlns=3D=22http://www.w3.org/1999/xhtml=22>
<head>
<title></title>
</head>
<body>
<div name=3D=22messageBodySection=22 style=3D=22font-size: 14px; font-fam=
ily: -apple-system, BlinkMacSystem=46ont, sans-serif;=22>Paul,</div>
<div name=3D=22messageSignatureSection=22><br />
<div class=3D=22match=46ont=22><span style=3D=22font-family: -apple-syste=
m, BlinkMacSystem=46ont, sans-serif; font-size: 14px;=22>On Jul 4, 2017, =
10:59 AM -0700, Paul Vixie &lt;paul=40redbarn.org&gt;, wrote:</span></div=
>
</div>
<div name=3D=22messageReplySection=22 style=3D=22font-size: 14px; font-fa=
mily: -apple-system, BlinkMacSystem=46ont, sans-serif;=22><br />
<blockquote type=3D=22cite=22 style=3D=22margin: 5px 5px; padding-left: 1=
0px; border-left: thin solid =231abc9c;=22>
<blockquote type=3D=22cite=22 style=3D=22margin: 5px 5px; padding-left: 1=
0px; border-left: thin solid =23e67e22;=22>
<blockquote type=3D=22cite=22 style=3D=22margin: 5px 5px; padding-left: 1=
0px; border-left: thin solid =233498db;=22>On 4 Jul 2017, at 18:49, Paul =
Vixie&lt;paul=40redbarn.org&gt; wrote:<br />
while IET=46 governs the protocol, ICANN only governs the IN class. &=231=
60;</blockquote>
</blockquote>
</blockquote>
<div><br /></div>
<div>Sorry, could you point me to anything that documents this=3F &=23160=
;My impression has always been that ICANN governs (I'd prefer the term co=
ordinates myself) what =22the community=22 feels it should coordinate. I =
don't recall this being limited to a particular DNS class, but I might ha=
ve missed it.</div>
<div><br /></div>
<blockquote type=3D=22cite=22 style=3D=22margin: 5px 5px; padding-left: 1=
0px; border-left: thin solid =231abc9c;=22>nobody ever got a bonus for ma=
king things simpler. &=23160;</blockquote>
<div><br /></div>
<div>Oh sure they have.</div>
<div><br /></div>
<div>
<div>
<div>
<div>
<div class=3D=22match=46ont=22>Thanks,<br />
-drc</div>
<div><br /></div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--595bda71_643c9869_da49--


From nobody Tue Jul  4 11:22:03 2017
Return-Path: <john@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 513E512896F; Tue,  4 Jul 2017 11:22:00 -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] 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 wbBqrpsxPtGW; Tue,  4 Jul 2017 11:21:58 -0700 (PDT)
Received: from bsa3.jck.com (static-65-175-133-137.cpe.metrocast.net [65.175.133.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D2BB13270A; Tue,  4 Jul 2017 11:21:55 -0700 (PDT)
Received: from hp5.int.jck.com ([198.252.137.153] helo=JcK-HP5.jck.com) by bsa3.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john@jck.com>) id 1dSSSC-000622-Vs; Tue, 04 Jul 2017 14:21:40 -0400
Date: Tue, 04 Jul 2017 14:21:35 -0400
From: John C Klensin <john@jck.com>
To: Jim Reid <jim@rfc1035.com>, Paul Vixie <paul@redbarn.org>
cc: dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>, william manning <chinese.apricot@gmail.com>
Subject: Re: new DNS classes
Message-ID: <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com>
In-Reply-To: <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/K8tYS0NfQsY-y9kT4q2_y4L2EwI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 18:22:00 -0000

--On Tuesday, July 04, 2017 6:53 PM +0100 Jim Reid
<jim@rfc1035.com> wrote:

>> On 4 Jul 2017, at 18:49, Paul Vixie <paul@redbarn.org> wrote:
>> 
>> while IETF governs the protocol, ICANN only governs the IN
>> class. i expect that there will be other classes some day, in
>> order to avoid some aspect of ICANN.
> 
> Attempts have already been made to do just that. It would be
> nice not to have to put out those fires all over again.

Jim, Paul,

First of all, if only because "QCLASS=ANY" is supposed to do
something sensible, one really cannot have different, per-Class,
roots (more of that argument and the difficulties for many of
the things people have wanted to use CLASSes for in recent years
appears in draft-sullivan-dns-class-useless).   While I don't
believe "useless", I don't see any hope for using the CLASS
mechanism to "avoid ... ICANN".

More important, given historical difficulties with adoption and
broad deployment of new features, I suggest that anyone who sees
ICANN avoidance as am important goal would find establishing an
alternate root and building support for it far easily and more
plausible than anything that could be done with CLASSes, if only
because an ICANN-free class mechanism would, AFAICT, require a
root (even for Class=IN) that was not controlled by ICANN
anyway.  

Having enough of the world get aggravated enough at ICANN (or
some other entity of one's choice) to make general adoption of
an alternate root plausible is another matter and I don't think
we are there, at least yet.  The level of confusion and global
inconsistencies that would accompany any transition to a
different root and root management structure would be bad enough
that I hope the day at which that aggravation threshold is
reached does not come even if, ICANN seems to be trying some
days.

Those who are contemplating that sort of adventure might find at
least parts of draft-klensin-dns-function-considerations amusing
reading.  In particular, Section 3.6 briefly addresses the topic
of different CLASSes as a mechanism for doing new and different
things (technical or administrative). 

best,
    john


From nobody Tue Jul  4 11:39:24 2017
Return-Path: <paul@redbarn.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCC8A132763; Tue,  4 Jul 2017 11:39:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, 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 qdCOjBB0_E_V; Tue,  4 Jul 2017 11:39:21 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B20D132762; Tue,  4 Jul 2017 11:39:21 -0700 (PDT)
Received: from [IPv6:2001:559:8000:c9:dc3:59e3:1fa5:69dc] (unknown [IPv6:2001:559:8000:c9:dc3:59e3:1fa5:69dc]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 8B68C61FF3; Tue,  4 Jul 2017 18:39:20 +0000 (UTC)
Message-ID: <595BE0D5.5000106@redbarn.org>
Date: Tue, 04 Jul 2017 11:39:17 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.15 (Windows/20170609)
MIME-Version: 1.0
To: dnsop <dnsop@ietf.org>
CC: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: new DNS classes
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com>
In-Reply-To: <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cji0yivio_iWlcLy3ZcOjZaFVgA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 18:39:23 -0000

John C Klensin wrote:
>
> --On Tuesday, July 04, 2017 6:53 PM +0100 Jim Reid
> <jim@rfc1035.com>  wrote:
>
>>> On 4 Jul 2017, at 18:49, Paul Vixie<paul@redbarn.org>  wrote:
>>>
>>> while IETF governs the protocol, ICANN only governs the IN
>>> class. i expect that there will be other classes some day, in
>>> order to avoid some aspect of ICANN.
>> Attempts have already been made to do just that. It would be
>> nice not to have to put out those fires all over again.
>
> Jim, Paul,
>
> First of all, if only because "QCLASS=ANY" is supposed to do
> something sensible, one really cannot have different, per-Class,
> roots (more of that argument and the difficulties for many of
> the things people have wanted to use CLASSes for in recent years
> appears in draft-sullivan-dns-class-useless).   While I don't
> believe "useless", I don't see any hope for using the CLASS
> mechanism to "avoid ... ICANN".

half of the foundational specification of the dns protocol assumes that 
classes are inside rrsets. the other half assumes that zones are inside 
classes. when i started on bind in 1990 or so it tried to do both. by 
1995 i had disambiguated in favour of zones-in-classes, and all others 
since then have done likewise. qtype=any was a casualty of that work.

separately, i agree that using class to avoid icann would be useless, if 
by useless you mean "there's no way to create a competitor to IN". 
however, the chaos and hesiod classes did get used at varying times, and 
i can easily imagine something like bluetooth or appletalk or lopan 
(each of which has its own naming system, so, these aren't practical 
examples but rather theoretical ones) using the dns protocol on a 
different class, and passing ICANN like ships in the night.

> Having enough of the world get aggravated enough at ICANN ...

for those keeping score, i have been aggravated at ICANN, but am not 
now. i consider the recent transition away from NTIA, and the corporate 
governance changes made to enable that transition, to have been well 
considered and well executed, and to have benefited from almost two 
decades of experience and evolution. if i were designing a replacement 
for the dns protocol today, i would do all in my power to keep the "one 
internet, one namespace" element reflected by ICANN's current role. so, 
please don't misunderstand my participation in this thread as agitation 
for further evolutionary change. i think we're in a good place now.

-- 
P Vixie


From nobody Tue Jul  4 12:37:19 2017
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8071D132830; Tue,  4 Jul 2017 12:37:17 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Melinda Shore <melinda.shore@gmail.com>
To: <secdir@ietf.org>
Cc: draft-ietf-httpbis-early-hints.all@ietf.org, ietf@ietf.org, ietf-http-wg@w3.org
Subject: Secdir last call review of draft-ietf-httpbis-early-hints-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149919703750.15996.5462759432298024921@ietfa.amsl.com>
Date: Tue, 04 Jul 2017 12:37:17 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/u3DCnx2vlsy97qh3d-NwbU1Fw0U>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 19:37:18 -0000

Reviewer: Melinda Shore
Review result: Has Issues

I have reviewed this document as part of the security directorate's 
ongoing effort to review all IETF documents being processed by the 
IESG.  These comments were written primarily for the benefit of the 
security area directors.  Document editors and WG chairs should treat 
these comments just like any other last call comments.

Summary:   Has minor issues.

This draft defines a status code for sending an informational 
response that contains header fields that are likely to be included in the 
final response.  A server can send the informational response containing 
some of the header fields to help the client start making preparations 
for processing the final response, and then run time-consuming operations 
to generate the final response.  The informational response can also be used by an
origin server to trigger HTTP/2 server push at a caching intermediary.

Passed nit checker without complaints other than publication date.  Sections
5 and 6 should be appendices.

One minor issue: in the security considerations section, "Therefore, 
a server might refrain from sending Early Hints over HTTP/1.1 unless when 
the client is known to handle informational responses correctly" is a bit squishy
(and contains a superfluous "when").  I'm not sure this merits a text change and
I'm rather certain that it doesn't merit normative 2119 language but it did stand
out as an overly soft recommendation.


From nobody Tue Jul  4 13:33:46 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C16913174D for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 13:33:45 -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 BtwmamiJhDxB for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 13:33:43 -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 B6BAE1316B0 for <ietf@ietf.org>; Tue,  4 Jul 2017 13:33:42 -0700 (PDT)
Received: by mail-pg0-x231.google.com with SMTP id j186so114047520pge.2 for <ietf@ietf.org>; Tue, 04 Jul 2017 13:33:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=HK6JwbP/bkdcrKkCPlojafS4Ue6ZlKXW4cyWaSKzrNI=; b=K5ntGKB2I5P8VNudbknZr3O42vh7vPYlvMzUO11xp4+pC/zo8qMEolw+fZy4njKRAt HgB0ujiBMmZEjbmwwdywt5tAl661psK77BHMOMTtGPxZqJB6YRG8BsL+O77fXAnRZUYm fDaPztKq+h4HAzVc7YBBdbrm3bTz81elF7xbnClECTkjwIq+nfGiM+3wHzmOOdfFecQw pJay0ywhhqSeoESQoNWSqfjOtEZjUo2Da1MECSpIjzI5mnwI2qq5i+VUUDDeqPnmJRft /FFbKuRQfy+YskAgZCqhDZXMNXpy97BuedOaGw6J9F+4IHmB+jUBGqh/UJ9co48kePAf X76w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=HK6JwbP/bkdcrKkCPlojafS4Ue6ZlKXW4cyWaSKzrNI=; b=NpI6l/nbJU2Jrc1J1/vUAqdNUz1BSVlDjLKWLvExwwq6xQqhc1c18Sp3h/oa5tLSzK dBRKDgLA2LXa/IYJe4/cHKA14oJEjrxLXFKuA9FguTafCEFdfdy0kKO3hzp9pyiiyolA yLEAMLX7+2bzpKLoXF2aPIZSQQHbvPxB5ucmROqXXzUHtjQDTfYBEa9X2CTpZJfokMNN RzSpXL9qmO7ej0dXX/o5Wcs0qA/tsujaEIsMDFnpsbuUdizxJGo6yRL6Awa0q9j8Pf21 dtltRQA3wFU8Pc/z6MqDkuAyhn2qmu+3ESF9Tm3hQqw2598iiO4qxiEfRblLIlI00uFU 51wA==
X-Gm-Message-State: AIVw1101eZTl7hu0P0RNemPm0qSogdnHWyinxUEWl+VaW1NGt5nfpkN6 ctXDPUriHdQIUooh
X-Received: by 10.99.123.17 with SMTP id w17mr17335555pgc.100.1499200422187; Tue, 04 Jul 2017 13:33:42 -0700 (PDT)
Received: from ?IPv6:2406:e007:4f03:1:28cc:dc4c:9703:6781? ([2406:e007:4f03:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id u9sm47016420pfk.131.2017.07.04.13.33.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Jul 2017 13:33:41 -0700 (PDT)
Subject: Re: Internet Draft block on post-IETF LC IDs
To: John C Klensin <john-ietf@jck.com>, "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>, ietf@ietf.org
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6386604@GLKXM0002V.GREENLNK.net> <D42C259F293B1C4AF75DD857@JcK-HP5.jck.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <5e8750e4-b649-c35b-f095-9318dc228f51@gmail.com>
Date: Wed, 5 Jul 2017 08:33:40 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <D42C259F293B1C4AF75DD857@JcK-HP5.jck.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/150HKFHyrKbYQaQVR9eCeWNU0mM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 20:33:45 -0000

On 05/07/2017 02:56, John C Klensin wrote:
...
> So, with or without the posting deadline, I would prefer that
> there be explicit AD signoff on _any_ I-D revision during or
> after IETF Last Call.  Such permission means that the AD has
> reviewed the document and found that the changes are
> insufficiently important to justify reopening the Last Call (or
> a heads-up to reopen the Last Call if needed).  

I don't think that quite works. When trying to understand and clear
DISCUSS ballots, I would much rather that changes are unambiguously
displayed for everybody to see, rather than being buried in quite
complex email threads (or in non-standard places such as GitHub).

Of course you are 100% correct that substantive changes need to pass
the rough consensus test, at least on the WG list and possibly at Last
Call level, under the AD's responsibility. But I don't think that
making it harder to post updates after Last Call is a feature.

Regards
   Brian


From nobody Tue Jul  4 13:43:53 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 423E71317E2 for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 13:43:48 -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] 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 LaDaiMBLR9E8 for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 13:43:44 -0700 (PDT)
Received: from bsa3.jck.com (static-65-175-133-137.cpe.metrocast.net [65.175.133.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1329A13177A for <ietf@ietf.org>; Tue,  4 Jul 2017 13:43:44 -0700 (PDT)
Received: from hp5.int.jck.com ([198.252.137.153] helo=JcK-HP5.jck.com) by bsa3.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dSUfW-0006tq-3c; Tue, 04 Jul 2017 16:43:34 -0400
Date: Tue, 04 Jul 2017 16:43:29 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>, ietf@ietf.org
Subject: Re: Internet Draft block on post-IETF LC IDs
Message-ID: <E47EAC7AE29C3358691D12C9@JcK-HP5.jck.com>
In-Reply-To: <5e8750e4-b649-c35b-f095-9318dc228f51@gmail.com>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6386604@GLKXM0002V.GREENLNK.net> <D42C259F293B1C4AF75DD857@JcK-HP5.jck.com> <5e8750e4-b649-c35b-f095-9318dc228f51@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kyS8SeL3AneOmkeOp5ZL8UjIwN4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 20:43:48 -0000

--On Wednesday, July 05, 2017 8:33 AM +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> On 05/07/2017 02:56, John C Klensin wrote:
> ...
>> So, with or without the posting deadline, I would prefer that
>> there be explicit AD signoff on _any_ I-D revision during or
>> after IETF Last Call.  Such permission means that the AD has
>> reviewed the document and found that the changes are
>> insufficiently important to justify reopening the Last Call
>> (or a heads-up to reopen the Last Call if needed).  
> 
> I don't think that quite works. When trying to understand and
> clear DISCUSS ballots, I would much rather that changes are
> unambiguously displayed for everybody to see, rather than
> being buried in quite complex email threads (or in
> non-standard places such as GitHub).
> 
> Of course you are 100% correct that substantive changes need
> to pass the rough consensus test, at least on the WG list and
> possibly at Last Call level, under the AD's responsibility.
> But I don't think that making it harder to post updates after
> Last Call is a feature.

Didn't intend "harder".  I just think it is important to have a
clear (and, btw, appeal-able) chain of responsibility and
accountability for changes made after IETF LC review.   We are
in complete agreement about both complex mail threads and
non-standard places, but, IMO, the IESG is supposed to be making
decisions about documents and the state of IETF consensus about
those documents, not conversations that no one can follow and
that may not be documented.

best,
    john



From nobody Tue Jul  4 16:33:34 2017
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7FDE13154E; Tue,  4 Jul 2017 16:33:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 Mjaw9-PC69rs; Tue,  4 Jul 2017 16:33:24 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (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 E90EA13013C; Tue,  4 Jul 2017 16:33:23 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id C4C3E24AE08; Tue,  4 Jul 2017 23:33:14 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 5D141160045; Tue,  4 Jul 2017 23:33:18 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 295FB160098; Tue,  4 Jul 2017 23:33:18 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 93qHIB75g40v; Tue,  4 Jul 2017 23:33:18 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 82C42160045; Tue,  4 Jul 2017 23:33:17 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id AAA7D7D84127; Wed,  5 Jul 2017 09:33:15 +1000 (AEST)
To: John C Klensin <john@jck.com>
Cc: Jim Reid <jim@rfc1035.com>, Paul Vixie <paul@redbarn.org>, dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>, william manning <chinese.apricot@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com>
Subject: Re: new DNS classes
In-reply-to: Your message of "Tue, 04 Jul 2017 14:21:35 -0400." <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com>
Date: Wed, 05 Jul 2017 09:33:15 +1000
Message-Id: <20170704233315.AAA7D7D84127@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RSNUyM4kOrpLqjGfkyh0A2B4Caw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 23:33:26 -0000

In message <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com>, John C Klensin writes:
> 
> 
> --On Tuesday, July 04, 2017 6:53 PM +0100 Jim Reid
> <jim@rfc1035.com> wrote:
> 
> >> On 4 Jul 2017, at 18:49, Paul Vixie <paul@redbarn.org> wrote:
> >> 
> >> while IETF governs the protocol, ICANN only governs the IN
> >> class. i expect that there will be other classes some day, in
> >> order to avoid some aspect of ICANN.
> > 
> > Attempts have already been made to do just that. It would be
> > nice not to have to put out those fires all over again.
> 
> Jim, Paul,
> 
> First of all, if only because "QCLASS=ANY" is supposed to do
> something sensible, one really cannot have different, per-Class,
> roots (more of that argument and the difficulties for many of
> the things people have wanted to use CLASSes for in recent years
> appears in draft-sullivan-dns-class-useless).   While I don't
> believe "useless", I don't see any hope for using the CLASS
> mechanism to "avoid ... ICANN".

draft-sullivan-dns-class-useless has lots provably invalid assumptions
in it that it is worthless in determining if new classes could be
deployed.  The only thing useful in it is the warning not to make
all new type allocations class independent as it chews through the
<type,class> tuple space too fast.  We should be updating the
instructions to IANA to allocate types as class dependent unless
it can be show that they should be class independent.  Note we can
always type X class A is identical to type X class B in the future.

As to whether a class has a parallel heirachy or not depends on
how we define the use of the class.

> More important, given historical difficulties with adoption and
> broad deployment of new features, I suggest that anyone who sees
> ICANN avoidance as am important goal would find establishing an
> alternate root and building support for it far easily and more
> plausible than anything that could be done with CLASSes, if only
> because an ICANN-free class mechanism would, AFAICT, require a
> root (even for Class=IN) that was not controlled by ICANN
> anyway.  

Getting new features support into name servers hasn't actually been
hard.  All STD 13 compliant name servers and resolvers *already*
support new classes.

What's hard to do is to get GoDaddy and ilk to update their web
interfaces.

> Having enough of the world get aggravated enough at ICANN (or
> some other entity of one's choice) to make general adoption of
> an alternate root plausible is another matter and I don't think
> we are there, at least yet.  The level of confusion and global
> inconsistencies that would accompany any transition to a
> different root and root management structure would be bad enough
> that I hope the day at which that aggravation threshold is
> reached does not come even if, ICANN seems to be trying some
> days.
> 
> Those who are contemplating that sort of adventure might find at
> least parts of draft-klensin-dns-function-considerations amusing
> reading.  In particular, Section 3.6 briefly addresses the topic
> of different CLASSes as a mechanism for doing new and different
> things (technical or administrative). 
> 
> best,
>     john
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Tue Jul  4 17:04:02 2017
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D82D13154E; Tue,  4 Jul 2017 17:03:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 Bt5DK5KuQBpR; Tue,  4 Jul 2017 17:03:52 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (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 2D85512EC71; Tue,  4 Jul 2017 17:03:52 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id 0E3F324AE08; Wed,  5 Jul 2017 00:02:28 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id B8910160045; Wed,  5 Jul 2017 00:02:31 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 8506F160098; Wed,  5 Jul 2017 00:02:31 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id D-MTbki4BCqF; Wed,  5 Jul 2017 00:02:31 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 293A1160045; Wed,  5 Jul 2017 00:02:31 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 5918D7D8457F; Wed,  5 Jul 2017 10:02:29 +1000 (AEST)
To: Ted Lemon <mellon@fugue.com>
Cc: william manning <chinese.apricot@gmail.com>, Randy Bush <randy@psg.com>, dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com>
Subject: Re: [DNSOP] Minor editorial change to draft-ietf-dnsop-sutld-ps
In-reply-to: Your message of "Tue, 04 Jul 2017 13:39:53 -0400." <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com>
Date: Wed, 05 Jul 2017 10:02:29 +1000
Message-Id: <20170705000229.5918D7D8457F@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KYcnPvGxm-Bt-m0AQL1TWWS2658>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 00:03:54 -0000

In message <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com>, Ted Lemon writes:
> On Jul 4, 2017, at 1:32 PM, william manning <chinese.apricot@gmail.com>
> wrote:
> > I find Randys line of discussion mirroring my own thoughts.
> > And to answer your question above, technically, the TLD  org.  is a
> > member of the IN class, so in the OF class, it is credible to posit the
> > existence of  a org. TLD.   TLDs are per class... :)
>
> Technically, yes. Would ICANN object?  Id be astonished if they did not.
> Is there any practical value in an alternative class hierarchy?  No. So
> its moot.

Actually there is practical value in an alternative classes if only
to make the type space effectively 32 bits and implicit with that
is a alternative class hierarchy (delegation may exist in one that
do not exist in the other and they may point to other servers).

Who owns a name is a different question to what machines serve the
<name,type,class> tuple and how do you reach those machines.  There
is absolutely no reason why the zones <name,IN> and <name,CLASS56>
need to be served by the same machines.  There is a argument for
them both being under control of the same people.

Mark

> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Tue Jul  4 18:39:58 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B71B7126E3A for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 18:39:56 -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 KNag1E3_esOW for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 18:39:55 -0700 (PDT)
Received: from miucha.iecc.com (w6.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC6DE120227 for <ietf@ietf.org>; Tue,  4 Jul 2017 18:39:54 -0700 (PDT)
Received: (qmail 83981 invoked from network); 5 Jul 2017 01:39:53 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 5 Jul 2017 01:39:53 -0000
Date: 5 Jul 2017 01:39:31 -0000
Message-ID: <20170705013931.67812.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Cc: john@jck.com
Subject: Re: new DNS classes or anything else
In-Reply-To: <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-sNF78B5uFdQb1uMt5EiTy5Trh8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 01:39:57 -0000

In article <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> you write:
>Having enough of the world get aggravated enough at ICANN (or
>some other entity of one's choice) to make general adoption of
>an alternate root plausible is another matter and I don't think
>we are there, at least yet.

Here in the IETF we are so close to ICANN that we suffer from sample
bias.  To the extent the outside world is even aware of ICANN, they
see that .com, .org, .net, and the large ccTLDs all work, registering
in them is straightforward and not too expensive, and everything else
is noise.  One advantage of ICANN's turgid bureaucratic processes is
that it makes it unlikely that they will do anything seriously
destructive because it would be too hard.

We all know how to run our own roots if that's what we want to do, but
I continue to observe approximately none of us doing it.

R's,
John


From nobody Tue Jul  4 18:47:16 2017
Return-Path: <ggm@algebras.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDE5E126B71 for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 18:47:13 -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, 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=algebras-org.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 PGpZtjwvE5WF for <ietf@ietfa.amsl.com>; Tue,  4 Jul 2017 18:47:11 -0700 (PDT)
Received: from mail-vk0-x22c.google.com (mail-vk0-x22c.google.com [IPv6:2607:f8b0:400c:c05::22c]) (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 992CE120227 for <ietf@ietf.org>; Tue,  4 Jul 2017 18:47:11 -0700 (PDT)
Received: by mail-vk0-x22c.google.com with SMTP id y70so117217690vky.3 for <ietf@ietf.org>; Tue, 04 Jul 2017 18:47:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=algebras-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Xz4QFjffdFUWoAn9o6OvSLyWSshoMQ34XA7QJdwrO3w=; b=zqe2G+6srWpXzDMxyvClrkppaLwoeKcNum5dz38A88/d2BzoXRXypHWoTSCNqcaet8 D3S+LC+qcDjVLNRAti1O4XCx3fmION6SoF5SS+glNbBVMwUd/WvOAkXTD3Zo5EZLM38s Blk16HhuUjzhkPkCneam3PgNfc7HAbRlaMNOLsXuvRRFmCRaL7mKKmud/7CrN0RgRylf n9fPlehUoQPg0RnGmnDI1U0NV7HhD5Kpn2sIzVihwX7mS8EANfUupwZCYn1Me2LVIR3E +k4pYwytaRp/fRq8aCJBVDQWmhajs+HaroA6UxXAyUxhWYVhSrWfHMklTPFrwy5huX46 A5hg==
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=Xz4QFjffdFUWoAn9o6OvSLyWSshoMQ34XA7QJdwrO3w=; b=EtiQ6wnXaXN3CmGSHbwMJrEgP7L+v1gs+42CNhSooO8ed6bYy1QjGSHrQHDt55IzvI WFyAD1BWFQzJvcfS+cY5uFu6sdVb2ftJVkTQRzHkhOt/BSn0wHvdhcGxTwC5AV5IHhNr 1GWEu7XDpSk+W5JLVCKYrEBT2V48KYSzitmKxUkcUpmzOZuNx754kg46Tgym13srO57G J6mQ+t4Q/rVh6m8L1egQQA3qhfCDRi5LGtisTPjgpwr46I7fhx2x5g50xwhWJyemBDSb EyueJiKE5hzFiMmY7kMowkjIslZbdK0/QpvmKqc0TTqgQwqiHm51KC/qKC1RY59yykdo aDQw==
X-Gm-Message-State: AIVw110LgEBvHsk9u+jav0PfnAsy6XZ3s7TpxLvFleo1Ss3HnlLbkh2O sY+q9wD0qNqDk6zP3BfPosNX11+902s8
X-Received: by 10.31.53.4 with SMTP id c4mr9636770vka.12.1499219230686; Tue, 04 Jul 2017 18:47:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.90.18 with HTTP; Tue, 4 Jul 2017 18:47:10 -0700 (PDT)
X-Originating-IP: [203.119.0.128]
In-Reply-To: <20170705013931.67812.qmail@ary.lan>
References: <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <20170705013931.67812.qmail@ary.lan>
From: George Michaelson <ggm@algebras.org>
Date: Wed, 5 Jul 2017 11:47:10 +1000
Message-ID: <CAKr6gn2zJgBxaca87y4O79hCfF+HrpVQcDWKwTfc6o6Nt+z0oQ@mail.gmail.com>
Subject: Re: new DNS classes or anything else
To: John Levine <johnl@taugh.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>, john@jck.com
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DYXzquRqQufdIjHQWpTDSyAoeqM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 01:47:14 -0000

some people have said to me that "put it in the DNS" was funny until
DNSSEC was cooked, at which point it becomes the giant
single-point-of-failure we all depend on, to provide a single unitary
TA over attested things, testable.

it's possible the unitary namespace value is now more about "I can
prove <x>" than its about the simple unique label question.

-G

On Wed, Jul 5, 2017 at 11:39 AM, John Levine <johnl@taugh.com> wrote:
> In article <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> you write:
>>Having enough of the world get aggravated enough at ICANN (or
>>some other entity of one's choice) to make general adoption of
>>an alternate root plausible is another matter and I don't think
>>we are there, at least yet.
>
> Here in the IETF we are so close to ICANN that we suffer from sample
> bias.  To the extent the outside world is even aware of ICANN, they
> see that .com, .org, .net, and the large ccTLDs all work, registering
> in them is straightforward and not too expensive, and everything else
> is noise.  One advantage of ICANN's turgid bureaucratic processes is
> that it makes it unlikely that they will do anything seriously
> destructive because it would be too hard.
>
> We all know how to run our own roots if that's what we want to do, but
> I continue to observe approximately none of us doing it.
>
> R's,
> John
>


From nobody Tue Jul  4 19:23:58 2017
Return-Path: <phluid61@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3846C12708C; Tue,  4 Jul 2017 19:23:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level: 
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, 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, 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 Hk-p8NQhb6x9; Tue,  4 Jul 2017 19:23:55 -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 D525E1243FE; Tue,  4 Jul 2017 19:23:54 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id r36so78695520ioi.1; Tue, 04 Jul 2017 19:23:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=jYQ2QOn8eQPLD8Esu0GIsS3u7rsB8jx+JvW66/nMLlw=; b=L64ZRiwlyuBrtaXh8qSY67jQJT8uVDyodeRF4wTEDpIXEJlVFXI0016NtNceQcLckH 23s4nJa1HWZmOxYlUVJTVODPHuYI/+Doy5a+UAa3NiZ6Y7LYEAlZsmsRpSQ5JLqr7R1P OnayLlqlU6AA2fa+uMbH0XCraETrVHQsMZEaGDbky/U9s+EZ26/hTeiArhqh/8QmdCJH w/6SX35cVlofBHbmu4IOPYPr7uV0eFY3bjiCLUVcdeZHSWkkA4jabrGsbc3A0lhGB2MJ EvAFFMmIoql/IB8fQ8KIEUdp3n8tNyxw1iMvmEGIxkZv2BtFhCFKTGOlvepK2hIEx4HL X9WQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=jYQ2QOn8eQPLD8Esu0GIsS3u7rsB8jx+JvW66/nMLlw=; b=q4P4RTAYnoVLVSckZEqQju4AlTQKw4fFcddUTHJQICrZPong5hBllkSo+XNmxkEAJy SB2i1nYuxYLbnHC43bRJay/4SReCS+a9w23BJNfWrnOHtf0nq/o9wVrCKndZLGxrwJdS 4FeGipRv6gEZkxD+3ohp98k9bwsizSweenrkStLvFcuJn5LNubPuulq9nt/U5NOsDZae gODRJq2oqw53VPwlS/lufiXc7XbBNGEsTCiI3YCSauvUqMPxem+awRew0G6ArIdKhEol f1Qk4OaPH4GqCC/MtmVQP7dP6/vDMOQ2Tu4o4lFI7xOvZll3xFjeQ6c1ROuI1TCUunZ8 jQwg==
X-Gm-Message-State: AIVw111Z9SWYEXmqI1EvAIM0nGpN8pIinTwIvT0uy1g1jQwhe3mu0mhe fKGNYy+sG6NW4sNa8afFXhc9yGqSoA==
X-Received: by 10.107.46.165 with SMTP id u37mr1215217iou.217.1499221434235; Tue, 04 Jul 2017 19:23:54 -0700 (PDT)
MIME-Version: 1.0
Sender: phluid61@gmail.com
Received: by 10.107.18.7 with HTTP; Tue, 4 Jul 2017 19:23:53 -0700 (PDT)
In-Reply-To: <20170705000229.5918D7D8457F@rock.dv.isc.org>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <20170705000229.5918D7D8457F@rock.dv.isc.org>
From: Matthew Kerwin <matthew@kerwin.net.au>
Date: Wed, 5 Jul 2017 12:23:53 +1000
X-Google-Sender-Auth: OfnhEjXWfv0h7gZn8xsuBP5SQGc
Message-ID: <CACweHNCAi7JcOW9CX=6FViv1wUoe5fhn7deJ2eieP2-D_FhaSA@mail.gmail.com>
Subject: Re: [DNSOP] Minor editorial change to draft-ietf-dnsop-sutld-ps
To: Mark Andrews <marka@isc.org>
Cc: dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6Q29sMoMphNnKkaWdXXlEN9oL8Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 02:23:57 -0000

On 5 July 2017 at 10:02, Mark Andrews <marka@isc.org> wrote:
>
> Who owns a name is a different question to what machines serve the
> <name,type,class> tuple and how do you reach those machines.  There
> is absolutely no reason why the zones <name,IN> and <name,CLASS56>
> need to be served by the same machines.  There is a argument for
> them both being under control of the same people.
>
> Mark
>

Hi, I'm jumping in at a random time with a possibly dumb question, but
the talk of <name,type> and <name,type,class> tuples got me wondering
about representation in general, and URLs in particular.

RFCs 3986 and 7230 say[*] that every 'host' in a HTTP URL that looks
like a DNS name is a DNS name, and that they have to be resolved to IP
addresses if you want to fetch them, but they don't talk meaningfully
about how to do that resolution. Given that we always assume class=IN
(not to mention type=A|AAAA via happy eyeballs), how would we go about
practically presenting an alternative class in things like URLs?
(Registering a new "alt-http" URL scheme doesn't strike me as a great
idea.)

Because it's all well and good setting up your own .org hierarchy
under class=FOO or whatever, but there's not much point if you can't
send people to www.not-icann.org using it. Unless you don't want to
expose your new hierarchy to the web ...?

Cheers


[*] https://tools.ietf.org/html/rfc3986#section-3.2.2 :

   """A registered name intended for lookup in the DNS uses the syntax
   defined in Section 3.5 of [RFC1034] and Section 2.1 of [RFC1123]."""

I read that as: "if it matches RFC1034 (and isn't overridden by the
specific URI scheme's rules) it's a DNS name."  It could be read the
other way, but that just adds more assumptions.

-- 
  Matthew Kerwin
  http://matthew.kerwin.net.au/


From nobody Tue Jul  4 19:36:48 2017
Return-Path: <chinese.apricot@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CCB11243FE; Tue,  4 Jul 2017 19:36:47 -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 fvaAeWbhxZBS; Tue,  4 Jul 2017 19:36:44 -0700 (PDT)
Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::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 6D5EF127601; Tue,  4 Jul 2017 19:36:44 -0700 (PDT)
Received: by mail-io0-x235.google.com with SMTP id h64so78723921iod.0; Tue, 04 Jul 2017 19:36:44 -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=1dqQGD5puf7Dlu+IcYs4nRjWmT+Ly9rk1Ar4UTxGMMM=; b=U6+NChRKrY+xJ3+CpxaEAYnQwywpLw+mY9xlToOMgXJJ6hKI7a2lYkopfmvPuVbvXx d2mylhEo1Y1mmYV6n/3kP8jcQYPyyzfRqkSaKHiOCTqSon2MssMB7qpRsooZEB1Djloo vHQTBS58+rzMt7U3wsGnj8aJ2krTiB9cU5T1gKFTzwIe9NtDmD16JlFr/UEh2QPSUFba TvsdgboHKMMHp2Kbr4mHIgBIsv38DBnPIoTrQxMOQRHMm00owH+7QRQpZ9NeHD358eZq m/jcsYtutn/IXL9o1i+yhQL5Ax5lfjzwioYYH63zl8om+B+5ebHC3bShYHzg7qbg4P25 harg==
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=1dqQGD5puf7Dlu+IcYs4nRjWmT+Ly9rk1Ar4UTxGMMM=; b=ZzbLXfHMEVSKxH7E+0v44Kj5hFMe4BS02atjQYHXyr+mohatdj/xD8wRanJUijIGJi l41VigUjIuPTSzh+f5XixKCeqly7JYSRjNldZWrKTmuoHBXCFas81iLvxNMIoV1XngNG Fqoqxq3EaWCzyZhHmCVVPkauMFU3ACdsxskCkqR4U2e+iU86cXTktX2zJwnFEupBudOK SNoJLRyC9MrVKfW8waElAcSIFzgUxBUTPzolmSI95amdxZq1Rzhz5tQMjsTfqHOfY0tM BoPL8D/pNg4n8fIkHdk5wGTia5IU4IFKVMVmRzEVXRe2dcKxKcazycwRkwUlCZJBVoyY szSw==
X-Gm-Message-State: AKS2vOwfnpQD/k8phEE9qWq7XKtjxmdIgwvF9bRdqFnVnjMMo1CUFnti 2BrS7as33VdJjWwfEmktoLHeYhrDiQ==
X-Received: by 10.107.128.230 with SMTP id k99mr40480581ioi.115.1499222203825;  Tue, 04 Jul 2017 19:36:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.18.170 with HTTP; Tue, 4 Jul 2017 19:36:43 -0700 (PDT)
In-Reply-To: <CACweHNCAi7JcOW9CX=6FViv1wUoe5fhn7deJ2eieP2-D_FhaSA@mail.gmail.com>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <20170705000229.5918D7D8457F@rock.dv.isc.org> <CACweHNCAi7JcOW9CX=6FViv1wUoe5fhn7deJ2eieP2-D_FhaSA@mail.gmail.com>
From: william manning <chinese.apricot@gmail.com>
Date: Tue, 4 Jul 2017 19:36:43 -0700
Message-ID: <CACfw2hjahuUH=xnBPpP80NteEjyBB1aWp4hk_xpoQ6Vw12TWhA@mail.gmail.com>
Subject: Re: [DNSOP] Minor editorial change to draft-ietf-dnsop-sutld-ps
To: Matthew Kerwin <matthew@kerwin.net.au>
Cc: Mark Andrews <marka@isc.org>, dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a113f8b1ee608f7055388de18"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dcqtL0AjcEGSPALmo_0gThEAAHk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 02:36:47 -0000

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

Most of the other application (besides dns) presume a single class, IN,
hence the URL presumption of "DNS name" will -always- be in the IN class.
Technically imprecise and sloppy, but pragmatically it works...  until some
loons come along and do something creative with classes.   Then all bets
are off.
RFC 1034 also uses IN in its examples and most folks forget inheritence
rules.

/Wm

On Tue, Jul 4, 2017 at 7:23 PM, Matthew Kerwin <matthew@kerwin.net.au>
wrote:

> On 5 July 2017 at 10:02, Mark Andrews <marka@isc.org> wrote:
> >
> > Who owns a name is a different question to what machines serve the
> > <name,type,class> tuple and how do you reach those machines.  There
> > is absolutely no reason why the zones <name,IN> and <name,CLASS56>
> > need to be served by the same machines.  There is a argument for
> > them both being under control of the same people.
> >
> > Mark
> >
>
> Hi, I'm jumping in at a random time with a possibly dumb question, but
> the talk of <name,type> and <name,type,class> tuples got me wondering
> about representation in general, and URLs in particular.
>
> RFCs 3986 and 7230 say[*] that every 'host' in a HTTP URL that looks
> like a DNS name is a DNS name, and that they have to be resolved to IP
> addresses if you want to fetch them, but they don't talk meaningfully
> about how to do that resolution. Given that we always assume class=IN
> (not to mention type=A|AAAA via happy eyeballs), how would we go about
> practically presenting an alternative class in things like URLs?
> (Registering a new "alt-http" URL scheme doesn't strike me as a great
> idea.)
>
> Because it's all well and good setting up your own .org hierarchy
> under class=FOO or whatever, but there's not much point if you can't
> send people to www.not-icann.org using it. Unless you don't want to
> expose your new hierarchy to the web ...?
>
> Cheers
>
>
> [*] https://tools.ietf.org/html/rfc3986#section-3.2.2 :
>
>    """A registered name intended for lookup in the DNS uses the syntax
>    defined in Section 3.5 of [RFC1034] and Section 2.1 of [RFC1123]."""
>
> I read that as: "if it matches RFC1034 (and isn't overridden by the
> specific URI scheme's rules) it's a DNS name."  It could be read the
> other way, but that just adds more assumptions.
>
> --
>   Matthew Kerwin
>   http://matthew.kerwin.net.au/
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>

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

<div dir=3D"ltr">Most of the other application (besides dns) presume a sing=
le class, IN, hence the URL presumption of &quot;DNS name&quot; will -alway=
s- be in the IN class.=C2=A0 Technically imprecise and sloppy, but pragmati=
cally it works... =C2=A0until some loons come along and do something creati=
ve with classes. =C2=A0 Then all bets are off.<div>RFC 1034 also uses IN in=
 its examples and most folks forget inheritence rules.</div><div><br></div>=
<div>/Wm</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quot=
e">On Tue, Jul 4, 2017 at 7:23 PM, Matthew Kerwin <span dir=3D"ltr">&lt;<a =
href=3D"mailto:matthew@kerwin.net.au" target=3D"_blank">matthew@kerwin.net.=
au</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D""=
>On 5 July 2017 at 10:02, Mark Andrews &lt;<a href=3D"mailto:marka@isc.org"=
>marka@isc.org</a>&gt; wrote:<br>
&gt;<br>
&gt; Who owns a name is a different question to what machines serve the<br>
&gt; &lt;name,type,class&gt; tuple and how do you reach those machines.=C2=
=A0 There<br>
&gt; is absolutely no reason why the zones &lt;name,IN&gt; and &lt;name,CLA=
SS56&gt;<br>
&gt; need to be served by the same machines.=C2=A0 There is a argument for<=
br>
&gt; them both being under control of the same people.<br>
&gt;<br>
&gt; Mark<br>
&gt;<br>
<br>
</span>Hi, I&#39;m jumping in at a random time with a possibly dumb questio=
n, but<br>
the talk of &lt;name,type&gt; and &lt;name,type,class&gt; tuples got me won=
dering<br>
about representation in general, and URLs in particular.<br>
<br>
RFCs 3986 and 7230 say[*] that every &#39;host&#39; in a HTTP URL that look=
s<br>
like a DNS name is a DNS name, and that they have to be resolved to IP<br>
addresses if you want to fetch them, but they don&#39;t talk meaningfully<b=
r>
about how to do that resolution. Given that we always assume class=3DIN<br>
(not to mention type=3DA|AAAA via happy eyeballs), how would we go about<br=
>
practically presenting an alternative class in things like URLs?<br>
(Registering a new &quot;alt-http&quot; URL scheme doesn&#39;t strike me as=
 a great<br>
idea.)<br>
<br>
Because it&#39;s all well and good setting up your own .org hierarchy<br>
under class=3DFOO or whatever, but there&#39;s not much point if you can&#3=
9;t<br>
send people to <a href=3D"http://www.not-icann.org" rel=3D"noreferrer" targ=
et=3D"_blank">www.not-icann.org</a> using it. Unless you don&#39;t want to<=
br>
expose your new hierarchy to the web ...?<br>
<br>
Cheers<br>
<br>
<br>
[*] <a href=3D"https://tools.ietf.org/html/rfc3986#section-3.2.2" rel=3D"no=
referrer" target=3D"_blank">https://tools.ietf.org/html/<wbr>rfc3986#sectio=
n-3.2.2</a> :<br>
<br>
=C2=A0 =C2=A0&quot;&quot;&quot;A registered name intended for lookup in the=
 DNS uses the syntax<br>
=C2=A0 =C2=A0defined in Section 3.5 of [RFC1034] and Section 2.1 of [RFC112=
3].&quot;&quot;&quot;<br>
<br>
I read that as: &quot;if it matches RFC1034 (and isn&#39;t overridden by th=
e<br>
specific URI scheme&#39;s rules) it&#39;s a DNS name.&quot;=C2=A0 It could =
be read the<br>
other way, but that just adds more assumptions.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
=C2=A0 Matthew Kerwin<br>
=C2=A0 <a href=3D"http://matthew.kerwin.net.au/" rel=3D"noreferrer" target=
=3D"_blank">http://matthew.kerwin.net.au/</a><br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
______________________________<wbr>_________________<br>
DNSOP mailing list<br>
<a href=3D"mailto:DNSOP@ietf.org">DNSOP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/dnsop</a><br>
</div></div></blockquote></div><br></div>

--001a113f8b1ee608f7055388de18--


From nobody Tue Jul  4 20:21:36 2017
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4493412EC38; Tue,  4 Jul 2017 20:21:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 JYQk5SfooSzc; Tue,  4 Jul 2017 20:21:22 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (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 C9E9312EC20; Tue,  4 Jul 2017 20:21:22 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id 2E20A24AE12; Wed,  5 Jul 2017 03:19:57 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id ED1F7160045; Wed,  5 Jul 2017 03:20:00 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id D81C5160050; Wed,  5 Jul 2017 03:20:00 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id k9Slb0ZcaJ2G; Wed,  5 Jul 2017 03:20:00 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 4E893160045; Wed,  5 Jul 2017 03:20:00 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 834B97D8FBDD; Wed,  5 Jul 2017 13:19:57 +1000 (AEST)
To: Matthew Kerwin <matthew@kerwin.net.au>
Cc: dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <20170705000229.5918D7D8457F@rock.dv.isc.org> <CACweHNCAi7JcOW9CX=6FViv1wUoe5fhn7deJ2eieP2-D_FhaSA@mail.gmail.com>
Subject: Re: [DNSOP] Minor editorial change to draft-ietf-dnsop-sutld-ps
In-reply-to: Your message of "Wed, 05 Jul 2017 12:23:53 +1000." <CACweHNCAi7JcOW9CX=6FViv1wUoe5fhn7deJ2eieP2-D_FhaSA@mail.gmail.com>
Date: Wed, 05 Jul 2017 13:19:57 +1000
Message-Id: <20170705031957.834B97D8FBDD@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tLP_jMskw1jymHPiSeopl600kyA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 03:21:28 -0000

In message <CACweHNCAi7JcOW9CX=6FViv1wUoe5fhn7deJ2eieP2-D_FhaSA@mail.gmail.com>, Matthew Kerwin writes:
> On 5 July 2017 at 10:02, Mark Andrews <marka@isc.org> wrote:
> >
> > Who owns a name is a different question to what machines serve the
> > <name,type,class> tuple and how do you reach those machines.  There
> > is absolutely no reason why the zones <name,IN> and <name,CLASS56>
> > need to be served by the same machines.  There is a argument for
> > them both being under control of the same people.
> >
> > Mark
> >
> 
> Hi, I'm jumping in at a random time with a possibly dumb question, but
> the talk of <name,type> and <name,type,class> tuples got me wondering
> about representation in general, and URLs in particular.
> 
> RFCs 3986 and 7230 say[*] that every 'host' in a HTTP URL that looks
> like a DNS name is a DNS name, and that they have to be resolved to IP
> addresses if you want to fetch them, but they don't talk meaningfully
> about how to do that resolution. Given that we always assume class=IN
> (not to mention type=A|AAAA via happy eyeballs), how would we go about
> practically presenting an alternative class in things like URLs?
> (Registering a new "alt-http" URL scheme doesn't strike me as a great
> idea.)

mailto: is tied to <MX,IN> then <A,IN> and <AAAA,IN> directly or indirectly.
http: is tied to <A,IN> or <AAAA,IN> and perhaps in the future <SRV,IN>

Note the linkage is not in the name but in the definition of the
scheme.

If some scheme needs <type56000,CLASS100> it will be defined in
that scheme and you will call the resolver with <name,type56000,CLASS100>
to lookup data.  That may then result in a call to lookup
<name2,AAAAA,IN> to get the addresses of the servers based on the
data returned.

Remember we call resolvers most of the time with <name,type,IN>
today.  Changing IN to something else is not hard.  You just need
to know to do that and when people write the code to support the
scheme they will do that.

When a new globally resolvable class becomes active whois will show
a set of nameservers for class IN and a set of nameservers for class
FOO.  They may be the same or they may be different.  One set may
be empty.

Remember this in not new stuff.  HS was used this way but without
central delegations.  You were still expected to use the namespace
delegated to you.  The recursive servers knew how to locate the HS
data.  getpwnam() knew how to map from user name to <domain name,
TXT, HS> and lookup the data by calling the resolver with those
values.

> Because it's all well and good setting up your own .org hierarchy
> under class=FOO or whatever, but there's not much point if you can't
> send people to www.not-icann.org using it. Unless you don't want to
> expose your new hierarchy to the web ...?
>
> Cheers
> 
> 
> [*] https://tools.ietf.org/html/rfc3986#section-3.2.2 :
> 
>    """A registered name intended for lookup in the DNS uses the syntax
>    defined in Section 3.5 of [RFC1034] and Section 2.1 of [RFC1123]."""
> 
> I read that as: "if it matches RFC1034 (and isn't overridden by the
> specific URI scheme's rules) it's a DNS name."  It could be read the
> other way, but that just adds more assumptions.
> 
> -- 
>   Matthew Kerwin
>   http://matthew.kerwin.net.au/
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Tue Jul  4 21:24:01 2017
Return-Path: <phluid61@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 073E9129AEA; Tue,  4 Jul 2017 21:24:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level: 
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, 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, 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 XpYvvfGDj1I5; Tue,  4 Jul 2017 21:23:57 -0700 (PDT)
Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (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 65372126D45; Tue,  4 Jul 2017 21:23:57 -0700 (PDT)
Received: by mail-io0-x233.google.com with SMTP id h134so79645962iof.2; Tue, 04 Jul 2017 21:23:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=/pnFIgZB/9WJCI7pJBpDNLeN/pdDOiOZQqSyolpmpuo=; b=JcjyTKOeVVXja/VCMvK94K2naGVm+4kCsHMcaQ7biNojNpvBlWb4koT2WssmYOqJ7y R+t/spXEchXWiUNGWtIlj+CFE9F83CGxCQDbsPlqAGo5uPiGI/4J2utG9CND2U7OAXr6 rQX9sHmT/ag8A6px7ej+DkY9yH+mzj4yng3yYhepHkZbKtJYrRjbPqTIDZUei+jtukjo U3rnW9d0Qncblaj0e69QhCY2aTfIpol2a/zfIP9kxm2gvAnAC7z9jQqSrO+jrXbRUuF/ q793vQVIkgIeB21y4JQUOy7NrkDJYtwpdA8BRdGKQ7dXNCOhXOZ2nzeV8/Hz7pLUOrE1 5nbw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=/pnFIgZB/9WJCI7pJBpDNLeN/pdDOiOZQqSyolpmpuo=; b=k6eJIBN2bWYXjCzmgxuIIY2TM2gGfGuJL6oNDhH5czmqCodI98nl0IPoU/fAgnK9zi fAhHsVHZFM5sAqLWWo+c5su70WCIH6lWjxar0jj6y9FzZketIKDjtPyZfWmedgvSY3w9 sF1qdZ+UD4Y9b3xzuyfvLQQs8z8IclGT+DrkNaxv8DcHBAwxRrEeCQTZLOTzTYJ+/8PX g7EWylPYo5aUboiKqZUrgh/0wMvBWKpCYOzdRkMzHr1UJlICTPQU+Xlim4AZpDie3WDk 4yYsoMNybehQlh4jX0grDV7l6QvNUgAdMpmBaUjypAs8+s/WZVyE7PPst65bVJMHOZ9I RQcQ==
X-Gm-Message-State: AKS2vOw2bKqdvtpOcH19SMAMtcFUa24eWwJUqM3FwbVMEcy3PY9WhG2S 2Wa+ZrW915xzWrZYcbKXEjnh5ROS8g==
X-Received: by 10.107.58.86 with SMTP id h83mr38243411ioa.28.1499228636762; Tue, 04 Jul 2017 21:23:56 -0700 (PDT)
MIME-Version: 1.0
Sender: phluid61@gmail.com
Received: by 10.107.18.7 with HTTP; Tue, 4 Jul 2017 21:23:56 -0700 (PDT)
In-Reply-To: <20170705031957.834B97D8FBDD@rock.dv.isc.org>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <20170705000229.5918D7D8457F@rock.dv.isc.org> <CACweHNCAi7JcOW9CX=6FViv1wUoe5fhn7deJ2eieP2-D_FhaSA@mail.gmail.com> <20170705031957.834B97D8FBDD@rock.dv.isc.org>
From: Matthew Kerwin <matthew@kerwin.net.au>
Date: Wed, 5 Jul 2017 14:23:56 +1000
X-Google-Sender-Auth: QrcC7p-hQJl6t_ikxlQyxU-0Svg
Message-ID: <CACweHNCAmZPOUmat5ruh6qkYrECM2fh15n49P+zDcJ0gfoEGvg@mail.gmail.com>
Subject: Re: [DNSOP] Minor editorial change to draft-ietf-dnsop-sutld-ps
To: Mark Andrews <marka@isc.org>
Cc: dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xBLqdpEcV6QwV6YXVbg3685pR0g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 04:24:00 -0000

On 5 July 2017 at 13:19, Mark Andrews <marka@isc.org> wrote:
>
> In message <CACweHNCAi7JcOW9CX=6FViv1wUoe5fhn7deJ2eieP2-D_FhaSA@mail.gmail.com>, Matthew Kerwin writes:
>> On 5 July 2017 at 10:02, Mark Andrews <marka@isc.org> wrote:
>> >
>> > Who owns a name is a different question to what machines serve the
>> > <name,type,class> tuple and how do you reach those machines.  There
>> > is absolutely no reason why the zones <name,IN> and <name,CLASS56>
>> > need to be served by the same machines.  There is a argument for
>> > them both being under control of the same people.
>> >
>> > Mark
>> >
>>
>> Hi, I'm jumping in at a random time with a possibly dumb question, but
>> the talk of <name,type> and <name,type,class> tuples got me wondering
>> about representation in general, and URLs in particular.
>>
>> RFCs 3986 and 7230 say[*] that every 'host' in a HTTP URL that looks
>> like a DNS name is a DNS name, and that they have to be resolved to IP
>> addresses if you want to fetch them, but they don't talk meaningfully
>> about how to do that resolution. Given that we always assume class=IN
>> (not to mention type=A|AAAA via happy eyeballs), how would we go about
>> practically presenting an alternative class in things like URLs?
>> (Registering a new "alt-http" URL scheme doesn't strike me as a great
>> idea.)
>
> mailto: is tied to <MX,IN> then <A,IN> and <AAAA,IN> directly or indirectly.
> http: is tied to <A,IN> or <AAAA,IN> and perhaps in the future <SRV,IN>
>
> Note the linkage is not in the name but in the definition of the
> scheme.
>

In the case of http it seems to be by convention, because I can't find
anything anywhere that specifies it.  That said, my actual experience
in resolving URLs only goes as deep as gethostbyname() so it's never
mattered to me.

At a similar level, I *get* how RFC 6761 sits between the 'host' name
and the IP address, but it's far enough outside my expertise that I
don't see how all the bits fit together in any detail.

[snip]

>
> Remember this in not new stuff.  HS was used this way but without
> central delegations.  You were still expected to use the namespace
> delegated to you.  The recursive servers knew how to locate the HS
> data.  getpwnam() knew how to map from user name to <domain name,
> TXT, HS> and lookup the data by calling the resolver with those
> values.
>

I'm not really a DNS person -- nor am I enough of a sysadmin (nor old
enough) to know much about HS -- which is why I asked.  I guess that
means if someone wanted to wrest control of the names used on the web
from ICANN, they'd have to set up alt-http and alt-https schemes, and
convince everyone that they're better (and to update all their
existing bookmarks, links, templates, etc.)

I guess that's one way of future-proofing us against such an event.
(That's slightly back toward the track of the original discussion,
isn't it?)

Cheers

>
>> Because it's all well and good setting up your own .org hierarchy
>> under class=FOO or whatever, but there's not much point if you can't
>> send people to www.not-icann.org using it. Unless you don't want to
>> expose your new hierarchy to the web ...?
>>

-- 
  Matthew Kerwin
  http://matthew.kerwin.net.au/


From nobody Wed Jul  5 01:47:54 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2CB8131BB5; Wed,  5 Jul 2017 01:47:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 gORbDvJTXQZ3; Wed,  5 Jul 2017 01:47:45 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 63AEC131BBA; Wed,  5 Jul 2017 01:47:45 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dSfyJ-000527-A0; Wed, 05 Jul 2017 08:47:43 +0000
Date: Wed, 05 Jul 2017 10:47:41 +0200
Message-ID: <m2mv8jw9qq.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Paul Vixie <paul@redbarn.org>
Cc: dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: new DNS classes
In-Reply-To: <595BE0D5.5000106@redbarn.org>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dKPs7GvaC93JsfbWduyuzlitly0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 08:47:47 -0000

i think avoiding icann is a red herring.  if the draft in question had
done a decent job of exploring the taxa of needs for name resolution
outside of the 'normal' topology, we would have the start of a base on
which to discuss this.

randy


From nobody Wed Jul  5 01:48:46 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBCDD131BC5 for <ietf@ietfa.amsl.com>; Wed,  5 Jul 2017 01:48:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 EqF9MmjYv1DP for <ietf@ietfa.amsl.com>; Wed,  5 Jul 2017 01:48:43 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 D4301131BC0 for <ietf@ietf.org>; Wed,  5 Jul 2017 01:48:43 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dSfzG-00052Q-CB; Wed, 05 Jul 2017 08:48:42 +0000
Date: Wed, 05 Jul 2017 10:48:40 +0200
Message-ID: <m2lgo3w9p3.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: "John Levine" <johnl@taugh.com>
Cc: ietf@ietf.org, john@jck.com
Subject: Re: new DNS classes or anything else
In-Reply-To: <20170705013931.67812.qmail@ary.lan>
References: <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <20170705013931.67812.qmail@ary.lan>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ts70M_hs5H1ninO2gEB6xuOoKQo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 08:48:45 -0000

> We all know how to run our own roots if that's what we want to do, but
> I continue to observe approximately none of us doing it.

you seem to have missed vixie's current kashpureff vector

randy


From nobody Wed Jul  5 05:02:00 2017
Return-Path: <suzworldwide@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E81B2132978; Wed,  5 Jul 2017 05:01: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, 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 05yK57Jo313R; Wed,  5 Jul 2017 05:01:39 -0700 (PDT)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d: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 9F9CC13297E; Wed,  5 Jul 2017 05:01:35 -0700 (PDT)
Received: by mail-qk0-x22e.google.com with SMTP id 16so187503748qkg.2; Wed, 05 Jul 2017 05:01:35 -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=FbSQWMF5YTqw4gIJCTtdbI/LZGLMXwJt/gliUZN2470=; b=Hnx/56I1hUT36A4RH9gQBy70afSlnTTSzeyt1vYvR9Bvlila6biGI6fsC/Gz1CH7OS 9l5+rRMTd5YaM9nFWluJY/yR0iFQZl9HiQkZtDWkcx0gaVFNQacjUipKJLGXL7Z9udAU yD51gHibPaetFUMYXovAwBd6gGB5Q4rq3m0RE4SMs/ARCGVW65b+CpzZTdPy0K8sMVN7 t4HWWfhjexx/rYq6OjRdNtOXiUjC2Q9nhwY/k/8JrEXO6MWRG103M+5cr9yBHYydm60h M2EY/Lsce9lCroItMhGcVfcEqsQxMfPsI5vPgoy19du/qJOQrIacRwnLIOnj/XcjnFJE PrvQ==
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=FbSQWMF5YTqw4gIJCTtdbI/LZGLMXwJt/gliUZN2470=; b=hZDaj5qs+WWvAckbC4m5yvmKOQjvJcPn0FsunfQH6zDdCnWuC3KucYh8oPDPAbyVam 7VlRvySbaawavUYnVPOJUESwMm5ghRaSzUkO2RUkI/jlCs3hjHTU35jiSofStKcQ80SX QDb54BpstPV9NIq1JOu6xISuMabdtDBIpUvB+eF/FWDHDY3XMJcKK7vdE3xuMkQX/KkA G30vEfzrf8hC7mUIavRCjyyozmYEhCGWAzmqiYyvFH3uRFucTvOEOLhHaTdvbMhoB93T rpIIAv5bom/In4o22zEIiIm7TxuCHmdCQUCy7/a7awQnmRPPooStLi3YQiv+usahzcok wCtg==
X-Gm-Message-State: AKS2vOzkuz4yjNKGq6OtkwOM9YKZQ/y8rYSx6vzlqjjv7IjGhlBYQ7rz 3/QshT4T9Njc4Q==
X-Received: by 10.55.139.68 with SMTP id n65mr50969999qkd.172.1499256094576; Wed, 05 Jul 2017 05:01:34 -0700 (PDT)
Received: from [10.232.156.114] ([73.114.23.114]) by smtp.gmail.com with ESMTPSA id 7sm6796572qtt.27.2017.07.05.05.01.32 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 05 Jul 2017 05:01:33 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: Minor editorial change to draft-ietf-dnsop-sutld-ps
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com>
Date: Wed, 5 Jul 2017 08:01:30 -0400
Cc: Randy Bush <randy@psg.com>, dnsop@ietf.org, IETF Rinse Repeat <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2ABF6534-D3DA-42B0-AC75-57C667CC38B2@gmail.com>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Hcr4BkzIBZWaT5Lpjhmvr8gUoc8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 12:01:54 -0000

(not sure which hat. Probably doc shepherd.)

> On Jul 4, 2017, at 9:23 AM, Ted Lemon <mellon@fugue.com> wrote:
>=20
> On Jul 4, 2017, at 3:39 AM, Randy Bush <randy@psg.com> wrote:
>> is there a companion document with the list of benefits/advantages?  =
or
>> is thins just one of those ietf documents from on high meant to kill
>> something?

>=20
> This is a very good question. We weren=E2=80=99t asked to answer that =
question, so we didn=E2=80=99t.  It is assumed throughout the document =
that various proponents of special use domains have good reasons for =
wanting them, and further that it is already accepted in principle that =
if their reason for wanting them is valid, they can have them (modulo =
technical constraints like delegation). So we didn=E2=80=99t delve into =
that. But perhaps we should have.=20

I=E2=80=99d go a step further: RFC 6761 alludes to some general reasons, =
but assumes people who=E2=80=99d go through the IETF standards process =
or an IESG approval process to get an entry in the special use names =
registry have good enough reasons that the special handling requested =
should be accepted as part of the DNS protocol. (I=E2=80=99m one of the =
people who isn=E2=80=99t comfortable with this assertion, but we=E2=80=99r=
e living with what RFC 6761 says, not what I think it should have said.)=20=


That is, RFC 6761 leaves to other processes to assess the value of the =
request and the reasons offered, but strictly speaking doesn=E2=80=99t =
require them to be documented or evaluated; required documentation for =
the registry entry consists mostly of assessing how it interacts with =
the DNS, not its primary use. (Sec. 4 starts by saying =E2=80=9CIf it is =
determined that special handling of a name is required in order to =
implement some desired new functionality,=E2=80=9D the registry entry =
policy applies, but openly avoids describing how that determination =
should be made.)

This isn=E2=80=99t really strange=E2=80=94 plenty of registries don=E2=80=99=
t require any particular discussion of the merits of an entry; ISTM that =
=E2=80=9Cstandards action=E2=80=9D presumes such evaluation as part of =
IETF consensus. But it does seem like a significant part of the observed =
problem=E2=80=94 there are only subjective and ad hoc bases for =
evaluation for a request that=E2=80=99s not otherwise justified by a =
standards track document, leading to endless repetitions of discussions =
like whether a new CLASS would be a =E2=80=9Cbetter=E2=80=9D way to =
solve a problem that isn=E2=80=99t actually documented in the request.

I think the observation that people aren=E2=80=99t really required to =
document what problem they are trying to solve with their special use =
name is in the draft, but perhaps could be more explicit.=20

Some few people already have been convinced that there should be some =
general guidance available for making the determination that a domain =
name requires special handling in the DNS. But that also seems to be a =
different document.



Suzanne=


From nobody Wed Jul  5 05:32:08 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60F521329C5 for <ietf@ietfa.amsl.com>; Wed,  5 Jul 2017 05:32:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 a01bhhQC7FAg for <ietf@ietfa.amsl.com>; Wed,  5 Jul 2017 05:32:04 -0700 (PDT)
Received: from bsa3.jck.com (static-65-175-133-137.cpe.metrocast.net [65.175.133.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6D1D131CD4 for <ietf@ietf.org>; Wed,  5 Jul 2017 05:32:04 -0700 (PDT)
Received: from hp5.int.jck.com ([198.252.137.153] helo=JcK-HP5.jck.com) by bsa3.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dSjTK-000DF3-4p; Wed, 05 Jul 2017 08:31:58 -0400
Date: Wed, 05 Jul 2017 08:31:53 -0400
From: John C Klensin <john-ietf@jck.com>
To: John Levine <johnl@taugh.com>, ietf@ietf.org
Subject: Re: new DNS classes or anything else
Message-ID: <2A04F4AA4BA9DCBC344AF7DA@JcK-HP5.jck.com>
In-Reply-To: <20170705013931.67812.qmail@ary.lan>
References: <20170705013931.67812.qmail@ary.lan>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RiWDKXAW8zerhiWRlsntCt1wiNE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 12:32:06 -0000

--On Wednesday, July 05, 2017 1:39 AM +0000 John Levine
<johnl@taugh.com> wrote:

> In article <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> you
> write:
>> Having enough of the world get aggravated enough at ICANN (or
>> some other entity of one's choice) to make general adoption of
>> an alternate root plausible is another matter and I don't
>> think we are there, at least yet.
> 
> Here in the IETF we are so close to ICANN that we suffer from
> sample bias.  To the extent the outside world is even aware of
> ICANN, they see that .com, .org, .net, and the large ccTLDs
> all work, registering in them is straightforward and not too
> expensive, and everything else is noise.  One advantage of
> ICANN's turgid bureaucratic processes is that it makes it
> unlikely that they will do anything seriously destructive
> because it would be too hard.

Were ICANN be the source of a serious problem (see below), I
think it would be far more likely to be the result of a "can't
say 'no'" failure of those processes that allows something
seriously destructive to occur than the result of an affirmative
decision to do something.  I think we've had some near-misses in
that regard, YMMD.  Beyond that, I could quibble, but, in the
interest of brevity, won't.

> We all know how to run our own roots if that's what we want to
> do, but I continue to observe approximately none of us doing
> it.

Completely consistent with my earlier comment.  I think. or at
least hope, that we all understand the advantages of a single
and unique root (those who don't might want to review RFC 2826).
An alternate root is a tipping-point problem.  For one to be
plausible, there would have to be a rather large number of
committed adopters (my guess is that it would take a collection
of significant state actors, but there are other scenarios).
Your making the switch, my making the switch, even every
participant in the IETF making the switch wouldn't amount to
anything.

If one asks the question of what it would take for a collection
of significant state actors to make the move, my guess it that
it would take a crisis event that would either be very
disruptive or get a lot of bad publicity.  "Aggravated enough at
ICANN" was shorthand for the most likely collection of sources
of (or blame for) such an event I could think of quickly.   I do
not consider that likely.  Indeed, I think it is more likely
that assorted IETF work to expand DNS capabilities beyond their
rational limits are more likely to cause serious problems.  But
that doesn't seem to be the topic of this thread.

    john





From nobody Wed Jul  5 05:49:33 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AD6A131CE1; Wed,  5 Jul 2017 05:49:25 -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] 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 b-VwcKcSxa2q; Wed,  5 Jul 2017 05:49:24 -0700 (PDT)
Received: from bsa3.jck.com (static-65-175-133-137.cpe.metrocast.net [65.175.133.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 783D11329D8; Wed,  5 Jul 2017 05:49:22 -0700 (PDT)
Received: from hp5.int.jck.com ([198.252.137.153] helo=JcK-HP5.jck.com) by bsa3.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dSjk7-000DNX-Hd; Wed, 05 Jul 2017 08:49:19 -0400
Date: Wed, 05 Jul 2017 08:49:14 -0400
From: John C Klensin <john-ietf@jck.com>
To: Suzanne Woolf <suzworldwide@gmail.com>
cc: Ted Lemon <mellon@fugue.com>, dnsop@ietf.org, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: Minor editorial change to draft-ietf-dnsop-sutld-ps
Message-ID: <1D0C8C6993058C5A6A40ABB8@JcK-HP5.jck.com>
In-Reply-To: <2ABF6534-D3DA-42B0-AC75-57C667CC38B2@gmail.com>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <2ABF6534-D3DA-42B0-AC75-57C667CC38B2@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/K-il2nO1RISOoZz8YKwZ_lAe60U>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 12:49:26 -0000

--On Wednesday, July 05, 2017 8:01 AM -0400 Suzanne Woolf
<suzworldwide@gmail.com> wrote:

> (not sure which hat. Probably doc shepherd.)
>...

>> This is a very good question. We weren't asked to answer
>> that question, so we didn't.  It is assumed throughout the
>> document that various proponents of special use domains have
>> good reasons for wanting them, and further that it is already
>> accepted in principle that if their reason for wanting them
>> is valid, they can have them (modulo technical constraints
>> like delegation). So we didn't delve into that. But perhaps
>> we should have. 
> 
> I'd go a step further: RFC 6761 alludes to some general
> reasons, but assumes people who'd go through the IETF
> standards process or an IESG approval process to get an entry
> in the special use names registry have good enough reasons
> that the special handling requested should be accepted as part
> of the DNS protocol. (I'm one of the people who isn't
> comfortable with this assertion, but we're living with what
> RFC 6761 says, not what I think it should have said.) 
> 
> That is, RFC 6761 leaves to other processes to assess the
> value of the request and the reasons offered, but strictly
> speaking doesn't require them to be documented or evaluated;
> required documentation for the registry entry consists mostly
> of assessing how it interacts with the DNS, not its primary
> use. (Sec. 4 starts by saying "If it is determined that
> special handling of a name is required in order to implement
> some desired new functionality," the registry entry policy
> applies, but openly avoids describing how that determination
> should be made.)
>...
> I think the observation that people aren't really required
> to document what problem they are trying to solve with their
> special use name is in the draft, but perhaps could be more
> explicit. 
> 
> Some few people already have been convinced that there should
> be some general guidance available for making the
> determination that a domain name requires special handling in
> the DNS. But that also seems to be a different document.

Suzanne,

Independent of "general guidance", I think the combination of
the I-D, this thread to date, and your comments above make an
extremely strong case for updating RFC 6761 to require
documentation of the problem and discussion of other
alternatives and why they are unworkable.  Whatever else the
problem statement does, I think it makes it clear that yet
another special name should be viewed as a preference only if
there are no reasonable alternatives rather than, e.g., an
option for global vanity names.  

While "general guidance for making the determination" would be,
IMO, desirable, I can imagine months (or years) of quibbling
before agreement could be reached on such criteria.  In the
interim, I'd think a requirement for documentation and
explanation sufficient to satisfy the IETF would be in order if
only as an interim measure to prevent proposals whose main
justification is "because I want one of my very own".

Anyone in DNSOP want to write a one-page RFC?

   john
 


From nobody Wed Jul  5 05:55:32 2017
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1A55131CE9 for <ietf@ietfa.amsl.com>; Wed,  5 Jul 2017 05:55:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.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 xpFXWnqo_-Ip for <ietf@ietfa.amsl.com>; Wed,  5 Jul 2017 05:55:28 -0700 (PDT)
Received: from mail-ua0-x22a.google.com (mail-ua0-x22a.google.com [IPv6:2607:f8b0:400c:c08::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 A2D42131CE0 for <ietf@ietf.org>; Wed,  5 Jul 2017 05:55:28 -0700 (PDT)
Received: by mail-ua0-x22a.google.com with SMTP id z22so142508459uah.1 for <ietf@ietf.org>; Wed, 05 Jul 2017 05:55:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=JcK5DwVaN8MW5LeAtVce4f8DXWrqzgokZ1RVG96mwGA=; b=Shh1G92JEHwQ0i/6ggXzvC/ompL1F8BJhrJJYaTP7ZdUGdX8+dsyiqMvK4U39hJLuP gdfgB8aJ6hD1ae++zJIOnx23etT3Hwyk5zbXt0XquYCyHEv3Ivj+S/U1weH6+yckuOuO 8l6AKKQmWf34rMJOgAMEifqtuYnAGleKxmqBKQlJ7S9pz1itFw3DtbKT2PFdNjGkEEIx 4AXLUZBVlk8M70/eym4pvinx2B9C8B1HY/mgWsLEbdrp2WqMgzbAe/0yRG0UGdNLA4Jz K6hORs5SxIIweeOLSNtlQi/qZ0IvryVj6i/mvQ+FeeVg0AmuxfS4avUIYFnWSrX5W2QJ oNIQ==
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=JcK5DwVaN8MW5LeAtVce4f8DXWrqzgokZ1RVG96mwGA=; b=ojbAO0DKZv1Bad64cYT/bkGO/nbmd2lenX5eQbQMu8joC1FHmje8XOwJqlZkvZ2Yb9 GwJGiAQ4KNB4odmkIvezJkygoH0YFliBJoyV8SWv4Ec7JL3poxQhKfT8F8bCYO+N5xJC jYGLW3Syff2+VA1cNHJvM6TW0OR1brrtj35YrUoARxnwzfu3pxlCW8jyyAngOou6mx+P VBOdV7gPDDxtJzhFmk3Sxn7fXGx6onH/vf4IZj0O0pYdAvd9D8cc1v1Zfqk2JjFdotqm SqOY4bBo8wGjjP4cDmYqEGP5v2rf+G9UlQPYgFmadHKvfBktSYGUnEFQtuMwxZq+e2M1 zR/w==
X-Gm-Message-State: AIVw111T+W0Vxabu9bOv/IId7MnW6omZlOHVY+f0Bo5VlYS/vfVj1uTi TDL9wTy/UjtmZ4BtfCVA6cX8kEupuzYQ
X-Received: by 10.159.58.97 with SMTP id r33mr17831231uag.110.1499259327583; Wed, 05 Jul 2017 05:55:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.39.165 with HTTP; Wed, 5 Jul 2017 05:54:47 -0700 (PDT)
In-Reply-To: <CACfw2hjahuUH=xnBPpP80NteEjyBB1aWp4hk_xpoQ6Vw12TWhA@mail.gmail.com>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <20170705000229.5918D7D8457F@rock.dv.isc.org> <CACweHNCAi7JcOW9CX=6FViv1wUoe5fhn7deJ2eieP2-D_FhaSA@mail.gmail.com> <CACfw2hjahuUH=xnBPpP80NteEjyBB1aWp4hk_xpoQ6Vw12TWhA@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
Date: Wed, 5 Jul 2017 08:54:47 -0400
Message-ID: <CAHw9_iJSWQNotk1hO8WY6SA99NgZHj290G9q2XyQwfaqOtp3gg@mail.gmail.com>
Subject: Re: [DNSOP] Minor editorial change to draft-ietf-dnsop-sutld-ps
To: william manning <chinese.apricot@gmail.com>
Cc: Matthew Kerwin <matthew@kerwin.net.au>, dnsop <dnsop@ietf.org>,  IETF Rinse Repeat <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cDs8gE1SaA3gYkVXKtbhcQIH7fQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 12:55:31 -0000

Been trying to figure out where to insert this.

https://tools.ietf.org/html/draft-sullivan-dns-class-useless-03

Abstract

   Domain Name System Resource Records are identified in part by their
   class.  The class field is not effective, and it is not used the way
   it appears to have been intended.  This memo suspends additions to
   the DNS class registry pending greater clarity on how classes might
   be used, and until such clarification requires those defining new
   RRTYPEs to define them for all classes.


Answer wrote a draft about this a few months / years ago.
W

On Tue, Jul 4, 2017 at 10:36 PM, william manning
<chinese.apricot@gmail.com> wrote:
> Most of the other application (besides dns) presume a single class, IN,
> hence the URL presumption of "DNS name" will -always- be in the IN class.
> Technically imprecise and sloppy, but pragmatically it works...  until some
> loons come along and do something creative with classes.   Then all bets are
> off.
> RFC 1034 also uses IN in its examples and most folks forget inheritence
> rules.
>
> /Wm
>
> On Tue, Jul 4, 2017 at 7:23 PM, Matthew Kerwin <matthew@kerwin.net.au>
> wrote:
>>
>> On 5 July 2017 at 10:02, Mark Andrews <marka@isc.org> wrote:
>> >
>> > Who owns a name is a different question to what machines serve the
>> > <name,type,class> tuple and how do you reach those machines.  There
>> > is absolutely no reason why the zones <name,IN> and <name,CLASS56>
>> > need to be served by the same machines.  There is a argument for
>> > them both being under control of the same people.
>> >
>> > Mark
>> >
>>
>> Hi, I'm jumping in at a random time with a possibly dumb question, but
>> the talk of <name,type> and <name,type,class> tuples got me wondering
>> about representation in general, and URLs in particular.
>>
>> RFCs 3986 and 7230 say[*] that every 'host' in a HTTP URL that looks
>> like a DNS name is a DNS name, and that they have to be resolved to IP
>> addresses if you want to fetch them, but they don't talk meaningfully
>> about how to do that resolution. Given that we always assume class=IN
>> (not to mention type=A|AAAA via happy eyeballs), how would we go about
>> practically presenting an alternative class in things like URLs?
>> (Registering a new "alt-http" URL scheme doesn't strike me as a great
>> idea.)
>>
>> Because it's all well and good setting up your own .org hierarchy
>> under class=FOO or whatever, but there's not much point if you can't
>> send people to www.not-icann.org using it. Unless you don't want to
>> expose your new hierarchy to the web ...?
>>
>> Cheers
>>
>>
>> [*] https://tools.ietf.org/html/rfc3986#section-3.2.2 :
>>
>>    """A registered name intended for lookup in the DNS uses the syntax
>>    defined in Section 3.5 of [RFC1034] and Section 2.1 of [RFC1123]."""
>>
>> I read that as: "if it matches RFC1034 (and isn't overridden by the
>> specific URI scheme's rules) it's a DNS name."  It could be read the
>> other way, but that just adds more assumptions.
>>
>> --
>>   Matthew Kerwin
>>   http://matthew.kerwin.net.au/
>>
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop
>
>



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf


From nobody Wed Jul  5 06:02:29 2017
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D599D1329EA; Wed,  5 Jul 2017 06:02:15 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
To: <tsv-art@ietf.org>
Cc: draft-ietf-trill-mtu-negotiation.all@ietf.org, ietf@ietf.org, trill@ietf.org
Subject: Tsvart telechat review of draft-ietf-trill-mtu-negotiation-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149925973580.17545.6979655005275084891@ietfa.amsl.com>
Date: Wed, 05 Jul 2017 06:02:15 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YCS090DCG9W6NanhqdbzySMiz-c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 13:02:16 -0000

Reviewer: Magnus Westerlund
Review result: Not Ready

This TSV-ART review is influenced by that I did the review of
draft-ietf-trill-over-ip.

1. So draft-ietf-trill-over-ip-10 has MTU discovery needs for
determining if the UDP encapsulation will work or not. It references  in
Section 8.4 the old RFC, i.e. RFC 6325, which is updated by
draft-ietf-trill-mtu-negotiation.

    TRILL IS-IS MTU PDUs, as specified in Section 5 of [RFC6325] and in
    [RFC7177], can be used to obtain added assurance of the MTU of a
    link.

However, this is not quite true, as if the IP path MTU is below 1470
bytes, which is not unheard of, the algorithm in the MTU negotiation
draft can't determine it. It will only report the IP path as having an
MTU to small when the 1470 bytes probe fail.

So, if the trill-over-ip authors want to use this as a mechanism, then the MTU
negotiation draft needs to be expanded to have more flexible lower
boundaries. However, that appear to affect MTU negotiation quite
significant as it needs to separate algorithm for finding MTU, from the
different usage of the algorithm with different starting points. Where
the normal will have a lower bound of 1470, and be more tightly coupled
to Sz when finding Lz. While the Trill-over-IP has a different usage.

I think the trill WG needs to decide on how to slice this. If the
MTU-negotiation only targets the explicit targets in the current draft and goes
forward now. Or if they want to meet trill-over-ip's goals which will require
restructuring.

2. Another issue, is that I think the algorithm is a bit short on
transmission scheduling recommendations:

    1) If RB1 successfully receives the MTU-ack from RB2 to the probe of
       the value of link-wide Lz within k tries (where k is a
       configurable parameter whose default is 3), link MTU size is set
       to the size of link-wide Lz and stop.

If I do this test with all three packets back to back at line rate, I could
potentially get all probes lost in the same burst loss in router queue or
switch fabric. What I think is needed here is a specification on how these
probes are transmitted. Spaced in a particular way, or at least minimal
distance, and are the additional probes only sent after the previous has been
judged to have been lost, which makes it interact with the next issue.

3. This is also unclear on what the criteria is for determining that something
is lost:

      a) If RB1 fails to receive an MTU-ack from RB2 after k tries, RB1
          sets the "failed minimum MTU test" flag for RB2 in RB1's Hello
          and stop.

I fail to see any specification for the criteria when an MTU-ack should be
considered to have failed to reach the probing entity. So this appear to
require a timeout, and thus a timeout interval. Is the RTT known so that one
can define something as lost after N*RTT? Are there possible delays in sending
the MTU-ack that are considered okay that can affect this?

4. Section 3, the algorithm in Step 1 is unable to reach the first termination
condition (3) "If lowerBound >= upperBound" in some cases.

  Step 1: RB1 tries to send an MTU-probe padded to the size x.

   1) If RB1 fails to receive an MTU-ack from RB2 after k tries:

         upperBound is set to x and x is set to [(lowerBound +
         upperBound)/2], rounded up to the nearest integer.

   2) If RB1 receives an MTU-ack to a probe of size x from RB2:

         link MTU size is set to x, lowerBound is set to x and x is set
         to [(lowerBound + upperBound)/2], rounded up to the nearest
         integer.

   3) If lowerBound >= upperBound or Step 1 has been repeated n times
      (where n is a configurable parameter whose default value is 5),
      stop.

   4) Repeat Step 1.

I run this on the input data: Lower bound = 1470, Upper bound = 9216 and with
an MTU of 7935 and gets the following sequence:

Lower   Upper   X
1470    9216    5343
5343    9216    7280
7280    9216    8248
7280    8248    7764
7764    8248    8006
7764    8006    7885
7885    8006    7946
7885    7946    7916
7916    7946    7931
7931    7946    7939
7931    7939    7935
7935    7939    7937
7935    7937    7936
7935    7936    7936
7935    7936    7936

Thus, the termination condition needs to change. The second I notice is that
having a limitation on number of steps as 5, results in quite a large gap
between upper and lower bound in which the MTU exists in.

5. I frankly gets confused by the application of the binary search. First it
will in many case not be run to termination where the actual MTU is determined.
Then the result of the upper and lower bound are just used to confirm the Sz
value. There are no discussion about using the MTU search to determine a new
possible value for Sz. The text is not even explicit that lower bound is the
highest known to work Transmission unit size at the time of testing. I think
section 3, should conclude in determine some TU value, and if that is Sz or
something other appears quite relevant for what to do in the later sections.



From nobody Wed Jul  5 08:08:48 2017
Return-Path: <aaron.falk@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 514F9131D4F; Wed,  5 Jul 2017 08:08:39 -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 SuvtAWgZh_1O; Wed,  5 Jul 2017 08:08:36 -0700 (PDT)
Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::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 9E86313192B; Wed,  5 Jul 2017 08:08:36 -0700 (PDT)
Received: by mail-qt0-x235.google.com with SMTP id i2so188718032qta.3; Wed, 05 Jul 2017 08:08:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:subject:date:message-id:in-reply-to:references:mime-version;  bh=/LAezUBA8AM26Dnp0omzRW4yvB/cw6zUY65ZmVyyW3w=; b=vZWPozJQRadUUNhrCEQ1ILYLLqzu6/ukfIr3MCTuLyIiPjk5OueP1+RI1fhtygb2UZ jVdL402DY/acgTf8+dI09CixMWn0wOAUP20V/Jaem/i9kfHxbzmAdE6Xsvb2+kY9WK1R ut7TM9nIkCkAxb2BRXI1RtQJHcI9EXJodoAeksEm9IWJ3swmZg08OPqc2g73QmVMGIpo N6FD/zBECsDvJ8fpQ5SpWVm9C7+7yRJ8v69onjYKcIWdQkxqAPn2i+rO+CzwauJRdfz+ 5IjHKciC8XFuH6zy/jNsy31q7S2AbiXV11arVDiWvWyQeLrsTVMkUaglOUZgi3L6R6ZS bOZQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:in-reply-to :references:mime-version; bh=/LAezUBA8AM26Dnp0omzRW4yvB/cw6zUY65ZmVyyW3w=; b=RkPPKCTbw7x0JUIKTYoBpFPtxuir1zYo0PCVLpGioqMZiX8vu4CFTv7n9ymxeUaEfU UOd0/1gmuTPqGWDdyPw9eiK1kQVKNaeb0WZqo6pOGQl5fTFqaOkXgM8UZvKNTpkERIyi PWFFicOmLQC286xPXlmFhtZCI/TbdJbeIMQqiE540uneoIeEaMlt44+vi8LC5cF1jIoX un/I199yHb/I3d5cMo80bDTKpm8Mtf2tdTRW6gS/lJyaqO8BpRgXda4CHlluWbVVMAfc ZFO+5dd1a0TwvwIBpHkj5dItZLEBho9rIpJW0gFcnnY+snnpibp4hxjFbIlhBIWLyTgU +Yuw==
X-Gm-Message-State: AIVw1103yrolExiGYJakQRPD0JDP1jDeyYCa27GffPSmrcWLBfzYyIBJ MRPyHqwsRra9uj1y6EI=
X-Received: by 10.237.48.174 with SMTP id 43mr23056257qtf.201.1499267315569; Wed, 05 Jul 2017 08:08:35 -0700 (PDT)
Received: from [172.19.37.166] ([2601:184:4980:a321:c555:fa0a:3752:abaf]) by smtp.gmail.com with ESMTPSA id y58sm18354724qtc.36.2017.07.05.08.08.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Jul 2017 08:08:35 -0700 (PDT)
From: "Aaron Falk" <aaron.falk@gmail.com>
To: ietf@ietf.org, "99attendees@ietf.org" <99attendees@ietf.org>
Subject: Re: PechaKucha presenters for Prague?
Date: Wed, 05 Jul 2017 11:08:34 -0400
Message-ID: <7B789905-2EB2-4650-B085-BE39F3E048ED@gmail.com>
In-Reply-To: <F11AED30-9781-409D-89BD-BB676BB2E371@gmail.com>
References: <D53C2422-8C47-4E42-B5AF-9A263FB89730@gmail.com> <F11AED30-9781-409D-89BD-BB676BB2E371@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_02915F07-3C6E-4A49-9A8F-EEBF719D63D7_="
X-Mailer: MailMate (1.9.6r5356)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JtJl_MO7BjZQ4iX9S6U8DkQWzqU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 15:08:39 -0000

--=_MailMate_02915F07-3C6E-4A49-9A8F-EEBF719D63D7_=
Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown
Content-Transfer-Encoding: quoted-printable

We=E2=80=99ve hit critical mass and the event is ON!  Logistics TBA.  Sti=
ll =

room for more presenters, should you be interested.  Email me with your =

interest and a working title to grab a slot.

=E2=80=94aaron

On 3 Jul 2017, at 14:06, Aaron Falk wrote:

> I have five folks signed up.  IMO, that seems to be right on the cusp =

> of making it worth the effort to hold the event.  Anyone else want to =

> step up?
>
> On 21 Jun 2017, at 18:09, Aaron Falk wrote:
>
>> This is a poll for folks who are interested in presenting at a =

>> PechaKucha in Prague.  The number of folks presenting has declined =

>> slightly and I=E2=80=99m contemplating whether holding a session at ev=
ery =

>> IETF meeting is too frequent.  If I don=E2=80=99t hear from enough fol=
ks =

>> we=E2=80=99ll wait until Singapore to do the next one.  In other words=
, if =

>> you want to give a talk, please send me a note ASAP.
>>
>> Standard invitation and background info below.
>>
>> Thanks!
>>
>> =E2=80=94aaron
>>
>> ____
>>
>> A Pecha Kucha is a lightning-talk presentation format, originating in =

>> Japan, where a speaker presents 20 image-only slides that are each on =

>> the screen for 20 seconds and advance automatically.  With each talk =

>> lasting for 6:40, it has the feature of forcing presentations -- good =

>> or bad -- to be focused and brief.  This is an unofficial event. =

>> Topics are encouraged to be a IETF-related and satirical or =

>> controversial in some way, although not mean-spirited.  Anyone can =

>> participate in this social event.  Video from the Berlin, Seoul, and =

>> Chicago PKs can be found [here](http://snaggletooth.akam.ai).
>>
>> Format Details:
>>
>> * Presentation slots are open to all, assigned first come, first =

>> served.
>> * To reserve a presentation slot, send a name and title to =

>> aaron.falk@gmail.com and receive confirmation.
>> * Presenters must agree to adhere to the Pecha Kucha format (20 =

>> slides, primarily image-only, automatically advancing every 20 =

>> seconds).
>> * There are lots of online tutorials and suggestions for how to make =

>> a good Pecha Kucha.  Here are a few: =

>> [[1](http://www.pechakucha.org/)], =

>> [[2](http://blog.indezine.com/2012/05/10-tips-to-create-and-present-pe=
cha.html)], =

>> [[3](https://catherinecronin.wordpress.com/2012/06/13/pecha-kucha/)].

--=_MailMate_02915F07-3C6E-4A49-9A8F-EEBF719D63D7_=
Content-Type: text/html; charset=utf-8
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">We=E2=80=99ve hit critical mass and the event is ON!  Log=
istics TBA.  Still room for more presenters, should you be interested.  E=
mail me with your interest and a working title to grab a slot.</p>

<p dir=3D"auto">=E2=80=94aaron</p>

<p dir=3D"auto">On 3 Jul 2017, at 14:06, Aaron Falk wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<p dir=3D"auto">I have five folks signed up.  IMO, that seems to be right=
 on the cusp of making it worth the effort to hold the event.  Anyone els=
e want to step up?</p>

<p dir=3D"auto">On 21 Jun 2017, at 18:09, Aaron Falk wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#999; margin:0 0 5=
px; padding-left:5px; border-left-color:#999">
<p dir=3D"auto">This is a poll for folks who are interested in presenting=
 at a PechaKucha in Prague.  The number of folks presenting has declined =
slightly and I=E2=80=99m contemplating whether holding a session at every=
 IETF meeting is too frequent.  If I don=E2=80=99t hear from enough folks=
 we=E2=80=99ll wait until Singapore to do the next one.  In other words, =
if you want to give a talk, please send me a note ASAP.</p>

<p dir=3D"auto">Standard invitation and background info below.</p>

<p dir=3D"auto">Thanks!</p>

<p dir=3D"auto">=E2=80=94aaron</p>

<hr style=3D"background:#333; background-image:linear-gradient(to right, =
#ccc, #333, #ccc); border:0; height:1px" height=3D"1">

<p dir=3D"auto">A Pecha Kucha is a lightning-talk presentation format, or=
iginating in Japan, where a speaker presents 20 image-only slides that ar=
e each on the screen for 20 seconds and advance automatically.  With each=
 talk lasting for 6:40, it has the feature of forcing presentations -- go=
od or bad -- to be focused and brief.  This is an unofficial event. Topic=
s are encouraged to be a IETF-related and satirical or controversial in s=
ome way, although not mean-spirited.  Anyone can participate in this soci=
al event.  Video from the Berlin, Seoul, and Chicago PKs can be found <a =
href=3D"http://snaggletooth.akam.ai" style=3D"color:#999">here</a>.</p>

<p dir=3D"auto">Format Details:</p>

<ul>
<li>Presentation slots are open to all, assigned first come, first served=
=2E</li>
<li>To reserve a presentation slot, send a name and title to <a href=3D"m=
ailto:aaron.falk@gmail.com" style=3D"color:#999">aaron.falk@gmail.com</a>=
 and receive confirmation.</li>
<li>Presenters must agree to adhere to the Pecha Kucha format (20 slides,=
 primarily image-only, automatically advancing every 20 seconds).</li>
<li>There are lots of online tutorials and suggestions for how to make a =
good Pecha Kucha.  Here are a few: [<a href=3D"http://www.pechakucha.org/=
" style=3D"color:#999">1</a>], [<a href=3D"http://blog.indezine.com/2012/=
05/10-tips-to-create-and-present-pecha.html" style=3D"color:#999">2</a>],=
 [<a href=3D"https://catherinecronin.wordpress.com/2012/06/13/pecha-kucha=
/" style=3D"color:#999">3</a>].</li>
</ul>
</blockquote>
</blockquote>
</div>
</div>
</body>
</html>

--=_MailMate_02915F07-3C6E-4A49-9A8F-EEBF719D63D7_=--


From nobody Wed Jul  5 09:35:08 2017
Return-Path: <akatlas@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51FED129B3A for <ietf@ietfa.amsl.com>; Wed,  5 Jul 2017 09:35:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.738
X-Spam-Level: 
X-Spam-Status: No, score=-1.738 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, HTML_OBFUSCATE_05_10=0.26, 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 L6jVkIJPUaWb for <ietf@ietfa.amsl.com>; Wed,  5 Jul 2017 09:35:05 -0700 (PDT)
Received: from mail-wr0-x22d.google.com (mail-wr0-x22d.google.com [IPv6:2a00:1450:400c:c0c::22d]) (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 E9C0F131D75 for <ietf@ietf.org>; Wed,  5 Jul 2017 09:35:04 -0700 (PDT)
Received: by mail-wr0-x22d.google.com with SMTP id c11so266149433wrc.3 for <ietf@ietf.org>; Wed, 05 Jul 2017 09:35:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=87bkqP2qFoerfg23oyH3SQKdxG+CHJRXUDtcGRsHdF4=; b=dYFRz/IY2Er6dy06MmMTg/VM7xp1V1B94uNdX78Wb6GWln/vmzmCy7Qp8mhjYhLjD+ KvNNZng4TBiJf5b2ryFXn7DcsvW7XQl7ah54/8HptVmOijyWaEQbErT24ONr3UKOtPCj 83Vb6Sg7Cw9/jZsjTO4ARnSsdb7gBkIyxVuk8UV3JKAsMlKC7EEEohuw23mAyutWlate uZh6j6mocM5BZqbkYplxyb+070nRf2DQdBi2ThlTYOP46RI5sYgM7F0fX8KZN+ihaMFq ESEYe40PYP9TNnnBEAbiJM9MeWwFUdgGRyB1kZzK5Kjou78BjNbS/Hi3n7yafyGkjsH+ BweA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=87bkqP2qFoerfg23oyH3SQKdxG+CHJRXUDtcGRsHdF4=; b=a4KwADEbdAx9egBdWbQxVOXJV1x7LxYkJI5ku6wpsrpa7quEy1iFC26boHOWxh8OwR X6WV6kXr8TDO2ajp23NKxTyvJO4p4sEbcbiUL8cISebBIqS0f3vxT38WCdz/2h231Ni7 wvEI7Avm6TqT8jfQc/uSqiOa+YFuj1HFzIJbgg/WeHn9vv+v2hguJPe2l2WUljDaCnjM p/KKMLSOikD4MhLxJwWsWLhj0MHX2yRADp5WILzXd137pLC+zCKAfemPOR+y8Fa3/KPF VjQu2aKFUGpf/03fscpb5dr2PpElm8cJb1HOEY6moRuzhyiPGbwUA3R3Icuo2kBbU/Od cfkA==
X-Gm-Message-State: AKS2vOw8yqu/FZPikdbHGe848EwKRYlekZK3PUyB+I/Fgd8sUwkFagCU +M9LXdNLqstnP4tC8sQc55Zk8y6c6Cwf
X-Received: by 10.223.163.12 with SMTP id c12mr38457619wrb.85.1499272503257; Wed, 05 Jul 2017 09:35:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.130.179 with HTTP; Wed, 5 Jul 2017 09:35:02 -0700 (PDT)
From: Alia Atlas <akatlas@gmail.com>
Date: Wed, 5 Jul 2017 12:35:02 -0400
Message-ID: <CAG4d1rdoou33FO=X2jVSmhJSJjh5dZY=7cg6pkOiz9KvOeyPtQ@mail.gmail.com>
Subject: strawman policy for handling geo-focused outreach: draft-atlas-geo-focused-activities-00.txt
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="f403045f214efa73210553949415"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cOPx1QLx7-DZeK-g74nhdl79Qh4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 16:35:07 -0000

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

If you are interested in this discussion, I expect that follow-up on the
vmeet@ietf.org mailing list makes sense.

Regards,
Alia


---------- Forwarded message ----------
From: Alia Atlas <akatlas@gmail.com>
Date: Wed, Jul 5, 2017 at 12:30 PM
Subject: strawman policy for handling geo-focused outreach:
draft-atlas-geo-focused-activities-00.txt
To: vmeet <vmeet@ietf.org>


Here is a draft suggesting how to connect in the various
geographically-focused activities into the IETF with light oversight and
considering how various IETF policies should apply.

I hope that it will spur conversation so we can determine the right way
forward.

Regards,
Alia


---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: Tue, Jul 4, 2017 at 1:35 PM
Subject: I-D Action: draft-atlas-geo-focused-activities-00.txt
To: i-d-announce@ietf.org



A New Internet-Draft is available from the on-line Internet-Drafts
directories.


        Title           : Geographically-Focused IETF Activities
        Authors         : Alia Atlas
                          Christian O'Flaherty
                          Harish Chowdhary
        Filename        : draft-atlas-geo-focused-activities-00.txt
        Pages           : 14
        Date            : 2017-07-04

Abstract:
   The document defines how Geographically-Focused IETF Activities are
   organized and how IETF policies apply.  It is intended for eventual
   publication as a BCP but this is currently an initial strawman
   proposal based upon the existing variety of experience with the
   experimental activities in this space over the past several years.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-atlas-geo-focused-activities/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-atlas-geo-focused-activities-00
https://datatracker.ietf.org/doc/html/draft-atlas-geo-focused-activities-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft
<https://www.ietf.org/mailman/listinfo/i-d-announceInternet-Draft>
directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

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

<div dir=3D"ltr"><div>If you are interested in this discussion, I expect th=
at follow-up on the <a href=3D"mailto:vmeet@ietf.org">vmeet@ietf.org</a> ma=
iling list makes sense.</div><div><br></div><div>Regards,</div><div>Alia</d=
iv><div><br></div><br><div class=3D"gmail_quote">---------- Forwarded messa=
ge ----------<br>From: <b class=3D"gmail_sendername">Alia Atlas</b> <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:akatlas@gmail.com">akatlas@gmail.com</a>&g=
t;</span><br>Date: Wed, Jul 5, 2017 at 12:30 PM<br>Subject: strawman policy=
 for handling geo-focused outreach: draft-atlas-geo-focused-activities-00.t=
xt<br>To: vmeet &lt;<a href=3D"mailto:vmeet@ietf.org">vmeet@ietf.org</a>&gt=
;<br><br><br><div dir=3D"ltr"><div>Here is a draft suggesting how to connec=
t in the various geographically-focused activities into the IETF with light=
 oversight and considering how various IETF policies should apply.</div><di=
v><br></div><div>I hope that it will spur conversation so we can determine =
the right way forward.</div><div><br></div><div>Regards,</div><div>Alia</di=
v><div><br></div><br><div class=3D"gmail_quote">---------- Forwarded messag=
e ----------<br>From: <b class=3D"gmail_sendername"></b> <span dir=3D"ltr">=
&lt;<a href=3D"mailto:internet-drafts@ietf.org" target=3D"_blank">internet-=
drafts@ietf.org</a>&gt;</span><br>Date: Tue, Jul 4, 2017 at 1:35 PM<br>Subj=
ect: I-D Action: draft-atlas-geo-focused-<wbr>activities-00.txt<br>To: <a h=
ref=3D"mailto:i-d-announce@ietf.org" target=3D"_blank">i-d-announce@ietf.or=
g</a><br><br><br><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 Geographically-Focused IETF Activities<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Alia=
 Atlas<br>
=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 Christian O&#39;Flaherty<br>
=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 Harish Chowdhary<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-atl=
as-geo-focused-activi<wbr>ties-00.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 14<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2017-07-04<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0The document defines how Geographically-Focused IETF Activitie=
s are<br>
=C2=A0 =C2=A0organized and how IETF policies apply.=C2=A0 It is intended fo=
r eventual<br>
=C2=A0 =C2=A0publication as a BCP but this is currently an initial strawman=
<br>
=C2=A0 =C2=A0proposal based upon the existing variety of experience with th=
e<br>
=C2=A0 =C2=A0experimental activities in this space over the past several ye=
ars.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-atlas-geo-focused-activit=
ies/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/d<w=
br>oc/draft-atlas-geo-focused-act<wbr>ivities/</a><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-atlas-geo-focused-activities-0=
0" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/dr<wbr>=
aft-atlas-geo-focused-activiti<wbr>es-00</a><br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-atlas-geo-focused-ac=
tivities-00" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.=
org/d<wbr>oc/html/draft-atlas-geo-focuse<wbr>d-activities-00</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" target=
=3D"_blank">ftp://ftp.ietf.org/internet-dr<wbr>afts/</a><br>
<br>
______________________________<wbr>_________________<br>
I-D-Announce mailing list<br>
<a href=3D"mailto:I-D-Announce@ietf.org" target=3D"_blank">I-D-Announce@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i-d-announceInternet-Draft=
" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/l<wbr>i=
stinfo/i-d-announce<br>
Internet-Draft</a> directories: <a href=3D"http://www.ietf.org/shadow.html"=
 rel=3D"noreferrer" target=3D"_blank">http://www.ietf.org/shadow.htm<wbr>l<=
/a><br>
or <a href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" rel=3D"noreferrer"=
 target=3D"_blank">ftp://ftp.ietf.org/ietf/1shado<wbr>w-sites.txt</a><br>
</div><br></div>
</div><br></div>

--f403045f214efa73210553949415--


From nobody Wed Jul  5 10:22:15 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EC7F131AB1 for <ietf@ietfa.amsl.com>; Wed,  5 Jul 2017 10:22:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 qHRGRWTRA2Io for <ietf@ietfa.amsl.com>; Wed,  5 Jul 2017 10:22:10 -0700 (PDT)
Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (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 A05B0129B3A for <ietf@ietf.org>; Wed,  5 Jul 2017 10:22:10 -0700 (PDT)
Received: by mail-qt0-x22c.google.com with SMTP id r30so191978615qtc.0 for <ietf@ietf.org>; Wed, 05 Jul 2017 10:22:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=O36WfedRiDsk0G9pyri0mxH7KDRrteiCcBg5gHkOIu4=; b=LXAwA5Oe7qA0/XI2N0UTMZTD2D0QCsGer7EatLrwWqMrrf0Jk4EZgKydaz2B61VYY9 SbmCPjHFzIARiANeSzzF8oAwXAMPIEB3nSWAjpcM0yIBVLGVhcnaNBgqkp5hfpfJz9eJ jJ2OQIAeACb++ZzZxQAxP1FL6V3hTCPI5ijIWXUmVwXLBl1T4UNgLuRbTZOeyth4WRas fJzUwITmNhOQgOziOfTN+B+KxYLrj3V4t2T9CN5iTgypMp6Udc3lxrRtbGK6zwjVvs5f tBWeOHOVf3wG3Y5dGYAk6keX+ltySnYD+UUq7TNlu5dRGJx1aL+7Yy01y+dh9mYZ/OTq Lqfg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=O36WfedRiDsk0G9pyri0mxH7KDRrteiCcBg5gHkOIu4=; b=kQGAYWnac4p9VTai0JE/aU8XtgwRFd+0nzoS8CYp6GtnAY16i/skWbaApHnotCM4FV NjyqiR6ynh1jM7meM+cUMF/rEZptl75HHj0NcDUDzHsZpUUbR64yp3d2Jno9X8fIt9jc V9tUKDYD40l6lpc9LEW/DC7zzfead1mcNE4+us1GPYgK0QVXqgiOGZGXwheaaU2wL+ZO 7PC5Mn00z8keX6hr2E1q3vGyot/0yNprOqpVL2cBemognXe46zm0lZ/wZByxw89g6eOT QTQ51EV591pr06fXxfBACi7ar3VtOlUToWabgNla9TPMcij3dvgZxqx97bDMOb5rWR0R KS7Q==
X-Gm-Message-State: AKS2vOyG4/5ZccjuCwxQa36vjn4z6mUbz7wJ1atPqwO19qZSlrcPXzlc jtjTQfiXgt6cWZyW
X-Received: by 10.200.54.38 with SMTP id m35mr58328970qtb.220.1499275329848; Wed, 05 Jul 2017 10:22:09 -0700 (PDT)
Received: from macbook-pro-6.ether.lede.home (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id b64sm15922535qkc.32.2017.07.05.10.22.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Jul 2017 10:22:09 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <69A1DC89-EEA7-40E7-8F6D-8B1574895BE8@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4D4227A7-F19F-478A-9D12-752F35A8803A"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [DNSOP] Minor editorial change to draft-ietf-dnsop-sutld-ps
Date: Wed, 5 Jul 2017 13:22:08 -0400
In-Reply-To: <CACweHNCAi7JcOW9CX=6FViv1wUoe5fhn7deJ2eieP2-D_FhaSA@mail.gmail.com>
Cc: Mark Andrews <marka@isc.org>, dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
To: Matthew Kerwin <matthew@kerwin.net.au>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <20170705000229.5918D7D8457F@rock.dv.isc.org> <CACweHNCAi7JcOW9CX=6FViv1wUoe5fhn7deJ2eieP2-D_FhaSA@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0aVxuS-LYhIyIx2vaFNB2v3tJBs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 17:22:12 -0000

--Apple-Mail=_4D4227A7-F19F-478A-9D12-752F35A8803A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jul 4, 2017, at 10:23 PM, Matthew Kerwin <matthew@kerwin.net.au> =
wrote:
> Hi, I'm jumping in at a random time with a possibly dumb question, but
> the talk of <name,type> and <name,type,class> tuples got me wondering
> about representation in general, and URLs in particular.

This is an interesting topic, but out of scope for the document being =
discussed.   There was discussion of this topic at a BoF a couple of =
IETFs ago, I think run by Andrew Sullivan and Suzanne Woolf, but I may =
be misremembering.


--Apple-Mail=_4D4227A7-F19F-478A-9D12-752F35A8803A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jul 4, 2017, at 10:23 PM, Matthew Kerwin &lt;<a =
href=3D"mailto:matthew@kerwin.net.au" =
class=3D"">matthew@kerwin.net.au</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">Hi, I'm jumping in at a random time with =
a possibly dumb question, but</span><br style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">the talk of =
&lt;name,type&gt; and &lt;name,type,class&gt; tuples got me =
wondering</span><br style=3D"font-family: Menlo-Regular; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">about representation in general, and URLs =
in particular.</span></div></blockquote></div><br class=3D""><div =
class=3D"">This is an interesting topic, but out of scope for the =
document being discussed. &nbsp; There was discussion of this topic at a =
BoF a couple of IETFs ago, I think run by Andrew Sullivan and Suzanne =
Woolf, but I may be misremembering.</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_4D4227A7-F19F-478A-9D12-752F35A8803A--


From nobody Wed Jul  5 10:25:25 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1C75131D4F for <ietf@ietfa.amsl.com>; Wed,  5 Jul 2017 10:25:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 dFfOvrF_x-yh for <ietf@ietfa.amsl.com>; Wed,  5 Jul 2017 10:25:22 -0700 (PDT)
Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (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 B29A9131AB1 for <ietf@ietf.org>; Wed,  5 Jul 2017 10:25:21 -0700 (PDT)
Received: by mail-qt0-x22c.google.com with SMTP id 32so192186607qtv.1 for <ietf@ietf.org>; Wed, 05 Jul 2017 10:25:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=AoLCXvpYs03z+5hHrwXCBFfDkWQHqqs0CF/68CnSRpI=; b=Z2ZQ4YEIkFGE3HfbMY+Fesf2+9yMDaVe+qiVIrYrCaZLIz5LVgxUD3H74OsnP5kkJQ daPuMFqyEftYADx1Z7isyx2lX2T53+cyAZPcDku0yF4x99YyeWnu+SqbQXw6afPLrJf2 3Zt/xlSwbXNj9VgUVxtkfbsG/QpdZYpRh8GKiL40ifT3C4ltrXbRxzQSXBtxvSnF1B5Y hVLw3E9zk8TfZ+U1KuzV+PIZlK80ky9zq/Hgx+XlUPLtunshq8Y8yPGVr9OmoPIqCe4N 0jKxfe9pMk/nvhdO3KNSqE08IQ4Xf1DNIsfcKYTXfJ2o02lExzmvZOcYRwweKOMLjSRN ITkA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=AoLCXvpYs03z+5hHrwXCBFfDkWQHqqs0CF/68CnSRpI=; b=XXpfl8krpMeSQA0ZIZ8sCpFmr9j5NCf5Ra0NziABfjixetOI0t4vhSim81mGbxbA+v jDtBdVWjhJo9agJZZhPQ+XOA5pV63Q7ZZcT13Dx1J5x95ZpTEnA0Dt86hso417GR1+cy uAX04pSykeLtx6gE8Chv5XPPzTzaPp4tLSjPtrv9nUUXUGRxKyUwrgfX+xIhJ0tjfY2S yzBRcrrHVF4sDdLFb0xGw7u0oOnJTk+SxK1hHW0Chpa9dtMH4TL4DLOmJjCKP9fj3PY2 fE7RRlJK3drsJzJU58N6SyO1g6qO5ZVE4xRk95g7fPUPO/63T+Yashvk8PoPIyXupzr2 LbyA==
X-Gm-Message-State: AIVw112AmI69GxrZ2CdOXxxcMFdUvxCf6Res/TpckmUs6NBqjCMi2B7A HwV4Ht/Wk2Qd2zOmgABsgQ==
X-Received: by 10.200.58.4 with SMTP id w4mr4753746qte.188.1499275520892; Wed, 05 Jul 2017 10:25:20 -0700 (PDT)
Received: from macbook-pro-6.ether.lede.home (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id y6sm17098619qky.1.2017.07.05.10.25.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Jul 2017 10:25:20 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <965D02EE-48D0-45CF-80EE-70A97C5C330D@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_45302548-BEDA-49AB-A75A-73AAB8EEC7EC"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Minor philosophical update to draft-ietf-dnsop-sutld-ps
Date: Wed, 5 Jul 2017 13:25:19 -0400
In-Reply-To: <20170704170910.66459.qmail@ary.lan>
Cc: ietf@ietf.org
To: John Levine <johnl@taugh.com>
References: <20170704170910.66459.qmail@ary.lan>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dSrlhSpXqQDxanzc75k-fUD6U2g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 17:25:24 -0000

--Apple-Mail=_45302548-BEDA-49AB-A75A-73AAB8EEC7EC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Jul 4, 2017, at 1:09 PM, John Levine <johnl@taugh.com> wrote:
> Special use TLDs are the North Korea of the IETF.  Everyone agrees
> they're a problem, but there's no agreement about what to do, with
> attitudes ranging from resigned acceptance to aggressive
> countermeasures.
>=20
> The countermeasures all have problems.  Some make implausible
> assumptions like knowing in advance where all the missile launchers,
> er, stunt resolvers are.  Others would take strong action that would
> produce a toxic rain of collateral damage on their allies.

Actually, one of the reasons we did a problem statement document and not =
a "why are these useful" document as Randy has suggested is that there =
is no consensus even that special-use names are a problem.   A lot of =
people think that it's gTLDs that are the problem, not special-use =
names: gTLDs, by allocating names that ought to have been special-use =
names, have created a serious problem in that we can no longer use =
special-use names freely, and that not all uses of special-use names =
remain possible.

I don't mean to open a discussion into that topic here=E2=80=94I realize =
that there is no consensus on it, and that this position is not shared =
by various people, yourself included.   I just want to point out that =
you've expressed it as universally true that people think special-use =
names are bad, and that is not in fact the case: if it were, we wouldn't =
need to publish this document.


--Apple-Mail=_45302548-BEDA-49AB-A75A-73AAB8EEC7EC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jul 4, 2017, at 1:09 PM, John Levine &lt;<a =
href=3D"mailto:johnl@taugh.com" class=3D"">johnl@taugh.com</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">Special use TLDs =
are the North Korea of the IETF. &nbsp;Everyone agrees</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">they're a problem, but there's no agreement =
about what to do, with</span><br style=3D"font-family: Menlo-Regular; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">attitudes ranging =
from resigned acceptance to aggressive</span><br style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" =
class=3D"">countermeasures.</span><br style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">The countermeasures all have problems. =
&nbsp;Some make implausible</span><br style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">assumptions like =
knowing in advance where all the missile launchers,</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">er, stunt resolvers are. &nbsp;Others would take =
strong action that would</span><br style=3D"font-family: Menlo-Regular; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">produce a toxic =
rain of collateral damage on their =
allies.</span></div></blockquote></div><br class=3D""><div =
class=3D"">Actually, one of the reasons we did a problem statement =
document and not a "why are these useful" document as Randy has =
suggested is that there is no consensus even that special-use names are =
a problem. &nbsp; A lot of people think that it's gTLDs that are the =
problem, not special-use names: gTLDs, by allocating names that ought to =
have been special-use names, have created a serious problem in that we =
can no longer use special-use names freely, and that not all uses of =
special-use names remain possible.</div><div class=3D""><br =
class=3D""></div><div class=3D"">I don't mean to open a discussion into =
that topic here=E2=80=94I realize that there is no consensus on it, and =
that this position is not shared by various people, yourself included. =
&nbsp; I just want to point out that you've expressed it as universally =
true that people think special-use names are bad, and that is not in =
fact the case: if it were, we wouldn't need to publish this =
document.</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_45302548-BEDA-49AB-A75A-73AAB8EEC7EC--


From nobody Wed Jul  5 10:29:48 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F79C131D8A for <ietf@ietfa.amsl.com>; Wed,  5 Jul 2017 10:29:43 -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); dkim=pass (1536-bit key) header.d=iecc.com header.b=DIjK9i1J; dkim=pass (1536-bit key) header.d=taugh.com header.b=AXteJXqV
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 XTBhDhz_buHb for <ietf@ietfa.amsl.com>; Wed,  5 Jul 2017 10:29:41 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D577C131D4F for <ietf@ietf.org>; Wed,  5 Jul 2017 10:29:40 -0700 (PDT)
Received: (qmail 20587 invoked from network); 5 Jul 2017 17:29:39 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=5068.595d2203.k1707; bh=606xQ5tP06oN79BLFB8ZDvUd5VlwLhNEup7GmXquliM=; b=DIjK9i1J4MEZvOF0RdKpuSkt08pZ9Sp5gR2u3krcE1vaV4dlybFJiANJXg9vq6tnUzPvE86zrRaXm+zCoG9pYAfw+aeiZwaB53b1SZe9y0Dog2mqWE0Dkj/nNJfdctmTX+VBlq91XIaQShOWk+/HK7lKa5mItkp3bE2sWddQbEjdoi7giJ96DFpviwXe1F/5MjCzdffXahm46C8EtSb3+ykj3QdYgxjzfWKUgTEIAxj4k/kizptgj4SJDfq401+O
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=5068.595d2203.k1707; bh=606xQ5tP06oN79BLFB8ZDvUd5VlwLhNEup7GmXquliM=; b=AXteJXqVJnkfj/2nP4CGUQFeOwAkCG0pn2INf6g2VkcZDW+6erIMyADZtZH5eZNmld2xSjAvkncvq5fQq3qgKY7cAXC+tIG3G+UEhsQU6P5xUZTxuFXQNKuIkOrTUhuPGwa4JeqTxZYBEoKjNpyh6wvMNgZEFtdCweve6PTElz1Q0xLf4bfY4BL1b8WCFAb4xecS8o/M+WMJ353wEwMcnG86LzSYmTmvQWvgEyBFctbeEl1/3KikX1+UZ5TWPEtg
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 05 Jul 2017 17:29:39 -0000
Date: 5 Jul 2017 13:29:39 -0400
Message-ID: <alpine.OSX.2.21.1707051328530.86608@ary.qy>
From: "John R Levine" <johnl@taugh.com>
To: "Ted Lemon" <mellon@fugue.com>
Cc: "IETF general list" <ietf@ietf.org>
Subject: Re: Minor philosophical update to draft-ietf-dnsop-sutld-ps
In-Reply-To: <965D02EE-48D0-45CF-80EE-70A97C5C330D@fugue.com>
References: <20170704170910.66459.qmail@ary.lan> <965D02EE-48D0-45CF-80EE-70A97C5C330D@fugue.com>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-1275218499-1499275779=:86608"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1YXVPcVBxmY_bP9Kfcvhgf8HQio>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 17:29:44 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-1275218499-1499275779=:86608
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT

> I don't mean to open a discussion into that topic here—I realize that there is no consensus on it, and that this position is not shared by various people, yourself included.   I just want to point out that you've expressed it as universally true that people think special-use names are bad, and that is not in fact the case: if it were, we wouldn't need to publish this document.

I didn't say they're bad, I said they're a problem which is not the same 
thing.

It really isn't helpful to rephrase other people's statements and get them 
wrong, particularly when everyone can just read the original.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly
--0-1275218499-1499275779=:86608--


From nobody Wed Jul  5 10:40:12 2017
Return-Path: <fielding@gbiv.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82ABD131C88; Wed,  5 Jul 2017 10:40:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.019
X-Spam-Level: 
X-Spam-Status: No, score=-2.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gbiv.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 BizkT1VFhzUx; Wed,  5 Jul 2017 10:40:00 -0700 (PDT)
Received: from homiemail-a59.g.dreamhost.com (sub5.mail.dreamhost.com [208.113.200.129]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2910D131C81; Wed,  5 Jul 2017 10:40:00 -0700 (PDT)
Received: from homiemail-a59.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a59.g.dreamhost.com (Postfix) with ESMTP id 8F6D5E036902; Wed,  5 Jul 2017 10:38:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gbiv.com; h=content-type :mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=gbiv.com; bh=DK/a8Xow23nO7et9Bc9A7ySc/DE=; b=StIWitCY7ys1iS4UnHYJC6LYXhfB IdKDCMsyKG3hzs8EAiryuD9s5DgV3QFYRllM/lK6XjbXxO/p9U3gE1ZUr2/0mm3i HFRX5CT8hzne2HAPa1B3IRyvKNpDF3DTXt9CAySytVsyrNqLUSby9PcYqiQwP82Q cRWKFQDvt5XuUog=
Received: from [192.168.1.11] (ip68-228-64-138.oc.oc.cox.net [68.228.64.138]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: fielding@gbiv.com) by homiemail-a59.g.dreamhost.com (Postfix) with ESMTPSA id D9D61E003A95; Wed,  5 Jul 2017 10:29:18 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: [DNSOP] Minor editorial change to draft-ietf-dnsop-sutld-ps
From: "Roy T. Fielding" <fielding@gbiv.com>
In-Reply-To: <CACweHNCAmZPOUmat5ruh6qkYrECM2fh15n49P+zDcJ0gfoEGvg@mail.gmail.com>
Date: Wed, 5 Jul 2017 10:29:18 -0700
Cc: Mark Andrews <marka@isc.org>, dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <765A15BF-8505-4470-9628-70CE9665BC16@gbiv.com>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <20170705000229.5918D7D8457F@rock.dv.isc.org> <CACweHNCAi7JcOW9CX=6FViv1wUoe5fhn7deJ2eieP2-D_FhaSA@mail.gmail.com> <20170705031957.834B97D8FBDD@rock.dv.isc.org> <CACweHNCAmZPOUmat5ruh6qkYrECM2fh15n49P+zDcJ0gfoEGvg@mail.gmail.com>
To: Matthew Kerwin <matthew@kerwin.net.au>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hhVwtw6wOyJXuHzJ2i2JTD5QD_4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 17:40:03 -0000

> On Jul 4, 2017, at 9:23 PM, Matthew Kerwin <matthew@kerwin.net.au> =
wrote:
>=20
> On 5 July 2017 at 13:19, Mark Andrews <marka@isc.org> wrote:
>>=20
>> In message =
<CACweHNCAi7JcOW9CX=3D6FViv1wUoe5fhn7deJ2eieP2-D_FhaSA@mail.gmail.com>, =
Matthew Kerwin writes:
>>> On 5 July 2017 at 10:02, Mark Andrews <marka@isc.org> wrote:
>>>>=20
>>>> Who owns a name is a different question to what machines serve the
>>>> <name,type,class> tuple and how do you reach those machines.  There
>>>> is absolutely no reason why the zones <name,IN> and <name,CLASS56>
>>>> need to be served by the same machines.  There is a argument for
>>>> them both being under control of the same people.
>>>>=20
>>>> Mark
>>>>=20
>>>=20
>>> Hi, I'm jumping in at a random time with a possibly dumb question, =
but
>>> the talk of <name,type> and <name,type,class> tuples got me =
wondering
>>> about representation in general, and URLs in particular.
>>>=20
>>> RFCs 3986 and 7230 say[*] that every 'host' in a HTTP URL that looks
>>> like a DNS name is a DNS name, and that they have to be resolved to =
IP
>>> addresses if you want to fetch them, but they don't talk =
meaningfully

No, RFC3986 does not say anything of the sort.  Neither does 7230.

>>> [*] https://tools.ietf.org/html/rfc3986#section-3.2.2 :
>>>=20
>>>   """A registered name intended for lookup in the DNS uses the =
syntax
>>>   defined in Section 3.5 of [RFC1034] and Section 2.1 of =
[RFC1123]."""
>>>=20
>>> I read that as: "if it matches RFC1034 (and isn't overridden by the
>>> specific URI scheme's rules) it's a DNS name."  It could be read the
>>> other way, but that just adds more assumptions.

Just read the text as written:  "A registered name intended for lookup =
in DNS ..."
which doesn't limit much at all, and certainly doesn't say that all =
dot-notations
are DNS names.

The sentence immediately preceding that one is:

   A host identified by a registered name is a sequence of characters
   usually intended for lookup within a locally defined host or service
   name registry, though the URI's scheme-specific semantics may require
   that a specific registry (or fixed name table) be used instead.

with both "usually" and "locally defined" being relevant.

And two paragraphs later it has:

   This specification does not mandate a particular registered name
   lookup technology and therefore does not restrict the syntax of reg-
   name beyond what is necessary for interoperability.  Instead, it
   delegates the issue of registered name syntax conformance to the
   operating system of each application performing URI resolution, and
   that operating system decides what it will allow for the purpose of
   host identification.  A URI resolution implementation might use DNS,
   host tables, yellow pages, NetInfo, WINS, or any other system for
   lookup of registered names.  However, a globally scoped naming
   system, such as DNS fully qualified domain names, is necessary for
   URIs intended to have global scope.  URI producers should use names
   that conform to the DNS syntax, even when use of DNS is not
   immediately apparent, and should limit these names to no more than
   255 characters in length.

And that's exactly how it works, in practice.

....Roy


From nobody Wed Jul  5 11:03:35 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 840E5131563 for <ietf@ietfa.amsl.com>; Wed,  5 Jul 2017 11:03:33 -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 dhSllxKaWpMg for <ietf@ietfa.amsl.com>; Wed,  5 Jul 2017 11:03:32 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB572131D80 for <ietf@ietf.org>; Wed,  5 Jul 2017 11:03:31 -0700 (PDT)
Received: (qmail 24850 invoked from network); 5 Jul 2017 18:03:31 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 5 Jul 2017 18:03:31 -0000
Date: 5 Jul 2017 18:03:09 -0000
Message-ID: <20170705180309.71215.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: new DNS classes
In-Reply-To: <20170704233315.AAA7D7D84127@rock.dv.isc.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/38yLGgGaBC8wPzC3fv1FLHqAR74>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 18:03:33 -0000

In article <20170704233315.AAA7D7D84127@rock.dv.isc.org> you write:
>As to whether a class has a parallel heirachy or not depends on
>how we define the use of the class.

It hardly matters, because there's no practical way to bootstrap a new
class.

If all classes have the same root, the root servers for any new class
are the same as the ICANN managed root, and short of an implusible
revolt by the root server operators (one of which is of course ICANN),
they'll have the same management issues that the IN tree does.

Or if they don't have the same root, it's just another alt root, and
we know where that leads.

R's,
John

PS: I would also note that several special use TLDs do things you
can't even express in the DNS.  When you resolve a .onion name,
you don't get an rrset, you get an open socket.


From nobody Wed Jul  5 14:04:57 2017
Return-Path: <mjethanandani@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F0A7131DE0; Wed,  5 Jul 2017 14:04:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mahesh Jethanandani <mjethanandani@gmail.com>
To: <ops-dir@ietf.org>
Cc: draft-ietf-trill-arp-optimization.all@ietf.org, ietf@ietf.org, trill@ietf.org
Subject: Opsdir last call review of draft-ietf-trill-arp-optimization-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149928869116.8318.7080669996560577650@ietfa.amsl.com>
Date: Wed, 05 Jul 2017 14:04:51 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zrRvWiOw0YQpwrjFJmFkNFjZ0ZQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 21:04:51 -0000

Reviewer: Mahesh Jethanandani
Review result: Has Nits

I have reviewed this document as part of the Operational directorate’s ongoing
effort to review all IETF documents being processed by the IESG.
 These comments were written with the intent of improving the
operational aspects of the IETF drafts. Comments that are not addressed in last
call may be included in AD reviews during the IESG review.  Document editors
and WG chairs should treat these comments just like any other last
call comments.

Document reviewed:  draft-ietf-trill-arp-optimization-08

Summary: Ready with Nits

Document Status: Standard Track

General Comments: The abstract of the document says that the draft tries “To
reduce the burden on a TRILL campus caused by these multi-destination messages,
RBridges MAY implement an "optimized ARP/ND response", as specified herein,
when the target's location is known by the ingress RBridge or can be obtained
from a directory. This avoids ARP/ND query and answer flooding.” Implementation
of this draft will impact the operations of the network. As such careful
consideration should be placed on operational and management impact of the
draft.

The following comments look at the document both from an operational
perspective as well as a management perspective.

Operational Considerations:

Operational considerations include installation and initial setup, migration
path, requirements on other protocols, impact on network operations and
verification of correct operation.

>From an impact on network operations perspective, this draft proposes to reduce
the traffic in the network by preventing a network wide broadcast and multicast
of messages. As such it should reduce the impact on the network, when operating
correctly. In the worst case, that it is not operating or operating
incorrectly, these network broadcast and multicast messages will “leak” into
the broader network, where they will be treated just as they are in todays
network. For this reason, a migration path may not be required, or existing
protocols modified to deal with the change.

>From a verification of correct operations, it is not clear how one determines
that the RBridge is operating correctly beyond observing individual ARP/ND
messages. Does it keep track of ARP/ND messages it has intercepted and
responded to on the local network, which would have escaped to the broader
network? Keeping track of statistics will allow for tracking the operation of
what is defined in the draft.

Management Considerations:

Management considerations include interoperability, fault management,
configuration management, accounting, performance and security.

>From a configuration management perspective, it is not clear how the
configuration of the RBridge is realized. For example, per the draft, RBridge
might not verify an IP address if the network manager's policy is to have the
network behave, for each Data Label, as if it were a single link and just
believe an ARP/ND it receives. If such a configuration is desired, this or an
accompanying document needs to define the manageability aspect of RBridge,
preferably in the form of a YANG model.

>From a accounting perspective, For example, in the draft, RBridge could for
generic ARP/ND request seeking the MAC address corresponding to an IP address,
if the edge RBridge knows the IP address and corresponding MAC, behavior is as
in item (a), otherwise behavior is as in item (b). Behavior for gratuitous ARP
and ND Unsolicited Neighbor Advertisements [RFC4861] is given in item (c). And
item (d) covers handling of Address Probe ARP Query. Are there specific
statistics being maintained for each of these options? Keeping track of
individual options allows for capacity management and planning.

A run of idnits revealed a few warnings:

Miscellaneous warnings:
  ----------------------------------------------------------------------------

  == Line 99 has weird spacing: '...enience  along...'

  -- The document date (April 17, 2017) is 79 days in the past.  Is this
     intentional?

  Checking references for intended status: Proposed Standard
  ----------------------------------------------------------------------------

     (See RFCs 3967 and 4897 for information about using normative references
     to lower-maturity documents in RFCs)

  == Missing Reference: 'IA-draft' is mentioned on line 390, but not defined

  == Unused Reference: 'RFC7356' is defined on line 540, but no explicit
     reference was found in the text

  == Outdated reference: draft-ietf-trill-directory-assist-mechanisms has
     been published as RFC 8171

     Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 1 comment (--).

     Run idnits with the --verbose option for more detailed information about
     the items above.

--------------------------------------------------------------------------------



From nobody Wed Jul  5 14:21:16 2017
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D2371316A5 for <ietf@ietfa.amsl.com>; Wed,  5 Jul 2017 14:21:10 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.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 inES52U0uP2N for <ietf@ietfa.amsl.com>; Wed,  5 Jul 2017 14:21:09 -0700 (PDT)
Received: from mail-vk0-x231.google.com (mail-vk0-x231.google.com [IPv6:2607:f8b0:400c: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 9F88E131DE0 for <ietf@ietf.org>; Wed,  5 Jul 2017 14:21:07 -0700 (PDT)
Received: by mail-vk0-x231.google.com with SMTP id 191so467719vko.2 for <ietf@ietf.org>; Wed, 05 Jul 2017 14:21:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ypmNCJ5tpUYBBtW6z5rFClnHI6OoFjhfc1gORxAQC5M=; b=B9jkYbMC7HbC/6HaG4yjsdlEnSeS245W5IhoTUZ+l8zqjfDDL5csTJMBdMKtceF97i tgxXnmak5gKGvbywKBkFD4HcjKERXIivO2veBBxzjgOi7nVr9f+oPRXSa5oRjZly9LvN EpFrJSJvld3+s00Es0T7+N6lc3kxxci9E07nD3F3yTik5xWEET08ogFP1LiEhWx6gf9J Z183Ob7TRDgUV351Brl51dWIglPGw4H+HFMJ7lrwPTFh+2RFW/xxN/Tz56tQ2ee+l1CC FEuNjp6fHZ3tQHC0O2MLIdV4SsvvKg3OZrL1l1JLP94G0vkysYEN8Mk6xi39e8VCJhxY pTMA==
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=ypmNCJ5tpUYBBtW6z5rFClnHI6OoFjhfc1gORxAQC5M=; b=XgDxVAd7EmfNjHGi5U3IfVnBv8xG5EPsehBVmtH7tKc0GDHGf1U/XlIqcgE8i58wm4 9H95U+Iz3Qd0gzqPqSaamTXL64V0OzOgXWRnuCJjH6E2elrSfbf2ZhxmoZrqehMlD8sw SUopSlbxnbTjMi10NCpaZW1tRK/qTdKIFKmtszhtIw6S2aHtT1TevLoFYWqngI/b/nPa G5kjFntOPM+dTND91Q5zOocz5BiaGmk50YdtV7YbpnUUQ+QABgxSxoOhOj7694aPyeMu 40/zKNFDbsN/S04Ddqxy/c9LH0Yt8SfgtsywOFOjT/nd86XGSFzZHlJNf42CYS0iGib3 7v0g==
X-Gm-Message-State: AIVw1114DxlwQL4mQgWpx5u6N0ShEEozqM1SmzKx9gC/M1RnajVHfaWF nu9DyYGBhHEk5ArGK2lowWMDkbhFn3LSgks=
X-Received: by 10.31.75.66 with SMTP id y63mr3967308vka.65.1499289666622; Wed, 05 Jul 2017 14:21:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.39.165 with HTTP; Wed, 5 Jul 2017 14:20:26 -0700 (PDT)
In-Reply-To: <149925973580.17545.6979655005275084891@ietfa.amsl.com>
References: <149925973580.17545.6979655005275084891@ietfa.amsl.com>
From: Warren Kumari <warren@kumari.net>
Date: Wed, 5 Jul 2017 17:20:26 -0400
Message-ID: <CAHw9_iJPpDj5Sz6dcXT8H-886v-QhXfyR+m2SpEkgYLr9UPkkA@mail.gmail.com>
Subject: Re: Tsvart telechat review of draft-ietf-trill-mtu-negotiation-06
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Cc: tsv-art@ietf.org, draft-ietf-trill-mtu-negotiation.all@ietf.org,  IETF Discuss <ietf@ietf.org>, trill@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/o1MYV3Ebs70RBHw7SvL5wCDgv-A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 21:21:10 -0000

I wanted to quickly thank Magnus for this review - it is well thought
out, and clear.

I usually focus on the OpsDir reviews, but wanted to explicitly call
this out as a good one.

W

On Wed, Jul 5, 2017 at 9:02 AM, Magnus Westerlund
<magnus.westerlund@ericsson.com> wrote:
> Reviewer: Magnus Westerlund
> Review result: Not Ready
>
> This TSV-ART review is influenced by that I did the review of
> draft-ietf-trill-over-ip.
>
> 1. So draft-ietf-trill-over-ip-10 has MTU discovery needs for
> determining if the UDP encapsulation will work or not. It references  in
> Section 8.4 the old RFC, i.e. RFC 6325, which is updated by
> draft-ietf-trill-mtu-negotiation.
>
>     TRILL IS-IS MTU PDUs, as specified in Section 5 of [RFC6325] and in
>     [RFC7177], can be used to obtain added assurance of the MTU of a
>     link.
>
> However, this is not quite true, as if the IP path MTU is below 1470
> bytes, which is not unheard of, the algorithm in the MTU negotiation
> draft can't determine it. It will only report the IP path as having an
> MTU to small when the 1470 bytes probe fail.
>
> So, if the trill-over-ip authors want to use this as a mechanism, then the MTU
> negotiation draft needs to be expanded to have more flexible lower
> boundaries. However, that appear to affect MTU negotiation quite
> significant as it needs to separate algorithm for finding MTU, from the
> different usage of the algorithm with different starting points. Where
> the normal will have a lower bound of 1470, and be more tightly coupled
> to Sz when finding Lz. While the Trill-over-IP has a different usage.
>
> I think the trill WG needs to decide on how to slice this. If the
> MTU-negotiation only targets the explicit targets in the current draft and goes
> forward now. Or if they want to meet trill-over-ip's goals which will require
> restructuring.
>
> 2. Another issue, is that I think the algorithm is a bit short on
> transmission scheduling recommendations:
>
>     1) If RB1 successfully receives the MTU-ack from RB2 to the probe of
>        the value of link-wide Lz within k tries (where k is a
>        configurable parameter whose default is 3), link MTU size is set
>        to the size of link-wide Lz and stop.
>
> If I do this test with all three packets back to back at line rate, I could
> potentially get all probes lost in the same burst loss in router queue or
> switch fabric. What I think is needed here is a specification on how these
> probes are transmitted. Spaced in a particular way, or at least minimal
> distance, and are the additional probes only sent after the previous has been
> judged to have been lost, which makes it interact with the next issue.
>
> 3. This is also unclear on what the criteria is for determining that something
> is lost:
>
>       a) If RB1 fails to receive an MTU-ack from RB2 after k tries, RB1
>           sets the "failed minimum MTU test" flag for RB2 in RB1's Hello
>           and stop.
>
> I fail to see any specification for the criteria when an MTU-ack should be
> considered to have failed to reach the probing entity. So this appear to
> require a timeout, and thus a timeout interval. Is the RTT known so that one
> can define something as lost after N*RTT? Are there possible delays in sending
> the MTU-ack that are considered okay that can affect this?
>
> 4. Section 3, the algorithm in Step 1 is unable to reach the first termination
> condition (3) "If lowerBound >= upperBound" in some cases.
>
>   Step 1: RB1 tries to send an MTU-probe padded to the size x.
>
>    1) If RB1 fails to receive an MTU-ack from RB2 after k tries:
>
>          upperBound is set to x and x is set to [(lowerBound +
>          upperBound)/2], rounded up to the nearest integer.
>
>    2) If RB1 receives an MTU-ack to a probe of size x from RB2:
>
>          link MTU size is set to x, lowerBound is set to x and x is set
>          to [(lowerBound + upperBound)/2], rounded up to the nearest
>          integer.
>
>    3) If lowerBound >= upperBound or Step 1 has been repeated n times
>       (where n is a configurable parameter whose default value is 5),
>       stop.
>
>    4) Repeat Step 1.
>
> I run this on the input data: Lower bound = 1470, Upper bound = 9216 and with
> an MTU of 7935 and gets the following sequence:
>
> Lower   Upper   X
> 1470    9216    5343
> 5343    9216    7280
> 7280    9216    8248
> 7280    8248    7764
> 7764    8248    8006
> 7764    8006    7885
> 7885    8006    7946
> 7885    7946    7916
> 7916    7946    7931
> 7931    7946    7939
> 7931    7939    7935
> 7935    7939    7937
> 7935    7937    7936
> 7935    7936    7936
> 7935    7936    7936
>
> Thus, the termination condition needs to change. The second I notice is that
> having a limitation on number of steps as 5, results in quite a large gap
> between upper and lower bound in which the MTU exists in.
>
> 5. I frankly gets confused by the application of the binary search. First it
> will in many case not be run to termination where the actual MTU is determined.
> Then the result of the upper and lower bound are just used to confirm the Sz
> value. There are no discussion about using the MTU search to determine a new
> possible value for Sz. The text is not even explicit that lower bound is the
> highest known to work Transmission unit size at the time of testing. I think
> section 3, should conclude in determine some TU value, and if that is Sz or
> something other appears quite relevant for what to do in the later sections.
>
>



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf


From nobody Wed Jul  5 14:24:20 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8D9F131DF7 for <ietf@ietfa.amsl.com>; Wed,  5 Jul 2017 14:24:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 ZQIqUqpxiGGH for <ietf@ietfa.amsl.com>; Wed,  5 Jul 2017 14:24:18 -0700 (PDT)
Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::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 55A841316A5 for <ietf@ietf.org>; Wed,  5 Jul 2017 14:24:18 -0700 (PDT)
Received: by mail-qt0-x236.google.com with SMTP id 32so1258689qtv.1 for <ietf@ietf.org>; Wed, 05 Jul 2017 14:24:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=L/nrDdo+hE8iCwpWhdt4lxpGmraHhxdH9peDHKQbQyM=; b=A58VNFp2bGrdfNx9C85ItFjY51DVkuyxmiQTYQdQaD9zk6ThjCBf1Bu9bCOqRoA7In USKWKJB9ILFSHbrM0iqSrZkyN0WEYzuwYGwOo1r9TmIU2zu0LgmjIGZke44sHVmT7ZdI Em78e45lXC/Opo+qCGYOKbysKKQr6IfGtGOJJ0wjYtWBnpHSDtW+RtGj/slHJZjh9LK0 adGeSiwXOxpzONmrddFDd9z4TH0eX+s3D5Rl3XhFef0UVTSB+x9MgWtoGjuDGybbqDSk kvnOeBChfTpRcKYV0qvrxyFaKxYxXDur1aEcWyYumYWwMgXymxlAk8wBqQKb7EdRMvan xgXg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=L/nrDdo+hE8iCwpWhdt4lxpGmraHhxdH9peDHKQbQyM=; b=dMkJ8VRQjwGg4BOcVNA2jmc03aDIsQ2b3DrWwXzZv8AqtataonCtEey39R+lJE6xh4 on62X/uqQGjQipWq3zOO5R8zEQnDAQF3HlDnDzLJFf5SLNmHG/AMXHhLMUzwXVODLQBt r5OePvkWF5knejhZkBCLmvVokAZ7YgpbLUTJ708v1Q0+5XlXwc1vty5Vs070bPJQbp9Y udNBOM1Hx/mnX8WhJd4oEUqahdak5lMyc52fZsCpNRkjGzuAwHfTVCssSz+jzvpjaoMe 59lNxQNf5zQQuAvgwcVDrSDfKciOU6GApOifNeQ8Qh7BEapg61mgyd+g3sZiXvy+BWEF 5tNw==
X-Gm-Message-State: AKS2vOxhTNWR1QlYalt2Oo9cT9gOtvmnGWS9qcZHrAjWAtUv3h8oBDqI wxtt2b4Th2Z/5iDQoyfjdQ==
X-Received: by 10.237.37.174 with SMTP id x43mr59697559qtc.133.1499289857352;  Wed, 05 Jul 2017 14:24:17 -0700 (PDT)
Received: from macbook-pro-6.ether.lede.home (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id f128sm98407qkc.13.2017.07.05.14.24.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Jul 2017 14:24:16 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <647E3C09-C8E4-40E4-85A6-8A76BB37097A@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_10FB41A8-A85A-4DEE-AF3F-E5338A46B9EB"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Minor philosophical update to draft-ietf-dnsop-sutld-ps
Date: Wed, 5 Jul 2017 17:24:15 -0400
In-Reply-To: <alpine.OSX.2.21.1707051328530.86608@ary.qy>
Cc: IETF general list <ietf@ietf.org>
To: John R Levine <johnl@taugh.com>
References: <20170704170910.66459.qmail@ary.lan> <965D02EE-48D0-45CF-80EE-70A97C5C330D@fugue.com> <alpine.OSX.2.21.1707051328530.86608@ary.qy>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zNeIJug1Wkmlphcc7v7D4pRiMX4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 21:24:20 -0000

--Apple-Mail=_10FB41A8-A85A-4DEE-AF3F-E5338A46B9EB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jul 5, 2017, at 1:29 PM, John R Levine <johnl@taugh.com> wrote:
> It really isn't helpful to rephrase other people's statements and get =
them wrong, particularly when everyone can just read the original.

Actually it is helpful, because if you get it wrong, they clarify.   I'm =
sorry for having gotten it wrong, of course, but that's how I read what =
you said.


--Apple-Mail=_10FB41A8-A85A-4DEE-AF3F-E5338A46B9EB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jul 5, 2017, at 1:29 PM, John R Levine &lt;<a =
href=3D"mailto:johnl@taugh.com" class=3D"">johnl@taugh.com</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">It really isn't =
helpful to rephrase other people's statements and get them wrong, =
particularly when everyone can just read the original.</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""></div></blockquote></div><br class=3D""><div =
class=3D"">Actually it is helpful, because if you get it wrong, they =
clarify. &nbsp; I'm sorry for having gotten it wrong, of course, but =
that's how I read what you said.</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_10FB41A8-A85A-4DEE-AF3F-E5338A46B9EB--


From nobody Wed Jul  5 16:11:16 2017
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42A7A126B6E; Wed,  5 Jul 2017 16:11:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 HrM3A69TEmxV; Wed,  5 Jul 2017 16:11:12 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (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 03662120227; Wed,  5 Jul 2017 16:11:12 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id 8A3AB24AE15; Wed,  5 Jul 2017 23:11:02 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 3C822160098; Wed,  5 Jul 2017 23:11:06 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 2A6F7160099; Wed,  5 Jul 2017 23:11:06 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ts9GJnjE8INH; Wed,  5 Jul 2017 23:11:06 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 7F304160098; Wed,  5 Jul 2017 23:11:05 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id E23E77D9B7A1; Thu,  6 Jul 2017 09:11:01 +1000 (AEST)
To: "Roy T. Fielding" <fielding@gbiv.com>
Cc: Matthew Kerwin <matthew@kerwin.net.au>, dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <20170705000229.5918D7D8457F@rock.dv.isc.org> <CACweHNCAi7JcOW9CX=6FViv1wUoe5fhn7deJ2eieP2-D_FhaSA@mail.gmail.com> <20170705031957.834B97D8FBDD@rock.dv.isc.org> <CACweHNCAmZPOUmat5ruh6qkYrECM2fh15n49P+zDcJ0gfoEGvg@mail.gmail.com> <765A15BF-8505-4470-9628-70CE9665BC16@gbiv.com>
Subject: Re: [DNSOP] Minor editorial change to draft-ietf-dnsop-sutld-ps
In-reply-to: Your message of "Wed, 05 Jul 2017 10:29:18 -0700." <765A15BF-8505-4470-9628-70CE9665BC16@gbiv.com>
Date: Thu, 06 Jul 2017 09:11:01 +1000
Message-Id: <20170705231101.E23E77D9B7A1@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/G30mTpZMR8Gd6aLDCdM8MUw3kmA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 23:11:14 -0000

In message <765A15BF-8505-4470-9628-70CE9665BC16@gbiv.com>, "Roy T. Fielding" writes:
> > On Jul 4, 2017, at 9:23 PM, Matthew Kerwin <matthew@kerwin.net.au> =
> wrote:
> >=20
> > On 5 July 2017 at 13:19, Mark Andrews <marka@isc.org> wrote:
> >>=20
> >> In message =
> <CACweHNCAi7JcOW9CX=3D6FViv1wUoe5fhn7deJ2eieP2-D_FhaSA@mail.gmail.com>, =
> Matthew Kerwin writes:
> >>> On 5 July 2017 at 10:02, Mark Andrews <marka@isc.org> wrote:
> >>>>=20
> >>>> Who owns a name is a different question to what machines serve the
> >>>> <name,type,class> tuple and how do you reach those machines.  There
> >>>> is absolutely no reason why the zones <name,IN> and <name,CLASS56>
> >>>> need to be served by the same machines.  There is a argument for
> >>>> them both being under control of the same people.
> >>>>=20
> >>>> Mark
> >>>>=20
> >>>=20
> >>> Hi, I'm jumping in at a random time with a possibly dumb question, =
> but
> >>> the talk of <name,type> and <name,type,class> tuples got me =
> wondering
> >>> about representation in general, and URLs in particular.
> >>>=20
> >>> RFCs 3986 and 7230 say[*] that every 'host' in a HTTP URL that looks
> >>> like a DNS name is a DNS name, and that they have to be resolved to =
> IP
> >>> addresses if you want to fetch them, but they don't talk =
> meaningfully
> 
> No, RFC3986 does not say anything of the sort.  Neither does 7230.
> 
> >>> [*] https://tools.ietf.org/html/rfc3986#section-3.2.2 :
> >>>=20
> >>>   """A registered name intended for lookup in the DNS uses the =
> syntax
> >>>   defined in Section 3.5 of [RFC1034] and Section 2.1 of =
> [RFC1123]."""
> >>>=20
> >>> I read that as: "if it matches RFC1034 (and isn't overridden by the
> >>> specific URI scheme's rules) it's a DNS name."  It could be read the
> >>> other way, but that just adds more assumptions.
> 
> Just read the text as written:  "A registered name intended for lookup =
> in DNS ..."
> which doesn't limit much at all, and certainly doesn't say that all =
> dot-notations
> are DNS names.
> 
> The sentence immediately preceding that one is:
> 
>    A host identified by a registered name is a sequence of characters
>    usually intended for lookup within a locally defined host or service
>    name registry, though the URI's scheme-specific semantics may require
>    that a specific registry (or fixed name table) be used instead.
> 
> with both "usually" and "locally defined" being relevant.
> 
> And two paragraphs later it has:
> 
>    This specification does not mandate a particular registered name
>    lookup technology and therefore does not restrict the syntax of reg-
>    name beyond what is necessary for interoperability.  Instead, it
>    delegates the issue of registered name syntax conformance to the
>    operating system of each application performing URI resolution, and
>    that operating system decides what it will allow for the purpose of
>    host identification.  A URI resolution implementation might use DNS,
>    host tables, yellow pages, NetInfo, WINS, or any other system for
>    lookup of registered names.  However, a globally scoped naming
>    system, such as DNS fully qualified domain names, is necessary for
>    URIs intended to have global scope.  URI producers should use names
>    that conform to the DNS syntax, even when use of DNS is not
>    immediately apparent, and should limit these names to no more than
>    255 characters in length.
> 
> And that's exactly how it works, in practice.
> 
> ....Roy

And the actual presentation limit for LDH with DNS is 253 (encodes
as 255 octets on the wire).  Remember URI names do not have a final
period and the each label has length octet when encoded as a DNS
name and the name is terminated by the root label (0x00) in DNS
wire form and the DNS wire name is limited to 255 octets.

The name "a" is 0x01 0x61 0x00 on the wire when encoded in the DNS.
The name "a.b" is 0x01 0x61 0x01 0x62 0x00 on the wire when encoded
in the DNS.

An arbitary DNS name may be up to 1004 ascii characters when converted
to presentation format.  0x00 has a presentation format of "\000"
and this may occur up to 250 times as the maximum label length is
63.  Add in seperating periods (3) and a final period the becomes
1004 in absolute form.  As a C NUL terminated string you need a
buffer of 1005 bytes to hold it.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Wed Jul  5 21:36:19 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 193C8129461; Wed,  5 Jul 2017 21:36:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 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, 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 Vci55RV2p_rE; Wed,  5 Jul 2017 21:36:16 -0700 (PDT)
Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (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 41B951243FE; Wed,  5 Jul 2017 21:36:16 -0700 (PDT)
Received: by mail-lf0-x22c.google.com with SMTP id h22so4400569lfk.3; Wed, 05 Jul 2017 21:36:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=V8dDEX5M0XIia6gUEqiksXZFnKBoTQBiiR7LFzF8d08=; b=fFN36po4WTLFNsUR1emAnSQMOw+s4M3Asrs1YDZn4fnx8921WlYsJLWVM4B8tENehS mP5J+riEJjtkCkaxuaxGQFlFZXQHY6alxaO1MqvZ9lFg5zrpqClvEwSj7yxKzNPPA5YC HUru+1YnkMtw5FvQflmEusTNltJSK5sE/nmsn9evAZ3S3MDizdjCunuyPbscMPSgCTtj oEfZvkI8zozJlaqhqpdQZeftzcozvccql1l2TIYyNIuJjbY15e8FOJ9Ip4L48a7jE3Nn Af2xK732090fFS9FddlkF96RgK6dJoD0AwfLiU4AlMcBziK+egso+YiGLh2eMuOJnrfk CLEQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=V8dDEX5M0XIia6gUEqiksXZFnKBoTQBiiR7LFzF8d08=; b=icAH8GGPEc8S7tFsBiO/Gu/zrLomkKzddbRoVBD0L85YYaGfFloaLO2WOYVFh7pqqC d53+G63H7oG62mBoooHgjbtZdlofdDWfCiqof1vlCSwD9hDwZcdJN52eo54uePKuxEPo 7SFZaPjJ6waNfKWMy4tSfHd9LQD7n/BjQRyGSoF0zH6MhnZ9WY/I9GixrGXGFW6OFKc0 w5We1U1X4EUPoBwrHJAx1KcEeb7bLqghcHyItntyZEhN6mwmGsDqmBsPrxY1yxAyPLxB Z/s1XQUFt8q2cn1SUVS6z0IU5xZEGD5rCKIzVCb3DHh9ZG6kew38yAahJB5eX2qTvbp4 K5+w==
X-Gm-Message-State: AKS2vOz4nA33sjERjYXb2+8WMfMEGp06nmn2U5/T3V9pVZVgD+9Cielp bj22RekIzC/s6WYnmxKq7LdZ7y1Wxg==
X-Received: by 10.46.22.22 with SMTP id w22mr14248753ljd.76.1499315774526; Wed, 05 Jul 2017 21:36:14 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.25.181.214 with HTTP; Wed, 5 Jul 2017 21:36:13 -0700 (PDT)
In-Reply-To: <595BE0D5.5000106@redbarn.org>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 6 Jul 2017 00:36:13 -0400
X-Google-Sender-Auth: 11VU_fcJcw2ddh7WhambWdWUxQM
Message-ID: <CAMm+Lwjd6xVp-EDp=doevx=AP8qws_Mv++aL733yHEyUF72EMA@mail.gmail.com>
Subject: Re: new DNS classes
To: Paul Vixie <paul@redbarn.org>
Cc: dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="f403045fb428259b6605539ea89e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sCzL46_ecxkxYowFxXGBZlBTqUY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jul 2017 04:36:18 -0000

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

There are changes to the DNS that are practical and those that are not. For
better or worse, I can't see any way that teaching DNS to use new classes
makes any sense at this point. The only point at which it would have made
sense was when internationalization happened. But the path chosen makes
more sense.

ICANN will manage whatever bits of the DNS consensus agrees it should
manage. The only events likely to break consensus would be an attempt by
some government to strong arm ICANN into a breach of faith with the
community and succeeding or some really spectacular peculation.

It seems to me that if people want to do anything new with DNS that they
should use prefixes, new RRs or both as the mechanism, not the class which
is limited anyway.

DNS is not a full service directory. Nor does it need to be. A UDP packet
is big enough for a link, a fingerprint and a digital signature. That is
all that you ever need.

The X.500 and UDDI models were broken because there is no point in putting
information into a directory if the service can return it in a service
handshake.

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">The=
re are changes to the DNS that are practical and those that are not. For be=
tter or worse, I can&#39;t see any way that teaching DNS to use new classes=
 makes any sense at this point. The only point at which it would have made =
sense was when internationalization happened. But the path chosen makes mor=
e sense.</div><div class=3D"gmail_default" style=3D"font-size:small"><br></=
div><div class=3D"gmail_default" style=3D"font-size:small">ICANN will manag=
e whatever bits of the DNS consensus agrees it should manage. The only even=
ts likely to break consensus would be an attempt by some government to stro=
ng arm ICANN into a breach of faith with the community and succeeding or so=
me really spectacular peculation.</div><div class=3D"gmail_default" style=
=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"font-s=
ize:small">It seems to me that if people want to do anything new with DNS t=
hat they should use prefixes, new RRs or both as the mechanism, not the cla=
ss which is limited anyway.</div><div class=3D"gmail_default" style=3D"font=
-size:small"><br></div><div class=3D"gmail_default" style=3D"font-size:smal=
l">DNS is not a full service directory. Nor does it need to be. A UDP packe=
t is big enough for a link, a fingerprint and a digital signature. That is =
all that you ever need.</div><div class=3D"gmail_default" style=3D"font-siz=
e:small"><br></div><div class=3D"gmail_default" style=3D"font-size:small">T=
he X.500 and UDDI models were broken because there is no point in putting i=
nformation into a directory if the service can return it in a service hands=
hake.</div><div class=3D"gmail_default" style=3D"font-size:small"><br></div=
><div class=3D"gmail_default" style=3D"font-size:small"><br></div><div clas=
s=3D"gmail_default" style=3D"font-size:small"><br></div></div>

--f403045fb428259b6605539ea89e--


From nobody Wed Jul  5 23:25:27 2017
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50D58127419; Wed,  5 Jul 2017 23:25:15 -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 v4afxM_IO5Yf; Wed,  5 Jul 2017 23:25:13 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 C3A4F127076; Wed,  5 Jul 2017 23:25:12 -0700 (PDT)
X-AuditID: c1b4fb3a-bea2a9c000001b2f-8b-595dd7c63330
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id EC.76.06959.6C7DD595; Thu,  6 Jul 2017 08:25:11 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.98]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0352.000; Thu, 6 Jul 2017 08:25:10 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Elwyn Davies <elwynd@dial.pipex.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-sipcore-content-id.all@ietf.org" <draft-ietf-sipcore-content-id.all@ietf.org>, "sipcore@ietf.org" <sipcore@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Genart telechat review of draft-ietf-sipcore-content-id-07
Thread-Topic: Genart telechat review of draft-ietf-sipcore-content-id-07
Thread-Index: AQHS9Kv2eEN+imnuHUCXFFEalQVB+aJGV7yQ
Date: Thu, 6 Jul 2017 06:25:10 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4CC5278F@ESESSMB109.ericsson.se>
References: <149916225425.16088.10318703158229973440@ietfa.amsl.com>
In-Reply-To: <149916225425.16088.10318703158229973440@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupgkeLIzCtJLcpLzFFi42KZGbFdWvf49dhIg8cvOS1mnt3FYrHtuKDF 1VefWSyebZzPYvH1xyY2B1aP4yt2snssWfKTKYApissmJTUnsyy1SN8ugSvj4LNW1oIlvBW7 GnaxNjD+4Oli5OSQEDCROLjvOHsXIxeHkMARRol1b39BOYsYJX6dW8HaxcjBwSZgIdH9Txuk QUQgUGLm6gmsIDXMAisZJa5MaWEBSQgLuEt8urSIEaLIQ+LRpt9MELaRxLbuVewgc1gEVCRa T5WBhHkFfCXWL3vHBmILCbhINO2ewAxicwq4Srz8OpsdxGYUEJP4fmoN2BhmAXGJW0/mM0Ec LSCxZM95ZghbVOLl43+sELaSROOSJ2AnMwtoSqzfpQ/RqigxpfshO8RaQYmTM5+wTGAUnYVk 6iyEjllIOmYh6VjAyLKKUbQ4tbg4N93ISC+1KDO5uDg/Ty8vtWQTIzB+Dm75bbWD8eBzx0OM AhyMSjy8xcdiI4VYE8uKK3MPMUpwMCuJ8B46CRTiTUmsrEotyo8vKs1JLT7EKM3BoiTO67Dv QoSQQHpiSWp2ampBahFMlomDU6qBseZG8ZvPKzRkLj1bxuIU+PfgjcnWbusrls9dWt6efffb C+sVBz5on2Rete6qC4tFYk+z1XpWTuEr+xTblrQf5wi0TI665a/1VjIwcaq0wueIyPKTaRoM FkXnfE87Z/6wkz+VtfaLye3oN7MuPGFPFl8cyLZZPU+AT75BP+nYql0RF/lLvO96K7EUZyQa ajEXFScCAL3I4vibAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_6eumF25DeNKbQb3xukDawpz2VY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jul 2017 06:25:15 -0000

SGkgRWx3eW4sDQoNCldlIHdpbGwgbWFrZSB0aGUgcmVmZXJlbmNlcyBiZWxvdyBpbmZvcm1hdGl2
ZSBpbiB0aGUgbmV4dCB2ZXJzaW9uLg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQotLS0tLU9y
aWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogRWx3eW4gRGF2aWVzIFttYWlsdG86ZWx3eW5kQGRp
YWwucGlwZXguY29tXSANClNlbnQ6IDA0IEp1bHkgMjAxNyAxMTo1OA0KVG86IGdlbi1hcnRAaWV0
Zi5vcmcNCkNjOiBkcmFmdC1pZXRmLXNpcGNvcmUtY29udGVudC1pZC5hbGxAaWV0Zi5vcmc7IHNp
cGNvcmVAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmcNClN1YmplY3Q6IEdlbmFydCB0ZWxlY2hhdCBy
ZXZpZXcgb2YgZHJhZnQtaWV0Zi1zaXBjb3JlLWNvbnRlbnQtaWQtMDcNCg0KUmV2aWV3ZXI6IEVs
d3luIERhdmllcw0KUmV2aWV3IHJlc3VsdDogUmVhZHkNCg0KSSBhbSB0aGUgYXNzaWduZWQgR2Vu
LUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gVGhlIEdlbmVyYWwgQXJlYSBSZXZpZXcgVGVh
bSAoR2VuLUFSVCkgcmV2aWV3cyBhbGwgSUVURiBkb2N1bWVudHMgYmVpbmcgcHJvY2Vzc2VkIGJ5
IHRoZSBJRVNHIGZvciB0aGUgSUVURiBDaGFpci4gUGxlYXNlIHdhaXQgZm9yIGRpcmVjdGlvbiBm
cm9tIHlvdXIgZG9jdW1lbnQgc2hlcGhlcmQgb3IgQUQgYmVmb3JlIHBvc3RpbmcgYSBuZXcgdmVy
c2lvbiBvZiB0aGUgZHJhZnQuDQoNCkZvciBtb3JlIGluZm9ybWF0aW9uLCBwbGVhc2Ugc2VlIHRo
ZSBGQVEgYXQNCg0KPGh0dHBzOi8vdHJhYy5pZXRmLm9yZy90cmFjL2dlbi93aWtpL0dlbkFydGZh
cT4uDQoNCkRvY3VtZW50OiBkcmFmdC1pZXRmLXNpcGNvcmUtY29udGVudC1pZC0wNw0KUmV2aWV3
ZXI6IEVsd3luIERhdmllcw0KUmV2aWV3IERhdGU6IDIwMTctMDctMDQNCklFVEYgTEMgRW5kIERh
dGU6IDIwMTctMDYtMjcNCklFU0cgVGVsZWNoYXQgZGF0ZTogMjAxNy0wNy0wNg0KDQpTdW1tYXJ5
Og0KUmVhZHkuICBUaGFuayB5b3UgZm9yIGFkZHJlc3NpbmcgdGhlIGNvbW1lbnRzIGluIG15IGxh
c3QgY2FsbCByZXZpZXcuDQoNCk1ham9yIGlzc3VlczoNCg0KTWlub3IgaXNzdWVzOg0KDQpOaXRz
L2VkaXRvcmlhbCBjb21tZW50czoNClRoZSByZWZlcmVuY2VzIHRvIFJGQyA1MzY4IGFuZCBSRkMg
NjQ0MiBhcmUgaW5mb3JtYXRpdmUgcmF0aGVyIHRoYW4gbm9ybWF0aXZlIC0geW91IGRvbid0IG5l
ZWQgdGhlIGRldGFpbHMgdG8gaW1wbGVtZW50IHRoaXMgdXBkYXRlLg0KDQo=


From nobody Thu Jul  6 08:15:46 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60B43131548; Thu,  6 Jul 2017 08:15:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 2iP2yO2Rkf0z; Thu,  6 Jul 2017 08:15:45 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B85F129B66; Thu,  6 Jul 2017 08:15:45 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dT8VI-0009FI-Tl; Thu, 06 Jul 2017 11:15:40 -0400
Date: Thu, 06 Jul 2017 11:15:34 -0400
From: John C Klensin <john-ietf@jck.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>, Paul Vixie <paul@redbarn.org>
cc: dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: new DNS classes
Message-ID: <562EC659F89FA92A09CAC4DB@PSB>
In-Reply-To: <CAMm+Lwjd6xVp-EDp=doevx=AP8qws_Mv++aL733yHEyUF72EMA@mail.gmail.com>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <CAMm+Lwjd6xVp-EDp=doevx=AP8qws_Mv++aL733yHEyUF72EMA@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/q9jHULoSIDfQlSJhD-A2X6ebDb8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jul 2017 15:15:46 -0000

--On Thursday, July 6, 2017 00:36 -0400 Phillip Hallam-Baker
<phill@hallambaker.com> wrote:

> There are changes to the DNS that are practical and those that
> are not. For better or worse, I can't see any way that
> teaching DNS to use new classes makes any sense at this point.
> The only point at which it would have made sense was when
> internationalization happened. But the path chosen makes more
> sense.

As the author of the I-D that proposed using a Class to deal
with internationalization, it would not have worked, and the two
important reasons are perhaps worth understanding.   First, that
approach included a transition strategy that permitted legacy
clients and registrations to keep working in a way that users
would see as normal.  But that strategy depends on CLASSes
sharing the same root and hierarchy.  At Paul points out, that
interpretation of 1034/1035 is not universally accepted and
implemented.  Second, IIR, we intended that the different CLASS
allow a different set of matching rule assumptions and
conditions.  Because labels must generally be interpreted and
compared before CLASS values are accessed and, perhaps more
important, in optimization of databases, one probably needs
label types to do that, not CLASSes.   And label types don't
have a good history.

> ICANN will manage whatever bits of the DNS consensus agrees it
> should manage. The only events likely to break consensus would
> be an attempt by some government to strong arm ICANN into a
> breach of faith with the community and succeeding or some
> really spectacular peculation.

We disagree about that, but I no proof that my impressions/
predictions are any better than yours.

> It seems to me that if people want to do anything new with DNS
> that they should use prefixes, new RRs or both as the
> mechanism, not the class which is limited anyway.
> 
> DNS is not a full service directory. Nor does it need to be. A
> UDP packet is big enough for a link, a fingerprint and a
> digital signature. That is all that you ever need.

As I think you know, I just love "all you will ever need"
statements about the Internet (and its predecessors) although my
favorite remains "we will never need more than 8 bits of address
space".


> The X.500 and UDDI models were broken because there is no
> point in putting information into a directory if the service
> can return it in a service handshake.

The X.500 and UDDI approaches failed because... sorry, I lost
count of the reasons :-(

    john





From nobody Thu Jul  6 08:40:04 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 632371317C4; Thu,  6 Jul 2017 08:40:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 GBDm5KSYDChC; Thu,  6 Jul 2017 08:40:01 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DF561317C8; Thu,  6 Jul 2017 08:40:01 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTP id A136FC0028BB; Thu,  6 Jul 2017 08:40:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=kYjLJSqN5bcVCU gZEYpNGC9mLIQ=; b=ylF7B86MeUvSNOgJk/QiEoJfbmIKcCO5KwIYhZd9mwweAD e4IbWAncThxaKJgWUzUrWxMuOMQLRlBdeUAj6RXVP2GL7NWpZRYsbwwvJpvRHn0F w0Ap/PR9F9To3sFKqUoGYAQj+5Zq46H7g2RJeWa+8/HPRNcb8LOkxCoz4nyog=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTPSA id 24CEBC0028BA; Thu,  6 Jul 2017 08:40:00 -0700 (PDT)
Date: Thu, 6 Jul 2017 10:39:56 -0500
From: Nico Williams <nico@cryptonector.com>
To: John C Klensin <john-ietf@jck.com>
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, Paul Vixie <paul@redbarn.org>, dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: new DNS classes
Message-ID: <20170706153955.GB3393@localhost>
References: <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <CAMm+Lwjd6xVp-EDp=doevx=AP8qws_Mv++aL733yHEyUF72EMA@mail.gmail.com> <562EC659F89FA92A09CAC4DB@PSB>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <562EC659F89FA92A09CAC4DB@PSB>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/M_XR_E3h2xsrz9prSf-RH59Ah40>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jul 2017 15:40:02 -0000

On Thu, Jul 06, 2017 at 11:15:34AM -0400, John C Klensin wrote:
> --On Thursday, July 6, 2017 00:36 -0400 Phillip Hallam-Baker
> <phill@hallambaker.com> wrote:
> > The X.500 and UDDI models were broken because there is no
> > point in putting information into a directory if the service
> > can return it in a service handshake.
> 
> The X.500 and UDDI approaches failed because... sorry, I lost
> count of the reasons :-(

The complexity and general ugliness of x.400/x.500 naming (indeed, the
inability to correctly and canonically represent such names in TEXT!)
are all the reason anyone ever should have needed.  (See what I did
there?)  And yet some bits of that horrible thing are still with us
(PKIX, LDAP), though of course with various adaptations (eg, SANs) to
make them suck less and more Internet-like.

DNS is not a directory, but when your only off-the-shelf choices are DNS
or LDAP...

I'll contribute this extension to your earlier argument about root
sharing/non-sharing.  I think new classes will only ever be feasible
provided that a) they share roots with IN, or b) are like a local HS not
really meant to federate at all (thus root sharing / alt. roots would be
moot).  (a) classes would basically be an RR type extension field for
IN.  (b) is probably not worth considering -- the lack of security in HS
was a big reason for not using it, and so DNSSEC (or something like it)
would be a requirement in order to use an HS-like class, but if you'll
want DNSSEC then you'll want delegation hierarchy anyways and thus
you'll want shared roots, making any HS-like classes just IN-class RR
type extension fields.  It's easier to develop a new protocol for (b)
than to shove whatever it is into DNS.

So new classes will only be useful to extend the IN-class RR type
namespace.  We won't get there.  New RR types can be very difficult to
deploy due to lack of interest by registrars and domain hosting
services.  TXT RRs forever.  :(

Cheers,

Nico
-- 


From nobody Thu Jul  6 09:07:01 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D66B131684; Thu,  6 Jul 2017 09:06:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 J928WB0qADDx; Thu,  6 Jul 2017 09:06:45 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 DFB53127444; Thu,  6 Jul 2017 09:06:44 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dT9Ie-0004HA-DG; Thu, 06 Jul 2017 16:06:40 +0000
Date: Thu, 06 Jul 2017 18:06:39 +0200
Message-ID: <m237a9tur4.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Nico Williams <nico@cryptonector.com>
Cc: John C Klensin <john-ietf@jck.com>, dnsop <dnsop@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>, Paul Vixie <paul@redbarn.org>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: new DNS classes
In-Reply-To: <20170706153955.GB3393@localhost>
References: <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <CAMm+Lwjd6xVp-EDp=doevx=AP8qws_Mv++aL733yHEyUF72EMA@mail.gmail.com> <562EC659F89FA92A09CAC4DB@PSB> <20170706153955.GB3393@localhost>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sIJnylwpbExOr-82RMm3cOTdHq4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jul 2017 16:06:47 -0000

> DNS is not a directory, but when your only off-the-shelf choices are DNS
> or LDAP...

this is the ietf.  do not ignore bgp and ldp.


From nobody Thu Jul  6 09:36:51 2017
Return-Path: <shogunx@sleekfreak.ath.cx>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83C4313168A; Thu,  6 Jul 2017 09:36:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.918
X-Spam-Level: 
X-Spam-Status: No, score=-0.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_DYNAMIC=0.982] 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 DFgE6M1KK9bQ; Thu,  6 Jul 2017 09:36:40 -0700 (PDT)
Received: from sleekfreak.ath.cx (rrcs-67-79-182-226.se.biz.rr.com [67.79.182.226]) (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 92BED13164A; Thu,  6 Jul 2017 09:36:40 -0700 (PDT)
Received: from shogunx (helo=localhost) by sleekfreak.ath.cx with local-esmtp (Exim 4.89) (envelope-from <shogunx@sleekfreak.ath.cx>) id 1dT9jU-0004Q7-4i; Thu, 06 Jul 2017 12:34:24 -0400
Date: Thu, 6 Jul 2017 12:34:23 -0400 (EDT)
From: shogunx@sleekfreak.ath.cx
To: Randy Bush <randy@psg.com>
cc: Nico Williams <nico@cryptonector.com>, John C Klensin <john-ietf@jck.com>,  dnsop <dnsop@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>,  Paul Vixie <paul@redbarn.org>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: new DNS classes
In-Reply-To: <m237a9tur4.wl-randy@psg.com>
Message-ID: <alpine.DEB.2.10.1707061225240.20783@sleekfreak.ath.cx>
References: <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <CAMm+Lwjd6xVp-EDp=doevx=AP8qws_Mv++aL733yHEyUF72EMA@mail.gmail.com> <562EC659F89FA92A09CAC4DB@PSB> <20170706153955.GB3393@localhost> <m237a9tur4.wl-randy@psg.com>
User-Agent: Alpine 2.10 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/H-NHv2m5gyBNS8opmA_4ZjKcA1Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jul 2017 16:36:41 -0000

On Thu, 6 Jul 2017, Randy Bush wrote:

>> DNS is not a directory, but when your only off-the-shelf choices are DNS
>> or LDAP...
>
> this is the ietf.  do not ignore bgp and ldp.

+1


From nobody Thu Jul  6 09:57:48 2017
Return-Path: <alissa@cooperw.in>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EB31131670 for <ietf@ietfa.amsl.com>; Thu,  6 Jul 2017 09:57:47 -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, HTML_MESSAGE=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=cooperw.in header.b=CrDJbg+f; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=R2MQtNHa
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 0reRFeHvsoPj for <ietf@ietfa.amsl.com>; Thu,  6 Jul 2017 09:57:45 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2190E12700F for <ietf@ietf.org>; Thu,  6 Jul 2017 09:57:45 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 914D520879 for <ietf@ietf.org>; Thu,  6 Jul 2017 12:57:44 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Thu, 06 Jul 2017 12:57:44 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= 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=YBspLD3hR4FdV10X43WuCI5Ljdsqbf11DNpsM8yPG 3k=; b=CrDJbg+fULEns7qg85IWhjc+EPhh69rVqa6Pge5ip9YF+tc4c3ZBqBIdj nT/dMbW/OtK8QEKlv+n6pP1tcvhA95TZTDE/Lb5qVpvlNvNMUOQxhT908xI5v6id PpZiWEEYm5MndQonGXOaWJCidY8AkCuBw2ZhVYmQLu3lpfJ9S7L9MmXWR7g/dplC B7MIBUDxOv7V0YIs8vugnZwb9X4VbgueMtyBKZyugfbAko8sRc3BKDLpy/e2EZCg hwfWgafUXfBX+rr13IT6irI4+7E4vH0uk2j16u4E8M5kXUIwoAUetpV0V/z73LVY B3D+EfglPDzjEqlf26+gzpjhdoinA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=YBspLD3hR4FdV10X43 WuCI5Ljdsqbf11DNpsM8yPG3k=; b=R2MQtNHaLilk9jwupISFEJQB8uCHPAjw6T 4zJ9nIGwm2vGGtfiGdZ1fZg6j1VN22CD+d/L8lUqoJe7EBShislxoVZVvWGi5LiH 0IV9Tci8MGUJaQzH2jPFDYokP2Lt7eGFlWB3vIRRIta4Y5/VjQRYo9KQesamBVWk hLOd8Rtowr94LX6B+zrMVurso+xnux7URM891UrqwuPtsOya2/KVFfbmWLeCVCw9 niqigRcWI+xqminUbDyU2t6V0+gzIktNk8OuAbHA3B1/GbYCLx9OTrIu6MfzAZWU 1ZG1i4Tv0vZl8/toMIu9JNZt6ekZOtdwA0UVekxz9C4ZnlqrX8tw==
X-ME-Sender: <xms:CGxeWcQ9hWCLPR51CP8Lz44Sg9-Rp5mUZtgzeWubCDAKIddsGSYL3w>
X-Sasl-enc: roc9AgZwCOarIDO4pZmDj0PDRSoXpD2eU7JMo2vQ3+Qw 1499360264
Received: from sjc-alcoop-8814.cisco.com (unknown [128.107.241.163]) by mail.messagingengine.com (Postfix) with ESMTPA id E21D87E6B1 for <ietf@ietf.org>; Thu,  6 Jul 2017 12:57:43 -0400 (EDT)
From: Alissa Cooper <alissa@cooperw.in>
Content-Type: multipart/alternative; boundary="Apple-Mail=_302ADD3C-16D9-4665-81FD-EE5F0547976A"
Message-Id: <1FD8B344-CAFC-434B-8F95-4E8EA0332682@cooperw.in>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Registration for remote participation
Date: Thu, 6 Jul 2017 12:57:42 -0400
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org>
To: IETF Discussion <ietf@ietf.org>
In-Reply-To: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nxDHpprMppNQPKkA18FcZ75_GfM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jul 2017 16:57:47 -0000

--Apple-Mail=_302ADD3C-16D9-4665-81FD-EE5F0547976A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Thanks again for all of the feedback on this proposal. We have =
implemented it for IETF 99. The changes to the remote registration form =
are live at https://www.ietf.org/registration/ietf99/remotereg.py =
<https://www.ietf.org/registration/ietf99/remotereg.py>. The =E2=80=98Join=
 without registration ID option=E2=80=99 that was previously available =
on the remote participation login page will be removed, and we will =
instead include a link to the audio stream for those who do not want to =
register.=20

We received some excellent suggestions for new questions designed to =
help us learn about remote participants; however those questions seem =
better suited to a post-meeting survey than a registration form, =
particularly if we are attempting to keep the form simple and avoid =
imposing any requirements on remote participants that are notably =
different from those included on the in-person registration form. The =
secretariat will be incorporating the feedback into questions for the =
post-meeting survey.=20

Many other suggestions centered around allowing people to use their =
datatracker logins to register for a meeting. This feature is already a =
part of the requirements document that is being developed by the =
secretariat for the new meeting registration system currently in =
development.

Alissa


> On May 9, 2017, at 3:01 PM, IETF Chair <chair@ietf.org> wrote:
>=20
> For remote participants at IETF meetings, registration is currently =
optional. Remote participants may join a session at an IETF meeting by =
entering any name or pseudonym of their choice into the current form =
used for logging in to MeetEcho.
>=20
> The IESG is soliciting community feedback on a proposal to require =
registration for remote participants at IETF meetings. The objective of =
requiring registration for real-time remote participation is to provide =
better data to the IETF community and leadership about the size and =
make-up of the remote participant base. As remote participation grows, =
having more reliable remote participation data will allow the service to =
be better tailored to those using it and the community as a whole, and =
will help us understand the potential impact of remote participation on =
in-person participation. We understand that even with required =
registration the data collected will not be perfect, complete, or =
unspoofable, but we believe it would provide a more credible basis for =
analysis than the data available today.
>=20
> The proposal is as follows:
>=20
> Remote participants would be required to register (for free) by =
providing the information below (* denotes required fields). =
Registration would be mandatory to access MeetEcho sessions in real time =
and to join the remote mic queue during a session.
>=20
> Title
> First / Given Name*
> Last / Family Name*
> Company / Organization
> ISO 3166 Country of Residence*
> Email*
> Gender
> Have you attended an IETF meeting in person before?
> Have you attended an IETF meeting remotely before?
>=20
> Upon registering, participants would be issued a registration ID, just =
as they are today.
>=20
> To join a session, participants would be asked to input the =
registration ID. The same email-based facility that is currently =
available to retrieve a forgotten registration ID would continue to be =
available. The cookie-based =E2=80=9CRemember me=E2=80=9D option would =
also still be available. The only difference from how login works today =
is that the option to "Join without registration ID" would be removed. =
Other options for authentication (leveraging a user-chosen password or =
datatracker credentials) might be explored further in the future.
>=20
> Remote participation registration data would be stored and secured by =
AMS and MeetEcho just as it is currently today. As is the case now, no =
registration or login would be required to access MeetEcho recordings, =
audio recordings, YouTube videos, or jabber rooms. And no changes are =
being proposed as to the handling of virtual blue sheets.
>=20
> We'd like to hear from the community about this proposal. Please send =
comments to ietf@ietf.org <mailto:ietf@ietf.org>, or exceptionally to =
iesg@ietf.org <mailto:iesg@ietf.org>, preferably by May 30, 2017.
>=20
> Thanks,
> The IESG
>=20
>=20


--Apple-Mail=_302ADD3C-16D9-4665-81FD-EE5F0547976A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div class=3D"">Thanks again for all of the feedback on this =
proposal. We have implemented it for IETF 99. The changes to the remote =
registration form are live at&nbsp;<a =
href=3D"https://www.ietf.org/registration/ietf99/remotereg.py" =
class=3D"">https://www.ietf.org/registration/ietf99/remotereg.py</a>. =
The =E2=80=98Join without registration ID option=E2=80=99 that was =
previously available on the remote participation login page will be =
removed, and we will instead include a link to the audio stream for =
those who do not want to register.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">We received some excellent suggestions =
for new questions designed to help us learn about remote participants; =
however those questions seem better suited to a post-meeting survey than =
a registration&nbsp;form, particularly if we are attempting to keep the =
form simple and avoid imposing any requirements on remote participants =
that are notably different from those included on the in-person =
registration form. The secretariat will be incorporating the feedback =
into questions for the post-meeting survey.&nbsp;<br class=3D""><br =
class=3D"">Many other suggestions centered around allowing people to use =
their datatracker logins to register for a meeting. This feature is =
already a part of the requirements document that is being developed by =
the secretariat for the new meeting registration system currently in =
development.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Alissa</div><div class=3D""><br class=3D""></div><br =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
May 9, 2017, at 3:01 PM, IETF Chair &lt;<a href=3D"mailto:chair@ietf.org" =
class=3D"">chair@ietf.org</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><meta =
http-equiv=3D"Content-Type" content=3D"text/html charset=3Dutf-8" =
class=3D""><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space;" class=3D""><div =
class=3D""><div class=3D"">For remote participants at IETF meetings, =
registration is currently optional. Remote participants may join a =
session at an IETF meeting by entering any name or pseudonym of their =
choice into the current form used for logging in to MeetEcho.</div><div =
class=3D""><br class=3D""></div><div class=3D"">The IESG is soliciting =
community feedback on a proposal to require registration for remote =
participants at IETF meetings. The objective of requiring registration =
for real-time remote participation is to provide better data to the IETF =
community and leadership about the size and make-up of the remote =
participant base. As remote participation grows, having more reliable =
remote participation data will allow the service to be better tailored =
to those using it and the community as a whole, and will help us =
understand the potential impact of remote participation on in-person =
participation. We understand that even with required registration the =
data collected will not be perfect, complete, or unspoofable, but we =
believe it would provide a more credible basis for analysis than the =
data available today.</div><div class=3D""><br class=3D""></div><div =
class=3D"">The proposal is as follows:</div><div class=3D""><br =
class=3D""></div><div class=3D"">Remote participants would be required =
to register (for free) by providing the information below (* denotes =
required fields). Registration would be mandatory to access MeetEcho =
sessions in real time and to join the remote mic queue during a =
session.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Title</div><div class=3D"">First / Given Name*</div><div =
class=3D"">Last / Family Name*</div><div class=3D"">Company / =
Organization</div><div class=3D"">ISO 3166 Country of =
Residence*</div><div class=3D"">Email*</div><div =
class=3D"">Gender</div><div class=3D"">Have you attended an IETF meeting =
in person before?</div><div class=3D"">Have you attended an IETF meeting =
remotely before?</div><div class=3D""><br class=3D""></div><div =
class=3D"">Upon registering, participants would be issued a registration =
ID, just as they are today.</div><div class=3D""><br class=3D""></div><div=
 class=3D"">To join a session, participants would be asked to input the =
registration ID. The same email-based facility that is currently =
available to retrieve a forgotten registration ID would continue to be =
available. The cookie-based =E2=80=9CRemember me=E2=80=9D option would =
also still be available. The only difference from how login works today =
is that the option to "Join without registration ID" would be removed. =
Other options for authentication (leveraging a user-chosen password or =
datatracker credentials) might be explored further in the =
future.</div><div class=3D""><br class=3D""></div><div class=3D"">Remote =
participation registration data would be stored and secured by AMS and =
MeetEcho just as it is currently today. As is the case now, no =
registration or login would be required to access MeetEcho recordings, =
audio recordings, YouTube videos, or jabber rooms. And no changes are =
being proposed as to the handling of virtual blue sheets.</div><div =
class=3D""><br class=3D""></div><div class=3D"">We'd like to hear from =
the community about this proposal. Please send comments to&nbsp;<a =
href=3D"mailto:ietf@ietf.org" class=3D"">ietf@ietf.org</a>, or =
exceptionally to&nbsp;<a href=3D"mailto:iesg@ietf.org" =
class=3D"">iesg@ietf.org</a>, preferably by May 30, =
2017.</div></div><div class=3D""><br class=3D""></div><div =
class=3D"">Thanks,</div><div class=3D"">The IESG</div><div class=3D""><br =
class=3D""></div><div class=3D""><br =
class=3D""></div></div></div></blockquote></div><br =
class=3D""></body></html>=

--Apple-Mail=_302ADD3C-16D9-4665-81FD-EE5F0547976A--


From nobody Thu Jul  6 11:04:23 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17F6A13188A; Thu,  6 Jul 2017 11:04:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 ZmLOzk9ivNm2; Thu,  6 Jul 2017 11:04:20 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A79F1131879; Thu,  6 Jul 2017 11:04:20 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dTB8S-0009TV-WC; Thu, 06 Jul 2017 14:04:17 -0400
Date: Thu, 06 Jul 2017 14:04:10 -0400
From: John C Klensin <john-ietf@jck.com>
To: Mark Andrews <marka@isc.org>, "Roy T. Fielding" <fielding@gbiv.com>
cc: dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: [DNSOP] Minor editorial change to draft-ietf-dnsop-sutld-ps
Message-ID: <901C29488D8446E4176CF83E@PSB>
In-Reply-To: <20170705231101.E23E77D9B7A1@rock.dv.isc.org>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <20170705000229.5918D7D8457F@rock.dv.isc.org> <CACweHNCAi7JcOW9CX=6FViv1wUoe5fhn7deJ2eieP2-D_FhaSA@mail.gmail.com> <20170705031957.834B97D8FBDD@rock.dv.isc.org> <CACweHNCAmZPOUmat5ruh6qkYrECM2fh15n49P+zDcJ0gfoEGvg@mail.gmail.com> <765A15BF-8505-4470-9628-70CE9665BC16@gbiv.com> <20170705231101.E23E77D9B7A1@rock.dv.isc.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Uu01a55qXtBGHiQzQD6hCUQoev8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jul 2017 18:04:22 -0000

--On Thursday, July 6, 2017 09:11 +1000 Mark Andrews
<marka@isc.org> wrote:

>...
> And the actual presentation limit for LDH with DNS is 253
> (encodes as 255 octets on the wire).  Remember URI names do
> not have a final period and the each label has length octet
> when encoded as a DNS name and the name is terminated by the
> root label (0x00) in DNS wire form and the DNS wire name is
> limited to 255 octets.

Mark,

My apologies for nit-picking, but RFC 3986, Section 3.2.2 is
quite clear than DNS names in URIs are permitted to have a final
period and encouraged to do so under some circumstances.
Specifically,

	"The rightmost domain label of a fully qualified domain
	name in DNS may be followed by a single "." and should
	be if it is necessary to distinguish between the
	complete domain name and some local domain."

I don't think that changes the 253 octet limit, but the comment
about URIs is misleading and could contribute to an, IMO,
already high level of confusion about what RFC 3986 does or does
not specify.

The same subsection of RFC 3986 also uses the term "host
subcomponent" for what you are referring to as a name and allows
it to be a "registered name" (or <reg-name>) that might not be a
DNS name or reference at all -- whether it is or not is
scheme-dependent. 

best,
   john

  



From nobody Thu Jul  6 11:21:47 2017
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F35CF131660 for <ietf@ietfa.amsl.com>; Thu,  6 Jul 2017 11:21:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.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 jA5QEm2Y1aji for <ietf@ietfa.amsl.com>; Thu,  6 Jul 2017 11:21:44 -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 61C5C13189A for <ietf@ietf.org>; Thu,  6 Jul 2017 11:21:44 -0700 (PDT)
Received: from resomta-ch2-10v.sys.comcast.net ([69.252.207.106]) by resqmta-ch2-08v.sys.comcast.net with ESMTP id TBObdnBds2eJLTBPLdpS12; Thu, 06 Jul 2017 18:21:43 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1499365303; bh=LW0qZmctX9DLN3Hk1yx4+9Muo6VreNDkAcXGQW3uhVA=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=CzDwKWKpi2FxEKM/gQqOSRvxHSwSF8/UTLFI5r2rtqKPNKm+UowX/QRg4Nwul19Q4 HURXZCEgP83L+gH0EStY6R8Y5KvZaSPmQUPv97z1cQbvcoVSzD6t0KIraeLyNlKvQr RR1CwVKdIz1D8DQ3/qT2UqyV1ow30Jc5XQ5lfhhRZpYubOfyPTnzVKc4YqnOgPvkTf hNzLlv767kPUfngJ1JGdOZplmbljlNtzgp7gFMIhSk6k/v4a/9qCi6PlYUby+5sD/a zo7sTRyWkiBUd+8hgY2PtuDkVngPG7oYKEhFFknoxFeo8iDYxs0NbsyoXlD5FaAyhU WDGPdNn12dUTw==
Received: from [192.168.1.100] ([68.83.216.246]) by resomta-ch2-10v.sys.comcast.net with SMTP id TBPKdVXxJWNlvTBPLddLyP; Thu, 06 Jul 2017 18:21:43 +0000
Subject: Re: NomCom randomness results... delayed
To: ietf@ietf.org
References: <149935833402.2269.4238729858373783963.idtracker@ietfa.amsl.com>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <573cd826-66f3-46cf-e191-b58b367276f3@comcast.net>
Date: Thu, 6 Jul 2017 14:21:42 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <149935833402.2269.4238729858373783963.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-CMAE-Envelope: MS4wfMhsNGrw2b1AdTeJhaCNcTCnDGMGVjTKzoKfYwTxxPscjynsVR88wEd7aewpuvb+zoHol9lB6AYmev6dTGaLW8BR8smPyjyE+Ldy7846+Rn0h3PIeJiw 23kyadBCeVQjpxyCM0+T1KIB7/OMTdduVZIxTC1BRnjV1joGIsvTLeNV
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2NL6sZstJVOuy6nTKJI4XdXV7rw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jul 2017 18:21:46 -0000

On 7/6/2017 12:25 PM, NomCom Chair 2017 wrote:
> I had planned to pull the randomness results today, but there will be a slight delay.  While the EuroMillions and Powerball results are available (nothing like the lottery for being timely), the US debt numbers are still only showing the values for July 3rd.  The July 4th US holiday may have something to do with that, although I would have expected the July 5th numbers to be up by now.
>
> My plan for the moment is to examine the numbers tomorrow and see if the expected US debt data are available.  If so, I'll run with the published inputs.  If not, I'll have to use the latest available US debt numbers, which I will document in the randomness results announcement.  Please let me know if this plan causes any concerns.
>
> Peter Yee
> NomCom Chair 2017-18
> peter at akayla dot com
> nomcom-chair-2017 at ietf dot org
>
Hi Peter -

You should pick a new date and a new set of variables, and announce 
rather than mixing and matching data you (we) already know with 
something you would pick later.  That maintains the integrity of the 
process by keeping human choice out of the process.  I'd probably also 
provide a caveat for when the data isn't available (e.g. a substitute).

Mike



From nobody Thu Jul  6 11:41:04 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 82A611318F1; Thu,  6 Jul 2017 11:40:57 -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: urn@ietf.org, ietf@ietf.org, draft-ietf-urnbis-ns-reg-transition.all@ietf.org
Subject: Genart last call review of draft-ietf-urnbis-ns-reg-transition-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149936645745.2270.11265321386883433757@ietfa.amsl.com>
Date: Thu, 06 Jul 2017 11:40:57 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6mop511YMjtIQ86p80rTHJblKo0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jul 2017 18:40:57 -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-urnbis-ns-reg-transition-??
Reviewer: Joel Halpern
Review Date: 2017-07-06
IETF LC End Date: 2017-07-17
IESG Telechat date: Not scheduled for a telechat

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

Major issues: N/A

Minor issues: N/A

Nits/editorial comments: N/A 



From nobody Thu Jul  6 11:42:10 2017
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC74B131907; Thu,  6 Jul 2017 11:41:49 -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 AAoCW5e2phmT; Thu,  6 Jul 2017 11:41:48 -0700 (PDT)
Received: from mail-it0-x22d.google.com (mail-it0-x22d.google.com [IPv6:2607:f8b0:4001:c0b::22d]) (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 964D9131563; Thu,  6 Jul 2017 11:41:41 -0700 (PDT)
Received: by mail-it0-x22d.google.com with SMTP id m68so11141453ith.1; Thu, 06 Jul 2017 11:41:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=vRtuJcePOEWW6kXa0tAecDZaDz70NM6UNGGu90ass78=; b=MitmEtQIq9dib/ji7vAg0YX1eoTyg3TycwlEuPDRGApcMBRK007G251PnrTcs8KeRE iyfUmCDfSMM0JijHsv57c4CSKO8j8Z1vPcLOLTbP9KN3K620DTlE2ykbPJbx2jgMWt62 /G4apzpw/K474XhmAFTtjpKKQgGEEbb8QApN9rIRvtKATFX+Y1bLLJNlx50uOPbvPhLn ZfHi+OSZGdw9YOuIf5LBKDeweH+sdA0CnNTwnSp6yi7bNZ6PFBZ9QfZKP7X1YuhmhrZD O/x7fTvyz2LF5CZaSw3lJwh6/7VsXj58Gw8DIslmAK1L9B/QHbaWBw8I0Cgxb1Zx+t8d +tng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=vRtuJcePOEWW6kXa0tAecDZaDz70NM6UNGGu90ass78=; b=C1p62EYBduFHBoVBDClkIQaW5l61bS906XS7uj9WmLMcT5vGE6AB5YgUob4y1+eVK4 cJ1KeEjrO4Q5S5zmxOiQMR5763+ThxA978E+Cuw7GaeJcaUVIe+KMb7LymKSvrtdewUg MtUhG3l5I8Bn4UfX6xh7lgHN6XE9EyT7+QQtx/cPXe3PL77vn+0bQnIUtrjLxTzLctIG FZr9ceIJti2yOu59bkqZ4WChrdAFEx0TovBo1uAgu+zh14O0Q2y9TPa/swMziw5BbOXN s67gifBFj62QsbFiL8XpmLAAsDGzoxeE3cyT7jRx3+eL3HQBsREouOI+H4lU7Mg+b0xn HT3w==
X-Gm-Message-State: AKS2vOy1ixu7UaNOm+2kisyahX/rUJG9ps19cr0PZH2ZKB+H1YhhBQer NKWn5a/yWYQ0JAdl8iFWRu6BszI6/g==
X-Received: by 10.107.15.170 with SMTP id 42mr52248128iop.170.1499366500897; Thu, 06 Jul 2017 11:41:40 -0700 (PDT)
MIME-Version: 1.0
Sender: barryleiba@gmail.com
Received: by 10.107.173.26 with HTTP; Thu, 6 Jul 2017 11:41:40 -0700 (PDT)
In-Reply-To: <149936645745.2270.11265321386883433757@ietfa.amsl.com>
References: <149936645745.2270.11265321386883433757@ietfa.amsl.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 6 Jul 2017 20:41:40 +0200
X-Google-Sender-Auth: mbie3mbdv55GNfyHDQ7wa2F0JgY
Message-ID: <CALaySJKmX08cLM3H7YaPv6YnkHgbnUEXf2QxeZX8+k2ed35pxg@mail.gmail.com>
Subject: Re: Genart last call review of draft-ietf-urnbis-ns-reg-transition-08
To: Joel Halpern <jmh@joelhalpern.com>
Cc: General Area Review Team <gen-art@ietf.org>, "urn@ietf.org" <urn@ietf.org>, IETF discussion list <ietf@ietf.org>,  draft-ietf-urnbis-ns-reg-transition.all@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Hmvyn_rfiUmCQtX6PPCX-h37csk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jul 2017 18:41:50 -0000

Thanks for the review, Joel!

Barry

On Thu, Jul 6, 2017 at 8:40 PM, Joel Halpern <jmh@joelhalpern.com> wrote:
> 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-urnbis-ns-reg-transition-??
> Reviewer: Joel Halpern
> Review Date: 2017-07-06
> IETF LC End Date: 2017-07-17
> IESG Telechat date: Not scheduled for a telechat
>
> Summary: This document is ready for publication as a Proposed Standard RFC.
>
> Major issues: N/A
>
> Minor issues: N/A
>
> Nits/editorial comments: N/A
>
>



-- 
Barry
--
Barry Leiba  (barryleiba@computer.org)
http://internetmessagingtechnology.org/


From nobody Thu Jul  6 13:32:45 2017
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADACE12EC1E; Thu,  6 Jul 2017 13:32:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.921
X-Spam-Level: 
X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 oi6yI-s-76aQ; Thu,  6 Jul 2017 13:32:41 -0700 (PDT)
Received: from smtpde02.smtp.sap-ag.de (smtpde02.smtp.sap-ag.de [155.56.68.140]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90BBB126DC2; Thu,  6 Jul 2017 13:32:41 -0700 (PDT)
Received: from mail07.wdf.sap.corp (mail04.sap.corp [194.39.131.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtpde02.smtp.sap-ag.de (Postfix) with ESMTPS id 3x3TvC3hqHz25fP; Thu,  6 Jul 2017 22:32:39 +0200 (CEST)
X-purgate-ID: 152705::1499373159-00000810-56044B32/0/0
X-purgate-size: 2009
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate-type: clean
X-SAP-SPAM-Status: clean
Received: from ld9781.wdf.sap.corp (ld9781.wdf.sap.corp [10.21.82.193]) by mail07.wdf.sap.corp (Postfix) with ESMTP id 3x3TvB1MtmzGnsf; Thu,  6 Jul 2017 22:32:38 +0200 (CEST)
Received: by ld9781.wdf.sap.corp (Postfix, from userid 10159) id 1F32D1A6C7; Thu,  6 Jul 2017 22:32:38 +0200 (CEST)
Subject: Re: [DNSOP] Minor editorial change to draft-ietf-dnsop-sutld-ps
In-Reply-To: <901C29488D8446E4176CF83E@PSB>
To: John C Klensin <john-ietf@jck.com>
Date: Thu, 6 Jul 2017 22:32:38 +0200 (CEST)
CC: Mark Andrews <marka@isc.org>, "Roy T. Fielding" <fielding@gbiv.com>,  dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
Reply-To: mrex@sap.com
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20170706203238.1F32D1A6C7@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9wetUlhDcKbUVX36UUV3Chqvy88>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jul 2017 20:32:43 -0000

John C Klensin wrote:
> 
> --On Thursday, July 6, 2017 09:11 +1000 Mark Andrews
> <marka@isc.org> wrote:
> 
>>...
>> And the actual presentation limit for LDH with DNS is 253
>> (encodes as 255 octets on the wire).  Remember URI names do
>> not have a final period and the each label has length octet
>> when encoded as a DNS name and the name is terminated by the
>> root label (0x00) in DNS wire form and the DNS wire name is
>> limited to 255 octets.
> 
> My apologies for nit-picking, but RFC 3986, Section 3.2.2 is
> quite clear than DNS names in URIs are permitted to have a final
> period and encouraged to do so under some circumstances.
> Specifically,
> 
> 	"The rightmost domain label of a fully qualified domain
> 	name in DNS may be followed by a single "." and should
> 	be if it is necessary to distinguish between the
> 	complete domain name and some local domain."


Also apologies from my side for nitpicking.

While I do believe that final periods on DNS names in URLs should work,
they still seem somewhat unusual, and there is a varing amount of breakage
around _matching_ DNS names with a final period to names without one
in various areas of communication protocols.

example: rfc2818 section 3.1 server endpoint identification
While _recent_ versions of Firefox & Chrome seem to no longer fail to
match them to TLS server certs, users of the blue stuff from Redmond
seem to be less lucky and still face cert hostname mismatch errors.

(but Google Chrome started delibertatly violating a MUST requirement from
 rfc2818 3.1 for certs without SANs, so name matching in Chrome _is_ broken,
 just differently broken).

There are other places where the DNS names from URLs will be placed,
e.g. TLS extension SNI client-side, TLS extension SNI server-side (virtual
hosts), HTTP Host: header fields, Cookies?, Same-origin-policies?

and I would not be surprised about more failures comparing DNS names
where one carries a final period.

-Martin


From nobody Thu Jul  6 13:45:24 2017
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A62B1131882 for <ietf@ietfa.amsl.com>; Thu,  6 Jul 2017 13:45:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 fKkJ22t-zpYn for <ietf@ietfa.amsl.com>; Thu,  6 Jul 2017 13:45:21 -0700 (PDT)
Received: from mail-wr0-x230.google.com (mail-wr0-x230.google.com [IPv6:2a00:1450:400c:c0c::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 4FFB6131563 for <ietf@ietf.org>; Thu,  6 Jul 2017 13:45:21 -0700 (PDT)
Received: by mail-wr0-x230.google.com with SMTP id 77so19040360wrb.1 for <ietf@ietf.org>; Thu, 06 Jul 2017 13:45:21 -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=P8fkAIxSUY/BqFh1hnAyUC7AdhOOeUMIPkF50UZPsVo=; b=pVKSTTAbpcqIiU0uLCsTB04gJ444Fm5TD8Flj5zVmh9x8hjf9EOK5jkz6lxdFjWmd0 nSvnLrLvbweOE8dVrR1zX6FciyShXVSC+3XKFaNhzVZPJ7//oTZqT4S9mdtGsiwIXZ8z DmAZVrrInJr53cq7xCI4vSevK3oIOpcP9fI9nIGlSyB2yMdh7qfjPeBRbn6kzWiPaPdZ 5atmao20++BgS0sRMb5HZn1kjJEm6H/yntKfOkO1Y///3hlxroFURPgthkVZSOof/uT2 EBLDU9sY24wOigeAOtWWjt62T09GJSudCBmHyb5+RBI3nFnfN7No2Vc80bdBHy4MV+lI po5Q==
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=P8fkAIxSUY/BqFh1hnAyUC7AdhOOeUMIPkF50UZPsVo=; b=WWehYc9fOjj+vk265/iFjhPOXSdFcjG3pdY5WhxQ0DUpwIPR6yTWQGtgxyY5f+QV1n KdbmpPQKBgStHcQTFpp0BJIpTD7FvBRm/+7U8LlpJgvZw2Jl567ap+sHX08+qbN3Ombp xjfk5yyelTBYUOIqS5PjS7cNpTMnuk0uAcnwohGqAoRGxZsJkFhnnFNrzGdxsVwZzdoO f2m64DQRDlO+tVvmyXstEOzDtVXfGKFRABQg7ifOloSweiRUsC/XOQj7+T6D4wMyvV/h 3XyxhRTN/FsUwnDZZDEvkSjXaVmyQ7VGxmDtJBxVWyai5/O0K8HXpZDk+KRqZMtoyC7Q N87Q==
X-Gm-Message-State: AKS2vOzuSnoB6lPQSyA2DW/l6Ti8NUjSY3wYBpVx27OV16228Ik/w9IK IGSZv736ftpzuCp6mq0C659UQTXu0A==
X-Received: by 10.223.176.119 with SMTP id g52mr43907445wra.26.1499373919904;  Thu, 06 Jul 2017 13:45:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.138.207 with HTTP; Thu, 6 Jul 2017 13:45:19 -0700 (PDT)
Reply-To: sarikaya@ieee.org
In-Reply-To: <573cd826-66f3-46cf-e191-b58b367276f3@comcast.net>
References: <149935833402.2269.4238729858373783963.idtracker@ietfa.amsl.com> <573cd826-66f3-46cf-e191-b58b367276f3@comcast.net>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Thu, 6 Jul 2017 15:45:19 -0500
Message-ID: <CAC8QAcf5f9BrZVfdReGN9_bmgK8Z5gn=+5frw-vUZVS9khpaWw@mail.gmail.com>
Subject: Re: NomCom randomness results... delayed
To: Michael StJohns <mstjohns@comcast.net>
Cc: IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a113cae76e1a84d0553ac3139"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AnnNQK9YEIHdTQk5P7JYCmtKZHE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jul 2017 20:45:23 -0000

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

Hi all,

Regarding the list of volunteers, I had checked the box for volunteering
for Nomcom when I registered for IETF 99 with payment,despite that my name
is not in the list.

What makes?

Regards,

Behcet

On Thu, Jul 6, 2017 at 1:21 PM, Michael StJohns <mstjohns@comcast.net>
wrote:

> On 7/6/2017 12:25 PM, NomCom Chair 2017 wrote:
>
>> I had planned to pull the randomness results today, but there will be a
>> slight delay.  While the EuroMillions and Powerball results are available
>> (nothing like the lottery for being timely), the US debt numbers are still
>> only showing the values for July 3rd.  The July 4th US holiday may have
>> something to do with that, although I would have expected the July 5th
>> numbers to be up by now.
>>
>> My plan for the moment is to examine the numbers tomorrow and see if the
>> expected US debt data are available.  If so, I'll run with the published
>> inputs.  If not, I'll have to use the latest available US debt numbers,
>> which I will document in the randomness results announcement.  Please let
>> me know if this plan causes any concerns.
>>
>> Peter Yee
>> NomCom Chair 2017-18
>> peter at akayla dot com
>> nomcom-chair-2017 at ietf dot org
>>
>> Hi Peter -
>
> You should pick a new date and a new set of variables, and announce rather
> than mixing and matching data you (we) already know with something you
> would pick later.  That maintains the integrity of the process by keeping
> human choice out of the process.  I'd probably also provide a caveat for
> when the data isn't available (e.g. a substitute).
>
> Mike
>
>
>

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

<div dir=3D"ltr"><div><div><div><div>Hi all,<br><br></div>Regarding the lis=
t of volunteers, I had checked the box for volunteering for Nomcom when I r=
egistered for IETF 99 with payment,despite that my name is not in the list.=
<br><br></div>What makes?<br><br></div>Regards,<br><br></div>Behcet<br></di=
v><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Jul 6, =
2017 at 1:21 PM, Michael StJohns <span dir=3D"ltr">&lt;<a href=3D"mailto:ms=
tjohns@comcast.net" target=3D"_blank">mstjohns@comcast.net</a>&gt;</span> w=
rote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">On 7/6/2017 12:25 PM, NomCom Chair =
2017 wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I had planned to pull the randomness results today, but there will be a sli=
ght delay.=C2=A0 While the EuroMillions and Powerball results are available=
 (nothing like the lottery for being timely), the US debt numbers are still=
 only showing the values for July 3rd.=C2=A0 The July 4th US holiday may ha=
ve something to do with that, although I would have expected the July 5th n=
umbers to be up by now.<br>
<br>
My plan for the moment is to examine the numbers tomorrow and see if the ex=
pected US debt data are available.=C2=A0 If so, I&#39;ll run with the publi=
shed inputs.=C2=A0 If not, I&#39;ll have to use the latest available US deb=
t numbers, which I will document in the randomness results announcement.=C2=
=A0 Please let me know if this plan causes any concerns.<br>
<br>
Peter Yee<br>
NomCom Chair 2017-18<br>
peter at akayla dot com<br>
nomcom-chair-2017 at ietf dot org<br>
<br>
</blockquote>
Hi Peter -<br>
<br>
You should pick a new date and a new set of variables, and announce rather =
than mixing and matching data you (we) already know with something you woul=
d pick later.=C2=A0 That maintains the integrity of the process by keeping =
human choice out of the process.=C2=A0 I&#39;d probably also provide a cave=
at for when the data isn&#39;t available (e.g. a substitute).<br>
<br>
Mike<br>
<br>
<br>
</blockquote></div><br></div>

--001a113cae76e1a84d0553ac3139--


From nobody Thu Jul  6 14:00:47 2017
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1A621317D2 for <ietf@ietfa.amsl.com>; Thu,  6 Jul 2017 14:00:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 IYSy-xh0VGYD for <ietf@ietfa.amsl.com>; Thu,  6 Jul 2017 14:00:43 -0700 (PDT)
Received: from p3plsmtpa12-07.prod.phx3.secureserver.net (p3plsmtpa12-07.prod.phx3.secureserver.net [68.178.252.236]) (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 5ACD912EA58 for <ietf@ietf.org>; Thu,  6 Jul 2017 14:00:43 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by :SMTPAUTH: with SMTP id TDsiddi9pKEkdTDsidmRHm; Thu, 06 Jul 2017 14:00:12 -0700
From: "Peter Yee" <peter@akayla.com>
To: <sarikaya@ieee.org>
Cc: "'IETF'" <ietf@ietf.org>
References: <149935833402.2269.4238729858373783963.idtracker@ietfa.amsl.com> <573cd826-66f3-46cf-e191-b58b367276f3@comcast.net> <CAC8QAcf5f9BrZVfdReGN9_bmgK8Z5gn=+5frw-vUZVS9khpaWw@mail.gmail.com>
In-Reply-To: <CAC8QAcf5f9BrZVfdReGN9_bmgK8Z5gn=+5frw-vUZVS9khpaWw@mail.gmail.com>
Subject: RE: NomCom randomness results... delayed
Date: Thu, 6 Jul 2017 14:00:27 -0700
Message-ID: <06e701d2f69a$e5adba10$b1092e30$@akayla.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_06E8_01D2F660.394FA560"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQCRV8v0HLk1D/UMEjSCPMhQV2WhEQKBWb7oAfPOvq+kptxD0A==
Content-Language: en-us
X-CMAE-Envelope: MS4wfLTga0W7yaiz6vJIehew38Mj8S8VgFs4WZkKGSNJzUISqGK68RvmlsbZbzJDx06Pg9D4w7n5VfOCYWkpiTsPwkAB4OfLDZbOZltpnyh9JYNOnuy4f8Sl fpYW66LLN57kPXlXWKw33reU3kz0T7eEmOqXi1nGx3lNFMvyQERYjJwo
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/02ZXdYSpv155kfGtG5JcwqDs3OA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jul 2017 21:00:46 -0000

This is a multipart message in MIME format.

------=_NextPart_000_06E8_01D2F660.394FA560
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

For the 2017-2018 NomCom, you would have needed to check the box for =
registration for any of IETF 96-98 (Berlin, Seoul, and Chicago).  Your =
checking the box on the IETF 99 registration form will put you on the =
list of the 2018-2019 NomCom, assuming you are eligible.

=20

                -Peter

=20

From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Behcet Sarikaya
Sent: Thursday, July 06, 2017 1:45 PM
To: Michael StJohns
Cc: IETF
Subject: Re: NomCom randomness results... delayed

=20

Hi all,

Regarding the list of volunteers, I had checked the box for volunteering =
for Nomcom when I registered for IETF 99 with payment,despite that my =
name is not in the list.

What makes?

Regards,

Behcet

=20

On Thu, Jul 6, 2017 at 1:21 PM, Michael StJohns <mstjohns@comcast.net> =
wrote:

On 7/6/2017 12:25 PM, NomCom Chair 2017 wrote:

I had planned to pull the randomness results today, but there will be a =
slight delay.  While the EuroMillions and Powerball results are =
available (nothing like the lottery for being timely), the US debt =
numbers are still only showing the values for July 3rd.  The July 4th US =
holiday may have something to do with that, although I would have =
expected the July 5th numbers to be up by now.

My plan for the moment is to examine the numbers tomorrow and see if the =
expected US debt data are available.  If so, I'll run with the published =
inputs.  If not, I'll have to use the latest available US debt numbers, =
which I will document in the randomness results announcement.  Please =
let me know if this plan causes any concerns.

Peter Yee
NomCom Chair 2017-18
peter at akayla dot com
nomcom-chair-2017 at ietf dot org

Hi Peter -

You should pick a new date and a new set of variables, and announce =
rather than mixing and matching data you (we) already know with =
something you would pick later.  That maintains the integrity of the =
process by keeping human choice out of the process.  I'd probably also =
provide a caveat for when the data isn't available (e.g. a substitute).

Mike



=20


------=_NextPart_000_06E8_01D2F660.394FA560
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=3DGenerator content=3D"Microsoft Word 14 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	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;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.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=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>For the 2017-2018 NomCom, you would have needed to check the box for =
registration for any of IETF 96-98 (Berlin, Seoul, and Chicago).=C2=A0 =
Your checking the box on the IETF 99 registration form will put you on =
the list of the 2018-2019 NomCom, assuming you are =
eligible.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>=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 -Peter<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
ietf [mailto:ietf-bounces@ietf.org] <b>On Behalf Of </b>Behcet =
Sarikaya<br><b>Sent:</b> Thursday, July 06, 2017 1:45 PM<br><b>To:</b> =
Michael StJohns<br><b>Cc:</b> IETF<br><b>Subject:</b> Re: NomCom =
randomness results... delayed<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><div><div><div><p =
class=3DMsoNormal style=3D'margin-bottom:12.0pt'>Hi =
all,<o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>Regarding the list of volunteers, I had =
checked the box for volunteering for Nomcom when I registered for IETF =
99 with payment,despite that my name is not in the =
list.<o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>What makes?<o:p></o:p></p></div><p =
class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>Regards,<o:p></o:p></p></div><p =
class=3DMsoNormal>Behcet<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>On Thu, =
Jul 6, 2017 at 1:21 PM, Michael StJohns &lt;<a =
href=3D"mailto:mstjohns@comcast.net" =
target=3D"_blank">mstjohns@comcast.net</a>&gt; wrote:<o:p></o:p></p><p =
class=3DMsoNormal>On 7/6/2017 12:25 PM, NomCom Chair 2017 =
wrote:<o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>I had planned to pull the randomness =
results today, but there will be a slight delay.&nbsp; While the =
EuroMillions and Powerball results are available (nothing like the =
lottery for being timely), the US debt numbers are still only showing =
the values for July 3rd.&nbsp; The July 4th US holiday may have =
something to do with that, although I would have expected the July 5th =
numbers to be up by now.<br><br>My plan for the moment is to examine the =
numbers tomorrow and see if the expected US debt data are =
available.&nbsp; If so, I'll run with the published inputs.&nbsp; If =
not, I'll have to use the latest available US debt numbers, which I will =
document in the randomness results announcement.&nbsp; Please let me =
know if this plan causes any concerns.<br><br>Peter Yee<br>NomCom Chair =
2017-18<br>peter at akayla dot com<br>nomcom-chair-2017 at ietf dot =
org<o:p></o:p></p><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>Hi =
Peter -<br><br>You should pick a new date and a new set of variables, =
and announce rather than mixing and matching data you (we) already know =
with something you would pick later.&nbsp; That maintains the integrity =
of the process by keeping human choice out of the process.&nbsp; I'd =
probably also provide a caveat for when the data isn't available (e.g. a =
substitute).<br><br>Mike<br><br><o:p></o:p></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_06E8_01D2F660.394FA560--


From nobody Thu Jul  6 14:10:43 2017
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76B3613168B for <ietf@ietfa.amsl.com>; Thu,  6 Jul 2017 14:10:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 o3pa1J8OCrf7 for <ietf@ietfa.amsl.com>; Thu,  6 Jul 2017 14:10:39 -0700 (PDT)
Received: from mail-wr0-x234.google.com (mail-wr0-x234.google.com [IPv6:2a00:1450:400c:c0c::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 96939131553 for <ietf@ietf.org>; Thu,  6 Jul 2017 14:10:38 -0700 (PDT)
Received: by mail-wr0-x234.google.com with SMTP id 77so19884062wrb.1 for <ietf@ietf.org>; Thu, 06 Jul 2017 14:10:38 -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=ZdvEzs2c3D0hDvuwjHsYahaBgm8vF7t584eeKfKhHCA=; b=FEVV5oBwgNCf0GngWUV8QQDWyPCfKAjzUSXFixvF2BJCbe5sVK70GHp5TB4cxKOHgz 0UA6AahidAcVv9/Pul5NCl2pJZTIVWsM9wN382KP4O+rtHbvJRaV8k90B3aBuYQRfYn4 YCr2yryGfzMen0J0usPqJ7sX46kq+3fKN1bVPr1cLzcahwXjVm9ujzmZ2a11NfQNY5L3 naaFAZg4Bi2yn+gOh7sk54oB2o7SCd3aqJQlLrTvJCg0cHh/Prkbq35ip+BvldrutfS8 3Scb3bjFJiQfFlBUGmc0RqjepqExo+fBSBMGn8x6WYemAH+5QFnJCv/JxnfPzqZsCcsS r68Q==
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=ZdvEzs2c3D0hDvuwjHsYahaBgm8vF7t584eeKfKhHCA=; b=YwxdyyllglrKdkKBbUyE4eZBwoLfT+epm8Dm0YhKLGg2xIZlgAo8jF0UYYui50buHT VZ4hSKAbs5w/QMXMHrdpOFDlRJ5sO2sX5J1enSiehzg1B5jqSaxjRl/uPFuaQuNttQxG GrFrB4Xka+YtEQh565OTE/oR2xiUwiA3dmGX4nAe3sKhJaiC6bBoJ4S1cjLwBD7q76jT nNdJdBpN2j6edM+5k7lWqU83/mDihL7GSTVJtJ1/wUvJqTCjzpxOmeXbLGDpmbh4tQdK FHJjYcyfOgpiu/FCPQfX4c7ErUH0YkKplrT7wmSLCdCdVgUNnsEjqn60mdMJsBXrRNHH MA6A==
X-Gm-Message-State: AKS2vOzL2qt1ixrKoVTW/QB/8pa+7+H9LixRxEk+G8Be42GgiYo7Nnq5 dXAiu4OnFhTXqRqFoRKvO4aWMeNPbtSE
X-Received: by 10.223.171.3 with SMTP id q3mr41442813wrc.12.1499375437168; Thu, 06 Jul 2017 14:10:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.138.207 with HTTP; Thu, 6 Jul 2017 14:10:36 -0700 (PDT)
Reply-To: sarikaya@ieee.org
In-Reply-To: <06e701d2f69a$e5adba10$b1092e30$@akayla.com>
References: <149935833402.2269.4238729858373783963.idtracker@ietfa.amsl.com> <573cd826-66f3-46cf-e191-b58b367276f3@comcast.net> <CAC8QAcf5f9BrZVfdReGN9_bmgK8Z5gn=+5frw-vUZVS9khpaWw@mail.gmail.com> <06e701d2f69a$e5adba10$b1092e30$@akayla.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Thu, 6 Jul 2017 16:10:36 -0500
Message-ID: <CAC8QAccB+GQAPTjgT=yepz-o76Q9Mv6AxMPDdwvcWTtVpD6v=A@mail.gmail.com>
Subject: Re: NomCom randomness results... delayed
To: Peter Yee <peter@akayla.com>
Cc: IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c1b440a5148a00553ac8c08"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OsPLe-NuUhLyhryr0yEY_Mmblm4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jul 2017 21:10:40 -0000

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

Hi Peter,


On Thu, Jul 6, 2017 at 4:00 PM, Peter Yee <peter@akayla.com> wrote:

> For the 2017-2018 NomCom, you would have needed to check the box for
> registration for any of IETF 96-98 (Berlin, Seoul, and Chicago).  Your
> checking the box on the IETF 99 registration form will put you on the list
> of the 2018-2019 NomCom, assuming you are eligible.
>
>
>

Thanks. This was not what I understood when I checked the box. Maybe it
should be made clearer in the future forms.
This is the question in the form:

Are you willing to volunteer for the Nomcom?


Behcet

>                 -Peter
>
>
>
> *From:* ietf [mailto:ietf-bounces@ietf.org] *On Behalf Of *Behcet Sarikaya
> *Sent:* Thursday, July 06, 2017 1:45 PM
> *To:* Michael StJohns
> *Cc:* IETF
> *Subject:* Re: NomCom randomness results... delayed
>
>
>
> Hi all,
>
> Regarding the list of volunteers, I had checked the box for volunteering
> for Nomcom when I registered for IETF 99 with payment,despite that my name
> is not in the list.
>
> What makes?
>
> Regards,
>
> Behcet
>
>
>
> On Thu, Jul 6, 2017 at 1:21 PM, Michael StJohns <mstjohns@comcast.net>
> wrote:
>
> On 7/6/2017 12:25 PM, NomCom Chair 2017 wrote:
>
> I had planned to pull the randomness results today, but there will be a
> slight delay.  While the EuroMillions and Powerball results are available
> (nothing like the lottery for being timely), the US debt numbers are still
> only showing the values for July 3rd.  The July 4th US holiday may have
> something to do with that, although I would have expected the July 5th
> numbers to be up by now.
>
> My plan for the moment is to examine the numbers tomorrow and see if the
> expected US debt data are available.  If so, I'll run with the published
> inputs.  If not, I'll have to use the latest available US debt numbers,
> which I will document in the randomness results announcement.  Please let
> me know if this plan causes any concerns.
>
> Peter Yee
> NomCom Chair 2017-18
> peter at akayla dot com
> nomcom-chair-2017 at ietf dot org
>
> Hi Peter -
>
> You should pick a new date and a new set of variables, and announce rather
> than mixing and matching data you (we) already know with something you
> would pick later.  That maintains the integrity of the process by keeping
> human choice out of the process.  I'd probably also provide a caveat for
> when the data isn't available (e.g. a substitute).
>
> Mike
>
>
>

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

<div dir=3D"ltr">Hi Peter,<br><br><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Thu, Jul 6, 2017 at 4:00 PM, Peter Yee <span dir=3D"ltr=
">&lt;<a href=3D"mailto:peter@akayla.com" target=3D"_blank">peter@akayla.co=
m</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
"><div lang=3D"EN-US"><div class=3D"gmail-m_-8985875076160390948WordSection=
1"><p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:rgb(31,73,125)">For the 2017-2018=
 NomCom, you would have needed to check the box for registration for any of=
 IETF 96-98 (Berlin, Seoul, and Chicago).=C2=A0 Your checking the box on th=
e IETF 99 registration form will put you on the list of the 2018-2019 NomCo=
m, assuming you are eligible.<u></u><u></u></span></p><p class=3D"MsoNormal=
"><span style=3D"font-size:11pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:rgb(31,73,125)"><u></u>=C2=A0</span></p></div></div></blo=
ckquote><div><br></div><div>Thanks. This was not what I understood when I c=
hecked the box. Maybe it should be made clearer in the future forms.<br></d=
iv><div>This is the question in the form:<br><br><span style=3D"color:rgb(3=
8,68,91);font-family:Arial;font-size:13.3333px;font-style:normal;font-varia=
nt-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spac=
ing:normal;text-align:left;text-indent:0px;text-transform:none;white-space:=
normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-s=
tyle:initial;text-decoration-color:initial;display:inline;float:none">Are y=
ou willing to volunteer for the Nomcom?<br><br><br></span></div><div><span =
style=3D"color:rgb(38,68,91);font-family:Arial;font-size:13.3333px;font-sty=
le:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weigh=
t:normal;letter-spacing:normal;text-align:left;text-indent:0px;text-transfo=
rm:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,25=
5);text-decoration-style:initial;text-decoration-color:initial;display:inli=
ne;float:none">Behcet</span> <br></div><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"><div lang=3D"EN-US"><div class=3D"gmail-m_-898587507616039094=
8WordSection1"><p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-fa=
mily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:rgb(31,73,125)"><u></=
u></span></p><p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-fami=
ly:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:rgb(31,73,125)">=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 -Peter<u></u><u></u></span></p><p class=3D"MsoNormal"><span style=
=3D"font-size:11pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;c=
olor:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p><p class=3D"MsoNormal">=
<b><span style=3D"font-size:10pt;font-family:&quot;Tahoma&quot;,&quot;sans-=
serif&quot;">From:</span></b><span style=3D"font-size:10pt;font-family:&quo=
t;Tahoma&quot;,&quot;sans-serif&quot;"> ietf [mailto:<a href=3D"mailto:ietf=
-bounces@ietf.org" target=3D"_blank">ietf-bounces@ietf.org</a>] <b>On Behal=
f Of </b>Behcet Sarikaya<br><b>Sent:</b> Thursday, July 06, 2017 1:45 PM<br=
><b>To:</b> Michael StJohns<br><b>Cc:</b> IETF<br><b>Subject:</b> Re: NomCo=
m randomness results... delayed<u></u><u></u></span></p><div><div class=3D"=
gmail-h5"><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><div><div><div><di=
v><div><p class=3D"MsoNormal" style=3D"margin-bottom:12pt">Hi all,<u></u><u=
></u></p></div><p class=3D"MsoNormal" style=3D"margin-bottom:12pt">Regardin=
g the list of volunteers, I had checked the box for volunteering for Nomcom=
 when I registered for IETF 99 with payment,despite that my name is not in =
the list.<u></u><u></u></p></div><p class=3D"MsoNormal" style=3D"margin-bot=
tom:12pt">What makes?<u></u><u></u></p></div><p class=3D"MsoNormal" style=
=3D"margin-bottom:12pt">Regards,<u></u><u></u></p></div><p class=3D"MsoNorm=
al">Behcet<u></u><u></u></p></div><div><p class=3D"MsoNormal"><u></u>=C2=A0=
<u></u></p><div><p class=3D"MsoNormal">On Thu, Jul 6, 2017 at 1:21 PM, Mich=
ael StJohns &lt;<a href=3D"mailto:mstjohns@comcast.net" target=3D"_blank">m=
stjohns@comcast.net</a>&gt; wrote:<u></u><u></u></p><p class=3D"MsoNormal">=
On 7/6/2017 12:25 PM, NomCom Chair 2017 wrote:<u></u><u></u></p><p class=3D=
"MsoNormal" style=3D"margin-bottom:12pt">I had planned to pull the randomne=
ss results today, but there will be a slight delay.=C2=A0 While the EuroMil=
lions and Powerball results are available (nothing like the lottery for bei=
ng timely), the US debt numbers are still only showing the values for July =
3rd.=C2=A0 The July 4th US holiday may have something to do with that, alth=
ough I would have expected the July 5th numbers to be up by now.<br><br>My =
plan for the moment is to examine the numbers tomorrow and see if the expec=
ted US debt data are available.=C2=A0 If so, I&#39;ll run with the publishe=
d inputs.=C2=A0 If not, I&#39;ll have to use the latest available US debt n=
umbers, which I will document in the randomness results announcement.=C2=A0=
 Please let me know if this plan causes any concerns.<br><br>Peter Yee<br>N=
omCom Chair 2017-18<br>peter at akayla dot com<br>nomcom-chair-2017 at ietf=
 dot org<u></u><u></u></p><p class=3D"MsoNormal" style=3D"margin-bottom:12p=
t">Hi Peter -<br><br>You should pick a new date and a new set of variables,=
 and announce rather than mixing and matching data you (we) already know wi=
th something you would pick later.=C2=A0 That maintains the integrity of th=
e process by keeping human choice out of the process.=C2=A0 I&#39;d probabl=
y also provide a caveat for when the data isn&#39;t available (e.g. a subst=
itute).<br><br>Mike<br><br><u></u><u></u></p></div><p class=3D"MsoNormal"><=
u></u>=C2=A0<u></u></p></div></div></div></div></div></blockquote></div><br=
></div></div>

--94eb2c1b440a5148a00553ac8c08--


From nobody Thu Jul  6 14:17:26 2017
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52BD9131575 for <ietf@ietfa.amsl.com>; Thu,  6 Jul 2017 14:17:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 JiTgO_s0C-85 for <ietf@ietfa.amsl.com>; Thu,  6 Jul 2017 14:17:23 -0700 (PDT)
Received: from p3plsmtpa07-10.prod.phx3.secureserver.net (p3plsmtpa07-10.prod.phx3.secureserver.net [173.201.192.239]) (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 475D412EC2B for <ietf@ietf.org>; Thu,  6 Jul 2017 14:17:23 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by :SMTPAUTH: with SMTP id TE8pdyB2s7W3yTE8pdlFQs; Thu, 06 Jul 2017 14:16:52 -0700
From: "Peter Yee" <peter@akayla.com>
To: <sarikaya@ieee.org>
Cc: "'IETF'" <ietf@ietf.org>
References: <149935833402.2269.4238729858373783963.idtracker@ietfa.amsl.com> <573cd826-66f3-46cf-e191-b58b367276f3@comcast.net> <CAC8QAcf5f9BrZVfdReGN9_bmgK8Z5gn=+5frw-vUZVS9khpaWw@mail.gmail.com> <06e701d2f69a$e5adba10$b1092e30$@akayla.com> <CAC8QAccB+GQAPTjgT=yepz-o76Q9Mv6AxMPDdwvcWTtVpD6v=A@mail.gmail.com>
In-Reply-To: <CAC8QAccB+GQAPTjgT=yepz-o76Q9Mv6AxMPDdwvcWTtVpD6v=A@mail.gmail.com>
Subject: RE: NomCom randomness results... delayed
Date: Thu, 6 Jul 2017 14:17:06 -0700
Message-ID: <06ff01d2f69d$392af2a0$ab80d7e0$@akayla.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0700_01D2F662.8CCD5320"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQCRV8v0HLk1D/UMEjSCPMhQV2WhEQKBWb7oAfPOvq8CNqyKHALT93KjpH6LeaA=
Content-Language: en-us
X-CMAE-Envelope: MS4wfI0LA262O+IEHMM6Fhp8/7/82ewuy7fNKstdrlcgivspCGL2DHIwSD3dkiS1yQBjvbIyeXHwrLnVyDq9JSHDkxclN9GCPEi9TXjnk73fRqOqxf5gq05E lQ8x6yc3boatK2S6fKP3tjBaYw9OreoVj0A413ukbWMpGpxlWnXq/XT1
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gg73tLYfeJW0C7Kbt0OyQ-VhNyo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jul 2017 21:17:25 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0700_01D2F662.8CCD5320
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Behcet,

=20

                You=E2=80=99re right, it=E2=80=99s ambiguous as to which =
NomCom you=E2=80=99re volunteering for during registration for the July =
meetings.  I=E2=80=99ll ask AMS if there=E2=80=99s something we can do =
to make it clearer for future registrations.

=20

                Alternatively, to volunteer for the 2017-2018 NomCom, =
you could have sent me an email during the call for volunteers.  Of =
course, that would be predicated on your knowing that the 2017-2018 =
NomCom was not covered by the IETF 99 registration.  We=E2=80=99ll try =
to do better in the future.

=20

                                -Peter

=20

From: Behcet Sarikaya [mailto:sarikaya2012@gmail.com]=20
Sent: Thursday, July 06, 2017 2:11 PM
To: Peter Yee
Cc: IETF
Subject: Re: NomCom randomness results... delayed

=20

Hi Peter,

=20

On Thu, Jul 6, 2017 at 4:00 PM, Peter Yee <peter@akayla.com> wrote:

For the 2017-2018 NomCom, you would have needed to check the box for =
registration for any of IETF 96-98 (Berlin, Seoul, and Chicago).  Your =
checking the box on the IETF 99 registration form will put you on the =
list of the 2018-2019 NomCom, assuming you are eligible.

=20

=20

Thanks. This was not what I understood when I checked the box. Maybe it =
should be made clearer in the future forms.

This is the question in the form:

Are you willing to volunteer for the Nomcom?



Behcet=20

                -Peter

=20

From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Behcet Sarikaya
Sent: Thursday, July 06, 2017 1:45 PM
To: Michael StJohns
Cc: IETF
Subject: Re: NomCom randomness results... delayed

=20

Hi all,

Regarding the list of volunteers, I had checked the box for volunteering =
for Nomcom when I registered for IETF 99 with payment,despite that my =
name is not in the list.

What makes?

Regards,

Behcet

=20

On Thu, Jul 6, 2017 at 1:21 PM, Michael StJohns <mstjohns@comcast.net> =
wrote:

On 7/6/2017 12:25 PM, NomCom Chair 2017 wrote:

I had planned to pull the randomness results today, but there will be a =
slight delay.  While the EuroMillions and Powerball results are =
available (nothing like the lottery for being timely), the US debt =
numbers are still only showing the values for July 3rd.  The July 4th US =
holiday may have something to do with that, although I would have =
expected the July 5th numbers to be up by now.

My plan for the moment is to examine the numbers tomorrow and see if the =
expected US debt data are available.  If so, I'll run with the published =
inputs.  If not, I'll have to use the latest available US debt numbers, =
which I will document in the randomness results announcement.  Please =
let me know if this plan causes any concerns.

Peter Yee
NomCom Chair 2017-18
peter at akayla dot com
nomcom-chair-2017 at ietf dot org

Hi Peter -

You should pick a new date and a new set of variables, and announce =
rather than mixing and matching data you (we) already know with =
something you would pick later.  That maintains the integrity of the =
process by keeping human choice out of the process.  I'd probably also =
provide a caveat for when the data isn't available (e.g. a substitute).

Mike

=20

=20


------=_NextPart_000_0700_01D2F662.8CCD5320
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=3DGenerator content=3D"Microsoft Word 14 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.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=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Behcet,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>=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 You=E2=80=99re right, it=E2=80=99s ambiguous as to =
which NomCom you=E2=80=99re volunteering for during registration for the =
July meetings.=C2=A0 I=E2=80=99ll ask AMS if there=E2=80=99s something =
we can do to make it clearer for future =
registrations.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>=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 Alternatively, to volunteer for the 2017-2018 NomCom, =
you could have sent me an email during the call for volunteers.=C2=A0 Of =
course, that would be predicated on your knowing that the 2017-2018 =
NomCom was not covered by the IETF 99 registration.=C2=A0 We=E2=80=99ll =
try to do better in the future.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>=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=C2=A0=C2=A0=C2=A0=C2=A0 -Peter<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Behcet Sarikaya [mailto:sarikaya2012@gmail.com] <br><b>Sent:</b> =
Thursday, July 06, 2017 2:11 PM<br><b>To:</b> Peter Yee<br><b>Cc:</b> =
IETF<br><b>Subject:</b> Re: NomCom randomness results... =
delayed<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>Hi Peter,<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>On Thu, =
Jul 6, 2017 at 4:00 PM, Peter Yee &lt;<a =
href=3D"mailto:peter@akayla.com" =
target=3D"_blank">peter@akayla.com</a>&gt; =
wrote:<o:p></o:p></p><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>For the 2017-2018 NomCom, you would have needed to check the box for =
registration for any of IETF 96-98 (Berlin, Seoul, and Chicago).&nbsp; =
Your checking the box on the IETF 99 registration form will put you on =
the list of the 2018-2019 NomCom, assuming you are =
eligible.</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Thanks. This was not what I understood when I checked =
the box. Maybe it should be made clearer in the future =
forms.<o:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>This is the question in the =
form:<br><br><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#26445B;=
background:white'>Are you willing to volunteer for the =
Nomcom?<br><br></span><o:p></o:p></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#26445B;=
background:white'>Behcet</span> <o:p></o:p></p></div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in =
6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; -Peter</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
ietf [mailto:<a href=3D"mailto:ietf-bounces@ietf.org" =
target=3D"_blank">ietf-bounces@ietf.org</a>] <b>On Behalf Of </b>Behcet =
Sarikaya<br><b>Sent:</b> Thursday, July 06, 2017 1:45 PM<br><b>To:</b> =
Michael StJohns<br><b>Cc:</b> IETF<br><b>Subject:</b> Re: NomCom =
randomness results... delayed</span><o:p></o:p></p><div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><div><div><div><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'>Hi =
all,<o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'>Regarding the =
list of volunteers, I had checked the box for volunteering for Nomcom =
when I registered for IETF 99 with payment,despite that my name is not =
in the list.<o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'>What =
makes?<o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'>Regards,<o:p></o:p=
></p></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Behcet<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On Thu, Jul =
6, 2017 at 1:21 PM, Michael StJohns &lt;<a =
href=3D"mailto:mstjohns@comcast.net" =
target=3D"_blank">mstjohns@comcast.net</a>&gt; wrote:<o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On 7/6/2017 =
12:25 PM, NomCom Chair 2017 wrote:<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'>I had planned to =
pull the randomness results today, but there will be a slight =
delay.&nbsp; While the EuroMillions and Powerball results are available =
(nothing like the lottery for being timely), the US debt numbers are =
still only showing the values for July 3rd.&nbsp; The July 4th US =
holiday may have something to do with that, although I would have =
expected the July 5th numbers to be up by now.<br><br>My plan for the =
moment is to examine the numbers tomorrow and see if the expected US =
debt data are available.&nbsp; If so, I'll run with the published =
inputs.&nbsp; If not, I'll have to use the latest available US debt =
numbers, which I will document in the randomness results =
announcement.&nbsp; Please let me know if this plan causes any =
concerns.<br><br>Peter Yee<br>NomCom Chair 2017-18<br>peter at akayla =
dot com<br>nomcom-chair-2017 at ietf dot org<o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'>Hi Peter =
-<br><br>You should pick a new date and a new set of variables, and =
announce rather than mixing and matching data you (we) already know with =
something you would pick later.&nbsp; That maintains the integrity of =
the process by keeping human choice out of the process.&nbsp; I'd =
probably also provide a caveat for when the data isn't available (e.g. a =
substitute).<br><br>Mike<o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div></div></div></div></div></blockquote></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_0700_01D2F662.8CCD5320--


From nobody Thu Jul  6 14:52:53 2017
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 869A7126B7F; Thu,  6 Jul 2017 14:52:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 SWzmPiCsgN1O; Thu,  6 Jul 2017 14:52:45 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (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 25383124217; Thu,  6 Jul 2017 14:52:45 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id 97DB924AE0D; Thu,  6 Jul 2017 21:52:36 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 509F9160047; Thu,  6 Jul 2017 21:52:40 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 110C4160098; Thu,  6 Jul 2017 21:52:40 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id qOdQSm_dyZ_F; Thu,  6 Jul 2017 21:52:39 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 8262B160047; Thu,  6 Jul 2017 21:52:39 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 99A8C7DB2FBA; Fri,  7 Jul 2017 07:52:36 +1000 (AEST)
To: Nico Williams <nico@cryptonector.com>
Cc: John C Klensin <john-ietf@jck.com>, dnsop <dnsop@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>, Paul Vixie <paul@redbarn.org>, IETF Rinse Repeat <ietf@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <CAMm+Lwjd6xVp-EDp=doevx=AP8qws_Mv++aL733yHEyUF72EMA@mail.gmail.com> <562EC659F89FA92A09CAC4DB@PSB> <20170706153955.GB3393@localhost>
Subject: Re: new DNS classes
In-reply-to: Your message of "Thu, 06 Jul 2017 10:39:56 -0500." <20170706153955.GB3393@localhost>
Date: Fri, 07 Jul 2017 07:52:36 +1000
Message-Id: <20170706215236.99A8C7DB2FBA@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZVpq9_s9cE4EofmUobIz5_nU1WA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jul 2017 21:52:46 -0000

In message <20170706153955.GB3393@localhost>, Nico Williams writes:
> So new classes will only be useful to extend the IN-class RR type
> namespace.  We won't get there.  New RR types can be very difficult to
> deploy due to lack of interest by registrars and domain hosting
> services.  TXT RRs forever.  :(

Or you could stop trying to reinforce the myth that new RR types
are hard to deploy.  They really aren't.  They actually get used
all the time.

> Cheers,
> 
> Nico
> -- 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Thu Jul  6 17:28:02 2017
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B71BF12F28A; Thu,  6 Jul 2017 17:28:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.88
X-Spam-Level: 
X-Spam-Status: No, score=-5.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 s_LIhyIKIJP5; Thu,  6 Jul 2017 17:27:59 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (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 2166B129AAD; Thu,  6 Jul 2017 17:27:59 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id B6E2B24AE09; Fri,  7 Jul 2017 00:26:35 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 9E46F160047; Fri,  7 Jul 2017 00:26:39 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 753D5160098; Fri,  7 Jul 2017 00:26:39 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ZQK65qSA3tCX; Fri,  7 Jul 2017 00:26:39 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 00E41160047; Fri,  7 Jul 2017 00:26:39 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id E51E97DB60EE; Fri,  7 Jul 2017 10:26:35 +1000 (AEST)
Cc: Nico Williams <nico@cryptonector.com>, John C Klensin <john-ietf@jck.com>, dnsop <dnsop@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>, Paul Vixie <paul@redbarn.org>, IETF Rinse Repeat <ietf@ietf.org>
From: Mark Andrews <marka@isc.org>
Subject: Re: new DNS classes
In-reply-to: Your message of "Fri, 07 Jul 2017 07:52:36 +1000."
Date: Fri, 07 Jul 2017 10:26:35 +1000
Message-Id: <20170707002635.E51E97DB60EE@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3sFhVQYE77Hlkusqw1GMyHfUaRI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 00:28:01 -0000

As for those that think deploying a new class would be hard the
tools that start to lookup records in the class would need to react
to error responses like this with a message saying "please install
root hints for class50 in your DNS recursive server".

[rock:~/git/bind9] marka% dig class50 type1 .

; <<>> DiG 9.12.0-pre-alpha+hotspot+add-prefetch+marka <<>> class50 type1 .
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 60872
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 151e2fd665595893dcd132c0595ecd8c1771012331aceded (good)
;; QUESTION SECTION:
;.				CLASS50	A

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Jul 07 09:53:48 AEST 2017
;; MSG SIZE  rcvd: 56

[rock:~/git/bind9] marka% 

In practice the new set of hints will almost certainly already be
compiled into the recursive server like root hints for class IN are
today with configuration directives to allow them to be overridden.
Adding a new class will be mostly transparent.

If you care about a name not existing you would need to check all
the active classes for NXDOMAIN but otherwise tools would just work
like they always had.

It requires planning and some lead time before you start to use it
in urnest but it is achievable.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Thu Jul  6 17:44:30 2017
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09CB9129562; Thu,  6 Jul 2017 17:44:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 XckLVaVw8iFw; Thu,  6 Jul 2017 17:44:21 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (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 970461293D6; Thu,  6 Jul 2017 17:44:21 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id 3DCAA24AE09; Fri,  7 Jul 2017 00:42:58 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id D147D160047; Fri,  7 Jul 2017 00:43:01 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 8A298160098; Fri,  7 Jul 2017 00:43:01 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id jWbkpEXdm5hh; Fri,  7 Jul 2017 00:43:01 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 3B6F8160047; Fri,  7 Jul 2017 00:43:01 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 541A17DB62A2; Fri,  7 Jul 2017 10:42:59 +1000 (AEST)
To: John C Klensin <john-ietf@jck.com>
Cc: "Roy T. Fielding" <fielding@gbiv.com>, dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <20170705000229.5918D7D8457F@rock.dv.isc.org> <CACweHNCAi7JcOW9CX=6FViv1wUoe5fhn7deJ2eieP2-D_FhaSA@mail.gmail.com> <20170705031957.834B97D8FBDD@rock.dv.isc.org> <CACweHNCAmZPOUmat5ruh6qkYrECM2fh15n49P+zDcJ0gfoEGvg@mail.gmail.com> <765A15BF-8505-4470-9628-70CE9665BC16@gbiv.com> <20170705231101.E23E77D9B7A1@rock.dv.isc.org> <901C29488D8446E4176CF83E@PSB>
Subject: Re: [DNSOP] Minor editorial change to draft-ietf-dnsop-sutld-ps
In-reply-to: Your message of "Thu, 06 Jul 2017 14:04:10 -0400." <901C29488D8446E4176CF83E@PSB>
Date: Fri, 07 Jul 2017 10:42:59 +1000
Message-Id: <20170707004259.541A17DB62A2@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Vz2k7wMxHemxP8sgyOaGEef0DgU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 00:44:23 -0000

In message <901C29488D8446E4176CF83E@PSB>, John C Klensin writes:
> 
> 
> --On Thursday, July 6, 2017 09:11 +1000 Mark Andrews
> <marka@isc.org> wrote:
> 
> >...
> > And the actual presentation limit for LDH with DNS is 253
> > (encodes as 255 octets on the wire).  Remember URI names do
> > not have a final period and the each label has length octet
> > when encoded as a DNS name and the name is terminated by the
> > root label (0x00) in DNS wire form and the DNS wire name is
> > limited to 255 octets.
> 
> Mark,
> 
> My apologies for nit-picking, but RFC 3986, Section 3.2.2 is
> quite clear than DNS names in URIs are permitted to have a final
> period and encouraged to do so under some circumstances.
> Specifically,
> 
> 	"The rightmost domain label of a fully qualified domain
> 	name in DNS may be followed by a single "." and should
> 	be if it is necessary to distinguish between the
> 	complete domain name and some local domain."
> 
> I don't think that changes the 253 octet limit, but the comment
> about URIs is misleading and could contribute to an, IMO,
> already high level of confusion about what RFC 3986 does or does
> not specify.
> 
> The same subsection of RFC 3986 also uses the term "host
> subcomponent" for what you are referring to as a name and allows
> it to be a "registered name" (or <reg-name>) that might not be a
> DNS name or reference at all -- whether it is or not is
> scheme-dependent. 
> 
> best,
>    john

Which really should never have been allowed.  Beyound the UI
everything should be absolute.  Relative names in URI really don't
work in practice because search lists are not constistent even
inside a single organisation.

I had my ISP hand me a relative link for their support pages.  IT
DID NOT WORK.  There support line got a call complaining about it.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Thu Jul  6 20:36:40 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ECA912741D; Thu,  6 Jul 2017 20:36:32 -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, RP_MATCHES_RCVD=-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 RrKXrtlQN8Dz; Thu,  6 Jul 2017 20:36:30 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 427B61317B0; Thu,  6 Jul 2017 20:36:30 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dTK4A-000AWp-Sb; Thu, 06 Jul 2017 23:36:26 -0400
Date: Thu, 06 Jul 2017 23:36:21 -0400
From: John C Klensin <john-ietf@jck.com>
To: Mark Andrews <marka@isc.org>
cc: "Roy T. Fielding" <fielding@gbiv.com>, dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: [DNSOP] Minor editorial change to draft-ietf-dnsop-sutld-ps
Message-ID: <707A073EEBAE4B87504AB9B4@PSB>
In-Reply-To: <20170707004259.541A17DB62A2@rock.dv.isc.org>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <20170705000229.5918D7D8457F@rock.dv.isc.org> <CACweHNCAi7JcOW9CX=6FViv1wUoe5fhn7deJ2eieP2-D_FhaSA@mail.gmail.com> <20170705031957.834B97D8FBDD@rock.dv.isc.org> <CACweHNCAmZPOUmat5ruh6qkYrECM2fh15n49P+zDcJ0gfoEGvg@mail.gmail.com> <765A15BF-8505-4470-9628-70CE9665BC16@gbiv.com> <20170705231101.E23E77D9B7A1@rock.dv.isc.org> <901C29488D8446E4176CF83E@PSB> <20170707004259.541A17DB62A2@rock.dv.isc.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yRCFxauyIwjG-910suHIuURMedM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 03:36:32 -0000

--On Friday, July 7, 2017 10:42 +1000 Mark Andrews
<marka@isc.org> wrote:

>> The same subsection of RFC 3986 also uses the term "host
>> subcomponent" for what you are referring to as a name and
>> allows it to be a "registered name" (or <reg-name>) that
>> might not be a DNS name or reference at all -- whether it is
>> or not is scheme-dependent. 
>...

> Which really should never have been allowed.  Beyound the UI
> everything should be absolute.  Relative names in URI really
> don't work in practice because search lists are not
> constistent even inside a single organisation.

Mark, it is no secret that I'm not a fan of relative URIs or of
3986 generally.  But the latter is, for better or worse, a full
standard that went through the IETF process.   If you think it
is seriously flawed, I'd encourage you to write in I-D to fix it
and see if you can get it through the system.  My experience
predicts that any attempt to do such a thing will produce an
outcry about the astronomical number of web pages that contain
and depend on such references and the only slightly smaller
number of them that are used every day, but maybe you will do
better than I did when I tried to get something with far
narrower scope through the system.

> I had my ISP hand me a relative link for their support pages.
> IT DID NOT WORK.  There support line got a call complaining
> about it.

With the above in mind, so?  The number of links most of us see
a week that don't work --whether the references are relative or
absolute-- is rather too large to view one failure as horrible
breakage in the model.

    john


From nobody Thu Jul  6 21:40:11 2017
Return-Path: <kazuhooku@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7098F12EC1C; Thu,  6 Jul 2017 21:40:09 -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 PxALMlTBQ74Y; Thu,  6 Jul 2017 21:40:07 -0700 (PDT)
Received: from mail-pg0-x22d.google.com (mail-pg0-x22d.google.com [IPv6:2607:f8b0:400e:c05::22d]) (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 901AF124D85; Thu,  6 Jul 2017 21:40:07 -0700 (PDT)
Received: by mail-pg0-x22d.google.com with SMTP id t186so11204891pgb.1; Thu, 06 Jul 2017 21:40:07 -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=h3TGgKimQqBFyGHcd9y1oiGbpFwHsWNBlN9QXv6g2Uc=; b=JrANn2ACo6aoni6iXhcQDwOOpBOepnPDHCn2c6WOAvzaOLaWOFvEg4JFkDX37VN0k1 yPIfwbUw/OciwVimUfAhFZq1Jih9embei5F933MytcW0oP06wY/SDebvueYyD6EAgrfI IOHLQBz27hZqX6o7Kgm+r6+oyxq31YHsLs263Yw+keoGznKYvGpWYA/8j4LQD6jSolWy V41hJiC35fYbPuu/F+AL3f7KFozi8QUkbUN9VUFTXtJaif+/vbNG/4lZBpKWRY/33ryp wIVJxGkW+vWXAWnl8pnHrTiiPehRoseapAyqJXRiYbl7Mpq3150jiCT44sIwPJ4gKwrW yeBw==
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=h3TGgKimQqBFyGHcd9y1oiGbpFwHsWNBlN9QXv6g2Uc=; b=ch4cUp6zj4RogF2w53M82kUUXLXAO2lp3uNPHnM6vfhRnXBkrk+KqQwd8kxW/oEsLD Y4w0Szand6/iw0W6/HUpL1IO97jtdwB2kYE6y6+7PHtGvMfBV2eGF6PEib6/SpDMh+Je dt3lKTh0oVeNYgQy/mCis+ZVtl/UzdjCs2V3r2/1qTQ5TLbBAtvBgYCZYYcDkInJv8Qq Fa2T3WgD0tcCy3LbMGCzs7ZBdic5PGWmkoQ9rfXMx4TqXJySlAzM0wpoj58YcUNGvNHH /gG/wGcmkgLpzJ+2UxIL7xyoxSmCBGSPRRHAhRA7Vg6oanI5L78jOpa6BXunrBoeK9me hOLQ==
X-Gm-Message-State: AIVw111+OX2oyJQA2ba7Iw+Sqo9ITwShMjGUxaYslNB29aPYfX7SbSsd FCHKNS2Ms5R6Z/9GgSD6J9IRlK6z7Q==
X-Received: by 10.99.104.74 with SMTP id d71mr30456784pgc.7.1499402407145; Thu, 06 Jul 2017 21:40:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.130.3 with HTTP; Thu, 6 Jul 2017 21:40:06 -0700 (PDT)
In-Reply-To: <149919703750.15996.5462759432298024921@ietfa.amsl.com>
References: <149919703750.15996.5462759432298024921@ietfa.amsl.com>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Fri, 7 Jul 2017 13:40:06 +0900
Message-ID: <CANatvzx8GsvoYMscHciKNrOwRzcz1v7=jTCUUp4Z5E=jO9Wd6g@mail.gmail.com>
Subject: Re: Secdir last call review of draft-ietf-httpbis-early-hints-03
To: Melinda Shore <melinda.shore@gmail.com>
Cc: secdir@ietf.org, draft-ietf-httpbis-early-hints.all@ietf.org,  IETF Discussion Mailing List <ietf@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PRlcje8L9kBrEDcge_4osnrP4OI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 04:40:09 -0000

Hi Melinda,

Thank you very much for the review. My responses below.

2017-07-05 4:37 GMT+09:00 Melinda Shore <melinda.shore@gmail.com>:
> Reviewer: Melinda Shore
> Review result: Has Issues
>
> I have reviewed this document as part of the security directorate's
> ongoing effort to review all IETF documents being processed by the
> IESG.  These comments were written primarily for the benefit of the
> security area directors.  Document editors and WG chairs should treat
> these comments just like any other last call comments.
>
> Summary:   Has minor issues.
>
> This draft defines a status code for sending an informational
> response that contains header fields that are likely to be included in the
> final response.  A server can send the informational response containing
> some of the header fields to help the client start making preparations
> for processing the final response, and then run time-consuming operations
> to generate the final response.  The informational response can also be used by an
> origin server to trigger HTTP/2 server push at a caching intermediary.
>
> Passed nit checker without complaints other than publication date.  Sections
> 5 and 6 should be appendices.

The issue has been fixed in the github repo.

>
> One minor issue: in the security considerations section, "Therefore,
> a server might refrain from sending Early Hints over HTTP/1.1 unless when
> the client is known to handle informational responses correctly" is a bit squishy
> (and contains a superfluous "when").  I'm not sure this merits a text change and
> I'm rather certain that it doesn't merit normative 2119 language but it did stand
> out as an overly soft recommendation.

The superfluous "when" has been removed from the github repo.

Regarding the wording, I think it would be better to keep the tone
as-is, rather than suggesting implementers not to send an Early Hints
response over HTTP/1.1 depending on the client.

Users behind a proxy that cannot handle informational response
correctly is exposed to response splitting attack regardless of if
Early Hints is used (in HTTP/1.1, a server is allowed to send any
informational response at it's own discretion).

So while it is beneficial to warn the risks, I think that there is no
merit in restricting the use of Early Hints.

-- 
Kazuho Oku


From nobody Thu Jul  6 22:53:27 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0D0A12EA58; Thu,  6 Jul 2017 22:53:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 HMKlTdQ0X7lu; Thu,  6 Jul 2017 22:53:19 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A54CE126D45; Thu,  6 Jul 2017 22:53:19 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTP id D85E1C0028BA; Thu,  6 Jul 2017 22:53:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=bZLi8BEwlnk1FP hFiOr7zO3DpBw=; b=fFPg68NI3ud7kVns8FcFhb7OE2Ftq7vQ0XvGDu0VKzeUZk jafTDJXtCpE+XrU97pgbbQ5Sy4VmpaMGDmBjXTfX4C6rTCB26tTs817dWksBE/ED PQhJUMePIpzJDY7JDpPTrYGt5R6ndAs31gyAiKnRJKSiDjye0Eq1ML38YEP3g=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTPSA id 2DD34C0028B8; Thu,  6 Jul 2017 22:53:18 -0700 (PDT)
Date: Fri, 7 Jul 2017 00:53:16 -0500
From: Nico Williams <nico@cryptonector.com>
To: Mark Andrews <marka@isc.org>
Cc: John C Klensin <john-ietf@jck.com>, dnsop <dnsop@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>, Paul Vixie <paul@redbarn.org>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: new DNS classes
Message-ID: <20170707055315.GC3393@localhost>
References: <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <CAMm+Lwjd6xVp-EDp=doevx=AP8qws_Mv++aL733yHEyUF72EMA@mail.gmail.com> <562EC659F89FA92A09CAC4DB@PSB> <20170706153955.GB3393@localhost> <20170706215236.99A8C7DB2FBA@rock.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170706215236.99A8C7DB2FBA@rock.dv.isc.org>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/U-RCDGZefOWV3h2q8H8AlB5ijDE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 05:53:21 -0000

On Fri, Jul 07, 2017 at 07:52:36AM +1000, Mark Andrews wrote:
> In message <20170706153955.GB3393@localhost>, Nico Williams writes:
> > So new classes will only be useful to extend the IN-class RR type
> > namespace.  We won't get there.  New RR types can be very difficult to
> > deploy due to lack of interest by registrars and domain hosting
> > services.  TXT RRs forever.  :(
> 
> Or you could stop trying to reinforce the myth that new RR types
> are hard to deploy.  They really aren't.  They actually get used
> all the time.

I'm well aware that as to clients and servers, deploying new RR types is
easy.  The hard part is the management backend and UIs.  Not all of them
allow you to enter raw RDATA (hex-encoded or whatever).

We've struggled with this in KITTEN WG.  Deploying the URI RR type when
you're using a hosting service can be anywhere from annoying (must enter
raw RDATA) to impossible (the hosting service doesn't give a damn).  I
suppose it's just a matter of time; perhaps things have improved since
we last looked.

Nico
-- 


From nobody Thu Jul  6 22:54:07 2017
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAD2C12FEE1; Thu,  6 Jul 2017 22:54:05 -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 M38TgKKxAq-W; Thu,  6 Jul 2017 22:54:01 -0700 (PDT)
Received: from mail-pf0-x234.google.com (mail-pf0-x234.google.com [IPv6:2607:f8b0:400e:c00::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 62BC812F257; Thu,  6 Jul 2017 22:54:01 -0700 (PDT)
Received: by mail-pf0-x234.google.com with SMTP id e7so11998769pfk.0; Thu, 06 Jul 2017 22:54:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=5poBw+n7N9x7eJzrIhs1M1VExP+MFP3lWFUVhGDSkq8=; b=lSAGZoJG2NCF/M6lnbmupRt0a+X0IT2ajgkd67VNavozq4vlHf2+xL256uJTJTA0Bh eQ4xgxnLkbKwjz7uIkrdJNKFyKGbLbXjwpkGbl9ckwSJBgxcieDeFpy1bSs66r+byqgx z0YIc8U2jgAO5/VwpUSc0feEOvURfjKvDs+bsTwIVmmeI2IjEZKurbx4J+uzzCoYKaz+ sHj+zRnrV8CKjqIdzNt1nwyJyxStozzoUVUgGNQJAt4Rf/Ukt5l6UGN8Zj//66g6iGYB W34aMj/ynZhIiYMJ7RQfhW2ZMd4p/HACM4yNx6ekGOqUBMbZiQ4AwwQyGDYBUlboSCUO IMsg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=5poBw+n7N9x7eJzrIhs1M1VExP+MFP3lWFUVhGDSkq8=; b=uQ3roHhn3rrEufsT6r5RHkMNcLxuyHX7VZLvybcOmOM8tG3EDePSSvn7vG0i19QSil x9/9/AG3t/BaS2/iOiN/HI9IOUOWakIw5YiabGwh1wsiuGRAe0/nt3jc2OpqyZ8K/lGX gyH2fm+izOc1RTvPdRuQYNU3cmzjOzYWzhoPW+8fTWJfOKv2vRdmivp34Btite9SVr4T M3LliiJo30V5KGVc/vQckGHTdBPjugNHJmtmgLaN4btaEwshSr8nU78/jQ1N4ej3hqPY sG5P+s5/4ppeaTeEsa5N8mtjn493LCqofcB+vDaDMCW7I41LxDW0DwXptDkmOkmRPkMI BMWQ==
X-Gm-Message-State: AIVw113EAL4m2eWZryGDEWR7a7wrQwh3FI4gM/iqT+EfQnsC1US7NjjM AanrsTUeCl6w4Q==
X-Received: by 10.99.165.28 with SMTP id n28mr29641696pgf.163.1499406840877; Thu, 06 Jul 2017 22:54:00 -0700 (PDT)
Received: from aspen.local (216-67-119-73-radius.dynamic.acsalaska.net. [216.67.119.73]) by smtp.gmail.com with ESMTPSA id p77sm3424077pfd.62.2017.07.06.22.53.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Jul 2017 22:53:59 -0700 (PDT)
Subject: Re: Secdir last call review of draft-ietf-httpbis-early-hints-03
To: Kazuho Oku <kazuhooku@gmail.com>
References: <149919703750.15996.5462759432298024921@ietfa.amsl.com> <CANatvzx8GsvoYMscHciKNrOwRzcz1v7=jTCUUp4Z5E=jO9Wd6g@mail.gmail.com>
Cc: secdir@ietf.org, draft-ietf-httpbis-early-hints.all@ietf.org, IETF Discussion Mailing List <ietf@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <7273f8ab-c1ff-5dff-862e-0a1ead6d28b2@gmail.com>
Date: Thu, 6 Jul 2017 21:53:53 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CANatvzx8GsvoYMscHciKNrOwRzcz1v7=jTCUUp4Z5E=jO9Wd6g@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Tjam5Rpp1D8XFnUOWslnmBv3pTBb37dHF"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ofh6dcTwafW5hoFKuXTSYMxSvOk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 05:54:06 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--Tjam5Rpp1D8XFnUOWslnmBv3pTBb37dHF
Content-Type: multipart/mixed; boundary="nFa2W5wKPdwcbSct4vbstqABB4BHX1W9Q";
 protected-headers="v1"
From: Melinda Shore <melinda.shore@gmail.com>
To: Kazuho Oku <kazuhooku@gmail.com>
Cc: secdir@ietf.org, draft-ietf-httpbis-early-hints.all@ietf.org,
 IETF Discussion Mailing List <ietf@ietf.org>,
 HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <7273f8ab-c1ff-5dff-862e-0a1ead6d28b2@gmail.com>
Subject: Re: Secdir last call review of draft-ietf-httpbis-early-hints-03
References: <149919703750.15996.5462759432298024921@ietfa.amsl.com>
 <CANatvzx8GsvoYMscHciKNrOwRzcz1v7=jTCUUp4Z5E=jO9Wd6g@mail.gmail.com>
In-Reply-To: <CANatvzx8GsvoYMscHciKNrOwRzcz1v7=jTCUUp4Z5E=jO9Wd6g@mail.gmail.com>

--nFa2W5wKPdwcbSct4vbstqABB4BHX1W9Q
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 7/6/17 8:40 PM, Kazuho Oku wrote:
> Regarding the wording, I think it would be better to keep the tone
> as-is, rather than suggesting implementers not to send an Early Hints
> response over HTTP/1.1 depending on the client.

Yeah, you don't want to discourage implementation.  I think
the goal is to find some balance between not putting off
implementers on the one hand, and having to deal with an
embarrassing incident on the other.  I'd be more comfortable
with language that's a bit stronger but it's not a huge
issue, certainly not one that's an impediment to moving the
document forward (particularly given that it's intended for
publication as an experimental standard).  In general I
thought the draft was clearly written and straightforward,
and ready for publication modulo this one minor issue.

Melinda



--nFa2W5wKPdwcbSct4vbstqABB4BHX1W9Q--

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

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJZXyHyAAoJELiGRpM6HoEufgQQAKCMtE1IioaC+U80toAhu7FS
3IxxHAClVOI4PTzcrq3MVytnfUUPSW/hExDe6ll7RfaeN0a5dFiT7V+vVBvRgRGa
Kz1ygu34aO69LJhgkJCEK1YqVF3RRDMHa4hhtHLqQvApt5i1TSc1vrnCr2IvbgsO
Mn9d3z0QLE/nDF6laXzwgohWF436QAEJppoHNMjd4S5iN3y3cPN8JGfIA/qQiRCT
/GHGIrI7H42vrWQAKjD8U/0MfI6+09LLR8LtfsyZ64O4IxTqVEVkvoLkek/m2RGQ
1mKhOiZsK79/3MkVmUmlNgc0rsH26CeO17PZTBDGM8fQKSQWqEZG+yXygUhxxKDo
Lr5bBIO01F9dX6oGgpP7UAaG7j8YEB/8kTR2f1TuX1F9uUdFImXzGZV73FzEBLVb
eGSVj3ufn+ylXBKUegFxoYjwtI7lvBs5pNlVIq75GxnJNvEiagWdIiV3eQFO5inN
BLBwd4uEDTs+cbxeID03C2fe3WRDJ5Qy3d3auMQZtwq0n7oB0IUxyGC/AMLQYJqQ
Cwi1yqFhNJ16o11G/Ao4wwQTk7bRP7cW34JJXzxYLVJUwHX88TLzYXtkZRbdxAgf
5iCvyz1MBL0K94yP1xv/l6Q3kMUz408AOEUwYa4wvXZiigcTouN4vMfEWQ7toojj
/7Td1UNgPvJ32UH6Hx4u
=x16F
-----END PGP SIGNATURE-----

--Tjam5Rpp1D8XFnUOWslnmBv3pTBb37dHF--


From nobody Thu Jul  6 23:56:51 2017
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BF6C126579; Thu,  6 Jul 2017 23:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 3rum1OPm5FkA; Thu,  6 Jul 2017 23:56:42 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (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 D2B8D131445; Thu,  6 Jul 2017 23:56:42 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 7711E3493BB; Fri,  7 Jul 2017 06:56:40 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 511BD16004A; Fri,  7 Jul 2017 06:56:40 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 26D79160055; Fri,  7 Jul 2017 06:56:40 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id C8rb3xHjmOAA; Fri,  7 Jul 2017 06:56:40 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id CC55D16004A; Fri,  7 Jul 2017 06:56:39 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id EB9C07DBDEF2; Fri,  7 Jul 2017 16:56:37 +1000 (AEST)
To: Nico Williams <nico@cryptonector.com>
Cc: John C Klensin <john-ietf@jck.com>, dnsop <dnsop@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>, Paul Vixie <paul@redbarn.org>, IETF Rinse Repeat <ietf@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <CAMm+Lwjd6xVp-EDp=doevx=AP8qws_Mv++aL733yHEyUF72EMA@mail.gmail.com> <562EC659F89FA92A09CAC4DB@PSB> <20170706153955.GB3393@localhost> <20170706215236.99A8C7DB2FBA@rock.dv.isc.org> <20170707055315.GC3393@localhost>
Subject: Re: new DNS classes
In-reply-to: Your message of "Fri, 07 Jul 2017 00:53:16 -0500." <20170707055315.GC3393@localhost>
Date: Fri, 07 Jul 2017 16:56:37 +1000
Message-Id: <20170707065637.EB9C07DBDEF2@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0shDtvBJQZFZQLbi0xYKwy0iSHg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 06:56:44 -0000

In message <20170707055315.GC3393@localhost>, Nico Williams writes:
> On Fri, Jul 07, 2017 at 07:52:36AM +1000, Mark Andrews wrote:
> > In message <20170706153955.GB3393@localhost>, Nico Williams writes:
> > > So new classes will only be useful to extend the IN-class RR type
> > > namespace.  We won't get there.  New RR types can be very difficult to
> > > deploy due to lack of interest by registrars and domain hosting
> > > services.  TXT RRs forever.  :(
> > 
> > Or you could stop trying to reinforce the myth that new RR types
> > are hard to deploy.  They really aren't.  They actually get used
> > all the time.
> 
> I'm well aware that as to clients and servers, deploying new RR types is
> easy.  The hard part is the management backend and UIs.  Not all of them
> allow you to enter raw RDATA (hex-encoded or whatever).
> 
> We've struggled with this in KITTEN WG.  Deploying the URI RR type when
> you're using a hosting service can be anywhere from annoying (must enter
> raw RDATA) to impossible (the hosting service doesn't give a damn).  I
> suppose it's just a matter of time; perhaps things have improved since
> we last looked.

Then change domain hosting providers and tell them why or run you
own master server or use a service which allows for dynamic updates
which shouldn't care about the record types.  There are plenty of
DNS providers that will slave content.

As a DNS server vendor we get requests to add the new type within
days the type being allocated.  We usually already have code written
and merged to support the new type in all current branches before
those request come in as we poll the type registry daily.  It is
available over git to anyone that wants to pull it down support for
the new type prior to the next maintainence releases.  Adding a new
type is as simple as adding to files to the source tree and rebuilding
the tools.  Once that is done all the tools we ship support it.

Mark

> Nico
> -- 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Fri Jul  7 02:23:28 2017
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D8A7126B6D; Fri,  7 Jul 2017 02:23:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, 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 lqGdnzzFhqAd; Fri,  7 Jul 2017 02:23:25 -0700 (PDT)
Received: from 1wt.eu (wtarreau.pck.nerim.net [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id DC1D41204DA; Fri,  7 Jul 2017 02:23:24 -0700 (PDT)
Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id v679NG3K027610; Fri, 7 Jul 2017 11:23:16 +0200
Date: Fri, 7 Jul 2017 11:23:16 +0200
From: Willy Tarreau <w@1wt.eu>
To: Melinda Shore <melinda.shore@gmail.com>
Cc: Kazuho Oku <kazuhooku@gmail.com>, secdir@ietf.org, draft-ietf-httpbis-early-hints.all@ietf.org, IETF Discussion Mailing List <ietf@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Subject: Re: Secdir last call review of  draft-ietf-httpbis-early-hints-03
Message-ID: <20170707092316.GA27560@1wt.eu>
References: <149919703750.15996.5462759432298024921@ietfa.amsl.com> <CANatvzx8GsvoYMscHciKNrOwRzcz1v7=jTCUUp4Z5E=jO9Wd6g@mail.gmail.com> <7273f8ab-c1ff-5dff-862e-0a1ead6d28b2@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7273f8ab-c1ff-5dff-862e-0a1ead6d28b2@gmail.com>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SwGBkFTlGMKeFBIMqk3DZ_t94Yc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 09:23:27 -0000

On Fri, Jul 07, 2017 at 05:54:41AM +0000, Melinda Shore wrote:
> On 7/6/17 8:40 PM, Kazuho Oku wrote:
> > Regarding the wording, I think it would be better to keep the tone
> > as-is, rather than suggesting implementers not to send an Early Hints
> > response over HTTP/1.1 depending on the client.
> 
> Yeah, you don't want to discourage implementation.  I think
> the goal is to find some balance between not putting off
> implementers on the one hand, and having to deal with an
> embarrassing incident on the other.  I'd be more comfortable
> with language that's a bit stronger but it's not a huge
> issue, certainly not one that's an impediment to moving the
> document forward (particularly given that it's intended for
> publication as an experimental standard).

I'm just thinking about the fact that we're not even sure that any 
HTTP/1.1 client doesn't support these informational responses,
because such clients can already make use of Expect: 100-continue
(so they know about 100), and if I remember well when designing the
101 upgrade for WebSocket, which was reused for HTTP/2, some of
the difficulties we faced was that some clients/intermediaries
were consuming 101 as 1xx and waiting for a final response after
it.

Maybe the stronger wording should be oriented differently, such as
"Servers MUST not send 103 to HTTP/1.0 clients nor to any client
known not to support 1xx informational responses" ? This way it
leaves the possibility opened (ie rely on version and/or user-agent
or anything else once an exception is known).

Just my two cents,
Willy


From nobody Fri Jul  7 02:33:32 2017
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6AA4129AD0; Fri,  7 Jul 2017 02:33:25 -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, 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=mnot.net header.b=Cma8/Rkw; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=puPRxddm
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 mU9U5EJOReF7; Fri,  7 Jul 2017 02:33:22 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3A541204DA; Fri,  7 Jul 2017 02:33:22 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 38B8A20AED; Fri,  7 Jul 2017 05:33:22 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Fri, 07 Jul 2017 05:33:22 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; 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=6Ez5dztVkOe0no5bFI AR8hk3QaCOUlMCN4iPKfnWRZY=; b=Cma8/RkwvpQO0Sie4hey5Hk9ExK8phDzvo zv+U1cYY9w0Q2/Gg1GcKRb2ZarT/wxhB2GzIwMoja8X7TN7TUsQwx95cYbsSyOHn 5zsqipIpGPCYrOrBN7Lr3A+G4u1Wj9yhbqm83nDoP4bYAWa/q7D7qmNr/Vw82e4p aLrORisfT9DjcRv+gG/cX8WQDrm1vS2zFyVeVn4H0zf0Dcb3xNtisij0QWhiMPN1 iOf+Htcvz+WJ9teS2BhfeuyltBjQPj/LGY8XFUuRSJ+BLfaEuOagLi11Qf3XlXX0 DIj+tbv1nYV2WrBM5HG123D5OZvWC+xF5Uhz6iQO78PZMSPzU8AA==
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=6Ez5dztVkOe0no5bFIAR8hk3QaCOUlMCN4iPKfnWRZY=; b=puPRxddm rhvDjLPBDOq7SjJqWNC4PV+4EroHYRjZcQ3WWbbGX1JOnNyUl5eUAI8WBRs/RNR4 vw/TUG6A7vEe8Lacr6EQ/YccYAT0rYRo+kfILzdUlFiLNu4n9yovAqATAhleyEQW SqLcs3zogTW5rZL40L6wfwsGdWye9W3kqVb8V0LJPexQ/RVXqnonqtolMMgICVIn 3/4blOAOUukqBFAglFSpR14ZDD9St1T1s3cu1LecWGpOsVNx38Nh2DCiZhVP7joa C4i2Itbf0UHQsZkvaATwXKGcOZVLK/3bgvqoeg/WOfL5Za3Y3vIOF/0Nc1SENdaZ xwIVhkGabFBsuw==
X-ME-Sender: <xms:YlVfWQnMLrbuFq8jYHLN1skACD4pE2O-EbYC2qZlM1rJ6w6zRGpybQ>
X-Sasl-enc: Fe7ag9UYwYd4bVPwo1iczLrddTr7u7FilIlrfXoZFfwf 1499420001
Received: from [192.168.1.14] (cpe-124-188-19-231.hdbq1.win.bigpond.net.au [124.188.19.231]) by mail.messagingengine.com (Postfix) with ESMTPA id ED5167E622; Fri,  7 Jul 2017 05:33:19 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Secdir last call review of  draft-ietf-httpbis-early-hints-03
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <20170707092316.GA27560@1wt.eu>
Date: Fri, 7 Jul 2017 19:33:17 +1000
Cc: Melinda Shore <melinda.shore@gmail.com>, Kazuho Oku <kazuhooku@gmail.com>,  secdir <secdir@ietf.org>, draft-ietf-httpbis-early-hints.all@ietf.org, IETF Discussion Mailing List <ietf@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A1A1FDB3-C346-4F52-8942-BBEF05849A3F@mnot.net>
References: <149919703750.15996.5462759432298024921@ietfa.amsl.com> <CANatvzx8GsvoYMscHciKNrOwRzcz1v7=jTCUUp4Z5E=jO9Wd6g@mail.gmail.com> <7273f8ab-c1ff-5dff-862e-0a1ead6d28b2@gmail.com> <20170707092316.GA27560@1wt.eu>
To: Willy Tarreau <w@1wt.eu>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/21CYoEqiJw6O-_BzxhKjk5GtiO0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 09:33:26 -0000

On 7 Jul 2017, at 7:23 pm, Willy Tarreau <w@1wt.eu> wrote:
>=20
> Maybe the stronger wording should be oriented differently, such as
> "Servers MUST not send 103 to HTTP/1.0 clients nor to any client
> known not to support 1xx informational responses" ? This way it
> leaves the possibility opened (ie rely on version and/or user-agent
> or anything else once an exception is known).

RFC7231 already says "Since HTTP/1.0 did not define any 1xx status =
codes, a server MUST NOT send a 1xx response to an HTTP/1.0 client."


--
Mark Nottingham   https://www.mnot.net/



From nobody Fri Jul  7 04:29:46 2017
Return-Path: <kazuhooku@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB497129B4C; Fri,  7 Jul 2017 04:29:38 -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 LaugGBbv1rvI; Fri,  7 Jul 2017 04:29:37 -0700 (PDT)
Received: from mail-pg0-x22e.google.com (mail-pg0-x22e.google.com [IPv6:2607:f8b0:400e:c05::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 67CD8129B2C; Fri,  7 Jul 2017 04:29:37 -0700 (PDT)
Received: by mail-pg0-x22e.google.com with SMTP id u62so15901996pgb.3; Fri, 07 Jul 2017 04:29:37 -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=IEUlzBRv5plxZSUVTaichvRvfRAM4EwEQnR14+AQ7EA=; b=phqCYs5f1xP1+IMVmaGK5fYb2wcWtwk5kZ1Izk8VZRzGgctZQppIxbGcqTUx3iPvxg bZZU6ovAKp8tCs0GlTBW5J41yYZMz0owIaxBXoMzsOZ1CcUlC08ceFO6YQPovvQWzJwt e8a+r8ClpkS18Tdkt333oDsirt2BviI/Ed1Ci/GR2abOlCt5tqhEEqY4TOEJusqxSlJr IThZRUAw/8CRUCF9MIzuqFEJ6+0D8w1cpgwK6Oc8eDGccqW3p21IUS0tCweYvFA3eX1Z aETtBB2tH4AnzaPAb74ZxSVl2zwrdMh5uOokacdmfx/Ffd2CIEkKBX4ajS4PZ8Lqvx5X 2qCA==
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=IEUlzBRv5plxZSUVTaichvRvfRAM4EwEQnR14+AQ7EA=; b=W0VWlPCHDRszRBKx2CJ6/YpNUSEg5GfO+U7IPb7S9bY6/dLzCcMjNLh54fJz/WSBof r53ySxW1srAog4c1Bh6wg5AiRKFKbV/OCM9/6oS0AksZa/asLjVgQHdi5Aaaan9uBoyc 5dvhSqJt+GC3vqbJm06gbZSSem2e4u4WJ+29XzTk1JIP3zSXxJm04EnDVbz3J8vh/u9G aoZGSDuUwpIEBDPxlQVIM3d1A44t6M5e/m9CZZDdogOR7PhR+N7CnLe29duCqUfZ9g6L pGDbcEdMSpJh/XRJausxP4NMAZ200BivLwIhcq5d/tjqZmLzBMZvgnSnqY54rhNj6Yos nnYQ==
X-Gm-Message-State: AIVw112oBZKUxUJeZsi6EoaDe389B89aYn+iNgRTw0uOOGlcmNfYgc0N QMu0lG4kp87CPhre6GC49jrUaE/LSQ==
X-Received: by 10.98.79.130 with SMTP id f2mr31197225pfj.133.1499426976952; Fri, 07 Jul 2017 04:29:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.130.3 with HTTP; Fri, 7 Jul 2017 04:29:36 -0700 (PDT)
In-Reply-To: <20170707092316.GA27560@1wt.eu>
References: <149919703750.15996.5462759432298024921@ietfa.amsl.com> <CANatvzx8GsvoYMscHciKNrOwRzcz1v7=jTCUUp4Z5E=jO9Wd6g@mail.gmail.com> <7273f8ab-c1ff-5dff-862e-0a1ead6d28b2@gmail.com> <20170707092316.GA27560@1wt.eu>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Fri, 7 Jul 2017 20:29:36 +0900
Message-ID: <CANatvzygATN6Rd7nGPuGLSpbYs65TV01BFMFrB9Atq1ojcXHJQ@mail.gmail.com>
Subject: Re: Secdir last call review of draft-ietf-httpbis-early-hints-03
To: Willy Tarreau <w@1wt.eu>
Cc: Melinda Shore <melinda.shore@gmail.com>, secdir@ietf.org,  draft-ietf-httpbis-early-hints.all@ietf.org,  IETF Discussion Mailing List <ietf@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5TwlCl2MGrFt-QOUoCL5gJ1-GSI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 11:29:39 -0000

2017-07-07 18:23 GMT+09:00 Willy Tarreau <w@1wt.eu>:
> On Fri, Jul 07, 2017 at 05:54:41AM +0000, Melinda Shore wrote:
>> On 7/6/17 8:40 PM, Kazuho Oku wrote:
>> > Regarding the wording, I think it would be better to keep the tone
>> > as-is, rather than suggesting implementers not to send an Early Hints
>> > response over HTTP/1.1 depending on the client.
>>
>> Yeah, you don't want to discourage implementation.  I think
>> the goal is to find some balance between not putting off
>> implementers on the one hand, and having to deal with an
>> embarrassing incident on the other.  I'd be more comfortable
>> with language that's a bit stronger but it's not a huge
>> issue, certainly not one that's an impediment to moving the
>> document forward (particularly given that it's intended for
>> publication as an experimental standard).
>
> I'm just thinking about the fact that we're not even sure that any
> HTTP/1.1 client doesn't support these informational responses,
> because such clients can already make use of Expect: 100-continue
> (so they know about 100), and if I remember well when designing the
> 101 upgrade for WebSocket, which was reused for HTTP/2, some of
> the difficulties we faced was that some clients/intermediaries
> were consuming 101 as 1xx and waiting for a final response after
> it.
>
> Maybe the stronger wording should be oriented differently, such as
> "Servers MUST not send 103 to HTTP/1.0 clients nor to any client
> known not to support 1xx informational responses" ? This way it
> leaves the possibility opened (ie rely on version and/or user-agent
> or anything else once an exception is known).

Considering that this is merely an advice on how to deal with broken
clients, I think that we should not use the verbs defined in RFC 2119
or state a strong prohibition.

I also believe that a whitelist-based approach will be a better choice
than a blacklist-based one, since 103 is an optimization that is
beneficial when sent to a client that is known to make use of it. For
most websites, whitelisting the major browsers that support it (once
they do) or the CDN they use will be enough to get the most out of the
status code.

> Just my two cents,
> Willy



-- 
Kazuho Oku


From nobody Fri Jul  7 04:44:27 2017
Return-Path: <stefan.eissing@greenbytes.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 971B112EA7C; Fri,  7 Jul 2017 04:44:25 -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, RP_MATCHES_RCVD=-0.001, 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=greenbytes.de header.b=FK0WGOGU; dkim=pass (1024-bit key) header.d=greenbytes.de header.b=MQie0i0t
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 9Jl7l4J-KUfb; Fri,  7 Jul 2017 04:44:23 -0700 (PDT)
Received: from mail.greenbytes.de (mail.greenbytes.de [217.91.35.233]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17F6B129AD2; Fri,  7 Jul 2017 04:44:22 -0700 (PDT)
Received: by mail.greenbytes.de (Postfix, from userid 117) id 9FEA615A3BC2; Fri,  7 Jul 2017 13:44:20 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=greenbytes.de; s=mail; t=1499427860; bh=0mXG+i6vAshXeCMWrnXN6xMGBPErEjzMWIY/WYLK54w=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=FK0WGOGUzTLJiNzoqRpOB2wK6gBnNfFntSsDruDyceZc92Ww6FE7lFC7vl0Ukdrbt 1QgvlZZ55kq0OxU3ZwABUU/FRPqFhMREhK2KXJonrPuM20xCJj9g1jMwHsvK1m4OHw BIhfPhMUqunH/g5XgfwwJXUNlUkWBwipAyKuiuXs=
Received: from resistance.greenbytes.local (unknown [217.91.35.233]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail.greenbytes.de (Postfix) with ESMTPSA id 7342815A0221; Fri,  7 Jul 2017 13:44:19 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=greenbytes.de; s=mail; t=1499427859; bh=0mXG+i6vAshXeCMWrnXN6xMGBPErEjzMWIY/WYLK54w=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=MQie0i0taoJuO8AHwqH4QtSVOXq1oO0KNeiBaUttj8PPlqW+QRX6lH6e/eZg7ubT+ 5RBpMqFyR1PIi9Z7xNZUze+f7M10/GN1RckvM9S/IR3FICTflHyb9IcCVFJkNGlr7W HwyePHYRaNE9g/RL5nocMirsktNtyujtlfJUppIU=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Secdir last call review of draft-ietf-httpbis-early-hints-03
From: Stefan Eissing <stefan.eissing@greenbytes.de>
In-Reply-To: <CANatvzygATN6Rd7nGPuGLSpbYs65TV01BFMFrB9Atq1ojcXHJQ@mail.gmail.com>
Date: Fri, 7 Jul 2017 13:44:19 +0200
Cc: Willy Tarreau <w@1wt.eu>, Melinda Shore <melinda.shore@gmail.com>, secdir@ietf.org, draft-ietf-httpbis-early-hints.all@ietf.org, IETF Discussion Mailing List <ietf@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <AA1F7609-89D8-4199-AFF7-8880637DFF01@greenbytes.de>
References: <149919703750.15996.5462759432298024921@ietfa.amsl.com> <CANatvzx8GsvoYMscHciKNrOwRzcz1v7=jTCUUp4Z5E=jO9Wd6g@mail.gmail.com> <7273f8ab-c1ff-5dff-862e-0a1ead6d28b2@gmail.com> <20170707092316.GA27560@1wt.eu> <CANatvzygATN6Rd7nGPuGLSpbYs65TV01BFMFrB9Atq1ojcXHJQ@mail.gmail.com>
To: Kazuho Oku <kazuhooku@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/B6j4uHkmAQS8NjOg6DAkUYZ5Ycs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 11:44:25 -0000

I am not a big fan of "MUST not use protocol features if it is known not =
to work" advise.

> Am 07.07.2017 um 13:29 schrieb Kazuho Oku <kazuhooku@gmail.com>:
>=20
> 2017-07-07 18:23 GMT+09:00 Willy Tarreau <w@1wt.eu>:
>> On Fri, Jul 07, 2017 at 05:54:41AM +0000, Melinda Shore wrote:
>>> On 7/6/17 8:40 PM, Kazuho Oku wrote:
>>>> Regarding the wording, I think it would be better to keep the tone
>>>> as-is, rather than suggesting implementers not to send an Early =
Hints
>>>> response over HTTP/1.1 depending on the client.
>>>=20
>>> Yeah, you don't want to discourage implementation.  I think
>>> the goal is to find some balance between not putting off
>>> implementers on the one hand, and having to deal with an
>>> embarrassing incident on the other.  I'd be more comfortable
>>> with language that's a bit stronger but it's not a huge
>>> issue, certainly not one that's an impediment to moving the
>>> document forward (particularly given that it's intended for
>>> publication as an experimental standard).
>>=20
>> I'm just thinking about the fact that we're not even sure that any
>> HTTP/1.1 client doesn't support these informational responses,
>> because such clients can already make use of Expect: 100-continue
>> (so they know about 100), and if I remember well when designing the
>> 101 upgrade for WebSocket, which was reused for HTTP/2, some of
>> the difficulties we faced was that some clients/intermediaries
>> were consuming 101 as 1xx and waiting for a final response after
>> it.
>>=20
>> Maybe the stronger wording should be oriented differently, such as
>> "Servers MUST not send 103 to HTTP/1.0 clients nor to any client
>> known not to support 1xx informational responses" ? This way it
>> leaves the possibility opened (ie rely on version and/or user-agent
>> or anything else once an exception is known).
>=20
> Considering that this is merely an advice on how to deal with broken
> clients, I think that we should not use the verbs defined in RFC 2119
> or state a strong prohibition.
>=20
> I also believe that a whitelist-based approach will be a better choice
> than a blacklist-based one, since 103 is an optimization that is
> beneficial when sent to a client that is known to make use of it. For
> most websites, whitelisting the major browsers that support it (once
> they do) or the CDN they use will be enough to get the most out of the
> status code.
>=20
>> Just my two cents,
>> Willy
>=20
>=20
>=20
> --=20
> Kazuho Oku
>=20


From nobody Fri Jul  7 04:56:11 2017
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6CA612EAAA; Fri,  7 Jul 2017 04:56:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, 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 R9y5Jy3OsUAw; Fri,  7 Jul 2017 04:56:07 -0700 (PDT)
Received: from 1wt.eu (wtarreau.pck.nerim.net [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 7EDE4129AD2; Fri,  7 Jul 2017 04:56:07 -0700 (PDT)
Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id v67Bu1EG027915; Fri, 7 Jul 2017 13:56:01 +0200
Date: Fri, 7 Jul 2017 13:56:01 +0200
From: Willy Tarreau <w@1wt.eu>
To: Kazuho Oku <kazuhooku@gmail.com>
Cc: Melinda Shore <melinda.shore@gmail.com>, secdir@ietf.org, draft-ietf-httpbis-early-hints.all@ietf.org, IETF Discussion Mailing List <ietf@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Subject: Re: Secdir last call review of draft-ietf-httpbis-early-hints-03
Message-ID: <20170707115601.GB27560@1wt.eu>
References: <149919703750.15996.5462759432298024921@ietfa.amsl.com> <CANatvzx8GsvoYMscHciKNrOwRzcz1v7=jTCUUp4Z5E=jO9Wd6g@mail.gmail.com> <7273f8ab-c1ff-5dff-862e-0a1ead6d28b2@gmail.com> <20170707092316.GA27560@1wt.eu> <CANatvzygATN6Rd7nGPuGLSpbYs65TV01BFMFrB9Atq1ojcXHJQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CANatvzygATN6Rd7nGPuGLSpbYs65TV01BFMFrB9Atq1ojcXHJQ@mail.gmail.com>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9KMlg3WxZn1zmBxXkxgpxQ2E_zw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 11:56:10 -0000

On Fri, Jul 07, 2017 at 08:29:36PM +0900, Kazuho Oku wrote:
> I also believe that a whitelist-based approach will be a better choice
> than a blacklist-based one, since 103 is an optimization that is
> beneficial when sent to a client that is known to make use of it. For
> most websites, whitelisting the major browsers that support it (once
> they do) or the CDN they use will be enough to get the most out of the
> status code.

OK. That was just a proposal :-)

Willy


From nobody Fri Jul  7 06:07:20 2017
Return-Path: <bruno.decraene@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7136F1201F2; Fri,  7 Jul 2017 06:07:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level: 
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 gK8K-IhfazPZ; Fri,  7 Jul 2017 06:07:16 -0700 (PDT)
Received: from relais-inet.orange.com (mta239.mail.business.static.orange.com [80.12.66.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34060131444; Fri,  7 Jul 2017 06:07:12 -0700 (PDT)
Received: from opfedar07.francetelecom.fr (unknown [xx.xx.xx.9]) by opfedar23.francetelecom.fr (ESMTP service) with ESMTP id C109516024B; Fri,  7 Jul 2017 15:07:10 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.31]) by opfedar07.francetelecom.fr (ESMTP service) with ESMTP id 71AABC0081; Fri,  7 Jul 2017 15:07:10 +0200 (CEST)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILM22.corporate.adroot.infra.ftgroup ([fe80::8c90:f4e9:be28:2a1%19]) with mapi id 14.03.0352.000; Fri, 7 Jul 2017 15:07:10 +0200
From: <bruno.decraene@orange.com>
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, Pete Resnick <presnick@qti.qualcomm.com>
CC: "gen-art@ietf.org" <gen-art@ietf.org>, "spring@ietf.org" <spring@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-spring-oam-usecase.all@ietf.org" <draft-ietf-spring-oam-usecase.all@ietf.org>
Subject: RE: Genart last call review of draft-ietf-spring-oam-usecase-06
Thread-Topic: Genart last call review of draft-ietf-spring-oam-usecase-06
Thread-Index: AQHS8DzDWIhR6rTu8UG+oA8joThdh6JBQjKAgAceyfA=
Date: Fri, 7 Jul 2017 13:07:09 +0000
Message-ID: <5238_1499432830_595F877E_5238_249_1_53C29892C857584299CBF5D05346208A477F5711@OPEXCLILM21.corporate.adroot.infra.ftgroup>
References: <149867468440.7527.6305996146978005032@ietfa.amsl.com> <FFB75186-880F-4288-9DCB-19CF1D666939@cisco.com>
In-Reply-To: <FFB75186-880F-4288-9DCB-19CF1D666939@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
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/ietf/P5_RcejT0Yc8bAi4cCpF3SJ5vng>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 13:07:18 -0000

SGkgUGV0ZSwgQ2FybG9zLA0KDQo+IEZyb206IENhcmxvcyBQaWduYXRhcm8gKGNwaWduYXRhKSBb
bWFpbHRvOmNwaWduYXRhQGNpc2NvLmNvbV0gID4gU2VudDogU3VuZGF5LCBKdWx5IDAyLCAyMDE3
IDEwOjE0IFBNDQo+IA0KID4gSGksIFBldGUsDQogPiANCiA+IE1hbnkgdGhhbmtzIGZvciB0aGUg
dGltZSB0byByZWFkIGFuZCByZXZpZXcgdGhpcyBkb2N1bWVudCENCiA+IA0KID4gTGlrZSBSdWVk
aWdlciwgSSB3aWxsIGxldCB0aGUgc2hlcGhlcmQsIGNoYWlycywgYW5kIEFEIHdlaWdodCBpbiDi
gJQgYnV0IGluIHRoZSBtZWFudGltZSwgSQ0KID4gd2FudGVkIHRvIG9mZmVyIGEgY291cGxlIG9m
IG9ic2VydmF0aW9ucyBmb3IgY29uc2lkZXJhdGlvbi4gUGxlYXNlIHNlZSBpbmxpbmUuDQogPiAN
CiA+IA0KID4gPiBPbiBKdW4gMjgsIDIwMTcsIGF0IDI6MzEgUE0sIFBldGUgUmVzbmljayA8cHJl
c25pY2tAcXRpLnF1YWxjb21tLmNvbT4gd3JvdGU6DQogPiA+DQogPiA+IFJldmlld2VyOiBQZXRl
IFJlc25pY2sNCiA+ID4gUmV2aWV3IHJlc3VsdDogTm90IFJlYWR5DQogPiA+DQogPiA+IEkgYW0g
dGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIFRoZSBHZW5lcmFs
IEFyZWENCiA+ID4gUmV2aWV3IFRlYW0gKEdlbi1BUlQpIHJldmlld3MgYWxsIElFVEYgZG9jdW1l
bnRzIGJlaW5nIHByb2Nlc3NlZA0KID4gPiBieSB0aGUgSUVTRyBmb3IgdGhlIElFVEYgQ2hhaXIu
ICBQbGVhc2UgdHJlYXQgdGhlc2UgY29tbWVudHMganVzdA0KID4gPiBsaWtlIGFueSBvdGhlciBs
YXN0IGNhbGwgY29tbWVudHMuDQogPiA+DQogPiA+IEZvciBtb3JlIGluZm9ybWF0aW9uLCBwbGVh
c2Ugc2VlIHRoZSBGQVEgYXQNCiA+ID4NCiA+ID4gPGh0dHBzOi8vdHJhYy5pZXRmLm9yZy90cmFj
L2dlbi93aWtpL0dlbkFydGZhcT4uDQogPiA+DQogPiA+IERvY3VtZW50OiBkcmFmdC1pZXRmLXNw
cmluZy1vYW0tdXNlY2FzZS0wNg0KID4gPiBSZXZpZXdlcjogUGV0ZSBSZXNuaWNrDQogPiA+IFJl
dmlldyBEYXRlOiAyMDE3LTA2LTI4DQogPiA+IElFVEYgTEMgRW5kIERhdGU6IDIwMTctMDYtMzAN
CiA+ID4gSUVTRyBUZWxlY2hhdCBkYXRlOiBOb3Qgc2NoZWR1bGVkIGZvciBhIHRlbGVjaGF0DQog
PiA+DQogPiA+IFN1bW1hcnk6IE5vdCBSZWFkeSBmb3IgcHVibGljYXRpb24gYXMgSW5mb3JtYXRp
b25hbCwgYnV0IG1pZ2h0IGJlIFJlYWR5IGZvcg0KID4gPiBwdWJsaWNhdGlvbiBhcyBQcm9wb3Nl
ZCBTdGFuZGFyZA0KID4gPg0KID4gPiBNYWpvciBpc3N1ZXM6DQogPiA+DQogPiA+IFRoaXMgaXMg
YW4gYWRtaXR0ZWRseSB1bnVzdWFsIHJldmlldy4gSSBoYXZlIHJlYWQgdGhyb3VnaCB0aGUgZW50
aXJlIGRvY3VtZW50LA0KID4gPiBhbmQgdGhlIHRlY2huaWNhbCB3b3JrIHNlZW1zIGZpbmUsIGJ1
dCBpcyB3ZWxsIGJleW9uZCBteSB0ZWNobmljYWwgZXhwZXJ0aXNlLA0KID4gPiBzbyBJIGNhbid0
IHJlYWxseSBjb21tZW50IG9uIHRoZSB0ZWNobmljYWwgY29ycmVjdG5lc3MuIEhvd2V2ZXIsIGl0
IGlzDQogPiA+IGFic29sdXRlbHkgY2xlYXIgdG8gbWUgdGhhdCB0aGlzIGlzICpub3QqIGEgInVz
ZSBjYXNlIiBkb2N1bWVudCBhdCBhbGwNCiA+IA0KID4gSSBhZ3JlZSB3aXRoIHRoZSBhc3Nlc3Nt
ZW50IHRoYXQgdGhpcyBpcyBub3QgYSDigJx1c2UtY2FzZeKAnSBkb2N1bWVudCAoaW4gYSBzdHJp
Y3Qgb3IgdHJhZGl0aW9uYWwNCiA+IHNlbnNlKTsgdGhpcyBkb2N1bWVudCBkZXNjcmliZXMgYSBk
ZXBsb3ltZW50IGNhc2UgYW5kIGEgc29sdXRpb24gdG8gYSB1c2UgY2FzZSwgdXNpbmcNCiA+IGV4
aXN0aW5nIHRlY2hub2xvZ3kgYmxvY2tzLiBJdCBkb2VzIG5vdCBkZWZpbmUgbmV3IHByb3RvY29s
IG5vciAobW9yZSBpbXBvcnRhbnRseSkgY3JlYXRlcw0KID4gaW50ZXJvcGVyYWJpbGl0eSBjb25z
aWRlcmF0aW9ucy4NCg0KQXMgdGhlIGRvYyBzaGVwaGVyZCwgSSBhZ3JlZSB0aGF0IHRoaXMgZG9j
dW1lbnQgaXMgbW9yZSB0aGFuIGEgdXNlIGNhc2UgYW5kIGRlc2NyaWJlcyBib3RoIGEgdXNlIGNh
c2UgKHNlY3Rpb25zIDEsIDQpIGFuZCBhIG1vbml0b3Jpbmcgc3lzdGVtIChzZWN0aW9ucyAzIGFu
ZCA2IHRvIDgpLiBBbmQgdGhlcmUgaXMgZXZlbiBhbiBpbXBsZW1lbnRhdGlvbiByZXBvcnQ6IGh0
dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1sZWlwbml0ei1zcHJpbmctcG1zLWltcGxl
bWVudGF0aW9uLXJlcG9ydC0wMA0KDQpIb3dldmVyLCB0aGUgc29sdXRpb24gcmVsYXRlZCBwYXJ0
IGRvZXMgbm90IHJlcXVpcmUgc3RhbmQgdHJhY2sgZG9jdW1lbnQgYXMgaXQgcnVucyBhcyBhIHN0
YW5kYWxvbmUgZGV2aWNlIHdpdGggbm8gbmVlZCBmb3IgaW50ZXJvcGVyYWJpbGl0eS4gSW5kZWVk
LCB0aGUgc29sdXRpb24gbGV2ZXJhZ2VzIFNlZ21lbnQgUm91dGluZy9TUFJJTkcgc28gdGhhdCBh
IHVuaXF1ZSBub2RlIGlzIHVzZWQgYXMgYm90aCB0aGUgc2VuZGVyIGFuZCB0aGUgcmVjZWl2ZXIu
IEFzIHN1Y2gsIHRoZSBzeXN0ZW0gaXMgZnJlZSB0byB1c2UgYW55IE9BTSBwcm90b2NvbC9wYWNr
ZXQgZm9ybWF0IHdpdGggbm8gaW50ZXJvcGVyYWJpbGl0eSBjb25zaWRlcmF0aW9uLiBJdCBsb29r
cyB0byBtZSB0aGF0IHN1Y2ggZnJlZWRvbSBpcyBwYXJ0IG9mIHRoaXMgUGF0aCBNb25pdG9yaW5n
IFN5c3RlbSB1c2UgY2FzZS9zeXN0ZW0uDQpQbHVzLCBJIGZlYXIgdGhhdCBtb3ZpbmcgdG8gc3Rh
bmRhcmQgdHJhY2sgd291bGQgbWVhbiBjaGFuZ2luZyB0aGUgZG9jdW1lbnQgaW50byBhIHByZWNp
c2Ugc3BlY2lmaWNhdGlvbiAoZS5nLiB3aGljaCBPQU0gdG9vbChzKSB0byB1c2UgYW5kIHRoZSB3
YXkgdG8gdXNlIHRoZW0pIHdoaWNoIHdhcyBub3QgdGhlIGdvYWwsIG1heSByZXF1aXJlIHNpZ25p
ZmljYW50IHdvcmsgYW5kIGRlbGF5LCBhbmQgbWF5IGV2ZW4gYmUgc3Vib3B0aW1hbCBpbiByZW1v
dmluZyBmcmVlZG9tLg0KDQpUTDtEUjogT24gbXkgc2lkZSwgSSBkb24ndCBmZWVsIHRoYXQgdGhl
IGRvY3VtZW50IG5lZWRzIHRvIGJlIHN0YW5kYXJkIHRyYWNrLiBCdXQgSSBndWVzcyB0aGF0IHVs
dGltYXRlbHkgdGhlIGRlY2lzaW9uIGlzIG9uIHRoZSBBRC9JRVNHIHNpZGUuDQoNClRoYW5rcywN
Ci0tQnJ1bm8NCiANCiA+ID4gYW5kIEkNCiA+ID4gZG9uJ3QgdGhpbmsgaXQncyBhcHByb3ByaWF0
ZSBhcyBhbiBJbmZvcm1hdGlvbmFsIGRvY3VtZW50Lg0KID4gDQogPiBOb3csIHJlZ2FyZGluZyB0
aGUgbW9zdCBhcHByb3ByaWF0ZSBpbnRlbmRlZCBzdGF0dXMsIEkgY291bGQgcGVyc29uYWxseSBh
cmd1ZSBib3RoIHNpZGVzLA0KID4gYW5kIGZyYW5rbHksIEkgZG8gbm90IGhhdmUgYSBzdHJvbmcg
cHJlZmVyZW5jZSBvciBjb25jZXJuIGVpdGhlciB3YXkuDQogPiANCiA+IFRoZSBuZXQgb2YgaXQg
aXMgdGhhdCB0aGlzIChpbmZvcm1hdGlvbmFsL3NwZWNpZmljYXRpb24pIGRvY3VtZW50IGRvZXMg
bm90IGNyZWF0ZQ0KID4gcmVxdWlyZW1lbnRzIGZvciBTUFJJTkcgbm9kZXMsIGNoYW5nZXMgaW4g
U1BSSU5HLCBub3IgZXhwb3NlcyBpbnRlcm9wZXJhYmlsaXR5IGlzc3Vlcy4gSXQNCiA+IGJhc2lj
YWxseSBsZXZlcmFnZXMgYXMtaXMgdGhlIHVuZGVybHlpbmcgY2FwYWJpbGl0aWVzIGNyZWF0ZWQg
d2l0aCBTUFJJTkcuIEZyb20gdGhhdCBhbmdsZSwNCiA+IEluZm9ybWF0aW9uYWwgaXMgYSB2ZXJ5
IGFwcHJvcHJpYXRlIGZpdC4gT24gdGhlIG90aGVyIGhhbmQsIEkgZG8gbm90IGRpc2FncmVlIHdp
dGggdGhpcw0KID4gZG9jdW1lbnQgc3BlY2lmeWluZyBhIHN5c3RlbSwgYW5kIHRoZSBwbGF5LW9m
LXdvcmRzIHRoYXQgcmVzdWx0cyBpbiBzdGFuZGFyZHMtdHJhY2sg4oCUIHNvDQogPiBpdCBpcyBh
IHNwZWMgZm9yIHRoZSBwYXRoIG1vbml0b3Jpbmcgc3lzdGVtLCBidXQgcHJvdmlkZXMgaW5mb3Jt
YXRpb24gdG8gdGhlIG5ldHdvcmsgYW5kIHRvDQogPiBTUFJJTkcgc3BlY3Mgb24gaG93IHRoZSBu
ZXcgdGVjaCBjYW4gYmUgdXNlZC4NCiA+IA0KID4gTmV0LW5ldCwgSSBzZWUgSW5mb3JtYXRpb25h
bCBidXQgY2FuIHVuZGVyc3RhbmQgeW91ciByYXRpb25hbGUuDQogPiANCiA+IEluIGFueSBjYXNl
LCB3aGF0IGRvZXMgY29uY2VybiBtZSBtb3JlIGlzIHdoZXRoZXIgYSBwb3RlbnRpYWwgY2hhbmdl
IG9mIGludGVuZGVkIHN0YXR1cw0KID4gd291bGQgYWRkIHNpZ25pZmljYW50IGRlbGF5IGFuZCBy
ZXNldCBwcm9jZXNzIHRpbWVycyBvbiBhIHRpbWVsaW5lIHRoYXQgaXMgYWxyZWFkeQ0KID4gb3Zl
cnN0cmV0Y2hlZCBhbmQgYSB2ZXJ5IHNsb3cgcHJvZ3Jlc3PigKYNCiA+IA0KID4gPiBUaGlzIGlz
IGNsZWFybHkgYQ0KID4gPiAqc3BlY2lmaWNhdGlvbiogb2YgYSBwYXRoIG1vbml0b3Jpbmcgc3lz
dGVtLiBJdCBnaXZlcyBndWlkYW5jZXMgYXMgdG8gcmVxdWlyZWQsDQogPiA+IHJlY29tbWVuZGVk
LCBhbmQgb3B0aW9uYWwgcGFyYW1ldGVycywgYW5kIHNwZWNpZmllcyBob3cgdG8gdXNlIGRpZmZl
cmVudA0KID4gPiBwcm90b2NvbCBwaWVjZXMuIEl0IGlzIGF0IHRoZSB2ZXJ5IGxlYXN0IHdoYXQg
UkZDIDIwMjYgcmVmZXJzIHRvIGFzIGFuDQogPiA+ICJBcHBsaWNhYmlsaXR5IFN0YXRlbWVudCAo
QVMpIiAoc2VlIFJGQyAyMDI2LCBzZWMuIDMuMikuIEl0ICptaWdodCogYmUgYSBCQ1AsDQogPiA+
IGJ1dCBpdCBpcyBub3Qgc3RyaWN0bHkgZ2l2aW5nICJjb21tb24gZ3VpZGVsaW5lcyBmb3IgcG9s
aWNpZXMgYW5kIG9wZXJhdGlvbnMiDQogPiA+ICgyMDI2LCBzZWMuIDUpLCBzbyBJIGRvbid0IHJl
YWxseSB0aGluayB0aGF0J3MgcmlnaHQsIGFuZCBpbnN0ZWFkIHRoaXMgc2hvdWxkDQogPiA+IGJl
IG9mZmVyZWQgZm9yIFByb3Bvc2VkIFN0YW5kYXJkLiBFaXRoZXIgd2F5LCBJIHRoaW5rIEluZm9y
bWF0aW9uYWwgaXMgbm90DQogPiA+IGNvcnJlY3QuIEltcG9ydGFudGx5LCBJIHRoaW5rIHRoZXJl
IGlzIGEgZ29vZCBsaWtlbGlob29kIHRoYXQgdGhpcyBkb2N1bWVudCBoYXMNCiA+ID4gbm90IHJl
Y2VpdmVkIHRoZSBhcHByb3ByaWF0ZSBhbW91bnQgb2YgcmV2aWV3OyBwZW9wbGUgdGVuZCB0byBp
Z25vcmUNCiA+ID4gSW5mb3JtYXRpb25hbCAidXNlIGNhc2UiIGRvY3VtZW50cywNCiA+IA0KID4g
VGhpcywgaG93ZXZlciwgSSB0aGluayBpcyBhbiBpbmFwcHJvcHJpYXRlIGV4dHJhcG9sYXRpb24u
IEFsdGhvdWdoIHRoZSBzaGVwaGVyZCwgV0cgYW5kDQogPiBjaGFpcnMgYWxyZWFkeSBjb25zaWRl
cmVkIHRoZSBpbnRlbmRlZCBzdGF0dXMsIEkgdGhpbmsgaXQgaXMgaW1wb3J0YW50IHRvIHJlLXRo
aW5rIHdoYXTigJlzIGJlc3QNCiA+IGZvciB0aGlzIGRvY3VtZW50IGluIHRoZSBjb250ZXh0IG9m
IHRoZSBtZXJpdHMsIHN0cnVjdHVyZSBhbmQgZ29hbHMuIEJ1dCBqdXN0aWZ5aW5nIGl0IG5vdA0K
ID4gYmVpbmcgaW5mb3JtYXRpb25hbCBiZWNhdXNlIOKAnHBlb3BsZSB0ZW5kIHRvIGlnbm9yZSBb
4oCmXeKAnSBzZWVtcyBhIHJlZCBoZXJyaW5nLg0KID4gDQogPiA+IGFuZCB0aGVyZSBoYXZlIGJl
ZW4gbm8gTGFzdCBDYWxsIGNvbW1lbnRzDQogPiA+IGJleW9uZCBKb2VsJ3MgUlRHIEFyZWEgUmV2
aWV3Lg0KID4gDQogPiBXaXRoaW4gU1BSSU5HLCB0aGlzIGRvY3VtZW50IGRhdGVzIHRoZSBvcmln
aW5zIG9mIHRoZSBXRy4gSXQgd2FzIHByZXNlbnRlZCBpbiBtYW55IFdHcw0KID4gbnVtZXJvdXMg
dGltZXMgYW5kIGl0ZXJhdGVkIHRocm91Z2ggbWFueSB2ZXJzaW9ucyAod2l0aGluIHRocmVlIGZp
bGVuYW1lcykgYXMgdmFyaW91cw0KID4gcmV2aWV3cyBjYW1lIGluLiBJ4oCZZCByZWNvbW1lbmQg
eW91IGFsc28gZ28gYmFjayBhbmQgY2hlY2sgdGhlIHRpbWVsaW5lLiBJIHdvdWxkIG5vdCBhbHNv
DQogPiBtYWtlIGhhcmQgY29uY2x1c2lvbnMgYmFzZWQgb24gTEMgdHJhZmZpYy4NCiA+IA0KID4g
PiBFdmVuIGluIElFU0cgcmV2aWV3LCBhbiBJbmZvcm1hdGlvbmFsIGRvY3VtZW50DQogPiA+IG9u
bHkgdGFrZXMgdGhlIHNwb25zb3JpbmcgQUQgdG8gYXBwcm92ZTsgZXZlcnkgb3RoZXIgQUQgY2Fu
IHN1bW1hcmlseSBpZ25vcmUNCiA+ID4gdGhlIGRvY3VtZW50LCBvciBldmVuIGJhbGxvdCBBQlNU
QUlOLCBhbmQgdGhlIGRvY3VtZW50IHdpbGwgc3RpbGwgYmUgcHVibGlzaGVkDQogPiA+ICh0aG91
Z2ggdGhhdCBkb2VzIG5vdCBub3JtYWxseSBoYXBwZW4pLiBUaGlzIGRvY3VtZW50IHNob3VsZCBo
YXZlIG11Y2ggbW9yZQ0KID4gPiB0aGFuIHRoYXQgbGV2ZWwgb2YgcmV2aWV3LiBJIHN0cm9uZ2x5
IHJlY29tbWVuZCB0byB0aGUgV0cgYW5kIEFEIHRoYXQgdGhpcw0KID4gPiBkb2N1bWVudCBiZSB3
aXRoZHJhd24gYXMgYW4gSW5mb3JtYXRpb25hbCBkb2N1bWVudCBhbmQgcmVzdWJtaXR0ZWQgZm9y
IFByb3Bvc2VkDQogPiA+IFN0YW5kYXJkIGFuZCBoYXZlIHRoYXQgbGV2ZWwgb2YgcmV2aWV3IGFu
ZCBzY3J1dGlueSBhcHBsaWVkIHRvIGl0Lg0KID4gDQogPiBBcyBJIHNhaWQsIEkgYW0gaGFwcHkg
d2l0aCBlaXRoZXIgc3RhdHVzIGFuZCBjYW4gc2VlIGFyZ3VtZW50cyBib3RoIHdheXMuIEkgd291
bGQgbm90DQogPiBvYmplY3QgdG8gYSBjaGFuZ2UuDQogPiANCiA+IEhvd2V2ZXIsIHBlcnNvbmFs
bHksIEkgZG8gbm90IHNlZSB0aGUgbmVlZC4NCiA+IA0KID4gPg0KID4gPiBNaW5vciBpc3N1ZXM6
DQogPiA+DQogPiA+IE5vbmUuDQogPiA+DQogPiA+IE5pdHMvZWRpdG9yaWFsIGNvbW1lbnRzOg0K
ID4gPg0KID4gPiBUaGlzIGRvY3VtZW50IHJlZmVycyB0byBSRkMgNDM3OSwgd2hpY2ggaGFzIGJl
ZW4gb2Jzb2xldGVkIGJ5IFJGQyA4MDI5LiBJdA0KID4gPiBzZWVtcyBsaWtlIHRoZSByZWZlcmVu
Y2VzIHNob3VsZCBiZSB1cGRhdGVkLg0KID4gPg0KID4gPg0KID4gDQogPiBJbmRlZWQuIERvbmUg
aW4gLTA3IGFuZCAtMDguDQogPiANCiA+IFRoYW5rcyBhZ2FpbiwgUGV0ZSENCiA+IA0KID4g4oCU
DQogPiBDYXJsb3MgUGlnbmF0YXJvLCBjYXJsb3NAY2lzY28uY29tDQogPiANCiA+IOKAnFNvbWV0
aW1lcyBJIHVzZSBiaWcgd29yZHMgdGhhdCBJIGRvIG5vdCBmdWxseSB1bmRlcnN0YW5kLCB0byBt
YWtlIG15c2VsZiBzb3VuZCBtb3JlDQogPiBwaG90b3N5bnRoZXNpcy4iDQoNCgpfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCgpD
ZSBtZXNzYWdlIGV0IHNlcyBwaWVjZXMgam9pbnRlcyBwZXV2ZW50IGNvbnRlbmlyIGRlcyBpbmZv
cm1hdGlvbnMgY29uZmlkZW50aWVsbGVzIG91IHByaXZpbGVnaWVlcyBldCBuZSBkb2l2ZW50IGRv
bmMKcGFzIGV0cmUgZGlmZnVzZXMsIGV4cGxvaXRlcyBvdSBjb3BpZXMgc2FucyBhdXRvcmlzYXRp
b24uIFNpIHZvdXMgYXZleiByZWN1IGNlIG1lc3NhZ2UgcGFyIGVycmV1ciwgdmV1aWxsZXogbGUg
c2lnbmFsZXIKYSBsJ2V4cGVkaXRldXIgZXQgbGUgZGV0cnVpcmUgYWluc2kgcXVlIGxlcyBwaWVj
ZXMgam9pbnRlcy4gTGVzIG1lc3NhZ2VzIGVsZWN0cm9uaXF1ZXMgZXRhbnQgc3VzY2VwdGlibGVz
IGQnYWx0ZXJhdGlvbiwKT3JhbmdlIGRlY2xpbmUgdG91dGUgcmVzcG9uc2FiaWxpdGUgc2kgY2Ug
bWVzc2FnZSBhIGV0ZSBhbHRlcmUsIGRlZm9ybWUgb3UgZmFsc2lmaWUuIE1lcmNpLgoKVGhpcyBt
ZXNzYWdlIGFuZCBpdHMgYXR0YWNobWVudHMgbWF5IGNvbnRhaW4gY29uZmlkZW50aWFsIG9yIHBy
aXZpbGVnZWQgaW5mb3JtYXRpb24gdGhhdCBtYXkgYmUgcHJvdGVjdGVkIGJ5IGxhdzsKdGhleSBz
aG91bGQgbm90IGJlIGRpc3RyaWJ1dGVkLCB1c2VkIG9yIGNvcGllZCB3aXRob3V0IGF1dGhvcmlz
YXRpb24uCklmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgZW1haWwgaW4gZXJyb3IsIHBsZWFzZSBu
b3RpZnkgdGhlIHNlbmRlciBhbmQgZGVsZXRlIHRoaXMgbWVzc2FnZSBhbmQgaXRzIGF0dGFjaG1l
bnRzLgpBcyBlbWFpbHMgbWF5IGJlIGFsdGVyZWQsIE9yYW5nZSBpcyBub3QgbGlhYmxlIGZvciBt
ZXNzYWdlcyB0aGF0IGhhdmUgYmVlbiBtb2RpZmllZCwgY2hhbmdlZCBvciBmYWxzaWZpZWQuClRo
YW5rIHlvdS4KCg==


From nobody Fri Jul  7 06:32:44 2017
Return-Path: <dave@davecake.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4C88127B73; Fri,  7 Jul 2017 06:32:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.106
X-Spam-Level: 
X-Spam-Status: No, score=-1.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, 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 GQLYnXr00x1M; Fri,  7 Jul 2017 06:32:34 -0700 (PDT)
Received: from agwe.difference.com.au (unknown [103.4.235.78]) by ietfa.amsl.com (Postfix) with ESMTP id 4EFD8129B10; Fri,  7 Jul 2017 06:32:34 -0700 (PDT)
Received: from [192.168.0.195] (unknown [1.126.11.186]) by agwe.difference.com.au (Postfix) with ESMTPSA id E03DD154058; Fri,  7 Jul 2017 23:32:30 +1000 (AEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [DNSOP] new DNS classes
From: David Cake <dave@davecake.net>
In-Reply-To: <m2mv8jw9qq.wl-randy@psg.com>
Date: Fri, 7 Jul 2017 15:32:21 +0200
Cc: Paul Vixie <paul@redbarn.org>, dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <33235E8D-147D-4178-BC45-DFC1E1C27B99@davecake.net>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <m2mv8jw9qq.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LQEN1vovlRU-lktuRqHy4r6fHg4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 13:32:37 -0000

If you have a single centralised root for your new class, you will =
probably either recreate the problems of ICANN, or create one or more of =
the problems that ICANN has very consciously tried to avoid.
If you have a system of name resolution that avoids the need for a =
centralised root, you probably don=E2=80=99t need a new class to =
implement it.=20
The few marginal cases that need to interact with the one root but not =
be ICANN controlled are why we have the RFC 6761 process.=20

I agree a taxa of needs that do not fit within those three cases would =
have been useful.=20

David


> On 5 Jul 2017, at 10:47 am, Randy Bush <randy@psg.com> wrote:
>=20
> i think avoiding icann is a red herring.  if the draft in question had
> done a decent job of exploring the taxa of needs for name resolution
> outside of the 'normal' topology, we would have the start of a base on
> which to discuss this.
>=20
> randy
>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


From nobody Fri Jul  7 08:09:46 2017
Return-Path: <paul@redbarn.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC1CF131636; Fri,  7 Jul 2017 08:09:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, 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 pLNCyiHikIgJ; Fri,  7 Jul 2017 08:09:35 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 681AB131610; Fri,  7 Jul 2017 08:09:35 -0700 (PDT)
Received: from [10.170.78.140] (adsl-70-234-237-173.dsl.rcsntx.sbcglobal.net [70.234.237.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 9209C61FF3; Fri,  7 Jul 2017 15:09:34 +0000 (UTC)
Message-ID: <595FA42A.7050604@redbarn.org>
Date: Fri, 07 Jul 2017 08:09:30 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.15 (Windows/20170609)
MIME-Version: 1.0
To: Nico Williams <nico@cryptonector.com>
CC: Mark Andrews <marka@isc.org>, John C Klensin <john-ietf@jck.com>,  dnsop <dnsop@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>,  IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: new DNS classes
References: <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <CAMm+Lwjd6xVp-EDp=doevx=AP8qws_Mv++aL733yHEyUF72EMA@mail.gmail.com> <562EC659F89FA92A09CAC4DB@PSB> <20170706153955.GB3393@localhost> <20170706215236.99A8C7DB2FBA@rock.dv.isc.org> <20170707055315.GC3393@localhost>
In-Reply-To: <20170707055315.GC3393@localhost>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nGoB8u-5NkM0iTr_uPwVSa2paDA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 15:09:36 -0000

Nico Williams wrote:
> ...
>
> I'm well aware that as to clients and servers, deploying new RR types is
> easy.  The hard part is the management backend and UIs.  Not all of them
> allow you to enter raw RDATA (hex-encoded or whatever).
>
> We've struggled with this in KITTEN WG.  Deploying the URI RR type when
> you're using a hosting service can be anywhere from annoying (must enter
> raw RDATA) to impossible (the hosting service doesn't give a damn).  I
> suppose it's just a matter of time; perhaps things have improved since
> we last looked.

that would be a prior restraint, and bad for innovation. just like 
middle boxes or the nearly universal assumption that ip means tcp or 
udp. i know this kind of thinking is common. but there is a stark choice 
for all of us: do all of our future protocol work on tcp/80 and make 
everything fit in JSON, so that we can get our work done; or keep doing 
what the internet used to mean, and eventually put enough stress on 
middle box makers, isp's, and in your case dns hosting services, that 
they have to learn about the internet rather than just the web.

i know which future i'd rather live in. i also feel in-year pressure to 
get my work done. i vacillate as to who gets to receive which burdens.

-- 
P Vixie


From nobody Fri Jul  7 09:35:20 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 382891316BB; Fri,  7 Jul 2017 09:35:18 -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_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5] 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 MA1RWBtj8wMD; Fri,  7 Jul 2017 09:35:16 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E76E1316B2; Fri,  7 Jul 2017 09:35:16 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTP id DAED8C086D10; Fri,  7 Jul 2017 09:35:15 -0700 (PDT)
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTPSA id 51E03C086D08; Fri,  7 Jul 2017 09:35:15 -0700 (PDT)
Date: Fri, 7 Jul 2017 11:35:13 -0500
From: Nico Williams <nico@cryptonector.com>
To: Mark Andrews <marka@isc.org>
Cc: John C Klensin <john-ietf@jck.com>, dnsop <dnsop@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>, Paul Vixie <paul@redbarn.org>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: new DNS classes
Message-ID: <20170707163511.GD3393@localhost>
References: <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <CAMm+Lwjd6xVp-EDp=doevx=AP8qws_Mv++aL733yHEyUF72EMA@mail.gmail.com> <562EC659F89FA92A09CAC4DB@PSB> <20170706153955.GB3393@localhost> <20170706215236.99A8C7DB2FBA@rock.dv.isc.org> <20170707055315.GC3393@localhost> <20170707065637.EB9C07DBDEF2@rock.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170707065637.EB9C07DBDEF2@rock.dv.isc.org>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/o1d0__Hrlc8FZRvzu1op_R0Lz3U>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 16:35:18 -0000

On Fri, Jul 07, 2017 at 04:56:37PM +1000, Mark Andrews wrote:
> In message <20170707055315.GC3393@localhost>, Nico Williams writes:
> > We've struggled with this in KITTEN WG.  Deploying the URI RR type when
> > you're using a hosting service can be anywhere from annoying (must enter
> > raw RDATA) to impossible (the hosting service doesn't give a damn).  I
> > suppose it's just a matter of time; perhaps things have improved since
> > we last looked.
> 
> Then change domain hosting providers and tell them why or run you
> own master server or use a service which allows for dynamic updates
> which shouldn't care about the record types.  There are plenty of
> DNS providers that will slave content.

That's easy enough if *I* am the user.  Of course I can change hosting
providers.  However, it's NOT easy when your *customer* is the user that
has to change hosting providers -- they'll balk, and you'll just work
around it.

In the KITTEN WG case there definitely was a vendor who needed to
support customers who use hosting providers that didn't support the URI
RR type.  Can you blame them for not wanting to go with the URI RR type?

Sure we should do it anyways -- it might help.  But that vnedor will
still have to cope with cases where URI is not available, and that
actually means falling back onto alternative, possibly slower, methods
that need to be specified too and which might have annoying knock-on
effects.

(In the KITTEN WG case the idea is to improve discovery of Kerberos KDC
services.  We currently use SRV RRs, but this requires multiple
requests, and every time we add a new transport we need to add more
requests.  One could parallelize the requests, but that's not
necessarily very nice, and anyways, it sucks from a resolver API
perspective.  A URI RR type would solve the problem.  But if you have to
fallback then you've slowed things down for what might be the common
case.)

> As a DNS server vendor we get requests to add the new type within
> days the type being allocated.  We usually already have code written
> and merged to support the new type in all current branches before
> those request come in as we poll the type registry daily.  It is
> available over git to anyone that wants to pull it down support for
> the new type prior to the next maintainence releases.  Adding a new
> type is as simple as adding to files to the source tree and rebuilding
> the tools.  Once that is done all the tools we ship support it.

Of course.  *You* are NOT the problem.  That's great.  The problem is
always some knucklehead somewhere who doesn't care to fix *their* system.

Nico
-- 


From nobody Fri Jul  7 09:37:45 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1F701316C5; Fri,  7 Jul 2017 09:37:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 HhRSBEW36Ft3; Fri,  7 Jul 2017 09:37:42 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FF71129AAA; Fri,  7 Jul 2017 09:37:42 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTP id 1F6DFC086D0C; Fri,  7 Jul 2017 09:37:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=HfHTLw0Xajipqk WJUexbsofUDl0=; b=PMiMCnU69GThxmor1AE0iVA1ZJxwy5r7p4Y0jfKYDBeLLB 71Smoj2jKXwBC1sBsLPNUcSt1cuDzJ3d90cJI6thaiQXsNwni0f3/04lzhWXxbDF sKgi3SLRBzh6n3DSexbKC3sj0ldJC9bwlwzA8lK7GpentsljmS7Imu1Ris4zw=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTPSA id 5BC08C086D08; Fri,  7 Jul 2017 09:37:41 -0700 (PDT)
Date: Fri, 7 Jul 2017 11:37:39 -0500
From: Nico Williams <nico@cryptonector.com>
To: Paul Vixie <paul@redbarn.org>
Cc: Mark Andrews <marka@isc.org>, John C Klensin <john-ietf@jck.com>, dnsop <dnsop@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: new DNS classes
Message-ID: <20170707163738.GE3393@localhost>
References: <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <CAMm+Lwjd6xVp-EDp=doevx=AP8qws_Mv++aL733yHEyUF72EMA@mail.gmail.com> <562EC659F89FA92A09CAC4DB@PSB> <20170706153955.GB3393@localhost> <20170706215236.99A8C7DB2FBA@rock.dv.isc.org> <20170707055315.GC3393@localhost> <595FA42A.7050604@redbarn.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <595FA42A.7050604@redbarn.org>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iTGkFvfb9z3b7B9V3hWWZbd5ppY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 16:37:44 -0000

On Fri, Jul 07, 2017 at 08:09:30AM -0700, Paul Vixie wrote:
> Nico Williams wrote:
> >...
> >
> >I'm well aware that as to clients and servers, deploying new RR types is
> >easy.  The hard part is the management backend and UIs.  Not all of them
> >allow you to enter raw RDATA (hex-encoded or whatever).
> >
> >We've struggled with this in KITTEN WG.  Deploying the URI RR type when
> >you're using a hosting service can be anywhere from annoying (must enter
> >raw RDATA) to impossible (the hosting service doesn't give a damn).  I
> >suppose it's just a matter of time; perhaps things have improved since
> >we last looked.
> 
> that would be a prior restraint, and bad for innovation. just like middle
> boxes or the nearly universal assumption that ip means tcp or udp. i know
> this kind of thinking is common. but there is a stark choice for all of us:
> do all of our future protocol work on tcp/80 and make everything fit in
> JSON, so that we can get our work done; or keep doing what the internet used
> to mean, and eventually put enough stress on middle box makers, isp's, and
> in your case dns hosting services, that they have to learn about the
> internet rather than just the web.
> 
> i know which future i'd rather live in. i also feel in-year pressure to get
> my work done. i vacillate as to who gets to receive which burdens.

I'm with you on this.  I badly want to be able to use new RR types
without further ado.  I would prefer to push on the middleboxes and
middlepeople -- but we need to do a better job of this altogether so
that we don't have to wait a decade.  We don't have a spec police, so
all we can do is nag.

Nico
-- 


From nobody Fri Jul  7 09:46:52 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D05F9131765; Fri,  7 Jul 2017 09:46:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 lqM2my8a6vRd; Fri,  7 Jul 2017 09:46:44 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EB1913173B; Fri,  7 Jul 2017 09:46:44 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTP id 302A5C086D08; Fri,  7 Jul 2017 09:46:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=tkXLYYz+H2KIf+ 33XQ9dvYBEMns=; b=ZNznOIQKnltqn6TJbIffjH6CP9+n5t4IfDIIBhoP+KzPGD nA/m/bqKI5GeVjFSfp8bRVU2shwhaMKgYUt2T+fBLnGb3GdKJaDZGtbR2U/VQt1x np2W1o/zwJyp3rTfX1UHUJAsx/0R2Mlfia5CVNlSa9yY5y+CSEnGgwoIB9m+U=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTPSA id 3EF6BC0028BA; Fri,  7 Jul 2017 09:46:43 -0700 (PDT)
Date: Fri, 7 Jul 2017 11:46:41 -0500
From: Nico Williams <nico@cryptonector.com>
To: Paul Vixie <paul@redbarn.org>
Cc: Mark Andrews <marka@isc.org>, John C Klensin <john-ietf@jck.com>, dnsop <dnsop@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: new DNS classes
Message-ID: <20170707164639.GF3393@localhost>
References: <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <CAMm+Lwjd6xVp-EDp=doevx=AP8qws_Mv++aL733yHEyUF72EMA@mail.gmail.com> <562EC659F89FA92A09CAC4DB@PSB> <20170706153955.GB3393@localhost> <20170706215236.99A8C7DB2FBA@rock.dv.isc.org> <20170707055315.GC3393@localhost> <595FA42A.7050604@redbarn.org> <20170707163738.GE3393@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170707163738.GE3393@localhost>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lZTqFGELqs_GnOwSadF_bh9AG2s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 16:46:46 -0000

On Fri, Jul 07, 2017 at 11:37:39AM -0500, Nico Williams wrote:
> On Fri, Jul 07, 2017 at 08:09:30AM -0700, Paul Vixie wrote:
> > Nico Williams wrote:
> > >...
> > 
> > ...
> > 
> > i know which future i'd rather live in. i also feel in-year pressure to get
> > my work done. i vacillate as to who gets to receive which burdens.
> 
> I'm with you on this.  [...]

I should add too that in order to do better at pushing on middleboxes we
need to acknowledge the problem.  Please don't tell me to stop spreading
the myth that it's difficult to deploy new RR types!  Work with us to
fix the problem, and recognize that it is largely a social one.

If we ever want to use CLASSes to expand the RR type namespace, we'll
definitely need even more support from clients/servers/providers.  So
it's worth considering that now rather than later, because we shouldn't
want to have to go through this middlebox un-break exercise multiple
times.

I would even suggest that we immediately add such a new class or three
just to be able to test compliance.  This wouldn't preclude new classes
that aren't IN RR type namespace extension classes.

Nico
-- 


From nobody Fri Jul  7 09:55:21 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 032AC131777; Fri,  7 Jul 2017 09:55:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level: 
X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 YCt0BkIFOq9D; Fri,  7 Jul 2017 09:55:17 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CB73131769; Fri,  7 Jul 2017 09:55:17 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTP id 29843C0028BA; Fri,  7 Jul 2017 09:55:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to:content-transfer-encoding; s= cryptonector.com; bh=Y2mfow/2aEnPdOy54Gra5zwUJN8=; b=cSQB3oqhF8/ 3/OHAYJiwPrJzyV9UQp7sAERg5/sDslJwrVFYSJ854Smdnlob+ebCGAl2ztiwqPk qSkDIVg5b3GgUIfV/ZFFeaDpKNGUypbmA81S4VfQ78dj7JIzQHZ3GCEypQ+Cobua zblOxcYChvLESMReTCISAFB4i1eMVTFw=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTPSA id 5398BC086D0C; Fri,  7 Jul 2017 09:55:16 -0700 (PDT)
Date: Fri, 7 Jul 2017 11:55:14 -0500
From: Nico Williams <nico@cryptonector.com>
To: David Cake <dave@davecake.net>
Cc: Randy Bush <randy@psg.com>, dnsop <dnsop@ietf.org>, Paul Vixie <paul@redbarn.org>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: [DNSOP] new DNS classes
Message-ID: <20170707165513.GG3393@localhost>
References: <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <m2mv8jw9qq.wl-randy@psg.com> <33235E8D-147D-4178-BC45-DFC1E1C27B99@davecake.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <33235E8D-147D-4178-BC45-DFC1E1C27B99@davecake.net>
User-Agent: Mutt/1.5.24 (2015-08-30)
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JPiKC6YoNZJfEeZ5-lpVUqlK7B4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 16:55:19 -0000

On Fri, Jul 07, 2017 at 03:32:21PM +0200, David Cake wrote:
> > On 5 Jul 2017, at 10:47 am, Randy Bush <randy@psg.com> wrote:
> >=20
> > i think avoiding icann is a red herring.  if the draft in question ha=
d
> > done a decent job of exploring the taxa of needs for name resolution
> > outside of the 'normal' topology, we would have the start of a base o=
n
> > which to discuss this.
>=20
> If you have a single centralised root for your new class, you will
> probably either recreate the problems of ICANN, or create one or more
> of the problems that ICANN has very consciously tried to avoid.  If
> you have a system of name resolution that avoids the need for a
> centralised root, you probably don=E2=80=99t need a new class to implem=
ent it.
> The few marginal cases that need to interact with the one root but not
> be ICANN controlled are why we have the RFC 6761 process.=20
>=20
> I agree a taxa of needs that do not fit within those three cases would
> have been useful.=20

Well, there's a) the rooted hierarchy of the public DNS (IN class),
b) mDNS (which isn't really DNS, just a local discovery mechanism based
on the DNS protocol), c) the HS class, which traditionally wasn't used
in a federated manner (but maybe I'm wrong about that), so it doesn't
need a rooted hierarchy, though it also could use one.  (b) and (c) are
niches, with no real place on the open, public Internet.

One could use something like HS as an alternative to LDAP, say, but
recall that the vision of a world of federated and open directories
never materialized NOT because of limitations of DAP/LDAP, but because
of confidentiality/ privacy considerations.  Such a class would really
need to use the same rooted hierarchy, and, really, the same root, as
the public DNS IN class -- i.e., an IN RR type namespace extension
class, so it's best to consider such a class in those terms rather than
as a "directory class".

I am having a very difficult time imagining, say, a peer-to-peer or
web-of-trust DNS (other than mDNS).  Perhaps my imagination fails me.

A rooted hierarchy is and has been incredibly useful, and the simplest
method of providing a consisten Internet to all users.  It seems to me
very unlikely that we'll ever move from that.  At most we may have
alternative roots, but a mostly common set of TLDs (e.g., as happens in
many private (corporate) networks).

Nico
--=20


From nobody Fri Jul  7 11:01:12 2017
Return-Path: <mjethanandani@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 453F31317AD; Fri,  7 Jul 2017 11:01:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.988
X-Spam-Level: 
X-Spam-Status: No, score=-1.988 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, T_KAM_HTML_FONT_INVALID=0.01, 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 1qHc1qW1QZxF; Fri,  7 Jul 2017 11:01:06 -0700 (PDT)
Received: from mail-pg0-x242.google.com (mail-pg0-x242.google.com [IPv6:2607:f8b0:400e:c05::242]) (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 F1D1713168D; Fri,  7 Jul 2017 11:01:05 -0700 (PDT)
Received: by mail-pg0-x242.google.com with SMTP id d193so4874715pgc.2; Fri, 07 Jul 2017 11:01:05 -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:message-id:references :to; bh=hQ13NaugTis6/X6OvHqDxhpWb1dUvuKkeDD86CSeR2I=; b=U/HMPLxaxy/DLZH32dR0DTBfQpz4YvbWyQ5gpmRFEdh60zA1ie/PXRRVYX95TiuBU7 mjtlbgMHohK1F90WI1IRCwT+6gJEtSJiRDZchxyfE0l9mGR0K1vQgI3PfaksVtL0q1f+ v3elh43pJ9cfOWZau2oLPDPKlNRtonOiECftxhVqYruATPNSBFZ94NwbP9sDmfWKSueF jwvczm5sbKn3u3CB5f+3W2f4Ty72+1aLe1LkP2odedxfC0/9cIKh00L0p9lbeAG8SCE5 qbHWFKIU0BUR86HCd9piaKgCT+MkFKFVEDgkHKyVTEad8kO7mMOFEVAwT99f0nX/Fdwk 3+cg==
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 :message-id:references:to; bh=hQ13NaugTis6/X6OvHqDxhpWb1dUvuKkeDD86CSeR2I=; b=gsD1QNySX9ceux9zkDLjZU+WtkTosLyXyT6BQ6jXGLj9W5mMhReKB1/eLQG2sgT3+3 KmblLmgn2AYnLIjR3AOOAGP6AF033ZUSVx5PFdoW1QbqUc/dkX2qfSoq0plSs8wHIW1u Dli/cnCRi/XXN7av/KZVrNYBBZYZZctIWLxh59eAtz/zRkjeT8jmWYPe83Dx9Gb5YSfj 6lP/WsB6dtUQ6GAB8DJGN+EpSg8RxK8QVdd0/Ob3+mccpM2nVoJyFXVmALRTRoCRXkim 62AZicN8pt+nFnruWS1/4ilrey0sOj/fSVQTMRUz60gy41yiSNT+Jc8/3OnlWjSoP3QA cTEg==
X-Gm-Message-State: AIVw111Zt7Uqp5Kphp/AruNhF7Wn1PLqcP+BrNXGFnXEZ+RJF6IcGjd2 p/iAGqk89DfMiA==
X-Received: by 10.84.132.73 with SMTP id 67mr4283683ple.53.1499450465464; Fri, 07 Jul 2017 11:01:05 -0700 (PDT)
Received: from ?IPv6:2602:306:cf77:df90:ece3:5fed:de5b:51da? ([2602:306:cf77:df90:ece3:5fed:de5b:51da]) by smtp.gmail.com with ESMTPSA id v64sm9246915pfk.126.2017.07.07.11.01.03 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 07 Jul 2017 11:01:04 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_944ECD3E-BFAA-4C67-A328-78701A6C314D"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: [Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-08
From: Mahesh Jethanandani <mjethanandani@gmail.com>
In-Reply-To: <024a01d2f44b$465229c0$d2f67d40$@gmail.com>
Date: Fri, 7 Jul 2017 11:01:02 -0700
Cc: Robert Wilton <rwilton@cisco.com>, Benoit Claise <bclaise@cisco.com>, Xufeng Liu <Xufeng_Liu@jabil.com>, yang-doctors@ietf.org, ietf@ietf.org, teas@ietf.org, draft-ietf-teas-yang-te-topo.all@ietf.org
Message-Id: <88816B14-11E8-48E8-80C0-681EDC770A6A@gmail.com>
References: <149564066257.28529.12761629961042171907@ietfa.amsl.com> <BN3PR0201MB08670E55FFB5470F338E998DF1CD0@BN3PR0201MB0867.namprd02.prod.outlook.com> <5d4541d3-9426-787d-e02b-9c2dbc3a5400@cisco.com> <BN3PR0201MB0867315F3E88577B9EEF6584F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com> <3a1c319f-0255-b8ee-ecbd-739568c1dc7f@cisco.com> <1ab3a0d8-de3e-1d7c-2967-97b74b1c68a5@cisco.com> <BN3PR0201MB0867664CBDA460C283DC8043F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com> <04b933e2-189a-6fe2-5d24-310167f91b69@cisco.com> <00d001d2f37c$22d3dd10$687b9730$@gmail.com> <a83f8acd-2c14-2d28-f196-96b5fd7833a9@cisco.com> <024a01d2f44b$465229c0$d2f67d40$@gmail.com>
To: Xufeng Liu <xufeng.liu.ietf@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/K4oSMLKB8yhbZUqGXpMlcRLWNPo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 18:01:10 -0000

--Apple-Mail=_944ECD3E-BFAA-4C67-A328-78701A6C314D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I see 14 errors being reported by yanglint. Have they been addressed?

> On Jul 3, 2017, at 3:25 PM, Xufeng Liu <xufeng.liu.ietf@gmail.com> =
wrote:
>=20
> HI Rob,
> =20
> Just posted =
https://datatracker.ietf.org/doc/draft-ietf-teas-yang-te-topo/ =
<https://datatracker.ietf.org/doc/draft-ietf-teas-yang-te-topo/>  to fix =
the snippets, along with a missing IANA entry.
> =20
> Thanks,
> - Xufeng
> =20
> From: Robert Wilton [mailto:rwilton@cisco.com]=20
> Sent: Monday, July 3, 2017 5:13 AM
> To: Xufeng Liu <xufeng.liu.ietf@gmail.com>; 'Benoit Claise' =
<bclaise@cisco.com>; 'Xufeng Liu' <Xufeng_Liu@jabil.com>; 'Mahesh =
Jethanandani' <mjethanandani@gmail.com>; yang-doctors@ietf.org
> Cc: ietf@ietf.org; teas@ietf.org; =
draft-ietf-teas-yang-te-topo.all@ietf.org
> Subject: Re: [Teas] Yangdoctors last call review of =
draft-ietf-teas-yang-te-topo-08
> =20
> Hi Xufeng,
> Thanks for updating the modules to be NMDA compliant.  I think that =
getting structural consistency across the IETF YANG modules will make =
them far more compelling as a solution.
> I noticed that some of the snippets of YANG tree output in the draft =
still illustrate using the "split oc-style config/state structure" and =
hence also need to be updated.  Probably this could be done as part of =
the WG LC.
> To find the instances, just search the draft for "rw config" and "ro =
state".
> Thanks,
> Rob
> =20
> On 02/07/2017 22:42, Xufeng Liu wrote:
>> An updated revision of the TE topology model has been posted at =
https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-10 =
<https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-10>.
>> =20
>> This new revision now contains the NMDA compliant module and a =
companion =E2=80=9C-state=E2=80=9D module, after the I2RS topology model =
that we augment has been update with a =E2=80=9C-state=E2=80=9D module.
>> =20
>> Now that this issue has been solved, the authors and contributors =
think that the draft is ready for the last call.
>> =20
>> Thanks,
>> - Xufeng
>> =20
>> P.S. Because of the structure changes of the TE topology model, all =
augmenting models need to be updated. Sorry for the short notice.
>> =20
>> From: Teas [mailto:teas-bounces@ietf.org =
<mailto:teas-bounces@ietf.org>] On Behalf Of Benoit Claise
>> Sent: Monday, June 26, 2017 6:46 AM
>> To: Xufeng Liu <Xufeng_Liu@jabil.com> <mailto:Xufeng_Liu@jabil.com>; =
Robert Wilton <rwilton@cisco.com> <mailto:rwilton@cisco.com>; Mahesh =
Jethanandani <mjethanandani@gmail.com> <mailto:mjethanandani@gmail.com>; =
yang-doctors@ietf.org <mailto:yang-doctors@ietf.org>
>> Cc: Benoit Claise <bclaise@cisco.com> <mailto:bclaise@cisco.com>; =
ietf@ietf.org <mailto:ietf@ietf.org>; teas@ietf.org =
<mailto:teas@ietf.org>; draft-ietf-teas-yang-te-topo.all@ietf.org =
<mailto:draft-ietf-teas-yang-te-topo.all@ietf.org>
>> Subject: Re: [Teas] Yangdoctors last call review of =
draft-ietf-teas-yang-te-topo-08
>> =20
>> Hi Xufeng,
>>> Hi Benoit,
>>> =20
>>>> -----Original Message-----
>>>> From: Benoit Claise [mailto:bclaise@cisco.com =
<mailto:bclaise@cisco.com>]
>>>> Sent: Thursday, June 22, 2017 6:12 AM
>>>> To: Robert Wilton <rwilton@cisco.com> <mailto:rwilton@cisco.com>; =
Xufeng Liu <Xufeng_Liu@jabil.com> <mailto:Xufeng_Liu@jabil.com>;
>>>> Mahesh Jethanandani <mjethanandani@gmail.com> =
<mailto:mjethanandani@gmail.com>; yang-doctors@ietf.org =
<mailto:yang-doctors@ietf.org>
>>>> Cc: ietf@ietf.org <mailto:ietf@ietf.org>; teas@ietf.org =
<mailto:teas@ietf.org>; draft-ietf-teas-yang-te-topo.all@ietf.org =
<mailto:draft-ietf-teas-yang-te-topo.all@ietf.org>
>>>> Subject: Re: [Teas] Yangdoctors last call review of =
draft-ietf-teas-yang-te-topo-
>>>> 08
>>>> =20
>>>> Dear draft-ietf-teas-yang-te-topo authors,
>>>>> Hi Xufeng,
>>>>> =20
>>>>> OK, by tooling, I don't mean the pyang plugins that I have been
>>>>> working on to convert between different types of models.  As you
>>>>> aware, the TE YANG models can easily be converted to NMDA style =
since
>>>>> I have already done it
>>>>> (https://github.com/rgwilton/ietf-models-to-combined =
<https://github.com/rgwilton/ietf-models-to-combined>).
>>>>> =20
>>>>> My comment actually relates to the fact the structure used by TE =
YANG
>>>>> modules don't match any other YANG modules - they are using their =
own
>>>>> unique style of structure.
>>>> This is an important issue to resolve.
>>>>> =20
>>>>> Today, there are three common styles of modules:
>>>>> (1) IETF style split config/state trees (e.g. ietf-interfaces).
>>>>> (2) IETF NMDA style combined config/state trees (i.e. where all =
IETF
>>>>> modules are heading to).
>>>>> (3) OpenConfig style modules with the config/state containers
>>>>> immediately above the config leaves.
>>>>> =20
>>>>> Tooling is likely to be optimized to work with these model =
structures,
>>>>> but the TE modules do not fit into any of the three styles above.
>>>>> They are a yet another OpenConfig-like style, but that is =
different
>>>>> enough that tooling that is designed to work with OpenConfig style
>>>>> YANG modules would likely not work with the TE YANG modules.
>>>>> =20
>>>>> Specifically, for clients that expecting to work with an =
OpenConfig
>>>>> style YANG module, then if it knows the path to config leaf X, =
then
>>>>> they would expect the applied config value to be available at the =
path
>>>>> "../state/X".  But, this doesn't hold for the structure being used =
in
>>>>> the TE YANG models.
>>>>> =20
>>>>> I believe strongly that the models being produced by organizations
>>>>> should be structures in a consistent way, hence why I think that =
the
>>>>> published standard version of the TE YANG modules should =
immediately
>>>>> align to the NMDA style.
>>>> Agreed.
>>>> Here is the OPS and RTG AD message:
>>>> https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html =
<https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html>
>>>> =20
>>>> I understand that the I2RS topology YANG modules will be improved =
to the
>>>> NMDA style.
>>> [Xufeng] The I2RS topology model is already NMDA style, but the NMDA =
models are not immediately implementable without NETCONF/RESTCONF =
protocol update. We will need the "-state" module for the I2RS topology =
model (and for all the top-level models) for now.=20
>> Adding -state to the Appendix is a possibility.
>> "In all cases, the NMDA and non-NMDA modules SHOULD be published in =
the same document, with NMDA modules in the document main body and the =
non-NMDA modules in an Appendix."
>> See =
https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html =
<https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html>
>>=20
>>=20
>>> While the NMDA is nice, the NMDA discussions have already =
significantly delayed publishing new models, and doing NMDA without =
staging will further delay the process.
>> This is not solving the important issue brought up by Rob Witlon:
>>> My comment actually relates to the fact the structure used by TE =
YANG modules don't match any other YANG modules - they are using their =
own unique style of structure.
>> Regards, B.
>>=20
>>=20
>>> =20
>>> Thanks,  Xufeng
>>>> =20
>>>> Regards, Benoit
>>>>> =20
>>>>> Thanks,
>>>>> Rob
>>>>> =20
>>>>> =20
>>>>> On 22/06/2017 04:16, Xufeng Liu wrote:
>>>>>> Hi Rob,
>>>>>> =20
>>>>>> While the tooling is very nice to have, especially for writing =
new
>>>>>> models or converting models, we do not have to use it for every
>>>>>> model. It seems not necessary to use the tooling on this model =
for
>>>>>> now. We already know that we can manually convert it to NMDA =
style if
>>>>>> needed.
>>>>>> =20
>>>>>> Thanks,
>>>>>> - Xufeng
>>>>>> =20
>>>>>>> -----Original Message-----
>>>>>>> From: Robert Wilton [mailto:rwilton@cisco.com =
<mailto:rwilton@cisco.com>]
>>>>>>> Sent: Wednesday, June 21, 2017 5:34 AM
>>>>>>> To: Xufeng Liu <Xufeng_Liu@jabil.com> =
<mailto:Xufeng_Liu@jabil.com>; Mahesh Jethanandani
>>>>>>> <mjethanandani@gmail.com> <mailto:mjethanandani@gmail.com>; =
yang-doctors@ietf.org <mailto:yang-doctors@ietf.org>
>>>>>>> Cc: ietf@ietf.org <mailto:ietf@ietf.org>; teas@ietf.org =
<mailto:teas@ietf.org>;
>>>>>>> draft-ietf-teas-yang-te-topo.all@ietf.org =
<mailto:draft-ietf-teas-yang-te-topo.all@ietf.org>
>>>>>>> Subject: Re: [Teas] Yangdoctors last call review of
>>>>>>> draft-ietf-teas-yang-te-topo-
>>>>>>> 08
>>>>>>> =20
>>>>>>> Hi Xufeng,
>>>>>>> =20
>>>>>>> On 12/06/2017 22:28, Xufeng Liu wrote:
>>>>>>>> Hi Mahesh,
>>>>>>>> =20
>>>>>>>> Thank you much for the review. We have submitted an updated =
draft
>>>>>>> (https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09 =
<https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09>) to
>>>>>>> address these issues. More detailed explanations are put below
>>>>>>> inline.
>>>>>>>> If the responses and updates are satisfactory, we are ready for =
the
>>>>>>>> last call.
>>>>>>>> =20
>>>>>>>> Best regards,
>>>>>>>> - Xufeng
>>>>>>>> =20
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: Mahesh Jethanandani [mailto:mjethanandani@gmail.com =
<mailto:mjethanandani@gmail.com>]
>>>>>>>>> Sent: Wednesday, May 24, 2017 11:44 AM
>>>>>>>>> To: yang-doctors@ietf.org <mailto:yang-doctors@ietf.org>
>>>>>>>>> Cc: ietf@ietf.org <mailto:ietf@ietf.org>; teas@ietf.org =
<mailto:teas@ietf.org>;
>>>>>>>>> draft-ietf-teas-yang-te-topo.all@ietf.org =
<mailto:draft-ietf-teas-yang-te-topo.all@ietf.org>
>>>>>>>>> Subject: Yangdoctors last call review of
>>>>>>>>> draft-ietf-teas-yang-te-topo-08
>>>>>>>>> =20
>>>>>>>>> Reviewer: Mahesh Jethanandani
>>>>>>>>> Review result: Ready with Issues
>>>>>>>>> =20
>>>>>>>>> Document reviewed: draft-ietf-teas-yang-te-topo-08
>>>>>>>>> =20
>>>>>>>>> Status: Ready with Issues
>>>>>>>>> =20
>>>>>>>>> I am not an expert in Traffic Engineering. This review is =
looking
>>>>>>>>> at the draft from a YANG perspective. With that said, I have
>>>>>>>>> marked it as =E2=80=9CReady
>>>>>>> with Issues=E2=80=9D
>>>>>>>>> because of some of the points discussed below.
>>>>>>>>> =20
>>>>>>>>> Summary:
>>>>>>>>> =20
>>>>>>>>> This document defines a YANG data model for representing,
>>>>>>>>> retrieving and manipulating TE Topologies. The model serves as =
a
>>>>>>>>> base model that other technology specific TE Topology models =
can
>>>> augment.
>>>>>>>>> =20
>>>>>>>>> Comments:
>>>>>>>>> =20
>>>>>>>>> Almost all the containers in the model are presence =
containers. Is
>>>>>>>>> there a reason why they have to be presence containers? Note, =
that
>>>>>>>>> presence containers are containers whose existence itself
>>>>>>>>> represents configuration data. What particular configuration =
data
>>>>>>>>> is each container
>>>>>>> representing in itself?
>>>>>>>> [Xufeng] Containers that use =E2=80=9Cpresence=E2=80=9D are:
>>>>>>>>     - Container =E2=80=9Cunderlay=E2=80=9D
>>>>>>>>       o  We have changed 13 occurrences of such containers to =
be
>>>>>>>> not
>>>>>>> presence container.
>>>>>>>>     - Container =E2=80=9Cte=E2=80=9D under augmentation
>>>>>>>>       o  To indicate that =E2=80=9CTE=E2=80=9D is enabled =
(configuration data)
>>>>>>>>       o  Also used to do augmentation. The =E2=80=9Cpresence=E2=80=
=9D statement can
>>>>>>> prevent the mandatory child from affecting augmented base model.
>>>>>>>>     - /nw:networks/nw:network/nw:network-types/te-topology!
>>>>>>>>       o  A mechanism required by I2RS topology model to specify =
the
>>>>>>> topology type.
>>>>>>>>> It is difficult to co-relate the diagram with the model itself
>>>>>>>>> because of different terms being used to define different =
parts of
>>>>>>>>> the model.
>>>>>>>>> There is =E2=80=9CTE Topology Model=E2=80=9D and then there is =
=E2=80=9CGeneric TE
>>>>>>>>> Topology
>>>>>>> Model=E2=80=9D.
>>>>>>>>> Are these one and the same models? If so, a common term for =
both
>>>>>>>>> of them would be helpful.
>>>>>>>> [Xufeng] Yes. These two terms are the same. Figure 12, Figure =
13,
>>>>>>>> and relevant
>>>>>>> descriptions have been updated to make the document consistent.
>>>>>>>>> There is extensive use of groupings in the document. However, =
not
>>>>>>>>> all instances of groupings are used multiple number of times.
>>>>>>>>> Where they are not being repeated, it would be better to move =
the
>>>>>>>>> grouping directly where the uses statement resides. Case in =
point
>>>>>>>>> the grouping
>>>>>>> connectivity-label-restriction-list.
>>>>>>>> [Xufeng] We have removed the following groupings
>>>>>>>>       te-link-augment
>>>>>>>>       te-node-augment
>>>>>>>>       te-termination-point-augment
>>>>>>>>       te-topologies-augment
>>>>>>>>       te-topology-augment
>>>>>>>>       te-link-state-underlay-attributes
>>>>>>>>       te-node-state-derived-notification
>>>>>>>>       te-topology-type
>>>>>>>> =20
>>>>>>>> The remaining groupings have been kept so that we can:
>>>>>>>>     - Share the groupings in this model
>>>>>>>>     - Prepare to be shared by a model augmenting this model
>>>>>>>>     - Prevent a grouping or configuration section from being =
too long
>>>>>>>>     - Improve readability
>>>>>>>> =20
>>>>>>>>> The split between config and state containers does not seem to
>>>>>>>>> follow any particular pattern.
>>>>>>>> [Xufeng] The pattern is clear:
>>>>>>>> For each manageable entity (object), there is a config =
container
>>>>>>>> and state
>>>>>>> container. The configurable properties go into the config =
container
>>>>>>> and state properties go into the state container. Such objects =
are
>>>>>>> identified by a list item or a presence container so that the
>>>>>>> =E2=80=9Ccreate=E2=80=9D, =E2=80=9Cdelete=E2=80=9D, and =
=E2=80=9Cmodify=E2=80=9D
>>>>>>> operations
>>>>>>> can be performed on them. The non-presence containers do not
>>>>>>> represent configuration data so they do not introduce such =
objects.
>>>>>>>>> It is neither a top level split, as is the case with existing =
IETF
>>>>>>>>> models,
>>>>>>>> [Xufeng] We could not do top level split because the base I2RS
>>>>>>>> network
>>>>>>> topology model
>>>>>>> (https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo =
<https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo>-
>>>>>>> 12) that we augment does not have the top-level split (for its =
own
>>>>>>> reasons).
>>>>>>>>> nor do they follow the OpenConfig style of splitting config =
and
>>>>>>>>> state under each relevant leaf,
>>>>>>>> [Xufeng] The pattern is consistent with this style in =
principle,
>>>>>>>> with some
>>>>>>> adjustments to fit to our multiple levels of hierarchy.
>>>>>>> This is effectively a new forth style of YANG models that is not
>>>>>>> consistent with any of the three existing styles, i.e.:
>>>>>>>    - Current IETF config/state split model style
>>>>>>>    - NMDA combined config/state tree
>>>>>>>    - OpenConfig split config/state containers immediately above =
the
>>>>>>> config true leaves.
>>>>>>> =20
>>>>>>> Tooling that it designed to work with OpenConfig models will =
need
>>>>>>> customization to work with these TE models because the =
config/state
>>>>>>> containers will not be where the tooling expects them to be.
>>>>>>> =20
>>>>>>> Thanks,
>>>>>>> Rob
>>>>> =20
>>>>> .
>>>>> =20
>>> =20
>> =20
> =20

Mahesh Jethanandani
mjethanandani@gmail.com




--Apple-Mail=_944ECD3E-BFAA-4C67-A328-78701A6C314D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">I see 14 errors being reported by yanglint. Have they been =
addressed?<div class=3D""><br class=3D""><div><blockquote type=3D"cite" =
class=3D""><div class=3D"">On Jul 3, 2017, at 3:25 PM, Xufeng Liu &lt;<a =
href=3D"mailto:xufeng.liu.ietf@gmail.com" =
class=3D"">xufeng.liu.ietf@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"WordSection1" style=3D"page: WordSection1; font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
background-color: rgb(255, 255, 255);"><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"color: windowtext;" class=3D"">HI Rob,<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"color: windowtext;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">Just posted<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-teas-yang-te-topo/" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-teas-yang-te-topo/<=
/a><span class=3D"Apple-converted-space">&nbsp;</span>&nbsp;to fix the =
snippets, along with a missing IANA entry.<span style=3D"color: =
windowtext;" class=3D""><o:p class=3D""></o:p></span></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"color: windowtext;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"color: windowtext;" class=3D"">Thanks,<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"color: windowtext;" class=3D"">- Xufeng<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"color: windowtext;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div style=3D"border-style: none =
none none solid; border-left-color: blue; border-left-width: 1.5pt; =
padding: 0in 0in 0in 4pt;" class=3D""><div class=3D""><div =
style=3D"border-style: solid none none; border-top-color: rgb(225, 225, =
225); border-top-width: 1pt; padding: 3pt 0in 0in;" class=3D""><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><b class=3D""><span style=3D"color: =
windowtext;" class=3D"">From:</span></b><span style=3D"color: =
windowtext;" class=3D""><span =
class=3D"Apple-converted-space">&nbsp;</span>Robert Wilton [<a =
href=3D"mailto:rwilton@cisco.com" =
class=3D"">mailto:rwilton@cisco.com</a>]<span =
class=3D"Apple-converted-space">&nbsp;</span><br class=3D""><b =
class=3D"">Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Monday, July 3, 2017 5:13 =
AM<br class=3D""><b class=3D"">To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Xufeng Liu &lt;<a =
href=3D"mailto:xufeng.liu.ietf@gmail.com" =
class=3D"">xufeng.liu.ietf@gmail.com</a>&gt;; 'Benoit Claise' &lt;<a =
href=3D"mailto:bclaise@cisco.com" class=3D"">bclaise@cisco.com</a>&gt;; =
'Xufeng Liu' &lt;<a href=3D"mailto:Xufeng_Liu@jabil.com" =
class=3D"">Xufeng_Liu@jabil.com</a>&gt;; 'Mahesh Jethanandani' &lt;<a =
href=3D"mailto:mjethanandani@gmail.com" =
class=3D"">mjethanandani@gmail.com</a>&gt;; <a =
href=3D"mailto:yang-doctors@ietf.org" =
class=3D"">yang-doctors@ietf.org</a><br class=3D""><b =
class=3D"">Cc:</b><span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:ietf@ietf.org" class=3D"">ietf@ietf.org</a>; <a =
href=3D"mailto:teas@ietf.org" class=3D"">teas@ietf.org</a>; <a =
href=3D"mailto:draft-ietf-teas-yang-te-topo.all@ietf.org" =
class=3D"">draft-ietf-teas-yang-te-topo.all@ietf.org</a><br class=3D""><b =
class=3D"">Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [Teas] Yangdoctors last =
call review of draft-ietf-teas-yang-te-topo-08<o:p =
class=3D""></o:p></span></div></div></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div><div class=3D"">Hi =
Xufeng,<o:p class=3D""></o:p></div><div class=3D"">Thanks for updating =
the modules to be NMDA compliant.&nbsp; I think that getting structural =
consistency across the IETF YANG modules will make them far more =
compelling as a solution.<o:p class=3D""></o:p></div><div class=3D"">I =
noticed that some of the snippets of YANG tree output in the draft still =
illustrate using the "split oc-style config/state structure" and hence =
also need to be updated.&nbsp; Probably this could be done as part of =
the WG LC.<o:p class=3D""></o:p></div><div class=3D"">To find the =
instances, just search the draft for "rw config" and "ro state".<o:p =
class=3D""></o:p></div><div class=3D"">Thanks,<br class=3D"">Rob<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div class=3D""><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">On 02/07/2017 22:42, Xufeng Liu wrote:<o:p =
class=3D""></o:p></div></div><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">An updated revision of the TE topology model has been posted =
at<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-10" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-10</a>=
.<o:p class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">&nbsp;<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">This new =
revision now contains the NMDA compliant module and a companion =
=E2=80=9C-state=E2=80=9D module, after the I2RS topology model that we =
augment has been update with a =E2=80=9C-state=E2=80=9D module.<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">&nbsp;<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">Now that =
this issue has been solved, the authors and contributors think that the =
draft is ready for the last call.<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">&nbsp;<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">Thanks,<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">- Xufeng<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">&nbsp;<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">P.S. Because of the structure changes =
of the TE topology model, all augmenting models need to be updated. =
Sorry for the short notice.<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"color: windowtext;" =
class=3D"">&nbsp;</span><o:p class=3D""></o:p></div><div =
style=3D"border-style: none none none solid; border-left-color: blue; =
border-left-width: 1.5pt; padding: 0in 0in 0in 4pt;" class=3D""><div =
class=3D""><div style=3D"border-style: solid none none; =
border-top-color: rgb(225, 225, 225); border-top-width: 1pt; padding: =
3pt 0in 0in;" class=3D""><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><b =
class=3D""><span style=3D"color: windowtext;" =
class=3D"">From:</span></b><span style=3D"color: windowtext;" =
class=3D""><span class=3D"Apple-converted-space">&nbsp;</span>Teas [<a =
href=3D"mailto:teas-bounces@ietf.org" style=3D"color: purple; =
text-decoration: underline;" =
class=3D"">mailto:teas-bounces@ietf.org</a>]<span =
class=3D"Apple-converted-space">&nbsp;</span><b class=3D"">On Behalf =
Of<span class=3D"Apple-converted-space">&nbsp;</span></b>Benoit =
Claise<br class=3D""><b class=3D"">Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Monday, June 26, 2017 6:46 =
AM<br class=3D""><b class=3D"">To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Xufeng Liu<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:Xufeng_Liu@jabil.com" style=3D"color: purple; =
text-decoration: underline;" class=3D"">&lt;Xufeng_Liu@jabil.com&gt;</a>; =
Robert Wilton<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:rwilton@cisco.com" style=3D"color: purple; =
text-decoration: underline;" class=3D"">&lt;rwilton@cisco.com&gt;</a>; =
Mahesh Jethanandani<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:mjethanandani@gmail.com" style=3D"color: purple; =
text-decoration: underline;" =
class=3D"">&lt;mjethanandani@gmail.com&gt;</a>;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:yang-doctors@ietf.org" style=3D"color: purple; =
text-decoration: underline;" class=3D"">yang-doctors@ietf.org</a><br =
class=3D""><b class=3D"">Cc:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Benoit Claise<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:bclaise@cisco.com" style=3D"color: purple; =
text-decoration: underline;" =
class=3D"">&lt;bclaise@cisco.com&gt;</a>;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:ietf@ietf.org" style=3D"color: purple; text-decoration: =
underline;" class=3D"">ietf@ietf.org</a>;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:teas@ietf.org" style=3D"color: purple; text-decoration: =
underline;" class=3D"">teas@ietf.org</a>;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:draft-ietf-teas-yang-te-topo.all@ietf.org" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">draft-ietf-teas-yang-te-topo.all@ietf.org</a><br class=3D""><b =
class=3D"">Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [Teas] Yangdoctors last =
call review of draft-ietf-teas-yang-te-topo-08</span><o:p =
class=3D""></o:p></div></div></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">&nbsp;<o:p class=3D""></o:p></div><div class=3D""><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">Hi Xufeng,<o:p =
class=3D""></o:p></div></div><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">Hi =
Benoit,<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; =
font-family: 'Courier New';" class=3D"">-----Original Message-----<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">From: Benoit =
Claise [<a href=3D"mailto:bclaise@cisco.com" style=3D"color: purple; =
text-decoration: underline;" class=3D"">mailto:bclaise@cisco.com</a>]<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Sent: Thursday, =
June 22, 2017 6:12 AM<o:p class=3D""></o:p></pre><pre style=3D"margin: =
0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">To: Robert Wilton <a href=3D"mailto:rwilton@cisco.com" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">&lt;rwilton@cisco.com&gt;</a>; Xufeng Liu <a =
href=3D"mailto:Xufeng_Liu@jabil.com" style=3D"color: purple; =
text-decoration: underline;" =
class=3D"">&lt;Xufeng_Liu@jabil.com&gt;</a>;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Mahesh =
Jethanandani <a href=3D"mailto:mjethanandani@gmail.com" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">&lt;mjethanandani@gmail.com&gt;</a>; <a =
href=3D"mailto:yang-doctors@ietf.org" style=3D"color: purple; =
text-decoration: underline;" class=3D"">yang-doctors@ietf.org</a><o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Cc: <a =
href=3D"mailto:ietf@ietf.org" style=3D"color: purple; text-decoration: =
underline;" class=3D"">ietf@ietf.org</a>; <a href=3D"mailto:teas@ietf.org"=
 style=3D"color: purple; text-decoration: underline;" =
class=3D"">teas@ietf.org</a>; <a =
href=3D"mailto:draft-ietf-teas-yang-te-topo.all@ietf.org" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">draft-ietf-teas-yang-te-topo.all@ietf.org</a><o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Subject: Re: =
[Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">08<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Dear =
draft-ietf-teas-yang-te-topo authors,<o:p =
class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">Hi =
Xufeng,<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">OK,=
 by tooling, I don't mean the pyang plugins that I have been<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">working on to =
convert between different types of models.&nbsp; As you<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">aware, the TE =
YANG models can easily be converted to NMDA style since<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">I have already =
done it<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">(<a =
href=3D"https://github.com/rgwilton/ietf-models-to-combined" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">https://github.com/rgwilton/ietf-models-to-combined</a>).<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">My comment =
actually relates to the fact the structure used by TE YANG<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">modules don't =
match any other YANG modules - they are using their own<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">unique style of =
structure.<o:p class=3D""></o:p></pre></blockquote><pre style=3D"margin: =
0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">This is an important issue to resolve.<o:p =
class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Today, there are three common styles of modules:<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">(1) IETF style =
split config/state trees (e.g. ietf-interfaces).<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">(2) IETF NMDA =
style combined config/state trees (i.e. where all IETF<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">modules are =
heading to).<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">(3) =
OpenConfig style modules with the config/state containers<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">immediately =
above the config leaves.<o:p class=3D""></o:p></pre><pre style=3D"margin: =
0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Tooling is likely to be optimized to work with these model =
structures,<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">but =
the TE modules do not fit into any of the three styles above.<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">They are a yet =
another OpenConfig-like style, but that is different<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">enough that =
tooling that is designed to work with OpenConfig style<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">YANG modules =
would likely not work with the TE YANG modules.<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Specifically, =
for clients that expecting to work with an OpenConfig<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">style YANG =
module, then if it knows the path to config leaf X, then<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">they would =
expect the applied config value to be available at the path<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" =
class=3D"">"../state/X".&nbsp; But, this doesn't hold for the structure =
being used in<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">the =
TE YANG models.<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">I =
believe strongly that the models being produced by organizations<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">should be =
structures in a consistent way, hence why I think that the<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">published =
standard version of the TE YANG modules should immediately<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">align to the =
NMDA style.<o:p class=3D""></o:p></pre></blockquote><pre style=3D"margin: =
0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Agreed.<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Here is the OPS and RTG AD message:<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D""><a =
href=3D"https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html=
" style=3D"color: purple; text-decoration: underline;" =
class=3D"">https://www.ietf.org/mail-archive/web/netmod/current/msg18252.h=
tml</a><o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">I =
understand that the I2RS topology YANG modules will be improved to =
the<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">NMDA style.<o:p =
class=3D""></o:p></pre></blockquote><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">[Xufeng] The I2RS topology model is already NMDA style, but =
the NMDA models are not immediately implementable without =
NETCONF/RESTCONF protocol update. We will need the "-state" module for =
the I2RS topology model (and for all the top-level models) for now. <o:p =
class=3D""></o:p></pre></blockquote><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">Adding -state to the Appendix is a possibility.<br =
class=3D"">"In all cases, the NMDA and non-NMDA modules SHOULD be =
published in the same document, with NMDA modules in the document main =
body and the non-NMDA modules in an Appendix."<br class=3D"">See<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html=
" style=3D"color: purple; text-decoration: underline;" =
class=3D"">https://www.ietf.org/mail-archive/web/netmod/current/msg18252.h=
tml</a><br class=3D""><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></div><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">While the NMDA is nice, the NMDA discussions have already =
significantly delayed publishing new models, and doing NMDA without =
staging will further delay the process.<o:p =
class=3D""></o:p></pre></blockquote><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">This is not solving the important issue brought up by Rob =
Witlon:<o:p class=3D""></o:p></div><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">My comment actually relates to the fact the structure used by =
TE YANG modules don't match any other YANG modules - they are using =
their own unique style of structure.<o:p =
class=3D""></o:p></div></blockquote><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">Regards, B.<br class=3D""><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></div><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Thanks,&nbsp; Xufeng<o:p class=3D""></o:p></pre><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; =
font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Regards, =
Benoit<o:p class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Thanks,<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Rob<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">On =
22/06/2017 04:16, Xufeng Liu wrote:<o:p class=3D""></o:p></pre><blockquote=
 style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; =
font-family: 'Courier New';" class=3D"">Hi Rob,<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">While the =
tooling is very nice to have, especially for writing new<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">models or =
converting models, we do not have to use it for every<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">model. It seems =
not necessary to use the tooling on this model for<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">now. We already =
know that we can manually convert it to NMDA style if<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">needed.<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Thanks,<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">- Xufeng<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">-----Original Message-----<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">From: Robert Wilton [<a =
href=3D"mailto:rwilton@cisco.com" style=3D"color: purple; =
text-decoration: underline;" class=3D"">mailto:rwilton@cisco.com</a>]<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Sent: =
Wednesday, June 21, 2017 5:34 AM<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">To: Xufeng Liu <a =
href=3D"mailto:Xufeng_Liu@jabil.com" style=3D"color: purple; =
text-decoration: underline;" class=3D"">&lt;Xufeng_Liu@jabil.com&gt;</a>; =
Mahesh Jethanandani<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D""><a =
href=3D"mailto:mjethanandani@gmail.com" style=3D"color: purple; =
text-decoration: underline;" =
class=3D"">&lt;mjethanandani@gmail.com&gt;</a>; <a =
href=3D"mailto:yang-doctors@ietf.org" style=3D"color: purple; =
text-decoration: underline;" class=3D"">yang-doctors@ietf.org</a><o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Cc: <a =
href=3D"mailto:ietf@ietf.org" style=3D"color: purple; text-decoration: =
underline;" class=3D"">ietf@ietf.org</a>; <a href=3D"mailto:teas@ietf.org"=
 style=3D"color: purple; text-decoration: underline;" =
class=3D"">teas@ietf.org</a>;<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D""><a =
href=3D"mailto:draft-ietf-teas-yang-te-topo.all@ietf.org" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">draft-ietf-teas-yang-te-topo.all@ietf.org</a><o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Subject: Re: =
[Teas] Yangdoctors last call review of<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">draft-ietf-teas-yang-te-topo-<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">08<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Hi Xufeng,<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">On 12/06/2017 =
22:28, Xufeng Liu wrote:<o:p class=3D""></o:p></pre><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; =
font-family: 'Courier New';" class=3D"">Hi Mahesh,<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Thank you much =
for the review. We have submitted an updated draft<o:p =
class=3D""></o:p></pre></blockquote><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">(<a =
href=3D"https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09</a>=
) to<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">address these =
issues. More detailed explanations are put below<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">inline.<o:p =
class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">If =
the responses and updates are satisfactory, we are ready for the<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">last call.<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Best =
regards,<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">- =
Xufeng<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; =
font-family: 'Courier New';" class=3D"">-----Original Message-----<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">From: Mahesh =
Jethanandani [<a href=3D"mailto:mjethanandani@gmail.com" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">mailto:mjethanandani@gmail.com</a>]<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Sent: =
Wednesday, May 24, 2017 11:44 AM<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">To: <a href=3D"mailto:yang-doctors@ietf.org" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">yang-doctors@ietf.org</a><o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">Cc: <a href=3D"mailto:ietf@ietf.org" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">ietf@ietf.org</a>; <a href=3D"mailto:teas@ietf.org" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">teas@ietf.org</a>;<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D""><a =
href=3D"mailto:draft-ietf-teas-yang-te-topo.all@ietf.org" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">draft-ietf-teas-yang-te-topo.all@ietf.org</a><o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Subject: =
Yangdoctors last call review of<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">draft-ietf-teas-yang-te-topo-08<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Reviewer: =
Mahesh Jethanandani<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Review result: Ready with Issues<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Document =
reviewed: draft-ietf-teas-yang-te-topo-08<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">Status: Ready with Issues<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">I am not an =
expert in Traffic Engineering. This review is looking<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">at the draft =
from a YANG perspective. With that said, I have<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">marked it as =
=E2=80=9CReady<o:p class=3D""></o:p></pre></blockquote></blockquote><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">with Issues=E2=80=9D<o:p =
class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; =
font-family: 'Courier New';" class=3D"">because of some of the points =
discussed below.<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Summary:<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">This document defines a YANG data model for representing,<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">retrieving and =
manipulating TE Topologies. The model serves as a<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">base model that =
other technology specific TE Topology models can<o:p =
class=3D""></o:p></pre></blockquote></blockquote></blockquote></blockquote=
></blockquote><pre style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; =
font-family: 'Courier New';" class=3D"">augment.<o:p =
class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><blockquote style=3D"margin-top: 5pt; margin-bottom: 5pt;" =
class=3D"" type=3D"cite"><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; =
font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Comments:<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Almost all the =
containers in the model are presence containers. Is<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">there a reason =
why they have to be presence containers? Note, that<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">presence =
containers are containers whose existence itself<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">represents =
configuration data. What particular configuration data<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">is each =
container<o:p class=3D""></o:p></pre></blockquote></blockquote><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">representing in itself?<o:p =
class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">[Xufeng] Containers that use =E2=80=9Cpresence=E2=80=9D =
are:<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp; - Container =E2=80=9Cunderlay=E2=80=9D<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; o&nbsp; We have changed 13 =
occurrences of such containers to be<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">not<o:p =
class=3D""></o:p></pre></blockquote><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">presence container.<o:p class=3D""></o:p></pre><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; =
font-family: 'Courier New';" class=3D"">&nbsp;&nbsp;&nbsp; - Container =
=E2=80=9Cte=E2=80=9D under augmentation<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; o&nbsp; To =
indicate that =E2=80=9CTE=E2=80=9D is enabled (configuration data)<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; o&nbsp; Also used to do =
augmentation. The =E2=80=9Cpresence=E2=80=9D statement can<o:p =
class=3D""></o:p></pre></blockquote><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">prevent=
 the mandatory child from affecting augmented base model.<o:p =
class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp; - =
/nw:networks/nw:network/nw:network-types/te-topology!<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; o&nbsp; A mechanism required =
by I2RS topology model to specify the<o:p =
class=3D""></o:p></pre></blockquote><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">topology type.<o:p class=3D""></o:p></pre><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><blockquote style=3D"margin-top: 5pt; margin-bottom: 5pt;" =
class=3D"" type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">It is difficult =
to co-relate the diagram with the model itself<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">because of =
different terms being used to define different parts of<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">the model.<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">There is =E2=80=9C=
TE Topology Model=E2=80=9D and then there is =E2=80=9CGeneric TE<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Topology<o:p =
class=3D""></o:p></pre></blockquote></blockquote><pre style=3D"margin: =
0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Model=E2=80=9D.<o:p class=3D""></o:p></pre><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><blockquote style=3D"margin-top: 5pt; margin-bottom: 5pt;" =
class=3D"" type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Are these one =
and the same models? If so, a common term for both<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">of them would =
be helpful.<o:p class=3D""></o:p></pre></blockquote><pre style=3D"margin: =
0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">[Xufeng] Yes. These two terms are the same. Figure 12, Figure =
13,<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">and =
relevant<o:p class=3D""></o:p></pre></blockquote><pre style=3D"margin: =
0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">descriptions have been updated to make the document =
consistent.<o:p class=3D""></o:p></pre><blockquote style=3D"margin-top: =
5pt; margin-bottom: 5pt;" class=3D"" type=3D"cite"><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; =
font-family: 'Courier New';" class=3D"">There is extensive use of =
groupings in the document. However, not<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">all instances of groupings are used multiple =
number of times.<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Where they are not being repeated, it would be better to move =
the<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">grouping =
directly where the uses statement resides. Case in point<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">the =
grouping<o:p class=3D""></o:p></pre></blockquote></blockquote><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">connectivity-label-restriction-list.<o:p =
class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">[Xufeng] We have removed the following groupings<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; te-link-augment<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; te-node-augment<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
te-termination-point-augment<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
te-topologies-augment<o:p class=3D""></o:p></pre><pre style=3D"margin: =
0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; te-topology-augment<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
te-link-state-underlay-attributes<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
te-node-state-derived-notification<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;te-topology-type<o:p class=3D""></o:p></pre><pre style=3D"margin: =
0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">The=
 remaining groupings have been kept so that we can:<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp; - Share the groupings in this model<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp; - Prepare to be shared by a model =
augmenting this model<o:p class=3D""></o:p></pre><pre style=3D"margin: =
0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp; - Prevent a grouping or configuration =
section from being too long<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">&nbsp;&nbsp;&nbsp; - Improve readability<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">The=
 split between config and state containers does not seem to<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">follow any =
particular pattern.<o:p class=3D""></o:p></pre></blockquote><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">[Xufeng] The pattern is clear:<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">For each =
manageable entity (object), there is a config container<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">and state<o:p =
class=3D""></o:p></pre></blockquote><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">container. The configurable properties go into the config =
container<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">and =
state properties go into the state container. Such objects are<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">identified by a =
list item or a presence container so that the<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">=E2=80=9Ccreate=E2=
=80=9D, =E2=80=9Cdelete=E2=80=9D, and =E2=80=9Cmodify=E2=80=9D<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">operations<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">can be =
performed on them. The non-presence containers do not<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">represent =
configuration data so they do not introduce such objects.<o:p =
class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; =
font-family: 'Courier New';" class=3D"">It is neither a top level split, =
as is the case with existing IETF<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">models,<o:p =
class=3D""></o:p></pre></blockquote><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">[Xufeng] We could not do top level split because the base =
I2RS<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">network<o:p =
class=3D""></o:p></pre></blockquote><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">topology model<o:p class=3D""></o:p></pre><pre style=3D"margin:=
 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">(<a =
href=3D"https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo</=
a>-<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">12) that we =
augment does not have the top-level split (for its own<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">reasons).<o:p =
class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; =
font-family: 'Courier New';" class=3D"">nor do they follow the =
OpenConfig style of splitting config and<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">state under each relevant leaf,<o:p =
class=3D""></o:p></pre></blockquote><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">[Xufeng] The pattern is consistent with this style in =
principle,<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">with =
some<o:p class=3D""></o:p></pre></blockquote><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">adjustments to fit to our multiple levels of hierarchy.<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">This is =
effectively a new forth style of YANG models that is not<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">consistent with =
any of the three existing styles, i.e.:<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">&nbsp;&nbsp; - Current IETF config/state =
split model style<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp; - NMDA combined config/state tree<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;&nbsp; - =
OpenConfig split config/state containers immediately above the<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">config true =
leaves.<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Tooling that it designed to work with OpenConfig models will =
need<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">customization =
to work with these TE models because the config/state<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">containers will =
not be where the tooling expects them to be.<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Thanks,<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Rob<o:p =
class=3D""></o:p></pre></blockquote></blockquote><pre style=3D"margin: =
0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">.<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre></blockquote></blockquote><pre style=3D"margin: =
0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre></blockquote><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">&nbsp;<o:p =
class=3D""></o:p></div></div></blockquote><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div></div></div></blockquote></div><br =
class=3D""><div class=3D"">
<div class=3D"">Mahesh Jethanandani</div><div class=3D""><a =
href=3D"mailto:mjethanandani@gmail.com" =
class=3D"">mjethanandani@gmail.com</a></div><div class=3D""><br =
class=3D""></div><br class=3D"Apple-interchange-newline">

</div>
<br class=3D""></div></body></html>=

--Apple-Mail=_944ECD3E-BFAA-4C67-A328-78701A6C314D--


From nobody Fri Jul  7 11:13:43 2017
Return-Path: <mjethanandani@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0C0B131621; Fri,  7 Jul 2017 11:13:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.988
X-Spam-Level: 
X-Spam-Status: No, score=-1.988 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, T_KAM_HTML_FONT_INVALID=0.01, 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 X5jIDJGyUay2; Fri,  7 Jul 2017 11:13:38 -0700 (PDT)
Received: from mail-pg0-x244.google.com (mail-pg0-x244.google.com [IPv6:2607:f8b0:400e:c05::244]) (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 1FCC7126C0F; Fri,  7 Jul 2017 11:13:38 -0700 (PDT)
Received: by mail-pg0-x244.google.com with SMTP id u36so4900960pgn.3; Fri, 07 Jul 2017 11:13:38 -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:message-id:references :to; bh=cuVrbV0j/sunc9+fw7rZT07kE6h5nDuGnGvCdgvX31o=; b=ZNi9Sn6OUuIEKL4VxyR3pig4sU4qVKUA9ubRnPGYwBi7umFmyaksy3HKBbHqSmv+kF XBHvzjpdUz4Wk+alRlvkgT9/4zCb3CWiRjvcZdu0s0TsYCR1Gi+G/la2fglCTCLKQwNg oKfWwW532uI6iklKwbqmgZ0FsOkKMpWb8HhMZ2AzjGssiCqV01VxApNF79qskLlmFpXT 6ZJsOYLxtEKpz6lBDB6XJkGEbdIq72brcbnLIAUElF1LQ6cTT8FGL63ertsMGLvVVlMP sTZwSbanjA9wbn2KE8wq+yS28IFuWIB/DG+thTx7CjWQitK2ioSir/BL0czktrGIqJz/ uwfA==
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 :message-id:references:to; bh=cuVrbV0j/sunc9+fw7rZT07kE6h5nDuGnGvCdgvX31o=; b=RP4+eFu/PMeQz4tUNYbb9q+zUoNmt4GVDFapEuZl1pBE6QNcexUY8dIvZIjuuxnGJ8 g3bt9bfvEqBX04QUh2I7EzlFXcgnQdYBUh0+gtVoEHkc0aBOSnr/OoePof/G+pD3Q5oz vaWN+1jQDPAbij+ve1symqMBtieJGYQSs2qhT63yFktPCMLxSQPtC8IpjYmsPqCo35x7 zgpzyhn6Ea64aSDcnYGAk/c5V94N0a41BYrGFflJyVhy58NByy6gJGQvKM4CW/DSz8GY VVjrA6tyAghZVS+39XzVBDZpcUV1VermJxhJBvExoKQewSUSS5Zh3f1botRG4lw1Zh6/ VOaQ==
X-Gm-Message-State: AIVw1134Ub6z09q+qGY6b27ifFlxhNrQVMQuTrpEyfnUd8MOq2OxJuKj V5+qCOCnPpJcfw==
X-Received: by 10.84.194.37 with SMTP id g34mr4491042pld.111.1499451217575; Fri, 07 Jul 2017 11:13:37 -0700 (PDT)
Received: from ?IPv6:2602:306:cf77:df90:ece3:5fed:de5b:51da? ([2602:306:cf77:df90:ece3:5fed:de5b:51da]) by smtp.gmail.com with ESMTPSA id t78sm8917402pfa.48.2017.07.07.11.13.35 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 07 Jul 2017 11:13:36 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_878BBB3D-E53E-4A9D-9A7D-69573F8471A8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: [Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-08
From: Mahesh Jethanandani <mjethanandani@gmail.com>
In-Reply-To: <024a01d2f44b$465229c0$d2f67d40$@gmail.com>
Date: Fri, 7 Jul 2017 11:13:35 -0700
Cc: Robert Wilton <rwilton@cisco.com>, Benoit Claise <bclaise@cisco.com>, Xufeng Liu <Xufeng_Liu@jabil.com>, yang-doctors@ietf.org, ietf@ietf.org, teas@ietf.org, draft-ietf-teas-yang-te-topo.all@ietf.org
Message-Id: <57EAC7E8-66B5-43D7-AA03-3D5E1008FC49@gmail.com>
References: <149564066257.28529.12761629961042171907@ietfa.amsl.com> <BN3PR0201MB08670E55FFB5470F338E998DF1CD0@BN3PR0201MB0867.namprd02.prod.outlook.com> <5d4541d3-9426-787d-e02b-9c2dbc3a5400@cisco.com> <BN3PR0201MB0867315F3E88577B9EEF6584F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com> <3a1c319f-0255-b8ee-ecbd-739568c1dc7f@cisco.com> <1ab3a0d8-de3e-1d7c-2967-97b74b1c68a5@cisco.com> <BN3PR0201MB0867664CBDA460C283DC8043F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com> <04b933e2-189a-6fe2-5d24-310167f91b69@cisco.com> <00d001d2f37c$22d3dd10$687b9730$@gmail.com> <a83f8acd-2c14-2d28-f196-96b5fd7833a9@cisco.com> <024a01d2f44b$465229c0$d2f67d40$@gmail.com>
To: Xufeng Liu <xufeng.liu.ietf@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/USYmBL4h5ZKX9cPj3CZJ1zBPTQM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 18:13:42 -0000

--Apple-Mail=_878BBB3D-E53E-4A9D-9A7D-69573F8471A8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Also, couple of changes in the YANG modules:

Under revision, can you make sure there is a reference back to the RFC =
number that will be assigned to the draft. Something like:

  revision "YYYY-MM-DD" {
    description
     "Initial version";
    reference
     "RFC XXXX: YANG - TE Topology";
  }

with a note to RFC editor to replace XXXX with the number assigned to =
the RFC.

Prefix organization with IETF. Something like =E2=80=9CIETF Traffic =
Engineering Architecture and Signaling (TEAS) Working Group=E2=80=9D

Thanks.


> On Jul 3, 2017, at 3:25 PM, Xufeng Liu <xufeng.liu.ietf@gmail.com> =
wrote:
>=20
> HI Rob,
> =20
> Just posted =
https://datatracker.ietf.org/doc/draft-ietf-teas-yang-te-topo/ =
<https://datatracker.ietf.org/doc/draft-ietf-teas-yang-te-topo/>  to fix =
the snippets, along with a missing IANA entry.
> =20
> Thanks,
> - Xufeng
> =20
> From: Robert Wilton [mailto:rwilton@cisco.com]=20
> Sent: Monday, July 3, 2017 5:13 AM
> To: Xufeng Liu <xufeng.liu.ietf@gmail.com>; 'Benoit Claise' =
<bclaise@cisco.com>; 'Xufeng Liu' <Xufeng_Liu@jabil.com>; 'Mahesh =
Jethanandani' <mjethanandani@gmail.com>; yang-doctors@ietf.org
> Cc: ietf@ietf.org; teas@ietf.org; =
draft-ietf-teas-yang-te-topo.all@ietf.org
> Subject: Re: [Teas] Yangdoctors last call review of =
draft-ietf-teas-yang-te-topo-08
> =20
> Hi Xufeng,
> Thanks for updating the modules to be NMDA compliant.  I think that =
getting structural consistency across the IETF YANG modules will make =
them far more compelling as a solution.
> I noticed that some of the snippets of YANG tree output in the draft =
still illustrate using the "split oc-style config/state structure" and =
hence also need to be updated.  Probably this could be done as part of =
the WG LC.
> To find the instances, just search the draft for "rw config" and "ro =
state".
> Thanks,
> Rob
> =20
> On 02/07/2017 22:42, Xufeng Liu wrote:
>> An updated revision of the TE topology model has been posted at =
https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-10 =
<https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-10>.
>> =20
>> This new revision now contains the NMDA compliant module and a =
companion =E2=80=9C-state=E2=80=9D module, after the I2RS topology model =
that we augment has been update with a =E2=80=9C-state=E2=80=9D module.
>> =20
>> Now that this issue has been solved, the authors and contributors =
think that the draft is ready for the last call.
>> =20
>> Thanks,
>> - Xufeng
>> =20
>> P.S. Because of the structure changes of the TE topology model, all =
augmenting models need to be updated. Sorry for the short notice.
>> =20
>> From: Teas [mailto:teas-bounces@ietf.org =
<mailto:teas-bounces@ietf.org>] On Behalf Of Benoit Claise
>> Sent: Monday, June 26, 2017 6:46 AM
>> To: Xufeng Liu <Xufeng_Liu@jabil.com> <mailto:Xufeng_Liu@jabil.com>; =
Robert Wilton <rwilton@cisco.com> <mailto:rwilton@cisco.com>; Mahesh =
Jethanandani <mjethanandani@gmail.com> <mailto:mjethanandani@gmail.com>; =
yang-doctors@ietf.org <mailto:yang-doctors@ietf.org>
>> Cc: Benoit Claise <bclaise@cisco.com> <mailto:bclaise@cisco.com>; =
ietf@ietf.org <mailto:ietf@ietf.org>; teas@ietf.org =
<mailto:teas@ietf.org>; draft-ietf-teas-yang-te-topo.all@ietf.org =
<mailto:draft-ietf-teas-yang-te-topo.all@ietf.org>
>> Subject: Re: [Teas] Yangdoctors last call review of =
draft-ietf-teas-yang-te-topo-08
>> =20
>> Hi Xufeng,
>>> Hi Benoit,
>>> =20
>>>> -----Original Message-----
>>>> From: Benoit Claise [mailto:bclaise@cisco.com =
<mailto:bclaise@cisco.com>]
>>>> Sent: Thursday, June 22, 2017 6:12 AM
>>>> To: Robert Wilton <rwilton@cisco.com> <mailto:rwilton@cisco.com>; =
Xufeng Liu <Xufeng_Liu@jabil.com> <mailto:Xufeng_Liu@jabil.com>;
>>>> Mahesh Jethanandani <mjethanandani@gmail.com> =
<mailto:mjethanandani@gmail.com>; yang-doctors@ietf.org =
<mailto:yang-doctors@ietf.org>
>>>> Cc: ietf@ietf.org <mailto:ietf@ietf.org>; teas@ietf.org =
<mailto:teas@ietf.org>; draft-ietf-teas-yang-te-topo.all@ietf.org =
<mailto:draft-ietf-teas-yang-te-topo.all@ietf.org>
>>>> Subject: Re: [Teas] Yangdoctors last call review of =
draft-ietf-teas-yang-te-topo-
>>>> 08
>>>> =20
>>>> Dear draft-ietf-teas-yang-te-topo authors,
>>>>> Hi Xufeng,
>>>>> =20
>>>>> OK, by tooling, I don't mean the pyang plugins that I have been
>>>>> working on to convert between different types of models.  As you
>>>>> aware, the TE YANG models can easily be converted to NMDA style =
since
>>>>> I have already done it
>>>>> (https://github.com/rgwilton/ietf-models-to-combined =
<https://github.com/rgwilton/ietf-models-to-combined>).
>>>>> =20
>>>>> My comment actually relates to the fact the structure used by TE =
YANG
>>>>> modules don't match any other YANG modules - they are using their =
own
>>>>> unique style of structure.
>>>> This is an important issue to resolve.
>>>>> =20
>>>>> Today, there are three common styles of modules:
>>>>> (1) IETF style split config/state trees (e.g. ietf-interfaces).
>>>>> (2) IETF NMDA style combined config/state trees (i.e. where all =
IETF
>>>>> modules are heading to).
>>>>> (3) OpenConfig style modules with the config/state containers
>>>>> immediately above the config leaves.
>>>>> =20
>>>>> Tooling is likely to be optimized to work with these model =
structures,
>>>>> but the TE modules do not fit into any of the three styles above.
>>>>> They are a yet another OpenConfig-like style, but that is =
different
>>>>> enough that tooling that is designed to work with OpenConfig style
>>>>> YANG modules would likely not work with the TE YANG modules.
>>>>> =20
>>>>> Specifically, for clients that expecting to work with an =
OpenConfig
>>>>> style YANG module, then if it knows the path to config leaf X, =
then
>>>>> they would expect the applied config value to be available at the =
path
>>>>> "../state/X".  But, this doesn't hold for the structure being used =
in
>>>>> the TE YANG models.
>>>>> =20
>>>>> I believe strongly that the models being produced by organizations
>>>>> should be structures in a consistent way, hence why I think that =
the
>>>>> published standard version of the TE YANG modules should =
immediately
>>>>> align to the NMDA style.
>>>> Agreed.
>>>> Here is the OPS and RTG AD message:
>>>> https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html =
<https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html>
>>>> =20
>>>> I understand that the I2RS topology YANG modules will be improved =
to the
>>>> NMDA style.
>>> [Xufeng] The I2RS topology model is already NMDA style, but the NMDA =
models are not immediately implementable without NETCONF/RESTCONF =
protocol update. We will need the "-state" module for the I2RS topology =
model (and for all the top-level models) for now.=20
>> Adding -state to the Appendix is a possibility.
>> "In all cases, the NMDA and non-NMDA modules SHOULD be published in =
the same document, with NMDA modules in the document main body and the =
non-NMDA modules in an Appendix."
>> See =
https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html =
<https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html>
>>=20
>>=20
>>> While the NMDA is nice, the NMDA discussions have already =
significantly delayed publishing new models, and doing NMDA without =
staging will further delay the process.
>> This is not solving the important issue brought up by Rob Witlon:
>>> My comment actually relates to the fact the structure used by TE =
YANG modules don't match any other YANG modules - they are using their =
own unique style of structure.
>> Regards, B.
>>=20
>>=20
>>> =20
>>> Thanks,  Xufeng
>>>> =20
>>>> Regards, Benoit
>>>>> =20
>>>>> Thanks,
>>>>> Rob
>>>>> =20
>>>>> =20
>>>>> On 22/06/2017 04:16, Xufeng Liu wrote:
>>>>>> Hi Rob,
>>>>>> =20
>>>>>> While the tooling is very nice to have, especially for writing =
new
>>>>>> models or converting models, we do not have to use it for every
>>>>>> model. It seems not necessary to use the tooling on this model =
for
>>>>>> now. We already know that we can manually convert it to NMDA =
style if
>>>>>> needed.
>>>>>> =20
>>>>>> Thanks,
>>>>>> - Xufeng
>>>>>> =20
>>>>>>> -----Original Message-----
>>>>>>> From: Robert Wilton [mailto:rwilton@cisco.com =
<mailto:rwilton@cisco.com>]
>>>>>>> Sent: Wednesday, June 21, 2017 5:34 AM
>>>>>>> To: Xufeng Liu <Xufeng_Liu@jabil.com> =
<mailto:Xufeng_Liu@jabil.com>; Mahesh Jethanandani
>>>>>>> <mjethanandani@gmail.com> <mailto:mjethanandani@gmail.com>; =
yang-doctors@ietf.org <mailto:yang-doctors@ietf.org>
>>>>>>> Cc: ietf@ietf.org <mailto:ietf@ietf.org>; teas@ietf.org =
<mailto:teas@ietf.org>;
>>>>>>> draft-ietf-teas-yang-te-topo.all@ietf.org =
<mailto:draft-ietf-teas-yang-te-topo.all@ietf.org>
>>>>>>> Subject: Re: [Teas] Yangdoctors last call review of
>>>>>>> draft-ietf-teas-yang-te-topo-
>>>>>>> 08
>>>>>>> =20
>>>>>>> Hi Xufeng,
>>>>>>> =20
>>>>>>> On 12/06/2017 22:28, Xufeng Liu wrote:
>>>>>>>> Hi Mahesh,
>>>>>>>> =20
>>>>>>>> Thank you much for the review. We have submitted an updated =
draft
>>>>>>> (https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09 =
<https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09>) to
>>>>>>> address these issues. More detailed explanations are put below
>>>>>>> inline.
>>>>>>>> If the responses and updates are satisfactory, we are ready for =
the
>>>>>>>> last call.
>>>>>>>> =20
>>>>>>>> Best regards,
>>>>>>>> - Xufeng
>>>>>>>> =20
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: Mahesh Jethanandani [mailto:mjethanandani@gmail.com =
<mailto:mjethanandani@gmail.com>]
>>>>>>>>> Sent: Wednesday, May 24, 2017 11:44 AM
>>>>>>>>> To: yang-doctors@ietf.org <mailto:yang-doctors@ietf.org>
>>>>>>>>> Cc: ietf@ietf.org <mailto:ietf@ietf.org>; teas@ietf.org =
<mailto:teas@ietf.org>;
>>>>>>>>> draft-ietf-teas-yang-te-topo.all@ietf.org =
<mailto:draft-ietf-teas-yang-te-topo.all@ietf.org>
>>>>>>>>> Subject: Yangdoctors last call review of
>>>>>>>>> draft-ietf-teas-yang-te-topo-08
>>>>>>>>> =20
>>>>>>>>> Reviewer: Mahesh Jethanandani
>>>>>>>>> Review result: Ready with Issues
>>>>>>>>> =20
>>>>>>>>> Document reviewed: draft-ietf-teas-yang-te-topo-08
>>>>>>>>> =20
>>>>>>>>> Status: Ready with Issues
>>>>>>>>> =20
>>>>>>>>> I am not an expert in Traffic Engineering. This review is =
looking
>>>>>>>>> at the draft from a YANG perspective. With that said, I have
>>>>>>>>> marked it as =E2=80=9CReady
>>>>>>> with Issues=E2=80=9D
>>>>>>>>> because of some of the points discussed below.
>>>>>>>>> =20
>>>>>>>>> Summary:
>>>>>>>>> =20
>>>>>>>>> This document defines a YANG data model for representing,
>>>>>>>>> retrieving and manipulating TE Topologies. The model serves as =
a
>>>>>>>>> base model that other technology specific TE Topology models =
can
>>>> augment.
>>>>>>>>> =20
>>>>>>>>> Comments:
>>>>>>>>> =20
>>>>>>>>> Almost all the containers in the model are presence =
containers. Is
>>>>>>>>> there a reason why they have to be presence containers? Note, =
that
>>>>>>>>> presence containers are containers whose existence itself
>>>>>>>>> represents configuration data. What particular configuration =
data
>>>>>>>>> is each container
>>>>>>> representing in itself?
>>>>>>>> [Xufeng] Containers that use =E2=80=9Cpresence=E2=80=9D are:
>>>>>>>>     - Container =E2=80=9Cunderlay=E2=80=9D
>>>>>>>>       o  We have changed 13 occurrences of such containers to =
be
>>>>>>>> not
>>>>>>> presence container.
>>>>>>>>     - Container =E2=80=9Cte=E2=80=9D under augmentation
>>>>>>>>       o  To indicate that =E2=80=9CTE=E2=80=9D is enabled =
(configuration data)
>>>>>>>>       o  Also used to do augmentation. The =E2=80=9Cpresence=E2=80=
=9D statement can
>>>>>>> prevent the mandatory child from affecting augmented base model.
>>>>>>>>     - /nw:networks/nw:network/nw:network-types/te-topology!
>>>>>>>>       o  A mechanism required by I2RS topology model to specify =
the
>>>>>>> topology type.
>>>>>>>>> It is difficult to co-relate the diagram with the model itself
>>>>>>>>> because of different terms being used to define different =
parts of
>>>>>>>>> the model.
>>>>>>>>> There is =E2=80=9CTE Topology Model=E2=80=9D and then there is =
=E2=80=9CGeneric TE
>>>>>>>>> Topology
>>>>>>> Model=E2=80=9D.
>>>>>>>>> Are these one and the same models? If so, a common term for =
both
>>>>>>>>> of them would be helpful.
>>>>>>>> [Xufeng] Yes. These two terms are the same. Figure 12, Figure =
13,
>>>>>>>> and relevant
>>>>>>> descriptions have been updated to make the document consistent.
>>>>>>>>> There is extensive use of groupings in the document. However, =
not
>>>>>>>>> all instances of groupings are used multiple number of times.
>>>>>>>>> Where they are not being repeated, it would be better to move =
the
>>>>>>>>> grouping directly where the uses statement resides. Case in =
point
>>>>>>>>> the grouping
>>>>>>> connectivity-label-restriction-list.
>>>>>>>> [Xufeng] We have removed the following groupings
>>>>>>>>       te-link-augment
>>>>>>>>       te-node-augment
>>>>>>>>       te-termination-point-augment
>>>>>>>>       te-topologies-augment
>>>>>>>>       te-topology-augment
>>>>>>>>       te-link-state-underlay-attributes
>>>>>>>>       te-node-state-derived-notification
>>>>>>>>       te-topology-type
>>>>>>>> =20
>>>>>>>> The remaining groupings have been kept so that we can:
>>>>>>>>     - Share the groupings in this model
>>>>>>>>     - Prepare to be shared by a model augmenting this model
>>>>>>>>     - Prevent a grouping or configuration section from being =
too long
>>>>>>>>     - Improve readability
>>>>>>>> =20
>>>>>>>>> The split between config and state containers does not seem to
>>>>>>>>> follow any particular pattern.
>>>>>>>> [Xufeng] The pattern is clear:
>>>>>>>> For each manageable entity (object), there is a config =
container
>>>>>>>> and state
>>>>>>> container. The configurable properties go into the config =
container
>>>>>>> and state properties go into the state container. Such objects =
are
>>>>>>> identified by a list item or a presence container so that the
>>>>>>> =E2=80=9Ccreate=E2=80=9D, =E2=80=9Cdelete=E2=80=9D, and =
=E2=80=9Cmodify=E2=80=9D
>>>>>>> operations
>>>>>>> can be performed on them. The non-presence containers do not
>>>>>>> represent configuration data so they do not introduce such =
objects.
>>>>>>>>> It is neither a top level split, as is the case with existing =
IETF
>>>>>>>>> models,
>>>>>>>> [Xufeng] We could not do top level split because the base I2RS
>>>>>>>> network
>>>>>>> topology model
>>>>>>> (https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo =
<https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo>-
>>>>>>> 12) that we augment does not have the top-level split (for its =
own
>>>>>>> reasons).
>>>>>>>>> nor do they follow the OpenConfig style of splitting config =
and
>>>>>>>>> state under each relevant leaf,
>>>>>>>> [Xufeng] The pattern is consistent with this style in =
principle,
>>>>>>>> with some
>>>>>>> adjustments to fit to our multiple levels of hierarchy.
>>>>>>> This is effectively a new forth style of YANG models that is not
>>>>>>> consistent with any of the three existing styles, i.e.:
>>>>>>>    - Current IETF config/state split model style
>>>>>>>    - NMDA combined config/state tree
>>>>>>>    - OpenConfig split config/state containers immediately above =
the
>>>>>>> config true leaves.
>>>>>>> =20
>>>>>>> Tooling that it designed to work with OpenConfig models will =
need
>>>>>>> customization to work with these TE models because the =
config/state
>>>>>>> containers will not be where the tooling expects them to be.
>>>>>>> =20
>>>>>>> Thanks,
>>>>>>> Rob
>>>>> =20
>>>>> .
>>>>> =20
>>> =20
>> =20
> =20

Mahesh Jethanandani
mjethanandani@gmail.com




--Apple-Mail=_878BBB3D-E53E-4A9D-9A7D-69573F8471A8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Also, couple of changes in the YANG modules:<div class=3D""><br=
 class=3D""></div><div class=3D"">Under revision, can you make sure =
there is a reference back to the RFC number that will be assigned to the =
draft. Something like:<div class=3D""><br class=3D""></div><div =
class=3D""><div class=3D"">&nbsp; revision "YYYY-MM-DD" {</div><div =
class=3D"">&nbsp; &nbsp; description</div><div class=3D"">&nbsp; &nbsp; =
&nbsp;"Initial version";</div><div class=3D"">&nbsp; &nbsp; =
reference</div><div class=3D"">&nbsp; &nbsp; &nbsp;"RFC XXXX: YANG - TE =
Topology";</div><div class=3D"">&nbsp; }</div><div class=3D""><br =
class=3D""></div><div class=3D"">with a note to RFC editor to replace =
XXXX with the number assigned to the RFC.</div><div class=3D""><br =
class=3D""></div><div style=3D"orphans: 2; widows: 2;" class=3D"">Prefix =
organization with IETF. Something like =E2=80=9CIETF&nbsp;<span =
style=3D"font-size: 13.3333px; orphans: 2; widows: 2;" class=3D"">Traffic =
Engineering Architecture and Signaling (TEAS)&nbsp;</span><span =
style=3D"font-size: 13.3333px; orphans: 2; widows: 2;" class=3D"">Working =
Group</span><font size=3D"2" class=3D"">=E2=80=9D</font></div><div =
class=3D""><span style=3D"font-size: 13.3333px; orphans: 2; widows: 2;" =
class=3D""><br class=3D""></span></div><div class=3D""><span =
style=3D"font-size: 13.3333px; orphans: 2; widows: 2;" =
class=3D"">Thanks.</span></div><div class=3D""><br class=3D""></div><div =
class=3D""><br class=3D""></div><div><blockquote type=3D"cite" =
class=3D""><div class=3D"">On Jul 3, 2017, at 3:25 PM, Xufeng Liu &lt;<a =
href=3D"mailto:xufeng.liu.ietf@gmail.com" =
class=3D"">xufeng.liu.ietf@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"WordSection1" style=3D"page: WordSection1; font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
background-color: rgb(255, 255, 255);"><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"color: windowtext;" class=3D"">HI Rob,<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"color: windowtext;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">Just posted<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-teas-yang-te-topo/" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-teas-yang-te-topo/<=
/a><span class=3D"Apple-converted-space">&nbsp;</span>&nbsp;to fix the =
snippets, along with a missing IANA entry.<span style=3D"color: =
windowtext;" class=3D""><o:p class=3D""></o:p></span></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"color: windowtext;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"color: windowtext;" class=3D"">Thanks,<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"color: windowtext;" class=3D"">- Xufeng<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"color: windowtext;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div style=3D"border-style: none =
none none solid; border-left-color: blue; border-left-width: 1.5pt; =
padding: 0in 0in 0in 4pt;" class=3D""><div class=3D""><div =
style=3D"border-style: solid none none; border-top-color: rgb(225, 225, =
225); border-top-width: 1pt; padding: 3pt 0in 0in;" class=3D""><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><b class=3D""><span style=3D"color: =
windowtext;" class=3D"">From:</span></b><span style=3D"color: =
windowtext;" class=3D""><span =
class=3D"Apple-converted-space">&nbsp;</span>Robert Wilton [<a =
href=3D"mailto:rwilton@cisco.com" =
class=3D"">mailto:rwilton@cisco.com</a>]<span =
class=3D"Apple-converted-space">&nbsp;</span><br class=3D""><b =
class=3D"">Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Monday, July 3, 2017 5:13 =
AM<br class=3D""><b class=3D"">To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Xufeng Liu &lt;<a =
href=3D"mailto:xufeng.liu.ietf@gmail.com" =
class=3D"">xufeng.liu.ietf@gmail.com</a>&gt;; 'Benoit Claise' &lt;<a =
href=3D"mailto:bclaise@cisco.com" class=3D"">bclaise@cisco.com</a>&gt;; =
'Xufeng Liu' &lt;<a href=3D"mailto:Xufeng_Liu@jabil.com" =
class=3D"">Xufeng_Liu@jabil.com</a>&gt;; 'Mahesh Jethanandani' &lt;<a =
href=3D"mailto:mjethanandani@gmail.com" =
class=3D"">mjethanandani@gmail.com</a>&gt;; <a =
href=3D"mailto:yang-doctors@ietf.org" =
class=3D"">yang-doctors@ietf.org</a><br class=3D""><b =
class=3D"">Cc:</b><span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:ietf@ietf.org" class=3D"">ietf@ietf.org</a>; <a =
href=3D"mailto:teas@ietf.org" class=3D"">teas@ietf.org</a>; <a =
href=3D"mailto:draft-ietf-teas-yang-te-topo.all@ietf.org" =
class=3D"">draft-ietf-teas-yang-te-topo.all@ietf.org</a><br class=3D""><b =
class=3D"">Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [Teas] Yangdoctors last =
call review of draft-ietf-teas-yang-te-topo-08<o:p =
class=3D""></o:p></span></div></div></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div><div class=3D"">Hi =
Xufeng,<o:p class=3D""></o:p></div><div class=3D"">Thanks for updating =
the modules to be NMDA compliant.&nbsp; I think that getting structural =
consistency across the IETF YANG modules will make them far more =
compelling as a solution.<o:p class=3D""></o:p></div><div class=3D"">I =
noticed that some of the snippets of YANG tree output in the draft still =
illustrate using the "split oc-style config/state structure" and hence =
also need to be updated.&nbsp; Probably this could be done as part of =
the WG LC.<o:p class=3D""></o:p></div><div class=3D"">To find the =
instances, just search the draft for "rw config" and "ro state".<o:p =
class=3D""></o:p></div><div class=3D"">Thanks,<br class=3D"">Rob<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div class=3D""><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">On 02/07/2017 22:42, Xufeng Liu wrote:<o:p =
class=3D""></o:p></div></div><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">An updated revision of the TE topology model has been posted =
at<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-10" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-10</a>=
.<o:p class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">&nbsp;<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">This new =
revision now contains the NMDA compliant module and a companion =
=E2=80=9C-state=E2=80=9D module, after the I2RS topology model that we =
augment has been update with a =E2=80=9C-state=E2=80=9D module.<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">&nbsp;<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">Now that =
this issue has been solved, the authors and contributors think that the =
draft is ready for the last call.<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">&nbsp;<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">Thanks,<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">- Xufeng<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">&nbsp;<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">P.S. Because of the structure changes =
of the TE topology model, all augmenting models need to be updated. =
Sorry for the short notice.<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"color: windowtext;" =
class=3D"">&nbsp;</span><o:p class=3D""></o:p></div><div =
style=3D"border-style: none none none solid; border-left-color: blue; =
border-left-width: 1.5pt; padding: 0in 0in 0in 4pt;" class=3D""><div =
class=3D""><div style=3D"border-style: solid none none; =
border-top-color: rgb(225, 225, 225); border-top-width: 1pt; padding: =
3pt 0in 0in;" class=3D""><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><b =
class=3D""><span style=3D"color: windowtext;" =
class=3D"">From:</span></b><span style=3D"color: windowtext;" =
class=3D""><span class=3D"Apple-converted-space">&nbsp;</span>Teas [<a =
href=3D"mailto:teas-bounces@ietf.org" style=3D"color: purple; =
text-decoration: underline;" =
class=3D"">mailto:teas-bounces@ietf.org</a>]<span =
class=3D"Apple-converted-space">&nbsp;</span><b class=3D"">On Behalf =
Of<span class=3D"Apple-converted-space">&nbsp;</span></b>Benoit =
Claise<br class=3D""><b class=3D"">Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Monday, June 26, 2017 6:46 =
AM<br class=3D""><b class=3D"">To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Xufeng Liu<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:Xufeng_Liu@jabil.com" style=3D"color: purple; =
text-decoration: underline;" class=3D"">&lt;Xufeng_Liu@jabil.com&gt;</a>; =
Robert Wilton<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:rwilton@cisco.com" style=3D"color: purple; =
text-decoration: underline;" class=3D"">&lt;rwilton@cisco.com&gt;</a>; =
Mahesh Jethanandani<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:mjethanandani@gmail.com" style=3D"color: purple; =
text-decoration: underline;" =
class=3D"">&lt;mjethanandani@gmail.com&gt;</a>;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:yang-doctors@ietf.org" style=3D"color: purple; =
text-decoration: underline;" class=3D"">yang-doctors@ietf.org</a><br =
class=3D""><b class=3D"">Cc:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Benoit Claise<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:bclaise@cisco.com" style=3D"color: purple; =
text-decoration: underline;" =
class=3D"">&lt;bclaise@cisco.com&gt;</a>;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:ietf@ietf.org" style=3D"color: purple; text-decoration: =
underline;" class=3D"">ietf@ietf.org</a>;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:teas@ietf.org" style=3D"color: purple; text-decoration: =
underline;" class=3D"">teas@ietf.org</a>;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:draft-ietf-teas-yang-te-topo.all@ietf.org" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">draft-ietf-teas-yang-te-topo.all@ietf.org</a><br class=3D""><b =
class=3D"">Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [Teas] Yangdoctors last =
call review of draft-ietf-teas-yang-te-topo-08</span><o:p =
class=3D""></o:p></div></div></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">&nbsp;<o:p class=3D""></o:p></div><div class=3D""><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">Hi Xufeng,<o:p =
class=3D""></o:p></div></div><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">Hi =
Benoit,<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; =
font-family: 'Courier New';" class=3D"">-----Original Message-----<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">From: Benoit =
Claise [<a href=3D"mailto:bclaise@cisco.com" style=3D"color: purple; =
text-decoration: underline;" class=3D"">mailto:bclaise@cisco.com</a>]<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Sent: Thursday, =
June 22, 2017 6:12 AM<o:p class=3D""></o:p></pre><pre style=3D"margin: =
0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">To: Robert Wilton <a href=3D"mailto:rwilton@cisco.com" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">&lt;rwilton@cisco.com&gt;</a>; Xufeng Liu <a =
href=3D"mailto:Xufeng_Liu@jabil.com" style=3D"color: purple; =
text-decoration: underline;" =
class=3D"">&lt;Xufeng_Liu@jabil.com&gt;</a>;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Mahesh =
Jethanandani <a href=3D"mailto:mjethanandani@gmail.com" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">&lt;mjethanandani@gmail.com&gt;</a>; <a =
href=3D"mailto:yang-doctors@ietf.org" style=3D"color: purple; =
text-decoration: underline;" class=3D"">yang-doctors@ietf.org</a><o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Cc: <a =
href=3D"mailto:ietf@ietf.org" style=3D"color: purple; text-decoration: =
underline;" class=3D"">ietf@ietf.org</a>; <a href=3D"mailto:teas@ietf.org"=
 style=3D"color: purple; text-decoration: underline;" =
class=3D"">teas@ietf.org</a>; <a =
href=3D"mailto:draft-ietf-teas-yang-te-topo.all@ietf.org" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">draft-ietf-teas-yang-te-topo.all@ietf.org</a><o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Subject: Re: =
[Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">08<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Dear =
draft-ietf-teas-yang-te-topo authors,<o:p =
class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">Hi =
Xufeng,<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">OK,=
 by tooling, I don't mean the pyang plugins that I have been<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">working on to =
convert between different types of models.&nbsp; As you<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">aware, the TE =
YANG models can easily be converted to NMDA style since<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">I have already =
done it<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">(<a =
href=3D"https://github.com/rgwilton/ietf-models-to-combined" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">https://github.com/rgwilton/ietf-models-to-combined</a>).<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">My comment =
actually relates to the fact the structure used by TE YANG<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">modules don't =
match any other YANG modules - they are using their own<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">unique style of =
structure.<o:p class=3D""></o:p></pre></blockquote><pre style=3D"margin: =
0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">This is an important issue to resolve.<o:p =
class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Today, there are three common styles of modules:<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">(1) IETF style =
split config/state trees (e.g. ietf-interfaces).<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">(2) IETF NMDA =
style combined config/state trees (i.e. where all IETF<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">modules are =
heading to).<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">(3) =
OpenConfig style modules with the config/state containers<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">immediately =
above the config leaves.<o:p class=3D""></o:p></pre><pre style=3D"margin: =
0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Tooling is likely to be optimized to work with these model =
structures,<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">but =
the TE modules do not fit into any of the three styles above.<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">They are a yet =
another OpenConfig-like style, but that is different<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">enough that =
tooling that is designed to work with OpenConfig style<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">YANG modules =
would likely not work with the TE YANG modules.<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Specifically, =
for clients that expecting to work with an OpenConfig<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">style YANG =
module, then if it knows the path to config leaf X, then<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">they would =
expect the applied config value to be available at the path<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" =
class=3D"">"../state/X".&nbsp; But, this doesn't hold for the structure =
being used in<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">the =
TE YANG models.<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">I =
believe strongly that the models being produced by organizations<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">should be =
structures in a consistent way, hence why I think that the<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">published =
standard version of the TE YANG modules should immediately<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">align to the =
NMDA style.<o:p class=3D""></o:p></pre></blockquote><pre style=3D"margin: =
0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Agreed.<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Here is the OPS and RTG AD message:<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D""><a =
href=3D"https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html=
" style=3D"color: purple; text-decoration: underline;" =
class=3D"">https://www.ietf.org/mail-archive/web/netmod/current/msg18252.h=
tml</a><o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">I =
understand that the I2RS topology YANG modules will be improved to =
the<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">NMDA style.<o:p =
class=3D""></o:p></pre></blockquote><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">[Xufeng] The I2RS topology model is already NMDA style, but =
the NMDA models are not immediately implementable without =
NETCONF/RESTCONF protocol update. We will need the "-state" module for =
the I2RS topology model (and for all the top-level models) for now. <o:p =
class=3D""></o:p></pre></blockquote><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">Adding -state to the Appendix is a possibility.<br =
class=3D"">"In all cases, the NMDA and non-NMDA modules SHOULD be =
published in the same document, with NMDA modules in the document main =
body and the non-NMDA modules in an Appendix."<br class=3D"">See<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html=
" style=3D"color: purple; text-decoration: underline;" =
class=3D"">https://www.ietf.org/mail-archive/web/netmod/current/msg18252.h=
tml</a><br class=3D""><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></div><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">While the NMDA is nice, the NMDA discussions have already =
significantly delayed publishing new models, and doing NMDA without =
staging will further delay the process.<o:p =
class=3D""></o:p></pre></blockquote><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">This is not solving the important issue brought up by Rob =
Witlon:<o:p class=3D""></o:p></div><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">My comment actually relates to the fact the structure used by =
TE YANG modules don't match any other YANG modules - they are using =
their own unique style of structure.<o:p =
class=3D""></o:p></div></blockquote><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">Regards, B.<br class=3D""><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></div><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Thanks,&nbsp; Xufeng<o:p class=3D""></o:p></pre><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; =
font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Regards, =
Benoit<o:p class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Thanks,<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Rob<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">On =
22/06/2017 04:16, Xufeng Liu wrote:<o:p class=3D""></o:p></pre><blockquote=
 style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; =
font-family: 'Courier New';" class=3D"">Hi Rob,<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">While the =
tooling is very nice to have, especially for writing new<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">models or =
converting models, we do not have to use it for every<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">model. It seems =
not necessary to use the tooling on this model for<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">now. We already =
know that we can manually convert it to NMDA style if<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">needed.<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Thanks,<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">- Xufeng<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">-----Original Message-----<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">From: Robert Wilton [<a =
href=3D"mailto:rwilton@cisco.com" style=3D"color: purple; =
text-decoration: underline;" class=3D"">mailto:rwilton@cisco.com</a>]<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Sent: =
Wednesday, June 21, 2017 5:34 AM<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">To: Xufeng Liu <a =
href=3D"mailto:Xufeng_Liu@jabil.com" style=3D"color: purple; =
text-decoration: underline;" class=3D"">&lt;Xufeng_Liu@jabil.com&gt;</a>; =
Mahesh Jethanandani<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D""><a =
href=3D"mailto:mjethanandani@gmail.com" style=3D"color: purple; =
text-decoration: underline;" =
class=3D"">&lt;mjethanandani@gmail.com&gt;</a>; <a =
href=3D"mailto:yang-doctors@ietf.org" style=3D"color: purple; =
text-decoration: underline;" class=3D"">yang-doctors@ietf.org</a><o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Cc: <a =
href=3D"mailto:ietf@ietf.org" style=3D"color: purple; text-decoration: =
underline;" class=3D"">ietf@ietf.org</a>; <a href=3D"mailto:teas@ietf.org"=
 style=3D"color: purple; text-decoration: underline;" =
class=3D"">teas@ietf.org</a>;<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D""><a =
href=3D"mailto:draft-ietf-teas-yang-te-topo.all@ietf.org" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">draft-ietf-teas-yang-te-topo.all@ietf.org</a><o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Subject: Re: =
[Teas] Yangdoctors last call review of<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">draft-ietf-teas-yang-te-topo-<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">08<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Hi Xufeng,<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">On 12/06/2017 =
22:28, Xufeng Liu wrote:<o:p class=3D""></o:p></pre><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; =
font-family: 'Courier New';" class=3D"">Hi Mahesh,<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Thank you much =
for the review. We have submitted an updated draft<o:p =
class=3D""></o:p></pre></blockquote><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">(<a =
href=3D"https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09</a>=
) to<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">address these =
issues. More detailed explanations are put below<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">inline.<o:p =
class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">If =
the responses and updates are satisfactory, we are ready for the<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">last call.<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Best =
regards,<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">- =
Xufeng<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; =
font-family: 'Courier New';" class=3D"">-----Original Message-----<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">From: Mahesh =
Jethanandani [<a href=3D"mailto:mjethanandani@gmail.com" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">mailto:mjethanandani@gmail.com</a>]<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Sent: =
Wednesday, May 24, 2017 11:44 AM<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">To: <a href=3D"mailto:yang-doctors@ietf.org" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">yang-doctors@ietf.org</a><o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">Cc: <a href=3D"mailto:ietf@ietf.org" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">ietf@ietf.org</a>; <a href=3D"mailto:teas@ietf.org" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">teas@ietf.org</a>;<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D""><a =
href=3D"mailto:draft-ietf-teas-yang-te-topo.all@ietf.org" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">draft-ietf-teas-yang-te-topo.all@ietf.org</a><o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Subject: =
Yangdoctors last call review of<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">draft-ietf-teas-yang-te-topo-08<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Reviewer: =
Mahesh Jethanandani<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Review result: Ready with Issues<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Document =
reviewed: draft-ietf-teas-yang-te-topo-08<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">Status: Ready with Issues<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">I am not an =
expert in Traffic Engineering. This review is looking<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">at the draft =
from a YANG perspective. With that said, I have<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">marked it as =
=E2=80=9CReady<o:p class=3D""></o:p></pre></blockquote></blockquote><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">with Issues=E2=80=9D<o:p =
class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; =
font-family: 'Courier New';" class=3D"">because of some of the points =
discussed below.<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Summary:<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">This document defines a YANG data model for representing,<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">retrieving and =
manipulating TE Topologies. The model serves as a<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">base model that =
other technology specific TE Topology models can<o:p =
class=3D""></o:p></pre></blockquote></blockquote></blockquote></blockquote=
></blockquote><pre style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; =
font-family: 'Courier New';" class=3D"">augment.<o:p =
class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><blockquote style=3D"margin-top: 5pt; margin-bottom: 5pt;" =
class=3D"" type=3D"cite"><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; =
font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Comments:<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Almost all the =
containers in the model are presence containers. Is<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">there a reason =
why they have to be presence containers? Note, that<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">presence =
containers are containers whose existence itself<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">represents =
configuration data. What particular configuration data<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">is each =
container<o:p class=3D""></o:p></pre></blockquote></blockquote><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">representing in itself?<o:p =
class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">[Xufeng] Containers that use =E2=80=9Cpresence=E2=80=9D =
are:<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp; - Container =E2=80=9Cunderlay=E2=80=9D<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; o&nbsp; We have changed 13 =
occurrences of such containers to be<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">not<o:p =
class=3D""></o:p></pre></blockquote><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">presence container.<o:p class=3D""></o:p></pre><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; =
font-family: 'Courier New';" class=3D"">&nbsp;&nbsp;&nbsp; - Container =
=E2=80=9Cte=E2=80=9D under augmentation<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; o&nbsp; To =
indicate that =E2=80=9CTE=E2=80=9D is enabled (configuration data)<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; o&nbsp; Also used to do =
augmentation. The =E2=80=9Cpresence=E2=80=9D statement can<o:p =
class=3D""></o:p></pre></blockquote><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">prevent=
 the mandatory child from affecting augmented base model.<o:p =
class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp; - =
/nw:networks/nw:network/nw:network-types/te-topology!<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; o&nbsp; A mechanism required =
by I2RS topology model to specify the<o:p =
class=3D""></o:p></pre></blockquote><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">topology type.<o:p class=3D""></o:p></pre><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><blockquote style=3D"margin-top: 5pt; margin-bottom: 5pt;" =
class=3D"" type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">It is difficult =
to co-relate the diagram with the model itself<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">because of =
different terms being used to define different parts of<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">the model.<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">There is =E2=80=9C=
TE Topology Model=E2=80=9D and then there is =E2=80=9CGeneric TE<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Topology<o:p =
class=3D""></o:p></pre></blockquote></blockquote><pre style=3D"margin: =
0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Model=E2=80=9D.<o:p class=3D""></o:p></pre><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><blockquote style=3D"margin-top: 5pt; margin-bottom: 5pt;" =
class=3D"" type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Are these one =
and the same models? If so, a common term for both<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">of them would =
be helpful.<o:p class=3D""></o:p></pre></blockquote><pre style=3D"margin: =
0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">[Xufeng] Yes. These two terms are the same. Figure 12, Figure =
13,<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">and =
relevant<o:p class=3D""></o:p></pre></blockquote><pre style=3D"margin: =
0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">descriptions have been updated to make the document =
consistent.<o:p class=3D""></o:p></pre><blockquote style=3D"margin-top: =
5pt; margin-bottom: 5pt;" class=3D"" type=3D"cite"><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; =
font-family: 'Courier New';" class=3D"">There is extensive use of =
groupings in the document. However, not<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">all instances of groupings are used multiple =
number of times.<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Where they are not being repeated, it would be better to move =
the<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">grouping =
directly where the uses statement resides. Case in point<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">the =
grouping<o:p class=3D""></o:p></pre></blockquote></blockquote><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">connectivity-label-restriction-list.<o:p =
class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">[Xufeng] We have removed the following groupings<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; te-link-augment<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; te-node-augment<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
te-termination-point-augment<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
te-topologies-augment<o:p class=3D""></o:p></pre><pre style=3D"margin: =
0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; te-topology-augment<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
te-link-state-underlay-attributes<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
te-node-state-derived-notification<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;te-topology-type<o:p class=3D""></o:p></pre><pre style=3D"margin: =
0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">The=
 remaining groupings have been kept so that we can:<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp; - Share the groupings in this model<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp; - Prepare to be shared by a model =
augmenting this model<o:p class=3D""></o:p></pre><pre style=3D"margin: =
0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp; - Prevent a grouping or configuration =
section from being too long<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">&nbsp;&nbsp;&nbsp; - Improve readability<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">The=
 split between config and state containers does not seem to<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">follow any =
particular pattern.<o:p class=3D""></o:p></pre></blockquote><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">[Xufeng] The pattern is clear:<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">For each =
manageable entity (object), there is a config container<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">and state<o:p =
class=3D""></o:p></pre></blockquote><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">container. The configurable properties go into the config =
container<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">and =
state properties go into the state container. Such objects are<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">identified by a =
list item or a presence container so that the<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">=E2=80=9Ccreate=E2=
=80=9D, =E2=80=9Cdelete=E2=80=9D, and =E2=80=9Cmodify=E2=80=9D<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">operations<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">can be =
performed on them. The non-presence containers do not<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">represent =
configuration data so they do not introduce such objects.<o:p =
class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; =
font-family: 'Courier New';" class=3D"">It is neither a top level split, =
as is the case with existing IETF<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">models,<o:p =
class=3D""></o:p></pre></blockquote><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">[Xufeng] We could not do top level split because the base =
I2RS<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">network<o:p =
class=3D""></o:p></pre></blockquote><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">topology model<o:p class=3D""></o:p></pre><pre style=3D"margin:=
 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">(<a =
href=3D"https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo</=
a>-<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">12) that we =
augment does not have the top-level split (for its own<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">reasons).<o:p =
class=3D""></o:p></pre><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D"" =
type=3D"cite"><pre style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; =
font-family: 'Courier New';" class=3D"">nor do they follow the =
OpenConfig style of splitting config and<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">state under each relevant leaf,<o:p =
class=3D""></o:p></pre></blockquote><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">[Xufeng] The pattern is consistent with this style in =
principle,<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" class=3D"">with =
some<o:p class=3D""></o:p></pre></blockquote><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">adjustments to fit to our multiple levels of hierarchy.<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">This is =
effectively a new forth style of YANG models that is not<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">consistent with =
any of the three existing styles, i.e.:<o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: =
'Courier New';" class=3D"">&nbsp;&nbsp; - Current IETF config/state =
split model style<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp; - NMDA combined config/state tree<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;&nbsp; - =
OpenConfig split config/state containers immediately above the<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">config true =
leaves.<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">Tooling that it designed to work with OpenConfig models will =
need<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">customization =
to work with these TE models because the config/state<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">containers will =
not be where the tooling expects them to be.<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Thanks,<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';" class=3D"">Rob<o:p =
class=3D""></o:p></pre></blockquote></blockquote><pre style=3D"margin: =
0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in =
0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">.<o:p class=3D""></o:p></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p =
class=3D""></o:p></pre></blockquote></blockquote><pre style=3D"margin: =
0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;<o:p class=3D""></o:p></pre></blockquote><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">&nbsp;<o:p =
class=3D""></o:p></div></div></blockquote><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div></div></div></blockquote></div><br =
class=3D""><div class=3D"">
<div class=3D"">Mahesh Jethanandani</div><div class=3D""><a =
href=3D"mailto:mjethanandani@gmail.com" =
class=3D"">mjethanandani@gmail.com</a></div><div class=3D""><br =
class=3D""></div><br class=3D"Apple-interchange-newline">

</div>
<br class=3D""></div></div></body></html>=

--Apple-Mail=_878BBB3D-E53E-4A9D-9A7D-69573F8471A8--


From nobody Fri Jul  7 11:18:47 2017
Return-Path: <drc@virtualized.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59EE71317C2 for <ietf@ietfa.amsl.com>; Fri,  7 Jul 2017 11:18:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=virtualized-org.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 Y1ymz6RD6e61 for <ietf@ietfa.amsl.com>; Fri,  7 Jul 2017 11:18:44 -0700 (PDT)
Received: from mail-pg0-x233.google.com (mail-pg0-x233.google.com [IPv6:2607:f8b0:400e:c05::233]) (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 52AFE1317E3 for <ietf@ietf.org>; Fri,  7 Jul 2017 11:18:12 -0700 (PDT)
Received: by mail-pg0-x233.google.com with SMTP id j186so20768727pge.2 for <ietf@ietf.org>; Fri, 07 Jul 2017 11:18:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=virtualized-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version; bh=INc4g4aQKmd8qjvTeOIoFypi3Nz/yXLa0WXXgnb3AD4=; b=sbK2trJB/uXopVoA7BurAuKp1jFllSvWPKoaPiZ+C0sjdRNOepOyry+GaCmJg7nGvj lpewim2LsOpkxQZJRIsdnU1eWlhI5ZBxcHj5V260hKdeQ2tDYsvSfXwcmyGzDxSv5oXZ e8EF+UT+ohUd6cKiGOHg9s5VFDc9dmt2OP7aWmBRaFPZc4B355v19QGL5mwt4kvue10a WM6G1ldDb0YhaZVH6MuEL2m4P3huDSQSdcxY9lAax8jgy43/z3jTP7XHtSCdIi5LvB16 dAi43ZTQZ/uG+mNHE/Hm00/N4gPSVmZ8Z+bH1rWaoTUKE061W59AziLCZKq+K8Kc6dNt v2cw==
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:message-id:in-reply-to :references:subject:mime-version; bh=INc4g4aQKmd8qjvTeOIoFypi3Nz/yXLa0WXXgnb3AD4=; b=Q9uKqNOP7wsxogw9ed0K9+Dd1ya3lCUafxwqWzkbg7MSiXFsrIJnWO67J4MAuWnQ36 TYsfTkhGmWTqgwdvID+D+UYtL0XrreMeikYP2IduZ5SaPvTcBlDKT3xBJuQMp3dmFkLP MOvrI6G4RpWOUD9QWCgc80bmZj2KHG1yMJiyXNPBgZ4Ht8gX3U79y9JlsrSHChtlijw4 Wx7wbJP/ZK7FECA57Fzgy6rW4TW0d/7VxDrVM4xzbQYhLAN+V7eeLhLXTSniH0diGQKs GgWA3nnvr7lQKv5gBo2dLTMh0zeoZtniloypgFmOBSZ17ZtHpIiAIUfpBZN95VlCDBMw R8BA==
X-Gm-Message-State: AIVw111ZxlExvXrdbhGSXXwLyM9o3BC0g3qDqgXojWTLPQOqa4o6vxJF +JHq0UYKps61NmVr
X-Received: by 10.84.215.135 with SMTP id l7mr4429955pli.194.1499451491804; Fri, 07 Jul 2017 11:18:11 -0700 (PDT)
Received: from [192.168.7.50] (c-24-6-172-77.hsd1.ca.comcast.net. [24.6.172.77]) by smtp.gmail.com with ESMTPSA id s64sm10021276pfd.77.2017.07.07.11.18.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 07 Jul 2017 11:18:10 -0700 (PDT)
Date: Fri, 7 Jul 2017 09:32:09 -0700
From: David Conrad <drc@virtualized.org>
To: Nico Williams <nico@cryptonector.com>, Mark Andrews <marka@isc.org>
Cc: John C Klensin <john-ietf@jck.com>, dnsop <dnsop@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>, Paul Vixie <paul@redbarn.org>,  IETF Rinse Repeat <ietf@ietf.org>
Message-ID: <61283000-0504-43f5-a0b0-65e48e399efc@Spark>
In-Reply-To: <20170707065637.EB9C07DBDEF2@rock.dv.isc.org>
References: <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <CAMm+Lwjd6xVp-EDp=doevx=AP8qws_Mv++aL733yHEyUF72EMA@mail.gmail.com> <562EC659F89FA92A09CAC4DB@PSB> <20170706153955.GB3393@localhost> <20170706215236.99A8C7DB2FBA@rock.dv.isc.org> <20170707055315.GC3393@localhost> <20170707065637.EB9C07DBDEF2@rock.dv.isc.org>
Subject: Re: [DNSOP] new DNS classes
X-Readdle-Message-ID: 61283000-0504-43f5-a0b0-65e48e399efc@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="595fd061_6b8b4567_624"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LBUtAYDkZwR8eM1YIl2m6cYRhxQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 18:18:46 -0000

--595fd061_6b8b4567_624
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Mark,

On Jul 6, 2017, 11:56 PM -0700, Mark Andrews <marka=40isc.org>, wrote:
> > > Or you could stop trying to reinforce the myth that new RR types
> > > are hard to deploy. They really aren't.

Please stop trying to minimize the amount of work here. They really are. =
Not for you, but for the folks who make domain names available for use by=
 non-technical types.

> Then change domain hosting providers and tell them why or run you
> own master server or use a service which allows for dynamic updates
> which shouldn't care about the record types. There are plenty of
> DNS providers that will slave content.

The number of folks who even understand what you've written above, much l=
ess can actually do it, is insignificant in the context of seeing signifi=
cant adoption of new RRs.

> As a DNS server vendor

You need to look at the wider world.

The DNS server side of deploying a new RR is the easiest part and while n=
ecessary, it's no where even close to sufficient to getting a new RR depl=
oyed. It's like trying to move the automobile industry to hydrogen fuel: =
building a car that runs on hydrogen is easy, relatively speaking. Howeve=
r to actually do anything useful with that car, you need need to modify t=
he fuel delivery infrastructure, which is vastly harder, involves a vastl=
y larger set of players, very few of which have any sort of financial inc=
entive to make the change. Standard chicken-or-egg problem.

ICANN funded John Levine to develop=C2=A0https://metacpan.org/release/JRL=
EVINE/Net-DNS-Extlang-0.1 to try to make it easier to break the chicken-o=
r-egg problem by hopefully giving the folks who provide the UIs by which =
domain names are managed by non-geeks better tools. However, that's just =
the first step -- the domain name managers still need to be encouraged to=
 use them. =C2=A0Pretending this is an easy problem isn't helping.

Regards,
-drc

--595fd061_6b8b4567_624
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<html xmlns=3D=22http://www.w3.org/1999/xhtml=22>
<head>
<title></title>
</head>
<body>
<div name=3D=22messageBodySection=22 style=3D=22font-size: 14px; font-fam=
ily: -apple-system, BlinkMacSystem=46ont, sans-serif;=22>Mark,</div>
<div name=3D=22messageReplySection=22 style=3D=22font-size: 14px; font-fa=
mily: -apple-system, BlinkMacSystem=46ont, sans-serif;=22><br />
On Jul 6, 2017, 11:56 PM -0700, Mark Andrews &lt;marka=40isc.org&gt;, wro=
te:<br />
<blockquote type=3D=22cite=22 style=3D=22margin: 5px 5px; padding-left: 1=
0px; border-left: thin solid =231abc9c;=22>
<blockquote type=3D=22cite=22 style=3D=22margin: 5px 5px; padding-left: 1=
0px; border-left: thin solid =23e67e22;=22></blockquote>
<blockquote type=3D=22cite=22 style=3D=22margin: 5px 5px; padding-left: 1=
0px; border-left: thin solid =23e67e22;=22>
<blockquote type=3D=22cite=22 style=3D=22margin: 5px 5px; padding-left: 1=
0px; border-left: thin solid =233498db;=22>Or you could stop trying to re=
inforce the myth that new RR types<br />
are hard to deploy. They really aren't.<br /></blockquote>
</blockquote>
</blockquote>
<div><br /></div>
Please stop trying to minimize the amount of work here. They really are. =
Not for you, but for the folks who make domain names available for use by=
 non-technical types.<br />
<div><br /></div>
<blockquote type=3D=22cite=22 style=3D=22margin: 5px 5px; padding-left: 1=
0px; border-left: thin solid =231abc9c;=22>Then change domain hosting pro=
viders and tell them why or run you<br />
own master server or use a service which allows for dynamic updates<br />=

which shouldn't care about the record types. There are plenty of<br />
DNS providers that will slave content.&=23160;<br /></blockquote>
<div><br /></div>
<div>The number of folks who even understand what you've written above, m=
uch less can actually do it, is insignificant in the context of seeing si=
gnificant adoption of new RRs.&=23160;</div>
<div><br /></div>
<blockquote type=3D=22cite=22 style=3D=22margin: 5px 5px; padding-left: 1=
0px; border-left: thin solid =231abc9c;=22>As a DNS server vendor &=23160=
;</blockquote>
<div><br /></div>
<div>You need to look at the wider world.</div>
<div><br /></div>
<div>The DNS server side of deploying a new RR is the easiest part and wh=
ile necessary, it's no where even close to sufficient to getting a new RR=
 deployed. It's like trying to move the automobile industry to hydrogen f=
uel: building a car that runs on hydrogen is easy, relatively speaking. H=
owever to actually do anything useful with that car, you need need to mod=
ify the fuel delivery infrastructure, which is vastly harder, involves a =
vastly larger set of players, very few of which have any sort of financia=
l incentive to make the change. Standard chicken-or-egg problem.</div>
<div><br /></div>
<div>ICANN funded John Levine to develop&=23160;https://metacpan.org/rele=
ase/JRLEVINE/Net-DNS-Extlang-0.1 to try to make it easier to break the ch=
icken-or-egg problem by hopefully giving the folks who provide the UIs by=
 which domain names are managed by non-geeks better tools. However, that'=
s just the first step -- the domain name managers still need to be encour=
aged to use them. &=23160;Pretending this is an easy problem isn't helpin=
g.</div>
<div><br /></div>
<div>Regards,</div>
<div>-drc</div>
</div>
</body>
</html>

--595fd061_6b8b4567_624--


From nobody Fri Jul  7 11:27:52 2017
Return-Path: <chinese.apricot@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9387C13162F; Fri,  7 Jul 2017 11:27:48 -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 BKDZkK-TBt8T; Fri,  7 Jul 2017 11:27:46 -0700 (PDT)
Received: from mail-it0-x22d.google.com (mail-it0-x22d.google.com [IPv6:2607:f8b0:4001:c0b::22d]) (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 941BD1275AB; Fri,  7 Jul 2017 11:27:46 -0700 (PDT)
Received: by mail-it0-x22d.google.com with SMTP id m84so1432175ita.0; Fri, 07 Jul 2017 11:27:46 -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=/RfGFmSWwIV6Va3Gv2F7w4L60uerI1klCPmqZbtIFtg=; b=AM1/OLJLfzTWwXVCLXMisolAjG8r+iEKJXWAsCuvcit5zNBACc2JfU50PRNvScnCtw ab/I0yznMVUkKysULeLUUGv715E3iodz4jM+Pnye36XZ3WbO2P/UyudPQzVD2FtxMKBE 6h2erVh90k+nxWahjYiWpJ5Np3bwdz45lLl3KtU7CN/8AlccdO164vjfzhKZZ9nljDLD HvvAAqpbDJxOlAFdUIh+p6fCA7J22m0Ga2cdtrRU8ce7YAJybAMIwmqalgA8J6Trpqgz ePYTFdKmqScMwT90sr8X95akprtyvq41zkkUW228UBm2wxUeBtAmEALbebWVY63t/y+4 9gag==
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=/RfGFmSWwIV6Va3Gv2F7w4L60uerI1klCPmqZbtIFtg=; b=k2JWHSQt9HlMJO4NL4jLcITUbmXjNQYnPaBfVnCuinBw1WV+bfyBgtMCpsmRGOzx6U B4cc549PuZAaslF8brPiTOKrgZZ0IOpOuOC3HlBULA1p+C+lxiJ3BzDNF1TK0DZKIJcY H0huRbuerwAJtYbMWT1hqZ6oi8C5ZPwLoIdNywxAkRDonq2pWCWYSJwiCXVBLfO01+r6 7h07Ayb+9xP2XqX1r6IFjsmuW9bo/W5Q90m6+MR4thYih9pQm9Zk2UTxBaHiFYeXWcyy Wfhlps8DRmEzzKmJE/gMZaHwCyuD1SWawVpce4bfQt6rfWDL0ypyyMkn5gcnfTxpSExl v8NA==
X-Gm-Message-State: AIVw113H/fA8qQrdcYdIzPd8E+DfrHhFMbbgh1RrBsrL8FIbt8oss8gj F3379SLy8wrtIGlVa9zPgWMkw4Emeg==
X-Received: by 10.36.248.4 with SMTP id a4mr249978ith.69.1499452065951; Fri, 07 Jul 2017 11:27:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.18.170 with HTTP; Fri, 7 Jul 2017 11:27:45 -0700 (PDT)
In-Reply-To: <20170707165513.GG3393@localhost>
References: <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <m2mv8jw9qq.wl-randy@psg.com> <33235E8D-147D-4178-BC45-DFC1E1C27B99@davecake.net> <20170707165513.GG3393@localhost>
From: william manning <chinese.apricot@gmail.com>
Date: Fri, 7 Jul 2017 11:27:45 -0700
Message-ID: <CACfw2hi8Grd+jeyXTR-Hfcx+Axeh8YjJzwO=QM3MndhhwvYZJw@mail.gmail.com>
Subject: Re: new DNS classes
To: Nico Williams <nico@cryptonector.com>
Cc: David Cake <dave@davecake.net>, Randy Bush <randy@psg.com>, dnsop <dnsop@ietf.org>,  Paul Vixie <paul@redbarn.org>, IETF Rinse Repeat <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c0b1cb4bfb7fa0553be63aa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DNB7j54uHkhUKz41qOYjFm7qVM8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 18:27:48 -0000

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

You need a better imagination then.   mDNS is a crippled DNS implementation
that was hobbled on purpose.   HS was/is an entirely different addressing
scheme that emerged from project Athena @ MIT.  To the extent that when all
you have been given is the IN class and it's associated rooted hierarchy,
you first,second,&third inclination is to treat EVERYTHING as being easily
integrated into that model.  And the ietf is going to go right along with
you.   After all, when all you have is a hammer, everything looks like a
nail.

On Saturday, July 8, 2017, Nico Williams <nico@cryptonector.com> wrote:

> On Fri, Jul 07, 2017 at 03:32:21PM +0200, David Cake wrote:
> > > On 5 Jul 2017, at 10:47 am, Randy Bush <randy@psg.com <javascript:;>>
> wrote:
> > >
> > > i think avoiding icann is a red herring.  if the draft in question ha=
d
> > > done a decent job of exploring the taxa of needs for name resolution
> > > outside of the 'normal' topology, we would have the start of a base o=
n
> > > which to discuss this.
> >
> > If you have a single centralised root for your new class, you will
> > probably either recreate the problems of ICANN, or create one or more
> > of the problems that ICANN has very consciously tried to avoid.  If
> > you have a system of name resolution that avoids the need for a
> > centralised root, you probably don=E2=80=99t need a new class to implem=
ent it.
> > The few marginal cases that need to interact with the one root but not
> > be ICANN controlled are why we have the RFC 6761 process.
> >
> > I agree a taxa of needs that do not fit within those three cases would
> > have been useful.
>
> Well, there's a) the rooted hierarchy of the public DNS (IN class),
> b) mDNS (which isn't really DNS, just a local discovery mechanism based
> on the DNS protocol), c) the HS class, which traditionally wasn't used
> in a federated manner (but maybe I'm wrong about that), so it doesn't
> need a rooted hierarchy, though it also could use one.  (b) and (c) are
> niches, with no real place on the open, public Internet.
>
> One could use something like HS as an alternative to LDAP, say, but
> recall that the vision of a world of federated and open directories
> never materialized NOT because of limitations of DAP/LDAP, but because
> of confidentiality/ privacy considerations.  Such a class would really
> need to use the same rooted hierarchy, and, really, the same root, as
> the public DNS IN class -- i.e., an IN RR type namespace extension
> class, so it's best to consider such a class in those terms rather than
> as a "directory class".
>
> I am having a very difficult time imagining, say, a peer-to-peer or
> web-of-trust DNS (other than mDNS).  Perhaps my imagination fails me.
>
> A rooted hierarchy is and has been incredibly useful, and the simplest
> method of providing a consisten Internet to all users.  It seems to me
> very unlikely that we'll ever move from that.  At most we may have
> alternative roots, but a mostly common set of TLDs (e.g., as happens in
> many private (corporate) networks).
>
> Nico
> --
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org <javascript:;>
> https://www.ietf.org/mailman/listinfo/dnsop
>

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

You need a better imagination then. =C2=A0 mDNS is a crippled DNS implement=
ation that was hobbled on purpose. =C2=A0 HS was/is an entirely different a=
ddressing scheme that emerged from project Athena @ MIT.=C2=A0 To the exten=
t that when all you have been given is the IN class and it&#39;s associated=
 rooted hierarchy, you first,second,&amp;third inclination is to treat EVER=
YTHING as being easily integrated into that model.=C2=A0 And the ietf is go=
ing to go right along with you. =C2=A0 After all, when all you have is a ha=
mmer, everything looks like a nail.<br><br>On Saturday, July 8, 2017, Nico =
Williams &lt;<a href=3D"mailto:nico@cryptonector.com">nico@cryptonector.com=
</a>&gt; wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, Jul 07, 2017 at 0=
3:32:21PM +0200, David Cake wrote:<br>
&gt; &gt; On 5 Jul 2017, at 10:47 am, Randy Bush &lt;<a href=3D"javascript:=
;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;randy@psg.com&#39;)">randy@psg=
.com</a>&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt; i think avoiding icann is a red herring.=C2=A0 if the draft in qu=
estion had<br>
&gt; &gt; done a decent job of exploring the taxa of needs for name resolut=
ion<br>
&gt; &gt; outside of the &#39;normal&#39; topology, we would have the start=
 of a base on<br>
&gt; &gt; which to discuss this.<br>
&gt;<br>
&gt; If you have a single centralised root for your new class, you will<br>
&gt; probably either recreate the problems of ICANN, or create one or more<=
br>
&gt; of the problems that ICANN has very consciously tried to avoid.=C2=A0 =
If<br>
&gt; you have a system of name resolution that avoids the need for a<br>
&gt; centralised root, you probably don=E2=80=99t need a new class to imple=
ment it.<br>
&gt; The few marginal cases that need to interact with the one root but not=
<br>
&gt; be ICANN controlled are why we have the RFC 6761 process.<br>
&gt;<br>
&gt; I agree a taxa of needs that do not fit within those three cases would=
<br>
&gt; have been useful.<br>
<br>
Well, there&#39;s a) the rooted hierarchy of the public DNS (IN class),<br>
b) mDNS (which isn&#39;t really DNS, just a local discovery mechanism based=
<br>
on the DNS protocol), c) the HS class, which traditionally wasn&#39;t used<=
br>
in a federated manner (but maybe I&#39;m wrong about that), so it doesn&#39=
;t<br>
need a rooted hierarchy, though it also could use one.=C2=A0 (b) and (c) ar=
e<br>
niches, with no real place on the open, public Internet.<br>
<br>
One could use something like HS as an alternative to LDAP, say, but<br>
recall that the vision of a world of federated and open directories<br>
never materialized NOT because of limitations of DAP/LDAP, but because<br>
of confidentiality/ privacy considerations.=C2=A0 Such a class would really=
<br>
need to use the same rooted hierarchy, and, really, the same root, as<br>
the public DNS IN class -- i.e., an IN RR type namespace extension<br>
class, so it&#39;s best to consider such a class in those terms rather than=
<br>
as a &quot;directory class&quot;.<br>
<br>
I am having a very difficult time imagining, say, a peer-to-peer or<br>
web-of-trust DNS (other than mDNS).=C2=A0 Perhaps my imagination fails me.<=
br>
<br>
A rooted hierarchy is and has been incredibly useful, and the simplest<br>
method of providing a consisten Internet to all users.=C2=A0 It seems to me=
<br>
very unlikely that we&#39;ll ever move from that.=C2=A0 At most we may have=
<br>
alternative roots, but a mostly common set of TLDs (e.g., as happens in<br>
many private (corporate) networks).<br>
<br>
Nico<br>
--<br>
<br>
______________________________<wbr>_________________<br>
DNSOP mailing list<br>
<a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;DNSOP@ie=
tf.org&#39;)">DNSOP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" target=3D"_blank">h=
ttps://www.ietf.org/mailman/<wbr>listinfo/dnsop</a><br>
</blockquote>

--94eb2c0b1cb4bfb7fa0553be63aa--


From nobody Fri Jul  7 11:41:30 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F07BA128DE5; Fri,  7 Jul 2017 11:41:29 -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, RP_MATCHES_RCVD=-0.001, 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 yu3pa78foC8V; Fri,  7 Jul 2017 11:41:28 -0700 (PDT)
Received: from alexa-out-lv-02.qualcomm.com (alexa-out.qualcomm.com [129.46.98.28]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 290FA126C0F; Fri,  7 Jul 2017 11:41:28 -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=1499452888; x=1530988888; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=FZElHdLr959RonMfR2E+2l2LoxaJjUcPuAQDhl3jHWM=; b=K4W6K2ReEEHrk3gEgBZRPMoQyMjE6lIa1HXVmGMtCzV9QpeKRSMipWJL kT/J6XsqhH46hapOR0PXKdywJPlwP8N9+GTUx6mJ4zcBuu9QNvCSW9CTn PYNKmNA7DJXmiFjfE3wgYEanjZ9gKL96MHW4FsQDttdpqKPRhWbVBEkuh 0=;
X-IronPort-AV: E=Sophos;i="5.40,324,1496127600";  d="scan'208";a="454653"
Received: from ironmsg04-l-new.qualcomm.com (HELO Ironmsg04-L.qualcomm.com) ([10.53.140.111]) by alexa-out-lv-02.qualcomm.com with ESMTP; 07 Jul 2017 11:41:27 -0700
X-IronPort-AV: E=McAfee;i="5800,7501,8584"; a="1383125604"
X-MGA-submission: =?us-ascii?q?MDHtIBtne2XriEwECItyfgLXlYN6Ix2vXEmlF5?= =?us-ascii?q?JDfRquCNHVkGgI6roXfKQLIoaixN0pw9hu8o/3Ao4U8qyqQvyma2/nTt?= =?us-ascii?q?Y9C0yfYygSrb6QpfvMYFb0PdKxiMLWGJadH5WvPR57sG+uaSdsGUo3GK?= =?us-ascii?q?be?=
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 07 Jul 2017 11:41:27 -0700
Received: from [10.64.110.227] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 7 Jul 2017 11:41:26 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Mark Andrews <marka@isc.org>
CC: Nico Williams <nico@cryptonector.com>, John C Klensin <john-ietf@jck.com>,  dnsop <dnsop@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>, Paul Vixie <paul@redbarn.org>, IETF <ietf@ietf.org>
Subject: Re: new DNS classes
Date: Fri, 7 Jul 2017 13:41:24 -0500
Message-ID: <A94C17CD-DC4B-43C9-AD3D-69735FC6B2BC@qti.qualcomm.com>
In-Reply-To: <20170706215236.99A8C7DB2FBA@rock.dv.isc.org>
References: <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <CAMm+Lwjd6xVp-EDp=doevx=AP8qws_Mv++aL733yHEyUF72EMA@mail.gmail.com> <562EC659F89FA92A09CAC4DB@PSB> <20170706153955.GB3393@localhost> <20170706215236.99A8C7DB2FBA@rock.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; markup=markdown
X-Mailer: MailMate (1.9.6r5347)
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/ietf/qEX1mxcYVu6jJgoKyRzxLGOd1-Q>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 18:41:30 -0000

[Apologies for the re-send. Using the correct address.]

On 6 Jul 2017, at 16:52, Mark Andrews wrote:

> Or you could stop trying to reinforce the myth that new RR types
> are hard to deploy.  They really aren't.  They actually get used
> all the time.

I'm running the latest version of MacOS Server. I can't get a new RR 
type into the UI. Even if I use the command line "dnsconfig" tool, I 
can't add a record of a type it doesn't know about; I only get A, AAAA, 
CNAME, NS, MX, PTR, SRV, and TXT. Yes, I could go hacking around in the 
BIND configs that underly their implementation. And at that point I say, 
"New RR types are hard to deploy; not a myth." Telling me I can use a 
different operating system or not use a validating UI is not a 
reasonable response.

The fact is the DNS doesn't provide a way for implementations to 
dynamically update the RR types to provide sensible UI; it's left as an 
exercise for each individual implementer. (Yes, I know about 
draft-levine-dnsextlang; it doesn't seem to have gotten anywhere.) You 
can't much complain about the difficulty of deployment when the 
community won't provide the tools to make deployment easier.

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


From nobody Fri Jul  7 12:15:01 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6BC8131690; Fri,  7 Jul 2017 12:14:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 N111kaPinebh; Fri,  7 Jul 2017 12:14:51 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15A0313168F; Fri,  7 Jul 2017 12:14:51 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTP id 7507EC086D10; Fri,  7 Jul 2017 12:14:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=ztW/XQD1COjUjI oAitweYzDMliw=; b=Gdnm8OVof5gmfRMLwF7naF5WA5RehNdzU0UC/9x71L/mtH AjYmeFuNb5Anx+0EMvJJrKVyXAJarwaxRNJlxL6jjuJS9Et6Zjy9douPUWeCIZH0 KZW0MIhm1IILGJGUvH2QOj6dw17ce/4pqarUA3ANGuu/2JeMQa+yC/vESyM4Q=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTPSA id D49E1C086D0C; Fri,  7 Jul 2017 12:14:49 -0700 (PDT)
Date: Fri, 7 Jul 2017 14:14:47 -0500
From: Nico Williams <nico@cryptonector.com>
To: william manning <chinese.apricot@gmail.com>
Cc: David Cake <dave@davecake.net>, Randy Bush <randy@psg.com>, dnsop <dnsop@ietf.org>, Paul Vixie <paul@redbarn.org>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: new DNS classes
Message-ID: <20170707191445.GH3393@localhost>
References: <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <m2mv8jw9qq.wl-randy@psg.com> <33235E8D-147D-4178-BC45-DFC1E1C27B99@davecake.net> <20170707165513.GG3393@localhost> <CACfw2hi8Grd+jeyXTR-Hfcx+Axeh8YjJzwO=QM3MndhhwvYZJw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CACfw2hi8Grd+jeyXTR-Hfcx+Axeh8YjJzwO=QM3MndhhwvYZJw@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yy6UA2akv6RR-uy5PkHKQYDHg6I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 19:14:53 -0000

On Fri, Jul 07, 2017 at 11:27:45AM -0700, william manning wrote:
> You need a better imagination then.   mDNS is a crippled DNS implementation
> that was hobbled on purpose.   HS was/is an entirely different addressing
> scheme that emerged from project Athena @ MIT.  To the extent that when all
> you have been given is the IN class and it's associated rooted hierarchy,
> you first,second,&third inclination is to treat EVERYTHING as being easily
> integrated into that model.  And the ietf is going to go right along with
> you.   After all, when all you have is a hammer, everything looks like a
> nail.

Did you read what I wrote??

The thing I'm having trouble imagining is distinct from the things that
you list that I also listed (and then lecture about as if I had no idea
what they were).  A peer-to-peer DNS might be mDNS-like without whatever
crippling you have in mind, but it's still difficult to imagine how to
organize a coherent Internet around it.  And as to web of trust, I don't
see how that would work either.  You decry my lack of imagination but
provide none of your own.

Nico
-- 


From nobody Fri Jul  7 16:56:57 2017
Return-Path: <nomcom-chair-2017@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DBD6E12EC34; Fri,  7 Jul 2017 16:56:55 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: NomCom Chair 2017 <nomcom-chair-2017@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: ietf@ietf.org
Subject: Nomcom 2017-2018: Result of random selection process
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.2
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org
Message-ID: <149947181581.30276.8386472277531434520.idtracker@ietfa.amsl.com>
Date: Fri, 07 Jul 2017 16:56:55 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OtRxjkSIBnTaOyqGw3eNv7slArI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 23:56:56 -0000

Please join me in welcoming the following folks to the 2016-2017 NomCom:

#       First/Last Name              Company
----------------------------------------------------------
157     Ronald       in 't Velt      TNO
108     Lucy         Yong            Huawei Technologies
 31     Dan          York            Internet Society
 23     Charles      Eckel           Cisco
151     Rich         Salz            Akamai Technologies
130     Niel         Harper          Internet Society
145     Phillip      Sorber          Comcast
 52     Fred         Baker           Independent
147     Ram (Ramki)  Krishnan        Dell
125     Mohit        Sethi           Ericsson

No one was disqualified due to company weighting per RFC 7437.

With this announcement, a one week challenge period starts wherein the community may challenge the results to the NomCom Chair (in writing, email is fine).  See RFC 7437, Section 4.17 for details.

I will be contacting the selected volunteers to ensure they remain willing and available to serve.

Peter Yee
peter at akayla dot com
nomcom-chair-2017 at ietf dot org


From nobody Fri Jul  7 17:18:32 2017
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75B7613166A; Fri,  7 Jul 2017 17:18:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 N16c-wMtcCBa; Fri,  7 Jul 2017 17:18:29 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (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 94CB712F28C; Fri,  7 Jul 2017 17:18:29 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 9DCE13493BB; Sat,  8 Jul 2017 00:18:26 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 8684C16004A; Sat,  8 Jul 2017 00:18:26 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 730A8160067; Sat,  8 Jul 2017 00:18:26 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id lQ0mXvBUlgc4; Sat,  8 Jul 2017 00:18:26 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id E49B516004A; Sat,  8 Jul 2017 00:18:25 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 2FB117DFD520; Sat,  8 Jul 2017 10:18:25 +1000 (AEST)
To: Pete Resnick <presnick@qti.qualcomm.com>
Cc: Nico Williams <nico@cryptonector.com>, John C Klensin <john-ietf@jck.com>, dnsop <dnsop@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>, Paul Vixie <paul@redbarn.org>, IETF <ietf@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <CAMm+Lwjd6xVp-EDp=doevx=AP8qws_Mv++aL733yHEyUF72EMA@mail.gmail.com> <562EC659F89FA92A09CAC4DB@PSB> <20170706153955.GB3393@localhost> <20170706215236.99A8C7DB2FBA@rock.dv.isc.org> <A94C17CD-DC4B-43C9-AD3D-69735FC6B2BC@qti.qualcomm.com>
Subject: Re: new DNS classes
In-reply-to: Your message of "Fri, 07 Jul 2017 13:41:24 -0500." <A94C17CD-DC4B-43C9-AD3D-69735FC6B2BC@qti.qualcomm.com>
Date: Sat, 08 Jul 2017 10:18:25 +1000
Message-Id: <20170708001825.2FB117DFD520@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3csnzAxukPv5HosLzqaiKmx_o_A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Jul 2017 00:18:31 -0000

In message <A94C17CD-DC4B-43C9-AD3D-69735FC6B2BC@qti.qualcomm.com>, Pete Resnick writes:
> [Apologies for the re-send. Using the correct address.]
> 
> On 6 Jul 2017, at 16:52, Mark Andrews wrote:
> 
> > Or you could stop trying to reinforce the myth that new RR types
> > are hard to deploy.  They really aren't.  They actually get used
> > all the time.
> 
> I'm running the latest version of MacOS Server. I can't get a new RR 
> type into the UI. Even if I use the command line "dnsconfig" tool, I 
> can't add a record of a type it doesn't know about; I only get A, AAAA, 
> CNAME, NS, MX, PTR, SRV, and TXT. Yes, I could go hacking around in the 
> BIND configs that underly their implementation. And at that point I say, 
> "New RR types are hard to deploy; not a myth." Telling me I can use a 
> different operating system or not use a validating UI is not a 
> reasonable response.

Well use nsupdate.  That also ships with the Mac.  The version Apple
ships is a little bit old but it can still handle unknown types and
classes.  It can also use SIG(0) or TSIG to sign the updates messages.
It also supports the following types if I've matched the version
of BIND correctly (BIND 9.8.3.P1).  

a, a6, aaaa, afsdb, apl, cert, cname, dhcid, dlv, dname, dnskey,
ds, gpos, hinfo, hip, ipseckey, isdn, key, keydata, kx, loc, mb,
md, mf, mg, minfo, mr, mx, naptr, ns, nsap, nsap-ptr, nsec, nsec3,
nsec3param, null, nxt, ptr, px, rp, rrsig, rt, sig, soa, spf, srv,
sshfp, tkey, tlsa, txt, unspec, wks, x25

[rock:~/git/bind9] marka% /usr/bin/nsupdate 
> update add xxxxx 0 class40 type9000 \# 1 00
> show
Outgoing update query:
;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id:      0
;; flags:; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0
;; UPDATE SECTION:
xxxxx.			0	CLASS40	TYPE9000 \# 1 00

> quit
[rock:~/git/bind9] marka% uname -a
Darwin rock.dv.isc.org 16.6.0 Darwin Kernel Version 16.6.0: Fri Apr 14 16:21:16 PDT 2017; root:xnu-3789.60.24~6/RELEASE_X86_64 x86_64
[rock:~/git/bind9] marka% 

> The fact is the DNS doesn't provide a way for implementations to 
> dynamically update the RR types to provide sensible UI; it's left as an 
> exercise for each individual implementer. (Yes, I know about 
> draft-levine-dnsextlang; it doesn't seem to have gotten anywhere.) You 
> can't much complain about the difficulty of deployment when the 
> community won't provide the tools to make deployment easier.

Well BIND is designed to allow new types to be added easily.  It
may require recompiling rather than updating a text file but it is
not beyond people to do because we see people doing just that.  All
the record types are defined in a single place and adding in a new
type is usally as simple as cutting and pasting bits from the
existing type definitions to make a new one.

We also ship a tool which only purpose is to translate between
unknown record format and known record format.  You don't need to
update you whole web api to add in a new type.  Just update the
tool.  It also provides a list of known types it supports so you
can use it to update the web api's list of supported types at
runtime.

[rock:~/git/bind9] marka% echo in a 1.2.3.4 | named-rrchecker -u
CLASS1	TYPE1	\# 4 01020304
[rock:~/git/bind9] marka% 

[rock:~/git/bind9] marka% named-rrchecker -T | fmt
A NS MD MF CNAME SOA MB MG MR NULL WKS PTR HINFO MINFO MX TXT RP
AFSDB X25 ISDN RT NSAP NSAP-PTR SIG KEY PX GPOS AAAA LOC NXT EID
NIMLOC SRV ATMA NAPTR KX CERT A6 DNAME SINK APL DS SSHFP IPSECKEY
RRSIG NSEC DNSKEY DHCID NSEC3 NSEC3PARAM TLSA SMIMEA HIP NINFO RKEY
TALINK CDS CDNSKEY OPENPGPKEY CSYNC SPF UINFO UID GID UNSPEC NID
L32 L64 LP EUI48 EUI64 URI CAA AVC TA DLV
[rock:~/git/bind9] marka% 

Mark

> pr
> -- 
> Pete Resnick <http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Fri Jul  7 22:57:37 2017
Return-Path: <zhangmingui@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B09BD12783A; Fri,  7 Jul 2017 22:57:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.322
X-Spam-Level: 
X-Spam-Status: No, score=-2.322 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, 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 UMQFC2IVROa3; Fri,  7 Jul 2017 22:57:15 -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 8D10C12896F; Fri,  7 Jul 2017 22:57:14 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml703-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DJY62493; Sat, 08 Jul 2017 05:57:12 +0000 (GMT)
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml703-cah.china.huawei.com (10.201.108.44) with Microsoft SMTP Server (TLS) id 14.3.301.0; Sat, 8 Jul 2017 06:57:11 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0235.001; Sat, 8 Jul 2017 13:57:05 +0800
From: "Zhangmingui (Martin)" <zhangmingui@huawei.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, "tsv-art@ietf.org" <tsv-art@ietf.org>
CC: "draft-ietf-trill-mtu-negotiation.all@ietf.org" <draft-ietf-trill-mtu-negotiation.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "trill@ietf.org" <trill@ietf.org>
Subject: RE: Tsvart telechat review of draft-ietf-trill-mtu-negotiation-06
Thread-Topic: Tsvart telechat review of draft-ietf-trill-mtu-negotiation-06
Thread-Index: AQHS9Y7xZDZHsOYJgke3/J9kjsDvXqJJJE3f
Date: Sat, 8 Jul 2017 05:57:04 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E7A6546EF1@NKGEML515-MBX.china.huawei.com>
References: <149925973580.17545.6979655005275084891@ietfa.amsl.com>
In-Reply-To: <149925973580.17545.6979655005275084891@ietfa.amsl.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.108.158]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020203.59607439.0011, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: e7df6c39eabc6c7f3615b22f29a18d90
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lJE3cBoNS62mQl5VtQpSPNRrWO8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Jul 2017 05:57:22 -0000

Hi Magnus,

Thanks for your careful review. Please see the reponses inline below.

________________________________________
From: Magnus Westerlund [magnus.westerlund@ericsson.com]
Sent: Wednesday, July 05, 2017 21:02
To: tsv-art@ietf.org
Cc: draft-ietf-trill-mtu-negotiation.all@ietf.org; ietf@ietf.org; trill@iet=
f.org
Subject: Tsvart telechat review of draft-ietf-trill-mtu-negotiation-06

Reviewer: Magnus Westerlund
Review result: Not Ready

This TSV-ART review is influenced by that I did the review of
draft-ietf-trill-over-ip.

1. So draft-ietf-trill-over-ip-10 has MTU discovery needs for
determining if the UDP encapsulation will work or not. It references  in
Section 8.4 the old RFC, i.e. RFC 6325, which is updated by
draft-ietf-trill-mtu-negotiation.

    TRILL IS-IS MTU PDUs, as specified in Section 5 of [RFC6325] and in
    [RFC7177], can be used to obtain added assurance of the MTU of a
    link.

However, this is not quite true, as if the IP path MTU is below 1470
bytes, which is not unheard of, the algorithm in the MTU negotiation
draft can't determine it. It will only report the IP path as having an
MTU to small when the 1470 bytes probe fail.

[Mingui]   I copied the relevant text from RFC 6325.=20
    "The desired minimum acceptable inter-RBridge link MTU for the
      campus, that is, originatingLSPBufferSize.  This is a 16-bit
      unsigned integer number of octets that defaults to 1470 bytes,
      which is the minimum valid value.  Any lower value being
      advertised by an RBridge is ignored."
So the minimum value of Sz would be 1470. IOW, IP path with MTU below 1470 =
will not be qualified as an adjaceny of the TRILL network topology.


So, if the trill-over-ip authors want to use this as a mechanism, then the =
MTU
negotiation draft needs to be expanded to have more flexible lower
boundaries. However, that appear to affect MTU negotiation quite
significant as it needs to separate algorithm for finding MTU, from the
different usage of the algorithm with different starting points. Where
the normal will have a lower bound of 1470, and be more tightly coupled
to Sz when finding Lz. While the Trill-over-IP has a different usage.

I think the trill WG needs to decide on how to slice this. If the
MTU-negotiation only targets the explicit targets in the current draft and =
goes
forward now. Or if they want to meet trill-over-ip's goals which will requi=
re
restructuring.

2. Another issue, is that I think the algorithm is a bit short on
transmission scheduling recommendations:

    1) If RB1 successfully receives the MTU-ack from RB2 to the probe of
       the value of link-wide Lz within k tries (where k is a
       configurable parameter whose default is 3), link MTU size is set
       to the size of link-wide Lz and stop.

If I do this test with all three packets back to back at line rate, I could
potentially get all probes lost in the same burst loss in router queue or
switch fabric. What I think is needed here is a specification on how these
probes are transmitted. Spaced in a particular way, or at least minimal
distance, and are the additional probes only sent after the previous has be=
en
judged to have been lost, which makes it interact with the next issue.

[Mingui] This seems an implementation space. However, the document may offe=
r recommendations. The being recommended minimum interval between two succe=
ssive probes would affect the boot up speed of a TRILL campus. One RTT is a=
 reasonable value.

3. This is also unclear on what the criteria is for determining that someth=
ing
is lost:

      a) If RB1 fails to receive an MTU-ack from RB2 after k tries, RB1
          sets the "failed minimum MTU test" flag for RB2 in RB1's Hello
          and stop.

I fail to see any specification for the criteria when an MTU-ack should be
considered to have failed to reach the probing entity. So this appear to
require a timeout, and thus a timeout interval. Is the RTT known so that on=
e
can define something as lost after N*RTT? Are there possible delays in send=
ing
the MTU-ack that are considered okay that can affect this?

[Mingui] Yes, this makes sense. An MTU-ack should be considered to have fai=
led two RTT after the probe is sent out.

4. Section 3, the algorithm in Step 1 is unable to reach the first terminat=
ion
condition (3) "If lowerBound >=3D upperBound" in some cases.

[Mingui] This algorithm has been updated through a few rounds of revisions.=
 Let me insert a few minor updates to the cited text as below.

  Step 1: RB1 tries to send an MTU-probe padded to the size x.

   1) If RB1 fails to receive an MTU-ack from RB2 after k tries:

         upperBound is set to x and x is set to [(lowerBound +
         upperBound)/2], rounded up to the nearest integer.

[Mingui] s/uppperBound is set to x/uppperBound is set to x-1/
[Mingui] s/rounded up to the nearest integer./rounded down to the nearest i=
nteger./


   2) If RB1 receives an MTU-ack to a probe of size x from RB2:

         link MTU size is set to x, lowerBound is set to x and x is set
         to [(lowerBound + upperBound)/2], rounded up to the nearest
         integer.

[Mingui] s/rounded up to the nearest integer./rounded down to the nearest i=
nteger./
[Mingui] Append one condistion to this step 2): If lowerBound equals upperB=
ound-1 then x is set to upperBound.

   3) If lowerBound >=3D upperBound or Step 1 has been repeated n times
      (where n is a configurable parameter whose default value is 5),
      stop.

   4) Repeat Step 1.

I run this on the input data: Lower bound =3D 1470, Upper bound =3D 9216 an=
d with
an MTU of 7935 and gets the following sequence:

Lower   Upper   X
1470    9216    5343
5343    9216    7280
7280    9216    8248
7280    8248    7764
7764    8248    8006
7764    8006    7885
7885    8006    7946
7885    7946    7916
7916    7946    7931
7931    7946    7939
7931    7939    7935
7935    7939    7937
7935    7937    7936
7935    7936    7936
7935    7936    7936

Thus, the termination condition needs to change.=20

[Mingui] After the update of the text, the sequence would become:
Lower   Upper   X
1470    9216    5343
5343    9216    7279
7279    9216    8247
7279    8246    7762
7762    8246    8004
7762    8003    7882
7882    8003    7942
7882    7941    7911
7911    7941    7926
7926    7941    7933
7933    7941    7937
7933    7936    7934
7934    7936    7935
7935    7936    7935
7935    7936    7936
7935    7935    7935

The second I notice is that having a limitation on number of steps as 5,=20

[Mingui] Since the testing might be too resource consuming, implementors su=
ggested this limitation. Afterall, the purpose of testing a Lz value is to =
improve the efficiency (if Lz > Sz) rather than reach the optimal efficienc=
y.=20

results in quite a large gap
between upper and lower bound in which the MTU exists in.

5. I frankly gets confused by the application of the binary search. First i=
t
will in many case not be run to termination where the actual MTU is determi=
ned.
Then the result of the upper and lower bound are just used to confirm the S=
z
value. There are no discussion about using the MTU search to determine a ne=
w
possible value for Sz.

[Mingui] Because the MTU search will NOT be used to determine a new possibl=
e value for Sz. It is only applicable to Lz.=20

 The text is not even explicit that lower bound is the
highest known to work Transmission unit size at the time of testing. I thin=
k
section 3, should conclude in determine some TU value, and if that is Sz or
something other appears quite relevant for what to do in the later sections=
.

[Mingui] As specified in Section 3, =93link MTU size=94 is already set to t=
he lower bound. This tested =93link MTU size=94 is the =93TU=94 value. This=
 value is potentially larger than Sz as explained in the introduction and S=
ection 2.

Thanks,
Mingui=


From nobody Sat Jul  8 01:15:46 2017
Return-Path: <chopps@chopps.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FAED1296C6; Sat,  8 Jul 2017 01:15:31 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Christian Hopps <chopps@chopps.org>
To: <rtg-dir@ietf.org>
Cc: i2rs@ietf.org, ietf@ietf.org, draft-ietf-i2rs-yang-l3-topology.all@ietf.org
Subject: Rtgdir early review of draft-ietf-i2rs-yang-l3-topology-10
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149950173106.2877.12360295603653924176@ietfa.amsl.com>
Date: Sat, 08 Jul 2017 01:15:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jFxI7FUn9A68Uu9pr9nUQMEBBxM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Jul 2017 08:15:31 -0000

Reviewer: Christian Hopps
Review result: Has Nits

Hello,

I have been selected to do a routing directorate “early” review of this draft.

  https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-l3-topology/

The purpose of this review is to determine it's compatibility with the new
revised datastore model guidelines.

For more information about the Routing Directorate, please see
​http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir

Document: draft-ietf-i2rs-yang-l3-topology-10.txt
Reviewer: Christian Hopps
Review Date: July 8, 2017
Intended Status: Standards Track

Summary:

- This document is basically ready for publication, but has nits that should be
  considered prior to being submitted to the IESG.

Comments:

- This document adapts the suggested NMDA guidelines quite nicely.

- Perhaps an informative reference to the NMDA guidelines draft would be useful.

- Appendix A: Second Paragraph, last sentence:
  - I believe that it should say:

      "instead of ietf-network and ietf-network-topology"

    it currently says:

      "instead of ietf-network and ietf-network-state"

- IS-IS example model (sorry couldn't help myself :)

  - The example IS-IS l3-node-attributes augmentation isis-node-attributes
    includes an "iso-pseudonode-id". This isn't a node attribute, but rather a
    link one (it is repeated later under link attributes).

  - The isis-wg suggests to use "IS-IS" consistently, where possible, in
    documents rather than "isis" or "ISIS".



From nobody Sat Jul  8 05:04:39 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A62A5126C22; Sat,  8 Jul 2017 05:04:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level: 
X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=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 UsYJwoBMKpfq; Sat,  8 Jul 2017 05:04:30 -0700 (PDT)
Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::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 F1B851204DA; Sat,  8 Jul 2017 05:04:29 -0700 (PDT)
Received: by mail-lf0-x232.google.com with SMTP id h22so37418055lfk.3; Sat, 08 Jul 2017 05:04:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=O8lcg9dLU4jaXcF4DTGemkf5CGH0HBwgmJyc9urUY6U=; b=HrMjyE91hU8nLYEDv4Hb1h2/ymaf032aM/Cf88UZ7LJWdCQjR+I49MB6NV3r0Qisfz yROk2tc5Tf2DucrpmpVfVeQqVsyrr/Sz8y4376g8iR3BxK+78/f1AUWbqY+Z9DzIVm9x /LjZjMqms2s4RJwbcg6hzAI/tkgD0oYHL7P/DBLd2COst5vjPrXP44zNiXXW/EKIdBOa +PXset+3iibrltg2YGGKDSjNnAAksaasrWazEVPGZtP4D66KVKShdLHQf6qThat5HCkF unCGKa3j/TUHp6rF18WzWCyVvUfGxTlqxTQRtwwhIk/PsF0GQUdhiVIYbhj/iLemUqnW kAiA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=O8lcg9dLU4jaXcF4DTGemkf5CGH0HBwgmJyc9urUY6U=; b=cTDdwU1vq8l2Yq/Fzw7pNa7M+9y2AqQFL3V6Zt0kCzQEGWWvCGeqrRa42Q+GwB6P1F 6SzQzi1TvjgiBu14IXP3cGcP+5YAzuxaX+2MzR4ZqY1vwuqiX/pofJxQJr98rtpJN+uL +B/A/Z2WxpcIcmlUIk/IgI3yDRIGMpMcbeqA1mZGsO05BUcgM799X0jO5fB27VY5acHZ /Rl2LCd7VwW5k6K7D/ukbhBb15jYx0F0dkiSYGGvyHwrOkJPN0MlPNQsAMFolDKa32k7 D68nepZ/G1/E0WIE17L8glev4C7eIahd3INXMwuuHcpoRUJc8e3kEOBVh0Mr29Y3N/tG pFsA==
X-Gm-Message-State: AKS2vOxtHqSSb+Cha6dswINneIUF6ioeI2Hm1dnMcZstSEwgeWwePtsd lXjzVqrclg/iaj2flWUnm5xbjmYCIA==
X-Received: by 10.25.17.75 with SMTP id g72mr20381061lfi.122.1499515468193; Sat, 08 Jul 2017 05:04:28 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.25.181.214 with HTTP; Sat, 8 Jul 2017 05:04:26 -0700 (PDT)
In-Reply-To: <562EC659F89FA92A09CAC4DB@PSB>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <CAMm+Lwjd6xVp-EDp=doevx=AP8qws_Mv++aL733yHEyUF72EMA@mail.gmail.com> <562EC659F89FA92A09CAC4DB@PSB>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Sat, 8 Jul 2017 08:04:26 -0400
X-Google-Sender-Auth: -jEDFB7gIHtktcQi93hlUf9SJac
Message-ID: <CAMm+LwjXiAtozbH4DJwRfU2Q6NcVMg76kKzLd8poQZhakLQtmw@mail.gmail.com>
Subject: Re: new DNS classes
To: John C Klensin <john-ietf@jck.com>
Cc: Paul Vixie <paul@redbarn.org>, dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a11401a18d125470553cd265c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/s-U4HyQL1kQF89tMCdeW6W_OCR0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Jul 2017 12:04:32 -0000

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

On Thu, Jul 6, 2017 at 11:15 AM, John C Klensin <john-ietf@jck.com> wrote:

>
>
> --On Thursday, July 6, 2017 00:36 -0400 Phillip Hallam-Baker
> <phill@hallambaker.com> wrote:
>
> > There are changes to the DNS that are practical and those that
> > are not. For better or worse, I can't see any way that
> > teaching DNS to use new classes makes any sense at this point.
> > The only point at which it would have made sense was when
> > internationalization happened. But the path chosen makes more
> > sense.
>
> As the author of the I-D that proposed using a Class to deal
> with internationalization, it would not have worked, and the two
> important reasons are perhaps worth understanding.   First, that
> approach included a transition strategy that permitted legacy
> clients and registrations to keep working in a way that users
> would see as normal.  But that strategy depends on CLASSes
> sharing the same root and hierarchy.  At Paul points out, that
> interpretation of 1034/1035 is not universally accepted and
> implemented.  Second, IIR, we intended that the different CLASS
> allow a different set of matching rule assumptions and
> conditions.  Because labels must generally be interpreted and
> compared before CLASS values are accessed and, perhaps more
> important, in optimization of databases, one probably needs
> label types to do that, not CLASSes.   And label types don't
> have a good history.


=E2=80=8BMy point was that all the reasons not to use class for
internationalization are likely general and apply to any attempt to use
class.

> It seems to me that if people want to do anything new with DNS
> > that they should use prefixes, new RRs or both as the
> > mechanism, not the class which is limited anyway.
> >
> > DNS is not a full service directory. Nor does it need to be. A
> > UDP packet is big enough for a link, a fingerprint and a
> > digital signature. That is all that you ever need.
>
> As I think you know, I just love "all you will ever need"
> statements about the Internet (and its predecessors) although my
> favorite remains "we will never need more than 8 bits of address
> space".


=E2=80=8BThe question that always comes up in a directory service is how mu=
ch
service description information to put in the =E2=80=8Bdirectory and whethe=
r the
service itself should provide some of the description.

DNS is irritatingly constraining when it comes to distributing information
like a digital certificate. But we have managed to live in those
constraints for the past 20 or so years after they started to be an issue.

What you need and what you might want are different things.


=E2=80=8BIf people find that they do need 'more than 8 bits', then =E2=80=
=8BI guess we end
up having to design DNS/2 protocol. But I think it unlikely we get there
anytime soon.

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Ju=
l 6, 2017 at 11:15 AM, John C Klensin <span dir=3D"ltr">&lt;<a href=3D"mail=
to:john-ietf@jck.com" target=3D"_blank">john-ietf@jck.com</a>&gt;</span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex"><br>
<br>
--On Thursday, July 6, 2017 00:36 -0400 Phillip Hallam-Baker<br>
<span class=3D"">&lt;<a href=3D"mailto:phill@hallambaker.com">phill@hallamb=
aker.com</a>&gt; wrote:<br>
<br>
&gt; There are changes to the DNS that are practical and those that<br>
&gt; are not. For better or worse, I can&#39;t see any way that<br>
&gt; teaching DNS to use new classes makes any sense at this point.<br>
&gt; The only point at which it would have made sense was when<br>
&gt; internationalization happened. But the path chosen makes more<br>
&gt; sense.<br>
<br>
</span>As the author of the I-D that proposed using a Class to deal<br>
with internationalization, it would not have worked, and the two<br>
important reasons are perhaps worth understanding.=C2=A0 =C2=A0First, that<=
br>
approach included a transition strategy that permitted legacy<br>
clients and registrations to keep working in a way that users<br>
would see as normal.=C2=A0 But that strategy depends on CLASSes<br>
sharing the same root and hierarchy.=C2=A0 At Paul points out, that<br>
interpretation of 1034/1035 is not universally accepted and<br>
implemented.=C2=A0 Second, IIR, we intended that the different CLASS<br>
allow a different set of matching rule assumptions and<br>
conditions.=C2=A0 Because labels must generally be interpreted and<br>
compared before CLASS values are accessed and, perhaps more<br>
important, in optimization of databases, one probably needs<br>
label types to do that, not CLASSes.=C2=A0 =C2=A0And label types don&#39;t<=
br>
have a good history.</blockquote><div><br></div><div><div class=3D"gmail_de=
fault" style=3D"font-size:small">=E2=80=8BMy point was that all the reasons=
 not to use class for internationalization are likely general and apply to =
any attempt to use class.</div></div><div class=3D"gmail_default" style=3D"=
font-size:small"><br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">
&gt; It seems to me that if people want to do anything new with DNS<br>
&gt; that they should use prefixes, new RRs or both as the<br>
&gt; mechanism, not the class which is limited anyway.<br>
&gt;<br>
&gt; DNS is not a full service directory. Nor does it need to be. A<br>
&gt; UDP packet is big enough for a link, a fingerprint and a<br>
&gt; digital signature. That is all that you ever need.<br>
<br>
</span>As I think you know, I just love &quot;all you will ever need&quot;<=
br>
statements about the Internet (and its predecessors) although my<br>
favorite remains &quot;we will never need more than 8 bits of address<br>
space&quot;.</blockquote><div><br></div><div><div class=3D"gmail_default" s=
tyle=3D"font-size:small">=E2=80=8BThe question that always comes up in a di=
rectory service is how much service description information to put in the =
=E2=80=8Bdirectory and whether the service itself should provide some of th=
e description.</div><div class=3D"gmail_default" style=3D"font-size:small">=
<br></div><div class=3D"gmail_default" style=3D"font-size:small">DNS is irr=
itatingly constraining when it comes to distributing information like a dig=
ital certificate. But we have managed to live in those constraints for the =
past 20 or so years after they started to be an issue.</div><div class=3D"g=
mail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_defau=
lt" style=3D"font-size:small">What you need and what you might want are dif=
ferent things.</div><br></div><div><br></div><div><div class=3D"gmail_defau=
lt" style=3D"font-size:small">=E2=80=8BIf people find that they do need &#3=
9;more than 8 bits&#39;, then =E2=80=8BI guess we end up having to design D=
NS/2 protocol. But I think it unlikely we get there anytime soon.</div><div=
 class=3D"gmail_default" style=3D"font-size:small"><br></div><br></div></di=
v></div></div>

--001a11401a18d125470553cd265c--


From nobody Sat Jul  8 09:05:15 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BE1E129B72; Sat,  8 Jul 2017 09:05:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.002
X-Spam-Level: 
X-Spam-Status: No, score=-7.002 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_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 DFjkZawNxUxb; Sat,  8 Jul 2017 09:05:05 -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 D86F0127873; Sat,  8 Jul 2017 09:05:05 -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=1499529905; x=1531065905; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=C/YtHOKCp+1yWmIkJHw7H3uj3Imrt3EFdinJ+CoKWu4=; b=FsjpRpnHSeLyAYBlgIbNbqsoynLjF8rc35q5cQSMyCRa1YbMfDCJtT0D LD9FVUm5d12xXvQlEpEfznhAUqTS0htUNXuahcFIoBWhnvwc2/bN0rBuG lbIwCVMyYu36WhFGVIdr244FJLg73+mynWHW8sJzgRD1pzhuh/qRTLCrC c=;
X-IronPort-AV: E=Sophos;i="5.40,329,1496127600"; d="scan'208";a="109989335"
Received: from unknown (HELO Ironmsg03-R.qualcomm.com) ([10.53.140.107]) by sabertooth01.qualcomm.com with ESMTP; 08 Jul 2017 09:05:04 -0700
X-IronPort-AV: E=McAfee;i="5800,7501,8585"; a="1402247209"
X-MGA-submission: =?us-ascii?q?MDHQ+L3s0NEb7pK1EW4NTcei0QGSZiUiwzMYFX?= =?us-ascii?q?131AlYLHxHjCegMKiA9rU2RXqlmPKMooa6tVFiFe7+PhUvRXPov5M9Yz?= =?us-ascii?q?c25xlifZd/XgAjvBysxidP16/QlPtoRZ4pJLRgPYWqrFYj3h1cmDyJqY?= =?us-ascii?q?vj?=
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 08 Jul 2017 09:05:04 -0700
Received: from [10.64.110.227] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Sat, 8 Jul 2017 09:05:03 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Mark Andrews <marka@isc.org>
CC: Nico Williams <nico@cryptonector.com>, John C Klensin <john-ietf@jck.com>,  dnsop <dnsop@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>, Paul Vixie <paul@redbarn.org>, IETF <ietf@ietf.org>
Subject: Re: new DNS classes
Date: Sat, 8 Jul 2017 11:05:01 -0500
Message-ID: <EDFEF9A1-99CF-4F25-9C1C-051E78949967@qti.qualcomm.com>
In-Reply-To: <20170708001825.2FB117DFD520@rock.dv.isc.org>
References: <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <CAMm+Lwjd6xVp-EDp=doevx=AP8qws_Mv++aL733yHEyUF72EMA@mail.gmail.com> <562EC659F89FA92A09CAC4DB@PSB> <20170706153955.GB3393@localhost> <20170706215236.99A8C7DB2FBA@rock.dv.isc.org> <A94C17CD-DC4B-43C9-AD3D-69735FC6B2BC@qti.qualcomm.com> <20170708001825.2FB117DFD520@rock.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5347)
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/ietf/_0bf630FKAJiPThX1BPKf9Na3vk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Jul 2017 16:05:07 -0000

On 7 Jul 2017, at 19:18, Mark Andrews wrote:

> In message <A94C17CD-DC4B-43C9-AD3D-69735FC6B2BC@qti.qualcomm.com>, 
> Pete Resnick writes:
>>
>> On 6 Jul 2017, at 16:52, Mark Andrews wrote:
>>
>>> Or you could stop trying to reinforce the myth that new RR types
>>> are hard to deploy.  They really aren't.  They actually get used
>>> all the time.
>>
>> I'm running the latest version of MacOS Server. I can't get a new RR
>> type into the UI. Even if I use the command line "dnsconfig" tool, I
>> can't add a record of a type it doesn't know about; I only get A, 
>> AAAA,
>> CNAME, NS, MX, PTR, SRV, and TXT. Yes, I could go hacking around in 
>> the
>> BIND configs that underly their implementation. And at that point I 
>> say,
>> "New RR types are hard to deploy; not a myth." Telling me I can use a
>> different operating system or not use a validating UI is not a
>> reasonable response.
>
> Well use nsupdate.  That also ships with the Mac.

Of course doing that likely means I'll have records that don't show up 
in the server UI. Not entirely thrilling. And I could accomplish exactly 
the same thing by directly editing the BIND config files, so I'm not 
sure what that gains me in terms of "not hard to deploy".

>> The fact is the DNS doesn't provide a way for implementations to
>> dynamically update the RR types to provide sensible UI; it's left as 
>> an
>> exercise for each individual implementer. (Yes, I know about
>> draft-levine-dnsextlang; it doesn't seem to have gotten anywhere.) 
>> You
>> can't much complain about the difficulty of deployment when the
>> community won't provide the tools to make deployment easier.
>
> Well BIND is designed to allow new types to be added easily.  It
> may require recompiling rather than updating a text file but it is
> not beyond people to do because we see people doing just that.

¬(∃𝑥𝐶(𝑥) → ∀𝑥𝐶(𝑥))

Just because you you see some people recompiling does not mean that all 
(or most, or a significant number) can. Set that aside, it is nowhere 
near reasonable for knowing how to recompile a piece of code to be 
required in order for me to add a new RR type. Set that aside, this is 
the epitome of "hard to deploy": Some implementations can't do it at 
all, some implementations you have to go hacking around in hidden config 
files, and some implementations you have to recompile the binary to get 
a reasonable UI experience.

This is the problem with DNS being considered a system service rather 
than a user application. It's got both aspects. Until the user 
experience for configuring the DNS with a new RR type does not require 
the skills of someone able to recompile code, it is absolutely going to 
be the case that new RR types are hard to deploy, and calling it a myth 
is not helpful.

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


From nobody Sat Jul  8 18:59:07 2017
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E0CF128D40; Sat,  8 Jul 2017 18:59:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, PP_MIME_FAKE_ASCII_TEXT=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 uzvzUil72M9a; Sat,  8 Jul 2017 18:58:58 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (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 DDF1F127F0E; Sat,  8 Jul 2017 18:58:58 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id E2F883493C9; Sun,  9 Jul 2017 01:58:55 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id A293416003D; Sun,  9 Jul 2017 01:58:55 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 879EC160053; Sun,  9 Jul 2017 01:58:55 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id l7L6bkdQS1fJ; Sun,  9 Jul 2017 01:58:55 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 14DF116003D; Sun,  9 Jul 2017 01:58:55 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id E5C877E07ADA; Sun,  9 Jul 2017 11:58:51 +1000 (AEST)
To: Pete Resnick <presnick@qti.qualcomm.com>
Cc: Nico Williams <nico@cryptonector.com>, John C Klensin <john-ietf@jck.com>, dnsop <dnsop@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>, Paul Vixie <paul@redbarn.org>, IETF <ietf@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <CAMm+Lwjd6xVp-EDp=doevx=AP8qws_Mv++aL733yHEyUF72EMA@mail.gmail.com> <562EC659F89FA92A09CAC4DB@PSB> <20170706153955.GB3393@localhost> <20170706215236.99A8C7DB2FBA@rock.dv.isc.org> <A94C17CD-DC4B-43C9-AD3D-69735FC6B2BC@qti.qualcomm.com> <20170708001825.2FB117DFD520@rock.dv.isc.org> <EDFEF9A1-99CF-4F25-9C1C-051E78949967@qti.qualcomm.com>
Subject: Re: new DNS classes
In-reply-to: Your message of "Sat, 08 Jul 2017 11:05:01 -0500." <EDFEF9A1-99CF-4F25-9C1C-051E78949967@qti.qualcomm.com>
Date: Sun, 09 Jul 2017 11:58:51 +1000
Message-Id: <20170709015851.E5C877E07ADA@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/a02jDUhW7QsWfEcE7MYkHpwKtzs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Jul 2017 01:59:01 -0000

In message <EDFEF9A1-99CF-4F25-9C1C-051E78949967@qti.qualcomm.com>, Pete Resnic
k writes:
> On 7 Jul 2017, at 19:18, Mark Andrews wrote:
> 
> > In message <A94C17CD-DC4B-43C9-AD3D-69735FC6B2BC@qti.qualcomm.com>, 
> > Pete Resnick writes:
> >>
> >> On 6 Jul 2017, at 16:52, Mark Andrews wrote:
> >>
> >>> Or you could stop trying to reinforce the myth that new RR types
> >>> are hard to deploy.  They really aren't.  They actually get used
> >>> all the time.
> >>
> >> I'm running the latest version of MacOS Server. I can't get a new RR
> >> type into the UI. Even if I use the command line "dnsconfig" tool, I
> >> can't add a record of a type it doesn't know about; I only get A, 
> >> AAAA,
> >> CNAME, NS, MX, PTR, SRV, and TXT. Yes, I could go hacking around in 
> >> the
> >> BIND configs that underly their implementation. And at that point I 
> >> say,
> >> "New RR types are hard to deploy; not a myth." Telling me I can use a
> >> different operating system or not use a validating UI is not a
> >> reasonable response.
> >
> > Well use nsupdate.  That also ships with the Mac.
> 
> Of course doing that likely means I'll have records that don't show up 
> in the server UI. Not entirely thrilling. And I could accomplish exactly 
> the same thing by directly editing the BIND config files, so I'm not 
> sure what that gains me in terms of "not hard to deploy".

Given Macs can register their own addresses in the DNS using UPDATE
I doubt that the strawman you are attempting to raise here happens
and if it does log a bug with Apple.  Log a bug with Apple that the
tool doesn't support all known types and that it doesn't support
unknown types.

> >> The fact is the DNS doesn't provide a way for implementations to
> >> dynamically update the RR types to provide sensible UI; it's left as 
> >> an
> >> exercise for each individual implementer. (Yes, I know about
> >> draft-levine-dnsextlang; it doesn't seem to have gotten anywhere.) 
> >> You
> >> can't much complain about the difficulty of deployment when the
> >> community won't provide the tools to make deployment easier.
> >
> > Well BIND is designed to allow new types to be added easily.  It
> > may require recompiling rather than updating a text file but it is
> > not beyond people to do because we see people doing just that.
> 
> ¬(∃𝑥𝐶(𝑥) → ∀𝑥𝐶(𝑥))
> 
> Just because you you see some people recompiling does not mean that all 
> (or most, or a significant number) can. Set that aside, it is nowhere 
> near reasonable for knowing how to recompile a piece of code to be 
> required in order for me to add a new RR type. Set that aside, this is 
> the epitome of "hard to deploy": Some implementations can't do it at 
> all, some implementations you have to go hacking around in hidden config 
> files, and some implementations you have to recompile the binary to get 
> a reasonable UI experience.
> 
> This is the problem with DNS being considered a system service rather 
> than a user application. It's got both aspects. Until the user 
> experience for configuring the DNS with a new RR type does not require 
> the skills of someone able to recompile code, it is absolutely going to 
> be the case that new RR types are hard to deploy, and calling it a myth 
> is not helpful.

We supply user applications to manipulate the DNS.  Those tools are
capable of updating yet to be defined types.  Putting a front end
on those tools that takes the new type someone dreams up is easy.

We also supply C libraries that can do the same thing.  No one needs
to wait to use a new type.

There are python and perl tools available that can also send update
messages.

If you just want the new records to be a blob of text a shell script
like this will convert the record to unknown format suitable to be
used by nsupdate.

% sh junk
hello world
\# 11 68656C6C6F20776F726C64
% cat junk
read record
hex=`printf "%s" "$record" | hexdump -ve '/1 "%02X"'`
length=`printf "%s" "$hex" | wc -c`
length=`expr $length / 2`
echo '\#' $length $hex
% 

You can create all DNS records similarly.  Building them up
field by field.

One can do something similar in any scripting language.

So no it isn't hard to use a new type.  You just need to stop waiting
for the stupid DNS hoster to do it for you and organise to do it
yourself.

> pr
> -- 
> Pete Resnick <http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Sat Jul  8 22:55:41 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94F4F127698; Sat,  8 Jul 2017 22:55:32 -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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 qZBJ-rlU7iXB; Sat,  8 Jul 2017 22:55:31 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E9AE12741D; Sat,  8 Jul 2017 22:55:31 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTP id EFA78C086D20; Sat,  8 Jul 2017 22:55:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=AD4NqTP0FFpFpi MtB9fcXamVPaM=; b=cDpIN+rezwd/nhsuPUJEm/fOZUbVtbOYdeIsOo7EsGuZRg EaK0zDHptTqlnHJtGBuS1BtKWOUuHQ3i7LJVaiToXF+APELpxcRCZYAoF4PNHdl6 CD7ZQV+N3UjVyrxvlftYgqR/2UJtp6TK+ij5ITYkOrbJerDavJBj/cwu4sfJI=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTPSA id 4C8B0C086D0C; Sat,  8 Jul 2017 22:55:30 -0700 (PDT)
Date: Sun, 9 Jul 2017 00:55:27 -0500
From: Nico Williams <nico@cryptonector.com>
To: Mark Andrews <marka@isc.org>
Cc: Pete Resnick <presnick@qti.qualcomm.com>, John C Klensin <john-ietf@jck.com>, dnsop <dnsop@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>, Paul Vixie <paul@redbarn.org>, IETF <ietf@ietf.org>
Subject: Re: new DNS classes
Message-ID: <20170709055526.GI3393@localhost>
References: <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <CAMm+Lwjd6xVp-EDp=doevx=AP8qws_Mv++aL733yHEyUF72EMA@mail.gmail.com> <562EC659F89FA92A09CAC4DB@PSB> <20170706153955.GB3393@localhost> <20170706215236.99A8C7DB2FBA@rock.dv.isc.org> <A94C17CD-DC4B-43C9-AD3D-69735FC6B2BC@qti.qualcomm.com> <20170708001825.2FB117DFD520@rock.dv.isc.org> <EDFEF9A1-99CF-4F25-9C1C-051E78949967@qti.qualcomm.com> <20170709015851.E5C877E07ADA@rock.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170709015851.E5C877E07ADA@rock.dv.isc.org>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1PvHcsHCvH6V3BsBRI8CUxNnNRk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Jul 2017 05:55:33 -0000

On Sun, Jul 09, 2017 at 11:58:51AM +1000, Mark Andrews wrote:
> One can do something similar in any scripting language.

Sure.  The people on this list can, and many others too.  Still, all of
us together are a tiny proportion of the users that would need to be
able to.

> So no it isn't hard to use a new type.  You just need to stop waiting
> for the stupid DNS hoster to do it for you and organise to do it
> yourself.

Stop.  Don't tell us.  Don't tell the customers.  Start writing emails
and making calls to hosting providers instead; get them to fix their
crap.  Make, publish, and keep up to date a list of viable providers.

Nico
-- 


From nobody Sun Jul  9 09:44:09 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D77412EB13; Sun,  9 Jul 2017 09:44:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.001
X-Spam-Level: 
X-Spam-Status: No, score=-7.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_HI=-5, RP_MATCHES_RCVD=-0.001, 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 P3ONop8iIGrT; Sun,  9 Jul 2017 09:44:06 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55C2812EAF7; Sun,  9 Jul 2017 09:44:06 -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=1499618646; x=1531154646; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=GsoJscYUGW266ZkEqVmDpnkDzh0Io6q2ODnO8JWntiI=; b=RUKGoNvIsG2uV7eTJrKo7lTsSXlPIz6ALBzI1Sdc3KuRRgP305yp2STH AvCjnV74+lsqVnpDgm7tU0tGBHKXlIlW3smhcNXeydJhpI0aXc46V6UI4 x/E/g/Pdco9e15gGt0vpSb4vPZznj/NRFnrISkbPzZAYPqKfjwFfMbbWu A=;
X-IronPort-AV: E=Sophos;i="5.40,335,1496127600"; d="scan'208";a="111094214"
Received: from unknown (HELO Ironmsg03-L.qualcomm.com) ([10.53.140.110]) by sabertooth02.qualcomm.com with ESMTP; 09 Jul 2017 09:44:05 -0700
X-IronPort-AV: E=McAfee;i="5800,7501,8586"; a="1406799185"
X-MGA-submission: =?us-ascii?q?MDGlyaJpnhahzANAUX+TX1cQmzfjB57vHQdBjm?= =?us-ascii?q?YnjHtOuQhyj7FeSqcD0LUsQUqV9NvPH0Y2dQBeA8BhjxGbQ8H7X3n0mA?= =?us-ascii?q?LBtOaRcbO5rE0RN4L5JcXvZw+JuJtLbVfQN57Ttf+gw4ZMziDDy4cqVj?= =?us-ascii?q?XA?=
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 09 Jul 2017 09:44:05 -0700
Received: from [10.64.97.228] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Sun, 9 Jul 2017 09:44:04 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Mark Andrews <marka@isc.org>
CC: Nico Williams <nico@cryptonector.com>, John C Klensin <john-ietf@jck.com>,  dnsop <dnsop@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>, Paul Vixie <paul@redbarn.org>, IETF <ietf@ietf.org>
Subject: Re: new DNS classes
Date: Sun, 9 Jul 2017 11:44:02 -0500
Message-ID: <D491DDB9-0788-41B4-AD63-586CCA98512E@qti.qualcomm.com>
In-Reply-To: <20170709015851.E5C877E07ADA@rock.dv.isc.org>
References: <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <CAMm+Lwjd6xVp-EDp=doevx=AP8qws_Mv++aL733yHEyUF72EMA@mail.gmail.com> <562EC659F89FA92A09CAC4DB@PSB> <20170706153955.GB3393@localhost> <20170706215236.99A8C7DB2FBA@rock.dv.isc.org> <A94C17CD-DC4B-43C9-AD3D-69735FC6B2BC@qti.qualcomm.com> <20170708001825.2FB117DFD520@rock.dv.isc.org> <EDFEF9A1-99CF-4F25-9C1C-051E78949967@qti.qualcomm.com> <20170709015851.E5C877E07ADA@rock.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.6r5347)
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/ietf/X4EWp2biYDnZrM8J_rIgrMsdKHw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Jul 2017 16:44:08 -0000

On 8 Jul 2017, at 20:58, Mark Andrews wrote:

> In message <EDFEF9A1-99CF-4F25-9C1C-051E78949967@qti.qualcomm.com>, 
> Pete Resnic
> k writes:
>> On 7 Jul 2017, at 19:18, Mark Andrews wrote:
>>
>>> Well use nsupdate.  That also ships with the Mac.
>>
>> Of course doing that likely means I'll have records that don't show 
>> up
>> in the server UI. Not entirely thrilling. And I could accomplish 
>> exactly
>> the same thing by directly editing the BIND config files, so I'm not
>> sure what that gains me in terms of "not hard to deploy".
>
> Given Macs can register their own addresses in the DNS using UPDATE...

You mean an A or AAAA record, which the UI does support?

> ...Log a bug with Apple that the
> tool doesn't support all known types and that it doesn't support
> unknown types.

And in the meanwhile, you still say, "new RR types are not hard to 
deploy"?

> We supply user applications to manipulate the DNS.  Those tools are
> capable of updating yet to be defined types.  Putting a front end
> on those tools that takes the new type someone dreams up is easy.

To quote a favorite line of mine, I grant the point: If things were 
different, they wouldn't be the same.

Creating these front ends apparently has not happened, so how does this 
address the point that new RR types are hard to deploy?

> We also supply C libraries that can do the same thing.  No one needs
> to wait to use a new type.

I refer the honourable gentleman to the answer I gave some moments ago.

Sure, it would be easy to write code to make tools exist that would make 
it be easy to deploy. Those tools do not currently exist. It is 
therefore still hard to deploy.

> There are python and perl tools available that can also send update
> messages.

I refer the honourable gentleman to the answer I gave some moments ago.

> If you just want the new records to be a blob of text a shell script
> like this will convert the record to unknown format suitable to be
> used by nsupdate.
>
> % sh junk
> hello world
> \# 11 68656C6C6F20776F726C64
> % cat junk
> read record
> hex=`printf "%s" "$record" | hexdump -ve '/1 "%02X"'`
> length=`printf "%s" "$hex" | wc -c`
> length=`expr $length / 2`
> echo '\#' $length $hex
> %
>
> You can create all DNS records similarly.  Building them up
> field by field.
>
> One can do something similar in any scripting language.

I think you have proved my point exceedingly well there.

> So no it isn't hard to use a new type.

Nobody said "use". The word was "deploy". Until a huge number of hosting 
providers and OS vendors and tool writers get their act together writ 
large (and that includes tool vendors who require recompiles and/or fun 
shell scripts in order to have a remotely sane UI experience), 
deployment of a new RR type is hard.

> You just need to stop waiting
> for the stupid DNS hoster to do it for you and organise to do it
> yourself.

That does not solve the deployment problem.

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


From nobody Sun Jul  9 12:27:08 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6790012ECCE; Sun,  9 Jul 2017 12:27:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 tAGauVd3BRws; Sun,  9 Jul 2017 12:27:00 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 4692812ECC3; Sun,  9 Jul 2017 12:27:00 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dUHr3-0003UD-5w; Sun, 09 Jul 2017 19:26:53 +0000
Date: Sun, 09 Jul 2017 21:26:43 +0200
Message-ID: <m2fue51kek.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Cc: Mark Andrews <marka@isc.org>, Phillip Hallam-Baker <phill@hallambaker.com>, IETF <ietf@ietf.org>, dnsop <dnsop@ietf.org>, Paul Vixie <paul@redbarn.org>, John C Klensin <john-ietf@jck.com>
Subject: Re: new DNS classes
In-Reply-To: <D491DDB9-0788-41B4-AD63-586CCA98512E@qti.qualcomm.com>
References: <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <CAMm+Lwjd6xVp-EDp=doevx=AP8qws_Mv++aL733yHEyUF72EMA@mail.gmail.com> <562EC659F89FA92A09CAC4DB@PSB> <20170706153955.GB3393@localhost> <20170706215236.99A8C7DB2FBA@rock.dv.isc.org> <A94C17CD-DC4B-43C9-AD3D-69735FC6B2BC@qti.qualcomm.com> <20170708001825.2FB117DFD520@rock.dv.isc.org> <EDFEF9A1-99CF-4F25-9C1C-051E78949967@qti.qualcomm.com> <20170709015851.E5C877E07ADA@rock.dv.isc.org> <D491DDB9-0788-41B4-AD63-586CCA98512E@qti.qualcomm.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qKf8C2WqRYOg7C6iwrfvs4hG56c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Jul 2017 19:27:01 -0000

while i enjoy berating vendors for bugs and poor feature sets as much as
the next person, well maybe more, it's a target rich environment.  if we
could come to agreement on what the right thing is, what we actually
want here, we could at least beat them on the right vector.

but as i said at the beginning, i am not even sure dns classes are the
answer.  this is exacerbated by the draft in question trying to shoot
down the users' needs without even exploring them.  and that is still my
main issue.  we're shooting down solutions when we have not yet defined
the problem.

30c in praha today

randy


From nobody Sun Jul  9 18:14:41 2017
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21DF3129AEB; Sun,  9 Jul 2017 18:14:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 Mk-26MkRcxiS; Sun,  9 Jul 2017 18:14:31 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (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 B262E126D05; Sun,  9 Jul 2017 18:14:31 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 5979C3493D3; Mon, 10 Jul 2017 01:14:29 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 4469916003A; Mon, 10 Jul 2017 01:14:29 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 30239160053; Mon, 10 Jul 2017 01:14:29 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id nusaM9SBB0yk; Mon, 10 Jul 2017 01:14:29 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id D367616003A; Mon, 10 Jul 2017 01:14:28 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 3BE867E1FE36; Mon, 10 Jul 2017 11:14:26 +1000 (AEST)
To: Randy Bush <randy@psg.com>
Cc: Pete Resnick <presnick@qti.qualcomm.com>, Phillip Hallam-Baker <phill@hallambaker.com>, IETF <ietf@ietf.org>, dnsop <dnsop@ietf.org>, Paul Vixie <paul@redbarn.org>, John C Klensin <john-ietf@jck.com>
From: Mark Andrews <marka@isc.org>
References: <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <595BD53E.60701@redbarn.org> <E739C1CB-E60E-4B4B-99CF-1E6C68CB6926@rfc1035.com> <7DCA3DAF1993A2E66915D0DD@JcK-HP5.jck.com> <595BE0D5.5000106@redbarn.org> <CAMm+Lwjd6xVp-EDp=doevx=AP8qws_Mv++aL733yHEyUF72EMA@mail.gmail.com> <562EC659F89FA92A09CAC4DB@PSB> <20170706153955.GB3393@localhost> <20170706215236.99A8C7DB2FBA@rock.dv.isc.org> <A94C17CD-DC4B-43C9-AD3D-69735FC6B2BC@qti.qualcomm.com> <20170708001825.2FB117DFD520@rock.dv.isc.org> <EDFEF9A1-99CF-4F25-9C1C-051E78949967@qti.qualcomm.com> <20170709015851.E5C877E07ADA@rock.dv.isc.org> <D491DDB9-0788-41B4-AD63-586CCA98512E@qti.qualcomm.com> <m2fue51kek.wl-randy@psg.com>
Subject: Re: new DNS classes
In-reply-to: Your message of "Sun, 09 Jul 2017 21:26:43 +0200." <m2fue51kek.wl-randy@psg.com>
Date: Mon, 10 Jul 2017 11:14:26 +1000
Message-Id: <20170710011426.3BE867E1FE36@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eDj4hvo3YwWvED_uAEGK2x02X5Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jul 2017 01:14:33 -0000

In message <m2fue51kek.wl-randy@psg.com>, Randy Bush writes:
> while i enjoy berating vendors for bugs and poor feature sets as much as
> the next person, well maybe more, it's a target rich environment.  if we
> could come to agreement on what the right thing is, what we actually
> want here, we could at least beat them on the right vector.

a) For DNS tools to support unknown types and classes (RFC 3597).

b) For DNS tools to add support for allocated data types within X
   months of them being assigned by IANA.  Allocated types are
   supposed to have stable wire and presentation formats.

for a reasonable value of X (<= 12?).

> but as i said at the beginning, i am not even sure dns classes are the
> answer.  this is exacerbated by the draft in question trying to shoot
> down the users' needs without even exploring them.  and that is still my
> main issue.  we're shooting down solutions when we have not yet defined
> the problem.
> 
> 30c in praha today
> 
> randy
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Sun Jul  9 19:01:35 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B2E312EC39 for <ietf@ietfa.amsl.com>; Sun,  9 Jul 2017 19:01:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 n2BlDsvmgYxj for <ietf@ietfa.amsl.com>; Sun,  9 Jul 2017 19:01:31 -0700 (PDT)
Received: from miucha.iecc.com (w6.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7203C129B43 for <ietf@ietf.org>; Sun,  9 Jul 2017 19:01:31 -0700 (PDT)
Received: (qmail 74584 invoked from network); 10 Jul 2017 02:01:29 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 10 Jul 2017 02:01:29 -0000
Date: 10 Jul 2017 02:01:07 -0000
Message-ID: <20170710020107.91388.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Cc: presnick@qti.qualcomm.com
Subject: Re: new DNS classes
In-Reply-To: <D491DDB9-0788-41B4-AD63-586CCA98512E@qti.qualcomm.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3K0gzsHTyyKdXcAx1plHDtycTsM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jul 2017 02:01:33 -0000

In article <D491DDB9-0788-41B4-AD63-586CCA98512E@qti.qualcomm.com> you write:
>And in the meanwhile, you still say, "new RR types are not hard to 
>deploy"?

Clearly it depends on your frame of reference.  If I needed to publish
some new RRs to enable stealth malware that would prevent a North
Korean nuclear missile launch, I could probably figure out how to do
it using some of Mark's kludges.

In real life, with most configuration software, it's still too hard.

R's,
John


From nobody Mon Jul 10 05:13:44 2017
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5EBC127010; Mon, 10 Jul 2017 05:13:42 -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 UoAT-xWubVkn; Mon, 10 Jul 2017 05:13:40 -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 6FB72126BF0; Mon, 10 Jul 2017 05:13:38 -0700 (PDT)
X-AuditID: c1b4fb30-aeec49c000001664-3f-59636f71af8d
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.183.42]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id E5.ED.05732.17F63695; Mon, 10 Jul 2017 14:13:37 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.44) with Microsoft SMTP Server id 14.3.352.0; Mon, 10 Jul 2017 14:13:35 +0200
Subject: Re: Tsvart telechat review of draft-ietf-trill-mtu-negotiation-06
To: "Zhangmingui (Martin)" <zhangmingui@huawei.com>, "tsv-art@ietf.org" <tsv-art@ietf.org>
CC: "draft-ietf-trill-mtu-negotiation.all@ietf.org" <draft-ietf-trill-mtu-negotiation.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "trill@ietf.org" <trill@ietf.org>
References: <149925973580.17545.6979655005275084891@ietfa.amsl.com> <4552F0907735844E9204A62BBDD325E7A6546EF1@NKGEML515-MBX.china.huawei.com>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <1419a786-f8c4-ad1b-1fb0-9e4562939445@ericsson.com>
Date: Mon, 10 Jul 2017 14:13:33 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <4552F0907735844E9204A62BBDD325E7A6546EF1@NKGEML515-MBX.china.huawei.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms090101070908000509020904"
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprAIsWRmVeSWpSXmKPExsUyM2K7lm5hfnKkwdsnghab/r1msXi2cT6L xfvJ29ksZu1ZxGJxZW4jmwOrR8uRt6weS5b8ZApgiuKySUnNySxLLdK3S+DKuLt/GVPBhA7G iiU3brI2MD4r7GLk5JAQMJGYvWA1UxcjF4eQwBFGiQmdp9khnOWMEs0zX7CAVAkLeElMuXUc qIqDQ0QgRmLi5wyQGmaB1YwSF5dtg2roZ5TYf3AHG0gDm4CFxM0fjWA2r4C9xMTtZ8EGsQio SmzY9ZgRxBYFGnRt5h1WiBpBiZMzn4DVcAqESUw5t4sFYkM3o0TbrP1MIAkhAW2JhqYO1gmM /LOQ9MxCVgeSYBYwk5i3+SEzhK0tsWzhayhbXOLWk/lQNdYSM34dZIOwFSWmdD9kh7BNJV4f /cgIYRtJvNvTyL6AkXMVo2hxanFSbrqRkV5qUWZycXF+nl5easkmRmDcHNzy22AH48vnjocY BTgYlXh4y62SI4VYE8uKK3MPMaoAzXm0YfUFRimWvPy8VCUR3hspQGnelMTKqtSi/Pii0pzU 4kOM0hwsSuK8jvsuRAgJpCeWpGanphakFsFkmTg4pRoY9a7L3HGcPy81KPqlx/uqtDid390i 3UZF5zqnBJl7+++cG3XQVP+h+Kmv7EdiTv9bamMVs7L7MEvtkZ4V1w9+nRr0oun5gZZjB1nK vnFWe6TyLEr6xqbpJbN5VUTmxhBfzXleWerNX3aYvf60Uffbd8ZkFSPu2a8m3fFX5P54YI8y zyvpZTP9lFiKMxINtZiLihMB4FzAzaMCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0vDJNAbASN1N-mcoPf-2-8T_dro>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jul 2017 12:13:42 -0000

--------------ms090101070908000509020904
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US

Den 2017-07-08 kl. 07:57, skrev Zhangmingui (Martin):
> Hi Magnus,
>
> Thanks for your careful review. Please see the reponses inline below.
>
> ________________________________________
> From: Magnus Westerlund [magnus.westerlund@ericsson.com]
> Sent: Wednesday, July 05, 2017 21:02
> To: tsv-art@ietf.org
> Cc: draft-ietf-trill-mtu-negotiation.all@ietf.org; ietf@ietf.org; trill=
@ietf.org
> Subject: Tsvart telechat review of draft-ietf-trill-mtu-negotiation-06
>
> Reviewer: Magnus Westerlund
> Review result: Not Ready
>
> This TSV-ART review is influenced by that I did the review of
> draft-ietf-trill-over-ip.
>
> 1. So draft-ietf-trill-over-ip-10 has MTU discovery needs for
> determining if the UDP encapsulation will work or not. It references  i=
n
> Section 8.4 the old RFC, i.e. RFC 6325, which is updated by
> draft-ietf-trill-mtu-negotiation.
>
>      TRILL IS-IS MTU PDUs, as specified in Section 5 of [RFC6325] and i=
n
>      [RFC7177], can be used to obtain added assurance of the MTU of a
>      link.
>
> However, this is not quite true, as if the IP path MTU is below 1470
> bytes, which is not unheard of, the algorithm in the MTU negotiation
> draft can't determine it. It will only report the IP path as having an
> MTU to small when the 1470 bytes probe fail.
>
> [Mingui]   I copied the relevant text from RFC 6325.
>      "The desired minimum acceptable inter-RBridge link MTU for the
>        campus, that is, originatingLSPBufferSize.  This is a 16-bit
>        unsigned integer number of octets that defaults to 1470 bytes,
>        which is the minimum valid value.  Any lower value being
>        advertised by an RBridge is ignored."
> So the minimum value of Sz would be 1470. IOW, IP path with MTU below 1=
470 will not be qualified as an adjaceny of the TRILL network topology.

So this issue (1) is mostly bringing up what I saw as an discrepancy=20
between trill-over-ip and this document. I think it is quite reasonable=20
to push the needed extensions for more generalized IP path MTU discovery =

in the Trill context onto the trill-over-ip document. However, I want to =

note that from my perspective if one think one can run Trill-over-IP=20
then one better have a mechanism that can do fragmentation and=20
reassembly to handle IP MTUs that will not let trill packets of 1470=20
bytes through as that is quite common, in fact IPv6/UDP/Trill over=20
regular ethernet with 1500 bytes IP MTU is sufficient to fail that=20
criteria.

>
> So, if the trill-over-ip authors want to use this as a mechanism, then =
the MTU
> negotiation draft needs to be expanded to have more flexible lower
> boundaries. However, that appear to affect MTU negotiation quite
> significant as it needs to separate algorithm for finding MTU, from the=

> different usage of the algorithm with different starting points. Where
> the normal will have a lower bound of 1470, and be more tightly coupled=

> to Sz when finding Lz. While the Trill-over-IP has a different usage.
>
> I think the trill WG needs to decide on how to slice this. If the
> MTU-negotiation only targets the explicit targets in the current draft =
and goes
> forward now. Or if they want to meet trill-over-ip's goals which will r=
equire
> restructuring.
>
> 2. Another issue, is that I think the algorithm is a bit short on
> transmission scheduling recommendations:
>
>      1) If RB1 successfully receives the MTU-ack from RB2 to the probe =
of
>         the value of link-wide Lz within k tries (where k is a
>         configurable parameter whose default is 3), link MTU size is se=
t
>         to the size of link-wide Lz and stop.
>
> If I do this test with all three packets back to back at line rate, I c=
ould
> potentially get all probes lost in the same burst loss in router queue =
or
> switch fabric. What I think is needed here is a specification on how th=
ese
> probes are transmitted. Spaced in a particular way, or at least minimal=

> distance, and are the additional probes only sent after the previous ha=
s been
> judged to have been lost, which makes it interact with the next issue.
>
> [Mingui] This seems an implementation space. However, the document may =
offer recommendations. The being recommended minimum interval between two=
 successive probes would affect the boot up speed of a TRILL campus. One =
RTT is a reasonable value.

Okay, for this there might be some implementation variations. However,=20
it can clearly affect the performance of the implementation so some=20
recommendation are likely good. I also think a spacing of one per RTT is =

quite reasonable. However, that leads to the question, how does the=20
sender know what RTT there is? Is there something in the TRILL protocol=20
that will determine the RTT and have a current value? Sorry, I don't=20
have time to digest the whole TRILL suit of specifications.


>
> 3. This is also unclear on what the criteria is for determining that so=
mething
> is lost:
>
>        a) If RB1 fails to receive an MTU-ack from RB2 after k tries, RB=
1
>            sets the "failed minimum MTU test" flag for RB2 in RB1's Hel=
lo
>            and stop.
>
> I fail to see any specification for the criteria when an MTU-ack should=
 be
> considered to have failed to reach the probing entity. So this appear t=
o
> require a timeout, and thus a timeout interval. Is the RTT known so tha=
t one
> can define something as lost after N*RTT? Are there possible delays in =
sending
> the MTU-ack that are considered okay that can affect this?
>
> [Mingui] Yes, this makes sense. An MTU-ack should be considered to have=
 failed two RTT after the probe is sent out.

So two questions on this. First, can a receiver know which MTU probe it=20
gets response to, i.e. are there some token or sequence number being=20
acked? Second, 2*RTT appear to be to short to make that conclusion in.=20
The reasons I say so is that there will be networks where the jitter of=20
the path is larger than the RTT sample, thus leading to=20
misinterpretation. Thus, I would recommend a bit more robustness to=20
misinterpretation and likely some minimal value that avoids low latency=20
paths wrongly classify the path. Note, I think it is needed to define=20
what the criteria is for when an MTU is considered lost, just because it =

appears that it affects both startup and robustness of the probing. It=20
also becomes a question of what tools in the probes that are used for=20
this, and if you actually need some additional ones.

>
> 4. Section 3, the algorithm in Step 1 is unable to reach the first term=
ination
> condition (3) "If lowerBound >=3D upperBound" in some cases.
>
> [Mingui] This algorithm has been updated through a few rounds of revisi=
ons. Let me insert a few minor updates to the cited text as below.
>
>    Step 1: RB1 tries to send an MTU-probe padded to the size x.
>
>     1) If RB1 fails to receive an MTU-ack from RB2 after k tries:
>
>           upperBound is set to x and x is set to [(lowerBound +
>           upperBound)/2], rounded up to the nearest integer.
>
> [Mingui] s/uppperBound is set to x/uppperBound is set to x-1/
> [Mingui] s/rounded up to the nearest integer./rounded down to the neare=
st integer./
>
>
>     2) If RB1 receives an MTU-ack to a probe of size x from RB2:
>
>           link MTU size is set to x, lowerBound is set to x and x is se=
t
>           to [(lowerBound + upperBound)/2], rounded up to the nearest
>           integer.
>
> [Mingui] s/rounded up to the nearest integer./rounded down to the neare=
st integer./
> [Mingui] Append one condistion to this step 2): If lowerBound equals up=
perBound-1 then x is set to upperBound.
>
>     3) If lowerBound >=3D upperBound or Step 1 has been repeated n time=
s
>        (where n is a configurable parameter whose default value is 5),
>        stop.
>
>     4) Repeat Step 1.
>
> I run this on the input data: Lower bound =3D 1470, Upper bound =3D 921=
6 and with
> an MTU of 7935 and gets the following sequence:
>
> Lower   Upper   X
> 1470    9216    5343
> 5343    9216    7280
> 7280    9216    8248
> 7280    8248    7764
> 7764    8248    8006
> 7764    8006    7885
> 7885    8006    7946
> 7885    7946    7916
> 7916    7946    7931
> 7931    7946    7939
> 7931    7939    7935
> 7935    7939    7937
> 7935    7937    7936
> 7935    7936    7936
> 7935    7936    7936
>
> Thus, the termination condition needs to change.
>
> [Mingui] After the update of the text, the sequence would become:
> Lower   Upper   X
> 1470    9216    5343
> 5343    9216    7279
> 7279    9216    8247
> 7279    8246    7762
> 7762    8246    8004
> 7762    8003    7882
> 7882    8003    7942
> 7882    7941    7911
> 7911    7941    7926
> 7926    7941    7933
> 7933    7941    7937
> 7933    7936    7934
> 7934    7936    7935
> 7935    7936    7935
Shouldn't the above line result in that X becomes 7936, as the probe=20
before it succeeds, and then the new additional rule in step (2) then X=20
becomes upper bound.

> 7935    7936    7936
> 7935    7935    7935
>
> The second I notice is that having a limitation on number of steps as 5=
,
>
> [Mingui] Since the testing might be too resource consuming, implementor=
s suggested this limitation. Afterall, the purpose of testing a Lz value =
is to improve the efficiency (if Lz > Sz) rather than reach the optimal e=
fficiency.

Ok.

>
> results in quite a large gap
> between upper and lower bound in which the MTU exists in.
>
> 5. I frankly gets confused by the application of the binary search. Fir=
st it
> will in many case not be run to termination where the actual MTU is det=
ermined.
> Then the result of the upper and lower bound are just used to confirm t=
he Sz
> value. There are no discussion about using the MTU search to determine =
a new
> possible value for Sz.
>
> [Mingui] Because the MTU search will NOT be used to determine a new pos=
sible value for Sz. It is only applicable to Lz.
>
>   The text is not even explicit that lower bound is the
> highest known to work Transmission unit size at the time of testing. I =
think
> section 3, should conclude in determine some TU value, and if that is S=
z or
> something other appears quite relevant for what to do in the later sect=
ions.
>
> [Mingui] As specified in Section 3, =E2=80=9Clink MTU size=E2=80=9D is =
already set to the lower bound. This tested =E2=80=9Clink MTU size=E2=80=9D=
 is the =E2=80=9CTU=E2=80=9D value. This value is potentially larger than=
 Sz as explained in the introduction and Section 2.
>

Ok, I think I am getting what the different values are for.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Media Technologies, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------



--------------ms090101070908000509020904
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME-kryptografisk signatur

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
DLkwggX7MIID46ADAgECAhEA75oIXW3eBHJH2u7brn5gnDANBgkqhkiG9w0BAQUFADA6MREw
DwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2
MjAeFw0xNTAxMjMwODUwNTdaFw0xODAxMjMwODUwNTdaMHAxETAPBgNVBAoMCEVyaWNzc29u
MRowGAYDVQQDDBFNYWdudXMgV2VzdGVybHVuZDEtMCsGCSqGSIb3DQEJARYebWFnbnVzLndl
c3Rlcmx1bmRAZXJpY3Nzb24uY29tMRAwDgYDVQQFEwdlcmFtc3dkMIIBIjANBgkqhkiG9w0B
AQEFAAOCAQ8AMIIBCgKCAQEAkULrp/ViIWFfDbY2Ycew0bXJc2In2WNQbPORLyFXNpRhjhmg
ot5P/0w90T4HY0H6QayjIPK6qIGt1DBXwkq/QHoRsFZiDK9JDnk2WUDcqbJaHqMXvkhj4Jl4
KvonZ31T3NF/8OlcEjumVc8AUA6iccOeUva3TvL/EOqY3f4bsem4ER3KAcY/lTPWivSY+/Aw
vS64JjaANOHVhZ0LUj10JTe9CpdXB+1nMpqLFYkjse/2ahQuKyaBKhKJs35pSYijh3Ln+vMv
YUNEna2LjHvkCPVo5Oihylxjmd1OSDXND7125tgo/kB08RtaJ9u6PNw0CoUgA+d23UzVzlYg
aSJbhwIDAQABo4IBxDCCAcAwSAYDVR0fBEEwPzA9oDugOYY3aHR0cDovL2NybC50cnVzdC50
ZWxpYS5jb20vZXJpY3Nzb25ubGluZGl2aWR1YWxjYXYyLmNybDCBggYIKwYBBQUHAQEEdjB0
MCgGCCsGAQUFBzABhhxodHRwOi8vb2NzcDIudHJ1c3QudGVsaWEuY29tMEgGCCsGAQUFBzAC
hjxodHRwOi8vY2EudHJ1c3QudGVsaWFzb25lcmEuY29tL2VyaWNzc29ubmxpbmRpdmlkdWFs
Y2F2Mi5jZXIwKQYDVR0RBCIwIIEebWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24uY29tMFUG
A1UdIAROMEwwSgYMKwYBBAGCDwIDAQESMDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3Np
dG9yeS50cnVzdC50ZWxpYXNvbmVyYS5jb20vQ1BTMB0GA1UdJQQWMBQGCCsGAQUFBwMEBggr
BgEFBQcDAjAdBgNVHQ4EFgQUwff+Y5pMEPJX7xortCv8deSKeQEwHwYDVR0jBBgwFoAUsQ3K
1Ea3r4YCwy9vBsoOdnF/SzcwDgYDVR0PAQH/BAQDAgWgMA0GCSqGSIb3DQEBBQUAA4ICAQBy
rk0JhGgu9Fd/0Fg1cMhSa882HMQZWQLT1V4PFQpU6t2an8xaqT5JsxOpuxb+WxwpKG+UDbzQ
cWgcb/DPW3Mc0AvhTFII1qAYf6Smkq6SOD/8TACjH+dy7JrbcNYJcTlVNBlC/V/C+waICkER
wuMC/8QjXs0ExJekAD3i/3GUok9WnvEHsohIL04qk1lbvJN4WGHCHFercX11Ch+UjStHwtyw
zyFWi64CqD48kKqPwEne3Lj7ozxzuwCCaJI9fmCQgLfSL+UcDgEb7cQucMAnB/Zxlz6U6ohd
PRlQHaLevAYD2UK+BlhZKLAv/DNUz0nk6fx4CiJF5DIRteUdzGoeGcnWMWO9hv5PkEJC1WkZ
gYXZ/91HMUjsYUuy5/EsmkqvkCalRudoqe6Pex3A34iFGNvDhI3fCrbvmRS4FARPse5D8BLu
e/PIvAPNUC7xl8UcfnTNVgy5ITzWNiY9hIrbAzfPbTXyZSIdMD+HTNg33ziMbu2Iry/2eS1X
/whXkApnQNpHplvzf1xMEeNPlDKtL8OOg+9y4ESdn27EKxeeaaFXsrhb3z1woIjQxXINft5W
EPXWnks/YBCvrLTH8kRCLZgH17zDxb+MLqKj1XUQtBKgDhb+VswJM6GF+dDeBJoEYjvLR1Sx
l5yfaRj0F7HYkjRUwyehwSHgTVqtgnT9QjCCBrYwggSeoAMCAQICEQCgDMvMm5mY7OI6cPR8
wcBZMA0GCSqGSIb3DQEBBQUAMDcxFDASBgNVBAoMC1RlbGlhU29uZXJhMR8wHQYDVQQDDBZU
ZWxpYVNvbmVyYSBSb290IENBIHYxMB4XDTE0MDUyNzA3NDYyMVoXDTI0MDUyNzA3NDYyMVow
OjERMA8GA1UECgwIRXJpY3Nzb24xJTAjBgNVBAMMHEVyaWNzc29uIE5MIEluZGl2aWR1YWwg
Q0EgdjIwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQDaulPrX0iWU5+JOOqjddx4
Gnl17DJhklkoXOgOSBMhW6FzGVt5RR7KPv+rjt2YpbwdoqWSYa4VPkS/72vuQoWsvz2avWWX
hPTdNzrB3zs5cJO7sKIyd+LRy4l/8kKK4iPm+Q18XyGF0xTuc5WS3WiMScJSxEKdIOP8xehB
raHZabrGh9OxQHC4iBHkzD0YF3J/vBqBTr7blRzYf1h3j5a7qVIHCPfz+eCE175mResXDQRI
7LvMiZtVaqitBl0oAJiJyeBmvEujBNsIEgUQ6JcQFG5ny0EazLywv7clwb7izvLgoXc6SFrd
0D7TGJtkdldVJtMwDYXpyFMGAijT6uf8h2kuPIwrDgQFNEyIQZ4q52ZpRGwugC6sMxgHEDGj
A/CxX9aC5Vi1EMRJiOGF6gV3T+V5yHDHSBBeQbVAXm8wSTDBfXQwdro/AXqET0mG6Rpe4q2F
GBaauE8qHEO6qR3WAEgvjVfFU2k6xZx1qmvwhkXadxh6ZIMXzgb6WpjivLnR0GEKNrgN2DXd
vo+6eAt45Bhvmeka2TrJDxMLWiBy8QYgNeNXYQsuREnDsjWo6wF0LqbA5769om9nn/uJzmzx
b3nT1iHue5co9J93ta06kxiASHvcIzZwAOjKnmk0vR3IT7Qbzq2of3E1s18xo8DM9D91Cak0
Nq+RALtdv1uZKQIDAQABo4IBuDCCAbQwgYoGCCsGAQUFBwEBBH4wfDAtBggrBgEFBQcwAYYh
aHR0cDovL29jc3AudHJ1c3QudGVsaWFzb25lcmEuY29tMEsGCCsGAQUFBzAChj9odHRwOi8v
cmVwb3NpdG9yeS50cnVzdC50ZWxpYXNvbmVyYS5jb20vdGVsaWFzb25lcmFyb290Y2F2MS5j
ZXIwEgYDVR0TAQH/BAgwBgEB/wIBADBVBgNVHSAETjBMMEoGDCsGAQQBgg8CAwEBAjA6MDgG
CCsGAQUFBwIBFixodHRwczovL3JlcG9zaXRvcnkudHJ1c3QudGVsaWFzb25lcmEuY29tL0NQ
UzBLBgNVHR8ERDBCMECgPqA8hjpodHRwOi8vY3JsLTMudHJ1c3QudGVsaWFzb25lcmEuY29t
L3RlbGlhc29uZXJhcm9vdGNhdjEuY3JsMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcD
BDAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFLENytRGt6+GAsMvbwbKDnZxf0s3MB8GA1Ud
IwQYMBaAFPCPWTgAs/WPmpYM1ev6e6oX6BMSMA0GCSqGSIb3DQEBBQUAA4ICAQBuByBsr6x3
PZBCsmGbcSZ/XL+0tnVMblInoJgL1Bh3PiRicgdo8l+6cvWp/ArBwMYNwSNyrvY9IewyaV8n
65c5oN+l2JDUuzrdANVKnYxha7ZyCEiPmY98sB2bnZgxfJLXQYoRwI7pOOwfyoP2fCYVCd+x
hsfysYiIl4ORzE3TpeppQ2yWkyBBmoHUXJh97ue6+bJ2fqnVUoOVMVnYYEtvsz67v7w2z3fv
dcy04/RnoylxSenxADi1tY9iIydHMgyOu3dfzsxU8AivMGG4aKStsCfUEyg0LlkbhqMrdnes
s3e1qAEueSRNASLfpFwyRmzmiuNh9onzuhER2yYhK/6IeCs4HQHrPhkY8JUmhtmdL2uErOZW
Os38FQhGWHWXI0g6SgdDObU0GEHju0MkDziOhm+BVwPZKN7B7wD7OPj6vlLVo6d8vLGK9byw
hEfXjxLIC3Qhtu5lJPTgIo5Bup+aBBjiJ/u9BfqryqZpudnWfG+wxC327rpNAq2OKdFsR92w
behSZD3mSSAemDVwGB2Yu0XHQYyyYfpWsGyGEyRSHKFhRwJdINPzWLI89wy4Wc+PgqyekkEm
Jqe6g4XSQFj4mqtwvqhP4dg2QCcKM/bh62RwfM7GeSS/LFGe84KmJjTDfvT8c2rK8nEyZ/em
OtwCGXQ6tZCByMNLxeDwU1TGbTGCAxcwggMTAgEBME8wOjERMA8GA1UECgwIRXJpY3Nzb24x
JTAjBgNVBAMMHEVyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EgdjICEQDvmghdbd4Eckfa7tuu
fmCcMA0GCWCGSAFlAwQCAQUAoIIBmTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqG
SIb3DQEJBTEPFw0xNzA3MTAxMjEzMzNaMC8GCSqGSIb3DQEJBDEiBCBkZp9Bjy09dKpnz9y9
P2u2SFhzoz+4gc1M0v9dU79aWzBeBgkrBgEEAYI3EAQxUTBPMDoxETAPBgNVBAoMCEVyaWNz
c29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyAhEA75oIXW3eBHJH
2u7brn5gnDBgBgsqhkiG9w0BCRACCzFRoE8wOjERMA8GA1UECgwIRXJpY3Nzb24xJTAjBgNV
BAMMHEVyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EgdjICEQDvmghdbd4Eckfa7tuufmCcMGwG
CSqGSIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAO
BggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgw
DQYJKoZIhvcNAQEBBQAEggEAZinfCAzEixREzQENdGMyuBiBn4LbCzfIbmDFb6oCyE50FH8z
BspCndEyYr1U+upoS+n5zExgEWpi/FDM+ULHukKGuv38qBLEL/Yg84pX7IGd0+CGHs7L6Zc7
Pxk9dju2vlsMNiAMSyLcjpmnxcv1ja/5AA/BtI8reCnaWC4Sv56XNBO3mPca6wl06PlRPa7L
VjC+O4uLHOeCy/m8qYGnSgDnhAX2hF38NTYXJ4rLxaOypmZ3FlpF68uelny+R1U+16OlGNeD
K8XnBI2qG0yf95F1J6jU/GA8/U4wmRc4s0LH8h/FZ0LvKsUFitwBK7yYLUm3nlgQPJ29UHYH
fFTEmAAAAAAAAA==
--------------ms090101070908000509020904--


From nobody Mon Jul 10 06:40:12 2017
Return-Path: <petr.spacek@nic.cz>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1486613176E for <ietf@ietfa.amsl.com>; Mon, 10 Jul 2017 06:40:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.001
X-Spam-Level: 
X-Spam-Status: No, score=-7.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_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 bsEC-Tz7DFqm for <ietf@ietfa.amsl.com>; Mon, 10 Jul 2017 06:40:09 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (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 E519312EC2B for <ietf@ietf.org>; Mon, 10 Jul 2017 06:40:08 -0700 (PDT)
Received: from [IPv6:2001:1488:fffe:6:c89f:f3ff:febd:be30] (unknown [IPv6:2001:1488:fffe:6:c89f:f3ff:febd:be30]) by mail.nic.cz (Postfix) with ESMTPSA id 0FBE660732; Mon, 10 Jul 2017 15:40:07 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1499694007; bh=W7kC3t5bR3lo+HtkiolOWnG9M6w7dostVNqMhDBvBUc=; h=To:From:Date; b=tEMhMp41woBpBfEXipY+/fIvEbPAwc5rD/8QypfV8AqmGaiHfRgGlZIC0TjQNctx5 GyffVjfYEGTqx+EoVDJLMjtiePZFNoC73wjh9XJJSwWPMJ5dKoQIz/9fmjo415mqsi 0eDupOjtDizkL1eOOWv48hxLlYWsbORPDXMQP50g=
Subject: Re: Call for Participation, Workshop on Internet naming systems
To: iab@iab.org
References: <9afa1487-e1f7-8758-7ead-ab8114b822ed@iab.org> <1743F4BA-1D2E-470E-9D84-6F7CCCDF9861@abc.se>
Cc: ietf@ietf.org
From: =?UTF-8?B?UGV0ciDFoHBhxI1law==?= <petr.spacek@nic.cz>
Organization: CZ.NIC
Message-ID: <ff9f8b7f-81ec-1eca-34c2-a770c67e9ea5@nic.cz>
Date: Mon, 10 Jul 2017 15:40:06 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0
MIME-Version: 1.0
In-Reply-To: <1743F4BA-1D2E-470E-9D84-6F7CCCDF9861@abc.se>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QK_e_UBT2oBz-ybxwXnyFvDdMfk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jul 2017 13:40:11 -0000

Hello,

beside other things, the proposed dates collide with DNS OARC 27
https://indico.dns-oarc.net/event/27/

Petr Špaček  @  CZ.NIC


On 29.6.2017 21:48, Börje Ohlman wrote:
> Dear All,
> 
> The topic of this IAB workshop is very closely related to the research
> area Information-centric Networking (ICN) which is addresses by the IRTF
> ICNRG. We therefore think it is very unfortunate that the proposed dates
> coincide with the major conference in the ICN field, ACM ICN-2017 which
> takes place in Berlin, Germany September 26-28,
> 2017, http://conferences2.sigcomm.org/acm-icn/2017/
> We are also planning an ICNRG interim meeting in Berlin September 29,
> 2017, as a followup to the
> conference, https://trac.ietf.org/trac/irtf/wiki/icnrg
> We would therefore ask you to consider some alternative dates for this
> IAB workshop.
> 
> Best regards,
> Dirk, Dave & Börje (IRTF ICNRG co-chairs)
> 
>> On 22 Jun 2017, at 22:53, IAB Chair <iab-chair@iab.org
>> <mailto:iab-chair@iab.org>> wrote:
>>
>> Call for Participation
>> IAB workshop on Explicit Internet Naming Systems
>>
>> Internet namespaces rely on Internet connected systems sharing a
>> common set of assumptions on the scope, method of resolution, and
>> uniqueness of the names.    That set of assumption allowed the
>> creation of URIs and other systems which presumed that you could
>> authoritatively identify a service using an Internet name, a service
>> port, and a set of locally-significant path elements.  
>>
>> There are now multiple challenges to maintaining that commonality of
>> understanding.  
>>
>>   * Some naming systems wish to use URIs to identify both a service
>>     and the method of resolution used to map the name to a serving
>>     node.  Because there is no common facility for varying the
>>     resolution method in the URI structure, those naming systems must
>>     either mint new URI schemes for each resolution service or infer
>>     the resolution method from a reserved name or pattern.  Both
>>     methods are currently difficult and costly, and the effort thus
>>     scales poorly.
>>   * Users’ intentions to refer to specific names are now often
>>     expressed in voice input, gestures, and other methods which must
>>     be interpreted before being put into practice.  The systems which
>>     carry on that interpretation often infer which intent a user is
>>     expressing, and thus what name is meant, by contextual elements.
>>      Those systems are linked to existing systems who have no access
>>     to that context and which may thus return results or create
>>     security expectations for an unintended name.
>>
>>   * Unicode allows for both combining characters and composed
>>     characters when local language communities have different
>>     practices.  When these do not have a single normalization, context
>>     is required to determine which to produce or assume in resolution.
>>      How can this context be maintained in Internet systems?
>>
>> While any of these challenges could easily be the topic of a
>> stand-alone effort, this workshop seeks to explore whether there is a
>> common set of root problems in the explicitness of the resolution
>> context, heuristic derivation of intent, or language matching.   If
>> so, it seeks to identify promising areas for the development of new,
>> more explicit naming systems for the Internet.
>>
>> We invite position papers on this topic to be submitted by July 28,
>> 2017 to ename@iab.org <mailto:ename@iab.org>.    Decisions on accepted
>> submissions will be made by August 11, 2017.
>>
>> Proposed dates for the workshop are September 28th and 29th, 2017 and
>> the proposed location is in the Pacific North West of North America.
>>  Finalized logistics will be announced prior to the deadline for
>> submissions.
>>
>> Ted Hardie
>> for the IAB


From nobody Mon Jul 10 09:07:30 2017
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0C111317C4; Mon, 10 Jul 2017 09:07:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-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=yitter.info header.b=Vy9bGSAE; dkim=pass (1024-bit key) header.d=yitter.info header.b=VEj+ZbcB
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 jSyqKXNJg9nl; Mon, 10 Jul 2017 09:07:22 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67AB3129B05; Mon, 10 Jul 2017 09:07:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 9B88EC03BA; Mon, 10 Jul 2017 16:06:51 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1499702811; bh=yPpQhG0wMXoKCiTNTy6Jv+1bzGTmOqrlEWsaq50TTHQ=; h=Date:From:To:Subject:References:In-Reply-To:From; b=Vy9bGSAEIq+2EAHhkpNmRSh9k/DbMw6hS3qVfR7s/QdZfxWSF4awVAKlBnHS8sROH QVrSaWI8PquWQc+S48UcXD7eFZvN8rh8ig6nVRyQbNVsrBaJTpt5bgMoxoAquXAQLP AAYPZGj+hK7cjmt9v6iJo0PAvQJnOzHGElU4IOA0=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VHtjGh4BbE-4; Mon, 10 Jul 2017 16:06:50 +0000 (UTC)
Date: Mon, 10 Jul 2017 12:06:48 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1499702810; bh=yPpQhG0wMXoKCiTNTy6Jv+1bzGTmOqrlEWsaq50TTHQ=; h=Date:From:To:Subject:References:In-Reply-To:From; b=VEj+ZbcBDdUxnFhDKcvBPhr3AfryuKOX9/v42pd4HwZbaSYWFuR6JUT81ogrLv3EG p7kXO+UBS+h4Jq1rN56XWFIuueBM1bBmHB5//8zUzX059LTPz+fRilo41iQy3GiA6H ugVwB9PpWYXsxM8/tG2ZW8DGG8lgnu9G36uyPM4I=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org, dnsop@ietf.org
Subject: Re: [DNSOP] new DNS classes
Message-ID: <20170710160648.svrng2b4hppfsizb@mx4.yitter.info>
References: <562EC659F89FA92A09CAC4DB@PSB> <20170706153955.GB3393@localhost> <20170706215236.99A8C7DB2FBA@rock.dv.isc.org> <A94C17CD-DC4B-43C9-AD3D-69735FC6B2BC@qti.qualcomm.com> <20170708001825.2FB117DFD520@rock.dv.isc.org> <EDFEF9A1-99CF-4F25-9C1C-051E78949967@qti.qualcomm.com> <20170709015851.E5C877E07ADA@rock.dv.isc.org> <D491DDB9-0788-41B4-AD63-586CCA98512E@qti.qualcomm.com> <m2fue51kek.wl-randy@psg.com> <20170710011426.3BE867E1FE36@rock.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170710011426.3BE867E1FE36@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Gg71zZMC9wprbug50xRddnx_BJM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jul 2017 16:07:24 -0000

On Mon, Jul 10, 2017 at 11:14:26AM +1000, Mark Andrews wrote:
> b) For DNS tools to add support for allocated data types within X
>    months of them being assigned by IANA.  Allocated types are
>    supposed to have stable wire and presentation formats.
> 
> for a reasonable value of X (<= 12?).

With all due respect, that sounds like you want to make some sort of
expectation of people on the Internet -- one requiring that they spend
time or money or both to solve a problem that they apparently don't
have.  If they _did_ have it, they would already be solving it.

For instance, infrastructure operation on the Internet provides thin
profit margins.  If a customer requires a lot of attention or
hand-holding then the profit margin on that customer can disappear
pretty quickly.  Therefore, it is of critical importance to have a lot
of automated checking in place that ensures that the customer's
expectations are met.  Tools to smooth the rough edges need to be
foolproof -- customers don't want to do "rocket science" or even
"appliance science".  The tools must not only to handle a user's
input, but to be able to be pretty confident that it is going to do
something like what they wanted it to do (or else give them a hint).
Otherwise, the angry customer contacts support and wipes out the
profit on them.  The natural consequence of that is just that the more
obscure RRs are just not going to be supported in those kinds of
tools.  The risk to companies' reputations and customer satisfaction
is too great for the meagre reward.

Is this bad for the Internet?  Yes.  But that's what you get in a
system that depends on voluntary participation: sometimes other people
don't want to play your game, and unless it seems like it will be
rewarding enough most of them aren't even going to bother asking what
the rules are.

And that's just for RRTYPEs.  There is no evidence whatever that a new
CLASS is of any utility at all to anyone except maybe DNS nerds.

It is ridiculous to claim that everyone else on the Internet is wrong
and, if they would just do what we say, everything would be good.  The
Internet did not eat every other communication technology because
people found it hard to follow the Official Rules Made Up By Netgods.
It took over because it worked well enough for most people most of the
time without too much effort.  Everything actually deployed on the
Internet scratches someone's itch.  Adding support for stuff to the
DNS is a hair shirt.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Mon Jul 10 10:22:48 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8E1112EA7C for <ietf@ietfa.amsl.com>; Mon, 10 Jul 2017 10:22:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 3MrZuhB-VOuN for <ietf@ietfa.amsl.com>; Mon, 10 Jul 2017 10:22:45 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CA70129432 for <ietf@ietf.org>; Mon, 10 Jul 2017 10:22:45 -0700 (PDT)
Received: (qmail 85360 invoked from network); 10 Jul 2017 17:22:44 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 10 Jul 2017 17:22:44 -0000
Date: 10 Jul 2017 17:22:22 -0000
Message-ID: <20170710172222.94206.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: new DNS classes
In-Reply-To: <20170710011426.3BE867E1FE36@rock.dv.isc.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UvX9CNThmYQa5FfpS8NP3DDXgYI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jul 2017 17:22:47 -0000

In article <20170710011426.3BE867E1FE36@rock.dv.isc.org> you write:
>b) For DNS tools to add support for allocated data types within X
>   months of them being assigned by IANA.  Allocated types are
>   supposed to have stable wire and presentation formats.

I think we can agree that we all want a pony.

R's,
John


From nobody Mon Jul 10 11:17:23 2017
Return-Path: <alexander.clemm@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 839EF13183F; Mon, 10 Jul 2017 11:17:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.222
X-Spam-Level: 
X-Spam-Status: No, score=-4.222 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, RP_MATCHES_RCVD=-0.001, 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 q6hpFTrMFAzw; Mon, 10 Jul 2017 11:17:05 -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 A526C131839; Mon, 10 Jul 2017 11:17:03 -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 DKC54971; Mon, 10 Jul 2017 18:17:01 +0000 (GMT)
Received: from SJCEML701-CHM.china.huawei.com (10.208.112.40) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 10 Jul 2017 19:17:00 +0100
Received: from SJCEML702-CHM.china.huawei.com ([169.254.4.142]) by SJCEML701-CHM.china.huawei.com ([169.254.3.186]) with mapi id 14.03.0301.000;  Mon, 10 Jul 2017 11:16:56 -0700
From: Alexander Clemm <alexander.clemm@huawei.com>
To: Christian Hopps <chopps@chopps.org>, "rtg-dir@ietf.org" <rtg-dir@ietf.org>
CC: "i2rs@ietf.org" <i2rs@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-i2rs-yang-l3-topology.all@ietf.org" <draft-ietf-i2rs-yang-l3-topology.all@ietf.org>
Subject: RE: [i2rs] Rtgdir early review of draft-ietf-i2rs-yang-l3-topology-10
Thread-Topic: [i2rs] Rtgdir early review of draft-ietf-i2rs-yang-l3-topology-10
Thread-Index: AQHS98KNUSDSz+AzG02R/9n7T9fsDqJNYazg
Date: Mon, 10 Jul 2017 18:16:55 +0000
Message-ID: <644DA50AFA8C314EA9BDDAC83BD38A2E0E0CD724@SJCEML702-CHM.china.huawei.com>
References: <149950173106.2877.12360295603653924176@ietfa.amsl.com>
In-Reply-To: <149950173106.2877.12360295603653924176@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.213.48.103]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.5963C49E.007F, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.4.142, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: ab8871c8153424ec3765661730c8f207
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lY9JZQBJcCg-5ilCwXyrTgjOkrc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jul 2017 18:17:07 -0000

SGVsbG8gQ2hyaXN0aWFuLA0KDQpUaGFuayB5b3UgZm9yIHlvdXIgcmV2aWV3LiAgV2Ugd2lsbCBh
cHBseSB0aGUgc3VnZ2VzdGVkIHVwZGF0ZXMuDQoNCi0tLSBBbGV4DQoNCi0tLS0tT3JpZ2luYWwg
TWVzc2FnZS0tLS0tDQpGcm9tOiBpMnJzIFttYWlsdG86aTJycy1ib3VuY2VzQGlldGYub3JnXSBP
biBCZWhhbGYgT2YgQ2hyaXN0aWFuIEhvcHBzDQpTZW50OiBTYXR1cmRheSwgSnVseSAwOCwgMjAx
NyAxOjE2IEFNDQpUbzogcnRnLWRpckBpZXRmLm9yZw0KQ2M6IGkycnNAaWV0Zi5vcmc7IGlldGZA
aWV0Zi5vcmc7IGRyYWZ0LWlldGYtaTJycy15YW5nLWwzLXRvcG9sb2d5LmFsbEBpZXRmLm9yZw0K
U3ViamVjdDogW2kycnNdIFJ0Z2RpciBlYXJseSByZXZpZXcgb2YgZHJhZnQtaWV0Zi1pMnJzLXlh
bmctbDMtdG9wb2xvZ3ktMTANCg0KUmV2aWV3ZXI6IENocmlzdGlhbiBIb3Bwcw0KUmV2aWV3IHJl
c3VsdDogSGFzIE5pdHMNCg0KSGVsbG8sDQoNCkkgaGF2ZSBiZWVuIHNlbGVjdGVkIHRvIGRvIGEg
cm91dGluZyBkaXJlY3RvcmF0ZSDigJxlYXJseeKAnSByZXZpZXcgb2YgdGhpcyBkcmFmdC4NCg0K
ICBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLWkycnMteWFuZy1s
My10b3BvbG9neS8NCg0KVGhlIHB1cnBvc2Ugb2YgdGhpcyByZXZpZXcgaXMgdG8gZGV0ZXJtaW5l
IGl0J3MgY29tcGF0aWJpbGl0eSB3aXRoIHRoZSBuZXcgcmV2aXNlZCBkYXRhc3RvcmUgbW9kZWwg
Z3VpZGVsaW5lcy4NCg0KRm9yIG1vcmUgaW5mb3JtYXRpb24gYWJvdXQgdGhlIFJvdXRpbmcgRGly
ZWN0b3JhdGUsIHBsZWFzZSBzZWUg4oCLaHR0cDovL3RyYWMudG9vbHMuaWV0Zi5vcmcvYXJlYS9y
dGcvdHJhYy93aWtpL1J0Z0Rpcg0KDQpEb2N1bWVudDogZHJhZnQtaWV0Zi1pMnJzLXlhbmctbDMt
dG9wb2xvZ3ktMTAudHh0DQpSZXZpZXdlcjogQ2hyaXN0aWFuIEhvcHBzDQpSZXZpZXcgRGF0ZTog
SnVseSA4LCAyMDE3DQpJbnRlbmRlZCBTdGF0dXM6IFN0YW5kYXJkcyBUcmFjaw0KDQpTdW1tYXJ5
Og0KDQotIFRoaXMgZG9jdW1lbnQgaXMgYmFzaWNhbGx5IHJlYWR5IGZvciBwdWJsaWNhdGlvbiwg
YnV0IGhhcyBuaXRzIHRoYXQgc2hvdWxkIGJlDQogIGNvbnNpZGVyZWQgcHJpb3IgdG8gYmVpbmcg
c3VibWl0dGVkIHRvIHRoZSBJRVNHLg0KDQpDb21tZW50czoNCg0KLSBUaGlzIGRvY3VtZW50IGFk
YXB0cyB0aGUgc3VnZ2VzdGVkIE5NREEgZ3VpZGVsaW5lcyBxdWl0ZSBuaWNlbHkuDQoNCi0gUGVy
aGFwcyBhbiBpbmZvcm1hdGl2ZSByZWZlcmVuY2UgdG8gdGhlIE5NREEgZ3VpZGVsaW5lcyBkcmFm
dCB3b3VsZCBiZSB1c2VmdWwuDQoNCi0gQXBwZW5kaXggQTogU2Vjb25kIFBhcmFncmFwaCwgbGFz
dCBzZW50ZW5jZToNCiAgLSBJIGJlbGlldmUgdGhhdCBpdCBzaG91bGQgc2F5Og0KDQogICAgICAi
aW5zdGVhZCBvZiBpZXRmLW5ldHdvcmsgYW5kIGlldGYtbmV0d29yay10b3BvbG9neSINCg0KICAg
IGl0IGN1cnJlbnRseSBzYXlzOg0KDQogICAgICAiaW5zdGVhZCBvZiBpZXRmLW5ldHdvcmsgYW5k
IGlldGYtbmV0d29yay1zdGF0ZSINCg0KLSBJUy1JUyBleGFtcGxlIG1vZGVsIChzb3JyeSBjb3Vs
ZG4ndCBoZWxwIG15c2VsZiA6KQ0KDQogIC0gVGhlIGV4YW1wbGUgSVMtSVMgbDMtbm9kZS1hdHRy
aWJ1dGVzIGF1Z21lbnRhdGlvbiBpc2lzLW5vZGUtYXR0cmlidXRlcw0KICAgIGluY2x1ZGVzIGFu
ICJpc28tcHNldWRvbm9kZS1pZCIuIFRoaXMgaXNuJ3QgYSBub2RlIGF0dHJpYnV0ZSwgYnV0IHJh
dGhlciBhDQogICAgbGluayBvbmUgKGl0IGlzIHJlcGVhdGVkIGxhdGVyIHVuZGVyIGxpbmsgYXR0
cmlidXRlcykuDQoNCiAgLSBUaGUgaXNpcy13ZyBzdWdnZXN0cyB0byB1c2UgIklTLUlTIiBjb25z
aXN0ZW50bHksIHdoZXJlIHBvc3NpYmxlLCBpbg0KICAgIGRvY3VtZW50cyByYXRoZXIgdGhhbiAi
aXNpcyIgb3IgIklTSVMiLg0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fDQppMnJzIG1haWxpbmcgbGlzdA0KaTJyc0BpZXRmLm9yZw0KaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pMnJzDQo=


From nobody Mon Jul 10 14:49:41 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE8341318FA for <ietf@ietfa.amsl.com>; Mon, 10 Jul 2017 14:49:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 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, 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 D4ydkj81jjzo for <ietf@ietfa.amsl.com>; Mon, 10 Jul 2017 14:49:38 -0700 (PDT)
Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (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 A6DBF1318F7 for <ietf@ietf.org>; Mon, 10 Jul 2017 14:49:37 -0700 (PDT)
Received: by mail-lf0-x22c.google.com with SMTP id t72so71886130lff.1 for <ietf@ietf.org>; Mon, 10 Jul 2017 14:49:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=9Y38xwyFU5RdIRxwteR5bTYl7sU+K7KmfOxwC5dyneo=; b=E6/i884IZp3kXhzKgwZh1yDNsCLSZt2zBOWD5yaxw99XGUykI2ZcuiwwrhWP9uWi3L bnwrMq16KDvH+DAzSVm5yK5Hzv7R5H9n94Zz+vggWJDvFdHQJt9WKphWgrrC1hIzzsbi 9VBJ/CVmu0ionED7KQE1BssUWJkZICCiOmCbwD8tfwhKaV51gafGeN7m8+3/ve5Z8Xpp Iqx0IcwIxQQFukRiLFRs+jQ4vTcPbpUiRj6G2bNk5kqsFLPLXlabMcgwjgeW9IAAAQx4 UsiUlsGBIh/R87qfimmLuq3g72YckyP74nEPe3mQj8XiZwuiEA0+Q6yr0hYbaGJlyQbJ O8ig==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=9Y38xwyFU5RdIRxwteR5bTYl7sU+K7KmfOxwC5dyneo=; b=JRGeDx5Ta7k8SuWQZ+anVVAxRxWIoKd6SlhkKW39R2hClnPqJZ+VUzpwEpMjbHNa9+ TckmP+s9HdjaKY7KbIchKIDOmXDc15ezGqtbXE5Szeb5wwk/aIDTPYdjlqHxPoohSmmz Jnp3bPE0UO/xoAnizokRTL5Lvz2vEIeuGTqVcFp3GyqGrkyzH8SYITmLZItMAlmrRMhY v7hZ74+/3pT2woueDJ25xaLxz8Hldyj6VS11tk+PYSSCTBRYSRLb494j7gI7A9DPYgzC yFWWKAwm0v0YCLipUpwL+ons25J+bsssILV6ky9rHEkU/fedlwVG/ywrcEnyx8EzNlJE 32Lw==
X-Gm-Message-State: AIVw113qkzKTMwFCHd8xjtInJPitTZXH866HCRex/X7G5z3+CoYDZHbL iO7Lk8gNFlXrK9+Gcw0UqEbhB52qzQ==
X-Received: by 10.46.80.77 with SMTP id v13mr4935777ljd.129.1499723375954; Mon, 10 Jul 2017 14:49:35 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.25.181.214 with HTTP; Mon, 10 Jul 2017 14:49:34 -0700 (PDT)
In-Reply-To: <20170710172222.94206.qmail@ary.lan>
References: <20170710011426.3BE867E1FE36@rock.dv.isc.org> <20170710172222.94206.qmail@ary.lan>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Mon, 10 Jul 2017 17:49:34 -0400
X-Google-Sender-Auth: lRUwi0Gpb5zFOJxNmuLR3yNF_OY
Message-ID: <CAMm+LwiimZH3nHuJ5YVuny5HLU7PBi4ehtxKA7BwN6=EpbviDg@mail.gmail.com>
Subject: Re: new DNS classes
To: John Levine <johnl@taugh.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="f403045fbd0c15cf890553fd8f03"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pIuInFBJBApygA9YOcFjumZV1eU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jul 2017 21:49:40 -0000

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

On Mon, Jul 10, 2017 at 1:22 PM, John Levine <johnl@taugh.com> wrote:

> In article <20170710011426.3BE867E1FE36@rock.dv.isc.org> you write:
> >b) For DNS tools to add support for allocated data types within X
> >   months of them being assigned by IANA.  Allocated types are
> >   supposed to have stable wire and presentation formats.
>
> I think we can agree that we all want a pony.
>

=E2=80=8BThat mis-states the argument. Someone made a factual claim that de=
ployment
of new RRs was not hard. Others repudiated that claim. Instead of
retracting the statement, the argument changed to how easy it would be to
fix it.
=E2=80=8B

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Ju=
l 10, 2017 at 1:22 PM, John Levine <span dir=3D"ltr">&lt;<a href=3D"mailto:=
johnl@taugh.com" target=3D"_blank">johnl@taugh.com</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex"><span class=3D"">In article &lt;<a href=3D"=
mailto:20170710011426.3BE867E1FE36@rock.dv.isc.org">20170710011426.3BE867E1=
FE36@<wbr>rock.dv.isc.org</a>&gt; you write:<br>
&gt;b) For DNS tools to add support for allocated data types within X<br>
&gt;=C2=A0 =C2=A0months of them being assigned by IANA.=C2=A0 Allocated typ=
es are<br>
&gt;=C2=A0 =C2=A0supposed to have stable wire and presentation formats.<br>
<br>
</span>I think we can agree that we all want a pony.<br></blockquote><div><=
br></div><div><div class=3D"gmail_default" style=3D"font-size:small">=E2=80=
=8BThat mis-states the argument. Someone made a factual claim that deployme=
nt of new RRs was not hard. Others repudiated that claim. Instead of retrac=
ting the statement, the argument changed to how easy it would be to fix it.=
</div><div class=3D"gmail_default" style=3D"font-size:small">=E2=80=8B<br><=
/div><br></div><div>=C2=A0</div></div></div></div>

--f403045fbd0c15cf890553fd8f03--


From nobody Mon Jul 10 15:15:39 2017
Return-Path: <vijay.gurbani@nokia.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 44A7512F27C; Mon, 10 Jul 2017 15:15:31 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Vijay Gurbani <vijay.gurbani@nokia.com>
To: <gen-art@ietf.org>
Cc: ietf@ietf.org, draft-turner-est-extensions.all@ietf.org
Subject: Genart telechat review of draft-turner-est-extensions-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149972493112.12836.11322162271657108676@ietfa.amsl.com>
Date: Mon, 10 Jul 2017 15:15:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WBVdIZUjJ4uq-ejYcXdpEoDrilA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jul 2017 22:15:31 -0000

Reviewer: Vijay Gurbani
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-turner-est-extensions-??
Reviewer: Vijay Gurbani
Review Date: 2017-07-10
IETF LC End Date: 2017-07-11
IESG Telechat date: Not scheduled for a telechat

Summary: Ready with nits.

Major issues: 0

Minor issues: 1

Nits/editorial comments: 2

Minor:
- S2, I understand that a PAL may be represented as a XML file or a JSON
 object, but I note that the underlying semantic content of the resource,
 irrespective of representation as shown in Sections 2.1.2 and 2.1.3 is
 different.  I suspect that is by design, but could not figure out why the
 XML and JSON resource would have different semantic content.

Nits:
- S1, top of page 5: What is TA?  The expansion is not defined before being
 used here for the first time; I suspect it is "Trust Anchor", but may help
 to expand it here rather than in S7.

- S1.1, "air gap" --- I understand what it means from rfc4949, but someone
 not familiar (or too lazy to look up rfc4949 or simply much too younger than
 us) may assume that "air gap" refers to "wifi".  Admittedly in 2007 when
 rfc4949 was written, 802.11{g,e,n} were just released [1], and only three
 years before, in 2004, Economist predicted that the worldwide market for WiFi
 devices in 2006 will be 50 million (!) [2].

 I don't know that we can do much here, but it was with some chuckle that
 the term "air gap" lead me to the statistics I mention above.

[1] http://www.ucopia.com/en/news/history-of-wi-fi/
[2] http://www.economist.com/node/2724397




From nobody Mon Jul 10 17:17:23 2017
Return-Path: <michelle.cotton@iana.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7575612EC30 for <ietf@ietfa.amsl.com>; Mon, 10 Jul 2017 17:17:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.189
X-Spam-Level: 
X-Spam-Status: No, score=-4.189 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=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 baM8zxcT81dM for <ietf@ietfa.amsl.com>; Mon, 10 Jul 2017 17:17:19 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-1.pexch112.icann.org [64.78.40.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C986812EC19 for <ietf@ietf.org>; Mon, 10 Jul 2017 17:17:19 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Mon, 10 Jul 2017 17:17:17 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1178.000; Mon, 10 Jul 2017 17:17:17 -0700
From: Michelle Cotton <michelle.cotton@iana.org>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Reminder: IANA Services Focus Groups
Thread-Topic: Reminder: IANA Services Focus Groups
Thread-Index: AQHS+dsNiz+cBcT5sUqZmyGnesy3hw==
Date: Tue, 11 Jul 2017 00:17:16 +0000
Message-ID: <406B73E9-63B5-4E19-B6AA-DFBA0D09EAE4@iana.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.23.0.170610
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha256; boundary="B_3582551836_1290091703"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Nh45HFHy1ywtzVLqz-1OhZAWCrA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jul 2017 00:17:21 -0000

--B_3582551836_1290091703
Content-type: multipart/alternative;
	boundary="B_3582551835_1254613254"


--B_3582551835_1254613254
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

Reminder:=C2=A0 If anyone is interested in volunteering, please see below for i=
nstructions.=C2=A0 Please reply as soon as possible so that we can work on sched=
uling time with you.

=20

Thanks!=C2=A0 See you in Prague.

=20

Michelle Cotton

Protocol Parameters Engagement Manager

IANA Services

ICANN/PTI

=20

=20

From: Michelle Cotton <michelle.cotton@iana.org>
Date: Tuesday, June 27, 2017 at 10:48 AM
To: <ietf@ietf.org>
Subject: IANA Services Focus Groups

=20

Attention IETF Participants:

    =20

During the upcoming Prague IETF, we are looking for volunteers to meet with=
 the IANA Services team to discuss user experience with the use of protocol =
parameter registries. We are looking for a broad cross-section of users, fro=
m those who are heavily involved in the IETF and IANA Services processes, to=
 newcomers who have had limited experience.

=20

We would like to either meet one-on-one or in small groups to get different=
 perspectives.  Some of the topics we will cover include:

    -Submitting requests for protocol parameter registrations

    -Website/Registry usage and navigation

    -Feedback on I-D reviews

    -Expert review interactions

=20

If you are interested in meeting with us, please send an email to iana@iana=
.org with =E2=80=9CIETF-99 Focus Groups=E2=80=9D in the subject line.

Please include your contact information and what type of user you are of IA=
NA Services (template provided below).  We cannot guarantee meeting with eve=
ryone, but we will do our best to work around the meetings schedule to find =
time.  Meetings will take place at the IANA Services Office Hours desk or ot=
her room TBD.  We will contact you regarding specific meeting day/times.  We=
 will be scheduling meetings based on the responses/interest we receive.

=20

Please DO NOT reply to this email.

=20

Thank you and we look forward to seeing you in Prague.

=20

Michelle Cotton

Protocol Parameters Engagement Manager

IANA Services

ICANN/PTI

=20

Copy and paste template:=20

=20

Subject: IETF-99 Focus Groups

=20

Name:

Email:

=20

Focus area for feedback:

(describe areas here where you have experience and specific feedback if you=
 like. Examples: Do you submit registration requests? Do you review the prot=
ocol parameter registries? Are you a document author? Are you an IESG design=
ated Expert? Do you submit early allocation requests for your working group?=
  ETC.)

=20

Availability:=20

Monday-Thursday

When are you available?  What meeting timeslots might you be available to m=
eet?

See agenda at: https://datatracker.ietf.org/meeting/99/agenda.html

=20

=20

=20

=20

=20

=20

=20

    =20

=20

=20


--B_3582551835_1254613254
Content-type: text/html;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:schema=
s-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/office/20=
04/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DTitle c=
ontent=3D""><meta name=3DKeywords content=3D""><meta http-equiv=3DContent-Type conte=
nt=3D"text/html; charset=3Dutf-8"><meta name=3DGenerator content=3D"Microsoft Word 1=
5 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Arial;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:DengXian;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:12.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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.msoIns
	{mso-style-type:export-only;
	mso-style-name:"";
	text-decoration:underline;
	color:teal;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style></head><body bgcolor=3Dwhite lang=3DEN-US link=3D"#0563C1" vlink=3D"#954=
F72"><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'font-size:11.0p=
t'>Reminder:=C2=A0 If anyone is interested in volunteering, please see below for=
 instructions.=C2=A0 Please reply as soon as possible so that we can work on sch=
eduling time with you.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'=
font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt'>Thanks!=C2=A0 See you in Prague.<o:p></o:p></span></p><p cla=
ss=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p c=
lass=3DMsoNormal><span lang=3Dfr style=3D'font-size:11.0pt'>Michelle Cotton<o:p></=
o:p></span></p><p class=3DMsoNormal><span lang=3DFR style=3D'font-size:11.0pt'>Pro=
tocol Parameters Engagement Manager</span><span lang=3Dfr style=3D'font-size:11.=
0pt'><o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DFR style=3D'font-size=
:11.0pt'>IANA Services</span><span style=3D'font-size:11.0pt'><o:p></o:p></spa=
n></p><p class=3DMsoNormal><span lang=3DFR style=3D'font-size:11.0pt'>ICANN/PTI</s=
pan><span style=3D'font-size:11.0pt'><o:p></o:p></span></p><p class=3DMsoNormal>=
<span style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNorma=
l><span style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><div style=3D'bor=
der:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3D=
MsoNormal><b><span style=3D'color:black'>From: </span></b><span style=3D'color:b=
lack'>Michelle Cotton &lt;michelle.cotton@iana.org&gt;<br><b>Date: </b>Tuesd=
ay, June 27, 2017 at 10:48 AM<br><b>To: </b>&lt;ietf@ietf.org&gt;<br><b>Subj=
ect: </b>IANA Services Focus Groups<o:p></o:p></span></p></div><div><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p></div>=
<p class=3DMsoNormal><span style=3D'font-size:11.0pt'>Attention IETF Participant=
s:</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span s=
tyle=3D'font-size:11.0pt'>During the upcoming Prague IETF, we are looking for =
volunteers to meet with the IANA Services team to discuss user experience wi=
th the use of protocol parameter registries.&nbsp;We are looking for a broad=
 cross-section of users, from those who are heavily involved in the IETF and=
 IANA Services processes, to newcomers who have had limited experience.</spa=
n><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>&nbsp;</s=
pan><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>We woul=
d like to either meet one-on-one or in small groups to get different perspec=
tives.&nbsp; Some of the topics we will cover include:</span><o:p></o:p></p>=
<p class=3DMsoNormal><span style=3D'font-size:11.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;-S=
ubmitting requests for protocol parameter registrations</span><o:p></o:p></p=
><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;-=
Website/Registry usage and navigation</span><o:p></o:p></p><p class=3DMsoNorma=
l><span style=3D'font-size:11.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;-Feedback on I-D re=
views</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'=
>&nbsp;&nbsp;&nbsp; -Expert review interactions</span><o:p></o:p></p><p clas=
s=3DMsoNormal><span style=3D'font-size:11.0pt'>&nbsp;</span><o:p></o:p></p><p cl=
ass=3DMsoNormal><span style=3D'font-size:11.0pt'>If you are interested in meetin=
g with us, please send an email to <a href=3D"mailto:iana@iana.org">iana@iana.=
org</a> with =E2=80=9CIETF-99 Focus Groups=E2=80=9D in the subject line.</span><o:p></o:=
p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>Please include your =
contact information and what type of user you are of IANA Services (template=
 provided below).&nbsp; We cannot guarantee meeting with everyone, but we wi=
ll do our best to work around the meetings schedule to find time.&nbsp; Meet=
ings will take place at the IANA Services Office Hours desk or other room TB=
D.&nbsp; We will contact you regarding specific meeting day/times.&nbsp; We =
will be scheduling meetings based on the responses/interest we receive.</spa=
n><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>&nbsp;</s=
pan><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>Please =
DO NOT reply to this email.</span><o:p></o:p></p><p class=3DMsoNormal><span st=
yle=3D'font-size:11.0pt'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt'>Thank you and we look forward to seeing you in Prag=
ue.</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>&=
nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span lang=3DFR style=3D'font-size=
:11.0pt'>Michelle Cotton</span><o:p></o:p></p><p class=3DMsoNormal><span lang=3D=
FR style=3D'font-size:11.0pt'>Protocol Parameters Engagement Manager</span><o:=
p></o:p></p><p class=3DMsoNormal><span lang=3DFR style=3D'font-size:11.0pt'>IANA S=
ervices</span><o:p></o:p></p><p class=3DMsoNormal><span lang=3DFR style=3D'font-si=
ze:11.0pt'>ICANN/PTI</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'fo=
nt-size:11.0pt'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'=
font-size:11.0pt'>Copy and paste template: </span><o:p></o:p></p><p class=3DMs=
oNormal><span style=3D'font-size:11.0pt'>&nbsp;</span><o:p></o:p></p><p class=3D=
MsoNormal><span style=3D'font-size:11.0pt'>Subject: IETF-99 Focus Groups</span=
><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>&nbsp;</sp=
an><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>Name:</s=
pan><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>Email:<=
/span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>&nbsp=
;</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>Foc=
us area for feedback:</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt'>(describe areas here where you have experience and specific=
 feedback if you like. Examples: Do you submit registration requests? Do you=
 review the protocol parameter registries? Are you a document author? Are yo=
u an IESG designated Expert? Do you submit early allocation requests for you=
r working group? &nbsp;ETC.)</span><o:p></o:p></p><p class=3DMsoNormal><span s=
tyle=3D'font-size:11.0pt'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span=
 style=3D'font-size:11.0pt'>Availability: </span><o:p></o:p></p><p class=3DMsoNo=
rmal><span style=3D'font-size:11.0pt'>Monday-Thursday</span><o:p></o:p></p><p =
class=3DMsoNormal><span style=3D'font-size:11.0pt'>When are you available?&nbsp;=
 What meeting timeslots might you be available to meet?</span><o:p></o:p></p=
><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>See agenda at:</span> <sp=
an style=3D'font-size:11.0pt'><a href=3D"https://datatracker.ietf.org/meeting/99=
/agenda.html">https://datatracker.ietf.org/meeting/99/agenda.html</a></span>=
<o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>&nbsp;</s=
pan><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>&nbsp;<=
/span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>&nbsp=
;</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>&nb=
sp;</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>&=
nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'=
>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:11.0p=
t'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><s=
pan style=3D'font-size:11.0pt'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal>=
<span style=3D'font-size:11.0pt'>&nbsp;</span><o:p></o:p></p></div></body></ht=
ml>

--B_3582551835_1254613254--

--B_3582551836_1290091703
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIISBAYJKoZIhvcNAQcCoIIR9TCCEfECAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0B
BwGggg+5MIIFqDCCBJCgAwIBAgIQCuvDwxHaHKymSygUiz0IATANBgkqhkiG9w0BAQsFADBl
MQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGln
aWNlcnQuY29tMSQwIgYDVQQDExtEaWdpQ2VydCBTSEEyIEFzc3VyZWQgSUQgQ0EwHhcNMTYx
MDAzMDAwMDAwWhcNMTkxMDAzMTIwMDAwWjCBxTELMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNh
bGlmb3JuaWExFDASBgNVBAcTC0xvcyBBbmdlbGVzMTwwOgYDVQQKEzNJbnRlcm5ldCBDb3Jw
b3JhdGlvbiBmb3IgQXNzaWduZWQgTmFtZXMgYW5kIE51bWJlcnMxJDAiBgNVBAMTG01pY2hl
bGxlIENvdHRvbiBJQU5BIDNPY3QxNjEnMCUGCSqGSIb3DQEJARYYbWljaGVsbGUuY290dG9u
QGlhbmEub3JnMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA6V4aMB8RQMy4vQOd
nvINsoYARWq26DERE228XVCA7SxnxpHKRAgnpV4iBoL5rgjsiJy5utpRlbCZcV7PVaVp6yxM
ozNUSzmiSu+O04PyYWjvJRzSLda6W0hc8B766JDK3V8QVX+5Pnt9E2JxyYL6j5zTrD/kZGTB
XpaRNBF5DorhvPEwXNuRyWt5yD3m4vMwinCahC+5DB78PlxvbbEgTLenW8ZnSOunflX11Q8W
XkYBAHEWLSDEO8MY4t7b7FBTWoDA6arnmiJApfBm+tfJ9VPto6KX1YWWuUMrmg7PVF6jfiuW
ncwVZzed6VBW9Sp1oVKWP3GXraq0glyTutf5MQIDAQABo4IB8TCCAe0wHwYDVR0jBBgwFoAU
5wIjgABP2Ne8lAvZP3Q5STI8inkwHQYDVR0OBBYEFD4OJSm8pR0KSROJ2Te94XiGhEJAMAwG
A1UdEwEB/wQCMAAwIwYDVR0RBBwwGoEYbWljaGVsbGUuY290dG9uQGlhbmEub3JnMA4GA1Ud
DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwQwYDVR0gBDwwOjA4
BgpghkgBhv1sBAECMCowKAYIKwYBBQUHAgEWHGh0dHBzOi8vd3d3LmRpZ2ljZXJ0LmNvbS9D
UFMwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY3JsMy5kaWdpY2VydC5jb20vRGlnaUNl
cnRTSEEyQXNzdXJlZElEQ0EtZzIuY3JsMD2gO6A5hjdodHRwOi8vY3JsNC5kaWdpY2VydC5j
b20vRGlnaUNlcnRTSEEyQXNzdXJlZElEQ0EtZzIuY3JsMHkGCCsGAQUFBwEBBG0wazAkBggr
BgEFBQcwAYYYaHR0cDovL29jc3AuZGlnaWNlcnQuY29tMEMGCCsGAQUFBzAChjdodHRwOi8v
Y2FjZXJ0cy5kaWdpY2VydC5jb20vRGlnaUNlcnRTSEEyQXNzdXJlZElEQ0EuY3J0MA0GCSqG
SIb3DQEBCwUAA4IBAQCFn08dbc9474OYmBeeFe4I08uzdP/Glg78Au1o7+IhufO+BN/fqn31
VhE7Q2aYCh28LF99PbdJ2IOBsz+BUGlrz7C0UvrHjmbXBTuR/gHez2Hmk6SOu0o4anLJqVFl
xMzQtpBQXWM0K8GlyqDlPtiWQDORtUsMOXnL2+smNqb5xoz1SyK30KEMMeq9ZndDuBpM1Gyh
7JdgiLypKnYfRc1c1INCWiDlvpTA+C60BZSv5e/k1GMW0USd7TZTzphQxKmLNRUXUxRjub3H
Yiby5y1hTnUyalL6HHbYVJX8bOgmaaOAjLvsJzX0rHRaMYlFbC4CgNlQNExJd4Xt7c39ghay
MIIGTjCCBTagAwIBAgIQBK55YGZmkBq5xX+mbFvczTANBgkqhkiG9w0BAQsFADBlMQswCQYD
VQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGlnaWNlcnQu
Y29tMSQwIgYDVQQDExtEaWdpQ2VydCBBc3N1cmVkIElEIFJvb3QgQ0EwHhcNMTMxMTA1MTIw
MDAwWhcNMjgxMTA1MTIwMDAwWjBlMQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQg
SW5jMRkwFwYDVQQLExB3d3cuZGlnaWNlcnQuY29tMSQwIgYDVQQDExtEaWdpQ2VydCBTSEEy
IEFzc3VyZWQgSUQgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDc+BEjP2q1
78AneRstBYeiEEMx3w7UFRtPd6Qizj6McPC+B47dJyq8AR22LArK3WlYH0HtagUf2mN4WR4i
LCv4un7JNTtW8R98Qn4lsCMZxkU41z1E+SB8YK4csFoYBL6PO/ep8JSapgxjSbZBF1NAMr1P
5lB6UB8lRejxia/N/17/UPPwFxH/vcWJ9b1iudj7jkUEhW2ZzcVITf0mqwI2Reo2119q4hqC
QQrc6dn1kReOxiGtODwT5h5/ZpzVTdlG2vbPUqd9OyTDtMFRNcab69TvfuR7A+FEvXoLN+BP
y4KKDXEY5KbgiSwb87JzPMGwkp4Yfb2rfcV9CKEswp9zAgMBAAGjggL4MIIC9DASBgNVHRMB
Af8ECDAGAQH/AgEAMA4GA1UdDwEB/wQEAwIBhjA0BggrBgEFBQcBAQQoMCYwJAYIKwYBBQUH
MAGGGGh0dHA6Ly9vY3NwLmRpZ2ljZXJ0LmNvbTCBgQYDVR0fBHoweDA6oDigNoY0aHR0cDov
L2NybDQuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0QXNzdXJlZElEUm9vdENBLmNybDA6oDigNoY0
aHR0cDovL2NybDMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0QXNzdXJlZElEUm9vdENBLmNybDAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwggGzBgNVHSAEggGqMIIBpjCCAaIGCmCG
SAGG/WwAAgQwggGSMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy5kaWdpY2VydC5jb20vQ1BT
MIIBZAYIKwYBBQUHAgIwggFWHoIBUgBBAG4AeQAgAHUAcwBlACAAbwBmACAAdABoAGkAcwAg
AEMAZQByAHQAaQBmAGkAYwBhAHQAZQAgAGMAbwBuAHMAdABpAHQAdQB0AGUAcwAgAGEAYwBj
AGUAcAB0AGEAbgBjAGUAIABvAGYAIAB0AGgAZQAgAEQAaQBnAGkAQwBlAHIAdAAgAEMAUAAv
AEMAUABTACAAYQBuAGQAIAB0AGgAZQAgAFIAZQBsAHkAaQBuAGcAIABQAGEAcgB0AHkAIABB
AGcAcgBlAGUAbQBlAG4AdAAgAHcAaABpAGMAaAAgAGwAaQBtAGkAdAAgAGwAaQBhAGIAaQBs
AGkAdAB5ACAAYQBuAGQAIABhAHIAZQAgAGkAbgBjAG8AcgBwAG8AcgBhAHQAZQBkACAAaABl
AHIAZQBpAG4AIABiAHkAIAByAGUAZgBlAHIAZQBuAGMAZQAuMB0GA1UdDgQWBBTnAiOAAE/Y
17yUC9k/dDlJMjyKeTAfBgNVHSMEGDAWgBRF66Kv9JLLgjEtUYunpyGd823IDzANBgkqhkiG
9w0BAQsFAAOCAQEATtSJJ7n9HYd3fg8oBZDxCi/JOz69k5yQxq/6kVGHMlRr6MrBcVFcmY61
+uBiGZmmB5p8Eyfb5QKihBLZFfYKRFfENI9tcx861qABPd7jguRFa7LrJf2AXh05kL5bQvbO
kWDj+aBWDEgQzjNoe82Tq/Bqy09YD7l7XRsEgZ6nIuJXSSfukpMIvmkIUwI6Ll3IGfRQgE4C
2bBdkbSTh/mWloFVQI5m7YLYuyhf7Uxh7QZYKBlTEUS8RyApsgRs2IlUmTt122d4LB6SeMZV
PVgSETJuvUMMTTTbe8ZC2+y+q5thTAaS447fISpQVwTAYKI11SSeZjcJSc/V+GWz4OJuwjCC
A7cwggKfoAMCAQICEAzn4OUX2Eb+j+Vg/BvwMDkwDQYJKoZIhvcNAQEFBQAwZTELMAkGA1UE
BhMCVVMxFTATBgNVBAoTDERpZ2lDZXJ0IEluYzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNv
bTEkMCIGA1UEAxMbRGlnaUNlcnQgQXNzdXJlZCBJRCBSb290IENBMB4XDTA2MTExMDAwMDAw
MFoXDTMxMTExMDAwMDAwMFowZTELMAkGA1UEBhMCVVMxFTATBgNVBAoTDERpZ2lDZXJ0IElu
YzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNvbTEkMCIGA1UEAxMbRGlnaUNlcnQgQXNzdXJl
ZCBJRCBSb290IENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArQ4VzuRDgFyx
h/O3YPlxEqWu3CaUiKr0zvUgOShYYAz4gNqpFZUyYTy1sSiEiorcnwoMgxd6j5Csiud5U1wx
hCr2D5gyNnbM3t08qKLvavsh8lJh358g1x/isdn+GGTSEltf+VgYNbxHzaE2+Wt/1LA4PsEb
w4wz2dgvGP4oD7Ong9bDbkTAYTWWFv5ZnIt2bdfxoksNK/8LctqeYNCOkDXGeFWHIKHP5W0K
yEl8MZgzbCLph9AyWqK6E4IR7TkXnZk6cqHm+qTZ1Rcxda6FfSKuPwFGhvYoecix2uRXF8R+
HA6wtJKmVrO9spftqqfwt8WoP5UW0P+hlusIXxh3TwIDAQABo2MwYTAOBgNVHQ8BAf8EBAMC
AYYwDwYDVR0TAQH/BAUwAwEB/zAdBgNVHQ4EFgQUReuir/SSy4IxLVGLp6chnfNtyA8wHwYD
VR0jBBgwFoAUReuir/SSy4IxLVGLp6chnfNtyA8wDQYJKoZIhvcNAQEFBQADggEBAKIOvN/i
7fDjcnN6ZJS/93Jm2DLkQnVirofr8tXZ3lazn8zOFCi5DZdgXBJMWOTTPYNJRViXNWkaqEfq
VsZ5qxLYZ4GE338JPJTmuCYsIL09syiJ91//IuKXhB/pZe+H4N/BZ0mzXeuyCSrrJu14vn0/
K/O3JjVtX4kBtklbnwEFm6s9JcHMtn/C8W+GxvpkaOuBLZTrQrf6jB7dYvG+UGe3bL3z8R9r
DDYHFn83fKlbbXrxEkZgg9cnBL5Lzpe+w2cqaBHfgOcMM2a/Ew0UbvN/H2MQHvqNGyVtbI+l
t2EBsdKjJqEQcZ2t4sP5w5lRtysHCM4u5lCyp/oKRS+i8PIxggIPMIICCwIBATB5MGUxCzAJ
BgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2Vy
dC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IFNIQTIgQXNzdXJlZCBJRCBDQQIQCuvDwxHaHKym
SygUiz0IATANBglghkgBZQMEAgEFAKBpMC8GCSqGSIb3DQEJBDEiBCB48+pYJARVGyaeuGp2
qtpuQks9A85NmtWC9gHIiDT/4TAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0xNzA3MTEwMDE3MTVaMA0GCSqGSIb3DQEBAQUABIIBAOSv/EIh3pc9Xi0I8uM7
mTMZ42+2/vU7aU1GyjSQSJwuheMbPZzL/f+5cK93hjPtMwwo1ZDVTyEvKmtQIi4oPzq5HC+M
vrfWvUs4/m5DTi3oIQwdig8B2lOmHrw2ZJgn2fSpSkwS0bOMX2FpbqQ8gDOJCYE6MDlSENtK
ZYiXdqVMcVWkAu6eDhi2hKQX3YyDFCtImdBrusnz/6WJDse5UU+TsZ8nIO338oMDH88ID9ga
4o+f1f7Fi480ddxyD2SZubkhl4d/2w0wBM7tVijEN0h4o7iYlX5mrInVP/VttFPllz21lmsh
O8D8nNl//hmc1K/iJd/VKYbmGPUAg+yP3sQ=

--B_3582551836_1290091703--


From nobody Tue Jul 11 11:42:04 2017
Return-Path: <eckelcu@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B806B13179B; Tue, 11 Jul 2017 11:42:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 R0X7cjz_40Qa; Tue, 11 Jul 2017 11:42:02 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCD43131798; Tue, 11 Jul 2017 11:42:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=322; q=dns/txt; s=iport; t=1499798521; x=1501008121; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=WJ0y59+FeGFUdZVCfCpPoTMaPVmiwaTdOSXQM78Kl+Y=; b=Vu0hIMSSKJnsmwh/n2y/Mu8wrLB5hIDxHUI3JeWyO8PwgeganpuA8nek zReCfRj+ecN9WKLpNBwvJu4NckZ0J8W1ytLYiCA7VvZnNw/Om2aSy1yAZ fc+GG6Txrj3GMiEwEJc+26Ao1QtUWMQalqfMGyw2ZijLrI4oeTmXUz8/e 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BbAwA3G2VZ/5JdJa1dGwEBAQMBAQEJA?= =?us-ascii?q?QEBg1qBf59PmDaFdhyDJEIVAQIBAQEBAQEBax0LhUIRRRIBIgImAgQwFRIEDh+?= =?us-ascii?q?KFawHgiaLIgEBAQEBAQEBAQEBAQEBAQEBAQEBAR2BC4IdhVkLimswgjEFnyQCl?= =?us-ascii?q?AqBdAGQMJVGATUigQp1FVsBhwOIF4ENAQEB?=
X-IronPort-AV: E=Sophos;i="5.40,347,1496102400"; d="scan'208";a="453893820"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Jul 2017 18:42:01 +0000
Received: from XCH-ALN-017.cisco.com (xch-aln-017.cisco.com [173.36.7.27]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id v6BIg1ZL006446 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 11 Jul 2017 18:42:01 GMT
Received: from xch-aln-018.cisco.com (173.36.7.28) by XCH-ALN-017.cisco.com (173.36.7.27) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 11 Jul 2017 13:42:00 -0500
Received: from xch-aln-018.cisco.com ([173.36.7.28]) by XCH-ALN-018.cisco.com ([173.36.7.28]) with mapi id 15.00.1210.000; Tue, 11 Jul 2017 13:42:00 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "hackathon@ietf.org" <hackathon@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: Hackathon Registration Closing at end of today
Thread-Topic: Hackathon Registration Closing at end of today
Thread-Index: AQHS+nVhGTVWalboN061ixi9yTHgNQ==
Date: Tue, 11 Jul 2017 18:42:00 +0000
Message-ID: <884CF365-66BD-4EBE-9938-A9F93ABEB978@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.22.0.170515
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.154.177.226]
Content-Type: text/plain; charset="utf-8"
Content-ID: <E8CCC6DAF6EA434995EA2B8C7E66E872@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SyiJ0ZN6meOCpr192oPhUpa8Lz4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jul 2017 18:42:03 -0000

VGhhbmtzIHRvIGFsbCBvZiB5b3Ugd2hvIGhhdmUgcmVnaXN0ZXJlZCBmb3IgdGhlIGhhY2thdGhv
bi4gDQpUaGUgZ29vZCBuZXdzIGlzIHdlIGhhdmUgYSByZWNvcmQgbnVtYmVyIG9mIHJlZ2lzdHJh
dGlvbnMuDQpUaGUgYmFkIG5ld3MgaXMsIHdlIGhhdmUgcnVuIG91dCBvZiBzcGFjZS4NClJlZ2lz
dHJhdGlvbiB3aWxsIGJlIGNsb3NlZCBhZnRlciB0b2RheS4NCg0KQ2hlZXJzLA0KQ2hhcmxlcw0K
DQoNCg==


From nobody Tue Jul 11 17:34:39 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 464A71316FC for <ietf@ietfa.amsl.com>; Tue, 11 Jul 2017 17:34:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 PFpHW030EkhW for <ietf@ietfa.amsl.com>; Tue, 11 Jul 2017 17:34:37 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 346E912EC2F for <ietf@ietf.org>; Tue, 11 Jul 2017 17:34:37 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dV5bv-0006Xd-Gx for ietf@ietf.org; Wed, 12 Jul 2017 00:34:35 +0000
Date: Wed, 12 Jul 2017 02:34:34 +0200
Message-ID: <m2eftmwl0l.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Rinse Repeat <ietf@ietf.org>
Subject: meeting ietf-legacy ssid
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/I9eW0gChX-jqIPBrsrDzEuVPQNg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 00:34:38 -0000

the noc sees a quite large number of associations to the unencrypted
ietf-legacy ssid as opposed to say the encrypted ietf ssid

some of us are wondering if those using ietf-legacy

  o do not realize it is completely unencrypted over the air, or

  o don't care as their threat model sees runnin' nekkid over the air as
    not a significant additional weakness, or

  o believe that they are using sufficient encryption at higher layers
    to meet their needs, or

  o other

these days, some meetings do not provide unencrypted wifi at all and
seem not to get complaints.  maybe their attendees are just geekier
and/or more security conscious.

clue bat, please.  unicast responses accepted too.

randy


From nobody Tue Jul 11 17:43:07 2017
Return-Path: <paul@nohats.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D611B13182C for <ietf@ietfa.amsl.com>; Tue, 11 Jul 2017 17:42: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, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 ntKdeI0OCAkN for <ietf@ietfa.amsl.com>; Tue, 11 Jul 2017 17:42:57 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (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 1437213182B for <ietf@ietf.org>; Tue, 11 Jul 2017 17:42:57 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3x6gCf4bwHz1jf; Wed, 12 Jul 2017 02:42:54 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1499820174; bh=ZeGw2DRLDodpvMd5t2jFvxc6yyWVGC8KccAHS0Xm2jM=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=Ug6mchK2aaaGP2Md6YxPETOdGTbdoijJLDsClUX/bxeYTM42T6xDo1J42LxcAHO7K cMM4O2ySHblAszQg+/KrKLmCkgdXj2GbmDYvdOgyJMPkth3UCbntmldetcLiSbnggH fV8GPKo1m2QlCzdH80QqQZCb0Evt1vFjDjX7BWlw=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id Al0grKE2Sd8c; Wed, 12 Jul 2017 02:42:53 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Wed, 12 Jul 2017 02:42:53 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 7300C908; Tue, 11 Jul 2017 20:42:52 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 7300C908
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 5AA9D40D3592; Tue, 11 Jul 2017 20:42:52 -0400 (EDT)
Date: Tue, 11 Jul 2017 20:42:52 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: Randy Bush <randy@psg.com>
cc: IETF <ietf@ietf.org>
Subject: Re: meeting ietf-legacy ssid
In-Reply-To: <m2eftmwl0l.wl-randy@psg.com>
Message-ID: <alpine.LRH.2.21.1707112040001.25538@bofh.nohats.ca>
References: <m2eftmwl0l.wl-randy@psg.com>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EIGS8pfVqISf15E9wetzyaWwjWk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 00:43:00 -0000

On Wed, 12 Jul 2017, Randy Bush wrote:

> some of us are wondering if those using ietf-legacy

>  o other

Why should I trust anyone at the IETF? The security is out of my control,
so it is as good as unencrypted to me.

And of course, if you can't not trust your friends, who can you not trust?

Paul


From nobody Tue Jul 11 17:59:59 2017
Return-Path: <prvs=1366b16ed2=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6544D127867 for <ietf@ietfa.amsl.com>; Tue, 11 Jul 2017 17:59:58 -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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
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 QDOcJMFquwTp for <ietf@ietfa.amsl.com>; Tue, 11 Jul 2017 17:59:56 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D161913182C for <ietf@ietf.org>; Tue, 11 Jul 2017 17:59:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1499821193; x=1500425993; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=tQSpxZRoGUYlTnmo0HGUj/KBb mINLUfjxIZ75CSphKQ=; b=gKwKEK1N45CRi5AoOg5kg8GtpFuyH/rJWrDGpaL2W XLPUUuCMnR2xn148Kyk8ZaScsCMcMzoEtzdvy1wlaZj9h3d4TLQ2MArVkmX8VLZM XbGE1ICLK8d/m5UdrOcYAshc8Gf54+m2/GUHtHAt8Dt5ihZguWmsHWRFqh66kYaY kY=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=XFXi7qv8x8ovGedZW2Rwby4Vzh7/gMV1FkgUyGThBCn5SGGzD6pqJm/az7vY TKwQ4ZsRg+1O8ISRdIqycpX4d4XzAuWI2x2LBprxxrh/auJ32PzNwh04W hQ8o87RgzxeX7jLA5UxPtlJdKMvccmpa87fWrSZE0EQqwmqDitYdMA=;
X-MDAV-Processed: mail.consulintel.es, Wed, 12 Jul 2017 02:59:53 +0200
X-Spam-Processed: mail.consulintel.es, Wed, 12 Jul 2017 02:59:53 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005472768.msg for <ietf@ietf.org>; Wed, 12 Jul 2017 02:59:53 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170712:md50005472768::KWe4kqSMyVcSYia+:000082Mz
X-Return-Path: prvs=1366b16ed2=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.21.0.170409
Date: Wed, 12 Jul 2017 02:59:51 +0200
Subject: Re: meeting ietf-legacy ssid
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IETF Rinse Repeat <ietf@ietf.org>
Message-ID: <523AE95D-9A71-4C9F-9017-F24F10592711@consulintel.es>
Thread-Topic: meeting ietf-legacy ssid
References: <m2eftmwl0l.wl-randy@psg.com>
In-Reply-To: <m2eftmwl0l.wl-randy@psg.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0YhrdRUBNgWIFELhHDNCGh4_7Mo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 00:59:58 -0000

Hi Randy,

It may be a side effect of some OSs. It seems that many of them remember th=
e SSID, and they tend to use the first one that was learnt or the one that =
offers better signal, etc.

So, if the user chooses ietf-legacy in an OS, at some point and then later =
used ietf5ghz (just to put an example), the OS will =E2=80=9Cprefer=E2=80=
=9D ietf-legacy, unless you go to your control panel and change the =E2=80=
=9Corder=E2=80=9D of those SSIDs preference.

So, a simple way to avoid that, is to rename the ietf-legacy at each IETF m=
eeting with the IETF meeting number, for example ietf-legacy99 for the next=
 one.

At this way, the standard SSID (ietf5ghz in my example) gain the preference=
.

Same scheme of ssdi+ietfnumber, can be used to make sure that as many users=
 as we wish, go to our =E2=80=9Cpreferred=E2=80=9D network (for example NAT=
64). We just need to change our actual mind to get used to it.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Randy Bush <randy@psg.com>
Responder a: <randy@psg.com>
Fecha: mi=C3=A9rcoles, 12 de julio de 2017, 2:34
Para: IETF Rinse Repeat <ietf@ietf.org>
Asunto: meeting ietf-legacy ssid

    the noc sees a quite large number of associations to the unencrypted
    ietf-legacy ssid as opposed to say the encrypted ietf ssid
   =20
    some of us are wondering if those using ietf-legacy
   =20
      o do not realize it is completely unencrypted over the air, or
   =20
      o don't care as their threat model sees runnin' nekkid over the air a=
s
        not a significant additional weakness, or
   =20
      o believe that they are using sufficient encryption at higher layers
        to meet their needs, or
   =20
      o other
   =20
    these days, some meetings do not provide unencrypted wifi at all and
    seem not to get complaints.  maybe their attendees are just geekier
    and/or more security conscious.
   =20
    clue bat, please.  unicast responses accepted too.
   =20
    randy
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Tue Jul 11 18:01:05 2017
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF60212EC15 for <ietf@ietfa.amsl.com>; Tue, 11 Jul 2017 18:01:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 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_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=mnot.net header.b=GI8ZYOT9; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=IBw9ga/7
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 7vpwqDfqms_B for <ietf@ietfa.amsl.com>; Tue, 11 Jul 2017 18:01:02 -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 49F3C127867 for <ietf@ietf.org>; Tue, 11 Jul 2017 18:01:02 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id B9C9420944; Tue, 11 Jul 2017 21:01:00 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Tue, 11 Jul 2017 21:01:00 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; 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=db/auIyD4nZ/XAup54 cWvxZoGjKrpdtgqBaKscxQ13Y=; b=GI8ZYOT9nIW5t5mTUJC0URBLhjtFN6Vkhg aiFO5svpSKVSgNAR597Tc0ZBHMr8iXbbFCE511/bgpuElDhCBMebON5JtxWNw5EA 7z8A9HlTv9h+UZrLxIyzAGobWSqp+zkY8+xUQmvsMSVhUTy3b2YH7dItIY4Fh7Av x5KB637xPDHb9eDnTQ01c5KrIWLPx1CTUNAcbzynw/KGlTKpS/0Um4t1IKu3gs8j /BZh9pUy63Ihhf760OPsAkggh4rUU+jcNP3J2BBth+X0imVOBp045WFDlNoR9Goj j6YPnIH6Z/QgXQrOQB3wptCxK8DXP03Ob6Fv2dhV2m6daVxb6liQ==
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=db/auIyD4nZ/XAup54cWvxZoGjKrpdtgqBaKscxQ13Y=; b=IBw9ga/7 lQb0bQgHiInfbqR5kOjXkXe0zqmSLPK5EGKllaXg24AdgL99pyxzNFXYvNbAfRFy FxHLVSd0jkFg8J+Hz+D6CunkwXcVaajGCpBNN6KKfaRph+fKSuD/sOMCYmrlEkfV 7ld0OiQoTiGA4ZdmqXBBhqntlfPIzlgtXthxWdyEKSFWypfDkK+UORzS0kGkhJm+ TE4eniUMc68tMIUCpjP1NLEJBnDPMixPHAO2EAysi6ExBKJIA/r8zDNkCQOfx/tJ 6RCCdyntKlOF/e+U9zo02QZJoMPt3j1aXDZFfuwewLW50/WLbCNw+J7KvR/vqmDq CrwXoG2gQIWcvQ==
X-ME-Sender: <xms:zHRlWTapebcHaYdBsKTfaNcMP3cMaFWeR0KWMa3jHE_F19KtLYNp1Q>
X-Sasl-enc: JmoINe3vMr+QEit6nvxvo+mjQ/sCCjFW5qSMuoRsF067 1499821260
Received: from [192.168.1.18] (cpe-124-188-19-231.hdbq1.win.bigpond.net.au [124.188.19.231]) by mail.messagingengine.com (Postfix) with ESMTPA id BA98E24426; Tue, 11 Jul 2017 21:00:59 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: meeting ietf-legacy ssid
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <m2eftmwl0l.wl-randy@psg.com>
Date: Wed, 12 Jul 2017 11:00:55 +1000
Cc: IETF Rinse Repeat <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <BEF20349-0893-4450-8C23-83DA4F175A7B@mnot.net>
References: <m2eftmwl0l.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ctWWcSULA3H0p0O8KZTcg0z7Oyw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 01:01:05 -0000

Perhaps it's non-IETF people using what looks to be very high-quality, =
free wifi?


> On 12 Jul 2017, at 10:34 am, Randy Bush <randy@psg.com> wrote:
>=20
> the noc sees a quite large number of associations to the unencrypted
> ietf-legacy ssid as opposed to say the encrypted ietf ssid
>=20
> some of us are wondering if those using ietf-legacy
>=20
>  o do not realize it is completely unencrypted over the air, or
>=20
>  o don't care as their threat model sees runnin' nekkid over the air =
as
>    not a significant additional weakness, or
>=20
>  o believe that they are using sufficient encryption at higher layers
>    to meet their needs, or
>=20
>  o other
>=20
> these days, some meetings do not provide unencrypted wifi at all and
> seem not to get complaints.  maybe their attendees are just geekier
> and/or more security conscious.
>=20
> clue bat, please.  unicast responses accepted too.
>=20
> randy
>=20

--
Mark Nottingham   https://www.mnot.net/


From nobody Tue Jul 11 18:36:00 2017
Return-Path: <jared@puck.nether.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8064F12F287 for <ietf@ietfa.amsl.com>; Tue, 11 Jul 2017 18:35:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level: 
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 an2ddQO2-Xzq for <ietf@ietfa.amsl.com>; Tue, 11 Jul 2017 18:35:57 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id D40C412EC46 for <ietf@ietf.org>; Tue, 11 Jul 2017 18:35:57 -0700 (PDT)
Received: from [IPv6:2603:3015:3603:8e00:cccb:6ec9:8eaa:a9ce] (unknown [IPv6:2603:3015:3603:8e00:cccb:6ec9:8eaa:a9ce]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 3316D5404D4; Tue, 11 Jul 2017 21:35:56 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: meeting ietf-legacy ssid
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <m2eftmwl0l.wl-randy@psg.com>
Date: Tue, 11 Jul 2017 21:35:55 -0400
Cc: IETF Rinse Repeat <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2A4AE56B-2059-4811-80DA-FE7394ED9418@puck.nether.net>
References: <m2eftmwl0l.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1lKXwnXapBqvfmhhKL2hPW5KRA8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 01:35:59 -0000

> On Jul 11, 2017, at 8:34 PM, Randy Bush <randy@psg.com> wrote:
>=20
> the noc sees a quite large number of associations to the unencrypted
> ietf-legacy ssid as opposed to say the encrypted ietf ssid
>=20
> some of us are wondering if those using ietf-legacy
>=20
>  o do not realize it is completely unencrypted over the air, or

This is not the case for me.  I also run unencrypted at home but have
a large property where without a directional antenna you can not receive
my wifi.  If you put that much effort into it, it still may not work due
to trees.

I seem to recall (this may not be true) that ietf-legacy is also only
2.4ghz, so sometimes my device sees this first as there are fewer =
channels
to scan compared to the 5ghz + DFS frequencies while waiting for a =
beacon.

>  o don't care as their threat model sees runnin' nekkid over the air =
as
>    not a significant additional weakness, or

This is part 1.  Model covers unencrypted SSID as that=E2=80=99s =
commonly given
out at hotels and other venues.

>=20
>  o believe that they are using sufficient encryption at higher layers
>    to meet their needs, or

This is happening, I=E2=80=99m using SSH, SSL and my DNS is tunneled =
through
a VPN (to a non dual-stack server, gah!)

>  o other
>=20
> these days, some meetings do not provide unencrypted wifi at all and
> seem not to get complaints.  maybe their attendees are just geekier
> and/or more security conscious.

I tend to end up with all the SSIDs pre-programmed, including ietf-hotel
which is valuable as it permits me to not roam, but have a seamless user
experience.

My experience is with the conferences that encrypt WiFi 100% of the =
time,
I must re-enter the username/password or might not have them handy, or
my device says ACHTUNG regarding the certificate change and requires me =
to
take a manual action to join this seemingly =E2=80=9Cnew=E2=80=9D =
network, even if it=E2=80=99s
a familiar one.

This means I tend to have to force it once to rejoin the secure network,
but I=E2=80=99ve likely already fallen back to the insecure network =
first.

At least this is the way it=E2=80=99s generally presented to me via =
MacOS.  I have
also had mobile devices, including Raspberry PI type things that join =
the
wifi when I=E2=80=99m doing other experimental things.  They can be =
configured
to just join the first open SSID that is available.  This is nice as I =
don=E2=80=99t
have to do as much configuration work to make it happen, and I=E2=80=99m =
already
using SSH or some other transport to access the devices.


Related:

If the open SSID were to go away, I don=E2=80=99t expect there to be any =
issues
other than a few newcomers needing to learn what the passwords are.  =
This
caused me issues with one of my first meetings when presented with a =
non-
open wireless network, but I was able to ask what the password was and=20=

easily received it.

If Con is doing his statistics board again of the SSIDs, perhaps putting =
the
username/password there would also be of value should the legacy ssid be =
phased
out.

- Jared=


From nobody Tue Jul 11 19:01:20 2017
Return-Path: <allison.mankin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58057131832; Tue, 11 Jul 2017 19:01:12 -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 xttdqBJgPj4N; Tue, 11 Jul 2017 19:01:10 -0700 (PDT)
Received: from mail-wr0-x22a.google.com (mail-wr0-x22a.google.com [IPv6:2a00:1450:400c:c0c::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 9048F126D46; Tue, 11 Jul 2017 19:01:10 -0700 (PDT)
Received: by mail-wr0-x22a.google.com with SMTP id c11so13010091wrc.3; Tue, 11 Jul 2017 19:01:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=+RMLkVDcG7JqFd4e0sRsk2QTxwHyg/0kKh64AjeKcxs=; b=Bn/L8K11jzZQMc2hyiR+QGFPM//vVWSmmxgiYZ7Aq11bh1PFsJJYzdCO+3AljaCFQx 3dUrAHRnA+PSxAuV+hFA9tHhd5mgU9cX1fF7Zse/LF5938macqhMh+nRJjOp22m2nlul OchvDaWzMBX18Squf9iY4mPVKHMBnioksmiomwp8jvdiAnRrhplJzwGQmKJTHl0vMTP8 XrUTOi5Ys46CeXFqr6K30ca8STimsG7kr2qFh9VWwDZItBx/rIxx8lzC5ePV11Blt6lL HrzH0vsGOCCL5q2a42brUc4jI+Rj6B/CdMHF8dqVQToHzRdBS9raCkrNmmCKUcmkg94x IXww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=+RMLkVDcG7JqFd4e0sRsk2QTxwHyg/0kKh64AjeKcxs=; b=Sf7jWkFz6Tqh6WQwVAWpcuzhN3lDhk+PpKGMOwqViLuFMkUNXqtxFmDA7LWdiHnHxv oyIW5V2GJ2sBBSvhnFNGVQMuSNmwuUCMwEbDQ8H2JUdr4bBLnh+XVjid/7PDFLDby6yo b523dR5h9Ib9Tsqm5/8gawiXDQ5v0xO68twf/7Ff3TJ442ioZN/T0IboyZddG8yyg+ss r5qGslhJ2KtJ5glgEaR73e0tSxj2v/3sqmGK8fZfvf08ySb7kIk10+s3wjrfWLzJesnO Nw02L4WkIetHY9Y7RKZZwUqJbICyTjaz2u3LuISxI6Vj5Ho/guOmSgM5QtQnjp4jHwep HTOA==
X-Gm-Message-State: AIVw113bJ7VxQ3I/DAbsqgwapOUr++1q1LxlUn7D8vBZhzCiXd3UmhAA 6sg8BVVaNUyjRhrttMRF37kkrL0ziBep
X-Received: by 10.80.177.29 with SMTP id k29mr4477335edd.83.1499824868931; Tue, 11 Jul 2017 19:01:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.80.138.69 with HTTP; Tue, 11 Jul 2017 19:01:08 -0700 (PDT)
From: Allison Mankin <allison.mankin@gmail.com>
Date: Tue, 11 Jul 2017 22:01:08 -0400
Message-ID: <CAP8yD=soP9wzaO1+Fq+Cx-eM0tc0MHaif=daCE+G30xOQOnKDQ@mail.gmail.com>
Subject: Systers Networking - Thursday lunchtime in Prague
To: 99attendees@ietf.org, IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="f403045c14f689bc6a055415303c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RWt7xxap09iLqHSN9E3PaEzwqd0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 02:01:12 -0000

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

IETF Systers is a networking group for women in the IETF.  We have kindly
been sponsored by several organizations (Cisco, Comcast, and Dell) for
gatherings at each IETF, and will meet this IETF in Prague during lunchtime
on Thursday, at a location in the meeting hotel TBA soon.

Women colleagues, please join the systers@ietf.org mailing list if you are
not already there for more information and with any questions (and/or you
can email me).  There's a Doodle poll for the headcount at:

https://beta.doodle.com/poll/ics3z7sy862u743f#table

Safe travels, and see everyone soon,

Allison (on behalf of the women of IETF Systers)

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif">IETF Systers is a networking group for women in the IET=
F.=C2=A0 We have kindly been sponsored by several organizations (Cisco, Com=
cast, and Dell) for gatherings at each IETF, and will meet this IETF in Pra=
gue during lunchtime on Thursday, at a location in the meeting hotel TBA so=
on.<br><br></div><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif">Women colleagues, please join the <a href=3D"mailto:sys=
ters@ietf.org">systers@ietf.org</a> mailing list if you are not already the=
re for more information and with any questions (and/or you can email me).=
=C2=A0 There&#39;s a Doodle poll for the headcount at:<br><br><a href=3D"ht=
tps://beta.doodle.com/poll/ics3z7sy862u743f#table">https://beta.doodle.com/=
poll/ics3z7sy862u743f#table</a><br><br></div><div class=3D"gmail_default" s=
tyle=3D"font-family:arial,helvetica,sans-serif">Safe travels, and see every=
one soon,<br><br></div><div class=3D"gmail_default" style=3D"font-family:ar=
ial,helvetica,sans-serif">Allison (on behalf of the women of IETF Systers)<=
br><br><br></div></div>

--f403045c14f689bc6a055415303c--


From nobody Tue Jul 11 19:10:52 2017
Return-Path: <ggm@algebras.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 034651241FC for <ietf@ietfa.amsl.com>; Tue, 11 Jul 2017 19:10:51 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=algebras-org.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 3cQi1-QsK3rL for <ietf@ietfa.amsl.com>; Tue, 11 Jul 2017 19:10:49 -0700 (PDT)
Received: from mail-vk0-x22b.google.com (mail-vk0-x22b.google.com [IPv6:2607:f8b0:400c:c05::22b]) (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 CAAE5120725 for <ietf@ietf.org>; Tue, 11 Jul 2017 19:10:48 -0700 (PDT)
Received: by mail-vk0-x22b.google.com with SMTP id r126so5411805vkg.0 for <ietf@ietf.org>; Tue, 11 Jul 2017 19:10:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=algebras-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ZOtWVM18WSFF02t733vm20DzfkYBqoVmyJqGbLLvTxE=; b=tSFQCv78d08tLZ4liIrUogmkqYgIFpfVv4sY2hM2u9idHys2mHRw+qCb0sqDNPIfSQ bL4JYdemXWYBTvpGFxVJCPNsBSI99eUhe4mL5lJeKr7Q7HMxEGxx/uBSlKNn5sReuzzt TjgHERI1q++aQEoTJaUMcbHzKWdKkWyqwktVS741GtfG5wULxXBYpA19Ecbf4wiRhJ+Y 7HAdVa44lcXwvaWCl9cebnIMS1Xrasc/Oi9yb6bIjJzDuFCqg7mQBJClWO2cqCTdxNWS e/vfhU+j+I8R9sK7ZxPYMfcarj9xiZpNLGbDTzXY7iw75TsHqW60BNY7u9EHCdJs/IP6 ipbQ==
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=ZOtWVM18WSFF02t733vm20DzfkYBqoVmyJqGbLLvTxE=; b=pUe9sQuDR6evqumCUrgeU1RrZxrqOxwqEMwvUbbSrD0rQVIazRv/99f6w5ZcWRIUER uBI7c/ecqIYtIGk8TwIjUiTnKGqlLV8jbgeRbZkHrrKCGUKWSjaYFNrP7x6d68xAnoCj MY2Z+TzXuftwmdKUagXV8yCjnuPkxj1m11TwqCOh5wR/eVEczK/J9Y7rjRmNxp8YTz9m G1lUySbDfwaz8Ss4dOnz9NAHQNWjhd0tZovSXkk2R0bPRhfsnCFCM3QsgarM+Ph5FYnD FcScISOq65NqotOYhAW58L0xZxB3EuK+uTVqChBnlogSf9mKuSSc1lDChHbVxFv6FGoE sjUg==
X-Gm-Message-State: AIVw110COEyTfUTdLufGxnCkGjMGxrMyBe1jm+Rzq2OOgdFX8CZORkbx EHPiqGP7cerp8JiYlDtCv0W/AU8Xnui6H84=
X-Received: by 10.31.223.196 with SMTP id w187mr76511vkg.75.1499825447730; Tue, 11 Jul 2017 19:10:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.90.18 with HTTP; Tue, 11 Jul 2017 19:10:47 -0700 (PDT)
X-Originating-IP: [2001:dc0:2001:210:68c5:8324:85e:ad1c]
In-Reply-To: <m2eftmwl0l.wl-randy@psg.com>
References: <m2eftmwl0l.wl-randy@psg.com>
From: George Michaelson <ggm@algebras.org>
Date: Wed, 12 Jul 2017 12:10:47 +1000
Message-ID: <CAKr6gn15ZKBQpvWwfkJjVQS8-NOgWkCmgdj2bEa_GS4vcLbfEg@mail.gmail.com>
Subject: Re: meeting ietf-legacy ssid
To: Randy Bush <randy@psg.com>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7jsGm_TlwkS5TzxD6jGYz1hrxE4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 02:10:51 -0000

>From time to time, my devices fail to bind adequately to the secure SSID.

When that happens, I find the unsecured one works.  Perhaps simpler
logic, perhaps different codepaths? I don't know. I observe that it
works more often than not.

So, I use it opportunistically, as a function of unknown failures in
cryptographically secured SSD binding logic, as exposed in OSX and
Android.

I don't use it by preference: I use it as a fallback.

When the SSID binding is fine, the DHCP/DHCPv6/slaac is all a
subsequent issue. I do still find that from time to time, the WiFi
decides not to have a default router. If you tcpdump your WiFi the
typical view at these times, is a million IETF people sending ARP. I
like to imagine the NOC looks like a herd of kittens with a large ball
of wool, desperately searching for an end, while simultaneously biting
each others tails.

-George

On Wed, Jul 12, 2017 at 10:34 AM, Randy Bush <randy@psg.com> wrote:
> the noc sees a quite large number of associations to the unencrypted
> ietf-legacy ssid as opposed to say the encrypted ietf ssid
>
> some of us are wondering if those using ietf-legacy
>
>   o do not realize it is completely unencrypted over the air, or
>
>   o don't care as their threat model sees runnin' nekkid over the air as
>     not a significant additional weakness, or
>
>   o believe that they are using sufficient encryption at higher layers
>     to meet their needs, or
>
>   o other
>
> these days, some meetings do not provide unencrypted wifi at all and
> seem not to get complaints.  maybe their attendees are just geekier
> and/or more security conscious.
>
> clue bat, please.  unicast responses accepted too.
>
> randy
>


From nobody Tue Jul 11 19:20:54 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0232D120725 for <ietf@ietfa.amsl.com>; Tue, 11 Jul 2017 19:20:53 -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 YeaIlrR1Uwa4 for <ietf@ietfa.amsl.com>; Tue, 11 Jul 2017 19:20:51 -0700 (PDT)
Received: from mail-pf0-x231.google.com (mail-pf0-x231.google.com [IPv6:2607:f8b0:400e:c00::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 B080C120454 for <ietf@ietf.org>; Tue, 11 Jul 2017 19:20:51 -0700 (PDT)
Received: by mail-pf0-x231.google.com with SMTP id q86so5109012pfl.3 for <ietf@ietf.org>; Tue, 11 Jul 2017 19:20:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=Eq+NnvtVVPKcHB7Ba+FRv1aRL5rjMw7AKmSFsCGXuSY=; b=NdxxhR3zzho0mkp481FKGX+vslhjTKtFRO8NhKqd8Spna1kWUDqoF14RsLizo1MabI yAcYBFxQNVFMfH4Nx96LfBo0dzlCOOnuGV1iBA+gODHJ76ahTTWGYHu5voEZP/3u8hsZ 7jH1IS7LDowlM6PYc8zrilotLn/XpL0B6GJ6ZJ4TFBvED/zE3nu4sUDQUs2kXNGGZNby kG7TCbMMyws4vXPegc6AwoS8uRdQnE6a6Z6/xL3HBUP3uonbaOLObg4jJ4eePnZppKP3 H5QDVU1QV9MZguw2lv7qQUF9yZbuv6p0RrzAFpf51l3rRktMRneOtpL4WIcTZdjp1WS9 N1CQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=Eq+NnvtVVPKcHB7Ba+FRv1aRL5rjMw7AKmSFsCGXuSY=; b=dE4ZYjh13xH/dt5OTNHK9ic3EVesJo8HA/tCFSSh1E40ABB0kzKJ84z6f13wLf9rlB d+NYaPfZUlJELoFhkoM2YNvNUFdX/3qV+Ux2C5/Vjh89VzCLXLzpxsdMLQqbQdJgyOzv 5EQ9EGgoZRk36mvcJFOKWa94az86RXae4PjOh003VY3Ei/7H1+1YHo0qc44ikJarcVue H3+8LM87ZIT+eA3DwcWILu7dZd260ClB31hje5mFJo+PVeoeuSxe5pbsFN1vegcu0zlN 4scSRdGd6NTmItRavYOm6Eu2jQbne96CLAewilBpzFX9tyLWFCsEfa2cqLVUNjRw+O4f kHhQ==
X-Gm-Message-State: AIVw110UKuyO2ZJ66F4ukAERMaI8miTTgANUH8xA3Jjxo8O9TZkwMPQZ Nsq15zw+i4/H2Ubs
X-Received: by 10.84.217.150 with SMTP id p22mr1594345pli.270.1499826050818; Tue, 11 Jul 2017 19:20:50 -0700 (PDT)
Received: from [192.168.178.21] ([118.148.76.144]) by smtp.gmail.com with ESMTPSA id l85sm1166925pfi.53.2017.07.11.19.20.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Jul 2017 19:20:50 -0700 (PDT)
Subject: Re: meeting ietf-legacy ssid
To: Randy Bush <randy@psg.com>, IETF discussion list <ietf@ietf.org>
References: <m2eftmwl0l.wl-randy@psg.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <e6a9d5b5-f50b-c0ec-fcf8-1a2d036c9421@gmail.com>
Date: Wed, 12 Jul 2017 14:20:50 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <m2eftmwl0l.wl-randy@psg.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Kynxz5flGHiY3YxwMffijgYU37c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 02:20:53 -0000

On 12/07/2017 12:34, Randy Bush wrote:
> the noc sees a quite large number of associations to the unencrypted
> ietf-legacy ssid as opposed to say the encrypted ietf ssid
> 
> some of us are wondering if those using ietf-legacy
> 
>   o do not realize it is completely unencrypted over the air, or
> 
>   o don't care as their threat model sees runnin' nekkid over the air as
>     not a significant additional weakness, or

If you don't feel that way, there are millions of networks you can never
use, including most hotels, cafes etc.

>   o believe that they are using sufficient encryption at higher layers
>     to meet their needs, or

If you believe that, you're probably wrong ;-)
 
>   o other

1) For whatever reason my Android 4.3 phone has always seemed allergic
to the ietf network (although after much torture, it agreed to connect
to eduroam). So it only knows about ietf-legacy and ietf-hotel.

2) On my laptop things are better, but I do have ietf-legacy lower in
the list as a fallback.
 
> these days, some meetings do not provide unencrypted wifi at all and
> seem not to get complaints.  maybe their attendees are just geekier
> and/or more security conscious.

...or they just don't care as long as it works. There's a lot of
that about.

Jordi is correct about the ordering of SSIDs in the list kept by the
o/s. If you don't manually push ietf-legacy down the list, it may well
be picked automatically.

    Brian


From nobody Tue Jul 11 19:45:46 2017
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F34512762F for <ietf@ietfa.amsl.com>; Tue, 11 Jul 2017 19:45:44 -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 NP69ePh4-EQn for <ietf@ietfa.amsl.com>; Tue, 11 Jul 2017 19:45:42 -0700 (PDT)
Received: from mail-wr0-x236.google.com (mail-wr0-x236.google.com [IPv6:2a00:1450:400c:c0c::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 1CF3A120725 for <ietf@ietf.org>; Tue, 11 Jul 2017 19:45:42 -0700 (PDT)
Received: by mail-wr0-x236.google.com with SMTP id c11so13936101wrc.3 for <ietf@ietf.org>; Tue, 11 Jul 2017 19:45:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=RXCy9mSbfWMzSSs/YNYxT6umxWBNpif8cDYW5WqyjWc=; b=Af4P264/lX1OkhRn/Ll7MKJWZybeif2Kx3e0ki3EN2CKONEC6Vg2iOQcZQAS7VSAbW llz4fOdxm+qbcPw92ftkqp85CM9KY4WQ1jiaSupGfosul3rK/6zTm9ccOQxiGsG1j4yz P4ttIAYaw+c2PCVUP0xxUMf/dPBvDRprAD/cU8rM8Kjd+79z1YSh3zcny7l8c+adk/7I QgZ9sBCjR3Z/5ZWzSGLDg7I8ffEbhB0JZrOYZEKKTcp49J+Ffa6Fo8geA8t44f9jzkVo ko4oZyKz47iq7nqVTEEV1fqOUaH/YvxC79zoTgrTKZzP8ZUjEcvMC4QtY6gu56l372q7 dhtw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=RXCy9mSbfWMzSSs/YNYxT6umxWBNpif8cDYW5WqyjWc=; b=fwfuLP0NjspvXo9HOkgzyKWCuIFKv/tO8/76LYbj0+4acIrAaDqZ4mqLSIcFAxJQId 0Xl4mGWLxFRg7t0NbUIeI8aHeEx3Upw1wMlcgLnT8fwzhaj34+mjaTFXWTP69DMSIwAZ i6k0jII2Xkb5lfssd1VtudMIihmD47z3Qvjk48gpP9FULNhGnCCrHD2BhvNAOK/o5bZl xcFHIL6Bh/a/s6KiERPPzN4TENzvZQ8U9SFAjnfEoZBhV2b77YVwHR9zlRejF+A5ghxO i2vXWu2YpshlRl1/2moXVCq7yBI7ATNh+Ddl4md8ZJXE7ZVCZ2SUn8n2RhCIkgypUJXB dMfg==
X-Gm-Message-State: AIVw113QqxCmero6pqSt25jZWj32eGkei7fCcI53e1jt3/oEWdOi2Zen hhNPTuoGl9Br0g==
X-Received: by 10.28.103.132 with SMTP id b126mr788925wmc.10.1499827540623; Tue, 11 Jul 2017 19:45:40 -0700 (PDT)
Received: from ?IPv6:2601:647:4d01:db10:8979:d684:7992:1d0b? ([2601:647:4d01:db10:8979:d684:7992:1d0b]) by smtp.gmail.com with ESMTPSA id w30sm1483321wrb.49.2017.07.11.19.45.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Jul 2017 19:45:39 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <6A2F8BE0-4B60-4B55-AFA5-66F22BC6CB3C@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_9FE09562-699E-475A-9F86-235241107B82"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: meeting ietf-legacy ssid
Date: Tue, 11 Jul 2017 19:45:36 -0700
In-Reply-To: <e6a9d5b5-f50b-c0ec-fcf8-1a2d036c9421@gmail.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, Randy Bush <randy@psg.com>, IETF <ietf@ietf.org>
To: Brian Carpenter <brian.e.carpenter@gmail.com>
References: <m2eftmwl0l.wl-randy@psg.com> <e6a9d5b5-f50b-c0ec-fcf8-1a2d036c9421@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/W0cNNcMOEqMjwFYFkx3aK4DOnTU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 02:45:44 -0000

--Apple-Mail=_9FE09562-699E-475A-9F86-235241107B82
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I think that, as an experiment to see what the impact is, we should not =
have ietf-legacy at IETF99.

The IETF is telling the word it=E2=80=99s important to use encryption, =
we should be eating our own dog food.

Bob

> On Jul 11, 2017, at 7:20 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>=20
> On 12/07/2017 12:34, Randy Bush wrote:
>> the noc sees a quite large number of associations to the unencrypted
>> ietf-legacy ssid as opposed to say the encrypted ietf ssid
>>=20
>> some of us are wondering if those using ietf-legacy
>>=20
>>  o do not realize it is completely unencrypted over the air, or
>>=20
>>  o don't care as their threat model sees runnin' nekkid over the air =
as
>>    not a significant additional weakness, or
>=20
> If you don't feel that way, there are millions of networks you can =
never
> use, including most hotels, cafes etc.
>=20
>>  o believe that they are using sufficient encryption at higher layers
>>    to meet their needs, or
>=20
> If you believe that, you're probably wrong ;-)
>=20
>>  o other
>=20
> 1) For whatever reason my Android 4.3 phone has always seemed allergic
> to the ietf network (although after much torture, it agreed to connect
> to eduroam). So it only knows about ietf-legacy and ietf-hotel.
>=20
> 2) On my laptop things are better, but I do have ietf-legacy lower in
> the list as a fallback.
>=20
>> these days, some meetings do not provide unencrypted wifi at all and
>> seem not to get complaints.  maybe their attendees are just geekier
>> and/or more security conscious.
>=20
> ...or they just don't care as long as it works. There's a lot of
> that about.
>=20
> Jordi is correct about the ordering of SSIDs in the list kept by the
> o/s. If you don't manually push ietf-legacy down the list, it may well
> be picked automatically.
>=20
>    Brian
>=20


--Apple-Mail=_9FE09562-699E-475A-9F86-235241107B82
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJZZY1RAAoJEK7rdBF357uoaCUIALR0/4aP634t7zQgyBY+pMVZ
YDDcvq/qkDRXxgsfKMOIIlQuL7IgRsmIbwHMEJF4agw2WaCr8rOnZQzQlmhAsvMy
e7TwOul3EJl8zgwT0zS/oP7visGv7uXHeF3ainWKQHLTzeT6xcE89kD9jD5RutD9
9dxIJrZB5WzH8EB18/3SkKzsEuJVy/G12tIqNdfX43b7VYyXppMmNNTB+KlYvQm7
JXAve9Sgj8O3VXpwRyEFVnoo7WP6AAwvHHEtATEaN45WYoyIoq+76SmZUTDNfFv2
nBvt9D1U8TvbKtluK/AqALCh79mtM0IJ46JD06oMjW/pWixLHy+UVb05mJf+6s0=
=l6PK
-----END PGP SIGNATURE-----

--Apple-Mail=_9FE09562-699E-475A-9F86-235241107B82--


From nobody Tue Jul 11 19:55:32 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F55E12955F for <ietf@ietfa.amsl.com>; Tue, 11 Jul 2017 19:55:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 5ZNO-NayublB for <ietf@ietfa.amsl.com>; Tue, 11 Jul 2017 19:55:29 -0700 (PDT)
Received: from miucha.iecc.com (w6.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 391A912762F for <ietf@ietf.org>; Tue, 11 Jul 2017 19:55:29 -0700 (PDT)
Received: (qmail 74718 invoked from network); 12 Jul 2017 02:55:28 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 12 Jul 2017 02:55:28 -0000
Date: 12 Jul 2017 02:55:06 -0000
Message-ID: <20170712025506.1358.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: meeting ietf-legacy ssid
In-Reply-To: <BEF20349-0893-4450-8C23-83DA4F175A7B@mnot.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/f4WCTd3WHDFbHznafGKHdB0lU4U>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 02:55:30 -0000

In article <BEF20349-0893-4450-8C23-83DA4F175A7B@mnot.net> you write:
>Perhaps it's non-IETF people using what looks to be very high-quality, free wifi?

We tend to fill up whatever hotel we're in do I doubt that's it.

I like the theory that our devices remember whatever networks we've
used and reconnect automatically.  My Mac certainly does, and I need to twiddle the
settings to push the better networks higher in the list.

R's,
John


From nobody Tue Jul 11 20:08:24 2017
Return-Path: <worley@ariadne.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 450BB12F290; Tue, 11 Jul 2017 20:08:17 -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-pce-pceps.all@ietf.org, pce@ietf.org, ietf@ietf.org
Subject: Genart last call review of draft-ietf-pce-pceps-14
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149982889725.9262.6380278547558008402@ietfa.amsl.com>
Date: Tue, 11 Jul 2017 20:08:17 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6hsoB0lolxLhHzv5fjsFp1BoJ-c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 03:08:17 -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 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-pce-pceps-14
Reviewer:  Dale R. Worley
Review Date:  2017-07-11
IETF LC End Date:  2017-07-12
IESG Telechat date:  2017-08-03

Summary:

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

Nits/editorial comments:

A few of these may rise to the level of minor technical issues,
especially:
section 3.2: whether error TBA2/2 is distinct from error 1/1
section 3.2: the receipt of an PCErr during the failure of TLS
             establishment
section 3.3: the distinction between StartTLSWait and OpenWait
section 5:   a full discussion of backward compatibility considerations
section 8.2: MIB extension

1.  Introduction

   This document describes a security container for the transport of
   PCEP messages, and therefore they do not affect the flexibility and
   extensibility of PCEP.

There is no plural antecedent for "they" to reference.  I think you
could use "it", but the Editor may have better suggestions.

3.2.  Initiating the TLS Procedures

   with a PCErr message with Error-Type set to [TBA2 by IANA] (PCEP
   StartTLS failure)

It seems that we shouldn't use this Error-Type to object to the use of
a message other than Open and StartTLS as an initial message, as that
error isn't a misuse of StartTLS per se and is only incidentally
related to StartTLS.  Indeed, isn't there already an Error-Type for
this error (unexpected initial message), since two RFC 5440
implementations can commit/detect it?  Looking at RFC 5440 section
7.15, I see:

   Error-Type    Meaning
      1          PCEP session establishment failure
                 Error-value=1: reception of an invalid Open message or
                                a non Open message.

It seems to me that this document is adjusting the meaning of error
1/1, rather than defining a new error situation.

   If the PCEP speaker that does not support PCEPS, receives a StartTLS
   message, it MUST behave according to the existing error mechanism
   described in section 6.2 of [RFC5440] (in case message is received
   prior to an Open message) or section 6.9 of [RFC5440] (for the case
   of reception of unknown message).

I think you want s/MUST/will/, since the described behavior isn't
specified by this document, but rather by RFC 5440.

In any case, this paragraph might want to reference the
backward-compatibility consideration that I would expect to appear in
section 5 -- How does the PCEPS-supporting element deal with the
non-PCEPS-supporting element after the connection attempt with
StartTLS fails?

   After the exchange of startTLS messages, if a PCEP speaker cannot
   establish a TLS connection for some reason (e.g. the required
   mechanisms for certificate revocation checking are not available), it
   MUST return a PCErr message (in clear) with Error-Type set to [TBA2
   by IANA] (PCEP StartTLS failure) and Error-value set to:

s/startTLS/StartTLS/

Is there a well-defined way for a participant in a TLS connection
start to receive *either* a PCErr message in the clear *or* whatever
comes next in TLS setup -- and know which case has happened?  Is there
a way to use popular modular TLS libraries and have the application
above the library receive such a PCErr message?  I don't understand
TLS nearly well enough to know the answer to this, but it would
probably help implementors if answers were given to these questions.

      The peer MAY choose to re-establish the PCEP session
      without TLS next.

I think you mean "The peer that initiated the connection MAY choose to
re-establish ...".  As written, "the peer" seems to refer to the peer
that generated the PCErr, but if it was the receiving peer that
generated the PCErr, you probably don't want it to attempt to
re-establish the session but rather wait for the initiating peer to do
so.

   Given the asymmetric nature of TLS for connection establishment it is
   relevant to identify the roles of each of the PCEP peers in it.  The
   PCC SHALL act as TLS client, and the PCE SHALL act as TLS server,
   according to [RFC5246].

See comments re section 4 about terminology.  I think you need to have
terms for the element that is initiating the connection (either a PCC
or a PCE) and the element that is receiving the connection (always a
PCE).

3.3.  The StartTLS Message

   Once the TCP connection has been successfully established and the
   StartTLS message sent, the sender MUST start a timer called
   StartTLSWait timer, after the expiration of which, if no StartTLS
   message has been received, it MUST send a PCErr message and releases
   the TCP connection with Error-Type set to [TBA2 by IANA] and Error-
   value set to 5 (no StartTLS message received before the expiration of
   the StartTLSWait timer).  A RECOMMENDED value for StartTLSWait timer
   is 60 seconds.

Really, the timer is the time to wait for *any* message to received.
Open messages will cause start of upward-compatibility mechanisms (if
any); any other message will be immediately rejected as an error.

Indeed, isn't there already a timer which a peer uses to wait for the
other peer to send a message?  Isn't StartTLSWait functionally the
same as OpenWait (RFC 5440 section 6.2)?

   ... it MUST send a PCErr message and releases ...

This sentence is grammatically interesting.  One part is logically "it
MUST send a PCErr message".  The second part might be "it MUST release
the TCP connection", or "it releases the TCP connection".  Strictly
speaking, the rules of English grammar cause the release/releases
distinction to disambiguate whether MUST applies to both parts or only
to the first part.  But I don't think you want to rely on that, and
you want to say "... and MUST release the TCP connection ...".

3.4.  TLS Connection Establishment

   1.  Immediately negotiate TLS sessions according to [RFC5246].

In this case, you'd say "Immediately negotiate a TLS session ...".

3.5.  Peer Identity

   At least the following parameters of the X.509 certificate SHOULD
   be exposed:

   o  Peer's IP address

   o  Peer's fully qualified domain name (FQDN)

To the naive (me), these two items seem to refer to the TCP connection
that was established.  But I suspect that they're intended to refer to
the IP address and FQDN that might be encoded in the certificate (as
in, "The following precedence applies: for DNS name validation,
subjectAltName:DNS has precedence over CN; for IP address validation,
subjectAltName:iPAddr has precedence over CN.")

And it seems that the actual remote IP address of the TCP connection
and whatever remote FQDN or IP address was used to initiate the
connection should also be exposed to the administrative system.

So I think there's room to expand on and clarify exactly the data
items that are intended here.

4.  Discovery Mechanisms

   A PCE can advertise its capability to support PCEPS using the IGP
   advertisement and discovery mechanism.

If I understand this correctly, IGP is "Interior Gateway Protocol",
and it's a category of protocols, not a specific protocol.  And what
you're saying is that a PCE can advertise using the relevant IGP's
mechanism.  In that case, I think you'd say "the IGP's advertisement
and discovery mechanism".  (Unless somehow IS-IS and OSPF are seen as
variants of the same protocol, which can generically be called IGP.)

   A new
   capability flag bit for the PCE-CAP-FLAGS sub-TLV that can be
   announced as attribute to distribute PCEP security support
   information is proposed in [I-D.wu-pce-discovery-pceps-support]

s/announced as attribute/announced as an attribute/.

But you don't want to say "is proposed in ..." because that suggests
that the proposal might not be approved, and you've already positively
stated "A PCE can advertise ...".  So you want to say "A new
capability flag ... is defined in ..." -- and raise
draft-wu-pce-discovery-pceps-support to a normative reference.

Similar considerations apply to discovery via DNS
(draft-wu-pce-dns-pce-discovery) -- you want to mention it here and
consider it a normative reference.

-- Unless you choose to make this part of the section clearly
hypothetical by starting "This document does not specify any method a
PCE can advertise that it supports (or requires) PCEPS, but two
mechanisms have been proposed:"

   When DNS is used by a PCC (or a PCE acting as a client, for the rest
   of the section, PCC refers to both) willing to use PCEPS to locate an
   appropriate PCE [I-D.wu-pce-dns-pce-discovery], the PCC as an
   initiating entity, chooses at least one of the returned FQDNs to
   resolve, which it does by performing DNS "A" or "AAAA" lookups on the
   FDQN.

s/FDQN/FQDN/

This one sentence uses the terms "acting as a client" and "as an
initiating entity" to mean the same thing.  You should fix on one
term.  And given that the same concept arises in the discussion of TLS
initiation (section 3.2), you probably want to define the term for "a
PCC (or a PCE acting as a client)" near the beginning as document-wide
terminology.  Once you've got names for the concepts of the initiating
entity and the receiving entity, a number of things in the document
can then be stated more clearly.

   If the PCC receives a response to its SRV query but it is not able to
   establish a PCEPS connection using the data received in the response,
   as initiating entity it MAY fall back to lookup a PCE that uses TCP
   as transport.

This is unclear -- if the process of resolving the original FQDN into
addresses fails to produce an address that can be contacted, how can
the PCC "fall back to lookup a PCE that uses TCP as transport" -- it has
already done the looking up, and that failed.

I suspect you mean that the PCC is required to first attempt to
contact each address using TLS, and then only if all of those attempts
fail is it then permitted to fall back to using TCP.  But you don't
actually say that.

5.  Backward Compatibility

It would help if this section gave a more comprehensive discussion of
how PCEPS-supporting PCEs/PCCs and non-PCEPS-supporting PCEs/PCCs can
interwork, i.e., how to incrementally deploy PCEPS into an AS.  The
two major points seem to be (1) arranging that any two elements will
communicate with the highest level of security that they both
implement, and (2) any system of PCEPS-supporting and
non-PCEPS-supporting elements can interwork successfully.  There
probably are some "interesting" management and security issues
involved in this.

6.2.  New Error-Values

I've noted above that the function of Error-Type=TBA2/Error-Value=2
seems to duplicate that of Error-Type=1/Error-Value=1.

The meaning of Error-Type=TBA2 is named "StartTLS Failure" here, but
the rest of the text uses "StartTLS failure".  The table given in RFC
5440 section 7.15 is not consistent about capitalization in the names
of Error-Types, but most entries do not capitalize non-initial words.
That suggests "StartTLS failure" should be used here.

7.  Security Considerations

There needs to be some consideration of interoperation of mixed
PCEPS-capable and non-PCEPS-capable elements (unless such mixtures are
NOT RECOMMENDED).

8.1.  Control of Function and Policy

   A PCEP implementation SHOULD allow configuring the following PCEP
   security parameters:

   o  StartTLSWait timer value

   PCEPS implementations MAY provide ...

If I read this correctly, there is only one security parameter in this
list.  But since the text says "the following PCEP security
parameters:", on my first reading, I assumed that "PCEPS
implementation MAY provide ..."  was the beginning of a second item
(with the initial "o" omitted).

   provide ways for the operator to complete the following tasks:

It looks like all of the following tasks are with regard to a selected
PCEP session, though only the first task is labeled as such, whereas
the 2nd through 4th are not.  It seems like you want to say "to
complete the following tasks in regard to any PCEP session:" and
change the 1st to "Determine if the session is protected via PCEPS."

8.2.  Information and Data Models

   The PCEP MIB module SHOULD be extended to include PCEPS capabilities,
   information, and status.

This isn't a "SHOULD" because it isn't a constraint on
implementations, it's a statement of what would be a desirable action
by the IETF. -- Unless the idea is that the implementor SHOULD add a
(necessarily proprietary) extension to the MIB.  In any case, RFC 7420
should be referenced.)

8.4.  Verify Correct Operations

This section title is a verb phrase while the rest of the titles are
noun phrases.  Perhaps "Verification of Correct Operations".

8.5.  Requirements on Other Protocols

   Mechanisms defined in this document do not imply any new requirements
   on other protocols.

There is a correlated discovery mechanism:
draft-wu-pce-discovery-pceps-support defines a correlated change to
OSPF and IS-IS.  I suppose that isn't *required* by this document, as
draft-wu-pce-dns-pce-discovery or configuration might be used.  But
conceptually, the two discovery mechanisms are implied by this
document.

10.1.  Normative References

It seems to me that draft-wu-pce-discovery-pceps-support and
draft-wu-pce-dns-pce-discovery should be considered normative
references.



From nobody Wed Jul 12 00:04:02 2017
Return-Path: <vaibhavsinghacads@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F47D130141 for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 00:04:01 -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 UMsKtnWCVgz0 for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 00:03:59 -0700 (PDT)
Received: from mail-it0-x235.google.com (mail-it0-x235.google.com [IPv6:2607:f8b0:4001:c0b::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 CD4B213010C for <ietf@ietf.org>; Wed, 12 Jul 2017 00:03:59 -0700 (PDT)
Received: by mail-it0-x235.google.com with SMTP id m84so8132174ita.0 for <ietf@ietf.org>; Wed, 12 Jul 2017 00:03:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=bCZe0dnTF1p6bEdnqsPYeOY9bNSNZSPptJzTiXPGW0o=; b=MJ8mBQsVQbFCwEfQz9ithHu1lJLf0gt3Ceo3oL/UpgnFd2p8MavixKsgONlYTYoVV/ iOCZOYGYzHXf5ANFp4RWGB1iPlyY3RIU2kq/vOtC5gE0qGX2cf1ha3Imv6aBXOK+xMLG zfdgZ3Vc49DvJpUXuJ7ds2GgZJVCr1E5EUT9L6+Mvue3xwYrvqJOl61fKkxj1HkcIaQ5 dqwZY7HZpDP58o8Jqo1SOo4/FXgO4upoSaoI3SDf6SN0SsewKSlAivo5DC/NKEXVatfm NVFT6h3S+pldgaMTfDXos1bFIcNiTUJGYafGnjyaYzEdx2KFwECTiJFPqDWRyjX0/ILX KPgg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=bCZe0dnTF1p6bEdnqsPYeOY9bNSNZSPptJzTiXPGW0o=; b=EX75a+B9CvgRcXaQGF4sks9cljnYMsvxuO2D0zZuBvcALPPc67W6cydGd2E5P0SfA3 iK7dKk26PigHCJZ6sm8+9SXP0HkW5D12dzJAxscwtVvMeCKA00fojvZem8SFa4/1WRU7 EGRxieY4WFiy8n4EdntcrGhH6Y/A2MEpj1Gyh9sI0l0lcqhio0QagpEF82QuY+vNMa0K NXkEnkUyNb7ZCB6UXYnXushUY43ZaMJ6eUAvDLMbkGTEROIYedtNMLEV63UmZWqhjYaj 0PhCtYg3TRn/lmSxh2Bsu4WnpiHKeox0z6v807TZhY4RR2weXQO0mh1SJPjoSmJS7sZV nRIQ==
X-Gm-Message-State: AIVw111C9pwTlIGqkTxMwlCXsp0MrjfC9Vp1QQ2FKXV7nxrCwUWTrC0N jkZDrTpPpYCH7/k18+gSNSjx6JrqPw==
X-Received: by 10.36.41.67 with SMTP id p64mr14076302itp.14.1499843038955; Wed, 12 Jul 2017 00:03:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.0.210 with HTTP; Wed, 12 Jul 2017 00:03:58 -0700 (PDT)
From: vaibhav singh <vaibhavsinghacads@gmail.com>
Date: Wed, 12 Jul 2017 12:33:58 +0530
Message-ID: <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com>
Subject: Need for secured email delegation workflow
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary="001a11441afa8e4cb20554196b68"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wbuzbHMBnYAjzf1_fgUtmgzYQSs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 07:04:01 -0000

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

Hi,

First of all, I am kind of new and still learning how email infrastructure
fits in, so please feel free to highlight any glaring issues with my logic.

I was working on implementing Email Delegation for my email server, and
felt a need to highlight a couple of things.

1.) I could not find a place where this workflow is outlined. It seems like
everyone, from Microsoft to Google, have an implementation for email
delegation, and they are all kind of doing their own thing.

2.) As I could not find any RFC/Internet Draft covering this flow, I could,
potentially, create a really bad email delegation implementation in which I
could allow potentially anyone to send mails on behalf of anyone, and I
will still be, say, RFC-2822 compatible (I may be incorrect here, but I
could not really find any place which would restrict a user from sending an
email on someone's behalf, by editing the "Sender" header before sending an
IMAP request.)

Am I missing something here? Is this something which should be an Internet
draft/RFC?

-- 

Regards,
Vaibhav Singh

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

<div dir=3D"ltr"><div><div><div>Hi,<br><br></div><div>First of all, I am ki=
nd of new and still learning how email infrastructure fits in, so please fe=
el free to highlight any glaring issues with my logic.<br><br></div>I was w=
orking on implementing Email Delegation for my email server, and felt a nee=
d to highlight a couple of things. <br><br></div>1.) I could not find a pla=
ce where this workflow is outlined. It seems like everyone, from Microsoft =
to Google, have an implementation for email delegation, and they are all ki=
nd of doing their own thing.<br><br></div>2.) As I could not find any RFC/I=
nternet Draft covering this flow, I could, potentially, create a really bad=
 email delegation implementation in which I could allow potentially anyone =
to send mails on behalf of anyone, and I will still be, say, RFC-2822 compa=
tible (I may be incorrect here, but I could not really find any place which=
 would restrict a user from sending an email on someone&#39;s behalf, by ed=
iting the &quot;Sender&quot; header before sending an IMAP request.)<br cle=
ar=3D"all"><div><div><div><div><br></div><div>Am I missing something here? =
Is this something which should be an Internet draft/RFC?<br><br></div><div>=
-- <br><div class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><d=
iv dir=3D"ltr"><div><br></div>Regards,<div>Vaibhav Singh</div></div></div>
</div></div></div></div></div>

--001a11441afa8e4cb20554196b68--


From nobody Wed Jul 12 01:26:39 2017
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 222FA13166A; Wed, 12 Jul 2017 01:26:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netapp.onmicrosoft.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 3hO2_Qxb1aFu; Wed, 12 Jul 2017 01:26:28 -0700 (PDT)
Received: from mx143.netapp.com (mx143.netapp.com [216.240.21.24]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2BA5126E64; Wed, 12 Jul 2017 01:26:28 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.40,349,1496127600";  d="asc'?scan'208";a="205398505"
Received: from vmwexchts03-prd.hq.netapp.com ([10.122.105.31]) by mx143-out.netapp.com with ESMTP; 12 Jul 2017 01:00:53 -0700
Received: from VMWEXCCAS09-PRD.hq.netapp.com (10.122.105.27) by VMWEXCHTS03-PRD.hq.netapp.com (10.122.105.31) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 12 Jul 2017 01:21:26 -0700
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (10.120.60.153) by VMWEXCCAS09-PRD.hq.netapp.com (10.122.105.27) with Microsoft SMTP Server (TLS) id 15.0.1210.3 via Frontend Transport; Wed, 12 Jul 2017 01:21:26 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netapp.onmicrosoft.com; s=selector1-netapp-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=0ari9PQhKfRp3k+eMZYSprpyrOYnrxWOqn9Xwn7359s=; b=cMA2+rpnP1Tz/412dJc9/h2fC2tyQLnuon9fxhVgnlpOFkKTUrsFS9HuqfGEKsg5iunfPw0UBYtjh0K2jghowHqmb4CsP97mHXdlY/y7VNuQcSLjSfOYz06BAQ8zNpZ2uy0AZbW9NMX+Io8UmNOYwg+1fygXA/oOO4lqHo+ECIU=
Received: from BLUPR06MB1764.namprd06.prod.outlook.com (10.162.224.150) by BLUPR06MB1764.namprd06.prod.outlook.com (10.162.224.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1261.13; Wed, 12 Jul 2017 08:21:26 +0000
Received: from BLUPR06MB1764.namprd06.prod.outlook.com ([10.162.224.150]) by BLUPR06MB1764.namprd06.prod.outlook.com ([10.162.224.150]) with mapi id 15.01.1261.015; Wed, 12 Jul 2017 08:21:26 +0000
From: "Eggert, Lars" <lars@netapp.com>
To: Orit Levin <oritl@microsoft.com>
CC: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-tcpm-dctcp.all@tools.ietf.org" <draft-ietf-tcpm-dctcp.all@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Gen-ART Last Call review of draft-ietf-tcpm-dctcp-07
Thread-Topic: Gen-ART Last Call review of draft-ietf-tcpm-dctcp-07
Thread-Index: AdLnXhfXFS3sUvXFRwmmocCfhO+vxATicI6A
Date: Wed, 12 Jul 2017 08:21:26 +0000
Message-ID: <2160AFCF-D2A9-4443-AA98-04109FFA514E@netapp.com>
References: <BN6PR03MB2612D009D446DBCF899488DBADC60@BN6PR03MB2612.namprd03.prod.outlook.com>
In-Reply-To: <BN6PR03MB2612D009D446DBCF899488DBADC60@BN6PR03MB2612.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3273)
authentication-results: microsoft.com; dkim=none (message not signed) header.d=none;microsoft.com; dmarc=none action=none header.from=netapp.com;
x-originating-ip: [217.70.211.15]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BLUPR06MB1764; 7:H49yocyK1XyFcPhE0yr5TGNBOHmF/xvnD4Gmh1Xi2TbaYJhyYpfbUq7Ao9OpNDZCuDdlVArhNQuEKYseNZYZ4FDizpy4xvPy/GhjTvrWvpPcQgEn+ZdEE3OeXnyfA0+TGw210MLBfS3sb70uHMc2eyH+Y+KMvNHrQLvTScnaRZyFAmmJf+9e15iiYJDDPhqtQDlZSefkIhEF/GQS0kDlBRdOikXM4zuejgUgoQxlznbB7i8l9MrAHnMkxBq26y7m2C+mg5d/5KoRGacmABlgGVjarDQj0OeBrcFYdJ6lmHGvjcSLelrAetYLUb4qgrQuBhKUsTJzDUUNpGIJCa2Sgf7l+MSvY0JfdIki08IYCCV30gObvAwwm2EkUKf/f8D+a/pw0YyRZlKnaTdzKr+L+qFaSc5j6icdG/qH2TMVv5omoTVPFrpWAspLEnMCInF2Plb2FAOh9R3unGl471ofMeJoiGxdfOT90DSUPImwTIzKlOkKvgtrlCeax7b5ojeKABaqFS59Qg03nOifvRhgIyEtSKkmV7oUItPb7GO7MEGtV+7XRJxbn4lHtdtjz2oSpOKvdNdRJgzqFxyCrTu37D2Qsoas9tIhtfIEChVRYbqgYJ/uNX2e9k/R2TM+WWreT+OAvyh6Was929PBjbUZCl6Xr/6N9vK0kHjzB375zUURShYKGtHphQ+/rpkLM0cAf4NRzGmyaUP2AHdDIIgylzKj8xibpAB1ekrbM0sbjVOPARJ8B3ZHyfPOQIqUnVTu+iN3//MbQvP89oXKlnQeHRJzfL9KDMGeeKbsBoZezIk=
x-ms-office365-filtering-correlation-id: ecc5d44f-76af-4118-451f-08d4c8fefd44
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(300000503095)(300135400095)(2017052603031)(49563074)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:BLUPR06MB1764; 
x-ms-traffictypediagnostic: BLUPR06MB1764:
x-exchange-antispam-report-test: UriScan:(48057245064654);
x-microsoft-antispam-prvs: <BLUPR06MB1764B0CA578AA8B39A080973A7AF0@BLUPR06MB1764.namprd06.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(102415395)(6040450)(601004)(2401047)(2017060910075)(5005006)(8121501046)(3002001)(100000703101)(100105400095)(10201501046)(93006095)(93001095)(6055026)(6041248)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123560025)(20161123562025)(20161123558100)(20161123555025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BLUPR06MB1764; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BLUPR06MB1764; 
x-forefront-prvs: 036614DD9C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39840400002)(39850400002)(39450400003)(39410400002)(39400400002)(5660300001)(77096006)(76176999)(50986999)(99936001)(3660700001)(7736002)(86362001)(305945005)(6916009)(3280700002)(110136004)(2421001)(38730400002)(2906002)(6246003)(81166006)(229853002)(8676002)(57306001)(50226002)(8936002)(2950100002)(189998001)(558084003)(2900100001)(6506006)(1511001)(14454004)(66066001)(6486002)(33656002)(83716003)(2561002)(478600001)(53936002)(54906002)(25786009)(82746002)(230783001)(99286003)(6512007)(6116002)(8666007)(36756003)(3846002)(102836003)(4326008)(6436002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR06MB1764; H:BLUPR06MB1764.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; boundary="Apple-Mail=_3CDAE271-75BB-45D9-9E7C-7E2068C60EAF"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Jul 2017 08:21:26.1190 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4b0911a0-929b-4715-944b-c03745165b3a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR06MB1764
X-OriginatorOrg: netapp.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ltIZXO6SqSgSp6YaUFM-Pbmr6X8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 08:26:30 -0000

--Apple-Mail=_3CDAE271-75BB-45D9-9E7C-7E2068C60EAF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

I missed your comments when I posted -08 - sorry! Will post -09 with =
fixes shortly.

Thanks,
Lars

--Apple-Mail=_3CDAE271-75BB-45D9-9E7C-7E2068C60EAF
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAlll3AUACgkQVLXDCb9w
wVeExBAAoD4EYOtKXjfdzn2BsOK6kl3s2Ud3noOEOkouXuAyAavAg86DDJW8dDR2
d/mC9oCYYFVaIzGbtonhc0gTJq3Gw26ORqYe/2bSovT7r9qjSYXf3MB1hkAUhKne
yqz3bIDFSsWXO12fQdlB/LJ/HrZHOeIPQvT3hiu+Zom1KRzpoDNA/6P1nplOnJ+/
aVJYc+2SVnzOmRTcf6OZhTSgZDg5cwOHDusQAdIMjS0jUX9SQsZdgqMJ/evITCuK
pdzN9fftmEeGh3W7YaYDDsQsiLJJdjlpv4PUibzuZr4s0QQbwboUXZsJGpTx5ByM
SEafCCkfC+bpMsNDrzN4KbYjmvr3WUBrehIadOVSD2h/LtK1AnpXQtDwQKM+lTqa
fPtI+fLf5OCKO8O2p8lfj+aB+gbZoiklUmmeUBaZ/1hVlRgPu1DYAmoN58Ye8V2I
Dr45DYac7z1L0Y+YZldH3EmFEtOeTAxFZpJFvJP/KzhKCePJxVtnCP/CiPsAOHf0
tQ47PqljbfdV4Thr5qlbljy7jbbEkCYwciYH9Wqen3xNPGcXIv9Vc1ZY1MSZEV6f
olb5qOzePx85/VsBSWJuN2ndBd4wUEYVd7ey8M2A6FO4JHIwrlKXo32l+mSF+JUq
EJWrxX10RCO0OyDvBZd9HOFG9gDkNP4aPA5ccUfb7jgJs2INFYE=
=zg2L
-----END PGP SIGNATURE-----

--Apple-Mail=_3CDAE271-75BB-45D9-9E7C-7E2068C60EAF--


From nobody Wed Jul 12 01:26:45 2017
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBEB0126E64; Wed, 12 Jul 2017 01:26:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netapp.onmicrosoft.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 JrkHcj7vPVgA; Wed, 12 Jul 2017 01:26:29 -0700 (PDT)
Received: from mx143.netapp.com (mx143.netapp.com [216.240.21.24]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFDA7131839; Wed, 12 Jul 2017 01:26:28 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.40,349,1496127600";  d="asc'?scan'208";a="205398515"
Received: from hioexcmbx07-prd.hq.netapp.com ([10.122.105.40]) by mx143-out.netapp.com with ESMTP; 12 Jul 2017 01:00:56 -0700
Received: from VMWEXCCAS10-PRD.hq.netapp.com (10.122.105.28) by hioexcmbx07-prd.hq.netapp.com (10.122.105.40) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 12 Jul 2017 01:21:29 -0700
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (10.120.60.153) by VMWEXCCAS10-PRD.hq.netapp.com (10.122.105.28) with Microsoft SMTP Server (TLS) id 15.0.1210.3 via Frontend Transport; Wed, 12 Jul 2017 01:21:28 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netapp.onmicrosoft.com; s=selector1-netapp-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=rOzZoUb0wa/lERURKiy3Q6NpcpyPooiK1/WxtUE3yEM=; b=I5UeTss83swC4T1IS7vRNViOiI4DF0KaMMzzUftq/kt+QgxLuUHTHKdFGSES50hs2ieCFZJxqSX/uNaqsp949U16hRaWUbQAbLMbvRVVXW8zwm2SEtfxBLNXnsXa3WPiWHwMycedvOVTdUTHTOSLXYWkirHjO0n8IP5FDo44ZfY=
Received: from BLUPR06MB1764.namprd06.prod.outlook.com (10.162.224.150) by BLUPR06MB1764.namprd06.prod.outlook.com (10.162.224.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1261.13; Wed, 12 Jul 2017 08:21:29 +0000
Received: from BLUPR06MB1764.namprd06.prod.outlook.com ([10.162.224.150]) by BLUPR06MB1764.namprd06.prod.outlook.com ([10.162.224.150]) with mapi id 15.01.1261.015; Wed, 12 Jul 2017 08:21:29 +0000
From: "Eggert, Lars" <lars@netapp.com>
To: Joe Clarke <jclarke@cisco.com>, Praveen Balasubramanian <pravb@microsoft.com>
CC: "ops-dir@ietf.org" <ops-dir@ietf.org>, "draft-ietf-tcpm-dctcp.all@ietf.org" <draft-ietf-tcpm-dctcp.all@ietf.org>, "tcpm@ietf.org" <tcpm@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Opsdir last call review of draft-ietf-tcpm-dctcp-07
Thread-Topic: Opsdir last call review of draft-ietf-tcpm-dctcp-07
Thread-Index: AQHS4G9uEHRke2qlCUmwiw4BRirK9aJQDtgA
Date: Wed, 12 Jul 2017 08:21:29 +0000
Message-ID: <D0745B0D-8622-41C9-B547-AD3D59BC36D5@netapp.com>
References: <149693721791.15103.13571928856211954021@ietfa.amsl.com>
In-Reply-To: <149693721791.15103.13571928856211954021@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3273)
authentication-results: cisco.com; dkim=none (message not signed) header.d=none;cisco.com; dmarc=none action=none header.from=netapp.com;
x-originating-ip: [217.70.211.15]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BLUPR06MB1764; 7:g3MrsLG/r3DPparR5UAtNYol79rral1MyGqbEyicmOBKogWCG80g0YlDKy2NUw3Jp+0rsEXbHHN1M7uP1kq9KabMkbttP/7S/DecItTrUupOT3UEkLDYYDdwcd+HT5Xbd+QFsohzyhv4O+ocTDnQC6P8/k4KLAy4QYDjh0ihXc9EXcYNqif/526Ew3zjmc/8wS0Dw0HXuqP/811mdUWIzamcf39CTVDpF807sD4Qmv1O8osZ6S4pzqdzgnEmdma+U9avxIxkAxYU8u9AjpMqr+NuwZustiuCQNu1s6eWPXefu17yFNZmF4Pl32bvT3G8TgtlGhJ3l2vgmkqSjyO2W0pOh7nJkKqgfHYS5aj03jFrYfAxgzHoVbDgWhmqW0WWC5yeae1hipOfMi2hNuxZWE0ScTtF9YDaEDkmkfAneWNvK38QDLFVRcTHLpr4r0QGMcCf7uRb0/eGlqyyIYLd5qs1Wxzbtn0lwfSwXUImTj3SVsoTzPnOs8XFAoIxmqQqtAf7LYPtzGMpUg0t/tEWo8fTgExXZOsqKe04qmw0mDjK4Fjf8ijjgikqVS53/8BWGrQHbC9GNaS54DX37qcjVRkMdS22hI5gve74o8EjUe4AhfLSgGp+EF412GsATz5YoMRlxTFoSaGYfZIt1AVgZz93fHs7cZvEsGsFIVdxVmaWjbSO4uU+wJOsfPUxuiHQVlqA0W0NYbIZD8adJS9U9uC8PGXs4YOqCZzZtcqXuJ1dqxWXWS9Q4ixRSw0JUdrnsFSz65IrJpVQzx5FMP6j7CQm162gIfIm1wHTzrB9RkM=
x-ms-office365-filtering-correlation-id: c20f91ad-a056-4323-e539-08d4c8feff25
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(300000503095)(300135400095)(2017052603031)(49563074)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:BLUPR06MB1764; 
x-ms-traffictypediagnostic: BLUPR06MB1764:
x-exchange-antispam-report-test: UriScan:(236129657087228)(48057245064654)(148574349560750)(247924648384137); 
x-microsoft-antispam-prvs: <BLUPR06MB1764AFE3D7DFC3326083A60DA7AF0@BLUPR06MB1764.namprd06.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(102415395)(6040450)(601004)(2401047)(2017060910075)(5005006)(8121501046)(3002001)(100000703101)(100105400095)(10201501046)(93006095)(93001095)(6055026)(6041248)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123560025)(20161123562025)(20161123558100)(20161123555025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BLUPR06MB1764; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BLUPR06MB1764; 
x-forefront-prvs: 036614DD9C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39840400002)(39850400002)(39450400003)(39410400002)(39400400002)(5660300001)(77096006)(76176999)(50986999)(99936001)(3660700001)(7736002)(86362001)(305945005)(3280700002)(2421001)(38730400002)(2906002)(6246003)(81166006)(229853002)(8676002)(57306001)(50226002)(8936002)(2950100002)(189998001)(2900100001)(6506006)(1511001)(14454004)(66066001)(6486002)(33656002)(83716003)(2561002)(478600001)(53936002)(54906002)(25786009)(82746002)(230783001)(99286003)(6512007)(6116002)(8666007)(36756003)(3846002)(102836003)(4326008)(6436002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR06MB1764; H:BLUPR06MB1764.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; boundary="Apple-Mail=_D50875DC-B86A-4D9A-BABD-23AF9365E104"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Jul 2017 08:21:29.3223 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4b0911a0-929b-4715-944b-c03745165b3a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR06MB1764
X-OriginatorOrg: netapp.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_XeOLCa0WtJQNOPovyeWOvx5nac>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 08:26:32 -0000

--Apple-Mail=_D50875DC-B86A-4D9A-BABD-23AF9365E104
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

I missed your comments when I posted -08 - sorry! Will post -09 with =
fixes shortly.

> You refer to DCTCP.Alpha before defining it.  While you refer to =
Section 3.3
> here, the impact of an incorrect Alpha value is not fully appreciated =
in this
> text.  Perhaps this could be changed to reflect the impact the =
incorrect Alpha
> value would have?

done

> My abbreviating DCTCP.CE as CE in your state machine diagram, it is a =
bit
> confusing as to the difference between CE and DCTCP.CE.  The =
description of the
> state machine above requires the CE codepoint to have a certain value =
in order
> for DCTCP.CE to change.  Perhaps you can use D.CE as an abbreviation =
to be a
> bit clearer here.

I used DCTCP.CE and did some reformatting

> It is not clear if 'g' can be inclusive of 0 and 1.

Nice catch. Clarified this in "Implementation Issues".

> You define DCTCP.WindowEnd as the threshold for beginning a new =
observation
> window, but maybe to complement the state variable name, you should =
define it
> as the following:
>=20
> The TCP sequence number threshold when one observation window ends and =
other is
> to begin; initialized to SND.UNA.

Applied your suggestion.

> Section 3.3:
>=20
> You state:
>=20
> Thus, when no bytes sent experienced congestion, DCTCP.Alpha equals
> zero, and cwnd is left unchanged
>=20
> But if I use a value of 1/16 for g, with DCTCP.Alpha initialized to 1 =
as you
> say, I get a value of DCTCP.Alpha =3D=3D 15/16 when there is no =
congestion (i.e., M
> =3D=3D 0).

Good catch. Checking with my co-authors what the thinking here was. =
There may be a condition missing. Praveen?

> You have an extra space here before the comma:

Already fixed in -08.

> You do not define ECT before using it.

> Can you provide a reference for NewReno?

Already fixed in -08.

> Can you reference or define AQM and RED?

Added refs to 2309 and 7567.

Thanks,
Lars

--Apple-Mail=_D50875DC-B86A-4D9A-BABD-23AF9365E104
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAlll3AgACgkQVLXDCb9w
wVffmA//Zx64d+fSvgqWSIWl6+KxBWweCvFKKLL2n+5vzPPOdUYT5dXSa9qjjRPQ
okv3lSHIxZSugKrWl4X8r0qso3x2YQViJ4KAtHJwPAFz72/tiPufcbneRs9X4iLs
5acE9c+ILc7LC2LPs14cdHR7Ozy4zHUPEe2SZu4zY8Z+IusI4ZZBjyfBmPTqGioh
bwUuGzoixkjldgBpTDPRPs/2Tm4LDJSkPq65gj3iRnFCEBo1eFyUyKm0d5sXo/ie
0GsFh4V9/xzpXb4IphIbnOc/KndqWtJ1Y2AQgvymuSQ3L7q8Ttd4XGO+jAorAOEh
ldiQoQco8OOzeSJG274XPBoyCkpdVxbx2om0aU8MrF7r5LT6rdetXRU+O4o1WRjW
nbVbwGX/lZEk0lHDk+22LQBFOCQMhYqbrlKEPKrrSQXK7QVBmG1+/Ww2wPvX6/J6
PCzeNvtHMx4a7HbJ04abXtZJAgrVtbahByAFBFuTGC1wWgIYIKrKoSFrlF6379cK
DRzK0QUxc+qiIRhV4n7LtfdtiTxAdiX+ZqjSUf2etdluln9HXlButBVRHS1JZL/0
wTlhjX8OEgRahiyM1oe5DClIJ2indOrbBibKAoZt67H9086NWuf0VaJAdvxC3pty
Mn5KKRquDjo2VFtEDZcdHt0s5wkT1lHggRnRbwguee8W56S91VQ=
=JRvq
-----END PGP SIGNATURE-----

--Apple-Mail=_D50875DC-B86A-4D9A-BABD-23AF9365E104--


From nobody Wed Jul 12 01:30:04 2017
Return-Path: <jclarke@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2578E128768; Wed, 12 Jul 2017 01:29:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 gvFKHBlqhums; Wed, 12 Jul 2017 01:29:54 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A288F126E64; Wed, 12 Jul 2017 01:29:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2388; q=dns/txt; s=iport; t=1499848194; x=1501057794; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=ZXNT1GwRZMItVKc2VElxbqWFjjxsjl7qs5/c6sR70I4=; b=kysHNi6CqDi/ZrosNlGoMNBYXXHp+ECGeMF+3pk6kQQrls1yKrw2lX/K A2PzAGI8NMaCkINDRoQwt6qKCCV4vOo0j1IQ2B2F9lUnlqas6A7Pzn9Iz IM0OLCeWJ/6eX3x30l2K/+zSqHKXG3RZgSyUmogq11/RJYhY/dJtEzzRy A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D8AAD23GVZ/5NdJa1dGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBg1pkjx2RTCKWA4IRhXYCg0U/GAECAQEBAQEBAWsohRgBAQEBAgF5EAs?= =?us-ascii?q?YHRFXBgEMCAEBiiMIrkaLIQEBAQEBAQEBAQEBAQEBAQEBASCDKINNggwLgm6Ea?= =?us-ascii?q?oV0AQSQVI5Uiw+JAIsmhn+VTR84gQpSIxWFWQIBHIIDJIhkAQEB?=
X-IronPort-AV: E=Sophos;i="5.40,349,1496102400"; d="scan'208";a="267105211"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Jul 2017 08:29:53 +0000
Received: from [10.82.241.248] (rtp-vpn2-504.cisco.com [10.82.241.248]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id v6C8TqQg010334; Wed, 12 Jul 2017 08:29:52 GMT
Subject: Re: Opsdir last call review of draft-ietf-tcpm-dctcp-07
To: "Eggert, Lars" <lars@netapp.com>, Praveen Balasubramanian <pravb@microsoft.com>
Cc: "ops-dir@ietf.org" <ops-dir@ietf.org>, "draft-ietf-tcpm-dctcp.all@ietf.org" <draft-ietf-tcpm-dctcp.all@ietf.org>, "tcpm@ietf.org" <tcpm@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
References: <149693721791.15103.13571928856211954021@ietfa.amsl.com> <D0745B0D-8622-41C9-B547-AD3D59BC36D5@netapp.com>
From: Joe Clarke <jclarke@cisco.com>
Organization: Cisco
Message-ID: <ce7c2406-3cdd-ea60-9170-ea888b43f0f0@cisco.com>
Date: Wed, 12 Jul 2017 04:29:52 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <D0745B0D-8622-41C9-B547-AD3D59BC36D5@netapp.com>
Content-Type: text/plain; charset=windows-1252
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wE_dnj0oa1Yrqs6aKBF_HBSVzaU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 08:29:56 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 7/12/17 04:21, Eggert, Lars wrote:
> Hi,
> 
> I missed your comments when I posted -08 - sorry! Will post -09
> with fixes shortly.

Thanks, Lars.  Looking forward to the new version.

Joe

> 
>> You refer to DCTCP.Alpha before defining it.  While you refer to
>> Section 3.3 here, the impact of an incorrect Alpha value is not
>> fully appreciated in this text.  Perhaps this could be changed to
>> reflect the impact the incorrect Alpha value would have?
> 
> done
> 
>> My abbreviating DCTCP.CE as CE in your state machine diagram, it
>> is a bit confusing as to the difference between CE and DCTCP.CE.
>> The description of the state machine above requires the CE
>> codepoint to have a certain value in order for DCTCP.CE to
>> change.  Perhaps you can use D.CE as an abbreviation to be a bit
>> clearer here.
> 
> I used DCTCP.CE and did some reformatting
> 
>> It is not clear if 'g' can be inclusive of 0 and 1.
> 
> Nice catch. Clarified this in "Implementation Issues".
> 
>> You define DCTCP.WindowEnd as the threshold for beginning a new
>> observation window, but maybe to complement the state variable
>> name, you should define it as the following:
>> 
>> The TCP sequence number threshold when one observation window
>> ends and other is to begin; initialized to SND.UNA.
> 
> Applied your suggestion.
> 
>> Section 3.3:
>> 
>> You state:
>> 
>> Thus, when no bytes sent experienced congestion, DCTCP.Alpha
>> equals zero, and cwnd is left unchanged
>> 
>> But if I use a value of 1/16 for g, with DCTCP.Alpha initialized
>> to 1 as you say, I get a value of DCTCP.Alpha == 15/16 when there
>> is no congestion (i.e., M == 0).
> 
> Good catch. Checking with my co-authors what the thinking here was.
> There may be a condition missing. Praveen?
> 
>> You have an extra space here before the comma:
> 
> Already fixed in -08.
> 
>> You do not define ECT before using it.
> 
>> Can you provide a reference for NewReno?
> 
> Already fixed in -08.
> 
>> Can you reference or define AQM and RED?
> 
> Added refs to 2309 and 7567.
> 
> Thanks, Lars
> 

-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQTMiWQHc8wChijkr7lvaI+K/hTPhwUCWWXd/AAKCRBvaI+K/hTP
h8BMAKCQ0rdNKc9t9MDV1EqMpcJwiDasNACeJlq8ocdUfe417DJ6BdAMErMmv7Y=
=Zgwv
-----END PGP SIGNATURE-----


From nobody Wed Jul 12 01:37:14 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76973131895 for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 01:37:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 bYf3zHwCyYHs for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 01:37:04 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 8538D13189A for <ietf@ietf.org>; Wed, 12 Jul 2017 01:37:04 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dVD8p-00028Z-3k for ietf@ietf.org; Wed, 12 Jul 2017 08:37:03 +0000
Date: Wed, 12 Jul 2017 10:37:00 +0200
Message-ID: <m2bmoqvyoj.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: meeting ietf-legacy ssid
In-Reply-To: <EC1FFD9E-F9FA-4780-B279-A71AB93A57FD@shrubbery.net> <180e5a78-603f-6038-3bcd-60758d8f03d4@cisco.com> <432404b3-49aa-69fb-cdbb-0224f1b6b5eb@huitema.net>
References: <m2eftmwl0l.wl-randy@psg.com> <EC1FFD9E-F9FA-4780-B279-A71AB93A57FD@shrubbery.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/b_LwMa_An4JBpET77JqkCu8DVyY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 08:37:09 -0000

On Wed, 12 Jul 2017 07:38:20 +0200, a linux hacker wrote privately:
> 
> Ive used it because my linux laptop wouldnt bind to anything else. Not
> sure why.

this is a case that worries me deeply.  folk with issues should visit
the help desk in the terminal-less room or visit the noc.

On Wed, 12 Jul 2017 07:54:44 +0200, Eliot Lear wrote:
>
> Why not just turn it off and see what happens?

because the noc thinks of the attendees as those strange critters called
"customers."  this creates implications for service continuity.

On Wed, 12 Jul 2017 08:46:11 +0200, Christian Huitema wrote:
> 
> You may want to tabulate the OS version of the devices on the
> un-encrypted network. Can your DHCP server do that? That should give you
> some indication.

i proposed measuring a number of aspects of use of ietf-legacy, mostly
port use; wanting to get a feel if the use was protected above layer
three.  i specifically avoided proposing looking inside the packsts as i
do not have time to deal rigorously with the PII issues.  when i asked
if i could measure port use, i was asked to write up a formal project
description.  as this is not my paying $dayjob, i hit delete.

for me, the botttom line here is

   please try networks other than ietf-legacy.  if you have problems
   which drive you to legacy, please come to the noc and debug.

   this is something to be revisited when we know more.

thanks for the clues.

randy


From nobody Wed Jul 12 02:30:07 2017
Return-Path: <nick@foobar.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67DF2131899 for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 02:30:04 -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 bMgpnKCVOgba for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 02:30:02 -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 59D8A13182A for <ietf@ietf.org>; Wed, 12 Jul 2017 02:30:01 -0700 (PDT)
X-Envelope-To: ietf@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 v6C9Ts10028236 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 12 Jul 2017 10:29:55 +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: <5965EC12.7040905@foobar.org>
Date: Wed, 12 Jul 2017 10:29:54 +0100
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.15 (Macintosh/20170609)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: Randy Bush <randy@psg.com>, IETF discussion list <ietf@ietf.org>
Subject: Re: meeting ietf-legacy ssid
References: <m2eftmwl0l.wl-randy@psg.com> <e6a9d5b5-f50b-c0ec-fcf8-1a2d036c9421@gmail.com>
In-Reply-To: <e6a9d5b5-f50b-c0ec-fcf8-1a2d036c9421@gmail.com>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JdxK8eaKu-J0PL8R-e1rFO_yR2I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 09:30:04 -0000

Brian E Carpenter wrote:
> Jordi is correct about the ordering of SSIDs in the list kept by the
> o/s. If you don't manually push ietf-legacy down the list, it may well
> be picked automatically.

At RIPE meetings, they work around this by having a unique legacy SSID
per meeting, which has driven down usage noticeably.

Nick


From nobody Wed Jul 12 03:09:03 2017
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FADB1296C9 for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 03:09:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.503
X-Spam-Level: 
X-Spam-Status: No, score=-14.503 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_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 gOyJtv2pgIpj for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 03:09:00 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A974E126B72 for <ietf@ietf.org>; Wed, 12 Jul 2017 03:08:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2254; q=dns/txt; s=iport; t=1499854139; x=1501063739; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=z10SAgAxx62QmBDXGm1403b1u8SWWGLEjf94j71ZUTM=; b=J0SHeBIyT8iXw+r0dLot+PamLcMCdwY944pDVUJcHFmMCAVsbD7km/1b fUOxeG+pIUjiDKuEEu53MiC3kpZADjSn9+8OSzVeZuZfT7pzODNKNZvLp /hNkJC9BJTTPIQb+3QogUMfbnxn5RLzLQvo+y/E+xjx7VHPpv2cKkDL44 I=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CMAADY9GVZ/xbLJq1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBk1tzkH2WA4IRB4VvAoQHGAECAQEBAQEBAWsohRkBBSNmCxgqAgJ?= =?us-ascii?q?XBgEMCAEBiiusR4ImiyIBAQEBAQEBAwEBAQEBAQESD4MohVmCeYd9gmEBBJ8oh?= =?us-ascii?q?CqCHY1IiyaGf5VNHziBCjEhCBsVhVwcgWk+iGQBAQE?=
X-IronPort-AV: E=Sophos;i="5.40,349,1496102400";  d="asc'?scan'208";a="695760117"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Jul 2017 10:08:48 +0000
Received: from [10.61.241.136] ([10.61.241.136]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v6CA8m8O014355; Wed, 12 Jul 2017 10:08:48 GMT
Subject: Re: meeting ietf-legacy ssid
To: Randy Bush <randy@psg.com>, IETF Rinse Repeat <ietf@ietf.org>
References: <m2eftmwl0l.wl-randy@psg.com> <EC1FFD9E-F9FA-4780-B279-A71AB93A57FD@shrubbery.net> <m2bmoqvyoj.wl-randy@psg.com>
From: Eliot Lear <lear@cisco.com>
Message-ID: <8f92a3c0-084d-973e-e805-632d0352c115@cisco.com>
Date: Wed, 12 Jul 2017 12:08:47 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <m2bmoqvyoj.wl-randy@psg.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="TrJHndS6cvsxtxQhT5NxE8UPR63SIpdq1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WwsaCx7YwfPXToG3kcBd7KfOgZ4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 10:09:01 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--TrJHndS6cvsxtxQhT5NxE8UPR63SIpdq1
Content-Type: multipart/mixed; boundary="0lMEfhkJhGX2FEDb594NCK401RnUd1DCB";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: Randy Bush <randy@psg.com>, IETF Rinse Repeat <ietf@ietf.org>
Message-ID: <8f92a3c0-084d-973e-e805-632d0352c115@cisco.com>
Subject: Re: meeting ietf-legacy ssid
References: <m2eftmwl0l.wl-randy@psg.com>
 <EC1FFD9E-F9FA-4780-B279-A71AB93A57FD@shrubbery.net>
 <m2bmoqvyoj.wl-randy@psg.com>
In-Reply-To: <m2bmoqvyoj.wl-randy@psg.com>

--0lMEfhkJhGX2FEDb594NCK401RnUd1DCB
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US

Hi Randy,

If you want to run experiments, I think that's fine, personally.  But as
to this:

On 7/12/17 10:37 AM, Randy Bush wrote:
> On Wed, 12 Jul 2017 07:54:44 +0200, Eliot Lear wrote:
>> Why not just turn it off and see what happens?
> because the noc thinks of the attendees as those strange critters calle=
d
> "customers."  this creates implications for service continuity.

The rest of the world who aren't engineers seem to manage ok with WPA.=20
Unless there is an accessibility requirement hidden here.  Another
approach: turn -legacy into a hotel network and simply ask people why
they're not using the other.  Not the most secure way to go about
things, but again, we're supposed to have a clue.

Eliot



--0lMEfhkJhGX2FEDb594NCK401RnUd1DCB--

--TrJHndS6cvsxtxQhT5NxE8UPR63SIpdq1
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

iQEcBAEBCAAGBQJZZfUvAAoJEIe2a0bZ0nozHI4IALTptpEZEIJGf3q4i5Cp3Hzy
dH7B4a0bKbIRlhF6r84LVk+vJFCiIVPho9HlxVATxFgWOLzuWOOuhp02nbgcGH3I
WlCSHMubWqQt0xMx5NkqAN2kL+5TVuvdQY+wrqq1DA2wOg+pN4maFcLfRxxiW6NZ
UHcolYYeIV2EFUhC8QA+9ElWW45lalJ3UaXEbsR1zs2d0qVQyWSmEiOfp4c/KR/2
CtUoj8rn2smbzahT8sGsycFc+/gsQDF40nrobwP5mpxtR/7s7bQ2SKXyBXNfrsjL
J9ciWrl10RfhptzFfSDHOSf9bNMDTeuFk71+/uBtnwOw2UG1dCfHWmt5m+ftu24=
=W09d
-----END PGP SIGNATURE-----

--TrJHndS6cvsxtxQhT5NxE8UPR63SIpdq1--


From nobody Wed Jul 12 03:23:58 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1905812EC0F for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 03:23:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 Q8qDQLG2Tiwr for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 03:23:56 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 8DC4D12EBFA for <ietf@ietf.org>; Wed, 12 Jul 2017 03:23:54 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dVEoB-0002yR-Eb; Wed, 12 Jul 2017 10:23:51 +0000
Date: Wed, 12 Jul 2017 12:23:50 +0200
Message-ID: <m2tw2iuf61.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Nick Hilliard <nick@foobar.org>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF discussion list <ietf@ietf.org>
Subject: Re: meeting ietf-legacy ssid
In-Reply-To: <5965EC12.7040905@foobar.org>
References: <m2eftmwl0l.wl-randy@psg.com> <e6a9d5b5-f50b-c0ec-fcf8-1a2d036c9421@gmail.com> <5965EC12.7040905@foobar.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Wi_zlmMclDyer4dewWai5Oi5i_4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 10:23:57 -0000

>> Jordi is correct about the ordering of SSIDs in the list kept by the
>> o/s. If you don't manually push ietf-legacy down the list, it may well
>> be picked automatically.
> 
> At RIPE meetings, they work around this by having a unique legacy SSID
> per meeting, which has driven down usage noticeably.

/me likes

should not break anyone; though takes thought starting up if you want to
run nekkid.  that's kind of a feature.


From nobody Wed Jul 12 03:50:10 2017
Return-Path: <zhangmingui@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32036126B72; Wed, 12 Jul 2017 03:50:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.222
X-Spam-Level: 
X-Spam-Status: No, score=-4.222 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, RP_MATCHES_RCVD=-0.001, 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 Yswg3zJgAtN6; Wed, 12 Jul 2017 03:50:05 -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 B148E12ECCB; Wed, 12 Jul 2017 03:50:04 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DQY79039; Wed, 12 Jul 2017 10:50:02 +0000 (GMT)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 12 Jul 2017 11:50:02 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0235.001; Wed, 12 Jul 2017 18:49:56 +0800
From: "Zhangmingui (Martin)" <zhangmingui@huawei.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, "tsv-art@ietf.org" <tsv-art@ietf.org>
CC: "draft-ietf-trill-mtu-negotiation.all@ietf.org" <draft-ietf-trill-mtu-negotiation.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "trill@ietf.org" <trill@ietf.org>
Subject: RE: Tsvart telechat review of draft-ietf-trill-mtu-negotiation-06
Thread-Topic: Tsvart telechat review of draft-ietf-trill-mtu-negotiation-06
Thread-Index: AQHS9Y7xZDZHsOYJgke3/J9kjsDvXqJJJE3fgANWXoCAA4UoSg==
Date: Wed, 12 Jul 2017 10:49:55 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E7A6548A27@NKGEML515-MBX.china.huawei.com>
References: <149925973580.17545.6979655005275084891@ietfa.amsl.com> <4552F0907735844E9204A62BBDD325E7A6546EF1@NKGEML515-MBX.china.huawei.com>, <1419a786-f8c4-ad1b-1fb0-9e4562939445@ericsson.com>
In-Reply-To: <1419a786-f8c4-ad1b-1fb0-9e4562939445@ericsson.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.110.244]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090202.5965FEDB.0025, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 1adcb1bec569771c5316c707b7db5434
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PGPVQXaQWlegQCW3luo-LWDSyKk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 10:50:09 -0000

Hi Magnus,=20

Thanks for your further comments. Please see my responses inline below.

________________________________________
From: Magnus Westerlund [magnus.westerlund@ericsson.com]
Sent: Monday, July 10, 2017 20:13
To: Zhangmingui (Martin); tsv-art@ietf.org
Cc: draft-ietf-trill-mtu-negotiation.all@ietf.org; ietf@ietf.org; trill@iet=
f.org
Subject: Re: Tsvart telechat review of draft-ietf-trill-mtu-negotiation-06

Den 2017-07-08 kl. 07:57, skrev Zhangmingui (Martin):
> Hi Magnus,
>
> Thanks for your careful review. Please see the reponses inline below.
>
> ________________________________________
> From: Magnus Westerlund [magnus.westerlund@ericsson.com]
> Sent: Wednesday, July 05, 2017 21:02
> To: tsv-art@ietf.org
> Cc: draft-ietf-trill-mtu-negotiation.all@ietf.org; ietf@ietf.org; trill@i=
etf.org
> Subject: Tsvart telechat review of draft-ietf-trill-mtu-negotiation-06
>
> Reviewer: Magnus Westerlund
> Review result: Not Ready
>
> This TSV-ART review is influenced by that I did the review of
> draft-ietf-trill-over-ip.
>
> 1. So draft-ietf-trill-over-ip-10 has MTU discovery needs for
> determining if the UDP encapsulation will work or not. It references  in
> Section 8.4 the old RFC, i.e. RFC 6325, which is updated by
> draft-ietf-trill-mtu-negotiation.
>
>      TRILL IS-IS MTU PDUs, as specified in Section 5 of [RFC6325] and in
>      [RFC7177], can be used to obtain added assurance of the MTU of a
>      link.
>
> However, this is not quite true, as if the IP path MTU is below 1470
> bytes, which is not unheard of, the algorithm in the MTU negotiation
> draft can't determine it. It will only report the IP path as having an
> MTU to small when the 1470 bytes probe fail.
>
> [Mingui]   I copied the relevant text from RFC 6325.
>      "The desired minimum acceptable inter-RBridge link MTU for the
>        campus, that is, originatingLSPBufferSize.  This is a 16-bit
>        unsigned integer number of octets that defaults to 1470 bytes,
>        which is the minimum valid value.  Any lower value being
>        advertised by an RBridge is ignored."
> So the minimum value of Sz would be 1470. IOW, IP path with MTU below 147=
0 will not be qualified as an adjaceny of the TRILL network topology.

So this issue (1) is mostly bringing up what I saw as an discrepancy
between trill-over-ip and this document. I think it is quite reasonable
to push the needed extensions for more generalized IP path MTU discovery
in the Trill context onto the trill-over-ip document. However, I want to
note that from my perspective if one think one can run Trill-over-IP
then one better have a mechanism that can do fragmentation and
reassembly to handle IP MTUs that will not let trill packets of 1470
bytes through as that is quite common, in fact IPv6/UDP/Trill over
regular ethernet with 1500 bytes IP MTU is sufficient to fail that
criteria.

[Mingui] I think the MTU for a TRILL-over-IP link with under layer IP-MTU=
=3D1470 is actually more than 1470 if fragmentation and reassembly is suppo=
rted. This had been explained in paragraph 2 of Section 8.4 in the TRILL ov=
er IP draft.

>
> So, if the trill-over-ip authors want to use this as a mechanism, then th=
e MTU
> negotiation draft needs to be expanded to have more flexible lower
> boundaries. However, that appear to affect MTU negotiation quite
> significant as it needs to separate algorithm for finding MTU, from the
> different usage of the algorithm with different starting points. Where
> the normal will have a lower bound of 1470, and be more tightly coupled
> to Sz when finding Lz. While the Trill-over-IP has a different usage.
>
> I think the trill WG needs to decide on how to slice this. If the
> MTU-negotiation only targets the explicit targets in the current draft an=
d goes
> forward now. Or if they want to meet trill-over-ip's goals which will req=
uire
> restructuring.
>
> 2. Another issue, is that I think the algorithm is a bit short on
> transmission scheduling recommendations:
>
>      1) If RB1 successfully receives the MTU-ack from RB2 to the probe of
>         the value of link-wide Lz within k tries (where k is a
>         configurable parameter whose default is 3), link MTU size is set
>         to the size of link-wide Lz and stop.
>
> If I do this test with all three packets back to back at line rate, I cou=
ld
> potentially get all probes lost in the same burst loss in router queue or
> switch fabric. What I think is needed here is a specification on how thes=
e
> probes are transmitted. Spaced in a particular way, or at least minimal
> distance, and are the additional probes only sent after the previous has =
been
> judged to have been lost, which makes it interact with the next issue.
>
> [Mingui] This seems an implementation space. However, the document may of=
fer recommendations. The being recommended minimum interval between two suc=
cessive probes would affect the boot up speed of a TRILL campus. One RTT is=
 a reasonable value.

Okay, for this there might be some implementation variations. However,
it can clearly affect the performance of the implementation so some
recommendation are likely good. I also think a spacing of one per RTT is
quite reasonable. However, that leads to the question, how does the
sender know what RTT there is? Is there something in the TRILL protocol
that will determine the RTT and have a current value? Sorry, I don't
have time to digest the whole TRILL suit of specifications.

[Mingui] I think the typical RTT value should be used as a default but conf=
igurable value. Operators can determine and change it by using "ping" tools=
.

>
> 3. This is also unclear on what the criteria is for determining that some=
thing
> is lost:
>
>        a) If RB1 fails to receive an MTU-ack from RB2 after k tries, RB1
>            sets the "failed minimum MTU test" flag for RB2 in RB1's Hello
>            and stop.
>
> I fail to see any specification for the criteria when an MTU-ack should b=
e
> considered to have failed to reach the probing entity. So this appear to
> require a timeout, and thus a timeout interval. Is the RTT known so that =
one
> can define something as lost after N*RTT? Are there possible delays in se=
nding
> the MTU-ack that are considered okay that can affect this?
>
> [Mingui] Yes, this makes sense. An MTU-ack should be considered to have f=
ailed two RTT after the probe is sent out.

So two questions on this. First, can a receiver know which MTU probe it
gets response to, i.e. are there some token or sequence number being
acked?=20

[Mingui] No, there is no such thing which would make the test too complicat=
ed.=20

Second, 2*RTT appear to be to short to make that conclusion in.
The reasons I say so is that there will be networks where the jitter of
the path is larger than the RTT sample, thus leading to
misinterpretation.=20

[Mingui] The MTU messageas are exchanged between two adjacent RBridges rath=
er than a long-haul "path".  Note that, even the rare misinterpretation doe=
s occur, it will not fail the network. It will merely reduce the room for t=
he efficiency improvement.


Thus, I would recommend a bit more robustness to
misinterpretation and likely some minimal value that avoids low latency
paths wrongly classify the path. Note, I think it is needed to define
what the criteria is for when an MTU is considered lost, just because it
appears that it affects both startup and robustness of the probing. It
also becomes a question of what tools in the probes that are used for
this, and if you actually need some additional ones.

[Mingui] I think the method to detect the optimal RTTs for each link deserv=
es a separate document.

Thanks,
Mingui

>
> 4. Section 3, the algorithm in Step 1 is unable to reach the first termin=
ation
> condition (3) "If lowerBound >=3D upperBound" in some cases.
>
> [Mingui] This algorithm has been updated through a few rounds of revision=
s. Let me insert a few minor updates to the cited text as below.
>
>    Step 1: RB1 tries to send an MTU-probe padded to the size x.
>
>     1) If RB1 fails to receive an MTU-ack from RB2 after k tries:
>
>           upperBound is set to x and x is set to [(lowerBound +
>           upperBound)/2], rounded up to the nearest integer.
>
> [Mingui] s/uppperBound is set to x/uppperBound is set to x-1/
> [Mingui] s/rounded up to the nearest integer./rounded down to the nearest=
 integer./
>
>
>     2) If RB1 receives an MTU-ack to a probe of size x from RB2:
>
>           link MTU size is set to x, lowerBound is set to x and x is set
>           to [(lowerBound + upperBound)/2], rounded up to the nearest
>           integer.
>
> [Mingui] s/rounded up to the nearest integer./rounded down to the nearest=
 integer./
> [Mingui] Append one condistion to this step 2): If lowerBound equals uppe=
rBound-1 then x is set to upperBound.
>
>     3) If lowerBound >=3D upperBound or Step 1 has been repeated n times
>        (where n is a configurable parameter whose default value is 5),
>        stop.
>
>     4) Repeat Step 1.
>
> I run this on the input data: Lower bound =3D 1470, Upper bound =3D 9216 =
and with
> an MTU of 7935 and gets the following sequence:
>
> Lower   Upper   X
> 1470    9216    5343
> 5343    9216    7280
> 7280    9216    8248
> 7280    8248    7764
> 7764    8248    8006
> 7764    8006    7885
> 7885    8006    7946
> 7885    7946    7916
> 7916    7946    7931
> 7931    7946    7939
> 7931    7939    7935
> 7935    7939    7937
> 7935    7937    7936
> 7935    7936    7936
> 7935    7936    7936
>
> Thus, the termination condition needs to change.
>
> [Mingui] After the update of the text, the sequence would become:
> Lower   Upper   X
> 1470    9216    5343
> 5343    9216    7279
> 7279    9216    8247
> 7279    8246    7762
> 7762    8246    8004
> 7762    8003    7882
> 7882    8003    7942
> 7882    7941    7911
> 7911    7941    7926
> 7926    7941    7933
> 7933    7941    7937
> 7933    7936    7934
> 7934    7936    7935
> 7935    7936    7935
Shouldn't the above line result in that X becomes 7936, as the probe
before it succeeds, and then the new additional rule in step (2) then X
becomes upper bound.

> 7935    7936    7936
> 7935    7935    7935
>
> The second I notice is that having a limitation on number of steps as 5,
>
> [Mingui] Since the testing might be too resource consuming, implementors =
suggested this limitation. Afterall, the purpose of testing a Lz value is t=
o improve the efficiency (if Lz > Sz) rather than reach the optimal efficie=
ncy.

Ok.

>
> results in quite a large gap
> between upper and lower bound in which the MTU exists in.
>
> 5. I frankly gets confused by the application of the binary search. First=
 it
> will in many case not be run to termination where the actual MTU is deter=
mined.
> Then the result of the upper and lower bound are just used to confirm the=
 Sz
> value. There are no discussion about using the MTU search to determine a =
new
> possible value for Sz.
>
> [Mingui] Because the MTU search will NOT be used to determine a new possi=
ble value for Sz. It is only applicable to Lz.
>
>   The text is not even explicit that lower bound is the
> highest known to work Transmission unit size at the time of testing. I th=
ink
> section 3, should conclude in determine some TU value, and if that is Sz =
or
> something other appears quite relevant for what to do in the later sectio=
ns.
>
> [Mingui] As specified in Section 3, =93link MTU size=94 is already set to=
 the lower bound. This tested =93link MTU size=94 is the =93TU=94 value. Th=
is value is potentially larger than Sz as explained in the introduction and=
 Section 2.
>

Ok, I think I am getting what the different values are for.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Media Technologies, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------=


From nobody Wed Jul 12 06:04:44 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78D3B130154 for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 06:04:42 -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, 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=fugue-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 3faobndVLaoh for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 06:04:41 -0700 (PDT)
Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (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 5C3BD131689 for <ietf@ietf.org>; Wed, 12 Jul 2017 06:04:41 -0700 (PDT)
Received: by mail-qk0-x233.google.com with SMTP id 16so21994338qkg.2 for <ietf@ietf.org>; Wed, 12 Jul 2017 06:04:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=PQSpfSH3+2UZ6+IkakoQCk2NzuXf3qXWw1X46TEGeH0=; b=uIUqpQzW/z09Dj8Y2bEYADYRb4bFy+NJCMXQULTa81szFxepEhw9+GDjNJBM/FEy9s ZjrQ0mKVyQpSbyZ9+QFtBdNMvhKLaE4kIpyzv79yXdz+2tTY73U2NrRfw6YSXgxR6ywQ 85bADwW2k8+VAA/MQIMjaNy77Z0KIAKfUHokRTXTXeQ4I5DkQeXO2rhpS/GtMmhOKu8K eczGqSb7nZymVKDV5zA+mu3PCjBZrq4sTlr2mB0pNZVWukcBJJ7tpApAwRrfiCVCT1rN NOq+Vs24Ky3PxJxHtvnPQm7S1an6biPLVsvSF68aLgV5oIX7wqdco1n95QhGRFN0oGjj MGAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=PQSpfSH3+2UZ6+IkakoQCk2NzuXf3qXWw1X46TEGeH0=; b=m+dQkczuZWJJABK3lhW1MfW0aVab+Bkz+MJRjLzfn+jYYY9VWY7cOcgcobaAq9bSIg gNxLsRnR5tz6bFmh//GpCXpV4O0GDd+hZjO9KgJAfXRFn1r6Mzt1/5VcvHZj3JsifUi8 ElbsTT+qo8kHdNuLTfv0kQU/qu4VvIRI8asKeKPxUtiV5j6GcW7tiZD5uOJPrhqwyXlh tCun//oMlgONlvDyT8AtWG7jx0Eajm7f8ZGuvkg0H5zdAUkr4SFGKFLHG4QzOhRlgxUn IyVQIZq/Yeq7U7lVuKCEGlFUdpBZtfP8EBg10zlIcg6o8lPy00kDaVzZkTfI450+nSfW txWg==
X-Gm-Message-State: AIVw110nKG5selXx6nR2jpLOD9ej9skL6gQfT0d+RA6GALEmoN6pqr1O UT53O+AIEaxDgnVk
X-Received: by 10.55.64.73 with SMTP id n70mr5770309qka.35.1499864680544; Wed, 12 Jul 2017 06:04:40 -0700 (PDT)
Received: from macbook-pro-6.w50.lede.home (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id v34sm1799200qtg.31.2017.07.12.06.04.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Jul 2017 06:04:38 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <B6FE3785-A975-4B31-95BB-30A849E51766@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_CD3CED41-E2B4-4137-8BC7-C236867C1C13"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: meeting ietf-legacy ssid
Date: Wed, 12 Jul 2017 09:04:36 -0400
In-Reply-To: <6A2F8BE0-4B60-4B55-AFA5-66F22BC6CB3C@gmail.com>
Cc: Brian Carpenter <brian.e.carpenter@gmail.com>, IETF <ietf@ietf.org>
To: Bob Hinden <bob.hinden@gmail.com>
References: <m2eftmwl0l.wl-randy@psg.com> <e6a9d5b5-f50b-c0ec-fcf8-1a2d036c9421@gmail.com> <6A2F8BE0-4B60-4B55-AFA5-66F22BC6CB3C@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JCFO9KHSkqdtyKtziBOlr8ylvh8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 13:04:42 -0000

--Apple-Mail=_CD3CED41-E2B4-4137-8BC7-C236867C1C13
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Jul 11, 2017, at 10:45 PM, Bob Hinden <bob.hinden@gmail.com> wrote:
> The IETF is telling the word it=E2=80=99s important to use encryption, =
we should be eating our own dog food.

Perhaps so, but if that's the case we might want to do real security and =
not universal-shared-symmetric-key security.   But I think the IETF =
generally takes the position that security is something that happens =
above layer 2, right?


--Apple-Mail=_CD3CED41-E2B4-4137-8BC7-C236867C1C13
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jul 11, 2017, at 10:45 PM, Bob Hinden &lt;<a =
href=3D"mailto:bob.hinden@gmail.com" =
class=3D"">bob.hinden@gmail.com</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">The IETF is telling the word it=E2=80=99s =
important to use encryption, we should be eating our own dog =
food.</span><br style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""></div></blockquote></div><br =
class=3D""><div class=3D"">Perhaps so, but if that's the case we might =
want to do real security and not universal-shared-symmetric-key =
security. &nbsp; But I think the IETF generally takes the position that =
security is something that happens above layer 2, right?</div><div =
class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_CD3CED41-E2B4-4137-8BC7-C236867C1C13--


From nobody Wed Jul 12 06:09:25 2017
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68CC11316BE for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 06:09:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
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 dvQukxN07OvQ for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 06:09:21 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEE911316A8 for <ietf@ietf.org>; Wed, 12 Jul 2017 06:09:20 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6CD9GB3003788; Wed, 12 Jul 2017 14:09:16 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v6CD9GB3003788
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1499864956; bh=/6Oo6hsNyrEUzPb96el42M2RN8c=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=CCHtW2aElqhS9/jQ4IFVJIFgDcvmiCVhdYt2aOgD5F9mixSwn9HR2oZo2cENNDaBq iNf0lM+2X1xCxCaSHIMqN3wDXDcXNGte0fkMRj0eRJhWV1KynFgd+ASEWU1RM7bKy1 oFkzjIVgCwK1DyvJ8wkceA2SZVCJyTLdRX3ZGSDk=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id y6BE9B0950705991C6 ret-id none; Wed, 12 Jul 2017 14:09:16 +0100
Received: from [10.5.91.245] ([217.33.22.114]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6CD96b8006693 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 12 Jul 2017 14:09:06 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: meeting ietf-legacy ssid
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <m2bmoqvyoj.wl-randy@psg.com>
Date: Wed, 12 Jul 2017 14:09:08 +0100
Cc: IETF Rinse Repeat <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|9524d679479c53e9c82dfaefd8777bc4y6BE9B03tjc|ecs.soton.ac.uk|C8A9ABDB-8B82-446C-AF61-82B03879EA28@ecs.soton.ac.uk>
References: <m2eftmwl0l.wl-randy@psg.com> <EC1FFD9E-F9FA-4780-B279-A71AB93A57FD@shrubbery.net> <m2bmoqvyoj.wl-randy@psg.com> <C8A9ABDB-8B82-446C-AF61-82B03879EA28@ecs.soton.ac.uk>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3273)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=y6BE9A095070599100; tid=y6BE9B0950705991C6; client=relay,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v6CD9GB3003788
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DJjkZj6mRbafcsDmxF_xzX4t-ik>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 13:09:23 -0000

> On 12 Jul 2017, at 09:37, Randy Bush <randy@psg.com> wrote:
>=20
> On Wed, 12 Jul 2017 07:38:20 +0200, a linux hacker wrote privately:
>>=20
>> Ive used it because my linux laptop wouldnt bind to anything else. =
Not
>> sure why.
>=20
> this is a case that worries me deeply.  folk with issues should visit
> the help desk in the terminal-less room or visit the noc.

This recent Apple support article is relevant, at least for iOS users :)

https://support.apple.com/en-gb/HT202831

> On Wed, 12 Jul 2017 07:54:44 +0200, Eliot Lear wrote:
>>=20
>> Why not just turn it off and see what happens?
>=20
> because the noc thinks of the attendees as those strange critters =
called
> "customers."  this creates implications for service continuity.
>=20
> On Wed, 12 Jul 2017 08:46:11 +0200, Christian Huitema wrote:
>>=20
>> You may want to tabulate the OS version of the devices on the
>> un-encrypted network. Can your DHCP server do that? That should give =
you
>> some indication.
>=20
> i proposed measuring a number of aspects of use of ietf-legacy, mostly
> port use; wanting to get a feel if the use was protected above layer
> three.  i specifically avoided proposing looking inside the packsts as =
i
> do not have time to deal rigorously with the PII issues.  when i asked
> if i could measure port use, i was asked to write up a formal project
> description.  as this is not my paying $dayjob, i hit delete.
>=20
> for me, the botttom line here is
>=20
>   please try networks other than ietf-legacy.  if you have problems
>   which drive you to legacy, please come to the noc and debug.
>=20
>   this is something to be revisited when we know more.
>=20
> thanks for the clues.

The above Apple article suggests that once you do switch, your device =
will prefer the most recently used SSID.

Personally I use eduroam, and it=E2=80=99s preferred for me by iOS. The =
snag is that if some other SSID is auto-joined, it=E2=80=99s not clearly =
indicated on the device; you just see the WiFi indication in place of =
3/4G.

Tim

>=20
> randy
>=20


From nobody Wed Jul 12 07:57:06 2017
Return-Path: <Jason_Livingood@comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36DE61316F0 for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 07:57:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, 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 kP2t894muYGF for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 07:57:03 -0700 (PDT)
Received: from vaadcmhout01.cable.comcast.com (vaadcmhout01.cable.comcast.com [96.114.28.75]) (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 0063C12F3D0 for <ietf@ietf.org>; Wed, 12 Jul 2017 07:57:02 -0700 (PDT)
X-AuditID: 60721c4b-b87ab9a000000a8e-81-596638bb391c
Received: from VAADCEX38.cable.comcast.com (vaadcmhoutvip.cable.comcast.com [96.115.73.56]) (using TLS with cipher AES256-SHA256 (256/256 bits)) (Client did not present a certificate) by vaadcmhout01.cable.comcast.com (SMTP Gateway) with SMTP id D2.65.02702.BB836695; Wed, 12 Jul 2017 10:56:59 -0400 (EDT)
Received: from VAADCEX37.cable.comcast.com (147.191.103.214) by VAADCEX38.cable.comcast.com (147.191.103.215) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Wed, 12 Jul 2017 10:56:58 -0400
Received: from VAADCEX37.cable.comcast.com ([fe80::3aea:a7ff:fe12:38b0]) by VAADCEX37.cable.comcast.com ([fe80::3aea:a7ff:fe12:38b0%19]) with mapi id 15.00.1293.002; Wed, 12 Jul 2017 10:56:58 -0400
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Randy Bush <randy@psg.com>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: meeting ietf-legacy ssid
Thread-Topic: meeting ietf-legacy ssid
Thread-Index: AQHS+qavm7mwzBODM06Ykidm1Uwl2qJP3t45gABqC4A=
Date: Wed, 12 Jul 2017 14:56:58 +0000
Message-ID: <7D401DCF-C3DB-49AB-BFA9-7CFF3914C661@cable.comcast.com>
References: <m2eftmwl0l.wl-randy@psg.com> <EC1FFD9E-F9FA-4780-B279-A71AB93A57FD@shrubbery.net> <m2bmoqvyoj.wl-randy@psg.com>
In-Reply-To: <m2bmoqvyoj.wl-randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.21.0.170409
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [96.114.156.7]
Content-Type: text/plain; charset="utf-8"
Content-ID: <47B72A4819BB2B4683F0E3D24F5207DF@comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA11Uf2wTVRzPu/bGtezB221t344N2RFJtkg3zJyFTH4kJEBQwUgiNSTs1t7a umu73LXdZjSp8kPcqtkfIqyoQBgxyiLKj8AQZ+wwWoRsyVDYjIHFOQT+IWiEBRXf6123q3/1 k8/nvc/38/n25TgL/7Zd4EKRmKxGJEUsslubtA2epV96Wrx1A2P1nqkvDlo9U7tuMauZ9X19 08z6vb0HwGbmZXujX1ZCCVmtXdlkD3b/OcW2jXMdo8leNgnOc13AxmFUjy/dHJjTBewcj84w +FT3EKACjzIAZ9OP6TgL8O6dz1BchBrwL4evWCguQ2vw4aGjDMWl6HG8c+iNIp1fgh9lxogP R/AK/OD9pZS2kiM/Prwyh2KI1uJ/9vaw+twkwI8++Jalgg3V4OEHH1spBsiJ71/sz/lbkAuP Tx5k9NAI950ftujYgW/9+m/urgO58U93P7Hq/BP48tVJoOM6fProoMEvwqmefRaazYKq8fFz tbr9Cnz365usjqvwe90TRs4SnO2dNK668NCFs2wPENKmROlZp7TJKW1ySpucDgH2U7AwIUl+ XzgYjcfqlrl9UrMiu33RsE/SYvT3BKB/sVqx8Sz4bHpdBiAOiMWQq27x8qyU0DrDGdDKMaID jv4te/l5zVF/Z1DSgtvVuCJrYhlMAXISztDNcaVVFGDL04QtnWEjcrumyDHypsSFMOvweXnX jKbFtbaQLxSNa9vjqkJeAmchthvqqa1f6nxVVqP6sAxYwFlFF7z2JAmCAlJMbpXlNlnNqzvI ctA7/cdGgGCNRCOyiOEmGqNElQNyR0tIieXPEhPQQBRkVnLJK+HcEZLOaRZM4avgK4NkuGCW /5+f4WwZEOCKSYmfcyW0NimshQLG6FL4eS1hi/Nsbmw5nKBJ+TxpGlkJJSdNlJcKx10E3YBL 75/+i+FOPfz+PsPnmgsueD3Xj14KxiMzxQUnzL7Q5OXnmwQaQKiAKco7TPxsBmER/J2q5Sa1 MEb+M3Eb+MjzKYUqbVNMPiKzvXn4A4001yBztTHMUq7E4EytK+BHtLXDUAqn3SbrZch6+1v9 dL0xKWZeb1jx0/UarLHee/QonycL1hui5515qXCSkATulNZz8qn90faBG/OnKyfePbNyFze1 u2bk+WbbiUu2MLu8q7HXG/Cu3lR9fN+C18vXjL05cOQ7d3VZxRbLqCcx9s289j07hj88MP7V a+sudDyXfHELemt8z+X01jvLE47Fw/dWXfOt2rzt0G9e4dk7V92NR9a+tPj6NvWPqhsN54rK U4PH/KJVC0rLaiyqJv0HkWEhNJwFAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2wmqO8lYfZfsT98svrLPZdi7pVc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 14:57:04 -0000

T24gNy8xMi8xNywgNDozNyBBTSwgImlldGYgb24gYmVoYWxmIG9mIFJhbmR5IEJ1c2giIDxpZXRm
LWJvdW5jZXNAaWV0Zi5vcmcgb24gYmVoYWxmIG9mIHJhbmR5QHBzZy5jb20+IHdyb3RlOg0KT24g
V2VkLCAxMiBKdWwgMjAxNyAwNzo1NDo0NCArMDIwMCwgRWxpb3QgTGVhciB3cm90ZToNCiAgICA+
DQogICAgPiBXaHkgbm90IGp1c3QgdHVybiBpdCBvZmYgYW5kIHNlZSB3aGF0IGhhcHBlbnM/DQog
ICAgDQogICAgYmVjYXVzZSB0aGUgbm9jIHRoaW5rcyBvZiB0aGUgYXR0ZW5kZWVzIGFzIHRob3Nl
IHN0cmFuZ2UgY3JpdHRlcnMgY2FsbGVkDQogICAgImN1c3RvbWVycy4iICB0aGlzIGNyZWF0ZXMg
aW1wbGljYXRpb25zIGZvciBzZXJ2aWNlIGNvbnRpbnVpdHkuDQogICAgDQpbSkxdIEZhaXIgZW5v
dWdoLiBIb3cgYWJvdXQgYW55IHRyYWZmaWMgdG8gdGhhdCBTU0lEIHBvcHMgYSB1c2VyIG1lc3Nh
Z2UgdGhhdCBzYXlzIHRoaXMgaXMgYW4gb2xkIFNTSUQgYW5kIGlzIGJlaW5nIHBoYXNlZCBvdXQs
IHBsZWFzZSBjaGFuZ2UgdG8gYW5vdGhlciBvbmUgbm93LCBldGMuIFRoZSBDQVBQT1JUIFdHIG1h
eSBoYXZlIHNvbWUgcnVubmluZyBjb2RlIHRoZXkgY2FuIHVzZSB0byB0cnkgdGhpcyBvdXQuIEFu
ZCBhcyBvdGhlcnMgaGF2ZSBzYWlkLCBJIHdvdWxkIGJldCB0aGF0IG1vc3QgcHJpb3IgYXR0ZW5k
ZWVzIGhhdmUgbWFueSBJRVRGIFNTSURzIGluIHRoZWlyIGNvbmZpZyBhbmQgdHVybmluZyBvbmUg
b2ZmIHdpbGwganVzdCByZXN1bHQgaW4gdGhlIE9TIHBpY2tpbmcgYSBkaWZmZXJlbnQgb25lIG9u
IHRoZSBsaXN0Lg0KDQo=


From nobody Wed Jul 12 08:06:32 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5703F12FEE1 for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 08:06:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 iQfHnmnu7r0c for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 08:06:29 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 47980129B2E for <ietf@ietf.org>; Wed, 12 Jul 2017 08:06:29 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dVJDf-0004KZ-Ee; Wed, 12 Jul 2017 15:06:27 +0000
Date: Wed, 12 Jul 2017 17:06:26 +0200
Message-ID: <m2eftlvgnh.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: "Livingood, Jason" <Jason_Livingood@comcast.com>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: meeting ietf-legacy ssid
In-Reply-To: <7D401DCF-C3DB-49AB-BFA9-7CFF3914C661@cable.comcast.com>
References: <m2eftmwl0l.wl-randy@psg.com> <EC1FFD9E-F9FA-4780-B279-A71AB93A57FD@shrubbery.net> <m2bmoqvyoj.wl-randy@psg.com> <7D401DCF-C3DB-49AB-BFA9-7CFF3914C661@cable.comcast.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BP8r2X4A6amPJRjSWFtteBaU3Ec>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 15:06:30 -0000

>> Why not just turn it off and see what happens?
> because the noc thinks of the attendees as those strange critters
> called "customers."  this creates implications for service continuity.
> [JL] Fair enough. How about any traffic to that SSID pops a user
> message that says this is an old SSID and is being phased out, please
> change to another one now, etc. The CAPPORT WG may have some running
> code they can use to try this out. And as others have said, I would
> bet that most prior attendees have many IETF SSIDs in their config and
> turning one off will just result in the OS picking a different one on
> the list.

ripe meeting solution, e.g. renaming the ietf-legacy ssid to
ietf-legacy##, for every meeting.

from the discussion so far, it is not clear that there are no folk
depending on legacy; excuse the double negative.

randy


From nobody Wed Jul 12 08:23:15 2017
Return-Path: <ietfjournal@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F058612ECBF; Wed, 12 Jul 2017 06:59:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.802
X-Spam-Level: 
X-Spam-Status: No, score=-4.802 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.org
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 YVa34pbjbh4E; Wed, 12 Jul 2017 06:59:02 -0700 (PDT)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0047.outbound.protection.outlook.com [104.47.36.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D70E12ECB7; Wed, 12 Jul 2017 06:59:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.org; s=selector1;  h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=EDQbPnPDIph4chEwhXJikA+2pEAW/3pVezwzTJ+FSO4=; b=aXQXrMm1X+WwwZ4sAdozK6xC8WdK726Qas5BanPDYe2pigPf/jRGpgh9Xto0+N8xL2A2ZdPrI9qAF38X956ybmmvduRTtsFt9klgmWJtbBWE4dHNMk6G8j1VRCSvj5Zmg1BscHIKiCzyz9ITodDDT5VeLEPBjCujncL0rIKgZr8=
Authentication-Results: isoc.org; dkim=none (message not signed) header.d=none;isoc.org; dmarc=none action=none header.from=isoc.org;
Received: from [IPv6:2001:8b0:dcb:7d85:6d21:af54:8e10:fad7] (2001:8b0:dcb:7d85:6d21:af54:8e10:fad7) by DM5PR06MB2634.namprd06.prod.outlook.com (10.168.199.7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1240.13; Wed, 12 Jul 2017 13:58:58 +0000
From: IETF Journal <ietfjournal@isoc.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Wed, 12 Jul 2017 14:59:00 +0100
Subject: IETF Journal: Latest issue (Volume 13, Issue 1) now available
Message-Id: <6FA78372-1BD5-4A21-8FB7-C010DEDA94C7@isoc.org>
To: IETF Journal <ietfjournal@isoc.org>
X-Mailer: Apple Mail (2.3273)
X-Originating-IP: [2001:8b0:dcb:7d85:6d21:af54:8e10:fad7]
X-ClientProxiedBy: HE1PR05CA0212.eurprd05.prod.outlook.com (10.171.110.140) To DM5PR06MB2634.namprd06.prod.outlook.com (10.168.199.7)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 8c78ac2c-9bf7-4ceb-4242-08d4c92e2598
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(300000503095)(300135400095)(201703131423075)(201703031133081)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:DM5PR06MB2634; 
X-Microsoft-Exchange-Diagnostics: 1; DM5PR06MB2634; 3:8M2659eFWMUKjx+riMOH770hDIjhNqQ7dZYIlRbgBW86fSiGUopZmTl/i53OP8FYsV0bzhRD2ypB5vDAiXRQQqh+VkRj2nCWMbicrQFjaw2+nLwGT8mHTH6uTutFanVRyR0xZh2C/VsdnZUBNFIKzrzBiH32QgnLbQDfgYadWYtgt8USd5OVDxRJfaapad+lmwXLKQl89kMfBKEFk6ezbgdtM0AUYMt4WgHbxjkb3xtZugdO4vKXz5Eq6cpxgZmLpXZ6n4gxkxO6EPiG4ftYhACkWmHhgQ5+AhelwcNCt7D9a2wjogobXFyCoYrSz8FfCTJXLFHJT3PWCnwQRcjdIGbtpLZcd+WcxONdfBiWvuPv7Vj2pn6r4+i6093HzP6qJ36Nrx48H74zztNf/nuC4KRApFBdxiZAsB8/UTjJnRArsvVqtlo0PArTcqImCLz5xl7adsnDnrVQCTyu1ufwX4OJV5kluGU3xoX6FvS5XDPdvdlW0z6d91J9Jwyw7fVWNndk+yFKrLVYKIvEx4Xi1gzCrjR6MrQOjJM0Jbs87AgGSHlCLuPm+PpV4UwAni5N1I8p3WpZNyx6cq6Lxjk7xsRW7bGe7bc2oHJvdFVb7yWVlmsou7rPsMDx46cuwKiJUH5GgrhdqCuRYvE+1/CP9mf3EYH/q2GlRy09lLtEing9KRDtJ5mwajq41ZI87VHJx24mibFDIusajuzemyQKX0Sx5cwbrKrjRlPxmDrz9f0=
X-MS-TrafficTypeDiagnostic: DM5PR06MB2634:
X-Microsoft-Exchange-Diagnostics: 1; DM5PR06MB2634; 25:x0angwPu1FZos1J9Gmyq1mOrlv5fh/gw4FgQUBTpzAAxb1Q/vl1uq9xPsteGlWjPZPPZa7bC+v3ajChj5xj4Pncm5e6cACPaHN727oqYrdoNFqoAuDqu2GeOJyDRaLwC/YoQpwkjmEj68jxKFQLYM9qsNP3Jm7a2ZsjvGS/QShsHjlsASJeQ1v/kLcZltEUFggNP9joe7MnKj8SScke0OOPYsf0Ocm8lU4Z446hYpWApgmjNBA7G/Hx/1N7qakJZL83RN8KfLAeziCGzip0DwN0BnDaEIBFYwuTAEEiZsPeqDrPG5Rx95FlfyHavUTVX7hMWi9auOeIDB+v35Q0lro3uA6Il7XIaEKbDBVgeXNXqimfvh3hjF8zOla4cgqWIugQK+O3x5O3yGVLrtrsKxaKBCTOrtXpNc7Utjv7jSZ0lmWUdvI1PGY+/3Jnn59pEFtAbb4tQ0kq2OVuC5iB61coPiFSgZJKH9zOIrtqLMmxr+LFIjNfytYWyd16z9fIvesKIA956kqCIJPHsezvWmy2ICiUpUVpYoVa28+75lbvbBfmF3LucVGMoOFUJh7P2Tcp0VaToNb2E2x/6GJn6HpBSKOHfclM2lgCnzolT5oO2gX9lk8549rZiUOdPyW1eCa+ayLvFzZZsn336kbHI0Zc18xuzMAXq5Xgq9wfti7Akb1w14O5m/rqk4OAYB9yRqiwaJ34ethjieumnu5aV590xc1BY0jWEan6AfS0B7lR4bIoyfdA6PZj5zLJrAlGkiqblrR4zOn9VvYEHtwJ/xttrNE4QGjGZPce6ljUuYjjbPgQsWupmf8O4Bmb3DilvX8vuc6BPQWQf2NSQS9D0o/zKDwyYmjghgyKxDlTL3bL7jJk/7LZ9OnQwqeFffdv/ylNnaxzY8Svq5herBvOe1a5CdxOKMjibhjTmE67JIoE=
X-LD-Processed: 89f84dfb-7285-4810-bc4d-8b9b5794554f,ExtAddr
X-Microsoft-Exchange-Diagnostics: 1; DM5PR06MB2634; 31:XXTDwH2gMs4/Re5pBjECBE9T5ljPelXMXWqaH4vNeyX+D53nWBJ/amQ8a3mBKm54srUTU0UJjCUumpYbDE20N7A8a9hlDnqSani37Z+kG44UbRM0BZk9q6QfMTHRJPJVD6KpuOEvxfxChojt+m+LptgBSphM5gpnkb58/jraLl/Op3sBXHfij+qQNCnuD6ls5mVEI4qU+wffPAWAiQlPDq57QcOW048Apvv5ItYQt/8UpspOzTGWRFLdPenYcOxGPmcMHp0z94n7LatPuHsswZVA7jJTAO7g9r//rO3yyKido4VUp/gRmIDZk7cI2BR7e4LxoXzQYmoDOoUuMbZAuPwfi0Q5FxDtBd1S4mM/dNYmjCoLQnoQi3X7EvlN7QGZ/h4h/rxAWTwptnauiA0aY9AcIxuf8O8atVamt/Litf/UVmSiyugkauS0Che0bNk2gZfJZEJ4QOiNdXZTRDDIC4DYZoMAMfBMHz4YNO7hGe0ChTYQXoIvJemmbM5YxAxwMDM4Fo989Kq0O8BDIePn72me4N6+b4Y0t+vkQ3JTp/XPAql+YvzmADU7skydKURmifoFzsa6Ciefe1tjutw63craQQ4ZZDYctDbYbZANyTV+rLvgLRiX2JN65OyqOWwJU+Y5Qst3HOo1MAkyhi3ekpMtnZ33ZWVVjZ4ghXPxIBxCgHdkLFKRbQiUSbrzQvJp4QIC38iK4z5DdNps2Seozg==
X-Microsoft-Exchange-Diagnostics: 1; DM5PR06MB2634; 20:hJw9YldatHT1JugpmHcxD36PwJNsoP6W/afQxM6ooXdjFZ+KrLIDwir2b5dwSOjGcm4+ZcSx9Snv0l/HGSP2BpDpkPHnQEXq5GxcW1qOut1zNAJM3i+yYwREgAvgMLWMdwrsrrhWrrU6WkRWB7I3O/rAlctid5TLDCkONd4pc9tpCMrBw1RUJ6K626J8KZ/xa0H43G0BJUDD92sg8cO+O45B6yIHRDi70wOynbo/aDPEpDyh6fLP3FO7XIm+cAXk+0IrT5Bm/T6OHIrdAkE5GBOIeLr9aCdMY13wcpnvErlOIwql60HYLWMNayTJieQz8igPqGY+ob91AiGdUU4LDPkisW4no1NzT5zyrKXi143mHvF1iZ3s3dBBFdjEGI3ZLHoDm+KtkvDoAiSFRg9k04GOV19aYTyIwLPeNf99ER/t/pfPu8NksPBK9F6ixJ3BSGvUH8tr7rHm1Rb+RB+T48KDwXxtZb/6KPGqwNmvzUQTT3QkFlF+jhiiZW7Rk4n9
X-Exchange-Antispam-Report-Test: UriScan:(148322886591682)(72170088055959)(209352067349851)(236129657087228)(192374486261705)(48057245064654)(199457065432035)(148574349560750)(81227570615382)(167848164394848);
X-Microsoft-Antispam-PRVS: <DM5PR06MB263453197874E216E559C703C7AF0@DM5PR06MB2634.namprd06.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(5005006)(8121501046)(2017060910075)(3002001)(93006095)(93001095)(100000703101)(100105400095)(10201501046)(6041248)(20161123564025)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(20161123555025)(20161123560025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DM5PR06MB2634; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DM5PR06MB2634; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtETTVQUjA2TUIyNjM0OzQ6VzV5TjdzUWQ0THBxV1A1VU85eTg3TnNjaFl5?= =?utf-8?B?VDd6QjJDYlA5N1RveFYzYS9TWHlzYUczYUxWVGRxUGNoNmkydUUxQVJtamZ2?= =?utf-8?B?QjlTMHVxNHFab1E4c08zR3ErYlNaYkZvV0lnTHM0cVQwYmZBT2NocWVJeWNR?= =?utf-8?B?NEpscDhSU1pKZUN6UlRTVFdwdXVQdmwydS9sS01UR015ZVB3M05uUVh6d2s2?= =?utf-8?B?cGVOOUxORkJoUFIwcjQ0NlJ5WTRSS2k5emdESEhRSXN0cGNyK093Z3UxeGdE?= =?utf-8?B?MEZXWENIYlM0YjQ2aEw3T0k4TDZZR1RwRjNIdjM4b1ZhT20xVlJQQXlXcEpE?= =?utf-8?B?Y3JtTVMvOUZFSC81WXJrR3JJMUVGQit1OHl0dUs4SGNDM0xuUitMcnRtVzJK?= =?utf-8?B?K0lEV1h5VkIvRWNQR1duZngvc3AxbTlzZFcySXNUWlVFNHdKbWdKSHI5VWw2?= =?utf-8?B?VzlnVURsRjNaWU93SzBOdkllVitNOThseklRRWhEOFkwZDgrUjBpS1NNbk96?= =?utf-8?B?UGF2WVgycTJiems0ZFRVM3VWV3Z6SEFwU09icTF0V0JBQVBQcTRLamEvOTRN?= =?utf-8?B?N21NUWg2NmZFTGtacy9FU3p3cDlGaENEaHpPa29PZkx4RVlFcVg0ZEpyVTB1?= =?utf-8?B?T2laVU5rb2NxNFRydWU1K3hCVnBrZWl4dEtIcW5Cdkw5RVYrYlFBblViQjUv?= =?utf-8?B?V0t4TS9Hc29jUkF3T3ZiaDdzNitCUk1pNWZVMDVJdG9QNG5QNU02VnBPZjJx?= =?utf-8?B?a0VkOVJOVlpzejlpRkVSUzFyV0o4MUx5L2d3cnk5WVJTTTk3MHRDRzB6QUhz?= =?utf-8?B?Y2FVWXZyWWc1b29vYnQ5TWc5MEthNUhVdHVDWjZobnUxOWtvVFVUckZGVlc2?= =?utf-8?B?S2htUzUwV3BLM3laeXJMZmc3Qm9zUlVzTTNBdXNXSm9ibVBhVHJobmVhcDl3?= =?utf-8?B?Wm1IeS9tVlhGREw0TFJkVEd2a2pGbSs2NFdYMmxyaDFWZkFoRk51bUNCSkZs?= =?utf-8?B?bzFZWWJqU3hoek9URno3RFBMM0cwTnViUnlOOGs3Y0xWdmVyWm8rLzVuUjI2?= =?utf-8?B?eVJvaXZRdkpJMkxRbmYzSHczU05GaW1jS0FzYkFoZExpejEyVFNvTmpHTUFl?= =?utf-8?B?R0NTWDRMMDVhUytTME9EbFhsRlBZTjhyZTV6Nitsc1lqYkhnZjR5V1lDQjVt?= =?utf-8?B?OHlkSnBFME9yUzlrZmgrOHptQUppSkFNT3pTNVVDQlZiV0hKalhrMm1oUWpD?= =?utf-8?B?cmUrT0dxa0FYZTBrNllBeWtzekNDZjFJRzBMME5pYktQVEp0aVpZYk5UblY0?= =?utf-8?B?QllYRnVwcUpoaDhqbWpaVUsxbjJIM1psVk9ZY3dTakRUejBmQ243ODZ5djZG?= =?utf-8?B?V3NIeHNHUFEyT1Q2WnJSb3o2TUZzYVRBTFlmTzliaWFZR3hRWHVjV0MwKzBn?= =?utf-8?B?akEyZG9TMCtzcVhPQzg1WGZmTnBQZUVBQWZaWlcwZEFrQWh0cnpEeDAvLzVZ?= =?utf-8?B?STdScE15R2grOE41ampUTTZjOFRMazVlR1ZsanBSYyt1YWxhK1psL1MwdHJk?= =?utf-8?B?SHlvd2tIQW1MNkE3UDYraHNuamZsR1hrZWFpM2JHelFuWXJKR0VMRlQ5OGJR?= =?utf-8?B?bFQxZmVaQUxjd3h3RHVqUnlMMzgvQjNOdzVsdU4zSXI3Uy9pSGRRdmlhcHBL?= =?utf-8?B?NzF3V0NjaUxWVldDcjhPT1YxSUtlZXBtRGFkZ3RRaVM5SE9KTzlwaVEzeXJu?= =?utf-8?B?WWs1RWhoaWRGM2dISm9oU1BqYkNwck1ndmRkKy9tQmptTXNRd2JlR0RaTzRK?= =?utf-8?B?QStzRVArcndHdjVJQVBNSzVMcEc3aVkrelV6UWFQQVVna3oyZmhNZkFaVzIv?= =?utf-8?B?bkNqYXdBNk5sNUt3azNlUmVnTGN0UHdUWHltb2k2NE1NWkMyZ2hyM05QWit5?= =?utf-8?B?LzBSa01PSVZ4WkVFS1dERGVXVWdINmU5UHovNUxXV2d5bGgrUUNINFZqdlFh?= =?utf-8?B?WWZ1WmtzT2VYVURBSHU4WWJocU5EUS8xT01YR3h1VmprZUZHOHQycW8xS296?= =?utf-8?Q?tFZliYIGDRW80HTAbaJvsziy?=
X-Forefront-PRVS: 036614DD9C
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(4630300001)(7370300001)(6009001)(39830400002)(39400400002)(39410400002)(39450400003)(5403001)(66654002)(10533003)(50226002)(25786009)(6862004)(6116002)(6486002)(23676002)(7736002)(8746002)(53936002)(38730400002)(8676002)(478600001)(81166006)(6200100001)(50986999)(110136004)(2906002)(33656002)(83716003)(86362001)(7350300001)(50466002)(5660300001)(82746002)(305945005)(42186005)(6306002)(36756003)(6666003)(47776003)(189998001); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR06MB2634; H:[IPv6:2001:8b0:dcb:7d85:6d21:af54:8e10:fad7]; FPR:; SPF:None; MLV:sfv; LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtETTVQUjA2TUIyNjM0OzIzOnRROWtyeC91K3kxcTNVMmVZMFNWYTZUZis5?= =?utf-8?B?YUZGWU9keW5ORHFnck82NVVERy9BRXh1MTRhLzR0ZUxGakMrK1F4b3dWV1pz?= =?utf-8?B?V01FU0Z1Q0FqMXI0aUlvUTBETUdVWkNxbnd5cG5lN0IvQmlLUE5CSC9QK2RR?= =?utf-8?B?OTdPRTRDK08yTTRYMTZka29oWnFMWHVHZkVidU9YaiszdUcyMEhNdjVFWHR2?= =?utf-8?B?SkhiQVRPcTIvcksyNXJ5WG84VXpSZGtOdmtWK0xUaHNtTVNnbXlWWGxBUWFE?= =?utf-8?B?SmZKNTQ1RjRFcUkvTlFrcW1pQ2JmU1JQTFY0dW0xaGJhSmJ6THNiUE9WdUlp?= =?utf-8?B?QzZYRnRZdU1CZWt5YTRCdkZDeFNieE03OEp3L0ZSaEIyVEw4Y1RuSEJ0NEI2?= =?utf-8?B?MU5XNVU5WVZGYWJQM1Q4UjBNUG0yUGloU3dqUnRjNitHY21WdmJhaEcxZUJo?= =?utf-8?B?eDdEN3FEWkxXUWtqU1lGYjcrSGpVRWdJUUpKNUcxSThXVmhFdWROZm45OHZj?= =?utf-8?B?S0ludHdYcHhWRHBIWkJ6NUw1ZGtVTXJrQm9wN252QUVwQ1h6Q3gzWGpGRXho?= =?utf-8?B?Q0tVbjF2YURmVUJIL1gyM0RLUEtxWVkyM0FXWENRVC8vQXdQUjZ0VmVNV3hB?= =?utf-8?B?b2d4cTllTy9BYWkrdjNsdTJtTzFTWWJIV3B1RGJPV3RwSzNDUlkvQk4rK3BL?= =?utf-8?B?UlR1TDNVaHFDYmVOTmFlS1orMHpxaXlaYjFQcWVWMGNXN0t2NmdWQnlrekls?= =?utf-8?B?Z1ROeitLdjZFSmdKT2VaajVXWFN5YjNhUlQxS290Z01mQVBRQW0yMytVYUQ2?= =?utf-8?B?eFRnSUNjcnVQSmtqTW5vNC82RnkvdVZ3c0FZM0ZLamJmemZ5eDF3UG1qUTNU?= =?utf-8?B?aGJqVTc1eEhJR01CUC9WbGlWYm1LTk5FTXFFV0Q5MnloN3VhVU41R0xGRXJo?= =?utf-8?B?R3dTQ3Y2REdaY3FRNnBhWTFObitoVnlGOTlMbFpUVXdqK1UycHVQWEg3bjla?= =?utf-8?B?UEwrRkhackJVSEpaQzVzazNYb1lSdXNzZ0Z5ckFlQTM4VVhDZHhjVi9mZDNK?= =?utf-8?B?Qjc1cndZcXhsUkJyL0Fuai85eTdRb2tmRTRQQ29iT3lzVTZwbHh1SjJlVTRm?= =?utf-8?B?eWZkaDI3RU9KWEVDR0cvY05FMk13OWJXK2JaeG56MVpNU1N3b1hpdzQzQ3U3?= =?utf-8?B?bndlL0ZhcFVHdWhodkVEaWxyMGVCb2JCWTQ5WFpkcXk3UC94OTJUYmJmUlJ2?= =?utf-8?B?MFVBUnF4dC9kS1ExVHJFdmM1Vm81SUtWQlBXYU5rQlhkNVJ2M1diWWFGU3Bv?= =?utf-8?B?aFVXazc0RVFsb25xVnZLZm9uZXRCajBmYjh1UmZBbFcxRUlzK2x0WDBXSnRE?= =?utf-8?B?UGVFbTd5ckdTWXBNL011eTJBSmdsOUlVa0RUdVZZTUFMdGNEYVNiemlDeGp3?= =?utf-8?Q?48BCnU=3D?=
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtETTVQUjA2TUIyNjM0OzY6SngxNEpDREM1bG9yakJQVE1BVUROaTZjT2hi?= =?utf-8?B?cVZ1VENLci9sa0prQnE3OEs0VUR1bXYzeVlQUWdiQ3RKaGM1OGtjSWlBd0RH?= =?utf-8?B?Qld4a3A4cjYwcEhydlFkbkROckw4Uzc4Rk0vMmVIdGU0ZTlaSGNBSUZNTE1T?= =?utf-8?B?bHZuOUVVQUhHWHk1c1pWNC94OTUxWTRNcitFSVdUSUN2aFp4U3BZQnkvRzBB?= =?utf-8?B?cVNEck5rd05QdkJCbWo2TSttd2N4ZC9TVlZJVlhwNDNML3lHeFBKNkdMUDR1?= =?utf-8?B?RHN5amxqbmFtbXI5cWduOWFpcG9TMkh4RU5VSzBRc2tSTUN4cEg4cUhSTGpB?= =?utf-8?B?VVoyc0QzSFBrakxTMlhLYUd0aVZ0b1IyV2pHQlhWMjVWck9XcVlRTWZ0dTd5?= =?utf-8?B?b3p1WTVkajl2bVRNOG1GYTFkMFp5SzBQNkFPNVVsOTZjdzBkWWhRbjYySkl2?= =?utf-8?B?K2czTjczZDRWVGdLTlo4SmVVc3lRMzZrai96UXVaamtyaGwzMzhvWW9uSkhR?= =?utf-8?B?S3I3cWQwQ1NVNUh6QVdFK05xbHF2NjlETUFJUTI2UEduckVJNndibmNydnVX?= =?utf-8?B?aHhTclZ0UmgxNFFDdGVFZys5UGlGM1d0T1hqS3NYSmlSdVdUVnFJS2JhOEov?= =?utf-8?B?VXc4dVpWa1QzcklQaVd3NzNlVnliY1RiSDZjQnBJVlFIUlZEdmV1ZkpHenNE?= =?utf-8?B?K1hZb0hQWjFGWUlTZDNHb1R0ZytnZkh3ZUhYbHFEMFl0d2o2ZG1sM0RBNTdt?= =?utf-8?B?TUVZNWJXaUZLYSsyUUl3RnNCU0djMzA0bWl6N3dIcmEvZVBzTkdMbkNIY0Z3?= =?utf-8?B?K0d3MGx3ZzZWVEVoZjZLSjBOclNzdGVkUStBTnFkTGk4QW5iQXcvRWJKMUl3?= =?utf-8?B?VGkyREs1TktuaTRISEVERS9sV3p1dE9tSmZ5RGc0dEo3WFBGZVY2WmVlM3Jl?= =?utf-8?B?MDFKNlRDV0cxTG1Iek9IT0N2QWovR0tHbnJKcnMxT3Q4dXEvSDdKTzBMb3lC?= =?utf-8?B?SGVCZ3Jwd1NORVF1cWw5S0t2YlVDeGN1bCtvMkNCa2pZRVk3TzcydEJTNVo0?= =?utf-8?B?bFZvZWJuTVB6YzUxNjV6Y0dYOHYzOEZMU2N3aVVXWi9nK3ZoSHBZNmlNU2lL?= =?utf-8?B?bjZsUEhRbWNZSStaRXlCNlBDY1RNRVVoOGVVOUw2NkRmZEtLdWdEWVVzVmVr?= =?utf-8?B?bGZoYi9JMDBuOXZ2ZUcvaGRLZnRHMnh4d3Jab0VBbjNQNHlVL3NaaEJzL3Ra?= =?utf-8?B?WnpPU3NBNHJ5SE83dW1yem5tamlZNEZoYTdpVzd0MEVyRkdib3RES3kwTUNZ?= =?utf-8?Q?OUWMm75qRXYDScc7WjRNJLVZllTkSak=3D?=
X-Microsoft-Exchange-Diagnostics: 1; DM5PR06MB2634; 5:sxYArbDWomZZ1C0nampsQBc/nOdNEEWQNuSGgL5pCwRTu8T7YrPzLU+FhesetmzGBs8+NmPCD8mQ8h8lMuBGObToVLxGvB1wMUeVN3EcJV9XlUwc6QyU3fh6qsvvcdot9+leOp2iOeEUY67Mc4JoIBBx4GydnOiNphHAsCFz7rBw4c2Sc2FGCoxAuHzMj3q3y7cRQduMo7GtLEjz8aZlvbWv2D4mWGdGm0gZK0tbw0MaxH1k06eYdXwjeFp6xh5YyvWmZJLrlrNTXyluxn8BMCZSCQFQbxZ2OcvKQW1Ss0/x93S9FROb6iPE+Tks+jAvgVk/lZvCgDMhB65WtEMLC+ioNPiLcwYWxcrIuVycwtJz5YGAy6G/pfljBoV+v05LzHTVwjIEXAADAZ67ACzgwukkkaGRTf2SCuc09A4rO+1TaA1rAffTEvEirQ9NELbfR65ETSUoEz0GdANhjcEthJk3bXLE4BqJ+Az/jVm8EKxAkPqgySgBQuuY2+wSUDuN; 24:GUsYZ9xMKu8SnsP4aT49gN6376cN2jjXLrqfB6hRKBIqDR5qpVzNZhshbt4fZOZ32x3l2TZvRgKeTnC3ehzLsW4qbl/Iwud+xxWGEqeRHkQ=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; DM5PR06MB2634; 7:uZMKL8bWMt8+WIgmEeFSquXG4E7EwBmQruFeR95dPZ0jeIFDXvTGglizJ1aA4HMhzP1CQglvf2QUQjKORK+a/UcMai2h7phDiI/39aliqw6uNoTmM2WlR6jAO9BZWgE0ZGNw+PDQ23XB6FKSCx/J1q5WfVgguEgrN1AtSv00hxVwkzCUP7mYCE6H09yISY8i33WYv+pmG2KzPH2sEQCerJb+3Poa9BVEhUdqyKyhW52QG64V8eB50ukn+Ke4AU1R90R42yov8B1SF1OF5hlOXYY+yBCW5RVip2OPTzZfXz5APZZlF61o1kKKGj/MFLKHnTqH5gN3uhhXp/bIqUTse2jKW9Bdud1tRsUu8qGwqjnaiiGsZmRh/cx0iZ5KOT2djdNhUTll3p0a7xzQv3HZBIyw4mbuKFZT9iEavT5Vrehv6+dAlM80tOej9APZDPG64WJXlm8L7Tj1VMs3YbZn9Gc9qZLGasT2Q/wDPLdTLeXDEM6tpxnzSrrUi1VWECQzkaNYxI01vYhHd8SrPmlaH60jXjwGnlkpLmxS621WvgV/HAjLpdpMdTzkWbEEzw7yoKC9R/SZcCcyO8as9E3LPPUeE58uX921uH5dmkHIweKX0zGOeDyCl3U6cY7bvpJtZJQJWA47SHa8gJ9WBQ9Zth+ssdoh7KrAC9OcS2C2W7BXVdkddbG2xIhIQ/bBmucoG+EdrTsPH9ELMDyUshRE7SYVL5utpFAiur+3sNbHgdg0sw1pUGwj8ZuA1rNecKb0f4IqSzXKlmYxw/MmOTRegecxV+oVl003EwZ3udUBtoA=
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 12 Jul 2017 13:58:58.9595 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR06MB2634
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pk2aVoOjEKkv0FXvrxkaM0HUKlA>
X-Mailman-Approved-At: Wed, 12 Jul 2017 08:23:14 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 13:59:04 -0000

Hello! [and =C2=A1Hola! to our Spanish-readers - see below]

As we gear up for the next IETF meeting, I=E2=80=99m happy to announce =
that the latest version of the IETF Journal (Volume 13, Issue 1) is now =
online:

	<http://www.ietfjournal.org/journal-issues/july-2017/>

Our cover article is a deep dive into Segment Routing, a new =
traffic-engineering technology being developed by the SPRING Working =
Group. Also in this issue, you=E2=80=99ll learn about the many =
activities of the new Education and Mentoring Directorate, which aims to =
enhance the productivity, diversity, and inclusiveness of the IETF. We =
also present an update from the Security Automation and Continuous =
Monitoring WG, BoF updates, a readout from the pre-IETF Hackathon, and =
an article about the Internet Society Policy Guests to the IETF. Our =
regular columns from the IETF, IRTF, and IAB chairs and coverage of the =
IETF plenary wrap up the issue.

Spanish speakers, please note the entire *March* issue (the last one) is =
translated and online at =
<http://www.ietfjournal.org/journal-issues/marzo-2017/> This is an =
upgrade from previously only offering the translations as a PDF to =
download. We=E2=80=99ll do the same for this issue soon.

You can read this issue online or download the full issue in PDF format. =
You can also keep up to date by subscribing to the IETF Journal as an =
email edition or have it delivered to your postal address in hardcopy.

IETF Journal is on Facebook (www.facebook.com/ietfjournal/) and Twitter =
(@ietfjournal).

Hardcopies will be available as usual at the upcoming IETF 99 meeting in =
Prague, Czechia.

Many thanks to all our contributors. Please send any comments or =
suggestions for future issues to ietfjournal@isoc.org.


Thanks, and happy reading!=20

=E2=80=94 Mat


Mat Ford
Managing Editor
IETF Journal
<https://www.ietfjournal.org/>=


From nobody Wed Jul 12 08:37:15 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BACC1316D6 for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 08:37:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 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, 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 MyHtZRABL_G5 for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 08:37:11 -0700 (PDT)
Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (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 7DA32130A94 for <ietf@ietf.org>; Wed, 12 Jul 2017 08:37:10 -0700 (PDT)
Received: by mail-lf0-x22d.google.com with SMTP id z78so20738095lff.0 for <ietf@ietf.org>; Wed, 12 Jul 2017 08:37:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=BS2nLVQx115ARUTymbhHSh6HHsPijT6+ggQjJIw6MQA=; b=cvZ7IDU0s5u5VIRrlmNZ3N6PTGW+m/QlorbQU7ExAlQXUItZrHsy/NlY7UNwhdjHRa EweDFm7QypgS47x5d1cxQxe7+avXMKuQGpY0HoHt+NeuzMQALTZaw71DLfT5UERYAqv8 xXH69wRoQLmvGdPX0TK4ato1VNbMrEEyuJ4kgERYzg1I6HIAnrJZdQC6C9vhlVtLZQK9 oNEGcWEcyXuJ60eATwwhKECuHuZ3AkwSnd38ZdT248B9OGEy659Y0RD9feqccpK11Gbf 2gId+aHlqWgmpmsh49wAKnfn7e6mWMUe0QAlsn4YscdmrqTUqRCVPOex7i2E9p+PbCCw VcTA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=BS2nLVQx115ARUTymbhHSh6HHsPijT6+ggQjJIw6MQA=; b=ZVolG6djCz2QhbJgkLjfAJIDUdALCxINWqTdXHTEJQ/gFfiBD52s029JU8sF6rfZlx oIOjoPu3hxUGHGjtOLSwMb/ZfLrodcqGkM+ZsnzacYVNUi/JHucfAjHViYJBSH+1WC2J kuAO1FkH0YJe3a6iuVfSzT+rjHNLfPZ6deYBbNM3JN3n8dVh5mmxbpyQPBdRIwMexbHl kvTE9ATdpuhHIGAbV1RDEai7wHNIHqux5HgWCOfkrEIX+DICtbkcS4lpk0Qrsx0yjymJ Th/Y7h1OaEbFH6KurWZ8swGmTY6nq105DkOxI1jUdwm+nFGs3EB3H0Ct8cl+0UFAfXEF SmAA==
X-Gm-Message-State: AIVw110PNkGXf9gjDyybh/UDhsp7QbPqp3eUfPPla22645VDlmZhIoEf 0DxCtNdi4EdDeRaxgR7XI3z2xHRdiw==
X-Received: by 10.25.199.131 with SMTP id x125mr1779953lff.75.1499873828755; Wed, 12 Jul 2017 08:37:08 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.25.181.214 with HTTP; Wed, 12 Jul 2017 08:37:07 -0700 (PDT)
In-Reply-To: <EMEW3|9524d679479c53e9c82dfaefd8777bc4y6BE9B03tjc|ecs.soton.ac.uk|C8A9ABDB-8B82-446C-AF61-82B03879EA28@ecs.soton.ac.uk>
References: <m2eftmwl0l.wl-randy@psg.com> <EC1FFD9E-F9FA-4780-B279-A71AB93A57FD@shrubbery.net> <C8A9ABDB-8B82-446C-AF61-82B03879EA28@ecs.soton.ac.uk> <m2bmoqvyoj.wl-randy@psg.com> <EMEW3|9524d679479c53e9c82dfaefd8777bc4y6BE9B03tjc|ecs.soton.ac.uk|C8A9ABDB-8B82-446C-AF61-82B03879EA28@ecs.soton.ac.uk>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Wed, 12 Jul 2017 11:37:07 -0400
X-Google-Sender-Auth: M_-AZ1FU_uyQZVhMzBil-fT8TNQ
Message-ID: <CAMm+LwgcGhTm6+oYTYZK5zrM7V2B9JZjQ0sOqw215qq1e4uBDA@mail.gmail.com>
Subject: Re: meeting ietf-legacy ssid
To: Tim Chown <tjc@ecs.soton.ac.uk>
Cc: Randy Bush <randy@psg.com>, IETF Rinse Repeat <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c19bb2ec55f2d0554209673"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mtJIufQwDvqBBisEPn32f-kj-nw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 15:37:13 -0000

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

Lets face it, the whole WiFi connection thing is junk and it is a part of
the network that is not in a place where the IETF usually acts - the UI.

Well, that is fine because the IETF is part of ISOC and do you know what
else just became a part of ISOC? The Online Trust Alliance. And they are
all about security, trust and UI.

I think that we maybe should have a talk about this with some ISOC folk
because it is definitely an area where maybe we need a bit of 'joined up
standards making'. There are parts of this problem that lie in CABForum
space, OTA space and IETF space.

I presume that there will be ISOC people there. We should talk about what
parts of the problem should lie where. I am not happy with the fact that
the WiFi alliance has still not provided a secure user experience after all
this time and obviously sees no need for one.

This issue is becoming a very serious political issue and has been the
reason that I have been making trips to D.C. recently to speak to members
of Congress and their staff. With Congress gridlocked, the range of
legislation they can get through is small, the only thing that people can
agree on is the need for better cyber security. Do people want to have that
conversation under the ISOC umbrella or do I have to use congressional
staffers to jackhammer the obvious into people's management chains?


Yes, the WiFi thing is a problem. And yes we need to fix it. Maybe get
round a whiteboard with some beers. Think outside the box and this problem
solves itself: have a mechanism for the access points to say 'ietf-legacy
is also me' and the client can upgrade. But that is just one detail and we
won't solve the user's problem if all we do is solve each problem as it
presents itself, taking three years each. Lets just design something that
does not stink and to do that we have to admit some of the reasons that
Security Usability remains miserable.


The big problem that I see with the Security Usability folk is that many
think it fine to say, 'users can't understand security indicators' so we
don't do them. This is wrong for several reasons.

1) We spend an inordinate amount of time telling users they they should
take care online but not how to make themselves safe. A product that
refuses to even let the user see the information that would allow an expert
to make that determination is a bad product.

So that is the first thing to realize. If the research tells you that your
product stinks. Don't you dare use that research to say that the problem is
impossible. Because your bosses-bosses-boss might just end up in a hearing
next to me and he might just end up agreeing with me.


2) If we can't give useful advice now, we have to work out how to change
the protocol so that we can in future. Users cannot understand a
Certificate Transparency log or a PKIX cert chain. But they might just be
able to intuit that the older a certificate is, the more likely it is that
they might understand it. Hence my proposal for a 'First Issued' aka
'Member Since' extension for certs.


3) The alternative is allowing certain large Internet services to turn
parts of the net into gated communities. Having obstructed (or demolished)
all the infrastructures that could provide some security for users against
the attacks THEY care about (identity theft, not mass surveillance) they
will stick to the big names they know and trust to prevent them going into
the 'bad' parts of the net.

This is of course the old walled gardens issue but in a different form. Oh
and my is the US Republican Party onto that one. If you look at the
legislation some members that claim to be anti-regulation have proposed
recently, it is a real eye opener.

The people I am meeting with know what I am and what my roles are. The
reason they are giving me time of day is because they know that a gated
community run by two companies very strongly aligned with their opposition
is not in their interest. It is not in our interest either to have security
systems to be a part of applications and platforms that are welded in so
the user has no choice over them.

Microsoft recognizes this, that is why there is an API for anti-virus to
plug into and you can choose to use the Microsoft one or a different one.

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">Let=
s face it, the whole WiFi connection thing is junk and it is a part of the =
network that is not in a place where the IETF usually acts - the UI.</div><=
div class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=
=3D"gmail_default" style=3D"font-size:small">Well, that is fine because the=
 IETF is part of ISOC and do you know what else just became a part of ISOC?=
 The Online Trust Alliance. And they are all about security, trust and UI.<=
/div><div class=3D"gmail_default" style=3D"font-size:small"><br></div><div =
class=3D"gmail_default" style=3D"font-size:small">I think that we maybe sho=
uld have a talk about this with some ISOC folk because it is definitely an =
area where maybe we need a bit of &#39;joined up standards making&#39;. The=
re are parts of this problem that lie in CABForum space, OTA space and IETF=
 space.</div><div class=3D"gmail_default" style=3D"font-size:small"><br></d=
iv><div class=3D"gmail_default" style=3D"font-size:small">I presume that th=
ere will be ISOC people there. We should talk about what parts of the probl=
em should lie where. I am not happy with the fact that the WiFi alliance ha=
s still not provided a secure user experience after all this time and obvio=
usly sees no need for one.</div><div class=3D"gmail_default" style=3D"font-=
size:small"><br></div><div class=3D"gmail_default" style=3D"font-size:small=
">This issue is becoming a very serious political issue and has been the re=
ason that I have been making trips to D.C. recently to speak to members of =
Congress and their staff. With Congress gridlocked, the range of legislatio=
n they can get through is small, the only thing that people can agree on is=
 the need for better cyber security. Do people want to have that conversati=
on under the ISOC umbrella or do I have to use congressional staffers to ja=
ckhammer the obvious into people&#39;s management chains?</div><div class=
=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_=
default" style=3D"font-size:small"><br></div><div class=3D"gmail_default" s=
tyle=3D"font-size:small">Yes, the WiFi thing is a problem. And yes we need =
to fix it. Maybe get round a whiteboard with some beers. Think outside the =
box and this problem solves itself: have a mechanism for the access points =
to say &#39;ietf-legacy is also me&#39; and the client can upgrade. But tha=
t is just one detail and we won&#39;t solve the user&#39;s problem if all w=
e do is solve each problem as it presents itself, taking three years each. =
Lets just design something that does not stink and to do that we have to ad=
mit some of the reasons that Security Usability remains miserable.</div><di=
v class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D=
"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_def=
ault" style=3D"font-size:small">The big problem that I see with the Securit=
y Usability folk is that many think it fine to say, &#39;users can&#39;t un=
derstand security indicators&#39; so we don&#39;t do them. This is wrong fo=
r several reasons.</div><div class=3D"gmail_default" style=3D"font-size:sma=
ll"><br></div><div class=3D"gmail_default" style=3D"font-size:small">1) We =
spend an inordinate amount of time telling users they they should take care=
 online but not how to make themselves safe. A product that refuses to even=
 let the user see the information that would allow an expert to make that d=
etermination is a bad product.</div><div class=3D"gmail_default" style=3D"f=
ont-size:small"><br></div><div class=3D"gmail_default" style=3D"font-size:s=
mall">So that is the first thing to realize. If the research tells you that=
 your product stinks. Don&#39;t you dare use that research to say that the =
problem is impossible. Because your bosses-bosses-boss might just end up in=
 a hearing next to me and he might just end up agreeing with me.</div><div =
class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"g=
mail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_defau=
lt" style=3D"font-size:small">2) If we can&#39;t give useful advice now, we=
 have to work out how to change the protocol so that we can in future. User=
s cannot understand a Certificate Transparency log or a PKIX cert chain. Bu=
t they might just be able to intuit that the older a certificate is, the mo=
re likely it is that they might understand it. Hence my proposal for a &#39=
;First Issued&#39; aka &#39;Member Since&#39; extension for certs.</div><di=
v class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D=
"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_def=
ault" style=3D"font-size:small">3) The alternative is allowing certain larg=
e Internet services to turn parts of the net into gated communities. Having=
 obstructed (or demolished) all the infrastructures that could provide some=
 security for users against the attacks THEY care about (identity theft, no=
t mass surveillance) they will stick to the big names they know and trust t=
o prevent them going into the &#39;bad&#39; parts of the net.</div><div cla=
ss=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmai=
l_default" style=3D"font-size:small">This is of course the old walled garde=
ns issue but in a different form. Oh and my is the US Republican Party onto=
 that one. If you look at the legislation some members that claim to be ant=
i-regulation have proposed recently, it is a real eye opener.=C2=A0</div><d=
iv class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=
=3D"gmail_default" style=3D"font-size:small">The people I am meeting with k=
now what I am and what my roles are. The reason they are giving me time of =
day is because they know that a gated community run by two companies very s=
trongly aligned with their opposition is not in their interest. It is not i=
n our interest either to have security systems to be a part of applications=
 and platforms that are welded in so the user has no choice over them.</div=
><div class=3D"gmail_default" style=3D"font-size:small"><br></div><div clas=
s=3D"gmail_default" style=3D"font-size:small">Microsoft recognizes this, th=
at is why there is an API for anti-virus to plug into and you can choose to=
 use the Microsoft one or a different one.</div><div class=3D"gmail_default=
" style=3D"font-size:small"><br></div></div>

--94eb2c19bb2ec55f2d0554209673--


From nobody Wed Jul 12 09:30:24 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3758213172B for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 09:30:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 HOpSACFi16Yd for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 09:30:21 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C0CD1300CF for <ietf@ietf.org>; Wed, 12 Jul 2017 09:30:21 -0700 (PDT)
Received: (qmail 78475 invoked from network); 12 Jul 2017 16:30:20 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 12 Jul 2017 16:30:20 -0000
Date: 12 Jul 2017 16:29:58 -0000
Message-ID: <20170712162958.3037.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Cc: vaibhavsinghacads@gmail.com
Subject: Re: Need for secured email delegation workflow
In-Reply-To: <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fXu1LqtY27bYJmUhKzSZKuV0UIs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 16:30:22 -0000

In article <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com> you write:
>I was working on implementing Email Delegation for my email server, and
>felt a need to highlight a couple of things.

Email Delegation is not as far as I can tell a phrase that has ever
appeared in an RFC, and I have no idea what it means.

Can you tell us what you're trying to do?

R's,
John


From nobody Wed Jul 12 09:42:55 2017
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D1F2131731 for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 09:42:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.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 pOUqjxsrWJLh for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 09:42:52 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 3C58D131725 for <ietf@ietf.org>; Wed, 12 Jul 2017 09:42:52 -0700 (PDT)
Received: from [10.35.254.222] (sccc-208-115-86-69.smartcity.com [208.115.86.69] (may be forged)) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v6CGh3gj014483 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 12 Jul 2017 09:43:04 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1499877784; bh=Twj/8fOM2h6wHZd83yqL4mAsN84WGGVs2reEz0cZYJU=; h=Subject:To:References:Cc:Reply-To:From:Date:In-Reply-To:From; b=RSwDeEdcGDfPezOq9g6hkgEy+vOPKJtmmoWyuPRxDYkHW4JYXd2Ty99yQuI9BGP73 UTf+mHuiC4QztpgTnXZnroid2CUYhem9gAo+CZqArEZutqWd3crn79u9GhYzO2XRI4 hjFHikOFVxi0KabeJ89QnDLfut3vfVZ+DC8lR9Y0=
Subject: Re: Need for secured email delegation workflow
To: vaibhav singh <vaibhavsinghacads@gmail.com>
References: <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com>
Cc: ietf@ietf.org
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <bce5e020-5dd2-2c16-70a1-6ea68a859ad3@dcrocker.net>
Date: Wed, 12 Jul 2017 09:42:49 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tz7xzBUXBK341IE69f-hgrpQcrs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 16:42:53 -0000

On 7/12/2017 12:03 AM, vaibhav singh wrote:
> 1.) I could not find a place where this workflow is outlined.


It's possible that Internet Mail Architecture (RFC 5598) will assist 
your efforts, including use of common vocabulary.


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Wed Jul 12 09:57:01 2017
Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1633B131751 for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 09:56:59 -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] 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 j0U2wU6bq9eF for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 09:56:58 -0700 (PDT)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [108.5.242.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FB4B13173F for <ietf@ietf.org>; Wed, 12 Jul 2017 09:56:58 -0700 (PDT)
Received: from vpro.lan (cpe-74-71-8-253.nyc.res.rr.com [74.71.8.253]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mournblade.imrryr.org (Postfix) with ESMTPSA id 14C2D7A32F1 for <ietf@ietf.org>; Wed, 12 Jul 2017 16:56:57 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Need for secured email delegation workflow
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com>
Date: Wed, 12 Jul 2017 12:56:56 -0400
Content-Transfer-Encoding: quoted-printable
Reply-To: IETF general list <ietf@ietf.org>
Message-Id: <7712EED1-9F72-4155-853A-6CC02572222E@dukhovni.org>
References: <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com>
To: IETF general list <ietf@ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/j6zT-3Ql6TBW9Jv3pTdqqouoVYA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 16:57:00 -0000

> On Jul 12, 2017, at 3:03 AM, vaibhav singh =
<vaibhavsinghacads@gmail.com> wrote:
>=20
> I was working on implementing Email Delegation for my email server, =
and felt a need to highlight a couple of things.=20
>=20
> 1.) I could not find a place where this workflow is outlined. It seems =
like everyone, from Microsoft to Google, have an implementation for =
email delegation, and they are all kind of doing their own thing.

I suspect this topic is not really appropriate for this list, so I'll =
keep this brief.

> Am I missing something here? Is this something which should be an =
Internet draft/RFC?

It seems you want to authorize a third party to send email on your =
behalf.
It is not clear that logistical guidance of how to do is proper subject
matter for an RFC.  The relevant technical standards are:

	* DKIM, allows you to delegate a keypair and a "selector" for a =
third
	  party to send authenticated email with =
"d=3D<yourdomain.example>"

	* SPF, allows you designate a set of SMTP clients that are =
authorized
	  to originate email with envelope sender addresses in your =
mail.

	* SMTP generally allows any client to send from any domain.  Any
          constraints that block third parties from sending on behalf of
	  of your domain are "self inflicted" (restrictive SPF, =
abominable
          DMARC).  To the extent that you employ these, they provide the
          means to exempt third parties from your own restrictive =
policies.

Any process that the third party wants you to follow in order to =
register
with them to send on your behalf is I think outside the scope of IETF
standards.

--=20
	Viktor.=


From nobody Wed Jul 12 10:11:02 2017
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D69B4131745 for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 10:10:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-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=yitter.info header.b=hzDPLuiw; dkim=pass (1024-bit key) header.d=yitter.info header.b=IBdr0sv0
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 E0RIBYqLBD4j for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 10:10:52 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8E8D131738 for <ietf@ietf.org>; Wed, 12 Jul 2017 10:10:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id B0411C03BA for <ietf@ietf.org>; Wed, 12 Jul 2017 17:10:20 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1499879420; bh=atlHumScE2TBFAA2JYzckUKAStI2wGTP1/yp6Rx7tqU=; h=Date:From:To:Subject:References:In-Reply-To:From; b=hzDPLuiwtKgXXoCnA/yY7uxx5djtQIA6gPswjkgcWuTjci50nz1qEgkqX0u6EThR/ 9iC1HsplhI75E39P+vP7tH7o6rAMXZclM5Yt0peW9DUo7aYA7yRs0M1gqogKaySIxV rbaKr+NU0JrL3izIyaYNidhcZVMIqMvXEC8/IzYM=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I_l1gYKMeBeJ for <ietf@ietf.org>; Wed, 12 Jul 2017 17:10:19 +0000 (UTC)
Date: Wed, 12 Jul 2017 13:10:19 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1499879419; bh=atlHumScE2TBFAA2JYzckUKAStI2wGTP1/yp6Rx7tqU=; h=Date:From:To:Subject:References:In-Reply-To:From; b=IBdr0sv0AFXbPeyNDLaxA5J50+2dxIZrMx+QJFExsXAD2+8Ri7lLgVRaEukpD2ahL 55hGOnEDMVyCwa7ZPv2YrDeN2pkYFQh4HVaEvaqhloWRRiflePP2ZKl4QqjrtD5G4X 5/ftKM4hczETBCNasjxEQ8oGung/Tk3RhdPl46Wg=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Need for secured email delegation workflow
Message-ID: <20170712171019.jn42poj4lx7l73ru@mx4.yitter.info>
References: <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com> <7712EED1-9F72-4155-853A-6CC02572222E@dukhovni.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7712EED1-9F72-4155-853A-6CC02572222E@dukhovni.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/95__oZucB4juULrAtEWTGAZPweQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 17:10:58 -0000

On Wed, Jul 12, 2017 at 12:56:56PM -0400, Viktor Dukhovni wrote:
> It seems you want to authorize a third party to send email on your behalf.
> It is not clear that logistical guidance of how to do is proper subject
> matter for an RFC.

Why?  We have a whole area dedicated to Management and Operations,
including one named DNSOP.

> Any process that the third party wants you to follow in order to register
> with them to send on your behalf is I think outside the scope of IETF
> standards.

The more general thing is that there is no way for a domain operator
to signal to a possible vendor its authority to allow said vendor to
operate $thing on the domain operator's behalf.  It would have been
nice if the protocol we stumbled into creating that was well-suited to
this (RDAP) didn't have a bootstrapping mechanism that was nailed to
the historical facts about whois, but some of us lost that fight in
the WG.  The way this is mostly done today is to put a bunch of TXT
records at the apex of the zone in question, thereby permanently
bloating DNS answers for large numbers of domains for no good reason
(and offering a useful amplification mechanism in passing).

I can think of more than one existing IETF standard that might be good
for this, but I can't think of one that solves the use case today.  It
might be a useful thing for some of us to discuss in the halls in
Prague.  If anyone is interested in having that conversation, please
contact me off-list.  I hear there is beer in Prague.  Maybe we can
arrange for various birds to get together in a bar rather than a hall.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Wed Jul 12 11:34:23 2017
Return-Path: <alissa@cooperw.in>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52E3A131781 for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 11:34:21 -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, HTML_MESSAGE=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=cooperw.in header.b=nngA9Gov; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=re/P5wGY
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 dprK_yWh83El for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 11:34:19 -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 0BF0E131782 for <ietf@ietf.org>; Wed, 12 Jul 2017 11:34:19 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 56C0B20B90 for <ietf@ietf.org>; Wed, 12 Jul 2017 14:34:18 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Wed, 12 Jul 2017 14:34:18 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= 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=anpj53S3aNXBV/3BHQPqO9oyupJD3b7QX9ZXNrbeF zw=; b=nngA9GovORhRWae/Pi5qq7IH493VAqvNEefIbund2bPrM0+Am77sFuHuB UqZXJ3w+XZ+5FQEGDYupjopKirRUSd12iq8BUZrf64MJbLOPrhfkgo7zoeKuLmhm 2zTftNOQ8f2O6nogO3vXTXMPghR2Atf3qJwZV4WwRinaV3DOXtc5JFa6T0DBJjbA A479WVpxPXb4oh1d3u7IplB3Ih1Nd7TZX3V5tEDPQEv0LAZM+NyHU6paNVD5pfsE Tui9ZxmTGSG3HwiDPnhKD+XqIsCLgZbSxF6FGtjaa5LxVRFXs7/2u9A84Tq0w3LE M3NzZknGRBld7iP7DryMkf5ax9lJQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=anpj53S3aNXBV/3BHQ PqO9oyupJD3b7QX9ZXNrbeFzw=; b=re/P5wGYREAlSBhiPIoNJNkog4J4M7/+D8 uVqsjescxSndfRsa5GTIjzAmXxrx7ZuZLCwNz4mmNn1aRyF9RtvomtwI+i6jlRNh IdKnudCSBAFFJ3kNqm61KDY4no0lpBKZpLsceMVI0BLEsBCBeJuiwJNfgnOE1FiQ 7gdDVNrKvUiTlOU0d563Yya7wXAb8NpTbCd1E9mYK79/133cK0dCfXnU93avNc6x lv/y8ZwHm7poKa4odlXEoGNw8Z8vaHXUlg7sHVV7axV2MooSGd0QyLTR8OY24vVf cQGvdLxh4MD0EDeQmuuV5Hs+C8t9UKViZ4D6BRLz4wHiu5G8h14Q==
X-ME-Sender: <xms:qmtmWXygTJpLcpAOjI2Z3UzmSjvy7HljvBBpaXGlH7aC-42XRFZnxQ>
X-Sasl-enc: Uqgdfgc8Ryfc4tqBGje8e91yBVst5k/Is9vFOvKicrC7 1499884457
Received: from sjc-alcoop-8816.cisco.com (unknown [128.107.241.173]) by mail.messagingengine.com (Postfix) with ESMTPA id C72CE7E21C for <ietf@ietf.org>; Wed, 12 Jul 2017 14:34:17 -0400 (EDT)
From: Alissa Cooper <alissa@cooperw.in>
Content-Type: multipart/alternative; boundary="Apple-Mail=_958A9AC3-CC4B-4241-B7F1-EE31079D4792"
Message-Id: <6D02B052-4151-4718-8BAB-F9FFE8E387F1@cooperw.in>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Saturday as start day
Date: Wed, 12 Jul 2017 14:34:16 -0400
References: <63406DFB-217A-4306-B717-E86D97BA2AA9@cooperw.in>
To: IETF Discussion <ietf@ietf.org>
In-Reply-To: <63406DFB-217A-4306-B717-E86D97BA2AA9@cooperw.in>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ouvkfzno8qrRhN6-EdWN9GjFFAE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 18:34:21 -0000

--Apple-Mail=_958A9AC3-CC4B-4241-B7F1-EE31079D4792
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Thanks to everyone for the feedback. Based on the feedback, the IESG is =
going to go ahead with this change starting with IETF 100. We will also =
incorporate the comments received about the length of the meeting week =
into ongoing IESG discussions about different ways of managing the =
agenda time overall.

Alissa

> On Jun 21, 2017, at 8:34 AM, Alissa Cooper <alissa@cooperw.in> wrote:
>=20
> Hi all,
>=20
> Based on a suggestion from Paul Hoffman, the IESG believes it would be =
beneficial to denote the official start of IETF meetings to be on =
Saturday rather than Sunday, starting with IETF 100. We believe this =
would be sensible given that events such as the hackathon and code =
sprint start on Saturday, and may make it easier for some participants =
to get travel approval to attend those events. This change would be =
reflected in the dates posted on the IETF web site and sent out in email =
announcements. We are not proposing any changes in terms of the =
scheduling of any meeting-related events, the full availability of the =
meeting network starting on Sunday, the opening of on-site registration, =
or the meeting fee.
>=20
> If you have feedback about this change, please send it to =
ietf@ietf.org <mailto:ietf@ietf.org>, or exceptionally to iesg@ietf.org =
<mailto:iesg@ietf.org>, by July 5, 2017.
>=20
> Thanks,
> The IESG


--Apple-Mail=_958A9AC3-CC4B-4241-B7F1-EE31079D4792
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div class=3D"">Thanks to everyone for the feedback. Based on =
the feedback, the IESG is going to go ahead with this change starting =
with IETF 100. We will also incorporate the comments received about the =
length of the meeting week into ongoing IESG discussions about different =
ways of managing the agenda time overall.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Alissa</div><br =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
Jun 21, 2017, at 8:34 AM, Alissa Cooper &lt;<a =
href=3D"mailto:alissa@cooperw.in" class=3D"">alissa@cooperw.in</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><meta =
http-equiv=3D"Content-Type" content=3D"text/html charset=3Dus-ascii" =
class=3D""><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space;" class=3D"">Hi all,<div =
class=3D""><br class=3D""></div><div class=3D""><div class=3D"">Based on =
a suggestion from Paul Hoffman, the IESG believes it would be beneficial =
to denote the official start of IETF meetings to be on Saturday rather =
than Sunday, starting with IETF 100. We believe this would be sensible =
given that events such as the hackathon and code sprint start on =
Saturday, and may make it easier for some participants to get travel =
approval to attend those events. This change would be reflected in the =
dates posted on the IETF web site and sent out in email announcements. =
We are not proposing any changes in terms of the scheduling of any =
meeting-related events, the full availability of the meeting network =
starting on Sunday, the opening of on-site registration, or the meeting =
fee.</div><div class=3D""><br class=3D""></div><div class=3D"">If you =
have feedback about this change, please send it to&nbsp;<a =
href=3D"mailto:ietf@ietf.org" class=3D"">ietf@ietf.org</a>, or =
exceptionally to&nbsp;<a href=3D"mailto:iesg@ietf.org" =
class=3D"">iesg@ietf.org</a>, by July 5, 2017.<br class=3D""><br =
class=3D"">Thanks,<br class=3D"">The =
IESG</div></div></div></div></blockquote></div><br =
class=3D""></body></html>=

--Apple-Mail=_958A9AC3-CC4B-4241-B7F1-EE31079D4792--


From nobody Wed Jul 12 12:34:45 2017
Return-Path: <sanjay.mishra@verizon.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E0ED12EAF7 for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 12:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=verizon.com header.b=uhsXUO3V; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=verizon.com header.b=Bs9wD/xf; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=verizon.com header.b=Bs9wD/xf
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 7p30n7defIVn for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 12:34:43 -0700 (PDT)
Received: from omzsmtpe02.verizonbusiness.com (omzsmtpe02.verizonbusiness.com [199.249.25.209]) (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 20E6612EA74 for <ietf@ietf.org>; Wed, 12 Jul 2017 12:34:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verizon.com; i=@verizon.com; q=dns/txt; s=corp; t=1499888083; x=1531424083; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=RA6tYO/S2ey14UMO47ZdtRze3Nx8xf1kEFhyHkR4490=; b=uhsXUO3VntEtw+7zOhqBVCoo4qIMBu5rPzFJxEp+wMrwAMj2CPLj63pk NZDoJWR01HFPTGuNrIRU6xP2sbUFiH3P6bKRpd5wZNxZJFS8kU1o52nSg jqjmBkYPrB7fTznVL+BhtVMW+eLHZGtFuXhHJIgeDj/VGic4ZL5iQuqh2 M=;
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi01.verizon.com) ([166.68.71.143]) by omzsmtpe02.verizonbusiness.com with ESMTP; 12 Jul 2017 19:34:41 +0000
From: "Mishra, Sanjay" <sanjay.mishra@verizon.com>
X-IronPort-AV: E=Sophos;i="5.39,316,1493683200"; d="scan'208";a="231138007"
Received: from rogue-10-255-192-101.rogue.vzwcorp.com (HELO atlantis.verizonwireless.com) ([10.255.192.101]) by fldsmtpi01.verizon.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 12 Jul 2017 19:34:06 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verizon.com; i=@verizon.com; q=dns/txt; s=corp; t=1499888046; x=1531424046; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=RA6tYO/S2ey14UMO47ZdtRze3Nx8xf1kEFhyHkR4490=; b=Bs9wD/xfpM0YYd576iK5yyIZamnXuHXCEzRccm8BxkBIITfTvvJ0IsW/ Cv6cejDejK/Tn4flN3mbmaStuYhRo7agstMZglmCVrYbNStAG1vBVwVug EErDjEsQBrMGEF959nK5UqMoDp1M6p5OJWzoEBnT3W1q/O2tE2qe5vQn6 M=;
Received: from discovery.odc.vzwcorp.com (HELO mercury.verizonwireless.com) ([10.255.240.25]) by atlantis.verizonwireless.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 12 Jul 2017 15:34:06 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verizon.com; i=@verizon.com; q=dns/txt; s=corp; t=1499888046; x=1531424046; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=RA6tYO/S2ey14UMO47ZdtRze3Nx8xf1kEFhyHkR4490=; b=Bs9wD/xfpM0YYd576iK5yyIZamnXuHXCEzRccm8BxkBIITfTvvJ0IsW/ Cv6cejDejK/Tn4flN3mbmaStuYhRo7agstMZglmCVrYbNStAG1vBVwVug EErDjEsQBrMGEF959nK5UqMoDp1M6p5OJWzoEBnT3W1q/O2tE2qe5vQn6 M=;
X-Host: discovery.odc.vzwcorp.com
Received: from casac1exh002.uswin.ad.vzwcorp.com ([10.11.218.44]) by mercury.verizonwireless.com with ESMTP/TLS/AES128-SHA256; 12 Jul 2017 19:34:06 +0000
Received: from scwexch01apd.uswin.ad.vzwcorp.com (153.114.130.20) by CASAC1EXH002.uswin.ad.vzwcorp.com (10.11.218.44) with Microsoft SMTP Server (TLS) id 14.3.248.2; Wed, 12 Jul 2017 12:33:40 -0700
Received: from OMZP1LUMXCA06.uswin.ad.vzwcorp.com (144.8.22.179) by scwexch01apd.uswin.ad.vzwcorp.com (153.114.130.20) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Wed, 12 Jul 2017 12:33:40 -0700
Received: from OMZP1LUMXCA08.uswin.ad.vzwcorp.com (144.8.22.181) by OMZP1LUMXCA06.uswin.ad.vzwcorp.com (144.8.22.179) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Wed, 12 Jul 2017 14:33:38 -0500
Received: from OMZP1LUMXCA08.uswin.ad.vzwcorp.com ([144.8.22.181]) by OMZP1LUMXCA08.uswin.ad.vzwcorp.com ([144.8.22.181]) with mapi id 15.00.1263.000; Wed, 12 Jul 2017 14:33:39 -0500
To: Randy Bush <randy@psg.com>, IETF Rinse Repeat <ietf@ietf.org>
Subject: RE: [E] meeting ietf-legacy ssid
Thread-Topic: [E] meeting ietf-legacy ssid
Thread-Index: AQHS+qa2rAuvCvKA/E6KKp7qzD3OjaJQlIQQ
Date: Wed, 12 Jul 2017 19:33:39 +0000
Message-ID: <3517db0060ab459baf07d494b91b9791@OMZP1LUMXCA08.uswin.ad.vzwcorp.com>
References: <m2eftmwl0l.wl-randy@psg.com>
In-Reply-To: <m2eftmwl0l.wl-randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.144.60.250]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tJ_UW493dChlv5GQ5OTl3S6esnU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 19:34:44 -0000

On Wed, 12 Jul 2017, Randy Bush wrote:

>the noc sees a quite large number of associations to the unencrypted ietf-=
legacy ssid as opposed to say the encrypted ietf ssid

>some of us are wondering if those using ietf-legacy

>  o do not realize it is completely unencrypted over the air, or

>  o don't care as their threat model sees runnin' nekkid over the air as
    not a significant additional weakness, or

My corporate laptop using any major browser, such as Chrome, Firefox or IE,=
 fails to bind. The error message pops up a message something along the lin=
es that cannot validate the SSL owner or certificate....And sadly, leaving =
no choice but to connect to IETF-legacy or IETF-Hotel. I will be happy to w=
alk over to the NOC to help troubleshoot.


From nobody Wed Jul 12 13:13:22 2017
Return-Path: <fluffy@iii.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98EF712EC3A for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 13:13:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 IR6ly0aPgMRD for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 13:13:19 -0700 (PDT)
Received: from smtp94.ord1c.emailsrvr.com (smtp94.ord1c.emailsrvr.com [108.166.43.94]) (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 5946112EAF7 for <ietf@ietf.org>; Wed, 12 Jul 2017 13:13:19 -0700 (PDT)
Received: from smtp12.relay.ord1c.emailsrvr.com (localhost [127.0.0.1]) by smtp12.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id A2184C0673; Wed, 12 Jul 2017 16:13:16 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp12.relay.ord1c.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 06CF2C028F;  Wed, 12 Jul 2017 16:13:15 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [192.168.4.119] ([UNAVAILABLE]. [128.107.241.185]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:587 (trex/5.7.12); Wed, 12 Jul 2017 16:13:16 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: meeting ietf-legacy ssid
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <m2eftmwl0l.wl-randy@psg.com>
Date: Wed, 12 Jul 2017 14:13:14 -0600
Cc: IETF Rinse Repeat <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F2B610F6-D55F-4283-8CD9-82949D514606@iii.ca>
References: <m2eftmwl0l.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dHvJBQtQQgHdilFPPnm3cag2m7I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 20:13:21 -0000

I use "IETF Legacy" because 1) it is easy 2) if you think encrypting =
your traffic over the first 50 feet is all you need to do, well what can =
I say. (and of course I understand Randy and probably everyone else on =
this thread does not think that)

I'd use something else if it was as easy and worked as well - perhaps if =
we turned off Legacy, I would be forced to discover there was something =
I liked better but in general I am at IETF to get work done not to eat =
dog food. In general I think that the IETF has spent a good amount of =
time on "making it harder for the bad guys" but not enough time on =
making security "easy for the good guys".=20



> On Jul 11, 2017, at 6:34 PM, Randy Bush <randy@psg.com> wrote:
>=20
> the noc sees a quite large number of associations to the unencrypted
> ietf-legacy ssid as opposed to say the encrypted ietf ssid
>=20
> some of us are wondering if those using ietf-legacy
>=20
>  o do not realize it is completely unencrypted over the air, or
>=20
>  o don't care as their threat model sees runnin' nekkid over the air =
as
>    not a significant additional weakness, or
>=20
>  o believe that they are using sufficient encryption at higher layers
>    to meet their needs, or
>=20
>  o other
>=20
> these days, some meetings do not provide unencrypted wifi at all and
> seem not to get complaints.  maybe their attendees are just geekier
> and/or more security conscious.
>=20
> clue bat, please.  unicast responses accepted too.
>=20
> randy
>=20


From nobody Wed Jul 12 13:30:07 2017
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCFDA12EC57 for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 13:30:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.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 iTqAqdx-pLCp for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 13:30:05 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 F3DBB12EC0B for <ietf@ietf.org>; Wed, 12 Jul 2017 13:30:04 -0700 (PDT)
Received: from [10.35.254.222] (sccc-208-115-86-69.smartcity.com [208.115.86.69] (may be forged)) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v6CKUHxn026471 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for <ietf@ietf.org>; Wed, 12 Jul 2017 13:30:18 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1499891418; bh=j7bPadh4dXJyIWEhm/3WDQRkcEi0J9pSSGUu8SASiTk=; h=Subject:To:References:Reply-To:From:Date:In-Reply-To:From; b=kYiqmOT8STpA5uwDkaz5unksUH08VDtDJu5kuRoGIZNRelbfdCmOuTBXm4wpw4ajY c90rwkqhqbpJTGax1AgueeAcc868ytN+NSxrljVBOYxw69K3Y9V+1xrGfy4U+dP9KQ NmeqRQyggfxmhlt3De20t3PoZgQjur27yu+AKTEU=
Subject: Re: meeting ietf-legacy ssid
To: ietf@ietf.org
References: <m2eftmwl0l.wl-randy@psg.com>
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <b96df1c5-7b07-de1a-a78f-0e8a4c2ac6b7@dcrocker.net>
Date: Wed, 12 Jul 2017 13:30:03 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <m2eftmwl0l.wl-randy@psg.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Tv8d25d1NaEm1jgVSbP4KxZeRmg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 20:30:06 -0000

On 7/11/2017 5:34 PM, Randy Bush wrote:
>    o don't care as their threat model sees runnin' nekkid over the air as
>      not a significant additional weakness, or
> 
>    o believe that they are using sufficient encryption at higher layers
>      to meet their needs, or


Given that it is likely that at least one of the 1200 open-participation 
IETF meeting attendees -- all of whom have access to the WiFi password 
-- sometimes indulges in bad actor behavior, then it might be worth 
clarifying exactly what the incremental benefit is, in having WiFi 
encryption, if one is already using TLS liberally.

(For extra credit, it would be interesting to see where this benefit is 
already documented on the net.)

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Wed Jul 12 18:24:15 2017
Return-Path: <Xufeng_Liu@jabil.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E8F412EC12; Wed, 12 Jul 2017 18:24:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.7
X-Spam-Level: 
X-Spam-Status: No, score=-4.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_HELO_PASS=-0.001, 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=jabil.onmicrosoft.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 Q60hsl2EobF6; Wed, 12 Jul 2017 18:24:03 -0700 (PDT)
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (mail-sn1nam01on0091.outbound.protection.outlook.com [104.47.32.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E56B120726; Wed, 12 Jul 2017 18:24:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jabil.onmicrosoft.com;  s=selector1-jabil-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=lCl8IlIeMZs3RRi9HtG31nwjTiQ1dO/cF9F8NhCj9pM=; b=Af29lqJS+dRoh+2S2CEXr+3RPB69/LL/9Fknfv2iZtFXmKUTts1iP3Fhq2aYwYb7AXrjdQBNwJWqJ5SULbrT8iYOTdlys/wH28SvwdC7Bb/GSirIZXsNn3FpBU8ctPelAzFlDIDBs434htaFy9e6Vn4Xdw3YbrEFHli5fmO5aM8=
Received: from BN3PR0201MB0867.namprd02.prod.outlook.com (10.160.154.13) by BN3PR0201MB0867.namprd02.prod.outlook.com (10.160.154.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1261.13; Thu, 13 Jul 2017 01:24:00 +0000
Received: from BN3PR0201MB0867.namprd02.prod.outlook.com ([10.160.154.13]) by BN3PR0201MB0867.namprd02.prod.outlook.com ([10.160.154.13]) with mapi id 15.01.1261.015; Thu, 13 Jul 2017 01:24:00 +0000
From: Xufeng Liu <Xufeng_Liu@jabil.com>
To: Mahesh Jethanandani <mjethanandani@gmail.com>, Xufeng Liu <xufeng.liu.ietf@gmail.com>
CC: Robert Wilton <rwilton@cisco.com>, Benoit Claise <bclaise@cisco.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "teas@ietf.org" <teas@ietf.org>, "draft-ietf-teas-yang-te-topo.all@ietf.org" <draft-ietf-teas-yang-te-topo.all@ietf.org>
Subject: RE: [Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-08
Thread-Topic: [Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-08
Thread-Index: AQHS1KSedaTR9X/fGEeQz0ke1nZ/sKIh1EjwgA1lWACAASg0QIAAZ0GAgAANhoCAADiPAIAGGnuAgAolVQCAAMDXAIAA3W6AgAYC9oCACFOv4A==
Date: Thu, 13 Jul 2017 01:24:00 +0000
Message-ID: <BN3PR0201MB0867067D89B713E9D212C841F1AC0@BN3PR0201MB0867.namprd02.prod.outlook.com>
References: <149564066257.28529.12761629961042171907@ietfa.amsl.com> <BN3PR0201MB08670E55FFB5470F338E998DF1CD0@BN3PR0201MB0867.namprd02.prod.outlook.com> <5d4541d3-9426-787d-e02b-9c2dbc3a5400@cisco.com> <BN3PR0201MB0867315F3E88577B9EEF6584F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com> <3a1c319f-0255-b8ee-ecbd-739568c1dc7f@cisco.com> <1ab3a0d8-de3e-1d7c-2967-97b74b1c68a5@cisco.com> <BN3PR0201MB0867664CBDA460C283DC8043F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com> <04b933e2-189a-6fe2-5d24-310167f91b69@cisco.com> <00d001d2f37c$22d3dd10$687b9730$@gmail.com> <a83f8acd-2c14-2d28-f196-96b5fd7833a9@cisco.com> <024a01d2f44b$465229c0$d2f67d40$@gmail.com> <57EAC7E8-66B5-43D7-AA03-3D5E1008FC49@gmail.com>
In-Reply-To: <57EAC7E8-66B5-43D7-AA03-3D5E1008FC49@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-dg-ref: PG1ldGE+PGF0IG5tPSJib2R5Lmh0bWwiIHA9ImM6XHVzZXJzXHhsaXVcYXBwZGF0YVxyb2FtaW5nXDA5ZDg0OWI2LTMyZDMtNGE0MC04NWVlLTZiODRiYTI5ZTM1Ylxtc2dzXG1zZy1mMTkxNzU2ZS02NzY5LTExZTctOWMxYS0xODVlMGZlM2M0NWNcYW1lLXRlc3RcZjE5MTc1NzAtNjc2OS0xMWU3LTljMWEtMTg1ZTBmZTNjNDVjYm9keS5odG1sIiBzej0iMzkxNDYiIHQ9IjEzMTQ0MzgyNjM5MzM1NjY5OCIgaD0iTDVRam9hNlhhZkF2VWY0VUZ1UnlmaDQxa2xvPSIgaWQ9IiIgYmw9IjAiIGJvPSIxIi8+PC9tZXRhPg==
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=jabil.com;
x-originating-ip: [72.209.195.86]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN3PR0201MB0867; 7:zMrJJgHm3yC3a+ApIRNKuegofb15x0wfz3rKIEZsDBa4BZnEfT15M01njtNTXwKzVu0TY2jZZh/7fE9X2d0mvziCoZ1UGMSdBrmSZ3goIrpUtrz/UET5moYL80HXvsHcQ4SON52B5w+GMLke2ewhZwso7WbB9j7qv+TU491yBZz0D7dsiNyvv4ShsHqhsjm3oo3UjkiY7DPB0g0usQOcuysEiyiJhcuELLs595r3IVnaui8hWOj/wHPV6mPdxxMlNsP4h+CZm2VlEV1pHyqR4KfhIonP6qiql0dLdgmQtsvGlYBZ2y1JQrK8GjW3OIPaPyGTFfCyZrvCJE9CdXxMQZ7qAPoErSNQNAUv4auaGg659fBS1114PFIfbk1P+uUeTq5z6s5r5jQaLHyIQ9ANuOMbbgVSTwj5tuhCgmd6X7thflAFStT5h0yY9aCLxs/K2iUdSMGy3Q0i0tpFF9yt8IdnWuaKKvH0JHRcfZ6NRxi2gdyzt4c/in0EeVQHv7ArNA3wfiK56n7kPbAq3N8Zt/srSzTWedJCT57Gj3p5VupqHJMm+Mtd7T4uWOdwXlgp8uo7R4bhkE8WEUbtPcjPSdlm3AHWVZl7lWnIfToaRJ8Q2rVAC1hM17WLRbQ8IsCNqDdemSSx3m+BgHTMlbgGfH06fvH9FMONa9DbChocO4CTxSYk5CM2N+d2u3MIRe1d4TjztMByIQbD0nVVtFZtIpSpcZcKNXMzqyksSv8UEDf+l+zGZFUKpgbd0xJt3Sj3VyDJpDByUP+YaSwbewNEeaumhEEM7lQ/O4mhDdwyszk=
x-ms-office365-filtering-correlation-id: 2d742c48-a68a-4319-e4fe-08d4c98dd748
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(300000503095)(300135400095)(48565401081)(2017052603031)(201703131423075)(201703031133081)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:BN3PR0201MB0867; 
x-ms-traffictypediagnostic: BN3PR0201MB0867:
x-exchange-antispam-report-test: UriScan:(151999592597050)(278178393323532)(120809045254105)(166708455590820)(26388249023172)(236129657087228)(788757137089)(95692535739014)(21748063052155)(92977632026198);
x-microsoft-antispam-prvs: <BN3PR0201MB0867A240CCFD225B86D3D9D5F1AC0@BN3PR0201MB0867.namprd02.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(2017060910075)(5005006)(8121501046)(3002001)(100000703101)(100105400095)(93006095)(93001095)(10201501046)(6055026)(6041248)(20161123562025)(20161123564025)(20161123558100)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123560025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BN3PR0201MB0867; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BN3PR0201MB0867; 
x-forefront-prvs: 0367A50BB1
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(39450400003)(39400400002)(39410400002)(39840400002)(39850400002)(377454003)(51444003)(13464003)(24454002)(52584002)(606006)(54356999)(54896002)(53946003)(6246003)(9686003)(6306002)(236005)(3846002)(4326008)(102836003)(790700001)(25786009)(2906002)(72206003)(6116002)(189998001)(8936002)(3660700001)(53936002)(3280700002)(76176999)(5660300001)(14454004)(38730400002)(80792005)(50986999)(229853002)(7696004)(66066001)(9326002)(93886004)(39060400002)(74316002)(6506006)(8676002)(2900100001)(33656002)(68736007)(54906002)(478600001)(81166006)(77096006)(7736002)(6436002)(86362001)(55016002)(966005)(19609705001)(2950100002)(230783001)(99286003)(53546010); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR0201MB0867; H:BN3PR0201MB0867.namprd02.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BN3PR0201MB0867067D89B713E9D212C841F1AC0BN3PR0201MB0867_"
MIME-Version: 1.0
X-OriginatorOrg: jabil.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Jul 2017 01:24:00.4282 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bc876b21-f134-4c12-a265-8ed26b7f0f3b
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0201MB0867
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZxiWl50uBfenr7oG8ivUt1cpRUs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jul 2017 01:24:07 -0000

--_000_BN3PR0201MB0867067D89B713E9D212C841F1AC0BN3PR0201MB0867_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgTWFoZXNoLA0KDQpUaGFua3MuIFdlIHdpbGwgZml4IHRoZXNlIHdpdGhpbiBuZXh0IGZldyBk
YXlzLg0KDQpSZWdhcmRzLA0KLSBYdWZlbmcNCg0KRnJvbTogTWFoZXNoIEpldGhhbmFuZGFuaSBb
bWFpbHRvOm1qZXRoYW5hbmRhbmlAZ21haWwuY29tXQ0KU2VudDogRnJpZGF5LCBKdWx5IDcsIDIw
MTcgMjoxNCBQTQ0KVG86IFh1ZmVuZyBMaXUgPHh1ZmVuZy5saXUuaWV0ZkBnbWFpbC5jb20+DQpD
YzogUm9iZXJ0IFdpbHRvbiA8cndpbHRvbkBjaXNjby5jb20+OyBCZW5vaXQgQ2xhaXNlIDxiY2xh
aXNlQGNpc2NvLmNvbT47IFh1ZmVuZyBMaXUgPFh1ZmVuZ19MaXVAamFiaWwuY29tPjsgeWFuZy1k
b2N0b3JzQGlldGYub3JnOyBpZXRmQGlldGYub3JnOyB0ZWFzQGlldGYub3JnOyBkcmFmdC1pZXRm
LXRlYXMteWFuZy10ZS10b3BvLmFsbEBpZXRmLm9yZw0KU3ViamVjdDogUmU6IFtUZWFzXSBZYW5n
ZG9jdG9ycyBsYXN0IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtdGVhcy15YW5nLXRlLXRvcG8t
MDgNCg0KQWxzbywgY291cGxlIG9mIGNoYW5nZXMgaW4gdGhlIFlBTkcgbW9kdWxlczoNCg0KVW5k
ZXIgcmV2aXNpb24sIGNhbiB5b3UgbWFrZSBzdXJlIHRoZXJlIGlzIGEgcmVmZXJlbmNlIGJhY2sg
dG8gdGhlIFJGQyBudW1iZXIgdGhhdCB3aWxsIGJlIGFzc2lnbmVkIHRvIHRoZSBkcmFmdC4gU29t
ZXRoaW5nIGxpa2U6DQoNCiAgcmV2aXNpb24gIllZWVktTU0tREQiIHsNCiAgICBkZXNjcmlwdGlv
bg0KICAgICAiSW5pdGlhbCB2ZXJzaW9uIjsNCiAgICByZWZlcmVuY2UNCiAgICAgIlJGQyBYWFhY
OiBZQU5HIC0gVEUgVG9wb2xvZ3kiOw0KICB9DQoNCndpdGggYSBub3RlIHRvIFJGQyBlZGl0b3Ig
dG8gcmVwbGFjZSBYWFhYIHdpdGggdGhlIG51bWJlciBhc3NpZ25lZCB0byB0aGUgUkZDLg0KDQpQ
cmVmaXggb3JnYW5pemF0aW9uIHdpdGggSUVURi4gU29tZXRoaW5nIGxpa2Ug4oCcSUVURiBUcmFm
ZmljIEVuZ2luZWVyaW5nIEFyY2hpdGVjdHVyZSBhbmQgU2lnbmFsaW5nIChURUFTKSBXb3JraW5n
IEdyb3Vw4oCdDQoNCg0KVGhhbmtzLg0KDQoNCk9uIEp1bCAzLCAyMDE3LCBhdCAzOjI1IFBNLCBY
dWZlbmcgTGl1IDx4dWZlbmcubGl1LmlldGZAZ21haWwuY29tPG1haWx0bzp4dWZlbmcubGl1Lmll
dGZAZ21haWwuY29tPj4gd3JvdGU6DQoNCkhJIFJvYiwNCg0KSnVzdCBwb3N0ZWQgaHR0cHM6Ly9k
YXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi10ZWFzLXlhbmctdGUtdG9wby8gIHRv
IGZpeCB0aGUgc25pcHBldHMsIGFsb25nIHdpdGggYSBtaXNzaW5nIElBTkEgZW50cnkuDQoNClRo
YW5rcywNCi0gWHVmZW5nDQoNCkZyb206IFJvYmVydCBXaWx0b24gW21haWx0bzpyd2lsdG9uQGNp
c2NvLmNvbV0NClNlbnQ6IE1vbmRheSwgSnVseSAzLCAyMDE3IDU6MTMgQU0NClRvOiBYdWZlbmcg
TGl1IDx4dWZlbmcubGl1LmlldGZAZ21haWwuY29tPG1haWx0bzp4dWZlbmcubGl1LmlldGZAZ21h
aWwuY29tPj47ICdCZW5vaXQgQ2xhaXNlJyA8YmNsYWlzZUBjaXNjby5jb208bWFpbHRvOmJjbGFp
c2VAY2lzY28uY29tPj47ICdYdWZlbmcgTGl1JyA8WHVmZW5nX0xpdUBqYWJpbC5jb208bWFpbHRv
Olh1ZmVuZ19MaXVAamFiaWwuY29tPj47ICdNYWhlc2ggSmV0aGFuYW5kYW5pJyA8bWpldGhhbmFu
ZGFuaUBnbWFpbC5jb208bWFpbHRvOm1qZXRoYW5hbmRhbmlAZ21haWwuY29tPj47IHlhbmctZG9j
dG9yc0BpZXRmLm9yZzxtYWlsdG86eWFuZy1kb2N0b3JzQGlldGYub3JnPg0KQ2M6IGlldGZAaWV0
Zi5vcmc8bWFpbHRvOmlldGZAaWV0Zi5vcmc+OyB0ZWFzQGlldGYub3JnPG1haWx0bzp0ZWFzQGll
dGYub3JnPjsgZHJhZnQtaWV0Zi10ZWFzLXlhbmctdGUtdG9wby5hbGxAaWV0Zi5vcmc8bWFpbHRv
OmRyYWZ0LWlldGYtdGVhcy15YW5nLXRlLXRvcG8uYWxsQGlldGYub3JnPg0KU3ViamVjdDogUmU6
IFtUZWFzXSBZYW5nZG9jdG9ycyBsYXN0IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtdGVhcy15
YW5nLXRlLXRvcG8tMDgNCg0KSGkgWHVmZW5nLA0KVGhhbmtzIGZvciB1cGRhdGluZyB0aGUgbW9k
dWxlcyB0byBiZSBOTURBIGNvbXBsaWFudC4gIEkgdGhpbmsgdGhhdCBnZXR0aW5nIHN0cnVjdHVy
YWwgY29uc2lzdGVuY3kgYWNyb3NzIHRoZSBJRVRGIFlBTkcgbW9kdWxlcyB3aWxsIG1ha2UgdGhl
bSBmYXIgbW9yZSBjb21wZWxsaW5nIGFzIGEgc29sdXRpb24uDQpJIG5vdGljZWQgdGhhdCBzb21l
IG9mIHRoZSBzbmlwcGV0cyBvZiBZQU5HIHRyZWUgb3V0cHV0IGluIHRoZSBkcmFmdCBzdGlsbCBp
bGx1c3RyYXRlIHVzaW5nIHRoZSAic3BsaXQgb2Mtc3R5bGUgY29uZmlnL3N0YXRlIHN0cnVjdHVy
ZSIgYW5kIGhlbmNlIGFsc28gbmVlZCB0byBiZSB1cGRhdGVkLiAgUHJvYmFibHkgdGhpcyBjb3Vs
ZCBiZSBkb25lIGFzIHBhcnQgb2YgdGhlIFdHIExDLg0KVG8gZmluZCB0aGUgaW5zdGFuY2VzLCBq
dXN0IHNlYXJjaCB0aGUgZHJhZnQgZm9yICJydyBjb25maWciIGFuZCAicm8gc3RhdGUiLg0KVGhh
bmtzLA0KUm9iDQoNCk9uIDAyLzA3LzIwMTcgMjI6NDIsIFh1ZmVuZyBMaXUgd3JvdGU6DQpBbiB1
cGRhdGVkIHJldmlzaW9uIG9mIHRoZSBURSB0b3BvbG9neSBtb2RlbCBoYXMgYmVlbiBwb3N0ZWQg
YXQgaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtdGVhcy15YW5nLXRlLXRv
cG8tMTAuDQoNClRoaXMgbmV3IHJldmlzaW9uIG5vdyBjb250YWlucyB0aGUgTk1EQSBjb21wbGlh
bnQgbW9kdWxlIGFuZCBhIGNvbXBhbmlvbiDigJwtc3RhdGXigJ0gbW9kdWxlLCBhZnRlciB0aGUg
STJSUyB0b3BvbG9neSBtb2RlbCB0aGF0IHdlIGF1Z21lbnQgaGFzIGJlZW4gdXBkYXRlIHdpdGgg
YSDigJwtc3RhdGXigJ0gbW9kdWxlLg0KDQpOb3cgdGhhdCB0aGlzIGlzc3VlIGhhcyBiZWVuIHNv
bHZlZCwgdGhlIGF1dGhvcnMgYW5kIGNvbnRyaWJ1dG9ycyB0aGluayB0aGF0IHRoZSBkcmFmdCBp
cyByZWFkeSBmb3IgdGhlIGxhc3QgY2FsbC4NCg0KVGhhbmtzLA0KLSBYdWZlbmcNCg0KUC5TLiBC
ZWNhdXNlIG9mIHRoZSBzdHJ1Y3R1cmUgY2hhbmdlcyBvZiB0aGUgVEUgdG9wb2xvZ3kgbW9kZWws
IGFsbCBhdWdtZW50aW5nIG1vZGVscyBuZWVkIHRvIGJlIHVwZGF0ZWQuIFNvcnJ5IGZvciB0aGUg
c2hvcnQgbm90aWNlLg0KDQpGcm9tOiBUZWFzIFttYWlsdG86dGVhcy1ib3VuY2VzQGlldGYub3Jn
XSBPbiBCZWhhbGYgT2YgQmVub2l0IENsYWlzZQ0KU2VudDogTW9uZGF5LCBKdW5lIDI2LCAyMDE3
IDY6NDYgQU0NClRvOiBYdWZlbmcgTGl1IDxYdWZlbmdfTGl1QGphYmlsLmNvbT48bWFpbHRvOlh1
ZmVuZ19MaXVAamFiaWwuY29tPjsgUm9iZXJ0IFdpbHRvbiA8cndpbHRvbkBjaXNjby5jb20+PG1h
aWx0bzpyd2lsdG9uQGNpc2NvLmNvbT47IE1haGVzaCBKZXRoYW5hbmRhbmkgPG1qZXRoYW5hbmRh
bmlAZ21haWwuY29tPjxtYWlsdG86bWpldGhhbmFuZGFuaUBnbWFpbC5jb20+OyB5YW5nLWRvY3Rv
cnNAaWV0Zi5vcmc8bWFpbHRvOnlhbmctZG9jdG9yc0BpZXRmLm9yZz4NCkNjOiBCZW5vaXQgQ2xh
aXNlIDxiY2xhaXNlQGNpc2NvLmNvbT48bWFpbHRvOmJjbGFpc2VAY2lzY28uY29tPjsgaWV0ZkBp
ZXRmLm9yZzxtYWlsdG86aWV0ZkBpZXRmLm9yZz47IHRlYXNAaWV0Zi5vcmc8bWFpbHRvOnRlYXNA
aWV0Zi5vcmc+OyBkcmFmdC1pZXRmLXRlYXMteWFuZy10ZS10b3BvLmFsbEBpZXRmLm9yZzxtYWls
dG86ZHJhZnQtaWV0Zi10ZWFzLXlhbmctdGUtdG9wby5hbGxAaWV0Zi5vcmc+DQpTdWJqZWN0OiBS
ZTogW1RlYXNdIFlhbmdkb2N0b3JzIGxhc3QgY2FsbCByZXZpZXcgb2YgZHJhZnQtaWV0Zi10ZWFz
LXlhbmctdGUtdG9wby0wOA0KDQpIaSBYdWZlbmcsDQoNCkhpIEJlbm9pdCwNCg0KDQoNCi0tLS0t
T3JpZ2luYWwgTWVzc2FnZS0tLS0tDQoNCkZyb206IEJlbm9pdCBDbGFpc2UgW21haWx0bzpiY2xh
aXNlQGNpc2NvLmNvbV0NCg0KU2VudDogVGh1cnNkYXksIEp1bmUgMjIsIDIwMTcgNjoxMiBBTQ0K
DQpUbzogUm9iZXJ0IFdpbHRvbiA8cndpbHRvbkBjaXNjby5jb20+PG1haWx0bzpyd2lsdG9uQGNp
c2NvLmNvbT47IFh1ZmVuZyBMaXUgPFh1ZmVuZ19MaXVAamFiaWwuY29tPjxtYWlsdG86WHVmZW5n
X0xpdUBqYWJpbC5jb20+Ow0KDQpNYWhlc2ggSmV0aGFuYW5kYW5pIDxtamV0aGFuYW5kYW5pQGdt
YWlsLmNvbT48bWFpbHRvOm1qZXRoYW5hbmRhbmlAZ21haWwuY29tPjsgeWFuZy1kb2N0b3JzQGll
dGYub3JnPG1haWx0bzp5YW5nLWRvY3RvcnNAaWV0Zi5vcmc+DQoNCkNjOiBpZXRmQGlldGYub3Jn
PG1haWx0bzppZXRmQGlldGYub3JnPjsgdGVhc0BpZXRmLm9yZzxtYWlsdG86dGVhc0BpZXRmLm9y
Zz47IGRyYWZ0LWlldGYtdGVhcy15YW5nLXRlLXRvcG8uYWxsQGlldGYub3JnPG1haWx0bzpkcmFm
dC1pZXRmLXRlYXMteWFuZy10ZS10b3BvLmFsbEBpZXRmLm9yZz4NCg0KU3ViamVjdDogUmU6IFtU
ZWFzXSBZYW5nZG9jdG9ycyBsYXN0IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtdGVhcy15YW5n
LXRlLXRvcG8tDQoNCjA4DQoNCg0KDQpEZWFyIGRyYWZ0LWlldGYtdGVhcy15YW5nLXRlLXRvcG8g
YXV0aG9ycywNCg0KSGkgWHVmZW5nLA0KDQoNCg0KT0ssIGJ5IHRvb2xpbmcsIEkgZG9uJ3QgbWVh
biB0aGUgcHlhbmcgcGx1Z2lucyB0aGF0IEkgaGF2ZSBiZWVuDQoNCndvcmtpbmcgb24gdG8gY29u
dmVydCBiZXR3ZWVuIGRpZmZlcmVudCB0eXBlcyBvZiBtb2RlbHMuICBBcyB5b3UNCg0KYXdhcmUs
IHRoZSBURSBZQU5HIG1vZGVscyBjYW4gZWFzaWx5IGJlIGNvbnZlcnRlZCB0byBOTURBIHN0eWxl
IHNpbmNlDQoNCkkgaGF2ZSBhbHJlYWR5IGRvbmUgaXQNCg0KKGh0dHBzOi8vZ2l0aHViLmNvbS9y
Z3dpbHRvbi9pZXRmLW1vZGVscy10by1jb21iaW5lZCkuDQoNCg0KDQpNeSBjb21tZW50IGFjdHVh
bGx5IHJlbGF0ZXMgdG8gdGhlIGZhY3QgdGhlIHN0cnVjdHVyZSB1c2VkIGJ5IFRFIFlBTkcNCg0K
bW9kdWxlcyBkb24ndCBtYXRjaCBhbnkgb3RoZXIgWUFORyBtb2R1bGVzIC0gdGhleSBhcmUgdXNp
bmcgdGhlaXIgb3duDQoNCnVuaXF1ZSBzdHlsZSBvZiBzdHJ1Y3R1cmUuDQoNClRoaXMgaXMgYW4g
aW1wb3J0YW50IGlzc3VlIHRvIHJlc29sdmUuDQoNCg0KDQpUb2RheSwgdGhlcmUgYXJlIHRocmVl
IGNvbW1vbiBzdHlsZXMgb2YgbW9kdWxlczoNCg0KKDEpIElFVEYgc3R5bGUgc3BsaXQgY29uZmln
L3N0YXRlIHRyZWVzIChlLmcuIGlldGYtaW50ZXJmYWNlcykuDQoNCigyKSBJRVRGIE5NREEgc3R5
bGUgY29tYmluZWQgY29uZmlnL3N0YXRlIHRyZWVzIChpLmUuIHdoZXJlIGFsbCBJRVRGDQoNCm1v
ZHVsZXMgYXJlIGhlYWRpbmcgdG8pLg0KDQooMykgT3BlbkNvbmZpZyBzdHlsZSBtb2R1bGVzIHdp
dGggdGhlIGNvbmZpZy9zdGF0ZSBjb250YWluZXJzDQoNCmltbWVkaWF0ZWx5IGFib3ZlIHRoZSBj
b25maWcgbGVhdmVzLg0KDQoNCg0KVG9vbGluZyBpcyBsaWtlbHkgdG8gYmUgb3B0aW1pemVkIHRv
IHdvcmsgd2l0aCB0aGVzZSBtb2RlbCBzdHJ1Y3R1cmVzLA0KDQpidXQgdGhlIFRFIG1vZHVsZXMg
ZG8gbm90IGZpdCBpbnRvIGFueSBvZiB0aGUgdGhyZWUgc3R5bGVzIGFib3ZlLg0KDQpUaGV5IGFy
ZSBhIHlldCBhbm90aGVyIE9wZW5Db25maWctbGlrZSBzdHlsZSwgYnV0IHRoYXQgaXMgZGlmZmVy
ZW50DQoNCmVub3VnaCB0aGF0IHRvb2xpbmcgdGhhdCBpcyBkZXNpZ25lZCB0byB3b3JrIHdpdGgg
T3BlbkNvbmZpZyBzdHlsZQ0KDQpZQU5HIG1vZHVsZXMgd291bGQgbGlrZWx5IG5vdCB3b3JrIHdp
dGggdGhlIFRFIFlBTkcgbW9kdWxlcy4NCg0KDQoNClNwZWNpZmljYWxseSwgZm9yIGNsaWVudHMg
dGhhdCBleHBlY3RpbmcgdG8gd29yayB3aXRoIGFuIE9wZW5Db25maWcNCg0Kc3R5bGUgWUFORyBt
b2R1bGUsIHRoZW4gaWYgaXQga25vd3MgdGhlIHBhdGggdG8gY29uZmlnIGxlYWYgWCwgdGhlbg0K
DQp0aGV5IHdvdWxkIGV4cGVjdCB0aGUgYXBwbGllZCBjb25maWcgdmFsdWUgdG8gYmUgYXZhaWxh
YmxlIGF0IHRoZSBwYXRoDQoNCiIuLi9zdGF0ZS9YIi4gIEJ1dCwgdGhpcyBkb2Vzbid0IGhvbGQg
Zm9yIHRoZSBzdHJ1Y3R1cmUgYmVpbmcgdXNlZCBpbg0KDQp0aGUgVEUgWUFORyBtb2RlbHMuDQoN
Cg0KDQpJIGJlbGlldmUgc3Ryb25nbHkgdGhhdCB0aGUgbW9kZWxzIGJlaW5nIHByb2R1Y2VkIGJ5
IG9yZ2FuaXphdGlvbnMNCg0Kc2hvdWxkIGJlIHN0cnVjdHVyZXMgaW4gYSBjb25zaXN0ZW50IHdh
eSwgaGVuY2Ugd2h5IEkgdGhpbmsgdGhhdCB0aGUNCg0KcHVibGlzaGVkIHN0YW5kYXJkIHZlcnNp
b24gb2YgdGhlIFRFIFlBTkcgbW9kdWxlcyBzaG91bGQgaW1tZWRpYXRlbHkNCg0KYWxpZ24gdG8g
dGhlIE5NREEgc3R5bGUuDQoNCkFncmVlZC4NCg0KSGVyZSBpcyB0aGUgT1BTIGFuZCBSVEcgQUQg
bWVzc2FnZToNCg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9uZXRtb2Qv
Y3VycmVudC9tc2cxODI1Mi5odG1sDQoNCg0KDQpJIHVuZGVyc3RhbmQgdGhhdCB0aGUgSTJSUyB0
b3BvbG9neSBZQU5HIG1vZHVsZXMgd2lsbCBiZSBpbXByb3ZlZCB0byB0aGUNCg0KTk1EQSBzdHls
ZS4NCg0KW1h1ZmVuZ10gVGhlIEkyUlMgdG9wb2xvZ3kgbW9kZWwgaXMgYWxyZWFkeSBOTURBIHN0
eWxlLCBidXQgdGhlIE5NREEgbW9kZWxzIGFyZSBub3QgaW1tZWRpYXRlbHkgaW1wbGVtZW50YWJs
ZSB3aXRob3V0IE5FVENPTkYvUkVTVENPTkYgcHJvdG9jb2wgdXBkYXRlLiBXZSB3aWxsIG5lZWQg
dGhlICItc3RhdGUiIG1vZHVsZSBmb3IgdGhlIEkyUlMgdG9wb2xvZ3kgbW9kZWwgKGFuZCBmb3Ig
YWxsIHRoZSB0b3AtbGV2ZWwgbW9kZWxzKSBmb3Igbm93Lg0KQWRkaW5nIC1zdGF0ZSB0byB0aGUg
QXBwZW5kaXggaXMgYSBwb3NzaWJpbGl0eS4NCiJJbiBhbGwgY2FzZXMsIHRoZSBOTURBIGFuZCBu
b24tTk1EQSBtb2R1bGVzIFNIT1VMRCBiZSBwdWJsaXNoZWQgaW4gdGhlIHNhbWUgZG9jdW1lbnQs
IHdpdGggTk1EQSBtb2R1bGVzIGluIHRoZSBkb2N1bWVudCBtYWluIGJvZHkgYW5kIHRoZSBub24t
Tk1EQSBtb2R1bGVzIGluIGFuIEFwcGVuZGl4LiINClNlZSBodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsLWFyY2hpdmUvd2ViL25ldG1vZC9jdXJyZW50L21zZzE4MjUyLmh0bWwNCg0KDQoNCg0KV2hp
bGUgdGhlIE5NREEgaXMgbmljZSwgdGhlIE5NREEgZGlzY3Vzc2lvbnMgaGF2ZSBhbHJlYWR5IHNp
Z25pZmljYW50bHkgZGVsYXllZCBwdWJsaXNoaW5nIG5ldyBtb2RlbHMsIGFuZCBkb2luZyBOTURB
IHdpdGhvdXQgc3RhZ2luZyB3aWxsIGZ1cnRoZXIgZGVsYXkgdGhlIHByb2Nlc3MuDQpUaGlzIGlz
IG5vdCBzb2x2aW5nIHRoZSBpbXBvcnRhbnQgaXNzdWUgYnJvdWdodCB1cCBieSBSb2IgV2l0bG9u
Og0KTXkgY29tbWVudCBhY3R1YWxseSByZWxhdGVzIHRvIHRoZSBmYWN0IHRoZSBzdHJ1Y3R1cmUg
dXNlZCBieSBURSBZQU5HIG1vZHVsZXMgZG9uJ3QgbWF0Y2ggYW55IG90aGVyIFlBTkcgbW9kdWxl
cyAtIHRoZXkgYXJlIHVzaW5nIHRoZWlyIG93biB1bmlxdWUgc3R5bGUgb2Ygc3RydWN0dXJlLg0K
UmVnYXJkcywgQi4NCg0KDQoNCg0KDQoNClRoYW5rcywgIFh1ZmVuZw0KDQoNCg0KUmVnYXJkcywg
QmVub2l0DQoNCg0KDQpUaGFua3MsDQoNClJvYg0KDQoNCg0KDQoNCk9uIDIyLzA2LzIwMTcgMDQ6
MTYsIFh1ZmVuZyBMaXUgd3JvdGU6DQoNCkhpIFJvYiwNCg0KDQoNCldoaWxlIHRoZSB0b29saW5n
IGlzIHZlcnkgbmljZSB0byBoYXZlLCBlc3BlY2lhbGx5IGZvciB3cml0aW5nIG5ldw0KDQptb2Rl
bHMgb3IgY29udmVydGluZyBtb2RlbHMsIHdlIGRvIG5vdCBoYXZlIHRvIHVzZSBpdCBmb3IgZXZl
cnkNCg0KbW9kZWwuIEl0IHNlZW1zIG5vdCBuZWNlc3NhcnkgdG8gdXNlIHRoZSB0b29saW5nIG9u
IHRoaXMgbW9kZWwgZm9yDQoNCm5vdy4gV2UgYWxyZWFkeSBrbm93IHRoYXQgd2UgY2FuIG1hbnVh
bGx5IGNvbnZlcnQgaXQgdG8gTk1EQSBzdHlsZSBpZg0KDQpuZWVkZWQuDQoNCg0KDQpUaGFua3Ms
DQoNCi0gWHVmZW5nDQoNCg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KDQpGcm9tOiBS
b2JlcnQgV2lsdG9uIFttYWlsdG86cndpbHRvbkBjaXNjby5jb21dDQoNClNlbnQ6IFdlZG5lc2Rh
eSwgSnVuZSAyMSwgMjAxNyA1OjM0IEFNDQoNClRvOiBYdWZlbmcgTGl1IDxYdWZlbmdfTGl1QGph
YmlsLmNvbT48bWFpbHRvOlh1ZmVuZ19MaXVAamFiaWwuY29tPjsgTWFoZXNoIEpldGhhbmFuZGFu
aQ0KDQo8bWpldGhhbmFuZGFuaUBnbWFpbC5jb20+PG1haWx0bzptamV0aGFuYW5kYW5pQGdtYWls
LmNvbT47IHlhbmctZG9jdG9yc0BpZXRmLm9yZzxtYWlsdG86eWFuZy1kb2N0b3JzQGlldGYub3Jn
Pg0KDQpDYzogaWV0ZkBpZXRmLm9yZzxtYWlsdG86aWV0ZkBpZXRmLm9yZz47IHRlYXNAaWV0Zi5v
cmc8bWFpbHRvOnRlYXNAaWV0Zi5vcmc+Ow0KDQpkcmFmdC1pZXRmLXRlYXMteWFuZy10ZS10b3Bv
LmFsbEBpZXRmLm9yZzxtYWlsdG86ZHJhZnQtaWV0Zi10ZWFzLXlhbmctdGUtdG9wby5hbGxAaWV0
Zi5vcmc+DQoNClN1YmplY3Q6IFJlOiBbVGVhc10gWWFuZ2RvY3RvcnMgbGFzdCBjYWxsIHJldmll
dyBvZg0KDQpkcmFmdC1pZXRmLXRlYXMteWFuZy10ZS10b3BvLQ0KDQowOA0KDQoNCg0KSGkgWHVm
ZW5nLA0KDQoNCg0KT24gMTIvMDYvMjAxNyAyMjoyOCwgWHVmZW5nIExpdSB3cm90ZToNCg0KSGkg
TWFoZXNoLA0KDQoNCg0KVGhhbmsgeW91IG11Y2ggZm9yIHRoZSByZXZpZXcuIFdlIGhhdmUgc3Vi
bWl0dGVkIGFuIHVwZGF0ZWQgZHJhZnQNCg0KKGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9k
cmFmdC1pZXRmLXRlYXMteWFuZy10ZS10b3BvLTA5KSB0bw0KDQphZGRyZXNzIHRoZXNlIGlzc3Vl
cy4gTW9yZSBkZXRhaWxlZCBleHBsYW5hdGlvbnMgYXJlIHB1dCBiZWxvdw0KDQppbmxpbmUuDQoN
CklmIHRoZSByZXNwb25zZXMgYW5kIHVwZGF0ZXMgYXJlIHNhdGlzZmFjdG9yeSwgd2UgYXJlIHJl
YWR5IGZvciB0aGUNCg0KbGFzdCBjYWxsLg0KDQoNCg0KQmVzdCByZWdhcmRzLA0KDQotIFh1ZmVu
Zw0KDQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCg0KRnJvbTogTWFoZXNoIEpldGhh
bmFuZGFuaSBbbWFpbHRvOm1qZXRoYW5hbmRhbmlAZ21haWwuY29tXQ0KDQpTZW50OiBXZWRuZXNk
YXksIE1heSAyNCwgMjAxNyAxMTo0NCBBTQ0KDQpUbzogeWFuZy1kb2N0b3JzQGlldGYub3JnPG1h
aWx0bzp5YW5nLWRvY3RvcnNAaWV0Zi5vcmc+DQoNCkNjOiBpZXRmQGlldGYub3JnPG1haWx0bzpp
ZXRmQGlldGYub3JnPjsgdGVhc0BpZXRmLm9yZzxtYWlsdG86dGVhc0BpZXRmLm9yZz47DQoNCmRy
YWZ0LWlldGYtdGVhcy15YW5nLXRlLXRvcG8uYWxsQGlldGYub3JnPG1haWx0bzpkcmFmdC1pZXRm
LXRlYXMteWFuZy10ZS10b3BvLmFsbEBpZXRmLm9yZz4NCg0KU3ViamVjdDogWWFuZ2RvY3RvcnMg
bGFzdCBjYWxsIHJldmlldyBvZg0KDQpkcmFmdC1pZXRmLXRlYXMteWFuZy10ZS10b3BvLTA4DQoN
Cg0KDQpSZXZpZXdlcjogTWFoZXNoIEpldGhhbmFuZGFuaQ0KDQpSZXZpZXcgcmVzdWx0OiBSZWFk
eSB3aXRoIElzc3Vlcw0KDQoNCg0KRG9jdW1lbnQgcmV2aWV3ZWQ6IGRyYWZ0LWlldGYtdGVhcy15
YW5nLXRlLXRvcG8tMDgNCg0KDQoNClN0YXR1czogUmVhZHkgd2l0aCBJc3N1ZXMNCg0KDQoNCkkg
YW0gbm90IGFuIGV4cGVydCBpbiBUcmFmZmljIEVuZ2luZWVyaW5nLiBUaGlzIHJldmlldyBpcyBs
b29raW5nDQoNCmF0IHRoZSBkcmFmdCBmcm9tIGEgWUFORyBwZXJzcGVjdGl2ZS4gV2l0aCB0aGF0
IHNhaWQsIEkgaGF2ZQ0KDQptYXJrZWQgaXQgYXMg4oCcUmVhZHkNCg0Kd2l0aCBJc3N1ZXPigJ0N
Cg0KYmVjYXVzZSBvZiBzb21lIG9mIHRoZSBwb2ludHMgZGlzY3Vzc2VkIGJlbG93Lg0KDQoNCg0K
U3VtbWFyeToNCg0KDQoNClRoaXMgZG9jdW1lbnQgZGVmaW5lcyBhIFlBTkcgZGF0YSBtb2RlbCBm
b3IgcmVwcmVzZW50aW5nLA0KDQpyZXRyaWV2aW5nIGFuZCBtYW5pcHVsYXRpbmcgVEUgVG9wb2xv
Z2llcy4gVGhlIG1vZGVsIHNlcnZlcyBhcyBhDQoNCmJhc2UgbW9kZWwgdGhhdCBvdGhlciB0ZWNo
bm9sb2d5IHNwZWNpZmljIFRFIFRvcG9sb2d5IG1vZGVscyBjYW4NCg0KYXVnbWVudC4NCg0KDQoN
CkNvbW1lbnRzOg0KDQoNCg0KQWxtb3N0IGFsbCB0aGUgY29udGFpbmVycyBpbiB0aGUgbW9kZWwg
YXJlIHByZXNlbmNlIGNvbnRhaW5lcnMuIElzDQoNCnRoZXJlIGEgcmVhc29uIHdoeSB0aGV5IGhh
dmUgdG8gYmUgcHJlc2VuY2UgY29udGFpbmVycz8gTm90ZSwgdGhhdA0KDQpwcmVzZW5jZSBjb250
YWluZXJzIGFyZSBjb250YWluZXJzIHdob3NlIGV4aXN0ZW5jZSBpdHNlbGYNCg0KcmVwcmVzZW50
cyBjb25maWd1cmF0aW9uIGRhdGEuIFdoYXQgcGFydGljdWxhciBjb25maWd1cmF0aW9uIGRhdGEN
Cg0KaXMgZWFjaCBjb250YWluZXINCg0KcmVwcmVzZW50aW5nIGluIGl0c2VsZj8NCg0KW1h1ZmVu
Z10gQ29udGFpbmVycyB0aGF0IHVzZSDigJxwcmVzZW5jZeKAnSBhcmU6DQoNCiAgICAtIENvbnRh
aW5lciDigJx1bmRlcmxheeKAnQ0KDQogICAgICBvICBXZSBoYXZlIGNoYW5nZWQgMTMgb2NjdXJy
ZW5jZXMgb2Ygc3VjaCBjb250YWluZXJzIHRvIGJlDQoNCm5vdA0KDQpwcmVzZW5jZSBjb250YWlu
ZXIuDQoNCiAgICAtIENvbnRhaW5lciDigJx0ZeKAnSB1bmRlciBhdWdtZW50YXRpb24NCg0KICAg
ICAgbyAgVG8gaW5kaWNhdGUgdGhhdCDigJxUReKAnSBpcyBlbmFibGVkIChjb25maWd1cmF0aW9u
IGRhdGEpDQoNCiAgICAgIG8gIEFsc28gdXNlZCB0byBkbyBhdWdtZW50YXRpb24uIFRoZSDigJxw
cmVzZW5jZeKAnSBzdGF0ZW1lbnQgY2FuDQoNCnByZXZlbnQgdGhlIG1hbmRhdG9yeSBjaGlsZCBm
cm9tIGFmZmVjdGluZyBhdWdtZW50ZWQgYmFzZSBtb2RlbC4NCg0KICAgIC0gL253Om5ldHdvcmtz
L253Om5ldHdvcmsvbnc6bmV0d29yay10eXBlcy90ZS10b3BvbG9neSENCg0KICAgICAgbyAgQSBt
ZWNoYW5pc20gcmVxdWlyZWQgYnkgSTJSUyB0b3BvbG9neSBtb2RlbCB0byBzcGVjaWZ5IHRoZQ0K
DQp0b3BvbG9neSB0eXBlLg0KDQpJdCBpcyBkaWZmaWN1bHQgdG8gY28tcmVsYXRlIHRoZSBkaWFn
cmFtIHdpdGggdGhlIG1vZGVsIGl0c2VsZg0KDQpiZWNhdXNlIG9mIGRpZmZlcmVudCB0ZXJtcyBi
ZWluZyB1c2VkIHRvIGRlZmluZSBkaWZmZXJlbnQgcGFydHMgb2YNCg0KdGhlIG1vZGVsLg0KDQpU
aGVyZSBpcyDigJxURSBUb3BvbG9neSBNb2RlbOKAnSBhbmQgdGhlbiB0aGVyZSBpcyDigJxHZW5l
cmljIFRFDQoNClRvcG9sb2d5DQoNCk1vZGVs4oCdLg0KDQpBcmUgdGhlc2Ugb25lIGFuZCB0aGUg
c2FtZSBtb2RlbHM/IElmIHNvLCBhIGNvbW1vbiB0ZXJtIGZvciBib3RoDQoNCm9mIHRoZW0gd291
bGQgYmUgaGVscGZ1bC4NCg0KW1h1ZmVuZ10gWWVzLiBUaGVzZSB0d28gdGVybXMgYXJlIHRoZSBz
YW1lLiBGaWd1cmUgMTIsIEZpZ3VyZSAxMywNCg0KYW5kIHJlbGV2YW50DQoNCmRlc2NyaXB0aW9u
cyBoYXZlIGJlZW4gdXBkYXRlZCB0byBtYWtlIHRoZSBkb2N1bWVudCBjb25zaXN0ZW50Lg0KDQpU
aGVyZSBpcyBleHRlbnNpdmUgdXNlIG9mIGdyb3VwaW5ncyBpbiB0aGUgZG9jdW1lbnQuIEhvd2V2
ZXIsIG5vdA0KDQphbGwgaW5zdGFuY2VzIG9mIGdyb3VwaW5ncyBhcmUgdXNlZCBtdWx0aXBsZSBu
dW1iZXIgb2YgdGltZXMuDQoNCldoZXJlIHRoZXkgYXJlIG5vdCBiZWluZyByZXBlYXRlZCwgaXQg
d291bGQgYmUgYmV0dGVyIHRvIG1vdmUgdGhlDQoNCmdyb3VwaW5nIGRpcmVjdGx5IHdoZXJlIHRo
ZSB1c2VzIHN0YXRlbWVudCByZXNpZGVzLiBDYXNlIGluIHBvaW50DQoNCnRoZSBncm91cGluZw0K
DQpjb25uZWN0aXZpdHktbGFiZWwtcmVzdHJpY3Rpb24tbGlzdC4NCg0KW1h1ZmVuZ10gV2UgaGF2
ZSByZW1vdmVkIHRoZSBmb2xsb3dpbmcgZ3JvdXBpbmdzDQoNCiAgICAgIHRlLWxpbmstYXVnbWVu
dA0KDQogICAgICB0ZS1ub2RlLWF1Z21lbnQNCg0KICAgICAgdGUtdGVybWluYXRpb24tcG9pbnQt
YXVnbWVudA0KDQogICAgICB0ZS10b3BvbG9naWVzLWF1Z21lbnQNCg0KICAgICAgdGUtdG9wb2xv
Z3ktYXVnbWVudA0KDQogICAgICB0ZS1saW5rLXN0YXRlLXVuZGVybGF5LWF0dHJpYnV0ZXMNCg0K
ICAgICAgdGUtbm9kZS1zdGF0ZS1kZXJpdmVkLW5vdGlmaWNhdGlvbg0KDQogICAgICB0ZS10b3Bv
bG9neS10eXBlDQoNCg0KDQpUaGUgcmVtYWluaW5nIGdyb3VwaW5ncyBoYXZlIGJlZW4ga2VwdCBz
byB0aGF0IHdlIGNhbjoNCg0KICAgIC0gU2hhcmUgdGhlIGdyb3VwaW5ncyBpbiB0aGlzIG1vZGVs
DQoNCiAgICAtIFByZXBhcmUgdG8gYmUgc2hhcmVkIGJ5IGEgbW9kZWwgYXVnbWVudGluZyB0aGlz
IG1vZGVsDQoNCiAgICAtIFByZXZlbnQgYSBncm91cGluZyBvciBjb25maWd1cmF0aW9uIHNlY3Rp
b24gZnJvbSBiZWluZyB0b28gbG9uZw0KDQogICAgLSBJbXByb3ZlIHJlYWRhYmlsaXR5DQoNCg0K
DQpUaGUgc3BsaXQgYmV0d2VlbiBjb25maWcgYW5kIHN0YXRlIGNvbnRhaW5lcnMgZG9lcyBub3Qg
c2VlbSB0bw0KDQpmb2xsb3cgYW55IHBhcnRpY3VsYXIgcGF0dGVybi4NCg0KW1h1ZmVuZ10gVGhl
IHBhdHRlcm4gaXMgY2xlYXI6DQoNCkZvciBlYWNoIG1hbmFnZWFibGUgZW50aXR5IChvYmplY3Qp
LCB0aGVyZSBpcyBhIGNvbmZpZyBjb250YWluZXINCg0KYW5kIHN0YXRlDQoNCmNvbnRhaW5lci4g
VGhlIGNvbmZpZ3VyYWJsZSBwcm9wZXJ0aWVzIGdvIGludG8gdGhlIGNvbmZpZyBjb250YWluZXIN
Cg0KYW5kIHN0YXRlIHByb3BlcnRpZXMgZ28gaW50byB0aGUgc3RhdGUgY29udGFpbmVyLiBTdWNo
IG9iamVjdHMgYXJlDQoNCmlkZW50aWZpZWQgYnkgYSBsaXN0IGl0ZW0gb3IgYSBwcmVzZW5jZSBj
b250YWluZXIgc28gdGhhdCB0aGUNCg0K4oCcY3JlYXRl4oCdLCDigJxkZWxldGXigJ0sIGFuZCDi
gJxtb2RpZnnigJ0NCg0Kb3BlcmF0aW9ucw0KDQpjYW4gYmUgcGVyZm9ybWVkIG9uIHRoZW0uIFRo
ZSBub24tcHJlc2VuY2UgY29udGFpbmVycyBkbyBub3QNCg0KcmVwcmVzZW50IGNvbmZpZ3VyYXRp
b24gZGF0YSBzbyB0aGV5IGRvIG5vdCBpbnRyb2R1Y2Ugc3VjaCBvYmplY3RzLg0KDQpJdCBpcyBu
ZWl0aGVyIGEgdG9wIGxldmVsIHNwbGl0LCBhcyBpcyB0aGUgY2FzZSB3aXRoIGV4aXN0aW5nIElF
VEYNCg0KbW9kZWxzLA0KDQpbWHVmZW5nXSBXZSBjb3VsZCBub3QgZG8gdG9wIGxldmVsIHNwbGl0
IGJlY2F1c2UgdGhlIGJhc2UgSTJSUw0KDQpuZXR3b3JrDQoNCnRvcG9sb2d5IG1vZGVsDQoNCiho
dHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1pMnJzLXlhbmctbmV0d29yay10
b3BvLQ0KDQoxMikgdGhhdCB3ZSBhdWdtZW50IGRvZXMgbm90IGhhdmUgdGhlIHRvcC1sZXZlbCBz
cGxpdCAoZm9yIGl0cyBvd24NCg0KcmVhc29ucykuDQoNCm5vciBkbyB0aGV5IGZvbGxvdyB0aGUg
T3BlbkNvbmZpZyBzdHlsZSBvZiBzcGxpdHRpbmcgY29uZmlnIGFuZA0KDQpzdGF0ZSB1bmRlciBl
YWNoIHJlbGV2YW50IGxlYWYsDQoNCltYdWZlbmddIFRoZSBwYXR0ZXJuIGlzIGNvbnNpc3RlbnQg
d2l0aCB0aGlzIHN0eWxlIGluIHByaW5jaXBsZSwNCg0Kd2l0aCBzb21lDQoNCmFkanVzdG1lbnRz
IHRvIGZpdCB0byBvdXIgbXVsdGlwbGUgbGV2ZWxzIG9mIGhpZXJhcmNoeS4NCg0KVGhpcyBpcyBl
ZmZlY3RpdmVseSBhIG5ldyBmb3J0aCBzdHlsZSBvZiBZQU5HIG1vZGVscyB0aGF0IGlzIG5vdA0K
DQpjb25zaXN0ZW50IHdpdGggYW55IG9mIHRoZSB0aHJlZSBleGlzdGluZyBzdHlsZXMsIGkuZS46
DQoNCiAgIC0gQ3VycmVudCBJRVRGIGNvbmZpZy9zdGF0ZSBzcGxpdCBtb2RlbCBzdHlsZQ0KDQog
ICAtIE5NREEgY29tYmluZWQgY29uZmlnL3N0YXRlIHRyZWUNCg0KICAgLSBPcGVuQ29uZmlnIHNw
bGl0IGNvbmZpZy9zdGF0ZSBjb250YWluZXJzIGltbWVkaWF0ZWx5IGFib3ZlIHRoZQ0KDQpjb25m
aWcgdHJ1ZSBsZWF2ZXMuDQoNCg0KDQpUb29saW5nIHRoYXQgaXQgZGVzaWduZWQgdG8gd29yayB3
aXRoIE9wZW5Db25maWcgbW9kZWxzIHdpbGwgbmVlZA0KDQpjdXN0b21pemF0aW9uIHRvIHdvcmsg
d2l0aCB0aGVzZSBURSBtb2RlbHMgYmVjYXVzZSB0aGUgY29uZmlnL3N0YXRlDQoNCmNvbnRhaW5l
cnMgd2lsbCBub3QgYmUgd2hlcmUgdGhlIHRvb2xpbmcgZXhwZWN0cyB0aGVtIHRvIGJlLg0KDQoN
Cg0KVGhhbmtzLA0KDQpSb2INCg0KDQoNCi4NCg0KDQoNCg0KDQoNCg0KTWFoZXNoIEpldGhhbmFu
ZGFuaQ0KbWpldGhhbmFuZGFuaUBnbWFpbC5jb208bWFpbHRvOm1qZXRoYW5hbmRhbmlAZ21haWwu
Y29tPg0KDQoNCg0K

--_000_BN3PR0201MB0867067D89B713E9D212C841F1AC0BN3PR0201MB0867_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
SGVsdmV0aWNhOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDIgMiAyIDIgMiA0O30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAz
IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkRlbmdYaWFuOw0KCXBhbm9zZS0xOjMg
MCA1IDkgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0K
CXBhbm9zZS0xOjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1p
bHk6IlxARGVuZ1hpYW4iOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQt
ZmFjZQ0KCXtmb250LWZhbWlseTpDb25zb2xhczsNCglwYW5vc2UtMToyIDExIDYgOSAyIDIgNCAz
IDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1h
bCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsN
Cglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30N
CmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNv
bG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4u
TXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1
cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnByZQ0KCXttc28tc3R5bGUtcHJp
b3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwgUHJlZm9ybWF0dGVkIENoYXIiOw0KCW1h
cmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7DQoJ
Zm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpwLk1zb0xpc3RQYXJhZ3JhcGgsIGxpLk1zb0xp
c3RQYXJhZ3JhcGgsIGRpdi5Nc29MaXN0UGFyYWdyYXBoDQoJe21zby1zdHlsZS1wcmlvcml0eToz
NDsNCgltYXJnaW4tdG9wOjBpbjsNCgltYXJnaW4tcmlnaHQ6MGluOw0KCW1hcmdpbi1ib3R0b206
MGluOw0KCW1hcmdpbi1sZWZ0Oi41aW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQt
c2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KcC5tc29u
b3JtYWwwLCBsaS5tc29ub3JtYWwwLCBkaXYubXNvbm9ybWFsMA0KCXttc28tc3R5bGUtbmFtZTpt
c29ub3JtYWw7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFyZ2luLXJpZ2h0OjBpbjsN
Cgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVmdDowaW47DQoJZm9udC1z
aXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpzcGFuLmFw
cGxlLWNvbnZlcnRlZC1zcGFjZQ0KCXttc28tc3R5bGUtbmFtZTphcHBsZS1jb252ZXJ0ZWQtc3Bh
Y2U7fQ0Kc3Bhbi5IVE1MUHJlZm9ybWF0dGVkQ2hhcg0KCXttc28tc3R5bGUtbmFtZToiSFRNTCBQ
cmVmb3JtYXR0ZWQgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1s
aW5rOiJIVE1MIFByZWZvcm1hdHRlZCI7DQoJZm9udC1mYW1pbHk6Q29uc29sYXM7fQ0Kc3Bhbi5F
bWFpbFN0eWxlMjENCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1p
bHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hwRGVm
YXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30N
CkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4g
MS4waW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9u
MTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0
cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1b
aWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRt
YXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5k
aWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1
cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
SGkgTWFoZXNoLDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGFua3MuIFdlIHdpbGwgZml4IHRo
ZXNlIHdpdGhpbiBuZXh0IGZldyBkYXlzLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5SZWdhcmRz
LDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+LSBYdWZlbmc8bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdiBz
dHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBp
biAwaW4gMGluIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXIt
dG9wOnNvbGlkICNFMUUxRTEgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48Yj5Gcm9tOjwvYj4gTWFoZXNoIEpldGhhbmFuZGFuaSBbbWFpbHRv
Om1qZXRoYW5hbmRhbmlAZ21haWwuY29tXQ0KPGJyPg0KPGI+U2VudDo8L2I+IEZyaWRheSwgSnVs
eSA3LCAyMDE3IDI6MTQgUE08YnI+DQo8Yj5Ubzo8L2I+IFh1ZmVuZyBMaXUgJmx0O3h1ZmVuZy5s
aXUuaWV0ZkBnbWFpbC5jb20mZ3Q7PGJyPg0KPGI+Q2M6PC9iPiBSb2JlcnQgV2lsdG9uICZsdDty
d2lsdG9uQGNpc2NvLmNvbSZndDs7IEJlbm9pdCBDbGFpc2UgJmx0O2JjbGFpc2VAY2lzY28uY29t
Jmd0OzsgWHVmZW5nIExpdSAmbHQ7WHVmZW5nX0xpdUBqYWJpbC5jb20mZ3Q7OyB5YW5nLWRvY3Rv
cnNAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmc7IHRlYXNAaWV0Zi5vcmc7IGRyYWZ0LWlldGYtdGVh
cy15YW5nLXRlLXRvcG8uYWxsQGlldGYub3JnPGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBbVGVh
c10gWWFuZ2RvY3RvcnMgbGFzdCBjYWxsIHJldmlldyBvZiBkcmFmdC1pZXRmLXRlYXMteWFuZy10
ZS10b3BvLTA4PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5BbHNvLCBj
b3VwbGUgb2YgY2hhbmdlcyBpbiB0aGUgWUFORyBtb2R1bGVzOjxvOnA+PC9vOnA+PC9wPg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VW5kZXIgcmV2aXNpb24sIGNhbiB5b3UgbWFrZSBz
dXJlIHRoZXJlIGlzIGEgcmVmZXJlbmNlIGJhY2sgdG8gdGhlIFJGQyBudW1iZXIgdGhhdCB3aWxs
IGJlIGFzc2lnbmVkIHRvIHRoZSBkcmFmdC4gU29tZXRoaW5nIGxpa2U6PG86cD48L286cD48L3A+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7IHJldmlzaW9uICZx
dW90O1lZWVktTU0tREQmcXVvdDsgezxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7ICZuYnNwOyBkZXNjcmlwdGlvbjxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7ICZuYnNwOyAmbmJz
cDsmcXVvdDtJbml0aWFsIHZlcnNpb24mcXVvdDs7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsgJm5ic3A7IHJlZmVyZW5jZTxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7ICZuYnNw
OyAmbmJzcDsmcXVvdDtSRkMgWFhYWDogWUFORyAtIFRFIFRvcG9sb2d5JnF1b3Q7OzxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7IH08bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+d2l0aCBh
IG5vdGUgdG8gUkZDIGVkaXRvciB0byByZXBsYWNlIFhYWFggd2l0aCB0aGUgbnVtYmVyIGFzc2ln
bmVkIHRvIHRoZSBSRkMuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPlByZWZpeCBvcmdhbml6YXRpb24gd2l0aCBJRVRGLiBTb21ldGhpbmcgbGlr
ZSDigJxJRVRGJm5ic3A7PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQiPlRyYWZmaWMgRW5n
aW5lZXJpbmcgQXJjaGl0ZWN0dXJlIGFuZCBTaWduYWxpbmcgKFRFQVMpJm5ic3A7V29ya2luZyBH
cm91cOKAnTwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij48YnI+DQo8YnI+DQo8L3Nw
YW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+VGhhbmtzLjwvc3Bhbj48bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBw
dDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBK
dWwgMywgMjAxNywgYXQgMzoyNSBQTSwgWHVmZW5nIExpdSAmbHQ7PGEgaHJlZj0ibWFpbHRvOnh1
ZmVuZy5saXUuaWV0ZkBnbWFpbC5jb20iPnh1ZmVuZy5saXUuaWV0ZkBnbWFpbC5jb208L2E+Jmd0
OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5ISSBSb2IsPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+Jm5ic3A7
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0iYmFja2dyb3VuZDp3aGl0ZSI+SnVzdCBwb3N0ZWQ8c3BhbiBjbGFzcz0iYXBwbGUtY29udmVy
dGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+PGEgaHJlZj0iaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRm
Lm9yZy9kb2MvZHJhZnQtaWV0Zi10ZWFzLXlhbmctdGUtdG9wby8iPjxzcGFuIHN0eWxlPSJjb2xv
cjpwdXJwbGUiPmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtdGVh
cy15YW5nLXRlLXRvcG8vPC9zcGFuPjwvYT48c3BhbiBjbGFzcz0iYXBwbGUtY29udmVydGVkLXNw
YWNlIj4mbmJzcDs8L3NwYW4+Jm5ic3A7dG8NCiBmaXggdGhlIHNuaXBwZXRzLCBhbG9uZyB3aXRo
IGEgbWlzc2luZyBJQU5BIGVudHJ5LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPiZuYnNwOzxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tn
cm91bmQ6d2hpdGUiPlRoYW5rcyw8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj4tIFh1ZmVuZzxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tn
cm91bmQ6d2hpdGUiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2IHN0eWxlPSJi
b3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGluIDBpbiAw
aW4gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29s
aWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+PGI+RnJvbTo8L2I+PHNw
YW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPlJvYmVydCBXaWx0
b24gWzxhIGhyZWY9Im1haWx0bzpyd2lsdG9uQGNpc2NvLmNvbSI+bWFpbHRvOnJ3aWx0b25AY2lz
Y28uY29tPC9hPl08c3BhbiBjbGFzcz0iYXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJzcDs8L3Nw
YW4+PGJyPg0KPGI+U2VudDo8L2I+PHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRlZC1zcGFjZSI+
Jm5ic3A7PC9zcGFuPk1vbmRheSwgSnVseSAzLCAyMDE3IDU6MTMgQU08YnI+DQo8Yj5Ubzo8L2I+
PHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPlh1ZmVuZyBM
aXUgJmx0OzxhIGhyZWY9Im1haWx0bzp4dWZlbmcubGl1LmlldGZAZ21haWwuY29tIj54dWZlbmcu
bGl1LmlldGZAZ21haWwuY29tPC9hPiZndDs7ICdCZW5vaXQgQ2xhaXNlJyAmbHQ7PGEgaHJlZj0i
bWFpbHRvOmJjbGFpc2VAY2lzY28uY29tIj5iY2xhaXNlQGNpc2NvLmNvbTwvYT4mZ3Q7OyAnWHVm
ZW5nIExpdScgJmx0OzxhIGhyZWY9Im1haWx0bzpYdWZlbmdfTGl1QGphYmlsLmNvbSI+WHVmZW5n
X0xpdUBqYWJpbC5jb208L2E+Jmd0OzsNCiAnTWFoZXNoIEpldGhhbmFuZGFuaScgJmx0OzxhIGhy
ZWY9Im1haWx0bzptamV0aGFuYW5kYW5pQGdtYWlsLmNvbSI+bWpldGhhbmFuZGFuaUBnbWFpbC5j
b208L2E+Jmd0OzsNCjxhIGhyZWY9Im1haWx0bzp5YW5nLWRvY3RvcnNAaWV0Zi5vcmciPnlhbmct
ZG9jdG9yc0BpZXRmLm9yZzwvYT48YnI+DQo8Yj5DYzo8L2I+PHNwYW4gY2xhc3M9ImFwcGxlLWNv
bnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPjxhIGhyZWY9Im1haWx0bzppZXRmQGlldGYub3Jn
Ij5pZXRmQGlldGYub3JnPC9hPjsNCjxhIGhyZWY9Im1haWx0bzp0ZWFzQGlldGYub3JnIj50ZWFz
QGlldGYub3JnPC9hPjsgPGEgaHJlZj0ibWFpbHRvOmRyYWZ0LWlldGYtdGVhcy15YW5nLXRlLXRv
cG8uYWxsQGlldGYub3JnIj4NCmRyYWZ0LWlldGYtdGVhcy15YW5nLXRlLXRvcG8uYWxsQGlldGYu
b3JnPC9hPjxicj4NCjxiPlN1YmplY3Q6PC9iPjxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQt
c3BhY2UiPiZuYnNwOzwvc3Bhbj5SZTogW1RlYXNdIFlhbmdkb2N0b3JzIGxhc3QgY2FsbCByZXZp
ZXcgb2YgZHJhZnQtaWV0Zi10ZWFzLXlhbmctdGUtdG9wby0wODxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJi
YWNrZ3JvdW5kOndoaXRlIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNl
cmlmIj5IaSBYdWZlbmcsPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2Vy
aWYiPlRoYW5rcyBmb3IgdXBkYXRpbmcgdGhlIG1vZHVsZXMgdG8gYmUgTk1EQSBjb21wbGlhbnQu
Jm5ic3A7IEkgdGhpbmsgdGhhdCBnZXR0aW5nIHN0cnVjdHVyYWwgY29uc2lzdGVuY3kgYWNyb3Nz
IHRoZSBJRVRGIFlBTkcgbW9kdWxlcyB3aWxsIG1ha2UgdGhlbSBmYXINCiBtb3JlIGNvbXBlbGxp
bmcgYXMgYSBzb2x1dGlvbi48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1z
ZXJpZiI+SSBub3RpY2VkIHRoYXQgc29tZSBvZiB0aGUgc25pcHBldHMgb2YgWUFORyB0cmVlIG91
dHB1dCBpbiB0aGUgZHJhZnQgc3RpbGwgaWxsdXN0cmF0ZSB1c2luZyB0aGUgJnF1b3Q7c3BsaXQg
b2Mtc3R5bGUgY29uZmlnL3N0YXRlIHN0cnVjdHVyZSZxdW90OyBhbmQgaGVuY2UNCiBhbHNvIG5l
ZWQgdG8gYmUgdXBkYXRlZC4mbmJzcDsgUHJvYmFibHkgdGhpcyBjb3VsZCBiZSBkb25lIGFzIHBh
cnQgb2YgdGhlIFdHIExDLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNl
cmlmIj5UbyBmaW5kIHRoZSBpbnN0YW5jZXMsIGp1c3Qgc2VhcmNoIHRoZSBkcmFmdCBmb3IgJnF1
b3Q7cncgY29uZmlnJnF1b3Q7IGFuZCAmcXVvdDtybyBzdGF0ZSZxdW90Oy48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFj
a2dyb3VuZDp3aGl0ZSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZhbWlseTom
cXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZiI+VGhhbmtzLDxicj4NClJvYjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJiYWNrZ3JvdW5kOndoaXRlIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+T24g
MDIvMDcvMjAxNyAyMjo0MiwgWHVmZW5nIExpdSB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90
dG9tOjUuMHB0Ij4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3Vu
ZDp3aGl0ZSI+QW4gdXBkYXRlZCByZXZpc2lvbiBvZiB0aGUgVEUgdG9wb2xvZ3kgbW9kZWwgaGFz
IGJlZW4gcG9zdGVkIGF0PHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRlZC1zcGFjZSI+Jm5ic3A7
PC9zcGFuPjxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLXRl
YXMteWFuZy10ZS10b3BvLTEwIj48c3BhbiBzdHlsZT0iY29sb3I6cHVycGxlIj5odHRwczovL3Rv
b2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi10ZWFzLXlhbmctdGUtdG9wby0xMDwvc3Bhbj48
L2E+LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPlRoaXMg
bmV3IHJldmlzaW9uIG5vdyBjb250YWlucyB0aGUgTk1EQSBjb21wbGlhbnQgbW9kdWxlIGFuZCBh
IGNvbXBhbmlvbiDigJwtc3RhdGXigJ0gbW9kdWxlLCBhZnRlciB0aGUgSTJSUyB0b3BvbG9neSBt
b2RlbCB0aGF0IHdlIGF1Z21lbnQgaGFzIGJlZW4gdXBkYXRlIHdpdGggYSDigJwtc3RhdGXigJ0g
bW9kdWxlLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPk5v
dyB0aGF0IHRoaXMgaXNzdWUgaGFzIGJlZW4gc29sdmVkLCB0aGUgYXV0aG9ycyBhbmQgY29udHJp
YnV0b3JzIHRoaW5rIHRoYXQgdGhlIGRyYWZ0IGlzIHJlYWR5IGZvciB0aGUgbGFzdCBjYWxsLjxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
ImJhY2tncm91bmQ6d2hpdGUiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPlRoYW5rcyw8bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJi
YWNrZ3JvdW5kOndoaXRlIj4tIFh1ZmVuZzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPiZuYnNwOzxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJh
Y2tncm91bmQ6d2hpdGUiPlAuUy4gQmVjYXVzZSBvZiB0aGUgc3RydWN0dXJlIGNoYW5nZXMgb2Yg
dGhlIFRFIHRvcG9sb2d5IG1vZGVsLCBhbGwgYXVnbWVudGluZyBtb2RlbHMgbmVlZCB0byBiZSB1
cGRhdGVkLiBTb3JyeSBmb3IgdGhlIHNob3J0IG5vdGljZS48bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj4m
bmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9y
ZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDQuMHB0Ij4NCjxk
aXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNFMUUxRTEgMS4w
cHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPjxiPkZyb206PC9iPjxzcGFuIGNsYXNzPSJhcHBs
ZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj5UZWFzIFs8YSBocmVmPSJtYWlsdG86dGVh
cy1ib3VuY2VzQGlldGYub3JnIj48c3BhbiBzdHlsZT0iY29sb3I6cHVycGxlIj5tYWlsdG86dGVh
cy1ib3VuY2VzQGlldGYub3JnPC9zcGFuPjwvYT5dPHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRl
ZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPjxiPk9uDQogQmVoYWxmIE9mPHNwYW4gY2xhc3M9ImFwcGxl
LWNvbnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPjwvYj5CZW5vaXQgQ2xhaXNlPGJyPg0KPGI+
U2VudDo8L2I+PHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFu
Pk1vbmRheSwgSnVuZSAyNiwgMjAxNyA2OjQ2IEFNPGJyPg0KPGI+VG86PC9iPjxzcGFuIGNsYXNz
PSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj5YdWZlbmcgTGl1PHNwYW4gY2xh
c3M9ImFwcGxlLWNvbnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPjxhIGhyZWY9Im1haWx0bzpY
dWZlbmdfTGl1QGphYmlsLmNvbSI+PHNwYW4gc3R5bGU9ImNvbG9yOnB1cnBsZSI+Jmx0O1h1ZmVu
Z19MaXVAamFiaWwuY29tJmd0Ozwvc3Bhbj48L2E+OyBSb2JlcnQgV2lsdG9uPHNwYW4gY2xhc3M9
ImFwcGxlLWNvbnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPjxhIGhyZWY9Im1haWx0bzpyd2ls
dG9uQGNpc2NvLmNvbSI+PHNwYW4gc3R5bGU9ImNvbG9yOnB1cnBsZSI+Jmx0O3J3aWx0b25AY2lz
Y28uY29tJmd0Ozwvc3Bhbj48L2E+Ow0KIE1haGVzaCBKZXRoYW5hbmRhbmk8c3BhbiBjbGFzcz0i
YXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+PGEgaHJlZj0ibWFpbHRvOm1qZXRo
YW5hbmRhbmlAZ21haWwuY29tIj48c3BhbiBzdHlsZT0iY29sb3I6cHVycGxlIj4mbHQ7bWpldGhh
bmFuZGFuaUBnbWFpbC5jb20mZ3Q7PC9zcGFuPjwvYT47PHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZl
cnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPjxhIGhyZWY9Im1haWx0bzp5YW5nLWRvY3RvcnNAaWV0
Zi5vcmciPjxzcGFuIHN0eWxlPSJjb2xvcjpwdXJwbGUiPnlhbmctZG9jdG9yc0BpZXRmLm9yZzwv
c3Bhbj48L2E+PGJyPg0KPGI+Q2M6PC9iPjxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3Bh
Y2UiPiZuYnNwOzwvc3Bhbj5CZW5vaXQgQ2xhaXNlPHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRl
ZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPjxhIGhyZWY9Im1haWx0bzpiY2xhaXNlQGNpc2NvLmNvbSI+
PHNwYW4gc3R5bGU9ImNvbG9yOnB1cnBsZSI+Jmx0O2JjbGFpc2VAY2lzY28uY29tJmd0Ozwvc3Bh
bj48L2E+OzxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj48
YSBocmVmPSJtYWlsdG86aWV0ZkBpZXRmLm9yZyI+PHNwYW4gc3R5bGU9ImNvbG9yOnB1cnBsZSI+
aWV0ZkBpZXRmLm9yZzwvc3Bhbj48L2E+OzxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3Bh
Y2UiPiZuYnNwOzwvc3Bhbj48YSBocmVmPSJtYWlsdG86dGVhc0BpZXRmLm9yZyI+PHNwYW4gc3R5
bGU9ImNvbG9yOnB1cnBsZSI+dGVhc0BpZXRmLm9yZzwvc3Bhbj48L2E+OzxzcGFuIGNsYXNzPSJh
cHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj48YSBocmVmPSJtYWlsdG86ZHJhZnQt
aWV0Zi10ZWFzLXlhbmctdGUtdG9wby5hbGxAaWV0Zi5vcmciPjxzcGFuIHN0eWxlPSJjb2xvcjpw
dXJwbGUiPmRyYWZ0LWlldGYtdGVhcy15YW5nLXRlLXRvcG8uYWxsQGlldGYub3JnPC9zcGFuPjwv
YT48YnI+DQo8Yj5TdWJqZWN0OjwvYj48c3BhbiBjbGFzcz0iYXBwbGUtY29udmVydGVkLXNwYWNl
Ij4mbmJzcDs8L3NwYW4+UmU6IFtUZWFzXSBZYW5nZG9jdG9ycyBsYXN0IGNhbGwgcmV2aWV3IG9m
IGRyYWZ0LWlldGYtdGVhcy15YW5nLXRlLXRvcG8tMDg8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dy
b3VuZDp3aGl0ZSI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPkhpIFh1ZmVuZyw8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2lu
LXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6
d2hpdGUiPkhpIEJlbm9pdCw8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3Vu
ZDp3aGl0ZSI+Jm5ic3A7PG86cD48L286cD48L3ByZT4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJn
aW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPHByZSBzdHlsZT0iYmFja2dyb3Vu
ZDp3aGl0ZSI+LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS08bzpwPjwvbzpwPjwvcHJlPg0KPHBy
ZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+RnJvbTogQmVub2l0IENsYWlzZSBbPGEgaHJlZj0i
bWFpbHRvOmJjbGFpc2VAY2lzY28uY29tIj48c3BhbiBzdHlsZT0iY29sb3I6cHVycGxlIj5tYWls
dG86YmNsYWlzZUBjaXNjby5jb208L3NwYW4+PC9hPl08bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBz
dHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+U2VudDogVGh1cnNkYXksIEp1bmUgMjIsIDIwMTcgNjox
MiBBTTxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5Ubzog
Um9iZXJ0IFdpbHRvbiA8YSBocmVmPSJtYWlsdG86cndpbHRvbkBjaXNjby5jb20iPjxzcGFuIHN0
eWxlPSJjb2xvcjpwdXJwbGUiPiZsdDtyd2lsdG9uQGNpc2NvLmNvbSZndDs8L3NwYW4+PC9hPjsg
WHVmZW5nIExpdSA8YSBocmVmPSJtYWlsdG86WHVmZW5nX0xpdUBqYWJpbC5jb20iPjxzcGFuIHN0
eWxlPSJjb2xvcjpwdXJwbGUiPiZsdDtYdWZlbmdfTGl1QGphYmlsLmNvbSZndDs8L3NwYW4+PC9h
Pjs8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+TWFoZXNo
IEpldGhhbmFuZGFuaSA8YSBocmVmPSJtYWlsdG86bWpldGhhbmFuZGFuaUBnbWFpbC5jb20iPjxz
cGFuIHN0eWxlPSJjb2xvcjpwdXJwbGUiPiZsdDttamV0aGFuYW5kYW5pQGdtYWlsLmNvbSZndDs8
L3NwYW4+PC9hPjsgPGEgaHJlZj0ibWFpbHRvOnlhbmctZG9jdG9yc0BpZXRmLm9yZyI+PHNwYW4g
c3R5bGU9ImNvbG9yOnB1cnBsZSI+eWFuZy1kb2N0b3JzQGlldGYub3JnPC9zcGFuPjwvYT48bzpw
PjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+Q2M6IDxhIGhyZWY9
Im1haWx0bzppZXRmQGlldGYub3JnIj48c3BhbiBzdHlsZT0iY29sb3I6cHVycGxlIj5pZXRmQGll
dGYub3JnPC9zcGFuPjwvYT47IDxhIGhyZWY9Im1haWx0bzp0ZWFzQGlldGYub3JnIj48c3BhbiBz
dHlsZT0iY29sb3I6cHVycGxlIj50ZWFzQGlldGYub3JnPC9zcGFuPjwvYT47IDxhIGhyZWY9Im1h
aWx0bzpkcmFmdC1pZXRmLXRlYXMteWFuZy10ZS10b3BvLmFsbEBpZXRmLm9yZyI+PHNwYW4gc3R5
bGU9ImNvbG9yOnB1cnBsZSI+ZHJhZnQtaWV0Zi10ZWFzLXlhbmctdGUtdG9wby5hbGxAaWV0Zi5v
cmc8L3NwYW4+PC9hPjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndo
aXRlIj5TdWJqZWN0OiBSZTogW1RlYXNdIFlhbmdkb2N0b3JzIGxhc3QgY2FsbCByZXZpZXcgb2Yg
ZHJhZnQtaWV0Zi10ZWFzLXlhbmctdGUtdG9wby08bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHls
ZT0iYmFja2dyb3VuZDp3aGl0ZSI+MDg8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFj
a2dyb3VuZDp3aGl0ZSI+Jm5ic3A7PG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tn
cm91bmQ6d2hpdGUiPkRlYXIgZHJhZnQtaWV0Zi10ZWFzLXlhbmctdGUtdG9wbyBhdXRob3JzLDxv
OnA+PC9vOnA+PC9wcmU+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJn
aW4tYm90dG9tOjUuMHB0Ij4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPkhpIFh1ZmVu
Zyw8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+Jm5ic3A7
PG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPk9LLCBieSB0
b29saW5nLCBJIGRvbid0IG1lYW4gdGhlIHB5YW5nIHBsdWdpbnMgdGhhdCBJIGhhdmUgYmVlbjxv
OnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj53b3JraW5nIG9u
IHRvIGNvbnZlcnQgYmV0d2VlbiBkaWZmZXJlbnQgdHlwZXMgb2YgbW9kZWxzLiZuYnNwOyBBcyB5
b3U8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+YXdhcmUs
IHRoZSBURSBZQU5HIG1vZGVscyBjYW4gZWFzaWx5IGJlIGNvbnZlcnRlZCB0byBOTURBIHN0eWxl
IHNpbmNlPG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPkkg
aGF2ZSBhbHJlYWR5IGRvbmUgaXQ8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dy
b3VuZDp3aGl0ZSI+KDxhIGhyZWY9Imh0dHBzOi8vZ2l0aHViLmNvbS9yZ3dpbHRvbi9pZXRmLW1v
ZGVscy10by1jb21iaW5lZCI+PHNwYW4gc3R5bGU9ImNvbG9yOnB1cnBsZSI+aHR0cHM6Ly9naXRo
dWIuY29tL3Jnd2lsdG9uL2lldGYtbW9kZWxzLXRvLWNvbWJpbmVkPC9zcGFuPjwvYT4pLjxvOnA+
PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj4mbmJzcDs8bzpwPjwv
bzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+TXkgY29tbWVudCBhY3R1
YWxseSByZWxhdGVzIHRvIHRoZSBmYWN0IHRoZSBzdHJ1Y3R1cmUgdXNlZCBieSBURSBZQU5HPG86
cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPm1vZHVsZXMgZG9u
J3QgbWF0Y2ggYW55IG90aGVyIFlBTkcgbW9kdWxlcyAtIHRoZXkgYXJlIHVzaW5nIHRoZWlyIG93
bjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj51bmlxdWUg
c3R5bGUgb2Ygc3RydWN0dXJlLjxvOnA+PC9vOnA+PC9wcmU+DQo8L2Jsb2NrcXVvdGU+DQo8cHJl
IHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5UaGlzIGlzIGFuIGltcG9ydGFudCBpc3N1ZSB0byBy
ZXNvbHZlLjxvOnA+PC9vOnA+PC9wcmU+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1
LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUi
PiZuYnNwOzxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5U
b2RheSwgdGhlcmUgYXJlIHRocmVlIGNvbW1vbiBzdHlsZXMgb2YgbW9kdWxlczo8bzpwPjwvbzpw
PjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+KDEpIElFVEYgc3R5bGUgc3Bs
aXQgY29uZmlnL3N0YXRlIHRyZWVzIChlLmcuIGlldGYtaW50ZXJmYWNlcykuPG86cD48L286cD48
L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPigyKSBJRVRGIE5NREEgc3R5bGUg
Y29tYmluZWQgY29uZmlnL3N0YXRlIHRyZWVzIChpLmUuIHdoZXJlIGFsbCBJRVRGPG86cD48L286
cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPm1vZHVsZXMgYXJlIGhlYWRp
bmcgdG8pLjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj4o
MykgT3BlbkNvbmZpZyBzdHlsZSBtb2R1bGVzIHdpdGggdGhlIGNvbmZpZy9zdGF0ZSBjb250YWlu
ZXJzPG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPmltbWVk
aWF0ZWx5IGFib3ZlIHRoZSBjb25maWcgbGVhdmVzLjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0
eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj4mbmJzcDs8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHls
ZT0iYmFja2dyb3VuZDp3aGl0ZSI+VG9vbGluZyBpcyBsaWtlbHkgdG8gYmUgb3B0aW1pemVkIHRv
IHdvcmsgd2l0aCB0aGVzZSBtb2RlbCBzdHJ1Y3R1cmVzLDxvOnA+PC9vOnA+PC9wcmU+DQo8cHJl
IHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5idXQgdGhlIFRFIG1vZHVsZXMgZG8gbm90IGZpdCBp
bnRvIGFueSBvZiB0aGUgdGhyZWUgc3R5bGVzIGFib3ZlLjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJl
IHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5UaGV5IGFyZSBhIHlldCBhbm90aGVyIE9wZW5Db25m
aWctbGlrZSBzdHlsZSwgYnV0IHRoYXQgaXMgZGlmZmVyZW50PG86cD48L286cD48L3ByZT4NCjxw
cmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPmVub3VnaCB0aGF0IHRvb2xpbmcgdGhhdCBpcyBk
ZXNpZ25lZCB0byB3b3JrIHdpdGggT3BlbkNvbmZpZyBzdHlsZTxvOnA+PC9vOnA+PC9wcmU+DQo8
cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5ZQU5HIG1vZHVsZXMgd291bGQgbGlrZWx5IG5v
dCB3b3JrIHdpdGggdGhlIFRFIFlBTkcgbW9kdWxlcy48bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBz
dHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+Jm5ic3A7PG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5
bGU9ImJhY2tncm91bmQ6d2hpdGUiPlNwZWNpZmljYWxseSwgZm9yIGNsaWVudHMgdGhhdCBleHBl
Y3RpbmcgdG8gd29yayB3aXRoIGFuIE9wZW5Db25maWc8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBz
dHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+c3R5bGUgWUFORyBtb2R1bGUsIHRoZW4gaWYgaXQga25v
d3MgdGhlIHBhdGggdG8gY29uZmlnIGxlYWYgWCwgdGhlbjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJl
IHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj50aGV5IHdvdWxkIGV4cGVjdCB0aGUgYXBwbGllZCBj
b25maWcgdmFsdWUgdG8gYmUgYXZhaWxhYmxlIGF0IHRoZSBwYXRoPG86cD48L286cD48L3ByZT4N
CjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPiZxdW90Oy4uL3N0YXRlL1gmcXVvdDsuJm5i
c3A7IEJ1dCwgdGhpcyBkb2Vzbid0IGhvbGQgZm9yIHRoZSBzdHJ1Y3R1cmUgYmVpbmcgdXNlZCBp
bjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj50aGUgVEUg
WUFORyBtb2RlbHMuPG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hp
dGUiPiZuYnNwOzxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRl
Ij5JIGJlbGlldmUgc3Ryb25nbHkgdGhhdCB0aGUgbW9kZWxzIGJlaW5nIHByb2R1Y2VkIGJ5IG9y
Z2FuaXphdGlvbnM8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0
ZSI+c2hvdWxkIGJlIHN0cnVjdHVyZXMgaW4gYSBjb25zaXN0ZW50IHdheSwgaGVuY2Ugd2h5IEkg
dGhpbmsgdGhhdCB0aGU8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3
aGl0ZSI+cHVibGlzaGVkIHN0YW5kYXJkIHZlcnNpb24gb2YgdGhlIFRFIFlBTkcgbW9kdWxlcyBz
aG91bGQgaW1tZWRpYXRlbHk8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3Vu
ZDp3aGl0ZSI+YWxpZ24gdG8gdGhlIE5NREEgc3R5bGUuPG86cD48L286cD48L3ByZT4NCjwvYmxv
Y2txdW90ZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPkFncmVlZC48bzpwPjwvbzpw
PjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+SGVyZSBpcyB0aGUgT1BTIGFu
ZCBSVEcgQUQgbWVzc2FnZTo8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3Vu
ZDp3aGl0ZSI+PGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9u
ZXRtb2QvY3VycmVudC9tc2cxODI1Mi5odG1sIj48c3BhbiBzdHlsZT0iY29sb3I6cHVycGxlIj5o
dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2ViL25ldG1vZC9jdXJyZW50L21zZzE4
MjUyLmh0bWw8L3NwYW4+PC9hPjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3Jv
dW5kOndoaXRlIj4mbmJzcDs8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3Vu
ZDp3aGl0ZSI+SSB1bmRlcnN0YW5kIHRoYXQgdGhlIEkyUlMgdG9wb2xvZ3kgWUFORyBtb2R1bGVz
IHdpbGwgYmUgaW1wcm92ZWQgdG8gdGhlPG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJh
Y2tncm91bmQ6d2hpdGUiPk5NREEgc3R5bGUuPG86cD48L286cD48L3ByZT4NCjwvYmxvY2txdW90
ZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPltYdWZlbmddIFRoZSBJMlJTIHRvcG9s
b2d5IG1vZGVsIGlzIGFscmVhZHkgTk1EQSBzdHlsZSwgYnV0IHRoZSBOTURBIG1vZGVscyBhcmUg
bm90IGltbWVkaWF0ZWx5IGltcGxlbWVudGFibGUgd2l0aG91dCBORVRDT05GL1JFU1RDT05GIHBy
b3RvY29sIHVwZGF0ZS4gV2Ugd2lsbCBuZWVkIHRoZSAmcXVvdDstc3RhdGUmcXVvdDsgbW9kdWxl
IGZvciB0aGUgSTJSUyB0b3BvbG9neSBtb2RlbCAoYW5kIGZvciBhbGwgdGhlIHRvcC1sZXZlbCBt
b2RlbHMpIGZvciBub3cuIDxvOnA+PC9vOnA+PC9wcmU+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPkFkZGluZyAtc3Rh
dGUgdG8gdGhlIEFwcGVuZGl4IGlzIGEgcG9zc2liaWxpdHkuPGJyPg0KJnF1b3Q7SW4gYWxsIGNh
c2VzLCB0aGUgTk1EQSBhbmQgbm9uLU5NREEgbW9kdWxlcyBTSE9VTEQgYmUgcHVibGlzaGVkIGlu
IHRoZSBzYW1lIGRvY3VtZW50LCB3aXRoIE5NREEgbW9kdWxlcyBpbiB0aGUgZG9jdW1lbnQgbWFp
biBib2R5IGFuZCB0aGUgbm9uLU5NREEgbW9kdWxlcyBpbiBhbiBBcHBlbmRpeC4mcXVvdDs8YnI+
DQpTZWU8c3BhbiBjbGFzcz0iYXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+PGEg
aHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9uZXRtb2QvY3VycmVu
dC9tc2cxODI1Mi5odG1sIj48c3BhbiBzdHlsZT0iY29sb3I6cHVycGxlIj5odHRwczovL3d3dy5p
ZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2ViL25ldG1vZC9jdXJyZW50L21zZzE4MjUyLmh0bWw8L3Nw
YW4+PC9hPjxicj4NCjxicj4NCjxicj4NCjxicj4NCjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4N
CjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPldoaWxlIHRoZSBOTURBIGlzIG5pY2UsIHRo
ZSBOTURBIGRpc2N1c3Npb25zIGhhdmUgYWxyZWFkeSBzaWduaWZpY2FudGx5IGRlbGF5ZWQgcHVi
bGlzaGluZyBuZXcgbW9kZWxzLCBhbmQgZG9pbmcgTk1EQSB3aXRob3V0IHN0YWdpbmcgd2lsbCBm
dXJ0aGVyIGRlbGF5IHRoZSBwcm9jZXNzLjxvOnA+PC9vOnA+PC9wcmU+DQo8L2Jsb2NrcXVvdGU+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPlRo
aXMgaXMgbm90IHNvbHZpbmcgdGhlIGltcG9ydGFudCBpc3N1ZSBicm91Z2h0IHVwIGJ5IFJvYiBX
aXRsb246PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4t
dG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5NeSBjb21tZW50IGFjdHVhbGx5IHJlbGF0ZXMg
dG8gdGhlIGZhY3QgdGhlIHN0cnVjdHVyZSB1c2VkIGJ5IFRFIFlBTkcgbW9kdWxlcyBkb24ndCBt
YXRjaCBhbnkgb3RoZXIgWUFORyBtb2R1bGVzIC0gdGhleSBhcmUgdXNpbmcgdGhlaXIgb3duIHVu
aXF1ZSBzdHlsZSBvZiBzdHJ1Y3R1cmUuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvYmxvY2tx
dW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0
ZSI+UmVnYXJkcywgQi48YnI+DQo8YnI+DQo8YnI+DQo8YnI+DQo8bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1
LjBwdCI+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj4mbmJzcDs8bzpwPjwvbzpwPjwv
cHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+VGhhbmtzLCZuYnNwOyBYdWZlbmc8
bzpwPjwvbzpwPjwvcHJlPg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFy
Z2luLWJvdHRvbTo1LjBwdCI+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj4mbmJzcDs8
bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+UmVnYXJkcywg
QmVub2l0PG86cD48L286cD48L3ByZT4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUu
MHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+
Jm5ic3A7PG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPlRo
YW5rcyw8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+Um9i
PG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPiZuYnNwOzxv
OnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj4mbmJzcDs8bzpw
PjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+T24gMjIvMDYvMjAx
NyAwNDoxNiwgWHVmZW5nIExpdSB3cm90ZTo8bzpwPjwvbzpwPjwvcHJlPg0KPGJsb2NrcXVvdGUg
c3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8cHJlIHN0eWxl
PSJiYWNrZ3JvdW5kOndoaXRlIj5IaSBSb2IsPG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9
ImJhY2tncm91bmQ6d2hpdGUiPiZuYnNwOzxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJi
YWNrZ3JvdW5kOndoaXRlIj5XaGlsZSB0aGUgdG9vbGluZyBpcyB2ZXJ5IG5pY2UgdG8gaGF2ZSwg
ZXNwZWNpYWxseSBmb3Igd3JpdGluZyBuZXc8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0i
YmFja2dyb3VuZDp3aGl0ZSI+bW9kZWxzIG9yIGNvbnZlcnRpbmcgbW9kZWxzLCB3ZSBkbyBub3Qg
aGF2ZSB0byB1c2UgaXQgZm9yIGV2ZXJ5PG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJh
Y2tncm91bmQ6d2hpdGUiPm1vZGVsLiBJdCBzZWVtcyBub3QgbmVjZXNzYXJ5IHRvIHVzZSB0aGUg
dG9vbGluZyBvbiB0aGlzIG1vZGVsIGZvcjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJi
YWNrZ3JvdW5kOndoaXRlIj5ub3cuIFdlIGFscmVhZHkga25vdyB0aGF0IHdlIGNhbiBtYW51YWxs
eSBjb252ZXJ0IGl0IHRvIE5NREEgc3R5bGUgaWY8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHls
ZT0iYmFja2dyb3VuZDp3aGl0ZSI+bmVlZGVkLjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxl
PSJiYWNrZ3JvdW5kOndoaXRlIj4mbmJzcDs8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0i
YmFja2dyb3VuZDp3aGl0ZSI+VGhhbmtzLDxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJi
YWNrZ3JvdW5kOndoaXRlIj4tIFh1ZmVuZzxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJi
YWNrZ3JvdW5kOndoaXRlIj4mbmJzcDs8bzpwPjwvbzpwPjwvcHJlPg0KPGJsb2NrcXVvdGUgc3R5
bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8cHJlIHN0eWxlPSJi
YWNrZ3JvdW5kOndoaXRlIj4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxvOnA+PC9vOnA+PC9w
cmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5Gcm9tOiBSb2JlcnQgV2lsdG9uIFs8
YSBocmVmPSJtYWlsdG86cndpbHRvbkBjaXNjby5jb20iPjxzcGFuIHN0eWxlPSJjb2xvcjpwdXJw
bGUiPm1haWx0bzpyd2lsdG9uQGNpc2NvLmNvbTwvc3Bhbj48L2E+XTxvOnA+PC9vOnA+PC9wcmU+
DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5TZW50OiBXZWRuZXNkYXksIEp1bmUgMjEs
IDIwMTcgNTozNCBBTTxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndo
aXRlIj5UbzogWHVmZW5nIExpdSA8YSBocmVmPSJtYWlsdG86WHVmZW5nX0xpdUBqYWJpbC5jb20i
PjxzcGFuIHN0eWxlPSJjb2xvcjpwdXJwbGUiPiZsdDtYdWZlbmdfTGl1QGphYmlsLmNvbSZndDs8
L3NwYW4+PC9hPjsgTWFoZXNoIEpldGhhbmFuZGFuaTxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0
eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj48YSBocmVmPSJtYWlsdG86bWpldGhhbmFuZGFuaUBnbWFp
bC5jb20iPjxzcGFuIHN0eWxlPSJjb2xvcjpwdXJwbGUiPiZsdDttamV0aGFuYW5kYW5pQGdtYWls
LmNvbSZndDs8L3NwYW4+PC9hPjsgPGEgaHJlZj0ibWFpbHRvOnlhbmctZG9jdG9yc0BpZXRmLm9y
ZyI+PHNwYW4gc3R5bGU9ImNvbG9yOnB1cnBsZSI+eWFuZy1kb2N0b3JzQGlldGYub3JnPC9zcGFu
PjwvYT48bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+Q2M6
IDxhIGhyZWY9Im1haWx0bzppZXRmQGlldGYub3JnIj48c3BhbiBzdHlsZT0iY29sb3I6cHVycGxl
Ij5pZXRmQGlldGYub3JnPC9zcGFuPjwvYT47IDxhIGhyZWY9Im1haWx0bzp0ZWFzQGlldGYub3Jn
Ij48c3BhbiBzdHlsZT0iY29sb3I6cHVycGxlIj50ZWFzQGlldGYub3JnPC9zcGFuPjwvYT47PG86
cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPjxhIGhyZWY9Im1h
aWx0bzpkcmFmdC1pZXRmLXRlYXMteWFuZy10ZS10b3BvLmFsbEBpZXRmLm9yZyI+PHNwYW4gc3R5
bGU9ImNvbG9yOnB1cnBsZSI+ZHJhZnQtaWV0Zi10ZWFzLXlhbmctdGUtdG9wby5hbGxAaWV0Zi5v
cmc8L3NwYW4+PC9hPjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndo
aXRlIj5TdWJqZWN0OiBSZTogW1RlYXNdIFlhbmdkb2N0b3JzIGxhc3QgY2FsbCByZXZpZXcgb2Y8
bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+ZHJhZnQtaWV0
Zi10ZWFzLXlhbmctdGUtdG9wby08bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dy
b3VuZDp3aGl0ZSI+MDg8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3
aGl0ZSI+Jm5ic3A7PG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hp
dGUiPkhpIFh1ZmVuZyw8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3
aGl0ZSI+Jm5ic3A7PG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hp
dGUiPk9uIDEyLzA2LzIwMTcgMjI6MjgsIFh1ZmVuZyBMaXUgd3JvdGU6PG86cD48L286cD48L3By
ZT4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4w
cHQiPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+SGkgTWFoZXNoLDxvOnA+PC9vOnA+
PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj4mbmJzcDs8bzpwPjwvbzpwPjwv
cHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+VGhhbmsgeW91IG11Y2ggZm9yIHRo
ZSByZXZpZXcuIFdlIGhhdmUgc3VibWl0dGVkIGFuIHVwZGF0ZWQgZHJhZnQ8bzpwPjwvbzpwPjwv
cHJlPg0KPC9ibG9ja3F1b3RlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+KDxhIGhy
ZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLXRlYXMteWFuZy10ZS10
b3BvLTA5Ij48c3BhbiBzdHlsZT0iY29sb3I6cHVycGxlIj5odHRwczovL3Rvb2xzLmlldGYub3Jn
L2h0bWwvZHJhZnQtaWV0Zi10ZWFzLXlhbmctdGUtdG9wby0wOTwvc3Bhbj48L2E+KSB0bzxvOnA+
PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5hZGRyZXNzIHRoZXNl
IGlzc3Vlcy4gTW9yZSBkZXRhaWxlZCBleHBsYW5hdGlvbnMgYXJlIHB1dCBiZWxvdzxvOnA+PC9v
OnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5pbmxpbmUuPG86cD48L286
cD48L3ByZT4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0
b206NS4wcHQiPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+SWYgdGhlIHJlc3BvbnNl
cyBhbmQgdXBkYXRlcyBhcmUgc2F0aXNmYWN0b3J5LCB3ZSBhcmUgcmVhZHkgZm9yIHRoZTxvOnA+
PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5sYXN0IGNhbGwuPG86
cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPiZuYnNwOzxvOnA+
PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5CZXN0IHJlZ2FyZHMs
PG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPi0gWHVmZW5n
PG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPiZuYnNwOzxv
OnA+PC9vOnA+PC9wcmU+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJn
aW4tYm90dG9tOjUuMHB0Ij4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPi0tLS0tT3Jp
Z2luYWwgTWVzc2FnZS0tLS0tPG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91
bmQ6d2hpdGUiPkZyb206IE1haGVzaCBKZXRoYW5hbmRhbmkgWzxhIGhyZWY9Im1haWx0bzptamV0
aGFuYW5kYW5pQGdtYWlsLmNvbSI+PHNwYW4gc3R5bGU9ImNvbG9yOnB1cnBsZSI+bWFpbHRvOm1q
ZXRoYW5hbmRhbmlAZ21haWwuY29tPC9zcGFuPjwvYT5dPG86cD48L286cD48L3ByZT4NCjxwcmUg
c3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPlNlbnQ6IFdlZG5lc2RheSwgTWF5IDI0LCAyMDE3IDEx
OjQ0IEFNPG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPlRv
OiA8YSBocmVmPSJtYWlsdG86eWFuZy1kb2N0b3JzQGlldGYub3JnIj48c3BhbiBzdHlsZT0iY29s
b3I6cHVycGxlIj55YW5nLWRvY3RvcnNAaWV0Zi5vcmc8L3NwYW4+PC9hPjxvOnA+PC9vOnA+PC9w
cmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5DYzogPGEgaHJlZj0ibWFpbHRvOmll
dGZAaWV0Zi5vcmciPjxzcGFuIHN0eWxlPSJjb2xvcjpwdXJwbGUiPmlldGZAaWV0Zi5vcmc8L3Nw
YW4+PC9hPjsgPGEgaHJlZj0ibWFpbHRvOnRlYXNAaWV0Zi5vcmciPjxzcGFuIHN0eWxlPSJjb2xv
cjpwdXJwbGUiPnRlYXNAaWV0Zi5vcmc8L3NwYW4+PC9hPjs8bzpwPjwvbzpwPjwvcHJlPg0KPHBy
ZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+PGEgaHJlZj0ibWFpbHRvOmRyYWZ0LWlldGYtdGVh
cy15YW5nLXRlLXRvcG8uYWxsQGlldGYub3JnIj48c3BhbiBzdHlsZT0iY29sb3I6cHVycGxlIj5k
cmFmdC1pZXRmLXRlYXMteWFuZy10ZS10b3BvLmFsbEBpZXRmLm9yZzwvc3Bhbj48L2E+PG86cD48
L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPlN1YmplY3Q6IFlhbmdk
b2N0b3JzIGxhc3QgY2FsbCByZXZpZXcgb2Y8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0i
YmFja2dyb3VuZDp3aGl0ZSI+ZHJhZnQtaWV0Zi10ZWFzLXlhbmctdGUtdG9wby0wODxvOnA+PC9v
OnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj4mbmJzcDs8bzpwPjwvbzpw
PjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+UmV2aWV3ZXI6IE1haGVzaCBK
ZXRoYW5hbmRhbmk8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0
ZSI+UmV2aWV3IHJlc3VsdDogUmVhZHkgd2l0aCBJc3N1ZXM8bzpwPjwvbzpwPjwvcHJlPg0KPHBy
ZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+Jm5ic3A7PG86cD48L286cD48L3ByZT4NCjxwcmUg
c3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPkRvY3VtZW50IHJldmlld2VkOiBkcmFmdC1pZXRmLXRl
YXMteWFuZy10ZS10b3BvLTA4PG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91
bmQ6d2hpdGUiPiZuYnNwOzxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5k
OndoaXRlIj5TdGF0dXM6IFJlYWR5IHdpdGggSXNzdWVzPG86cD48L286cD48L3ByZT4NCjxwcmUg
c3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPiZuYnNwOzxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0
eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5JIGFtIG5vdCBhbiBleHBlcnQgaW4gVHJhZmZpYyBFbmdp
bmVlcmluZy4gVGhpcyByZXZpZXcgaXMgbG9va2luZzxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0
eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5hdCB0aGUgZHJhZnQgZnJvbSBhIFlBTkcgcGVyc3BlY3Rp
dmUuIFdpdGggdGhhdCBzYWlkLCBJIGhhdmU8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0i
YmFja2dyb3VuZDp3aGl0ZSI+bWFya2VkIGl0IGFzIOKAnFJlYWR5PG86cD48L286cD48L3ByZT4N
CjwvYmxvY2txdW90ZT4NCjwvYmxvY2txdW90ZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hp
dGUiPndpdGggSXNzdWVz4oCdPG86cD48L286cD48L3ByZT4NCjxibG9ja3F1b3RlIHN0eWxlPSJt
YXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGJsb2NrcXVvdGUgc3R5bGU9
Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8cHJlIHN0eWxlPSJiYWNr
Z3JvdW5kOndoaXRlIj5iZWNhdXNlIG9mIHNvbWUgb2YgdGhlIHBvaW50cyBkaXNjdXNzZWQgYmVs
b3cuPG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPiZuYnNw
OzxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5TdW1tYXJ5
OjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj4mbmJzcDs8
bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+VGhpcyBkb2N1
bWVudCBkZWZpbmVzIGEgWUFORyBkYXRhIG1vZGVsIGZvciByZXByZXNlbnRpbmcsPG86cD48L286
cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPnJldHJpZXZpbmcgYW5kIG1h
bmlwdWxhdGluZyBURSBUb3BvbG9naWVzLiBUaGUgbW9kZWwgc2VydmVzIGFzIGE8bzpwPjwvbzpw
PjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+YmFzZSBtb2RlbCB0aGF0IG90
aGVyIHRlY2hub2xvZ3kgc3BlY2lmaWMgVEUgVG9wb2xvZ3kgbW9kZWxzIGNhbjxvOnA+PC9vOnA+
PC9wcmU+DQo8L2Jsb2NrcXVvdGU+DQo8L2Jsb2NrcXVvdGU+DQo8L2Jsb2NrcXVvdGU+DQo8L2Js
b2NrcXVvdGU+DQo8L2Jsb2NrcXVvdGU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5h
dWdtZW50LjxvOnA+PC9vOnA+PC9wcmU+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1
LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9w
OjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10
b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2lu
LXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJn
aW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPHByZSBzdHlsZT0iYmFja2dyb3Vu
ZDp3aGl0ZSI+Jm5ic3A7PG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6
d2hpdGUiPkNvbW1lbnRzOjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5k
OndoaXRlIj4mbmJzcDs8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3
aGl0ZSI+QWxtb3N0IGFsbCB0aGUgY29udGFpbmVycyBpbiB0aGUgbW9kZWwgYXJlIHByZXNlbmNl
IGNvbnRhaW5lcnMuIElzPG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6
d2hpdGUiPnRoZXJlIGEgcmVhc29uIHdoeSB0aGV5IGhhdmUgdG8gYmUgcHJlc2VuY2UgY29udGFp
bmVycz8gTm90ZSwgdGhhdDxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5k
OndoaXRlIj5wcmVzZW5jZSBjb250YWluZXJzIGFyZSBjb250YWluZXJzIHdob3NlIGV4aXN0ZW5j
ZSBpdHNlbGY8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+
cmVwcmVzZW50cyBjb25maWd1cmF0aW9uIGRhdGEuIFdoYXQgcGFydGljdWxhciBjb25maWd1cmF0
aW9uIGRhdGE8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+
aXMgZWFjaCBjb250YWluZXI8bzpwPjwvbzpwPjwvcHJlPg0KPC9ibG9ja3F1b3RlPg0KPC9ibG9j
a3F1b3RlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+cmVwcmVzZW50aW5nIGluIGl0
c2VsZj88bzpwPjwvbzpwPjwvcHJlPg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4w
cHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5b
WHVmZW5nXSBDb250YWluZXJzIHRoYXQgdXNlIOKAnHByZXNlbmNl4oCdIGFyZTo8bzpwPjwvbzpw
PjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+Jm5ic3A7Jm5ic3A7Jm5ic3A7
IC0gQ29udGFpbmVyIOKAnHVuZGVybGF54oCdPG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9
ImJhY2tncm91bmQ6d2hpdGUiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBvJm5ic3A7
IFdlIGhhdmUgY2hhbmdlZCAxMyBvY2N1cnJlbmNlcyBvZiBzdWNoIGNvbnRhaW5lcnMgdG8gYmU8
bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+bm90PG86cD48
L286cD48L3ByZT4NCjwvYmxvY2txdW90ZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUi
PnByZXNlbmNlIGNvbnRhaW5lci48bzpwPjwvbzpwPjwvcHJlPg0KPGJsb2NrcXVvdGUgc3R5bGU9
Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8cHJlIHN0eWxlPSJiYWNr
Z3JvdW5kOndoaXRlIj4mbmJzcDsmbmJzcDsmbmJzcDsgLSBDb250YWluZXIg4oCcdGXigJ0gdW5k
ZXIgYXVnbWVudGF0aW9uPG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6
d2hpdGUiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBvJm5ic3A7IFRvIGluZGljYXRl
IHRoYXQg4oCcVEXigJ0gaXMgZW5hYmxlZCAoY29uZmlndXJhdGlvbiBkYXRhKTxvOnA+PC9vOnA+
PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj4mbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsgbyZuYnNwOyBBbHNvIHVzZWQgdG8gZG8gYXVnbWVudGF0aW9uLiBUaGUg4oCc
cHJlc2VuY2XigJ0gc3RhdGVtZW50IGNhbjxvOnA+PC9vOnA+PC9wcmU+DQo8L2Jsb2NrcXVvdGU+
DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5wcmV2ZW50IHRoZSBtYW5kYXRvcnkgY2hp
bGQgZnJvbSBhZmZlY3RpbmcgYXVnbWVudGVkIGJhc2UgbW9kZWwuPG86cD48L286cD48L3ByZT4N
CjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQi
Pg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IC0gL253
Om5ldHdvcmtzL253Om5ldHdvcmsvbnc6bmV0d29yay10eXBlcy90ZS10b3BvbG9neSE8bzpwPjwv
bzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7IG8mbmJzcDsgQSBtZWNoYW5pc20gcmVxdWlyZWQgYnkgSTJSUyB0b3Bv
bG9neSBtb2RlbCB0byBzcGVjaWZ5IHRoZTxvOnA+PC9vOnA+PC9wcmU+DQo8L2Jsb2NrcXVvdGU+
DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj50b3BvbG9neSB0eXBlLjxvOnA+PC9vOnA+
PC9wcmU+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9t
OjUuMHB0Ij4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0
b206NS4wcHQiPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+SXQgaXMgZGlmZmljdWx0
IHRvIGNvLXJlbGF0ZSB0aGUgZGlhZ3JhbSB3aXRoIHRoZSBtb2RlbCBpdHNlbGY8bzpwPjwvbzpw
PjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+YmVjYXVzZSBvZiBkaWZmZXJl
bnQgdGVybXMgYmVpbmcgdXNlZCB0byBkZWZpbmUgZGlmZmVyZW50IHBhcnRzIG9mPG86cD48L286
cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPnRoZSBtb2RlbC48bzpwPjwv
bzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+VGhlcmUgaXMg4oCcVEUg
VG9wb2xvZ3kgTW9kZWzigJ0gYW5kIHRoZW4gdGhlcmUgaXMg4oCcR2VuZXJpYyBURTxvOnA+PC9v
OnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5Ub3BvbG9neTxvOnA+PC9v
OnA+PC9wcmU+DQo8L2Jsb2NrcXVvdGU+DQo8L2Jsb2NrcXVvdGU+DQo8cHJlIHN0eWxlPSJiYWNr
Z3JvdW5kOndoaXRlIj5Nb2RlbOKAnS48bzpwPjwvbzpwPjwvcHJlPg0KPGJsb2NrcXVvdGUgc3R5
bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8YmxvY2txdW90ZSBz
dHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxwcmUgc3R5bGU9
ImJhY2tncm91bmQ6d2hpdGUiPkFyZSB0aGVzZSBvbmUgYW5kIHRoZSBzYW1lIG1vZGVscz8gSWYg
c28sIGEgY29tbW9uIHRlcm0gZm9yIGJvdGg8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0i
YmFja2dyb3VuZDp3aGl0ZSI+b2YgdGhlbSB3b3VsZCBiZSBoZWxwZnVsLjxvOnA+PC9vOnA+PC9w
cmU+DQo8L2Jsb2NrcXVvdGU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5bWHVmZW5n
XSBZZXMuIFRoZXNlIHR3byB0ZXJtcyBhcmUgdGhlIHNhbWUuIEZpZ3VyZSAxMiwgRmlndXJlIDEz
LDxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5hbmQgcmVs
ZXZhbnQ8bzpwPjwvbzpwPjwvcHJlPg0KPC9ibG9ja3F1b3RlPg0KPHByZSBzdHlsZT0iYmFja2dy
b3VuZDp3aGl0ZSI+ZGVzY3JpcHRpb25zIGhhdmUgYmVlbiB1cGRhdGVkIHRvIG1ha2UgdGhlIGRv
Y3VtZW50IGNvbnNpc3RlbnQuPG86cD48L286cD48L3ByZT4NCjxibG9ja3F1b3RlIHN0eWxlPSJt
YXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGJsb2NrcXVvdGUgc3R5bGU9
Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8cHJlIHN0eWxlPSJiYWNr
Z3JvdW5kOndoaXRlIj5UaGVyZSBpcyBleHRlbnNpdmUgdXNlIG9mIGdyb3VwaW5ncyBpbiB0aGUg
ZG9jdW1lbnQuIEhvd2V2ZXIsIG5vdDxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNr
Z3JvdW5kOndoaXRlIj5hbGwgaW5zdGFuY2VzIG9mIGdyb3VwaW5ncyBhcmUgdXNlZCBtdWx0aXBs
ZSBudW1iZXIgb2YgdGltZXMuPG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91
bmQ6d2hpdGUiPldoZXJlIHRoZXkgYXJlIG5vdCBiZWluZyByZXBlYXRlZCwgaXQgd291bGQgYmUg
YmV0dGVyIHRvIG1vdmUgdGhlPG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91
bmQ6d2hpdGUiPmdyb3VwaW5nIGRpcmVjdGx5IHdoZXJlIHRoZSB1c2VzIHN0YXRlbWVudCByZXNp
ZGVzLiBDYXNlIGluIHBvaW50PG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91
bmQ6d2hpdGUiPnRoZSBncm91cGluZzxvOnA+PC9vOnA+PC9wcmU+DQo8L2Jsb2NrcXVvdGU+DQo8
L2Jsb2NrcXVvdGU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5jb25uZWN0aXZpdHkt
bGFiZWwtcmVzdHJpY3Rpb24tbGlzdC48bzpwPjwvbzpwPjwvcHJlPg0KPGJsb2NrcXVvdGUgc3R5
bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8cHJlIHN0eWxlPSJi
YWNrZ3JvdW5kOndoaXRlIj5bWHVmZW5nXSBXZSBoYXZlIHJlbW92ZWQgdGhlIGZvbGxvd2luZyBn
cm91cGluZ3M8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHRlLWxpbmstYXVnbWVudDxvOnA+PC9vOnA+
PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj4mbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsgdGUtbm9kZS1hdWdtZW50PG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9
ImJhY2tncm91bmQ6d2hpdGUiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyB0ZS10ZXJt
aW5hdGlvbi1wb2ludC1hdWdtZW50PG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tn
cm91bmQ6d2hpdGUiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyB0ZS10b3BvbG9naWVz
LWF1Z21lbnQ8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHRlLXRvcG9sb2d5LWF1Z21lbnQ8bzpwPjwv
bzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7IHRlLWxpbmstc3RhdGUtdW5kZXJsYXktYXR0cmlidXRlczxvOnA+PC9v
OnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj4mbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsgdGUtbm9kZS1zdGF0ZS1kZXJpdmVkLW5vdGlmaWNhdGlvbjxvOnA+PC9v
OnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj4mbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsgJm5ic3A7dGUtdG9wb2xvZ3ktdHlwZTxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0
eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj4mbmJzcDs8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHls
ZT0iYmFja2dyb3VuZDp3aGl0ZSI+VGhlIHJlbWFpbmluZyBncm91cGluZ3MgaGF2ZSBiZWVuIGtl
cHQgc28gdGhhdCB3ZSBjYW46PG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91
bmQ6d2hpdGUiPiZuYnNwOyZuYnNwOyZuYnNwOyAtIFNoYXJlIHRoZSBncm91cGluZ3MgaW4gdGhp
cyBtb2RlbDxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj4m
bmJzcDsmbmJzcDsmbmJzcDsgLSBQcmVwYXJlIHRvIGJlIHNoYXJlZCBieSBhIG1vZGVsIGF1Z21l
bnRpbmcgdGhpcyBtb2RlbDxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5k
OndoaXRlIj4mbmJzcDsmbmJzcDsmbmJzcDsgLSBQcmV2ZW50IGEgZ3JvdXBpbmcgb3IgY29uZmln
dXJhdGlvbiBzZWN0aW9uIGZyb20gYmVpbmcgdG9vIGxvbmc8bzpwPjwvbzpwPjwvcHJlPg0KPHBy
ZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IC0gSW1wcm92ZSBy
ZWFkYWJpbGl0eTxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRl
Ij4mbmJzcDs8bzpwPjwvbzpwPjwvcHJlPg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6
NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRl
Ij5UaGUgc3BsaXQgYmV0d2VlbiBjb25maWcgYW5kIHN0YXRlIGNvbnRhaW5lcnMgZG9lcyBub3Qg
c2VlbSB0bzxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5m
b2xsb3cgYW55IHBhcnRpY3VsYXIgcGF0dGVybi48bzpwPjwvbzpwPjwvcHJlPg0KPC9ibG9ja3F1
b3RlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+W1h1ZmVuZ10gVGhlIHBhdHRlcm4g
aXMgY2xlYXI6PG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUi
PkZvciBlYWNoIG1hbmFnZWFibGUgZW50aXR5IChvYmplY3QpLCB0aGVyZSBpcyBhIGNvbmZpZyBj
b250YWluZXI8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+
YW5kIHN0YXRlPG86cD48L286cD48L3ByZT4NCjwvYmxvY2txdW90ZT4NCjxwcmUgc3R5bGU9ImJh
Y2tncm91bmQ6d2hpdGUiPmNvbnRhaW5lci4gVGhlIGNvbmZpZ3VyYWJsZSBwcm9wZXJ0aWVzIGdv
IGludG8gdGhlIGNvbmZpZyBjb250YWluZXI8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0i
YmFja2dyb3VuZDp3aGl0ZSI+YW5kIHN0YXRlIHByb3BlcnRpZXMgZ28gaW50byB0aGUgc3RhdGUg
Y29udGFpbmVyLiBTdWNoIG9iamVjdHMgYXJlPG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9
ImJhY2tncm91bmQ6d2hpdGUiPmlkZW50aWZpZWQgYnkgYSBsaXN0IGl0ZW0gb3IgYSBwcmVzZW5j
ZSBjb250YWluZXIgc28gdGhhdCB0aGU8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFj
a2dyb3VuZDp3aGl0ZSI+4oCcY3JlYXRl4oCdLCDigJxkZWxldGXigJ0sIGFuZCDigJxtb2RpZnni
gJ08bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+b3BlcmF0
aW9uczxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5jYW4g
YmUgcGVyZm9ybWVkIG9uIHRoZW0uIFRoZSBub24tcHJlc2VuY2UgY29udGFpbmVycyBkbyBub3Q8
bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+cmVwcmVzZW50
IGNvbmZpZ3VyYXRpb24gZGF0YSBzbyB0aGV5IGRvIG5vdCBpbnRyb2R1Y2Ugc3VjaCBvYmplY3Rz
LjxvOnA+PC9vOnA+PC9wcmU+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDtt
YXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0
O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+SXQg
aXMgbmVpdGhlciBhIHRvcCBsZXZlbCBzcGxpdCwgYXMgaXMgdGhlIGNhc2Ugd2l0aCBleGlzdGlu
ZyBJRVRGPG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPm1v
ZGVscyw8bzpwPjwvbzpwPjwvcHJlPg0KPC9ibG9ja3F1b3RlPg0KPHByZSBzdHlsZT0iYmFja2dy
b3VuZDp3aGl0ZSI+W1h1ZmVuZ10gV2UgY291bGQgbm90IGRvIHRvcCBsZXZlbCBzcGxpdCBiZWNh
dXNlIHRoZSBiYXNlIEkyUlM8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3Vu
ZDp3aGl0ZSI+bmV0d29yazxvOnA+PC9vOnA+PC9wcmU+DQo8L2Jsb2NrcXVvdGU+DQo8cHJlIHN0
eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj50b3BvbG9neSBtb2RlbDxvOnA+PC9vOnA+PC9wcmU+DQo8
cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj4oPGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRm
Lm9yZy9odG1sL2RyYWZ0LWlldGYtaTJycy15YW5nLW5ldHdvcmstdG9wbyI+PHNwYW4gc3R5bGU9
ImNvbG9yOnB1cnBsZSI+aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtaTJy
cy15YW5nLW5ldHdvcmstdG9wbzwvc3Bhbj48L2E+LTxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0
eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj4xMikgdGhhdCB3ZSBhdWdtZW50IGRvZXMgbm90IGhhdmUg
dGhlIHRvcC1sZXZlbCBzcGxpdCAoZm9yIGl0cyBvd248bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBz
dHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+cmVhc29ucykuPG86cD48L286cD48L3ByZT4NCjxibG9j
a3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGJs
b2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8
cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5ub3IgZG8gdGhleSBmb2xsb3cgdGhlIE9wZW5D
b25maWcgc3R5bGUgb2Ygc3BsaXR0aW5nIGNvbmZpZyBhbmQ8bzpwPjwvbzpwPjwvcHJlPg0KPHBy
ZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+c3RhdGUgdW5kZXIgZWFjaCByZWxldmFudCBsZWFm
LDxvOnA+PC9vOnA+PC9wcmU+DQo8L2Jsb2NrcXVvdGU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5k
OndoaXRlIj5bWHVmZW5nXSBUaGUgcGF0dGVybiBpcyBjb25zaXN0ZW50IHdpdGggdGhpcyBzdHls
ZSBpbiBwcmluY2lwbGUsPG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6
d2hpdGUiPndpdGggc29tZTxvOnA+PC9vOnA+PC9wcmU+DQo8L2Jsb2NrcXVvdGU+DQo8cHJlIHN0
eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5hZGp1c3RtZW50cyB0byBmaXQgdG8gb3VyIG11bHRpcGxl
IGxldmVscyBvZiBoaWVyYXJjaHkuPG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tn
cm91bmQ6d2hpdGUiPlRoaXMgaXMgZWZmZWN0aXZlbHkgYSBuZXcgZm9ydGggc3R5bGUgb2YgWUFO
RyBtb2RlbHMgdGhhdCBpcyBub3Q8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dy
b3VuZDp3aGl0ZSI+Y29uc2lzdGVudCB3aXRoIGFueSBvZiB0aGUgdGhyZWUgZXhpc3Rpbmcgc3R5
bGVzLCBpLmUuOjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRl
Ij4mbmJzcDsmbmJzcDsgLSBDdXJyZW50IElFVEYgY29uZmlnL3N0YXRlIHNwbGl0IG1vZGVsIHN0
eWxlPG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPiZuYnNw
OyZuYnNwOyAtIE5NREEgY29tYmluZWQgY29uZmlnL3N0YXRlIHRyZWU8bzpwPjwvbzpwPjwvcHJl
Pg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+Jm5ic3A7Jm5ic3A7IC0gT3BlbkNvbmZp
ZyBzcGxpdCBjb25maWcvc3RhdGUgY29udGFpbmVycyBpbW1lZGlhdGVseSBhYm92ZSB0aGU8bzpw
PjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+Y29uZmlnIHRydWUg
bGVhdmVzLjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj4m
bmJzcDs8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+VG9v
bGluZyB0aGF0IGl0IGRlc2lnbmVkIHRvIHdvcmsgd2l0aCBPcGVuQ29uZmlnIG1vZGVscyB3aWxs
IG5lZWQ8bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+Y3Vz
dG9taXphdGlvbiB0byB3b3JrIHdpdGggdGhlc2UgVEUgbW9kZWxzIGJlY2F1c2UgdGhlIGNvbmZp
Zy9zdGF0ZTxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj5j
b250YWluZXJzIHdpbGwgbm90IGJlIHdoZXJlIHRoZSB0b29saW5nIGV4cGVjdHMgdGhlbSB0byBi
ZS48bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+Jm5ic3A7
PG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPlRoYW5rcyw8
bzpwPjwvbzpwPjwvcHJlPg0KPHByZSBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+Um9iPG86cD48
L286cD48L3ByZT4NCjwvYmxvY2txdW90ZT4NCjwvYmxvY2txdW90ZT4NCjxwcmUgc3R5bGU9ImJh
Y2tncm91bmQ6d2hpdGUiPiZuYnNwOzxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJiYWNr
Z3JvdW5kOndoaXRlIj4uPG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQ6
d2hpdGUiPiZuYnNwOzxvOnA+PC9vOnA+PC9wcmU+DQo8L2Jsb2NrcXVvdGU+DQo8L2Jsb2NrcXVv
dGU+DQo8cHJlIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj4mbmJzcDs8bzpwPjwvbzpwPjwvcHJl
Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJiYWNr
Z3JvdW5kOndoaXRlIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Js
b2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6
d2hpdGUiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9i
bG9ja3F1b3RlPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpw
PjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+TWFoZXNoIEpldGhhbmFu
ZGFuaTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PGEgaHJlZj0ibWFpbHRvOm1qZXRoYW5hbmRhbmlAZ21haWwuY29tIj5tamV0aGFuYW5kYW5pQGdt
YWlsLmNvbTwvYT48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9k
eT4NCjwvaHRtbD4NCg==

--_000_BN3PR0201MB0867067D89B713E9D212C841F1AC0BN3PR0201MB0867_--


From nobody Wed Jul 12 20:35:12 2017
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 838761317BD for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 20:35:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 w3Rj6YZIcEYg for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 20:35:10 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [68.183.62.69]) (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 780341300BC for <ietf@ietf.org>; Wed, 12 Jul 2017 20:35:10 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QGMTMI4AWW00443W@mauve.mrochek.com> for ietf@ietf.org; Wed, 12 Jul 2017 20:33:32 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=us-ascii; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QGGZN1ZVAO0000D4@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 12 Jul 2017 20:33:29 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Cc: ietf@ietf.org
Message-id: <01QGMTMGLEO40000D4@mauve.mrochek.com>
Date: Wed, 12 Jul 2017 20:31:37 -0700 (PDT)
Subject: Re: meeting ietf-legacy ssid
In-reply-to: "Your message dated Wed, 12 Jul 2017 13:30:03 -0700" <b96df1c5-7b07-de1a-a78f-0e8a4c2ac6b7@dcrocker.net>
References: <m2eftmwl0l.wl-randy@psg.com> <b96df1c5-7b07-de1a-a78f-0e8a4c2ac6b7@dcrocker.net>
To: Dave Crocker <dhc@dcrocker.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Pr-2A9ca1FF-G2C3HzMrgzkoDxQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jul 2017 03:35:11 -0000

> On 7/11/2017 5:34 PM, Randy Bush wrote:
> >    o don't care as their threat model sees runnin' nekkid over the air as
> >      not a significant additional weakness, or
> >
> >    o believe that they are using sufficient encryption at higher layers
> >      to meet their needs, or


> Given that it is likely that at least one of the 1200 open-participation
> IETF meeting attendees -- all of whom have access to the WiFi password
> -- sometimes indulges in bad actor behavior, then it might be worth
> clarifying exactly what the incremental benefit is, in having WiFi
> encryption, if one is already using TLS liberally.

> (For extra credit, it would be interesting to see where this benefit is
> already documented on the net.)

This occurred to me too. There was another response that actually seemed to
indicate that there was incremental benefit even when using a VPN tunnel
solution. I'd like to hear about the benefits in that case as well.

				Ned


From nobody Wed Jul 12 20:55:49 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 053821317BD for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 20:55:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 9Sr9g04ueXbJ for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 20:55:47 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 C07621300BC for <ietf@ietf.org>; Wed, 12 Jul 2017 20:55:47 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dVVEA-0001NY-5W; Thu, 13 Jul 2017 03:55:46 +0000
Date: Thu, 13 Jul 2017 05:55:45 +0200
Message-ID: <m27ezdt2gu.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: ned+ietf@mauve.mrochek.com
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: meeting ietf-legacy ssid
In-Reply-To: <01QGMTMGLEO40000D4@mauve.mrochek.com>
References: <m2eftmwl0l.wl-randy@psg.com> <b96df1c5-7b07-de1a-a78f-0e8a4c2ac6b7@dcrocker.net> <01QGMTMGLEO40000D4@mauve.mrochek.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ubqnmhVO9t6jFZEaBo9KYxAqV1g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jul 2017 03:55:49 -0000

> This occurred to me too. There was another response that actually
> seemed to indicate that there was incremental benefit even when using
> a VPN tunnel solution. I'd like to hear about the benefits in that
> case as well.

defense in depth.  you do what you can on every link and layer.

and that ain't good enough.  had a raspberry pi pwned last night,
within a short time of it being on the wild net.  no, we have not
had time to RE yet.

randy


From nobody Wed Jul 12 22:30:18 2017
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 111AE1317DD for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 22:30:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_06_12=1.543, SPF_PASS=-0.001, 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 u9i-DEmvP3IA for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 22:30:16 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B10D1131807 for <ietf@ietf.org>; Wed, 12 Jul 2017 22:30:15 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [89.248.140.15]) by relay.sandelman.ca (Postfix) with ESMTPS id 07F511F942; Thu, 13 Jul 2017 05:30:12 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 8F7B01416; Wed, 12 Jul 2017 15:12:03 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: vaibhav singh <vaibhavsinghacads@gmail.com>
cc: ietf@ietf.org
Subject: Re: Need for secured email delegation workflow
In-reply-to: <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com>
References: <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com>
Comments: In-reply-to vaibhav singh <vaibhavsinghacads@gmail.com> message dated "Wed, 12 Jul 2017 12:33:58 +0530."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 12 Jul 2017 15:12:03 -0400
Message-ID: <28827.1499886723@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/chiIwNJMIBid4nB-4IEzk4E5nJM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jul 2017 05:30:17 -0000

--=-=-=
Content-Type: text/plain


vaibhav singh <vaibhavsinghacads@gmail.com> wrote:
    > First of all, I am kind of new and still learning how email
    > infrastructure fits in, so please feel free to highlight any glaring
    > issues with my logic.

    > I was working on implementing Email Delegation for my email server, and
    > felt a need to highlight a couple of things.

    > 1.) I could not find a place where this workflow is outlined. It seems
    > like everyone, from Microsoft to Google, have an implementation for
    > email delegation, and they are all kind of doing their own thing.

I think that when you say "email delegation", you mean where a manager
(or other person) authorizes their "PA" (personal assistant, formerly known
as "secretary") to send email on their behalf.  Back in the days of BNR COCOS
it was very common thing for middle management, but even in those dark days
of mainframe based email, it was usually accomplished by having the PA log in
with the manager's email.

It's good that microsoft(outlook) and google(gmail) have realized that
sharing passwords is a dumb thing.  I think that in the walled gardens of
those systems, that the email delegation is accomplished entirely within
their MUA/MTA.

    > 2.) As I could not find any RFC/Internet Draft covering this flow, I
    > could, potentially, create a really bad email delegation implementation
    > in which I could allow potentially anyone to send mails on behalf of
    > anyone, and I will still be, say, RFC-2822 compatible (I may be

RFC2822 (and 822 before it, and the one for that) always let anyone send any
email claiming to be from anyway.  That was both a strength ("permissionless
innovation"), and led to our spam disaster.  So as others in this thread
have mentioned, we have SPF to give clues as to which IP addresses are
authorized to speak authoritative for a domain, and DKIM to make sure that
the headers are authentic (and optionally body). Neither provides for content
signing that is reachable by end users at this time.
I don't think you are looking for SPF or DKIM, unless you are trying
to seperate the PA and the manager into different (submission) mail systems.

All of this is MTA to MTA protocol, not MUA to MTA.

    > incorrect here, but I could not really find any place which would
    > restrict a user from sending an email on someone's behalf, by editing
    > the "Sender" header before sending an IMAP request.)

Since you speak about IMAP, you are clearly not in the MTA business, but
I suspect in the MUA side of things.  Maybe I'm wrong and you are building
IMAP servers.  I didn't think that IMAP included email submission, but I'm
sure I'm not up to speed... (30 years since I wrote that MTA for AmigaOS...)
So let me speak about email submission protocol (rfc4409) and you can
substitute IMAP if that is in fact appropriate.

It seems to me that a mail server that has an authorized user SHOULD force
the SMTP From (aka "Sender") to the authorized user.  Perhaps it MAY also
force the body From: to a specific value, but I haven't encountered an
open source one that does.  It seems that you are asking how a MUA could
indicate (and provide proof) that it is authorized to set the From:
order Sender: to another value.  (I really think, btw, you want to set
the From: to the manager, and leave the Sender: as the PA)

This seems like it might be the space for a SAML assertion.
I believe that many IMAP servers use small subsets of SAML to provide mailbox
ACLs, and it would fit right in there.  I suspect that there is space for
an RFC about how to do this in a standard way.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJZZnSDAAoJEJVM4Vb9/EKQhpIH/jao/uGXrs7/ELbREzeQXyga
kfyBzEKEna6G8aHF4IPcINYEPJjp1e1t7B5Ri7RE1FcEwkf5yZ08Gp2NTLsdBgKf
7cY+D4s7YCzy2RVCm0EtzDeIUsU9bRKbe6A/1/Bcyfn/hz481NqWY4/nEtDZ37L4
8EdHxPDole1LOWgmyXU09NAveNGShRxKamfmx8xE7tVYsGi4kDaJhjZuiIXfn7ON
opOTTfM4S6nkHlwGtxzJOaZTsgpNY8Kl6hgzbxVL8zUU5ab517+0OpgyrnPwNPi5
I04hHK6tij3u8VkWetkiYOugCvAGZ0zbswQ0WMLLIJHZvrxbUyrHvKBDdzZGFpk=
=7f37
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Jul 12 23:08:43 2017
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24966129AD0 for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 23:08:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 jbo51Tg74HzS for <ietf@ietfa.amsl.com>; Wed, 12 Jul 2017 23:08:39 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 D2906120227 for <ietf@ietf.org>; Wed, 12 Jul 2017 23:08:39 -0700 (PDT)
Received: from mb.local (c-73-202-177-209.hsd1.ca.comcast.net [73.202.177.209]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id v6D68Ksp045070 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Thu, 13 Jul 2017 06:08:37 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host c-73-202-177-209.hsd1.ca.comcast.net [73.202.177.209] claimed to be mb.local
Subject: Re: meeting ietf-legacy ssid
To: Dave Crocker <dhc@dcrocker.net>, ietf@ietf.org
References: <m2eftmwl0l.wl-randy@psg.com> <b96df1c5-7b07-de1a-a78f-0e8a4c2ac6b7@dcrocker.net>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <d25b8b21-508c-8928-822b-e4a339349121@bogus.com>
Date: Wed, 12 Jul 2017 23:08:07 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:54.0) Gecko/20100101 Thunderbird/54.0
MIME-Version: 1.0
In-Reply-To: <b96df1c5-7b07-de1a-a78f-0e8a4c2ac6b7@dcrocker.net>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pjCB7fCGrI2CMTXK9iGAqlCKg9kDpaOHB"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/szCSYfMxmh6by7iiWY0oQvvW338>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jul 2017 06:08:41 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--pjCB7fCGrI2CMTXK9iGAqlCKg9kDpaOHB
Content-Type: multipart/mixed; boundary="HWqtrKCDU3bc8IgoEwehcgHPv420rE4mN";
 protected-headers="v1"
From: joel jaeggli <joelja@bogus.com>
To: Dave Crocker <dhc@dcrocker.net>, ietf@ietf.org
Message-ID: <d25b8b21-508c-8928-822b-e4a339349121@bogus.com>
Subject: Re: meeting ietf-legacy ssid
References: <m2eftmwl0l.wl-randy@psg.com>
 <b96df1c5-7b07-de1a-a78f-0e8a4c2ac6b7@dcrocker.net>
In-Reply-To: <b96df1c5-7b07-de1a-a78f-0e8a4c2ac6b7@dcrocker.net>

--HWqtrKCDU3bc8IgoEwehcgHPv420rE4mN
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 7/12/17 1:30 PM, Dave Crocker wrote:
> On 7/11/2017 5:34 PM, Randy Bush wrote:
>>    o don't care as their threat model sees runnin' nekkid over the air=
 as
>>      not a significant additional weakness, or
>>
>>    o believe that they are using sufficient encryption at higher layer=
s
>>      to meet their needs, or
>=20
>=20
> Given that it is likely that at least one of the 1200 open-participatio=
n
> IETF meeting attendees -- all of whom have access to the WiFi password
> -- sometimes indulges in bad actor behavior, then it might be worth
> clarifying exactly what the incremental benefit is, in having WiFi
> encryption, if one is already using TLS liberally.

wpa2 enterprise provides forward security, merely using the same
username and password doesn't provide you with the ability to snoop
other traffic.

> (For extra credit, it would be interesting to see where this benefit is=

> already documented on the net.)
>=20
> d/
>=20



--HWqtrKCDU3bc8IgoEwehcgHPv420rE4mN--

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

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAllnDk8ACgkQ8AA1q7Z/VrJ+5QCfQTJJeTcLSsOkdLkr1ikLoxLk
7cYAniFQ1m91erfIq3VIBDxgUsftPktk
=6me9
-----END PGP SIGNATURE-----

--pjCB7fCGrI2CMTXK9iGAqlCKg9kDpaOHB--


From nobody Thu Jul 13 01:09:07 2017
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B62813184E for <ietf@ietfa.amsl.com>; Thu, 13 Jul 2017 01:08:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 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_MED=-2.3, RP_MATCHES_RCVD=-0.001, 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=ecs.soton.ac.uk
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 4xZiQAYEuUff for <ietf@ietfa.amsl.com>; Thu, 13 Jul 2017 01:08:52 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4CF013146E for <ietf@ietf.org>; Thu, 13 Jul 2017 01:08:50 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6D87l0c011688; Thu, 13 Jul 2017 09:07:52 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v6D87l0c011688
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1499933273; bh=SlYfD5VejhhGdUxCaJfWKFfOg04=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=TXZ+A6Q2IFYgqaZT8RuyQzlXSgf5N6g+M4FBxlpjwTLz9td2oL/3kzjUD57TUAsjk /ZVOsELEx53+NBcH13TZePf7st/NSn2CE1opq3TzxpAdimXqehJTLpfl4zEFgKmfVI zwR/LEgDI7oAA618xsk7sYgOf3IYg23Pcgf5F624=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id y6C97g2564602063Gp ret-id none; Thu, 13 Jul 2017 09:07:53 +0100
Received: from [10.1.11.157] (firewall-lho-ext.management.janet.ac.uk [194.82.140.195]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6D87Yjw032424 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 Jul 2017 09:07:34 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: meeting ietf-legacy ssid
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <m2eftlvgnh.wl-randy@psg.com>
Date: Thu, 13 Jul 2017 09:07:35 +0100
Cc: "Livingood, Jason" <Jason_Livingood@comcast.com>, IETF Rinse Repeat <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|56aef81da44fd6e97524964c213cb5cby6C97g03tjc|ecs.soton.ac.uk|6AD4A518-D3C2-4F82-B54F-7BDE3EA9F2D0@ecs.soton.ac.uk>
References: <m2eftmwl0l.wl-randy@psg.com> <EC1FFD9E-F9FA-4780-B279-A71AB93A57FD@shrubbery.net> <m2bmoqvyoj.wl-randy@psg.com> <7D401DCF-C3DB-49AB-BFA9-7CFF3914C661@cable.comcast.com> <m2eftlvgnh.wl-randy@psg.com> <6AD4A518-D3C2-4F82-B54F-7BDE3EA9F2D0@ecs.soton.ac.uk>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3273)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=y6C97g256460206300; tid=y6C97g2564602063Gp; client=relay,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v6D87l0c011688
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/__8MChiEqIP3dCNkWqfYcSC2lL0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jul 2017 08:08:54 -0000

> On 12 Jul 2017, at 16:06, Randy Bush <randy@psg.com> wrote:
>=20
>>> Why not just turn it off and see what happens?
>> because the noc thinks of the attendees as those strange critters
>> called "customers."  this creates implications for service =
continuity.
>> [JL] Fair enough. How about any traffic to that SSID pops a user
>> message that says this is an old SSID and is being phased out, please
>> change to another one now, etc. The CAPPORT WG may have some running
>> code they can use to try this out. And as others have said, I would
>> bet that most prior attendees have many IETF SSIDs in their config =
and
>> turning one off will just result in the OS picking a different one on
>> the list.
>=20
> ripe meeting solution, e.g. renaming the ietf-legacy ssid to
> ietf-legacy##, for every meeting.

Nice idea; would force people to consciously choose it, and see the =
alternatives, rather than keep using it by default.

> from the discussion so far, it is not clear that there are no folk
> depending on legacy; excuse the double negative.

Tim


From nobody Thu Jul 13 06:52:51 2017
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1B1D130154 for <ietf@ietfa.amsl.com>; Thu, 13 Jul 2017 06:52:49 -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, 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 51xJTF1z9-w6 for <ietf@ietfa.amsl.com>; Thu, 13 Jul 2017 06:52:48 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 1FF01129B61 for <ietf@ietf.org>; Thu, 13 Jul 2017 06:52:47 -0700 (PDT)
Received: from [192.168.1.34] ([217.91.35.233]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0M0Ppl-1do8nI0fHB-00ucU5; Thu, 13 Jul 2017 15:52:29 +0200
Subject: Re: meeting ietf-legacy ssid
To: John Levine <johnl@taugh.com>, ietf@ietf.org
References: <20170712025506.1358.qmail@ary.lan>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <152a084b-19e1-426e-ff02-73999cbc61de@gmx.de>
Date: Thu, 13 Jul 2017 15:52:28 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <20170712025506.1358.qmail@ary.lan>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:I+wlGpGYrFod/Y0Ti5V0Xeen7USpJu5VcqMqThzydgegXilPhdl x09vQLANwfHT1wKu1POlxjrUfVzb0GvIrTBCxZffOxiaXhmGWv2U+cwbUVCOhw9IOIp1VzL EBYVzQwKK/SMN4I3BUtJ/Z9gi76q4flyNuzt8rd+kE5srEin1Pi6konKP3aIPnH0Kzw7nQa f5sXZ9tzhwvNHsJ1y0vbg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:1tT87/TIzUs=:xaAD3DtuccCTpiYOr2r8Ud 5feBpAzx6e2Hk1WBYpTawMS2LnLteGKyv+FrBkL5wzcOJkfjuFbcdHEUgXrQSDh5+tsI0KzVL oxex7zPKQE4ERLuFS3/yD9GAPhHUg69+fGQHUMoyRB8WraNtkE8I+LL9rhNgHcIB60K5xK0Ee mbOoR+R7sq7Udrj+9FdJF6qKwoVJtZ3hzqGVL0D/FodpIp5I/PPtFf5X2dCyv4vW5ETbknBtZ 38n0cd3efRxk2/94TxK+f6aBD9WzfQCuwsWxGZk+dFief2UI3XbF4Wx7YB9TZVbsK7/fNASp4 fv2IqIYqdd54fs5zeKhE3FmhguierW3x6VRd4G3kfQ2p1/vNbmPWh3jR8B8s538+YPBOtEoIK /MOGwBY5FoXH2J3GcmzJGjJik9TQJm63ts771h70LttZSm78XBoXRfpumsFXqCf1++YlJhu+y uA1htT799f5IcZEfWhwI2KFcHe8ABYmz+Pf5KihemTraxFoV/990Mht2zf4T6StxFCKKxdwnR haedwsuMPXBVD8/JCA+KH0Mwly2z6PJGrqgMVnTZJ/PnRwCEXAjydvFmPR9Psrxk2CGvyo0hv LRYejg0F1neOCAk4XjaOTRhOcwU21D/mTMI8ZvTXsGmMDE701Gy3NcBu5jcBfcrvaD6rKqiTn PswDE/Ygl29t3g6dSg+BnHjkH+mT52UeR1fI5rDnBNcWCFOfBKnlLrJheqDm9WRDtNJcBFLG/ 15lY/PIVFjpuoOiVg614t5TtD3l7RMuoHZCgmGcYTVltl70OQNQZYlfRsv0cgjDDpF381SOQT pWCcFRyjz72oZvrZlPBL+BlUuQ3yRPlV1QiSiS5SR3JWim0DaI=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4Sn7MonstQgS3gzITGbHilmSFSA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jul 2017 13:52:50 -0000

On 2017-07-12 04:55, John Levine wrote:
> In article <BEF20349-0893-4450-8C23-83DA4F175A7B@mnot.net> you write:
>> Perhaps it's non-IETF people using what looks to be very high-quality, free wifi?
> 
> We tend to fill up whatever hotel we're in do I doubt that's it.
> ...

...overheard during breakfast at the Toronto IETF meeting: "there seems 
to be a hotel nearby called 'IETF' which has a free high-speed WLAN".

Best regards, Julian


From nobody Thu Jul 13 06:53:36 2017
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54C69131A8E for <ietf@ietfa.amsl.com>; Thu, 13 Jul 2017 06:53:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.308
X-Spam-Level: 
X-Spam-Status: No, score=-0.308 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_03_06=1.592, SPF_PASS=-0.001, 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 dEWhJH2hApc7 for <ietf@ietfa.amsl.com>; Thu, 13 Jul 2017 06:53:19 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97A50131A8C for <ietf@ietf.org>; Thu, 13 Jul 2017 06:53:18 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [IPv6:2001:0:53aa:64c:14ec:3b3b:a18e:b3f3]) by relay.sandelman.ca (Postfix) with ESMTPS id AE0021F906 for <ietf@ietf.org>; Thu, 13 Jul 2017 13:53:14 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 4C3F415DB; Thu, 13 Jul 2017 05:38:09 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
Subject: Re: meeting ietf-legacy ssid
In-reply-to: <b96df1c5-7b07-de1a-a78f-0e8a4c2ac6b7@dcrocker.net>
References: <m2eftmwl0l.wl-randy@psg.com> <b96df1c5-7b07-de1a-a78f-0e8a4c2ac6b7@dcrocker.net>
Comments: In-reply-to Dave Crocker <dhc@dcrocker.net> message dated "Wed, 12 Jul 2017 13:30:03 -0700."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 13 Jul 2017 11:38:09 +0200
Message-ID: <17614.1499938689@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Kg2M7nZ56C5585OGmSyy0dxnZ-E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jul 2017 13:53:20 -0000

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable


Dave Crocker <dhc@dcrocker.net> wrote:
    >> o don't care as their threat model sees runnin' nekkid over the air =
as
    >> not a significant additional weakness, or
    >>=20
    >> o believe that they are using sufficient encryption at higher layers
    >> to meet their needs, or

    > Given that it is likely that at least one of the 1200
    > open-participation IETF meeting attendees -- all of whom have access =
to
    > the WiFi password -- sometimes indulges in bad actor behavior, then it
    > might be worth clarifying exactly what the incremental benefit is, in
    > having WiFi encryption, if one is already using TLS liberally.

My understanding is that our use of the EAP-TLS method, even with unverified
certificates, each attendee's device winds up generating a different "WEP"
key at the L2 level.  This means that attendees can not sniff each other's
traffic.
Without this, simple TCP RST attacks are trivial on TLS connections.

I don't know if we are enabling client isolation at the wifi level.
If we aren't then one could do ARP or RA impersonation, and my laptop could
convince your laptop to use me as a router, giving me access to your
unencrypted traffic.

Having said all that, I find wifi security to be generally a waste of time.

=2D-=20
]               Never tell me the odds!                 | ipv6 mesh network=
s [=20
]   Michael Richardson, Sandelman Software Works        | network architect=
  [=20
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [=20
=09

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJZZz+BAAoJEJVM4Vb9/EKQvs4H/iugzbVJFSCcN6PLj+aRSvsy
0+qq9ie9A2VwcA5t78Eq0bUqgYOeeliWMUz8H2LEFwBhOyewENb8oJwOIlavvyPz
XdM1UuePB2ZA3hY3trlqmHGQMjVJkLSpZYJOk55vXbg07ny7qWXkopSKLs3dCV3n
cxz8VufWzSIY02pOkja9NXhZ2/duB4N8j3+STlhBl9ouw7TVjzB12gJQp77bpmSj
Kqz5YNOlTvITycMoD/a8Sm+lz9PFTtc80IyfqmjbkKAdp15qJW/U9mhajylAfpjm
C9pn3Vr6ssjeREnYg2mkb9bGVJKazubuI3i8eU2U1q4+w3kdCE5jaXfyHQqd9e0=
=no6D
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Jul 13 06:59:53 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59146129AD3 for <ietf@ietfa.amsl.com>; Thu, 13 Jul 2017 06:59:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.398
X-Spam-Level: 
X-Spam-Status: No, score=-2.398 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, 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 cAkGTJNqn9Zy for <ietf@ietfa.amsl.com>; Thu, 13 Jul 2017 06:59:50 -0700 (PDT)
Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (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 567571200ED for <ietf@ietf.org>; Thu, 13 Jul 2017 06:59:50 -0700 (PDT)
Received: by mail-lf0-x22c.google.com with SMTP id z78so37410637lff.0 for <ietf@ietf.org>; Thu, 13 Jul 2017 06:59:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=WmTbQAM18lRSAP8bCLeGM/aUPt1SaCksJGSYX5keecE=; b=Yw9SBvZFEY8uoS2zmz2Ma+3kEOofQmZc7FJaa0PI1+xksWModQAE8A8fDut76w6PZU ME3zQAVi/Qg6/1qnsK+7u7hJ0z7FlxpRRoocF4pEJKozgw8TUhRSlYRe3qRneMad09vq 91INTuBGkyl8Or8/Gznq4V4h6pjFX3JN6EBoEWWWeyORuR6ivwbAeW2rWO2fFYsrFq+A gmZAvZN3oFr36jGPYqCALQuQhXbTThb+0JeU+ASDbgWkRmqkOppzXq9OIYYpVMMr3xZo TaF3Wu+97Xr57mrzJwFnvntMNl9NuYa4hzsyDC+QP1vi/ixmdIQ6G8lDAq9rAVVGFEin 6oqw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=WmTbQAM18lRSAP8bCLeGM/aUPt1SaCksJGSYX5keecE=; b=HR6xy752faQuZ9TfkZ4cJxH6cJZG/ym9/xvSjy4I2wwlR+1SSafn/GvZmiBxsK8uBV +9VCZ47WExFur9YnN65XYXKKhZoPmylRpA0HELsZWEMGf85L98+xK77+QrFYKuN0lubQ oD7Uo7TX3aEOY55EGAlDA9rtfgdjPz9bylRwLyv7wwjPTcweeEi02ooO798n/Q7bVh33 zqO+w+BiQ+P/aJawZqjpgqhyTBZNA2PPTgrMslZ2v0+oxVdRKmc6smfNDD3phglYAifi KaxAaqR4jdDXf3xWdvkWWC0TFsOqQ485HA3++uK2I3HUAPE5NroqtAwZ+0adxZK8SHgM 71cQ==
X-Gm-Message-State: AIVw113ORQRniF32x4luu0fGL4t+HekTNSrdcR0NkWgPEy1gBXu6OgiA nUcah2HNar2X6tdj+FZQESSa+QEQRA==
X-Received: by 10.25.233.219 with SMTP id j88mr1420187lfk.64.1499954388686; Thu, 13 Jul 2017 06:59:48 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.25.181.214 with HTTP; Thu, 13 Jul 2017 06:59:47 -0700 (PDT)
In-Reply-To: <152a084b-19e1-426e-ff02-73999cbc61de@gmx.de>
References: <20170712025506.1358.qmail@ary.lan> <152a084b-19e1-426e-ff02-73999cbc61de@gmx.de>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 13 Jul 2017 09:59:47 -0400
X-Google-Sender-Auth: c1TjNOAHHveLRj1nbQaBm4Fw5nM
Message-ID: <CAMm+LwhzuYrujsHcVKUKL2KFCkhTxa1Vc9Aq9Hq0YZupmJ3GqA@mail.gmail.com>
Subject: Re: meeting ietf-legacy ssid
To: Julian Reschke <julian.reschke@gmx.de>
Cc: John Levine <johnl@taugh.com>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a1149776a845fd505543358da"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BWil-T1tmoEoOHhU0qkPLkD-WMY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jul 2017 13:59:52 -0000

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

On Thu, Jul 13, 2017 at 9:52 AM, Julian Reschke <julian.reschke@gmx.de>
wrote:

> On 2017-07-12 04:55, John Levine wrote:
>
>> In article <BEF20349-0893-4450-8C23-83DA4F175A7B@mnot.net> you write:
>>
>>> Perhaps it's non-IETF people using what looks to be very high-quality,
>>> free wifi?
>>>
>>
>> We tend to fill up whatever hotel we're in do I doubt that's it.
>> ...
>>
>
> ...overheard during breakfast at the Toronto IETF meeting: "there seems t=
o
> be a hotel nearby called 'IETF' which has a free high-speed WLAN".
>
> Best regards, Julian
>

=E2=80=8BAt another meeting, some years back, before the iphone etc. "Is th=
ere some
laptop computer sales convention"

I am always amazed that the WiFi has enough bandwidth. Though I suspect we
are mostly using Web and mail rather than streaming video.

Where is the Game of Thrones fix on Sunday?=E2=80=8B

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Ju=
l 13, 2017 at 9:52 AM, Julian Reschke <span dir=3D"ltr">&lt;<a href=3D"mail=
to:julian.reschke@gmx.de" target=3D"_blank">julian.reschke@gmx.de</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"><span class=3D"">On 2017-07-=
12 04:55, John Levine wrote:<br>
</span><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><span class=3D"">
In article &lt;<a href=3D"mailto:BEF20349-0893-4450-8C23-83DA4F175A7B@mnot.=
net" target=3D"_blank">BEF20349-0893-4450-8C23-83DA4<wbr>F175A7B@mnot.net</=
a>&gt; you write:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Perhaps it&#39;s non-IETF people using what looks to be very high-quality, =
free wifi?<br>
</blockquote>
<br>
We tend to fill up whatever hotel we&#39;re in do I doubt that&#39;s it.<br=
></span>
...<br>
</blockquote>
<br>
...overheard during breakfast at the Toronto IETF meeting: &quot;there seem=
s to be a hotel nearby called &#39;IETF&#39; which has a free high-speed WL=
AN&quot;.<br>
<br>
Best regards, Julian<br></blockquote><div><br></div><div class=3D"gmail_def=
ault" style=3D"font-size:small">=E2=80=8BAt another meeting, some years bac=
k, before the iphone etc. &quot;Is there some laptop computer sales convent=
ion&quot;</div><div class=3D"gmail_default" style=3D"font-size:small"><br><=
/div><div class=3D"gmail_default" style=3D"font-size:small">I am always ama=
zed that the WiFi has enough bandwidth. Though I suspect we are mostly usin=
g Web and mail rather than streaming video.</div><div class=3D"gmail_defaul=
t" style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=
=3D"font-size:small">Where is the Game of Thrones fix on Sunday?=E2=80=8B</=
div></div><br></div></div>

--001a1149776a845fd505543358da--


From nobody Thu Jul 13 15:54:54 2017
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94FDB129B36 for <ietf@ietfa.amsl.com>; Thu, 13 Jul 2017 15:54:52 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, 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=dcrocker.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 yFhAfu0ODv-c for <ietf@ietfa.amsl.com>; Thu, 13 Jul 2017 15:54:51 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 831FE127444 for <ietf@ietf.org>; Thu, 13 Jul 2017 15:54:51 -0700 (PDT)
Received: from [10.35.254.222] (sccc-208-115-86-69.smartcity.com [208.115.86.69] (may be forged)) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v6DMt3CN026324 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 13 Jul 2017 15:55:03 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1499986503; bh=XMiXplWaNneGnA14F1lj9xuimGZF2hXhQjw1d+TC9eM=; h=Reply-To:Subject:To:References:From:Date:In-Reply-To:From; b=a2AWepkkRHxsgXsuQd0p4dJuzj0PVtYw6Fsq9kzaoVGuRTOF5fUC2YPRV/VtjXOVh 6t7nwMXDCDvcFZR8m5AhsJTckNo8tfF4TH8ejxKJagZlPiFg/aHcYfuLm3m5/uwwn3 CFXjjNAESUidcDqNhOOvmwMQiqAcc6lZzSelWvVM=
Reply-To: dcrocker@bbiw.net
Subject: Re: meeting ietf-legacy ssid
To: joel jaeggli <joelja@bogus.com>, ietf@ietf.org
References: <m2eftmwl0l.wl-randy@psg.com> <b96df1c5-7b07-de1a-a78f-0e8a4c2ac6b7@dcrocker.net> <d25b8b21-508c-8928-822b-e4a339349121@bogus.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <2538aba1-01e2-57e6-bb0f-d3e2df3e721f@dcrocker.net>
Date: Thu, 13 Jul 2017 15:54:46 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <d25b8b21-508c-8928-822b-e4a339349121@bogus.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Jra565J5jOooAdJUTadcFF0l_5A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jul 2017 22:54:52 -0000

On 7/12/2017 8:55 PM, Randy Bush wrote:
 > defense in depth.  you do what you can on every link and layer.

The problem with a generic cliche like defense in depth is that there is 
not way to judge what's meaningful and useful and what isn't.  Obviously 
there is defense in depth if I run two anti-virus applications rather 
than only one?  Oh... there isn't?

And the idea that it's best to do what you can at every layer presumably 
means that we need to put checksums back into IPv6?

On the other hand, the basic question of whether one is /positive/ that 
all activity is protected by TLS is worth considering (though such 
coverage was the premise to my original query.)



On 7/12/2017 11:08 PM, joel jaeggli wrote:
> wpa2 enterprise provides forward security, merely using the same
> username and password doesn't provide you with the ability to snoop
> other traffic.

Oh.  So a bad actor having the shared key and being able to wiretap the 
key exchange sequences at the startup of other users doesn't represent a 
threat?  (I'd heard otherwise, but admit to not having researched this 
carefully.)

And only WPA2 is supported on the IETF net(s)?



d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Thu Jul 13 16:51:10 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFE3512ECF0 for <ietf@ietfa.amsl.com>; Thu, 13 Jul 2017 16:51:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.398
X-Spam-Level: 
X-Spam-Status: No, score=-2.398 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, 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 j0rQX2gyd4Gu for <ietf@ietfa.amsl.com>; Thu, 13 Jul 2017 16:51:06 -0700 (PDT)
Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (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 E39D7131795 for <ietf@ietf.org>; Thu, 13 Jul 2017 16:51:05 -0700 (PDT)
Received: by mail-lf0-x22c.google.com with SMTP id h22so45084477lfk.3 for <ietf@ietf.org>; Thu, 13 Jul 2017 16:51:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=EQuIMo360RmwQ9lInhUIMtFyXU/vHsaLQibFa+1N2DQ=; b=MjmJfyBAKGkq4+PPKKLdPemPJdIk3u0iQoOsfziZSC1Pkro76xdsXViJ2hkaQOKbff 6FWCXIZF2LZyP/mknAymsSLx/6Sk8FtYwCZoKhgQV9VL5Gq9123zUoiwv/0W66rgQPrR uRRYaNaYLNB3GRZcgnAbTDWt8nHZUCY7kxlRcyk7CL0tQhLrzSJqWdfcPwMZcVZ+RWkX /jr5XjoOd1tHZugliuTBS2r4r662+wpROSErbZnrlkFADtCCcze6ibz7CaEiUyS5yAa5 LTvMYvSXp1xqIg5WSLLdFktD3CvG9WB31zXmL4YOgqPZBjSLo/GhEfsPbc0Tl+3QC2sz 1D9Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=EQuIMo360RmwQ9lInhUIMtFyXU/vHsaLQibFa+1N2DQ=; b=H033Igx2HlhTYU5vS0kuvb1/yp2hHsbuZC3XCEfVj1ozeYvTHEvsiQpoS60vwH7sor gC+eJ0KLU0Bq0wnh3r+b2WcW2dIoVkG43WSQtVdYyihdQs1WxYPNA7L+DmNEP4Km/ao/ 9F34GdNsvFwpIh8Vn31ctqdB7Ej0ULVpinSXTBDYSKCdMdiwLuuoTpYeeoLqtEUU/eLg Iy0Gu0ByNF/OpMjcfS7ZvJ5nleagmWVNXuhqSInw8NsP/cEppzJZTqpN0Xy/KKRmNsQY YX4YCIEnVpv2WTU7CLkfqY1U/IIrSrEnt3SbA8I/ddHlMbwkPUtmhNCUYuanCUYVc7iB kM/g==
X-Gm-Message-State: AIVw113rogQBqZnhnfPvsQEbCjlzpUa7eWj/GfrOrsXcRLXfmbyf2D2N LfohV3jtHAbu02Cus0iK2yyf2j9cjw==
X-Received: by 10.25.32.21 with SMTP id g21mr2293929lfg.183.1499989864281; Thu, 13 Jul 2017 16:51:04 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.25.181.214 with HTTP; Thu, 13 Jul 2017 16:51:03 -0700 (PDT)
In-Reply-To: <2538aba1-01e2-57e6-bb0f-d3e2df3e721f@dcrocker.net>
References: <m2eftmwl0l.wl-randy@psg.com> <b96df1c5-7b07-de1a-a78f-0e8a4c2ac6b7@dcrocker.net> <d25b8b21-508c-8928-822b-e4a339349121@bogus.com> <2538aba1-01e2-57e6-bb0f-d3e2df3e721f@dcrocker.net>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 13 Jul 2017 19:51:03 -0400
X-Google-Sender-Auth: kFb3IVCs-KW5wql41FiK-aJSKNY
Message-ID: <CAMm+Lwi2YgsG-YH_n8sLma5Y0hZbqGJW3yZQRJjXAG+GFsbT0Q@mail.gmail.com>
Subject: Re: meeting ietf-legacy ssid
To: Dave CROCKER <dcrocker@bbiw.net>
Cc: joel jaeggli <joelja@bogus.com>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a1140228006fe2205543b9b47"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qBH8NCs_Zzyyj0xs6mQiFq65d4s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jul 2017 23:51:08 -0000

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

On Thu, Jul 13, 2017 at 6:54 PM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 7/12/2017 8:55 PM, Randy Bush wrote:
> > defense in depth.  you do what you can on every link and layer.
>
> The problem with a generic cliche like defense in depth is that there is
> not way to judge what's meaningful and useful and what isn't.  Obviously
> there is defense in depth if I run two anti-virus applications rather tha=
n
> only one?  Oh... there isn't?
>
> And the idea that it's best to do what you can at every layer presumably
> means that we need to put checksums back into IPv6?
>
> On the other hand, the basic question of whether one is /positive/ that
> all activity is protected by TLS is worth considering (though such covera=
ge
> was the premise to my original query.)


=E2=80=8BDefense in depth is ambiguous, I agree. But it is not bogus. End t=
o end is
also ambiguous as ideas on where the ends are differ.

For the Mesh protocols, I use a Triple Lock approach. which I have not
finished writing up on. The idea is that we apply crypto at three different
layers to achieve different effects.

1) Transport Layer: Confidentiality gives us protection against traffic
analysis.

2) Session Layer: HTTP Web Service packets are authenticated with keys
negotiated at the application layer. This provides for transaction
isolation (no injection attacks) and authentication.

3) Data Level Signature: For non repudiation.

Although encryption is only mandated for every interaction at the first
layer, it is usually applied at 2 and often required at 3 as well.

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Ju=
l 13, 2017 at 6:54 PM, Dave Crocker <span dir=3D"ltr">&lt;<a href=3D"mailto=
:dhc@dcrocker.net" target=3D"_blank">dhc@dcrocker.net</a>&gt;</span> wrote:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex"><span class=3D"">On 7/12/2017 8:55 PM, R=
andy Bush wrote:<br>
&gt; defense in depth.=C2=A0 you do what you can on every link and layer.<b=
r>
<br></span>
The problem with a generic cliche like defense in depth is that there is no=
t way to judge what&#39;s meaningful and useful and what isn&#39;t.=C2=A0 O=
bviously there is defense in depth if I run two anti-virus applications rat=
her than only one?=C2=A0 Oh... there isn&#39;t?<br>
<br>
And the idea that it&#39;s best to do what you can at every layer presumabl=
y means that we need to put checksums back into IPv6?<br>
<br>
On the other hand, the basic question of whether one is /positive/ that all=
 activity is protected by TLS is worth considering (though such coverage wa=
s the premise to my original query.)</blockquote><div><br></div><div><div c=
lass=3D"gmail_default" style=3D"font-size:small">=E2=80=8BDefense in depth =
is ambiguous, I agree. But it is not bogus. End to end is also ambiguous as=
 ideas on where the ends are differ.</div><div class=3D"gmail_default" styl=
e=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"font-=
size:small">For the Mesh protocols, I use a Triple Lock approach. which I h=
ave not finished writing up on. The idea is that we apply crypto at three d=
ifferent layers to achieve different effects.</div><div class=3D"gmail_defa=
ult" style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=
=3D"font-size:small">1) Transport Layer: Confidentiality gives us protectio=
n against traffic analysis.</div><div class=3D"gmail_default" style=3D"font=
-size:small"><br></div><div class=3D"gmail_default" style=3D"font-size:smal=
l">2) Session Layer: HTTP Web Service packets are authenticated with keys n=
egotiated at the application layer. This provides for transaction isolation=
 (no injection attacks) and authentication.=C2=A0</div><div class=3D"gmail_=
default" style=3D"font-size:small"><br></div><div class=3D"gmail_default" s=
tyle=3D"font-size:small">3) Data Level Signature: For non repudiation.</div=
><div class=3D"gmail_default" style=3D"font-size:small"><br></div><div clas=
s=3D"gmail_default" style=3D"font-size:small">Although encryption is only m=
andated for every interaction at the first layer, it is usually applied at =
2 and often required at 3 as well.</div><div class=3D"gmail_default" style=
=3D"font-size:small"><br></div><br></div><div>=C2=A0</div></div></div></div=
>

--001a1140228006fe2205543b9b47--


From nobody Thu Jul 13 17:08:18 2017
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26F8712F26D for <ietf@ietfa.amsl.com>; Thu, 13 Jul 2017 17:08:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 60WICjwQu89r for <ietf@ietfa.amsl.com>; Thu, 13 Jul 2017 17:08:15 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 A65CB12EC1D for <ietf@ietf.org>; Thu, 13 Jul 2017 17:08:15 -0700 (PDT)
Received: from mbp-4.local (c-73-202-177-209.hsd1.ca.comcast.net [73.202.177.209]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id v6E08CL4053424 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Fri, 14 Jul 2017 00:08:13 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host c-73-202-177-209.hsd1.ca.comcast.net [73.202.177.209] claimed to be mbp-4.local
Subject: Re: meeting ietf-legacy ssid
To: Dave Crocker <dhc@dcrocker.net>, ietf@ietf.org
References: <m2eftmwl0l.wl-randy@psg.com> <b96df1c5-7b07-de1a-a78f-0e8a4c2ac6b7@dcrocker.net> <d25b8b21-508c-8928-822b-e4a339349121@bogus.com> <2538aba1-01e2-57e6-bb0f-d3e2df3e721f@dcrocker.net>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <c10c37a2-929c-77f1-8613-ea8855ec40cf@bogus.com>
Date: Thu, 13 Jul 2017 17:08:07 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <2538aba1-01e2-57e6-bb0f-d3e2df3e721f@dcrocker.net>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7xxrA4IO3f3h6QQw6kgNoDSdxtgak13pU"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nHhwZeKCfFJuCJ3Pz6eNxGkCDow>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jul 2017 00:08:17 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--7xxrA4IO3f3h6QQw6kgNoDSdxtgak13pU
Content-Type: multipart/mixed; boundary="qkfRsTT7IrHhVEhFJ45uanRocSWQ0Fwop";
 protected-headers="v1"
From: joel jaeggli <joelja@bogus.com>
To: Dave Crocker <dhc@dcrocker.net>, ietf@ietf.org
Message-ID: <c10c37a2-929c-77f1-8613-ea8855ec40cf@bogus.com>
Subject: Re: meeting ietf-legacy ssid
References: <m2eftmwl0l.wl-randy@psg.com>
 <b96df1c5-7b07-de1a-a78f-0e8a4c2ac6b7@dcrocker.net>
 <d25b8b21-508c-8928-822b-e4a339349121@bogus.com>
 <2538aba1-01e2-57e6-bb0f-d3e2df3e721f@dcrocker.net>
In-Reply-To: <2538aba1-01e2-57e6-bb0f-d3e2df3e721f@dcrocker.net>

--qkfRsTT7IrHhVEhFJ45uanRocSWQ0Fwop
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US


>
> On 7/12/2017 11:08 PM, joel jaeggli wrote:
>> wpa2 enterprise provides forward security, merely using the same
>> username and password doesn't provide you with the ability to snoop
>> other traffic.
>
> Oh.  So a bad actor having the shared key and being able to wiretap
> the key exchange sequences at the startup of other users doesn't
> represent a threat?  (I'd heard otherwise, but admit to not having
> researched this carefully.)
There's no pre-shared key, there's a cert from a legitimate-looking-ca
that you have to accept on faith the first time. and then the username
and password (ietf / ietf ) which you client caches presumably forever.
The handshake is eap peap or eap ttls so apart from the gratuitious TIFU
issue for most people, the mitm is going to need the cert's private key,
or get you to accept and enroll another cert.

you can examine the cert or grab a profile including it here:

https://802.1x-config.org/?idp=3D137&profile=3D101
> And only WPA2 is supported on the IETF net(s)?
we do 802.1x wpa2 ent with peap or ttls methods.
>
>
>
> d/
>



--qkfRsTT7IrHhVEhFJ45uanRocSWQ0Fwop--

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

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlloC2cACgkQ8AA1q7Z/VrLAYgCeMd3KApVWzWe4L4vHZK8akCYZ
k2MAn2zz+v0lpf00+3Ovj4RmyNB05PrS
=+1N7
-----END PGP SIGNATURE-----

--7xxrA4IO3f3h6QQw6kgNoDSdxtgak13pU--


From nobody Thu Jul 13 19:12:02 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0059A1318A4; Thu, 13 Jul 2017 19:11:54 -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
Subject: Genart last call review of draft-ietf-lamps-rfc5280-i18n-update-02
X-Test-IDTracker: no
X-IETF-IDTracker: 6.56.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149999831392.16399.16155350544896318430@ietfa.amsl.com>
Date: Thu, 13 Jul 2017 19:11:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qREsR2-bZyf2w0eeCJDc6Vsy2Ic>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jul 2017 02:11:54 -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-lamps-rfc5280-i18n-update-??
Reviewer: Joel Halpern
Review Date: 2017-07-13
IETF LC End Date: 2017-07-25
IESG Telechat date: Not scheduled for a telechat

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

Major issues: N/A

Minor issues: N/A

Nits/editorial comments:  N/A



From nobody Thu Jul 13 21:09:00 2017
Return-Path: <vaibhavsinghacads@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8FA213192B for <ietf@ietfa.amsl.com>; Thu, 13 Jul 2017 21:08:58 -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 shZ3x5qcx3oX for <ietf@ietfa.amsl.com>; Thu, 13 Jul 2017 21:08:57 -0700 (PDT)
Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (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 69D48126CC7 for <ietf@ietf.org>; Thu, 13 Jul 2017 21:08:57 -0700 (PDT)
Received: by mail-it0-x22b.google.com with SMTP id k192so12868997ith.1 for <ietf@ietf.org>; Thu, 13 Jul 2017 21:08:57 -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=MnoPRd3D5UcXB7BkQ51CZ5lJR3dFqWgEsy6TBBvlIzY=; b=CdUcnWnWrgcZc1cqVJq4neqcRTakUPPhTKI036bjspVphqaB8OCcJm8KqNWvEGjP+d qMeu7LTNLkNLvlUXQ/in62ko9pVzkifQUYJu1xrBFpPwNIvdVgyKkWQt/3+eGKumlApP E7SVjBdINjSo3HVrs25DCJsrYDPiBynqt43/MI1QO+Lc3VVcRlol7pIBTO06MMWjhZh2 7kZbQGIr9raEkagLXnPPF3aQtbbe0Sqw5/RqX1n4YDKZmi/SJBt+PCeYC5E4DylBXxzf PPr0Tti8uRoZnklfRrn1xd5y+UM/ARY+tERxnzP7OJJMsenPLhmGN6ivN8dH6pM4gP5N J9mA==
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=MnoPRd3D5UcXB7BkQ51CZ5lJR3dFqWgEsy6TBBvlIzY=; b=BblDuahp5C+Z/QefWbZ4Ab0wH4Sr02NV3+fHYWmg7rW+IGRsIolwh0kmpbnEzKFO1Z P5LVUAErTISTrs3illYCDcxGWhBRS/F0jum/bNiyL1LAh6mBN43dvgV7RLFfOvUb1k1G ceB1McjtiqIoMVAc1QyGU1Nd4mG6d+HkcESAOLBmgWSEi1RrcLiDYYZQD13mE1maAESi kEmM9u2riymdrwFetUXfwCSoV0dOykgOy7vCfxoPaSFutM3OgRUMUr8Gj5Xoyo/7SRQI DvPGeVtsgRDWymhHHb0aySWmLaoRpfRXCY3WUGZYdemZHIMXwI7byUOAxROlrzklqOMW /BRA==
X-Gm-Message-State: AIVw113+w6f+O6k6hZ6C2WoCaweuAzU5iQWlkfQNQVtuDTjTHLmvRX9k kDbrPCgQ5RO8U6SwYYo09tqizQNoGVJU
X-Received: by 10.107.164.106 with SMTP id n103mr6204403ioe.42.1500005336707;  Thu, 13 Jul 2017 21:08:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.0.210 with HTTP; Thu, 13 Jul 2017 21:08:56 -0700 (PDT)
In-Reply-To: <20170712162958.3037.qmail@ary.lan>
References: <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com> <20170712162958.3037.qmail@ary.lan>
From: vaibhav singh <vaibhavsinghacads@gmail.com>
Date: Fri, 14 Jul 2017 09:38:56 +0530
Message-ID: <CACZ1GioxHKVxduAMYJ5qv81Osgpi9fDdHxVRLETSotSPQCD-6w@mail.gmail.com>
Subject: Re: Need for secured email delegation workflow
To: John Levine <johnl@taugh.com>
Cc: ietf@ietf.org
Content-Type: multipart/alternative; boundary="001a11421b38417c1f05543f35ca"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EQGOHUUUE-xeOiTfKDgCk4W52bE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jul 2017 04:08:59 -0000

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

Hi John,

First of all, sorry for not defining things properly. I will be adding this
glossary to all Email Delegation threads:

Definition: Email Delegation will be the workflow in which a user is able
to send emails on behalf of another user. A general example will be a
secretary replying back to emails which his/her boss received.

Couple of terms:

*manager* = The user who wants to delegate some other user to manage his
account on his behalf.

*delegate* = The user who has to get access to the manager's account.

Please note that email delegation could also cover cases like creating
folders, deleting folders etc in the manager's account.

So, I was working on a similar workflow and looking around to see how
others have implemented this workflow, and felt that a proper document
describing this workflow would really help, as the Email Delegation
behavior did not seem consistent and sometimes, not secure.


On Wed, Jul 12, 2017 at 9:59 PM, John Levine <johnl@taugh.com> wrote:

> In article <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9ct
> i7FHug@mail.gmail.com> you write:
> >I was working on implementing Email Delegation for my email server, and
> >felt a need to highlight a couple of things.
>
> Email Delegation is not as far as I can tell a phrase that has ever
> appeared in an RFC, and I have no idea what it means.
>
> Can you tell us what you're trying to do?
>
> R's,
> John
>



-- 

Regards,
Vaibhav Singh

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

<div dir=3D"ltr"><div><div><div>Hi John,<br><br></div>First of all, sorry f=
or not defining things properly. I will be adding this glossary to all Emai=
l Delegation threads:<br><br></div>Definition: Email Delegation will be the=
 workflow in which a user is able to send emails on behalf of another user.=
 A general example will be a secretary replying back to emails which his/he=
r boss received.<br><br></div>Couple of terms:<br><b><br>manager</b> =3D Th=
e user who wants to delegate some other user
      to manage his account on his behalf.<b><br></b><p><b>delegate</b> =3D=
 The user who has to get access to the manager&#39;s
      account. <br></p><p>Please note that email delegation could also cove=
r cases like creating folders, deleting folders etc in the manager&#39;s ac=
count.<br></p><br>So, I was working on a similar workflow and looking aroun=
d to see how others have implemented this workflow, and felt that a proper =
document describing this workflow would really help, as the Email Delegatio=
n behavior did not seem consistent and sometimes, not secure.<br><div><br><=
/div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Jul =
12, 2017 at 9:59 PM, John Levine <span dir=3D"ltr">&lt;<a href=3D"mailto:jo=
hnl@taugh.com" target=3D"_blank">johnl@taugh.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"><span class=3D"">In article &lt;<a href=3D"ma=
ilto:CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com">CA=
CZ1GioM8Oiz5-<wbr>bkk33MkmxPBwORcoiPGVsBSg3Hn9ct<wbr>i7FHug@mail.gmail.com<=
/a>&gt; you write:<br>
&gt;I was working on implementing Email Delegation for my email server, and=
<br>
&gt;felt a need to highlight a couple of things.<br>
<br>
</span>Email Delegation is not as far as I can tell a phrase that has ever<=
br>
appeared in an RFC, and I have no idea what it means.<br>
<br>
Can you tell us what you&#39;re trying to do?<br>
<br>
R&#39;s,<br>
John<br>
</blockquote></div><br><br clear=3D"all"><br>-- <br><div class=3D"gmail_sig=
nature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><div><br></div>=
Regards,<div>Vaibhav Singh</div></div></div>
</div></div>

--001a11421b38417c1f05543f35ca--


From nobody Thu Jul 13 21:24:57 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69338131A91 for <ietf@ietfa.amsl.com>; Thu, 13 Jul 2017 21:24: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 (1536-bit key) header.d=iecc.com header.b=HwoPlIee; dkim=pass (1536-bit key) header.d=taugh.com header.b=toVwjK1y
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 VIe-lK2IcIj0 for <ietf@ietfa.amsl.com>; Thu, 13 Jul 2017 21:24:53 -0700 (PDT)
Received: from miucha.iecc.com (w6.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6A8D131A89 for <ietf@ietf.org>; Thu, 13 Jul 2017 21:24:52 -0700 (PDT)
Received: (qmail 75391 invoked from network); 14 Jul 2017 04:24:51 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=1267d.59684793.k1707; bh=OGKwywb0Huw0e3jbeNI4MhTDW+ywbsguFUnijkQrWTk=; b=HwoPlIeen2iqQ7fpOsJvARVMWzMYx6928aNI7Lb4CGFdYHKZ5eKdAJIHmHueMTJ8Al2pXs+0QvSerfG0p/M/+DpQbx6qh9KFtiGg2gnhkV31oNsfyT4oxyWl9e1OiH94iQ7obQF5cS1rcG1eD5wIpZrItpl3E1ZY2H9kvaITvBdL6xFbvYUNMUEJXWL29b6Mg1bqhhZfXUCU0ibQTviRcOQ8agL4AIcSbnp9flvlCSLed7vqti3S56EUW1ebuGWt
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=1267d.59684793.k1707; bh=OGKwywb0Huw0e3jbeNI4MhTDW+ywbsguFUnijkQrWTk=; b=toVwjK1yVsk+CGo8An8YEcm8S8GKHa74d5nAdtKNEpYsWvxHd0XqloNsfkRjOdqjs7O49gRs3GgIffw7pQlBZGMTkVEfDBaT106aEmJwYw4SY2gRQszhMeJ6aZK20ekKUaDgv/Sw/5GtEkX9L0KCzlu/Kkt5DGu/O7p/DsgtLK/VX3qkK9NuBOdGyj25xWoe60UIQxo6z7sLsKkMHZRuW+W+7bhxM1goB0pDq2ZrxO+5LHJfBIbckEl4sVvTS5oA
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 14 Jul 2017 04:24:51 -0000
Date: 14 Jul 2017 00:24:50 -0400
Message-ID: <alpine.OSX.2.21.1707140015230.28154@ary.qy>
From: "John R Levine" <johnl@taugh.com>
To: "vaibhav singh" <vaibhavsinghacads@gmail.com>
Cc: "IETF general list" <ietf@ietf.org>
Subject: Re: Need for secured email delegation workflow
In-Reply-To: <CACZ1GioxHKVxduAMYJ5qv81Osgpi9fDdHxVRLETSotSPQCD-6w@mail.gmail.com>
References: <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com> <20170712162958.3037.qmail@ary.lan> <CACZ1GioxHKVxduAMYJ5qv81Osgpi9fDdHxVRLETSotSPQCD-6w@mail.gmail.com>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Z8MzWmo17aNVehBIB8L_wlLgI04>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jul 2017 04:24:54 -0000

> Definition: Email Delegation will be the workflow in which a user is able
> to send emails on behalf of another user. A general example will be a
> secretary replying back to emails which his/her boss received.

Oh, OK.  This is rather outside the scope of IETF standards.  Historically 
(like more than a decade ago) mail programs let anyone put any address on 
the From: line.  These days we have some designs like SPF and DMARC that 
limit sending mail as other domains (e.g., as security@paypal.com if 
your regular address is boris@phish.wtf) but we've never said anything 
about how a system decides who's allowed to send mail from various 
addresses in the same domain.

We do have standards for logging into mail systems both to send and to 
pick up mail.  A widely used convention (not a standard) is that you can 
send mail with an address on the From: line if you have the credentials to 
pick up mail sent to that address.  If that's your local convention, we do 
have designs like oauth which allow access delegation.  That might be a 
useful place to look.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Thu Jul 13 21:30:28 2017
Return-Path: <vaibhavsinghacads@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6F5F131A94 for <ietf@ietfa.amsl.com>; Thu, 13 Jul 2017 21:30:26 -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 LCVy-scVTytK for <ietf@ietfa.amsl.com>; Thu, 13 Jul 2017 21:30:24 -0700 (PDT)
Received: from mail-it0-x234.google.com (mail-it0-x234.google.com [IPv6:2607:f8b0:4001:c0b::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 1F9C11317B6 for <ietf@ietf.org>; Thu, 13 Jul 2017 21:30:24 -0700 (PDT)
Received: by mail-it0-x234.google.com with SMTP id m84so13210021ita.0 for <ietf@ietf.org>; Thu, 13 Jul 2017 21:30:24 -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=C/4d6mp1353zJrC41h70GZeiJBYSxuO2MQUCBIXTyMk=; b=SXjOAVzxaObLS6e9QfJUqqXu0BZuufUvc6wK+84Q7IIeiT7VTgfq1/qaZZ3tmOQjnq sXVgr6kutzcE9Z1fH0srlrKKFeA/GhsNAddU8wlyxypcbH2u+EnjCaYVGqttDc0/4LMi 6Cc4Mhs0Uk7yM9jwC+TfDnsqrCxvz/havGcvRw93m2oa+4wqK3GMVyWohyBDkp1TIvTY ZI8NEpJazNfI8fN/mWdgBejahJdw7FnkfwXtAyzGkoKFGlqbD6V7sy9+rgf/EAZlCldC Zjf0pBxsfpp8deY8IIhB0IpHzr6c/4PKXq34riiml3EdfTrZoExfjhL7c3wPDeH9B6mj i9Kg==
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=C/4d6mp1353zJrC41h70GZeiJBYSxuO2MQUCBIXTyMk=; b=fvzT7InjbnE/uLpBvI3y56mclJJJ9Yui3bjCBTQ067rvv/VhKlAmJgUGNHQoECtINv vhsBklB2FbvJBFC/H/LsU7eCuKB9l/MzukEDWyX6Emhr96pj0fXHGNXAPYQyNk+92jBV 3NmKccv9sACyC0U9Y4Y5YIqKawZvXFae4N0n23EoJyGNYF5oQFNke+ZkLYLbtMa0XQmd Q7+H1jZ5mqyz3LAfUqzfYOBSPSUxeWUjQGy/p+9tjDu7DHsG+bnlyCiv16n91V/mlOiN AWxyJFp/161oTXCOZ4qh91I7EUZ2hxApt7rbIxnflyRpUolWtBhVALLLLfUc6DTabJMD QzoA==
X-Gm-Message-State: AIVw110H8pji6N+5+7EVr36sC6N2aSAFuFs3H3u7qwsEK7ldha8knv6t Fm0QqHenrUsAKgLb7XPxMWLN1c/FrfCq
X-Received: by 10.107.140.211 with SMTP id o202mr6346008iod.49.1500006623449;  Thu, 13 Jul 2017 21:30:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.0.210 with HTTP; Thu, 13 Jul 2017 21:30:22 -0700 (PDT)
In-Reply-To: <28827.1499886723@dooku.sandelman.ca>
References: <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com> <28827.1499886723@dooku.sandelman.ca>
From: vaibhav singh <vaibhavsinghacads@gmail.com>
Date: Fri, 14 Jul 2017 10:00:22 +0530
Message-ID: <CACZ1GiqmFTzD346x02_gvvFqfm1n-N=xBC01xb0_mEpUa_JYUA@mail.gmail.com>
Subject: Re: Need for secured email delegation workflow
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: ietf@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c06136ef3965205543f8126"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8qDnb5i0Ef9PR7BzUBlzOFwzx5I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jul 2017 04:30:27 -0000

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

On Thu, Jul 13, 2017 at 12:42 AM, Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> vaibhav singh <vaibhavsinghacads@gmail.com> wrote:
>     > First of all, I am kind of new and still learning how email
>     > infrastructure fits in, so please feel free to highlight any glaring
>     > issues with my logic.
>
>     > I was working on implementing Email Delegation for my email server,
> and
>     > felt a need to highlight a couple of things.
>
>     > 1.) I could not find a place where this workflow is outlined. It
> seems
>     > like everyone, from Microsoft to Google, have an implementation for
>     > email delegation, and they are all kind of doing their own thing.
>
> I think that when you say "email delegation", you mean where a manager
> (or other person) authorizes their "PA" (personal assistant, formerly known
> as "secretary") to send email on their behalf.  Back in the days of BNR
> COCOS
> it was very common thing for middle management, but even in those dark days
> of mainframe based email, it was usually accomplished by having the PA log
> in
> with the manager's email.
>
> It's good that microsoft(outlook) and google(gmail) have realized that
> sharing passwords is a dumb thing.  I think that in the walled gardens of
> those systems, that the email delegation is accomplished entirely within
> their MUA/MTA.
>

Exactly!! That is the workflow I am talking about. However, I feel that
this could be something which could be used for other things as well, for
example, in the place where I work, we have some automated tools where a
user can input certain data and the tool will send mails to our group email
address on behalf of the user.

Couple of terms:

*manager* = The user who wants to delegate some other user to manage his
account on his behalf.

*delegate* = The user who has to get access to the manager's account.

*entity *= Any email user.
Please note that email delegation could also cover cases like creating
folders, deleting folders etc in the manager's account.


This concept, in my opinion, could be generalized to include "entities"
which could request permission to send mails on behalf of some other
"entity". Sort of like OAUTH with emails, if you will. I am still hazy with
all the details and not sure about how useful this could be, but it seems
promising to me.

Another question which I was not clear about was how S/MIME would be
integrated with delegation. For example, suppose the delegate were to
create a signed email on behalf of the manager, in which case the manager
would have to share his private key with the delegate. This would
definitely not be secure.


>     > 2.) As I could not find any RFC/Internet Draft covering this flow, I
>     > could, potentially, create a really bad email delegation
> implementation
>     > in which I could allow potentially anyone to send mails on behalf of
>     > anyone, and I will still be, say, RFC-2822 compatible (I may be
>
> RFC2822 (and 822 before it, and the one for that) always let anyone send
> any
> email claiming to be from anyway.  That was both a strength
> ("permissionless
> innovation"), and led to our spam disaster.  So as others in this thread
> have mentioned, we have SPF to give clues as to which IP addresses are
> authorized to speak authoritative for a domain, and DKIM to make sure that
> the headers are authentic (and optionally body). Neither provides for
> content
> signing that is reachable by end users at this time.
> I don't think you are looking for SPF or DKIM, unless you are trying
> to seperate the PA and the manager into different (submission) mail
> systems.
>
> All of this is MTA to MTA protocol, not MUA to MTA.
>
>     > incorrect here, but I could not really find any place which would
>     > restrict a user from sending an email on someone's behalf, by editing
>     > the "Sender" header before sending an IMAP request.)
>
> Since you speak about IMAP, you are clearly not in the MTA business, but
> I suspect in the MUA side of things.  Maybe I'm wrong and you are building
> IMAP servers.  I didn't think that IMAP included email submission, but I'm
> sure I'm not up to speed... (30 years since I wrote that MTA for
> AmigaOS...)
> So let me speak about email submission protocol (rfc4409) and you can
> substitute IMAP if that is in fact appropriate.
>
>
It seems to me that a mail server that has an authorized user SHOULD force
> the SMTP From (aka "Sender") to the authorized user.  Perhaps it MAY also
> force the body From: to a specific value, but I haven't encountered an
> open source one that does.  It seems that you are asking how a MUA could
> indicate (and provide proof) that it is authorized to set the From:
> order Sender: to another value.  (I really think, btw, you want to set
> the From: to the manager, and leave the Sender: as the PA)
>
> This seems like it might be the space for a SAML assertion.
> I believe that many IMAP servers use small subsets of SAML to provide
> mailbox
> ACLs, and it would fit right in there.  I suspect that there is space for
> an RFC about how to do this in a standard way.
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
>


-- 

Regards,
Vaibhav Singh

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Thu, Jul 13, 2017 at 12:42 AM, Michael Richardson <span dir=3D"ltr">=
&lt;<a href=3D"mailto:mcr+ietf@sandelman.ca" target=3D"_blank">mcr+ietf@san=
delman.ca</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 class=3D"gmail-"><br>
vaibhav singh &lt;<a href=3D"mailto:vaibhavsinghacads@gmail.com">vaibhavsin=
ghacads@gmail.com</a>&gt; wrote:<br>
=C2=A0 =C2=A0 &gt; First of all, I am kind of new and still learning how em=
ail<br>
=C2=A0 =C2=A0 &gt; infrastructure fits in, so please feel free to highlight=
 any glaring<br>
=C2=A0 =C2=A0 &gt; issues with my logic.<br>
<br>
=C2=A0 =C2=A0 &gt; I was working on implementing Email Delegation for my em=
ail server, and<br>
=C2=A0 =C2=A0 &gt; felt a need to highlight a couple of things.<br>
<br>
=C2=A0 =C2=A0 &gt; 1.) I could not find a place where this workflow is outl=
ined. It seems<br>
=C2=A0 =C2=A0 &gt; like everyone, from Microsoft to Google, have an impleme=
ntation for<br>
=C2=A0 =C2=A0 &gt; email delegation, and they are all kind of doing their o=
wn thing.<br>
<br>
</span>I think that when you say &quot;email delegation&quot;, you mean whe=
re a manager<br>
(or other person) authorizes their &quot;PA&quot; (personal assistant, form=
erly known<br>
as &quot;secretary&quot;) to send email on their behalf.=C2=A0 Back in the =
days of BNR COCOS<br>
it was very common thing for middle management, but even in those dark days=
<br>
of mainframe based email, it was usually accomplished by having the PA log =
in<br>
with the manager&#39;s email.<br>
<br>
It&#39;s good that microsoft(outlook) and google(gmail) have realized that<=
br>
sharing passwords is a dumb thing.=C2=A0 I think that in the walled gardens=
 of<br>
those systems, that the email delegation is accomplished entirely within<br=
>
their MUA/MTA.<br></blockquote><div><br>Exactly!! That is the workflow I am=
 talking about. However, I feel that this could be something which could be=
 used for other things as well, for example, in the place where I work, we =
have some automated tools where a user can input certain data and the tool =
will send mails to our group email address on behalf of the user.<br><br></=
div><div>Couple of terms:<br><b><br>manager</b> =3D The user who wants to d=
elegate some other user
      to manage his account on his behalf.<b><br></b><p><b>delegate</b> =3D=
 The user who has to get access to the manager&#39;s
      account.=C2=A0</p><p><b>entity </b>=3D Any email user.<br></p>Please =
note that email delegation could also cover cases like creating folders, de=
leting folders etc in the manager&#39;s account.<br><br><br></div><div>This=
 concept, in my opinion, could be generalized to include &quot;entities&quo=
t; which could request permission to send mails on behalf of some other &qu=
ot;entity&quot;. Sort of like OAUTH with emails, if you will. I am still ha=
zy with all the details and not sure about how useful this could be, but it=
 seems promising to me.<br><br></div><div>Another question which I was not =
clear about was how S/MIME would be integrated with delegation. For example=
, suppose the delegate were to create a signed email on behalf of the manag=
er, in which case the manager would have to share his private key with the =
delegate. This would definitely not be secure.<br><br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">
<span class=3D"gmail-"><br>
=C2=A0 =C2=A0 &gt; 2.) As I could not find any RFC/Internet Draft covering =
this flow, I<br>
=C2=A0 =C2=A0 &gt; could, potentially, create a really bad email delegation=
 implementation<br>
=C2=A0 =C2=A0 &gt; in which I could allow potentially anyone to send mails =
on behalf of<br>
=C2=A0 =C2=A0 &gt; anyone, and I will still be, say, RFC-2822 compatible (I=
 may be<br>
<br>
</span>RFC2822 (and 822 before it, and the one for that) always let anyone =
send any<br>
email claiming to be from anyway.=C2=A0 That was both a strength (&quot;per=
missionless<br>
innovation&quot;), and led to our spam disaster.=C2=A0 So as others in this=
 thread<br>
have mentioned, we have SPF to give clues as to which IP addresses are<br>
authorized to speak authoritative for a domain, and DKIM to make sure that<=
br>
the headers are authentic (and optionally body). Neither provides for conte=
nt<br>
signing that is reachable by end users at this time.<br>
I don&#39;t think you are looking for SPF or DKIM, unless you are trying<br=
>
to seperate the PA and the manager into different (submission) mail systems=
.<br>
<br>
All of this is MTA to MTA protocol, not MUA to MTA.<br>
<span class=3D"gmail-"><br>
=C2=A0 =C2=A0 &gt; incorrect here, but I could not really find any place wh=
ich would<br>
=C2=A0 =C2=A0 &gt; restrict a user from sending an email on someone&#39;s b=
ehalf, by editing<br>
=C2=A0 =C2=A0 &gt; the &quot;Sender&quot; header before sending an IMAP req=
uest.)<br>
<br>
</span>Since you speak about IMAP, you are clearly not in the MTA business,=
 but<br>
I suspect in the MUA side of things.=C2=A0 Maybe I&#39;m wrong and you are =
building<br>
IMAP servers.=C2=A0 I didn&#39;t think that IMAP included email submission,=
 but I&#39;m<br>
sure I&#39;m not up to speed... (30 years since I wrote that MTA for AmigaO=
S...)<br>
So let me speak about email submission protocol (rfc4409) and you can<br>
substitute IMAP if that is in fact appropriate.<br>
=C2=A0<br></blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
It seems to me that a mail server that has an authorized user SHOULD force<=
br>
the SMTP From (aka &quot;Sender&quot;) to the authorized user.=C2=A0 Perhap=
s it MAY also<br>
force the body From: to a specific value, but I haven&#39;t encountered an<=
br>
open source one that does.=C2=A0 It seems that you are asking how a MUA cou=
ld<br>
indicate (and provide proof) that it is authorized to set the From:<br>
order Sender: to another value.=C2=A0 (I really think, btw, you want to set=
<br>
the From: to the manager, and leave the Sender: as the PA)<br>
<br>
This seems like it might be the space for a SAML assertion.<br>
I believe that many IMAP servers use small subsets of SAML to provide mailb=
ox<br>
ACLs, and it would fit right in there.=C2=A0 I suspect that there is space =
for<br>
an RFC about how to do this in a standard way.<br>
<br>
--<br>
Michael Richardson &lt;<a href=3D"mailto:mcr%2BIETF@sandelman.ca">mcr+IETF@=
sandelman.ca</a>&gt;, Sandelman Software Works<br>
=C2=A0-=3D IPv6 IoT consulting =3D-<br>
<br>
<br>
<br>
</blockquote></div><br><br clear=3D"all"><br>-- <br><div class=3D"gmail_sig=
nature"><div dir=3D"ltr"><div><br></div>Regards,<div>Vaibhav Singh</div></d=
iv></div>
</div></div>

--94eb2c06136ef3965205543f8126--


From nobody Thu Jul 13 21:51:51 2017
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A16F7131AA1 for <ietf@ietfa.amsl.com>; Thu, 13 Jul 2017 21:51:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.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 jKWPPYjrdkPC for <ietf@ietfa.amsl.com>; Thu, 13 Jul 2017 21:51:48 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 8A43D130133 for <ietf@ietf.org>; Thu, 13 Jul 2017 21:51:48 -0700 (PDT)
Received: from [192.168.1.75] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v6E4q1Mo005513 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 13 Jul 2017 21:52:02 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1500007922; bh=j7iR2KNAn/LuEMfRSV7kQUe4IfUP6j09ZlC42k245PY=; h=Subject:To:Cc:References:From:Reply-To:Date:In-Reply-To:From; b=hduWYAtkE3gWIX+Uuql2OUYa+5k26ewS522V4Px4WyuZmsbaLSZqwQnr/qD9huJ96 sJxqIPaMt9r/e/xKRZqin1Nq4zoz8nZKTge7+mqLXpwYSTuhdutuaj584yWzdt0eQo +10Q353FPf//sMSs8IImCG/y6cRb3KsTSyZ2Wekg=
Subject: Re: Need for secured email delegation workflow
To: John R Levine <johnl@taugh.com>
Cc: IETF general list <ietf@ietf.org>
References: <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com> <20170712162958.3037.qmail@ary.lan> <CACZ1GioxHKVxduAMYJ5qv81Osgpi9fDdHxVRLETSotSPQCD-6w@mail.gmail.com> <alpine.OSX.2.21.1707140015230.28154@ary.qy>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Reply-To: dcrocker@bbiw.net
Message-ID: <c683c0ae-6ec0-9a9f-e91d-2396388979b3@dcrocker.net>
Date: Thu, 13 Jul 2017 21:51:40 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <alpine.OSX.2.21.1707140015230.28154@ary.qy>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6qAzJ4uWkullLDAhFjyxPAufpv0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jul 2017 04:51:50 -0000

On 7/13/2017 9:24 PM, John R Levine wrote:
>> Definition: Email Delegation will be the workflow in which a user is able
>> to send emails on behalf of another user. A general example will be a
>> secretary replying back to emails which his/her boss received.
> 
> Oh, OK.  This is rather outside the scope of IETF standards.


Except that that scenario was exactly the reason for the rfc5322.Sender 
(originally rfc733.Sender) distinction from the rfc5322.From field. See 
Section 3.6.2, which still has this explained in those terms.

So it hasn't been specified with authentication protections -- and it's 
not clear that we now how to provide that granularity at scale, or 
rather there is pretty strong operational demonstration that we do /not/ 
know how -- but it has already been done as a semantic.  40 years ago, 
this year, with periodic renewals...

The problem now is that the construct has mostly been moved to the 'via' 
hack in the <display-name> field.


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Fri Jul 14 04:11:15 2017
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34327131B42 for <ietf@ietfa.amsl.com>; Fri, 14 Jul 2017 04:11:14 -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 mLzwPVF9oFCK for <ietf@ietfa.amsl.com>; Fri, 14 Jul 2017 04:11:10 -0700 (PDT)
Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) (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 15E47131B41 for <ietf@ietf.org>; Fri, 14 Jul 2017 04:11:10 -0700 (PDT)
Received: from pps.filterd (m0098420.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v6EB9Ksw060310 for <ietf@ietf.org>; Fri, 14 Jul 2017 07:11:09 -0400
Received: from e34.co.us.ibm.com (e34.co.us.ibm.com [32.97.110.152]) by mx0b-001b2d01.pphosted.com with ESMTP id 2bph7xyy70-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 14 Jul 2017 07:11:09 -0400
Received: from localhost by e34.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 14 Jul 2017 05:11:08 -0600
Received: from b03cxnp08026.gho.boulder.ibm.com (9.17.130.18) by e34.co.us.ibm.com (192.168.1.134) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 14 Jul 2017 05:11:06 -0600
Received: from b03ledav005.gho.boulder.ibm.com (b03ledav005.gho.boulder.ibm.com [9.17.130.236]) by b03cxnp08026.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v6EBB6bP64815200 for <ietf@ietf.org>; Fri, 14 Jul 2017 04:11:06 -0700
Received: from b03ledav005.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 0F230BE03B for <ietf@ietf.org>; Fri, 14 Jul 2017 05:11:06 -0600 (MDT)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b03ledav005.gho.boulder.ibm.com (Postfix) with ESMTPS id DC7ADBE040 for <ietf@ietf.org>; Fri, 14 Jul 2017 05:11:05 -0600 (MDT)
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.15.2/8.12.5) with ESMTP id v6EBB4eg008298 for <ietf@ietf.org>; Fri, 14 Jul 2017 07:11:04 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v6EBB3kf008282 for ietf@ietf.org; Fri, 14 Jul 2017 07:11:03 -0400
From: narten@us.ibm.com
Date: Fri, 14 Jul 2017 07:11:03 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-GCONF: 00
x-cbid: 17071411-0016-0000-0000-0000072CDD42
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00007364; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000214; SDB=6.00887401; UDB=6.00443066; IPR=6.00667551;  BA=6.00005470; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00016223; XFM=3.00000015; UTC=2017-07-14 11:11:07
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17071411-0017-0000-0000-00003A941BE4
Message-Id: <201707141111.v6EBB3kf008282@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-07-13_13:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=75 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1706020000 definitions=main-1707140184
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ubat1TBe1U7C6iKZciu-EsSUDmc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jul 2017 11:11:14 -0000

Total of 87 messages in the last 7 days.
 
script run at: Fri Jul 14 07:11:03 EDT 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  2.30% |    2 | 15.36% |   167754 | mjethanandani@gmail.com
  8.05% |    7 |  5.46% |    59687 | nico@cryptonector.com
  5.75% |    5 |  6.12% |    66890 | phill@hallambaker.com
  6.90% |    6 |  3.69% |    40286 | randy@psg.com
  1.15% |    1 |  7.93% |    86646 | xufeng_liu@jabil.com
  4.60% |    4 |  3.74% |    40801 | marka@isc.org
  3.45% |    3 |  2.80% |    30575 | presnick@qti.qualcomm.com
  3.45% |    3 |  2.02% |    22078 | dhc@dcrocker.net
  2.30% |    2 |  3.12% |    34075 | zhangmingui@huawei.com
  2.30% |    2 |  2.48% |    27113 | lars@netapp.com
  2.30% |    2 |  1.77% |    19349 | kazuhooku@gmail.com
  2.30% |    2 |  1.66% |    18186 | tjc@ecs.soton.ac.uk
  2.30% |    2 |  1.65% |    18050 | ajs@anvilwalrusden.com
  2.30% |    2 |  1.59% |    17400 | mnot@mnot.net
  2.30% |    2 |  1.55% |    16948 | joelja@bogus.com
  2.30% |    2 |  1.27% |    13834 | w@1wt.eu
  1.15% |    1 |  2.35% |    25654 | michelle.cotton@iana.org
  2.30% |    2 |  1.09% |    11907 | johnl@taugh.com
  1.15% |    1 |  2.23% |    24404 | magnus.westerlund@ericsson.com
  1.15% |    1 |  2.00% |    21857 | ietfjournal@isoc.org
  1.15% |    1 |  1.68% |    18372 | worley@ariadne.com
  1.15% |    1 |  1.40% |    15256 | chinese.apricot@gmail.com
  1.15% |    1 |  1.37% |    14927 | bruno.decraene@orange.com
  1.15% |    1 |  1.26% |    13808 | drc@virtualized.org
  1.15% |    1 |  1.08% |    11750 | alissa@cooperw.in
  1.15% |    1 |  0.97% |    10645 | melinda.shore@gmail.com
  1.15% |    1 |  0.96% |    10471 | bob.hinden@gmail.com
  1.15% |    1 |  0.95% |    10395 | mcr+ietf@sandelman.ca
  1.15% |    1 |  0.94% |    10300 | petr.spacek@nic.cz
  1.15% |    1 |  0.91% |     9941 | mellon@fugue.com
  1.15% |    1 |  0.91% |     9904 | sanjay.mishra@verizon.com
  1.15% |    1 |  0.90% |     9840 | stefan.eissing@greenbytes.de
  1.15% |    1 |  0.89% |     9771 | vaibhavsinghacads@gmail.com
  1.15% |    1 |  0.88% |     9654 | jclarke@cisco.com
  1.15% |    1 |  0.88% |     9579 | jordi.palet@consulintel.es
  1.15% |    1 |  0.85% |     9302 | lear@cisco.com
  1.15% |    1 |  0.83% |     9104 | jason_livingood@comcast.com
  1.15% |    1 |  0.83% |     9082 | brian.e.carpenter@gmail.com
  1.15% |    1 |  0.83% |     9062 | allison.mankin@gmail.com
  1.15% |    1 |  0.83% |     9017 | alexander.clemm@huawei.com
  1.15% |    1 |  0.82% |     8999 | ggm@algebras.org
  1.15% |    1 |  0.81% |     8876 | jared@puck.nether.net
  1.15% |    1 |  0.73% |     7923 | eckelcu@cisco.com
  1.15% |    1 |  0.71% |     7785 | fluffy@iii.ca
  1.15% |    1 |  0.70% |     7692 | ietf-dane@dukhovni.org
  1.15% |    1 |  0.70% |     7616 | paul@redbarn.org
  1.15% |    1 |  0.69% |     7495 | julian.reschke@gmx.de
  1.15% |    1 |  0.67% |     7277 | dave@davecake.net
  1.15% |    1 |  0.66% |     7222 | paul@nohats.ca
  1.15% |    1 |  0.64% |     7014 | ned+ietf@mauve.mrochek.com
  1.15% |    1 |  0.61% |     6623 | vijay.gurbani@nokia.com
  1.15% |    1 |  0.59% |     6480 | nick@foobar.org
  1.15% |    1 |  0.57% |     6275 | chopps@chopps.org
  1.15% |    1 |  0.54% |     5875 | nomcom-chair-2017@ietf.org
  1.15% |    1 |  0.50% |     5447 | jmh@joelhalpern.com
--------+------+--------+----------+------------------------
100.00% |   87 |100.00% |  1092273 | Total


From nobody Fri Jul 14 06:15:59 2017
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7D78131A63 for <ietf@ietfa.amsl.com>; Fri, 14 Jul 2017 06:15:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 S_T8GLpp0YIT for <ietf@ietfa.amsl.com>; Fri, 14 Jul 2017 06:15:56 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0337131A5A for <ietf@ietf.org>; Fri, 14 Jul 2017 06:15:56 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [62.168.35.69]) by relay.sandelman.ca (Postfix) with ESMTPS id 8E5B71F8FB; Fri, 14 Jul 2017 13:15:55 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id D00F759F; Fri, 14 Jul 2017 09:15:52 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: vaibhav singh <vaibhavsinghacads@gmail.com>
cc: ietf@ietf.org
Subject: Re: Need for secured email delegation workflow
In-reply-to: <CACZ1GiqmFTzD346x02_gvvFqfm1n-N=xBC01xb0_mEpUa_JYUA@mail.gmail.com>
References: <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com> <28827.1499886723@dooku.sandelman.ca> <CACZ1GiqmFTzD346x02_gvvFqfm1n-N=xBC01xb0_mEpUa_JYUA@mail.gmail.com>
Comments: In-reply-to vaibhav singh <vaibhavsinghacads@gmail.com> message dated "Fri, 14 Jul 2017 10:00:22 +0530."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 14 Jul 2017 15:15:52 +0200
Message-ID: <10572.1500038152@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JQtNoOTyTbvjPvo8Hj73kyIm2xc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jul 2017 13:15:57 -0000

--=-=-=
Content-Type: text/plain


vaibhav singh <vaibhavsinghacads@gmail.com> wrote:
    > Another question which I was not clear about was how S/MIME would be
    > integrated with delegation. For example, suppose the delegate were to
    > create a signed email on behalf of the manager, in which case the
    > manager would have to share his private key with the delegate. This
    > would definitely not be secure.

It is possible to have more than one certificate issued for a given DN,
but usually we try to avoid such things.   Some variation of this is probably
the right answer.  You'll have to talk to an enterprise CA provider to
understand if they do anything.  I suspect that if you can make contact
with the microsoft certificate authority people (I don't know them), they
will know if they have solved this problem.

I'm not sure if you read this part:

    mcr> This seems like it might be the space for a SAML assertion.
    mcr> I believe that many IMAP servers use small subsets of SAML to provide
    mcr> mailbox
    mcr> ACLs, and it would fit right in there. I suspect that there is space
    mcr> for
    mcr> an RFC about how to do this in a standard way.


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJZaMQIAAoJEJVM4Vb9/EKQJisH/3fYKGFHq1STOOndxcm+2KcI
pEOV7uMwEhVHLS4IK3F+T02D17DMsDBUumlHgB1fmIu+pgLhdAWUtefjFbngIUaD
vWPfh1U8laoT4tXDZkxAf+u/2q5Ppoq6nH02Tp3hvGL3Yn0bRtLZU4PTkM+zwobh
EhcY1hy/22UgnVSQgvA1YUGBp2AiX+k40eNm24Dk//ftSwThrYasGjywYNwDeorJ
1MXfHVgiOhh1S6Mc5GIio31J1yHjeTCZ9yQZIwCCXMvuzjI9s9ZiqFWrI8pyy0jp
IxUV9yC2Hl0yaJ7D7o6HAXuHfxfBXd8VXVp8xn90LA/AyAGGxDwV1JoNBaK4G2U=
=dgEY
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Jul 14 07:15:15 2017
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC5A4131A8A for <ietf@ietfa.amsl.com>; Fri, 14 Jul 2017 07:15:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.108
X-Spam-Level: 
X-Spam-Status: No, score=-1.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-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 g_aipmg1MMFl for <ietf@ietfa.amsl.com>; Fri, 14 Jul 2017 07:15:13 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64FFC13189D for <ietf@ietf.org>; Fri, 14 Jul 2017 07:15:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 751114773ABC for <ietf@ietf.org>; Fri, 14 Jul 2017 10:15:12 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aYmqL58zBnkA for <ietf@ietf.org>; Fri, 14 Jul 2017 10:15:12 -0400 (EDT)
Received: from [10.251.216.222] (unknown [65.112.10.218]) by sobco.sobco.com (Postfix) with ESMTPSA id EE8C24773AA2 for <ietf@ietf.org>; Fri, 14 Jul 2017 10:15:11 -0400 (EDT)
From: Scott Bradner <sob@sobco.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F41E588F-E6EB-475F-921A-BB67E6AF3EC4"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: IETF blog entry about the latest update to the IETF patent-related intellectual property rights rules
Message-Id: <05EB143F-DDD1-4F96-B6F0-EE5B5D5AA583@sobco.com>
Date: Fri, 14 Jul 2017 10:15:11 -0400
To: ietf@ietf.org
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Da0uwY18C1oJvjxeJI-4DM00Zy8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jul 2017 14:15:15 -0000

--Apple-Mail=_F41E588F-E6EB-475F-921A-BB67E6AF3EC4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

After too many years the update to the patent related parts of the IETF =
intellectual property rights rules has been=20
published as RFC 8179 (a.k.a BCP 79).  We have written an IETF blog =
entry that reviews the=20
changes in the rules defined by the new RFC.

Please see: https://www.ietf.org/blog/2017/07/whats-behind-bcp79bis =
<https://www.ietf.org/blog/2017/07/whats-behind-bcp79bis>

Jorge & Scott=

--Apple-Mail=_F41E588F-E6EB-475F-921A-BB67E6AF3EC4
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">After too many years the update to the patent related parts&nbsp;of the IETF intellectual property rights rules&nbsp;has been&nbsp;<div class="">published as RFC 8179&nbsp;(a.k.a BCP 79).&nbsp;&nbsp;We have written an IETF&nbsp;blog entry that reviews the&nbsp;</div><div class="">changes in the rules defined by the new RFC.<br class=""><br class="">Please see:&nbsp;<a href="https://www.ietf.org/blog/2017/07/whats-behind-bcp79bis" class="">https://www.ietf.org/blog/2017/07/whats-behind-bcp79bis</a><br class=""><br class="">Jorge &amp; Scott</div></body></html>
--Apple-Mail=_F41E588F-E6EB-475F-921A-BB67E6AF3EC4--


From nobody Fri Jul 14 07:42:11 2017
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C971013189D for <ietf@ietfa.amsl.com>; Fri, 14 Jul 2017 07:42:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 EBCW-l5qdu6s for <ietf@ietfa.amsl.com>; Fri, 14 Jul 2017 07:42:08 -0700 (PDT)
Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (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 043F91241FC for <ietf@ietf.org>; Fri, 14 Jul 2017 07:42:08 -0700 (PDT)
Received: by mail-wm0-x243.google.com with SMTP id j85so11183629wmj.0 for <ietf@ietf.org>; Fri, 14 Jul 2017 07:42:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=H3J4qL5YYAcQNYB5muO7ul/PoA2sIlPz8X0ZZyL7sMw=; b=EwjNl0CXngN11nE9jx5zSchGiqkbAsHFuGkltq4vvHAOAnkuRuW6sIL+/rF+efwOEu DjP5iYPXLwpiHGDF0r/jgsKbQJiimYvu7UEPHHRyFtM0sXs3WA5R511iwMadtFx+RCpn aZHTgUGogD7pWcv2ssBMWUNEyOl4P9XzCqb/Hmr9ln5C3ox5Hdq9oxYkEKfdWxnV0zC/ LajYS6WD3mjukU67lmUaM4fAGihgTwK9bQiKsH9nwe1YcMG7z5i80mefavFbNDugT990 mNmUYS7/5H4IVKjpONnF8ILLU1hxQst1RjF0L25RVwSsOXHkBiIO2RbQiSs3q5guq0rb 2WTQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=H3J4qL5YYAcQNYB5muO7ul/PoA2sIlPz8X0ZZyL7sMw=; b=kIgsY33+a0mxtICAiEZzT4EqyrnM9XaPj7SO+DUV6PIMOf2nlcRtlbxpBkOAH6uFfP ThC2F4RcJFiJ/OSZN+JHCFmvZde5aokbSZyooWh8DEfvXacHANVfrar1DtAcgVaAQlgg 5i99/zXENTTZB/cwzWIBgGW2QIZOMKPpprGR+7M+wAT04twoRA0qyqwPRplynfUfqBkH OxoLiBnEml0hNyD6wfEIOjdR0usBQ7WkRggp1Ee5vQaX56MvdJLXVreEZbZttO0upXOC VkCs9g172G3ntDDWVOEq57CfexBAb8UPVM77nQ0I6iR6MX+6aP5Klex6PinbyFkNNNX6 ZOLA==
X-Gm-Message-State: AIVw113nYRnzTc2kMQ6UydRnulBqXRVIUd9JUhSu9lp3Ma3KFPYDcPvM hkop+nibzIfUpMPFaRg=
X-Received: by 10.80.192.154 with SMTP id k26mr7113051edf.136.1500043326591; Fri, 14 Jul 2017 07:42:06 -0700 (PDT)
Received: from [192.168.1.18] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id f48sm5415534edf.30.2017.07.14.07.42.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 14 Jul 2017 07:42:05 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <62FDB3A5-C71A-4B5C-8CD9-94B0EE4DC313@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_996EF6F4-E6F8-4F15-B761-99DA31C23DD5"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Need for secured email delegation workflow
Date: Fri, 14 Jul 2017 17:42:03 +0300
In-Reply-To: <CACZ1GiqmFTzD346x02_gvvFqfm1n-N=xBC01xb0_mEpUa_JYUA@mail.gmail.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, ietf@ietf.org
To: vaibhav singh <vaibhavsinghacads@gmail.com>
References: <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com> <28827.1499886723@dooku.sandelman.ca> <CACZ1GiqmFTzD346x02_gvvFqfm1n-N=xBC01xb0_mEpUa_JYUA@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2_Ae9yivbsjoCdUkGO_WxgkRTk8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jul 2017 14:42:10 -0000

--Apple-Mail=_996EF6F4-E6F8-4F15-B761-99DA31C23DD5
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_D8D01DC4-820B-4ED3-9D86-D22F03774C4F"


--Apple-Mail=_D8D01DC4-820B-4ED3-9D86-D22F03774C4F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On 14 Jul 2017, at 7:30, vaibhav singh <vaibhavsinghacads@gmail.com> =
wrote:
>=20
>=20
>=20
> On Thu, Jul 13, 2017 at 12:42 AM, Michael Richardson =
<mcr+ietf@sandelman.ca <mailto:mcr+ietf@sandelman.ca>> wrote:
>=20
> vaibhav singh <vaibhavsinghacads@gmail.com =
<mailto:vaibhavsinghacads@gmail.com>> wrote:
>     > First of all, I am kind of new and still learning how email
>     > infrastructure fits in, so please feel free to highlight any =
glaring
>     > issues with my logic.
>=20
>     > I was working on implementing Email Delegation for my email =
server, and
>     > felt a need to highlight a couple of things.
>=20
>     > 1.) I could not find a place where this workflow is outlined. It =
seems
>     > like everyone, from Microsoft to Google, have an implementation =
for
>     > email delegation, and they are all kind of doing their own =
thing.
>=20
> I think that when you say "email delegation", you mean where a manager
> (or other person) authorizes their "PA" (personal assistant, formerly =
known
> as "secretary") to send email on their behalf.  Back in the days of =
BNR COCOS
> it was very common thing for middle management, but even in those dark =
days
> of mainframe based email, it was usually accomplished by having the PA =
log in
> with the manager's email.
>=20
> It's good that microsoft(outlook) and google(gmail) have realized that
> sharing passwords is a dumb thing.  I think that in the walled gardens =
of
> those systems, that the email delegation is accomplished entirely =
within
> their MUA/MTA.
>=20
> Exactly!! That is the workflow I am talking about. However, I feel =
that this could be something which could be used for other things as =
well, for example, in the place where I work, we have some automated =
tools where a user can input certain data and the tool will send mails =
to our group email address on behalf of the user.
>=20
> Couple of terms:
>=20
> manager =3D The user who wants to delegate some other user to manage =
his account on his behalf.

I think =E2=80=9Cprincipal=E2=80=9D is a better term. I would expect =
=E2=80=9Cmanager=E2=80=9D to authorize b to manage on behalf of c.
> delegate =3D The user who has to get access to the manager's account.
>=20
> entity =3D Any email user.
>=20
> Please note that email delegation could also cover cases like creating =
folders, deleting folders etc in the manager's account.
>=20
>=20
> This concept, in my opinion, could be generalized to include =
"entities" which could request permission to send mails on behalf of =
some other "entity". Sort of like OAUTH with emails, if you will. I am =
still hazy with all the details and not sure about how useful this could =
be, but it seems promising to me.
>=20
> Another question which I was not clear about was how S/MIME would be =
integrated with delegation. For example, suppose the delegate were to =
create a signed email on behalf of the manager, in which case the =
manager would have to share his private key with the delegate. This =
would definitely not be secure.

This is part of a wider issue. Even without delegation, if I use my own =
email account with several MUAs (say, my laptop and my phone), where is =
the private key stored?  Is it shared between laptop and phone?

You end up reading encrypted mail only using one MUA, which is one more =
thing dragging the use of S/Mime down.

While it may be OK to share a key with my phone (but too difficult to do =
securely in practice), sharing with a delegate is hairy on many =
different layers. But still it=E2=80=99s the same issue.

Yoav

--Apple-Mail=_D8D01DC4-820B-4ED3-9D86-D22F03774C4F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 14 Jul 2017, at 7:30, vaibhav singh &lt;<a =
href=3D"mailto:vaibhavsinghacads@gmail.com" =
class=3D"">vaibhavsinghacads@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><br =
class=3D"Apple-interchange-newline"><br style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><div =
class=3D"gmail_quote" style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;">On Thu, Jul 13, 2017 at 12:42 AM, =
Michael Richardson<span class=3D"Apple-converted-space">&nbsp;</span><span=
 dir=3D"ltr" class=3D"">&lt;<a href=3D"mailto:mcr+ietf@sandelman.ca" =
target=3D"_blank" class=3D"">mcr+ietf@sandelman.ca</a>&gt;</span><span =
class=3D"Apple-converted-space">&nbsp;</span>wrote:<br =
class=3D""><blockquote class=3D"gmail_quote" style=3D"margin: 0px 0px =
0px 0.8ex; border-left-width: 1px; border-left-style: solid; =
border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><span =
class=3D"gmail-"><br class=3D"">vaibhav singh &lt;<a =
href=3D"mailto:vaibhavsinghacads@gmail.com" =
class=3D"">vaibhavsinghacads@gmail.com</a>&gt; wrote:<br class=3D"">&nbsp;=
 &nbsp;<span class=3D"Apple-converted-space">&nbsp;</span>&gt; First of =
all, I am kind of new and still learning how email<br class=3D"">&nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span>&gt; =
infrastructure fits in, so please feel free to highlight any glaring<br =
class=3D"">&nbsp; &nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span>&gt; issues with my =
logic.<br class=3D""><br class=3D"">&nbsp; &nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span>&gt; I was working on =
implementing Email Delegation for my email server, and<br =
class=3D"">&nbsp; &nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span>&gt; felt a need to =
highlight a couple of things.<br class=3D""><br class=3D"">&nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span>&gt; 1.) I =
could not find a place where this workflow is outlined. It seems<br =
class=3D"">&nbsp; &nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span>&gt; like everyone, from =
Microsoft to Google, have an implementation for<br class=3D"">&nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span>&gt; email =
delegation, and they are all kind of doing their own thing.<br =
class=3D""><br class=3D""></span>I think that when you say "email =
delegation", you mean where a manager<br class=3D"">(or other person) =
authorizes their "PA" (personal assistant, formerly known<br class=3D"">as=
 "secretary") to send email on their behalf.&nbsp; Back in the days of =
BNR COCOS<br class=3D"">it was very common thing for middle management, =
but even in those dark days<br class=3D"">of mainframe based email, it =
was usually accomplished by having the PA log in<br class=3D"">with the =
manager's email.<br class=3D""><br class=3D"">It's good that =
microsoft(outlook) and google(gmail) have realized that<br =
class=3D"">sharing passwords is a dumb thing.&nbsp; I think that in the =
walled gardens of<br class=3D"">those systems, that the email delegation =
is accomplished entirely within<br class=3D"">their MUA/MTA.<br =
class=3D""></blockquote><div class=3D""><br class=3D"">Exactly!! That is =
the workflow I am talking about. However, I feel that this could be =
something which could be used for other things as well, for example, in =
the place where I work, we have some automated tools where a user can =
input certain data and the tool will send mails to our group email =
address on behalf of the user.<br class=3D""><br class=3D""></div><div =
class=3D"">Couple of terms:<br class=3D""><b class=3D""><br =
class=3D"">manager</b><span class=3D"Apple-converted-space">&nbsp;</span>=3D=
 The user who wants to delegate some other user to manage his account on =
his behalf.<b class=3D""><br =
class=3D""></b></div></div></div></blockquote><div><br class=3D""></div>I =
think =E2=80=9Cprincipal=E2=80=9D is a better term. I would expect =
=E2=80=9Cmanager=E2=80=9D to authorize b to manage on behalf of c.<br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"gmail_quote" style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;"><div class=3D""><p class=3D""><b =
class=3D"">delegate</b><span =
class=3D"Apple-converted-space">&nbsp;</span>=3D The user who has to get =
access to the manager's account.&nbsp;</p><p class=3D""><b =
class=3D"">entity<span class=3D"Apple-converted-space">&nbsp;</span></b>=3D=
 Any email user.<br class=3D""></p>Please note that email delegation =
could also cover cases like creating folders, deleting folders etc in =
the manager's account.<br class=3D""><br class=3D""><br =
class=3D""></div><div class=3D"">This concept, in my opinion, could be =
generalized to include "entities" which could request permission to send =
mails on behalf of some other "entity". Sort of like OAUTH with emails, =
if you will. I am still hazy with all the details and not sure about how =
useful this could be, but it seems promising to me.<br class=3D""><br =
class=3D""></div><div class=3D"">Another question which I was not clear =
about was how S/MIME would be integrated with delegation. For example, =
suppose the delegate were to create a signed email on behalf of the =
manager, in which case the manager would have to share his private key =
with the delegate. This would definitely not be secure.<br =
class=3D""></div></div></div></blockquote><div><br =
class=3D""></div></div><div class=3D"">This is part of a wider issue. =
Even without delegation, if I use my own email account with several MUAs =
(say, my laptop and my phone), where is the private key stored? &nbsp;Is =
it shared between laptop and phone?</div><div class=3D""><br =
class=3D""></div><div class=3D"">You end up reading encrypted mail only =
using one MUA, which is one more thing dragging the use of S/Mime =
down.</div><div class=3D""><br class=3D""></div><div class=3D"">While it =
may be OK to share a key with my phone (but too difficult to do securely =
in practice), sharing with a delegate is hairy on many different layers. =
But still it=E2=80=99s the same issue.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Yoav</div></body></html>=

--Apple-Mail=_D8D01DC4-820B-4ED3-9D86-D22F03774C4F--

--Apple-Mail=_996EF6F4-E6F8-4F15-B761-99DA31C23DD5
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJZaNg7AAoJELhJCxUKWMyZtv4H/1lwMvVBKsrYJqcKbfwDVed7
6BtxMrOHcoHG7zzaWVInx0jl8rCf/s53E8vtfZY+DMX3QWt7VhITK1/DAn+ao+CE
7eSDu9EkDhN6iYBezR6CXt4/KjJfhgA0hvT8aO9Kp5hzxRytSuFxZhmGiJy8yNoW
u1Yuy8K1uefbDFeVDtDrv4Kr59zvQHVXDiC74rcaM5eqZrhQzevf3l88slCs1R2l
YBgmkEc3M3xBzawqYUq99KlX7TO7bDc9IZ0NHZPQRxjiMWNYvpQV9CUJnSj41DpV
mPw8fIzCnE/1ChcQnbjS1FoU6br6Tpt7lc20LflqU/3isblbF8gSLgN5NPejAeM=
=+7rA
-----END PGP SIGNATURE-----

--Apple-Mail=_996EF6F4-E6F8-4F15-B761-99DA31C23DD5--


From nobody Fri Jul 14 15:36:18 2017
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB027129B62 for <ietf@ietfa.amsl.com>; Fri, 14 Jul 2017 15:36:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 1XKwmuFTX83V for <ietf@ietfa.amsl.com>; Fri, 14 Jul 2017 15:36:15 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 508DC126DEE for <ietf@ietf.org>; Fri, 14 Jul 2017 15:36:15 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [IPv6:2001:0:53aa:64c:38f3:78e2:a18e:b3f3]) by relay.sandelman.ca (Postfix) with ESMTPS id 24CA81F8FB; Fri, 14 Jul 2017 22:36:12 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id BD23C27F8; Sat, 15 Jul 2017 00:36:06 +0200 (CEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Yoav Nir <ynir.ietf@gmail.com>
cc: vaibhav singh <vaibhavsinghacads@gmail.com>, ietf@ietf.org
Subject: Re: Need for secured email delegation workflow
In-reply-to: <62FDB3A5-C71A-4B5C-8CD9-94B0EE4DC313@gmail.com>
References: <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com> <28827.1499886723@dooku.sandelman.ca> <CACZ1GiqmFTzD346x02_gvvFqfm1n-N=xBC01xb0_mEpUa_JYUA@mail.gmail.com> <62FDB3A5-C71A-4B5C-8CD9-94B0EE4DC313@gmail.com>
Comments: In-reply-to Yoav Nir <ynir.ietf@gmail.com> message dated "Fri, 14 Jul 2017 17:42:03 +0300."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Sat, 15 Jul 2017 00:36:06 +0200
Message-ID: <13500.1500071766@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FKOvewEhvihmZyWie_9xTZzAUIA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jul 2017 22:36:17 -0000

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable


Yoav Nir <ynir.ietf@gmail.com> wrote:
    > This is part of a wider issue. Even without delegation, if I use my o=
wn
    > email account with several MUAs (say, my laptop and my phone), where =
is
    > the private key stored? Is it shared between laptop and phone?

I think that simple delegation would be a better tool to delegate email
access from my desktop to my phone and/or laptop.  That way the server
knows it's an anciliary device, it could be revoked easier, and a more
suspicious profile could be applied by servers.   Google has tried to
do this with the "App passwords", but my understanding is that they still
not restricted to specific apps.  Just additional passwords that have
most access, but not password resetting access.

OpenPGP format permits a (public) key blog on contain many signing (sub)key=
s,
and so distributing a public key with a set of subkeys where the private
keys are stored into laptops and phones, etc. would work.

    > You end up reading encrypted mail only using one MUA, which is one mo=
re
    > thing dragging the use of S/Mime down.

Agreed; I'm not sure if PKIX has a subkey concept.  I suspect it's in a
standard, but I'm unclear if it was ever deployed.

=2D-=20
]               Never tell me the odds!                 | ipv6 mesh network=
s [=20
]   Michael Richardson, Sandelman Software Works        | network architect=
  [=20
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [=20
=09


--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJZaUdWAAoJEJVM4Vb9/EKQmR4IAKOS4fD8h3JYl7HsO1b20EUZ
8Nuqkv3JNNigD8xrS3ojZzOYAawtsTtPh9hOmPpLTgK9+Y1BhHeTQqrvm13PqwNt
J+KAgB/0gOYpcfp0dy2fOkzU33weZY2q8eq+rf++1sYwQJX2iaax/Ole3qvZRXkj
Isd8fzENYTf8GwlcJB3LfwSV8x12SOkYP/OsYA8TEHok/O4r8WixAnQChtpmJj7u
6XMexV3EUbnkozcP/HHTURGaao9RkzfHSTHJQKoQegJiDiLvjs5xmZpgLrr2+1W8
CJkBl9litChzsoxuSPnwflG8yCjyKKGdCgJ0Sx0kliVZsZVZK7AWnEM98IJdqY8=
=B46P
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Jul 14 16:54:17 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A51F12ECC1 for <ietf@ietfa.amsl.com>; Fri, 14 Jul 2017 16:54:16 -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, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=opendkim.org header.b=xacSWf7Q; dkim=pass (1024-bit key) header.d=elandsys.com header.b=tjdsjTXc
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 JuyqlPheMKH1 for <ietf@ietfa.amsl.com>; Fri, 14 Jul 2017 16:54:15 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6022D12EC25 for <ietf@ietf.org>; Fri, 14 Jul 2017 16:54:15 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.48.246]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id v6ENrtaY027046 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 14 Jul 2017 16:54:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1500076446; x=1500162846; bh=1NyDU+lWg4eAkUlxhOfTN4wg2/8Lmb6WjHmZ1gD5b68=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=xacSWf7QvPJZQS0Klv6FdjJ+7vnGRXHn5VX5Tf2VIu34yYiES7Ee2zIT/Kf3OqHUF oZ9MVW2u6nWgp4Y83Y7G5y53yf1dHUgI5ck17rr8K4gE1kCnAAlmOhESkbU/sp6IXG O9Nhq9DD7kuxxZ5NVPG3CIBVmeRwY1SHxpViRK7w=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1500076446; x=1500162846; i=@elandsys.com; bh=1NyDU+lWg4eAkUlxhOfTN4wg2/8Lmb6WjHmZ1gD5b68=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=tjdsjTXc2LHCI8Qjut9OcsVgFaN/s/J8fs+MlKQ0z4DaaK8rwQIrd3OTyvR6sAsNY aVsOntHzjB+zr4MLhRda7+PvqXWD4V2f0nPQ6iaNfA7qG7WxUryqCGm9BcL9hjumm1 4QVwE/CGYwD/JhkK0A61nEs3btu9RgW+nsHb0mq4=
Message-Id: <6.2.5.6.2.20170714165131.0ccffed0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 14 Jul 2017 16:53:25 -0700
To: vaibhav singh <vaibhavsinghacads@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Need for secured email delegation workflow
Cc: ietf@ietf.org
In-Reply-To: <CACZ1GioxHKVxduAMYJ5qv81Osgpi9fDdHxVRLETSotSPQCD-6w@mail.g mail.com>
References: <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com> <20170712162958.3037.qmail@ary.lan> <CACZ1GioxHKVxduAMYJ5qv81Osgpi9fDdHxVRLETSotSPQCD-6w@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dBM90mdOBMv4HTh6hlaXhC0i17w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jul 2017 23:54:16 -0000

Hi Vaibhav,
At 21:08 13-07-2017, vaibhav singh wrote:
>First of all, sorry for not defining things properly. I will be 
>adding this glossary to all Email Delegation threads:
>
>Definition: Email Delegation will be the workflow in which a user is 
>able to send emails on behalf of another user. A general example 
>will be a secretary replying back to emails which his/her boss received.

Please see Section 3.6.2 of RFC 5322

Regards,
S. Moonesamy 


From nobody Sat Jul 15 01:24:11 2017
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0488131B34 for <ietf@ietfa.amsl.com>; Sat, 15 Jul 2017 01:24:09 -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, 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 TFGm-ckQcH07 for <ietf@ietfa.amsl.com>; Sat, 15 Jul 2017 01:24:08 -0700 (PDT)
Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (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 53A40131B03 for <ietf@ietf.org>; Sat, 15 Jul 2017 01:24:08 -0700 (PDT)
Received: by mail-wm0-x244.google.com with SMTP id 15so2514183wmm.3 for <ietf@ietf.org>; Sat, 15 Jul 2017 01:24:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=eifIpx5OOwPXrdcFwTR5PVt38Iv3PrNZlLlmA03EtWE=; b=E/tSm43i+WUgdfCe/kW9/WwZQ2udLhp6afLRx/YSTXCE6yIg1p90PSyjdT+GsllvFr 9I0JfJWxBaiZL6ZFVtWUS014AUgqsE1sibGexYQv6Ih+rzdbnG28cSeRvph99bmH6vR1 vb8FdKKWxAZQ70HCX2kZR3pjvY7qZLLaoDYh5BOLmIJM/LIMesrzm8KUNOpEcLOOfGe+ YRbbha64+y6n3VRajra270DRzf8Rnvt4ygMw+gtvh1ldz1pxX9+e13KfjdsFBQhSoxvx 70d5ThYCWMiGGmcf8Yyqx1Ej87KMtTp3P3JGwe5PkLsogflohE+YjPwnQu/49CRgOm4t 96Aw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=eifIpx5OOwPXrdcFwTR5PVt38Iv3PrNZlLlmA03EtWE=; b=B27I4SFSUJc+OYb/y/Ea6XqPgq9vCU3eShBCkakwkgutshyO/80GkacCPPZjTCZ0O5 qj7InwugjQnVUBH03c37d1xndUNt8bVJ1ukA+bmAEyYp/CzTyCAQDrGUGrcmuea+yscf 8mI0O+N8CBIQClKoTyStel6L7FUYKSr+Q++cZbYD5Of/PAe4TOs3rty1NG1TWCEA53IY EL2JIh/N13YoKlAm8WV4Okz++Gf8JMjnGNzN5SFJFb/lKcn7cuO3y9GyEXUEHZO+daoW 4BfJpMsSlacUSAcLIbJQf/inEbZxb/O5+fDB1Ds+We3wuQXYynVUtfFz+NQ70O/yv1ZJ wfCw==
X-Gm-Message-State: AIVw113v0NSd0gyoAdGvBTo+0ufUKjwwxokm+b2tUWZlepCssTzeO8lY s+0Te3Z0sdAe1q7Npqc=
X-Received: by 10.80.150.196 with SMTP id z4mr9886978eda.184.1500107046921; Sat, 15 Jul 2017 01:24:06 -0700 (PDT)
Received: from [192.168.1.18] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id p49sm6426093edc.47.2017.07.15.01.24.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 15 Jul 2017 01:24:06 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <44A73F74-FA30-4ACB-A4DE-849650FD809C@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_6A35A55D-B71C-4F6B-A3F9-6A4BDFD33640"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Need for secured email delegation workflow
Date: Sat, 15 Jul 2017 11:24:04 +0300
In-Reply-To: <13500.1500071766@dooku.sandelman.ca>
Cc: vaibhav singh <vaibhavsinghacads@gmail.com>, ietf@ietf.org
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com> <28827.1499886723@dooku.sandelman.ca> <CACZ1GiqmFTzD346x02_gvvFqfm1n-N=xBC01xb0_mEpUa_JYUA@mail.gmail.com> <62FDB3A5-C71A-4B5C-8CD9-94B0EE4DC313@gmail.com> <13500.1500071766@dooku.sandelman.ca>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7eEkdMnTWm58aJiMKr_Lh-I4rX4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Jul 2017 08:24:10 -0000

--Apple-Mail=_6A35A55D-B71C-4F6B-A3F9-6A4BDFD33640
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On 15 Jul 2017, at 1:36, Michael Richardson <mcr+ietf@sandelman.ca> =
wrote:
>=20
>=20
> Yoav Nir <ynir.ietf@gmail.com> wrote:
>> This is part of a wider issue. Even without delegation, if I use my =
own
>> email account with several MUAs (say, my laptop and my phone), where =
is
>> the private key stored? Is it shared between laptop and phone?
>=20
> I think that simple delegation would be a better tool to delegate =
email
> access from my desktop to my phone and/or laptop.  That way the server
> knows it's an anciliary device, it could be revoked easier, and a more
> suspicious profile could be applied by servers.   Google has tried to
> do this with the "App passwords", but my understanding is that they =
still
> not restricted to specific apps.  Just additional passwords that have
> most access, but not password resetting access.
>=20
> OpenPGP format permits a (public) key blog on contain many signing =
(sub)keys,
> and so distributing a public key with a set of subkeys where the =
private
> keys are stored into laptops and phones, etc. would work.
>=20
>> You end up reading encrypted mail only using one MUA, which is one =
more
>> thing dragging the use of S/Mime down.
>=20
> Agreed; I'm not sure if PKIX has a subkey concept.  I suspect it's in =
a
> standard, but I'm unclear if it was ever deployed.

That works OK for signatures, but for encryption?  You=E2=80=99d have to =
encrypt the message with each subkey.  Yeah, I know only the symmetric =
key gets encrypted but it=E2=80=99s still ugly.

And we haven=E2=80=99t even mentioned the web MUA and where it stores =
the private keys.

--Apple-Mail=_6A35A55D-B71C-4F6B-A3F9-6A4BDFD33640
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJZadEkAAoJELhJCxUKWMyZvuYH+QF8ml5XvXJVx9mk1jNaYuhc
pVHZrKVd+WhD8NCfDtumtjGR9IO1vJRVdyqoT9Ki+2JycaYTvJBs8xgMoPrCJeKc
FfYrKaRha3GWXxXuz3m1k/IdIk1uB9rXLGMCXWUiBL/q+gdcmMmRiyDGZfTCfAVI
6ORgzlqUqywmqctuK+AYXUBvUkCKqSw2bmCWe4LGBh1nLWx0oD/HIVN8dKk2dSXz
ymKNPGxoG0wuc7jqB/0E91IxtUYG7Ov0yL9QmTtlnWCNql2DrMMXcLs2jaZjyx2j
lG9iXKG2P9usBAnXyZR41MECdN5ZH3cEPgJvNb0qKiY0AAFRd5FBp360AT7vPFY=
=1c7Q
-----END PGP SIGNATURE-----

--Apple-Mail=_6A35A55D-B71C-4F6B-A3F9-6A4BDFD33640--


From nobody Sat Jul 15 01:28:35 2017
Return-Path: <aaron.falk@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 392CA131B45; Sat, 15 Jul 2017 01:28:26 -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, 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 Tw-Mqf-P7C2S; Sat, 15 Jul 2017 01:28:24 -0700 (PDT)
Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (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 1FBC0131AD7; Sat, 15 Jul 2017 01:28:24 -0700 (PDT)
Received: by mail-wm0-x244.google.com with SMTP id 15so2526441wmm.3; Sat, 15 Jul 2017 01:28:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:subject:date:message-id:in-reply-to:references:mime-version;  bh=8tQKnVMrTFdM8BeevSw+lUYdImqvd6BLR6UTRE6YG8U=; b=dU9sOqnPzdL7M1CdPaFR/Jit0xsXWvpRzgYzsJ8XBTHchnvnkkccfy6kYhtIri75yb OVvSgkMRyv4HRP17k9zDzShCPWtKXAXmN/TBx5qePQvpIKfQWILR5NUhaI/pZWgJt8Bu XzlSfpAE4PUdMwODy5/b6HFdJjdm+R25fQDhR3Yd3ngfKS9aPhT2IIyW/3Gg5uDYPdw/ ef4MYvpqopuaOevZ2KPf4qTmUkE9eIe4rWrZh5eGhYkveTyLWUFVnrsc++DuIarb19z7 YZJHnJQRUNjNTvxu40+QSKFqX2VN5qtA6YQvLtoKdVbpL3jsATz4J7Gd9YSPJcqwB3z7 MeFQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:in-reply-to :references:mime-version; bh=8tQKnVMrTFdM8BeevSw+lUYdImqvd6BLR6UTRE6YG8U=; b=f+jPBGRPvJTblGLai8ky1kdWXrFiTBpuIcHAn2PGlHV4mNXIMp9fZihuaC4tBcv6HG kk0UgaXuN/IZksBBVaqaY5NDl0Tor2Mst7LNsgckLztcsfQH+JKdD2R5qOApEyX2BN9j EXl/zudJwk/UjDosdXcumK5z0JBAjay4jLVFkZXLAg+xcGCukEUW/h2yzo6ZVVr+0vB3 J+aH+X1+KGf8sHqQTtg8iSW93BerfC9pePUvDeKlSCqWUdmbLu/z5vXJM02LUAB3kRfa SWaB0E7cat/jQbfOVgz/wlovkGerv9P5tSw9JXhIyNXMHjgw4Q+XbBDwxjuqwzpkfzYO scQw==
X-Gm-Message-State: AIVw110OaDvdyOJHbARf6hIDdPag3aay5XolXaDDqSVJI4g+cvXOafHR Cn0wQv0xKPm+k2HTyEU=
X-Received: by 10.28.136.129 with SMTP id k123mr422459wmd.14.1500107302312; Sat, 15 Jul 2017 01:28:22 -0700 (PDT)
Received: from [172.19.152.118] ([2001:67c:370:128:2de7:b6d8:805a:fbe9]) by smtp.gmail.com with ESMTPSA id w30sm11813610wrb.49.2017.07.15.01.28.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 15 Jul 2017 01:28:20 -0700 (PDT)
From: "Aaron Falk" <aaron.falk@gmail.com>
To: ietf@ietf.org, "99attendees@ietf.org" <99attendees@ietf.org>
Subject: Re: PechaKucha presenters for Prague?
Date: Sat, 15 Jul 2017 10:28:19 +0200
Message-ID: <B798D8A8-4FCF-4C1C-9DE9-FCDD9A86F187@gmail.com>
In-Reply-To: <7B789905-2EB2-4650-B085-BE39F3E048ED@gmail.com>
References: <D53C2422-8C47-4E42-B5AF-9A263FB89730@gmail.com> <F11AED30-9781-409D-89BD-BB676BB2E371@gmail.com> <7B789905-2EB2-4650-B085-BE39F3E048ED@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_2889875C-D894-42A9-AB36-84B60A70169A_="
X-Mailer: MailMate (1.9.6r5356)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/q_gtG1Q9_KrZVCBLEOKR4LI98JE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Jul 2017 08:28:26 -0000

--=_MailMate_2889875C-D894-42A9-AB36-84B60A70169A_=
Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown
Content-Transfer-Encoding: quoted-printable

Last call for participation.  Please let me know ASAP if you want to =

present at the Thursday evening event.

=E2=80=94aaron

On 5 Jul 2017, at 17:08, Aaron Falk wrote:

> We=E2=80=99ve hit critical mass and the event is ON!  Logistics TBA.  S=
till =

> room for more presenters, should you be interested.  Email me with =

> your interest and a working title to grab a slot.
>
> =E2=80=94aaron
>
> On 3 Jul 2017, at 14:06, Aaron Falk wrote:
>
>> I have five folks signed up.  IMO, that seems to be right on the cusp =

>> of making it worth the effort to hold the event.  Anyone else want to =

>> step up?
>>
>> On 21 Jun 2017, at 18:09, Aaron Falk wrote:
>>
>>> This is a poll for folks who are interested in presenting at a =

>>> PechaKucha in Prague.  The number of folks presenting has declined =

>>> slightly and I=E2=80=99m contemplating whether holding a session at e=
very =

>>> IETF meeting is too frequent.  If I don=E2=80=99t hear from enough fo=
lks =

>>> we=E2=80=99ll wait until Singapore to do the next one.  In other word=
s, if =

>>> you want to give a talk, please send me a note ASAP.
>>>
>>> Standard invitation and background info below.
>>>
>>> Thanks!
>>>
>>> =E2=80=94aaron
>>>
>>> ____
>>>
>>> A Pecha Kucha is a lightning-talk presentation format, originating =

>>> in Japan, where a speaker presents 20 image-only slides that are =

>>> each on the screen for 20 seconds and advance automatically.  With =

>>> each talk lasting for 6:40, it has the feature of forcing =

>>> presentations -- good or bad -- to be focused and brief.  This is an =

>>> unofficial event. Topics are encouraged to be a IETF-related and =

>>> satirical or controversial in some way, although not mean-spirited.  =

>>> Anyone can participate in this social event.  Video from the Berlin, =

>>> Seoul, and Chicago PKs can be found =

>>> [here](http://snaggletooth.akam.ai).
>>>
>>> Format Details:
>>>
>>> * Presentation slots are open to all, assigned first come, first =

>>> served.
>>> * To reserve a presentation slot, send a name and title to =

>>> aaron.falk@gmail.com and receive confirmation.
>>> * Presenters must agree to adhere to the Pecha Kucha format (20 =

>>> slides, primarily image-only, automatically advancing every 20 =

>>> seconds).
>>> * There are lots of online tutorials and suggestions for how to make =

>>> a good Pecha Kucha.  Here are a few: =

>>> [[1](http://www.pechakucha.org/)], =

>>> [[2](http://blog.indezine.com/2012/05/10-tips-to-create-and-present-p=
echa.html)], =

>>> [[3](https://catherinecronin.wordpress.com/2012/06/13/pecha-kucha/)].=


--=_MailMate_2889875C-D894-42A9-AB36-84B60A70169A_=
Content-Type: text/html; charset=utf-8
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">Last call for participation.  Please let me know ASAP if =
you want to present at the Thursday evening event.</p>

<p dir=3D"auto">=E2=80=94aaron</p>

<p dir=3D"auto">On 5 Jul 2017, at 17:08, Aaron Falk wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<p dir=3D"auto">We=E2=80=99ve hit critical mass and the event is ON!  Log=
istics TBA.  Still room for more presenters, should you be interested.  E=
mail me with your interest and a working title to grab a slot.</p>

<p dir=3D"auto">=E2=80=94aaron</p>

<p dir=3D"auto">On 3 Jul 2017, at 14:06, Aaron Falk wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#999; margin:0 0 5=
px; padding-left:5px; border-left-color:#999">
<p dir=3D"auto">I have five folks signed up.  IMO, that seems to be right=
 on the cusp of making it worth the effort to hold the event.  Anyone els=
e want to step up?</p>

<p dir=3D"auto">On 21 Jun 2017, at 18:09, Aaron Falk wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB">
<p dir=3D"auto">This is a poll for folks who are interested in presenting=
 at a PechaKucha in Prague.  The number of folks presenting has declined =
slightly and I=E2=80=99m contemplating whether holding a session at every=
 IETF meeting is too frequent.  If I don=E2=80=99t hear from enough folks=
 we=E2=80=99ll wait until Singapore to do the next one.  In other words, =
if you want to give a talk, please send me a note ASAP.</p>

<p dir=3D"auto">Standard invitation and background info below.</p>

<p dir=3D"auto">Thanks!</p>

<p dir=3D"auto">=E2=80=94aaron</p>

<hr style=3D"background:#333; background-image:linear-gradient(to right, =
#ccc, #333, #ccc); border:0; height:1px" height=3D"1">

<p dir=3D"auto">A Pecha Kucha is a lightning-talk presentation format, or=
iginating in Japan, where a speaker presents 20 image-only slides that ar=
e each on the screen for 20 seconds and advance automatically.  With each=
 talk lasting for 6:40, it has the feature of forcing presentations -- go=
od or bad -- to be focused and brief.  This is an unofficial event. Topic=
s are encouraged to be a IETF-related and satirical or controversial in s=
ome way, although not mean-spirited.  Anyone can participate in this soci=
al event.  Video from the Berlin, Seoul, and Chicago PKs can be found <a =
href=3D"http://snaggletooth.akam.ai" style=3D"color:#BBB">here</a>.</p>

<p dir=3D"auto">Format Details:</p>

<ul>
<li>Presentation slots are open to all, assigned first come, first served=
=2E</li>
<li>To reserve a presentation slot, send a name and title to <a href=3D"m=
ailto:aaron.falk@gmail.com" style=3D"color:#BBB">aaron.falk@gmail.com</a>=
 and receive confirmation.</li>
<li>Presenters must agree to adhere to the Pecha Kucha format (20 slides,=
 primarily image-only, automatically advancing every 20 seconds).</li>
<li>There are lots of online tutorials and suggestions for how to make a =
good Pecha Kucha.  Here are a few: [<a href=3D"http://www.pechakucha.org/=
" style=3D"color:#BBB">1</a>], [<a href=3D"http://blog.indezine.com/2012/=
05/10-tips-to-create-and-present-pecha.html" style=3D"color:#BBB">2</a>],=
 [<a href=3D"https://catherinecronin.wordpress.com/2012/06/13/pecha-kucha=
/" style=3D"color:#BBB">3</a>].</li>
</ul>
</blockquote>
</blockquote>
</blockquote>
</div>
</div>
</body>
</html>

--=_MailMate_2889875C-D894-42A9-AB36-84B60A70169A_=--


From nobody Sat Jul 15 02:21:17 2017
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2247131B43 for <ietf@ietfa.amsl.com>; Sat, 15 Jul 2017 02:21:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 PJYGp9GSURos for <ietf@ietfa.amsl.com>; Sat, 15 Jul 2017 02:21:14 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B0FB12714F for <ietf@ietf.org>; Sat, 15 Jul 2017 02:21:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 738B03004BC for <ietf@ietf.org>; Sat, 15 Jul 2017 05:21:13 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id h30cXXS4A3SS for <ietf@ietf.org>; Sat, 15 Jul 2017 05:21:12 -0400 (EDT)
Received: from dhcp-88c4.meeting.ietf.org (dhcp-88c4.meeting.ietf.org [31.133.136.196]) by mail.smeinc.net (Postfix) with ESMTPSA id EC0FA300258 for <ietf@ietf.org>; Sat, 15 Jul 2017 05:21:11 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Revamp of the www.ietf.org website
Message-Id: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com>
Date: Sat, 15 Jul 2017 05:21:10 -0400
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bWB2xpxT-WbcuhBBl6Hbrg2juoY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Jul 2017 09:21:16 -0000

I am pleased to report that there has been a lot of progress on the =
project to revamp of the www.ietf.org website. The updated website will =
be the =E2=80=9Cfront door=E2=80=9D for the IETF, not only for for =
active IETF participants, but also provides an onramp for potential =
participants, and helps explain the work of the IETF to people who are =
not directly involved in developing Internet standards. The complete =
Scope of Work for the project is available at:

   https://iaoc.ietf.org/documents/IETF-Website-SOW-20140604-Final.pdf

Based on recent feedback, including the demo table at IETF 98, the =
initial design and features of the website have been improved in many =
ways. For example, in response to the feedback provided, there is now a =
single page that provides links to tools and resources commonly used by =
active IETF participants.

The project is now entering the next phase of the website development. =
The goal for this phase is to gather input more broadly. While there are =
still a few features to be implemented and some content still needs to =
be fine tuned, the general organization and the look-and-feel of the =
website has been implemented based on the initial research and input =
received to date. Of course, there will be some additional significant =
work before the site is ready for production; for example, before the =
website is final, we will implement methods to ensure that well-known =
URLs continue to work as expected.=20

The site is now accessible at:

   https://beta.ietf.org

Please take a look. We will be tracking issues that need addressing at:

   https://github.com/ietf/www.ietf.org/issues

Feedback can also be emailed directly to: webmaster@ietf.org

At IETF 99 in Prague, there will be a table near meeting registration to =
demonstrate the beta website with =E2=80=9Coffice hours" posted on a =
sign by the table. Please stop by if you are in Prague!  The office =
hours will be at least:

   Monday, July 17, 08:30-09:30 and 17:15-17:45

   Tuesday, July 18, 08:30-09:30

   Wednesday, July 19, 08:30-9:30

   Friday, July 12, 08:30-9:30

Thanks,
Russ Housley
IETF Website Revamp Project Manager=


From nobody Sat Jul 15 03:08:10 2017
Return-Path: <prvs=1369649c89=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADE1B131451 for <ietf@ietfa.amsl.com>; Sat, 15 Jul 2017 03:08:08 -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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
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 uLAvrexbzJz4 for <ietf@ietfa.amsl.com>; Sat, 15 Jul 2017 03:08:06 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35C0A126CD8 for <ietf@ietf.org>; Sat, 15 Jul 2017 03:08:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1500113284; x=1500718084; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=aNS3wmM4fZroiyR8QI9CqLWHU ukUvl7rN6RmITXU+ys=; b=CSq4L1B3KusWRw6tnPfmt6UcME+WqTOumkdbYMmLp R7kx143zsAWDeE64/A6R6368mxB/yep2PO+X8GQMyWGO+FgCS6yGyf9CsykYRoAK PWZ0cA5771KaEAtFJwZHPncJZFRzHxl1xMoVZv04V8oUdoMUQWanLF0jVejOTipe ZQ=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=htlFwKQLeszh6B+UhiZZ8oxxeZ6jpX0tEeQLQYCJ3eUlRlkCz+gYSuRtWmGK sP1dPR80aZs5xg/mADgYmu79gPpSUrRhIl+Yzu5exSxl3MH7MF/JGS58j ZUVV9HJUApqCoFZkRwySfdwcg3FKr0AZjyHhgkv8bRdM72k0dFU4oA=;
X-MDAV-Processed: mail.consulintel.es, Sat, 15 Jul 2017 12:08:04 +0200
X-Spam-Processed: mail.consulintel.es, Sat, 15 Jul 2017 12:08:03 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005476708.msg for <ietf@ietf.org>; Sat, 15 Jul 2017 12:08:02 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170715:md50005476708::8WtylGonmM0z1kgz:000038XG
X-Return-Path: prvs=1369649c89=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.24.0.170702
Date: Sat, 15 Jul 2017 12:08:00 +0200
Subject: Re: Revamp of the www.ietf.org website
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IETF <ietf@ietf.org>
Message-ID: <C1590F40-3B9E-45A0-9B87-59A0271B1952@consulintel.es>
Thread-Topic: Revamp of the www.ietf.org website
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com>
In-Reply-To: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/X0oMYDKhWrcWFzJKZItcJmxsK_o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Jul 2017 10:08:08 -0000

I think a missing aspect of the web site, which should be prominent in both=
 the home page and also the =E2=80=9Ccontact=E2=80=9D page, is all the soci=
al media.

I see there is a =E2=80=9Cshare this page=E2=80=9D at the right of the main=
 picture, but in my opinion, is not clearly visible and is not enough (the =
logos of the social networks should be recognized without needing to pass o=
ver the share this page text, for example, and allow to open a new windows =
to each of the social networks when you click on them).

We need to make sure that we increase our participation in social networks,=
 at least as a way to share news about IETF, contents announced in the anno=
uncements mailing list, etc.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Russ Housley <housley@vigilse=
c.com>
Responder a: <housley@vigilsec.com>
Fecha: s=C3=A1bado, 15 de julio de 2017, 11:21
Para: IETF <ietf@ietf.org>
Asunto: Revamp of the www.ietf.org website

    I am pleased to report that there has been a lot of progress on the pro=
ject to revamp of the www.ietf.org website. The updated website will be the=
 =E2=80=9Cfront door=E2=80=9D for the IETF, not only for for active IETF pa=
rticipants, but also provides an onramp for potential participants, and hel=
ps explain the work of the IETF to people who are not directly involved in =
developing Internet standards. The complete Scope of Work for the project i=
s available at:
   =20
       https://iaoc.ietf.org/documents/IETF-Website-SOW-20140604-Final.pdf
   =20
    Based on recent feedback, including the demo table at IETF 98, the init=
ial design and features of the website have been improved in many ways. For=
 example, in response to the feedback provided, there is now a single page =
that provides links to tools and resources commonly used by active IETF par=
ticipants.
   =20
    The project is now entering the next phase of the website development. =
The goal for this phase is to gather input more broadly. While there are st=
ill a few features to be implemented and some content still needs to be fin=
e tuned, the general organization and the look-and-feel of the website has =
been implemented based on the initial research and input received to date. =
Of course, there will be some additional significant work before the site i=
s ready for production; for example, before the website is final, we will i=
mplement methods to ensure that well-known URLs continue to work as expecte=
d.=20
   =20
    The site is now accessible at:
   =20
       https://beta.ietf.org
   =20
    Please take a look. We will be tracking issues that need addressing at:
   =20
       https://github.com/ietf/www.ietf.org/issues
   =20
    Feedback can also be emailed directly to: webmaster@ietf.org
   =20
    At IETF 99 in Prague, there will be a table near meeting registration t=
o demonstrate the beta website with =E2=80=9Coffice hours" posted on a sign=
 by the table. Please stop by if you are in Prague!  The office hours will =
be at least:
   =20
       Monday, July 17, 08:30-09:30 and 17:15-17:45
   =20
       Tuesday, July 18, 08:30-09:30
   =20
       Wednesday, July 19, 08:30-9:30
   =20
       Friday, July 12, 08:30-9:30
   =20
    Thanks,
    Russ Housley
    IETF Website Revamp Project Manager
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Sat Jul 15 04:03:38 2017
Return-Path: <iab-chair@iab.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 848AF12EC34; Sat, 15 Jul 2017 04:03:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.763
X-Spam-Level: 
X-Spam-Status: No, score=-1.763 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTP_ESCAPED_HOST=1.125, T_KAM_HTML_FONT_INVALID=0.01, 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 y5iEu91w8OjD; Sat, 15 Jul 2017 04:03:34 -0700 (PDT)
Received: from hardie-macbookpro2.roam.corp.google.com (unknown [IPv6:2001:67c:1232:144:64a9:29f9:3f80:5c38]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 10B8512708C; Sat, 15 Jul 2017 04:03:32 -0700 (PDT)
To: ietf-announce@ietf.org, ietf@ietf.org
From: IAB Chair <iab-chair@iab.org>
Subject: IAB report to the community for IETF 99
Message-ID: <10c8c747-39d8-8a19-5298-c24a733eaf09@iab.org>
Date: Sat, 15 Jul 2017 13:03:34 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------0D70F9C830E716A394030CB6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SewaNy91ruiLs0id6zF1ftIlSEw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Jul 2017 11:03:37 -0000

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

Dear colleagues,


Continuing the tradition started by Andrew Sullivan, here is the IAB 
report to the community about our activities.  We hope that this 
information allows you to prepare topics you might want to discuss 
during the upcoming open mic time.  Of course, if you have issues you 
want to discuss by email, feel free to send your comments to 
architecture-discuss@iab.org (our public discussion list) or iab@iab.org 
(to reach just the IAB).


The IAB has a few chartered roles. We confirm the appointments to the 
IESG and perform standards process oversight and handle appeals. We also 
perform architectural oversight (including appointing the IRTF Chair), 
we manage the RFC series and the IETF's relationship with IANA, and we 
handle liaisons and appointments both to ISOC and to other 
organizations. We try to ensure that anything we do is part of one of 
these areas of responsibility, and we try to make sure these are all 
covered.


Here's what we've been doing since our last report at IETF 98.  You can 
find mention of each of these on the IAB pages 
athttps://www.iab.org(where there's more background, too).


First, I’m happy to note that there were no appeals during this period. 
  (Appeals and standards process oversight)


In late March, the IAB published a statement on the registration of 
special use names in the ARPA domain 
<https://www.iab.org/documents/correspondence-reports-documents/2017-2/iab-statement-on-the-registration-of-special-use-names-in-the-arpa-domain/>. 
  This comment focused on the distinction between creating an entry in 
the Special Use Names registry and requesting a delegation within the 
DNS, and it reminded the community that .arpa was an appropriate choice 
for delegations that met the conditions in RFC 3172. (Architecture)


In early May, the IAB provided comments on ICANN’s draft IDN 
implementation guidelines. 
<https://www.icann.org/en/system/files/files/draft-idn-guidelines-03mar17-en.pdf> (Architecture)


In mid-May, the IAB formed a search committee to seek a successor for 
Nevil Brownlee as Independent Series Editor, as documented in RFC 6548. 
  The committee gathered suggestions and comments from the community and 
will be conducting interviews at the Prague IETF. Additional comments 
may be provided to the committee at ise-search18@iab.org. (RFC Series)


Also in mid-May, the IAB held its annual retreat, including some joint 
time with the IESG.  Among the topics the IAB discussed was the upcoming 
set of work on 5g.  Jari Arkko and Jeff Tantsura have written a blog 
post on 5g 
<https://www.ietf.org/blog/2017/06/5g-and-internet-technology/>that 
captures some of the related topics.  The IAB is also a host of a lunch 
meeting on Tuesday of this IETF, where 3GPP colleagues will be available 
to discuss “3GPP & IETF collaboration on 5g”.  Interested folks should 
join us in Congress Hall III or via the remote streams.  Another topic 
from the retreat was a look back at RFC 4084, captured in a blog post on 
the meaning of “Internet Access” 
<https://www.ietf.org/blog/2017/06/what-does-internet-access-mean/>.  As 
that post notes, we’d be happy for any comments on that topic to be sent 
to architecture-discuss@iab.org 
<mailto:architecture-discuss@iab.org>.(Architecture)


Later in May, the IAB sent a Liaison Statement to the Unicode technical 
committee on the relationship of Unicode Technical Standard #39 to IETF 
work 
<https://www.iab.org/documents/correspondence-reports-documents/2017-2/liaison-statement-from-the-iab-to-the-unicode-technical-committee/>. 
  There have since been several informal meetings with Unicode leaders 
on how to encourage increased cooperation between the two groups, and we 
expect to continue to work toward that end over the next year. (Liaisons 
and appointments)


During June, the IAB made three appointments to the Community 
Coordination Group as required by RFC 8090.   Russ Housley and Barry 
Leiba were appointed for two years and  Andrew Sullivan for one year. 
  The IETF representatives then selected Russ as CCG Co-chair, and the 
IAB confirmed him in that post.   We thank each of them for their 
service. (Liaisons and appointments)


A bit later in June, the IAB reappointed Jim Reid to the ICANN Root Zone 
Evolution Review Committee, the appointment being required by RFC 8128. 
  We appreciate Jim’s willingness to serve again.  (Liaisons and 
appointments).


During early July the RSOC program developed  a draft Statement of Work 
for the RFC Series Editor, which will go out for public comment this 
week.  Under the current timeline, the RSOC will make a recommendation 
to the IAB in late September, with the RSE term to begin January 1, 2018 
(RFC Series)


        DOCUMENTS


You can always find the documents the IAB has adopted and is working

on athttps://datatracker.ietf.org/stream/iab.


RFCs published since the last report are:


Coordinating Attack Response at Internet Scale (CARIS) Workshop Report 
<https://tools.ietf.org/html/rfc8073>

Appointment Procedures for the IETF Representatives to the Community 
Coordination Group (CCG) <https://tools.ietf.org/html/rfc8090>


IETF Appointment Procedures for the ICANN Root Zone Evolution Review 
Committee <https://tools.ietf.org/html/rfc8128>


Digital Preservation Considerations for the RFC Series 
<https://tools.ietf.org/html/rfc8153>


Planning for Protocol Adoption and Subsequent Transition 
<https://tools.ietf.org/html/rfc8170>s


There are some workshop reports still in process:


draft-iab-iotsu-workshop-01

    Report from the Internet of Things (IoT) Software Update (IoTSU)

    Workshop 2016 (with the RFC Editor now)

draft-iab-marnew-report-00

    IAB Workshop on Managing Radio Networks in an Encrypted World

    (MaRNEW) Report (undergoing community review)


        PROGRAMS


The IAB organizes its work, for the most part, into programs.  There are 
basically two classes: management programs and architectural programs. 
  The former are how we handle the oversight of various things, and the 
latter are where we do architectural work.  The former are expected to 
last as long as the IAB continues to have that oversight function; the 
latter last until the IAB has come to a conclusion on the relevant group 
of topics or has decided that the topic needs to be reframed.  Programs 
are listed at https://www.iab.org/activities/programs/.  As a general 
rule, each architectural program has a public mailing list, as well as a 
member-specific list.  For subscription instructions, see 
https://www.iab.org/iab-mailing-lists/.


We review these programs periodically.  In the period since our last 
report, the IAB made several personnel changes to recognize the change 
in the composition of the IAB, as well as charter updates to the Stack 
Evolution and  Privacy and Security programs.  The IAB also chose to 
close down the Internationalization program.  This was not because of a 
lack of focus on that topic; rather, the IAB felt the need to reframe 
some of the issues related to Internationalization and identifiers in 
Internet contexts.  For more on that, see the Workshop section below.


The Plenary Planning Program works to arrange a tech plenary topic for 
each meeting that is currently topical, broadly interesting to the IETF 
community as a whole, and for which we can engage interesting speakers. 
When it can't have all three, the IAB does not schedule a tech plenary. 
  Unfortunately, this time we didn't get to all three in time for 
Prague, but the program is already working on an IETF 100 technical plenary.


        WORKSHOPS


In June, the IAB sent out a call for participation in a workshop on 
Internet naming systems that explicitly called out their resolution 
method or context 
<%20https://www.iab.org/2017/06/22/call-for-participation-iab-workshop-on-explicit-internet-naming-systems>. 
  We invite position papers on this topic to be submitted by July 28, 
2017 to ename@iab.org. Decisions on accepted submissions will be made by 
August 11, 2017.  The final logistics for the workshop will be announced 
as soon as possible; some late information on conflicts mean that the 
original date announced will likely change.


Respectfully submitted,


Ted Hardie

for the IAB


--------------0D70F9C830E716A394030CB6
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 bgcolor="#FFFFFF" text="#000000">
    <p>
      <meta http-equiv="content-type" content="text/html; charset=utf-8">
    </p>
    <p>
      <meta charset="utf-8">
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"
        id="docs-internal-guid-fdc1bf80-45e9-add7-c119-2fbd143fb93d"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">Dear
          colleagues,</span></p>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">Continuing
          the tradition started by Andrew Sullivan, here is the IAB
          report to the community about our activities.  We hope that
          this information allows you to prepare topics you might want
          to discuss during the upcoming open mic time.  Of course, if
          you have issues you want to discuss by email, feel free to
          send your comments to <a class="moz-txt-link-abbreviated" href="mailto:architecture-discuss@iab.org">architecture-discuss@iab.org</a> (our public
          discussion list) or <a class="moz-txt-link-abbreviated" href="mailto:iab@iab.org">iab@iab.org</a> (to reach just the IAB).</span></p>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">The
          IAB has a few chartered roles. We confirm the appointments to
          the IESG and perform standards process oversight and handle
          appeals. We also perform architectural oversight (including
          appointing the IRTF Chair), we manage the RFC series and the
          IETF's relationship with IANA, and we handle liaisons and
          appointments both to ISOC and to other organizations. We try
          to ensure that anything we do is part of one of these areas of
          responsibility, and we try to make sure these are all covered.</span></p>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">Here's
          what we've been doing since our last report at IETF 98.  You
          can find mention of each of these on the IAB pages at</span><a
          href="https://www.iab.org" style="text-decoration:none;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
          </span><span
style="font-size:11pt;font-family:Arial;color:#1155cc;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;">https://www.iab.org</span></a><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
          (where there's more background, too).  </span></p>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">First,
          I’m happy to note that there were no appeals during this
          period.  (Appeals and standards process oversight)</span></p>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">In
          late March, the IAB published a statement </span><a
href="https://www.iab.org/documents/correspondence-reports-documents/2017-2/iab-statement-on-the-registration-of-special-use-names-in-the-arpa-domain/"
          style="text-decoration:none;"><span
style="font-size:11pt;font-family:Arial;color:#1155cc;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;">on
            the registration of special use names in the ARPA domain</span></a><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">.
           This comment focused on the distinction between creating an
          entry in the Special Use Names registry and requesting a
          delegation within the DNS, and it reminded the community that
          .arpa was an appropriate choice for delegations that met the
          conditions in RFC 3172. (Architecture)</span></p>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">In
          early May, the IAB provided comments on </span><a
href="https://www.icann.org/en/system/files/files/draft-idn-guidelines-03mar17-en.pdf"
          style="text-decoration:none;"><span
style="font-size:11pt;font-family:Arial;color:#1155cc;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;">ICANN’s
            draft IDN implementation guidelines.</span></a><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
           (Architecture)</span></p>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">In
          mid-May, the IAB formed a search committee to seek a successor
          for Nevil Brownlee as Independent Series Editor, as documented
          in RFC 6548.  The committee gathered suggestions and comments
          from the community and will be conducting interviews at the
          Prague IETF. Additional comments may be provided to the
          committee at <a class="moz-txt-link-abbreviated" href="mailto:ise-search18@iab.org">ise-search18@iab.org</a>. (RFC Series)</span></p>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">Also
          in mid-May, the IAB held its annual retreat, including some
          joint time with the IESG.  Among the topics the IAB discussed
          was the upcoming set of work on 5g.  Jari Arkko and Jeff
          Tantsura have written </span><a
          href="https://www.ietf.org/blog/2017/06/5g-and-internet-technology/"
          style="text-decoration:none;"><span
style="font-size:11pt;font-family:Arial;color:#1155cc;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;">a
            blog post on 5g</span></a><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
          that captures some of the related topics.  The IAB is also a
          host of a lunch meeting on Tuesday of this IETF, where 3GPP
          colleagues will be available to discuss “3GPP &amp; IETF
          collaboration on 5g”.  Interested folks should join us in
          Congress Hall III or via the remote streams.  Another topic
          from the retreat was a look back at RFC 4084, captured in a
          blog post on </span><a
          href="https://www.ietf.org/blog/2017/06/what-does-internet-access-mean/"
          style="text-decoration:none;"><span
style="font-size:11pt;font-family:Arial;color:#1155cc;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;">the
            meaning of “Internet Access”</span></a><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">.
           As that post notes, we’d be happy for any comments on that
          topic to be sent to </span><a
          href="mailto:architecture-discuss@iab.org"
          style="text-decoration:none;"><span
style="font-size:11pt;font-family:Arial;color:#1155cc;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;">architecture-discuss@iab.org</span></a><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
          .(Architecture)</span></p>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">Later
          in May, the IAB sent a Liaison Statement to the Unicode
          technical committee </span><a
href="https://www.iab.org/documents/correspondence-reports-documents/2017-2/liaison-statement-from-the-iab-to-the-unicode-technical-committee/"
          style="text-decoration:none;"><span
style="font-size:11pt;font-family:Arial;color:#1155cc;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;">on
            the relationship of Unicode Technical Standard #39 to IETF
            work</span></a><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">.
           There have since been several informal meetings with Unicode
          leaders on how to encourage increased cooperation between the
          two groups, and we expect to continue to work toward that end
          over the next year. (Liaisons and appointments)</span></p>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">During
          June, the IAB made three appointments to the Community
          Coordination Group as required by RFC 8090.   Russ Housley and
          Barry Leiba were appointed for two years and  Andrew Sullivan
          for one year.  The IETF representatives then selected Russ as
          CCG Co-chair, and the IAB confirmed him in that post.   We
          thank each of them for their service. (Liaisons and
          appointments)</span></p>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">A
          bit later in June, the IAB reappointed Jim Reid to the ICANN
          Root Zone Evolution Review Committee, the appointment being
          required by RFC 8128.  We appreciate Jim’s willingness to
          serve again.  (Liaisons and appointments).</span></p>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">During
          early July the RSOC program developed  a draft Statement of
          Work for the RFC Series Editor, which will go out for public
          comment this week.  Under the current timeline, the RSOC will
          make a recommendation to the IAB in late September, with the
          RSE term to begin January 1, 2018 (RFC Series)</span></p>
      <h4 dir="ltr"
        style="line-height:1.38;margin-top:14pt;margin-bottom:4pt;"><span
style="font-size:12pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">DOCUMENTS</span></h4>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">You
          can always find the documents the IAB has adopted and is
          working</span></p>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">on
          at</span><a href="https://datatracker.ietf.org/stream/iab"
          style="text-decoration:none;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
          </span><span
style="font-size:11pt;font-family:Arial;color:#1155cc;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;">https://datatracker.ietf.org/stream/iab</span></a><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">.</span></p>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">RFCs
          published since the last report are:</span></p>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><a
          href="https://tools.ietf.org/html/rfc8073"
          style="text-decoration:none;"><span
style="font-size:11pt;font-family:Arial;color:#1155cc;background-color:transparent;font-weight:700;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;">Coordinating
            Attack Response at Internet Scale (CARIS) Workshop Report</span></a></p>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
        </span></p>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><a
          href="https://tools.ietf.org/html/rfc8090"
          style="text-decoration:none;"><span
style="font-size:11pt;font-family:Arial;color:#1155cc;background-color:transparent;font-weight:700;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;">Appointment
            Procedures for the IETF Representatives to the Community
            Coordination Group (CCG)</span></a></p>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><a
          href="https://tools.ietf.org/html/rfc8128"
          style="text-decoration:none;"><span
style="font-size:11pt;font-family:Arial;color:#1155cc;background-color:transparent;font-weight:700;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;">IETF
            Appointment Procedures for the ICANN Root Zone Evolution
            Review Committee</span></a></p>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><a
          href="https://tools.ietf.org/html/rfc8153"
          style="text-decoration:none;"><span
style="font-size:11pt;font-family:Arial;color:#1155cc;background-color:transparent;font-weight:700;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;">Digital
            Preservation Considerations for the RFC Series</span></a></p>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><a
          href="https://tools.ietf.org/html/rfc8170"
          style="text-decoration:none;"><span
style="font-size:11pt;font-family:Arial;color:#1155cc;background-color:transparent;font-weight:700;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;">Planning
            for Protocol Adoption and Subsequent Transition</span></a><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:700;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">s</span></p>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">There
          are some workshop reports still in process:</span></p>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">draft-iab-iotsu-workshop-01</span></p>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
             Report from the Internet of Things (IoT) Software Update
          (IoTSU)</span></p>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
             Workshop 2016 (with the RFC Editor now)</span></p>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">draft-iab-marnew-report-00</span></p>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
             IAB Workshop on Managing Radio Networks in an Encrypted
          World</span></p>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
             (MaRNEW) Report (undergoing community review)</span></p>
      <h4 dir="ltr"
        style="line-height:1.38;margin-top:14pt;margin-bottom:4pt;"><span
style="font-size:12pt;font-family:Arial;color:#666666;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
        </span><span
style="font-size:12pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">PROGRAMS</span></h4>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">The
          IAB organizes its work, for the most part, into programs.
           There are basically two classes: management programs and
          architectural programs.  The former are how we handle the
          oversight of various things, and the latter are where we do
          architectural work.  The former are expected to last as long
          as the IAB continues to have that oversight function; the
          latter last until the IAB has come to a conclusion on the
          relevant group of topics or has decided that the topic needs
          to be reframed.  Programs are listed at </span><a
          href="https://www.iab.org/activities/programs/"
          style="text-decoration:none;"><span
style="font-size:11pt;font-family:Arial;color:#1155cc;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;">https://www.iab.org/activities/programs/</span></a><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">.
           As a general rule, each architectural program has a public
          mailing list, as well as a member-specific list.  For
          subscription instructions, see </span><a
          href="https://www.iab.org/iab-mailing-lists/"
          style="text-decoration:none;"><span
style="font-size:11pt;font-family:Arial;color:#1155cc;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;">https://www.iab.org/iab-mailing-lists/</span></a><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">.</span></p>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">We
          review these programs periodically.  In the period since our
          last report, the IAB made several personnel changes to
          recognize the change in the composition of the IAB, as well as
          charter updates to the Stack Evolution and  Privacy and
          Security programs.  The IAB also chose to close down the
          Internationalization program.  This was not because of a lack
          of focus on that topic; rather, the IAB felt the need to
          reframe some of the issues related to Internationalization and
          identifiers in Internet contexts.  For more on that, see the
          Workshop section below.</span></p>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">The
          Plenary Planning Program </span><span
style="font-size:11pt;font-family:Arial;color:#222222;background-color:#ffffff;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">works
          to arrange a tech plenary topic for each meeting that is
          currently topical, broadly interesting to the IETF community
          as a whole, and for which we can engage interesting speakers.
          When it can't have all three, the IAB does not schedule a tech
          plenary.  Unfortunately, this time we didn't get to all three
          in time for Prague, but the program is already working on an
          IETF 100 technical plenary.</span></p>
      <h4 dir="ltr"
        style="line-height:1.38;margin-top:14pt;margin-bottom:4pt;"><span
style="font-size:12pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">WORKSHOPS</span></h4>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">In
          June, the IAB sent out a call for participation in a </span><a
href="%20https://www.iab.org/2017/06/22/call-for-participation-iab-workshop-on-explicit-internet-naming-systems"
          style="text-decoration:none;"><span
style="font-size:11pt;font-family:Arial;color:#1155cc;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;">workshop
            on Internet naming systems that explicitly called out their
            resolution method or context</span></a><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">.
           We invite position papers on this topic to be submitted by
          July 28, 2017 to <a class="moz-txt-link-abbreviated" href="mailto:ename@iab.org">ename@iab.org</a>. Decisions on accepted
          submissions will be made by August 11, 2017.  The final
          logistics for the workshop will be announced as soon as
          possible; some late information on conflicts mean that the
          original date announced will likely change.</span></p>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">Respectfully
          submitted,</span></p>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">Ted
          Hardie</span></p>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">for
          the IAB</span></p>
    </p>
  </body>
</html>

--------------0D70F9C830E716A394030CB6--


From nobody Sat Jul 15 05:01:15 2017
Return-Path: <nordmark@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D33D12EC06 for <ietf@ietfa.amsl.com>; Sat, 15 Jul 2017 05:01:13 -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 Byg5dyVqkkWQ for <ietf@ietfa.amsl.com>; Sat, 15 Jul 2017 05:01:12 -0700 (PDT)
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (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 2273812EB8C for <ietf@ietf.org>; Sat, 15 Jul 2017 05:01:12 -0700 (PDT)
Received: from [31.133.137.43] (dhcp-892b.meeting.ietf.org [31.133.137.43]) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id v6FC155k018786 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 15 Jul 2017 05:01:09 -0700
To: ietf@ietf.org
From: Erik Nordmark <nordmark@acm.org>
Subject: Room available at Hilton
Message-ID: <abfa27c4-3bb3-c27c-7cda-9a1171afa8c6@acm.org>
Date: Sat, 15 Jul 2017 14:01:02 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Sonic-CAuth: UmFuZG9tSVbmVisHuBWvTgYmZUP9vWmiWLn2Mx70454tce/OghToPP2/BvswqUKfSs5h1+qhPO3nkkoEA4aVWOF6geEKRP8Z
X-Sonic-ID: C;vOvvR1Vp5xGMS/sKk0eh0A== M;2gEeSlVp5xGMS/sKk0eh0A==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/J3lrV_loB4C3H-2UvBSb3UNQ5zc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Jul 2017 12:01:13 -0000

I somehow managed to reserve a room twice at the Hilton (a few weeks 
apart) and they didn't tell me until I just checked in.

In someone is still looking for a room please contact me; I'd like to 
avoid paying twice for the whole week which is apparently the 
cancellation requirements.

    Erik


From nobody Sat Jul 15 06:17:16 2017
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BD45131667 for <ietf@ietfa.amsl.com>; Sat, 15 Jul 2017 06:17:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.898
X-Spam-Level: 
X-Spam-Status: No, score=-2.898 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, HTML_MESSAGE=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 ENYz080HTWPf for <ietf@ietfa.amsl.com>; Sat, 15 Jul 2017 06:17:13 -0700 (PDT)
Received: from sjc-alcoop-8816.cisco.com (unknown [128.107.241.183]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 035B512EC36 for <ietf@ietf.org>; Sat, 15 Jul 2017 06:17:12 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9EF4896D-5155-42E3-AEDE-6E8A9CC993C5"
Subject: IETF Chair and IESG Report for IETF 99
Message-Id: <4680DB98-9278-43B5-AE75-106C5648B95E@ietf.org>
Date: Sat, 15 Jul 2017 09:17:11 -0400
To: IETF Discussion <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7JyqGyNkcuEiK73NKoy7qG5tPaw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Jul 2017 13:17:14 -0000

--Apple-Mail=_9EF4896D-5155-42E3-AEDE-6E8A9CC993C5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Before each IETF, the IETF Chair and the IESG publish a brief report of
their activities. This is done to reduce reporting at the plenary.

Here is the report:

=
https://www.ietf.org/proceedings/99/slides/slides-99-ietf-sessb-ietf-chair=
-and-iesg-report-ietf-99-00.pdf =
<https://www.ietf.org/proceedings/99/slides/slides-99-ietf-sessb-ietf-chai=
r-and-iesg-report-ietf-99-00.pdf>

Comments, questions, suggestions, and feedback is always welcome!

Alissa Cooper=20
IETF Chair=

--Apple-Mail=_9EF4896D-5155-42E3-AEDE-6E8A9CC993C5
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Before each IETF, the IETF Chair and the IESG publish a brief report of<br class="">their activities. This is done to reduce reporting at the plenary.<br class=""><br class="">Here is the report:<br class=""><br class=""><a href="https://www.ietf.org/proceedings/99/slides/slides-99-ietf-sessb-ietf-chair-and-iesg-report-ietf-99-00.pdf" class="">https://www.ietf.org/proceedings/99/slides/slides-99-ietf-sessb-ietf-chair-and-iesg-report-ietf-99-00.pdf</a><br class=""><br class="">Comments, questions, suggestions, and feedback is always welcome!<br class=""><br class="">Alissa Cooper&nbsp;<div class="">IETF Chair</div></body></html>
--Apple-Mail=_9EF4896D-5155-42E3-AEDE-6E8A9CC993C5--


From nobody Sat Jul 15 06:19:15 2017
Return-Path: <amorris@amsl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D68E312EC15 for <ietf@ietfa.amsl.com>; Sat, 15 Jul 2017 06:19:13 -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, RP_MATCHES_RCVD=-0.001, 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 zcT0DjBLuYsu for <ietf@ietfa.amsl.com>; Sat, 15 Jul 2017 06:19:12 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADFDC127977 for <ietf@ietf.org>; Sat, 15 Jul 2017 06:19:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 82C561CA566 for <ietf@ietf.org>; Sat, 15 Jul 2017 06:19:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dejlDRTJXQ70 for <ietf@ietf.org>; Sat, 15 Jul 2017 06:19:06 -0700 (PDT)
Received: from [IPv6:2001:67c:370:128:8c77:b139:ccba:a460] (unknown [IPv6:2001:67c:370:128:8c77:b139:ccba:a460]) by c8a.amsl.com (Postfix) with ESMTPSA id 1DC8B1CA547 for <ietf@ietf.org>; Sat, 15 Jul 2017 06:19:05 -0700 (PDT)
From: Alexa Morris <amorris@amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Remote Participant Registration Reopened
Message-Id: <DB2F90BB-32CD-4628-9EC7-D4EDE0E61497@amsl.com>
Date: Sat, 15 Jul 2017 15:19:10 +0200
To: IETF general list <ietf@ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hAEV1U2FNn2VpcY1bYOtrz8QJ-k>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Jul 2017 13:19:14 -0000

Remote participant registration was briefly =E2=80=94 and accidentally =
=E2=80=94 closed but it has now reopened. If you plan to participate =
remotely at IETF 99 you can register here: =
https://ietf.org/meeting/remote-registration.html.=20

Please note that registration is now required for all remote =
participants. There is no fee to participate remotely but you will need =
to enter your registration ID before you will be permitted to join the =
Meetecho session.=20

If you do not want to register as a remote participant you can still =
audit the sessions via the audio streams, which you can access from with =
the meeting agenda: https://datatracker.ietf.org/meeting/agenda/.

Alexa=


From nobody Sat Jul 15 06:49:20 2017
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAEE1131A62 for <ietf@ietfa.amsl.com>; Sat, 15 Jul 2017 06:49:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.898
X-Spam-Level: 
X-Spam-Status: No, score=-2.898 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, HTML_MESSAGE=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 r4GE3f3pTIlP for <ietf@ietfa.amsl.com>; Sat, 15 Jul 2017 06:49:18 -0700 (PDT)
Received: from sjc-alcoop-8816.cisco.com (unknown [128.107.241.183]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 897AA131895 for <ietf@ietf.org>; Sat, 15 Jul 2017 06:49:18 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D6E70447-ADFE-4FCE-9481-5065DEFA68C8"
Subject: IETF 99 Preview
Message-Id: <8789047D-0C2D-4FAC-AAC5-2F575D3B2EF6@ietf.org>
Date: Sat, 15 Jul 2017 09:49:17 -0400
To: IETF Discussion <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AhZZxYmc3xQUUvg_dIDvbS1oFwY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Jul 2017 13:49:19 -0000

--Apple-Mail=_D6E70447-ADFE-4FCE-9481-5065DEFA68C8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I=E2=80=99ve posted a few highlights of sessions to look out for at IETF =
99: https://www.ietf.org/blog/2017/07/ietf-99-preview/ =
<https://www.ietf.org/blog/2017/07/ietf-99-preview/>

Have a great meeting!

Alissa Cooper
IETF Chair=

--Apple-Mail=_D6E70447-ADFE-4FCE-9481-5065DEFA68C8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">I=E2=80=99ve posted a few highlights of sessions to look out =
for at IETF 99:&nbsp;<a =
href=3D"https://www.ietf.org/blog/2017/07/ietf-99-preview/" =
class=3D"">https://www.ietf.org/blog/2017/07/ietf-99-preview/</a><div =
class=3D""><br class=3D""></div><div class=3D"">Have a great =
meeting!</div><div class=3D""><br class=3D""></div><div class=3D"">Alissa =
Cooper</div><div class=3D"">IETF Chair</div></body></html>=

--Apple-Mail=_D6E70447-ADFE-4FCE-9481-5065DEFA68C8--


From nobody Sat Jul 15 06:53:09 2017
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61F0D13170E for <ietf@ietfa.amsl.com>; Sat, 15 Jul 2017 06:53:07 -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 yOBWLf87yFOq for <ietf@ietfa.amsl.com>; Sat, 15 Jul 2017 06:53:05 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72F9012EC37 for <ietf@ietf.org>; Sat, 15 Jul 2017 06:53:05 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [IPv6:2001:0:53aa:64c:28d8:78e2:e07a:7eef]) by relay.sandelman.ca (Postfix) with ESMTPS id 549571F906; Sat, 15 Jul 2017 13:53:03 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 0FB742C5D; Sat, 15 Jul 2017 15:52:50 +0200 (CEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Yoav Nir <ynir.ietf@gmail.com>
cc: vaibhav singh <vaibhavsinghacads@gmail.com>, ietf@ietf.org
Subject: Re: Need for secured email delegation workflow
In-reply-to: <44A73F74-FA30-4ACB-A4DE-849650FD809C@gmail.com>
References: <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com> <28827.1499886723@dooku.sandelman.ca> <CACZ1GiqmFTzD346x02_gvvFqfm1n-N=xBC01xb0_mEpUa_JYUA@mail.gmail.com> <62FDB3A5-C71A-4B5C-8CD9-94B0EE4DC313@gmail.com> <13500.1500071766@dooku.sandelman.ca> <44A73F74-FA30-4ACB-A4DE-849650FD809C@gmail.com>
Comments: In-reply-to Yoav Nir <ynir.ietf@gmail.com> message dated "Sat, 15 Jul 2017 11:24:04 +0300."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Sat, 15 Jul 2017 15:52:50 +0200
Message-ID: <30686.1500126770@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1KVNJPJRWuo9yUkOB7E3NXz7nGE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Jul 2017 13:53:07 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Yoav Nir <ynir.ietf@gmail.com> wrote:
    >> OpenPGP format permits a (public) key blog on contain many signing
    >> (sub)keys, and so distributing a public key with a set of subkeys
    >> where the private keys are stored into laptops and phones, etc. would
    >> work.

    >>> You end up reading encrypted mail only using one MUA, which is one
    >>> more thing dragging the use of S/Mime down.

    >> Agreed; I'm not sure if PKIX has a subkey concept.  I suspect it's in
    >> a standard, but I'm unclear if it was ever deployed.

    > That works OK for signatures, but for encryption?  You=E2=80=99d have=
 to
    > encrypt the message with each subkey.  Yeah, I know only the symmetric
    > key gets encrypted but it=E2=80=99s still ugly.

I'm pretty sure that the spec already says to do that.

    > And we haven=E2=80=99t even mentioned the web MUA and where it stores=
 the
    > private keys.

There are existing S/MIME and PGP plugins and extensions for browsers that =
do
this.  I'm aware of one that has received significant commercial success in
some quarters.  I think that they can use the javascript local storage for
private keys, but I suspect that they also have options to store them
encrypted elsewhere.

=2D-
]               Never tell me the odds!                 | ipv6 mesh network=
s [
]   Michael Richardson, Sandelman Software Works        | network architect=
  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [



=2D-
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -=3D IPv6 IoT consulting =3D-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJZah4xAAoJEJVM4Vb9/EKQ2VkIAKmD1Uxg7oHYZnOjK+XD9Cif
Lokcg9KSKdGRuKmuEwyb0cpZpn1LkIjbtaPMjTXVq3rKgQ4kuiQ+s8X8GpDDcPL6
Qlg7VgA2D/j5GXDPTFfVinRPfqHxdWPHql9nHa5Rr17agMLcyk9MyS0JgPR1oehk
74GAmDxk+7ECk625nZNe7z8Qu46pWb3vT30gk+xiK4DPMWYCepJMPWW8pUzk/yWg
z3Rt43m9w+IWuS46/GzBO829tncBc0iGgZZFZ/DNxbCd1kuoBihresZ4s9MfMLka
fcmilp8sBfth1yTF8U2gTII5pG28hLxTfefuF45ZfilJu+17M2WjPCXIl9pTC8s=
=0JLb
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun Jul 16 06:50:11 2017
Return-Path: <iab-chair@iab.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46958129B4B for <ietf@ietfa.amsl.com>; Sun, 16 Jul 2017 06:50:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.899
X-Spam-Level: 
X-Spam-Status: No, score=-2.899 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, HTML_MESSAGE=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 dyAKH0hAmqLM; Sun, 16 Jul 2017 06:50:08 -0700 (PDT)
Received: from hardie-macbookpro2.roam.corp.google.com (unknown [IPv6:2001:67c:1232:144:551f:ea8d:e30d:b3fd]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id A7E781200FC; Sun, 16 Jul 2017 06:50:07 -0700 (PDT)
To: ietf@ietf.org, hardie@google.com
From: IAB Chair <iab-chair@iab.org>
Subject: Updated Call for Participation, Workshop on Internet naming systems
Message-ID: <03026a50-2066-dde2-5bf4-1fbc684210e7@iab.org>
Date: Sun, 16 Jul 2017 15:50:05 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------D07AF98F3FF2DF3BFCAA42E7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gZb0-vou65xxnTXhlDJZ0xbpNcM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Jul 2017 13:50:10 -0000

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

When the IAB issued the initial call for participation for the upcoming 
ENAME workshop, several folks pointed out conflicts for potential 
attendees on the proposed dates. Among the conflicts were meetings of 
the DNS Operations, Analysis, and Research Center (OARC),  ISO's 
technical committee on coded character sets (ISO/IEC JTC1/SC2),  and the 
Information-Centric Networking Research Group (ICNRG).  After 
considering these conflicts and others for the times near the original 
dates, the IAB has decided to change the dates to October 10th and 11th. 
Microsoft has kindly offered a venue in Vancouver, British Columbia  for 
these dates.


Note that the new dates immediately follow both Canadian Thanksgiving 
and the U.S. Columbus Day holiday.  While this represents a different 
conflict problem, the IAB has agreed that the overlap with OARC, ICNRG, 
SC2, and the related meetings were serious enough to accept the 
trade-off.  In order to minimize the impact of holiday travel to the 
extent possible, we intend for the workshop to be a half-day on the 10th 
and a full day on the 11th.


The updated call for participation is below.


regards,


Ted Hardie

for the IAB




Call for Participation

IAB workshop on Explicit Internet Naming Systems

Internet namespaces relyon Internet connected systems sharing a common 
set of assumptions on the scope, method of resolution, and uniqueness of 
the names.    That set of assumption allowed the creation of URIs and 
other systems which presumed that you could authoritatively identify a 
service using an Internet name, a service port, and a set of 
locally-significant path elements.

There are now multiple challenges to maintaining that commonality of 
understanding.

  * Some naming systems wish to use URIs to identify both a service and
    the method of resolution used to map the name to a serving node. 
    Because there is no common facility for varying the resolution
    method in the URI structure, those naming systems must either mint
    new URI schemes for each resolution service or infer the resolution
    method from a reserved name or pattern.  Both methods are currently
    difficult and costly, and the effort thus scales poorly.
  * Users’ intentions to refer to specific names are now often expressed
    in voice input, gestures, and other methods which must be
    interpreted before being put into practice.  The systems which carry
    on that interpretation often infer which intent a user is
    expressing, and thus what name is meant, by contextual elements. 
    Those systems are linked to existing systems who have no access to
    that context and which may thus return results or create security
    expectations for an unintended name.

  * Unicode allows for both combining characters and composed characters
    when local language communities have different practices. When these
    do not have a single normalization, context is required to determine
    which to produce or assume in resolution.  How can this context be
    maintained in Internet systems?

While any of these challenges could easily be the topic of a stand-alone 
effort, this workshop seeks to explore whether there is a common set of 
root problems in the explicitness of the resolution context, heuristic 
derivation of intent, or language matching.   If so, it seeks to 
identify promising areas for the development of new, more explicit 
naming systems for the Internet.

We invite position papers on this topic to be submitted by July 28, 2017 
toename@iab.org <mailto:ename@iab.org>.    Decisions on accepted 
submissions will be made by August 11, 2017.

Proposed dates for the workshop are October 10th and 11th, 2017 and the 
proposed location is Vancouver, British Columbia.  Further logistics 
will be provided to selected participants.

Ted Hardie

for the IAB



--------------D07AF98F3FF2DF3BFCAA42E7
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 bgcolor="#FFFFFF" text="#000000">
    <p>
      <meta http-equiv="content-type" content="text/html; charset=utf-8">
    </p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">When
        the IAB issued the initial call for participation for the
        upcoming ENAME workshop, several folks pointed out conflicts for
        potential attendees on the proposed dates.  </span><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">
        <meta http-equiv="content-type" content="text/html;
          charset=utf-8">
        <span
          class="m_3425431854733555235gmail-m_-4759927563509228757gmail-c0"><span
            style="font-family:&quot;Arial&quot;,sans-serif;color:black">Among
            the conflicts were meetings of the DNS Operations, Analysis,
            and Research Center (OARC),  ISO's technical committee on
            coded character sets (</span></span><span
          class="m_3425431854733555235gmail-m_-4759927563509228757gmail-c0"><span
            style="font-family:&quot;Arial&quot;,sans-serif;color:black">ISO/IEC
            JTC1/SC2),  and the Information-Centric Networking Research
            Group (ICNRG).</span></span>  After considering these
        conflicts and others for the times near the original dates, the
        IAB has decided to change the dates to October 10th and 11th. 
        Microsoft has kindly offered a venue in Vancouver, British
        Columbia  for these dates.</span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><br>
      </span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">Note
        that the new dates immediately follow both Canadian Thanksgiving
        and the U.S. Columbus Day holiday.  While this represents a
        different conflict problem, the IAB has agreed that the overlap
        with OARC, ICNRG, SC2, and the related meetings were serious
        enough to accept the trade-off.  In order to minimize the impact
        of holiday travel to the extent possible, we intend for the
        workshop to be a half-day on the 10th and a full day on the
        11th.  <br>
      </span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><br>
      </span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">The
        updated call for participation is below.</span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><br>
      </span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">regards,</span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><br>
      </span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">Ted
        Hardie</span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">for
        the IAB<br>
      </span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><br>
      </span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><br>
      </span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><br>
      </span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">Call
        for Participation</span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span>IAB
        workshop on Explicit Internet Naming Systems</span></p>
    <p class="m_-7295555480336933649gmail-c1
      m_-7295555480336933649gmail-c2"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;height:11pt;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"></span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span>Internet
        namespaces rely<span> </span></span><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">on
        Internet connected systems sharing a common set of assumptions
        on the scope, method of resolution, and uniqueness of the names.
           That set of assumption allowed the creation of URIs and other
        systems which presumed that you could authoritatively identify a
        service using an Internet name, a service port, and a set of
        locally-significant path elements.  </span></p>
    <p class="m_-7295555480336933649gmail-c1
      m_-7295555480336933649gmail-c2"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;height:11pt;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"></span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">There
        are now multiple challenges to maintaining that commonality of
        understanding.  </span></p>
    <p class="m_-7295555480336933649gmail-c1
      m_-7295555480336933649gmail-c2"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;height:11pt;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"></span></p>
    <ul class="m_-7295555480336933649gmail-c3
      m_-7295555480336933649gmail-lst-kix_vlchuldijmo2-0
      m_-7295555480336933649gmail-start"
style="padding:0px;margin:0px;list-style-type:none;color:rgb(0,0,0);font-family:&quot;Times
      New
Roman&quot;;font-size:medium;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial">
      <li class="m_-7295555480336933649gmail-c4"
style="color:rgb(0,0,0);font-size:11pt;font-family:Arial;margin-left:36pt;padding-top:0pt;padding-left:0pt;padding-bottom:10pt;line-height:1.15;text-align:left"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">Some
          naming systems wish to use URIs to identify both a service and
          the method of resolution used to map the name to a serving
          node.  Because there is no common facility for varying the
          resolution method in the URI structure, those naming systems
          must either mint new URI schemes for each resolution service
          or infer the resolution method from a reserved name or
          pattern.  Both methods are currently difficult and costly, and
          the effort thus scales poorly.</span></li>
      <li class="m_-7295555480336933649gmail-c4"
style="color:rgb(0,0,0);font-size:11pt;font-family:Arial;margin-left:36pt;padding-top:0pt;padding-left:0pt;padding-bottom:10pt;line-height:1.15;text-align:left"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">Users’
          intentions to refer to specific names are now often expressed
          in voice input, gestures, and other methods which must be
          interpreted before being put into practice.  The systems which
          carry on that interpretation often infer which intent a user
          is expressing, and thus what name is meant, by contextual
          elements.  Those systems are linked to existing systems who
          have no access to that context and which may thus return
          results or create security expectations for an unintended
          name.</span></li>
    </ul>
    <ul class="m_-7295555480336933649gmail-c3
      m_-7295555480336933649gmail-lst-kix_ykgz29z81s2h-0
      m_-7295555480336933649gmail-start"
style="padding:0px;margin:0px;list-style-type:none;color:rgb(0,0,0);font-family:&quot;Times
      New
Roman&quot;;font-size:medium;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial">
      <li class="m_-7295555480336933649gmail-c4"
style="color:rgb(0,0,0);font-size:11pt;font-family:Arial;margin-left:36pt;padding-top:0pt;padding-left:0pt;padding-bottom:10pt;line-height:1.15;text-align:left"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">Unicode
          allows for both combining characters and composed characters
          when local language communities have different practices. 
          When these do not have a single normalization, context is
          required to determine which to produce or assume in
          resolution.  How can this context be maintained in Internet
          systems?</span></li>
    </ul>
    <p class="m_-7295555480336933649gmail-c1
      m_-7295555480336933649gmail-c2"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;height:11pt;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"></span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">While
        any of these challenges could easily be the topic of a
        stand-alone effort, this workshop seeks to explore whether there
        is a common set of root problems in the explicitness of the
        resolution context, heuristic derivation of intent, or language
        matching.   If so, it seeks to identify promising areas for the
        development of new, more explicit naming systems for the
        Internet.</span></p>
    <p class="m_-7295555480336933649gmail-c1
      m_-7295555480336933649gmail-c2"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;height:11pt;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"></span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span>We
        invite position papers on this topic to be submitted by July 28,
        2017 to<span> </span></span><span
        class="m_-7295555480336933649gmail-c8"
        style="color:rgb(17,85,204);text-decoration:underline"><a
          class="m_-7295555480336933649gmail-c6"
          href="mailto:ename@iab.org"
          style="color:inherit;text-decoration:inherit" target="_blank">ename@iab.org</a></span><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">.
           Decisions on accepted submissions will be made by August 11,
        2017.</span></p>
    <p class="m_-7295555480336933649gmail-c1
      m_-7295555480336933649gmail-c2"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;height:11pt;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"></span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">Proposed
        dates for the workshop are October 10th and 11th, 2017 and the
        proposed location is Vancouver, British Columbia.  Further
        logistics will be provided to selected participants.</span></p>
    <p class="m_-7295555480336933649gmail-c1
      m_-7295555480336933649gmail-c2"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;height:11pt;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"></span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">Ted
        Hardie</span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">for
        the IAB</span></p>
    <p class="m_-7295555480336933649gmail-c1
      m_-7295555480336933649gmail-c2"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;height:11pt;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><br>
      </span></p>
  </body>
</html>

--------------D07AF98F3FF2DF3BFCAA42E7--


From nobody Sun Jul 16 06:52:34 2017
Return-Path: <iab-chair@iab.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92FA412F28A; Sun, 16 Jul 2017 06:52:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.899
X-Spam-Level: 
X-Spam-Status: No, score=-2.899 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, HTML_MESSAGE=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 n9G4dap23IOp; Sun, 16 Jul 2017 06:52:24 -0700 (PDT)
Received: from hardie-macbookpro2.roam.corp.google.com (unknown [IPv6:2001:67c:1232:144:551f:ea8d:e30d:b3fd]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 15F031200FC; Sun, 16 Jul 2017 06:52:22 -0700 (PDT)
To: ietf@ietf.org, ietf-announce@ietf.org, iab@iab.org
From: IAB Chair <iab-chair@iab.org>
Subject: Updated Call for Participation, Workshop on Internet naming systems
Message-ID: <d22eeed9-b3ab-71ab-8f8b-fafd2a3ffc52@iab.org>
Date: Sun, 16 Jul 2017 15:52:21 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------23DD4A3B928978D23339D9C5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Zf82HwAAcitdHnIBYGXP5-yQwSA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Jul 2017 13:52:26 -0000

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

When the IAB issued the initial call for participation for the upcoming 
ENAME workshop, several folks pointed out conflicts for potential 
attendees on the proposed dates. Among the conflicts were meetings of 
the DNS Operations, Analysis, and Research Center (OARC),  ISO's 
technical committee on coded character sets (ISO/IEC JTC1/SC2),  and the 
Information-Centric Networking Research Group (ICNRG).  After 
considering these conflicts and others for the times near the original 
dates, the IAB has decided to change the dates to October 10th and 11th. 
Microsoft has kindly offered a venue in Vancouver, British Columbia  for 
these dates.


Note that the new dates immediately follow both Canadian Thanksgiving 
and the U.S. Columbus Day holiday.  While this represents a different 
conflict problem, the IAB has agreed that the overlap with OARC, ICNRG, 
SC2, and the related meetings were serious enough to accept the 
trade-off.  In order to minimize the impact of holiday travel to the 
extent possible, we intend for the workshop to be a half-day on the 10th 
and a full day on the 11th.


The updated call for participation is below.


regards,


Ted Hardie

for the IAB




Call for Participation

IAB workshop on Explicit Internet Naming Systems

Internet namespaces relyon Internet connected systems sharing a common 
set of assumptions on the scope, method of resolution, and uniqueness of 
the names.    That set of assumption allowed the creation of URIs and 
other systems which presumed that you could authoritatively identify a 
service using an Internet name, a service port, and a set of 
locally-significant path elements.

There are now multiple challenges to maintaining that commonality of 
understanding.

  * Some naming systems wish to use URIs to identify both a service and
    the method of resolution used to map the name to a serving node. 
    Because there is no common facility for varying the resolution
    method in the URI structure, those naming systems must either mint
    new URI schemes for each resolution service or infer the resolution
    method from a reserved name or pattern.  Both methods are currently
    difficult and costly, and the effort thus scales poorly.
  * Users’ intentions to refer to specific names are now often expressed
    in voice input, gestures, and other methods which must be
    interpreted before being put into practice.  The systems which carry
    on that interpretation often infer which intent a user is
    expressing, and thus what name is meant, by contextual elements. 
    Those systems are linked to existing systems who have no access to
    that context and which may thus return results or create security
    expectations for an unintended name.

  * Unicode allows for both combining characters and composed characters
    when local language communities have different practices. When these
    do not have a single normalization, context is required to determine
    which to produce or assume in resolution.  How can this context be
    maintained in Internet systems?

While any of these challenges could easily be the topic of a stand-alone 
effort, this workshop seeks to explore whether there is a common set of 
root problems in the explicitness of the resolution context, heuristic 
derivation of intent, or language matching.   If so, it seeks to 
identify promising areas for the development of new, more explicit 
naming systems for the Internet.

We invite position papers on this topic to be submitted by July 28, 2017 
toename@iab.org <mailto:ename@iab.org>.    Decisions on accepted 
submissions will be made by August 11, 2017.

Proposed dates for the workshop are October 10th and 11th, 2017 and the 
proposed location is Vancouver, British Columbia.  Further logistics 
will be provided to selected participants.

Ted Hardie

for the IAB



--------------23DD4A3B928978D23339D9C5
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 bgcolor="#FFFFFF" text="#000000">
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">When
        the IAB issued the initial call for participation for the
        upcoming ENAME workshop, several folks pointed out conflicts for
        potential attendees on the proposed dates.  </span><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><span
class="m_3425431854733555235gmail-m_-4759927563509228757gmail-c0"><span
            style="font-family:&quot;Arial&quot;,sans-serif;color:black">Among
            the conflicts were meetings of the DNS Operations, Analysis,
            and Research Center (OARC),  ISO's technical committee on
            coded character sets (</span></span><span
          class="m_3425431854733555235gmail-m_-4759927563509228757gmail-c0"><span
            style="font-family:&quot;Arial&quot;,sans-serif;color:black">ISO/IEC
            JTC1/SC2),  and the Information-Centric Networking Research
            Group (ICNRG).</span></span>  After considering these
        conflicts and others for the times near the original dates, the
        IAB has decided to change the dates to October 10th and 11th. 
        Microsoft has kindly offered a venue in Vancouver, British
        Columbia  for these dates.</span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><br>
      </span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">Note
        that the new dates immediately follow both Canadian Thanksgiving
        and the U.S. Columbus Day holiday.  While this represents a
        different conflict problem, the IAB has agreed that the overlap
        with OARC, ICNRG, SC2, and the related meetings were serious
        enough to accept the trade-off.  In order to minimize the impact
        of holiday travel to the extent possible, we intend for the
        workshop to be a half-day on the 10th and a full day on the
        11th.  <br>
      </span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><br>
      </span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">The
        updated call for participation is below.</span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><br>
      </span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">regards,</span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><br>
      </span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">Ted
        Hardie</span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">for
        the IAB<br>
      </span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><br>
      </span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><br>
      </span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><br>
      </span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">Call
        for Participation</span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span>IAB
        workshop on Explicit Internet Naming Systems</span></p>
    <p class="m_-7295555480336933649gmail-c1
      m_-7295555480336933649gmail-c2"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;height:11pt;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"></span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span>Internet
        namespaces rely<span> </span></span><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">on
        Internet connected systems sharing a common set of assumptions
        on the scope, method of resolution, and uniqueness of the names.
           That set of assumption allowed the creation of URIs and other
        systems which presumed that you could authoritatively identify a
        service using an Internet name, a service port, and a set of
        locally-significant path elements.  </span></p>
    <p class="m_-7295555480336933649gmail-c1
      m_-7295555480336933649gmail-c2"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;height:11pt;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"></span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">There
        are now multiple challenges to maintaining that commonality of
        understanding.  </span></p>
    <p class="m_-7295555480336933649gmail-c1
      m_-7295555480336933649gmail-c2"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;height:11pt;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"></span></p>
    <ul class="m_-7295555480336933649gmail-c3
      m_-7295555480336933649gmail-lst-kix_vlchuldijmo2-0
      m_-7295555480336933649gmail-start"
style="padding:0px;margin:0px;list-style-type:none;color:rgb(0,0,0);font-family:&quot;Times
      New
Roman&quot;;font-size:medium;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial">
      <li class="m_-7295555480336933649gmail-c4"
style="color:rgb(0,0,0);font-size:11pt;font-family:Arial;margin-left:36pt;padding-top:0pt;padding-left:0pt;padding-bottom:10pt;line-height:1.15;text-align:left"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">Some
          naming systems wish to use URIs to identify both a service and
          the method of resolution used to map the name to a serving
          node.  Because there is no common facility for varying the
          resolution method in the URI structure, those naming systems
          must either mint new URI schemes for each resolution service
          or infer the resolution method from a reserved name or
          pattern.  Both methods are currently difficult and costly, and
          the effort thus scales poorly.</span></li>
      <li class="m_-7295555480336933649gmail-c4"
style="color:rgb(0,0,0);font-size:11pt;font-family:Arial;margin-left:36pt;padding-top:0pt;padding-left:0pt;padding-bottom:10pt;line-height:1.15;text-align:left"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">Users’
          intentions to refer to specific names are now often expressed
          in voice input, gestures, and other methods which must be
          interpreted before being put into practice.  The systems which
          carry on that interpretation often infer which intent a user
          is expressing, and thus what name is meant, by contextual
          elements.  Those systems are linked to existing systems who
          have no access to that context and which may thus return
          results or create security expectations for an unintended
          name.</span></li>
    </ul>
    <ul class="m_-7295555480336933649gmail-c3
      m_-7295555480336933649gmail-lst-kix_ykgz29z81s2h-0
      m_-7295555480336933649gmail-start"
style="padding:0px;margin:0px;list-style-type:none;color:rgb(0,0,0);font-family:&quot;Times
      New
Roman&quot;;font-size:medium;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial">
      <li class="m_-7295555480336933649gmail-c4"
style="color:rgb(0,0,0);font-size:11pt;font-family:Arial;margin-left:36pt;padding-top:0pt;padding-left:0pt;padding-bottom:10pt;line-height:1.15;text-align:left"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">Unicode
          allows for both combining characters and composed characters
          when local language communities have different practices. 
          When these do not have a single normalization, context is
          required to determine which to produce or assume in
          resolution.  How can this context be maintained in Internet
          systems?</span></li>
    </ul>
    <p class="m_-7295555480336933649gmail-c1
      m_-7295555480336933649gmail-c2"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;height:11pt;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"></span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">While
        any of these challenges could easily be the topic of a
        stand-alone effort, this workshop seeks to explore whether there
        is a common set of root problems in the explicitness of the
        resolution context, heuristic derivation of intent, or language
        matching.   If so, it seeks to identify promising areas for the
        development of new, more explicit naming systems for the
        Internet.</span></p>
    <p class="m_-7295555480336933649gmail-c1
      m_-7295555480336933649gmail-c2"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;height:11pt;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"></span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span>We
        invite position papers on this topic to be submitted by July 28,
        2017 to<span> </span></span><span
        class="m_-7295555480336933649gmail-c8"
        style="color:rgb(17,85,204);text-decoration:underline"><a
          class="m_-7295555480336933649gmail-c6"
          href="mailto:ename@iab.org"
          style="color:inherit;text-decoration:inherit" target="_blank">ename@iab.org</a></span><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">.
           Decisions on accepted submissions will be made by August 11,
        2017.</span></p>
    <p class="m_-7295555480336933649gmail-c1
      m_-7295555480336933649gmail-c2"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;height:11pt;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"></span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">Proposed
        dates for the workshop are October 10th and 11th, 2017 and the
        proposed location is Vancouver, British Columbia.  Further
        logistics will be provided to selected participants.</span></p>
    <p class="m_-7295555480336933649gmail-c1
      m_-7295555480336933649gmail-c2"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;height:11pt;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"></span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">Ted
        Hardie</span></p>
    <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">for
        the IAB</span></p>
    <p class="m_-7295555480336933649gmail-c1
      m_-7295555480336933649gmail-c2"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;height:11pt;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
        class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><br>
      </span></p>
  </body>
</html>

--------------23DD4A3B928978D23339D9C5--


From nobody Sun Jul 16 11:05:07 2017
Return-Path: <agenda@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DD5BA1316A1; Sun, 16 Jul 2017 11:05:05 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Agenda <agenda@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: 99all@ietf.org, ietf@ietf.org
Subject: IETF 99 Final Agenda Changes
X-Test-IDTracker: no
X-IETF-IDTracker: 6.56.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: IETF Agenda <agenda@ietf.org>
Message-ID: <150022830581.30577.12305955211504761016.idtracker@ietfa.amsl.com>
Date: Sun, 16 Jul 2017 11:05:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lNrHFlnUZwNBMDCrmnZREiA1nTw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Jul 2017 18:05:06 -0000

Hi Everyone! 

Below are changes to the final agenda. As always, the most up to date version of the agenda is online.

https://datatracker.ietf.org/meeting/99/agenda.html
https://datatracker.ietf.org/meeting/99/agenda.txt

CANCELED:
RTCWEB (was Mon 13:30)
SLIM (was Mon 17:40)
MMUSIC (was Thurs 09:30)

MOVED: 
CDNI moved from Monday at 15:00 to Monday at 17:40 in Berlin/Brussels

NEW:
TLS Session Monday 13:30-15:30 in Congress Hall I
ART AD Office Hours Tuesday 14:20-15:50 in Paris 
IAOC Office Hours Wednesday 15:00-15:20 in Roma
OPS AD Office hours Thursday 09:00 - 10:00 in Paris

Thanks!

IETF Secretariat


From nobody Mon Jul 17 00:33:28 2017
Return-Path: <John_Brzozowski@comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 849F3131A54; Mon, 17 Jul 2017 00:33:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, 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 cq47ZiAmqp1a; Mon, 17 Jul 2017 00:33:24 -0700 (PDT)
Received: from vaadcmhout01.cable.comcast.com (vaadcmhout01.cable.comcast.com [96.114.28.75]) (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 65F65131A56; Mon, 17 Jul 2017 00:33:24 -0700 (PDT)
X-AuditID: 60721c4b-719ff70000000a8e-b1-596c684133e3
Received: from VAADCEX15.cable.comcast.com (vaadcmhoutvip.cable.comcast.com [96.115.73.56]) (using TLS with cipher AES256-SHA256 (256/256 bits)) (Client did not present a certificate) by vaadcmhout01.cable.comcast.com (SMTP Gateway) with SMTP id 29.D0.02702.1486C695; Mon, 17 Jul 2017 03:33:23 -0400 (EDT)
Received: from VAADCEX09.cable.comcast.com (147.191.102.76) by VAADCEX15.cable.comcast.com (147.191.102.82) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Mon, 17 Jul 2017 03:33:20 -0400
Received: from VAADCEX09.cable.comcast.com ([fe80::3aea:a7ff:fe12:e2a0]) by VAADCEX09.cable.comcast.com ([fe80::3aea:a7ff:fe12:e2a0%19]) with mapi id 15.00.1293.002; Mon, 17 Jul 2017 03:33:20 -0400
From: "Brzozowski, John" <John_Brzozowski@comcast.com>
To: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
CC: Randy Bush <randy@psg.com>, Alissa Cooper <alissa@cooperw.in>, Jim Martin <jim@daedelus.com>, Jari Arkko <jari.arkko@piuha.net>, Suresh Krishnan <suresh.krishnan@gmail.com>, Russ Housley <housley@vigilsec.com>
Subject: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Thread-Topic: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Thread-Index: AQHS/s72kLMVBj7jjUiP+v4GRBo4ow==
Date: Mon, 17 Jul 2017 07:33:20 +0000
Message-ID: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.21.0.170409
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [96.115.73.252]
Content-Type: text/plain; charset="utf-8"
Content-ID: <0746708FE40CBA4391F4AB91C6022D64@comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA11UfUwbZRzOe/06Ku88rrR96QoZZ3Txq7BEXf1aSNTYZcGwsahFEzjaW1t7 bbHXsuESZF9/WGayGIVRlJmlUyRkbAqObYqz1jiI0zgXFgQyCRUH8Y85Fmp1Lt5718LVv+53 z/P+nuf5/fLmJVV0v95C+oIRLhxkeUarVzcJW+0PP+PlndV/pErt3d//C+yxOca+dH1KZ184 fUxtPzrWr7VPplT2hUOLhD116pKmhnTcSi8SjtifPxOOs/FZnSORyBKOkUS31vFeTy9wDMzc 0tTpGvRPuTne18qFq7Y06b03+t7StLxftWf+wAVtB+iwxUARiahH0GcHh0AM6EmaOkOgrndO auSfCwAtd47q5J9xgDr6RrS4RUs9hoa/npaIUqoLoLHet6UWFTUFUPpElwafMlA70FDnt6Iw KZ56CS2fs2K4lLKh/pufq3Ctpu5Ft2d71biG1LPo1EenCVwDyoQyE4NSraLM6Jf0MULOSqHE Fz+q5NqIFufvSFZGUXPyxidqGX8IXbqaBnJdjUZOjOXwSnSnd0iN46io+9HQuSpZ/gl0+e8Y kOtK9G7nnE6OU4LGe9K5VjP6JjWqOQLK4opE8TWluEIprlCKK5Q+BJoBUNHKsm5XwBuKRqo3 2VxsM8/ZXKGAixUi+PspwNchbN02Ck5mn08CigRMMfy4kXfSGrZVaAskgZ8kGCP8Set30uua Q+42Lyt4G8NRnhOYUqh1iyfhKtwc5f2MBW7BqGEVDXK7BZ6LiPePqYDHsZB5lROiQovP5QtF hcZomE8CRKpE2cP1WNbNtr3BhUOyWRKsJ9WMGd539jUnTXnYCOfnuBYunGd3kySD4D0esbEk zHm4Pbt8fCRPi31/PSgylJKRwpZDe8rnpE1KQpG3Ej6JaYuS/n9kgixKAg9ZLOa+xuHcQgsb EHyenLUB1rIiWpxHJdsymMVH6TyosCyHL+rEFZnyVKHdBOgEZPxodoUgh/+5mCFodTAU5Cxm +MouPB9u8kaDq4NbTHB8e5OTvltB4AAWKzyMcaMCX8tg2QCvY7ZMwRbGyL8iS8Al3hgD/A67 F4tvzNrcNFRj8K4cKI2N4A/4apTkMMXUVujEUxtzTKHbkrheQlyvoVZab4SNKNc7UyutN4fm 1nu5VlpvDixYbzemTHmq0MnSAXaMM/UNGevxwe7JnZmtF/fuM1yjd1ITm88fmk9ut2RWfsvA lWndo9Mz5+n5A68H6vZ/UMdebbg9EOYcg97KIzXDB5u8m237rqw/c8U3Gt+w8fHkfuYmu1CB vprueyHbnvh14972nnJ/+7J7ylFTH8kuzD39XOOXr87UL725brbo95cZteBlNz2gCgvsf4Lr yme7BQAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SobsGNlAbv6NhsChUBdnz_Lp5jk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jul 2017 07:33:26 -0000

QXBvbG9naWVzLCBJIHVuZGVyc3RhbmQgdGhpcyBtYWlsIGRpZCBub3QgbWFrZSBpdCB0byB0aGUg
dmFyaW91cyBsaXN0cy4NCg0KSm9obg0KKzEtNDg0LTk2Mi0wMDYwDQoNCi0tLS0tT3JpZ2luYWwg
TWVzc2FnZS0tLS0tDQpGcm9tOiBKb2huIEJyem96b3dza2kgPEpvaG5fQnJ6b3pvd3NraUBDYWJs
ZS5Db21jYXN0LmNvbT4NCkRhdGU6IFN1bmRheSwgSnVseSAxNiwgMjAxNyBhdCAyMDoyOA0KVG86
ICJkcmFmdC1qam1iLXY2b3BzLWlldGYtaXB2Ni1vbmx5LWluY3JlbWVudGFsQGlldGYub3JnIiA8
ZHJhZnQtamptYi12Nm9wcy1pZXRmLWlwdjYtb25seS1pbmNyZW1lbnRhbEBpZXRmLm9yZz4NCkNj
OiBSYW5keSBCdXNoIDxyYW5keUBwc2cuY29tPiwgQWxpc3NhIENvb3BlciA8YWxpc3NhQGNvb3Bl
cncuaW4+LCBKaW0gTWFydGluIDxqaW1AZGFlZGVsdXMuY29tPiwgSmFyaSBBcmtrbyA8amFyaS5h
cmtrb0BwaXVoYS5uZXQ+LCBTdXJlc2ggS3Jpc2huYW4gPHN1cmVzaC5rcmlzaG5hbkBnbWFpbC5j
b20+LCBSdXNzIEhvdXNsZXkgPGhvdXNsZXlAdmlnaWxzZWMuY29tPg0KU3ViamVjdDogSW5jcmVt
ZW50YWwgRGVwbG95bWVudCBvZiBJUHY2LW9ubHkgV2ktRmkgZm9yIElFVEYgTWVldGluZ3MNCg0K
ICAgIEZvbGtzLA0KICAgIA0KICAgIEFwb2xvZ2llcyBpbiBhZHZhbmNlIGZvciB0aGUgZ3JhdHVp
dG91cyBjcm9zcyBwb3N0aW5nICh2Nm9wcywgaWV0ZiwgaXB2Niwgc3Vuc2V0NCwgc29mdHdpcmVz
KS4gIEkgaG9wZSwgdG8geW91IGFsbCwgdGhpcyBpcyB3b3J0aCB0aGUgYWRkZWQgZW1haWwuDQog
ICAgDQogICAgVGhlIGRyYWZ0IGJlbG93IHdhcyB3cml0dGVuIHRvIHByb3ZpZGUgdGhlIG5lY2Vz
c2FyeSBkb2N1bWVudGF0aW9uIHRvIGVuYWJsZSB0aGUgSUVURiAodGhlIE5PQywgcGFydGljaXBh
bnRzLCBldGMuKSB0byBtaWdyYXRlIHRvIGFuIElQdjYgb25seSBwcmltYXJ5IG5ldHdvcmsgY29u
bmVjdGlvbiAoV2ktRmkgYW5kIHdpcmVkKSB0aGF0IHV0aWxpemVzIE5BVDY0K0ROUzY0IHRvIGFj
Y2VzcyBJUHY0IG9ubHkgY29udGVudC4gIFRoZSByZXF1ZXN0IGZvciBJRVRGIDk5IGhhcyBiZWVu
IHRvIGhhdmUgdGhlIHByaW1hcnkg4oCcaWV0ZuKAnSBTU0lEIGFkaGVyZSB0byB3aGF0IGlzIGRv
Y3VtZW50ZWQgaW4gdGhlIEktRCBiZWxvdy4gIEkgdHJ1c3QgdGhlIG1vdGl2YXRpb24gaXMgdW5k
ZXJzdG9vZC4gIFRoaXMgbWVhbnMgdGhhdCB0aGUgbWFpbiDigJxpZXRm4oCdIFNTSUQgd291bGQg
YmUgc3dpdGNoZWQgdG8gYmUgSVB2NiBvbmx5IHdpdGggTkFUNjQrRE5TNjQgKGF0IGxheWVyIDMp
IHBlciB0aGUgSS1EIGJlbG93LiAgR2l2ZW4gdGhlIHRoYXQgSUVURjk5IGlzIHVwb24gdXMsIHRo
aXMgbWF5IG9yIG1heSBub3QgYmUgZW50aXJlbHkgcG9zc2libGUuDQogICAgDQogICAgQXQgdGhp
cyBzdGFnZSwgdGhlIGluZnJhc3RydWN0dXJlIHByZXBhcmF0aW9ucyBmb3IgSUVURiA5OSBzaG91
bGQgYmUgaW4gcGxhY2UgdG8gZW5zdXJlIHRoYXQgdGhlIElFVEYgaGFzIHRoZSBuZWNlc3Nhcnkg
aGFyZHdhcmUgZm9yIHJlZHVuZGFuY3kgYW5kIHBlcmZvcm1hbmNlLg0KICAgIA0KICAgIFNvLCB3
ZSBhcmUgYWxsIHNlZWtpbmcgeW91ciBpbnB1dC4gIEdpdmVuIHRoZSBhYm92ZSwgd2hhdCB3b3Vs
ZCBhbGwgeW91IHN1Z2dlc3QgaXMgdG9sZXJhYmxlIGZvciBJRVRGOTkgYXMgaXQgcGVydGFpbnMg
dG8gdGhlIEktRCBiZWxvdz8NCiAgICANCiAgICDigKIgSVB2NiBvbmx5IHBlciB0aGUgSS1EIGZv
ciB0aGUgYmFsYW5jZSBvZiBJRVRGIHdlZWs/DQogICAg4oCiIElQdjYgb25seSBwZXIgdGhlIEkt
RCBmb3Igb25lIG9yIG1vcmUgZGF5cyB0aGlzIHdlZWs/DQogICAg4oCiIElQdjYgb25seSBwZXIg
dGhlIEktRCBmb3IgdGhlIHBsZW5hcnk/DQogICAg4oCiIElQdjYgb25seSBwZXIgdGhlIEktRCBm
b3IgdGhlIG5leHQgSUVURiBtZWV0aW5nPw0KICAgIA0KICAgIFBsZWFzZSBzZW5kIHVzIHlvdXIg
ZmVlZGJhY2suDQogICAgDQogICAgUmVnYXJkcywNCiAgICANCiAgICBKb2huDQogICAgKzEtNDg0
LTk2Mi0wMDYwDQogICAgDQogICAgLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCiAgICBGcm9t
OiAiaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIiA8aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnPg0K
ICAgIERhdGU6IFNhdHVyZGF5LCBKdWx5IDEsIDIwMTcgYXQgMDM6MDQNCiAgICBUbzogTWFyY3Vz
IEtlYW5lIDxtYXJjdXMua2VhbmVAbWljcm9zb2Z0LmNvbT4sIEplbiBMaW5rb3ZhIDxmdXJyeUBn
b29nbGUuY29tPiwgTG9yZW56byBDb2xpdHRpIDxsb3JlbnpvQGdvb2dsZS5jb20+LCBKb2huIEJy
em96b3dza2kgPEpvaG5fQnJ6b3pvd3NraUBDYWJsZS5Db21jYXN0LmNvbT4sIEVyaWsgS2xpbmUg
PGVrQGdvb2dsZS5jb20+LCBKb2huIEJyem96b3dza2kgPEpvaG5fQnJ6b3pvd3NraUBDYWJsZS5D
b21jYXN0LmNvbT4sIERhdmlkIFNjaGluYXppIDxkc2NoaW5hemlAYXBwbGUuY29tPiwgU3R1YXJ0
IENoZXNoaXJlIDxjaGVzaGlyZUBhcHBsZS5jb20+LCBKZW4gTGlua292YSA8ZnVycnlAZ29vZ2xl
LmNvbT4sIFBhdWwgU2FhYiA8cHNAZmIuY29tPiwgRGF2aWQgU2NoaW5hemkgPGRzY2hpbmF6aUBh
cHBsZS5jb20+DQogICAgU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFm
dC1qam1iLXY2b3BzLWlldGYtaXB2Ni1vbmx5LWluY3JlbWVudGFsLTAwLnR4dA0KICAgIA0KICAg
ICAgICANCiAgICAgICAgQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LWpqbWItdjZvcHMtaWV0
Zi1pcHY2LW9ubHktaW5jcmVtZW50YWwtMDAudHh0DQogICAgICAgIGhhcyBiZWVuIHN1Y2Nlc3Nm
dWxseSBzdWJtaXR0ZWQgYnkgSm9obiBKYXNvbiBCcnpvem93c2tpIGFuZCBwb3N0ZWQgdG8gdGhl
DQogICAgICAgIElFVEYgcmVwb3NpdG9yeS4NCiAgICAgICAgDQogICAgICAgIE5hbWU6CQlkcmFm
dC1qam1iLXY2b3BzLWlldGYtaXB2Ni1vbmx5LWluY3JlbWVudGFsDQogICAgICAgIFJldmlzaW9u
OgkwMA0KICAgICAgICBUaXRsZToJCUluY3JlbWVudGFsIERlcGxveW1lbnQgb2YgSVB2Ni1vbmx5
IFdpLUZpIGZvciBJRVRGIE1lZXRpbmdzDQogICAgICAgIERvY3VtZW50IGRhdGU6CTIwMTctMDYt
MzANCiAgICAgICAgR3JvdXA6CQlJbmRpdmlkdWFsIFN1Ym1pc3Npb24NCiAgICAgICAgUGFnZXM6
CQkxNQ0KICAgICAgICBVUkw6ICAgICAgICAgICAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvaW50ZXJu
ZXQtZHJhZnRzL2RyYWZ0LWpqbWItdjZvcHMtaWV0Zi1pcHY2LW9ubHktaW5jcmVtZW50YWwtMDAu
dHh0DQogICAgICAgIFN0YXR1czogICAgICAgICBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3Jn
L2RvYy9kcmFmdC1qam1iLXY2b3BzLWlldGYtaXB2Ni1vbmx5LWluY3JlbWVudGFsLw0KICAgICAg
ICBIdG1saXplZDogICAgICAgaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWpqbWIt
djZvcHMtaWV0Zi1pcHY2LW9ubHktaW5jcmVtZW50YWwtMDANCiAgICAgICAgSHRtbGl6ZWQ6ICAg
ICAgIGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2h0bWwvZHJhZnQtamptYi12Nm9w
cy1pZXRmLWlwdjYtb25seS1pbmNyZW1lbnRhbC0wMA0KICAgICAgICANCiAgICAgICAgDQogICAg
ICAgIEFic3RyYWN0Og0KICAgICAgICAgICBUaGUgcHVycG9zZSBvZiB0aGlzIGRvY3VtZW50IGlz
IHRvIHByb3ZpZGUgYSBibHVlcHJpbnQgYW5kIGd1aWRhbmNlDQogICAgICAgICAgIGZvciBkZXBs
b3lpbmcgSVB2Ni1vbmx5IFdpLUZpIGF0IElFVEYgbWVldGluZ3MuICBUaGlzIGRvY3VtZW50DQog
ICAgICAgICAgIG91dGxpbmVzIGluZnJhc3RydWN0dXJlIGFuZCBvcGVyYXRpb25hbCBndWlkYW5j
ZSB0aGF0IG9wZXJhdG9ycw0KICAgICAgICAgICBzaG91bGQgY29uc2lkZXIgd2hlbiBkZXBsb3lp
bmcgSVB2Ni1vbmx5IG5ldHdvcmtzIHVzaW5nIE5BVDY0IGFuZA0KICAgICAgICAgICBETlM2NCB0
byBzdXBwb3J0IGNvbW11bmljYXRpb24gdG8gbGVnYWN5IElQdjQtb25seSBzZXJ2aWNlcy4NCiAg
ICAgICAgDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICANCiAgICAgICAgDQogICAg
ICAgIA0KICAgICAgICBQbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxlIG9mIG1p
bnV0ZXMgZnJvbSB0aGUgdGltZSBvZiBzdWJtaXNzaW9uDQogICAgICAgIHVudGlsIHRoZSBodG1s
aXplZCB2ZXJzaW9uIGFuZCBkaWZmIGFyZSBhdmFpbGFibGUgYXQgdG9vbHMuaWV0Zi5vcmcuDQog
ICAgICAgIA0KICAgICAgICBUaGUgSUVURiBTZWNyZXRhcmlhdA0KICAgICAgICANCiAgICAgICAg
DQogICAgICAgIA0KICAgIA0KICAgIA0KDQo=


From nobody Mon Jul 17 01:43:30 2017
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C78BE131B1A; Mon, 17 Jul 2017 01:43:28 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?b?SsO8cmdlbiBTY2jDtm53w6RsZGVy?= <j.schoenwaelder@jacobs-university.de>
To: <yang-doctors@ietf.org>
Cc: draft-ietf-netconf-keystore.all@ietf.org, ietf@ietf.org, netconf@ietf.org
Subject: Yangdoctors last call review of draft-ietf-netconf-keystore-02
X-Test-IDTracker: no
X-IETF-IDTracker: 6.56.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150028100874.32703.14161403810529927281@ietfa.amsl.com>
Date: Mon, 17 Jul 2017 01:43:28 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uCiyF8hchg6_DTOkFAkNdvPCr3k>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jul 2017 08:43:29 -0000

Reviewer: Jürgen Schönwälder
Review result: Not Ready

draft-ietf-netconf-keystore-02

- s/YANG data module/YANG module/ or s/YANG data module/YANG model/

- Find a better phrase for 'hold onto'. Does the module allow
  configuration of trusted private keys and certificates? If so, say
  so.

- What is 'extends special consideration'?

- What is a 'semi-configurable' list?

- s/is MAY/MAY/ (does this may need to be allcaps?)

- s/an optional attributes/optional attributes/

- the module seems to use actions but the surrounding text talks about
  rpcs

- does the generate-private-key really take a key length as a parameter
  as promised in section 2?

- section 2.2. talks about 'examples above' but there are none 'above'

- Have the examples been validated? Is rsa1024 a valid identityref
  value?

- There are a number of binary fields where you show explanatory text
  in the examples instead of encoded data. Is this always clear?

  <private-key>...</private-key> <!-- elipsis placeholder for a base64 encoded key -->

- I am not sure I understand trusted-host-keys. On systems that have
  multiple user accounts, you usually have a per account list of
  trusted host keys in addition to a global system wide list. Perhaps
  make it clear that this models the global known hosts list only?

- Is it helpful that some examples use XML / NETCONF while others use
  JSON / RESTCONF or is this possibly confusing? If you include JSON
  examples, do you not need to reference RFC 7951?

- s/(c) 2014/(c) 2017/

- reference statement of the revision statement seems to have the
  wrong title

- Should the document title be aligned with other YANG module
  definitions, so it is easier to spot it?

- Since crypto algorithms come and go, is it reasonable to have the
  identities defined in a rather static RFC? Would an IANA maintained
  identity module perhaps make more sense?

- Oh, I now see that the key length is embedded in the algorithm
  identity. Perhaps clarify this earlier, see my confused comments
  above. Anyway, I think this makes the need for an IANA maintained
  module even stronger.

- "If additional algorithms are needed, they MAY be augmented in by
  another module" seems confusing; I think all that is needed is to
  define a new identity, right? If so, there is no augmentation in the
  YANG sense.

- The description of the keystore container talks about passwords and
  I am not sure this is correct. I am also not sure the terms 'active
  material' and 'passive material' really help.

- The description of keys says "A list of keys maintained by the
  keystore.". I think it would be more helpful to say "A list of
  public-private key pairs maintained by the keystore." Every list
  element seems to have two keys.

- What about the comment in the definition of algorithm-identifier?
  Looks like an open issue or something that should be resolved before
  publishing this document.

- Add a reference clause to the definition of private-key? Do we
  really need the INACCESSIBLE enum and the union? There is another
  open question right below the private-key definition...

- Add a reference clause to the definition of public-key?

- Why do certificate names have to be unique across all keys?

- Since the certs of a key do not contain a signature, where are signed
  certificates stored or are they outside the scope of the model?

- All references to RFCs and I-Ds in description clauses must resolve
  to regular citations somewhere and references in the references
  section.

- Is there any text needed to explain what happens if actions can't be
  carried out, e.g., the algorithm identity is not supported? Can a
  client actually learn which algorithm identities are supported or is
  the approach simply trial and error?

- I am a bit concerned about the two list names 'trusted-certificates'
  and 'trusted certificate' which mean very different things and can
  be potentially confused. (The same for 'trusted-host-keys' and
  'trusted-host-key'.) [No, I do not have a good naming proposal that
  I like, perhaps some brainstorming helps.]

- I am not sure what 'trusted certificate' here really means. What you
  are modeling is a set of sets of certificates. What such a set means
  depends on where this list is used. I am not sure what it means for
  a certificate in such a set to be 'trusted'.

- What about the // rename to 'data' comment? I like it, renaming to
  list certificate { key name; leaf name; leaf data; } seems less
  confusing (and it is even shorter). Perhaps something along this
  line would be better (not sure I like certificate-set)

	 +--rw certificate-set* [name]
         |  +--rw name                   string
         |  +--rw description?           string
         |  +--rw certificate* [name]
         |     +--rw name    string
         |     +--rw data?   binary

- Why is the certificate (data) leaf in trusted-certificate not
  mandatory? Does it make sense to have list elements where there
  is only a name?

- I am wondering whether it is really a good idea to handle both X509
  keys and certificates as well as some SSH host keys in this document.
  Perhaps it is better to really split things. Also think about devices
  that only do SSH or only to TLS.

- I am not sure I fully understood the call home statement in the
  description of trusted-host-key. This probably needs more or better
  explanation.

- Are SSH implementation encoding keys in ASN.1/DER? I doubt this very
  much. Perhaps this SSH stuff should be moved to a separate I-D since
  I believe this needs more work.

- You cite RFC 6020 (YANG 1) but you use actions which were only added
  in YANG 1.1. I think you should only cite YANG 1.1 (RFC 7950).
 
- The prefix is 'ks' and not 'kc' as stated in the IANA considerations
  section.

- Security considerations talk about 'RPC operations' but the data
  model actually uses actions. Perhaps simply talk about 'operations'.



From nobody Mon Jul 17 08:22:20 2017
Return-Path: <John_Brzozowski@comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FD861316C2; Sun, 16 Jul 2017 11:29:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 aZZ26WHmvCHp; Sun, 16 Jul 2017 11:29:03 -0700 (PDT)
Received: from vaadcmhout02.cable.comcast.com (vaadcmhout02.cable.comcast.com [96.114.28.76]) (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 40F3A12702E; Sun, 16 Jul 2017 11:29:03 -0700 (PDT)
X-AuditID: 60721c4c-4576e9a000004e62-cc-596bb06c3ee5
Received: from VAADCEX13.cable.comcast.com (vaadcmhoutvip.cable.comcast.com [96.115.73.56]) (using TLS with cipher AES256-SHA256 (256/256 bits)) (Client did not present a certificate) by vaadcmhout02.cable.comcast.com (SMTP Gateway) with SMTP id 26.3F.20066.C60BB695; Sun, 16 Jul 2017 14:29:00 -0400 (EDT)
Received: from VAADCEX09.cable.comcast.com (147.191.102.76) by VAADCEX13.cable.comcast.com (147.191.102.80) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Sun, 16 Jul 2017 14:28:58 -0400
Received: from VAADCEX09.cable.comcast.com ([fe80::3aea:a7ff:fe12:e2a0]) by VAADCEX09.cable.comcast.com ([fe80::3aea:a7ff:fe12:e2a0%19]) with mapi id 15.00.1293.002; Sun, 16 Jul 2017 14:28:58 -0400
From: "Brzozowski, John" <John_Brzozowski@comcast.com>
To: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>
CC: Randy Bush <randy@psg.com>, Alissa Cooper <alissa@cooperw.in>, Jim Martin <jim@daedelus.com>, Jari Arkko <jari.arkko@piuha.net>, Suresh Krishnan <suresh.krishnan@gmail.com>, Russ Housley <housley@vigilsec.com>
Subject: Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Thread-Topic: Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Thread-Index: AQHS/mFjyacM1/hfIEykN3ouQq0Z3w==
Date: Sun, 16 Jul 2017 18:28:57 +0000
Message-ID: <F73BB5CF-9600-404E-9A25-9DCDD1E2493D@cable.comcast.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.21.0.170409
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [96.115.73.252]
Content-Type: text/plain; charset="utf-8"
Content-ID: <81B121D76221E340A120022E53A6DCE2@comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA11Uf0wTZxjed3elB/LN46DtRwVib8NkxCFsk3TuR/xDhmYucf8s6RYDRznb o9eW3bUI+5H0H5cFtsQsCxvV+IOAE+JAiPiDsOlqIwNDHJuuOhc3B1F0y2ZcxBgd2/f1rnDd X33ved73eZ737eVYmn+Y62TlUERSQ6Ii5OQxDdoW99PK0YCn6upezn1jeD/jvjX9F+U+e2iU cvePn7a6z5/7it5o2dzb+4DaBt7Me7FJUuRWSV33ckOe/5+JL5iWn8vb7h2essTAr092gFwW cc+h2eFHVAfIY3nuBIUuje1m9IczAB1PPQL6wyRA1wfvATKSw9WgY99ctXYAli3iNHRzlic9 NHcFoLm+LgvpKeQ2ofHUDaD3bEH/XqogcBFXiYbnO9MtDFeORj45ZyU1xO13982n5QFnR/en jlCkpjkH+mluP6Un5VDv+AVar23o1uxiWseGNX+808/o+Fo0nZoDel2FRvu+NnAXWtwzxJA4 NPcUGhpbp8tvQBND3Va9dqFPO68bcQrQZPecMepAZ5MnLbtBcdyUKL6sFDcpxU1KcZPSAWAZ AGWtotjkDfrD0UjVM5VesVGRKr3hoFfUIuR3BJB/WC3ZehLc7dqcABwLhHw40xXw8BaxVWsP JkCApQQbnMnB0OON4aZ2v6j569WoImlCEWx4tdnDwyW4MaoEBCdcM4ibC5fQkLRTU6QIfqWE MthDhBxLnBbVWmSvHI5q9VFVSQDE0lh2w2e4CTaJ7e9Ialg3S4BVLCM44JpT2JHziREpIEkt kpphd7KsgOC+ITxYoEo+qW2HrEQyNJ4bJJk4M5MOWwrdSdnD282EKa8LvkBop5n+f2SKzU0A H5uPc79N7KHWIgY12WdYF8LQWzhyfgZN2xbDYdLKZ0CTZSl8w4ope4bKtpsCnYCNf/5ggWKP Pfz2PsUzoXBIcjrgQno/MuSPhpYWd9rh5OsNHn6liSABnCXwI4LbTPhyBudqOE/YYhObHSPz YbgNvPiNKYS7yDb5+LOxvDcP+0ikFQaYXhvBvQQrMDDT1iXQQ7a2GUy22218Xgqf94NmPzlv RIyYz2sJ+Ml5DdQ472ME5DNg1nnDRMWeobKdnDFw/onuNvuBYG1tf+z96prRX5rl+V3rK0ro 9ReuuLQ9B8Xfr/lWhy729LjurMh5L3ni4kJxPV8wvVC7MlYnf/h82UxqoOZ729RLQl3qj+nG HT+oW1d9/Irt2uWk+vf4tptfbjo68Odva5/t/666bvviodjs8dKy7fCylrTBkYmN5e++dmpM YDS/WF1Bq5r4H+QKnxGOBQAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hKCcayVVtiNH5hZZknlP4NLGgXo>
X-Mailman-Approved-At: Mon, 17 Jul 2017 08:22:19 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Jul 2017 18:29:05 -0000

Rm9sa3MsDQoNCkFwb2xvZ2llcyBpbiBhZHZhbmNlIGZvciB0aGUgZ3JhdHVpdG91cyBjcm9zcyBw
b3N0aW5nICh2Nm9wcywgaWV0ZiwgaXB2Niwgc3Vuc2V0NCwgc29mdHdpcmVzKS4gIEkgaG9wZSwg
dG8geW91IGFsbCwgdGhpcyBpcyB3b3J0aCB0aGUgYWRkZWQgZW1haWwuDQoNClRoZSBkcmFmdCBi
ZWxvdyB3YXMgd3JpdHRlbiB0byBwcm92aWRlIHRoZSBuZWNlc3NhcnkgZG9jdW1lbnRhdGlvbiB0
byBlbmFibGUgdGhlIElFVEYgKHRoZSBOT0MsIHBhcnRpY2lwYW50cywgZXRjLikgdG8gbWlncmF0
ZSB0byBhbiBJUHY2IG9ubHkgcHJpbWFyeSBuZXR3b3JrIGNvbm5lY3Rpb24gKFdpLUZpIGFuZCB3
aXJlZCkgdGhhdCB1dGlsaXplcyBOQVQ2NCtETlM2NCB0byBhY2Nlc3MgSVB2NCBvbmx5IGNvbnRl
bnQuICBUaGUgcmVxdWVzdCBmb3IgSUVURiA5OSBoYXMgYmVlbiB0byBoYXZlIHRoZSBwcmltYXJ5
IOKAnGlldGbigJ0gU1NJRCBhZGhlcmUgdG8gd2hhdCBpcyBkb2N1bWVudGVkIGluIHRoZSBJLUQg
YmVsb3cuICBJIHRydXN0IHRoZSBtb3RpdmF0aW9uIGlzIHVuZGVyc3Rvb2QuICBUaGlzIG1lYW5z
IHRoYXQgdGhlIG1haW4g4oCcaWV0ZuKAnSBTU0lEIHdvdWxkIGJlIHN3aXRjaGVkIHRvIGJlIElQ
djYgb25seSB3aXRoIE5BVDY0K0ROUzY0IChhdCBsYXllciAzKSBwZXIgdGhlIEktRCBiZWxvdy4g
IEdpdmVuIHRoZSB0aGF0IElFVEY5OSBpcyB1cG9uIHVzLCB0aGlzIG1heSBvciBtYXkgbm90IGJl
IGVudGlyZWx5IHBvc3NpYmxlLg0KDQpBdCB0aGlzIHN0YWdlLCB0aGUgaW5mcmFzdHJ1Y3R1cmUg
cHJlcGFyYXRpb25zIGZvciBJRVRGIDk5IHNob3VsZCBiZSBpbiBwbGFjZSB0byBlbnN1cmUgdGhh
dCB0aGUgSUVURiBoYXMgdGhlIG5lY2Vzc2FyeSBoYXJkd2FyZSBmb3IgcmVkdW5kYW5jeSBhbmQg
cGVyZm9ybWFuY2UuDQoNClNvLCB3ZSBhcmUgYWxsIHNlZWtpbmcgeW91ciBpbnB1dC4gIEdpdmVu
IHRoZSBhYm92ZSwgd2hhdCB3b3VsZCBhbGwgeW91IHN1Z2dlc3QgaXMgdG9sZXJhYmxlIGZvciBJ
RVRGOTkgYXMgaXQgcGVydGFpbnMgdG8gdGhlIEktRCBiZWxvdz8NCg0K4oCiIElQdjYgb25seSBw
ZXIgdGhlIEktRCBmb3IgdGhlIGJhbGFuY2Ugb2YgSUVURiB3ZWVrPw0K4oCiIElQdjYgb25seSBw
ZXIgdGhlIEktRCBmb3Igb25lIG9yIG1vcmUgZGF5cyB0aGlzIHdlZWs/DQrigKIgSVB2NiBvbmx5
IHBlciB0aGUgSS1EIGZvciB0aGUgcGxlbmFyeT8NCuKAoiBJUHY2IG9ubHkgcGVyIHRoZSBJLUQg
Zm9yIHRoZSBuZXh0IElFVEYgbWVldGluZz8NCg0KUGxlYXNlIHNlbmQgdXMgeW91ciBmZWVkYmFj
ay4NCg0KUmVnYXJkcywNCg0KSm9obg0KKzEtNDg0LTk2Mi0wMDYwDQoNCi0tLS0tT3JpZ2luYWwg
TWVzc2FnZS0tLS0tDQpGcm9tOiAiaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIiA8aW50ZXJuZXQt
ZHJhZnRzQGlldGYub3JnPg0KRGF0ZTogU2F0dXJkYXksIEp1bHkgMSwgMjAxNyBhdCAwMzowNA0K
VG86IE1hcmN1cyBLZWFuZSA8bWFyY3VzLmtlYW5lQG1pY3Jvc29mdC5jb20+LCBKZW4gTGlua292
YSA8ZnVycnlAZ29vZ2xlLmNvbT4sIExvcmVuem8gQ29saXR0aSA8bG9yZW56b0Bnb29nbGUuY29t
PiwgSm9obiBCcnpvem93c2tpIDxKb2huX0Jyem96b3dza2lAQ2FibGUuQ29tY2FzdC5jb20+LCBF
cmlrIEtsaW5lIDxla0Bnb29nbGUuY29tPiwgSm9obiBCcnpvem93c2tpIDxKb2huX0Jyem96b3dz
a2lAQ2FibGUuQ29tY2FzdC5jb20+LCBEYXZpZCBTY2hpbmF6aSA8ZHNjaGluYXppQGFwcGxlLmNv
bT4sIFN0dWFydCBDaGVzaGlyZSA8Y2hlc2hpcmVAYXBwbGUuY29tPiwgSmVuIExpbmtvdmEgPGZ1
cnJ5QGdvb2dsZS5jb20+LCBQYXVsIFNhYWIgPHBzQGZiLmNvbT4sIERhdmlkIFNjaGluYXppIDxk
c2NoaW5hemlAYXBwbGUuY29tPg0KU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZv
ciBkcmFmdC1qam1iLXY2b3BzLWlldGYtaXB2Ni1vbmx5LWluY3JlbWVudGFsLTAwLnR4dA0KDQog
ICAgDQogICAgQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LWpqbWItdjZvcHMtaWV0Zi1pcHY2
LW9ubHktaW5jcmVtZW50YWwtMDAudHh0DQogICAgaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1p
dHRlZCBieSBKb2huIEphc29uIEJyem96b3dza2kgYW5kIHBvc3RlZCB0byB0aGUNCiAgICBJRVRG
IHJlcG9zaXRvcnkuDQogICAgDQogICAgTmFtZToJCWRyYWZ0LWpqbWItdjZvcHMtaWV0Zi1pcHY2
LW9ubHktaW5jcmVtZW50YWwNCiAgICBSZXZpc2lvbjoJMDANCiAgICBUaXRsZToJCUluY3JlbWVu
dGFsIERlcGxveW1lbnQgb2YgSVB2Ni1vbmx5IFdpLUZpIGZvciBJRVRGIE1lZXRpbmdzDQogICAg
RG9jdW1lbnQgZGF0ZToJMjAxNy0wNi0zMA0KICAgIEdyb3VwOgkJSW5kaXZpZHVhbCBTdWJtaXNz
aW9uDQogICAgUGFnZXM6CQkxNQ0KICAgIFVSTDogICAgICAgICAgICBodHRwczovL3d3dy5pZXRm
Lm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtamptYi12Nm9wcy1pZXRmLWlwdjYtb25seS1pbmNy
ZW1lbnRhbC0wMC50eHQNCiAgICBTdGF0dXM6ICAgICAgICAgaHR0cHM6Ly9kYXRhdHJhY2tlci5p
ZXRmLm9yZy9kb2MvZHJhZnQtamptYi12Nm9wcy1pZXRmLWlwdjYtb25seS1pbmNyZW1lbnRhbC8N
CiAgICBIdG1saXplZDogICAgICAgaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWpq
bWItdjZvcHMtaWV0Zi1pcHY2LW9ubHktaW5jcmVtZW50YWwtMDANCiAgICBIdG1saXplZDogICAg
ICAgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvaHRtbC9kcmFmdC1qam1iLXY2b3Bz
LWlldGYtaXB2Ni1vbmx5LWluY3JlbWVudGFsLTAwDQogICAgDQogICAgDQogICAgQWJzdHJhY3Q6
DQogICAgICAgVGhlIHB1cnBvc2Ugb2YgdGhpcyBkb2N1bWVudCBpcyB0byBwcm92aWRlIGEgYmx1
ZXByaW50IGFuZCBndWlkYW5jZQ0KICAgICAgIGZvciBkZXBsb3lpbmcgSVB2Ni1vbmx5IFdpLUZp
IGF0IElFVEYgbWVldGluZ3MuICBUaGlzIGRvY3VtZW50DQogICAgICAgb3V0bGluZXMgaW5mcmFz
dHJ1Y3R1cmUgYW5kIG9wZXJhdGlvbmFsIGd1aWRhbmNlIHRoYXQgb3BlcmF0b3JzDQogICAgICAg
c2hvdWxkIGNvbnNpZGVyIHdoZW4gZGVwbG95aW5nIElQdjYtb25seSBuZXR3b3JrcyB1c2luZyBO
QVQ2NCBhbmQNCiAgICAgICBETlM2NCB0byBzdXBwb3J0IGNvbW11bmljYXRpb24gdG8gbGVnYWN5
IElQdjQtb25seSBzZXJ2aWNlcy4NCiAgICANCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
DQogICAgDQogICAgDQogICAgUGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBv
ZiBtaW51dGVzIGZyb20gdGhlIHRpbWUgb2Ygc3VibWlzc2lvbg0KICAgIHVudGlsIHRoZSBodG1s
aXplZCB2ZXJzaW9uIGFuZCBkaWZmIGFyZSBhdmFpbGFibGUgYXQgdG9vbHMuaWV0Zi5vcmcuDQog
ICAgDQogICAgVGhlIElFVEYgU2VjcmV0YXJpYXQNCiAgICANCiAgICANCiAgICANCg0K


From nobody Mon Jul 17 08:31:53 2017
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8681131C6E for <ietf@ietfa.amsl.com>; Mon, 17 Jul 2017 08:31:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.92
X-Spam-Level: 
X-Spam-Status: No, score=-6.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 JGdTUz2JquMJ for <ietf@ietfa.amsl.com>; Mon, 17 Jul 2017 08:31:49 -0700 (PDT)
Received: from smtpde01.smtp.sap-ag.de (smtpde01.smtp.sap-ag.de [155.56.68.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C130A131C62 for <ietf@ietf.org>; Mon, 17 Jul 2017 08:31:49 -0700 (PDT)
Received: from mail07.wdf.sap.corp (mail04.sap.corp [194.39.131.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtpde01.smtp.sap-ag.de (Postfix) with ESMTPS id 3xB6j01QW2z1HQ5; Mon, 17 Jul 2017 17:31:48 +0200 (CEST)
X-purgate-ID: 152705::1500305508-00000810-9AFDC6B2/0/0
X-purgate-size: 2736
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate-type: clean
X-SAP-SPAM-Status: clean
Received: from ld9781.wdf.sap.corp (ld9781.wdf.sap.corp [10.21.82.193]) by mail07.wdf.sap.corp (Postfix) with ESMTP id 3xB6hz6JxyzGp3X; Mon, 17 Jul 2017 17:31:47 +0200 (CEST)
Received: by ld9781.wdf.sap.corp (Postfix, from userid 10159) id D3EA61A6C8; Mon, 17 Jul 2017 17:31:47 +0200 (CEST)
Subject: Re: Revamp of the www.ietf.org website
In-Reply-To: <C1590F40-3B9E-45A0-9B87-59A0271B1952@consulintel.es>
To: jordi.palet@consulintel.es
Date: Mon, 17 Jul 2017 17:31:47 +0200 (CEST)
CC: IETF <ietf@ietf.org>
Reply-To: mrex@sap.com
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20170717153147.D3EA61A6C8@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Gy6dzFfsi4MVAxAAVv4eYfz-aUs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jul 2017 15:31:52 -0000

JORDI PALET MARTINEZ wrote:
>
> I think a missing aspect of the web site, which should be prominent in
> both the home page and also the ?contact? page, is all the social media.
> 
> I see there is a ?share this page? at the right of the main picture,
> but in my opinion, is not clearly visible and is not enough
> (the logos of the social networks should be recognized without...

Cough, cough, WHAT???

Please get rid of the "social media" crap entirely.  I thought that
there was an IETF consensus that privcay is sensible and useful, and
strong privacy protections should be the default.


Facebook, Twitter and other "social media" crap is the far opposite of
strongy privacy, so none of this should be encouraged or promoted by
the IETF.



Comparing the bandwidth necessary to load the entire homepage,
I notice the following issues:

  https://www.ietf.org/    Total 188176 bytes (mainly by accident, it seems)
                           The visible page _contents_ are just fine,

    but the page designer goofed the photo in the meeting information,
    because the picture is transferred at size 640x427 taking up 150270 bytes,
    although it is actually being displayed at just 200x133, where a
    pre-scaled image would need just 17 KBytes.

    Even on my 5" Smartphone, the https://www.ietf.org/ loads just fine,
    I get the whole picture immediately, and can zoon into my area of interest.


  http://www.ietf.org/     Total 1195800 bytes (ouch ouch ouch ouch).

    is a completely botched page design. it needs multi-page scrolldown
    even on a big desktop screen, and finding stuff has become extremely
    difficult.

    This page even manages to provide *ZERO* intelligible information
    when loaded on my SmartPhone

    only shows the Welcome / Revamp <Learn More>  + Social Media Crap Buttons

    and when scrolling down the multiple pages of crap on my SmartPhone,
    very close to zero of the links _that_used_to_be_ on https://www.ietf.org
    pass by.


    Normally I close such bloated ad & nag screens immediately, though
    nowadays uBlock saves my health by ensuring that most of such crap
    does not even get displayed on any of my screens (desktop & mobile)
    in the first place.

    The huge background picture (IETF-Past-Meetings.max-4000x4000.jpg)
    with 763216 Bytes is just crazy.  Is this about a party/festival?
    A *HUGE* waste of network bandwidth and memory (RAM and on-disk cache)
    and writing text over photos also make reading difficult (poor contrast).



All in all, my personal summary for https://beta.ietf.org/

disgusting and extremly bloated, usless and highly confusing.


-Martin


From nobody Mon Jul 17 09:34:12 2017
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0395131CA8 for <ietf@ietfa.amsl.com>; Mon, 17 Jul 2017 09:34:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, 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 JcaMwLFI4SQm for <ietf@ietfa.amsl.com>; Mon, 17 Jul 2017 09:34:10 -0700 (PDT)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 303E5131CAA for <ietf@ietf.org>; Mon, 17 Jul 2017 09:33:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1500309229; d=isode.com; s=june2016; i=@isode.com; bh=xMNO93hSQDVBkGiHUQuw/FYTdbWKwfQQ5/vYqFX+j9s=; 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=r4Gebp6TucSIXCAlrU4buLfL+ZvGmfqxt1UNT+5Qc6BA4PnVWwBAlGueX/HKYRKf7hkyVv Q5ZTCCp3RcdyxJZmU3biQocnxIfJ51g1S6a37uYAtPrLCIRltuZ26QzL3ppyZRIcdMIVL1 3a9UFyZhLtNkEmyogd9CSefzSC5XcZA=;
Received: from [31.133.129.198] (dhcp-81c6.meeting.ietf.org [31.133.129.198])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <WWzm6wBf=ocE@statler.isode.com>; Mon, 17 Jul 2017 17:33:48 +0100
To: "ietf@ietf.org" <ietf@ietf.org>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Subject: draft-ietf-jsonbis-rfc7159bis-03: recommendation to use UTF-8
Message-ID: <596CE6E3.3070808@isode.com>
Date: Mon, 17 Jul 2017 17:33:39 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ouhwmwhtYy-KCHN0Ln4LkeRn_Mc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jul 2017 16:34:11 -0000

Hi,

The JSONBIS WG decided to update recommendation on Unicode encoding to
be UTF-8. (For details see the RFC Editor's notes in the approval
message that will be sent out shortly.) This took a bit of time to
debate in the WG, so the document approval took a bit longer than
originally expected.

Best Regards,
Alexey, as the responsible AD


From nobody Mon Jul 17 12:35:18 2017
Return-Path: <prvs=13714351ed=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B9B3127B57 for <ietf@ietfa.amsl.com>; Mon, 17 Jul 2017 12:35:17 -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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
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 1VphCvMwZf2F for <ietf@ietfa.amsl.com>; Mon, 17 Jul 2017 12:35:15 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D896129B6A for <ietf@ietf.org>; Mon, 17 Jul 2017 12:35:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1500320113; x=1500924913; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=P2zANpu26pIeKRDo0lrSU288f aaAfGuVAug775poD9w=; b=js6nx1qmaMNf/vp3rQcqEY6ydDvEk3d+FjiFro0SN LpoQveU8tC5kRlTYBNvhq99rhBt14HIqx6Ml2qjOxK2UEIMXb6jwF2mCa9BDenj6 Q/zU6zgRVaR+5rYP4S/KCfRzlJMQtzczVg5Rsr+g0LvSmkRQCUQ4Ve+6IgQgRjIY Gs=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=gUEs9sKCbWFnotXjoOfe7o2qfK094rxRSLRiUB0+Js4Lw+q+tPS0KQL9Y9kk 0tPHKIGlznrrQLgDTsAwHG9pHOS6+4J+KR1euNfz6iBjjWoCoOwXjVh2G V86drBMcLWA88FC2ut7oRglI0FyRk0OJBB6HUIREAqGUgobZm5VKAY=;
X-MDAV-Processed: mail.consulintel.es, Mon, 17 Jul 2017 21:35:13 +0200
X-Spam-Processed: mail.consulintel.es, Mon, 17 Jul 2017 21:35:12 +0200
Received: from [31.133.186.60] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005478825.msg for <ietf@ietf.org>; Mon, 17 Jul 2017 21:35:12 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170717:md50005478825::e+uvlf1MFzma66EA:00003IBh
X-MDRemoteIP: 31.133.186.60
X-Return-Path: prvs=13714351ed=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.24.0.170702
Date: Mon, 17 Jul 2017 21:35:10 +0200
Subject: Re: Revamp of the www.ietf.org website
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IETF <ietf@ietf.org>
Message-ID: <748CC45D-1DDF-4A3B-A7CC-E3F5C990D550@consulintel.es>
Thread-Topic: Revamp of the www.ietf.org website
References: <C1590F40-3B9E-45A0-9B87-59A0271B1952@consulintel.es> <20170717153147.D3EA61A6C8@ld9781.wdf.sap.corp>
In-Reply-To: <20170717153147.D3EA61A6C8@ld9781.wdf.sap.corp>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/laptPlwSqTIpTzU7twbzR4R5ukI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jul 2017 19:35:17 -0000

I disagree on this.

Having our announcements for last calls, RFC, STDs, major events, etc., in =
social media, helps to disseminate IETF activities, and we like or not soci=
al networks (I=E2=80=99m personally not a fan of them), is an obligation to=
day. Many folks will not use a mailing list to know about =E2=80=9Cnew=E2=
=80=9D IETF work, but they will happily subscribe to a facebook or tweeter =
account.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Martin Rex <mrex@sap.com>
Responder a: <mrex@sap.com>
Fecha: lunes, 17 de julio de 2017, 17:32
Para: <jordi.palet@consulintel.es>
CC: IETF <ietf@ietf.org>
Asunto: Re: Revamp of the www.ietf.org website

    JORDI PALET MARTINEZ wrote:
    >
    > I think a missing aspect of the web site, which should be prominent i=
n
    > both the home page and also the ?contact? page, is all the social med=
ia.
    >=20
    > I see there is a ?share this page? at the right of the main picture,
    > but in my opinion, is not clearly visible and is not enough
    > (the logos of the social networks should be recognized without...
   =20
    Cough, cough, WHAT???
   =20
    Please get rid of the "social media" crap entirely.  I thought that
    there was an IETF consensus that privcay is sensible and useful, and
    strong privacy protections should be the default.
   =20
   =20
    Facebook, Twitter and other "social media" crap is the far opposite of
    strongy privacy, so none of this should be encouraged or promoted by
    the IETF.
   =20
   =20
   =20
    Comparing the bandwidth necessary to load the entire homepage,
    I notice the following issues:
   =20
      https://www.ietf.org/    Total 188176 bytes (mainly by accident, it s=
eems)
                               The visible page _contents_ are just fine,
   =20
        but the page designer goofed the photo in the meeting information,
        because the picture is transferred at size 640x427 taking up 150270=
 bytes,
        although it is actually being displayed at just 200x133, where a
        pre-scaled image would need just 17 KBytes.
   =20
        Even on my 5" Smartphone, the https://www.ietf.org/ loads just fine=
,
        I get the whole picture immediately, and can zoon into my area of i=
nterest.
   =20
   =20
      http://www.ietf.org/     Total 1195800 bytes (ouch ouch ouch ouch).
   =20
        is a completely botched page design. it needs multi-page scrolldown
        even on a big desktop screen, and finding stuff has become extremel=
y
        difficult.
   =20
        This page even manages to provide *ZERO* intelligible information
        when loaded on my SmartPhone
   =20
        only shows the Welcome / Revamp <Learn More>  + Social Media Crap B=
uttons
   =20
        and when scrolling down the multiple pages of crap on my SmartPhone=
,
        very close to zero of the links _that_used_to_be_ on https://www.ie=
tf.org
        pass by.
   =20
   =20
        Normally I close such bloated ad & nag screens immediately, though
        nowadays uBlock saves my health by ensuring that most of such crap
        does not even get displayed on any of my screens (desktop & mobile)
        in the first place.
   =20
        The huge background picture (IETF-Past-Meetings.max-4000x4000.jpg)
        with 763216 Bytes is just crazy.  Is this about a party/festival?
        A *HUGE* waste of network bandwidth and memory (RAM and on-disk cac=
he)
        and writing text over photos also make reading difficult (poor cont=
rast).
   =20
   =20
   =20
    All in all, my personal summary for https://beta.ietf.org/
   =20
    disgusting and extremly bloated, usless and highly confusing.
   =20
   =20
    -Martin
   =20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Mon Jul 17 12:53:00 2017
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F23F012EC48 for <ietf@ietfa.amsl.com>; Mon, 17 Jul 2017 12:52:57 -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 XvML4Oj86xkn for <ietf@ietfa.amsl.com>; Mon, 17 Jul 2017 12:52:56 -0700 (PDT)
Received: from mail-wr0-x243.google.com (mail-wr0-x243.google.com [IPv6:2a00:1450:400c:c0c::243]) (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 76376131699 for <ietf@ietf.org>; Mon, 17 Jul 2017 12:52:50 -0700 (PDT)
Received: by mail-wr0-x243.google.com with SMTP id 23so1995355wry.3 for <ietf@ietf.org>; Mon, 17 Jul 2017 12:52:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=coulNjIEVq4SUjugFyJLXdbLUIvf7Sd9N54Cg+5kAQ4=; b=PLJlZheg4FLxVU3fnTOBrMHdcrHn5WKy2DJdNwKYHwhOpWvxNIfoIcKkeAubSLvrx5 TyipfELLnGUl2luhMBpf9Kp7R548xmBf/ogO2e1uy2cl/8S3BH7LxLXltn42MzDvsFnT AHhQVIcxiOP4oLeMbmiswp/APZIP7iu3O9Oe1G3toPLbXW2bw7bPDE4XSabBUWmSCumy Rnzx946rXQBlEzeGfUKxEuEUmwmmZ5oNOJZE9sNp4oP9omxkZSKdSWCeyjtRDxf7qsSn wuYV5Dq15+bCh+APyc7mdrPF26pcLPalTmh8h9q3AqXw/hA/FFug5QZUj33D09pnYwQ7 7AxQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=coulNjIEVq4SUjugFyJLXdbLUIvf7Sd9N54Cg+5kAQ4=; b=oFKSOUbZoMRCwpdcFrHqPBSQQv4DrkVAEzQKodt4WbVHPY3hE+P0PwgvMWUOnPVVN6 8n56TgeFsAj7/gCthWwkApP8Nc1NLvLhUggDR2kG2UQxwfiF7iVdZM/Y2KmxrhznqXD8 VlQO8XoGEmmQ0erbOqG/+dPTDELIQtAOUc7VH8dvTBx+TzI+qQDL5XqBj5trAhZxafuT FAKr2FZVgmL2/29ixSZFwlj0st2IEpBhf2mwC9qPBvstspgqbKGlKyNRO1WDH14uCuNZ 57PVh+emQ+lb4NZz5+V4+Vj/Mo+bUaOu9QNxb/op6xAx+EVW3qu0gZp2+Kwze25yFcFq YsKw==
X-Gm-Message-State: AIVw113b6xu5/90C9ATFrxg2+aimUHp+lvErtZB9KXXdnVakapgY0q4e yxIGx8r3xx4Sqg==
X-Received: by 10.223.153.234 with SMTP id y97mr14091126wrb.41.1500321167958;  Mon, 17 Jul 2017 12:52:47 -0700 (PDT)
Received: from ?IPv6:2001:67c:1232:144:5d73:168a:9aad:9a1e? ([2001:67c:1232:144:5d73:168a:9aad:9a1e]) by smtp.gmail.com with ESMTPSA id l29sm83715wre.46.2017.07.17.12.52.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 17 Jul 2017 12:52:47 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <EFB7D71B-0BC3-4C82-AE8F-27B6F18E81A4@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_5488FBBA-708B-45E3-B72E-EEBCFBC5D237"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Revamp of the www.ietf.org website
Date: Mon, 17 Jul 2017 21:52:45 +0200
In-Reply-To: <20170717153147.D3EA61A6C8@ld9781.wdf.sap.corp>
Cc: jordi.palet@consulintel.es, IETF <ietf@ietf.org>
To: mrex@sap.com
References: <20170717153147.D3EA61A6C8@ld9781.wdf.sap.corp>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/APwfxY_hz2CI0yFPpdePVYcuVLo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jul 2017 19:52:58 -0000

--Apple-Mail=_5488FBBA-708B-45E3-B72E-EEBCFBC5D237
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On 17 Jul 2017, at 17:31, Martin Rex <mrex@sap.com> wrote:
>=20
> JORDI PALET MARTINEZ wrote:
>>=20
>> I think a missing aspect of the web site, which should be prominent =
in
>> both the home page and also the ?contact? page, is all the social =
media.
>>=20
>> I see there is a ?share this page? at the right of the main picture,
>> but in my opinion, is not clearly visible and is not enough
>> (the logos of the social networks should be recognized without...
>=20
> Cough, cough, WHAT???
>=20
> Please get rid of the "social media" crap entirely.  I thought that
> there was an IETF consensus that privcay is sensible and useful, and
> strong privacy protections should be the default.
>=20
>=20
> Facebook, Twitter and other "social media" crap is the far opposite of
> strongy privacy, so none of this should be encouraged or promoted by
> the IETF.
>=20
>=20
>=20
> Comparing the bandwidth necessary to load the entire homepage,
> I notice the following issues:
>=20
>  https://www.ietf.org/    Total 188176 bytes (mainly by accident, it =
seems)
>                           The visible page _contents_ are just fine,
>=20
>    but the page designer goofed the photo in the meeting information,
>    because the picture is transferred at size 640x427 taking up 150270 =
bytes,
>    although it is actually being displayed at just 200x133, where a
>    pre-scaled image would need just 17 KBytes.
>=20
>    Even on my 5" Smartphone, the https://www.ietf.org/ loads just =
fine,
>    I get the whole picture immediately, and can zoon into my area of =
interest.
>=20
>=20
>  http://www.ietf.org/     Total 1195800 bytes (ouch ouch ouch ouch).
>=20
>    is a completely botched page design. it needs multi-page scrolldown
>    even on a big desktop screen, and finding stuff has become =
extremely
>    difficult.
>=20
>    This page even manages to provide *ZERO* intelligible information
>    when loaded on my SmartPhone
>=20
>    only shows the Welcome / Revamp <Learn More>  + Social Media Crap =
Buttons
>=20
>    and when scrolling down the multiple pages of crap on my =
SmartPhone,
>    very close to zero of the links _that_used_to_be_ on =
https://www.ietf.org
>    pass by.
>=20
>=20
>    Normally I close such bloated ad & nag screens immediately, though
>    nowadays uBlock saves my health by ensuring that most of such crap
>    does not even get displayed on any of my screens (desktop & mobile)
>    in the first place.
>=20
>    The huge background picture (IETF-Past-Meetings.max-4000x4000.jpg)
>    with 763216 Bytes is just crazy.  Is this about a party/festival?
>    A *HUGE* waste of network bandwidth and memory (RAM and on-disk =
cache)
>    and writing text over photos also make reading difficult (poor =
contrast).
>=20
>=20
>=20
> All in all, my personal summary for https://beta.ietf.org/
>=20
> disgusting and extremly bloated, usless and highly confusing.

I disagree about social media. I believe those links are useless but =
mostly harmless. Really, nobody is going to get interested in Internet =
standardization because some friend shared the front page, but I don=E2=80=
=99t lose any privacy because somebody was sent a link to a public page.

I agree about the design.

Yoav


--Apple-Mail=_5488FBBA-708B-45E3-B72E-EEBCFBC5D237
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJZbRWOAAoJELhJCxUKWMyZwjgIAJtZmcNt58Ia1tbqQXY6bop5
eVuXHN0QM0FLMVtxtM+0cIj+dqMuoBcAJg5wAT0FtbrECNOQHZwoOTgF7RSVWFM+
4cvWPJWygEcJXIGyFjGu5mpxCDvh/8X9KqFFXiPL5fHP/S5U69TOR/lCvEzTidMq
N2PG65qXewBSqH0Y/cidQwz1KAqc+qPau0c346bUIsMEfLegK/8jdL6gRqA5z6Hi
+vlf56I+Z5Yt8zrJdSDGBOTTuVobgm58teWniOjkxEojk0B9wZFS2eb/xpgyhmeL
/rEgd1myuehzydsUSA0RgXrg9ivdBpA9qjIuetLJP4LibzCBCFrIbZDxtOsHmnQ=
=MEhz
-----END PGP SIGNATURE-----

--Apple-Mail=_5488FBBA-708B-45E3-B72E-EEBCFBC5D237--


From nobody Mon Jul 17 13:11:33 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8169131B15 for <ietf@ietfa.amsl.com>; Mon, 17 Jul 2017 13:11:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 saYsBoQY03LM for <ietf@ietfa.amsl.com>; Mon, 17 Jul 2017 13:11:30 -0700 (PDT)
Received: from mail-pf0-x22c.google.com (mail-pf0-x22c.google.com [IPv6:2607:f8b0:400e:c00::22c]) (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 8260E131B12 for <ietf@ietf.org>; Mon, 17 Jul 2017 13:11:30 -0700 (PDT)
Received: by mail-pf0-x22c.google.com with SMTP id e26so227394pfd.0 for <ietf@ietf.org>; Mon, 17 Jul 2017 13:11:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=j9+5bbZ55S6RD9FT8tCUzRA1Y1Bf0oQHGw8mz4B2RwU=; b=t92jmAeR551PJaI/TJq9+Kk6tEQ4cSeb71NQ1ldrSLp6o/HbyTFZKE9Kbps4wXSBlm g8ql3ckUZC1WJG7IbXBt74d/M6kwJD03fApoSETTVQG8C4K1yZZ2wPaynV7ms6Ehur2p LC5iuSCyA9r8Flw21EcOaxTdeyc20Znm6F8jOOnh/DPZ95u6GKlUQilreAv8lCiB/rkX TbUJKZXczpIMc1wLfAvFw3Y8sKIQDKtVQTI+k3Tl3aLHNBjXRu6SHkFJQQPTQK4Fnlly CkofGlzRKOlUm9to1VzUBvt/vVCqyGDEWjD6BB1URhDPIFioKxMiLeZcDMinKEabSrMQ r7Jw==
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=j9+5bbZ55S6RD9FT8tCUzRA1Y1Bf0oQHGw8mz4B2RwU=; b=TXltNo7zbUwiN8quaEN56NWpHtIoh0uwjlCf7/6y8k7Ofr8jzGFBqXZCcHtF5zLRVJ OIvz8t+PVP8R5OJ7GkAJSTWuRGtnWVm5Zx463udUQRnXjiRRr/BbJfX2dYd+graOW13a OR+7ZBJWuLZRvIlSu2U4Yj4Vhz4QMCNacL/6HiSn+0RzwiW1wbEkFptQ9Ym7oeNf7MUG 1gtBcJjCQ5/I6XceVRij8la46O1f6QKeUorcodv5WmmROuYN4B03RCIAdZSSkOtN8HSq 6LqulXqC96TQVhYRr0GLfoDBsPjNWNwVKTKcM8MKEx6BV/tyc2NDUq9dGaFcG4DprFnI Yk2g==
X-Gm-Message-State: AIVw113YiW68FlopwG3oeQ2d2jHHjnBdDJxDxcOOYq/jYnik/3+ZMHjr muRYMqsqfPFMG3FSk56sdTGUhcn4T1wD
X-Received: by 10.98.193.68 with SMTP id i65mr6397158pfg.142.1500322289688; Mon, 17 Jul 2017 13:11:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.181.42 with HTTP; Mon, 17 Jul 2017 13:10:49 -0700 (PDT)
In-Reply-To: <EFB7D71B-0BC3-4C82-AE8F-27B6F18E81A4@gmail.com>
References: <20170717153147.D3EA61A6C8@ld9781.wdf.sap.corp> <EFB7D71B-0BC3-4C82-AE8F-27B6F18E81A4@gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Mon, 17 Jul 2017 22:10:49 +0200
Message-ID: <CAPt1N1n9cTLMZtEMTSF=X9y9coEqiS4BPm21z3MrSKdwy_2vjA@mail.gmail.com>
Subject: Re: Revamp of the www.ietf.org website
To: Yoav Nir <ynir.ietf@gmail.com>
Cc: Martin Rex <mrex@sap.com>, IETF <ietf@ietf.org>,  JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Content-Type: multipart/alternative; boundary="94eb2c184720208b5e0554890151"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5pwAX2xS3-rwjegRYT4w4jhe13s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jul 2017 20:11:33 -0000

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

The links are harmless if they aren't cross-site images.   The reason
people complain about "share" links for the various social media sites is
because they are usually embedded images loaded from those sites, which
allows those sites to track page views.

On Mon, Jul 17, 2017 at 9:52 PM, Yoav Nir <ynir.ietf@gmail.com> wrote:

>
> > On 17 Jul 2017, at 17:31, Martin Rex <mrex@sap.com> wrote:
> >
> > JORDI PALET MARTINEZ wrote:
> >>
> >> I think a missing aspect of the web site, which should be prominent in
> >> both the home page and also the ?contact? page, is all the social medi=
a.
> >>
> >> I see there is a ?share this page? at the right of the main picture,
> >> but in my opinion, is not clearly visible and is not enough
> >> (the logos of the social networks should be recognized without...
> >
> > Cough, cough, WHAT???
> >
> > Please get rid of the "social media" crap entirely.  I thought that
> > there was an IETF consensus that privcay is sensible and useful, and
> > strong privacy protections should be the default.
> >
> >
> > Facebook, Twitter and other "social media" crap is the far opposite of
> > strongy privacy, so none of this should be encouraged or promoted by
> > the IETF.
> >
> >
> >
> > Comparing the bandwidth necessary to load the entire homepage,
> > I notice the following issues:
> >
> >  https://www.ietf.org/    Total 188176 bytes (mainly by accident, it
> seems)
> >                           The visible page _contents_ are just fine,
> >
> >    but the page designer goofed the photo in the meeting information,
> >    because the picture is transferred at size 640x427 taking up 150270
> bytes,
> >    although it is actually being displayed at just 200x133, where a
> >    pre-scaled image would need just 17 KBytes.
> >
> >    Even on my 5" Smartphone, the https://www.ietf.org/ loads just fine,
> >    I get the whole picture immediately, and can zoon into my area of
> interest.
> >
> >
> >  http://www.ietf.org/     Total 1195800 bytes (ouch ouch ouch ouch).
> >
> >    is a completely botched page design. it needs multi-page scrolldown
> >    even on a big desktop screen, and finding stuff has become extremely
> >    difficult.
> >
> >    This page even manages to provide *ZERO* intelligible information
> >    when loaded on my SmartPhone
> >
> >    only shows the Welcome / Revamp <Learn More>  + Social Media Crap
> Buttons
> >
> >    and when scrolling down the multiple pages of crap on my SmartPhone,
> >    very close to zero of the links _that_used_to_be_ on
> https://www.ietf.org
> >    pass by.
> >
> >
> >    Normally I close such bloated ad & nag screens immediately, though
> >    nowadays uBlock saves my health by ensuring that most of such crap
> >    does not even get displayed on any of my screens (desktop & mobile)
> >    in the first place.
> >
> >    The huge background picture (IETF-Past-Meetings.max-4000x4000.jpg)
> >    with 763216 Bytes is just crazy.  Is this about a party/festival?
> >    A *HUGE* waste of network bandwidth and memory (RAM and on-disk cach=
e)
> >    and writing text over photos also make reading difficult (poor
> contrast).
> >
> >
> >
> > All in all, my personal summary for https://beta.ietf.org/
> >
> > disgusting and extremly bloated, usless and highly confusing.
>
> I disagree about social media. I believe those links are useless but
> mostly harmless. Really, nobody is going to get interested in Internet
> standardization because some friend shared the front page, but I don=E2=
=80=99t lose
> any privacy because somebody was sent a link to a public page.
>
> I agree about the design.
>
> Yoav
>
>

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

<div dir=3D"ltr">The links are harmless if they aren&#39;t cross-site image=
s. =C2=A0 The reason people complain about &quot;share&quot; links for the =
various social media sites is because they are usually embedded images load=
ed from those sites, which allows those sites to track page views.</div><di=
v class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Jul 17, 2017=
 at 9:52 PM, Yoav Nir <span dir=3D"ltr">&lt;<a href=3D"mailto:ynir.ietf@gma=
il.com" target=3D"_blank">ynir.ietf@gmail.com</a>&gt;</span> wrote:<br><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt; On 17 Jul 2017, at 17:31, Martin Rex &lt;<a href=3D"mailto:mrex@sap.co=
m">mrex@sap.com</a>&gt; wrote:<br>
&gt;<br>
&gt; JORDI PALET MARTINEZ wrote:<br>
&gt;&gt;<br>
&gt;&gt; I think a missing aspect of the web site, which should be prominen=
t in<br>
&gt;&gt; both the home page and also the ?contact? page, is all the social =
media.<br>
&gt;&gt;<br>
&gt;&gt; I see there is a ?share this page? at the right of the main pictur=
e,<br>
&gt;&gt; but in my opinion, is not clearly visible and is not enough<br>
&gt;&gt; (the logos of the social networks should be recognized without...<=
br>
&gt;<br>
&gt; Cough, cough, WHAT???<br>
&gt;<br>
&gt; Please get rid of the &quot;social media&quot; crap entirely.=C2=A0 I =
thought that<br>
&gt; there was an IETF consensus that privcay is sensible and useful, and<b=
r>
&gt; strong privacy protections should be the default.<br>
&gt;<br>
&gt;<br>
&gt; Facebook, Twitter and other &quot;social media&quot; crap is the far o=
pposite of<br>
&gt; strongy privacy, so none of this should be encouraged or promoted by<b=
r>
&gt; the IETF.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Comparing the bandwidth necessary to load the entire homepage,<br>
&gt; I notice the following issues:<br>
&gt;<br>
&gt;=C2=A0 <a href=3D"https://www.ietf.org/" rel=3D"noreferrer" target=3D"_=
blank">https://www.ietf.org/</a>=C2=A0 =C2=A0 Total 188176 bytes (mainly by=
 accident, it seems)<br>
&gt;=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=A0The visible page _contents_ are just fine,<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 but the page designer goofed the photo in the meeting inf=
ormation,<br>
&gt;=C2=A0 =C2=A0 because the picture is transferred at size 640x427 taking=
 up 150270 bytes,<br>
&gt;=C2=A0 =C2=A0 although it is actually being displayed at just 200x133, =
where a<br>
&gt;=C2=A0 =C2=A0 pre-scaled image would need just 17 KBytes.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Even on my 5&quot; Smartphone, the <a href=3D"https://www=
.ietf.org/" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/</a> =
loads just fine,<br>
&gt;=C2=A0 =C2=A0 I get the whole picture immediately, and can zoon into my=
 area of interest.<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 <a href=3D"http://www.ietf.org/" rel=3D"noreferrer" target=3D"_b=
lank">http://www.ietf.org/</a>=C2=A0 =C2=A0 =C2=A0Total 1195800 bytes (ouch=
 ouch ouch ouch).<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 is a completely botched page design. it needs multi-page =
scrolldown<br>
&gt;=C2=A0 =C2=A0 even on a big desktop screen, and finding stuff has becom=
e extremely<br>
&gt;=C2=A0 =C2=A0 difficult.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 This page even manages to provide *ZERO* intelligible inf=
ormation<br>
&gt;=C2=A0 =C2=A0 when loaded on my SmartPhone<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 only shows the Welcome / Revamp &lt;Learn More&gt;=C2=A0 =
+ Social Media Crap Buttons<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 and when scrolling down the multiple pages of crap on my =
SmartPhone,<br>
&gt;=C2=A0 =C2=A0 very close to zero of the links _that_used_to_be_ on <a h=
ref=3D"https://www.ietf.org" rel=3D"noreferrer" target=3D"_blank">https://w=
ww.ietf.org</a><br>
&gt;=C2=A0 =C2=A0 pass by.<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Normally I close such bloated ad &amp; nag screens immedi=
ately, though<br>
&gt;=C2=A0 =C2=A0 nowadays uBlock saves my health by ensuring that most of =
such crap<br>
&gt;=C2=A0 =C2=A0 does not even get displayed on any of my screens (desktop=
 &amp; mobile)<br>
&gt;=C2=A0 =C2=A0 in the first place.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 The huge background picture (IETF-Past-Meetings.max-<wbr>=
4000x4000.jpg)<br>
&gt;=C2=A0 =C2=A0 with 763216 Bytes is just crazy.=C2=A0 Is this about a pa=
rty/festival?<br>
&gt;=C2=A0 =C2=A0 A *HUGE* waste of network bandwidth and memory (RAM and o=
n-disk cache)<br>
&gt;=C2=A0 =C2=A0 and writing text over photos also make reading difficult =
(poor contrast).<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; All in all, my personal summary for <a href=3D"https://beta.ietf.org/"=
 rel=3D"noreferrer" target=3D"_blank">https://beta.ietf.org/</a><br>
&gt;<br>
&gt; disgusting and extremly bloated, usless and highly confusing.<br>
<br>
</div></div>I disagree about social media. I believe those links are useles=
s but mostly harmless. Really, nobody is going to get interested in Interne=
t standardization because some friend shared the front page, but I don=E2=
=80=99t lose any privacy because somebody was sent a link to a public page.=
<br>
<br>
I agree about the design.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Yoav<br>
<br>
</font></span></blockquote></div><br></div>

--94eb2c184720208b5e0554890151--


From nobody Mon Jul 17 13:23:55 2017
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38DD8129B2A for <ietf@ietfa.amsl.com>; Mon, 17 Jul 2017 13:23:53 -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, 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 WwYqMGK_kC2e for <ietf@ietfa.amsl.com>; Mon, 17 Jul 2017 13:23:50 -0700 (PDT)
Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (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 55F111201F8 for <ietf@ietf.org>; Mon, 17 Jul 2017 13:23:50 -0700 (PDT)
Received: by mail-wm0-x241.google.com with SMTP id p204so986668wmg.1 for <ietf@ietf.org>; Mon, 17 Jul 2017 13:23:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=LTKy4blojweCWnfLUjzq5dmgrWDakdIE8xrYtHvdaog=; b=vZ6ZHt40f1dLWnNzpAAGBlqC1qcYBVjlkPBGbGEMOlT/XpLMXFaCpTRAGm2daUm3k+ WbxRxVp6wCk3qUD+MzWnL2zlBJEhJ/yYpgGKmmYxo2WrzS5XN+11RpXHM/PC2fbJba2h DPgCSzls5gG3y1Z7WjLIEkzqBXq83F6WmUR3Qjpm/Ue9qGyhmJiLbHKRzkRu0G85mGdc +dwR2eNXCkg9BHLe5NbQEDhRhvw3boDnHD+KA9vacUDck5jqU+kjiiiJoz7pQz+nPx+d SKqnlUb1HQKkcKEvL2fWM1+ckjki54NjTrzvVri8yFPJQBpcf2QhKPv3ukZH1sVyv6d0 Lp7A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=LTKy4blojweCWnfLUjzq5dmgrWDakdIE8xrYtHvdaog=; b=BtAeqm9cl0inqlRGMj4luawM/U1PfazueN/h/OYDB7hewIwPPpmcXP+vf6A0hl+Sud noki4RApsI+An8AbRvm6N1fvm7ztDbQup4YBv8SEeXcIwmITO18O+HFj3ICYTMLtePZb zh89T8ADsi2JO5hKYv5P+71r+J6R6PyGtzFuW0ZS0r53oS2myXYjI2fDy+R87hCIt3/K Z21bQbU5rNYDmg+XOgdfFPXPw1YAmDEIUedJm93UpJ0uyN8NHlPXceLTu387PeAoWCry K5fYv10/sAnSqwmDf/BDgJXMtkBWmgxPWTBg8bhvCyksBl1Jjs80NmdI+lY+C9sHCZpE gJlA==
X-Gm-Message-State: AIVw110UZW+rneAwsQ0yaGxjf/+341VPAhHSCgAqkO5Nvh6o3GAmUJAj hqTV7Md9a98lZl7G4N8=
X-Received: by 10.28.94.201 with SMTP id s192mr5572107wmb.100.1500323027285; Mon, 17 Jul 2017 13:23:47 -0700 (PDT)
Received: from ?IPv6:2001:67c:1232:144:5d73:168a:9aad:9a1e? ([2001:67c:1232:144:5d73:168a:9aad:9a1e]) by smtp.gmail.com with ESMTPSA id a3sm171015wra.17.2017.07.17.13.23.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 17 Jul 2017 13:23:46 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <A991682B-2388-4EB3-BD5E-1805054C41ED@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_7793EC2B-D50D-4228-AC24-817E8821AF69"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Revamp of the www.ietf.org website
Date: Mon, 17 Jul 2017 22:23:43 +0200
In-Reply-To: <CAPt1N1n9cTLMZtEMTSF=X9y9coEqiS4BPm21z3MrSKdwy_2vjA@mail.gmail.com>
Cc: Martin Rex <mrex@sap.com>, IETF <ietf@ietf.org>, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: Ted Lemon <mellon@fugue.com>
References: <20170717153147.D3EA61A6C8@ld9781.wdf.sap.corp> <EFB7D71B-0BC3-4C82-AE8F-27B6F18E81A4@gmail.com> <CAPt1N1n9cTLMZtEMTSF=X9y9coEqiS4BPm21z3MrSKdwy_2vjA@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aWzK4XwJ4y54GedW95tby6txlHw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jul 2017 20:23:53 -0000

--Apple-Mail=_7793EC2B-D50D-4228-AC24-817E8821AF69
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_66A9F1C9-9CE3-438A-824D-96DE3CF8B553"


--Apple-Mail=_66A9F1C9-9CE3-438A-824D-96DE3CF8B553
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Well, the facebook and Twitter icons seem to be embedded in the web =
page, not loaded from the social media websites, so we don=E2=80=99t =
need to worry about that at least.


> On 17 Jul 2017, at 22:10, Ted Lemon <mellon@fugue.com> wrote:
>=20
> The links are harmless if they aren't cross-site images.   The reason =
people complain about "share" links for the various social media sites =
is because they are usually embedded images loaded from those sites, =
which allows those sites to track page views.
>=20
> On Mon, Jul 17, 2017 at 9:52 PM, Yoav Nir <ynir.ietf@gmail.com =
<mailto:ynir.ietf@gmail.com>> wrote:
>=20
> > On 17 Jul 2017, at 17:31, Martin Rex <mrex@sap.com =
<mailto:mrex@sap.com>> wrote:
> >
> > JORDI PALET MARTINEZ wrote:
> >>
> >> I think a missing aspect of the web site, which should be prominent =
in
> >> both the home page and also the ?contact? page, is all the social =
media.
> >>
> >> I see there is a ?share this page? at the right of the main =
picture,
> >> but in my opinion, is not clearly visible and is not enough
> >> (the logos of the social networks should be recognized without...
> >
> > Cough, cough, WHAT???
> >
> > Please get rid of the "social media" crap entirely.  I thought that
> > there was an IETF consensus that privcay is sensible and useful, and
> > strong privacy protections should be the default.
> >
> >
> > Facebook, Twitter and other "social media" crap is the far opposite =
of
> > strongy privacy, so none of this should be encouraged or promoted by
> > the IETF.
> >
> >
> >
> > Comparing the bandwidth necessary to load the entire homepage,
> > I notice the following issues:
> >
> >  https://www.ietf.org/ <https://www.ietf.org/>    Total 188176 bytes =
(mainly by accident, it seems)
> >                           The visible page _contents_ are just fine,
> >
> >    but the page designer goofed the photo in the meeting =
information,
> >    because the picture is transferred at size 640x427 taking up =
150270 bytes,
> >    although it is actually being displayed at just 200x133, where a
> >    pre-scaled image would need just 17 KBytes.
> >
> >    Even on my 5" Smartphone, the https://www.ietf.org/ =
<https://www.ietf.org/> loads just fine,
> >    I get the whole picture immediately, and can zoon into my area of =
interest.
> >
> >
> >  http://www.ietf.org/ <http://www.ietf.org/>     Total 1195800 bytes =
(ouch ouch ouch ouch).
> >
> >    is a completely botched page design. it needs multi-page =
scrolldown
> >    even on a big desktop screen, and finding stuff has become =
extremely
> >    difficult.
> >
> >    This page even manages to provide *ZERO* intelligible information
> >    when loaded on my SmartPhone
> >
> >    only shows the Welcome / Revamp <Learn More>  + Social Media Crap =
Buttons
> >
> >    and when scrolling down the multiple pages of crap on my =
SmartPhone,
> >    very close to zero of the links _that_used_to_be_ on =
https://www.ietf.org <https://www.ietf.org/>
> >    pass by.
> >
> >
> >    Normally I close such bloated ad & nag screens immediately, =
though
> >    nowadays uBlock saves my health by ensuring that most of such =
crap
> >    does not even get displayed on any of my screens (desktop & =
mobile)
> >    in the first place.
> >
> >    The huge background picture =
(IETF-Past-Meetings.max-4000x4000.jpg)
> >    with 763216 Bytes is just crazy.  Is this about a party/festival?
> >    A *HUGE* waste of network bandwidth and memory (RAM and on-disk =
cache)
> >    and writing text over photos also make reading difficult (poor =
contrast).
> >
> >
> >
> > All in all, my personal summary for https://beta.ietf.org/ =
<https://beta.ietf.org/>
> >
> > disgusting and extremly bloated, usless and highly confusing.
>=20
> I disagree about social media. I believe those links are useless but =
mostly harmless. Really, nobody is going to get interested in Internet =
standardization because some friend shared the front page, but I don=E2=80=
=99t lose any privacy because somebody was sent a link to a public page.
>=20
> I agree about the design.
>=20
> Yoav
>=20
>=20


--Apple-Mail=_66A9F1C9-9CE3-438A-824D-96DE3CF8B553
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Well, the facebook and Twitter icons seem to be embedded in =
the web page, not loaded from the social media websites, so we don=E2=80=99=
t need to worry about that at least.<div class=3D""><br =
class=3D""></div><div class=3D""><br class=3D""><div><blockquote =
type=3D"cite" class=3D""><div class=3D"">On 17 Jul 2017, at 22:10, Ted =
Lemon &lt;<a href=3D"mailto:mellon@fugue.com" =
class=3D"">mellon@fugue.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
class=3D"">The links are harmless if they aren't cross-site images. =
&nbsp; The reason people complain about "share" links for the various =
social media sites is because they are usually embedded images loaded =
from those sites, which allows those sites to track page =
views.</div><div class=3D"gmail_extra"><br class=3D""><div =
class=3D"gmail_quote">On Mon, Jul 17, 2017 at 9:52 PM, Yoav Nir <span =
dir=3D"ltr" class=3D"">&lt;<a href=3D"mailto:ynir.ietf@gmail.com" =
target=3D"_blank" class=3D"">ynir.ietf@gmail.com</a>&gt;</span> =
wrote:<br class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div =
class=3D"HOEnZb"><div class=3D"h5"><br class=3D"">
&gt; On 17 Jul 2017, at 17:31, Martin Rex &lt;<a =
href=3D"mailto:mrex@sap.com" class=3D"">mrex@sap.com</a>&gt; wrote:<br =
class=3D"">
&gt;<br class=3D"">
&gt; JORDI PALET MARTINEZ wrote:<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt; I think a missing aspect of the web site, which should be =
prominent in<br class=3D"">
&gt;&gt; both the home page and also the ?contact? page, is all the =
social media.<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt; I see there is a ?share this page? at the right of the main =
picture,<br class=3D"">
&gt;&gt; but in my opinion, is not clearly visible and is not enough<br =
class=3D"">
&gt;&gt; (the logos of the social networks should be recognized =
without...<br class=3D"">
&gt;<br class=3D"">
&gt; Cough, cough, WHAT???<br class=3D"">
&gt;<br class=3D"">
&gt; Please get rid of the "social media" crap entirely.&nbsp; I thought =
that<br class=3D"">
&gt; there was an IETF consensus that privcay is sensible and useful, =
and<br class=3D"">
&gt; strong privacy protections should be the default.<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt; Facebook, Twitter and other "social media" crap is the far opposite =
of<br class=3D"">
&gt; strongy privacy, so none of this should be encouraged or promoted =
by<br class=3D"">
&gt; the IETF.<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt; Comparing the bandwidth necessary to load the entire homepage,<br =
class=3D"">
&gt; I notice the following issues:<br class=3D"">
&gt;<br class=3D"">
&gt;&nbsp; <a href=3D"https://www.ietf.org/" rel=3D"noreferrer" =
target=3D"_blank" class=3D"">https://www.ietf.org/</a>&nbsp; &nbsp; =
Total 188176 bytes (mainly by accident, it seems)<br class=3D"">
&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;The visible page _contents_ are just =
fine,<br class=3D"">
&gt;<br class=3D"">
&gt;&nbsp; &nbsp; but the page designer goofed the photo in the meeting =
information,<br class=3D"">
&gt;&nbsp; &nbsp; because the picture is transferred at size 640x427 =
taking up 150270 bytes,<br class=3D"">
&gt;&nbsp; &nbsp; although it is actually being displayed at just =
200x133, where a<br class=3D"">
&gt;&nbsp; &nbsp; pre-scaled image would need just 17 KBytes.<br =
class=3D"">
&gt;<br class=3D"">
&gt;&nbsp; &nbsp; Even on my 5" Smartphone, the <a =
href=3D"https://www.ietf.org/" rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/</a> loads just fine,<br class=3D"">
&gt;&nbsp; &nbsp; I get the whole picture immediately, and can zoon into =
my area of interest.<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt;&nbsp; <a href=3D"http://www.ietf.org/" rel=3D"noreferrer" =
target=3D"_blank" class=3D"">http://www.ietf.org/</a>&nbsp; &nbsp; =
&nbsp;Total 1195800 bytes (ouch ouch ouch ouch).<br class=3D"">
&gt;<br class=3D"">
&gt;&nbsp; &nbsp; is a completely botched page design. it needs =
multi-page scrolldown<br class=3D"">
&gt;&nbsp; &nbsp; even on a big desktop screen, and finding stuff has =
become extremely<br class=3D"">
&gt;&nbsp; &nbsp; difficult.<br class=3D"">
&gt;<br class=3D"">
&gt;&nbsp; &nbsp; This page even manages to provide *ZERO* intelligible =
information<br class=3D"">
&gt;&nbsp; &nbsp; when loaded on my SmartPhone<br class=3D"">
&gt;<br class=3D"">
&gt;&nbsp; &nbsp; only shows the Welcome / Revamp &lt;Learn =
More&gt;&nbsp; + Social Media Crap Buttons<br class=3D"">
&gt;<br class=3D"">
&gt;&nbsp; &nbsp; and when scrolling down the multiple pages of crap on =
my SmartPhone,<br class=3D"">
&gt;&nbsp; &nbsp; very close to zero of the links _that_used_to_be_ on =
<a href=3D"https://www.ietf.org/" rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org</a><br class=3D"">
&gt;&nbsp; &nbsp; pass by.<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt;&nbsp; &nbsp; Normally I close such bloated ad &amp; nag screens =
immediately, though<br class=3D"">
&gt;&nbsp; &nbsp; nowadays uBlock saves my health by ensuring that most =
of such crap<br class=3D"">
&gt;&nbsp; &nbsp; does not even get displayed on any of my screens =
(desktop &amp; mobile)<br class=3D"">
&gt;&nbsp; &nbsp; in the first place.<br class=3D"">
&gt;<br class=3D"">
&gt;&nbsp; &nbsp; The huge background picture =
(IETF-Past-Meetings.max-<wbr class=3D"">4000x4000.jpg)<br class=3D"">
&gt;&nbsp; &nbsp; with 763216 Bytes is just crazy.&nbsp; Is this about a =
party/festival?<br class=3D"">
&gt;&nbsp; &nbsp; A *HUGE* waste of network bandwidth and memory (RAM =
and on-disk cache)<br class=3D"">
&gt;&nbsp; &nbsp; and writing text over photos also make reading =
difficult (poor contrast).<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt; All in all, my personal summary for <a =
href=3D"https://beta.ietf.org/" rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://beta.ietf.org/</a><br class=3D"">
&gt;<br class=3D"">
&gt; disgusting and extremly bloated, usless and highly confusing.<br =
class=3D"">
<br class=3D"">
</div></div>I disagree about social media. I believe those links are =
useless but mostly harmless. Really, nobody is going to get interested =
in Internet standardization because some friend shared the front page, =
but I don=E2=80=99t lose any privacy because somebody was sent a link to =
a public page.<br class=3D"">
<br class=3D"">
I agree about the design.<br class=3D"">
<span class=3D"HOEnZb"><font color=3D"#888888" class=3D""><br class=3D"">
Yoav<br class=3D"">
<br class=3D"">
</font></span></blockquote></div><br class=3D""></div>
</div></blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_66A9F1C9-9CE3-438A-824D-96DE3CF8B553--

--Apple-Mail=_7793EC2B-D50D-4228-AC24-817E8821AF69
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJZbRzQAAoJELhJCxUKWMyZsdkIALzHRQNWrsGotOUhQcKRXg5P
/WNdW6FzGuk2srHujzTSIxsRIv8vdGEtlnxrAqecyGVuhpiGpuSV2KS0cC9MeqX4
6KrrvwDabpGbyHUnxWVrByh4r9nFk3Q0WxOP48kPLFFyQixFVU5IO/vvtXTH+kHT
rL1ztxjYVL4A9T1Wm6EsTSKaSU8GxZM9w3MnZrDQ1qV09qvww9+tMvEhhlFLKMeu
QnO//qJOxKNpBgI54IUVFOMF+WLUWtwAhiQp+O/7zu6pZallalkr7wIbTZNWbUSE
w1IRs5O6RMfPq5KrfViOXKHdKPD9Rk+4sqYD7hyi696UaqYU5j1scFf4cDplacI=
=yOmV
-----END PGP SIGNATURE-----

--Apple-Mail=_7793EC2B-D50D-4228-AC24-817E8821AF69--


From nobody Mon Jul 17 14:09:02 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC83E129ACD for <ietf@ietfa.amsl.com>; Mon, 17 Jul 2017 14:09:00 -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, RP_MATCHES_RCVD=-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 kUsIr1S0l-bH for <ietf@ietfa.amsl.com>; Mon, 17 Jul 2017 14:08:59 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D08301294A2 for <ietf@ietf.org>; Mon, 17 Jul 2017 14:08:58 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dXDGC-000G0T-K3; Mon, 17 Jul 2017 17:08:56 -0400
Date: Mon, 17 Jul 2017 17:08:50 -0400
From: John C Klensin <john-ietf@jck.com>
To: jordi.palet@consulintel.es
cc: IETF <ietf@ietf.org>
Subject: Re: Revamp of the www.ietf.org website
Message-ID: <F6924008EE2D26C4925CAD2D@PSB>
In-Reply-To: <748CC45D-1DDF-4A3B-A7CC-E3F5C990D550@consulintel.es>
References: <C1590F40-3B9E-45A0-9B87-59A0271B1952@consulintel.es> <20170717153147.D3EA61A6C8@ld9781.wdf.sap.corp> <748CC45D-1DDF-4A3B-A7CC-E3F5C990D550@consulintel.es>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gJjHr-_Fufe90boTSZKmlkegiYw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jul 2017 21:09:01 -0000

Jordi,

Three observations.  

* Noting that assorted social media are, from time to time, more
or less effectively blocked in assorted countries, I think we
need to be sure that all IETF participants are able to get to
all IETF announcements and materials on an equal basis unless
the IETF itself is blocked.  If someone wants to reflect IETF
announcements into some social media or supplemental mailing
list, that is fine and has been going on for years, but
substantive announcements and discussions need to stay on IETF
mailing lists and be archived on IETF facilities or we end up
with big openness and transparency problems. 

* Precisely because the IETF has some very large vendors among
its supporters, our being able to continue to claim that we are
not biased toward those vendors and that our standards decisions
are not for sale, we need to be careful about not forcing people
to contribute to the bottom line of those companies in order to
participate.  We've been reasonably careful (much more careful
than some other SDOs) to not require someone to purchase some
particular work processing package or office suite to
participate.   I suggest that, if the IETF is going to get tied
up with Social Media, the system(s) used must be ones that do
not have business models involving  "user as product", targeted
advertising to users, permission to spam users, or requirements
that users give up significant privacy in order to join, get
feeds. or equ9ivalent.  Again, if someone wants to re-{post,
chirp, tweet, vomit, etc.} materials from an IETF mailing list,
I think we have always allowed thet.  However, IMO, the IETF
needs to be really careful about getting more directly involved.

* I share Martin's concern about page size, complexity, and load
times, especially if we are serious about trying to involve
people in developing countries and otherwise with with marginal
connections. 

best,
    john


--On Monday, July 17, 2017 21:35 +0200 JORDI PALET MARTINEZ
<jordi.palet@consulintel.es> wrote:

> I disagree on this.
> 
> Having our announcements for last calls, RFC, STDs, major
> events, etc., in social media, helps to disseminate IETF
> activities, and we like or not social networks (I'm
> personally not a fan of them), is an obligation today. Many
> folks will not use a mailing list to know about "new" IETF
> work, but they will happily subscribe to a facebook or tweeter
> account.
> 
> Regards,
> Jordi
>  
> 
> -----Mensaje original-----
> De: ietf <ietf-bounces@ietf.org> en nombre de Martin Rex
> <mrex@sap.com> Responder a: <mrex@sap.com>
> Fecha: lunes, 17 de julio de 2017, 17:32
> Para: <jordi.palet@consulintel.es>
> CC: IETF <ietf@ietf.org>
> Asunto: Re: Revamp of the www.ietf.org website
> 
>     JORDI PALET MARTINEZ wrote:
>     >
>     > I think a missing aspect of the web site, which should
> be prominent in     > both the home page and also the
> ?contact? page, is all the social media.     > 
>     > I see there is a ?share this page? at the right of the
> main picture,     > but in my opinion, is not clearly visible
> and is not enough     > (the logos of the social networks
> should be recognized without...     
>     Cough, cough, WHAT???
>     
>     Please get rid of the "social media" crap entirely.  I
> thought that     there was an IETF consensus that privcay is
> sensible and useful, and     strong privacy protections should
> be the default.     
>     
>     Facebook, Twitter and other "social media" crap is the far
> opposite of     strongy privacy, so none of this should be
> encouraged or promoted by     the IETF.
>     
>     
>     
>     Comparing the bandwidth necessary to load the entire
> homepage,     I notice the following issues:
>     
>       https://www.ietf.org/    Total 188176 bytes (mainly by
> accident, it seems)                                The visible
> page _contents_ are just fine,     
>         but the page designer goofed the photo in the meeting
> information,         because the picture is transferred at
> size 640x427 taking up 150270 bytes,         although it is
> actually being displayed at just 200x133, where a
> pre-scaled image would need just 17 KBytes.
>     
>         Even on my 5" Smartphone, the https://www.ietf.org/
> loads just fine,         I get the whole picture immediately,
> and can zoon into my area of interest.     
>     
>       http://www.ietf.org/     Total 1195800 bytes (ouch ouch
> ouch ouch).     
>         is a completely botched page design. it needs
> multi-page scrolldown         even on a big desktop screen,
> and finding stuff has become extremely         difficult.
>     
>         This page even manages to provide *ZERO* intelligible
> information         when loaded on my SmartPhone
>     
>         only shows the Welcome / Revamp <Learn More>  + Social
> Media Crap Buttons     
>         and when scrolling down the multiple pages of crap on
> my SmartPhone,         very close to zero of the links
> _that_used_to_be_ on https://www.ietf.org         pass by.
>     
>     
>         Normally I close such bloated ad & nag screens
> immediately, though         nowadays uBlock saves my health by
> ensuring that most of such crap         does not even get
> displayed on any of my screens (desktop & mobile)         in
> the first place.
>     
>         The huge background picture
> (IETF-Past-Meetings.max-4000x4000.jpg)         with 763216
> Bytes is just crazy.  Is this about a party/festival?
> A *HUGE* waste of network bandwidth and memory (RAM and
> on-disk cache)         and writing text over photos also make
> reading difficult (poor contrast).     
>     
>     
>     All in all, my personal summary for https://beta.ietf.org/
>     
>     disgusting and extremly bloated, usless and highly
> confusing.     
>     
>     -Martin
>     
>     
>     
> 
> 
> 
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.consulintel.es
> The IPv6 Company
> 
> This electronic message contains information which may be
> privileged or confidential. The information is intended to be
> for the use of the individual(s) named above. If you are not
> the intended recipient be aware that any disclosure, copying,
> distribution or use of the contents of this information,
> including attached files, is prohibited.
> 
> 
> 





From nobody Mon Jul 17 19:43:03 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BEB912ECB0 for <ietf@ietfa.amsl.com>; Mon, 17 Jul 2017 19:43:01 -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 NMDYlm8g_7Ad for <ietf@ietfa.amsl.com>; Mon, 17 Jul 2017 19:43:00 -0700 (PDT)
Received: from mail-pf0-x22c.google.com (mail-pf0-x22c.google.com [IPv6:2607:f8b0:400e:c00::22c]) (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 E188B127076 for <ietf@ietf.org>; Mon, 17 Jul 2017 19:42:59 -0700 (PDT)
Received: by mail-pf0-x22c.google.com with SMTP id q86so3960236pfl.3 for <ietf@ietf.org>; Mon, 17 Jul 2017 19:42:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=ccCS1O0q8D2CCvaswQbD/zoI9MFcvQGzf1fViI8kUAs=; b=J1fEFGcupSfDqMqCcJpVKHY34fzaFxUs4DJQ31V3qSlV4KOwBPWAepI5qSJNtJLvhm 5/oelZc2xtN+/wAYRUBfwk5bfu3z7hRwC4ZUljj2x/LutIRf9mwyjgHnjPrOmml59yA+ RdWTKoxMsmn65gNEVOcOlnYoad4RvcUeYqxjaBke7vs5w86oqab7GG5pIPrOxmbq4G0B ifBUtTJicQ+/ulS6SbkBMTu4FGKcUMGU1LTZiniX3oWolFhBvZ/kLcdW4+9Rdoe2RNQF fdrAtT5JAtHNj38354yWq9yaHhjT2ykq7n3Y+AC/L7EfKRd/IkbrfeMh+eLn9SQHPCrw qKpQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=ccCS1O0q8D2CCvaswQbD/zoI9MFcvQGzf1fViI8kUAs=; b=it0GXQsfXofWbZOHvO/w4bgb42Ffj80zHq1UmLmVaUE98FKDmjWdBnjvECtNVY/yHK 8ceErRp1z82Dlh3sJ6pC1W0+LNVcgO/Mx/R2yhAidrDIbs/XRMmN/fSjDHRIUmRLqi4r qBhdD/zy6EmaiE/WiUVF4Rz++KigE3buZyUb5E9XWJBGEvGfLCp6emsizWCUP/swouM5 5SW6Qq+O2gdeiGe9qOSAmAmJRRulEgdNL5yKkkfzF4Ad4F6kahLq3YQGAIRR+aqwroS5 ISs7yFRK212JTzsAXKiTNJFDBcZI3syRIC+vbpgOrirEG1YcSYuz8vkxtG71j+eGXlb6 +BkQ==
X-Gm-Message-State: AIVw1136MdT1huEGwv9YY6eyePilMFOb7r7Sn1jGdZiT0NJV5S8xTTdK f9pCFihr3UM++PL9
X-Received: by 10.84.167.230 with SMTP id i35mr741528plg.181.1500345779336; Mon, 17 Jul 2017 19:42:59 -0700 (PDT)
Received: from ?IPv6:2001:df0:0:2006:c0da:ac17:5f6d:8e76? ([2001:df0:0:2006:c0da:ac17:5f6d:8e76]) by smtp.gmail.com with ESMTPSA id h90sm1042631pfh.133.2017.07.17.19.42.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 17 Jul 2017 19:42:58 -0700 (PDT)
Subject: Re: Revamp of the www.ietf.org website
To: Russ Housley <housley@vigilsec.com>, IETF <ietf@ietf.org>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <c9c759cd-2d56-1367-4e42-644b83f46f13@gmail.com>
Date: Tue, 18 Jul 2017 14:42:56 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yiSJ474onFkPhlQti6gyfBO5rbw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 02:43:01 -0000

On 15/07/2017 21:21, Russ Housley wrote:
...
> For example, in response to the feedback provided, there is now a single page that provides links to tools and resources commonly used by active IETF participants.

Thank you for that. The only thing is, it's not really a single page; I had to hit Page Down 4 times to see everything. On the current page (https://www.ietf.org/content.html) there's all that on one screen. Surely there must be a way to present the content more compactly, when not on a tiny screen, and with a default font size.

I mention that here because I think it's a very general point. I've entered tickets for some details, and I would encourage everybody to do that, because inevitably there will be errors in content conversion, and the more eyes looking for them, the better.

Thanks
    Brian


From nobody Mon Jul 17 22:52:40 2017
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C736129459; Mon, 17 Jul 2017 22:52:32 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Jaeggli <joelja@bogus.com>
To: <ops-dir@ietf.org>
Cc: draft-ietf-curdle-des-des-des-die-die-die.all@ietf.org, curdle@ietf.org, ietf@ietf.org
Subject: Opsdir last call review of draft-ietf-curdle-des-des-des-die-die-die-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.56.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150035715254.11356.14739890140093835216@ietfa.amsl.com>
Date: Mon, 17 Jul 2017 22:52:32 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/G8Pxsa7m07jxTmQcxDXqqbiYbWE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 05:52:32 -0000

Reviewer: Joel Jaeggli
Review result: Ready

Hello,

I have reviewed this document for operational considerations as part of the
IETF last call.

Depreciation of the listed encryption algorithms when it occurs will leave
behind certain legacy systems with respect to interoperability. This is
expected and normal. There are not other serious problems anticipated with the
advice provided in this document.

I believe that it is ready for publication.

Regards
Joel



From nobody Mon Jul 17 23:31:07 2017
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFC2A131548 for <ietf@ietfa.amsl.com>; Mon, 17 Jul 2017 23:31:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 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_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=mnot.net header.b=OiQwheZs; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=GJ42JYto
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 SauDSJCpvzyv for <ietf@ietfa.amsl.com>; Mon, 17 Jul 2017 23:31:03 -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 2E6B4131475 for <ietf@ietf.org>; Mon, 17 Jul 2017 23:31:03 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id A043020929; Tue, 18 Jul 2017 02:31:01 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Tue, 18 Jul 2017 02:31:01 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; 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=nc6BlLt3LDRgsZnXYy 2gCKoqvDwu8XWfH/8BuBjAIr8=; b=OiQwheZsS5qnTRTCQPCv45NgPwwV9vNNCd UY2i/SncipxSxg/OBZNPOEA6Uz9QmXvCIon45dqUuRmjw5KWvvD0gJsBZ5D26JZM kVchLzu8gDxJ89njUNOkwiHi18bVD0uAVNZnIggogpwsLPSOqDeWnJ7eH+N+6n13 XW+U51ku5G3vTE7qXH5NcWyJSowVXlTNNCCeZQCTWKqW3/MqDbeMoE0G+JQmuymE f3d136F4iTc9FFZl4WRIIBtrjCvv7SMMeEEFQVnye6hl/FzUO3+mwfeU9bphWAn9 XOVuFWJyZp54y9kQbn+47uzBglZ9xtxwp0qaJ6oaQoA9n8tKrGuw==
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=nc6BlLt3LDRgsZnXYy2gCKoqvDwu8XWfH/8BuBjAIr8=; b=GJ42JYto +yAzHWN4wgzDJJzGLbXEXHAPnxmmSXk9A2+Wp1HzhKuiaQNgMrYpTlqvBPFXk+zi ZdQdYT37UsUTYXwhGnRumHLDJqEf8Ek9JbNo0KuvQpB9hbw68m/VCS+fSIXrJYwp 93XSq+UtEIVe2gn+DjkO3Krd8PXY3yCsYvsfvh6LcP2FO2+MxPjkl2GeNw0ky9rz O0rM2YnMznqt+1jgj6lcFuNDgLtMM9oHcslFeUh/luOmWwPycKEPCu4yNuzCuyGY +RVfsqZ1qSzkonoLAsMTp9iF4I/NBrCLsXfVqoUsXxZCzJUyl+pSwMrRlGp2Ez9W sbgDXgMq+9HJjQ==
X-ME-Sender: <xms:JattWQGF02BxaBn9B2I9_3cMj9eO5DtAzvfQNwWNxrg3wbjTahsevw>
X-Sasl-enc: kxbXlrrtizCl0f7z3AE+3YvrKrc0WsTd1VrLaYhPs09v 1500359461
Received: from dhcp-813f.meeting.ietf.org (dhcp-813f.meeting.ietf.org [31.133.129.63]) by mail.messagingengine.com (Postfix) with ESMTPA id C2FA77E17E; Tue, 18 Jul 2017 02:31:00 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Revamp of the www.ietf.org website
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <F6924008EE2D26C4925CAD2D@PSB>
Date: Tue, 18 Jul 2017 08:30:59 +0200
Cc: jordi.palet@consulintel.es, IETF <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <728EAD91-6FF5-4FC0-BE1F-AB75CA8577C7@mnot.net>
References: <C1590F40-3B9E-45A0-9B87-59A0271B1952@consulintel.es> <20170717153147.D3EA61A6C8@ld9781.wdf.sap.corp> <748CC45D-1DDF-4A3B-A7CC-E3F5C990D550@consulintel.es> <F6924008EE2D26C4925CAD2D@PSB>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nfP7ZjmVuhATQX0Y97_EUVTtQtE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 06:31:06 -0000

> On 17 Jul 2017, at 11:08 pm, John C Klensin <john-ietf@jck.com> wrote:
>=20
> * Precisely because the IETF has some very large vendors among
> its supporters, our being able to continue to claim that we are
> not biased toward those vendors and that our standards decisions
> are not for sale, we need to be careful about not forcing people
> to contribute to the bottom line of those companies in order to
> participate.

How does linking to social media accounts constitute "forcing people... =
in order to participate"?

No one is suggesting that one be required to tweet in order to register =
an objection.


>  We've been reasonably careful (much more careful
> than some other SDOs) to not require someone to purchase some
> particular work processing package or office suite to
> participate.   I suggest that, if the IETF is going to get tied
> up with Social Media, the system(s) used must be ones that do
> not have business models involving  "user as product", targeted
> advertising to users, permission to spam users, or requirements
> that users give up significant privacy in order to join, get
> feeds. or equ9ivalent.

You seem to be making a pretty big leap from "we don't require you to =
use proprietary tools in order to participate" (something that I very =
much agree with) to "we don't even want the *appearance* of (very) =
indirect endorsement of large companies."=20

I could understand a complaint that (for example) Sina Weibo isn't in =
that list, but banning all such links seems to ignore how much of the =
Internet is used today -- which isn't such a good look for the body that =
purports to oversee the Internet's protocols.


> Again, if someone wants to re-{post,
> chirp, tweet, vomit, etc.} materials from an IETF mailing list,
> I think we have always allowed thet.  However, IMO, the IETF
> needs to be really careful about getting more directly involved.

I'm not sure why you bring that up; how would we stop it?


--
Mark Nottingham   https://www.mnot.net/



From nobody Mon Jul 17 23:53:05 2017
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 295EB131D0B; Mon, 17 Jul 2017 23:53:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.4
X-Spam-Level: 
X-Spam-Status: No, score=-5.4 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] 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 fUlSmeWlkfQe; Mon, 17 Jul 2017 23:53:02 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 2C96E127337; Mon, 17 Jul 2017 23:53:02 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.104.20]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LnlmV-1e7nKH3IYp-00htZr; Tue, 18 Jul 2017 08:52:58 +0200
Subject: Re: draft-ietf-jsonbis-rfc7159bis-03: recommendation to use UTF-8
To: Alexey Melnikov <alexey.melnikov@isode.com>, "ietf@ietf.org" <ietf@ietf.org>, "json@ietf.org" <json@ietf.org>
References: <596CE6E3.3070808@isode.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <92698d15-6557-8bb1-aad0-a0965e779e71@gmx.de>
Date: Tue, 18 Jul 2017 08:52:55 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <596CE6E3.3070808@isode.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:aECTRTHrNWb703SrRwkLkDAoZ3A+/wPff8hiJBnfPt0c3sUp5Ku 2a4WVS+gUb1H8qhOeemIySdh7lQs+e5PPbS/3Q9o03YP7m+3ViU85976WNqK7Rrjm4pXAiC oFgUrEpfJlREDC4IcF/R1aKWXMowRZQ1mt826Uk7Gyy2JPNGT+R2rdYXAEUezkTVbSkpgb/ HEZJCNZTcnnWDy6tsqukQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:RsNUN4ZRGrc=:QDwkyChM097G+qDs3QtjH3 bTIA9vt3lqif3lSlzQxaoiNq5lmWobnfslrDTRUY9B7nL1p06PgeZjd5kiQI+kpPtLsI0YPl1 OvnPa8emAFhv3hf5XlkdyACW0fednFPvUPrwsOa80UKaNqag/xF+l7oUyrS0T2eMCKR28V3ra xqjafIMCt2XIYykbPNXg65bIUDuejKSakXR9/GgW2CP5qFKAbxpmC+wvB5Qgt772VIkaQNiIN yLg73xGBJotSvjhPXwKzKQj7RFeqP4aM+LXu4/otXlm1opm+OK/WrV4If6rJ0HOaAyyhkDY3r JZ3MXgbk5Cea3EeSlBgktfN4JS0Rx6P00wt4u4pCGqJxExmLgI2Ijq+MAUjAfZvvFr4PIaVdx BZyDiUMoW2qWZuZKcUl9J0W5N1oYCWw5RoPCGVQK3jz3RqOAZNLe+o3OvtZKVuPKGZIYlv+qz eKKEedtIXDVWmneuoi+rjbGNelDH7dvDv6PZz1rTxw9VSrGlxolj7D2L9eTOteEBGTWLLMXeV ia6Rl/Myu9uNyffIga7RVxiY4p/J1N6hRlzrLpoKbzDCOOTi6Ml07SXIKuDSQi/FUoI7nxK1p WYmChhjXaZG12AQiXf8WP76bzKnleJ0890Hn9NXKqRb6Zw7kDfakbBOiXoGkWu8awHWjQAX1P Fzb9cVJfeNUjUMxmu6dxw1d0iEgvtgm8I8vcpGbO0QCgSNTR9Pngvbpx/6y7S1PxlvfVvUwh3 HEQeXqf9tk3zS7+r9ywLsDXK8jUWVfYdWxN8DgjxhLOJBe146Xsm6uWYfpEZuK0bUnoTwyMu4 dfXcwJTWdigIBXN6Un8gDS6acJcNEmA034Q9SRXt44NxVJO/mc=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uheKLH6yhFPZH4YEvbpS5VoMRE8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 06:53:04 -0000

On 2017-07-17 18:33, Alexey Melnikov wrote:
> Hi,
> 
> The JSONBIS WG decided to update recommendation on Unicode encoding to
> be UTF-8. (For details see the RFC Editor's notes in the approval
> message that will be sent out shortly.) This took a bit of time to
> debate in the WG, so the document approval took a bit longer than
> originally expected.
> 
> Best Regards,
> Alexey, as the responsible AD

The last WG mail related to this topic is over 2 months old, and I don't 
see any declaration of consensus.

It would be good if the chair would send a summary about what's going on 
to the WG mailing list before anything gets finalized.

(I note that 
<https://datatracker.ietf.org/doc/draft-ietf-jsonbis-rfc7159bis/> has 
been saying "Revised ID Needed" for 48 days, and I was under the 
assumption that there'd be indeed a revised ID).

Best regards, Julian


From nobody Tue Jul 18 00:41:10 2017
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86E56131691; Tue, 18 Jul 2017 00:40:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, 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 PQr4OiwA_QlC; Tue, 18 Jul 2017 00:40:55 -0700 (PDT)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id CC35512ECF0; Tue, 18 Jul 2017 00:40:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1500363654; d=isode.com; s=june2016; i=@isode.com; bh=vwrPx0PSglqewztan7UOZ4G0HnNkzkZ1saXMJ0PrIOQ=; 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=kNLC8/Mvb7U9VlVssxfWPKG5kNplLjSmPwP14RL3IljiqrxRl5qQ6k1OaZJSaS/jBAJmXb 7G26lpaepAD0eDUvLyRXIayJTql5Bz4vVNpaUhnl5w6QJoKLjol1NV6Ydc5qdgigcdfEb1 Ksy69NAEyhmWZvGICoVW5pso+e6Q4is=;
Received: from [172.16.18.185] (94.112.246.234.static.b2b.upcbusiness.cz [94.112.246.234])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <WW27hQBf=oKf@statler.isode.com>; Tue, 18 Jul 2017 08:40:53 +0100
Subject: Re: draft-ietf-jsonbis-rfc7159bis-03: recommendation to use UTF-8
From: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: iPad Mail (14F89)
In-Reply-To: <92698d15-6557-8bb1-aad0-a0965e779e71@gmx.de>
Date: Tue, 18 Jul 2017 10:05:26 +0200
Cc: "ietf@ietf.org" <ietf@ietf.org>, "json@ietf.org" <json@ietf.org>
Message-Id: <668A56FD-4B89-472C-9E4C-BE5C0E6921F9@isode.com>
References: <596CE6E3.3070808@isode.com> <92698d15-6557-8bb1-aad0-a0965e779e71@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0VbnyY4AvLb0ZbCCzr-brUOqWm4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 07:40:56 -0000

Hi Julian,

> On 18 Jul 2017, at 08:52, Julian Reschke <julian.reschke@gmx.de> wrote:
>=20
>> On 2017-07-17 18:33, Alexey Melnikov wrote:
>> Hi,
>> The JSONBIS WG decided to update recommendation on Unicode encoding to
>> be UTF-8. (For details see the RFC Editor's notes in the approval
>> message that will be sent out shortly.) This took a bit of time to
>> debate in the WG, so the document approval took a bit longer than
>> originally expected.
>> Best Regards,
>> Alexey, as the responsible AD
>=20
> The last WG mail related to this topic is over 2 months old, and I don't s=
ee any declaration of consensus.
>=20
> It would be good if the chair would send a summary about what's going on t=
o the WG mailing list before anything gets finalized.
>=20
> (I note that <https://datatracker.ietf.org/doc/draft-ietf-jsonbis-rfc7159b=
is/> has been saying "Revised ID Needed" for 48 days, and I was under the as=
sumption that there'd be indeed a revised ID).

I just posted a message on this: this is approved with updated RFC Editor no=
tes. See the approval message once it is sent.

Best Regards,
Alexey=


From nobody Tue Jul 18 01:17:45 2017
Return-Path: <prvs=1372826e48=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 359E5131947 for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 01:17:44 -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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
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 dgSideNUCFtN for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 01:17:42 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB6B7120227 for <ietf@ietf.org>; Tue, 18 Jul 2017 01:17:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1500365858; x=1500970658; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=fMlJtMv5eYBPDTDfNz6DXQBBd q/FVieZRJhSR2HtlTs=; b=P+OaFZCZcQHn0WY67WlyLFHbRxHrC8JdhDKhpqidS BCA+q3CBMdj1bDWCaO4XR5dX1L4moR8TBvzUrQz3lyJnU/BTHMzl39Xmfqvfk0b/ vRQbMGT5KwzLt4qokn0U+lKM5futCkv1fcxfsXFpXPHSWyxOKSZMM4FvJXqTMFt0 pk=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=OQYhGvmT/DP7opGb6YHUd2xpLM0pBtQPrePLnuhoi3ElBKAAC28XoSYmOsry EW1HR8fp93CN+WJP67uK/uplNKzL5yDpcpmm9iDi1KOwI8RtHPuilnUGk z2dYA87wQDAKveT4rUwm5evmizzBCO8ZhxWuNTRBEu7X1tfrV9qGt0=;
X-MDAV-Processed: mail.consulintel.es, Tue, 18 Jul 2017 10:17:38 +0200
X-Spam-Processed: mail.consulintel.es, Tue, 18 Jul 2017 10:17:37 +0200
Received: from [31.133.142.45] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005479360.msg for <ietf@ietf.org>; Tue, 18 Jul 2017 10:17:36 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170718:md50005479360::ScgT8M3sR9iK6yaW:00003Ray
X-MDRemoteIP: 31.133.142.45
X-Return-Path: prvs=1372826e48=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.24.0.170702
Date: Tue, 18 Jul 2017 10:17:33 +0200
Subject: Re: Revamp of the www.ietf.org website
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IETF <ietf@ietf.org>
Message-ID: <BA8A08D0-C574-47F4-8365-54989693FB11@consulintel.es>
Thread-Topic: Revamp of the www.ietf.org website
References: <C1590F40-3B9E-45A0-9B87-59A0271B1952@consulintel.es> <20170717153147.D3EA61A6C8@ld9781.wdf.sap.corp> <748CC45D-1DDF-4A3B-A7CC-E3F5C990D550@consulintel.es> <F6924008EE2D26C4925CAD2D@PSB>
In-Reply-To: <F6924008EE2D26C4925CAD2D@PSB>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8QV2yJbJSks7Y5i2XfotzhXfOok>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 08:17:44 -0000

To make it short. I disagree. I=E2=80=99m not asking to change the way IETF=
 procedures work or anything similar.

I think we need to be in the =E2=80=9Cmarket=E2=80=9D and that means that m=
any operators (or other communities) that don=E2=80=99t have the time or th=
e resources, or just they aren=E2=80=99t willing to subscribe to a mailing =
list, keep informed of our announcements, in an automated way, by means of =
as many social networks we can. Just informative, not as part of the =E2=80=
=9Ccontribution=E2=80=9D process, not replacing actual mail exploders, etc.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de John C Klensin <john-ietf@jck=
.com>
Responder a: <john-ietf@jck.com>
Fecha: lunes, 17 de julio de 2017, 23:09
Para: <jordi.palet@consulintel.es>
CC: IETF <ietf@ietf.org>
Asunto: Re: Revamp of the www.ietf.org website

    Jordi,
   =20
    Three observations. =20
   =20
    * Noting that assorted social media are, from time to time, more
    or less effectively blocked in assorted countries, I think we
    need to be sure that all IETF participants are able to get to
    all IETF announcements and materials on an equal basis unless
    the IETF itself is blocked.  If someone wants to reflect IETF
    announcements into some social media or supplemental mailing
    list, that is fine and has been going on for years, but
    substantive announcements and discussions need to stay on IETF
    mailing lists and be archived on IETF facilities or we end up
    with big openness and transparency problems.=20
   =20
    * Precisely because the IETF has some very large vendors among
    its supporters, our being able to continue to claim that we are
    not biased toward those vendors and that our standards decisions
    are not for sale, we need to be careful about not forcing people
    to contribute to the bottom line of those companies in order to
    participate.  We've been reasonably careful (much more careful
    than some other SDOs) to not require someone to purchase some
    particular work processing package or office suite to
    participate.   I suggest that, if the IETF is going to get tied
    up with Social Media, the system(s) used must be ones that do
    not have business models involving  "user as product", targeted
    advertising to users, permission to spam users, or requirements
    that users give up significant privacy in order to join, get
    feeds. or equ9ivalent.  Again, if someone wants to re-{post,
    chirp, tweet, vomit, etc.} materials from an IETF mailing list,
    I think we have always allowed thet.  However, IMO, the IETF
    needs to be really careful about getting more directly involved.
   =20
    * I share Martin's concern about page size, complexity, and load
    times, especially if we are serious about trying to involve
    people in developing countries and otherwise with with marginal
    connections.=20
   =20
    best,
        john
   =20
   =20
    --On Monday, July 17, 2017 21:35 +0200 JORDI PALET MARTINEZ
    <jordi.palet@consulintel.es> wrote:
   =20
    > I disagree on this.
    >=20
    > Having our announcements for last calls, RFC, STDs, major
    > events, etc., in social media, helps to disseminate IETF
    > activities, and we like or not social networks (I'm
    > personally not a fan of them), is an obligation today. Many
    > folks will not use a mailing list to know about "new" IETF
    > work, but they will happily subscribe to a facebook or tweeter
    > account.
    >=20
    > Regards,
    > Jordi
    > =20
    >=20
    > -----Mensaje original-----
    > De: ietf <ietf-bounces@ietf.org> en nombre de Martin Rex
    > <mrex@sap.com> Responder a: <mrex@sap.com>
    > Fecha: lunes, 17 de julio de 2017, 17:32
    > Para: <jordi.palet@consulintel.es>
    > CC: IETF <ietf@ietf.org>
    > Asunto: Re: Revamp of the www.ietf.org website
    >=20
    >     JORDI PALET MARTINEZ wrote:
    >     >
    >     > I think a missing aspect of the web site, which should
    > be prominent in     > both the home page and also the
    > ?contact? page, is all the social media.     >=20
    >     > I see there is a ?share this page? at the right of the
    > main picture,     > but in my opinion, is not clearly visible
    > and is not enough     > (the logos of the social networks
    > should be recognized without...    =20
    >     Cough, cough, WHAT???
    >    =20
    >     Please get rid of the "social media" crap entirely.  I
    > thought that     there was an IETF consensus that privcay is
    > sensible and useful, and     strong privacy protections should
    > be the default.    =20
    >    =20
    >     Facebook, Twitter and other "social media" crap is the far
    > opposite of     strongy privacy, so none of this should be
    > encouraged or promoted by     the IETF.
    >    =20
    >    =20
    >    =20
    >     Comparing the bandwidth necessary to load the entire
    > homepage,     I notice the following issues:
    >    =20
    >       https://www.ietf.org/    Total 188176 bytes (mainly by
    > accident, it seems)                                The visible
    > page _contents_ are just fine,    =20
    >         but the page designer goofed the photo in the meeting
    > information,         because the picture is transferred at
    > size 640x427 taking up 150270 bytes,         although it is
    > actually being displayed at just 200x133, where a
    > pre-scaled image would need just 17 KBytes.
    >    =20
    >         Even on my 5" Smartphone, the https://www.ietf.org/
    > loads just fine,         I get the whole picture immediately,
    > and can zoon into my area of interest.    =20
    >    =20
    >       http://www.ietf.org/     Total 1195800 bytes (ouch ouch
    > ouch ouch).    =20
    >         is a completely botched page design. it needs
    > multi-page scrolldown         even on a big desktop screen,
    > and finding stuff has become extremely         difficult.
    >    =20
    >         This page even manages to provide *ZERO* intelligible
    > information         when loaded on my SmartPhone
    >    =20
    >         only shows the Welcome / Revamp <Learn More>  + Social
    > Media Crap Buttons    =20
    >         and when scrolling down the multiple pages of crap on
    > my SmartPhone,         very close to zero of the links
    > _that_used_to_be_ on https://www.ietf.org         pass by.
    >    =20
    >    =20
    >         Normally I close such bloated ad & nag screens
    > immediately, though         nowadays uBlock saves my health by
    > ensuring that most of such crap         does not even get
    > displayed on any of my screens (desktop & mobile)         in
    > the first place.
    >    =20
    >         The huge background picture
    > (IETF-Past-Meetings.max-4000x4000.jpg)         with 763216
    > Bytes is just crazy.  Is this about a party/festival?
    > A *HUGE* waste of network bandwidth and memory (RAM and
    > on-disk cache)         and writing text over photos also make
    > reading difficult (poor contrast).    =20
    >    =20
    >    =20
    >     All in all, my personal summary for https://beta.ietf.org/
    >    =20
    >     disgusting and extremly bloated, usless and highly
    > confusing.    =20
    >    =20
    >     -Martin
    >    =20
    >    =20
    >    =20
    >=20
    >=20
    >=20
    > **********************************************
    > IPv4 is over
    > Are you ready for the new Internet ?
    > http://www.consulintel.es
    > The IPv6 Company
    >=20
    > This electronic message contains information which may be
    > privileged or confidential. The information is intended to be
    > for the use of the individual(s) named above. If you are not
    > the intended recipient be aware that any disclosure, copying,
    > distribution or use of the contents of this information,
    > including attached files, is prohibited.
    >=20
    >=20
    >=20
   =20
   =20
   =20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Tue Jul 18 01:19:28 2017
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9075131A4F; Tue, 18 Jul 2017 01:19:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.9
X-Spam-Level: 
X-Spam-Status: No, score=-4.9 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, RCVD_IN_SORBS_SPAM=0.5, 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 wRJ-7RdK-hVS; Tue, 18 Jul 2017 01:19:10 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 D47FB120227; Tue, 18 Jul 2017 01:19:09 -0700 (PDT)
Received: from [192.168.1.34] ([217.91.35.233]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MQyxa-1d4CmK3G18-00UMyd; Tue, 18 Jul 2017 10:19:06 +0200
Subject: Re: [Json] draft-ietf-jsonbis-rfc7159bis-03: recommendation to use UTF-8
To: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "json@ietf.org" <json@ietf.org>
References: <596CE6E3.3070808@isode.com> <92698d15-6557-8bb1-aad0-a0965e779e71@gmx.de> <668A56FD-4B89-472C-9E4C-BE5C0E6921F9@isode.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <6a42a587-f09c-14bc-847b-7882c8f3e9f7@gmx.de>
Date: Tue, 18 Jul 2017 10:19:04 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <668A56FD-4B89-472C-9E4C-BE5C0E6921F9@isode.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:Vkz88uHPQl53S3XzTnq0sE1FUWw6LtvE67N1EvmsJlvI4vco1zH D3gfRJR748p/dhjKomEgySlOXzwWsaFT3poeR9NbAnVVhwQr3r7lbVnLG8Y3eOwqTOXEh8+ OnxDdm0ZqRrgyuPEyVgL23nnmtem1+cZIZcx88QZognSA/Oie61/rtViEU8ED8Uc4AxUk8L HjXWZuex5NDxib2vTy1yw==
X-UI-Out-Filterresults: notjunk:1;V01:K0:s7NM6I86kvQ=:u9FUnhXBkaNtCFAijP1KsB gU6e5DOYxHFf1/TbZMSBxBkOhT+bUbxWvpDE8jIU6H5le+SiBvSzw0kVnufn5veheQrAA13u2 tTZs5bXYx9lx7SfVjW5TP/FTyaM0ETj2l7z75iLEzLddDnAyL4twGoTG+lM2JVDQgZ5N1QACQ BRR11aSqDtO7mksUQTsmwBMU9b7xWatIpRG4DM3ZHQneh05jQwZhHxus+ujPxpzvoxFjDJEX/ Nl4bnvH2RU0zSAvu2tOdhBGhNAqIOv92U+Z0B4HDjWfbcsuBs2Dj0UcSPp86aToYGyTj65Mrt wQeBrhZt28lKplZo9GlmRGZWwQrIhNd3wTRU942lRas1omllp8+d910K9r0welWo9DNdeB8qS F5Hp1g1/vHgvIyygrTwpGvRwyZDMif44B78bfmmMeXPJhl3l4LCUBRlqKM9yDGxxEvNNLy3l5 vVr3FsnFeQ5zDDQbBbofH/MUunSMP+KoJ16aI6q7RdwXNDKzLZuWqRpwsRyUsBh5KpSTbOHIY sseitKFgJSWsu4Eo2T0p+poYXOEMbAo/g5zD/uTD2FvMDGuO5IdadUUN2Ul+yCx3Q4VcI+peN 7D0HZ74G+9jzQ9L1wFqEtZcWOZkmNILkrov1qekSxPsoHUu+gQzZ0PAHniPVwgyThTSca6SnP QmVJyEMlx+M1yUpxaHb6eW9OjdjQFVE0cDcRfV5MtsGtEz1hKCcdZeFgYVwOWGZt3VcgbLUmQ QcBLn9je8bTuBubVfszx2YnewQtxhJSUEuTvUvtOfhQA5M6cKzfMmJnVoT6b80CbNAoRe57wB vphk1oxHobywxXZFCdUOzfrF7Ngad92UjfkRxqFj2z0io5nVfM=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/t6ckyYWt7mVY9EACC69ak-CUp6g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 08:19:12 -0000

On 2017-07-18 10:05, Alexey Melnikov wrote:
> Hi Julian,
> 
>> On 18 Jul 2017, at 08:52, Julian Reschke <julian.reschke@gmx.de> wrote:
>>
>>> On 2017-07-17 18:33, Alexey Melnikov wrote:
>>> Hi,
>>> The JSONBIS WG decided to update recommendation on Unicode encoding to
>>> be UTF-8. (For details see the RFC Editor's notes in the approval
>>> message that will be sent out shortly.) This took a bit of time to
>>> debate in the WG, so the document approval took a bit longer than
>>> originally expected.
>>> Best Regards,
>>> Alexey, as the responsible AD
>>
>> The last WG mail related to this topic is over 2 months old, and I don't see any declaration of consensus.
>>
>> It would be good if the chair would send a summary about what's going on to the WG mailing list before anything gets finalized.
>>
>> (I note that <https://datatracker.ietf.org/doc/draft-ietf-jsonbis-rfc7159bis/> has been saying "Revised ID Needed" for 48 days, and I was under the assumption that there'd be indeed a revised ID).
> 
> I just posted a message on this: this is approved with updated RFC Editor notes. See the approval message once it is sent.
> ...

This is not how it's supposed to work. Please have a new I-D posted and 
get people to review the changes in context. This is a *very* important 
piece of standards work - we need to make sure it meets quality standards.

 From a quick glance at 
<https://datatracker.ietf.org/doc/draft-ietf-jsonbis-rfc7159bis/writeup/>, 
I already note that the appendix "Changes from RFC 7159" is now incomplete.

Best regards, Julian


From nobody Tue Jul 18 02:06:38 2017
Return-Path: <chris.dearlove@baesystems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A8D712009C for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 02:06:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.921
X-Spam-Level: 
X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-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 eOcjr3k_8Occ for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 02:06:35 -0700 (PDT)
Received: from ukmta1.baesystems.com (ukmta1.baesystems.com [20.133.0.55]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D1FF131A92 for <ietf@ietf.org>; Tue, 18 Jul 2017 02:06:34 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.40,377,1496098800"; d="scan'208";a="13033744"
Received: from unknown (HELO baemasmds016.greenlnk.net) ([10.15.207.101]) by ukmta1.baesystems.com with ESMTP; 18 Jul 2017 10:06:32 +0100
X-IronPort-AV: E=Sophos;i="5.40,377,1496098800"; d="scan'208";a="11474622"
Received: from glkxh0003v.greenlnk.net ([10.109.2.34]) by baemasmds016.greenlnk.net with ESMTP; 18 Jul 2017 10:06:32 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.118]) by GLKXH0003V.GREENLNK.net ([10.109.2.34]) with mapi id 14.03.0248.002; Tue, 18 Jul 2017 10:06:32 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Russ Housley <housley@vigilsec.com>, IETF <ietf@ietf.org>
Subject: RE: Revamp of the www.ietf.org website
Thread-Topic: Revamp of the www.ietf.org website
Thread-Index: AQHS/Uu/plX70dSTWk+uFjh4J2OquaJZTnrg
Date: Tue, 18 Jul 2017 09:06:31 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6394482@GLKXM0002V.GREENLNK.net>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com>
In-Reply-To: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OA6uhiWjoDzs0Cf72Q_gkxKkUkA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 09:06:37 -0000

RXZlcnl0aGluZyBJIHdhbnQgb24gdGhlIGV4aXN0aW5nIElFVEYgd2Vic2l0ZSBpbiBpbiBhIHBh
bmVsIG9uIHRoZSBsZWZ0LiBJIHJhcmVseSBldmVuIGxvb2sgYXQgdGhlIHJpZ2h0bW9zdCB0aHJl
ZSBxdWFydGVycyBvZiB0aGUgc2NyZWVuLiBUaGF0IHBhbmVsIGNhbiBiZSB1c2VkIHRvIHRha2Ug
bWUgc3RyYWlnaHQgdG8gd2hlcmUgSSB3YW50IHRvIGdvLiBUaGUgbmV3IHNpdGUgYXQgaXQgYXBw
ZWFycyBhcyBsaW5rZWQgYmVsb3cgYXBwZWFycyB0byBoYXZlIHNlcmlvdXNseSByZWR1Y2VkIHRo
ZSB1c2FiaWxpdHkgb2YgdGhlIHNpdGUgZm9yIHBlb3BsZSB3aG8ga25vdyB3aGF0IHRoZXkgd2Fu
dCBhbmQgd2FudCB0byBnbyBzdHJhaWdodCB0byBpdC4gUHV0IHRoZSBwYW5lbCBiYWNrIChvciBt
YXliZSBpdCdzIGFsd2F5cyBpbnRlbmRlZCB0byBiZSB0aGVyZSwgYW5kIHRoaXMgaXMganVzdCB0
aGUgbWFpbiBwYW5lIGJlaW5nIGNvbnNpZGVyZWQpIGFuZCBJIGRvbid0IHJlYWxseSBtaW5kIHdo
YXQgeW91IGRvIHRoZXJlIChhcyBsb25nIGFzIGl0IGxvYWRzIHF1aWNrbHkpLg0KDQotLSANCkNo
cmlzdG9waGVyIERlYXJsb3ZlDQpTZW5pb3IgUHJpbmNpcGFsIEVuZ2luZWVyDQpCQUUgU3lzdGVt
cyBBcHBsaWVkIEludGVsbGlnZW5jZSBMYWJvcmF0b3JpZXMNCl9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQoN
ClQ6IMKgKzQ0IDMzMDAgNDY3NTAwIMKgfCDCoEU6IGNocmlzLmRlYXJsb3ZlQGJhZXN5c3RlbXMu
Y29tDQoNCkJBRSBTeXN0ZW1zIEFwcGxpZWQgSW50ZWxsaWdlbmNlLCBDaGVsbXNmb3JkIFRlY2hu
b2xvZ3kgUGFyaywgR3JlYXQgQmFkZG93LCBDaGVsbXNmb3JkLCBFc3NleCBDTTIgOEhOLg0Kd3d3
LmJhZXN5c3RlbXMuY29tL2FpDQpCQUUgU3lzdGVtcyBBcHBsaWVkIEludGVsbGlnZW5jZSBMaW1p
dGVkDQpSZWdpc3RlcmVkIGluIEVuZ2xhbmQgJiBXYWxlcyBObzogMDEzMzc0NTENClJlZ2lzdGVy
ZWQgT2ZmaWNlOiBTdXJyZXkgUmVzZWFyY2ggUGFyaywgR3VpbGRmb3JkLCBTdXJyZXksIEdVMiA3
WVANCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGlldGYgW21haWx0bzppZXRm
LWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBSdXNzIEhvdXNsZXkNClNlbnQ6IDE1IEp1
bHkgMjAxNyAxMDoyMQ0KVG86IElFVEYNClN1YmplY3Q6IFJldmFtcCBvZiB0aGUgd3d3LmlldGYu
b3JnIHdlYnNpdGUNCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSEgV0FSTklORyAhIC0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0gVGhpcyBtZXNzYWdlIG9yaWdpbmF0ZXMgZnJvbSBvdXRzaWRlIG91ciBv
cmdhbmlzYXRpb24sIGVpdGhlciBmcm9tIGFuIGV4dGVybmFsIHBhcnRuZXIgb3IgZnJvbSB0aGUg
aW50ZXJuZXQuDQpDb25zaWRlciBjYXJlZnVsbHkgd2hldGhlciB5b3Ugc2hvdWxkIGNsaWNrIG9u
IGFueSBsaW5rcywgb3BlbiBhbnkgYXR0YWNobWVudHMgb3IgcmVwbHkuDQpGb2xsb3cgdGhlICdS
ZXBvcnQgU3VzcGljaW91cyBFbWFpbHMnIGxpbmsgb24gSVQgbWF0dGVycyBmb3IgaW5zdHJ1Y3Rp
b25zIG9uIHJlcG9ydGluZyBzdXNwaWNpb3VzIGVtYWlsIG1lc3NhZ2VzLg0KLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0KSSBhbSBwbGVh
c2VkIHRvIHJlcG9ydCB0aGF0IHRoZXJlIGhhcyBiZWVuIGEgbG90IG9mIHByb2dyZXNzIG9uIHRo
ZSBwcm9qZWN0IHRvIHJldmFtcCBvZiB0aGUgd3d3LmlldGYub3JnIHdlYnNpdGUuIFRoZSB1cGRh
dGVkIHdlYnNpdGUgd2lsbCBiZSB0aGUg4oCcZnJvbnQgZG9vcuKAnSBmb3IgdGhlIElFVEYsIG5v
dCBvbmx5IGZvciBmb3IgYWN0aXZlIElFVEYgcGFydGljaXBhbnRzLCBidXQgYWxzbyBwcm92aWRl
cyBhbiBvbnJhbXAgZm9yIHBvdGVudGlhbCBwYXJ0aWNpcGFudHMsIGFuZCBoZWxwcyBleHBsYWlu
IHRoZSB3b3JrIG9mIHRoZSBJRVRGIHRvIHBlb3BsZSB3aG8gYXJlIG5vdCBkaXJlY3RseSBpbnZv
bHZlZCBpbiBkZXZlbG9waW5nIEludGVybmV0IHN0YW5kYXJkcy4gVGhlIGNvbXBsZXRlIFNjb3Bl
IG9mIFdvcmsgZm9yIHRoZSBwcm9qZWN0IGlzIGF2YWlsYWJsZSBhdDoNCg0KICAgaHR0cHM6Ly9p
YW9jLmlldGYub3JnL2RvY3VtZW50cy9JRVRGLVdlYnNpdGUtU09XLTIwMTQwNjA0LUZpbmFsLnBk
Zg0KDQpCYXNlZCBvbiByZWNlbnQgZmVlZGJhY2ssIGluY2x1ZGluZyB0aGUgZGVtbyB0YWJsZSBh
dCBJRVRGIDk4LCB0aGUgaW5pdGlhbCBkZXNpZ24gYW5kIGZlYXR1cmVzIG9mIHRoZSB3ZWJzaXRl
IGhhdmUgYmVlbiBpbXByb3ZlZCBpbiBtYW55IHdheXMuIEZvciBleGFtcGxlLCBpbiByZXNwb25z
ZSB0byB0aGUgZmVlZGJhY2sgcHJvdmlkZWQsIHRoZXJlIGlzIG5vdyBhIHNpbmdsZSBwYWdlIHRo
YXQgcHJvdmlkZXMgbGlua3MgdG8gdG9vbHMgYW5kIHJlc291cmNlcyBjb21tb25seSB1c2VkIGJ5
IGFjdGl2ZSBJRVRGIHBhcnRpY2lwYW50cy4NCg0KVGhlIHByb2plY3QgaXMgbm93IGVudGVyaW5n
IHRoZSBuZXh0IHBoYXNlIG9mIHRoZSB3ZWJzaXRlIGRldmVsb3BtZW50LiBUaGUgZ29hbCBmb3Ig
dGhpcyBwaGFzZSBpcyB0byBnYXRoZXIgaW5wdXQgbW9yZSBicm9hZGx5LiBXaGlsZSB0aGVyZSBh
cmUgc3RpbGwgYSBmZXcgZmVhdHVyZXMgdG8gYmUgaW1wbGVtZW50ZWQgYW5kIHNvbWUgY29udGVu
dCBzdGlsbCBuZWVkcyB0byBiZSBmaW5lIHR1bmVkLCB0aGUgZ2VuZXJhbCBvcmdhbml6YXRpb24g
YW5kIHRoZSBsb29rLWFuZC1mZWVsIG9mIHRoZSB3ZWJzaXRlIGhhcyBiZWVuIGltcGxlbWVudGVk
IGJhc2VkIG9uIHRoZSBpbml0aWFsIHJlc2VhcmNoIGFuZCBpbnB1dCByZWNlaXZlZCB0byBkYXRl
LiBPZiBjb3Vyc2UsIHRoZXJlIHdpbGwgYmUgc29tZSBhZGRpdGlvbmFsIHNpZ25pZmljYW50IHdv
cmsgYmVmb3JlIHRoZSBzaXRlIGlzIHJlYWR5IGZvciBwcm9kdWN0aW9uOyBmb3IgZXhhbXBsZSwg
YmVmb3JlIHRoZSB3ZWJzaXRlIGlzIGZpbmFsLCB3ZSB3aWxsIGltcGxlbWVudCBtZXRob2RzIHRv
IGVuc3VyZSB0aGF0IHdlbGwta25vd24gVVJMcyBjb250aW51ZSB0byB3b3JrIGFzIGV4cGVjdGVk
LiANCg0KVGhlIHNpdGUgaXMgbm93IGFjY2Vzc2libGUgYXQ6DQoNCiAgIGh0dHBzOi8vYmV0YS5p
ZXRmLm9yZw0KDQpQbGVhc2UgdGFrZSBhIGxvb2suIFdlIHdpbGwgYmUgdHJhY2tpbmcgaXNzdWVz
IHRoYXQgbmVlZCBhZGRyZXNzaW5nIGF0Og0KDQogICBodHRwczovL2dpdGh1Yi5jb20vaWV0Zi93
d3cuaWV0Zi5vcmcvaXNzdWVzDQoNCkZlZWRiYWNrIGNhbiBhbHNvIGJlIGVtYWlsZWQgZGlyZWN0
bHkgdG86IHdlYm1hc3RlckBpZXRmLm9yZw0KDQpBdCBJRVRGIDk5IGluIFByYWd1ZSwgdGhlcmUg
d2lsbCBiZSBhIHRhYmxlIG5lYXIgbWVldGluZyByZWdpc3RyYXRpb24gdG8gZGVtb25zdHJhdGUg
dGhlIGJldGEgd2Vic2l0ZSB3aXRoIOKAnG9mZmljZSBob3VycyIgcG9zdGVkIG9uIGEgc2lnbiBi
eSB0aGUgdGFibGUuIFBsZWFzZSBzdG9wIGJ5IGlmIHlvdSBhcmUgaW4gUHJhZ3VlISAgVGhlIG9m
ZmljZSBob3VycyB3aWxsIGJlIGF0IGxlYXN0Og0KDQogICBNb25kYXksIEp1bHkgMTcsIDA4OjMw
LTA5OjMwIGFuZCAxNzoxNS0xNzo0NQ0KDQogICBUdWVzZGF5LCBKdWx5IDE4LCAwODozMC0wOToz
MA0KDQogICBXZWRuZXNkYXksIEp1bHkgMTksIDA4OjMwLTk6MzANCg0KICAgRnJpZGF5LCBKdWx5
IDEyLCAwODozMC05OjMwDQoNClRoYW5rcywNClJ1c3MgSG91c2xleQ0KSUVURiBXZWJzaXRlIFJl
dmFtcCBQcm9qZWN0IE1hbmFnZXINCioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqClRoaXMgZW1haWwgYW5kIGFueSBhdHRh
Y2htZW50cyBhcmUgY29uZmlkZW50aWFsIHRvIHRoZSBpbnRlbmRlZApyZWNpcGllbnQgYW5kIG1h
eSBhbHNvIGJlIHByaXZpbGVnZWQuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZApyZWNpcGll
bnQgcGxlYXNlIGRlbGV0ZSBpdCBmcm9tIHlvdXIgc3lzdGVtIGFuZCBub3RpZnkgdGhlIHNlbmRl
ci4KWW91IHNob3VsZCBub3QgY29weSBpdCBvciB1c2UgaXQgZm9yIGFueSBwdXJwb3NlIG5vciBk
aXNjbG9zZSBvcgpkaXN0cmlidXRlIGl0cyBjb250ZW50cyB0byBhbnkgb3RoZXIgcGVyc29uLgoq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKgo=


From nobody Tue Jul 18 02:13:20 2017
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0C9D131AE6 for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 02:13: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, 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 yUFBVmdi8fmy for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 02:13:14 -0700 (PDT)
Received: from mail-wr0-x242.google.com (mail-wr0-x242.google.com [IPv6:2a00:1450:400c:c0c::242]) (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 1670E131A93 for <ietf@ietf.org>; Tue, 18 Jul 2017 02:13:14 -0700 (PDT)
Received: by mail-wr0-x242.google.com with SMTP id y67so1048657wrb.3 for <ietf@ietf.org>; Tue, 18 Jul 2017 02:13:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=VXs4UgMJ0IfcAbI7PvbE/BmrUu0fM1/9sBn+4c5Covc=; b=Hdgtu0sBzxwUwz7MIqLrT2geQwlp6w2HRdZZEG30qziR+EtgM19QujtfABccHUpgXV ksiipEz3HewK4mV3QfrHoqu4Vvi0K2tEEL/gpXKx5KsWsiuG8LgznAgQi4S3aYQmIeUY TduQtIQOF9ZeIAd43elfJvtHMb/rdrIHpuFrB4ghfWiVrW4JIbri610Fg1GrM7D73M0/ GeoeEO78g4vd3TBdtbb+kdHZyWKrhJvWgbUV710Df1HT360Lj7vhGjpXZz26Aijv1CaC XZuau2CZZ8B3MumyEOQFuPyNR8fAs9BdCivFfIw6D0Vb5O3VxYyWM7bejnpaSbV8g5+B OJww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=VXs4UgMJ0IfcAbI7PvbE/BmrUu0fM1/9sBn+4c5Covc=; b=Kbocyk9xQfz4e7m8PlDBYTVn+dy+5pcZlk9lUcLQU2FZ0La8xMrHzquazsOk3/1mx4 Rj+WCmQCFK7I00KFyezcBkm3Aiyi+CEkFAGSCXBDpLs2FbjTkVoj+rhDE8oqcgFxw8Rw Ek5QD3o0iOTUF/ZxBAh7IVO0zta9Vq0TNO32ct5vHAdXvlSRRQOVplbZTa5wlggIxf4B HaHpGvG+slwCvcQ3T+VZhwYnWyB7cGirRbwtPfXqKY86jF6ir/4KNuWGKF74ZAdTdraO 6cFWm+1hX72zYHendKQLGsO8V2wWSfCyqAZY2/t0WuAkvNa65QfdDYK6Up25Js2n542Z fs/A==
X-Gm-Message-State: AIVw11120s83dQX3uPXCUOqHUDPvvmanzLWbs+KCDDrkmnkifgw0KDgo XvpU8Q8r7eVUOg==
X-Received: by 10.223.154.183 with SMTP id a52mr493616wrc.47.1500369192671; Tue, 18 Jul 2017 02:13:12 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:128:1880:4289:3b62:de32? ([2001:67c:370:128:1880:4289:3b62:de32]) by smtp.gmail.com with ESMTPSA id p27sm2174235wmf.23.2017.07.18.02.13.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Jul 2017 02:13:11 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <39D1C0A9-DB43-42DD-BD3F-7D636856ECEF@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_137FBCB3-09CB-41D5-96E3-C042008B955E"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Revamp of the www.ietf.org website
Date: Tue, 18 Jul 2017 11:13:10 +0200
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6394482@GLKXM0002V.GREENLNK.net>
Cc: Russ Housley <housley@vigilsec.com>, IETF <ietf@ietf.org>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6394482@GLKXM0002V.GREENLNK.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8yGrZPFNQw05BCzlmPLGo7IFHgU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 09:13:19 -0000

--Apple-Mail=_137FBCB3-09CB-41D5-96E3-C042008B955E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On 18 Jul 2017, at 11:06, Dearlove, Christopher (UK) =
<chris.dearlove@baesystems.com> wrote:
>=20
> Everything I want on the existing IETF website in in a panel on the =
left. I rarely even look at the rightmost three quarters of the screen.

That=E2=80=99s because you don=E2=80=99t come to meetings. Around =
meetings the right half of the screen becomes useful.

> That panel can be used to take me straight to where I want to go. The =
new site at it appears as linked below appears to have seriously reduced =
the usability of the site for people who know what they want and want to =
go straight to it. Put the panel back (or maybe it's always intended to =
be there, and this is just the main pane being considered) and I don't =
really mind what you do there (as long as it loads quickly).

The new site is focused not on the existing people active in the IETF. =
It=E2=80=99s focused on the general public.  The place where work gets =
done these days is datatracker.

Yoav



--Apple-Mail=_137FBCB3-09CB-41D5-96E3-C042008B955E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJZbdEnAAoJELhJCxUKWMyZMxcIAL6GufqnWDG4YkX/zwYgCq+U
F0ImUZR1i1MO84hKRy3uCTptRhkQzg4YZ56Xhc8XkfpB4zMswCFtqgv5v4MGA0K+
IpoAkL1q0+mCoG5UDmDWdOtW7oyTYiWD8OR+SbjnmyXVPCmoSho4PMqglULkvGVj
1PuF3nbaqMoFar8Tkvx8f0k11fab6Jsp+jJrd4SPZ0OmYuHAzTDv8shuRHldM9Ri
AbhiCC2L34dmgjhJ0jvgxEr42sq03PyCnNLjcpQ3OTeLk/gMe9T2J25KUQS+4Z0M
cs+3AU75nzSS9Ru6ZflO9G+TMmqZSoZzCri/4hLVbPShIG9EZphwqQzXfVtKh2Y=
=Rnmy
-----END PGP SIGNATURE-----

--Apple-Mail=_137FBCB3-09CB-41D5-96E3-C042008B955E--


From nobody Tue Jul 18 02:23:59 2017
Return-Path: <chris.dearlove@baesystems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73A51131DD0 for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 02:23:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.921
X-Spam-Level: 
X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-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 LnQ7OhqfEMvk for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 02:23:54 -0700 (PDT)
Received: from ukmta1.baesystems.com (ukmta1.baesystems.com [20.133.0.55]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 111E6131DC7 for <ietf@ietf.org>; Tue, 18 Jul 2017 02:23:53 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.40,377,1496098800"; d="scan'208";a="13039762"
Received: from unknown (HELO baemasmds016.greenlnk.net) ([10.15.207.101]) by ukmta1.baesystems.com with ESMTP; 18 Jul 2017 10:23:52 +0100
X-IronPort-AV: E=Sophos;i="5.40,377,1496098800"; d="scan'208";a="11479792"
Received: from glkxh0003v.greenlnk.net ([10.109.2.34]) by baemasmds016.greenlnk.net with ESMTP; 18 Jul 2017 10:23:52 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.118]) by GLKXH0003V.GREENLNK.net ([10.109.2.34]) with mapi id 14.03.0248.002; Tue, 18 Jul 2017 10:23:52 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Yoav Nir <ynir.ietf@gmail.com>
CC: Russ Housley <housley@vigilsec.com>, IETF <ietf@ietf.org>
Subject: RE: Revamp of the www.ietf.org website
Thread-Topic: Revamp of the www.ietf.org website
Thread-Index: AQHS/Uu/plX70dSTWk+uFjh4J2OquaJZTnrg///yUQCAABDikA==
Date: Tue, 18 Jul 2017 09:23:51 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE63944B2@GLKXM0002V.GREENLNK.net>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6394482@GLKXM0002V.GREENLNK.net> <39D1C0A9-DB43-42DD-BD3F-7D636856ECEF@gmail.com>
In-Reply-To: <39D1C0A9-DB43-42DD-BD3F-7D636856ECEF@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Vw6B9Ih2VI7XMmNy28Dr559oA8M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 09:23:58 -0000

SSd2ZSBiZWVuIHRvIG1hbnkgbWVldGluZ3MgKG15IGZpcnN0IHdhcyBJRVRGIDU1KSwgdGhvdWdo
IG5vdCB2ZXJ5IHJlY2VudGx5LiBBbmQgeW91IGNhbiBnZXQgdG8gbWVldGluZ3Mgb2ZmIHRoZSBs
ZWZ0bW9zdCBwYW5lbCB0b28gaW4gYWJvdXQgdGhlIHNhbWUgdGltZS4NCg0KPiBUaGUgbmV3IHNp
dGUgaXMgZm9jdXNlZCBub3Qgb24gdGhlIGV4aXN0aW5nIHBlb3BsZSBhY3RpdmUgaW4gdGhlIElF
VEYuIEl04oCZcyBmb2N1c2VkIG9uIHRoZSBnZW5lcmFsIHB1YmxpYy4gDQoNCkxldCB0aGUgZ2Vu
ZXJhbCBwdWJsaWMgaGF2ZSB0aHJlZSBxdWFydGVycyBvZiB0aGUgcGFnZS4gTGV0IHVzIGhhdmUg
dGhlIG90aGVyIHF1YXJ0ZXIuDQoNCj4gVGhlIHBsYWNlIHdoZXJlIHdvcmsgZ2V0cyBkb25lIHRo
ZXNlIGRheXMgaXMgZGF0YXRyYWNrZXIuDQoNCkFuZCB0aGF0J3Mgb25lIG9mIHRoZSBwbGFjZXMg
b25lIGNhbiBlYXNpbHkgZ2V0IHRvLiBCdXQgdGhlcmUgYXJlIG90aGVycyB0b28uIEJ1dCBzb3Jy
eSwgdGhpcyBpcyBub3QgdGhlIHNvcnQgb2YgcmVzcG9uc2UgdGhhdCdzIHVzZWZ1bCAtIGRvbid0
IGNhcmUgYWJvdXQgcGVvcGxlIGRvaW5nIHRoZSB3b3JrICAoSSdtIGp1c3QgdHJ5aW5nIHRvIGZp
bmlzaCBteSBmaWZ0ZWVudGggUkZDIGFzIGFuIGF1dGhvcikgYW5kIHdoYXQgd29ya3MgZm9yIHRo
ZW0uIEFuZCAieW91IGRvbid0IGNvbWUgdG8gbWVldGluZ3MiIGFzIGEgZGlzbWlzc2l2ZSBjb21t
ZW50IGlzbid0IGhlbHBmdWwgZWl0aGVyLiBJbiBhZGRpdGlvbiB0aGVyZSdzIGFuIGluaGVyZW50
IGNvbnRyYWRpY3Rpb24gaW4geW91ciBjb21tZW50cy4gSWYgdGhlIHBhZ2UgaXMgaW50ZW5kZWQg
Zm9yIHRoZSBnZW5lcmFsIHB1YmxpYywgd2hvIHJlYWxseSBkb24ndCBjb21lIHRvIG1lZXRpbmdz
LCB0aGVuIHRoZSB2YWx1ZSB5b3UgY3VycmVudGx5IHNlZSBpbiB0aGUgcmlnaHQgaGFuZCBwYXJ0
IG9mIHRoZSBwYWdlIGFib3V0IG1lZXRpbmdzIHdpbGwgYWxzbyBnby4gKEFuZCBtZWV0aW5ncyBh
cmUgYSBwbGFjZSBmb3Igd29yayB0aGF0IGlzbid0IHRoZSBkYXRhdHJhY2tlci4pDQoNCi0tIA0K
Q2hyaXN0b3BoZXIgRGVhcmxvdmUNClNlbmlvciBQcmluY2lwYWwgRW5naW5lZXINCkJBRSBTeXN0
ZW1zIEFwcGxpZWQgSW50ZWxsaWdlbmNlIExhYm9yYXRvcmllcw0KX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N
Cg0KVDogwqArNDQgMzMwMCA0Njc1MDAgwqB8IMKgRTogY2hyaXMuZGVhcmxvdmVAYmFlc3lzdGVt
cy5jb20NCg0KQkFFIFN5c3RlbXMgQXBwbGllZCBJbnRlbGxpZ2VuY2UsIENoZWxtc2ZvcmQgVGVj
aG5vbG9neSBQYXJrLCBHcmVhdCBCYWRkb3csIENoZWxtc2ZvcmQsIEVzc2V4IENNMiA4SE4uDQp3
d3cuYmFlc3lzdGVtcy5jb20vYWkNCkJBRSBTeXN0ZW1zIEFwcGxpZWQgSW50ZWxsaWdlbmNlIExp
bWl0ZWQNClJlZ2lzdGVyZWQgaW4gRW5nbGFuZCAmIFdhbGVzIE5vOiAwMTMzNzQ1MQ0KUmVnaXN0
ZXJlZCBPZmZpY2U6IFN1cnJleSBSZXNlYXJjaCBQYXJrLCBHdWlsZGZvcmQsIFN1cnJleSwgR1Uy
IDdZUA0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBZb2F2IE5pciBbbWFp
bHRvOnluaXIuaWV0ZkBnbWFpbC5jb21dIA0KU2VudDogMTggSnVseSAyMDE3IDEwOjEzDQpUbzog
RGVhcmxvdmUsIENocmlzdG9waGVyIChVSykNCkNjOiBSdXNzIEhvdXNsZXk7IElFVEYNClN1Ympl
Y3Q6IFJlOiBSZXZhbXAgb2YgdGhlIHd3dy5pZXRmLm9yZyB3ZWJzaXRlDQoNCg0KPiBPbiAxOCBK
dWwgMjAxNywgYXQgMTE6MDYsIERlYXJsb3ZlLCBDaHJpc3RvcGhlciAoVUspIDxjaHJpcy5kZWFy
bG92ZUBiYWVzeXN0ZW1zLmNvbT4gd3JvdGU6DQo+IA0KPiBFdmVyeXRoaW5nIEkgd2FudCBvbiB0
aGUgZXhpc3RpbmcgSUVURiB3ZWJzaXRlIGluIGluIGEgcGFuZWwgb24gdGhlIGxlZnQuIEkgcmFy
ZWx5IGV2ZW4gbG9vayBhdCB0aGUgcmlnaHRtb3N0IHRocmVlIHF1YXJ0ZXJzIG9mIHRoZSBzY3Jl
ZW4uDQoNClRoYXTigJlzIGJlY2F1c2UgeW91IGRvbuKAmXQgY29tZSB0byBtZWV0aW5ncy4gQXJv
dW5kIG1lZXRpbmdzIHRoZSByaWdodCBoYWxmIG9mIHRoZSBzY3JlZW4gYmVjb21lcyB1c2VmdWwu
DQoNCj4gVGhhdCBwYW5lbCBjYW4gYmUgdXNlZCB0byB0YWtlIG1lIHN0cmFpZ2h0IHRvIHdoZXJl
IEkgd2FudCB0byBnby4gVGhlIG5ldyBzaXRlIGF0IGl0IGFwcGVhcnMgYXMgbGlua2VkIGJlbG93
IGFwcGVhcnMgdG8gaGF2ZSBzZXJpb3VzbHkgcmVkdWNlZCB0aGUgdXNhYmlsaXR5IG9mIHRoZSBz
aXRlIGZvciBwZW9wbGUgd2hvIGtub3cgd2hhdCB0aGV5IHdhbnQgYW5kIHdhbnQgdG8gZ28gc3Ry
YWlnaHQgdG8gaXQuIFB1dCB0aGUgcGFuZWwgYmFjayAob3IgbWF5YmUgaXQncyBhbHdheXMgaW50
ZW5kZWQgdG8gYmUgdGhlcmUsIGFuZCB0aGlzIGlzIGp1c3QgdGhlIG1haW4gcGFuZSBiZWluZyBj
b25zaWRlcmVkKSBhbmQgSSBkb24ndCByZWFsbHkgbWluZCB3aGF0IHlvdSBkbyB0aGVyZSAoYXMg
bG9uZyBhcyBpdCBsb2FkcyBxdWlja2x5KS4NCg0KVGhlIG5ldyBzaXRlIGlzIGZvY3VzZWQgbm90
IG9uIHRoZSBleGlzdGluZyBwZW9wbGUgYWN0aXZlIGluIHRoZSBJRVRGLiBJdOKAmXMgZm9jdXNl
ZCBvbiB0aGUgZ2VuZXJhbCBwdWJsaWMuICBUaGUgcGxhY2Ugd2hlcmUgd29yayBnZXRzIGRvbmUg
dGhlc2UgZGF5cyBpcyBkYXRhdHJhY2tlci4NCg0KWW9hdg0KDQoNCioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqClRoaXMg
ZW1haWwgYW5kIGFueSBhdHRhY2htZW50cyBhcmUgY29uZmlkZW50aWFsIHRvIHRoZSBpbnRlbmRl
ZApyZWNpcGllbnQgYW5kIG1heSBhbHNvIGJlIHByaXZpbGVnZWQuIElmIHlvdSBhcmUgbm90IHRo
ZSBpbnRlbmRlZApyZWNpcGllbnQgcGxlYXNlIGRlbGV0ZSBpdCBmcm9tIHlvdXIgc3lzdGVtIGFu
ZCBub3RpZnkgdGhlIHNlbmRlci4KWW91IHNob3VsZCBub3QgY29weSBpdCBvciB1c2UgaXQgZm9y
IGFueSBwdXJwb3NlIG5vciBkaXNjbG9zZSBvcgpkaXN0cmlidXRlIGl0cyBjb250ZW50cyB0byBh
bnkgb3RoZXIgcGVyc29uLgoqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKgo=


From nobody Tue Jul 18 02:40:07 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA3F81315FE for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 02:40:06 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 PosEsNzCR9sw for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 02:40:04 -0700 (PDT)
Received: from mail-pg0-x22c.google.com (mail-pg0-x22c.google.com [IPv6:2607:f8b0:400e:c05::22c]) (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 6D306126E3A for <ietf@ietf.org>; Tue, 18 Jul 2017 02:40:04 -0700 (PDT)
Received: by mail-pg0-x22c.google.com with SMTP id k14so9826489pgr.0 for <ietf@ietf.org>; Tue, 18 Jul 2017 02:40:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=2vlJADkJZES8BynHsqKAjoDIIlorSXuAyu/Y534X1Co=; b=wtynhbmKegYfmUYzjr0DuZH+dycPhSUKCdOq27bExtAlvnTQJJ/xwzpzcFC/vTpOm4 otQmEVX1v0W0vyxHyOMtYlKqzfg7YjdtrNmoY77ZOhK7+x2RBC2ZGUMn3SoePPPF/KjP szOJaXr0F+BYgwpgXZ0qrgJ+/Nv3LjNujMHIWck7uuYYOfzfkA1iOukqwQfCbwNudizn 0mWOY0aoLGbQJSuf40XqwZlIQquoUVrxsmdUNLV4arXDLFyp4mAnTdVZSZiVxRidZAme I5UKRi95YX1WSTCHA1My3ZVEieHKoEzgLFeEwQf9BVPpK8pajaRlEAdtklB/EGdgw0un nEWQ==
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=2vlJADkJZES8BynHsqKAjoDIIlorSXuAyu/Y534X1Co=; b=me4S1Nj5Ba2FLH+NZjM3Mv3tDKmO/VbrBnaU+OzfuQ4cpZArbGtuMl+b+2RLs5GsFR wlunUNk5w/xdUJhg2qetAypRL7sFTqGRG4/wS6FnWksq9BvnpuWq7Kem9jU79ef2iSQX t4RvXMpILd8OJ9cWC0WLF9OwenNQrmPd293Zenvju+FGR2kBCZ3ZyKyLifq4Or7REW1B lZ+zGsRa5HcWI7eytzBMwTtIvGK1/sPTQ24FUqGkEVURmWCf4+HEdvp7IUjvK84QsznD t6VSRA9gdybSXOhKLt5LFvFWmvGtQELqLLFe9H7XoGC5liMxlu4Wiqnquh+o5p6suTb3 cINw==
X-Gm-Message-State: AIVw1102EaUVbj5EdHss8tt2nBe8hB4ft9H8Fh5T3fOOBh4MLvpdU/2P N7wiO5hlJc4n7/oJLr2vlXIRKdByJwrr
X-Received: by 10.98.10.68 with SMTP id s65mr726967pfi.55.1500370803996; Tue, 18 Jul 2017 02:40:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.181.42 with HTTP; Tue, 18 Jul 2017 02:39:23 -0700 (PDT)
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE63944B2@GLKXM0002V.GREENLNK.net>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6394482@GLKXM0002V.GREENLNK.net> <39D1C0A9-DB43-42DD-BD3F-7D636856ECEF@gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE63944B2@GLKXM0002V.GREENLNK.net>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 18 Jul 2017 11:39:23 +0200
Message-ID: <CAPt1N1=Z=ie1pguc1mG9Y-UirNGFMqyE=PFZ3R_408HFOddPHg@mail.gmail.com>
Subject: Re: Revamp of the www.ietf.org website
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Cc: Yoav Nir <ynir.ietf@gmail.com>, IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a11459fbacdd0f70554944c25"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WQnmkWZwz3VK8SwanXpKapb2wIg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 09:40:07 -0000

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

The response is not "we don't care about the people who do the work."   It
is "people who do the work have a really awesome tool to use, the
datatracker, so they don't need IETF.org to address their use case."

So a better approach to this, if you feel the datatracker is not actually
addressing your needs, your efforts would be better aimed at working that
issue.   I think at the moment the side bar on datatracker has everything
that you need that was in the sidebar on ietf.org.

So can you say what is missing here?

On Tue, Jul 18, 2017 at 11:23 AM, Dearlove, Christopher (UK) <
chris.dearlove@baesystems.com> wrote:

> I've been to many meetings (my first was IETF 55), though not very
> recently. And you can get to meetings off the leftmost panel too in about
> the same time.
>
> > The new site is focused not on the existing people active in the IETF.
> It=E2=80=99s focused on the general public.
>
> Let the general public have three quarters of the page. Let us have the
> other quarter.
>
> > The place where work gets done these days is datatracker.
>
> And that's one of the places one can easily get to. But there are others
> too. But sorry, this is not the sort of response that's useful - don't ca=
re
> about people doing the work  (I'm just trying to finish my fifteenth RFC =
as
> an author) and what works for them. And "you don't come to meetings" as a
> dismissive comment isn't helpful either. In addition there's an inherent
> contradiction in your comments. If the page is intended for the general
> public, who really don't come to meetings, then the value you currently s=
ee
> in the right hand part of the page about meetings will also go. (And
> meetings are a place for work that isn't the datatracker.)
>
> --
> Christopher Dearlove
> Senior Principal Engineer
> BAE Systems Applied Intelligence Laboratories
> _________________________________________________________________________=
_
>
> T:  +44 3300 467500  |  E: chris.dearlove@baesystems.com
>
> BAE Systems Applied Intelligence, Chelmsford Technology Park, Great
> Baddow, Chelmsford, Essex CM2 8HN.
> www.baesystems.com/ai
> BAE Systems Applied Intelligence Limited
> Registered in England & Wales No: 01337451
> Registered Office: Surrey Research Park, Guildford, Surrey, GU2 7YP
>
>
> -----Original Message-----
> From: Yoav Nir [mailto:ynir.ietf@gmail.com]
> Sent: 18 July 2017 10:13
> To: Dearlove, Christopher (UK)
> Cc: Russ Housley; IETF
> Subject: Re: Revamp of the www.ietf.org website
>
>
> > On 18 Jul 2017, at 11:06, Dearlove, Christopher (UK) <
> chris.dearlove@baesystems.com> wrote:
> >
> > Everything I want on the existing IETF website in in a panel on the
> left. I rarely even look at the rightmost three quarters of the screen.
>
> That=E2=80=99s because you don=E2=80=99t come to meetings. Around meeting=
s the right half
> of the screen becomes useful.
>
> > That panel can be used to take me straight to where I want to go. The
> new site at it appears as linked below appears to have seriously reduced
> the usability of the site for people who know what they want and want to =
go
> straight to it. Put the panel back (or maybe it's always intended to be
> there, and this is just the main pane being considered) and I don't reall=
y
> mind what you do there (as long as it loads quickly).
>
> The new site is focused not on the existing people active in the IETF.
> It=E2=80=99s focused on the general public.  The place where work gets do=
ne these
> days is datatracker.
>
> Yoav
>
>
> ********************************************************************
> This email and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or
> distribute its contents to any other person.
> ********************************************************************
>

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

<div dir=3D"ltr">The response is not &quot;we don&#39;t care about the peop=
le who do the work.&quot; =C2=A0 It is &quot;people who do the work have a =
really awesome tool to use, the datatracker, so they don&#39;t need IETF.or=
g to address their use case.&quot;<div><br></div><div>So a better approach =
to this, if you feel the datatracker is not actually addressing your needs,=
 your efforts would be better aimed at working that issue. =C2=A0 I think a=
t the moment the side bar on datatracker has everything that you need that =
was in the sidebar on <a href=3D"http://ietf.org">ietf.org</a>.</div><div><=
br></div><div>So can you say what is missing here?</div></div><div class=3D=
"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Jul 18, 2017 at 11:23 =
AM, Dearlove, Christopher (UK) <span dir=3D"ltr">&lt;<a href=3D"mailto:chri=
s.dearlove@baesystems.com" target=3D"_blank">chris.dearlove@baesystems.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">I&#39;ve been to ma=
ny meetings (my first was IETF 55), though not very recently. And you can g=
et to meetings off the leftmost panel too in about the same time.<br>
<span class=3D""><br>
&gt; The new site is focused not on the existing people active in the IETF.=
 It=E2=80=99s focused on the general public.<br>
<br>
</span>Let the general public have three quarters of the page. Let us have =
the other quarter.<br>
<span class=3D""><br>
&gt; The place where work gets done these days is datatracker.<br>
<br>
</span>And that&#39;s one of the places one can easily get to. But there ar=
e others too. But sorry, this is not the sort of response that&#39;s useful=
 - don&#39;t care about people doing the work=C2=A0 (I&#39;m just trying to=
 finish my fifteenth RFC as an author) and what works for them. And &quot;y=
ou don&#39;t come to meetings&quot; as a dismissive comment isn&#39;t helpf=
ul either. In addition there&#39;s an inherent contradiction in your commen=
ts. If the page is intended for the general public, who really don&#39;t co=
me to meetings, then the value you currently see in the right hand part of =
the page about meetings will also go. (And meetings are a place for work th=
at isn&#39;t the datatracker.)<br>
<span class=3D"im HOEnZb"><br>
--<br>
Christopher Dearlove<br>
Senior Principal Engineer<br>
BAE Systems Applied Intelligence Laboratories<br>
______________________________<wbr>______________________________<wbr>_____=
_________<br>
<br>
T: =C2=A0<a href=3D"tel:%2B44%203300%20467500" value=3D"+443300467500">+44 =
3300 467500</a> =C2=A0| =C2=A0E: <a href=3D"mailto:chris.dearlove@baesystem=
s.com">chris.dearlove@baesystems.com</a><br>
<br>
BAE Systems Applied Intelligence, Chelmsford Technology Park, Great Baddow,=
 Chelmsford, Essex CM2 8HN.<br>
<a href=3D"http://www.baesystems.com/ai" rel=3D"noreferrer" target=3D"_blan=
k">www.baesystems.com/ai</a><br>
BAE Systems Applied Intelligence Limited<br>
Registered in England &amp; Wales No: 01337451<br>
Registered Office: Surrey Research Park, Guildford, Surrey, GU2 7YP<br>
<br>
<br>
-----Original Message-----<br>
</span><div class=3D"HOEnZb"><div class=3D"h5">From: Yoav Nir [mailto:<a hr=
ef=3D"mailto:ynir.ietf@gmail.com">ynir.ietf@gmail.com</a>]<br>
Sent: 18 July 2017 10:13<br>
To: Dearlove, Christopher (UK)<br>
Cc: Russ Housley; IETF<br>
Subject: Re: Revamp of the <a href=3D"http://www.ietf.org" rel=3D"noreferre=
r" target=3D"_blank">www.ietf.org</a> website<br>
<br>
<br>
&gt; On 18 Jul 2017, at 11:06, Dearlove, Christopher (UK) &lt;<a href=3D"ma=
ilto:chris.dearlove@baesystems.com">chris.dearlove@baesystems.com</a><wbr>&=
gt; wrote:<br>
&gt;<br>
&gt; Everything I want on the existing IETF website in in a panel on the le=
ft. I rarely even look at the rightmost three quarters of the screen.<br>
<br>
That=E2=80=99s because you don=E2=80=99t come to meetings. Around meetings =
the right half of the screen becomes useful.<br>
<br>
&gt; That panel can be used to take me straight to where I want to go. The =
new site at it appears as linked below appears to have seriously reduced th=
e usability of the site for people who know what they want and want to go s=
traight to it. Put the panel back (or maybe it&#39;s always intended to be =
there, and this is just the main pane being considered) and I don&#39;t rea=
lly mind what you do there (as long as it loads quickly).<br>
<br>
The new site is focused not on the existing people active in the IETF. It=
=E2=80=99s focused on the general public.=C2=A0 The place where work gets d=
one these days is datatracker.<br>
<br>
Yoav<br>
<br>
<br>
</div></div><div class=3D"HOEnZb"><div class=3D"h5">***********************=
*******<wbr>******************************<wbr>********<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
******************************<wbr>******************************<wbr>*****=
***<br>
</div></div></blockquote></div><br></div>

--001a11459fbacdd0f70554944c25--


From nobody Tue Jul 18 02:47:41 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CA1B131A93 for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 02:47:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 GlIZbgoY6TVd for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 02:47:37 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C354131A67 for <ietf@ietf.org>; Tue, 18 Jul 2017 02:47:37 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dXP6M-000Ju5-Cv; Tue, 18 Jul 2017 05:47:34 -0400
Date: Tue, 18 Jul 2017 05:47:27 -0400
From: John C Klensin <john-ietf@jck.com>
To: Mark Nottingham <mnot@mnot.net>
cc: jordi.palet@consulintel.es, IETF <ietf@ietf.org>
Subject: Re: Revamp of the www.ietf.org website
Message-ID: <8FC4A4E243E797B32C26B9ED@PSB>
In-Reply-To: <728EAD91-6FF5-4FC0-BE1F-AB75CA8577C7@mnot.net>
References: <C1590F40-3B9E-45A0-9B87-59A0271B1952@consulintel.es> <20170717153147.D3EA61A6C8@ld9781.wdf.sap.corp> <748CC45D-1DDF-4A3B-A7CC-E3F5C990D550@consulintel.es> <F6924008EE2D26C4925CAD2D@PSB> <728EAD91-6FF5-4FC0-BE1F-AB75CA8577C7@mnot.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2TZIM_SSaEj0Nv6m0WeUC84m-CM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 09:47:40 -0000

Mark,

You (and Jordi) are at least partially right and I was probably
overreacting.  So let me back up a little bit (inline below).

--On Tuesday, July 18, 2017 08:30 +0200 Mark Nottingham
<mnot@mnot.net> wrote:

> 
>> On 17 Jul 2017, at 11:08 pm, John C Klensin
>> <john-ietf@jck.com> wrote:
>> 
>> * Precisely because the IETF has some very large vendors among
>> its supporters, our being able to continue to claim that we
>> are not biased toward those vendors and that our standards
>> decisions are not for sale, we need to be careful about not
>> forcing people to contribute to the bottom line of those
>> companies in order to participate.
> 
> How does linking to social media accounts constitute "forcing
> people... in order to participate"?

With the qualification below, I can live with feeding
announcements through to selected social media sites in addition
maintaining the current announcement lists.  The main thing that
concerns me (as usual) is slippery slopes, in which those
announcements segue into discussions in non-IETF forums that we
are all expected to track.  That concern parallels my concern
about shifting mailing list discussions to github or various
wikis (and I know we might disagree about that).

> No one is suggesting that one be required to tweet in order to
> register an objection.

My reaction was just because we've seen other cases in which we
use some other system to announce or log or keep information and
it promptly leads a a subset of the community pointing out how
much more convenient they find that tool relative to, e.g.,
mailing lists and calls to make that use normal or required.
If we are agreed, and will stay agreed, that we won't go there,
then I have no problem.

>>  We've been reasonably careful (much more careful
>> than some other SDOs) to not require someone to purchase some
>> particular work processing package or office suite to
>> participate.   I suggest that, if the IETF is going to get
>> tied up with Social Media, the system(s) used must be ones
>> that do not have business models involving  "user as
>> product", targeted advertising to users, permission to spam
>> users, or requirements that users give up significant privacy
>> in order to join, get feeds. or equ9ivalent.
> 
> You seem to be making a pretty big leap from "we don't require
> you to use proprietary tools in order to participate"
> (something that I very much agree with) to "we don't even want
> the *appearance* of (very) indirect endorsement of large
> companies." 

See above.
 
> I could understand a complaint that (for example) Sina Weibo
> isn't in that list, but banning all such links seems to ignore
> how much of the Internet is used today -- which isn't such a
> good look for the body that purports to oversee the Internet's
> protocols.

That is the other issue.  Are we willing to feed
announcement-type information through to any plausible social
media site/ system for which there is a request?  If not, what
is the stopping rule or criterion?

>> Again, if someone wants to re-{post,
>> chirp, tweet, vomit, etc.} materials from an IETF mailing
>> list, I think we have always allowed thet.  However, IMO, the
>> IETF needs to be really careful about getting more directly
>> involved.
> 
> I'm not sure why you bring that up; how would we stop it?

Because I think there actually is a big difference between the
IETF doing something and some individual or organization picking
something up and carrying it elsewhere.  If nothing else, there
is a question of how IPR rules, etc., would apply to reposted
materials given that they are not obviously IETF Contributions.
Again, if we confined this to announcements, I don't see a
problem either way.  

If we wanted to --and I think it would be a disasterously bad
idea -- we could at least partially stop it the same way other
SDOs do -- imposing copyright or proprietary information rules
on access to the information and insisting it not be further
distributed and then making it clear that we would enforce those
rules.  I hope we never go there or anywhere near it.

Again, apologies for the initial overreaction.

    best,
    john


From nobody Tue Jul 18 03:15:59 2017
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41DEF12EA7C for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 03:15:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level: 
X-Spam-Status: No, score=-4.302 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_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
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 YBnDj-hsKQeb for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 03:15:56 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C60C712969E for <ietf@ietf.org>; Tue, 18 Jul 2017 03:15:55 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6IA2i2w001687; Tue, 18 Jul 2017 11:02:49 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v6IA2i2w001687
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1500372174; bh=mi6UL8k05vnJhMYhFluR0dl4AGU=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=l6z4PcQqK1lLO9Rz3JdzZm88dasNZQ+lL/rFUGwpQ8RHP6PeQVI1eFtaBEzbWbap7 NLiDRTCLNT6uvkBBBUPvM8JZ5FqfrrSONjxBgvA9jgb3LVIQDHvqfkGdiH75Q1joaQ vLZKoMW07ElHuELfcsf4t1ViK92IUJEaFMOr2CmE=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id y6HB2Y1815203842Hk ret-id none; Tue, 18 Jul 2017 11:02:54 +0100
Received: from [10.64.11.87] (globalprotect-nat3.net.soton.ac.uk [152.78.0.20]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6IA2VDZ029709 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Jul 2017 11:02:31 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Revamp of the www.ietf.org website
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <c9c759cd-2d56-1367-4e42-644b83f46f13@gmail.com>
Date: Tue, 18 Jul 2017 11:02:29 +0100
Cc: Russ Housley <housley@vigilsec.com>, IETF <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|81bdfca5ec289a124bb7f95d39e55fbey6HB2Y03tjc|ecs.soton.ac.uk|999909C7-70EE-44BD-AC4E-4F07F14E56A4@ecs.soton.ac.uk>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <c9c759cd-2d56-1367-4e42-644b83f46f13@gmail.com> <999909C7-70EE-44BD-AC4E-4F07F14E56A4@ecs.soton.ac.uk>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3273)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=y6HB2Y181520384200; tid=y6HB2Y1815203842Hk; client=relay,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v6IA2i2w001687
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/x-wQ78cMBR1xSF8ENS1EHZaoP9k>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 10:15:58 -0000

> On 18 Jul 2017, at 03:42, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>=20
> On 15/07/2017 21:21, Russ Housley wrote:
> ...
>> For example, in response to the feedback provided, there is now a =
single page that provides links to tools and resources commonly used by =
active IETF participants.
>=20
> Thank you for that. The only thing is, it's not really a single page; =
I had to hit Page Down 4 times to see everything. On the current page =
(https://www.ietf.org/content.html) there's all that on one screen. =
Surely there must be a way to present the content more compactly, when =
not on a tiny screen, and with a default font size.

I sent a very similar response to the feedback address.  It=E2=80=99s =
really frustrating to have both the main page, and the Tools page, so =
inefficient that you have to scroll, and scroll, and scroll.

The front page seems to be in the same style as many web sites now, and =
is clearly aimed much more at non-IETF people than those doing work in =
the IETF.  I get that, but it=E2=80=99s then frustrating that the page =
for IETF participants is also inefficient.

Can we not make the Tools page (button top right) more like the current =
IETF home page, which pretty much renders in one screen, and has all the =
links that IETF participants would commonly want, including the next =
meeting panel.

> I mention that here because I think it's a very general point. I've =
entered tickets for some details, and I would encourage everybody to do =
that, because inevitably there will be errors in content conversion, and =
the more eyes looking for them, the better.

The response I got was basically =E2=80=9Ccome and discuss it in person =
in Prague=E2=80=9D - the new site designer(s) are here, near the =
registration desk.  It=E2=80=99s not clear what feedback is sticking, or =
not :)

Tim=


From nobody Tue Jul 18 03:29:04 2017
Return-Path: <ve7jtb@ve7jtb.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A5EB9131DE2; Tue, 18 Jul 2017 03:29:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: John Bradley <ve7jtb@ve7jtb.com>
To: <secdir@ietf.org>
Cc: urn@ietf.org, ietf@ietf.org, draft-ietf-urnbis-ns-reg-transition.all@ietf.org
Subject: Secdir last call review of draft-ietf-urnbis-ns-reg-transition-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.56.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150037374265.11421.1599883952756977836@ietfa.amsl.com>
Date: Tue, 18 Jul 2017 03:29:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1OFQg1cJHQjSomAdnFColhXxtzE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 10:29:03 -0000

Reviewer: John Bradley
Review result: Ready

No security issues.


From nobody Tue Jul 18 03:33:13 2017
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06E0B12EB5F; Tue, 18 Jul 2017 03:33:12 -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 Z9n60apZZhLn; Tue, 18 Jul 2017 03:33:10 -0700 (PDT)
Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (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 AB58D1270B4; Tue, 18 Jul 2017 03:33:10 -0700 (PDT)
Received: by mail-io0-x22b.google.com with SMTP id z62so11248265ioi.3; Tue, 18 Jul 2017 03:33:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=C0+6Pltv2cByzuXtnkcVjoEZJQe8LrZ57Cd+l6+ni+o=; b=maCBvmGJmUmK7QPnfVemqz20Uv9oUXameN5OWOelOha3/vOScxJ9Ema/VQSJ2RcMQc gTGSWZSoE+p9qOtHlZxEN29JYJNlTGQDRdco0K/Oyd+cDPlrkxf5leWpaNAxCkQl8jpC ZFCOu9mH1BfyexoIqljb+lhr2bOQ5slKxGD9R9CEj+puiPak7n6Z+D6rmXo7qS0MB2BU DUeitPNp18g2CblglkEufSZs9NbV+LHW5y08J2BphyFIuYPpGA6PJk9oLaVX0Qm8gxuf 5bP8rj6Nd+rgm4Lnb3PXSSc4/TTklkxnln1B6OVC8JMs7rFKdqozvjuOWLuMVvgHUGou 45gw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=C0+6Pltv2cByzuXtnkcVjoEZJQe8LrZ57Cd+l6+ni+o=; b=L8hXsZG4oY/N5rhSeQtCGjOvUTLjckNG9VSbwR/Zhn7Cwj0oojY66zg5ICYliMXU5f cRd9WWcekzISc8GhqwoVjOni43ib+RskezIaAwnM8tEtEo/reQud1n36aRHyDbb05KSd y+xiFK1Lfq1VwUO8anVfdHyJA5Mob4NQTNuQQBoRCVvSyf5PG/c480t+tR49sY+phFki HF7khbehmByA4TN5fs1g7EDEpIbHfPX9jS3OXkbLpsP6m1UiTALUuj5V1tROn99nPTNI KT0GRf9wRJeqy+PEc/WwcWGmxwieZ3C85QhiZM3Xwkv7/g7kKJ1DR06FA21r46Mt9m3B PZqg==
X-Gm-Message-State: AIVw112WhRgG8ALfGnNmahSQHU7jw4aqgT0tj+0cAZH83PRimFqBk3p+ POOmct5uulpMKj64PS8B7oiEPV/fSw==
X-Received: by 10.107.166.212 with SMTP id p203mr786176ioe.112.1500373990032;  Tue, 18 Jul 2017 03:33:10 -0700 (PDT)
MIME-Version: 1.0
Sender: barryleiba@gmail.com
Received: by 10.107.152.80 with HTTP; Tue, 18 Jul 2017 03:33:09 -0700 (PDT)
In-Reply-To: <150037374265.11421.1599883952756977836@ietfa.amsl.com>
References: <150037374265.11421.1599883952756977836@ietfa.amsl.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 18 Jul 2017 12:33:09 +0200
X-Google-Sender-Auth: C8lr584325x9i6rhOP68u2yHKVM
Message-ID: <CALaySJJ_Dpmf7rDr+iA5S08ppGMiR6ytfSYywA-G3bFvA3NLRA@mail.gmail.com>
Subject: Re: Secdir last call review of draft-ietf-urnbis-ns-reg-transition-08
To: John Bradley <ve7jtb@ve7jtb.com>
Cc: "secdir@ietf.org" <secdir@ietf.org>, "urn@ietf.org" <urn@ietf.org>, IETF discussion list <ietf@ietf.org>,  draft-ietf-urnbis-ns-reg-transition.all@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NNxWVTxT3lzjM9W3zWWMXYw5lNs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 10:33:12 -0000

Thanks, John, for taking the time to review.

Barry

On Tue, Jul 18, 2017 at 12:29 PM, John Bradley <ve7jtb@ve7jtb.com> wrote:
> Reviewer: John Bradley
> Review result: Ready
>
> No security issues.
>



-- 
Barry
--
Barry Leiba  (barryleiba@computer.org)
http://internetmessagingtechnology.org/


From nobody Tue Jul 18 03:34:38 2017
Return-Path: <rsk@gsp.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE1B1131A67 for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 03:34:36 -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 WhDz5sXnWfUS for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 03:34:35 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) (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 2AFB212EB5F for <ietf@ietf.org>; Tue, 18 Jul 2017 03:34:35 -0700 (PDT)
Received: from gsp.org (localhost [127.0.0.1]) by taos.firemountain.net (8.15.1/8.14.9) with SMTP id v6IAYXCp002709 for <ietf@ietf.org>; Tue, 18 Jul 2017 06:34:33 -0400 (EDT)
Date: Tue, 18 Jul 2017 06:34:33 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: Revamp of the www.ietf.org website
Message-ID: <20170718103433.GA13668@gsp.org>
References: <C1590F40-3B9E-45A0-9B87-59A0271B1952@consulintel.es> <20170717153147.D3EA61A6C8@ld9781.wdf.sap.corp>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170717153147.D3EA61A6C8@ld9781.wdf.sap.corp>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MWjMbAhHKDIMoVJ_3fGPba5FBbQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 10:34:37 -0000

On Mon, Jul 17, 2017 at 05:31:47PM +0200, Martin Rex wrote:
> Please get rid of the "social media" crap entirely.  

Strongly seconded.  The IETF should not be aiding and abetting
some of the world's worst security and privacy offenders; instead,
it should be scrupulously avoiding using or advocating any of
these mass surveillance/data acquisition operations, particularly
in light of RFC 7258.  Doubly so because some of them are
chronic, relentless spammers who use web bugs to conduct even
*more* surveillance and tracking.

> All in all, my personal summary for https://beta.ietf.org/
> disgusting and extremly bloated, usless and highly confusing.

I really want to be less harsh than this, but unfortunately I also
strongly concur with this point: it's trendy-looking junk that's
horribly overrun by enormous, pointless graphics.  (I see zero reason
for just about *any* graphics [1]: there's no functional need
to accomodate illiterate people.)  This is a horribly-bloated
major downgrade from the current site and it should be discarded.

It looks to me like far more like an exercise in ego-gratifying graphic
design than an efficient, lightweight/minimal design intended for
professional use by technical personnel.  Economy and conciseness are
particularly important to those who don't have the privilege of cheap
high-speed connectivity and/or the wealth to pay the usurious rates
charged by some ISPs.  As the IETF seeks increased involvement and
diversity around the world (a goal I strongly support) I think it's
critical to ensure that the resources required for participation are
kept minimal.

I recommend rendering it in a text-only browser (e.g., w3m) to see what
the page would look like when stripped down to functional essentials.
There's about 5K of actual content plus 20K-ish of markup buried in about
1M of cruft: in other words, the page as it is right now is roughly 40X
the size it needs to be to get the job done.  That's ridiculous.

Let me also note that passing that page through validators like
tidy or the W3C validator yields quite a few errors and warnings.
No, it's not necessary to obsessively clobber every last one of
those, but a lot of them would just go away if all of the useless
cruft was stripped out.

---rsk

[1] Small, isolated, occasional exceptions -- let's say, a graph or
an illustration -- might be acceptable.  But they should probably be
thumbnails that link to the actual image, so that only those who are
interested in that particular item need to load it.


From nobody Tue Jul 18 04:04:36 2017
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E5C11252BA; Tue, 18 Jul 2017 04:04:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 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_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 z5YuLtfqDTMR; Tue, 18 Jul 2017 04:04:33 -0700 (PDT)
Received: from mail-qt0-x232.google.com (mail-qt0-x232.google.com [IPv6:2607:f8b0:400d:c0d::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 6D973129459; Tue, 18 Jul 2017 04:04:33 -0700 (PDT)
Received: by mail-qt0-x232.google.com with SMTP id 32so12632669qtv.1; Tue, 18 Jul 2017 04:04:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=9lK/fkfLUH+Iwx9t6xjmrRrnIOTGAQLYFEamncUknlA=; b=MosNaGM7L9E0mPRzhfmbdwUX7hxu4C20sGGTTkNEa0hz7X70Jcjb6WNbkXBw9YcpDw H0jTbTOUm5OisV5vcrzkT7nzXAFGwqlhwXVXyjl5PizxsOggtB52ei20e1t2DlIz+tfQ 28/jq6i3wG0Qby80y7qhbN1oXB03jUj528AVoPhbaoK+Z10i9vv86cilK1nrBN0uUjWy O/fYZ0ZqUvs3oQImGcyO/flHaWJP02dD9yV9gkM/L/XhFA4q7KNg2uSJbZ+3wBb+ylSq GQt5B4dNpWllKp2FOvSKI49on0nSZuiYjsFnf+2xyZMlvm7P5Dym8YsmhqfY56FCZVdG wzoQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=9lK/fkfLUH+Iwx9t6xjmrRrnIOTGAQLYFEamncUknlA=; b=hprkYmErTgdcEGlZWZzm3Y1a+8nUBtoLYOOoeQUYHiJ6nXUKg5FiRF1okxmO9700wk bEIDeeWq1gkyW3TgWL8D/tY+s6K/cBEKkK+nzih2mTC6H3k3neGX7tsK64h7yXyDxsSh 2o1O8YhhbVfOBLQ1gcHjR9QTweihP/cu0FuLXktBEGP0jBnXujVhUoWGe2cz+Jj0wbvm 4yXgNNB7cXWq9dsxZsBONgVEJscowf4EHtkl+nF0CvIpQpstSNjP/FiyjEh3S7FaDxWF r3XD9WRIxH7kudWs+gdDM/4n1AfSm/aM4F06dwcg5KPepoS6Fq+dbWLhqVZk2x+L4bbR RzuQ==
X-Gm-Message-State: AIVw111dG2se8xrXKoLpksM3jRzYmpYpcybSDzbmvZjS16JcDMvpeqUE t0rataLVYkmM91E2fucmp+lEK79ACw==
X-Received: by 10.237.44.225 with SMTP id g88mr1165391qtd.150.1500375872539; Tue, 18 Jul 2017 04:04:32 -0700 (PDT)
MIME-Version: 1.0
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.200.37.40 with HTTP; Tue, 18 Jul 2017 04:04:32 -0700 (PDT)
In-Reply-To: <6a42a587-f09c-14bc-847b-7882c8f3e9f7@gmx.de>
References: <596CE6E3.3070808@isode.com> <92698d15-6557-8bb1-aad0-a0965e779e71@gmx.de> <668A56FD-4B89-472C-9E4C-BE5C0E6921F9@isode.com> <6a42a587-f09c-14bc-847b-7882c8f3e9f7@gmx.de>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 18 Jul 2017 13:04:32 +0200
X-Google-Sender-Auth: GsoTXo3Hr3jvtx6EYYFqN4mN-yI
Message-ID: <CAC4RtVC0fBbw-YiifN5p-gPLxHYRB0jkSumankTTcY+KbyTasw@mail.gmail.com>
Subject: Re: [Json] draft-ietf-jsonbis-rfc7159bis-03: recommendation to use UTF-8
To: Julian Reschke <julian.reschke@gmx.de>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, "ietf@ietf.org" <ietf@ietf.org>, "json@ietf.org" <json@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IMl5y9QlqKHfvBqmLCMskxVt9qo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 11:04:35 -0000

I have to agree with Julian here: this is not a change that's
appropriate to do in an RFC Editor note.  The change is probably fine,
but draft revisions are cheap and it's easy enough to post a revised
I-D to make sure we can all see the final version in context.

Thanks,
Barry


On Tue, Jul 18, 2017 at 10:19 AM, Julian Reschke <julian.reschke@gmx.de> wrote:
> On 2017-07-18 10:05, Alexey Melnikov wrote:
>>
>> Hi Julian,
>>
>>> On 18 Jul 2017, at 08:52, Julian Reschke <julian.reschke@gmx.de> wrote:
>>>
>>>> On 2017-07-17 18:33, Alexey Melnikov wrote:
>>>> Hi,
>>>> The JSONBIS WG decided to update recommendation on Unicode encoding to
>>>> be UTF-8. (For details see the RFC Editor's notes in the approval
>>>> message that will be sent out shortly.) This took a bit of time to
>>>> debate in the WG, so the document approval took a bit longer than
>>>> originally expected.
>>>> Best Regards,
>>>> Alexey, as the responsible AD
>>>
>>>
>>> The last WG mail related to this topic is over 2 months old, and I don't
>>> see any declaration of consensus.
>>>
>>> It would be good if the chair would send a summary about what's going on
>>> to the WG mailing list before anything gets finalized.
>>>
>>> (I note that
>>> <https://datatracker.ietf.org/doc/draft-ietf-jsonbis-rfc7159bis/> has been
>>> saying "Revised ID Needed" for 48 days, and I was under the assumption that
>>> there'd be indeed a revised ID).
>>
>>
>> I just posted a message on this: this is approved with updated RFC Editor
>> notes. See the approval message once it is sent.
>> ...
>
>
> This is not how it's supposed to work. Please have a new I-D posted and get
> people to review the changes in context. This is a *very* important piece of
> standards work - we need to make sure it meets quality standards.
>
> From a quick glance at
> <https://datatracker.ietf.org/doc/draft-ietf-jsonbis-rfc7159bis/writeup/>, I
> already note that the appendix "Changes from RFC 7159" is now incomplete.
>
> Best regards, Julian
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json


From nobody Tue Jul 18 04:18:29 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9175813178B; Tue, 18 Jul 2017 04:18:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.002
X-Spam-Level: 
X-Spam-Status: No, score=-7.002 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_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 nxHRwuVRZvZ4; Tue, 18 Jul 2017 04:18:20 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EC8F131488; Tue, 18 Jul 2017 04:18:20 -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=1500376700; x=1531912700; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=f1aCV/FMkh3T51ytMuRUHO/4NIvcHJJL4QwQ/ggEx1A=; b=qDxOReyYyKQ/g3X/9XbD6sL2tawDkvEhW1diz2fB3wCr6LvDMteYnqXE DG69WtukpjZhGeQoVnKMARuII0Cd2EL/Q8w2AlLnBPW+tpDvu0qaDTqJ4 ZZmw/ZUGqwrP0uFWeI3RA3C+R9iWe39hpXurxR2kzn39FfRM7WQm9fid6 o=;
X-IronPort-AV: E=Sophos;i="5.40,377,1496127600"; d="scan'208";a="111796188"
Received: from unknown (HELO ironmsg02-R.qualcomm.com) ([10.53.140.106]) by sabertooth02.qualcomm.com with ESMTP; 18 Jul 2017 04:18:19 -0700
X-IronPort-AV: E=McAfee;i="5800,7501,8594"; a="1000376862"
X-MGA-submission: =?us-ascii?q?MDHdP7SZDsoDm676c6k/mkii9nF9Q3H+lG8Ce4?= =?us-ascii?q?v+KQ/XEtFHxg7glU+p2FvXE9pxFDK2gNPcm/VMASCf0/gj+k6wG9OJU4?= =?us-ascii?q?VmluZubRyJ0Ua4pXVXkG12CxJt9s71vzlBWrMe45WxcQQ4d+WT5VWbm8?= =?us-ascii?q?xr?=
Received: from nasanexm01b.na.qualcomm.com ([10.85.0.82]) by ironmsg02-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 18 Jul 2017 04:18:19 -0700
Received: from [10.64.103.81] (10.80.80.8) by NASANEXM01B.na.qualcomm.com (10.85.0.82) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Tue, 18 Jul 2017 04:18:18 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Barry Leiba <barryleiba@computer.org>
CC: Julian Reschke <julian.reschke@gmx.de>, Alexey Melnikov <alexey.melnikov@isode.com>, "ietf@ietf.org" <ietf@ietf.org>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] draft-ietf-jsonbis-rfc7159bis-03: recommendation to use UTF-8
Date: Tue, 18 Jul 2017 13:18:15 +0200
Message-ID: <28D32024-5E4C-44C7-A54A-049BA97289CE@qti.qualcomm.com>
In-Reply-To: <CAC4RtVC0fBbw-YiifN5p-gPLxHYRB0jkSumankTTcY+KbyTasw@mail.gmail.com>
References: <596CE6E3.3070808@isode.com> <92698d15-6557-8bb1-aad0-a0965e779e71@gmx.de> <668A56FD-4B89-472C-9E4C-BE5C0E6921F9@isode.com> <6a42a587-f09c-14bc-847b-7882c8f3e9f7@gmx.de> <CAC4RtVC0fBbw-YiifN5p-gPLxHYRB0jkSumankTTcY+KbyTasw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.6r5347)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01E.na.qualcomm.com (10.85.0.31) To NASANEXM01B.na.qualcomm.com (10.85.0.82)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LjZa6dJEtJJ5d_I-R1LrvDRlbcM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 11:18:22 -0000

Alexey,

I believe Julian and Barry's notes constitute an appeal of the Protocol 
Action, and I think they're probably right. Please rescind it, publish 
the new draft, and give people a bit to review. No need for another 
formal LC, but doing this in a note to the RFC Editor isn't kosher.

pr

On 18 Jul 2017, at 13:04, Barry Leiba wrote:

> I have to agree with Julian here: this is not a change that's
> appropriate to do in an RFC Editor note.  The change is probably fine,
> but draft revisions are cheap and it's easy enough to post a revised
> I-D to make sure we can all see the final version in context.
>
> Thanks,
> Barry
>
>
> On Tue, Jul 18, 2017 at 10:19 AM, Julian Reschke 
> <julian.reschke@gmx.de> wrote:
>> On 2017-07-18 10:05, Alexey Melnikov wrote:
>>>
>>> Hi Julian,
>>>
>>>> On 18 Jul 2017, at 08:52, Julian Reschke <julian.reschke@gmx.de> 
>>>> wrote:
>>>>
>>>>> On 2017-07-17 18:33, Alexey Melnikov wrote:
>>>>> Hi,
>>>>> The JSONBIS WG decided to update recommendation on Unicode 
>>>>> encoding to
>>>>> be UTF-8. (For details see the RFC Editor's notes in the approval
>>>>> message that will be sent out shortly.) This took a bit of time to
>>>>> debate in the WG, so the document approval took a bit longer than
>>>>> originally expected.
>>>>> Best Regards,
>>>>> Alexey, as the responsible AD
>>>>
>>>>
>>>> The last WG mail related to this topic is over 2 months old, and I 
>>>> don't
>>>> see any declaration of consensus.
>>>>
>>>> It would be good if the chair would send a summary about what's 
>>>> going on
>>>> to the WG mailing list before anything gets finalized.
>>>>
>>>> (I note that
>>>> <https://datatracker.ietf.org/doc/draft-ietf-jsonbis-rfc7159bis/> 
>>>> has been
>>>> saying "Revised ID Needed" for 48 days, and I was under the 
>>>> assumption that
>>>> there'd be indeed a revised ID).
>>>
>>>
>>> I just posted a message on this: this is approved with updated RFC 
>>> Editor
>>> notes. See the approval message once it is sent.
>>> ...
>>
>>
>> This is not how it's supposed to work. Please have a new I-D posted 
>> and get
>> people to review the changes in context. This is a *very* important 
>> piece of
>> standards work - we need to make sure it meets quality standards.
>>
>> From a quick glance at
>> <https://datatracker.ietf.org/doc/draft-ietf-jsonbis-rfc7159bis/writeup/>, 
>> I
>> already note that the appendix "Changes from RFC 7159" is now 
>> incomplete.
>>
>> Best regards, Julian
>>
>> _______________________________________________
>> json mailing list
>> json@ietf.org
>> https://www.ietf.org/mailman/listinfo/json


From nobody Tue Jul 18 04:24:26 2017
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D64521317D7 for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 04:24:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level: 
X-Spam-Status: No, score=-4.302 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_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
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 e6V9HAzPXGaG for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 04:24:22 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E21C131471 for <ietf@ietf.org>; Tue, 18 Jul 2017 04:24:22 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6IBMIRR020493; Tue, 18 Jul 2017 12:22:28 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v6IBMIRR020493
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1500376974; bh=BoJBif0xqauFwt2BexQE+iSlDeQ=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=d1H5mEDw6JEQOebAL8HUbKTtoqNWbSGjB+83cxyM2XN058OpGqmjR/E/MnUkMdvng 3tD7flCEJ67vu4xprFenOTgSh5E9lC/gwsaVzK5BuIb+3rH9Uwj+CbTXc/i2EwRadL STZJ+LetQy1w1/p7UgIKg2MxoR+AOW7SrnedQ+tY=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id y6HCM81815204738Gz ret-id none; Tue, 18 Jul 2017 12:22:53 +0100
Received: from [IPv6:2001:67c:370:1998:7cc3:29f1:a519:bb9d] ([IPv6:2001:67c:370:1998:7cc3:29f1:a519:bb9d]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6IBLQAa024320 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Jul 2017 12:21:27 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Revamp of the www.ietf.org website
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <CAPt1N1=Z=ie1pguc1mG9Y-UirNGFMqyE=PFZ3R_408HFOddPHg@mail.gmail.com>
Date: Tue, 18 Jul 2017 12:21:25 +0100
Cc: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>, IETF <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|f08866446f7363ed14c38a6f72e032fey6HCM803tjc|ecs.soton.ac.uk|A86DD342-6530-450B-9B45-8A7AAB08E411@ecs.soton.ac.uk>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6394482@GLKXM0002V.GREENLNK.net> <39D1C0A9-DB43-42DD-BD3F-7D636856ECEF@gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE63944B2@GLKXM0002V.GREENLNK.net> <CAPt1N1=Z=ie1pguc1mG9Y-UirNGFMqyE=PFZ3R_408HFOddPHg@mail.gmail.com> <A86DD342-6530-450B-9B45-8A7AAB08E411@ecs.soton.ac.uk>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3273)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-ECS-MailScanner-SpamScore: ssss
X-smtpf-Report: sid=y6HCLX181520473800; tid=y6HCM81815204738Gz; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=3:0; fails=2
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v6IBMIRR020493
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/D6Wm5OETewIqChe_Ss5H1YLbxxU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 11:24:25 -0000

> On 18 Jul 2017, at 10:39, Ted Lemon <mellon@fugue.com> wrote:
>=20
> The response is not "we don't care about the people who do the work."  =
 It is "people who do the work have a really awesome tool to use, the =
datatracker, so they don't need IETF.org to address their use case."
>=20
> So a better approach to this, if you feel the datatracker is not =
actually addressing your needs, your efforts would be better aimed at =
working that issue.   I think at the moment the side bar on datatracker =
has everything that you need that was in the sidebar on ietf.org.
>=20
> So can you say what is missing here?

The datatracker site sidebar is certainly useful. But a few things are =
presented rather differently, the meetings section being one notable =
example.

It seems the main IETF page/site is becoming the IETF corporate web =
site, and will look like many other such sites out there, and the IETF =
participant area is the =E2=80=9Cintranet=E2=80=9D, in the form of the =
datatracker and tools pages, for which to do many things you need to =
sign in.  That=E2=80=99s OK, and understood, and participants will learn =
to go to the different site in place of the main IETF site, but the =
functionality isn=E2=80=99t quite the same, yet.

Tim

> On Tue, Jul 18, 2017 at 11:23 AM, Dearlove, Christopher (UK) =
<chris.dearlove@baesystems.com> wrote:
> I've been to many meetings (my first was IETF 55), though not very =
recently. And you can get to meetings off the leftmost panel too in =
about the same time.
>=20
> > The new site is focused not on the existing people active in the =
IETF. It=E2=80=99s focused on the general public.
>=20
> Let the general public have three quarters of the page. Let us have =
the other quarter.
>=20
> > The place where work gets done these days is datatracker.
>=20
> And that's one of the places one can easily get to. But there are =
others too. But sorry, this is not the sort of response that's useful - =
don't care about people doing the work  (I'm just trying to finish my =
fifteenth RFC as an author) and what works for them. And "you don't come =
to meetings" as a dismissive comment isn't helpful either. In addition =
there's an inherent contradiction in your comments. If the page is =
intended for the general public, who really don't come to meetings, then =
the value you currently see in the right hand part of the page about =
meetings will also go. (And meetings are a place for work that isn't the =
datatracker.)
>=20
> --
> Christopher Dearlove
> Senior Principal Engineer
> BAE Systems Applied Intelligence Laboratories
> =
__________________________________________________________________________=

>=20
> T:  +44 3300 467500  |  E: chris.dearlove@baesystems.com
>=20
> BAE Systems Applied Intelligence, Chelmsford Technology Park, Great =
Baddow, Chelmsford, Essex CM2 8HN.
> www.baesystems.com/ai
> BAE Systems Applied Intelligence Limited
> Registered in England & Wales No: 01337451
> Registered Office: Surrey Research Park, Guildford, Surrey, GU2 7YP
>=20
>=20
> -----Original Message-----
> From: Yoav Nir [mailto:ynir.ietf@gmail.com]
> Sent: 18 July 2017 10:13
> To: Dearlove, Christopher (UK)
> Cc: Russ Housley; IETF
> Subject: Re: Revamp of the www.ietf.org website
>=20
>=20
> > On 18 Jul 2017, at 11:06, Dearlove, Christopher (UK) =
<chris.dearlove@baesystems.com> wrote:
> >
> > Everything I want on the existing IETF website in in a panel on the =
left. I rarely even look at the rightmost three quarters of the screen.
>=20
> That=E2=80=99s because you don=E2=80=99t come to meetings. Around =
meetings the right half of the screen becomes useful.
>=20
> > That panel can be used to take me straight to where I want to go. =
The new site at it appears as linked below appears to have seriously =
reduced the usability of the site for people who know what they want and =
want to go straight to it. Put the panel back (or maybe it's always =
intended to be there, and this is just the main pane being considered) =
and I don't really mind what you do there (as long as it loads quickly).
>=20
> The new site is focused not on the existing people active in the IETF. =
It=E2=80=99s focused on the general public.  The place where work gets =
done these days is datatracker.
>=20
> Yoav
>=20
>=20
> ********************************************************************
> This email and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or
> distribute its contents to any other person.
> ********************************************************************
>=20


From nobody Tue Jul 18 04:27:57 2017
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 951F9131AA6; Tue, 18 Jul 2017 04:27:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 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_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 nkWUBxezbZ4m; Tue, 18 Jul 2017 04:27:54 -0700 (PDT)
Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (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 3A328131A7B; Tue, 18 Jul 2017 04:27:54 -0700 (PDT)
Received: by mail-qt0-x22c.google.com with SMTP id 21so12940221qtx.3; Tue, 18 Jul 2017 04:27:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=U/N9XJxNb5Yn+4mpRLtcxYZT5644/VsHb5sOnEsFSC8=; b=ZrspHuW0YuvcwtuUOePiyVPtBamyAO3mivX5wSNtsbaupm0R5TvjYESAEoW7HdyZVh z3iLvhnaNpRmsiW4kKP70ZAHMz1S/uxWa89SJcFSicjlay7sk9unwY+wYhWWvbt04aMS 0O1rhOSd9R/UIEl52KjC8lpuISIjPnTOspJuUCJBm0KuINrx4Kq3juPuql7ma7u9uSZi VPvPmlEGz0w+YZmP7R9fMWk6fv5pk2BisFWNtNUYOaTW27hkLSwUtryh/IOp804csFiH cRuLuE16ATme/WwyqBqgTwa0Lmhw+1R0NMZxyWYV3g8BHRZJKgF43heMu4613X0Gzk0K xXxw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=U/N9XJxNb5Yn+4mpRLtcxYZT5644/VsHb5sOnEsFSC8=; b=t7qDcsBITw8kDA3SIXVS5IqZJcgPxLBNU4QfzHTqdceG+p6oO92GoKMTQqkx8vHOIH ZaJjtioA5qdQPzifqjDJl/+sTZpzFtSXNh4WrdeSXirMYF4/an0Tc5Iu2tKtzzv6elcx GRNQqvKsTEtMw8vlD3gct+D5znBIpdmctNcY1nBhKCMHMIrta0fILAPLQi9sSO63KoDR gb1pR6jUiQFhD6TpbU+yDT450x87woZJOQcQza8aWABPwyNTKGn7tJ6cexb7n5LBXIYY 44gQbEmEzLfpRFYZKRxIauf8xQVvoXSL0UbDOU7mnNDL2VSIeSe/7Pqt6ys/lNlKKSDo LKCA==
X-Gm-Message-State: AIVw110JZhX8Ug4C9RAhy8ToWKKYz+RlFOJN8fPHGcnfFVmVC9Xfyr9V 4Qu4heXBcv2O77U6FmhvqjiDEy9WwA==
X-Received: by 10.200.57.162 with SMTP id v31mr1220272qte.57.1500377273403; Tue, 18 Jul 2017 04:27:53 -0700 (PDT)
MIME-Version: 1.0
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.200.37.40 with HTTP; Tue, 18 Jul 2017 04:27:52 -0700 (PDT)
In-Reply-To: <28D32024-5E4C-44C7-A54A-049BA97289CE@qti.qualcomm.com>
References: <596CE6E3.3070808@isode.com> <92698d15-6557-8bb1-aad0-a0965e779e71@gmx.de> <668A56FD-4B89-472C-9E4C-BE5C0E6921F9@isode.com> <6a42a587-f09c-14bc-847b-7882c8f3e9f7@gmx.de> <CAC4RtVC0fBbw-YiifN5p-gPLxHYRB0jkSumankTTcY+KbyTasw@mail.gmail.com> <28D32024-5E4C-44C7-A54A-049BA97289CE@qti.qualcomm.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 18 Jul 2017 13:27:52 +0200
X-Google-Sender-Auth: Aj_LPBY7_DjgQ2Emrmu6XGeQkCA
Message-ID: <CAC4RtVB2dYSJXiozoR6=Zds73bEbiGpDsj_W+mbpJhqQNU5S5g@mail.gmail.com>
Subject: Re: [Json] draft-ietf-jsonbis-rfc7159bis-03: recommendation to use UTF-8
To: Pete Resnick <presnick@qti.qualcomm.com>
Cc: Julian Reschke <julian.reschke@gmx.de>, Alexey Melnikov <alexey.melnikov@isode.com>,  "ietf@ietf.org" <ietf@ietf.org>, "json@ietf.org" <json@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gqG1qMTbANHUfQrg0JDqKIsCAnc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 11:27:55 -0000

I hadn't thought of it as an appeal, but I do think the current
document state should be "Approved, Announcement to be Sent" with a
substate of "Revised I-D Needed".  If an appeal is what's needed to
change that, then... yeah, sure.

Barry

On Tue, Jul 18, 2017 at 1:18 PM, Pete Resnick <presnick@qti.qualcomm.com> wrote:
> Alexey,
>
> I believe Julian and Barry's notes constitute an appeal of the Protocol
> Action, and I think they're probably right. Please rescind it, publish the
> new draft, and give people a bit to review. No need for another formal LC,
> but doing this in a note to the RFC Editor isn't kosher.
>
> pr
>
>
> On 18 Jul 2017, at 13:04, Barry Leiba wrote:
>
>> I have to agree with Julian here: this is not a change that's
>> appropriate to do in an RFC Editor note.  The change is probably fine,
>> but draft revisions are cheap and it's easy enough to post a revised
>> I-D to make sure we can all see the final version in context.
>>
>> Thanks,
>> Barry
>>
>>
>> On Tue, Jul 18, 2017 at 10:19 AM, Julian Reschke <julian.reschke@gmx.de>
>> wrote:
>>>
>>> On 2017-07-18 10:05, Alexey Melnikov wrote:
>>>>
>>>>
>>>> Hi Julian,
>>>>
>>>>> On 18 Jul 2017, at 08:52, Julian Reschke <julian.reschke@gmx.de> wrote:
>>>>>
>>>>>> On 2017-07-17 18:33, Alexey Melnikov wrote:
>>>>>> Hi,
>>>>>> The JSONBIS WG decided to update recommendation on Unicode encoding to
>>>>>> be UTF-8. (For details see the RFC Editor's notes in the approval
>>>>>> message that will be sent out shortly.) This took a bit of time to
>>>>>> debate in the WG, so the document approval took a bit longer than
>>>>>> originally expected.
>>>>>> Best Regards,
>>>>>> Alexey, as the responsible AD
>>>>>
>>>>>
>>>>>
>>>>> The last WG mail related to this topic is over 2 months old, and I
>>>>> don't
>>>>> see any declaration of consensus.
>>>>>
>>>>> It would be good if the chair would send a summary about what's going
>>>>> on
>>>>> to the WG mailing list before anything gets finalized.
>>>>>
>>>>> (I note that
>>>>> <https://datatracker.ietf.org/doc/draft-ietf-jsonbis-rfc7159bis/> has
>>>>> been
>>>>> saying "Revised ID Needed" for 48 days, and I was under the assumption
>>>>> that
>>>>> there'd be indeed a revised ID).
>>>>
>>>>
>>>>
>>>> I just posted a message on this: this is approved with updated RFC
>>>> Editor
>>>> notes. See the approval message once it is sent.
>>>> ...
>>>
>>>
>>>
>>> This is not how it's supposed to work. Please have a new I-D posted and
>>> get
>>> people to review the changes in context. This is a *very* important piece
>>> of
>>> standards work - we need to make sure it meets quality standards.
>>>
>>> From a quick glance at
>>>
>>> <https://datatracker.ietf.org/doc/draft-ietf-jsonbis-rfc7159bis/writeup/>, I
>>> already note that the appendix "Changes from RFC 7159" is now incomplete.
>>>
>>> Best regards, Julian
>>>
>>> _______________________________________________
>>> json mailing list
>>> json@ietf.org
>>> https://www.ietf.org/mailman/listinfo/json
>
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json


From nobody Tue Jul 18 04:38:55 2017
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BA84131AAF for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 04:38:54 -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 ugwhNS3zCRur for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 04:38:52 -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 C04EF131AA6 for <ietf@ietf.org>; Tue, 18 Jul 2017 04:38:51 -0700 (PDT)
Received: by mail-wr0-x232.google.com with SMTP id y43so25137333wrd.3 for <ietf@ietf.org>; Tue, 18 Jul 2017 04:38:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=XAhayy8991a6RF7sxG9gvsuItAwp+b2Knvj4XgXpfpU=; b=PvXgUsyx6A5CSu+zqBPTZBtP1WH51kkYRryN3fF0ftOHhU+sJxQnORBaBAEO9IqoQU 248drHqI43el8PBbSwnDMLysKml6Unc9jA1lS1AVKmkMj7nrEHpKEFT5kKylTYh/YkZG Xr3sk5lCxw9gYSdq9R4sCeVd/9oTOuUcjjHWtwrVgDOI1FrEa5uny/69c7fgWmkfufrs jIwYDJ8zTLh4iYDfqxulWWJhpgvTNKBbS6YSP4NDRdk2udbiveCnAfoI4DUVOLfFbIrr Dbxy9psMKNo6/kbLrwQ/MtDcPKBCLRsvyNQm/wJ9hbFvzFGNn3FSeIaDZSmhOXp4m43F 98KA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=XAhayy8991a6RF7sxG9gvsuItAwp+b2Knvj4XgXpfpU=; b=A4JwPhpzT0LEAzm2B7WvZu1Zhf6Kn8XMgQfGV1Kjcm6UrOGuEDNx24y2g6RT92qKhZ 4D6AI7oPrXYQGxMpCxCVVKPVEiHs5HNmirvgXchB0liWT+PcazieFb/fbCYgmNy6jB2V 54qqPeEKJFfEEVo1HDc6A/Jq+16tWw9oWoKeXRkctJ+8S53jWZolJjO66K77yEQ03yP2 cbl7WPAIfRNiR9zB8M59t4LuFT7Yax9CF63aUPj086UswNga6+oA+fMZ6LlCRbzWXedI prfnmidi/6uQQbfx/rwd5x53fQpkVEQZl5ZIsA/te/+JsO1Mx66EkvG0hAK7JSej7jYu 27LQ==
X-Gm-Message-State: AIVw110UBptP0erw3/lggJa/82z5FcNIhKynebQO4Pew16++N7Vd5Aqr pFgyQWRwK+wCmLFhs7M=
X-Received: by 10.28.156.20 with SMTP id f20mr1871638wme.17.1500377930362; Tue, 18 Jul 2017 04:38:50 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:128:cdff:5c1a:87f0:2e96? ([2001:67c:370:128:cdff:5c1a:87f0:2e96]) by smtp.gmail.com with ESMTPSA id 49sm2192177wrv.23.2017.07.18.04.38.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Jul 2017 04:38:49 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <7C44A125-DF91-4938-B0AB-93B5DF5EEB12@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_14AE7DBC-6DC9-44D5-B6C8-CC7E2956B764"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Revamp of the www.ietf.org website
Date: Tue, 18 Jul 2017 13:38:48 +0200
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE63944B2@GLKXM0002V.GREENLNK.net>
Cc: Russ Housley <housley@vigilsec.com>, IETF <ietf@ietf.org>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6394482@GLKXM0002V.GREENLNK.net> <39D1C0A9-DB43-42DD-BD3F-7D636856ECEF@gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE63944B2@GLKXM0002V.GREENLNK.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kATp3bJ3hBGyreEHzH4s3pYYkj8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 11:38:54 -0000

--Apple-Mail=_14AE7DBC-6DC9-44D5-B6C8-CC7E2956B764
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_D5FBF23C-F398-4E51-8B50-01526C90DB6D"


--Apple-Mail=_D5FBF23C-F398-4E51-8B50-01526C90DB6D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On 18 Jul 2017, at 11:23, Dearlove, Christopher (UK) =
<chris.dearlove@baesystems.com> wrote:
>=20
> I've been to many meetings (my first was IETF 55), though not very =
recently. And you can get to meetings off the leftmost panel too in =
about the same time.
>=20
>> The new site is focused not on the existing people active in the =
IETF. It=E2=80=99s focused on the general public.
>=20
> Let the general public have three quarters of the page. Let us have =
the other quarter.

Or let the general public have a whole page for themselves and another =
for all our tools.

>> The place where work gets done these days is datatracker.
>=20
> And that's one of the places one can easily get to. But there are =
others too. But sorry, this is not the sort of response that's useful - =
don't care about people doing the work  (I'm just trying to finish my =
fifteenth RFC as an author) and what works for them. And "you don't come =
to meetings" as a dismissive comment isn't helpful either.

It=E2=80=99s not dismissive. The current main page has all the important =
links for the *current* meeting: registration, agenda, wiki, remote =
participation, hackathon. That=E2=80=99s two layers deep going from the =
box on the left. If you=E2=80=99re not here, none but perhaps the agenda =
matter.  But since I am at the meeting, this works (to use a 90s term) =
as a portal.

> In addition there's an inherent contradiction in your comments. If the =
page is intended for the general public, who really don't come to =
meetings, then the value you currently see in the right hand part of the =
page about meetings will also go. (And meetings are a place for work =
that isn't the datatracker.)

The current site (www.ietf.org <http://www.ietf.org/>) is meant for us. =
The new page (current beta.ietf.org <http://beta.ietf.org/>) is IMO not. =
Most of the links on the left side of the current page are to pages =
under datatracker. This probably needs to be our new portal to the IETF.

Yoav



--Apple-Mail=_D5FBF23C-F398-4E51-8B50-01526C90DB6D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 18 Jul 2017, at 11:23, Dearlove, Christopher (UK) &lt;<a =
href=3D"mailto:chris.dearlove@baesystems.com" =
class=3D"">chris.dearlove@baesystems.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">I've =
been to many meetings (my first was IETF 55), though not very recently. =
And you can get to meetings off the leftmost panel too in about the same =
time.<br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D"">The new site is focused not on the existing people active in =
the IETF. It=E2=80=99s focused on the general public. <br =
class=3D""></blockquote><br class=3D"">Let the general public have three =
quarters of the page. Let us have the other quarter.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>Or let the =
general public have a whole page for themselves and another for all our =
tools.</div><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><blockquote type=3D"cite" class=3D"">The =
place where work gets done these days is datatracker.<br =
class=3D""></blockquote><br class=3D"">And that's one of the places one =
can easily get to. But there are others too. But sorry, this is not the =
sort of response that's useful - don't care about people doing the work =
&nbsp;(I'm just trying to finish my fifteenth RFC as an author) and what =
works for them. And "you don't come to meetings" as a dismissive comment =
isn't helpful either.</div></div></blockquote><div><br =
class=3D""></div><div>It=E2=80=99s not dismissive. The current main page =
has all the important links for the *current* meeting: registration, =
agenda, wiki, remote participation, hackathon. That=E2=80=99s two layers =
deep going from the box on the left. If you=E2=80=99re not here, none =
but perhaps the agenda matter. &nbsp;But since I am at the meeting, this =
works (to use a 90s term) as a portal.</div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D""> In addition =
there's an inherent contradiction in your comments. If the page is =
intended for the general public, who really don't come to meetings, then =
the value you currently see in the right hand part of the page about =
meetings will also go. (And meetings are a place for work that isn't the =
datatracker.)<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>The current site (<a href=3D"http://www.ietf.org" =
class=3D"">www.ietf.org</a>) is meant for us. The new page (current <a =
href=3D"http://beta.ietf.org" class=3D"">beta.ietf.org</a>) is IMO not. =
Most of the links on the left side of the current page are to pages =
under datatracker. This probably needs to be our new portal to the =
IETF.</div><div><br class=3D""></div><div>Yoav</div><div><br =
class=3D""></div><div><br class=3D""></div></body></html>=

--Apple-Mail=_D5FBF23C-F398-4E51-8B50-01526C90DB6D--

--Apple-Mail=_14AE7DBC-6DC9-44D5-B6C8-CC7E2956B764
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJZbfNJAAoJELhJCxUKWMyZrlIIAKZ893yUwxCFiK5enbz5br0j
bsgRvin1ONHoHwBxv/lFssXMUeG+ic4kq0Bl0T8l2fCsGlGKmp9inPjcvpHdh+a5
+8fZw6U2mie9skqncwLRjPbUChF22NCouykal83KKZVYfv4xF88QfXZFv8qIVb7U
RJ5htrcyjZ//MZXSTmsKIDcEsTIodi8/AiEQujA50GNx9Qz3YuUnVfVH18L6Qv/S
5euXFFHIVOzgS7/dw3ulsxCkBE8IdhjPpDL5eeVdJo+rLmnA5ANmILIk5Q96n5gS
IR33EOlkBt/s4gL/hBoSreqHeOO5C8fWQv04dQ+EqzfheMF6SnjUIwRPM5ERv08=
=ePaw
-----END PGP SIGNATURE-----

--Apple-Mail=_14AE7DBC-6DC9-44D5-B6C8-CC7E2956B764--


From nobody Tue Jul 18 04:42:52 2017
Return-Path: <aaron.falk@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AEAC13178E; Tue, 18 Jul 2017 04:42:45 -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 uEGR7SPKUwW0; Tue, 18 Jul 2017 04:42:43 -0700 (PDT)
Received: from mail-wr0-x244.google.com (mail-wr0-x244.google.com [IPv6:2a00:1450:400c:c0c::244]) (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 4F66A131B13; Tue, 18 Jul 2017 04:42:41 -0700 (PDT)
Received: by mail-wr0-x244.google.com with SMTP id a10so4197812wrd.2; Tue, 18 Jul 2017 04:42:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:subject:date:message-id:mime-version; bh=euxXBC4Layv8UcYKxAqkfC/K9ddO4SvscsPlHTFtzXk=; b=oa/20t+6xUPalJOY0yikk9Ppp/8J31/5d7Zfl8vFddoOSW/L4kLuZX+Vlt9trfubM0 FFsN72dIX8Wmt789Ge9RW7cqas+XRhao1iMxgYAiaZFTf8bNXCSYW0epOUkuMJxjEEmk 5oJsJN3iw0Go2ld/X/VLybXTDly3CCjVVzShlM/8XZnyqrtH/GnVqlet9F/oJ1voBg2l cI5+9Y3uvwe5m3m6zWKdEdMIa1a11NV5+i47gTrCN/4Nqd5MuyWa+jI8v15Qrf0+SfHi mj8FmS4zbU79uOW+3X5Oedxrb2OQahKHEQwkZu8pnu0N7UuHqPLA3hLA7mam0zvTc1Vs /vnA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version; bh=euxXBC4Layv8UcYKxAqkfC/K9ddO4SvscsPlHTFtzXk=; b=mYxrvwONvoT9mQWMZpqJ46epua+3jrGlGQrv6yJwpC8T5FPaJgbkHzH1ZuHQwY2RBp TaX+1Ws7RcyjQcyitmrp3AdhZz/kUjlJde0FIabQLq4ZoUfIlUj5h9xWyUj3u3yvy6oa NzSFQQpmRur7xmt503Y8WEByEem1MLpXDx4uJ0PpqEXwMuN1A+8pI/Y0b0kSJKm6Vgue kxZL6N0KHzirjNmY25n/7w5fWyi+6LE5PWv+JMZAprt1E5M8dbaoJ4viAVhAYTjyXtOt K73gvEJZeD/MZxLRqwloqYOgcwTfFsvGCwU3TGeSmJcVoCR33IujEIpMtWHu0Nm9qhFk 2l1g==
X-Gm-Message-State: AIVw1139GM1ChUAKQbQeCaGQnqY/7K6dY30fN3SoN4NOu3FkjZfkxaBw mx2Bjmz2HteRVVNi0QJnCA==
X-Received: by 10.28.69.72 with SMTP id s69mr1862823wma.117.1500378159583; Tue, 18 Jul 2017 04:42:39 -0700 (PDT)
Received: from [172.19.152.191] ([2001:67c:370:128:6c6f:944a:9e01:5472]) by smtp.gmail.com with ESMTPSA id w96sm1582603wrc.33.2017.07.18.04.42.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Jul 2017 04:42:39 -0700 (PDT)
From: "Aaron Falk" <aaron.falk@gmail.com>
To: ietf@ietf.org, "99attendees@ietf.org" <99attendees@ietf.org>
Subject: Bad Attitude PechaKucha - logistics
Date: Tue, 18 Jul 2017 13:42:38 +0200
Message-ID: <B1B773AE-8B9A-4DFF-8EF7-B0317A84C414@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_E2056CD2-566A-4E97-9E0F-2E193B52F360_="
X-Mailer: MailMate (1.9.6r5356)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3Dg95NJs_6WF_dXfmTzD5SOYdHk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 11:42:45 -0000

--=_MailMate_E2056CD2-566A-4E97-9E0F-2E193B52F360_=
Content-Type: text/plain; format=flowed; markup=markdown

Date: Thursday, July 20, 2017
Start Time: ~21:30
Location: Grand Ballroom
Cash Bar from 2100 - 2300

____

A Pecha Kucha is a lightning-talk presentation format, originating in 
Japan, where a speaker presents 20 image-only slides that are each on 
the screen for 20 seconds and advance automatically.  With each talk 
lasting for 6:40, it has the feature of forcing presentations -- good or 
bad -- to be focused and brief.  This is an unofficial event. Topics are 
encouraged to be a IETF-related and satirical or controversial in some 
way, although not mean-spirited.  Anyone can participate in this social 
event.  Video from the Berlin, Seoul, and Chicago PKs can be found 
[here](http://snaggletooth.akam.ai).
--=_MailMate_E2056CD2-566A-4E97-9E0F-2E193B52F360_=
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">Date: Thursday, July 20, 2017<br>
Start Time: ~21:30<br>
Location: Grand Ballroom<br>
Cash Bar from 2100 - 2300</p>

<hr style=3D"background:#333; background-image:linear-gradient(to right, =
#ccc, #333, #ccc); border:0; height:1px" height=3D"1">

<p dir=3D"auto">A Pecha Kucha is a lightning-talk presentation format, or=
iginating in Japan, where a speaker presents 20 image-only slides that ar=
e each on the screen for 20 seconds and advance automatically.  With each=
 talk lasting for 6:40, it has the feature of forcing presentations -- go=
od or bad -- to be focused and brief.  This is an unofficial event. Topic=
s are encouraged to be a IETF-related and satirical or controversial in s=
ome way, although not mean-spirited.  Anyone can participate in this soci=
al event.  Video from the Berlin, Seoul, and Chicago PKs can be found <a =
href=3D"http://snaggletooth.akam.ai" style=3D"color:#3983C4">here</a>.</p=
>
</div>
</div>
</body>
</html>

--=_MailMate_E2056CD2-566A-4E97-9E0F-2E193B52F360_=--


From nobody Tue Jul 18 04:54:14 2017
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5DE8131838 for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 04:54:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Af3VrLk2RYda for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 04:54:12 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4FE9131828 for <ietf@ietf.org>; Tue, 18 Jul 2017 04:54:11 -0700 (PDT)
Received: from dooku.sandelman.ca (dhcp-8110.meeting.ietf.org [31.133.129.16]) by relay.sandelman.ca (Postfix) with ESMTPS id 4D6331F8EE for <ietf@ietf.org>; Tue, 18 Jul 2017 11:54:10 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id C287E2C66; Tue, 18 Jul 2017 13:54:02 +0200 (CEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
Subject: the terms "priority" and "precedence"
X-Attribution: mcr
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 18 Jul 2017 13:54:02 +0200
Message-ID: <25188.1500378842@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Tu-y0VYJ1vD-r55eB6UpGcA3xTA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 11:54:13 -0000

--=-=-=
Content-Type: text/plain


We have many places in protocols where we want to express some ordering of
pieces of information.  We call these fields priority or precedence or
sometimes other things.  Give encode things as numbers.

DNS's MX record has a "preference", in which lower numbers are better.
BGP has a LOCAL_PREF, in which higher numbers are better.
RAs have PreferenceLevel, in which higher numbers are better.
ROLL has "rank", in which lower numbers mean closer to the root.
OSPF has such numbers, which I forget at the moment.

Is there any consistent usage where preference is a term used when
higher numbers are better and priority when lower numbers are better?
Does the RFC-editor have any suggestions?  Or is it really all random.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [



--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJZbfbaAAoJEJVM4Vb9/EKQ+/kH/3+y5Ey8eWT+W47fnSlHU5LD
RA6wrRkHZh+GqbmvG4vPr7TTHqqUrrQ0uxaWMpQKVwEM3EmwCykF4nBP/EKOKpCJ
2lvlT/L8164F1aJpvwlPva0GVosLaUTu2tlhJvwqruSc90nNx3FAH9KTwNGmz2SG
50q20gllulDtZcsvk3PpUR9vi5gBiRGjHGZv0gaKgZv28IAsE4Ab2JU6sF6PHKRW
txWOkIJs7fuXIYDaWeAGHHGr8B/DJrlSTjmK3zdg734Rs6AN0/nYbwlD5w5Qazdo
+4gxDS4WccOdNBPOhhUJhF4AoiK088AjuAz6HPohRe61m4pJKTJwlzOO0ui5t64=
=rj5u
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Jul 18 05:07:49 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6D5E12EC19 for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 05:07:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level: 
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=MNzukMZc; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=cR/mNb+w
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 iMQ4egUQJKwp for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 05:07:47 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 07C25127599 for <ietf@ietf.org>; Tue, 18 Jul 2017 05:07:46 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.227.84.125]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id v6IC7FP4028493 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Jul 2017 05:07:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1500379647; x=1500466047; bh=5+RsN5aKZCbB7x64rc280T/qg0DmXx1GILJ8JZX33/g=; h=Date:To:From:Subject:In-Reply-To:References; b=MNzukMZcjadsUhzResz4+EKPdBXoX2DOLSsO5mOy7dLw1eLHmM7z8Vsd/5xw/3bnb y18tjeA/T2LpH/lR1dDKaa+ngXwZ/f1zEK0fGutEu3ya/fhXrJW9qTp8/+S2S+qX/j 34cvzOeVAJ2JbuO3XnBWiDkt6w1uJIo8SzUI5sWY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1500379647; x=1500466047; i=@elandsys.com; bh=5+RsN5aKZCbB7x64rc280T/qg0DmXx1GILJ8JZX33/g=; h=Date:To:From:Subject:In-Reply-To:References; b=cR/mNb+wLeIurqOS0aPS1JEu3bnyNOXkrffcA1rdJ900O3+e42V85bgTCtGVsu7KC TZ0ML6MmW2I5kK3DeJj+xP5v9BYwltIgFM7qlfJhK3Z/QkpDukRe+rbFDQbaMzYBKr wzdliKPUKbLRuoV4XakwysnNW43OCvgOX5Pju/tM=
Message-Id: <6.2.5.6.2.20170718041359.0e350668@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 18 Jul 2017 05:02:03 -0700
To: Rich Kulawiec <rsk@gsp.org>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Revamp of the www.ietf.org website
In-Reply-To: <20170718103433.GA13668@gsp.org>
References: <C1590F40-3B9E-45A0-9B87-59A0271B1952@consulintel.es> <20170717153147.D3EA61A6C8@ld9781.wdf.sap.corp> <20170718103433.GA13668@gsp.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ozJlc1Yo5cifNjG1AF9MhNO772g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 12:07:48 -0000

Hi Rich,
At 03:34 18-07-2017, Rich Kulawiec wrote:
>professional use by technical personnel.  Economy and conciseness are
>particularly important to those who don't have the privilege of cheap
>high-speed connectivity and/or the wealth to pay the usurious rates
>charged by some ISPs.  As the IETF seeks increased involvement and
>diversity around the world (a goal I strongly support) I think it's
>critical to ensure that the resources required for participation are
>kept minimal.

I did a quick test[1].  The current web site loads in under 5 seconds 
while the posh version takes around 20 seconds.  I would look at the 
revamp in terms of audience [2] and purpose.  From a UX perspective, 
it would be good if a participant could in one click from the "front 
door" reach the datatracker.

In a non-IETF meeting which I attended recently, there were comments 
about a topic being too technical [3].  Does the posh web site makes 
IETF content less technical and more accessible?

The posh web pages include support for Twitter summary cards [4] and 
Facebook OpenGraph tags [5].  Is that necessary?

Regards,
S. Moonesamy

1. Throttled to "slow ADSL".
2. That is covered in the SOW.
3. I would rate the level as well below the average level of an IETF 
technical discussion.
4. https://dev.twitter.com/cards/types/summary
5. https://developers.facebook.com/docs/sharing/overview 


From nobody Tue Jul 18 10:12:04 2017
Return-Path: <randy_presuhn@alumni.stanford.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 098CA12F257 for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 10:12:04 -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_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, 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 6V48aXtiMjAi for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 10:12:02 -0700 (PDT)
Received: from mail-pf0-f170.google.com (mail-pf0-f170.google.com [209.85.192.170]) (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 CCF8D131B82 for <ietf@ietf.org>; Tue, 18 Jul 2017 10:12:02 -0700 (PDT)
Received: by mail-pf0-f170.google.com with SMTP id s70so5286558pfs.0 for <ietf@ietf.org>; Tue, 18 Jul 2017 10:12:02 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=MDzau8hd4endN6kTITcmRYAQo76h7uxP/l+Ry9tCmWQ=; b=Ov0hVbyrQe83rHkrb4mBd+68An2zxYRRB0z8w/gJ/t0z1bhaEPBdVNwmkXjCO03Wx5 jO84U1TC2p9m4jYLh14e6vYH6bY8V94ssI5kwzfLYNQb5HZoj9EXXqqsEfZ1Z2DdZk5B pS1zh5cjM/606a5LOxYppQg2TkOPPu0D4w+dxyPjQo9LzSFZkHUlWUNRoIlC7+JdLtsi lpDkSc2cBnlIW7GPTz2ApA7twbEFhHiNCACknFzd5VCPCccU7GokHAKLlIEg04Fm7nY0 hHFi5QsYWWJS6v/1JqJAHEojAc4V9DQzOyLspZIKZAeFHaS0nr2y1MYSSWnc/Dz/TRpm 9xkw==
X-Gm-Message-State: AIVw112fJ0ZJx7qomZ7Df1uU8LaDg08Ns66XQI0/BR4q7BjRo/6HuYib pZsqlwtOv8oysoBxG36pew==
X-Received: by 10.99.56.5 with SMTP id f5mr2748780pga.14.1500397922011; Tue, 18 Jul 2017 10:12:02 -0700 (PDT)
Received: from [192.168.1.113] (c-24-130-218-233.hsd1.ca.comcast.net. [24.130.218.233]) by smtp.gmail.com with ESMTPSA id r17sm6178211pfk.73.2017.07.18.10.12.00 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Jul 2017 10:12:01 -0700 (PDT)
Subject: Re: Revamp of the www.ietf.org website
To: IETF Mailing List <ietf@ietf.org>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6394482@GLKXM0002V.GREENLNK.net> <39D1C0A9-DB43-42DD-BD3F-7D636856ECEF@gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE63944B2@GLKXM0002V.GREENLNK.net> <CAPt1N1=Z=ie1pguc1mG9Y-UirNGFMqyE=PFZ3R_408HFOddPHg@mail.gmail.com>
From: Randy Presuhn <randy_presuhn@alumni.stanford.edu>
Message-ID: <9ba7384f-bbb7-f901-de96-b7f1d231a3b5@alumni.stanford.edu>
Date: Tue, 18 Jul 2017 10:12:03 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CAPt1N1=Z=ie1pguc1mG9Y-UirNGFMqyE=PFZ3R_408HFOddPHg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4imygIJl0fQ40SuMW7eb3h0OEtc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 17:12:04 -0000

Hi -

On 7/18/2017 2:39 AM, Ted Lemon wrote:
> The response is not "we don't care about the people who do the work."   
> It is "people who do the work have a really awesome tool to use, the 
> datatracker, so they don't need IETF.org to address their use case."

Then why were *we* asked to even bother looking at this abomination?
If we are *not* the intended audience, and we're not in Prague to
meet with the culprits to elaborate on our feedback, what was the
point of this exercise?  Pfui.

Randy


From nobody Tue Jul 18 10:56:29 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBA34131B9C for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 10:56:27 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 iCGggrmVJ2uT for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 10:56:25 -0700 (PDT)
Received: from mail-pf0-x230.google.com (mail-pf0-x230.google.com [IPv6:2607:f8b0:400e:c00::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 D4296131B6A for <ietf@ietf.org>; Tue, 18 Jul 2017 10:56:25 -0700 (PDT)
Received: by mail-pf0-x230.google.com with SMTP id q85so14906944pfq.1 for <ietf@ietf.org>; Tue, 18 Jul 2017 10:56:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=AbylKX2sZfvOL2neeCpdVOD5IXUZFlNu4cXxFTqZoI8=; b=qJLRxKtFUCAR/xm3VGdjIED+cy5Y9WsLF5Zph5eS7b9R/NIPZYy1PmjeyfCikZ9kE6 c6yk9TA6ntNEhqnq18+Ijogb6FxHotTQ5UUNSyLjOGOdLomTVSFoUd38iZqKx/0HsiJF H4nok7wFAyBmPZVfxvBiv6GC/JolrYwT49q9CDFHdQ4z2kSbfopGuLwF5Hb9XK3UCOYC D1LTqUBhG9w0JsmuR08gz6ia0Tbp4h0cL1rTez1MkTvd6c0UOF8zl0jmg3DynmyEIqkr tsvyjPwTvirPzbMUlzLkXoQUX2rSt/sQUzLcztixNd4K286BY+X1pTCn7Y7z80YD388+ QZVg==
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=AbylKX2sZfvOL2neeCpdVOD5IXUZFlNu4cXxFTqZoI8=; b=e5aG+F0IpZU2EHVwBVai+X57emhqJQzv5G0ZUN2mlNn6hDAe1Fk5IyS419IKhHAQgA NKbDSAFOyTVZ72KQUKOvDkrTLgZcXkKIXl55c/tyX6Y8UbHw+Mk+1E7J80l+FxouWB0B bWNjWI15mrqYJqDoFI8l36ig2kpM3h9iAHZL0ZIPl1dEoSLyoqIKEfMI2N8bubGDLSVL JsHZ0IOhNasPImVO68uGGVGYADMCA2pl5I7lZqAKX6sPo6JCpgAVL9YyWZ6JihYB/hLX wwsNyi1LRcJaw+NmwpoMjFJGpAMpU3JVyLyY/SDkurh5J91QyL8HpKoOAZtMWyk8Rgg6 4boQ==
X-Gm-Message-State: AIVw1116it6XHr7ECUd+R418cj9aGjKDUjbdUyc0vEUPj48zF+Lyoc5U tQXNyyD72X7FHkEIZDqsqh35RhSfmehL
X-Received: by 10.98.10.68 with SMTP id s65mr2937306pfi.55.1500400585295; Tue, 18 Jul 2017 10:56:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.181.42 with HTTP; Tue, 18 Jul 2017 10:55:44 -0700 (PDT)
In-Reply-To: <9ba7384f-bbb7-f901-de96-b7f1d231a3b5@alumni.stanford.edu>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6394482@GLKXM0002V.GREENLNK.net> <39D1C0A9-DB43-42DD-BD3F-7D636856ECEF@gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE63944B2@GLKXM0002V.GREENLNK.net> <CAPt1N1=Z=ie1pguc1mG9Y-UirNGFMqyE=PFZ3R_408HFOddPHg@mail.gmail.com> <9ba7384f-bbb7-f901-de96-b7f1d231a3b5@alumni.stanford.edu>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 18 Jul 2017 19:55:44 +0200
Message-ID: <CAPt1N1=WQ9tNPDQdck5=MMZg3k2Z6o4fofFsxgjxTRPUhgE_2g@mail.gmail.com>
Subject: Re: Revamp of the www.ietf.org website
To: Randy Presuhn <randy_presuhn@alumni.stanford.edu>
Cc: IETF Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a11459fbaeb671b05549b3b58"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/K7QDG0Hv9eDv6sYp12jxfG-s-eo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 17:56:28 -0000

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

You were asked to look at it on the theory that you are internet-literate
and might provide useful feedback.   Which several people seem to have
done!   :)

On Tue, Jul 18, 2017 at 7:12 PM, Randy Presuhn <
randy_presuhn@alumni.stanford.edu> wrote:

> Hi -
>
> On 7/18/2017 2:39 AM, Ted Lemon wrote:
>
>> The response is not "we don't care about the people who do the work."
>>  It is "people who do the work have a really awesome tool to use, the
>> datatracker, so they don't need IETF.org to address their use case."
>>
>
> Then why were *we* asked to even bother looking at this abomination?
> If we are *not* the intended audience, and we're not in Prague to
> meet with the culprits to elaborate on our feedback, what was the
> point of this exercise?  Pfui.
>
> Randy
>
>

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

<div dir=3D"ltr">You were asked to look at it on the theory that you are in=
ternet-literate and might provide useful feedback. =C2=A0 Which several peo=
ple seem to have done! =C2=A0 :)</div><div class=3D"gmail_extra"><br><div c=
lass=3D"gmail_quote">On Tue, Jul 18, 2017 at 7:12 PM, Randy Presuhn <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:randy_presuhn@alumni.stanford.edu" target=
=3D"_blank">randy_presuhn@alumni.stanford.edu</a>&gt;</span> wrote:<br><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">Hi -<span class=3D""><br>
<br>
On 7/18/2017 2:39 AM, Ted Lemon wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The response is not &quot;we don&#39;t care about the people who do the wor=
k.&quot;=C2=A0 =C2=A0It is &quot;people who do the work have a really aweso=
me tool to use, the datatracker, so they don&#39;t need IETF.org to address=
 their use case.&quot;<br>
</blockquote>
<br></span>
Then why were *we* asked to even bother looking at this abomination?<br>
If we are *not* the intended audience, and we&#39;re not in Prague to<br>
meet with the culprits to elaborate on our feedback, what was the<br>
point of this exercise?=C2=A0 Pfui.<span class=3D"HOEnZb"><font color=3D"#8=
88888"><br>
<br>
Randy<br>
<br>
</font></span></blockquote></div><br></div>

--001a11459fbaeb671b05549b3b58--


From nobody Tue Jul 18 11:21:59 2017
Return-Path: <randy_presuhn@alumni.stanford.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6D1813169C for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 11:21:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 E6MZVfEv70Zj for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 11:21:54 -0700 (PDT)
Received: from mail-pg0-f49.google.com (mail-pg0-f49.google.com [74.125.83.49]) (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 9B5CB129AD3 for <ietf@ietf.org>; Tue, 18 Jul 2017 11:21:54 -0700 (PDT)
Received: by mail-pg0-f49.google.com with SMTP id 123so17020862pgj.1 for <ietf@ietf.org>; Tue, 18 Jul 2017 11:21:54 -0700 (PDT)
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 :content-transfer-encoding; bh=1HxDm2Eg9GAjDjNDQucsmFN7yHRDdFnGjsGuijUHIvo=; b=LGiaY7bl4z1tNeQgDkomFiGdPzH8iJWWETgcya2vouk78G8QunYCHAKBRaFdS6EflN LcixGSSOLC2LOmqKPIugxzrHJtV1af4bMU5WFKtYj8qn1RkvLTjoTYtKYTU4b+Fl2j1u SP+0KKDp2B34HxMZFUFLQZ9GWZi5HpHfWAPMVwHBFFLf7Sss2JWK/nuNK+G8RqN5V6/J QdZkMBqMGFmUlLjsRUTj+n+lU9VN5aocewb2xVSGroskKvvTdsRZSrApljs9wmI4Clgt PJrIVbx794oUvRQ9i/d4O+laPUVbm0jIWzdAaOZXwDfhdrQMVTXVSQfJf4EcQYD/pju6 j31Q==
X-Gm-Message-State: AIVw113IHdm6yVTtLFyhsgix24baG3eFv7/grcKZ9Rt/37bChGXFKoFT uVfAFxKMtTQfNYHGbDlAfg==
X-Received: by 10.84.171.197 with SMTP id l63mr3145932plb.167.1500402113854; Tue, 18 Jul 2017 11:21:53 -0700 (PDT)
Received: from [192.168.1.113] (c-24-130-218-233.hsd1.ca.comcast.net. [24.130.218.233]) by smtp.gmail.com with ESMTPSA id 85sm7557161pfr.90.2017.07.18.11.21.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Jul 2017 11:21:53 -0700 (PDT)
Subject: Re: Revamp of the www.ietf.org website
To: Ted Lemon <mellon@fugue.com>
Cc: IETF Mailing List <ietf@ietf.org>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6394482@GLKXM0002V.GREENLNK.net> <39D1C0A9-DB43-42DD-BD3F-7D636856ECEF@gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE63944B2@GLKXM0002V.GREENLNK.net> <CAPt1N1=Z=ie1pguc1mG9Y-UirNGFMqyE=PFZ3R_408HFOddPHg@mail.gmail.com> <9ba7384f-bbb7-f901-de96-b7f1d231a3b5@alumni.stanford.edu> <CAPt1N1=WQ9tNPDQdck5=MMZg3k2Z6o4fofFsxgjxTRPUhgE_2g@mail.gmail.com>
From: Randy Presuhn <randy_presuhn@alumni.stanford.edu>
Message-ID: <336bf300-4649-20bc-8f7a-b1d88283adb7@alumni.stanford.edu>
Date: Tue, 18 Jul 2017 11:21:54 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CAPt1N1=WQ9tNPDQdck5=MMZg3k2Z6o4fofFsxgjxTRPUhgE_2g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_llRGPbfvG0ptrs1UaW17DVaEeA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 18:21:55 -0000

Hi -

On 7/18/2017 10:55 AM, Ted Lemon wrote:
> You were asked to look at it on the theory that you are 
> internet-literate and might provide useful feedback.   Which several 
> people seem to have done!   :)

Since I'm apparently not internet-literate,
and since the feedback I provided (as requested)
to webmaster@ietf.org is apparently not deemed useful,
I'll stop wasting my time with this.

Randy


From nobody Tue Jul 18 11:43:48 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2BB6131B73 for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 11:43:46 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 y9zJREVicgaf for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 11:43:45 -0700 (PDT)
Received: from mail-pf0-x230.google.com (mail-pf0-x230.google.com [IPv6:2607:f8b0:400e:c00::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 5A2D6126DC2 for <ietf@ietf.org>; Tue, 18 Jul 2017 11:43:45 -0700 (PDT)
Received: by mail-pf0-x230.google.com with SMTP id e199so15357032pfh.2 for <ietf@ietf.org>; Tue, 18 Jul 2017 11:43:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=lnlNxfeAO8junh8YWUyDrjxQrtcLs/Ov/C0K4/HL8mU=; b=ZMTFUZutkxiXwXLNZMDcMwhFDjx0CcWWFwsKfKCvKzcjml5JFe8ht9/e4BHhpDueXu OdDfQT1qjxHotUekqJ2qXENdtRs1k5hGaWCxBZHiPC/Vm7AE0f0+vfOJE0wE2j7vYZTK o3e/7JeE3wjD14H/QAfCEkESv/Fk5MonqUK4Z1UQfVDCh1mUYXwRFpgcwEpnTpbR1TVN uVGL7xhl/SXkqnf0IZYjuGG5RHzVXjqJGFxGhgUquIwtFAWy/SOP+OKZIP2uB9jSVX50 XTTCdL4RUqBFXUgw5hJCjHhO4PbVvCDHD9JpOVS3X6Wi4mRocL6rWXI8n+FH8ynBQETR PHhA==
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=lnlNxfeAO8junh8YWUyDrjxQrtcLs/Ov/C0K4/HL8mU=; b=oKaZ8AGkAEDIBBxyO3Ma1MkgiZCxqNg9zfVWI42s8wI1p6sJ6bcyMSY4K20jfXzkAm 5LJsBnzcUs4WMUeXGQWdvl+Di4kEBP+mPyWgQAl8bMWNpizFFPBsEoYp/LUYBPmE0b52 EYV08s2R98HCyYhYpRarw2yIuBlKkx4d2pvcI/UpUa0TOMMc4KQ+dfSlxDLzF7jOZ31M FKfOug3j1znLg1XrB9ex8fJtmechjDw3Q6/c9ge4UhJm8djOYgmGVxghKq5afvF3wIWe CNq7SGV54W150VEIt+Uykak1Ulll6fWznz/1v1cPZ0Nl4rLdZzcmS7vhQOwK+q1ZpvzZ 3dEA==
X-Gm-Message-State: AIVw112krZedkhFpVXjv4SD6bZhehvEeGwJig43xEUuofDLxfGju51WK Vc7aF+z16U2WhDbaC/EC1ErfhVQ7RY4J
X-Received: by 10.84.132.39 with SMTP id 36mr3136425ple.237.1500403424994; Tue, 18 Jul 2017 11:43:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.181.42 with HTTP; Tue, 18 Jul 2017 11:43:04 -0700 (PDT)
In-Reply-To: <336bf300-4649-20bc-8f7a-b1d88283adb7@alumni.stanford.edu>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6394482@GLKXM0002V.GREENLNK.net> <39D1C0A9-DB43-42DD-BD3F-7D636856ECEF@gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE63944B2@GLKXM0002V.GREENLNK.net> <CAPt1N1=Z=ie1pguc1mG9Y-UirNGFMqyE=PFZ3R_408HFOddPHg@mail.gmail.com> <9ba7384f-bbb7-f901-de96-b7f1d231a3b5@alumni.stanford.edu> <CAPt1N1=WQ9tNPDQdck5=MMZg3k2Z6o4fofFsxgjxTRPUhgE_2g@mail.gmail.com> <336bf300-4649-20bc-8f7a-b1d88283adb7@alumni.stanford.edu>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 18 Jul 2017 20:43:04 +0200
Message-ID: <CAPt1N1mYyZOd5cXnOB-0H4Ozybjk=vRrjXBdPzo2xderrJ41AA@mail.gmail.com>
Subject: Re: Revamp of the www.ietf.org website
To: Randy Presuhn <randy_presuhn@alumni.stanford.edu>
Cc: IETF Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c12f7142ab92f05549be58b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/en3kKJjKlDsfjP6vx8ye3YoNK-A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 18:43:47 -0000

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

Why do you think it wasn't useful?

On Tue, Jul 18, 2017 at 8:21 PM, Randy Presuhn <
randy_presuhn@alumni.stanford.edu> wrote:

> Hi -
>
> On 7/18/2017 10:55 AM, Ted Lemon wrote:
>
>> You were asked to look at it on the theory that you are internet-literate
>> and might provide useful feedback.   Which several people seem to have
>> done!   :)
>>
>
> Since I'm apparently not internet-literate,
> and since the feedback I provided (as requested)
> to webmaster@ietf.org is apparently not deemed useful,
> I'll stop wasting my time with this.
>
> Randy
>

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

<div dir=3D"ltr">Why do you think it wasn&#39;t useful?</div><div class=3D"=
gmail_extra"><br><div class=3D"gmail_quote">On Tue, Jul 18, 2017 at 8:21 PM=
, Randy Presuhn <span dir=3D"ltr">&lt;<a href=3D"mailto:randy_presuhn@alumn=
i.stanford.edu" target=3D"_blank">randy_presuhn@alumni.stanford.edu</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">Hi -<span class=3D""><br>
<br>
On 7/18/2017 10:55 AM, Ted Lemon wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
You were asked to look at it on the theory that you are internet-literate a=
nd might provide useful feedback.=C2=A0 =C2=A0Which several people seem to =
have done!=C2=A0 =C2=A0:)<br>
</blockquote>
<br></span>
Since I&#39;m apparently not internet-literate,<br>
and since the feedback I provided (as requested)<br>
to <a href=3D"mailto:webmaster@ietf.org" target=3D"_blank">webmaster@ietf.o=
rg</a> is apparently not deemed useful,<br>
I&#39;ll stop wasting my time with this.<span class=3D"HOEnZb"><font color=
=3D"#888888"><br>
<br>
Randy<br>
</font></span></blockquote></div><br></div>

--94eb2c12f7142ab92f05549be58b--


From nobody Tue Jul 18 13:53:54 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82E911317A1 for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 13:53:52 -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 Wk-FlK8FmGNP for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 13:53:50 -0700 (PDT)
Received: from mail-pf0-x22c.google.com (mail-pf0-x22c.google.com [IPv6:2607:f8b0:400e:c00::22c]) (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 CC4A9131798 for <ietf@ietf.org>; Tue, 18 Jul 2017 13:53:50 -0700 (PDT)
Received: by mail-pf0-x22c.google.com with SMTP id o88so10426586pfk.3 for <ietf@ietf.org>; Tue, 18 Jul 2017 13:53:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=Ogjb2YLUMUV+hh6S5NCKNVOJWNrL+3Eg61AaHljcMHA=; b=HuQ0XwhGqUDsqOPhDHw+XPDWN+/lvZMkmvX9/cbhrEaAo4giZUQ5NxmJ1DYxL6CRbN gzprlCXpBYXFH1a81BfoTYbjRAPuGMnLsFd8munxOhMr/SteOHRMgfW2vfk8VnQSE8Dv 5LNj+M9+3bIlTElsQ+vBSzkSfo4d80Vkz/Ei9l+HutEmUmDi97IUz8FccLz6SMpcQz0s ctCD52xp3R/reSZ3oUjBqI75iP+Z89SmTeXLrg1Ob6X1KY0u8v/EPxpF1yJ3CFLKsfQG rnsag6z9rA4Zs1m3G0NbUPmO7F/fJb8HmTjEvTfzKEI6g5xzBhYGWsJGS8W+9vzxFsiY 8IqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=Ogjb2YLUMUV+hh6S5NCKNVOJWNrL+3Eg61AaHljcMHA=; b=EiAA013oWirtMeQrxlW0QeMNiX2MX7N8M7onq3r+oVfkgj+weYbCVt5jfRwjFCCiPu WlcVqc6e8GhjHj1f6fGWEvrkfuN1pyEmU62SJEjbtoepKWACqRh3uij5Ng2GLqeOiOVg 8lVZXjKSlWmIe8RgjcUfXQZiAG3u6ZiNgmjdS9c+piLLgI76o0r20Py+vcKYDZa+Z6Cc +JPdEMCu7P/AaGFsBwlDUl7xHX3LejL+eoamTQkzj6RfIOpmnvTi/RPB9NbRd81aocmV WPGFG53k8g8j5v8Bx46N3JAvc/ymlvBjXt1yFkg7M4xEOUQaP1ne2gz82yU5iuvHRQjD p7iA==
X-Gm-Message-State: AIVw112Ly7Cbos8FBg8BYq1Bv2uXsKXVzw7P7arMwW0B89KIbTE5Pv7Y NrFFwxy8A39LAugb
X-Received: by 10.84.129.12 with SMTP id 12mr3765900plb.242.1500411230215; Tue, 18 Jul 2017 13:53:50 -0700 (PDT)
Received: from ?IPv6:2406:e001:3dad:1:28cc:dc4c:9703:6781? ([2406:e001:3dad:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id h123sm5581914pgc.36.2017.07.18.13.53.48 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Jul 2017 13:53:49 -0700 (PDT)
Subject: Re: the terms "priority" and "precedence"
To: ietf@ietf.org
References: <25188.1500378842@dooku.sandelman.ca>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <3d294725-7d22-ef24-7c57-120d9418acc7@gmail.com>
Date: Wed, 19 Jul 2017 08:53:49 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <25188.1500378842@dooku.sandelman.ca>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/a2Mdm0gTEVobnCH6qCfz_T5cN_0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 20:53:52 -0000

On 18/07/2017 23:54, Michael Richardson wrote:
> 
> We have many places in protocols where we want to express some ordering of
> pieces of information.  We call these fields priority or precedence or

Just a side note: in the design of diffserv we paid a lot of attention
to that choice of words. You might care to read section 4.2.1 of RFC2474,
which could be summarised as precedence != priority. I think there is
quite some subtlety in this area, and not so much randomness in the choices.

   Brian

> sometimes other things.  Give encode things as numbers.
> 
> DNS's MX record has a "preference", in which lower numbers are better.
> BGP has a LOCAL_PREF, in which higher numbers are better.
> RAs have PreferenceLevel, in which higher numbers are better.
> ROLL has "rank", in which lower numbers mean closer to the root.
> OSPF has such numbers, which I forget at the moment.
> 
> Is there any consistent usage where preference is a term used when
> higher numbers are better and priority when lower numbers are better?
> Does the RFC-editor have any suggestions?  Or is it really all random.
> 
> --
> ]               Never tell me the odds!                 | ipv6 mesh networks [
> ]   Michael Richardson, Sandelman Software Works        | network architect  [
> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [
> 
> 
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
> 
> 
> 


From nobody Tue Jul 18 14:42:13 2017
Return-Path: <erosen@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ED29131B06 for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 14:42:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.802
X-Spam-Level: 
X-Spam-Status: No, score=-4.802 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=juniper.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 KZXw1vgXsB5v for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 14:42:09 -0700 (PDT)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0125.outbound.protection.outlook.com [104.47.36.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBE34131B05 for <ietf@ietf.org>; Tue, 18 Jul 2017 14:42:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ttfiB278tyUYvn+2+zEWcJZ+SVIPXnJ4363kBg2DEcY=; b=iWLOejhb/F3JN3H/+Uewpq3rSa2uwPacjzz94CvNxpXU0jPUaizrnhFlZztRpbfSl/SjAXTeCXsyUKjp+WSqEP+xuAVvBgILyErZja+ReBVDhg51jhbBu9GJvlYXIOZ6bQlpuj5Yquss5+B4PwHSQZXt0Mm2JUQAjAg2+T8vaAY=
Authentication-Results: juniper.net; dkim=none (message not signed) header.d=none;juniper.net; dmarc=none action=none header.from=juniper.net;
Received: from [172.29.32.91] (66.129.241.14) by BY2PR05MB2182.namprd05.prod.outlook.com (10.166.112.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1282.4; Tue, 18 Jul 2017 21:42:06 +0000
Subject: Re: Revamp of the www.ietf.org website
To: Russ Housley <housley@vigilsec.com>, IETF <ietf@ietf.org>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com>
From: Eric C Rosen <erosen@juniper.net>
Message-ID: <2a017f34-6ed6-f60f-d5a8-74d944bc40e1@juniper.net>
Date: Tue, 18 Jul 2017 17:41:56 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-Originating-IP: [66.129.241.14]
X-ClientProxiedBy: DM5PR21CA0012.namprd21.prod.outlook.com (10.173.176.150) To BY2PR05MB2182.namprd05.prod.outlook.com (10.166.112.10)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 471d3318-5543-40a2-34cd-08d4ce25d654
X-MS-Office365-Filtering-HT: Tenant
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(300000503095)(300135400095)(48565401081)(201703131423075)(201703031133081)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:BY2PR05MB2182; 
X-Microsoft-Exchange-Diagnostics: 1; BY2PR05MB2182; 3:ihoVVNkYQbItQ7pZoK6mK/P2iTiN/iAut79OpsD82xbTTQ7cSHCz8wAMCMSolRhzDyCs6DFqYOP56kIM7O50LWOyntvzsuCkqncEfS8xy+FXQqKUHtJKjROahou2SWN6w+VKdRtiWSRCbIfpMIR56W3w4vtrxsO3n3XQZBrL6+4mIOMCz4vcPsQ9wyxYWDG8V56mNkQ6sOTMDDBQTwe4xtDDzjfkU0uaoT4YBsGqlxYrEzoZXkhIQMatjJ9Etq8wJV695cZPQTUwGDvSUrHg4kmbZFqKVORzSEICjGLmSbOAwXWoFNw9Tqm0ojktfj9BxYd0c7ccnnUvP7gtczsrt1oLCYgczSWwBMvaI7rQ6riqDukoMN9CESfp/00sXlzM4FWYA+t/HUSOEWtNBVHkOLDpEntRS+toHW1QucaGbOXAYx6OV0X6DWIUyUPOfaVjYc9+KnI3lee8yo+TMgA3uljzrfNnghTSaLcjY8BLEMMN9/007bXUNdzOVvXd2p8WpVyEHU1NZ9GlxHar6E9xzAtk2XZfesS/8PS+IFVrbT0E/xYjRAWe70DLzt/BvuoJqV/RMXvQy2PFsPrcVj0ASIX+lFvfXF+pmBLrBoP7F8+6Ptgf2+Xhe7lIkJMMpuzUYqKGv5fr45nl//fh0UJ39FAvvLF9yQM3ALXUBYza6Vx7KMrQw9eeLWqIuNXXYifjSyKsHbY5TJo7HWVktwxAR/e+Q1FnNUCSgfD5Ri4tUPKurh9B8cuszDk4WxvP3EK7ptAuGARlWrkbjNUPai7dBA==
X-MS-TrafficTypeDiagnostic: BY2PR05MB2182:
X-Microsoft-Exchange-Diagnostics: 1; BY2PR05MB2182; 25:IyywIiCU5mKixxPHMFB7V3x7jMrXB2r1z4bzict4oqI0M1G0DQ5jN6Cw+Q9zzGJYlRvpTY69qcKoc92LEkPzWBg9GspKDIMVt3CWkkL95ycY5yW2UPEdR8lhUmrx+8Q+z8dsisb2KM87mGp/ziDC+s2YBYmnBgEQNUga2TpKsDkX+snr7uWaQEkzfKEa923BpAkAj97DswvcXjoTsZe/AHoOLT95NmeqLEGxxK7d/lUPcgVjwnR+W90T6WMxW9mFHhSV36Iq/0xsC6rwjj62pBXv8fVZCwNH3/ICGWzqic0u8Rm1VsxOFJ5D9MGGNjAZiWzjWHY4X/jcpjNKxam80uTvedMfTKRUyXysrVhqxP75j/InN06ew4UoOP8/l9Va3mZHJ6xVdi0itoG4PpQ1HrqCe27JBniUJKgnMsxPAL2qJkMTQomxbJ5Devbk7LaEVtJNrU4C7HeRBNTEr++y+nf8C8Z4SuMVOQB/Ad5C7psawsYwgK+0c2c+ZSIInAankNj+UFcOy3Qh87h/Yy3DIKI4rgIpgezCV3ipVprZQKzxPiV1cbsfv3+KasOJnqEzZfRgyc0Yo04Z8/+OVWG3V4mF/+Dr0j63/wKGSdnZCRR4QyFdQJShpganwW03AG842q9nWg+y8JFCrKBJvEYlayB6pwzS2QNwRIKRPCGvQHWjzJRfugTov0CX8hCLi50D1iRyC3RKlWUEPi3Gvgs8BrzMzl6VF/mouk+oYIq9H8k83R2+DxC8A+xeYGEL7pt4Aoei9bRzYsCJWwQKamcYlIUIoOmLvebv4oxHR7BmVZoEfqZPQpCPhupSyg5Tu58YicUEuUeUpNzojsW838BUgH50S04rQRqE1wYN5QBiIUY+af62VKu7+zbKMH19sNYblNrgEmZbnwA3vvDUfOLnOPosuvoN/9DA5isCvQ+wS+Q=
X-Microsoft-Exchange-Diagnostics: 1; BY2PR05MB2182; 31:ED6t6UO+CK8cV1s2d7tjhRJ2Z/xOQ9aMQggLfwPf8c38bW12L2Sta8o1uBIdEX6BowfiyCaY8i6fiOte/xa41ovMTG7s2/nHXpeGltaklMpEhUnRsSDx/gqnxb1P58cf4v9IN2Zm/YzNyl6NgEjUt/4JyoYBjly3iCu0lRCObbNtyqME1y0R+7/Yi9cPlNXQPFBoIrQ+yVFqG5qJKyPo1DEWqHzSfIOidCos09Fm6KpuBEdYmKF4wq1Q5uVt9ogQ/LKF2Vs7tvq2mHZhbQCqxhF7pq2Hj6L4YTM5dlpKogVwJZvZ6nRtOGVIW1gNkPwyiS3mePH5jEwJ0ONxU2lZsj/XxMFe1KGbaUtIhFLC5Rn9oHHO9VMss2DEKxe5n+QDoNlIlkjRkNPZxXg8euIEqxhA3c5j/ngus7/w1LX5D2PGHHWFTbOByIp7lLzqQVVmP5wJg+7yh3+WVCxeMEhHB6vzbYhr4tL/c0gVuVy2bJ5YTQ5ultEq6NQfzsCR2ekYAay9ZjdF8/HyXH6PtGN2lGRerNoqxVo2hDCG8Pc8NChE7YVmtvJTaksKJEeYpd1VukUq8IpgwmFfeHOb9uCK3s4xsQmWcbtE9l85kUy3DgijijxdiIfzDJ6dC94QeHGB+z0XZeQqnQviyXy1mp1BhjGibw/1Un7+xYqmQGST/ko=
X-Microsoft-Exchange-Diagnostics: 1; BY2PR05MB2182; 20:0Hb+gfd6j3sh5jJcB1NWlSzgxwVB1A74tYc+5Bwos5vcKDt23Ok1b8p+9M2RnMEVCle8yc4yvWNliW4MilXKrdhtSBX4GpRdAW12l0DMxqGYg5EhM4YO6qWvU/5cowQGQEjv4+OeNVxLowvUKfesczlWYsDAdn4KnqIyvyRbp/TgoMzGC+gVBcRXjUqIQqSe8THn/AtJQAWuT2Ryay/pNnOEL2EAlMHM3EYTb6onMotOEfuOyeoVCdKABL7bbC3YVciT0ekrPastgy7fjk7ZbmeN/R9hjezcsR7J5rWldqKP87HMU8tvVIqpYMD1U47feILdbEi41ut8ggyUb3gcxrtadsCFNTjOrngnbqs3m5hVZ8Prb0AEylrMyPOPnGP1+pQnd00wTPp+H/u130DSa8PP68NS3GvmbXFibWx7FMlcuzH86HASp6P7VMnq2C7xBmLOQvkP+uykiALTFATXafoC/U+pco0jKEchyPsdh9ZQ0rIozrAnOTy5Rm7ASQaTGJ6T6Xno9Vzt/d2U0NTdn7lHUa/OFkRSunkskgbOUAd6tiChygMBWl/6GYk8xi5S55y+XziNcn+siVAlVVm027HwX/m7kZX0hvZw+W8G4rQ=
X-Exchange-Antispam-Report-Test: UriScan:(236129657087228)(788757137089)(148574349560750); 
X-Microsoft-Antispam-PRVS: <BY2PR05MB2182D3A9F7767D4D549E1987D4A10@BY2PR05MB2182.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(5005006)(8121501046)(2017060910075)(10201501046)(93006095)(93001095)(100000703101)(100105400095)(3002001)(6055026)(6041248)(20161123564025)(20161123555025)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(20161123560025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BY2PR05MB2182; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BY2PR05MB2182; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtCWTJQUjA1TUIyMTgyOzQ6NTVPSU5OTTBaOUVUZnFMRGdtSHM2QUVEdjYw?= =?utf-8?B?bWR3VXpYbSttb0t6TjZwK2JsQkFBMjR4bi96SUlWY2FRdUhrZjdiQ0JRaHl3?= =?utf-8?B?TlNkMGtmdTZkSXhmd3ZmM1pIdGR1dURweVdlRDVsTmNycXQxRzc4cFRWWDc4?= =?utf-8?B?S3NyckxPVWVxR0pVdlFBY1JkczFGRWxWZm9EQ3RNWVJsdzdtWVdIVHdvME9o?= =?utf-8?B?Uk1xYlBZV1d3dm5IcnBHeFNXYnVpQWlmMDVuUkROd2RuVnlpZlRGMjU3Ri9v?= =?utf-8?B?Y20zeUpRc1JCUjQ0UXJRR05BcWcxYkV2L3NtdXpmMnJvZFIxK3RSb0ViTG9F?= =?utf-8?B?dW5IT0R1cHdudC9SWkhiVlpGSDBLYjFiU2pKemVkL29Hek9uYXVLTXhMbmVn?= =?utf-8?B?OVlCdEhtSEhjN08yYVFLQnRKbmJVWC9ESmV0OU5VMGtTYkFTUHJ4c3BMMWlM?= =?utf-8?B?WkdJc01PM2hOWk1pdFNENDg5dGVneVp2WmxKaGZOUXYwNXdpMk1qaEZFTXly?= =?utf-8?B?NGV5eVQ2WEJIUldnVG0rVHJxTCtxeTZmRXBlQlNJZWhWeCtFMUxiV21QMFFr?= =?utf-8?B?Z09RMDdiS3MyN0w4b04zNVpYdlcvajZId25taDRmR2lCM3htU0ViQnpQS0lt?= =?utf-8?B?OU5zVzRyNW9QeGIyckFmbWVUdlFZd1IzcXBWbXZkM3pKbkFhTVBTbjR1R3Ev?= =?utf-8?B?VFJ6MlBhLzUzQk52OXNUMUZHSTM1WFN4YlhUR0Y4VjFqWVpMM1NuVklrZUpj?= =?utf-8?B?M2F6d25BTGNGWVZjWXl1MUN0UmhsUzB4dmM0RjhMUHVzamFmSzAvUFFWeVh2?= =?utf-8?B?bTh1UG5VVG1ZWjdQV1NZTDBDQVplT3lwa3VMWlRDL0V0WjV4Z1UzdE5nd21u?= =?utf-8?B?NkRVV1ZxTGtYV1Y0MHZMUUNPblplUHZQZ3ozczdidSt2cDN2Z0FPa3l6Kzl2?= =?utf-8?B?b2VBZDFKb1ZndlRaRDJKS3gxOEwzNmI1RFMzQ3h4VlNaTFExY3hvOU1JY3hS?= =?utf-8?B?MlVrQUpBeFlGSFk3NVdqc2Mwcy9kaWVHZTRaOU9Pd0lPVlpLQmM1cXpBR2tY?= =?utf-8?B?eTRCbTlFRm84MDQvQkdmTnRIV3Y4SElDc1A0TFBETzZ0bitVNnlGcUtKaGRw?= =?utf-8?B?cFlZY3owbkhNZzRLcnYzT0tpdnNvdGRndGRzaGZqS0xLMk5wQlk4MlVxZGIy?= =?utf-8?B?NGxiSlVGRFNLaEIxQmUrSlVIcjhZVkdXNCtGc3c5YldEb0s0SmdIY01VTlRL?= =?utf-8?B?a3I0VDdXV2t4WnpTQkJPUFY5Wit6OTZ2enFSQ0hna09VbXhsSnlTTFZJeTh0?= =?utf-8?B?V0pZSnR1ZDdSRU1XS0ZIV1orNmJsMWRuVmpRZkNKZDl4dHlVQ2FIS3BuTTlQ?= =?utf-8?B?eVVDVHkxYTdqeHdYSlV1cjFXeEhuWFBTemFuUnRTa2pIR0lvSzRJSmVqc0Jo?= =?utf-8?B?OUtoL2ZiVTgzbjBjeGZpbUVBOW43bm8yNEYzWVBSMkwxZWZFdlM3WlFHdXZY?= =?utf-8?B?aVZRRnlhNG9GblNDa0ZvWjJaN2NYY1VtUXRYSHJtNEtkMVRaekJWTDF5TTlV?= =?utf-8?B?TTB6ZzcwOCtxWGVmRjVqeVJuVjk2VE5seGNOQVVab21ZOGdzaEMyNUlWcTU4?= =?utf-8?B?VXRTRkxuQ0FEZHRKcTRmSXlPTFh1dTUyeSs5KzZkOHNsODI2WHplVXl0UmJP?= =?utf-8?B?TzdocXl6dDdjZDh1V3FIODVzZzNxM1BzZzJyQ0k3LzY3ZDRpbzlqQ3JlM1ZY?= =?utf-8?Q?VgP/pvE6VDyjz0Af69S1yGpIDz8SshCDTaLM=3D?=
X-Forefront-PRVS: 037291602B
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(7370300001)(4630300001)(6009001)(6049001)(39410400002)(39850400002)(39450400003)(39400400002)(39860400002)(39840400002)(377454003)(24454002)(33646002)(65826007)(47776003)(5660300001)(50986999)(478600001)(76176999)(54356999)(230700001)(6246003)(77096006)(36756003)(6486002)(65806001)(66066001)(38730400002)(53936002)(7350300001)(3846002)(7736002)(53546010)(6116002)(305945005)(83506001)(2906002)(23676002)(3260700006)(31696002)(8676002)(86362001)(81166006)(25786009)(4001350100001)(189998001)(2950100002)(42186005)(64126003)(229853002)(6666003)(31686004)(90366009)(50466002)(163123001); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR05MB2182; H:[172.29.32.91]; FPR:; SPF:None; MLV:sfv; LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtCWTJQUjA1TUIyMTgyOzIzOnQ4WndWZjN0MlpjVUNVeVVhcjdocmlOb2VU?= =?utf-8?B?TWo1ZWhEc05sV25VODZaSXRibHpkNzE3SE01U1d1MkZ3RHNOUUZHOEU2SFIy?= =?utf-8?B?dUk3V0s3WjlWTTJnRkhqQjVBT3VwYUJkVzhncFVBNkVFcVVXd1dKckZHRjYy?= =?utf-8?B?L3d3TS9XcC9Canoranp5SFExMzNaNjZ5VU1uTTJlTGRCU09VaHV5Vm5WRENL?= =?utf-8?B?MUZhVGIzUVduTlVKZEhFOHhaVUsxWXlsVmZnS2xqRTlydzZDRkMzakE2NDFG?= =?utf-8?B?a1gzZ2RCeE5NMmxoWFhXNkJWVnhWV3k1OEg5NHVpT1dEdFFPdDlWK2ZKSnov?= =?utf-8?B?azZxd2c1elVqbkpCQXQ4KytxV2x3SEdCTEpoU2ZUWHo4OHIrVldubmlwalZq?= =?utf-8?B?d3ZWK1FUZGJmUDBnbWUzWDdmUytTb1B6ekdFcWQxaDg4b2cyYWVCMEc0QmRM?= =?utf-8?B?M3Rwb2I1YnJxUS9VcEVDQ2kzZUVqcmZQdHh1di9zQWVvUWYvM1lna1l3b1pF?= =?utf-8?B?Q3lqUFl6b1NWTHgzTXgyTXA1b0pGeEhBZVVrcWxMdjZWSjdFandFWWMwNkE0?= =?utf-8?B?UEFheEswUldId0NQdzY4R21IdmllNjN0SitWdzZCQ0NrZ05Ub3JYWWd0Y1hE?= =?utf-8?B?MjJUVHd0U2lHU0Q2Z2RPSkpTVVgvMlpXd09vTm1oamtJMGVCb3E2czdsRVA2?= =?utf-8?B?TlRCWGNWYVhaREU5eE53STEyVW5jN0tlczQzT1ZUUVVVYisvYUpvZE5MdGEz?= =?utf-8?B?VE5NbGNZeDZ6QkhwclRhVHlKS0lhd0dDUkVUNFZ0WitncWpRbTFGVFBDci9Q?= =?utf-8?B?UTM5aTNHL01Tc2lnck1KUXI0eHVwYjI5eXFYd0svRWlFL1JHZEFqWVQrS0tW?= =?utf-8?B?ZksyU2d4R3lIUDU0cFg4aVEzZW1HektveEJhRHV3ZHM0KzhKYWMzcGxCWjBU?= =?utf-8?B?YlJTVWFMUVlXWDNVL0wzVmY3YjFqRk9yTDdNQUtQNWJkUVNyeEw2YU94R3pF?= =?utf-8?B?alJ3NUlPQ1pNa25LQVcwUXQ4eDJjQkYvRnBjczM1VFZIMEJmVGVvQWw0TVNv?= =?utf-8?B?WllST3NNTjdsOEovcnNqVEh3UlcvL2lLVkJlN2liUTA1V0hFOFpGSXhzeXdm?= =?utf-8?B?RHhWTzEyd1lPTjRiTEI5NWxISXdDYnFJNk9MMTlITm1oV0hwa3Y3MlNsWXhM?= =?utf-8?B?bkJ3SmdVMHF5cmJrSC9WZ0RldFQvampLcDNFUnNFdU5WQlhxRURVUmlETVd5?= =?utf-8?B?Rmo1STg3OGhuNnk4TytYWUZ4a2ZDWjRaL2NmVGwzMER2UkYzVHZXcmRETktY?= =?utf-8?B?ZHFzRzJGdFNtQUx4WVh5OHM5SU1kUHA3d1ZSQzA4OU8yc0k0ZW1kZWlEQ3Nm?= =?utf-8?B?WFhtZ3IwUTBSMUJjM21rbU40bTlEQVQ4MnoxN2FKVlRtWUFndDhvN3ZQbWtX?= =?utf-8?B?WEltaDJLNXZyU3J3VHZBMlRJYys0WTd1Z2JKY21HSnpYSlBjaWR2T3hiSGRP?= =?utf-8?B?b2Z6cXp5eWdFcTEvUmtSdmVFYnAzTFRIUkluN2RSS2w4Y05sWlVwSE9NZUpD?= =?utf-8?B?VmI3aGwrdnBCbm1Bd1g4cG9DYk9KR2puMUpPdUROQ3Y1RzFzV0lwS3ZhUU9y?= =?utf-8?B?QkpZT1kyNDgyZkRlbUxlb0U2SVFtdUlRL2hTT1BrT1dPWkNKV2RyMmRuOXR4?= =?utf-8?B?b0s2Z1FGZ0FIaEI5a2VQSHJwWXdzcmxMVWx1R3UwTzJHR25FUGh5WWFVTmdW?= =?utf-8?B?WjEvOWJ4Sk9VNFgxcE9oRVhhL2VhazFTQU5lU3Y3ZzlVVlRjcGhsclFubjRa?= =?utf-8?B?NkEyNnU3WFRvekVOTDB2TlJqS1p0cCtwSWg0QVo5L2g0Z2hrUURTdkVNeWVh?= =?utf-8?Q?Z6DYpJsjeE4=3D?=
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtCWTJQUjA1TUIyMTgyOzY6UkovVjdLYi9hdHRINUhYdFVseDdSNUpJY2pR?= =?utf-8?B?Y3hYQ09YTldUTXl2N3FUSmJNU2hmMHhwcDRNODJiV0FlMDhic2kyMzhUdHZI?= =?utf-8?B?cEZOcWtFaFhhV2s2WHM0a3pTYllaajFWVTNScXNhWXhYMnN0UXFNbVlTMUFq?= =?utf-8?B?M21KSHgzN3JISGF4emNVZG4ycjVCY1JKNnVUNllFc04waCtOYWhGc0I1Ymc1?= =?utf-8?B?MGYreHBSdzFrclU5ZFhuN21XNGF2VHJOdGlvQnpvLytVQ3A5WVBOczIrZGFO?= =?utf-8?B?QnVUWEFCQ0pjKzRsWTZzL3YxUGFKR2xLbkdsNlVPU2JTdlMwWm5hakZpQnBt?= =?utf-8?B?N1NFVWtlb2c5ampvWkU0M1F3NnJTT05Na3c4eS9adGdJSmFqRWlpZjZCWEQ4?= =?utf-8?B?TXNkdnVsRHdjajJKQ3lvQWl2RGJ4eEJlaG1UaXBmMHJORFZXN1JmOEJjZ3p4?= =?utf-8?B?eWZoTWZ6MGZvWFVQNW04WjlRSnZXTzdsTCtBV2pSTmNPWGtVM0xDOHF2M3Jp?= =?utf-8?B?VnJiNTNnbTUwdnF1dXJKUFNnUUZDb1R0dG5NQ0Vnb1dCalNHdFZZQnlmc1BU?= =?utf-8?B?MVlSaVRVdGF6NkFyenlKVlI5UTIzdTRlZmovanVkMjdlTkFRY2M1MGpHb1g4?= =?utf-8?B?NTBSUVl4M1Q2S1RjcmVrUHkyNUtKT2t2L1dmVXpaUHRMY1JKYUZ4dTBoWmVx?= =?utf-8?B?dHdtOUVsWEY2czJFejc2RmkxLy9tZmYvZ2ZENlBHWjQ1Z2lsS1lsWFNXQmlZ?= =?utf-8?B?NnVYeEY3ZjZ4NGpxaVNzaDdYNHpRVm1sMFg3U2RwTlo1cml5Q1d6ZHkwK1Rj?= =?utf-8?B?czdCMFR4NnpFeTA5dmdzSUlkWm1xbGJ6ejNYK2ZHZ0NyUkhRcG5Razh6a0RM?= =?utf-8?B?cXR4c3plbklDWEdudGR1aFBIRHhNWVphaWhYV3JIaWJaWmdrZFUxUEVQZmRR?= =?utf-8?B?RWU5SHVUU1ZBYnY2M24yN0NQNFE1b0tvY004ZWJyR1lSZnRiNFpzSTczb3ZU?= =?utf-8?B?VUE3UUorZzBJRGpjQ0dYek96Y2dJdUg4NDYxTTk4R1V6NGpHc2d1WTU0Y2Ri?= =?utf-8?B?RTNVcTlWR0NRNFdzM25MNy94ZDRJR1M1RUV3V1NtZlBOMWd3UWtUZzBFSjhO?= =?utf-8?B?cmVRSlI0RS9KNTB2b2NKMmdydEtSYTVjMExSNGY4QldmbXU4YmlRV2Rtak1L?= =?utf-8?B?TFBGS25yN2tzNnUrMlFycjBCSDlOdi8yQWcwUW5DUkMzMXFwNkx5bG51RHRj?= =?utf-8?B?YnVod203RGMwbVRNcUx1ak1wbmNTSnFDNDlzNjYrdHlXMHpwRlhMUnNIS2Fy?= =?utf-8?B?QzNzcGFMdGRONWgyc1BGcEt4dmVUWmhhZ2cyUytXemJqZUZ5TVdoRjVKdkRl?= =?utf-8?Q?U8/F+Y8?=
X-Microsoft-Exchange-Diagnostics: 1; BY2PR05MB2182; 5:AoeqtyeKD98nmdRrmM6rBasm7AUS+lrk1ilt/rN+HEWhr3H2IQG1TyCKOQtzEE32ErzC8dEV+t2wrmmBnm41ApG60vUZIp4HoLEqAdQOn336GWRDogawf4a5IFdWOdsKyM1Vs8bug7GRoSxSSxG76JIxxiKudgwOLG20+VhQYIvPpS3LFModtTr8XAu/hku3SkSBbQMZOkU5Cf+cFcysCn8KBpI1ds1ueiBLfi1MDtngKiyPW+8jM8trvx+6wO+eCwlkktc6YZCrA5NHGoNJR3PWaNPD2GQEWifhQenjB3lPDaSF9aFMdDkPANVv+vV0TSZzYbCY6HK+RwOfdkjRWf/MjDen3nS9IAX6a/V86gXSTKFDFKobzU6P9SNkH95NIrya1kLasAgnv6AifJqsqILLQPaED/iTF20G/ZJrlr2pAWT+zdJcDtC/MKRzwHHGoQziti0LnklY+6Pst/UtLQiNeQF5Ibmvx6ndFKI0D2ZtcGNAM2goPtRDZ1zkTxfM; 24:ELFAyxFdKm2csqY0YFULLPPHYCqrkXuj37XUdFwPTel8c5GofPst1kY6qmwQvDsiVNIFE8JmO/Rx7IUavawNneOiuI3G3lNzPid0xadY4S4=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; BY2PR05MB2182; 7:B74WJg8ef/nUEqGUEhk+jBinxU9Pp/+2Mc0USZy7NESnbw2o5e+0oKlt6ko2F+RTX5Bp9ZmPZs/yqXDXoXh55PcNjx2RkuLS7c1WrwdgOv09xcok/K5sLCA8osuM6tfnLrck2Mz70I80CoyNd/8XeKN2jvnuka8mp4KXEfzBE6U0JcUXjvtsAL+7lKLm+xC08EaUhUpg1jP8k+F9UlL4ZWoFP0d4A5yKkXb1J/c3/WxNKKikzhjwxNgQsecLFEfUf5ycq2C5QL7/Dm9DI8eOqkMgJH9+K/QMaaeWIgOsnxPyAwumTTdQRw/IaKHr97XhUVSxF6Q3Nejqf/MtZ61TqtIQSDDzHIUTBY2hqJi2y4oKVF3Sl/dy3jFjNh3L+T7hzMMUgnr1MxGFUGI5vzFlqsQePxo88V+6G56mznuyEh0ZSXrqcoub2deO6OySF41MBNjGhmAk4wYLZ2sYFBclv9M7trdIyDvKeu3pYBQ7oLl6UQtGkpQoaP7pTyo9sy1V+Wz/3esmB3DktG+m7TVeAPcvrNIOwHptSQZwJpiicRtX+g+ScudPrDU1vY+rGPhuuJz8BVljURz+1B9DSHdQL/UK9IT7/4SCPc40UWmO58U4pk2UZ6OfIALnjsLLH/uyWSbXKGGghgappoFSQHPnl2sfQ5uSV2C+X7MQkiBn2s42kaqVnMos5I3nQcaItsa5i/R2nEwnGU8AncBuOKv9C4IFCxGBAP1z/hTHtbwU7vDWXKPIP4beFZkMujZb+4wjndQsiWBQv4dFptUIrLgWifHI9xpFPyBL/5ubXBNmU4k=
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 18 Jul 2017 21:42:06.3693 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR05MB2182
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Q9DlVIHxSHKSZaZhA9Inr6RN7yw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 21:42:11 -0000

On 7/15/2017 5:21 AM, Russ Housley wrote:
> the general organization and the look-and-feel of the website has been implemented based on the initial research and input received to date.

I've been waiting to hear somone say "I love the new web page.  It makes 
it much easier to quickly find the information I need".

I'm still waiting.

What I'm actually hearing is "The new web page makes it more difficult 
to find the information I need.  I can't tell where the information is 
hidden, and I'm always scrolling through screens and screens of 
content-free graphics to find it.  And then it takes longer to access it".

But there's a good response to this: "The new web page isn't supposed to 
make it easier to find the information you need, use the datatracker for 
that.  The new web page is supposed to look pretty to folks who don't 
actually use it regularly."

Of course, this is almost always what happens when a useful web page is 
redesigned so as to be more modern.

Now if we could just replace all our RFCs with youtube videos ...


From nobody Tue Jul 18 15:25:42 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A425129B05 for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 15:25:40 -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 LFufzsnSlgJi for <ietf@ietfa.amsl.com>; Tue, 18 Jul 2017 15:25:38 -0700 (PDT)
Received: from mail-pf0-x230.google.com (mail-pf0-x230.google.com [IPv6:2607:f8b0:400e:c00::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 B9895126B71 for <ietf@ietf.org>; Tue, 18 Jul 2017 15:25:38 -0700 (PDT)
Received: by mail-pf0-x230.google.com with SMTP id q85so17772904pfq.1 for <ietf@ietf.org>; Tue, 18 Jul 2017 15:25:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=U2DIC+TARxgz64XZG5fmzzemEVe6gMbEMmiy/TChX2M=; b=QB7NKEsp/a8+x1V9Xv/Rjm+NIYu42n+EhwC/QVMRoYGP0PPnTJVLH5+Wh2wtU3Mpzc 8MpSRlb18MdTPGDA/V7wjGUNmhpl6JnGNmGLXBA8HLmE2kk1UsGHMDkXS9Z4fxxPz+XD LFqHfCZ39fRm1c6jVWRPS8a6GV+hViFDft12O3iUMru4eOWPz1D4pr8ax24IHRUK+/cN nJ5AMyqtxqLt4eP5hmqzzE5VjbuddodD2VcoPrgpSXlRDtfMvD/oD5XWgYZ8DUkUsB+e Swn1kxEouS/R+uYsa6b0JC7Iuzj9kCy32f3cXPpPubUqtIjV2kAJgkSk19Rcffo7a1VG 7nJg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=U2DIC+TARxgz64XZG5fmzzemEVe6gMbEMmiy/TChX2M=; b=C1ELZxa3dE9yaSizDomP/udxKdcumD/r8FGEptuEONQlR/ztTGpxadLNHNQjb3IWtM fziubI00dIwf6GAb8NKUUJHZYnM9+rww7OCGVaQL/W+YrMriw+RkcajjZTqoDlUVBVMx A01sKOVQ9+dbnxkrsEOuToEPikKhpcV0+AXHSEuiAbx8sxl/mHweYqncquqIt4IlcXAY Gu0ltdor8ovqRCMGqXfuMA1bzqQCvikYcgI9czlnl+f8xsoZJd6wX24xXD7ko2TGC8+J 2Qm/d0kh2LUYL3YTAPaMaV3Bk+NLUK3KV3yvNVvUw6yhCzJ4NvO8EXIuo7ohrgpxbxFS rV4g==
X-Gm-Message-State: AIVw11385wlDoeZubR1P12B3YtSxgVfyfW5MkTwY+fFC358Ohm1KX2Xd GnFF523K/9zoo0hZ
X-Received: by 10.84.254.73 with SMTP id a9mr3958753pln.69.1500416738057; Tue, 18 Jul 2017 15:25:38 -0700 (PDT)
Received: from ?IPv6:2406:e001:3dad:1:28cc:dc4c:9703:6781? ([2406:e001:3dad:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id 74sm3565413pfk.58.2017.07.18.15.25.36 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Jul 2017 15:25:37 -0700 (PDT)
Subject: Re: Revamp of the www.ietf.org website
To: ietf@ietf.org
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <2a017f34-6ed6-f60f-d5a8-74d944bc40e1@juniper.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <a90fec47-d93b-23cb-ca88-fe389e3a919f@gmail.com>
Date: Wed, 19 Jul 2017 10:25:36 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <2a017f34-6ed6-f60f-d5a8-74d944bc40e1@juniper.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4JXKt_uXFj-8taI631whtu5rKUc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 22:25:40 -0000

On 19/07/2017 09:41, Eric C Rosen wrote:
> On 7/15/2017 5:21 AM, Russ Housley wrote:
>> the general organization and the look-and-feel of the website has been implemented based on the initial research and input received to date.
> 
> I've been waiting to hear somone say "I love the new web page.  It makes 
> it much easier to quickly find the information I need".
> 
> I'm still waiting.
> 
> What I'm actually hearing is "The new web page makes it more difficult 
> to find the information I need.  I can't tell where the information is 
> hidden, and I'm always scrolling through screens and screens of 
> content-free graphics to find it.  And then it takes longer to access it".
> 
> But there's a good response to this: "The new web page isn't supposed to 
> make it easier to find the information you need, use the datatracker for 
> that.  The new web page is supposed to look pretty to folks who don't 
> actually use it regularly."
> 
> Of course, this is almost always what happens when a useful web page is 
> redesigned so as to be more modern.

True. It happened once before, less badly, when the original home page
(approximately https://www.ietf.org/content.html) was replaced by
the current one, which I don't find useful. If https://beta.ietf.org/links/
can't be made to fit in a single screen, I'll be making my own private
equivalent of https://www.ietf.org/content.html anyway. We shouldn't
be afraid of having our web site look geeky.

Alternatively, it would be fine if the sidebar on the tracker
included everything currently covered by the sidebar on www.ietf.org.

> Now if we could just replace all our RFCs with youtube videos ...

Why, when everything worth saying can be said in a tweet?

       Brian
 


From nobody Wed Jul 19 00:43:35 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D418E131C09 for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 00:43:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level: 
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 mXyms0eQWdft for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 00:43:30 -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 C8E75131C05 for <ietf@ietf.org>; Wed, 19 Jul 2017 00:43:30 -0700 (PDT)
Received: from dhcp-8097.meeting.ietf.org (dhcp-8097.meeting.ietf.org [31.133.128.151]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v6J7hSuQ098286 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <ietf@ietf.org>; Wed, 19 Jul 2017 02:43:30 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
To: "ietf@ietf.org" <ietf@ietf.org>
From: Robert Sparks <rjsparks@nostrum.com>
Subject: Next steps in IETF list email archiving
Message-ID: <fe950cd9-bea8-7831-046d-2f48eaaeafb9@nostrum.com>
Date: Wed, 19 Jul 2017 09:43:24 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XJtVovqVTb-KAS8gQNJSwuNdFvs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 07:43:33 -0000

Several years ago, we identified a set of issues with the way
we were archiving email messages and new functionality that a
searching and browsing solution should contain. The initial
requirements for improvements were captured in RFC 6778, and a
subsequent round of requirements were captured in RFC 7842.

One of the key issues was (and is) related to management of
the archives.  Currently if a message has to be removed
(rare, but not as rare as we would like due to spam hitting
some lists), the secretariat has to touch many places. One
of those is Mhonarc. Touching one message there involves
changing many files (any other message that contains a
navigation link to this one, and the index files that speak
about the message).

As we built the new systems, we've targeted having one source
of truth for the archives. For instance, as we added IMAP
access to the archives (RFC 7017), we ensured that it was
served from the same bits used by mailarchive.ietf.org.  It
has been our expectation from the beginning that
mailarchive.org would replace the Mhonarc archives (see
section 2.7 of RFC 6778).

We believe we are getting close to the point where we can
make that replacement. The rate of bug reports and feature
requests for mailarchive.ietf.org is slow. (As we do for
the datatracker, we plan to continuously improve the
mailarchive interface. We know already of some things that
need to be improved when viewing on phone-sized displays.)

If you use the mhonarc archives heavily, and have not yet
explored mailarchive.ietf.org, we encourage you to do so now,
and report any difficulties you find. We recognize that the
experience is different, but many of the RFC 7842 driven
improvements focused on minimizing the transition pain.

We have successfully tested the code that will redirect all
existing Mhonarc URLs into the mailarchive using the
testlist.

We are not going to make this transition immediately, but
we do plan to make it more in the near future than the far
future. Please help us identify any additional things we can
do to minimize the disruption to your current workflow.

RjS



From nobody Wed Jul 19 01:59:45 2017
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57142131C3A for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 01:59:41 -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 2hOyZz7psEsf for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 01:59:40 -0700 (PDT)
Received: from mail-yb0-x233.google.com (mail-yb0-x233.google.com [IPv6:2607:f8b0:4002:c09::233]) (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 BCAAC131C38 for <ietf@ietf.org>; Wed, 19 Jul 2017 01:59:39 -0700 (PDT)
Received: by mail-yb0-x233.google.com with SMTP id w187so14206493ybc.0 for <ietf@ietf.org>; Wed, 19 Jul 2017 01:59:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=xuOjhjp6iVSuFwg0qRFpND9pSCcHA9BT7JTaXL6dvM0=; b=rYdm6YZCp0YBeK5JkqUhUtsD/gMS5TCSxbAAcLnFSMWhBoPpEEJz8732+2w/gB7acE Pwnf8vcUEqGUwQ3ZmS8pEdRDTGCFYfJ5s3k70ev5jbTzblEt2W8n7MjwzdaHbk1VXZVz AjUcTeSUTaaKlKilMqWP2a5btQh/183GoISzhy8T1iAiNyTe+kxx1k6zveGqbnEt3FgQ DfrgRRlof5wlEpLEh5IInkCnpvPIFfWV8aLRZ7hpr26GixSc+MeviU71eyiW2B2ge8UX n91sEGwUdLi8iJM3Muhc9+Xzk+ggqrKk9/+UcDFWDKYkvquhCyFqkJOdn+c+UBTUO3CG HhbQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=xuOjhjp6iVSuFwg0qRFpND9pSCcHA9BT7JTaXL6dvM0=; b=hxr+kX8a/xHyLe2rzOOGT8APlGDswKLIWF0wh9OCLid+ThC+Vajc+Dy24hWIhmSRbS MVJTDIWjby6Tv644Rl3Y8rRlP9Qh4Hnt3z3ecnRd/KfrnZVbRErWDXaYljZcDz8iPFbL UAFJtlak4+AZNIdviwa5npJiAAlnCc/mJD0ir/KrUAQN55gSqA0B7D5KjwlMT5cPGsOR TXVn5aBivL6fw+nGwZJB0WcD7fraf+TrA4xjMNQOdx9B7eX9ZMl6b+eqpHmm5D9R4jdF hKMj8kCwp0CZWrFWC3yYjcjicCnqCE+Ev/w1+jlobbc85BJJj3F8ChXVyAv6IYLGjVEE 6eHg==
X-Gm-Message-State: AIVw110DUbyQya+Hst6iwjwi6yfHRQ4w78y9nZ8pE637892VIAmjFyJh yWb2hodPrCPNsNEysjgWjZVtHLp3Bg==
X-Received: by 10.37.97.71 with SMTP id v68mr1404820ybb.37.1500454778681; Wed, 19 Jul 2017 01:59:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.45.101 with HTTP; Wed, 19 Jul 2017 01:59:38 -0700 (PDT)
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 19 Jul 2017 10:59:38 +0200
Message-ID: <CAKKJt-ehdzREsf3QzGZ+JFOkMm-dGpSdGVFBUJE4BhqWweY+Og@mail.gmail.com>
Subject: Slides, eye charts, and a beg for readability
To: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a1142ea3615c0e30554a7da6b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nPBTjEyDCTdHn3_EwHUYWBe8CXA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 08:59:41 -0000

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

Dear IETF participants who are mostly younger than I am ...

I've been routinely using Meetecho *in the room* so that I could read
slides with fonts too small to read from the back of the room. I'm fine
with that, although I don't know that everyone is.

I'm seeing a couple of presentations where the font is so small that I can
barely read it with reading glasses on Meetecho.

If people could ask themselves if they care about being understood enough
to use a font large enough to read, that would be great.

Thanks,

Spencer, who's 20/20, after surgery, so it shouldn't be this hard!

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

<div dir=3D"ltr">Dear IETF participants who are mostly younger than I am ..=
.<div><br></div><div>I&#39;ve been routinely using Meetecho *in the room* s=
o that I could read slides with fonts too small to read from the back of th=
e room. I&#39;m fine with that, although I don&#39;t know that everyone is.=
</div><div><br></div><div>I&#39;m seeing a couple of presentations where th=
e font is so small that I can barely read it with reading glasses on Meetec=
ho.=C2=A0</div><div><br></div><div>If people could ask themselves if they c=
are about being understood enough to use a font large enough to read, that =
would be great.</div><div><br></div><div>Thanks,</div><div><br></div><div>S=
pencer, who&#39;s 20/20, after surgery, so it shouldn&#39;t be this hard!</=
div></div>

--001a1142ea3615c0e30554a7da6b--


From nobody Wed Jul 19 02:04:00 2017
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CD8A131A5F for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 02:03:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 g5LX_2kEsabn for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 02:03:57 -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 CA51412ECC0 for <ietf@ietf.org>; Wed, 19 Jul 2017 02:03:56 -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 v6J93qwI001497; Wed, 19 Jul 2017 10:03:53 +0100
Received: from 950129200 (dhcp-8d56.meeting.ietf.org [31.133.141.86]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id v6J93pYs001477 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Jul 2017 10:03:52 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Spencer Dawkins at IETF'" <spencerdawkins.ietf@gmail.com>, <ietf@ietf.org>
References: <CAKKJt-ehdzREsf3QzGZ+JFOkMm-dGpSdGVFBUJE4BhqWweY+Og@mail.gmail.com>
In-Reply-To: <CAKKJt-ehdzREsf3QzGZ+JFOkMm-dGpSdGVFBUJE4BhqWweY+Og@mail.gmail.com>
Subject: RE: Slides, eye charts, and a beg for readability
Date: Wed, 19 Jul 2017 10:03:49 +0100
Message-ID: <08eb01d3006d$f0aa8a60$d1ff9f20$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_08EC_01D30076.5270C720"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKDsqVnxogA4fQB8x5ymF3DExiuBqD5djTg
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-23204.005
X-TM-AS-Result: No--18.808-10.0-31-10
X-imss-scan-details: No--18.808-10.0-31-10
X-TMASE-MatchedRID: DuKherWvI/s40Hl/szdmxvC1l8GignprOkDbNlgmO/UF0ByI7hu5pYLC CVfTVmLWGPtCd+WAW3G+pq6lzGCExKO3HsqbYTv7b/5HBZ6dvRgLy8o3bV9yTbV5fSMRD1zqRzn Bn/ptWd67swud9zS7ewhLAF5psSKt0YRMm/X9bI5T46Ow+EhYOL/I3arxTrvi4WNDrZWE/xveQ0 ny4xLfM7edAyoen50fkqZRWKnqgAeEKYksiicmGeYAh37ZsBDCuofcE6BrchB0PA/ki2kI7BxJE X0k/k7OLiNvWfV40DdEdqKGnxMcYDGgk0AvH9/hndu3heVAxaMP4vBWNr0zgSA6eO+NDmAxJZ3D 0zKPh7H10yQNuo1OJZfucML7iAp6c1BeS/J6aN9dMrg609R9BKO4XjVpMlFdn+lpJmYuEaN7ltq yJvHgp/JOjUaxKXKqGSKDIgjU9nky499dCbQy8IoLoibgjVEX1WPYxCHVrqdgHzfrfdHEt4c0B5 OUL/u1M5qWMflCo4dwtismKfx+71mKiy1F9pgLuIwLnB3Aqp13Bf9JIqsoeA8YwboCQc88CE7se pEW6CvzbeV2VN8Li3ZBE86uj+HtFIXwv4qc0ZOlhD9Iy+IVwyIEB/X0tggGlThwL2cA6F1R18Qp zXStTjhEMZsHJG9bERIFEmVIRRZTovWuZWqWkd/wYmMFcJSI3keXXBe59XlT+oAjVn9e0ORqQAx bWD9+4vM1YF6AJbbVZ0g740lL+SIQ5mZ5SqHPiBoDJxgvqvczIjSpN6AtDtQbdDkFUicJJOG84f QSWKq15EIEo79P/g==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dJruWLgAR36x_8W1DQ47fYR7RS4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 09:04:00 -0000

This is a multipart message in MIME format.

------=_NextPart_000_08EC_01D30076.5270C720
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Spencer,
=20
Aren't all the slides posted in the meeting materials at least 24 hours =
ahead of time to allow us to download them, use our own preferred tools, =
struggle with English not being our native language, and so on?
=20
Adrian
=20
From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Spencer Dawkins =
at IETF
Sent: 19 July 2017 10:00
To: ietf@ietf.org
Subject: Slides, eye charts, and a beg for readability
=20
Dear IETF participants who are mostly younger than I am ...
=20
I've been routinely using Meetecho *in the room* so that I could read =
slides with fonts too small to read from the back of the room. I'm fine =
with that, although I don't know that everyone is.
=20
I'm seeing a couple of presentations where the font is so small that I =
can barely read it with reading glasses on Meetecho.=20
=20
If people could ask themselves if they care about being understood =
enough to use a font large enough to read, that would be great.
=20
Thanks,
=20
Spencer, who's 20/20, after surgery, so it shouldn't be this hard!

------=_NextPart_000_08EC_01D30076.5270C720
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@01D30076.5006CC00"><!--[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-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";
	mso-fareast-language:EN-US;}
@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:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-fareast-language:EN-US;}
</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'>Spencer,<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'>Aren't all the slides posted =
in the meeting materials at least 24 hours ahead of time to allow us to =
download them, use our own preferred tools, struggle with English not =
being our native language, and so on?<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'>Adrian<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'> ietf =
[mailto:ietf-bounces@ietf.org] <b>On Behalf Of </b>Spencer Dawkins at =
IETF<br><b>Sent:</b> 19 July 2017 10:00<br><b>To:</b> =
ietf@ietf.org<br><b>Subject:</b> Slides, eye charts, and a beg for =
readability<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>Dear =
IETF participants who are mostly younger than I am =
...<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>I've been routinely using Meetecho *in the room* so =
that I could read slides with fonts too small to read from the back of =
the room. I'm fine with that, although I don't know that everyone =
is.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>I'm seeing a couple of presentations where the font is =
so small that I can barely read it with reading glasses on =
Meetecho.&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>If people could ask themselves if they care about =
being understood enough to use a font large enough to read, that would =
be great.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Thanks,<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Spencer, who's 20/20, after surgery, so it shouldn't =
be this hard!<o:p></o:p></p></div></div></div></div></body></html>
------=_NextPart_000_08EC_01D30076.5270C720--


From nobody Wed Jul 19 04:58:36 2017
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50F4D131B13 for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 04:58:35 -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 UChtx4Dkaf6U for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 04:58:33 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 774BB12EB99 for <ietf@ietf.org>; Wed, 19 Jul 2017 04:58:33 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [IPv6:2001:67c:370:1998:a11:96ff:fe01:81e0]) by relay.sandelman.ca (Postfix) with ESMTPS id B77C81F8F6; Wed, 19 Jul 2017 11:58:31 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id A817C1CCB; Wed, 19 Jul 2017 13:58:23 +0200 (CEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Robert Sparks <rjsparks@nostrum.com>
cc: "ietf\@ietf.org" <ietf@ietf.org>
Subject: Re: Next steps in IETF list email archiving
In-reply-to: <fe950cd9-bea8-7831-046d-2f48eaaeafb9@nostrum.com>
References: <fe950cd9-bea8-7831-046d-2f48eaaeafb9@nostrum.com>
Comments: In-reply-to Robert Sparks <rjsparks@nostrum.com> message dated "Wed, 19 Jul 2017 09:43:24 +0200."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 19 Jul 2017 13:58:23 +0200
Message-ID: <17106.1500465503@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yyyaCAI54ZYYTG0Mmlwa8hRhVB8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 11:58:35 -0000

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable


Robert Sparks <rjsparks@nostrum.com> wrote:
    > If you use the mhonarc archives heavily, and have not yet explored
    > mailarchive.ietf.org, we encourage you to do so now, and report any
    > difficulties you find. We recognize that the experience is different,
    > but many of the RFC 7842 driven improvements focused on minimizing the
    > transition pain.

I stopped using mailarchive and I almost exclusively use mhonarc
This is now easy since the dual links in the datatracker returned.
I was making up the correct links before, which was a pain.

I find the search-only interface to mailarchive annoying, and frankly slow.

While the thread support is better, it is still not anywhere as close
to MHonarc.  When I find an email that I care about, and I ask for the
thread view, I get the thread for the entire list --- yes, with that
email opened, but the entire thread is there.
If there is a URL for that thread, I don't know it, and it is not easily
found.

Frankly, I just feel stupid interacting with an active system when I
know a set of static files would satisfy my needs.   No matter how fast the
active system can be made...

    > We have successfully tested the code that will redirect all existing
    > Mhonarc URLs into the mailarchive using the testlist.

neat.  I understand the desire to get rid of mhonarc.  I want mailarchive
to succeed, but it still feels really klunky to me.

    > We are not going to make this transition immediately, but we do plan =
to
    > make it more in the near future than the far future. Please help us
    > identify any additional things we can do to minimize the disruption to
    > your current workflow.

It would be cool if I could get an IMAP URL from mailarchive, as that
would let me jump from searching the archives for a relevant thread,
and right into writing a reply to it.

=2D-=20
]               Never tell me the odds!                 | ipv6 mesh network=
s [=20
]   Michael Richardson, Sandelman Software Works        | network architect=
  [=20
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [=20
=09




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJZb0lfAAoJEJVM4Vb9/EKQrgQIAJ16/x73KHrtSpeN6IpKN/1l
LLaTJv5kmrrs+ejgNQ8QRIvwtCNT08fNvpRV8o/fnk4yqZgoCoz1Mp60N/7JII9z
M45sVBCEVUuj50N+21DpUBknBZXm0ij27lrNeX647w/24gIOKj1+Ht1vMmwll4p1
MMOYlAf9FsHrUN3zHnV178jUybFRlj4UH7Bhp6ZkRtS8dRZY/e/oZiVRaUcYc4RF
6z+lArlOiBbNjJ1043VO2UfZLXby7ef5bZCVmLWBNNUufQSRJ25RDXRdq32htjyc
5aQROYQN3Zbb+F+hVN1bcZgsCt5ndJXqOd/UdWR3jgqnxrlvtrbzzfNTyNhoUF0=
=PlZc
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Jul 19 05:04:00 2017
Return-Path: <nick@foobar.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2905F131692 for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 05:03:58 -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 60Jz8BjiWrFU for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 05:03:56 -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 02406131471 for <ietf@ietf.org>; Wed, 19 Jul 2017 05:03:55 -0700 (PDT)
X-Envelope-To: ietf@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 v6JC3p2j088537 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Jul 2017 13:03:52 +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: <596F4AA7.4040905@foobar.org>
Date: Wed, 19 Jul 2017 13:03:51 +0100
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.15 (Macintosh/20170609)
MIME-Version: 1.0
To: Michael Richardson <mcr+ietf@sandelman.ca>
CC: Robert Sparks <rjsparks@nostrum.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Next steps in IETF list email archiving
References: <fe950cd9-bea8-7831-046d-2f48eaaeafb9@nostrum.com> <17106.1500465503@dooku.sandelman.ca>
In-Reply-To: <17106.1500465503@dooku.sandelman.ca>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/feg47sFVNr2Xot7lSOXEeG4Z5SM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 12:03:58 -0000

without meaning to sound like a complete luddite (and top-posting for
extra effect), what Michael has written is exactly how I feel about both
systems, and I would be very unhappy to see mhonarc go.

Nick

Michael Richardson wrote:
> Robert Sparks <rjsparks@nostrum.com> wrote:
>     > If you use the mhonarc archives heavily, and have not yet explored
>     > mailarchive.ietf.org, we encourage you to do so now, and report any
>     > difficulties you find. We recognize that the experience is different,
>     > but many of the RFC 7842 driven improvements focused on minimizing the
>     > transition pain.
> 
> I stopped using mailarchive and I almost exclusively use mhonarc
> This is now easy since the dual links in the datatracker returned.
> I was making up the correct links before, which was a pain.
> 
> I find the search-only interface to mailarchive annoying, and frankly slow.
> 
> While the thread support is better, it is still not anywhere as close
> to MHonarc.  When I find an email that I care about, and I ask for the
> thread view, I get the thread for the entire list --- yes, with that
> email opened, but the entire thread is there.
> If there is a URL for that thread, I don't know it, and it is not easily
> found.
> 
> Frankly, I just feel stupid interacting with an active system when I
> know a set of static files would satisfy my needs.   No matter how fast the
> active system can be made...
> 
>     > We have successfully tested the code that will redirect all existing
>     > Mhonarc URLs into the mailarchive using the testlist.
> 
> neat.  I understand the desire to get rid of mhonarc.  I want mailarchive
> to succeed, but it still feels really klunky to me.
> 
>     > We are not going to make this transition immediately, but we do plan to
>     > make it more in the near future than the far future. Please help us
>     > identify any additional things we can do to minimize the disruption to
>     > your current workflow.
> 
> It would be cool if I could get an IMAP URL from mailarchive, as that
> would let me jump from searching the archives for a relevant thread,
> and right into writing a reply to it.
> 


From nobody Wed Jul 19 05:17:10 2017
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7478E131B16 for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 05:17:08 -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 QzRu1DdziEr5 for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 05:17:06 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0720F131CDE for <ietf@ietf.org>; Wed, 19 Jul 2017 05:17:06 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [IPv6:2001:67c:370:1998:a11:96ff:fe01:81e0]) by relay.sandelman.ca (Postfix) with ESMTPS id DC39D1F8F6; Wed, 19 Jul 2017 12:17:04 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 90E4A1CCB; Wed, 19 Jul 2017 14:16:56 +0200 (CEST)
From: Michael Richardson <mcr@sandelman.ca>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Slides, eye charts, and a beg for readability
In-reply-to: <CAKKJt-ehdzREsf3QzGZ+JFOkMm-dGpSdGVFBUJE4BhqWweY+Og@mail.gmail.com>
References: <CAKKJt-ehdzREsf3QzGZ+JFOkMm-dGpSdGVFBUJE4BhqWweY+Og@mail.gmail.com>
Comments: In-reply-to Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> message dated "Wed, 19 Jul 2017 10:59:38 +0200."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <18145.1500466616.1@dooku.sandelman.ca>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 19 Jul 2017 14:16:56 +0200
Message-ID: <18146.1500466616@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/l_0Q9_9w5a1fT-eQfRK4-b4d93g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 12:17:08 -0000

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> wrote:
    > I'm seeing a couple of presentations where the font is so small that=
 I
    > can barely read it with reading glasses on Meetecho.

E-TooManyWordsOnScreen

Many presenters need to read Presentation Zen.

-- =

]               Never tell me the odds!                 | ipv6 mesh networ=
ks [ =

]   Michael Richardson, Sandelman Software Works        | network architec=
t  [ =

]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails =
   [ =

	=




From nobody Wed Jul 19 06:17:03 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D61E131D1C for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 06:17:01 -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, RP_MATCHES_RCVD=-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 tGn2FO_uT8np for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 06:16:52 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61677131D27 for <ietf@ietf.org>; Wed, 19 Jul 2017 06:16:49 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dXoqN-000NUA-SC; Wed, 19 Jul 2017 09:16:47 -0400
Date: Wed, 19 Jul 2017 09:16:42 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, ietf@ietf.org
Subject: Re: Revamp of the www.ietf.org website
Message-ID: <6192DB6BFF5B6E62141B8236@PSB>
In-Reply-To: <a90fec47-d93b-23cb-ca88-fe389e3a919f@gmail.com>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <2a017f34-6ed6-f60f-d5a8-74d944bc40e1@juniper.net> <a90fec47-d93b-23cb-ca88-fe389e3a919f@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eUdhhcjbQH0JJUngg9mHfTa5hhg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 13:17:01 -0000

FWIW, +1

Suggestion: If the IESG is convinced that we need a page at
www.ietf.org that is designed for prettiness and attraction for
newcomers and those who are just browsing, would it be possible
to have an easily-remembered URL (and link from that home page
for those who forget) that essentially reflects the information
in the current sidebar plus maybe the "news" and "next meeting"
and "related web pages" panels, with zero images and no
animation or automation?   For those of us who use IETF web
pages only to get work done, attractiveness is often measured in
ease of navigation and minimizing the number of clicks needed to
reach something, goals that may be incompatible with "pretty",
"clever", or "attractive to those who are just browsing".

    john


--On Wednesday, July 19, 2017 10:25 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> On 19/07/2017 09:41, Eric C Rosen wrote:
>> On 7/15/2017 5:21 AM, Russ Housley wrote:
>>> the general organization and the look-and-feel of the
>>> website has been implemented based on the initial research
>>> and input received to date.
>> 
>> I've been waiting to hear somone say "I love the new web
>> page.  It makes  it much easier to quickly find the
>> information I need".
>> 
>> I'm still waiting.
>> 
>> What I'm actually hearing is "The new web page makes it more
>> difficult  to find the information I need.  I can't tell
>> where the information is  hidden, and I'm always scrolling
>> through screens and screens of  content-free graphics to find
>> it.  And then it takes longer to access it".
>> 
>> But there's a good response to this: "The new web page isn't
>> supposed to  make it easier to find the information you need,
>> use the datatracker for  that.  The new web page is supposed
>> to look pretty to folks who don't  actually use it regularly."
>> 
>> Of course, this is almost always what happens when a useful
>> web page is  redesigned so as to be more modern.
> 
> True. It happened once before, less badly, when the original
> home page (approximately https://www.ietf.org/content.html)
> was replaced by the current one, which I don't find useful. If
> https://beta.ietf.org/links/ can't be made to fit in a single
> screen, I'll be making my own private equivalent of
> https://www.ietf.org/content.html anyway. We shouldn't be
> afraid of having our web site look geeky.
> 
> Alternatively, it would be fine if the sidebar on the tracker
> included everything currently covered by the sidebar on
> www.ietf.org.
> 
>> Now if we could just replace all our RFCs with youtube videos
>> ...
> 
> Why, when everything worth saying can be said in a tweet?
> 
>        Brian
>  
> 





From nobody Wed Jul 19 06:44:05 2017
Return-Path: <ietf@meetecho.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22781131B44 for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 06:44:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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=aruba.it
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 acHXRUZExIC4 for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 06:44:00 -0700 (PDT)
Received: from smtpweb126.aruba.it (smtpweb126.aruba.it [62.149.158.126]) by ietfa.amsl.com (Postfix) with ESMTP id 1B9ED129B10 for <ietf@ietf.org>; Wed, 19 Jul 2017 06:43:59 -0700 (PDT)
Received: from [31.130.230.90] ([31.130.230.90]) by smtpcmd03.ad.aruba.it with bizsmtp id mdjv1v00j1xgSgX01djw2r; Wed, 19 Jul 2017 15:43:58 +0200
From: Meetecho IETF support <ietf@meetecho.com>
Subject: Meetecho recordings
To: ietf@ietf.org
Message-ID: <35b97a62-5dff-8878-c101-3532cd85b4f8@meetecho.com>
Date: Wed, 19 Jul 2017 15:43:53 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aruba.it; s=a1; t=1500471838; bh=iNoz8wlKXdTOnAvmuIZD/M34M6qS8FoN2E/MDKBHxn0=; h=From:Subject:To:Date:MIME-Version:Content-Type; b=I2Luxv3nXEnct/jtytEVUIgZVs0iPHKYU3vKZeC0qM0ZoiOne14nPP5Szi3e+zYHo 8LRfYcwBl/G8hYikYcBc5iCZXc8lxJ4yfdxgeVGTpMsyWzEtEhBig/H/E6PfGDACIz CjbLdEHxrq/ytNv5rAFZmOlczYXuTYsxWk7kWCO2YFLqROZFmDZ2km5YbMwbBnJWYs UGOZ7ji8NmIexBHgQ15EdqQ4nnzbdGc1JzpEOBm0tuUqfmYx4M2bxex1lSLbp3u22S mhK70QrHnMqeOh61jG/z/WW0jOPrPKAmfTU6gCHVR2ElCX6DwU39ai75CbDR/U/e1b USAvi03LAHJkA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7ze3qAClRIJorN4cClwj9nXBfhM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 13:44:03 -0000

Folks,

please find below some useful information about the Meetecho session 
recordings.

All meeting sessions video recordings are usually posted on the official 
IETF YouTube channel within 24 hours. You can find them all in the 
IETF99 playlist.

As some of you may have already noticed, we released a revamped and 
improved version of our playout web application, which integrates the 
audio/video with the Jabber logs. It can be accessed from the meeting 
agenda page by clicking on the M-shaped button.

A new feature we just added is the audio "transcript": at the bottom of 
the page, just below the video, you can find a tab with 
automatically-generated captions. You can click on a text snippet to 
jump to that point in the recording. The transcript is automatically 
generated by YouTube and may not be perfect, but seems quite accurate to 
us. Please note that the transcript is not immediately available (some 
post-processing is needed), but usually takes a few hours to appear.

Feedback welcome!

Cheers,
the Meetecho crew


From nobody Wed Jul 19 07:03:44 2017
Return-Path: <tony@att.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DC12131473 for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 07:03:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.4
X-Spam-Level: 
X-Spam-Status: No, score=-5.4 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, 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 oc_AEbF_JbPu for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 07:03:41 -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 A7DA8126CD8 for <ietf@ietf.org>; Wed, 19 Jul 2017 07:03:41 -0700 (PDT)
Received: from pps.filterd (m0049459.ppops.net [127.0.0.1]) by m0049459.ppops.net-00191d01. (8.16.0.17/8.16.0.17) with SMTP id v6JDuIhR024520 for <ietf@ietf.org>; Wed, 19 Jul 2017 10:03:38 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049459.ppops.net-00191d01. with ESMTP id 2bt5hv5sk1-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <ietf@ietf.org>; Wed, 19 Jul 2017 10:03:38 -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 v6JE3c0O000429 for <ietf@ietf.org>; Wed, 19 Jul 2017 10:03:38 -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 v6JE3VGr032756 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Wed, 19 Jul 2017 10:03:32 -0400
Received: from MISOUT7MSGHUBAH.ITServices.sbc.com (MISOUT7MSGHUBAH.itservices.sbc.com [130.9.129.152]) by mlpi407.sfdc.sbc.com (RSA Interceptor) for <ietf@ietf.org>; Wed, 19 Jul 2017 14:03:17 GMT
Received: from MISOUT7MSGUSRCG.ITServices.sbc.com ([169.254.7.78]) by MISOUT7MSGHUBAH.ITServices.sbc.com ([130.9.129.152]) with mapi id 14.03.0319.002; Wed, 19 Jul 2017 10:03:17 -0400
From: "HANSEN, TONY L" <tony@att.com>
To: IETF <ietf@ietf.org>
Subject: Re: Revamp of the www.ietf.org website
Thread-Topic: Revamp of the www.ietf.org website
Thread-Index: AQHTAA7AA1Cl0cnEW0+Lzsh/TCZeoqJbL2sA
Date: Wed, 19 Jul 2017 14:03:16 +0000
Message-ID: <62F2B217-081C-48D4-B7C0-4601AC004C68@att.com>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <2a017f34-6ed6-f60f-d5a8-74d944bc40e1@juniper.net>
In-Reply-To: <2a017f34-6ed6-f60f-d5a8-74d944bc40e1@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.210.12.53]
Content-Type: text/plain; charset="utf-8"
Content-ID: <663AF8A6606B5F4EBDEDB8D8579812C3@LOCAL>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-07-19_09:, , 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-1706020000 definitions=main-1707190227
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DqUQfjXUDXBkS9IKz-qtCcV17-U>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 14:03:43 -0000

T24gNy8xOC8xNywgNTo0MSBQTSwgImlldGYgb24gYmVoYWxmIG9mIEVyaWMgQyBSb3NlbiIgPGll
dGYtYm91bmNlc0BpZXRmLm9yZyBvbiBiZWhhbGYgb2YgZXJvc2VuQGp1bmlwZXIubmV0PiB3cm90
ZToNCg0KICAgIE9uIDcvMTUvMjAxNyA1OjIxIEFNLCBSdXNzIEhvdXNsZXkgd3JvdGU6DQogICAg
PiB0aGUgZ2VuZXJhbCBvcmdhbml6YXRpb24gYW5kIHRoZSBsb29rLWFuZC1mZWVsIG9mIHRoZSB3
ZWJzaXRlIGhhcyBiZWVuIGltcGxlbWVudGVkIGJhc2VkIG9uIHRoZSBpbml0aWFsIHJlc2VhcmNo
IGFuZCBpbnB1dCByZWNlaXZlZCB0byBkYXRlLg0KICAgIA0KICAgIEkndmUgYmVlbiB3YWl0aW5n
IHRvIGhlYXIgc29tb25lIHNheSAiSSBsb3ZlIHRoZSBuZXcgd2ViIHBhZ2UuICBJdCBtYWtlcyAN
CiAgICBpdCBtdWNoIGVhc2llciB0byBxdWlja2x5IGZpbmQgdGhlIGluZm9ybWF0aW9uIEkgbmVl
ZCIuDQogICAgDQogICAgSSdtIHN0aWxsIHdhaXRpbmcuDQogICAgDQogICAgV2hhdCBJJ20gYWN0
dWFsbHkgaGVhcmluZyBpcyAiVGhlIG5ldyB3ZWIgcGFnZSBtYWtlcyBpdCBtb3JlIGRpZmZpY3Vs
dCANCiAgICB0byBmaW5kIHRoZSBpbmZvcm1hdGlvbiBJIG5lZWQuICBJIGNhbid0IHRlbGwgd2hl
cmUgdGhlIGluZm9ybWF0aW9uIGlzIA0KICAgIGhpZGRlbiwgYW5kIEknbSBhbHdheXMgc2Nyb2xs
aW5nIHRocm91Z2ggc2NyZWVucyBhbmQgc2NyZWVucyBvZiANCiAgICBjb250ZW50LWZyZWUgZ3Jh
cGhpY3MgdG8gZmluZCBpdC4gIEFuZCB0aGVuIGl0IHRha2VzIGxvbmdlciB0byBhY2Nlc3MgaXQi
Lg0KDQoNCklmIGRhdGF0cmFja2VyIGlzIHRvIGJlIHRoZSBuZXcg4oCccmVhbOKAnSBpZXRmLm9y
ZyBwYWdlLCB0aGVuIHRoZXJlIG5lZWRzIHRvIGJlIGEgUVVJQ0sgc3RlcCB0byBnZXQgdG8gaXQg
ZnJvbSBiZXRhLmlldGYub3JnLiBSaWdodCBub3csIGEgbGluayB0byBpdCBpcyBmb3VuZCBvbmx5
IHVuZGVyIHRoZSBUb29scyBtZW51LCBidXQgSSBoYWQgdG8gc2VhcmNoIGZvciBpdC4gQW5kIG9u
IG15IGlQaG9uZSwgSSBjb3VsZCBOT1QgRklORCB0aGUgVG9vbHMgbWVudSwgYW5kIHN1YnNlcXVl
bnRseSBjb3VsZG7igJl0IGdldCB0byB0aGUgZGF0YXRyYWNrZXIgZnJvbSBpdC4NCg0KSSBhbHNv
IGRpZCBub3Qgc3BvdCBhIGxpbmsgdG8gdG9vbHMuaWV0Zi5vcmcuIEkgZmlndXJlZCB0aGF0IHdv
dWxkIGJlIHVuZGVyIHRoZSBUb29scyBtZW51IGFzIHdlbGwuDQoNClRoZSBkYXRhdHJhY2tlci5p
ZXRmLm9yZyBwYWdlIHdvdWxkIG5lZWQgc29tZSByZXdvcmsgdG8gYmUgYXMgdXNlZnVsIGFzIHRo
ZSBjdXJyZW50IHd3dy5pZXRmLm9yZyBwYWdlLiBBbmQgcGVyaGFwcyBhIGRpZXQgdG8gZWxpbWlu
YXRlIHNvbWUgc2Nyb2xsaW5nIHRvIGZpbmQgdGhlIGluZm8/DQoNClRoZSBJRVRGIDk5IFByYWd1
ZSBwYWdlIGxpbmtlZCB0byBmcm9tIGJldGEuaWV0Zi5vcmcgU0VFTVMgbGlrZSBpdCBoYXMgYWxs
IG9mIHRoZSBpbmZvcm1hdGlvbiBjdXJyZW50bHkgZm91bmQgb24gd3d3LmlldGYub3JnIGZvciB0
aGUgY3VycmVudCBtZWV0aW5nLiBCdXQgSSBoYWQgdG8gY2xpY2sgb24gYSBnYXppbGxpb24gZG93
biBhcnJvd3MgdG8gb3BlbiB1cCBlYWNoIHRvIHZlcmlmeSB0aGF0IHN0YXRlbWVudC4gVGhlcmUg
ZG9lc27igJl0IHNlZW0gdG8gYmUgYW4gZWFzeSB0byBvcGVuIHVwIEFMTCBvZiB0aGUgc3VibWVu
dXMgdG8gZ2V0IHRoZSBlcXVpdmFsZW50IOKAnG1lZXRpbmcgYXQgYSBnbGFuY2XigJ0ganVtcCBw
YWdlIHRoYXQgd2UgY3VycmVudGx5IGhhdmUuDQoNCglUb255IEhhbnNlbg0KDQo=


From nobody Wed Jul 19 07:21:17 2017
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53A0A131A61 for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 07:21:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 YRT8T13WakdG for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 07:21:15 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 21B5012EC51 for <ietf@ietf.org>; Wed, 19 Jul 2017 07:21:15 -0700 (PDT)
Received: from [10.47.60.52] (dhcp-9976.meeting.ietf.org [31.133.153.118]) (authenticated bits=0) by mail.proper.com (8.15.2/8.14.9) with ESMTPSA id v6JEKM49046594 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Wed, 19 Jul 2017 07:20:25 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host dhcp-9976.meeting.ietf.org [31.133.153.118] claimed to be [10.47.60.52]
From: "Paul Hoffman" <paul.hoffman@vpnc.org>
To: ietf@ietf.org
Subject: Re: Revamp of the www.ietf.org website
Date: Wed, 19 Jul 2017 16:21:07 +0200
Message-ID: <B8EE1B46-860E-45AC-951A-E9C70BA224DB@vpnc.org>
In-Reply-To: <6192DB6BFF5B6E62141B8236@PSB>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <2a017f34-6ed6-f60f-d5a8-74d944bc40e1@juniper.net> <a90fec47-d93b-23cb-ca88-fe389e3a919f@gmail.com> <6192DB6BFF5B6E62141B8236@PSB>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.6r5347)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xSLyyE36t0DKxXeE55u0zyYj3fg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 14:21:16 -0000

On 19 Jul 2017, at 15:16, John C Klensin wrote:

> Suggestion: If the IESG is convinced that we need a page at
> www.ietf.org that is designed for prettiness and attraction for
> newcomers and those who are just browsing, would it be possible
> to have an easily-remembered URL (and link from that home page
> for those who forget) that essentially reflects the information
> in the current sidebar plus maybe the "news" and "next meeting"
> and "related web pages" panels, with zero images and no
> animation or automation?   For those of us who use IETF web
> pages only to get work done, attractiveness is often measured in
> ease of navigation and minimizing the number of clicks needed to
> reach something, goals that may be incompatible with "pretty",
> "clever", or "attractive to those who are just browsing".

This seems like a good, serious proposal. https://www.ietf.org/basic or 
something like that would likely greatly help some of us who often have 
slow connections.

--Paul Hoffman


From nobody Wed Jul 19 07:22:43 2017
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0809131D0B for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 07:22:36 -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 H-f-V3tIhQqW for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 07:22:34 -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 CC910131B4B for <ietf@ietf.org>; Wed, 19 Jul 2017 07:22:33 -0700 (PDT)
Received: by mail-yw0-x229.google.com with SMTP id a12so1005372ywh.3 for <ietf@ietf.org>; Wed, 19 Jul 2017 07:22:33 -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=cBNrfej8BDN/mbuqGxqHn83pgfWQ9eurpM+6R3UERZU=; b=WVPFqQeu3Hg8gJKlzuSlzNdKF9PneuRG/e9siyitAQTyWb+iNZuO1Wmc+AHrKv4iWa 2o5ksOQhlgLdgV2hgJ1YcnId41u/XoewfEhKc+N57OQ1lJu9f7NsKz/1wDNiQzhAsB88 4GnB1DmjLF7xGZOQ3VG6ipHRS0+rPvxTQXBiGVZcrgpnWqgNWiO90EPqbbSEsEPFMpal XVrivJH0MbEeOtJrlUxlX2rj98CU9m+5xqhpz6IAf9NfAKWF1IQhwvtrQAPfPztuU+ls GVpTSaK/egxOxEdYx+zyhWAvNp5LwLEmvu2HFIVHX2P45JRkXcHqcm9HYcgKfRxgOEZH h8TQ==
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=cBNrfej8BDN/mbuqGxqHn83pgfWQ9eurpM+6R3UERZU=; b=mFEGfMr+eyqL/8vO0b29Yy0Lk/dF9Luc8DXAhtuuV8dfoy5wgcYDTRRlAKBwupWUqo 7LwMbtR31yK/uBFvvR6JEOkvXWzoCdJAuGtlGqqg2Yx1jm+wQ2QR3Hm++Se5x8yuj2qT AQawBQwHQzlyGU0VJ7bZpcrBiW6l+AmPgCjSdYEU6itRSDFV3vIggt/3hfk+rztnL1m3 r3OadgfXJiZyTr/t7K1ih8sAS9zkRX28uX443kUwPREXF2TRFoB2+uLEMBAj5OflWSAh GVXtxmXAPeDhrHO4h9Sz0EQ0JhT7EDplcSeQRzUOQ/Naed5Qp3gJ0QWBub/+M7/EIJWW ft7g==
X-Gm-Message-State: AIVw110Dhha2LbhfAuF3ZonI3qAqddERoCROrY8mxWET2BHmRFYisi8x rwymh9RSUvhBql1DHluo82X813TeXQ==
X-Received: by 10.13.213.148 with SMTP id x142mr230737ywd.311.1500474152937; Wed, 19 Jul 2017 07:22:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.45.101 with HTTP; Wed, 19 Jul 2017 07:22:32 -0700 (PDT)
In-Reply-To: <08eb01d3006d$f0aa8a60$d1ff9f20$@olddog.co.uk>
References: <CAKKJt-ehdzREsf3QzGZ+JFOkMm-dGpSdGVFBUJE4BhqWweY+Og@mail.gmail.com> <08eb01d3006d$f0aa8a60$d1ff9f20$@olddog.co.uk>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 19 Jul 2017 16:22:32 +0200
Message-ID: <CAKKJt-fhDgfi7UofBjmLo9xhHqjUe+tL8THs6yGYv3Cn9ETq0g@mail.gmail.com>
Subject: Re: Slides, eye charts, and a beg for readability
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a114fa266e1743e0554ac5cc4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hh6sjFRkM9OL3r8vB24u-6xml6M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 14:22:37 -0000

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

Hi, Adrian,

On Wed, Jul 19, 2017 at 11:03 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:

> Spencer,
>
>
>
> Aren't all the slides posted in the meeting materials at least 24 hours
> ahead of time to allow us to download them, use our own preferred tools,
> struggle with English not being our native language, and so on?
>

Well, MINE were in TSVAREA, but that's not always true. I sat in one
meeting that had no slides uploaded at all. Not naming names, because the
responsible person supervising that meeting was sitting in front of me, and
was also noticing that lack of meeting materials.

Alternatively, if we were going to tell people it's a good plan to listen
to the audio and try to stay synchronized on their own copies of the
slides, we could save the Meetecho people a lot of aggravation, and ISOC a
fair amount of money.

But let's not do that, OK?

Spencer

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

<div dir=3D"ltr">Hi, Adrian,<div class=3D"gmail_extra"><br><div class=3D"gm=
ail_quote">On Wed, Jul 19, 2017 at 11:03 AM, Adrian Farrel <span dir=3D"ltr=
">&lt;<a href=3D"mailto:adrian@olddog.co.uk" target=3D"_blank">adrian@olddo=
g.co.uk</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 lang=
=3D"EN-GB" link=3D"blue" vlink=3D"purple"><div class=3D"m_-4157903835872678=
042WordSection1"><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;fon=
t-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Spencer,=
<u></u><u></u></span></p><p class=3D"MsoNormal"><span style=3D"font-size:11=
.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=
<u></u>=C2=A0<u></u></span></p><p class=3D"MsoNormal"><span style=3D"font-s=
ize:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f=
497d">Aren&#39;t all the slides posted in the meeting materials at least 24=
 hours ahead of time to allow us to download them, use our own preferred to=
ols, struggle with English not being our native language, and so on?</span>=
</p></div></div></blockquote><div><br></div><div>Well, MINE were in TSVAREA=
, but that&#39;s not always true. I sat in one meeting that had no slides u=
ploaded at all. Not naming names, because the responsible person supervisin=
g that meeting was sitting in front of me, and was also noticing that lack =
of meeting materials.</div><div><br></div><div>Alternatively, if we were go=
ing to tell people it&#39;s a good plan to listen to the audio and try to s=
tay synchronized on their own copies of the slides, we could save the Meete=
cho people a lot of aggravation, and ISOC a fair amount of money.=C2=A0</di=
v><div><br></div><div>But let&#39;s not do that, OK?</div><div><br></div><d=
iv>Spencer=C2=A0</div></div></div></div>

--001a114fa266e1743e0554ac5cc4--


From nobody Wed Jul 19 07:44:50 2017
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BE58131D30 for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 07:44:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level: 
X-Spam-Status: No, score=-2.619 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] 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 UMRGLaSCn5-o for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 07:44:44 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 915C8131C08 for <ietf@ietf.org>; Wed, 19 Jul 2017 07:44:42 -0700 (PDT)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id v6JEidie008421; Wed, 19 Jul 2017 15:44:39 +0100
Received: from 950129200 (dhcp-8d56.meeting.ietf.org [31.133.141.86]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id v6JEicUr008406 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Jul 2017 15:44:38 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Spencer Dawkins at IETF'" <spencerdawkins.ietf@gmail.com>
Cc: <ietf@ietf.org>
References: <CAKKJt-ehdzREsf3QzGZ+JFOkMm-dGpSdGVFBUJE4BhqWweY+Og@mail.gmail.com> <08eb01d3006d$f0aa8a60$d1ff9f20$@olddog.co.uk> <CAKKJt-fhDgfi7UofBjmLo9xhHqjUe+tL8THs6yGYv3Cn9ETq0g@mail.gmail.com>
In-Reply-To: <CAKKJt-fhDgfi7UofBjmLo9xhHqjUe+tL8THs6yGYv3Cn9ETq0g@mail.gmail.com>
Subject: RE: Slides, eye charts, and a beg for readability
Date: Wed, 19 Jul 2017 15:44:35 +0100
Message-ID: <09d501d3009d$8b33f560$a19be020$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_09D6_01D300A5.ECFA5930"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKDsqVnxogA4fQB8x5ymF3DExiuBgI0d9K0Ar1ahBig0kZk4A==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-23204.006
X-TM-AS-Result: No--14.918-10.0-31-10
X-imss-scan-details: No--14.918-10.0-31-10
X-TMASE-MatchedRID: oCj5caaCQyk40Hl/szdmxvC1l8GignprUXlp1FHYSPU7y0F/Q/TLx7LW bXJhCVn5KPVv3SjjPZMk8VWT9a3vNCyYkC0b5PWKjoyKzEmtrEdQCOsAlaxN77rtDe4+j0ojd/d cq0rlBdQ70/blDRvoK35AOdFPgPzEouJ4645yK9DCu3097eieeclDADxBY+japoN42lMWt16aXS r9zCy3mDba6gSbbjl+QVYK+bzrDzjSxemNC+0f0HBRIrj8R47FtF9GMNu1bqLkOOZ1bT6psa7BV PFMOQQusrZgdv+SJ0/88SAvS2rKrnRue7aQeqLEsyw+ZJnFumQTskidPjB12hON+Q7elv5YPSaw iBLK6fcf9nvUckM1oVpzKEH0vVqvEnerDpp3+WMAGGKG8CG8Akh41hM/w6ZM+TdKNkxxkWRSUGH 6RuK0zz8NRz8HpCmSZEZKdSp4I705BGX7329oyQwfhKwa9GwDWq9ln3+CkiFnnK6mXN72mznuQW M5MjklgExzV+J9XRgQTt2sLHWhOSHe530PI7rwEgwM8US/pTF/r8x3wtvaXyejSyZ3UYtkAMf5J kUGtGokg8WaoMOWypJTzjwz+GzoSLzBQxkvS++L6bUMM+bbIv98fIf4wIXlFRlN8zTSzj7N2Wjb pqXgoZbTSn0tZbEPykd8OBP8tMSXBXaJoB9JZxRFJJyf5BJecmfM3DjaQLFsZUSYh+N/e/rXgnj Uztj1+TaqYly7gaERYGUjg+BCQclvoOuMIhYgRPjKtZ4ItxMQc9O2OAbbTXboNHf173bUOR2OOX UkwLhT85GlgtRz9Q==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Juk-CRYENWXcxwzVEoNWK2TDa48>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 14:44:46 -0000

This is a multipart message in MIME format.

------=_NextPart_000_09D6_01D300A5.ECFA5930
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Well,
=20
I do think that if the slides were available to be posted ahead of time, =
the chairs could make sure they are appropriate, sufficiently few in =
number, in the right font, etc., and the participants who want to could =
look at the slides in advance.
=20
To be honest, posting slides ahead of time is not rocket science and wen =
it doesn't happen it is often (barring the usual excuses) pretty =
unprofessional.
=20
Am I being overly smug?
=20
Adrian
=20
Aren't all the slides posted in the meeting materials at least 24 hours =
ahead of time to allow us to download them, use our own preferred tools, =
struggle with English not being our native language, and so on?
=20
Well, MINE were in TSVAREA, but that's not always true. I sat in one =
meeting that had no slides uploaded at all. Not naming names, because =
the responsible person supervising that meeting was sitting in front of =
me, and was also noticing that lack of meeting materials.
=20
Alternatively, if we were going to tell people it's a good plan to =
listen to the audio and try to stay synchronized on their own copies of =
the slides, we could save the Meetecho people a lot of aggravation, and =
ISOC a fair amount of money.=20
=20
But let's not do that, OK?

------=_NextPart_000_09D6_01D300A5.ECFA5930
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@01D300A5.EA934440"><!--[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;}
/* 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-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";
	mso-fareast-language:EN-US;}
@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:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-fareast-language:EN-US;}
</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'>Well,<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 do think that if the slides =
were available to be posted ahead of time, the chairs could make sure =
they are appropriate, sufficiently few in number, in the right font, =
etc., and the participants who want to could look at the slides in =
advance.<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'>To be honest, posting slides =
ahead of time is not rocket science and wen it doesn't happen it is =
often (barring the usual excuses) pretty =
unprofessional.<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'>Am I being overly =
smug?<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'>Adrian<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><div><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Aren't all the slides posted in the meeting materials at least 24 =
hours ahead of time to allow us to download them, use our own preferred =
tools, struggle with English not being our native language, and so =
on?</span><o:p></o:p></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Well, MINE were in TSVAREA, but that's not always =
true. I sat in one meeting that had no slides uploaded at all. Not =
naming names, because the responsible person supervising that meeting =
was sitting in front of me, and was also noticing that lack of meeting =
materials.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Alternatively, if we were going to tell people it's a =
good plan to listen to the audio and try to stay synchronized on their =
own copies of the slides, we could save the Meetecho people a lot of =
aggravation, and ISOC a fair amount of =
money.&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>But let's not do that, =
OK?<o:p></o:p></p></div></div></div></div></div></div></body></html>
------=_NextPart_000_09D6_01D300A5.ECFA5930--


From nobody Wed Jul 19 08:06:50 2017
Return-Path: <loa@pi.nu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8020812F268 for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 08:06:49 -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, RP_MATCHES_RCVD=-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 k7iw3F5qv4Lw for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 08:06:47 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 830A0129B15 for <ietf@ietf.org>; Wed, 19 Jul 2017 08:06:47 -0700 (PDT)
Received: from [31.133.147.14] (dhcp-930e.meeting.ietf.org [31.133.147.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id BD640180155A for <ietf@ietf.org>; Wed, 19 Jul 2017 17:06:47 +0200 (CEST)
Subject: Re: Slides, eye charts, and a beg for readability
To: ietf@ietf.org
References: <CAKKJt-ehdzREsf3QzGZ+JFOkMm-dGpSdGVFBUJE4BhqWweY+Og@mail.gmail.com> <08eb01d3006d$f0aa8a60$d1ff9f20$@olddog.co.uk> <CAKKJt-fhDgfi7UofBjmLo9xhHqjUe+tL8THs6yGYv3Cn9ETq0g@mail.gmail.com> <09d501d3009d$8b33f560$a19be020$@olddog.co.uk>
From: Loa Andersson <loa@pi.nu>
Message-ID: <b32cdd5e-1548-13dd-b00b-108998ea88c7@pi.nu>
Date: Wed, 19 Jul 2017 17:06:41 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <09d501d3009d$8b33f560$a19be020$@olddog.co.uk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AfRwB_ZB40uIBZnc05pDmi3QkeY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 15:06:49 -0000

Adrian,

I agree that it is not rocket science to get the slides in on time,
but that might be the very reason we don't see them in time.

This is in the "soon" domain!

/Loa

On 2017-07-19 16:44, Adrian Farrel wrote:
> Well,
>
>
>
> I do think that if the slides were available to be posted ahead of time,
> the chairs could make sure they are appropriate, sufficiently few in
> number, in the right font, etc., and the participants who want to could
> look at the slides in advance.
>
>
>
> To be honest, posting slides ahead of time is not rocket science and wen
> it doesn't happen it is often (barring the usual excuses) pretty
> unprofessional.
>
>
>
> Am I being overly smug?
>
>
>
> Adrian
>
>
>
> Aren't all the slides posted in the meeting materials at least 24 hours
> ahead of time to allow us to download them, use our own preferred tools,
> struggle with English not being our native language, and so on?
>
>
>
> Well, MINE were in TSVAREA, but that's not always true. I sat in one
> meeting that had no slides uploaded at all. Not naming names, because
> the responsible person supervising that meeting was sitting in front of
> me, and was also noticing that lack of meeting materials.
>
>
>
> Alternatively, if we were going to tell people it's a good plan to
> listen to the audio and try to stay synchronized on their own copies of
> the slides, we could save the Meetecho people a lot of aggravation, and
> ISOC a fair amount of money.
>
>
>
> But let's not do that, OK?
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64


From nobody Wed Jul 19 08:51:57 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D38EB131DA8 for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 08:51:46 -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, RP_MATCHES_RCVD=-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 9GpPyVwlX0Ok for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 08:51:37 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 957C1131C18 for <ietf@ietf.org>; Wed, 19 Jul 2017 08:51:29 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dXrG2-000NjZ-Td; Wed, 19 Jul 2017 11:51:26 -0400
Date: Wed, 19 Jul 2017 11:51:21 -0400
From: John C Klensin <john-ietf@jck.com>
To: adrian@olddog.co.uk
cc: 'Spencer Dawkins at IETF' <spencerdawkins.ietf@gmail.com>, ietf@ietf.org
Subject: RE: Slides, eye charts, and a beg for readability
Message-ID: <F58235813A5D5DD0E0300AB7@PSB>
In-Reply-To: <09d501d3009d$8b33f560$a19be020$@olddog.co.uk>
References: <CAKKJt-ehdzREsf3QzGZ+JFOkMm-dGpSdGVFBUJE4BhqWweY+Og@mail.gmail.com> <08eb01d3006d$f0aa8a60$d1ff9f20$@olddog.co.uk> <CAKKJt-fhDgfi7UofBjmLo9xhHqjUe+tL8THs6yGYv3Cn9ETq0g@mail.gmail.com> <09d501d3009d$8b33f560$a19be020$@olddog.co.uk>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DfquS4GrSJk2xJ0GECfrenjE6Nw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 15:51:47 -0000

--On Wednesday, July 19, 2017 15:44 +0100 Adrian Farrel
<adrian@olddog.co.uk> wrote:

> Well,
>  
> I do think that if the slides were available to be posted
> ahead of time, the chairs could make sure they are
> appropriate, sufficiently few in number, in the right font,
> etc., and the participants who want to could look at the
> slides in advance.  
> To be honest, posting slides ahead of time is not rocket
> science and wen it doesn't happen it is often (barring the
> usual excuses) pretty unprofessional.  
> Am I being overly smug?

In at least two ways, possibly so, but I'd describe it less as
"smug" than as missing part of the problem.

First, although it is rare (more rare than it should be, IMO),
there are meeting sessions in which parts of slides are
highlighted during a presentation and, more important, are
marked up in real time as the presentation goes forward.  Static
slides posted pre-meeting are a fairly poor approximation to
that.

Second, while I sympathize with Spencer's problem (and, being
both older and dimmer of vision than he is, have definitely had
it at meetings), there is another complication.  If one needs to
simultaneously follow, e.g., a Jabber session and look at the
slides, there is often a size and screen real estate management
and focus-maintaining problem with a typical laptop setup,  At
some meetings I've dealt with the problem by downloading
important the slides and printing them out, then balancing a
pile of paper on the laptop keyboard, but that has disadvantages
too (tree-killing not being the only one).

Speaking personally, while it is not high on the list of reasons
I'm not there in person, I'm actually better off from the
standpoint of slide readability when I'm sitting at home with a
desktop machine and two fairly large screens than I am in many
IETF meeting rooms.  But, even then, if I can't read the slides
through Meetecho, I start feeling as if I need three screens,
one for slides, one for Jabber, and one for whatever is going on
in Meetecho.   That is partially an element of what I thing are
some unfortunate screen layout choices with Meetecho that I
discussed with that team on and off for years but it is today's
reality.

However, more important than Spencer's vision issues (and mine),
every study of effective presentations I know of suggests
strongly that one minimize the number of text on slides, using
them to highlight only an outline or most important points, and
that slides dense enough to be read the whole presentation from
them, full-text documents, etc., tend to be distracting rather
than helpful.  I understand (and have taken advantage of) the
advantages of having relatively full text if one is trying to
work limitations in ability to understand the speaker, but that
is really something that should be dealt with as a separate
problem (and can be if we are really convinced it is important
enough).

best,
    john





From nobody Wed Jul 19 09:04:02 2017
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0494812F3CB for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 09:04:01 -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 eEW5498ZC-Ru for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 09:03:59 -0700 (PDT)
Received: from mail-yw0-x22d.google.com (mail-yw0-x22d.google.com [IPv6:2607:f8b0:4002:c05::22d]) (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 B99FD127B60 for <ietf@ietf.org>; Wed, 19 Jul 2017 09:03:59 -0700 (PDT)
Received: by mail-yw0-x22d.google.com with SMTP id x125so2477655ywa.0 for <ietf@ietf.org>; Wed, 19 Jul 2017 09:03:59 -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=bNVilhd8Ux/WBMIJyiDW2zqw2y26cIhJ9YqQxx6QGek=; b=OlzZfka5VY8Btz7Kh8tVpu9uw6JO5KvMrw98G7K5la0/a7r2qXxE177lIEpTm1PFbx hBPm5IuBK0V0SsWxFzag5HMFMEN174bMHgx+MoYsxqI1EsGAnpK1glj3U9OXLWFb+YOr Cive4nqKdnrhU6EdDhf8YJwuYm1mlSXz5seow/xCVK5ZCWpvh7/T6D2jPG9InoyRj38i ux5TRtGguv4xAgMnoN9yDFeMl2gEqce0Ped6ekAKO4oZStycoFbKeNOUZl6yapp6TWao izwp/4AmX5JkgPZ2TK/6W07TvVtW+3px0vj2/Nrk25MVk472vdDbZ+i9osWyEBJvy6HG Cvkw==
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=bNVilhd8Ux/WBMIJyiDW2zqw2y26cIhJ9YqQxx6QGek=; b=N9EtZiAG4BR80NS6m0Br52Yfi6qpPFDk3YkpsRM45Gr5b3w5qbZ0vAT/Zy+PBusv6c d45434hZIFiKwub1Xj3MV0tzz6jmTdky5r30d1UjGYPTdV8RcGOTNor9pci2O+3b7wL1 sI1/MydFPnBwoap0PijFTV+wnEcnX7jJTpQJ6c9s3mFOGErWlMe03b8kHyrxo2Vc0nli XWGvFlS34cgCKj76uo+wl3GX9fVZ7Fv/uDXQJCTGtuUvUFkEJTzk2sV3KF/ukVP/K3oB 4/vdMTiQXmUH1I2PZG9opRGSdkiXQbLtRib05evLkQ6yQLnLRq/TB02Hzv0oT2XV58ns cs7Q==
X-Gm-Message-State: AIVw111n3sCCLMy1uMMlKxbQ48tXMnhU65wdvWTYoXwOclskj4xiKA46 3cZ5J7Q4nfR5+tfmenPp0ZnYWdL1ycYW
X-Received: by 10.13.244.68 with SMTP id d65mr481193ywf.191.1500480238386; Wed, 19 Jul 2017 09:03:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.13.216.147 with HTTP; Wed, 19 Jul 2017 09:03:57 -0700 (PDT)
Received: by 10.13.216.147 with HTTP; Wed, 19 Jul 2017 09:03:57 -0700 (PDT)
In-Reply-To: <CAKKJt-ehdzREsf3QzGZ+JFOkMm-dGpSdGVFBUJE4BhqWweY+Og@mail.gmail.com>
References: <CAKKJt-ehdzREsf3QzGZ+JFOkMm-dGpSdGVFBUJE4BhqWweY+Og@mail.gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Wed, 19 Jul 2017 12:03:57 -0400
Message-ID: <CAPv4CP8UGr_xLDYW=zKQUP6mXaWgQ67JM+-_NJOvCgfOhXU2hQ@mail.gmail.com>
Subject: Re: Slides, eye charts, and a beg for readability
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
Cc: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c0356a49a7b120554adc73e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wGc16Y6GPUiCB7XDU4I2xlLZcrM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 16:04:01 -0000

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

Can't you just sit in front?

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

<div dir=3D"auto">Can&#39;t you just sit in front?=C2=A0</div>

--94eb2c0356a49a7b120554adc73e--


From nobody Wed Jul 19 10:25:14 2017
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D82BA131B74 for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 10:25:13 -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 O9kuXqfDpUYn for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 10:25:11 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (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 A8586131B6E for <ietf@ietf.org>; Wed, 19 Jul 2017 10:25:11 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id p188so6960372oia.0 for <ietf@ietf.org>; Wed, 19 Jul 2017 10:25:11 -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=AT4ZzDBTTJ5ylaFI9IrfgdbBKQ8vq1NVqq324UgUWpQ=; b=r9UkU3LbP6or4e9LVndMb7qsVvvkelqh+89f0PyARb2N7afYdLXSevee19IPYo3laR W2KmvxolYjUXmkcnpOt6eSzresX/KrCveXiGrA4h3SSz6tZ5N8fkh8Zk89pKrfaDnOqJ 7oI0jbYiKw4ec+oeNJ7hiN3ViDY3HCJaFfx8AVeMY0xQ2i1GEmsjlm/icrx6TQ9MTvFy Dz6GftGxJut6H7MH8fxX6ulPclfyhd8n+HoRa26HcivoAgtSE7pA3qASas4B6C5qejB/ xBFZwK1/37ALTbHtVDh9jc7nmlDwfaeex2KREa+XdwnfyVOoPxqfA2k9SHNELJoUQtm3 ilbQ==
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=AT4ZzDBTTJ5ylaFI9IrfgdbBKQ8vq1NVqq324UgUWpQ=; b=DEnMdfuU6j/SeQWZIB3I8x9/n0K0bA4ORJJDxawDIRrNVbYkotTnes17uPIZU5Vq+3 sDULQ7fyxQwdDnj+5N9RPhXBhhvPW0k/yaV6gLWUh61eQlhbhvzaMaNCX1Q/K3nGvEeL tdPlyBHwqtxDSX8b+F/BS6B73RCHcUEvrKryoQNoLOBAs+GMbQikw5qxD/upT5t7blht TPm/gc2Sxy78c9lSIBMVV2dXleCJCn0vlEwa2uriZE9XSJksZoVRyohb7jJ8yVtwE2tG SkGDMhd9lddFUXQ/MlEnqNULYNS9Ri40YHK8cgTScm/e5eaMXv4gkFYtmGrgwA8oZBeQ 3XyQ==
X-Gm-Message-State: AIVw111HCbvfWbbR8x/glCeN/5BRrcPpLecAP0vCCLR/P1PYNgqSOHLg 6+/xgnjn6179SYZ1P3nGnY5qfD+NM0H2
X-Received: by 10.202.59.212 with SMTP id i203mr2353613oia.104.1500485110889;  Wed, 19 Jul 2017 10:25:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.232.34 with HTTP; Wed, 19 Jul 2017 10:24:50 -0700 (PDT)
In-Reply-To: <fe950cd9-bea8-7831-046d-2f48eaaeafb9@nostrum.com>
References: <fe950cd9-bea8-7831-046d-2f48eaaeafb9@nostrum.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Wed, 19 Jul 2017 19:24:50 +0200
Message-ID: <CAA=duU21UXLo7eGUC+yRt59M-fsdyT_pRc-GJGnqOtpNBcBZuQ@mail.gmail.com>
Subject: Re: Next steps in IETF list email archiving
To: Robert Sparks <rjsparks@nostrum.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a113ccd8e0682c10554aeeaf5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DjzmquQfWxa5zQGic81didrWQqA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 17:25:14 -0000

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

Robert,

At mailarchive.ietf.org, I see a =E2=80=9CSign in=E2=80=9D button in the up=
per right.
What=E2=80=99s the advantage to signing in, and which credentials are accep=
ted, the
same as datatracker?

Thanks,
Andy


On Wed, Jul 19, 2017 at 9:43 AM, Robert Sparks <rjsparks@nostrum.com> wrote=
:

> Several years ago, we identified a set of issues with the way
> we were archiving email messages and new functionality that a
> searching and browsing solution should contain. The initial
> requirements for improvements were captured in RFC 6778, and a
> subsequent round of requirements were captured in RFC 7842.
>
> One of the key issues was (and is) related to management of
> the archives.  Currently if a message has to be removed
> (rare, but not as rare as we would like due to spam hitting
> some lists), the secretariat has to touch many places. One
> of those is Mhonarc. Touching one message there involves
> changing many files (any other message that contains a
> navigation link to this one, and the index files that speak
> about the message).
>
> As we built the new systems, we've targeted having one source
> of truth for the archives. For instance, as we added IMAP
> access to the archives (RFC 7017), we ensured that it was
> served from the same bits used by mailarchive.ietf.org.  It
> has been our expectation from the beginning that
> mailarchive.org would replace the Mhonarc archives (see
> section 2.7 of RFC 6778).
>
> We believe we are getting close to the point where we can
> make that replacement. The rate of bug reports and feature
> requests for mailarchive.ietf.org is slow. (As we do for
> the datatracker, we plan to continuously improve the
> mailarchive interface. We know already of some things that
> need to be improved when viewing on phone-sized displays.)
>
> If you use the mhonarc archives heavily, and have not yet
> explored mailarchive.ietf.org, we encourage you to do so now,
> and report any difficulties you find. We recognize that the
> experience is different, but many of the RFC 7842 driven
> improvements focused on minimizing the transition pain.
>
> We have successfully tested the code that will redirect all
> existing Mhonarc URLs into the mailarchive using the
> testlist.
>
> We are not going to make this transition immediately, but
> we do plan to make it more in the near future than the far
> future. Please help us identify any additional things we can
> do to minimize the disruption to your current workflow.
>
> RjS
>
>
>

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

<div dir=3D"ltr">Robert,<div><br></div><div>At=C2=A0<a href=3D"http://maila=
rchive.ietf.org/" rel=3D"noreferrer" target=3D"_blank" style=3D"font-size:1=
2.800000190734863px">mailarchive.ietf.org</a>, I see a =E2=80=9CSign in=E2=
=80=9D button in the upper right. What=E2=80=99s the advantage to signing i=
n, and which credentials are accepted, the same as datatracker?</div><div><=
br></div><div>Thanks,</div><div>Andy</div><div><br></div></div><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Jul 19, 2017 at 9:4=
3 AM, Robert Sparks <span dir=3D"ltr">&lt;<a href=3D"mailto:rjsparks@nostru=
m.com" target=3D"_blank">rjsparks@nostrum.com</a>&gt;</span> wrote:<br><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">Several years ago, we identified a set of issues=
 with the way<br>
we were archiving email messages and new functionality that a<br>
searching and browsing solution should contain. The initial<br>
requirements for improvements were captured in RFC 6778, and a<br>
subsequent round of requirements were captured in RFC 7842.<br>
<br>
One of the key issues was (and is) related to management of<br>
the archives.=C2=A0 Currently if a message has to be removed<br>
(rare, but not as rare as we would like due to spam hitting<br>
some lists), the secretariat has to touch many places. One<br>
of those is Mhonarc. Touching one message there involves<br>
changing many files (any other message that contains a<br>
navigation link to this one, and the index files that speak<br>
about the message).<br>
<br>
As we built the new systems, we&#39;ve targeted having one source<br>
of truth for the archives. For instance, as we added IMAP<br>
access to the archives (RFC 7017), we ensured that it was<br>
served from the same bits used by <a href=3D"http://mailarchive.ietf.org" r=
el=3D"noreferrer" target=3D"_blank">mailarchive.ietf.org</a>.=C2=A0 It<br>
has been our expectation from the beginning that<br>
<a href=3D"http://mailarchive.org" rel=3D"noreferrer" target=3D"_blank">mai=
larchive.org</a> would replace the Mhonarc archives (see<br>
section 2.7 of RFC 6778).<br>
<br>
We believe we are getting close to the point where we can<br>
make that replacement. The rate of bug reports and feature<br>
requests for <a href=3D"http://mailarchive.ietf.org" rel=3D"noreferrer" tar=
get=3D"_blank">mailarchive.ietf.org</a> is slow. (As we do for<br>
the datatracker, we plan to continuously improve the<br>
mailarchive interface. We know already of some things that<br>
need to be improved when viewing on phone-sized displays.)<br>
<br>
If you use the mhonarc archives heavily, and have not yet<br>
explored <a href=3D"http://mailarchive.ietf.org" rel=3D"noreferrer" target=
=3D"_blank">mailarchive.ietf.org</a>, we encourage you to do so now,<br>
and report any difficulties you find. We recognize that the<br>
experience is different, but many of the RFC 7842 driven<br>
improvements focused on minimizing the transition pain.<br>
<br>
We have successfully tested the code that will redirect all<br>
existing Mhonarc URLs into the mailarchive using the<br>
testlist.<br>
<br>
We are not going to make this transition immediately, but<br>
we do plan to make it more in the near future than the far<br>
future. Please help us identify any additional things we can<br>
do to minimize the disruption to your current workflow.<br>
<br>
RjS<br>
<br>
<br>
</blockquote></div><br></div>

--001a113ccd8e0682c10554aeeaf5--


From nobody Wed Jul 19 10:28:52 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 789F1131A69 for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 10:28:50 -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, MIME_QP_LONG_LINE=0.001, RP_MATCHES_RCVD=-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 GOLWFX4lbf33 for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 10:28:48 -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 3056B131B83 for <ietf@ietf.org>; Wed, 19 Jul 2017 10:28:41 -0700 (PDT)
Received: from [31.133.153.3] (dhcp-9903.meeting.ietf.org [31.133.153.3]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v6JHSbuU099320 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 19 Jul 2017 12:28:38 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host dhcp-9903.meeting.ietf.org [31.133.153.3] claimed to be [31.133.153.3]
Content-Type: multipart/alternative; boundary=Apple-Mail-4EBC9C5D-676D-4201-AD3C-4360B5578097
Mime-Version: 1.0 (1.0)
Subject: Re: Next steps in IETF list email archiving
From: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: iPhone Mail (14F89)
In-Reply-To: <CAA=duU21UXLo7eGUC+yRt59M-fsdyT_pRc-GJGnqOtpNBcBZuQ@mail.gmail.com>
Date: Wed, 19 Jul 2017 19:28:35 +0200
Cc: "ietf@ietf.org" <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <6BF4ADAA-9C58-44D7-8C3A-F0A3504CF305@nostrum.com>
References: <fe950cd9-bea8-7831-046d-2f48eaaeafb9@nostrum.com> <CAA=duU21UXLo7eGUC+yRt59M-fsdyT_pRc-GJGnqOtpNBcBZuQ@mail.gmail.com>
To: "Andrew G. Malis" <agmalis@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/U5tr3bBLX4XgPrBRCifgIv5EzW4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 17:28:50 -0000

--Apple-Mail-4EBC9C5D-676D-4201-AD3C-4360B5578097
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

Datatracker credentials. If you are on any restricted archive lists, like th=
e Iesg list, they'll show up.=20

Sent from my iPhone

> On Jul 19, 2017, at 7:24 PM, Andrew G. Malis <agmalis@gmail.com> wrote:
>=20
> Robert,
>=20
> At mailarchive.ietf.org, I see a =E2=80=9CSign in=E2=80=9D button in the u=
pper right. What=E2=80=99s the advantage to signing in, and which credential=
s are accepted, the same as datatracker?
>=20
> Thanks,
> Andy
>=20
>=20
>> On Wed, Jul 19, 2017 at 9:43 AM, Robert Sparks <rjsparks@nostrum.com> wro=
te:
>> Several years ago, we identified a set of issues with the way
>> we were archiving email messages and new functionality that a
>> searching and browsing solution should contain. The initial
>> requirements for improvements were captured in RFC 6778, and a
>> subsequent round of requirements were captured in RFC 7842.
>>=20
>> One of the key issues was (and is) related to management of
>> the archives.  Currently if a message has to be removed
>> (rare, but not as rare as we would like due to spam hitting
>> some lists), the secretariat has to touch many places. One
>> of those is Mhonarc. Touching one message there involves
>> changing many files (any other message that contains a
>> navigation link to this one, and the index files that speak
>> about the message).
>>=20
>> As we built the new systems, we've targeted having one source
>> of truth for the archives. For instance, as we added IMAP
>> access to the archives (RFC 7017), we ensured that it was
>> served from the same bits used by mailarchive.ietf.org.  It
>> has been our expectation from the beginning that
>> mailarchive.org would replace the Mhonarc archives (see
>> section 2.7 of RFC 6778).
>>=20
>> We believe we are getting close to the point where we can
>> make that replacement. The rate of bug reports and feature
>> requests for mailarchive.ietf.org is slow. (As we do for
>> the datatracker, we plan to continuously improve the
>> mailarchive interface. We know already of some things that
>> need to be improved when viewing on phone-sized displays.)
>>=20
>> If you use the mhonarc archives heavily, and have not yet
>> explored mailarchive.ietf.org, we encourage you to do so now,
>> and report any difficulties you find. We recognize that the
>> experience is different, but many of the RFC 7842 driven
>> improvements focused on minimizing the transition pain.
>>=20
>> We have successfully tested the code that will redirect all
>> existing Mhonarc URLs into the mailarchive using the
>> testlist.
>>=20
>> We are not going to make this transition immediately, but
>> we do plan to make it more in the near future than the far
>> future. Please help us identify any additional things we can
>> do to minimize the disruption to your current workflow.
>>=20
>> RjS
>>=20
>>=20
>=20

--Apple-Mail-4EBC9C5D-676D-4201-AD3C-4360B5578097
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=3D=
utf-8"></head><body dir=3D"auto"><div>Datatracker credentials. If you are on=
 any restricted archive lists, like the Iesg list, they'll show up.&nbsp;<br=
><br>Sent from my iPhone</div><div><br>On Jul 19, 2017, at 7:24 PM, Andrew G=
. Malis &lt;<a href=3D"mailto:agmalis@gmail.com">agmalis@gmail.com</a>&gt; w=
rote:<br><br></div><blockquote type=3D"cite"><div><div dir=3D"ltr">Robert,<d=
iv><br></div><div>At&nbsp;<a href=3D"http://mailarchive.ietf.org/" rel=3D"no=
referrer" target=3D"_blank" style=3D"font-size:12.800000190734863px">mailarc=
hive.ietf.org</a>, I see a =E2=80=9CSign in=E2=80=9D button in the upper rig=
ht. What=E2=80=99s the advantage to signing in, and which credentials are ac=
cepted, the same as datatracker?</div><div><br></div><div>Thanks,</div><div>=
Andy</div><div><br></div></div><div class=3D"gmail_extra"><br><div class=3D"=
gmail_quote">On Wed, Jul 19, 2017 at 9:43 AM, Robert Sparks <span dir=3D"ltr=
">&lt;<a href=3D"mailto:rjsparks@nostrum.com" target=3D"_blank">rjsparks@nos=
trum.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">Several year=
s ago, we identified a set of issues with the way<br>
we were archiving email messages and new functionality that a<br>
searching and browsing solution should contain. The initial<br>
requirements for improvements were captured in RFC 6778, and a<br>
subsequent round of requirements were captured in RFC 7842.<br>
<br>
One of the key issues was (and is) related to management of<br>
the archives.&nbsp; Currently if a message has to be removed<br>
(rare, but not as rare as we would like due to spam hitting<br>
some lists), the secretariat has to touch many places. One<br>
of those is Mhonarc. Touching one message there involves<br>
changing many files (any other message that contains a<br>
navigation link to this one, and the index files that speak<br>
about the message).<br>
<br>
As we built the new systems, we've targeted having one source<br>
of truth for the archives. For instance, as we added IMAP<br>
access to the archives (RFC 7017), we ensured that it was<br>
served from the same bits used by <a href=3D"http://mailarchive.ietf.org" re=
l=3D"noreferrer" target=3D"_blank">mailarchive.ietf.org</a>.&nbsp; It<br>
has been our expectation from the beginning that<br>
<a href=3D"http://mailarchive.org" rel=3D"noreferrer" target=3D"_blank">mail=
archive.org</a> would replace the Mhonarc archives (see<br>
section 2.7 of RFC 6778).<br>
<br>
We believe we are getting close to the point where we can<br>
make that replacement. The rate of bug reports and feature<br>
requests for <a href=3D"http://mailarchive.ietf.org" rel=3D"noreferrer" targ=
et=3D"_blank">mailarchive.ietf.org</a> is slow. (As we do for<br>
the datatracker, we plan to continuously improve the<br>
mailarchive interface. We know already of some things that<br>
need to be improved when viewing on phone-sized displays.)<br>
<br>
If you use the mhonarc archives heavily, and have not yet<br>
explored <a href=3D"http://mailarchive.ietf.org" rel=3D"noreferrer" target=3D=
"_blank">mailarchive.ietf.org</a>, we encourage you to do so now,<br>
and report any difficulties you find. We recognize that the<br>
experience is different, but many of the RFC 7842 driven<br>
improvements focused on minimizing the transition pain.<br>
<br>
We have successfully tested the code that will redirect all<br>
existing Mhonarc URLs into the mailarchive using the<br>
testlist.<br>
<br>
We are not going to make this transition immediately, but<br>
we do plan to make it more in the near future than the far<br>
future. Please help us identify any additional things we can<br>
do to minimize the disruption to your current workflow.<br>
<br>
RjS<br>
<br>
<br>
</blockquote></div><br></div>
</div></blockquote></body></html>=

--Apple-Mail-4EBC9C5D-676D-4201-AD3C-4360B5578097--


From nobody Wed Jul 19 11:48:40 2017
Return-Path: <samitac.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DCA112F28B for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 11:48:38 -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 uZYREf4lpoAs for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 11:48:36 -0700 (PDT)
Received: from mail-ua0-x233.google.com (mail-ua0-x233.google.com [IPv6:2607:f8b0:400c:c08::233]) (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 03C8312EC05 for <ietf@ietf.org>; Wed, 19 Jul 2017 11:48:36 -0700 (PDT)
Received: by mail-ua0-x233.google.com with SMTP id 80so6492874uas.0 for <ietf@ietf.org>; Wed, 19 Jul 2017 11:48:35 -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=FWpfRsxVRwCc3lDFnF63mWAzZBKpeL+/rPfIuwFD8kc=; b=SptRw12UcrU1hlX3x5AaC4wnmu85rVh0HCEUI4myGdizQ0AOLXy6dYeKsPZ3Y6RbvR uiEiq0CEsxzvN/XRxJSQx6qsACjRGi/o/yt8/LI6UX6KHlklkSP46e1vDdZc59224AGr qJ1RVnZLi1wadjMfNPKuMzZ2kJ8T6adFcHRzPZVhTGSP4XzHAGRX6v4wLerK9r+ZgP4d PpJNtoGuqPjXZpYok9wO4QI9Yxo4Y20iVtJIKHepHa4BWEZljDy3GDeXWhP98fRTpxMt IGDOeqvE+JGuKs16GP5zW14ILawkGDdMpeE/xROADUYuVm4T4h6Eyt2x05QRyk2GJZuH W9lw==
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=FWpfRsxVRwCc3lDFnF63mWAzZBKpeL+/rPfIuwFD8kc=; b=uVz/cOD/p9sjnEgYQO+TLHJzCwl58dYPdBQrrwD4HuSGty/GYGPcyuhxoBZNiGjO8j ojIHmYeIj51FmmIJJJ/5Gt9rHGj2d6oJ3tMm0vLq8ovQdMmc5hk9yohkfca/lB2Y4eDm +pmSEeHL84/tmVi10/FEKSSA3O+YAIcVlA1pqCUGZQMGhpP6NppQ6F+TCaOBquRn4s8h tWKcmutLWWt/RDCEMiMTti3q4CPv+EyCRyzm4rE0FO9/wLfoOY0h4yIYwb9Cq67xeFkB hoDACBoV+4O0QOhsrVmVapyXwSa9PsJ7Qg32SyBqbn/Z0dhVHOte7yu9430qrVLu3GdR mpow==
X-Gm-Message-State: AIVw110Cgm99ajeC1H0xzoBFjlQiBOWHuDpmQss9BRRV25+R/Mn2n0Vj X7aaZkFX6xmUaOHtFq2Ze3dE45w42w==
X-Received: by 10.31.50.129 with SMTP id y123mr601587vky.202.1500490115157; Wed, 19 Jul 2017 11:48:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.167.207 with HTTP; Wed, 19 Jul 2017 11:48:34 -0700 (PDT)
Received: by 10.31.167.207 with HTTP; Wed, 19 Jul 2017 11:48:34 -0700 (PDT)
In-Reply-To: <596F4AA7.4040905@foobar.org>
References: <fe950cd9-bea8-7831-046d-2f48eaaeafb9@nostrum.com> <17106.1500465503@dooku.sandelman.ca> <596F4AA7.4040905@foobar.org>
From: Samita Chakrabarti <samitac.ietf@gmail.com>
Date: Wed, 19 Jul 2017 11:48:34 -0700
Message-ID: <CAKmdBpdO4yE_=kJuzmBkjTqj=VcFTpGfu4cVjF4WgK_3jRq5pA@mail.gmail.com>
Subject: Re: Next steps in IETF list email archiving
To: Nick Hilliard <nick@foobar.org>
Cc: ietf@ietf.org, Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary="001a1146011e4d92c40554b014c7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/859ClogjnJgMHVXa9ZLpjjUg_cM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 18:48:38 -0000

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

+1.

I find MHonarc is much easier interface to use and better viewing
experience.

Wish mailarchive.ietf had a similar user interface. Currently, I use
MHonarc for this reason.

 -Samita

On Jul 19, 2017 5:04 AM, "Nick Hilliard" <nick@foobar.org> wrote:

without meaning to sound like a complete luddite (and top-posting for
extra effect), what Michael has written is exactly how I feel about both
systems, and I would be very unhappy to see mhonarc go.

Nick

Michael Richardson wrote:
> Robert Sparks <rjsparks@nostrum.com> wrote:
>     > If you use the mhonarc archives heavily, and have not yet explored
>     > mailarchive.ietf.org, we encourage you to do so now, and report any
>     > difficulties you find. We recognize that the experience is
different,
>     > but many of the RFC 7842 driven improvements focused on minimizing
the
>     > transition pain.
>
> I stopped using mailarchive and I almost exclusively use mhonarc
> This is now easy since the dual links in the datatracker returned.
> I was making up the correct links before, which was a pain.
>
> I find the search-only interface to mailarchive annoying, and frankly
slow.
>
> While the thread support is better, it is still not anywhere as close
> to MHonarc.  When I find an email that I care about, and I ask for the
> thread view, I get the thread for the entire list --- yes, with that
> email opened, but the entire thread is there.
> If there is a URL for that thread, I don't know it, and it is not easily
> found.
>
> Frankly, I just feel stupid interacting with an active system when I
> know a set of static files would satisfy my needs.   No matter how fast
the
> active system can be made...
>
>     > We have successfully tested the code that will redirect all existing
>     > Mhonarc URLs into the mailarchive using the testlist.
>
> neat.  I understand the desire to get rid of mhonarc.  I want mailarchive
> to succeed, but it still feels really klunky to me.
>
>     > We are not going to make this transition immediately, but we do
plan to
>     > make it more in the near future than the far future. Please help us
>     > identify any additional things we can do to minimize the disruption
to
>     > your current workflow.
>
> It would be cool if I could get an IMAP URL from mailarchive, as that
> would let me jump from searching the archives for a relevant thread,
> and right into writing a reply to it.
>

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

<div dir=3D"auto"><div>+1.</div><div dir=3D"auto"><br></div><div dir=3D"aut=
o">I find MHonarc is much easier interface to use and better viewing experi=
ence.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">Wish mailarc=
hive.ietf had a similar user interface. Currently, I use MHonarc for this r=
eason.</div><div dir=3D"auto"><br></div><div dir=3D"auto">=C2=A0-Samita<br>=
<div class=3D"gmail_extra" dir=3D"auto"><br><div class=3D"gmail_quote">On J=
ul 19, 2017 5:04 AM, &quot;Nick Hilliard&quot; &lt;<a href=3D"mailto:nick@f=
oobar.org">nick@foobar.org</a>&gt; wrote:<br type=3D"attribution"><blockquo=
te class=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">without meaning to sound like a complete luddite (and top-p=
osting for<br>
extra effect), what Michael has written is exactly how I feel about both<br=
>
systems, and I would be very unhappy to see mhonarc go.<br>
<font color=3D"#888888"><br>
Nick<br>
</font><div class=3D"elided-text"><br>
Michael Richardson wrote:<br>
&gt; Robert Sparks &lt;<a href=3D"mailto:rjsparks@nostrum.com">rjsparks@nos=
trum.com</a>&gt; wrote:<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; If you use the mhonarc archives heavily, and h=
ave not yet explored<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; <a href=3D"http://mailarchive.ietf.org" rel=3D=
"noreferrer" target=3D"_blank">mailarchive.ietf.org</a>, we encourage you t=
o do so now, and report any<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; difficulties you find. We recognize that the e=
xperience is different,<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; but many of the RFC 7842 driven improvements f=
ocused on minimizing the<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; transition pain.<br>
&gt;<br>
&gt; I stopped using mailarchive and I almost exclusively use mhonarc<br>
&gt; This is now easy since the dual links in the datatracker returned.<br>
&gt; I was making up the correct links before, which was a pain.<br>
&gt;<br>
&gt; I find the search-only interface to mailarchive annoying, and frankly =
slow.<br>
&gt;<br>
&gt; While the thread support is better, it is still not anywhere as close<=
br>
&gt; to MHonarc.=C2=A0 When I find an email that I care about, and I ask fo=
r the<br>
&gt; thread view, I get the thread for the entire list --- yes, with that<b=
r>
&gt; email opened, but the entire thread is there.<br>
&gt; If there is a URL for that thread, I don&#39;t know it, and it is not =
easily<br>
&gt; found.<br>
&gt;<br>
&gt; Frankly, I just feel stupid interacting with an active system when I<b=
r>
&gt; know a set of static files would satisfy my needs.=C2=A0 =C2=A0No matt=
er how fast the<br>
&gt; active system can be made...<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; We have successfully tested the code that will=
 redirect all existing<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Mhonarc URLs into the mailarchive using the te=
stlist.<br>
&gt;<br>
&gt; neat.=C2=A0 I understand the desire to get rid of mhonarc.=C2=A0 I wan=
t mailarchive<br>
&gt; to succeed, but it still feels really klunky to me.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; We are not going to make this transition immed=
iately, but we do plan to<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; make it more in the near future than the far f=
uture. Please help us<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; identify any additional things we can do to mi=
nimize the disruption to<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; your current workflow.<br>
&gt;<br>
&gt; It would be cool if I could get an IMAP URL from mailarchive, as that<=
br>
&gt; would let me jump from searching the archives for a relevant thread,<b=
r>
&gt; and right into writing a reply to it.<br>
&gt;<br>
<br>
</div></blockquote></div><br></div></div></div>

--001a1146011e4d92c40554b014c7--


From nobody Wed Jul 19 12:15:42 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6769C131BA9 for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 12:15:41 -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, RP_MATCHES_RCVD=-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 8_6SVsJplePt for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 12:15:39 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32A4D131BA8 for <ietf@ietf.org>; Wed, 19 Jul 2017 12:15:39 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dXuRe-000O24-8n for ietf@ietf.org; Wed, 19 Jul 2017 15:15:38 -0400
Date: Wed, 19 Jul 2017 15:15:32 -0400
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Subject: More and more virtual interims
Message-ID: <876859E45DFE49F23C5AD313@PSB>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/k9nLr3_-t2ldceHF-zYMCr1IEdc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 19:15:41 -0000

During the plenary, there was a strong pitch made for a
significantly increased number of virtual meetings, maybe even
every few weeks..  I want to play devil's advocate and point out
the downsides:

(1) We have usually thought that the IETF is at its best when
the vast majority of participants are designers, implementers,
and people with primary product responsibility rather than, at
the other extreme, professional standardizers.  For at least
some organizations, having to commit regular blocks of time (or
very long blocks of time) to specific standards work will
trigger the same sorts of "are those people too valuable to do
this or can we commit fewer or less valuable people" reviews
that are sometimes triggered by meetings in resorts or other
exotic and/or other places that are perceived as exceptionally
expensive or attractive to tourists.   In many other standards
bodies, including several whose work the IETF has treated with
some contempt in the past, there is a repeated pattern in which
the first generation of work actually engages those who
understand the architectural, design, and implementations but
later generators tend to be taken over by people whose jobs (and
skills) are in developing standards as a procedural matter
and/or protecting company interests in already-developed product
plans.  If we are inclined toward shifting toward more interim
meetings rather than emphasizing asynchronous email
communication, we should ask ourselves about the risks of
thereby shifting the profiles of the participants and the
possible consequences of doing that.

(2) Historically, we have considered active cross-area
participation and review as one of the strengths of the IETF.
As part of that, we've cited meetings that pull everyone
together for much of a week as an opportunity to get people to
drop in on WGs with which they aren't actively familiar.  That
doesn't work as well with remote participation although, if I've
set a week aside for IETF, dropping in on a WG about which I'm
merely curious is fairly easy and maybe likely.  It is quite
subjective, but my sense is that we've seen a rising percentage
of people participating in the IETF who are interested in a
single topic or even a single WG.  If we are interested in
crossfertilization across sets of skills and interests (not
merely the fallback of "area reviews" near or during IETF Last
Call), then, while we probably cannot resist tendencies toward
extreme specialization, we probably should not encourage them.
In that context, isolated interim WG meetings that people are
likely to sign up for or participate in only if they are
specifically interested in that WG and its subject matter are
likely to reinforce isolation and work that isn't seen from
other perspectives until IETF Last Call (if then). 

(3) For those for whom listing to, or expressing themselves in,
spoken English is not comfortable, an all-remote virtual interim
meeting may be even more of a barrier to full participation and
input than a mostly f2f one.  Noting other recent conversations
about slides and slide contents, that situation is even worse if
the same requirements about early posting of meeting materials
that apply to IETF f2f meetings don't apply to interims.  I note
that the IESG Statement on Interim Meetings
(https://www.ietf.org/iesg/statement/interim-meetings.html) does
not appear to impose that requirement on virtual interims (I
believe its coverage of f2f interim meetings is adequate for
that set of special issues.

None of those concerns is an argument against an occasional
interim meeting, especially when a real-time conversation may
help resolve controversial issues (and more especially where it
is possible that those issues result from misunderstandings or
miscommunication).   But, to the extent to which people are
advocating more and more interim meetings (either virtual or
f2f) as a normal way of doing business), we need to be careful
about possible side effects, most of which are not mentioned in
the IESG Statement.

   best,
    john
 


From nobody Wed Jul 19 13:07:51 2017
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5214120724 for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 13:07:46 -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, 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 m8s5LtGlJWBR for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 13:07:45 -0700 (PDT)
Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (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 E537E127ABE for <ietf@ietf.org>; Wed, 19 Jul 2017 13:07:44 -0700 (PDT)
Received: by mail-wm0-x241.google.com with SMTP id 65so1304542wmf.0 for <ietf@ietf.org>; Wed, 19 Jul 2017 13:07:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=95wKP1TP7yU4rJvWH4GX0ysczy8ds2Da0qc7avh2fBw=; b=A262wUraOje+saGBXEsBAd1JGnl7ZrCQTgRB8eARiw96clX18TxFPxqeqAbBPwrFQ3 goW8wqOQCjK+HawurWV6+HUo/ctmOvKd7MxhqT7bCYSkVVSYWtppH8OORDaCTByz3xb5 2PJHFoUdLTrz6Hce/ufQqtoYaoslxNm5xkyewu63vzCMKVcPfhpzfO0ca4LfP/qEWxe2 jYiIuAcyMqkQe7cwPiHPCAz1wR4MX24ojG5KdE56HvTmSvDSHunO/1YmIaqS0iLwlnn1 F051+PQjOO9DNRwTxgsg3X2ecYZzZfUsJSB0DxCIaxE9mrcjlhYk0qp70QEoQVxwr+j7 fIcg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=95wKP1TP7yU4rJvWH4GX0ysczy8ds2Da0qc7avh2fBw=; b=XxpaMC/tZlWklajPI2HsN008qKAX+6fjhw9yCCclWWS/lHtGlU++VXbNicfeYwuDyU 40Q1zB5JgVBucPo1S5Ra4zuFNjOr18PIiYPpkLBqzI2mqd3fCZWUGr9hXV/FRQEw9TDa x+uTP5q+sE+X+lX2vUgwtqS+hTV89aRiosh6tAlo2yOZFQHmkthasLjJLFtMaSGwcPtA jaDqc3U7X30V3tWNIfjq908I1UttKCQExEgw6oM8NkDPga1XK3XHnTW0X3+RGeJkweOc erFZO0o3V56tNB/XJ0XEIx9Es9nclHjFgeyvr5RxjX9SH0FTbboOLJAXTTv1EYfoJB9h quuA==
X-Gm-Message-State: AIVw113Gv+84ivTdEjMNH/j6UueZQTjj21B3o6CGa7+bp1zCpsdX4Ft9 WnwLgsmvojjsZt1Coh8=
X-Received: by 10.28.46.197 with SMTP id u188mr785476wmu.174.1500494863272; Wed, 19 Jul 2017 13:07:43 -0700 (PDT)
Received: from dhcp-9520.meeting.ietf.org (dhcp-9520.meeting.ietf.org. [31.133.149.32]) by smtp.gmail.com with ESMTPSA id b4sm1208628wrf.70.2017.07.19.13.07.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Jul 2017 13:07:41 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <BA5AEE60-90FA-4668-8D6F-5906723AA6C9@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_2FB101B4-45F2-4986-89AB-BDB288D7FB62"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: More and more virtual interims
Date: Wed, 19 Jul 2017 22:07:40 +0200
In-Reply-To: <876859E45DFE49F23C5AD313@PSB>
Cc: ietf@ietf.org
To: John C Klensin <john-ietf@jck.com>
References: <876859E45DFE49F23C5AD313@PSB>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/b-NDjbYhbXbwsLNHsUeX1YaGcBM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 20:07:47 -0000

--Apple-Mail=_2FB101B4-45F2-4986-89AB-BDB288D7FB62
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi, John.

I agree that over-emphasizing virtual interim meetings has its =
drawbacks, but I=E2=80=99d like to push back on your first point.

> On 19 Jul 2017, at 21:15, John C Klensin <john-ietf@jck.com> wrote:
>=20
> During the plenary, there was a strong pitch made for a
> significantly increased number of virtual meetings, maybe even
> every few weeks..  I want to play devil's advocate and point out
> the downsides:
>=20
> (1) We have usually thought that the IETF is at its best when
> the vast majority of participants are designers, implementers,
> and people with primary product responsibility rather than, at
> the other extreme, professional standardizers.  For at least
> some organizations, having to commit regular blocks of time (or
> very long blocks of time) to specific standards work will
> trigger the same sorts of "are those people too valuable to do
> this or can we commit fewer or less valuable people" reviews
> that are sometimes triggered by meetings in resorts or other
> exotic and/or other places that are perceived as exceptionally
> expensive or attractive to tourists.

Note that this is about virtual interim meetings, or as non-IETF people =
call them - conference calls. Blocking out one or two hours every two to =
three weeks is not that big a deal to employers. There is no travel =
approval, no flight, no hotel, no several day absence, no expense =
report. It=E2=80=99s a phone call (or Webex or some kind of WebRTC =
thing). This is nothing compared to a F2F meeting, where I=E2=80=99m =
gone for 5 days and have probably spent a total of one more day on all =
the stuff around that.

Your points about cross-fertilization and English stand, but a virtual =
interim is a far cheaper way (for all participants and their employers) =
to get a 1- or 2-hour slot for a WG meeting.

Yoav

--Apple-Mail=_2FB101B4-45F2-4986-89AB-BDB288D7FB62
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJZb7wMAAoJELhJCxUKWMyZf34H/1wejUezIcKPRFPYmapvNr9i
J7L/UEfsgxodehirsuKF2ltpmWVH7rJyNpw43G0ALJx4DpmzE81NhJ8TBtC8lpZH
5UO39zlCs3zYXJCvtR+itZMoMhaZhKqPtQPqRh9eD6imNyiJJg4BNaXUWXL0m1yC
xhSO6GATXeiDx60HS7tVufn71oJNywamcxkkEhyNi7TM1ZzTatyWiJJBgJigjO1q
cfgyJCnmIVKXgBdM+uaksaZO6ui5hq/ZtfYAUh+m5jUTai6waoqZXO/7FiZ7V2P8
0ropObiphLlVeXrjNozh6wlf/WIO0j5cKh7oORVDHW+o/LyanX5WZpvr/OXaMGI=
=Elkp
-----END PGP SIGNATURE-----

--Apple-Mail=_2FB101B4-45F2-4986-89AB-BDB288D7FB62--


From nobody Wed Jul 19 13:54:08 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB8A912F287 for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 13:54:06 -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 yaUk8bZV6Tr8 for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 13:54:04 -0700 (PDT)
Received: from mail-pg0-x232.google.com (mail-pg0-x232.google.com [IPv6:2607:f8b0:400e:c05::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 2526712ECEF for <ietf@ietf.org>; Wed, 19 Jul 2017 13:54:04 -0700 (PDT)
Received: by mail-pg0-x232.google.com with SMTP id v190so5109149pgv.2 for <ietf@ietf.org>; Wed, 19 Jul 2017 13:54:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=8vcXPwE8hCbm+CJpO3fGlMzuVaEgTeOHVxX6LW+E6cw=; b=HOaDFjugu9zaMBEDApBvgx+aPE8N9dWQNmLGmLqrYNV2NaF2BW5RD3KY6CbWIIBlGP JZ5IeRmKaAbErxFfJihWSPMSvo71kzT6pRwHFqTtIaXTOYmZjskimD/U8ulSMdCNDzIf 8XacssuckHVFTPZOhyRS4t7vSuTdpi4N+rUGOhuqUJx8VqCwEhpRrXbbo/9bVLB2xp1G P/MffBkJL3l1bhle8kuxoCo2CxzbQWWdv6wmJpdvSHGHt5k1HmTH5LS+DxHSlmaP62i0 2zBcF/DatKGBYNHs6kwLoJS0JjCq7OJ/yCCkgXpCgd4BfXKQp0h2f5bOOjiBG2iwegq9 nhPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=8vcXPwE8hCbm+CJpO3fGlMzuVaEgTeOHVxX6LW+E6cw=; b=hxKqC2NQlZLTb42jlhJxfH+vL6rV/h3j6eIEwhEor/tIA5zJWhCJXkI/pYLt+yGPhE JChouqyveLnHaPoCLRD/clU8UJco1ii5c1McydTtQSzuyNoHHmvxuVfxfGkBwPi2/ITk 1NYBHqQIST0FXL81Cw1K6HJAL2nPjRQ/0MLNF4cpF+d+IXqg6g6JkBDkbfI6Lr8BTdZl xerPIQX0wop2PjorNq7O+25nk71DUtXXiU0oV8MTHisQF6f4IANZ0f8keQRVz5xKmHoW o0c861e1IL6AE2v55hahzJsu0rozKsiZg4EwajRRyHtRQkWQAUH1BpE3cv58m5Ofk29L 0Wdg==
X-Gm-Message-State: AIVw110u9c6y2epgVlONY1cFZOA6NSzvJmwEtdao74LCMJxs0t8mYHNF Xsciw9HoN1CZPfMy
X-Received: by 10.101.87.205 with SMTP id q13mr1355770pgr.359.1500497643390; Wed, 19 Jul 2017 13:54:03 -0700 (PDT)
Received: from ?IPv6:2406:e001:3dad:1:28cc:dc4c:9703:6781? ([2406:e001:3dad:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id q3sm1171668pgf.69.2017.07.19.13.54.01 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Jul 2017 13:54:02 -0700 (PDT)
Subject: Re: Next steps in IETF list email archiving
To: ietf@ietf.org
References: <fe950cd9-bea8-7831-046d-2f48eaaeafb9@nostrum.com> <17106.1500465503@dooku.sandelman.ca> <596F4AA7.4040905@foobar.org> <CAKmdBpdO4yE_=kJuzmBkjTqj=VcFTpGfu4cVjF4WgK_3jRq5pA@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <ec5de4e6-5219-bea7-8e94-a40fc24e4c0c@gmail.com>
Date: Thu, 20 Jul 2017 08:54:04 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CAKmdBpdO4yE_=kJuzmBkjTqj=VcFTpGfu4cVjF4WgK_3jRq5pA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9UxJIFBY_F9Jra15RhHwbHqLeR0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 20:54:07 -0000

I find it varies. For some types of search Mhonarch is definitely better.
If I have a vague idea about when a thread occurred and a vague idea about
the subject header, paging through Mhonarch to find the thread works much
better. And then following the thread itself is pretty natural in Mhonarch.
Also, if you send someone the link they can follow the thread too.

Here's a challenge. Follow the recent threads on 6man about RFC4291bis.
It's very easy at https://www.ietf.org/mail-archive/web/ipv6/current/threads.html
It's not at all easy with the new tool. In fact I found two issues while
trying to do so:

1. I simply can't see how I'm supposed to restrict the search to the subject header.
All searches appear to be on header+body. Maybe I'm missing something?

2. I noticed that a whole thread whose subject header is "RE: <draft-ietf-6man-rfc4291bis-00.txt>"
displays in the search results as just plain "RE: ", which seems to be bug.

So if I was doing that search in real life, I would definitely use Mhonarch.

Regards
   Brian Carpenter



On 20/07/2017 06:48, Samita Chakrabarti wrote:
> +1.
> 
> I find MHonarc is much easier interface to use and better viewing
> experience.
> 
> Wish mailarchive.ietf had a similar user interface. Currently, I use
> MHonarc for this reason.
> 
>  -Samita
> 
> On Jul 19, 2017 5:04 AM, "Nick Hilliard" <nick@foobar.org> wrote:
> 
> without meaning to sound like a complete luddite (and top-posting for
> extra effect), what Michael has written is exactly how I feel about both
> systems, and I would be very unhappy to see mhonarc go.
> 
> Nick
> 
> Michael Richardson wrote:
>> Robert Sparks <rjsparks@nostrum.com> wrote:
>>     > If you use the mhonarc archives heavily, and have not yet explored
>>     > mailarchive.ietf.org, we encourage you to do so now, and report any
>>     > difficulties you find. We recognize that the experience is
> different,
>>     > but many of the RFC 7842 driven improvements focused on minimizing
> the
>>     > transition pain.
>>
>> I stopped using mailarchive and I almost exclusively use mhonarc
>> This is now easy since the dual links in the datatracker returned.
>> I was making up the correct links before, which was a pain.
>>
>> I find the search-only interface to mailarchive annoying, and frankly
> slow.
>>
>> While the thread support is better, it is still not anywhere as close
>> to MHonarc.  When I find an email that I care about, and I ask for the
>> thread view, I get the thread for the entire list --- yes, with that
>> email opened, but the entire thread is there.
>> If there is a URL for that thread, I don't know it, and it is not easily
>> found.
>>
>> Frankly, I just feel stupid interacting with an active system when I
>> know a set of static files would satisfy my needs.   No matter how fast
> the
>> active system can be made...
>>
>>     > We have successfully tested the code that will redirect all existing
>>     > Mhonarc URLs into the mailarchive using the testlist.
>>
>> neat.  I understand the desire to get rid of mhonarc.  I want mailarchive
>> to succeed, but it still feels really klunky to me.
>>
>>     > We are not going to make this transition immediately, but we do
> plan to
>>     > make it more in the near future than the far future. Please help us
>>     > identify any additional things we can do to minimize the disruption
> to
>>     > your current workflow.
>>
>> It would be cool if I could get an IMAP URL from mailarchive, as that
>> would let me jump from searching the archives for a relevant thread,
>> and right into writing a reply to it.
>>
> 


From nobody Wed Jul 19 14:07:09 2017
Return-Path: <kwatsen@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A39D812F287; Wed, 19 Jul 2017 14:07:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.801
X-Spam-Level: 
X-Spam-Status: No, score=-4.801 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_HELO_PASS=-0.001, 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=juniper.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 DGrFip6_9Mdd; Wed, 19 Jul 2017 14:07:05 -0700 (PDT)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02on0116.outbound.protection.outlook.com [104.47.37.116]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 957BB129AB2; Wed, 19 Jul 2017 14:07:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=F5CKawAGFWDy3eHj3DHGh8qHYkCC1GmTH5XPHvK2Bfc=; b=BrPuvBg/cdO4F8RcTHAmxlPp2fmqEtNgd0gYiP1WF1zhQ0jK0255cpiqy+vp2Kt2GcwAc2JaOxxraOGAR3EckesRJNk//wIx72azDWjg/vIsXUiUD2WsB2hTD/CmsBF2BTDKH+718vYv0LvHkwJA29mGy5SrT1pD0V/1vTKNbeY=
Received: from BN3PR0501MB1442.namprd05.prod.outlook.com (10.160.117.151) by BN3PR0501MB1411.namprd05.prod.outlook.com (10.160.117.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1282.4; Wed, 19 Jul 2017 21:06:59 +0000
Received: from BN3PR0501MB1442.namprd05.prod.outlook.com ([10.160.117.151]) by BN3PR0501MB1442.namprd05.prod.outlook.com ([10.160.117.151]) with mapi id 15.01.1282.011; Wed, 19 Jul 2017 21:06:59 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: =?utf-8?B?SsO8cmdlbiBTY2jDtm53w6RsZGVy?= <j.schoenwaelder@jacobs-university.de>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
CC: "draft-ietf-netconf-keystore.all@ietf.org" <draft-ietf-netconf-keystore.all@ietf.org>, "netconf@ietf.org" <netconf@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Yangdoctors last call review of draft-ietf-netconf-keystore-02
Thread-Topic: Yangdoctors last call review of draft-ietf-netconf-keystore-02
Thread-Index: AQHS/tjFB6LSB6mMA0ixt1H16U9uU6Jbyb8A
Date: Wed, 19 Jul 2017 21:06:59 +0000
Message-ID: <B1AC6895-5681-48F8-B7E7-418118120B4E@juniper.net>
References: <150028100874.32703.14161403810529927281@ietfa.amsl.com>
In-Reply-To: <150028100874.32703.14161403810529927281@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.20.0.170309
authentication-results: jacobs-university.de; dkim=none (message not signed) header.d=none;jacobs-university.de; dmarc=none action=none header.from=juniper.net;
x-originating-ip: [193.110.55.10]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN3PR0501MB1411; 7:+qcJojSOyvsg7SV4yOXkEjZP7PMQABNAi5tqtFrQJP8i65BnbSWFPTu5+sXR4WpCpGfc4op754aKcVRynQyTf8QMLhXn63RylNvq0xp27DglvISqb5di68b1NgUWOe/cbIPqJo7wKyNgsekSQrGEvOPrjLCy4PdCLF/OQNZNP6mWHuU75qOCAc7scMM5n7zaDEb9QEd7aGR/69wOs8zjogv/t9LDM8JFc5likx8uKW/bWFBfm9qyZa5PV5RkC3eitSFqDd1RW+6oNt6X67uUhWW7QuPPXuMKu7jyTYdJiSQ0w2rCon5k7TeH0YG24wr3iDie2eR+ROcs7KSwad/PQsECstHb/BuCki9ndTtOmWSycrVAyWEUmlsD7v0kDOY9wiolS3XtTYw+gbrKaWRwVACT3/sJDE/Miv7ISBnryx5/0v6p7rpOEP/dPZCxOuB3JeMw4tRrhD4wdTU+0w+9FKYIbAkY3RYVHM8owQxP8yJJdcSeLT6zxosI8OZYczJL6uUgQfSmYpmOe5RSWcRxwBF6HR4cU5wYdmqhc8egzKKD0Q2uIWAvh4SuIWjJ8YNDX4PaO1pEmwUVRbO9Nylu3gOZMC7iVsk3Sto9JurwAnV8ud1PdZthsiQ4c6UEEXROgs/SiH7fqkB73xVcgZZfGwJYOKHazpEOy3Zx/Yx6jI3pL5c2tOr1HW7lWvociK6UtfelivGnU60gdfinjLUyxbiCWINjBNFBdTm8fLEg0YOoMiK7K+ESsra7Qc8CerdVWUYtaxQcpH3HI0AQyyE2h4Fz6ROhtaEPEb2EluKPNDw=
x-ms-office365-filtering-correlation-id: 982ac265-fd0e-479a-587e-08d4ceea1890
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(48565401081)(300000503095)(300135400095)(2017052603031)(201703131423075)(201703031133081)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:BN3PR0501MB1411; 
x-ms-traffictypediagnostic: BN3PR0501MB1411:
x-exchange-antispam-report-test: UriScan:(278178393323532)(158342451672863)(133145235818549)(236129657087228)(192374486261705)(131327999870524)(48057245064654)(148574349560750)(167848164394848)(247924648384137);
x-microsoft-antispam-prvs: <BN3PR0501MB14115865224A8896FEE4490BA5A60@BN3PR0501MB1411.namprd05.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(2017060910075)(8121501046)(5005006)(100000703101)(100105400095)(93006095)(93001095)(10201501046)(3002001)(6055026)(6041248)(20161123555025)(20161123562025)(20161123564025)(20161123558100)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123560025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BN3PR0501MB1411; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BN3PR0501MB1411; 
x-forefront-prvs: 0373D94D15
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39860400002)(39850400002)(39450400003)(39400400002)(39840400002)(39410400002)(52314003)(51444003)(189998001)(8676002)(551544002)(478600001)(561944003)(4001350100001)(305945005)(53936002)(2501003)(81166006)(33656002)(38730400002)(25786009)(6486002)(86362001)(8936002)(77096006)(230783001)(5660300001)(50986999)(54356999)(2906002)(76176999)(6436002)(4326008)(14454004)(229853002)(3660700001)(66066001)(83506001)(82746002)(6506006)(3846002)(6246003)(54906002)(99286003)(6512007)(102836003)(6116002)(3280700002)(36756003)(2950100002)(2900100001)(83716003)(7736002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR0501MB1411; H:BN3PR0501MB1442.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <B03E6B73D1A7D1439A7D211625E15082@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Jul 2017 21:06:59.4770 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0501MB1411
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/t5SyAkkMtDO1Zckqbp454x3IkEQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 21:07:08 -0000

SGkgSnVlcmdlbiwNCg0KVGhhbmtzIGZvciB5b3VyIHJldmlldy4gIEJlbG93IGFyZSBteSByZXNw
b25zZXMgdG8geW91ciBjb21tZW50cy4NCg0KUFM6IHdoeSBpcyBpZXRmQGlldGYub3JnIGluIHRo
ZSBDQz8NCg0KS2VudA0KDQotLQ0KDQpSZXZpZXdlcjogSsO8cmdlbiBTY2jDtm53w6RsZGVyDQpS
ZXZpZXcgcmVzdWx0OiBOb3QgUmVhZHkNCg0KZHJhZnQtaWV0Zi1uZXRjb25mLWtleXN0b3JlLTAy
DQoNCi0gcy9ZQU5HIGRhdGEgbW9kdWxlL1lBTkcgbW9kdWxlLyBvciBzL1lBTkcgZGF0YSBtb2R1
bGUvWUFORyBtb2RlbC8NCg0KPEtFTlQ+IEZpeGVkLg0KDQotIEZpbmQgYSBiZXR0ZXIgcGhyYXNl
IGZvciAnaG9sZCBvbnRvJy4gRG9lcyB0aGUgbW9kdWxlIGFsbG93DQogIGNvbmZpZ3VyYXRpb24g
b2YgdHJ1c3RlZCBwcml2YXRlIGtleXMgYW5kIGNlcnRpZmljYXRlcz8gSWYgc28sIHNheQ0KICBz
by4NCg0KPEtFTlQ+IERvbmUuDQoNCi0gV2hhdCBpcyAnZXh0ZW5kcyBzcGVjaWFsIGNvbnNpZGVy
YXRpb24nPw0KDQo8S0VOVD4gcmV3b3JkZWQuDQoNCi0gV2hhdCBpcyBhICdzZW1pLWNvbmZpZ3Vy
YWJsZScgbGlzdD8NCg0KPEtFTlQ+IGZpeGVkIChwZXIgTWFydGluJ3MgY29tbWVudCBlYXJsaWVy
KQ0KDQotIHMvaXMgTUFZL01BWS8gKGRvZXMgdGhpcyBtYXkgbmVlZCB0byBiZSBhbGxjYXBzPykN
Cg0KPEtFTlQ+IHByZXZpb3VzbHkgZml4ZWQgYW5kIGNhc2UtbG93ZXJlZC4NCg0KLSBzL2FuIG9w
dGlvbmFsIGF0dHJpYnV0ZXMvb3B0aW9uYWwgYXR0cmlidXRlcy8NCg0KPEtFTlQ+IGZpeGVkLg0K
DQoNCi0gdGhlIG1vZHVsZSBzZWVtcyB0byB1c2UgYWN0aW9ucyBidXQgdGhlIHN1cnJvdW5kaW5n
IHRleHQgdGFsa3MgYWJvdXQgcnBjcw0KDQo8S0VOVD4gZml4ZWQuDQoNCi0gZG9lcyB0aGUgZ2Vu
ZXJhdGUtcHJpdmF0ZS1rZXkgcmVhbGx5IHRha2UgYSBrZXkgbGVuZ3RoIGFzIGEgcGFyYW1ldGVy
DQogIGFzIHByb21pc2VkIGluIHNlY3Rpb24gMj8NCg0KPEtFTlQ+IG5vIGl0IGRvZXNuJ3QgKGFu
eW1vcmUpLiBmaXhlZC4NCg0KDQotIHNlY3Rpb24gMi4yLiB0YWxrcyBhYm91dCAnZXhhbXBsZXMg
YWJvdmUnIGJ1dCB0aGVyZSBhcmUgbm9uZSAnYWJvdmUnDQoNCjxLRU5UPiBmaXhlZC4NCg0KDQot
IEhhdmUgdGhlIGV4YW1wbGVzIGJlZW4gdmFsaWRhdGVkPyBJcyByc2ExMDI0IGEgdmFsaWQgaWRl
bnRpdHlyZWYNCiAgdmFsdWU/DQoNCjxLRU5UPiBKdXN0IGRpZCwgZm91bmQgbm8gaXNzdWVzLg0K
DQoNCg0KLSBUaGVyZSBhcmUgYSBudW1iZXIgb2YgYmluYXJ5IGZpZWxkcyB3aGVyZSB5b3Ugc2hv
dyBleHBsYW5hdG9yeSB0ZXh0DQogIGluIHRoZSBleGFtcGxlcyBpbnN0ZWFkIG9mIGVuY29kZWQg
ZGF0YS4gSXMgdGhpcyBhbHdheXMgY2xlYXI/DQoNCiAgPHByaXZhdGUta2V5Pi4uLjwvcHJpdmF0
ZS1rZXk+IDwhLS0gZWxpcHNpcyBwbGFjZWhvbGRlciBmb3IgYSBiYXNlNjQgZW5jb2RlZCBrZXkg
LS0+DQoNCjxLRU5UPiBUaGlzIGlzc3VlIGhhcyBiZWVuIHJhaXNlZCBieSBvdGhlcnMgYXMgd2Vs
bC4gIEkgdXNlZCB0bw0KaGF2ZSBmdWxsIGJhc2U2NCB2YWx1ZXMsIGJ1dCBpdCBtYWRlIHRoZSBl
eGFtcGxlcyB2ZXJ5IGRpZmZpY3VsdA0KdG8gcmVhZC4gIEhtbW0sIEkgbGlrZSB5b3VyIHN1Z2dl
c3Rpb24sIGJ1dCB0aGUgcmVzdWx0aW5nIGxpbmUNCmlzIG11Y2ggbG9uZ2VyIHRoYW4gYWxsb3dl
ZC4gIEkgY291bGQgbGluZS13cmFwLCBidXQgdGhlIHJlc3VsdA0KbG9va3Mgd29yc2UuICBBbnkg
b3RoZXIgc3VnZ2VzdGlvbnM/DQoNCg0KLSBJIGFtIG5vdCBzdXJlIEkgdW5kZXJzdGFuZCB0cnVz
dGVkLWhvc3Qta2V5cy4gT24gc3lzdGVtcyB0aGF0IGhhdmUNCiAgbXVsdGlwbGUgdXNlciBhY2Nv
dW50cywgeW91IHVzdWFsbHkgaGF2ZSBhIHBlciBhY2NvdW50IGxpc3Qgb2YNCiAgdHJ1c3RlZCBo
b3N0IGtleXMgaW4gYWRkaXRpb24gdG8gYSBnbG9iYWwgc3lzdGVtIHdpZGUgbGlzdC4gUGVyaGFw
cw0KICBtYWtlIGl0IGNsZWFyIHRoYXQgdGhpcyBtb2RlbHMgdGhlIGdsb2JhbCBrbm93biBob3N0
cyBsaXN0IG9ubHk/DQoNCjxLRU5UPiBpdCdzIGEgbGlzdCBvZiBsaXN0cywgc28gdGhlcmUgY2Fu
IGJlIG1hbnkgZGlmZmVyZW50DQpzZXRzIGEgaG9zdC1rZXlzIGRlZmluZWQsIHdpdGggZWFjaCBh
cHBsaWNhdGlvbi91c2UgcG9pbnRpbmcNCnRvIGl0cyBvd24gZW50cnkuICBUaGUgaWV0Zi1zc2gt
Y2xpZW50IG1vZHVsZSdzIGdyb3VwaW5nIGhhcw0KYSBsZWFmcmVmIHRvIGEgc3BlY2lmaWMgZW50
cnkuICBGV0lXLCB0aGlzIGdyb3VwaW5nIGlzDQp1c2VkIGJ5IGlldGYtbmV0Y29uZi1jbGllbnQg
bW9kdWxlLiAgQXQgdGhlIG1vbWVudCwgdGhlcmUNCm5vIG90aGVyIHVzZXMgb2YgdGhpcyBncm91
cGluZy4gIEkgdGhpbmsgdGhhdCB5b3UgbWF5IGJlDQpnZXR0aW5nIGNvbmZ1c2VkIGJldHdlZW4g
dGhlIGtleSB0aGUgc2VydmVyIHByZXNlbnRzICh0aGUNCmhvc3Qta2V5KSB2ZXJzdXMgdGhlIGtl
eSB1c2VyIHByZXNlbnRzLg0KLg0KDQoNCi0gSXMgaXQgaGVscGZ1bCB0aGF0IHNvbWUgZXhhbXBs
ZXMgdXNlIFhNTCAvIE5FVENPTkYgd2hpbGUNCiAgb3RoZXJzIHVzZSBKU09OIC8gUkVTVENPTkYg
b3IgaXMgdGhpcyBwb3NzaWJseSBjb25mdXNpbmc/DQogIElmIHlvdSBpbmNsdWRlIEpTT04gZXhh
bXBsZXMsIGRvIHlvdSBub3QgbmVlZCB0byByZWZlcmVuY2UNCiAgUkZDIDc5NTE/DQoNCjxLRU5U
PiBJIHRob3VnaHQgdGhlcmUgd2FzIGEgY3JpdGljaXNtIGEgd2hpbGUgYmFjayB0aGF0DQpkcmFm
dHMgc2hvdWxkIHNob3cgYmFsYW5jZSBpbiB0aGVpciBleGFtcGxlcz8gIEluIHRoZSANCm1lYW53
aGlsZSwgSSByZXdvcmRlZCB0aGUgc2VudGVuY2UgdG8gbG9vayBtb3JlIGxpa2UgdGhlDQpvdGhl
ciB0d28gZXhhbXBsZXMgYW5kLCBpbiBkb2luZyBzbywgcmVtb3ZlZCB0aGUgIkpTT04NCmVuY29k
aW5nIiBzdHJpbmcgYWx0b2dldGhlci4NCg0KDQotIHMvKGMpIDIwMTQvKGMpIDIwMTcvDQoNCjxL
RU5UPiBmaXhlZCwgaW4gYWxsIG15IGRyYWZ0cy4NCg0KDQotIHJlZmVyZW5jZSBzdGF0ZW1lbnQg
b2YgdGhlIHJldmlzaW9uIHN0YXRlbWVudCBzZWVtcyB0byBoYXZlIHRoZQ0KICB3cm9uZyB0aXRs
ZQ0KDQo8S0VOVD4gZml4ZWQuDQoNCi0gU2hvdWxkIHRoZSBkb2N1bWVudCB0aXRsZSBiZSBhbGln
bmVkIHdpdGggb3RoZXIgWUFORyBtb2R1bGUNCiAgZGVmaW5pdGlvbnMsIHNvIGl0IGlzIGVhc2ll
ciB0byBzcG90IGl0Pw0KDQo8S0VOVD4gSSBkb24ndCB1bmRlcnN0YW5kLCB3aGF0IGRvIHlvdSBt
ZWFuPw0KDQoNCi0gU2luY2UgY3J5cHRvIGFsZ29yaXRobXMgY29tZSBhbmQgZ28sIGlzIGl0IHJl
YXNvbmFibGUgdG8gaGF2ZSB0aGUNCiAgaWRlbnRpdGllcyBkZWZpbmVkIGluIGEgcmF0aGVyIHN0
YXRpYyBSRkM/IFdvdWxkIGFuIElBTkEgbWFpbnRhaW5lZA0KICBpZGVudGl0eSBtb2R1bGUgcGVy
aGFwcyBtYWtlIG1vcmUgc2Vuc2U/DQoNCjxLRU5UPiBVbnN1cmUsIGJ1dCBJIHdvdWxkbid0IHN1
c3BlY3QgbmVlZGluZyB0byBtYWtlIHRoYXQNCmtpbmQgb2YgdXBkYXRlIGZvciBhIGxvbmcgdGlt
ZS4gIElmIHdlIHdlcmUgdG8gZGVmaW5lIGEgDQptb2R1bGUgZm9yIGFsZ29yaXRobSBpZGVudGl0
aWVzLCBpdCBtaWdodCBsZWFkIHRvIHVzIHdhbnRpbmcNCnRvIGRlZmluZSBldmVyeSBhbGdvcml0
aG0gKG5vdCBqdXN0IHB1YmxpYy1rZXkgYWxncyksIHdoaWNoDQpjb3VsZCB0YWtlIHNvbWUgdGlt
ZS4uLg0KDQoNCi0gT2gsIEkgbm93IHNlZSB0aGF0IHRoZSBrZXkgbGVuZ3RoIGlzIGVtYmVkZGVk
IGluIHRoZSBhbGdvcml0aG0NCiAgaWRlbnRpdHkuIFBlcmhhcHMgY2xhcmlmeSB0aGlzIGVhcmxp
ZXIsIHNlZSBteSBjb25mdXNlZCBjb21tZW50cw0KICBhYm92ZS4gQW55d2F5LCBJIHRoaW5rIHRo
aXMgbWFrZXMgdGhlIG5lZWQgZm9yIGFuIElBTkEgbWFpbnRhaW5lZA0KICBtb2R1bGUgZXZlbiBz
dHJvbmdlci4NCg0KPEtFTlQ+IHllcywgYnV0IHlvdXIgY29tbWVudCBiZWZvcmUgd2FzIHZhbGlk
LiAgSSBkb24ndCBzZWUgd2h5DQp0aGlzIG1ha2VzIGEgc3Ryb25nZXIgY2FzZSB0aG91Z2guLi4N
Cg0KDQotICJJZiBhZGRpdGlvbmFsIGFsZ29yaXRobXMgYXJlIG5lZWRlZCwgdGhleSBNQVkgYmUg
YXVnbWVudGVkIGluIGJ5DQogIGFub3RoZXIgbW9kdWxlIiBzZWVtcyBjb25mdXNpbmc7IEkgdGhp
bmsgYWxsIHRoYXQgaXMgbmVlZGVkIGlzIHRvDQogIGRlZmluZSBhIG5ldyBpZGVudGl0eSwgcmln
aHQ/IElmIHNvLCB0aGVyZSBpcyBubyBhdWdtZW50YXRpb24gaW4gdGhlDQogIFlBTkcgc2Vuc2Uu
DQoNCjxLRU5UPiBGaXhlZC4NCg0KDQotIFRoZSBkZXNjcmlwdGlvbiBvZiB0aGUga2V5c3RvcmUg
Y29udGFpbmVyIHRhbGtzIGFib3V0IHBhc3N3b3JkcyBhbmQNCiAgSSBhbSBub3Qgc3VyZSB0aGlz
IGlzIGNvcnJlY3QuIEkgYW0gYWxzbyBub3Qgc3VyZSB0aGUgdGVybXMgJ2FjdGl2ZQ0KICBtYXRl
cmlhbCcgYW5kICdwYXNzaXZlIG1hdGVyaWFsJyByZWFsbHkgaGVscC4NCg0KPEtFTlQ+IGFncmVl
ZC4gRml4ZWQuDQoNCg0KLSBUaGUgZGVzY3JpcHRpb24gb2Yga2V5cyBzYXlzICJBIGxpc3Qgb2Yg
a2V5cyBtYWludGFpbmVkIGJ5IHRoZQ0KICBrZXlzdG9yZS4iLiBJIHRoaW5rIGl0IHdvdWxkIGJl
IG1vcmUgaGVscGZ1bCB0byBzYXkgIkEgbGlzdCBvZg0KICBwdWJsaWMtcHJpdmF0ZSBrZXkgcGFp
cnMgbWFpbnRhaW5lZCBieSB0aGUga2V5c3RvcmUuIiBFdmVyeSBsaXN0DQogIGVsZW1lbnQgc2Vl
bXMgdG8gaGF2ZSB0d28ga2V5cy4NCg0KPEtFTlQ+IEZpeGVkLg0KDQotIFdoYXQgYWJvdXQgdGhl
IGNvbW1lbnQgaW4gdGhlIGRlZmluaXRpb24gb2YgYWxnb3JpdGhtLWlkZW50aWZpZXI/DQogIExv
b2tzIGxpa2UgYW4gb3BlbiBpc3N1ZSBvciBzb21ldGhpbmcgdGhhdCBzaG91bGQgYmUgcmVzb2x2
ZWQgYmVmb3JlDQogIHB1Ymxpc2hpbmcgdGhpcyBkb2N1bWVudC4NCg0KPEtFTlQ+IGNvbW1lbnQg
cmVtb3ZlZCBwZXIgTWFydGluJ3MgcmV2aWV3Lg0KDQotIEFkZCBhIHJlZmVyZW5jZSBjbGF1c2Ug
dG8gdGhlIGRlZmluaXRpb24gb2YgcHJpdmF0ZS1rZXk/IERvIHdlDQogIHJlYWxseSBuZWVkIHRo
ZSBJTkFDQ0VTU0lCTEUgZW51bSBhbmQgdGhlIHVuaW9uPyBUaGVyZSBpcyBhbm90aGVyDQogIG9w
ZW4gcXVlc3Rpb24gcmlnaHQgYmVsb3cgdGhlIHByaXZhdGUta2V5IGRlZmluaXRpb24uLi4NCg0K
PEtFTlQ+IGFkZGVkLg0KDQotIEFkZCBhIHJlZmVyZW5jZSBjbGF1c2UgdG8gdGhlIGRlZmluaXRp
b24gb2YgcHVibGljLWtleT8NCg0KPEtFTlQ+IGFkZGVkLg0KDQotIFdoeSBkbyBjZXJ0aWZpY2F0
ZSBuYW1lcyBoYXZlIHRvIGJlIHVuaXF1ZSBhY3Jvc3MgYWxsIGtleXM/DQoNCjxLRU5UPiBiZWNh
dXNlIG90aGVyd2lzZSBsZWFmcmVmcyBtaWdodCBiZSBhbWJpZ3VvdXMsIHJpZ2h0Pw0KDQoNCi0g
U2luY2UgdGhlIGNlcnRzIG9mIGEga2V5IGRvIG5vdCBjb250YWluIGEgc2lnbmF0dXJlLCB3aGVy
ZSBhcmUgc2lnbmVkDQogIGNlcnRpZmljYXRlcyBzdG9yZWQgb3IgYXJlIHRoZXkgb3V0c2lkZSB0
aGUgc2NvcGUgb2YgdGhlIG1vZGVsPw0KDQo8S0VOVD4gSSdtIGNvbmZ1c2VkLCBjZXJ0aWZpY2F0
ZXMgYXJlIHNpZ25lZCBzdHJ1Y3R1cmVzIGFscmVhZHkuLi4NCg0KDQotIEFsbCByZWZlcmVuY2Vz
IHRvIFJGQ3MgYW5kIEktRHMgaW4gZGVzY3JpcHRpb24gY2xhdXNlcyBtdXN0IHJlc29sdmUNCiAg
dG8gcmVndWxhciBjaXRhdGlvbnMgc29tZXdoZXJlIGFuZCByZWZlcmVuY2VzIGluIHRoZSByZWZl
cmVuY2VzDQogIHNlY3Rpb24uDQoNCjxLRU5UPiBGaXhlZC4NCg0KDQotIElzIHRoZXJlIGFueSB0
ZXh0IG5lZWRlZCB0byBleHBsYWluIHdoYXQgaGFwcGVucyBpZiBhY3Rpb25zIGNhbid0IGJlDQog
IGNhcnJpZWQgb3V0LCBlLmcuLCB0aGUgYWxnb3JpdGhtIGlkZW50aXR5IGlzIG5vdCBzdXBwb3J0
ZWQ/IENhbiBhDQogIGNsaWVudCBhY3R1YWxseSBsZWFybiB3aGljaCBhbGdvcml0aG0gaWRlbnRp
dGllcyBhcmUgc3VwcG9ydGVkIG9yIGlzDQogIHRoZSBhcHByb2FjaCBzaW1wbHkgdHJpYWwgYW5k
IGVycm9yPw0KDQo8S0VOVD4gSWYgYW4gYWN0aW9uIGZhaWxzLCB0aGVuIHN0YW5kYXJkIE5DL1JD
IGVycm9yIGlzIHJldHVybmVkLg0KVGhlcmUgaXMgbm8gc3VwcG9ydCB0byBsZWFybiB3aGljaCBh
bGdvcml0aG1zIGEgc2VydmVyIHN1cHBvcnRzLA0KYnV0IGJ5IHN1cHBvcnRpbmcgdGhpcyBtb2R1
bGUsIHRoZSBzZXJ2ZXIgbXVzdCBzdXBwb3J0IGFsbCBvZg0KdGhlc2UgYWxnb3JpdGhtcy4NCg0K
DQotIEkgYW0gYSBiaXQgY29uY2VybmVkIGFib3V0IHRoZSB0d28gbGlzdCBuYW1lcyAndHJ1c3Rl
ZC1jZXJ0aWZpY2F0ZXMnDQogIGFuZCAndHJ1c3RlZCBjZXJ0aWZpY2F0ZScgd2hpY2ggbWVhbiB2
ZXJ5IGRpZmZlcmVudCB0aGluZ3MgYW5kIGNhbg0KICBiZSBwb3RlbnRpYWxseSBjb25mdXNlZC4g
KFRoZSBzYW1lIGZvciAndHJ1c3RlZC1ob3N0LWtleXMnIGFuZA0KICAndHJ1c3RlZC1ob3N0LWtl
eScuKSBbTm8sIEkgZG8gbm90IGhhdmUgYSBnb29kIG5hbWluZyBwcm9wb3NhbCB0aGF0DQogIEkg
bGlrZSwgcGVyaGFwcyBzb21lIGJyYWluc3Rvcm1pbmcgaGVscHMuXQ0KDQo8S0VOVD4gb2theSwg
bGV0J3Mga2VlcCB0aGlzIG9uZSBvcGVuLg0KDQoNCi0gSSBhbSBub3Qgc3VyZSB3aGF0ICd0cnVz
dGVkIGNlcnRpZmljYXRlJyBoZXJlIHJlYWxseSBtZWFucy4gV2hhdCB5b3UNCiAgYXJlIG1vZGVs
aW5nIGlzIGEgc2V0IG9mIHNldHMgb2YgY2VydGlmaWNhdGVzLiBXaGF0IHN1Y2ggYSBzZXQgbWVh
bnMNCiAgZGVwZW5kcyBvbiB3aGVyZSB0aGlzIGxpc3QgaXMgdXNlZC4gSSBhbSBub3Qgc3VyZSB3
aGF0IGl0IG1lYW5zIGZvcg0KICBhIGNlcnRpZmljYXRlIGluIHN1Y2ggYSBzZXQgdG8gYmUgJ3Ry
dXN0ZWQnLg0KDQo8S0VOVD4geWVzLCB0aGUgY2VydHMgbWF5IGJlIHVzZWQgYnkgZGlmZmVyZW50
IG1vZHVsZXMgZm9yDQpkaWZmZXJlbnQgdXNlLWNhc2VzLCBidXQgdGhleSdkIGFsd2F5cyBiZSB0
cnVzdGVkLiAgRS5nLiwNCnRoZSBjZXJ0cyBwcmVpbnN0YWxsZWQgYnkgYSBicm93c2VyLi4uDQoN
Cg0KLSBXaGF0IGFib3V0IHRoZSAvLyByZW5hbWUgdG8gJ2RhdGEnIGNvbW1lbnQ/IEkgbGlrZSBp
dCwgcmVuYW1pbmcgdG8NCiAgbGlzdCBjZXJ0aWZpY2F0ZSB7IGtleSBuYW1lOyBsZWFmIG5hbWU7
IGxlYWYgZGF0YTsgfSBzZWVtcyBsZXNzDQogIGNvbmZ1c2luZyAoYW5kIGl0IGlzIGV2ZW4gc2hv
cnRlcikuIFBlcmhhcHMgc29tZXRoaW5nIGFsb25nIHRoaXMNCiAgbGluZSB3b3VsZCBiZSBiZXR0
ZXIgKG5vdCBzdXJlIEkgbGlrZSBjZXJ0aWZpY2F0ZS1zZXQpDQoNCgkgKy0tcncgY2VydGlmaWNh
dGUtc2V0KiBbbmFtZV0NCiAgICAgICAgIHwgICstLXJ3IG5hbWUgICAgICAgICAgICAgICAgICAg
c3RyaW5nDQogICAgICAgICB8ICArLS1ydyBkZXNjcmlwdGlvbj8gICAgICAgICAgIHN0cmluZw0K
ICAgICAgICAgfCAgKy0tcncgY2VydGlmaWNhdGUqIFtuYW1lXQ0KICAgICAgICAgfCAgICAgKy0t
cncgbmFtZSAgICBzdHJpbmcNCiAgICAgICAgIHwgICAgICstLXJ3IGRhdGE/ICAgYmluYXJ5DQoN
Cg0KPEtFTlQ+ICJzZXQiIGRvZXNuJ3Qgc291bmQgdG9vIGJhZCAtIGR1bm5vLiAgUmVnYXJkaW5n
IG1vdmluZw0KImRhdGEiLCBzZWUgdGhlIHRhaWwtZW5kIG9mIHRoZSBlbWFpbCBJIHNlbnQgb24g
SnVseSAxMS4NCg0KDQotIFdoeSBpcyB0aGUgY2VydGlmaWNhdGUgKGRhdGEpIGxlYWYgaW4gdHJ1
c3RlZC1jZXJ0aWZpY2F0ZSBub3QNCiAgbWFuZGF0b3J5PyBEb2VzIGl0IG1ha2Ugc2Vuc2UgdG8g
aGF2ZSBsaXN0IGVsZW1lbnRzIHdoZXJlIHRoZXJlDQogIGlzIG9ubHkgYSBuYW1lPw0KDQo8S0VO
VD4gSSB3YXMgc3VwcG9zZWQgdG8gYmUgbWFuZGF0b3J5LiAgRml4ZWQuDQoNCg0KLSBJIGFtIHdv
bmRlcmluZyB3aGV0aGVyIGl0IGlzIHJlYWxseSBhIGdvb2QgaWRlYSB0byBoYW5kbGUgYm90aCBY
NTA5DQogIGtleXMgYW5kIGNlcnRpZmljYXRlcyBhcyB3ZWxsIGFzIHNvbWUgU1NIIGhvc3Qga2V5
cyBpbiB0aGlzIGRvY3VtZW50Lg0KICBQZXJoYXBzIGl0IGlzIGJldHRlciB0byByZWFsbHkgc3Bs
aXQgdGhpbmdzLiBBbHNvIHRoaW5rIGFib3V0IGRldmljZXMNCiAgdGhhdCBvbmx5IGRvIFNTSCBv
ciBvbmx5IHRvIFRMUy4NCg0KPEtFTlQ+IEkgYmVsaWV2ZSB0aGF0IGl0IGlzIGNvcnJlY3QgZm9y
IHRoZSBrZXlzdG9yZSB0bw0KY29udGFpbiBhbGwgdGhlc2UgdGhpbmdzLCBhbmQgSSB0aGluayBp
dCdzIG1vc3QgcmVhZGFibGUNCmZvciB0aGVtIGFsbCB0byBiZSBkZWZpbmVkIGluIHRoaXMgZG9j
dW1lbnQuICBXaGF0IGRvDQpvdGhlcnMgdGhpbms/DQoNCg0KLSBJIGFtIG5vdCBzdXJlIEkgZnVs
bHkgdW5kZXJzdG9vZCB0aGUgY2FsbCBob21lIHN0YXRlbWVudCBpbiB0aGUNCiAgZGVzY3JpcHRp
b24gb2YgdHJ1c3RlZC1ob3N0LWtleS4gVGhpcyBwcm9iYWJseSBuZWVkcyBtb3JlIG9yIGJldHRl
cg0KICBleHBsYW5hdGlvbi4NCg0KPEtFTlQ+IGl0IHdhcyBkdW1iLCBJIHJlbW92ZWQgdGhlIHdo
b2xlIHBhcmFncmFwaC4NCg0KDQotIEFyZSBTU0ggaW1wbGVtZW50YXRpb24gZW5jb2Rpbmcga2V5
cyBpbiBBU04uMS9ERVI/IEkgZG91YnQgdGhpcyB2ZXJ5DQogIG11Y2guIFBlcmhhcHMgdGhpcyBT
U0ggc3R1ZmYgc2hvdWxkIGJlIG1vdmVkIHRvIGEgc2VwYXJhdGUgSS1EIHNpbmNlDQogIEkgYmVs
aWV2ZSB0aGlzIG5lZWRzIG1vcmUgd29yay4NCg0KPEtFTlQ+IEdvb2QgcG9pbnQuICBKdXN0IG5v
dyByZWFsaXppbmcgdGhhdCBpZXRmLXN5c3RlbSdzDQonYXV0aG9yaXplZC1rZXknIGhhcyBhIHdv
cmthYmxlIGRlZmluaXRpb24uICBJIGp1c3Qgc3dpdGNoZWQNCnRvIHVzaW5nIGl0Lg0KDQoNCg0K
LSBZb3UgY2l0ZSBSRkMgNjAyMCAoWUFORyAxKSBidXQgeW91IHVzZSBhY3Rpb25zIHdoaWNoIHdl
cmUgb25seSBhZGRlZA0KICBpbiBZQU5HIDEuMS4gSSB0aGluayB5b3Ugc2hvdWxkIG9ubHkgY2l0
ZSBZQU5HIDEuMSAoUkZDIDc5NTApLg0KIA0KPEtFTlQ+IEZpeGVkLg0KDQoNCi0gVGhlIHByZWZp
eCBpcyAna3MnIGFuZCBub3QgJ2tjJyBhcyBzdGF0ZWQgaW4gdGhlIElBTkEgY29uc2lkZXJhdGlv
bnMNCiAgc2VjdGlvbi4NCg0KPEtFTlQ+IGhvbGRvdmVyIGZyb20gd2hlbiBkcmFmdCB3YXMgY2Fs
bGVkICJrZXljaGFpbiIuICBGaXhlZC4NCg0KDQotIFNlY3VyaXR5IGNvbnNpZGVyYXRpb25zIHRh
bGsgYWJvdXQgJ1JQQyBvcGVyYXRpb25zJyBidXQgdGhlIGRhdGENCiAgbW9kZWwgYWN0dWFsbHkg
dXNlcyBhY3Rpb25zLiBQZXJoYXBzIHNpbXBseSB0YWxrIGFib3V0ICdvcGVyYXRpb25zJy4NCg0K
PEtFTlQ+IEZpeGVkLiAgKEJlbm9pdCBzaG91bGQgdXBkYXRlIGhpcyB0ZW1wbGF0ZSBhcyB3ZWxs
KQ0KDQoNCg0KDQoNCg==


From nobody Wed Jul 19 14:10:09 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D225A1270A3 for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 14:10:06 -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, RP_MATCHES_RCVD=-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 AQD5t64VWGQr for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 14:10:05 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C63EB120721 for <ietf@ietf.org>; Wed, 19 Jul 2017 14:10:05 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dXwEO-000OCd-G1; Wed, 19 Jul 2017 17:10:04 -0400
Date: Wed, 19 Jul 2017 17:09:59 -0400
From: John C Klensin <john-ietf@jck.com>
To: Yoav Nir <ynir.ietf@gmail.com>
cc: ietf@ietf.org
Subject: Re: More and more virtual interims
Message-ID: <3773E2A5945F3A70DE47C0AB@PSB>
In-Reply-To: <BA5AEE60-90FA-4668-8D6F-5906723AA6C9@gmail.com>
References: <876859E45DFE49F23C5AD313@PSB> <BA5AEE60-90FA-4668-8D6F-5906723AA6C9@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xW6ojMmaf3T4jX50uoBABiFoIIk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 21:10:07 -0000

--On Wednesday, July 19, 2017 22:07 +0200 Yoav Nir
<ynir.ietf@gmail.com> wrote:

> Hi, John.
> 
> I agree that over-emphasizing virtual interim meetings has its
> drawbacks, but I'd like to push back on your first point.
> 
>> On 19 Jul 2017, at 21:15, John C Klensin <john-ietf@jck.com>
>> wrote:
>> 
>> During the plenary, there was a strong pitch made for a
>> significantly increased number of virtual meetings, maybe even
>> every few weeks..  I want to play devil's advocate and point
>> out the downsides:
>> 
>> (1) We have usually thought that the IETF is at its best when
>> the vast majority of participants are designers, implementers,
>> and people with primary product responsibility rather than, at
>> the other extreme, professional standardizers.  For at least
>> some organizations, having to commit regular blocks of time
>> (or very long blocks of time) to specific standards work will
>> trigger the same sorts of "are those people too valuable to do
>> this or can we commit fewer or less valuable people" reviews
>> that are sometimes triggered by meetings in resorts or other
>> exotic and/or other places that are perceived as exceptionally
>> expensive or attractive to tourists.
> 
> Note that this is about virtual interim meetings, or as
> non-IETF people call them - conference calls. Blocking out one
> or two hours every two to three weeks is not that big a deal
> to employers. There is no travel approval, no flight, no
> hotel, no several day absence, no expense report. It's a
> phone call (or Webex or some kind of WebRTC thing). This is
> nothing compared to a F2F meeting, where I'm gone for 5 days
> and have probably spent a total of one more day on all the
> stuff around that.

Absolutely, but only up to a point.  Having been on both sides
of the approval process, if someone is going to do a phone call
every once in a while, it is, as you say, just a phone call.
Depending on the organization and particular roles, if it is
going to be a regular hour or two commitment every couple of
weeks, that may starts to be another issue, even though there
is, as you point out, no travel approval, flights, hotels, etc.
For just the latter reasons, if an interim meeting is needed,
there is absolutely no question that a virtual one is going to
mean less organizational stress, etc., than a physical one.

FWIW, I also believe that, as we get better at interim meetings,
conference calls, etc., we should be able to consider cutting
back week-long f2f meetings to maybe two per year rather than
three, with the advantages again being the ones you cite.

> Your points about cross-fertilization and English stand, but a
> virtual interim is a far cheaper way (for all participants and
> their employers) to get a 1- or 2-hour slot for a WG meeting.

Agreed.  What I'm trying to push on a bit is the assumption that
I thought I heard during the plenary, i.e., that interim
meetings, in quantity, should be encouraged as a better way to
do work than email and occasional "everyone gets together" IETF
plenaries.  It is, to me, a matter of finding and keeping the
right balance, rather than going overboard on any one approach.

best,
    john




From nobody Wed Jul 19 15:20:41 2017
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17838127978 for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 15:20:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 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_MED=-2.3, RP_MATCHES_RCVD=-0.001, 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=ecs.soton.ac.uk
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 RrYGW7UCfopy for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 15:20:32 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3331D1270A7 for <ietf@ietf.org>; Wed, 19 Jul 2017 15:20:32 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6JMJrwq030824; Wed, 19 Jul 2017 23:19:53 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v6JMJrwq030824
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1500502793; bh=z1A+nAk4dBdIJe5XCf16s9JQl2k=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=5OaiE8sYAAqp70+1o+Wp254PuZrQBJQvFQTqF4va2yJBOOrOj2BiHC4IW7je9RAGU xNElFIfbqeN5BkJbsH80F4aGm3BnZld4WmZ0lo3D32X24UCNUigWl8C2cwxl3iqPTt TzZ7qA4SAv0yzLh4aUaudT+FFNFH36uEcOCuJDuk=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id y6INJq06604124455n ret-id none; Wed, 19 Jul 2017 23:19:53 +0100
Received: from [IPv6:2001:67c:1232:144:c036:d443:acdf:6b3d] ([IPv6:2001:67c:1232:144:c036:d443:acdf:6b3d]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6JMJiG5029061 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Jul 2017 23:19:45 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Next steps in IETF list email archiving
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <ec5de4e6-5219-bea7-8e94-a40fc24e4c0c@gmail.com>
Date: Wed, 19 Jul 2017 23:19:44 +0100
Cc: ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|c18f8c8042eb51bd441730ebc1190d98y6INJq03tjc|ecs.soton.ac.uk|D61B9ED0-09EE-44D2-B642-D10ADED0144B@ecs.soton.ac.uk>
References: <fe950cd9-bea8-7831-046d-2f48eaaeafb9@nostrum.com> <17106.1500465503@dooku.sandelman.ca> <596F4AA7.4040905@foobar.org> <CAKmdBpdO4yE_=kJuzmBkjTqj=VcFTpGfu4cVjF4WgK_3jRq5pA@mail.gmail.com> <ec5de4e6-5219-bea7-8e94-a40fc24e4c0c@gmail.com> <D61B9ED0-09EE-44D2-B642-D10ADED0144B@ecs.soton.ac.uk>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3273)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-ECS-MailScanner-SpamScore: ssss
X-smtpf-Report: sid=y6INJq066041244500; tid=y6INJq06604124455n; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v6JMJrwq030824
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pIpxqjjsejJ5WWRbL6R9jbla3xI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 22:20:35 -0000

> On 19 Jul 2017, at 21:54, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>=20
> I find it varies. For some types of search Mhonarch is definitely =
better.
> If I have a vague idea about when a thread occurred and a vague idea =
about
> the subject header, paging through Mhonarch to find the thread works =
much
> better. And then following the thread itself is pretty natural in =
Mhonarch.
> Also, if you send someone the link they can follow the thread too.
>=20
> Here's a challenge. Follow the recent threads on 6man about =
RFC4291bis.
> It's very easy at =
https://www.ietf.org/mail-archive/web/ipv6/current/threads.html
> It's not at all easy with the new tool. In fact I found two issues =
while
> trying to do so:
>=20
> 1. I simply can't see how I'm supposed to restrict the search to the =
subject header.
> All searches appear to be on header+body. Maybe I'm missing something?
>=20
> 2. I noticed that a whole thread whose subject header is "RE: =
<draft-ietf-6man-rfc4291bis-00.txt>"
> displays in the search results as just plain "RE: ", which seems to be =
bug.
>=20
> So if I was doing that search in real life, I would definitely use =
Mhonarch.

A good summary, and my strong preference also.

Tim

>=20
> Regards
>   Brian Carpenter
>=20
>=20
>=20
> On 20/07/2017 06:48, Samita Chakrabarti wrote:
>> +1.
>>=20
>> I find MHonarc is much easier interface to use and better viewing
>> experience.
>>=20
>> Wish mailarchive.ietf had a similar user interface. Currently, I use
>> MHonarc for this reason.
>>=20
>> -Samita
>>=20
>> On Jul 19, 2017 5:04 AM, "Nick Hilliard" <nick@foobar.org> wrote:
>>=20
>> without meaning to sound like a complete luddite (and top-posting for
>> extra effect), what Michael has written is exactly how I feel about =
both
>> systems, and I would be very unhappy to see mhonarc go.
>>=20
>> Nick
>>=20
>> Michael Richardson wrote:
>>> Robert Sparks <rjsparks@nostrum.com> wrote:
>>>> If you use the mhonarc archives heavily, and have not yet explored
>>>> mailarchive.ietf.org, we encourage you to do so now, and report any
>>>> difficulties you find. We recognize that the experience is
>> different,
>>>> but many of the RFC 7842 driven improvements focused on minimizing
>> the
>>>> transition pain.
>>>=20
>>> I stopped using mailarchive and I almost exclusively use mhonarc
>>> This is now easy since the dual links in the datatracker returned.
>>> I was making up the correct links before, which was a pain.
>>>=20
>>> I find the search-only interface to mailarchive annoying, and =
frankly
>> slow.
>>>=20
>>> While the thread support is better, it is still not anywhere as =
close
>>> to MHonarc.  When I find an email that I care about, and I ask for =
the
>>> thread view, I get the thread for the entire list --- yes, with that
>>> email opened, but the entire thread is there.
>>> If there is a URL for that thread, I don't know it, and it is not =
easily
>>> found.
>>>=20
>>> Frankly, I just feel stupid interacting with an active system when I
>>> know a set of static files would satisfy my needs.   No matter how =
fast
>> the
>>> active system can be made...
>>>=20
>>>> We have successfully tested the code that will redirect all =
existing
>>>> Mhonarc URLs into the mailarchive using the testlist.
>>>=20
>>> neat.  I understand the desire to get rid of mhonarc.  I want =
mailarchive
>>> to succeed, but it still feels really klunky to me.
>>>=20
>>>> We are not going to make this transition immediately, but we do
>> plan to
>>>> make it more in the near future than the far future. Please help us
>>>> identify any additional things we can do to minimize the disruption
>> to
>>>> your current workflow.
>>>=20
>>> It would be cool if I could get an IMAP URL from mailarchive, as =
that
>>> would let me jump from searching the archives for a relevant thread,
>>> and right into writing a reply to it.
>>>=20
>>=20
>=20


From nobody Wed Jul 19 22:29:03 2017
Return-Path: <lloyd.wood@yahoo.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D736F12783A for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 22:29:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.491
X-Spam-Level: 
X-Spam-Status: No, score=-2.491 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_MUA_MOZILLA=2.309, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.co.uk
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 HhdKn01mcvE4 for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 22:29:00 -0700 (PDT)
Received: from sonic307-10.consmr.mail.ir2.yahoo.com (sonic307-10.consmr.mail.ir2.yahoo.com [87.248.110.35]) (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 57EF8126B6E for <ietf@ietf.org>; Wed, 19 Jul 2017 22:29:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s2048;  t=1500528538; bh=q92ljQXrUW1j0T9yFxlpyXZEBVkeOZJnI8IG+K9EJhk=;  h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject;  b=tHH1wF8xlIVfskSqoP5AgdvYrKnaf5DFlIv2ovaLmOOYI/F9B4k8abtDWUe8YZJe8h/YPwm2PUm2MNmZOvn0QXaBFkQzIxirGfpCkXWP1n9zwWTdCwHTI0AAZSN6m0EGpnvhXHlD8AnJnE1oPLbVWYtVl8Xb7wRvVwW5/wipbI87K9dC7kluwxjRIg4wszsG5nysb4cYnZAucj0je5dm4LBqx7t+6edXgG9CNDxa6G6hExgJJfmfvnCZBWLbLFhFo/+cd+pqwIrYOhFOYLZZBvtva4VayLkN782h9J8SflCkPS5CkhEBKWWh9cWruPLwFsIkhwx4uaZC+SHiK69vvQ==
X-YMail-OSG: Taq.ObUVM1nUalWVWz6f6dGjVI3T6FWA4CNKJy28mwZSKtFkRCKthqDPTTb0mgr W58yH_gCoR7T7z3IBykJ3hgGyLHJvP5PiuG6GZiEOd6ANKLz99rLmlWDFVKc.QY6ipnaGnGQryb3 _s6YFiNkuw6sQ3TZtLJ0N0MQkH590nQhHzEzyez7TI7tEKGaUwI8NYYGztUCSyzpX6G82bw2jbN2 8U1CTosp07qbGAprQBwoNjJI6BJRl5lN2j6d6R3PvK4rvs7IAsUi3F8BW6J7VGYvYBTV_z3s1jR1 3cPfGeCeG_NY2N7MCS4Len.PWVOX0MhNVR_5Dlt0yooxFnq0ZFpnDwDUxWQLZbzJ3Jhrf_zUrQMp iLxRFfonTpi0vhYT4LWhH6mEeVtBi21ku_mZjyXUptlznPhBQch7n.blwxlgMRXEtuj_38YGLAvT mKn145unLJBqeOgYUNvvJbaf73qNqQLa3EtN0je7zOrjoqfe0v6tpAGAUmyvlT34fAFz_U2faxgp wk2x2Z2KuGNPEjUHp1Gxy_Mzeu3oT3hfuKOuTTDL9YnDa5jcmIfjt
Received: from sonic.gate.mail.ne1.yahoo.com by sonic307.consmr.mail.ir2.yahoo.com with HTTP; Thu, 20 Jul 2017 05:28:58 +0000
Date: Thu, 20 Jul 2017 05:28:57 +0000 (UTC)
From: Lloyd Wood <lloyd.wood@yahoo.co.uk>
Reply-To: Lloyd Wood <lloyd.wood@yahoo.co.uk>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>,  'Spencer Dawkins at IETF' <spencerdawkins.ietf@gmail.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <2107809846.1308501.1500528537111@mail.yahoo.com>
In-Reply-To: <09d501d3009d$8b33f560$a19be020$@olddog.co.uk>
References: <CAKKJt-ehdzREsf3QzGZ+JFOkMm-dGpSdGVFBUJE4BhqWweY+Og@mail.gmail.com> <08eb01d3006d$f0aa8a60$d1ff9f20$@olddog.co.uk> <CAKKJt-fhDgfi7UofBjmLo9xhHqjUe+tL8THs6yGYv3Cn9ETq0g@mail.gmail.com> <09d501d3009d$8b33f560$a19be020$@olddog.co.uk>
Subject: Re: Slides, eye charts, and a beg for readability
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Mailer: WebService/1.1.10121 YahooMailNeo Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_YYr8bjBC5Q7Jg-g8Yk9bLyzSP4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 05:29:02 -0000

> in the right font,


the correct single font choice for the IETF is original
twelve-point monospace Courier.

obviously. 
Lloyd Wood lloyd.wood@yahoo.co.uk http://about.me/lloydwood 



________________________________
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Spencer Dawkins at IETF' <spencerdawkins.ietf@gmail.com> 
Cc: ietf@ietf.org
Sent: Thursday, 20 July 2017, 0:45
Subject: RE: Slides, eye charts, and a beg for readability



Well,
 
I do think that if the slides were available to be posted ahead of time, the chairs could make sure they are appropriate, sufficiently few in number, in the right font, etc., and the participants who want to could look at the slides in advance.
 
To be honest, posting slides ahead of time is not rocket science and wen it doesn't happen it is often (barring the usual excuses) pretty unprofessional.
 
Am I being overly smug?
 
Adrian
 
Aren't all the slides posted in the meeting materials at least 24 hours ahead of time to allow us to download them, use our own preferred tools, struggle with English not being our native language, and so on?
 
Well, MINE were in TSVAREA, but that's not always true. I sat in one meeting that had no slides uploaded at all. Not naming names, because the responsible person supervising that meeting was sitting in front of me, and was also noticing that lack of meeting materials.
 
Alternatively, if we were going to tell people it's a good plan to listen to the audio and try to stay synchronized on their own copies of the slides, we could save the Meetecho people a lot of aggravation, and ISOC a fair amount of money. 
 
But let's not do that, OK?


From nobody Wed Jul 19 22:35:56 2017
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37437126B6E for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 22:35:55 -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] 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 Wcc3ivhdjvvH for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 22:35:53 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 C167D12783A for <ietf@ietf.org>; Wed, 19 Jul 2017 22:35:53 -0700 (PDT)
Received: from [10.47.60.81] (dhcp-9976.meeting.ietf.org [31.133.153.118]) (authenticated bits=0) by mail.proper.com (8.15.2/8.14.9) with ESMTPSA id v6K5Z08r016782 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 19 Jul 2017 22:35:04 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host dhcp-9976.meeting.ietf.org [31.133.153.118] claimed to be [10.47.60.81]
From: "Paul Hoffman" <paul.hoffman@vpnc.org>
To: "Robert Sparks" <rjsparks@nostrum.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Next steps in IETF list email archiving
Date: Thu, 20 Jul 2017 07:35:46 +0200
Message-ID: <A547C358-3E70-4991-B6A9-03A6320D1285@vpnc.org>
In-Reply-To: <fe950cd9-bea8-7831-046d-2f48eaaeafb9@nostrum.com>
References: <fe950cd9-bea8-7831-046d-2f48eaaeafb9@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.6r5347)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7tpPLc1F0kv6YmxPFtnvt27qerU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 05:35:55 -0000

I apologize in advance for this engineering solution, but given how many 
people are saying "I prefer/need the MHonArc archives":

On 19 Jul 2017, at 9:43, Robert Sparks wrote:

> One of the key issues was (and is) related to management of
> the archives.  Currently if a message has to be removed
> (rare, but not as rare as we would like due to spam hitting
> some lists), the secretariat has to touch many places. One
> of those is Mhonarc. Touching one message there involves
> changing many files (any other message that contains a
> navigation link to this one, and the index files that speak
> about the message).

You may be over-touching. If someone needs a message "removed", you can 
leave the message in-place and simply change to content to "Message 
content removed" in the one file. No links are broken, no indexes need 
to be regenerated. (I did this for a while at VPNC.)

--Paul Hoffman


From nobody Wed Jul 19 22:52:06 2017
Return-Path: <blong@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3C8C131803 for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 22:52:00 -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, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 jrzVi2YcLcI7 for <ietf@ietfa.amsl.com>; Wed, 19 Jul 2017 22:51:59 -0700 (PDT)
Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003: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 4A8B112783A for <ietf@ietf.org>; Wed, 19 Jul 2017 22:51:59 -0700 (PDT)
Received: by mail-oi0-x229.google.com with SMTP id 191so18633526oii.2 for <ietf@ietf.org>; Wed, 19 Jul 2017 22:51:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=A7FSdXNYTDn8sxG4aJ4KarDk6Dzyw4AW+FD243jJG9E=; b=g260iEAChURE3KoFoM7QXWs2Qdxf+ERyw6LVr8wvA4gypYVAURz/xtrilVxUivS6Qo Xr3IDOVf2Df4/mHlod0jP0rzvsRcmZeTnMKIIjdrZtxc63wvRvFUDVnieLgCgmWflyDn Dv0gLmcR0V/ya7NX698fm83jCx/yv+N7A7EEM7MtxigPxH7zShH6WjRcEtalDVYRpevY d2qfaoSAwf4QZ++N4K4QEl2DMmB+mz0uqErZ9wBSISmD1MUt1l4EMtVltM+0nVxCSwdh pD5JXCEC85qzsijpEyYNIRcTkjCC3py4JF4Ou/wGmMM5iqGXLsDG3fG8M0WHWFmf9f4C dyIg==
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=A7FSdXNYTDn8sxG4aJ4KarDk6Dzyw4AW+FD243jJG9E=; b=aX3T8fXgaC4DrPUFmmAaTlVBx6cN3XWSVZikGhSqNuCVVWJfGuaNDBNgKd6y6+7BVT lTfGezZSJnsjoHfbZfVnMcbwFXwG8FvqcOaXY/iYBRMg8HBVTD6PWfFg4sQnpN2NYGBm sbrMvDitFVX7UqVh7h3XtqGZr+v7FFXqTlpsBQZN7LYa8DiWur6672JZ4Nm2UkOvAvo4 hougW296uqK3MSoGVdqP7segD0terxByspoqaa0uWxQnVtFN4uiZnUHjKmlYjPA2c5gk 3bJZwvlRUM9Yjo4FXxmAHuuTU65NJaHwhmDNdtzt2GOJkyJa1GK5GKp9hQGsLLbh5yzk wdPA==
X-Gm-Message-State: AIVw110cCIJ5QWhOF83WimVS5hcPG7A3fiG0lUuSa1xMlrWzjva7ufjs pnNtbk/UTyM3Ayx02AUXeB0EzKrgWRMi6Jk=
X-Received: by 10.202.227.193 with SMTP id a184mr4427803oih.121.1500529918216;  Wed, 19 Jul 2017 22:51:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.78.69 with HTTP; Wed, 19 Jul 2017 22:51:54 -0700 (PDT)
Received: by 10.74.78.69 with HTTP; Wed, 19 Jul 2017 22:51:54 -0700 (PDT)
In-Reply-To: <A547C358-3E70-4991-B6A9-03A6320D1285@vpnc.org>
References: <fe950cd9-bea8-7831-046d-2f48eaaeafb9@nostrum.com> <A547C358-3E70-4991-B6A9-03A6320D1285@vpnc.org>
From: Brandon Long <blong@google.com>
Date: Wed, 19 Jul 2017 22:51:54 -0700
Message-ID: <CABa8R6twqYXHerdy=h0tCO=8dhRAmvgQ6D3L2yOBgQ_jzVFtoQ@mail.gmail.com>
Subject: Re: Next steps in IETF list email archiving
To: Paul Hoffman <paul.hoffman@vpnc.org>
Cc: Robert Sparks <rjsparks@nostrum.com>, IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a1141729cc08cdd0554b95816"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XEKkAZc9nUZJGC0XEL_d4NhSBN4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 05:52:01 -0000

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

If we're now storing messages in some datastore, wouldn't it be possible to
generate mhonarc like pages on the fly?

Brandon

On Jul 19, 2017 10:36 PM, "Paul Hoffman" <paul.hoffman@vpnc.org> wrote:

> I apologize in advance for this engineering solution, but given how many
> people are saying "I prefer/need the MHonArc archives":
>
> On 19 Jul 2017, at 9:43, Robert Sparks wrote:
>
> One of the key issues was (and is) related to management of
>> the archives.  Currently if a message has to be removed
>> (rare, but not as rare as we would like due to spam hitting
>> some lists), the secretariat has to touch many places. One
>> of those is Mhonarc. Touching one message there involves
>> changing many files (any other message that contains a
>> navigation link to this one, and the index files that speak
>> about the message).
>>
>
> You may be over-touching. If someone needs a message "removed", you can
> leave the message in-place and simply change to content to "Message content
> removed" in the one file. No links are broken, no indexes need to be
> regenerated. (I did this for a while at VPNC.)
>
> --Paul Hoffman
>
>

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

<div dir=3D"auto">If we&#39;re now storing messages in some datastore, woul=
dn&#39;t it be possible to generate mhonarc like pages on the fly?<div dir=
=3D"auto"><br></div><div dir=3D"auto">Brandon</div></div><div class=3D"gmai=
l_extra"><br><div class=3D"gmail_quote">On Jul 19, 2017 10:36 PM, &quot;Pau=
l Hoffman&quot; &lt;<a href=3D"mailto:paul.hoffman@vpnc.org">paul.hoffman@v=
pnc.org</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">I apologize in advance for this engineering solution, but given how many=
 people are saying &quot;I prefer/need the MHonArc archives&quot;:<br>
<br>
On 19 Jul 2017, at 9:43, Robert Sparks wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
One of the key issues was (and is) related to management of<br>
the archives.=C2=A0 Currently if a message has to be removed<br>
(rare, but not as rare as we would like due to spam hitting<br>
some lists), the secretariat has to touch many places. One<br>
of those is Mhonarc. Touching one message there involves<br>
changing many files (any other message that contains a<br>
navigation link to this one, and the index files that speak<br>
about the message).<br>
</blockquote>
<br>
You may be over-touching. If someone needs a message &quot;removed&quot;, y=
ou can leave the message in-place and simply change to content to &quot;Mes=
sage content removed&quot; in the one file. No links are broken, no indexes=
 need to be regenerated. (I did this for a while at VPNC.)<br>
<br>
--Paul Hoffman<br>
<br>
</blockquote></div></div>

--001a1141729cc08cdd0554b95816--


From nobody Thu Jul 20 05:08:32 2017
Return-Path: <ralf.weber@nominum.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D3A92131C1A; Thu, 20 Jul 2017 05:08:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ralf Weber <ralf.weber@nominum.com>
To: <int-dir@ietf.org>
Cc: dhcwg@ietf.org, ietf@ietf.org, draft-ietf-dhc-relay-port.all@ietf.org
Subject: Intdir early review of draft-ietf-dhc-relay-port-05
X-Test-IDTracker: no
X-IETF-IDTracker: 6.57.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150055249283.9589.17482424577250077220@ietfa.amsl.com>
Date: Thu, 20 Jul 2017 05:08:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OFPvyVg9yn3EBMHC_BLrKxBryjM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 12:08:13 -0000

Reviewer: Ralf Weber
Review result: Ready with Nits

Moin!

I reviewed this document and I'm good with it. The only minor purely cosmetic
note is that it took me some time to understand why you record the port for the
IPv6 relay chain. According to a discussion I had with Bernie that is to be
able to have the agent stateless. Maybe add that to the motivation why you
store it in the packet at the end of section 4 (, to allow stateless operation
in a relay chain)

So long
-Ralf



From nobody Thu Jul 20 05:56:33 2017
Return-Path: <sean@sn3rd.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8A9812EB99 for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 05:56:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.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 LkMoS6qszzXP for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 05:56:24 -0700 (PDT)
Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::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 0E66F126E3A for <ietf@ietf.org>; Thu, 20 Jul 2017 05:56:23 -0700 (PDT)
Received: by mail-io0-x22e.google.com with SMTP id g13so11165803ioj.5 for <ietf@ietf.org>; Thu, 20 Jul 2017 05:56:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ZpOV5yQnuIMbccJmdSjHaIDgG52aNf67l3VNHMrR6IQ=; b=UQact3eO6u46/a1w5xobCrYytnAgnvgSHRcPjEUVyYuJEquT55Rw6F4V+xnRbFCgCw daH9llCjh7dDkQFCYutzd+8ivXOBeW+4SoFmFBlb8YVpDP6uaq1UBnN8Njg7wA+gTHZJ uObGYjZQq6Lf3ou4rl/5ro8KIZzKRrOIn7L7k=
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=ZpOV5yQnuIMbccJmdSjHaIDgG52aNf67l3VNHMrR6IQ=; b=i08Imq/uN/TpVRbKYI78D03PZCR3MbXm1oTDJYmwWy195E69Pdyq6FjqDWJgL3f+o+ diE5vc9Bkvv52twZ2u+UhQqmgPnun7R+IL/MsKDmsC+pUKNZB62x7BW4WPrYzXFnURBx roV03HVCqdxfUag8dqalCPtqV2Gt0TBMMWkKIGAsAbSkn0gnVmhGS73J3V3VAHKRZ3cA xMOgIX6mbRlQPssRxiafGfSes7l0S9t3EcpX5gUt8bkjzU8xzVeGj9WDKW3utsLPvhcm Cpfi7hEPD5FzwyVEo2CUpQe/Yb+tQ5FJdrKcneKGOlVapwPK/IJiNlmGE07cUoAcoQoe YFAQ==
X-Gm-Message-State: AIVw1112BunVmNgLIkyRvXkA2DED3xSVpoaJIF/oHv/rOovqNrYpQeIa oGJDK36XAA7NMxQg
X-Received: by 10.107.139.215 with SMTP id n206mr959821iod.31.1500555382412; Thu, 20 Jul 2017 05:56:22 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:128:9123:f1a6:1b8b:dae4? ([2001:67c:370:128:9123:f1a6:1b8b:dae4]) by smtp.gmail.com with ESMTPSA id y186sm574899ity.42.2017.07.20.05.56.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Jul 2017 05:56:21 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Genart telechat review of draft-turner-est-extensions-08
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <149972493112.12836.11322162271657108676@ietfa.amsl.com>
Date: Thu, 20 Jul 2017 14:56:17 +0200
Cc: gen-art@ietf.org, ietf@ietf.org, draft-turner-est-extensions.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <D606B61C-73C4-4FA8-BE0B-F7BFB704F5DB@sn3rd.com>
References: <149972493112.12836.11322162271657108676@ietfa.amsl.com>
To: Vijay Gurbani <vijay.gurbani@nokia.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ocz12iGiMte3zXsYxGaO1ITYmek>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 12:56:26 -0000

> On Jul 11, 2017, at 00:15, Vijay Gurbani <vijay.gurbani@nokia.com> =
wrote:
>=20
> Reviewer: Vijay Gurbani
> 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-turner-est-extensions-??
> Reviewer: Vijay Gurbani
> Review Date: 2017-07-10
> IETF LC End Date: 2017-07-11
> IESG Telechat date: Not scheduled for a telechat
>=20
> Summary: Ready with nits.
>=20
> Major issues: 0
>=20
> Minor issues: 1
>=20
> Nits/editorial comments: 2
>=20
> Minor:
> - S2, I understand that a PAL may be represented as a XML file or a =
JSON
> object, but I note that the underlying semantic content of the =
resource,
> irrespective of representation as shown in Sections 2.1.2 and 2.1.3 is
> different.  I suspect that is by design, but could not figure out why =
the
> XML and JSON resource would have different semantic content.

s2.1.2 is XML schema.  There=E2=80=99s no schema in JSON so that=E2=80=99s=
 why there a little different.

> Nits:
> - S1, top of page 5: What is TA?  The expansion is not defined before =
being
> used here for the first time; I suspect it is "Trust Anchor", but may =
help
> to expand it here rather than in S7.

TA =3D Trust Anchor - it=E2=80=99s expanded on p4 in the /crls bullet. =
;)

> - S1.1, "air gap" --- I understand what it means from rfc4949, but =
someone
> not familiar (or too lazy to look up rfc4949 or simply much too =
younger than
> us) may assume that "air gap" refers to "wifi".  Admittedly in 2007 =
when
> rfc4949 was written, 802.11{g,e,n} were just released [1], and only =
three
> years before, in 2004, Economist predicted that the worldwide market =
for WiFi
> devices in 2006 will be 50 million (!) [2].
>=20
> I don't know that we can do much here, but it was with some chuckle =
that
> the term "air gap" lead me to the statistics I mention above.

Yeah I wondered whether people would know what that was, but I could put =
in an reference reference to 4949 to make sure people know what I mean.

spt

> [1] http://www.ucopia.com/en/news/history-of-wi-fi/
> [2] http://www.economist.com/node/2724397
>=20
>=20
>=20


From nobody Thu Jul 20 06:00:07 2017
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6289F12EB99 for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 06:00:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-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=yitter.info header.b=hsYpo9Lv; dkim=pass (1024-bit key) header.d=yitter.info header.b=nRT0eBgf
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 1tR8Vn-rUX-3 for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 06:00:05 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 235B1129AC4 for <ietf@ietf.org>; Thu, 20 Jul 2017 06:00:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 284DFBD996 for <ietf@ietf.org>; Thu, 20 Jul 2017 12:59:32 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1500555572; bh=4SE5B/rzt7Mr0ePIwlrKylu0OBY6jvFidXwxnUy/msE=; h=Date:From:To:Subject:From; b=hsYpo9Lve/6j7EXdpj+PFBHo1+JZrrj6dW1FXmX/BLPG0zeIYGP3NCvHoY0BcVjVV odIzhr2s4YvuBhtmGFRddohJj2G8ak7epy7cftVElKUt2oZ9OZ8msRYL9Zz1hKikuA E/FZtZ5yq9gtaGM1KLRuXwBhMuVTXZtgtet9Pu00=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GOEIUS9HPl6t for <ietf@ietf.org>; Thu, 20 Jul 2017 12:59:31 +0000 (UTC)
Date: Thu, 20 Jul 2017 08:59:28 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1500555571; bh=4SE5B/rzt7Mr0ePIwlrKylu0OBY6jvFidXwxnUy/msE=; h=Date:From:To:Subject:From; b=nRT0eBgfV2YKkKTfsh0OGd+ECgJfcPxFEV8Ld42gaPraF6sSXUDA4oHnr7S4mFXT9 lZk+4upsw1yv4i57AjsfJdxvq5vFhH6LbzIMFUOPKJUD8SwpIPl5uVj24bqbJiFBJh NrQ1+/Kx4zabRwicq8NqUHg2SeTTlhg1kpTHetXE=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: quick observation about remote participation registration
Message-ID: <20170720125927.lbmtvwo3dncmoxmb@mx4.yitter.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/leC8Y2K9ikbLkswRb75Av-6d_KQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 13:00:06 -0000

Dear colleagues,

This is just an anecdote, but today I got to a room that was too
crowded (I was late because of another obligation).  Unwilling to
crawl over people, since I was the late one, I went back into the
hall.  In previous meetings I used meetecho to follow along in this
case, but since I hadn't registered it was a little troublesome.  I
just used the audio, and it's no big deal, but it might be a useful
illustration of one bit of friction that comes because of the remote
registration thing (unless everyone registered on-site automatically
gets a remote registration too, maybe conveniently printed on the
badge or something).

Note that I am _not_ saying this proves anything about whether
registration is a good or bad idea or whatever.  I only mention it as
another anecdote (and of course, in one sense the plural of "anecdote"
is too "data").

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Thu Jul 20 06:16:06 2017
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DD261315FF for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 06:16:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-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=yitter.info header.b=ALp5yHFp; dkim=pass (1024-bit key) header.d=yitter.info header.b=j4YYV+jp
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 toDi4PYoCPoO for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 06:16:03 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17DFE12EBF7 for <ietf@ietf.org>; Thu, 20 Jul 2017 06:16:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 6E0E9BD996 for <ietf@ietf.org>; Thu, 20 Jul 2017 13:15:32 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1500556532; bh=QEBVtUy4L301l/COriJYistcUGn70VSye9J2ISzuWKc=; h=Date:From:To:Subject:References:In-Reply-To:From; b=ALp5yHFpm+4qrQF3nOww6EJBlHfPo63iIhIQrrgOJd/wm/PWBzo25OqgrsDsi7D7c r7T6siU3afIVyWZVZT+ULMgxqZFnXZMRD+wrZUojf9TYMgLPGG6cTo0IU48AkqdX6i zuVPJURIoHY9E+/bQxpf1BJMGlX+TKObQIWJIyIM=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fvfFLPyMnlLC for <ietf@ietf.org>; Thu, 20 Jul 2017 13:15:31 +0000 (UTC)
Date: Thu, 20 Jul 2017 09:15:28 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1500556531; bh=QEBVtUy4L301l/COriJYistcUGn70VSye9J2ISzuWKc=; h=Date:From:To:Subject:References:In-Reply-To:From; b=j4YYV+jpqj+YaAHRjRHoIAWcXEg6plDxsgoWNojxg9I+7N2K/1wecYaK85UYYYVZe 8r6wMLI4WH17qtFlyxhVSuQvNf4cka9PjDxS/p0K6DGxDZlDo0ssvWAvdNwPfbIoGi aOFTvjmdyksj5yCxrfyxW3LJ866W7LCAHKW8Dzq0=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: More and more virtual interims
Message-ID: <20170720131527.e4bcjsry623leeih@mx4.yitter.info>
References: <876859E45DFE49F23C5AD313@PSB>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <876859E45DFE49F23C5AD313@PSB>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Xu6XZXikJdFqyq38vzU-M0zr-yo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 13:16:04 -0000

Dear colleagues,

On Wed, Jul 19, 2017 at 03:15:32PM -0400, John C Klensin wrote:
> plans.  If we are inclined toward shifting toward more interim
> meetings rather than emphasizing asynchronous email
> communication, we should ask ourselves about the risks of
> thereby shifting the profiles of the participants and the
> possible consequences of doing that.

One of the things I have wondered about, and in keeping with some
remarks in the plenary last night, I have been wondering why we do
virtual interim meetings as _meetings_.

Sometimes, rapid-fire real time discussion is needed to sort out a
complicated problem.  But in at least some cases (I'm sure I myself am
guilty of this), the meeting amounts to a forcing function to cause
work.  If one does that all virtually, then everyone needs to have the
enjoyment of time-shifting and jetlag without the benefit of
in-person-discussion in more casual ways (hallways, dinner, whatever).
Maybe what we need is not more virtual interims, but more time boxes.
This would do nothing for controversy that needs rapid interaction,
but it might meet the test of "faster progress".

One way to do that would be to set document sprint dates in advance,
and for chairs to reserve discussion of this or that other topic at
ome time.  Have any WGs tried this recently?

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Thu Jul 20 06:21:39 2017
Return-Path: <ford@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58D4A1317A7 for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 06:21:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.802
X-Spam-Level: 
X-Spam-Status: No, score=-4.802 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.org
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 izk7bCRK0Z11 for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 06:21:36 -0700 (PDT)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0071.outbound.protection.outlook.com [104.47.38.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88EF412EBFA for <ietf@ietf.org>; Thu, 20 Jul 2017 06:21:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.org; s=selector1;  h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=GzRGf32n8p1OwHYelxVh2lRfoXxchFzKBK5riNAdCm8=; b=wWXEKjfYL3VejRA2gBPkm+SuASXvP6QyzcCKEpJSoUYd+wpuaM3c3kHGKoDf3CQnJHDl+D4R3Hkc7UZfZkMaT2O8dZU+KAtuoSkU0jHkmPIeYZPDoyKCwOrWW9wJPELGUGWUXDiGjO/RQITHwu1FEAth3Dndjb/L7MZbts+pb2w=
Authentication-Results: anvilwalrusden.com; dkim=none (message not signed) header.d=none;anvilwalrusden.com; dmarc=none action=none header.from=isoc.org;
Received: from [IPv6:2001:67c:370:128:b905:de12:32d:4688] (2001:67c:370:128:b905:de12:32d:4688) by BY2PR06MB2216.namprd06.prod.outlook.com (10.166.113.154) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1282.10; Thu, 20 Jul 2017 13:21:32 +0000
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: quick observation about remote participation registration
From: Matthew Ford <ford@isoc.org>
In-Reply-To: <20170720125927.lbmtvwo3dncmoxmb@mx4.yitter.info>
Date: Thu, 20 Jul 2017 15:21:22 +0200
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A9FABAF6-91CB-4BD7-82F8-F20FFC8C513B@isoc.org>
References: <20170720125927.lbmtvwo3dncmoxmb@mx4.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.3273)
X-Originating-IP: [2001:67c:370:128:b905:de12:32d:4688]
X-ClientProxiedBy: VI1P194CA0009.EURP194.PROD.OUTLOOK.COM (10.175.178.19) To BY2PR06MB2216.namprd06.prod.outlook.com (10.166.113.154)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: a3319e3f-07f0-4b0b-4103-08d4cf723d9c
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(300000503095)(300135400095)(201703131423075)(201703031133081)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:BY2PR06MB2216; 
X-Microsoft-Exchange-Diagnostics: 1; BY2PR06MB2216; 3:izvWI7AJHgDZYgOse2tAnFZwhqswZ7A2jufm7Q0y2nuqUR1Rj6VrjIKkuQbaJInuNWTKW/xvJLMyinWyV3C8ceeGnQxrTR2ngKD53v6aX8INghwVNHnD/4BlCPl91LI9PJs610NSg+jnfGmWYXM+5/mCNE4LwOHKZWT1uWjOROMp4q5yNVIk90h4GDU1GH00PKDouduckRYGdY+HZG16kMGQu9xCbP5jLLdspiIf2mt+mHVwJ2WY+JRQW2804XDZA57d9rDVU8kZXD4TmQXmJtVuOJ849wnZgdl+hzukZ3O01avvxqMMrCZzr2/OurRGUbxlM/2EJt6g7uLcaAEjHKxfBDvmGwtWvbP789BsSbolXTB6jNFqaG58h/0323yozXFnPrZbKd3gZZGL5mYBXUXdiotSK5NoIz/SBJGkv1s1AI8yIow4DCOrUgD0Cw0tWqmjLe115lumVbrdhT+LWZw9g7ToO62FeQraF0Olyxogt1c0pkveRodMe5eKFpiiuxDNvYMzbqke0NUVX16aSfL7H2RXBrR5/Y8z920kvmnHP6651L7f6yctQLF3pCR9PLnWj9IlNgdpAgQG9mAQbKgf/CylGWujnujXAvvdSisTxJSWCyqEOqlOgdxiSOWwBiTq2huc+Rync4A/Dbq6cpCpgMoKew8uQNn2TknxPIbPFcW5QOOmdC8J9WXWN/sKjJjcNVtOYPG2ni3kQpCvquU0HJRY7T3KDPvDfuKGlI4=
X-MS-TrafficTypeDiagnostic: BY2PR06MB2216:
X-Microsoft-Exchange-Diagnostics: 1; BY2PR06MB2216; 25:G2zSoHwFINpttdWGTSVprO2ZDurM7I3DDXr2hpVWTyJcTK0k4BFYPaW/3UVmEQuuvMzlPzkhgSl/QZdPgsCl2caPU0tClEdyfqJ/64V10Uqz1VjbIfi2EpbLQ+3Z2FWngMdOtXSwm2fVPnYI2Zs4NeVAH7M5EY5VibPaRbUWKxnm9VhxaFOy9KEcF85sNr/mCV1gGmZnIkeRhvqWhHNZZFCaJu5ZqwCGpqmeBC/+fs+tvtWNkZl6YWLRs2Sy/Z1IXvF1Ve7nHKR4mKPwLSNZzSxa7g/Crj/U7twKMF9slfPvsrXmM3+9vW1IEdMABU1O2xOeg7HAunlw+kINeVbO9pAk6rOFCrAsWSUvWZjTYLTlVVmsqGJAUiEc2hHdBQ21RGQjmjXw4bcgFCbkzwVMcjgKW8boVlVrx9TiqhBc2lBPk6/2wqnGGPiL/rsvsJywnjQJUtO81xQAW8ZdHlwdkrwTEF1RAYxtGa/evwWZFstMjGBhmOpKLtikDvwOC3UCRNlPfzbBmY13T0662O1dQ2QU7EWhi9LXglahXvOA3g0Hj7Jk630LMgzij5cMhP02Lj0xRC/IWj83+MzaD/+OC5hhtV9/gb3ccOpNp+7zjWwsDs/H7hPgAK+Nd+0qJom2iQi6IjH8xE3dwOHgJdrHv7ankCLvnsEvnT5w+rT52XFtEy877fGv4p/2Q/uWPjYeys8M0sL1GDA9B8UcYOwRLzRpxvSdEG271Xjw2JiJAdpBZWQ4i0/cgAm6+Tbx5R6noBEOXOKdkMngt1nprcd66pkMKbCEM6NumBUK16k7ec87ambjDVTmXkPZNEv2EIi321i+76r17O9JqK8eDJpdkcTFTDCTm4L1c0Bt4SK7k51VWwqaSvgtEthwg6irvfquG8kQ4XNoOWOkyY6ahxtAjkvhkggZN/Eh29BAZRfpaUA=
X-Microsoft-Exchange-Diagnostics: 1; BY2PR06MB2216; 31:aSgBUUGQrL+yEnz6lzD0V8mhN2KrrOP2i/7XLgcvRAtHr5ygP5VtAyS64kuHrjj8EoPhfIFqw86cpBz7/aiKaN+gfSQiqMJzP4llCexyo6txUnFIYrhExxiE1HJqU03y0ItgFxVNymTyKI+7IVPkOSgXwtA3/5B5qMfywV14D5owXGXDHIwiLkTRJeK9TLEvdJ6Y+PEqvPDyVlLWdKwygy/NEZHTu3L4U61qpwcr3SwgokCI8rOz6yQET2aZ+tq+ZKRX9MBO0YpXvmbz08WBAOolOylnvF5/G8EN/pQFsUZDTv++U+ZbulooX+ONMIy7QJDFqGWJsgyep2FFYzXc4CGnM4XKJp0lV21VPD311FKhB7JfZR7RSwgjC+IU2teHSPUcSxQIOBVUfuoTJdgGZgTJL2VnjNafxS+Lr19RIvGBK/HWno+KhbvOgI3L903Y7gOx++0kfyhL0Ogeml+BKzKd2lNr4fVBMRdeNHHV6NvMgqWV0peEqv0KnzfI0HReCQ5BFOHMT7GbNxmpkxKqYhuMiBCIKioG5w+3yyi0SPben3kgQQ82vWi97WriV6YpmkN80pQ9R018uaElYKXISjKnGH11oKJKck0dgR+SZtR91LfI46tliVaZwZgNyPuHkj4plZBKjbxHEU5/1rSQa/plaKMKnn9hYdW0d4soyiQ=
X-Microsoft-Exchange-Diagnostics: 1; BY2PR06MB2216; 20:IuEsdB6fOFHT+Xa2r5DvsLfeSmdkWZzxvrnuKAxwbhnITidoQ+2ccYpo+i/W/m2yyS+lAxy9p5A3Wz1jKxQm0Bo9doY/mQdZ9lcW9VZ+AI7ON8zF0aK868n9dRJ456w8R5pon4HIO1Wgd88o9myxehFkGKpiJxN0OKH6/rETNpmI07IQCdSFGAZ4mTJPg/GErgFwqyQbuMtIbWYItND5HJa45iMxYw3/2jt+bF8IyAiDQmgBz2fNextDxrU8e6FoxEK9XJNivwzh4fjXybWZP7fb3AWO48TDKkuBFrqLXqxHUnG4SjRrdnn0dSvwKeo8oReqgEYHWiUKevWRHUAcFISLGTV6l58pkm2wgNLRfbL6d6Jxzn6vF8Dbpotu7BmgSwoILEQ020s7ZBtJQ/CeMglLHxnf9VwGzUIXrITXlKtGGRG3CzfezvuKWXisHWo/vriFIPSIWBuxxBsaXt82/vVh5gLtg2WxTwj/rjcs0iZqfAbMk79i9qOmrp7yIjf0
X-Exchange-Antispam-Report-Test: UriScan:(236129657087228)(90097320859284)(92977632026198)(247924648384137); 
X-Microsoft-Antispam-PRVS: <BY2PR06MB22167E7E78F5F8B97FDE506DA7A70@BY2PR06MB2216.namprd06.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(5005006)(2017060910075)(8121501046)(3002001)(100000703101)(100105400095)(93006095)(93001095)(10201501046)(6041248)(20161123558100)(20161123560025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123564025)(20161123555025)(20161123562025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BY2PR06MB2216; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BY2PR06MB2216; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtCWTJQUjA2TUIyMjE2OzQ6YjdtMDhpTlFLN3Vac0tRTDBrSEhIcy8yZjhG?= =?utf-8?B?d1paMHVCTVl0TFB1VStQVEVnTlA1bkRnZGxqdzl0UlREb2lodlZzd0pvdlg3?= =?utf-8?B?N3dTZFA3bm9tbk9FcXExd3I2a2piNU90UEc0Rkd0S01xUUc5TEFONTV5Y0xy?= =?utf-8?B?T3RscW8zU2xUZGRzM1NLdjUwZ2dadE5BNmI4TXRkQ3lCZnlyZ1ltdFJVMXBs?= =?utf-8?B?MnAwYXNwa3BhQ1l0c1JzRG9yYTljVFBCRTZYcUFZMW9vOTUyWnFSUkxIS0FW?= =?utf-8?B?K0FUdkYzTGUvYnlZSW9RQXhQNUpzazdTMlh1M0RVTmlLM1FHTkdteEQ2KzZt?= =?utf-8?B?ekFpOXhONXo5a3dUd2FCaWVVQXZ4aFdUUFJuT3czWFJEZ1VWeWJGZXJMSDR2?= =?utf-8?B?RThvejNQbVFVMnhubU9EVjdPUE8rWTNsdm9IbEV0Y0ZZZ2YvbjIrZ2N6SWRk?= =?utf-8?B?bi9EODBIYzB3OGRUZjk3TWhsVzVzTlAxeUxMTUdBaDU5TlpOZm01WkEzUlBJ?= =?utf-8?B?cjdkQk1uOEY4VFlHYlVNSmtOWGhEeXlSeHBuTGNxaytOcjJUVUZmbXY2T3Jj?= =?utf-8?B?RlZxK1JOOGxTZllqUmlhdjBhSVZWUVR6Y3Zsdkl5NzJzcWljOGlDWHJGRi9F?= =?utf-8?B?dC9yaEkrVUEwTTRyR3ZCUXVNalJuNUszTktxcngzY0NjYlkxMXBxVVJtU25L?= =?utf-8?B?MGUvdmp6cFBtRktEOVZZak9GZnRtZ3B0cUlVc1JpdnZ3c2laUGZhWWxOM0tI?= =?utf-8?B?UDFDdWJ4eUlmcDEydnBVRXFoVnRUZjRXend6RlBIZmtTd0RaUzFvdTRJNEU2?= =?utf-8?B?SEV1dkdvMkFHSUoydHdXQkFrd2lybmFEWWFWd1BIckFncStnaTN6VTkwbGFL?= =?utf-8?B?Q1BiWmFyV3hWM2oxSDg2VGNjZWJPKytsaFVVVUdseEw4SGZVY3FTd0kySmRq?= =?utf-8?B?V1phOE03M0Frem1WaDgyaDJhL1g3cXZ1R2htUUtCOGVHVTVrdVI0bllGRVoy?= =?utf-8?B?bUF4SXVlOUZUOTBWQ2FNaVVXRGNxVnRTakY4b2JHRU0xNnlyNUFPbEJXTldU?= =?utf-8?B?SitaSExpOUt6SVZyMGJNM2JVc0tnUWxMN1pQSUZkc0Y0d29jQldsMkpwTlEy?= =?utf-8?B?U3dsU2lva2xnUnkzdUNDU1YyUEtob2ZOTmN4d2ZPZmdJaDRGaFpaWGVEcjFK?= =?utf-8?B?V2cvSXhEREswT1NINlFmbHliVXVaVnhzeVVTa0syWVlSNThHNVhQc1l2bDE4?= =?utf-8?B?Tm94WnNpZVVXZ2YwSDkvSUFMUk5DWDJoTmx5RFdaZFlRZGRkUnlhaXEyUWZG?= =?utf-8?B?WUJwUzVxZTRqVHFtaVp6dHpUd2JPVXRJZUtPNDc3N3p5MzFhZ2lCNGU0WVBC?= =?utf-8?B?Z05TOW5yMzlqOHV0YThDNStYV0d5MHVkcnI0K0FibU03VzA3TUY1aFZHYjIz?= =?utf-8?B?NTQzcUJKdmZ3b0RPbVR6YkJIemV5MjRTV0x3QmYvK0hkSTgrbmJQVmtzbGw4?= =?utf-8?B?Yk15Um5tRTc3N0hTSFQzUVFvQTJJMG9hK2V3N0x2cS9BcGVjaTRUK2RvT2wy?= =?utf-8?B?Vm1nSWNpUk9hVTEvQ1NFL0RRTFFQM2JsN0RVQmlmTXRtMEkvMkR4dUg4dmlF?= =?utf-8?B?a2R0QzRZZ05TZ1c4Z2VXcWhnLzNCU2R6Mk1BZTVwRGR1cjYxYlNsK1dGa2Nk?= =?utf-8?B?N1ZqYk52MGhNTXlGNUwrSVgzS0ljUWdCYUIraERVR0VZTjlJNTNvTE5vbVV3?= =?utf-8?B?RkZXeFRXdjA4OTJ5WTc5S056RFJEMy92MElYcjJoeGZ1TVd0V0RHdW41K29z?= =?utf-8?Q?ZWy1CcdXuhF0?=
X-Forefront-PRVS: 0374433C81
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(4630300001)(7370300001)(6009001)(39830400002)(39400400002)(39410400002)(39450400003)(24454002)(82746002)(33656002)(478600001)(229853002)(7350300001)(25786009)(50466002)(23676002)(50986999)(76176999)(42186005)(86362001)(189998001)(413944005)(36756003)(2906002)(6116002)(6486002)(6246003)(110136004)(8676002)(50226002)(53546010)(81166006)(83716003)(6666003)(38730400002)(53936002)(8746002)(7736002)(47776003)(5660300001)(305945005)(57306001)(2950100002)(4326008)(6916009); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR06MB2216; H:[IPv6:2001:67c:370:128:b905:de12:32d:4688]; FPR:; SPF:None; MLV:sfv; LANG:en;
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtCWTJQUjA2TUIyMjE2OzIzOjMzT0JobE4zMjZGWTFDZG9jVzVldU1LWUZG?= =?utf-8?B?dXBPU2NDcnRhNlI4U1JvSEdWeVowM3JtOEZKOHJEUHFWaFZWNGp4K0E3V1ZX?= =?utf-8?B?NjVHTmR0U3g3SmR0R1F0SUxieEV5Lzc2S0pCdHkzQkFtKzByeGtxZUovVzBN?= =?utf-8?B?bWlrYlV5S2d4YVdCTUhSMEZBWDNQUkUrMFVVakhxZCtycU5HdG9zV2lOUmdY?= =?utf-8?B?akdnUkRHejdPUTE4UHNFM2g0MDBVbUdobS9pYjZZNDNNUGx2NFJXdTVhZU5C?= =?utf-8?B?SDZsanpVb3pFVGU3ZUc0YmJ2Z2lIOGNCTERtb3FXT0lkSDFlY2lkbks2NC9m?= =?utf-8?B?UENoQXVkQ2RsdEU4cmFabkk4dnRGeHl5RHZtdURHam9PMkp4d2p3ZEtpcDVk?= =?utf-8?B?RWVEdG9CbDJKcXBuZmZHTzBoZEROMmJPYitJN1ZiUWh0ekcxdC9yL3VYZ253?= =?utf-8?B?U0FsZkk3bGpmZU53SStDRk9NUkw0S09ObngzNGtvd1krYnVxS1ltdE8yV2xQ?= =?utf-8?B?Z0cxbXVlK20yenBrbDhzKzBsUjY1VEYwdHZaSnVZeEJlbExHWVVQaktWY1Jy?= =?utf-8?B?dWRXQjJsN21CbmszUFU0TEM1dk5jZmNBSVZqbFBoYWhRUzNiU3loQjBXUHBi?= =?utf-8?B?TlV6Z3pIV0ZMSTVXQjd4bEREZ1M4TnRHWnFsZTZsK3l1SWZ6VjVMS0t3V3A4?= =?utf-8?B?ZCtUQkw4U0NyRTIvUFhUOUNwOHlUcXlDa0ZQclNJQWs1d3NZakdZU3RoN255?= =?utf-8?B?aWFxMHRqVjZQeUZtaTh0b0RRNVd0ZjB0dERMVVFsNHR4MTFVVUJUR1F2Q1lt?= =?utf-8?B?bVNEM2hvdE54c2F2dm54Z3kyTktxN0tzaU1aZUZDY1NPUlVaTUVqUkVXKzgx?= =?utf-8?B?UjgrS2h2QmxLaHNlQkJab1REZlJBRmk1Z3A1L0dDdTYxTWprZ3YzQ3V3by9Q?= =?utf-8?B?N1VnYlhKOXFVT3dwRDNYclZ6M1QyUDFCWWF4OWZXNnZyWitUUGtGcFlkQ0t6?= =?utf-8?B?aTMvY1RWZ1lnK0N2MTR1NjF1emVqTHB1Mll1WnowWE5YTkw5bmtVc2JCRGIz?= =?utf-8?B?UnVFVTl4QVcxbDhSenBaQ0pkODNERHFrSnZ3TDNOem1sZGlIRENCVTRTV2dL?= =?utf-8?B?QzJ1RFZENi9MU1k3eVd2YVIyZFNHeUkzeDZndit1L0NkR2piNEF5c2NUcFov?= =?utf-8?B?OXlxNko5Qk1TL21RZFR4aDc1Nzhob0JjNjI1UktEYkJ0Mjl0WlFkS1VzaFEz?= =?utf-8?B?eHVpa0ZPRENKdW5PSkdIK0I3UFltS2hXWHZGM2VMSllsSGhVTmhmYkkyeXoy?= =?utf-8?B?Z3JZYmJsZksySVBGaDhnOWF1aUw4QUxsQW8zVVRWa2FsTkFmNCtnRHJ1cnZU?= =?utf-8?B?Q09ER0VjUllZSVhJT3ByRmU4MzVpYkhITHIzdlh0NG5hYk44YzNOQmtDYlFs?= =?utf-8?B?MVV4WTNtY3ZGQU9tWWp6aUpsTlBmVGx3RjdOUDNFZ0NsTlUvcXM2NTB0YlBy?= =?utf-8?Q?7NZcSTCc2tE8J6OtXPMVnfNTSvrqrcttwsjXKGoPI1ScMs?=
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtCWTJQUjA2TUIyMjE2OzY6YmlNelY0am5ha2tYU0pnY1UyaDF3RElVdTRS?= =?utf-8?B?QWs1QkdKRlY2UWRncUJEWFN6UUFnTTVIQXgzdWgzVXk5RHM0OW1OOXFFNVBY?= =?utf-8?B?SmVITVI4VXZuSng1a3VZK0pGQU9LNXFtVGZpeGg5QzdQczZORlE4UmFmWEJz?= =?utf-8?B?QWFpVDJ5SGtUOGhteHJsUUFBWVpmY3pGMWpIU1hUVjY4QmJCam5qY25yZnh5?= =?utf-8?B?eWRKY3h1eks3QU5CWDB4cDh0T0xhNTV5akgwMTdaNVQ5dHVuM0g2ZEFZZHBj?= =?utf-8?B?VzNFV05NTGRGVmVTWHNBdUYrN0JPMHVEeEZQUUJlT0hvdHNYT0MwcTVONG1u?= =?utf-8?B?NDhQcnhNemxWMUNhOFA5cTNER2Y0a2paSi9lcEFJZFRiK2dxRWVWM0dJdE5q?= =?utf-8?B?dXpuT2c4dCtlWWVVcHU1V0wzODR3cnA0eHNBWFpWb1lxdEtCdkRIRjFLYzhn?= =?utf-8?B?UGo4dngvN2dCd1kyajN5Z1BVNDBQTDlVUzhaMkFJb0x4OEpxTDJUVlQxMmRJ?= =?utf-8?B?OENoSjJiY0I5QWxLZU40NXJCc0oyWC9remhGN0YrUW9yQ3pHMC8vWnZYKzd5?= =?utf-8?B?Rm1QZjAvOEJGK0NhYmtnZy9JVHJwKzdUKzJ0VzBaZEU3MVkyL2dtdDN3SVQw?= =?utf-8?B?dlhJLzlIcTVGNlh2UlBZT1hiZVhKQWFiRUJKS3RYWVIvMm1sOUYrUHVzUEJv?= =?utf-8?B?NFlmYVdwYWVPNnBSOFdKdlNkNmtmUlJoZERXTVVCOUZWSkFvWVFmcHA0dVBM?= =?utf-8?B?K1dkUzl3YnpTS0JLdm5GWXVGejd5bk90RHF2UzBNOXU5RTJ5Vk9XU2VTTDEx?= =?utf-8?B?YzlUTDA3RnVjYWtBT1VXNkFIdE1yNFgrRnRmWW8rMlhkYjFkN213bEZmQjNZ?= =?utf-8?B?RGhkZWZiMHk2SHZpamV2WGEzaWJFc0xSS0tMbjdWZ1NKYytVV2NuUW03RWts?= =?utf-8?B?Qm9NSy9IRW9xd2x4aEZGdWdsOERGK21sK3FMRVREUmVnakRyY3Q0L0FldXls?= =?utf-8?B?ek1SQU1CMTdyTi94Y2VIL0VRRVdXRDlDVEJ6OGZ3aFlMV09rSGJMa21nTExC?= =?utf-8?B?TWdCeFVZY1g1Rkt6TkRNRFd3Q1lmN3hxWnh1aXc3Q005RXdMSWZVa3RzazNL?= =?utf-8?B?T09kaU9ESGxLelVJNjhhdDkyWloxNWloTVhYcnl5SnMrVTdlcnJvZ3BjR3d1?= =?utf-8?B?MDNQZlh0ODhUejE3N04xWEdsM3l5RWRFcGhzM21qTHF2L0VkbHRxVGxwY3la?= =?utf-8?B?TVVKVzZSMGRsN0xaWnBqMFM1eHlwK2tsUnpoNUwxTU5UMjlOVU90OVN3WEF1?= =?utf-8?Q?FyPLrQJWevgQiLzI0yMDiwGWaUY6m2E=3D?=
X-Microsoft-Exchange-Diagnostics: 1; BY2PR06MB2216; 5:6wBb/gIYGMFSqEB2Mt0p9W2kcuXcerBju2GBonm/0Pw7vYOByGm94WTG4V4Bb6SJmkDRqCl0tfW+hi8wP5oz7gI0MzTHyBa9FXXA9fJam7tuNYckXXAj3ISUpT+cqHgdx3Myis+NVQx3PYSVvoMk/Nizuo1yMl5Up+NF1wve9D44kB1EOh9PdOCIzgeGrD6GwAG356eluhNQOPh8edamwsrYjad/JBvj1NMKjXawkh9WOiSrSCne/D4pPSsaB6u7A4MujtW6ou82vK0RdkRIwf+KYPyhil2SNOpN+8c1STq0gNHUhfGGiBnw2ngHJWRuslc7k8rjAWtCNZDNCfFTX/HZ94BY9dyvWxJ18HDy38OGzThL5KcPVtS1fVJQGEFbaGPTPmE8wfFNC28tslMBJ4ymWadnSRKYxXmznvm9DSVwyZrGDFAS4KuqsQew3kAaAq0tEWllik0xfwTxYlrP8A3FizVUSFDvONamf+/I3a1Gn2kyDtaD3mWR990Wze+6; 24:tXOY8Qte7LZjXHvg1Q3TnYCzZI7p7fnNWjZImcjHn84j9PbkdO2aHOJ8PSu6Js7Wt/JHG9mZBaI9EhQupesJxLZQvEM0zRupZBgg+2Eoyvg=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; BY2PR06MB2216; 7:UyVncR5aMTk46wEN8mBNtBAx3UytU7HzfAxeitMyJyTrxMutu0SsLSPHwpelcDpih44fUzcGd8T+61K33zpbncvVyTGb+iZ31sNq+bFdZvFz8mNJApVWBsvf8HMftaXO0wp/Dgc7QpK/SkrgB2X7u5MN0cVfk91Nf0OHAN8AaHWlW1dXwCL/YchB5wyYMYBxJ19oFb8lwGAhJY4KSanUFIdjwTLljt/ZwlUji0l/grwApE355balsq7H21zx93klsDG1zQxvNU/WtCWvkcSSBzsEe20p6GTt5DudwpQvs+rvCPp5JhYT0Nmyz/bf/KUB0wp2vEtBRz986Bic+9q0HbEOgC1iEqo+7T/JZA1BZ0B3IAXHeaZF4gcHgzMtWbe33dtMKY2RoVxFOmWXANQd9R+eemEKiv+J5WNSjX78njnPyugZmSe0/5zWsUAnY8B18cou8DzMwIa3HSSaao8wWr/FenNLIPBq/hZJPCQdwPQ68iEU3JV9zCaiaKTYoU1s5BSipJanUDUq2XTAYnDY7OglBZh/NZ51B9LuzWaxySqsg2fOiqlmmkEqYuaH7YORcSzvqRPVpa/M5DaOeDs69TWXN+LmSjljYlWVk9IDmpb8Wd3J2kPnjhs3EJVNnfjMECBi8G8aYaTwVRXHbML/RXv63kdOZ/q3kKir32v+V2NrVoppWlcA5z/ES2T9UipogqVquYpL8fK2sRWU2+fFGO/+LGGhX0EL6Mrzjyp1bRbojuzOIL0NCYX3Gr/8Wjnhn93xEdOrtsx63mrjoz6GZbuScOievAVOhNM0VJyJH/Y=
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 20 Jul 2017 13:21:32.2485 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR06MB2216
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wALV8fPkL3fc-z48W9iIba6a9AM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 13:21:38 -0000

> On 20 Jul 2017, at 14:59, Andrew Sullivan <ajs@anvilwalrusden.com> =
wrote:
>=20
> Dear colleagues,
>=20
> This is just an anecdote, but today I got to a room that was too
> crowded (I was late because of another obligation).  Unwilling to
> crawl over people, since I was the late one, I went back into the
> hall.  In previous meetings I used meetecho to follow along in this
> case, but since I hadn't registered it was a little troublesome.  I
> just used the audio, and it's no big deal, but it might be a useful
> illustration of one bit of friction that comes because of the remote
> registration thing (unless everyone registered on-site automatically
> gets a remote registration too, maybe conveniently printed on the
> badge or something).
>=20

Having my IETF registration number on my badge would have helped me just =
now when I chose Meetecho from the hallway over standing at the back of =
the room in saag. But I found my number easily enough with a quick =
search for =E2=80=98registrar=E2=80=99 in my mail archive.

Mat


From nobody Thu Jul 20 06:22:22 2017
Return-Path: <john@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51DA9131C28 for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 06:22:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 IukWBKnr7JLu for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 06:22:19 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1311C131C20 for <ietf@ietf.org>; Thu, 20 Jul 2017 06:22:19 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john@jck.com>) id 1dYBPF-0000GR-J2; Thu, 20 Jul 2017 09:22:17 -0400
Date: Thu, 20 Jul 2017 09:22:11 -0400
From: John C Klensin <john@jck.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
Subject: Re: quick observation about remote participation registration
Message-ID: <30D585774FDAF7F5158A6A26@PSB>
In-Reply-To: <20170720125927.lbmtvwo3dncmoxmb@mx4.yitter.info>
References: <20170720125927.lbmtvwo3dncmoxmb@mx4.yitter.info>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_bsbLIKsZoryUNtTDiTXctHZ_40>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 13:22:20 -0000

Andrew,

I would think that this should be even easier because, unless
someone can think of a reason to not do so, the registration
code for on-site registrations should simply work in Meetecho.
Putting you through a second registration/ signup procedure when
you are already registered for the meeting (and, in your case
but less in Spencer's use of in-room Meetecho was slide viewer,
likely in a hurry) seems like unreasonable bureaucracy.   If we
need to keep a distinction between on-site and off-site remote
participants, that distinction should be embedded into the
registration codes, not require the user to pretend to be two
people (which would actually distort the statistics).

    john


--On Thursday, July 20, 2017 08:59 -0400 Andrew Sullivan
<ajs@anvilwalrusden.com> wrote:

> Dear colleagues,
> 
> This is just an anecdote, but today I got to a room that was
> too crowded (I was late because of another obligation).
> Unwilling to crawl over people, since I was the late one, I
> went back into the hall.  In previous meetings I used meetecho
> to follow along in this case, but since I hadn't registered it
> was a little troublesome.  I just used the audio, and it's no
> big deal, but it might be a useful illustration of one bit of
> friction that comes because of the remote registration thing
> (unless everyone registered on-site automatically gets a
> remote registration too, maybe conveniently printed on the
> badge or something).
> 
> Note that I am _not_ saying this proves anything about whether
> registration is a good or bad idea or whatever.  I only
> mention it as another anecdote (and of course, in one sense
> the plural of "anecdote" is too "data").
> 
> Best regards,
> 
> A





From nobody Thu Jul 20 07:01:57 2017
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A765F12EAF7 for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 07:01:55 -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 61Bjt5dneftB for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 07:01:54 -0700 (PDT)
Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::233]) (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 9230712704A for <ietf@ietf.org>; Thu, 20 Jul 2017 07:01:54 -0700 (PDT)
Received: by mail-oi0-x233.google.com with SMTP id p188so27647786oia.0 for <ietf@ietf.org>; Thu, 20 Jul 2017 07:01:54 -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=IwkejtaYTktkI94vgphzU1OGJETE3JUcVI0c+xZEXis=; b=F1o6jVIxBmhCpc4REKIfawXwOOmJhpr+KbxFRL0z3alD2KqwemIpSQs3mQvCqPYga8 O4YjO7zP9pDbzBczn26Wudc2zw8iPHVrCvsZaQXPIEdb1UZBXU0GXBHtKF3XCamxn9+g imScK8WyZ+4dn8MI+J9tDkaRcrErw6XDxdGSVt+7zqi9yza8xxOdOUWtB3bmAjHELV6I xL9S1a6XSKd9LU1/T0S9fIPs1rF0MecRvNZO36ODJaXk8Ra022YHHLPX5+1VizneTAaZ ZcrB7WyKpZ5lcmJKOrMuvkxlhUdiw6mtceUXv0h4IgU5306ocvfDz+CNEtfayuuVfQO4 482Q==
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=IwkejtaYTktkI94vgphzU1OGJETE3JUcVI0c+xZEXis=; b=VzzaF6+LumzAmk5kP//5UaBUEMM63bWxdrO6JDDPUKiuZcYH8mT6Gh1NEOl9/z2mUA vIggnBJynfq/SUXp2g2wsQtbNHphRDHgA+h1Upd9/bgx5QpWn/jldJhmH4OvnsLj2C78 KslkNQKvv0Ni0a3sUT97rvuSnHqmviNqkOv6S60GSSO8TxMemA0Uu8wcORiNg1KyQrkk asNrsSZ6/ekEErG5Sc4wqF1LHL1I65uP45tfXgRweAsDPR9RUyCadAbWBvqEHp9LIw/R R4sVY2NpU4VNnzARD0qKXKS2vDTiRftOcXUuJmIDIunSH7lthT2r1PkeKnG8hm5JAhwp HMcA==
X-Gm-Message-State: AIVw113ygRtNRVwsfjvi1Ll9eixJKIlZrgmhllkxvIGb3+OXKPbK+IZ1 R9R9lcsO1YSPQuZADZZKVuzkvUtYRA==
X-Received: by 10.202.59.212 with SMTP id i203mr5212160oia.104.1500559313882;  Thu, 20 Jul 2017 07:01:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.232.34 with HTTP; Thu, 20 Jul 2017 07:01:33 -0700 (PDT)
In-Reply-To: <A9FABAF6-91CB-4BD7-82F8-F20FFC8C513B@isoc.org>
References: <20170720125927.lbmtvwo3dncmoxmb@mx4.yitter.info> <A9FABAF6-91CB-4BD7-82F8-F20FFC8C513B@isoc.org>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Thu, 20 Jul 2017 16:01:33 +0200
Message-ID: <CAA=duU0csh0EHh6W3fZh1wABbP7OYWmGMOdVj9dNXXECaxv5zA@mail.gmail.com>
Subject: Re: quick observation about remote participation registration
To: Matthew Ford <ford@isoc.org>
Cc: Andrew Sullivan <ajs@anvilwalrusden.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a113ccd8ede56f40554c030dc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/T8y6YmvvIVYbrkpBNo5d8on27x0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 14:01:56 -0000

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

Mat,

On my badge, the registration number is printed on the back, under the bar
code.

Cheers,
Andy


On Thu, Jul 20, 2017 at 3:21 PM, Matthew Ford <ford@isoc.org> wrote:

>
> > On 20 Jul 2017, at 14:59, Andrew Sullivan <ajs@anvilwalrusden.com>
> wrote:
> >
> > Dear colleagues,
> >
> > This is just an anecdote, but today I got to a room that was too
> > crowded (I was late because of another obligation).  Unwilling to
> > crawl over people, since I was the late one, I went back into the
> > hall.  In previous meetings I used meetecho to follow along in this
> > case, but since I hadn't registered it was a little troublesome.  I
> > just used the audio, and it's no big deal, but it might be a useful
> > illustration of one bit of friction that comes because of the remote
> > registration thing (unless everyone registered on-site automatically
> > gets a remote registration too, maybe conveniently printed on the
> > badge or something).
> >
>
> Having my IETF registration number on my badge would have helped me just
> now when I chose Meetecho from the hallway over standing at the back of t=
he
> room in saag. But I found my number easily enough with a quick search for
> =E2=80=98registrar=E2=80=99 in my mail archive.
>
> Mat
>
>

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

<div dir=3D"ltr">Mat,<div><br></div><div>On my badge, the registration numb=
er is printed on the back, under the bar code.</div><div><br></div><div>Che=
ers,</div><div>Andy</div><div><br></div></div><div class=3D"gmail_extra"><b=
r><div class=3D"gmail_quote">On Thu, Jul 20, 2017 at 3:21 PM, Matthew Ford =
<span dir=3D"ltr">&lt;<a href=3D"mailto:ford@isoc.org" target=3D"_blank">fo=
rd@isoc.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span c=
lass=3D""><br>
&gt; On 20 Jul 2017, at 14:59, Andrew Sullivan &lt;<a href=3D"mailto:ajs@an=
vilwalrusden.com">ajs@anvilwalrusden.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Dear colleagues,<br>
&gt;<br>
&gt; This is just an anecdote, but today I got to a room that was too<br>
&gt; crowded (I was late because of another obligation).=C2=A0 Unwilling to=
<br>
&gt; crawl over people, since I was the late one, I went back into the<br>
&gt; hall.=C2=A0 In previous meetings I used meetecho to follow along in th=
is<br>
&gt; case, but since I hadn&#39;t registered it was a little troublesome.=
=C2=A0 I<br>
&gt; just used the audio, and it&#39;s no big deal, but it might be a usefu=
l<br>
&gt; illustration of one bit of friction that comes because of the remote<b=
r>
&gt; registration thing (unless everyone registered on-site automatically<b=
r>
&gt; gets a remote registration too, maybe conveniently printed on the<br>
&gt; badge or something).<br>
&gt;<br>
<br>
</span>Having my IETF registration number on my badge would have helped me =
just now when I chose Meetecho from the hallway over standing at the back o=
f the room in saag. But I found my number easily enough with a quick search=
 for =E2=80=98registrar=E2=80=99 in my mail archive.<br>
<br>
Mat<br>
<br>
</blockquote></div><br></div>

--001a113ccd8ede56f40554c030dc--


From nobody Thu Jul 20 07:06:53 2017
Return-Path: <ford@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20A6F131B05 for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 07:06:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.org
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 4uUPK7O0Yo6Z for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 07:06:49 -0700 (PDT)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0073.outbound.protection.outlook.com [104.47.33.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97A1912704A for <ietf@ietf.org>; Thu, 20 Jul 2017 07:06:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.org; s=selector1;  h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=bKvT1L3Wd0EabhpX6gGSoMAKto76y03zwpPNiZN5U/8=; b=XfPv66cuVN5WiJDJamhfC5IMsKsrdN9n0tGb5FvDAGkn7Rd8GH4iLQlpP7JfjVMYFKQi8W1E9ROdZt07wp3zsOMu36K6cTR9lfGzgpMwB4P/Qfjyay2dfnqi6Jj5LCaRSHLxY2IMIlcRebYufhAziH06Y1dEOO9Q4xyDQb5uV1E=
Authentication-Results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=isoc.org;
Received: from [IPv6:2001:67c:370:128:9d2d:9209:120d:57b0] (2001:67c:370:128:9d2d:9209:120d:57b0) by CY1PR06MB2218.namprd06.prod.outlook.com (10.166.193.153) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1261.13; Thu, 20 Jul 2017 14:06:46 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: quick observation about remote participation registration
From: Matthew Ford <ford@isoc.org>
In-Reply-To: <CAA=duU0csh0EHh6W3fZh1wABbP7OYWmGMOdVj9dNXXECaxv5zA@mail.gmail.com>
Date: Thu, 20 Jul 2017 16:06:42 +0200
Cc: Andrew Sullivan <ajs@anvilwalrusden.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <4D45C7FB-8AF0-4C7B-A496-02D73AB1EC08@isoc.org>
References: <20170720125927.lbmtvwo3dncmoxmb@mx4.yitter.info> <A9FABAF6-91CB-4BD7-82F8-F20FFC8C513B@isoc.org> <CAA=duU0csh0EHh6W3fZh1wABbP7OYWmGMOdVj9dNXXECaxv5zA@mail.gmail.com>
To: "Andrew G. Malis" <agmalis@gmail.com>
X-Mailer: Apple Mail (2.3273)
X-Originating-IP: [2001:67c:370:128:9d2d:9209:120d:57b0]
X-ClientProxiedBy: DM5PR12CA0050.namprd12.prod.outlook.com (10.175.83.140) To CY1PR06MB2218.namprd06.prod.outlook.com (10.166.193.153)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 71a1c9a9-7f75-4257-f77a-08d4cf788f8d
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(300000503095)(300135400095)(201703131423075)(201703031133081)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:CY1PR06MB2218; 
X-Microsoft-Exchange-Diagnostics: 1; CY1PR06MB2218; 3:dLNHPz6DX5f/iyK9qO0ujR4dvmQQUle6C9WMh27Xwg4+7QDGGdXCIjhuVZGV0+sEB3jDPdlJG6WopNyOI2JEmwBDzH/ulneNQ7TeYaovR26vGHKxBbXxkAcEdvET6DISmUPsXRlpvV2gVlE5A5H8a3aKMQiZ+r9Ycsrnp1E0GFYCzdCs36UZrMxxu3yhd1I8DxPu1WmguhcxD4lwlbZjMg0K+w8hnTRQhWzR0ty1iOrmMexVIzvaYTpUQ0L/kQJ3dlP8Qv3LCqNyJN68n7s6XNFD3D6HZ+V59Ic2ZavzxJa2uhgi1LuinQIyq2UWd8oo/k3dbtMS5G6RK61ZfgnxMOQUKC3+FXGpGBYTd2zjZkdfMDutktaYtkyUwBrfIU4V4Ii8qjTvOSvgQQu+HpdG3mKSXBDEVXVCwyjiyfMEexSJJXx1gkQQQ5p4wqi0Z4o62rSKF6EH3Sa7EqBt53RrtEt3pXCYlyN8jMaMZlD90Foid9hsQYfJa1G9nCtVjupxpMuTAUqUh8TdU4lRlW+SsiAxB9tTOZP15tTc+kZFp07Q5TjxbNZS6SV0YNsdsFAQJh0n06cdR3UDXxOPBgkCIBwcaHjMdqYGN3Hqpy00LtoahTuM+LDWUdWi8cbuFpSdIowmbJFKGgQLfbjJWiAIr9TnYSKyzZaSY74Rbpqk4ibOcC5N1AdnlsnpWl0Ok73hbWkgKQCgg+vWz/3gcfg+wh5dzolg0VPLc0eD8ZaH17g=
X-MS-TrafficTypeDiagnostic: CY1PR06MB2218:
X-Microsoft-Exchange-Diagnostics: 1; CY1PR06MB2218; 25:zO72Smfi1TZsq977u8tqRGdBQqH+9Us7RqAMgvw4eNzmzeuy9976Qwqg3WpfcwvdwKPfAXnrN1TOoW73buEKJyc69v6BtakKslprZzQmBCPaTO2Y5liySDPCgOUgekaBMZYZnVqysGxJs6bY7VoOEHbxojPAZ9pFiwwteid/JDA17tb2ipWh6BUbl74Lj8VXZJEumnbvVZOdJ1g5ULoNjASdBRwtMmGpZWtk9uht3nmTbeIoKt8CFLWt7JFJ/d8Ddydz3WNzCqH4RQINd08/xkMJRB01bxUuXIWHyFnnPoNIiBqxKElGXvphBd9Prrs2GX3CzV4jdomkFnxN6PQ3ZDrS0ZgjgYgBBZfWCIohGOxyfxppB42GjzvRiz73WNjTxpgrGeZkj/sCTS2wHWQWF/6kMdXEA75l21PQKxZJh0pfGUfrICvPFRt9N9tmNGCzDYgJ/3hXi04EdpXJfbR/L4U0rkwpLX7uVhfx3NhPqvzS6EFlfYeAoqO/4zhQlB8lXAtEmf5YVOvoQa6zZT+Vp0fOaPtjiP2Ihy9uawgrHau1BDeqjUkPBuqvRNyOfTSKzOc4XnZrP1qDzAuXi18CuPkPdLRoq1t5WGrqMVQOMwWGuycKZHaBq084wfEYqA8Po9eSW+tWWWwpRaM8nhXaRWnVVGhmAtnlaURUbTQAv/meTXlSu5Ax6O4LQNNYbky4ut9TapLGnzHye3dpmZ3g5l+jAJrxK0N1mnYliec7F0jY1x7p7Nw0d9IA5CHi50lAUfW9yX+gsspy0xvqU5GdQvtk6LvG5+NxfOGm5dYTbhrobDOAMSChH8YN7MMlr2PxCRaaVy7sg1jOrPfMVgPhSd10QbwdC0ty8vmHDIsHvt7WkN+8w6s7gd4AHdPpIxR5Yf8jEUI965GkfmfBxFajYp86AzVyJ6McEgMoLi6z4aM=
X-Microsoft-Exchange-Diagnostics: 1; CY1PR06MB2218; 31:QTW38drCA/ZTkRbrO7K3APzsLvuLqXtXTdZOOz0LyZ/pA4GVVhX4lyvs1oRLwICIv5DXedmmQpTXkXJ//lB+BhTMbpEt15ClwlLzESEDnSt9NjY/kS74a2IDUXRpQ5oV3IPFi0PuxyBdL5mLUyRM9DO7KHd5ZhbsuYmyfxAxCbe7A/VlEAf+MgDlZI1HTqk4KmrfC7bLJHhIGnRlGReFRFp0HRch5bGLxNQmKC0EmR58dJbau6xmFfkAysJyqnmDoSVYmFf02WLaf23eTAVj7mkULqq8Lk9boCAk8ibAw0TKxRrW50oyLGZStvwsgo6S/jcDUkfMQXDTzhUq7UMu18IzG60hIi8NKLCRSoaen2kiD1N1EOW4ZMbUfD1RsDdylxP1yqr5ZgGLYZwu7N5P93nRhUABcV1S7Bub/cwYA9NfCnX6Yoo5Kp6zTd88HC3gf9SaBTAQqbfkj92auiU/fSc9G5LJ3RgwjwSgDDRSjIlEfYogU6ZnYZHKag7Fipxq9soIf0jW6lX9f8svdjTmqgGm62ttZPGaFZ1tcEh6G8uuMU0k6iW0X4EhwBLZ9CuVFzXQg0nuGdzwRmFLd7QjosKR9uGesa3EAucp2b4/k3eMUcR6be4QYZcxm90nouqkMmtbIIO542A7wr1cBKqokVSHDsATuC1QdNcHxSjxqIk=
X-Microsoft-Exchange-Diagnostics: 1; CY1PR06MB2218; 20:UObp/qYqJ00My+m88uLGh/Yn5harcKKJwuFwAbQN27eK0getawCv2MH4LrcJqhUa890H1mBlzKOTUPsVin4mzkeu81l+y59rRLfwrmmVzGM8BELwYxMuFcfULNTzZwcKOdySeWnoUvrYWsAXtclglhkcI67vFL0UBDRNPxrrr9lelFIpv2CjDK3gwF3Wx6sgj4ZiNxw8tJAjOnw6SWCQURHVztZo6k0UTj3FFr0ayCpghre5AfG3XjOcOMtP/AUuz4X4UXoHYP05D6La/owiMZc//o2xx2ZqWM2UN/GCHl+F3EetT5/LwQvqIo2Cm06m8zmcbdbLqaqI4TAtehN4VKvcYCcOnZBkKtEIIdIEPMoU2ueHcnDhobaeElP3gOK/jhNJOMGERJD8v4129fx1ZLLD2OORQMb2cy8rFLYerb09LQJ20kDm4uQszfactZ4302myeRJYGXtaUYWO1HhnGQmCCnuqgW/0fUiaJUQji0lTNf1Crgo+05WOiJTdkhFC
X-Exchange-Antispam-Report-Test: UriScan:(236129657087228);
X-Microsoft-Antispam-PRVS: <CY1PR06MB22187D27B7D699AD862F61E7A7A70@CY1PR06MB2218.namprd06.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(5005006)(8121501046)(2017060910075)(10201501046)(93006095)(93001095)(100000703101)(100105400095)(3002001)(6041248)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123560025)(20161123564025)(20161123562025)(20161123558100)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:CY1PR06MB2218; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:CY1PR06MB2218; 
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; CY1PR06MB2218; 4:pxNuPq91MBcjWqCGWkC31zObSlNLuD2cARwOYajbG2?= =?us-ascii?Q?g2pVTvXlIZtaC4VZM5r5Dhi/PiiQWoljybyV4OXiRcGlCVeOaxfbIHbpMsgn?= =?us-ascii?Q?fjEYM1u0s3KT/sCKRSblzAanxQoFajUl2QVqgFZ+JiIxFkzT5UvHvNY74SmD?= =?us-ascii?Q?zTiB4LrW1+UrZvqx7Y+9Ayt5nl3Hr5cLtE0j18f2irkrT9Agc+tNyWQquJ2N?= =?us-ascii?Q?YtnYQm6jUBQEYJMWRfgWhj077HNgnlE0Oy7A36yAPDQSkXGrPYpLaZoG0JHg?= =?us-ascii?Q?Ig6lzFWDQr7zxrj/WpAYBEU/I71jPmV75KKNQwNzxmX7PK8MgU9Sk5tIAK0c?= =?us-ascii?Q?J61uyYmniVJniYId4Y1E+opxc4Ak/1iZhHc1ICeurxK7YySBXdhEyuu6JQ8H?= =?us-ascii?Q?6wjWpgN17vUivk4Qi1zAKudBWPSf935CNp8QOHCa3bCFzxJXLruwkLraRK0K?= =?us-ascii?Q?420ISy9c+UCBIBB2XY2eHrT8ZhhlFfe+bswzswYezQVFrQ8aOpzwTZ7eouly?= =?us-ascii?Q?EkAwscPyAcDHSgaBSgM6mlNOouozr1kiDCcm/MgYg3XZzhiJazE0Mixe528V?= =?us-ascii?Q?G2JFNVJyJdsFBPYFzoYI5I0T1mXvZqv5Rfa+elfaotk+2WPCYYOmUlaciRI7?= =?us-ascii?Q?RgMlFMZ/zEMZcypu5iwtK7qjnSDgx6IDfwmQ+RuVoFD77DZ5GPOpjxPmMbMR?= =?us-ascii?Q?FzSE4c34/4PQTNG7++Wgw2OGp0/IFyhyvEN9iVENzZod8QCsTZvql8U+L5fd?= =?us-ascii?Q?ak9Sdt/VGp166X6gzgwH119gwZmw1XVxsz7Eg+4X0q6NOyN/19UJSgIgMSY1?= =?us-ascii?Q?6BP/jua2JUpkhsXsSPMEhJDbnYuhUWrf/xJNr6a1EO9X9106YaDwoAgeGZnC?= =?us-ascii?Q?xGYCHhvvHyOkP0LSGR3X+e2LFlO8UCNP5CCBNN4aUAGPU62aLzkJU0fRqd5s?= =?us-ascii?Q?o7k84cEGSONiZaK1ZzvAp25/AzChJWzl2OjWFfP0B6sMr2OQRh9AG5lW3Uzs?= =?us-ascii?Q?3q1llVI5myLbmj3sc9a1xvM24JXyzYnn8vvhN/r1euZ+KKoy8P2CZzzT8ysn?= =?us-ascii?Q?bXTq9BKYDd5grpVZr3h0qIc41ydHQvJQtnk5DzpoHS2hqv1fVLlkDAugEZwi?= =?us-ascii?Q?5XCJIUUHsk4K/SjeH20lkAol3MO4+tpLKqi8pEK898IjXMywnDrSimU2iZnu?= =?us-ascii?Q?CYTNGBVb7E4Pml0mkIZ9dTlCFPpQzIJMgvg69y52i3IIBJwr5nVrcHNQ=3D?= =?us-ascii?Q?=3D?=
X-Forefront-PRVS: 0374433C81
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(7370300001)(4630300001)(6009001)(39830400002)(39400400002)(39450400003)(39410400002)(24454002)(5660300001)(25786009)(305945005)(7350300001)(23726003)(110136004)(189998001)(6116002)(38730400002)(53936002)(6246003)(478600001)(57306001)(2950100002)(6916009)(6666003)(2906002)(42186005)(558084003)(50226002)(8746002)(1411001)(81166006)(47776003)(8676002)(76176999)(50986999)(229853002)(86362001)(6486002)(4326008)(53546010)(50466002)(54906002)(82746002)(7736002)(33656002)(83716003)(36756003); DIR:OUT; SFP:1101; SCL:1; SRVR:CY1PR06MB2218; H:[IPv6:2001:67c:370:128:9d2d:9209:120d:57b0]; FPR:; SPF:None; MLV:sfv; LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; CY1PR06MB2218; 23:826q2XkzGWSmH557q/+m6/pWGvLHuFrRMkSEO04mF?= =?us-ascii?Q?5oOl7AmUenoOuT2XalctW2TI8ljKoPv5nfxSpF3bXuaIYLuCdkTFdplqbBLv?= =?us-ascii?Q?QmsZZ5DL8G9wgYUg7r9/AIf+SpZoK8461tqgBeuN+5eWpE0Il/KPcv7iZoTs?= =?us-ascii?Q?oDa0TMAOvLOXC7EtqlpZUSsWnCG1RRCzl5Q3f5QxCcqmtJYc/90EEMf+VCgD?= =?us-ascii?Q?SvvCzKEkHu5z9XeSfdiZ7epXJzDYya05/iJKEWzAm3f2OzIEWPFUHM1F/adI?= =?us-ascii?Q?/roWN/V2COQjiS4WjqdVmswsjhOonPyAIO/PrGOPawz6zeYK9sJ2ZR3iwC9H?= =?us-ascii?Q?uksvZ+BzEO6rW8lVkhvySwoszyN/pfnV+5mTMT1LcqtxtPvmK6lYKKv/j79t?= =?us-ascii?Q?JrQgoHbbZflpDPXLckJ9lsnx+iKxfeGAj5W9PiGEGB9CvtwNxZT+ZbuhzVEc?= =?us-ascii?Q?TkOBttNb4S84qRLziOsec944M+QOJbBltahv2BdoilhA77LJKdG4AcTRMh8h?= =?us-ascii?Q?eCz7DMzX7oULyZmKrWwJYN8dVNAsRDmUboG/Zj2tP2mYg1JuTdaAThWYGoNO?= =?us-ascii?Q?Oaz6FNHlzBfwp9aWA+S2qgOLxxxF+GKy1qVR02/Mzd3Qnfyk/pYVy/v8Hc4x?= =?us-ascii?Q?wTpX00mD5+nNuGPrL4aWVEt/3FisHSK5f8uDGdYBaWl26f1Bl9ofIpRWf30a?= =?us-ascii?Q?iAFkXPl4FnfS8m8haQs0/e7bwsLabM7Hbm2e5TSao1OkDQUtG5OBfM4I/WZQ?= =?us-ascii?Q?PrwBG4ScarYkIbYeHb/xKmCszWNssTox1L58rQa28Dfyp07mebdJGIjf5TFg?= =?us-ascii?Q?rldX2VWBgy3bXZuMFNYQF4sJP0GwPskchEMRTbb+4JMZD7zXP24iP7NPydq3?= =?us-ascii?Q?Uy4LPvMGuBaWguRHExNh7ODRzpvxxxQIaL9zLT3cdWpIA2jbFzEG0k3pM0dl?= =?us-ascii?Q?ftsBSW5qqZQmbToaufHaL7258+cl0zlZn2IMelA4QFdJr8Byd5JOa7mtjupl?= =?us-ascii?Q?FaFJb+6N1E3cdUKm86ggI5gpYLmj0jf1rmYpqu+buoqK3vU3Jd/g9tzov5Dw?= =?us-ascii?Q?YRQgrrrz9w9PFnElNj0vojxZWx2PQiMVodnrqeL/xJHNWUEtE59yq54++Z1r?= =?us-ascii?Q?iHuWJdKGyeWrO6uL8TiQrbcMs8Oi95xkE6bwwbRCSCzM2B+23xS3lBn0OLEE?= =?us-ascii?Q?i2NKfqUQ/8ReTs=3D?=
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; CY1PR06MB2218; 6:49NjfVhnCF0CO4ubMEc6jA0dNypBrjlt/IejLTDXA7?= =?us-ascii?Q?Sc8OOyycQzKzcy66MpqMsRxt1dK0AtcP3nFze7jKhBNGZn52WFr9weOFZMpl?= =?us-ascii?Q?yKRuOUO/fcbcTU9vgWVcnBAEzwzp34jHEMsKx0pF6HHJJPy3aQtdokem/vjq?= =?us-ascii?Q?B2FqFzfOmWQNtYlJAY/DFBOxph5D+bqIPBSiBTyoW/L9yOUYYjsWZwEjjNYL?= =?us-ascii?Q?msVoIo/ToFXV1pAp61mWJcEPxVM1TjEtVXaqZqKAPuFqhvbpONTgyQhaZuUY?= =?us-ascii?Q?UuNGICl+uABOWTPIIYLA0+xz+Vh/wdQXNNmct1250sjuh4ujg2LsIhjPExZi?= =?us-ascii?Q?nnUvrE7KrjOhJVsDQ2jMQMMDqXtq/WX3ibKAJIZp5syal+ioKXGvX9in1p3R?= =?us-ascii?Q?76JFt9sUQ2SkxDACk9ldmPguJHLhFUilZ5eAxbUQEC3o7YJ2IwSwHnYHZIVL?= =?us-ascii?Q?l1JXw5ECBQFR0/BtWyxV1/B2YL0b5fBaQFmytFak7JFKxYlU6EWU1NxyvtFv?= =?us-ascii?Q?bCuurLhUZQrSrOb9qwM1NMWpgyIni2Vm4QUbdyrCjoIjJulm1PNUQbXsk0+3?= =?us-ascii?Q?06CSPR/S/RSi+a29ksP+drUvXDNJNnAIJ00O03p3OjHRp9V21AURWVqBdSJ5?= =?us-ascii?Q?KuCwowAM+0HlsgyNIVyevD/i+nhx/VkujLgu8roZYqwSC+XuCCv3xHTtkxQa?= =?us-ascii?Q?bAORQKrm7BAxvEcAqnOzKzFij7TE7BMUPDiX8jxHtuvA7koqaB350yMuIk7W?= =?us-ascii?Q?b1/xI6RDjt4OC7cHbb95LB6WwP7ATU82M3+gHbeZVVStPCgwZmSS+A/qhCwb?= =?us-ascii?Q?j5CXG97lVqiSDQ0z3jxZXxGvPbxb3E0lrR7d9jS38ytElgO8nvfdUB8DsA8Q?= =?us-ascii?Q?KC9YTzM91FSszjaU+NlSEE4W9hl787s39XUNBWsYkOgsAGZfmSbTfAiXAK6J?= =?us-ascii?Q?FisgbFr50XlR3Muhil8yXo5c2dU5wF/lGEhQxq56i5s4x2n+INdSRpi9JVkW?= =?us-ascii?Q?c=3D?=
X-Microsoft-Exchange-Diagnostics: 1; CY1PR06MB2218; 5:nzGPCSZePFZl4J8VHeaFOb8A3LII36OHgWTY/Brk86VRkOLVLYMupX9o3irkdR2W6icfVWKFmuSmc+0mYy46GE3NAv3dVWmWy+CfW++wZNLRcNpTG4zLpduo6oz2B5jEOF7Hrn4zDciX0nz+jHyhzGjKGVbBBAmE6sAwyQ3CPTMPO2dFPSugfWH9HJer/vLO4rq/h1UkdvLHU9doyTrerUwGYMxqDsWWYm1TkFCbNZF8gkm5RhxznXU/ulTQ2w3MnGg4CWIkRtGhbxzEYryeVv42pSO4jjk0Bj1zJFaQZAVUG+giBOysZxr+5hKAWAt+LizKpyhGo83NceXSrVp/3tcxvB4VhFeiMfD7IMTRaYKlnYFoYMgFLuYDqTFU+7CeEhWn/DaWHSUd7DHlul5ev2k2bbV85CVJgMyWIXuPSv+HI//pZUd+HymYRT65SP2/MQu9j5Ot+pbSOWksQOphsmFvmI2V+UdOaWHA2aBLw+md1LZ91Ae435xVGuaPTNJn; 24:pICu5RMjPQX3cDAWXy7hJ/JWDSUEGJltIGKSkLx4f2jer/+3Qfl9AXRQaVfSZD8s5m2SQuiEkZmNOJVcaseViYvPTQWpIkopYQzC6UBDz9U=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; CY1PR06MB2218; 7:JITUTuL0/h/s+gVFA4r/q0W6PW28jPpJ2xrNh+KBg7cUQXt02okkyxcV8lKyX6fiqrwctTNtj/GKyehPMc+WCKYj5ZpZEHfuFnoCI6rTx+7gIeB6ZYJ8Vy6k3EH3DgEymdMSAldZvtbCd408H7asmkurjacUTzNNblLISWmxJ+Byqktb3lUEXA68r8jE5mnYnSAynVaiFmt+rH+QAqcxsi9f0liIMZUZp54c50O9lElh4SYcq3Iu/lcyoLJdnrhQZlFJhc3ed3Ia4bfigXR+AJNYTf7LO81ngIGh40eVSv4t3bzma2D558pWMG47qXAhFdotVkqXZvQD1vtG23jqAWS2DPlr5+tmoCokE9Zsy05tCdsshpVpZmZWOei1lugjea/yvS88pxGJ/whsOCj3MjW6lz6gEvdY6ycx1OAYV/4V26lDIyz2OuKFQqrfJHf6xFqMn7NdnWlHgWrBeV1gQq4oS87a5JJqdO3Hy6tjkjhVsM0FMHyAkPceSyFLBGj8eI3kffV8imdYIeFaGn4iyy0t5/0yz+zFB1lt53J0xxs2+x+VbkhnlqRRC8czKgq3HMcJpmfogbtn3UP4fr68Ep36+vlI/yhOX6mATWdfTmNot9XrI1q3meyUGtuA8buPTvlfMoc4Zz6t08q2XKp9Qg1GtFCEkppsCICgD1ujO5AYfxvUKqwxJ2xKAoVWl4CkI9TB7cLc/L1JmotvJPsHY+QrQu8Jd1cbs3NYKugSDVuoTj+t+SkxA+F6mP/qCPjNyGsHD6yqtRiiBCwuw05BuUGPoTIL9NVke6Y5jloAf3E=
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 20 Jul 2017 14:06:46.6146 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR06MB2218
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/b4uYDBgeTB-px4aABXZMwxYiY5s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 14:06:51 -0000

> On 20 Jul 2017, at 16:01, Andrew G. Malis <agmalis@gmail.com> wrote:
>=20
> Mat,
>=20
> On my badge, the registration number is printed on the back, under the =
bar code.

Impressive eyesight!

Mat


From nobody Thu Jul 20 07:09:46 2017
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EE0112704A for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 07:09:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-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=yitter.info header.b=WZ2gdMMY; dkim=pass (1024-bit key) header.d=yitter.info header.b=EiEu1HWU
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 s1oJyeJ-SBYF for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 07:09:44 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 290F6126CD6 for <ietf@ietf.org>; Thu, 20 Jul 2017 07:09:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 88500BD996 for <ietf@ietf.org>; Thu, 20 Jul 2017 14:09:43 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1500559783; bh=01zhaZwkbpnNVJeaFa68QHMOgzqXoIfRL72Lk+ww8ws=; h=Date:From:To:Subject:References:In-Reply-To:From; b=WZ2gdMMYQrS9UENGStTRFipInj2B6L8GbFoAjE2hyrbK5+CRtfcggLNPdWtM9MKpu p84lOCqduXrvZ19CMGfM9zA5xhuASl+iZlLHzWBweFPRqGVidlBM21npJ3V360OmDL uj/fvXs7CRr8sXuB2yE2hfKvThwwStoE7zO1Fmag=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xFGG1FPZ8CbC for <ietf@ietf.org>; Thu, 20 Jul 2017 14:09:42 +0000 (UTC)
Date: Thu, 20 Jul 2017 10:09:37 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1500559782; bh=01zhaZwkbpnNVJeaFa68QHMOgzqXoIfRL72Lk+ww8ws=; h=Date:From:To:Subject:References:In-Reply-To:From; b=EiEu1HWU0erMgWHFz77Z05YD+KlC0KZ7/a0y2xVkHw3cw+ggoNVpnZxR9YewgZFiC hh6izwbxWKLMXeumqJm76o9lvkhYZ1m3eSPwqVWt0V5pNKs3gGQNZGVH7SJkp05P/w WFQdnyDdLH4mK1BgjyPzSmUV4ttcdTd74JZ/ZhEE=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: quick observation about remote participation registration
Message-ID: <20170720140937.fa626yjuoiqhggjz@mx4.yitter.info>
References: <20170720125927.lbmtvwo3dncmoxmb@mx4.yitter.info> <A9FABAF6-91CB-4BD7-82F8-F20FFC8C513B@isoc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <A9FABAF6-91CB-4BD7-82F8-F20FFC8C513B@isoc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jhdbCHXn6TTJnXaIz6MJ_-tJ7bU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 14:09:45 -0000

On Thu, Jul 20, 2017 at 03:21:22PM +0200, Matthew Ford wrote:
> 
> Having my IETF registration number on my badge

It would have helped me to realise that it was the same registration
ID :-) This is probably user error, then, or at least a bit that was
unclear.  But I guess this is part of the same point I was trying to
make, in that it used to be a trivial alternative and now it is more
work.  Registration might still be a good thing; I just want us to be
clear what we're trading.  But if the registration id is there on my
badge (and I can even read it if I take off my glasses!), the barrier
is perhaps lower.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Thu Jul 20 07:26:38 2017
Return-Path: <sbanks@encrypted.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0A5D1288B8; Thu, 20 Jul 2017 07:26:37 -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] 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 acpo2ptoQOEn; Thu, 20 Jul 2017 07:26:36 -0700 (PDT)
Received: from aws.hosed.org (aws.hosed.org [50.16.104.137]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFDDE120725; Thu, 20 Jul 2017 07:26:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by aws.hosed.org (Postfix) with ESMTP id 1EAE9803BE; Thu, 20 Jul 2017 10:26:35 -0400 (EDT)
X-Virus-Scanned: Debian amavisd-new at aws.hosed.org
Received: from aws.hosed.org ([127.0.0.1]) by localhost (aws.hosed.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dxAJmqYdJmNd; Thu, 20 Jul 2017 10:26:35 -0400 (EDT)
Received: from dhcp-98c1.meeting.ietf.org (dhcp-98c1.meeting.ietf.org [31.133.152.193]) by aws.hosed.org (Postfix) with ESMTPSA id 8255B80368; Thu, 20 Jul 2017 10:26:34 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Registration for IETF 100 Opening Tomorrow
From: Sarah B <sbanks@encrypted.net>
In-Reply-To: <150055914463.22594.9866834513217613827.idtracker@ietfa.amsl.com>
Date: Thu, 20 Jul 2017 07:26:32 -0700
Cc: IETF Announcement List <ietf-announce@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <AB9E1B12-6A07-4343-8F04-FD45155C6672@encrypted.net>
References: <150055914463.22594.9866834513217613827.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KATTGayQdQRU8F72sG17tUEECDk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 14:26:38 -0000

For those of us on airplanes when this happens.. anyone know what =
hotel(s) are close to the venue?

Thanks
Sarah

> On Jul 20, 2017, at 6:59 AM, IETF Secretariat =
<ietf-secretariat@ietf.org> wrote:
>=20
> Registration for IETF 100 in Singapore will open tomorrow, Friday, =
July 21 at 15:30 CEST. Worldwide times at =
https://timeanddate.com/s/37rk. An announcement opening registration =
will be made at that time.
>=20
> Hotel reservations will also be open.
>=20
> Letters of Invitation may be requested during registration.
>=20
> - IETF Secretariat


From nobody Thu Jul 20 07:34:34 2017
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 699F6131C34; Thu, 20 Jul 2017 07:34:32 -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 xfpr1biACHah; Thu, 20 Jul 2017 07:34:26 -0700 (PDT)
Received: from mail-qt0-x231.google.com (mail-qt0-x231.google.com [IPv6:2607:f8b0:400d:c0d::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 12657129B62; Thu, 20 Jul 2017 07:34:26 -0700 (PDT)
Received: by mail-qt0-x231.google.com with SMTP id b40so24967232qtb.2; Thu, 20 Jul 2017 07:34:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=sAhp8JMYkWjlCl07gAWqff0tZNMYwwGAXgStwvVsVK8=; b=TjNB4QKoTWChc/1hAOW1MxdTT3JlkclQVdRQ1BZmWFMvnnasD2EzmTpI26VKOM9uvY txr3TWtiAmh8siXeduI4vrHTyDl+DHsBe3eJKsT/ObbSvrRGR9BtPa0qmrvgA2ODRj14 YBkz5k5Jw9aRQ7OIxJ0vG1e+xqURsVBLXLcI22I0oALslCBiusvYP6+IqpCbvb7NYoxE NOJ6woj8q2RqhyvsPJZGA2/VUw7K6P/1QoBZw6muDpCYM4u3LM04BuqhYcsm10urY2KR Sn7GMjvR4OyN/DezAWSECPuYucUJY3DheBKaWLABoJQ0gHQ/UEaKgZNjk4WfRXUMvdXt KgnA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=sAhp8JMYkWjlCl07gAWqff0tZNMYwwGAXgStwvVsVK8=; b=ejXVUvEjwi7wXIGmB6Lwj5jJzQw5VdFuuYPc9SjVNdnvIwpK7Lg3HkwkQ4oyQyRSoB Bv258col0fAAJ9SVrLBh82FSJScAAgvkjKjU++0oF8/tLLhFN6GubRbDrFJs5C914w+Y blyMtLWX600H+kYcD94ILlPXnZOrB67GVENKHSTZhTxWJzs5VH7JQjjWfG13JaTWHGL/ pE4ozeyY/gjZibPKCDbQRHNFOIuuSoxpi+uk04Q4y5buBLP500mhjC/6umnz1bkP6bBa mZDRkZy7+nG2z4oSjlc2oSSLpT8xf3FWMYPWQ+pjsZMr0cFe2Z1sh61vrLP648QNEWyd mqEw==
X-Gm-Message-State: AIVw111hJ7i4G1pX7EwHmz0p/R1Oo1cs4efmIL4SQ2zym8oxkI4NJdfT H70F1k1a8sQA5la1UBW9poi0jQFdSKVD
X-Received: by 10.200.33.194 with SMTP id 2mr5300693qtz.269.1500561265235; Thu, 20 Jul 2017 07:34:25 -0700 (PDT)
MIME-Version: 1.0
Sender: christopher.morrow@gmail.com
Received: by 10.140.86.39 with HTTP; Thu, 20 Jul 2017 07:34:24 -0700 (PDT)
In-Reply-To: <AB9E1B12-6A07-4343-8F04-FD45155C6672@encrypted.net>
References: <150055914463.22594.9866834513217613827.idtracker@ietfa.amsl.com> <AB9E1B12-6A07-4343-8F04-FD45155C6672@encrypted.net>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Thu, 20 Jul 2017 16:34:24 +0200
X-Google-Sender-Auth: woRiv0bjfztzxhP6YRFT1vmhr3I
Message-ID: <CAL9jLaZfeTMAz_Mw5ACJt1VtpdX=JOxr4cEFQ7Tp+TL-X9VHSQ@mail.gmail.com>
Subject: Re: Registration for IETF 100 Opening Tomorrow
To: Sarah B <sbanks@encrypted.net>
Cc: ietf <ietf@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>
Content-Type: multipart/alternative; boundary="001a113eeef82d9bec0554c0a59f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Q8rBJFkoTSNT76qGqkD3EpZPTIc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 14:34:32 -0000

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

On Thu, Jul 20, 2017 at 4:26 PM, Sarah B <sbanks@encrypted.net> wrote:

> For those of us on airplanes when this happens.. anyone know what hotel(s)
> are close to the venue?
>
>
I've said this before, but... use your favorite mapping application on the
web and 'nearby' or 'search near' or ...
I see a list of ~20 properties near the raffles.


> Thanks
> Sarah
>
> > On Jul 20, 2017, at 6:59 AM, IETF Secretariat <ietf-secretariat@ietf.org>
> wrote:
> >
> > Registration for IETF 100 in Singapore will open tomorrow, Friday, July
> 21 at 15:30 CEST. Worldwide times at https://timeanddate.com/s/37rk. An
> announcement opening registration will be made at that time.
> >
> > Hotel reservations will also be open.
> >
> > Letters of Invitation may be requested during registration.
> >
> > - IETF Secretariat
>
>

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Thu, Jul 20, 2017 at 4:26 PM, Sarah B <span dir=3D"ltr">&lt;<a href=
=3D"mailto:sbanks@encrypted.net" target=3D"_blank">sbanks@encrypted.net</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">For those of us on air=
planes when this happens.. anyone know what hotel(s) are close to the venue=
?<br>
<br></blockquote><div><br></div><div>I&#39;ve said this before, but... use =
your favorite mapping application on the web and &#39;nearby&#39; or &#39;s=
earch near&#39; or ...</div><div>I see a list of ~20 properties near the ra=
ffles.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks<br>
Sarah<br>
<br>
&gt; On Jul 20, 2017, at 6:59 AM, IETF Secretariat &lt;<a href=3D"mailto:ie=
tf-secretariat@ietf.org">ietf-secretariat@ietf.org</a>&gt; wrote:<br>
&gt;<br>
&gt; Registration for IETF 100 in Singapore will open tomorrow, Friday, Jul=
y 21 at 15:30 CEST. Worldwide times at <a href=3D"https://timeanddate.com/s=
/37rk" rel=3D"noreferrer" target=3D"_blank">https://timeanddate.com/s/37rk<=
/a><wbr>. An announcement opening registration will be made at that time.<b=
r>
&gt;<br>
&gt; Hotel reservations will also be open.<br>
&gt;<br>
&gt; Letters of Invitation may be requested during registration.<br>
&gt;<br>
&gt; - IETF Secretariat<br>
<br>
</blockquote></div><br></div></div>

--001a113eeef82d9bec0554c0a59f--


From nobody Thu Jul 20 08:09:18 2017
Return-Path: <mersue@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E42F131CC2; Thu, 20 Jul 2017 08:09:11 -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, FREEMAIL_FROM=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 8VAnO9TmDKAm; Thu, 20 Jul 2017 08:09:09 -0700 (PDT)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::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 CDC671252BA; Thu, 20 Jul 2017 08:09:08 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id g127so29809297wmd.0; Thu, 20 Jul 2017 08:09:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-transfer-encoding:thread-index:content-language; bh=rF4l9cJ915fnTAWLCCAkBTk6oEfhfIW+fWl0QwzwGY8=; b=syuJDPHSoz7AYPwBPmC6Kj2flLaoWmqpXOiWadfT+Ng41NCaewH1wQrQjgQfgZ93lj 1F/eXRUEjTphtQG5MrFNJgfexzt4fuFDy4ljxv+pg+jwo7bH3rjCM3pBCJe60X8h1My+ VH0rudZ2m6pKQHGohhyYsSXWTLQYGVtf/6BWcd7JbuZveQzAfrU7vAtgJ4KfU1Mmoqap TiYcfpbbW0fqxhWl0Vfm8Ez+j017nwK44lL607UqBLjGGBZKWQ7T2XHNvPcM2VgmtwLS PaJjNGUFfzs9DcboEUoYasRcEpM+n2IF+dS4UJN0K0wjtz0o/1RSi0HLrzpEbF1d6bk/ RX1Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=rF4l9cJ915fnTAWLCCAkBTk6oEfhfIW+fWl0QwzwGY8=; b=pqzxFmcJziCRt5BxcXkh7vNUTz9IO/jbgnKmAkY/GpZp6H+UGXMh5roTWnyfW59vpE jEDLY2pdjOu/672UOTF8GuDUdaQm72U5PL3fjqZSDDnL1BG11XagsDBN/5JJTUqghj+u BwWi7d8RdMAvzHg9QWU1+I/+QI553VOu8kdyT6o3VWB3dIAfLt1OqJji0Vz6COXkeeVV FrcHtoVxFnhZXglZYJwfU1nKjeNJe+oJd38pcfCuNjJPPDqXsFErszkJkDnIYqIDNXyJ WyCcN6PUBZg8rcftLpS1EDFiDy2sXZm6tXWS19/SFNb8pIhWE7RyeovXccts2UsaIFHm QnRg==
X-Gm-Message-State: AIVw1128wSOCb72YopWXJGJvsmkNxnvNHaXwbvACgkSkTB2btnhVZ8pi GxIci26RJOPpgtzq
X-Received: by 10.28.27.67 with SMTP id b64mr2734948wmb.11.1500563347103; Thu, 20 Jul 2017 08:09:07 -0700 (PDT)
Received: from DESKTOPFLHJVQJ ([2001:67c:370:128:bc85:b00b:ab77:1d7e]) by smtp.gmail.com with ESMTPSA id u30sm3659209wru.88.2017.07.20.08.09.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Jul 2017 08:09:06 -0700 (PDT)
From: "Mehmet Ersue" <mersue@gmail.com>
To: <ietf@ietf.org>, "'IETF Announcement List'" <ietf-announce@ietf.org>
References: <150055914463.22594.9866834513217613827.idtracker@ietfa.amsl.com>
In-Reply-To: <150055914463.22594.9866834513217613827.idtracker@ietfa.amsl.com>
Subject: RE: Registration for IETF 100 Opening Tomorrow
Date: Thu, 20 Jul 2017 17:09:08 +0200
Message-ID: <00be01d3016a$2385d190$6a9174b0$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQLCdjunuT+FHy0g2AN6LhBZ7loj2KB95ozA
Content-Language: de
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7Ts1qR4B6tL3DCTt8UEs6W_WWIE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 15:09:12 -0000

https://www.google.de/maps/search/Hotels/@1.2939717,103.851142,17z/data=3D=
!3m1!4b1!4m8!2m7!3m6!1sHotels!2s80+Bras+Basah+Road,+Raffles+City+Shopping=
+Centre,+Raffles+City+Convention+Centre,+Singapore+189560!3s0x31da19a67e1=
cda67:0xbdb7ce78de402ad8!4m2!1d103.8533468!2d1.2939556?hl=3Den=20

Basically the nearest are: Raffles ($$$$), Swissotel, Fairmont

Mehmet

> -----Original Message-----
> From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On Behalf =
Of
> IETF Secretariat
> Sent: Thursday, July 20, 2017 3:59 PM
> To: IETF Announcement List <ietf-announce@ietf.org>
> Subject: Registration for IETF 100 Opening Tomorrow
>=20
> Registration for IETF 100 in Singapore will open tomorrow, Friday, =
July 21 at
> 15:30 CEST. Worldwide times at https://timeanddate.com/s/37rk. An
> announcement opening registration will be made at that time.
>=20
> Hotel reservations will also be open.
>=20
> Letters of Invitation may be requested during registration.
>=20
> - IETF Secretariat



From nobody Thu Jul 20 08:37:01 2017
Return-Path: <olejacobsen@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0781128BC8; Thu, 20 Jul 2017 08:36:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.5
X-Spam-Level: 
X-Spam-Status: No, score=-5.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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=me.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 LPeChmH7g5je; Thu, 20 Jul 2017 08:36:58 -0700 (PDT)
Received: from pv42p55im-ztdg10051601.me.com (pv42p55im-ztdg10051601.me.com [17.139.148.156]) (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 16BBE131C3E; Thu, 20 Jul 2017 08:36:57 -0700 (PDT)
Received: from process-dkim-sign-daemon.pv42p55im-ztdg10051601.me.com by pv42p55im-ztdg10051601.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OTE00700BAH8200@pv42p55im-ztdg10051601.me.com>; Thu, 20 Jul 2017 15:36:56 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017; t=1500565016; bh=M7G2ohdPMyAW7hLkEGAozn/D9rgXw5RaySA7CgBICGA=; h=Content-type:MIME-version:Subject:From:Date:Message-id:To; b=HAPK0YRnUA1QtEx9mSj5jszyI7cywBj1MOOBj5jvN0xK3mZ2MT4iYySAY1NjrtyBJ s9izxuBS7EkxFYKZI5TM2lCItn+VjE0Dp0RKBcXcYPX4k/iN89M/SpqWt7V7i14YNX Tzmh2W9fXIMWqdgkVdjg8hj63QuQ7k4MBktoG+CSBbGlsjpQX4mbzjevhQL0MwPhz9 Z6RjNQW1vGvejMb80R4gDxenfRbqpByWuvsizoxWYjetIrz//HArSOBKH/lrd75zqs VitPDWTkg1ZE93peIz8o4XP6I/UWvJ76GPZR4zyZDsLbjZ7JwWDUhKime3ratxB5bA ImYdWAFNSM1OA==
Received: from icloud.com ([127.0.0.1]) by pv42p55im-ztdg10051601.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OTE00FZNBDFS530@pv42p55im-ztdg10051601.me.com>; Thu, 20 Jul 2017 15:36:55 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-07-20_08:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1701120000 definitions=main-1707200241
Content-type: multipart/alternative; boundary=Apple-Mail-9173BBE1-1957-4E0E-BC50-0D40A77A3958
MIME-version: 1.0 (1.0)
Subject: Re: Registration for IETF 100 Opening Tomorrow
From: Ole Jacobsen <olejacobsen@me.com>
X-Mailer: iPhone Mail (14G60)
In-reply-to: <00be01d3016a$2385d190$6a9174b0$@gmail.com>
Date: Thu, 20 Jul 2017 17:36:50 +0200
Cc: ietf@ietf.org, IETF Announcement List <ietf-announce@ietf.org>
Content-transfer-encoding: 7bit
Message-id: <A06E5D20-176D-455A-A46C-EB3A71FBD320@me.com>
References: <150055914463.22594.9866834513217613827.idtracker@ietfa.amsl.com> <00be01d3016a$2385d190$6a9174b0$@gmail.com>
To: Mehmet Ersue <mersue@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gWNYzGNP8OxHUreWrTof-WQk3mE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 15:37:00 -0000

--Apple-Mail-9173BBE1-1957-4E0E-BC50-0D40A77A3958
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

If you like The Hilton Group, there is a Conrad nearby, walkable underground=
.

Ole J. Jacobsen
Editor & Publisher
The Internet Protocol Journal
Cell: +1 415 370-4628
T-Mobile: +1 415 889-9821
http://protocoljournal.org

Sent from my iPhone

> On Jul 20, 2017, at 17:09, Mehmet Ersue <mersue@gmail.com> wrote:
>=20
> https://www.google.de/maps/search/Hotels/@1.2939717,103.851142,17z/data=3D=
!3m1!4b1!4m8!2m7!3m6!1sHotels!2s80+Bras+Basah+Road,+Raffles+City+Shopping+Ce=
ntre,+Raffles+City+Convention+Centre,+Singapore+189560!3s0x31da19a67e1cda67:=
0xbdb7ce78de402ad8!4m2!1d103.8533468!2d1.2939556?hl=3Den=20
>=20
> Basically the nearest are: Raffles ($$$$), Swissotel, Fairmont
>=20
> Mehmet
>=20
>> -----Original Message-----
>> From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On Behalf Of
>> IETF Secretariat
>> Sent: Thursday, July 20, 2017 3:59 PM
>> To: IETF Announcement List <ietf-announce@ietf.org>
>> Subject: Registration for IETF 100 Opening Tomorrow
>>=20
>> Registration for IETF 100 in Singapore will open tomorrow, Friday, July 2=
1 at
>> 15:30 CEST. Worldwide times at https://timeanddate.com/s/37rk. An
>> announcement opening registration will be made at that time.
>>=20
>> Hotel reservations will also be open.
>>=20
>> Letters of Invitation may be requested during registration.
>>=20
>> - IETF Secretariat
>=20
>=20

--Apple-Mail-9173BBE1-1957-4E0E-BC50-0D40A77A3958
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=3D=
utf-8"></head><body dir=3D"auto"><div>If you like The Hilton Group, there is=
 a Conrad nearby, walkable underground.<br><br><div><div style=3D"font-famil=
y: UICTFontTextStyleBody; font-size: 18px; -webkit-text-size-adjust: auto;">=
Ole J. Jacobsen</div><div style=3D"font-family: UICTFontTextStyleBody; font-=
size: 18px; -webkit-text-size-adjust: auto;">Editor &amp; Publisher</div><di=
v style=3D"font-family: UICTFontTextStyleBody; font-size: 18px; -webkit-text=
-size-adjust: auto;">The Internet Protocol Journal</div><div style=3D"font-f=
amily: UICTFontTextStyleBody; font-size: 18px; -webkit-text-size-adjust: aut=
o;">Cell: +1 415 370-4628</div><div style=3D"font-family: UICTFontTextStyleB=
ody; font-size: 18px; -webkit-text-size-adjust: auto;">T-Mobile: +1 415 889-=
9821</div></div><div style=3D"font-family: UICTFontTextStyleBody; font-size:=
 18px; -webkit-text-size-adjust: auto;"><a href=3D"http://protocoljournal.or=
g">http://protocoljournal.org</a></div><div><br></div>Sent from my iPhone</d=
iv><div><br>On Jul 20, 2017, at 17:09, Mehmet Ersue &lt;<a href=3D"mailto:me=
rsue@gmail.com">mersue@gmail.com</a>&gt; wrote:<br><br></div><blockquote typ=
e=3D"cite"><div><span><a href=3D"https://www.google.de/maps/search/Hotels/@1=
.2939717,103.851142,17z/data=3D!3m1!4b1!4m8!2m7!3m6!1sHotels!2s80+Bras+Basah=
+Road,+Raffles+City+Shopping+Centre,+Raffles+City+Convention+Centre,+Singapo=
re+189560!3s0x31da19a67e1cda67:0xbdb7ce78de402ad8!4m2!1d103.8533468!2d1.2939=
556?hl=3Den">https://www.google.de/maps/search/Hotels/@1.2939717,103.851142,=
17z/data=3D!3m1!4b1!4m8!2m7!3m6!1sHotels!2s80+Bras+Basah+Road,+Raffles+City+=
Shopping+Centre,+Raffles+City+Convention+Centre,+Singapore+189560!3s0x31da19=
a67e1cda67:0xbdb7ce78de402ad8!4m2!1d103.8533468!2d1.2939556?hl=3Den</a> </sp=
an><br><span></span><br><span>Basically the nearest are: Raffles ($$$$), Swi=
ssotel, Fairmont</span><br><span></span><br><span>Mehmet</span><br><span></s=
pan><br><blockquote type=3D"cite"><span>-----Original Message-----</span><br=
></blockquote><blockquote type=3D"cite"><span>From: IETF-Announce [<a href=3D=
"mailto:ietf-announce-bounces@ietf.org">mailto:ietf-announce-bounces@ietf.or=
g</a>] On Behalf Of</span><br></blockquote><blockquote type=3D"cite"><span>I=
ETF Secretariat</span><br></blockquote><blockquote type=3D"cite"><span>Sent:=
 Thursday, July 20, 2017 3:59 PM</span><br></blockquote><blockquote type=3D"=
cite"><span>To: IETF Announcement List &lt;<a href=3D"mailto:ietf-announce@i=
etf.org">ietf-announce@ietf.org</a>&gt;</span><br></blockquote><blockquote t=
ype=3D"cite"><span>Subject: Registration for IETF 100 Opening Tomorrow</span=
><br></blockquote><blockquote type=3D"cite"><span></span><br></blockquote><b=
lockquote type=3D"cite"><span>Registration for IETF 100 in Singapore will op=
en tomorrow, Friday, July 21 at</span><br></blockquote><blockquote type=3D"c=
ite"><span>15:30 CEST. Worldwide times at <a href=3D"https://timeanddate.com=
/s/37rk">https://timeanddate.com/s/37rk</a>. An</span><br></blockquote><bloc=
kquote type=3D"cite"><span>announcement opening registration will be made at=
 that time.</span><br></blockquote><blockquote type=3D"cite"><span></span><b=
r></blockquote><blockquote type=3D"cite"><span>Hotel reservations will also b=
e open.</span><br></blockquote><blockquote type=3D"cite"><span></span><br></=
blockquote><blockquote type=3D"cite"><span>Letters of Invitation may be requ=
ested during registration.</span><br></blockquote><blockquote type=3D"cite">=
<span></span><br></blockquote><blockquote type=3D"cite"><span>- IETF Secreta=
riat</span><br></blockquote><span></span><br><span></span><br></div></blockq=
uote></body></html>=

--Apple-Mail-9173BBE1-1957-4E0E-BC50-0D40A77A3958--


From nobody Thu Jul 20 08:47:36 2017
Return-Path: <ietf@meetecho.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E003131C73 for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 08:47:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.701
X-Spam-Level: 
X-Spam-Status: No, score=-4.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=aruba.it
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 JvAfgwGlPMHO for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 08:47:32 -0700 (PDT)
Received: from smtpweb126.aruba.it (smtpweb126.aruba.it [62.149.158.126]) by ietfa.amsl.com (Postfix) with ESMTP id 3412412EC46 for <ietf@ietf.org>; Thu, 20 Jul 2017 08:47:32 -0700 (PDT)
Received: from [31.130.230.90] ([31.130.230.90]) by smtpcmd03.ad.aruba.it with bizsmtp id n3nT1v01D1xgSgX013nUZW; Thu, 20 Jul 2017 17:47:30 +0200
Subject: Re: quick observation about remote participation registration
To: John C Klensin <john@jck.com>, Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
References: <20170720125927.lbmtvwo3dncmoxmb@mx4.yitter.info> <30D585774FDAF7F5158A6A26@PSB>
From: Meetecho IETF support <ietf@meetecho.com>
Message-ID: <04dbc05e-1c6b-d62c-8d21-6591b3f2d4d5@meetecho.com>
Date: Thu, 20 Jul 2017 17:47:24 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <30D585774FDAF7F5158A6A26@PSB>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aruba.it; s=a1; t=1500565650; bh=Bk6TcSPo245hPtCLF7eWSi2BBCBbT9qG2lGYoztiefc=; h=Subject:To:From:Date:MIME-Version:Content-Type; b=F/xulbicveRT78qPFfE3DCr089qIA9X9wxqCzQR05AKDzaaEp3+DFL/wb2+1s/Ldi FgCv0bfVwklawKstVLo+QqCx1lscVXe/AAD9flHkCq1z03i1QLaeFiqAEZF5HQ0XE5 DNI5nhmwZEDYw43Km6a62fQCh9xWtWAImLIX9+qf0Z2zkWTqX2sOhE8hqSzlwUSubw Zdy9t3nUUhgtpGdXRXeGK2iePHu/F36fiIRQ+gfaK0YfwggIf6ofT/5zMOiKTEa8Wv cRxBtVigUj+7NMyXY0v8Aj1M34auwBo0MFclZe6uTgNVtsXwsDLrj14Z1am1p2KD65 FbKIE4eCTrzDQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/udza4Va7iZcfSSkOW4ZdIpcaXGk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 15:47:35 -0000

> the registration code for on-site registrations should simply work in
> Meetecho.

It does indeed. Each registered participant (either on-site or remote) 
can access Meetecho through their Registration ID.

Regards,
the Meetecho team

Il 20/07/2017 15:22, John C Klensin ha scritto:
> Andrew,
>
> I would think that this should be even easier because, unless someone
> can think of a reason to not do so, the registration code for on-site
> registrations should simply work in Meetecho. Putting you through a
> second registration/ signup procedure when you are already registered
> for the meeting (and, in your case but less in Spencer's use of
> in-room Meetecho was slide viewer, likely in a hurry) seems like
> unreasonable bureaucracy.   If we need to keep a distinction between
> on-site and off-site remote participants, that distinction should be
> embedded into the registration codes, not require the user to pretend
> to be two people (which would actually distort the statistics).
>
> john
>
>
> --On Thursday, July 20, 2017 08:59 -0400 Andrew Sullivan
> <ajs@anvilwalrusden.com> wrote:
>
>> Dear colleagues,
>>
>> This is just an anecdote, but today I got to a room that was too
>> crowded (I was late because of another obligation). Unwilling to
>> crawl over people, since I was the late one, I went back into the
>> hall.  In previous meetings I used meetecho to follow along in this
>> case, but since I hadn't registered it was a little troublesome.  I
>> just used the audio, and it's no big deal, but it might be a useful
>> illustration of one bit of friction that comes because of the
>> remote registration thing (unless everyone registered on-site
>> automatically gets a remote registration too, maybe conveniently
>> printed on the badge or something).
>>
>> Note that I am _not_ saying this proves anything about whether
>> registration is a good or bad idea or whatever.  I only mention it
>> as another anecdote (and of course, in one sense the plural of
>> "anecdote" is too "data").
>>
>> Best regards,
>>
>> A
>
>
>
>


From nobody Thu Jul 20 08:53:48 2017
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2C46131C96; Thu, 20 Jul 2017 08:53:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, 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 jPZVkKmIzKF0; Thu, 20 Jul 2017 08:53:43 -0700 (PDT)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (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 4DEDC1252BA; Thu, 20 Jul 2017 08:53:35 -0700 (PDT)
Received: by mail-wm0-x22c.google.com with SMTP id l81so8250942wmg.1; Thu, 20 Jul 2017 08:53:35 -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=/J1WmpIU3l2UUZYBc+GkFMacCTczucqDoJT4c2xnJcI=; b=N+EHAX7f5q0oo3Dc5R9s6nGo4DW6gxWj3j9IXG00x87v/01fH1Tk3+bFwWELXfwNI+ OEovGcs+jZsa9wUMmrzmxfCf9tI2fRLDsAG9FvV8TekcirB85B3KY7nU1fyoZwD+LO+S xwSd7m64+kNaLXEB351neSfHetYO+nH3fEdRV1XNQ6GNh0mycnV6sFiNTGAPEGDbiXuY APh5bD8tailW8g5WKJnzfdZOCnuqkgzE/MZLKICsbKBxwAkcZkcT1htpfw8ALS3Lw1BN 8HSa9oqylJ92i+UY7u50lmBPF+ymlswKgiRmPK9nOaFuxz4mxsD396DC13yrbviiQUYw tLaQ==
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=/J1WmpIU3l2UUZYBc+GkFMacCTczucqDoJT4c2xnJcI=; b=gsdvV8n8S7vqpNNjjVLKRIIZcnRJ0gR1lvI1OmF1HASmYgWZF4Fsg+81MI5iie8s/A LImE49DjnmKNeHpwWP3MIwuQOCcE2+ZzH9yI6eEWugpiZB6OOUNZmX6ouYPm17hqm2nS avItj6DeJooVm76q+W+/BiHFxCiLJ6z6TBLjpH4nnZhQul95koRq+SYhptMT9Oa3+Gin qL0rwuE8GHffEpaAxVXJ5BrGdMXMFW/uPlXlf8H5RQZjjIT85H/RN6eNTCKs7gZ8KI1H WtRzbpoIo7QLbKGdfA52cxd15ulF3mTW+FgsdEFisqOi7dr2427VhTzMjMWa/GAU2xZq 8hJg==
X-Gm-Message-State: AIVw113cpx3xj8+9Z9FMMwmUORNIKGenjBUR7uZsfz8BAb+QIycxQGk+ 8S3szxeYHf29Ll6eeKcx4CQlQolrZw==
X-Received: by 10.28.71.5 with SMTP id u5mr2946534wma.138.1500566013909; Thu, 20 Jul 2017 08:53:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.138.212 with HTTP; Thu, 20 Jul 2017 08:53:33 -0700 (PDT)
Reply-To: sarikaya@ieee.org
In-Reply-To: <A06E5D20-176D-455A-A46C-EB3A71FBD320@me.com>
References: <150055914463.22594.9866834513217613827.idtracker@ietfa.amsl.com> <00be01d3016a$2385d190$6a9174b0$@gmail.com> <A06E5D20-176D-455A-A46C-EB3A71FBD320@me.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Thu, 20 Jul 2017 10:53:33 -0500
Message-ID: <CAC8QAcdHdR4a_rmTvAy+1rqxv6SEWTnztA9jaH9HW=8A=Yw+hQ@mail.gmail.com>
Subject: Re: Registration for IETF 100 Opening Tomorrow
To: Ole Jacobsen <olejacobsen@me.com>
Cc: Mehmet Ersue <mersue@gmail.com>, IETF <ietf@ietf.org>,  IETF Announcement List <ietf-announce@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c0720fc38a4390554c1c070"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2BCi-YHBYusz_6oQ3cm5z3hDYsQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 15:53:46 -0000

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

Is Hilton going to have special price for IETF?



On Thu, Jul 20, 2017 at 10:36 AM, Ole Jacobsen <olejacobsen@me.com> wrote:

> If you like The Hilton Group, there is a Conrad nearby, walkable
> underground.
>
> Ole J. Jacobsen
> Editor & Publisher
> The Internet Protocol Journal
> Cell: +1 415 370-4628 <(415)%20370-4628>
> T-Mobile: +1 415 889-9821 <(415)%20889-9821>
> http://protocoljournal.org
>
> Sent from my iPhone
>
> On Jul 20, 2017, at 17:09, Mehmet Ersue <mersue@gmail.com> wrote:
>
> https://www.google.de/maps/search/Hotels/@1.2939717,103.
> 851142,17z/data=!3m1!4b1!4m8!2m7!3m6!1sHotels!2s80+Bras+
> Basah+Road,+Raffles+City+Shopping+Centre,+Raffles+City+
> Convention+Centre,+Singapore+189560!3s0x31da19a67e1cda67:
> 0xbdb7ce78de402ad8!4m2!1d103.8533468!2d1.2939556?hl=en
>
> Basically the nearest are: Raffles ($$$$), Swissotel, Fairmont
>
> Mehmet
>
> -----Original Message-----
>
> From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org
> <ietf-announce-bounces@ietf.org>] On Behalf Of
>
> IETF Secretariat
>
> Sent: Thursday, July 20, 2017 3:59 PM
>
> To: IETF Announcement List <ietf-announce@ietf.org>
>
> Subject: Registration for IETF 100 Opening Tomorrow
>
>
> Registration for IETF 100 in Singapore will open tomorrow, Friday, July 21
> at
>
> 15:30 CEST. Worldwide times at https://timeanddate.com/s/37rk. An
>
> announcement opening registration will be made at that time.
>
>
> Hotel reservations will also be open.
>
>
> Letters of Invitation may be requested during registration.
>
>
> - IETF Secretariat
>
>
>
>

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

<div dir=3D"ltr">Is Hilton going to have special price for IETF?<br><br><br=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Ju=
l 20, 2017 at 10:36 AM, Ole Jacobsen <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:olejacobsen@me.com" target=3D"_blank">olejacobsen@me.com</a>&gt;</span> w=
rote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex"><div dir=3D"auto"><div>If you like =
The Hilton Group, there is a Conrad nearby, walkable underground.<br><br><d=
iv><div style=3D"font-family:UICTFontTextStyleBody;font-size:18px">Ole J. J=
acobsen</div><div style=3D"font-family:UICTFontTextStyleBody;font-size:18px=
">Editor &amp; Publisher</div><div style=3D"font-family:UICTFontTextStyleBo=
dy;font-size:18px">The Internet Protocol Journal</div><div style=3D"font-fa=
mily:UICTFontTextStyleBody;font-size:18px">Cell: <a href=3D"tel:(415)%20370=
-4628" value=3D"+14153704628" target=3D"_blank">+1 415 370-4628</a></div><d=
iv style=3D"font-family:UICTFontTextStyleBody;font-size:18px">T-Mobile: <a =
href=3D"tel:(415)%20889-9821" value=3D"+14158899821" target=3D"_blank">+1 4=
15 889-9821</a></div></div><div style=3D"font-family:UICTFontTextStyleBody;=
font-size:18px"><a href=3D"http://protocoljournal.org" target=3D"_blank">ht=
tp://protocoljournal.org</a></div><div><br></div>Sent from my iPhone</div><=
div><div class=3D"h5"><div><br>On Jul 20, 2017, at 17:09, Mehmet Ersue &lt;=
<a href=3D"mailto:mersue@gmail.com" target=3D"_blank">mersue@gmail.com</a>&=
gt; wrote:<br><br></div><blockquote type=3D"cite"><div><span><a href=3D"htt=
ps://www.google.de/maps/search/Hotels/@1.2939717,103.851142,17z/data=3D!3m1=
!4b1!4m8!2m7!3m6!1sHotels!2s80+Bras+Basah+Road,+Raffles+City+Shopping+Centr=
e,+Raffles+City+Convention+Centre,+Singapore+189560!3s0x31da19a67e1cda67:0x=
bdb7ce78de402ad8!4m2!1d103.8533468!2d1.2939556?hl=3Den" target=3D"_blank">h=
ttps://www.google.de/maps/<wbr>search/Hotels/@1.2939717,103.<wbr>851142,17z=
/data=3D!3m1!4b1!4m8!<wbr>2m7!3m6!1sHotels!2s80+Bras+<wbr>Basah+Road,+Raffl=
es+City+<wbr>Shopping+Centre,+Raffles+City+<wbr>Convention+Centre,+Singapor=
e+<wbr>189560!3s0x31da19a67e1cda67:<wbr>0xbdb7ce78de402ad8!4m2!1d103.<wbr>8=
533468!2d1.2939556?hl=3Den</a> </span><br><span></span><br><span>Basically =
the nearest are: Raffles ($$$$), Swissotel, Fairmont</span><br><span></span=
><br><span>Mehmet</span><br><span></span><br><blockquote type=3D"cite"><spa=
n>-----Original Message-----</span><br></blockquote><blockquote type=3D"cit=
e"><span>From: IETF-Announce [<a href=3D"mailto:ietf-announce-bounces@ietf.=
org" target=3D"_blank">mailto:ietf-announce-bounces@<wbr>ietf.org</a>] On B=
ehalf Of</span><br></blockquote><blockquote type=3D"cite"><span>IETF Secret=
ariat</span><br></blockquote><blockquote type=3D"cite"><span>Sent: Thursday=
, July 20, 2017 3:59 PM</span><br></blockquote><blockquote type=3D"cite"><s=
pan>To: IETF Announcement List &lt;<a href=3D"mailto:ietf-announce@ietf.org=
" target=3D"_blank">ietf-announce@ietf.org</a>&gt;</span><br></blockquote><=
blockquote type=3D"cite"><span>Subject: Registration for IETF 100 Opening T=
omorrow</span><br></blockquote><blockquote type=3D"cite"><span></span><br><=
/blockquote><blockquote type=3D"cite"><span>Registration for IETF 100 in Si=
ngapore will open tomorrow, Friday, July 21 at</span><br></blockquote><bloc=
kquote type=3D"cite"><span>15:30 CEST. Worldwide times at <a href=3D"https:=
//timeanddate.com/s/37rk" target=3D"_blank">https://timeanddate.com/s/37rk<=
/a><wbr>. An</span><br></blockquote><blockquote type=3D"cite"><span>announc=
ement opening registration will be made at that time.</span><br></blockquot=
e><blockquote type=3D"cite"><span></span><br></blockquote><blockquote type=
=3D"cite"><span>Hotel reservations will also be open.</span><br></blockquot=
e><blockquote type=3D"cite"><span></span><br></blockquote><blockquote type=
=3D"cite"><span>Letters of Invitation may be requested during registration.=
</span><br></blockquote><blockquote type=3D"cite"><span></span><br></blockq=
uote><blockquote type=3D"cite"><span>- IETF Secretariat</span><br></blockqu=
ote><span></span><br><span></span><br></div></blockquote></div></div></div>=
</blockquote></div><br></div>

--94eb2c0720fc38a4390554c1c070--


From nobody Thu Jul 20 09:44:27 2017
Return-Path: <akatlas@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6BA2131C4E for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 09:44:25 -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 C6SuQzYJhUBy for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 09:44:24 -0700 (PDT)
Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::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 D6ADA131A84 for <ietf@ietf.org>; Thu, 20 Jul 2017 09:44:23 -0700 (PDT)
Received: by mail-wm0-x231.google.com with SMTP id g127so32175903wmd.0 for <ietf@ietf.org>; Thu, 20 Jul 2017 09:44:23 -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=z75B2b4aM6txUizitObhXcwmeh659HMxlmBHtBT/MPg=; b=Sqp5S86ieHqc/i41YYGhEDlL/5iUwpu/F410xbl68LJn24VypykKIo20AUzLW3LCjj FoKtgm4Ez/5BKs4iHgRZgnw9d67br881MU2OFAjr8S2LPGnOhGEeU/39YheCJvWtxFQH KRj5dp+cJMv8RxltMEKYCFgS++LRHyG2UCYhf2P2tSxS8q3WaILKhSw5BzX4bVxucvZp BauqCVsPrcyTVWdh0qfpfwTW7LSqbdJcmNY2VKvXb93urdPFWU61MPGBphc4mNiAO9bs QQuD4n1aYrAGEh1jNqxBIHt4Axs86ab3HUqyjWT+xX+FZgdfTFzHNdvEySduZQUgADv1 Xbvw==
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=z75B2b4aM6txUizitObhXcwmeh659HMxlmBHtBT/MPg=; b=d8D+KJ1kzwmWQ7mbRRAYLk6PRl9q/dcX9C7+sZ2mDl1hm7fOg8cw4aabR4GOSd/Sxu rw01m5Jj/niCRlPru5hhhFR4R2O/hbUhpjKvCvsQKVAs1GyYJV1Wc+iKD6JrhiE7hHsT ugCt1dLr6j4rgZuhwWl4fYLOusxCF4/71hv5zXsnA+OM0BWHYOPMLyKCGnVbiu0JLvGc Ydzj7UcvfwlNDizipixJBnISuzojRWQCwH5yKvehcMREAe1ixl2h5N0sTaaspEm97Liq Vmdl33Ea+7mUGJUAa8YT7DpLOVZp8olN80ROkJfPf8d0tpDj1WiunuMz9qN4tBhHapSB g07w==
X-Gm-Message-State: AIVw1124/gAE7kVCOSHrdJTu+Mx5IzVe8YUAl39bDeXaXokc8lSyEZ00 gLgaW4h9qI7CjUN6lUQPZexkqwcZJw==
X-Received: by 10.28.155.84 with SMTP id d81mr2870506wme.163.1500569062367; Thu, 20 Jul 2017 09:44:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.183.1 with HTTP; Thu, 20 Jul 2017 09:44:21 -0700 (PDT)
In-Reply-To: <04dbc05e-1c6b-d62c-8d21-6591b3f2d4d5@meetecho.com>
References: <20170720125927.lbmtvwo3dncmoxmb@mx4.yitter.info> <30D585774FDAF7F5158A6A26@PSB> <04dbc05e-1c6b-d62c-8d21-6591b3f2d4d5@meetecho.com>
From: Alia Atlas <akatlas@gmail.com>
Date: Thu, 20 Jul 2017 12:44:21 -0400
Message-ID: <CAG4d1rdHr5BWOXdEx1thkRCUNBYbdZqUcu89C4QwMWS=k8sJHA@mail.gmail.com>
Subject: Re: quick observation about remote participation registration
To: Meetecho IETF support <ietf@meetecho.com>
Cc: John C Klensin <john@jck.com>, Andrew Sullivan <ajs@anvilwalrusden.com>,  IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a1144f60eec66290554c27533"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GtZcTxB18NPVT7R9RUsLiBJ_824>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 16:44:26 -0000

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

Thank you for being so organized and foresightful!

Regards,
Alia

On Thu, Jul 20, 2017 at 11:47 AM, Meetecho IETF support <ietf@meetecho.com>
wrote:

> the registration code for on-site registrations should simply work in
>> Meetecho.
>>
>
> It does indeed. Each registered participant (either on-site or remote) can
> access Meetecho through their Registration ID.
>
> Regards,
> the Meetecho team
>
>
> Il 20/07/2017 15:22, John C Klensin ha scritto:
>
>> Andrew,
>>
>> I would think that this should be even easier because, unless someone
>> can think of a reason to not do so, the registration code for on-site
>> registrations should simply work in Meetecho. Putting you through a
>> second registration/ signup procedure when you are already registered
>> for the meeting (and, in your case but less in Spencer's use of
>> in-room Meetecho was slide viewer, likely in a hurry) seems like
>> unreasonable bureaucracy.   If we need to keep a distinction between
>> on-site and off-site remote participants, that distinction should be
>> embedded into the registration codes, not require the user to pretend
>> to be two people (which would actually distort the statistics).
>>
>> john
>>
>>
>> --On Thursday, July 20, 2017 08:59 -0400 Andrew Sullivan
>> <ajs@anvilwalrusden.com> wrote:
>>
>> Dear colleagues,
>>>
>>> This is just an anecdote, but today I got to a room that was too
>>> crowded (I was late because of another obligation). Unwilling to
>>> crawl over people, since I was the late one, I went back into the
>>> hall.  In previous meetings I used meetecho to follow along in this
>>> case, but since I hadn't registered it was a little troublesome.  I
>>> just used the audio, and it's no big deal, but it might be a useful
>>> illustration of one bit of friction that comes because of the
>>> remote registration thing (unless everyone registered on-site
>>> automatically gets a remote registration too, maybe conveniently
>>> printed on the badge or something).
>>>
>>> Note that I am _not_ saying this proves anything about whether
>>> registration is a good or bad idea or whatever.  I only mention it
>>> as another anecdote (and of course, in one sense the plural of
>>> "anecdote" is too "data").
>>>
>>> Best regards,
>>>
>>> A
>>>
>>
>>
>>
>>
>>
>

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

<div dir=3D"ltr">Thank you for being so organized and foresightful!<div><br=
></div><div>Regards,</div><div>Alia</div></div><div class=3D"gmail_extra"><=
br><div class=3D"gmail_quote">On Thu, Jul 20, 2017 at 11:47 AM, Meetecho IE=
TF support <span dir=3D"ltr">&lt;<a href=3D"mailto:ietf@meetecho.com" targe=
t=3D"_blank">ietf@meetecho.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><span class=3D""><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
the registration code for on-site registrations should simply work in<br>
Meetecho.<br>
</blockquote>
<br></span>
It does indeed. Each registered participant (either on-site or remote) can =
access Meetecho through their Registration ID.<br>
<br>
Regards,<br>
the Meetecho team<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
Il 20/07/2017 15:22, John C Klensin ha scritto:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Andrew,<br>
<br>
I would think that this should be even easier because, unless someone<br>
can think of a reason to not do so, the registration code for on-site<br>
registrations should simply work in Meetecho. Putting you through a<br>
second registration/ signup procedure when you are already registered<br>
for the meeting (and, in your case but less in Spencer&#39;s use of<br>
in-room Meetecho was slide viewer, likely in a hurry) seems like<br>
unreasonable bureaucracy.=C2=A0 =C2=A0If we need to keep a distinction betw=
een<br>
on-site and off-site remote participants, that distinction should be<br>
embedded into the registration codes, not require the user to pretend<br>
to be two people (which would actually distort the statistics).<br>
<br>
john<br>
<br>
<br>
--On Thursday, July 20, 2017 08:59 -0400 Andrew Sullivan<br>
&lt;<a href=3D"mailto:ajs@anvilwalrusden.com" target=3D"_blank">ajs@anvilwa=
lrusden.com</a>&gt; wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Dear colleagues,<br>
<br>
This is just an anecdote, but today I got to a room that was too<br>
crowded (I was late because of another obligation). Unwilling to<br>
crawl over people, since I was the late one, I went back into the<br>
hall.=C2=A0 In previous meetings I used meetecho to follow along in this<br=
>
case, but since I hadn&#39;t registered it was a little troublesome.=C2=A0 =
I<br>
just used the audio, and it&#39;s no big deal, but it might be a useful<br>
illustration of one bit of friction that comes because of the<br>
remote registration thing (unless everyone registered on-site<br>
automatically gets a remote registration too, maybe conveniently<br>
printed on the badge or something).<br>
<br>
Note that I am _not_ saying this proves anything about whether<br>
registration is a good or bad idea or whatever.=C2=A0 I only mention it<br>
as another anecdote (and of course, in one sense the plural of<br>
&quot;anecdote&quot; is too &quot;data&quot;).<br>
<br>
Best regards,<br>
<br>
A<br>
</blockquote>
<br>
<br>
<br>
<br>
</blockquote>
<br>
</div></div></blockquote></div><br></div>

--001a1144f60eec66290554c27533--


From nobody Thu Jul 20 10:00:14 2017
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DE73131AFC; Thu, 20 Jul 2017 09:59:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 R5uSMooa3WqG; Thu, 20 Jul 2017 09:59:45 -0700 (PDT)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EC3D129B15; Thu, 20 Jul 2017 09:59:45 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id 5223B4C6; Thu, 20 Jul 2017 18:59:44 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.217]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id cJu0cUhfC5bT; Thu, 20 Jul 2017 18:59:40 +0200 (CEST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas5.jacobs-university.de (Postfix) with ESMTPS; Thu, 20 Jul 2017 18:59:44 +0200 (CEST)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id 2A753200AD; Thu, 20 Jul 2017 18:59:44 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius4.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id jmT_TR5yXNVr; Thu, 20 Jul 2017 18:59:43 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 278B7200A8; Thu, 20 Jul 2017 18:59:43 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 0513F3FF7D55; Thu, 20 Jul 2017 18:59:43 +0200 (CEST)
Date: Thu, 20 Jul 2017 18:59:42 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Kent Watsen <kwatsen@juniper.net>
Cc: "yang-doctors@ietf.org" <yang-doctors@ietf.org>, "draft-ietf-netconf-keystore.all@ietf.org" <draft-ietf-netconf-keystore.all@ietf.org>,  "netconf@ietf.org" <netconf@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Yangdoctors last call review of draft-ietf-netconf-keystore-02
Message-ID: <20170720165942.GB21506@elstar.local>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Kent Watsen <kwatsen@juniper.net>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>, "draft-ietf-netconf-keystore.all@ietf.org" <draft-ietf-netconf-keystore.all@ietf.org>,  "netconf@ietf.org" <netconf@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
References: <150028100874.32703.14161403810529927281@ietfa.amsl.com> <B1AC6895-5681-48F8-B7E7-418118120B4E@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <B1AC6895-5681-48F8-B7E7-418118120B4E@juniper.net>
User-Agent: Mutt/1.6.0 (2016-04-01)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vopFApj79vhishR0ohG8TGn_PCw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 16:59:48 -0000

On Wed, Jul 19, 2017 at 09:06:59PM +0000, Kent Watsen wrote:
> Hi Juergen,
> 
> Thanks for your review.  Below are my responses to your comments.
> 
> PS: why is ietf@ietf.org in the CC?

I used the datatracker form and it does what it does.
 
> - There are a number of binary fields where you show explanatory text
>   in the examples instead of encoded data. Is this always clear?
> 
>   <private-key>...</private-key> <!-- elipsis placeholder for a base64 encoded key -->
> 
> <KENT> This issue has been raised by others as well.  I used to
> have full base64 values, but it made the examples very difficult
> to read.  Hmmm, I like your suggestion, but the resulting line
> is much longer than allowed.  I could line-wrap, but the result
> looks worse.  Any other suggestions?

Assuming people will figure out that ... is just a marker, what about
this?
 
   <private-key>...</private-key> <!-- base64 encoded key  -->

> - I am not sure I understand trusted-host-keys. On systems that have
>   multiple user accounts, you usually have a per account list of
>   trusted host keys in addition to a global system wide list. Perhaps
>   make it clear that this models the global known hosts list only?
> 
> <KENT> it's a list of lists, so there can be many different
> sets a host-keys defined, with each application/use pointing
> to its own entry.  The ietf-ssh-client module's grouping has
> a leafref to a specific entry.  FWIW, this grouping is
> used by ietf-netconf-client module.  At the moment, there
> no other uses of this grouping.  I think that you may be
> getting confused between the key the server presents (the
> host-key) versus the key user presents.
> .

I though these are the authorized host keys? Yes, I am confused. If
these are user public keys, they should not be called host keys. But
yes, I am confused (but I started to read the other documents).

> - Should the document title be aligned with other YANG module
>   definitions, so it is easier to spot it?
> 
> <KENT> I don't understand, what do you mean?
 
We often use "[A] YANG Data Model for ....".

https://en.wikipedia.org/wiki/YANG#Usage_in_Standards

The current name does not say YANG (sometimes I search for YANG in the
RFC index) and Keystore is also pretty broad given the related work we
have.
 
> - Since crypto algorithms come and go, is it reasonable to have the
>   identities defined in a rather static RFC? Would an IANA maintained
>   identity module perhaps make more sense?
> 
> <KENT> Unsure, but I wouldn't suspect needing to make that
> kind of update for a long time.  If we were to define a 
> module for algorithm identities, it might lead to us wanting
> to define every algorithm (not just public-key algs), which
> could take some time...

I think an IANA maintained registry can be as incomplete or complete
as the I-D. I understand that the mechanics of working out the proper
registry can be painful (there likely are already N registries) but
clearly crypto algorithm identities must be easily extensible.

> - Oh, I now see that the key length is embedded in the algorithm
>   identity. Perhaps clarify this earlier, see my confused comments
>   above. Anyway, I think this makes the need for an IANA maintained
>   module even stronger.
> 
> <KENT> yes, but your comment before was valid.  I don't see why
> this makes a stronger case though...

Well, the notion of what is strong changes every N years.

> - Why do certificate names have to be unique across all keys?
> 
> <KENT> because otherwise leafrefs might be ambiguous, right?

OK. Perhaps explain this detail so it is obvious to everybody.

> - Since the certs of a key do not contain a signature, where are signed
>   certificates stored or are they outside the scope of the model?
> 
> <KENT> I'm confused, certificates are signed structures already...

Well, the description of certificates/certificate/value says:

   An unsigned PKCS #7 SignedData structure, as specified
   by Section 9.1 in RFC 2315, containing just certificates
   (no content, signatures, or CRLs), encoded using ASN.1
   distinguished encoding rules (DER), as specified in
   ITU-T X.690.

Yes, I am confused how this works.
 
> - Is there any text needed to explain what happens if actions can't be
>   carried out, e.g., the algorithm identity is not supported? Can a
>   client actually learn which algorithm identities are supported or is
>   the approach simply trial and error?
> 
> <KENT> If an action fails, then standard NC/RC error is returned.
> There is no support to learn which algorithms a server supports,
> but by supporting this module, the server must support all of
> these algorithms.

This may raise a red flag by the security people. They take crypto
agility serious and there might be very valid reasons to not support
some of the algorithms at a certain point in time. Actually, there is
a difference between supporting (in the sense of implemented) and
enabled (in the sense can be used).

Anyway, this is usually regulated by protocol specifications,
protocols often define mandatory to implement algorithms etc. Is the
keystore going to interfer with this? Or should it better be silent
about what is mandatory?
 
> - I am not sure what 'trusted certificate' here really means. What you
>   are modeling is a set of sets of certificates. What such a set means
>   depends on where this list is used. I am not sure what it means for
>   a certificate in such a set to be 'trusted'.
> 
> <KENT> yes, the certs may be used by different modules for
> different use-cases, but they'd always be trusted.  E.g.,
> the certs preinstalled by a browser...

If an application (i.e. a RESTCONF server) trusts some set of
certificates, the certificates in that set become trusted by that
specific application. But without concrete context, isn't it unclear
what is trusting a listed certificate and why?
 
> - What about the // rename to 'data' comment? I like it, renaming to
>   list certificate { key name; leaf name; leaf data; } seems less
>   confusing (and it is even shorter). Perhaps something along this
>   line would be better (not sure I like certificate-set)
> 
> 	 +--rw certificate-set* [name]
>          |  +--rw name                   string
>          |  +--rw description?           string
>          |  +--rw certificate* [name]
>          |     +--rw name    string
>          |     +--rw data?   binary
> 
> 
> <KENT> "set" doesn't sound too bad - dunno.  Regarding moving
> "data", see the tail-end of the email I sent on July 11.

Aha. Not sure this resolves this (or I looked at the wrong message).

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>


From nobody Thu Jul 20 10:18:35 2017
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9546A127077; Thu, 20 Jul 2017 10:18:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 XfseM9xbdE7j; Thu, 20 Jul 2017 10:18:32 -0700 (PDT)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD50F12700F; Thu, 20 Jul 2017 10:18:31 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id 9E81666D; Thu, 20 Jul 2017 19:18:30 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.217]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id JHHjtgSh9vw5; Thu, 20 Jul 2017 19:18:26 +0200 (CEST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas5.jacobs-university.de (Postfix) with ESMTPS; Thu, 20 Jul 2017 19:18:30 +0200 (CEST)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id 8515B200B8; Thu, 20 Jul 2017 19:18:30 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id x-TCW32gc2B6; Thu, 20 Jul 2017 19:18:30 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 29529200AA; Thu, 20 Jul 2017 19:18:30 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 133563FF7E39; Thu, 20 Jul 2017 19:18:30 +0200 (CEST)
Date: Thu, 20 Jul 2017 19:18:30 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Kent Watsen <kwatsen@juniper.net>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>, "draft-ietf-netconf-keystore.all@ietf.org" <draft-ietf-netconf-keystore.all@ietf.org>,  "netconf@ietf.org" <netconf@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Yangdoctors last call review of draft-ietf-netconf-keystore-02
Message-ID: <20170720171829.GA21659@elstar.local>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Kent Watsen <kwatsen@juniper.net>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>, "draft-ietf-netconf-keystore.all@ietf.org" <draft-ietf-netconf-keystore.all@ietf.org>,  "netconf@ietf.org" <netconf@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
References: <150028100874.32703.14161403810529927281@ietfa.amsl.com> <B1AC6895-5681-48F8-B7E7-418118120B4E@juniper.net> <20170720165942.GB21506@elstar.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170720165942.GB21506@elstar.local>
User-Agent: Mutt/1.6.0 (2016-04-01)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7yPViz4NkmicipsVngySWaQdRJo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 17:18:34 -0000

On Thu, Jul 20, 2017 at 06:59:42PM +0200, Juergen Schoenwaelder wrote:

> > - Since crypto algorithms come and go, is it reasonable to have the
> >   identities defined in a rather static RFC? Would an IANA maintained
> >   identity module perhaps make more sense?
> > 
> > <KENT> Unsure, but I wouldn't suspect needing to make that
> > kind of update for a long time.  If we were to define a 
> > module for algorithm identities, it might lead to us wanting
> > to define every algorithm (not just public-key algs), which
> > could take some time...
> 
> I think an IANA maintained registry can be as incomplete or complete
> as the I-D. I understand that the mechanics of working out the proper
> registry can be painful (there likely are already N registries) but
> clearly crypto algorithm identities must be easily extensible.
>

I looked a bit more and you define

  identity key-algorithm {
    description
      "Base identity from which all key-algorithms are derived.";
  }

plus a bunch of concrete algorithms. draft-ietf-rtgwg-yang-key-chain-24
defines

     identity crypto-algorithm {
       description
         "Base identity of cryptographic algorithm options.";
     }

and then a bunch of concrete algorithms (hashes and symmetric ones).
They also do not expect IANA to maintain things. I would love if
security area people would help us with getting this right, well
perhaps they jump in during secdir review.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>


From nobody Thu Jul 20 13:35:22 2017
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E5FA126B7F for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 13:35:20 -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] 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 haWGEnb1A6Jo for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 13:35:18 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 9C641124D68 for <ietf@ietf.org>; Thu, 20 Jul 2017 13:35:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v6KKZFB0025594; Thu, 20 Jul 2017 22:35:15 +0200 (CEST)
Received: from surfer-172-30-2-218-hotspot.internet-for-guests.com (107.223.broadband2.iol.cz [83.208.223.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3xD5Hl0vRCz3ZFm; Thu, 20 Jul 2017 22:35:15 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: quick observation about remote participation registration
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAA=duU0csh0EHh6W3fZh1wABbP7OYWmGMOdVj9dNXXECaxv5zA@mail.gmail.com>
Date: Thu, 20 Jul 2017 22:35:13 +0200
Cc: Matthew Ford <ford@isoc.org>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-Mao-Original-Outgoing-Id: 522275713.350584-cb09f8e04cd2b2075c448d95da3af995
Content-Transfer-Encoding: quoted-printable
Message-Id: <7E07969D-0CC1-47EA-A7DC-3C162DE0A1E9@tzi.org>
References: <20170720125927.lbmtvwo3dncmoxmb@mx4.yitter.info> <A9FABAF6-91CB-4BD7-82F8-F20FFC8C513B@isoc.org> <CAA=duU0csh0EHh6W3fZh1wABbP7OYWmGMOdVj9dNXXECaxv5zA@mail.gmail.com>
To: "Andrew G. Malis" <agmalis@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/W649NjxSSgFBWqtObJiCFnaw7bE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 20:35:20 -0000

On Jul 20, 2017, at 16:01, Andrew G. Malis <agmalis@gmail.com> wrote:
>=20
> On my badge, the registration number is printed on the back, under the =
bar code.

Yes, and next time I=E2=80=99ll bring my trusty KDC200i and =
surreptitiously scan everyone=E2=80=99s bar code and then in the plenary =
make the largest remote speaker request queue that we ever had :-). (OK, =
that can be had a bit easier than that way.)

Gr=C3=BC=C3=9Fe, Carsten


From nobody Thu Jul 20 14:26:03 2017
Return-Path: <yoshiro.yoneya@jprs.co.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92A7D126C3D; Thu, 20 Jul 2017 14:26:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, 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 kQrHjggBXDQi; Thu, 20 Jul 2017 14:26:01 -0700 (PDT)
Received: from off-send01.osa.jprs.co.jp (off-send01.osa.jprs.co.jp [IPv6:2001:218:3001:17::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 008791201F2; Thu, 20 Jul 2017 14:26:00 -0700 (PDT)
Received: from off-sendsmg01.osa.jprs.co.jp (off-sendsmg01.osa.jprs.co.jp [172.23.8.61]) by off-send01.osa.jprs.co.jp (8.14.4/8.14.4) with ESMTP id v6KLPvB1013498; Fri, 21 Jul 2017 06:25:57 +0900
Received: from off-sendsmg01.osa.jprs.co.jp (localhost [127.0.0.1]) by postfix.imss71 (Postfix) with ESMTP id 11309180064; Fri, 21 Jul 2017 06:25:56 +0900 (JST)
Received: from NOTE768 (off-cpu05.osa.jprs.co.jp [172.23.4.15]) by off-sendsmg01.osa.jprs.co.jp (Postfix) with SMTP id C1716180062; Fri, 21 Jul 2017 06:25:53 +0900 (JST)
Date: Fri, 21 Jul 2017 06:25:50 +0900
From: Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>
To: "Aaron Falk" <aaron.falk@gmail.com>
Cc: ietf@ietf.org, "99attendees@ietf.org" <99attendees@ietf.org>
Subject: Re: Bad Attitude PechaKucha - logistics
Message-Id: <20170721062550.72a8b33b59639c5e09cde123@jprs.co.jp>
In-Reply-To: <B1B773AE-8B9A-4DFF-8EF7-B0317A84C414@gmail.com>
References: <B1B773AE-8B9A-4DFF-8EF7-B0317A84C414@gmail.com>
X-Mailer: Sylpheed 3.6.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1690-8.1.0.1062-23208.002
X-TM-AS-Result: No--6.454-5.0-31-10
X-imss-scan-details: No--6.454-5.0-31-10
X-TMASE-MatchedRID: I5Fk1qs03HZITndh1lLRAe5i6weAmSDKWDesRNOOJ5QzFWOYrWw6A6s7 H9ycK/boFOWvoMddHQ0HsHD3MHqgdkkkO4zqprNO2os3ueKAsFQ49Hq9hbQQk5/oviapr7hkbS3 fBD3xsm8WXnfGw1s5cEQSrG2oYEShDPcQ8d9u8CjwtZfBooJ6axiue5Gf9pmpvizcrGDYksTl6A M4Aa3gFpWJNgy/LIBn3xMxBgBrYWbtvMVN/9JMyv3NPiyUzKzdSz4b9Xroru5ScXQMxepe+zJl3 MhaKU4m4vM1YF6AJbZcLc3sLtjOt6ryC8RS5234Zz0AAGWYgqKM1Gu9aimtieTCMddcL/gjOwBX M346/+wXyH0QVcBA0oiONR5GSrog3prs9EsG5Hp80S72MGmVGGbfTKeau0Vz
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7YLfJH_tkcySuRiy1U_yaNj3CRk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 21:26:02 -0000

Thank you for the awsome night as usual!

-- 
Yoshiro YONEYA <yoshiro.yoneya@jprs.co.jp>

On Tue, 18 Jul 2017 13:42:38 +0200 "Aaron Falk" <aaron.falk@gmail.com> wrote:

> Date: Thursday, July 20, 2017
> Start Time: ~21:30
> Location: Grand Ballroom
> Cash Bar from 2100 - 2300
> 
> ____
> 
> A Pecha Kucha is a lightning-talk presentation format, originating in 
> Japan, where a speaker presents 20 image-only slides that are each on 
> the screen for 20 seconds and advance automatically.  With each talk 
> lasting for 6:40, it has the feature of forcing presentations -- good or 
> bad -- to be focused and brief.  This is an unofficial event. Topics are 
> encouraged to be a IETF-related and satirical or controversial in some 
> way, although not mean-spirited.  Anyone can participate in this social 
> event.  Video from the Berlin, Seoul, and Chicago PKs can be found 
> [here](http://snaggletooth.akam.ai).


From nobody Thu Jul 20 15:13:56 2017
Return-Path: <allison.mankin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 492D4126B7E; Thu, 20 Jul 2017 15:13:50 -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 Ln1sx6g7fL1r; Thu, 20 Jul 2017 15:13:49 -0700 (PDT)
Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (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 B44DF1250B8; Thu, 20 Jul 2017 15:13:48 -0700 (PDT)
Received: by mail-wm0-x22b.google.com with SMTP id v76so7389669wmv.1; Thu, 20 Jul 2017 15:13:48 -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=jdTz2kan7A2as9RNJmB7U0H+5aeHk3JEkrd2q2XwXeY=; b=qXRk8RwNYIbOZJ7wRm6xLOP88wyrVm6C99+vBbAtL4jb+c9wTAH6q5Uie4RfatN8Ea 1hCPI+LzsuplFWMDzVXgeAg9P3lSlyjnIfccqaOIygkOGI3uA6Cm1EEcOcx/kE1peIGB Iac4E6cgQ7JNupToVXvV5aZ7la/w5JNYZ5SuZGOeQgjFk/7LxnSNHJMOg1ztdcDIa6zo S3n6pBYuvXsO0d7sP6jlV8caBaOIR8DnBORZCPRlcAHopFO9pLjnmJTPNvGCGxQqQpHq hx5TuUuOLwJUfFLWqDr1CqA4VWOBztXigQOE5FeRPEnmwC7Y4MnSoZDOzgBCj2bnCl36 L6IA==
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=jdTz2kan7A2as9RNJmB7U0H+5aeHk3JEkrd2q2XwXeY=; b=Czc+rSKTNlBdBhig3DBDwBZVL1Bte/Wl+C2xE7OiQZXO2Ao7umBhabWXc76NCzc7r9 fp6RaN5z89IHQeCfnCrj9w2ZoZzhjd6sJPOgPWKYZpmwvMcu9UvEyIka5ZdBYNXWssa6 ZpPOAT4uh03p5GJyyxYRDr+mUIMMeSmr/BG+sO4JodXiR6NvcJqcIjal2t7BeFfbc5PT QdzwzZsusMKGjDj0dOb8VUmKGe56BULaoBaO/OZR6xOnvApG1lhJyjlhsHCLo7KbNwf+ rlKFxx7dYYVt/UYcMddYwbui041pGX7NmTlIo2J/471tEDceD9kAEkJQ5tKi55h4VGUd m7Vw==
X-Gm-Message-State: AIVw111LzgMf8yIJRYbkeV4hIPitjhhPhgnXDDsbLrnEy43DQwbUIbE+ iofdkDCE1bklHm3w8UyFFcVDNPPk0w==
X-Received: by 10.80.171.77 with SMTP id t13mr3949928edc.242.1500588827268; Thu, 20 Jul 2017 15:13:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.80.138.69 with HTTP; Thu, 20 Jul 2017 15:13:46 -0700 (PDT)
In-Reply-To: <B1B773AE-8B9A-4DFF-8EF7-B0317A84C414@gmail.com>
References: <B1B773AE-8B9A-4DFF-8EF7-B0317A84C414@gmail.com>
From: Allison Mankin <allison.mankin@gmail.com>
Date: Fri, 21 Jul 2017 00:13:46 +0200
Message-ID: <CAP8yD=tMp33UWLzCXMrYOt7fC5aUEiR6n4LKK3kR+pVmQXw7pw@mail.gmail.com>
Subject: Re: [99attendees] Bad Attitude PechaKucha - logistics
To: Aaron Falk <aaron.falk@gmail.com>
Cc: IETF Discussion <ietf@ietf.org>, "99attendees@ietf.org" <99attendees@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c0ebb3800db930554c710ef"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OaAefTwBQGnCxOuZAHHZUtC9sTI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 22:13:50 -0000

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

This was so much fun.  Thank you, Aaron, for your sustained dedication to
our Attitudes, and for walking the perfect hosting/heckling line.

Great talks by all too.

Allison

P.S. Alia's onto something:  Gamify the IETF!

On 18 July 2017 at 13:42, Aaron Falk <aaron.falk@gmail.com> wrote:

> Date: Thursday, July 20, 2017
> Start Time: ~21:30
> Location: Grand Ballroom
> Cash Bar from 2100 - 2300
> ------------------------------
>
> A Pecha Kucha is a lightning-talk presentation format, originating in
> Japan, where a speaker presents 20 image-only slides that are each on the
> screen for 20 seconds and advance automatically. With each talk lasting for
> 6:40, it has the feature of forcing presentations -- good or bad -- to be
> focused and brief. This is an unofficial event. Topics are encouraged to be
> a IETF-related and satirical or controversial in some way, although not
> mean-spirited. Anyone can participate in this social event. Video from the
> Berlin, Seoul, and Chicago PKs can be found here
> <http://snaggletooth.akam.ai>.
>
> _______________________________________________
> 99attendees mailing list
> 99attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/99attendees
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif">This was so much fun.=C2=A0 Thank you, Aaron, for your =
sustained dedication to our Attitudes, and for walking the perfect hosting/=
heckling line. <br><br>Great talks by all too.<br><br></div><div class=3D"g=
mail_default" style=3D"font-family:arial,helvetica,sans-serif">Allison<br><=
/div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans=
-serif"><br>P.S. Alia&#39;s onto something:=C2=A0 Gamify the IETF! <br></di=
v></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On 18 Jul=
y 2017 at 13:42, Aaron Falk <span dir=3D"ltr">&lt;<a href=3D"mailto:aaron.f=
alk@gmail.com" target=3D"_blank">aaron.falk@gmail.com</a>&gt;</span> wrote:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex"><u></u>




<div>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">Date: Thursday, July 20, 2017<br>
Start Time: ~21:30<br>
Location: Grand Ballroom<br>
Cash Bar from 2100 - 2300</p>

<hr style=3D"background:#333;background-image:linear-gradient(to right,#ccc=
,#333,#ccc);border:0;height:1px" height=3D"1">

<p dir=3D"auto">A Pecha Kucha is a lightning-talk presentation format, orig=
inating in Japan, where a speaker presents 20 image-only slides that are ea=
ch on the screen for 20 seconds and advance automatically.  With each talk =
lasting for 6:40, it has the feature of forcing presentations -- good or ba=
d -- to be focused and brief.  This is an unofficial event. Topics are enco=
uraged to be a IETF-related and satirical or controversial in some way, alt=
hough not mean-spirited.  Anyone can participate in this social event.  Vid=
eo from the Berlin, Seoul, and Chicago PKs can be found <a href=3D"http://s=
naggletooth.akam.ai" style=3D"color:#3983c4" target=3D"_blank">here</a>.</p=
>
</div>
</div>
</div>

<br>______________________________<wbr>_________________<br>
99attendees mailing list<br>
<a href=3D"mailto:99attendees@ietf.org">99attendees@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/99attendees" rel=3D"norefe=
rrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/99attend=
ees</a><br>
<br></blockquote></div><br></div>

--94eb2c0ebb3800db930554c710ef--


From nobody Thu Jul 20 15:22:50 2017
Return-Path: <aaron.falk@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C190126B72; Thu, 20 Jul 2017 15:22:41 -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 ciKgTh4gOaNH; Thu, 20 Jul 2017 15:22:39 -0700 (PDT)
Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (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 308791250B8; Thu, 20 Jul 2017 15:22:39 -0700 (PDT)
Received: by mail-qt0-x22c.google.com with SMTP id 32so32330826qtv.1; Thu, 20 Jul 2017 15:22:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=AYXlZ3bxBTK9bLbystJE2xhXD7qgiMZgTmbHgZ9mUHw=; b=bWXUoIUvf5CM+SZ4rRIrG7hAzB0b9BOK+pG6oonq9eB+BmTSXmsZdJP6l0gjqCXblK myeJuTy3+77TNWRzTQKYO9zgL1D5TnqrMIK+WZ/+9De2veqqXNgL8KaAoyd2Q/HV4dAF mZHIfObJqQCTqT3O0ukNy8exy/qreLBzXCF5fCmhD7e2kOskGX+PSHq1aE7H2WwBezPW eGZAEqLvkIPnVTu1ITAX+/oqVZNZ53/CB4bUWC65+qImIpMxohUEPIOmKBnA/USTcoE8 UpEFMFE53Pq2lTSU7NdINKsxMCXb0SiM5fgOYYs9jOJpwCeDED8hWZ3A4fRX8FD3m6QE CmgQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=AYXlZ3bxBTK9bLbystJE2xhXD7qgiMZgTmbHgZ9mUHw=; b=ohErK8uCqScolviFkrEujfn4MmKXM4RIAS4tirhb1Y9df7V0nmrpuXeqfKaO45OidD lUkczIKcwj7IOjGCnMjLD4c3Y3EwbyENLRX56HK/YGCHVjwfdnFxpjeZC0cuRV1VUl5P 3e3w+OY8dabZeD/PcCm5Pqd8lEypfeyoRU1lbIx5v3ugTS4CbzksHaQ36ldNvlZW5AMf qvOblyK0ozKrdOmf3Nv5wsRZTgG/dhB/waGokGx7GB0xNGNU0zlL8MHapgsj7IVIN711 alTrsBnVUgq2LoXxavqJ1m5Ihbd4AvQzKMlOiqPFCl61l1/AiA5d3QpOGM6+PI3KnBWr dvZg==
X-Gm-Message-State: AIVw113KpIhfiZ2pFdLzirvdjI/FGXHtiJNxN7txunj/Q5INbclDgqrl 6x4SnQRpZqUkoOnSMfLX53FaCiUA2g==
X-Received: by 10.237.58.102 with SMTP id n93mr7665017qte.109.1500589358260; Thu, 20 Jul 2017 15:22:38 -0700 (PDT)
MIME-Version: 1.0
References: <B1B773AE-8B9A-4DFF-8EF7-B0317A84C414@gmail.com> <CAP8yD=tMp33UWLzCXMrYOt7fC5aUEiR6n4LKK3kR+pVmQXw7pw@mail.gmail.com>
In-Reply-To: <CAP8yD=tMp33UWLzCXMrYOt7fC5aUEiR6n4LKK3kR+pVmQXw7pw@mail.gmail.com>
From: Aaron Falk <aaron.falk@gmail.com>
Date: Thu, 20 Jul 2017 22:22:27 +0000
Message-ID: <CAD62q9U4+yD7x4hkG8YpmxJameZW-6FwQoZ_-MaivGuEPMnyxA@mail.gmail.com>
Subject: Re: [99attendees] Bad Attitude PechaKucha - logistics
To: Allison Mankin <allison.mankin@gmail.com>
Cc: IETF Discussion <ietf@ietf.org>, "99attendees@ietf.org" <99attendees@ietf.org>
Content-Type: multipart/alternative; boundary="001a113f458ca72ad10554c72f4d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JfGtwEcJKFxBHRn9lw6pmnBxxcY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 22:22:42 -0000

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

Thanks, Allison! I love doing this. Please, all, keep making awesome talks.
Let's do it again!
On Fri, Jul 21, 2017 at 00:13 Allison Mankin <allison.mankin@gmail.com>
wrote:

> This was so much fun.  Thank you, Aaron, for your sustained dedication to
> our Attitudes, and for walking the perfect hosting/heckling line.
>
> Great talks by all too.
>
> Allison
>
> P.S. Alia's onto something:  Gamify the IETF!
>
> On 18 July 2017 at 13:42, Aaron Falk <aaron.falk@gmail.com> wrote:
>
>> Date: Thursday, July 20, 2017
>> Start Time: ~21:30
>> Location: Grand Ballroom
>> Cash Bar from 2100 - 2300
>> ------------------------------
>>
>> A Pecha Kucha is a lightning-talk presentation format, originating in
>> Japan, where a speaker presents 20 image-only slides that are each on the
>> screen for 20 seconds and advance automatically. With each talk lasting for
>> 6:40, it has the feature of forcing presentations -- good or bad -- to be
>> focused and brief. This is an unofficial event. Topics are encouraged to be
>> a IETF-related and satirical or controversial in some way, although not
>> mean-spirited. Anyone can participate in this social event. Video from the
>> Berlin, Seoul, and Chicago PKs can be found here
>> <http://snaggletooth.akam.ai>.
>>
>> _______________________________________________
>> 99attendees mailing list
>> 99attendees@ietf.org
>> https://www.ietf.org/mailman/listinfo/99attendees
>>
>>

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

Thanks, Allison!  I love doing this. Please, all, keep making awesome talks=
. Let&#39;s do it again!<br><div class=3D"gmail_quote"><div dir=3D"ltr">On =
Fri, Jul 21, 2017 at 00:13 Allison Mankin &lt;<a href=3D"mailto:allison.man=
kin@gmail.com">allison.mankin@gmail.com</a>&gt; wrote:<br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"=
font-family:arial,helvetica,sans-serif">This was so much fun.=C2=A0 Thank y=
ou, Aaron, for your sustained dedication to our Attitudes, and for walking =
the perfect hosting/heckling line. <br><br>Great talks by all too.<br><br><=
/div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans=
-serif">Allison<br></div><div class=3D"gmail_default" style=3D"font-family:=
arial,helvetica,sans-serif"><br>P.S. Alia&#39;s onto something:=C2=A0 Gamif=
y the IETF! <br></div></div><div class=3D"gmail_extra"><br><div class=3D"gm=
ail_quote"></div></div><div class=3D"gmail_extra"><div class=3D"gmail_quote=
">On 18 July 2017 at 13:42, Aaron Falk <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:aaron.falk@gmail.com" target=3D"_blank">aaron.falk@gmail.com</a>&gt;</s=
pan> wrote:<br></div></div><div class=3D"gmail_extra"><div class=3D"gmail_q=
uote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><u></u>




<div>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">Date: Thursday, July 20, 2017<br>
Start Time: ~21:30<br>
Location: Grand Ballroom<br>
Cash Bar from 2100 - 2300</p>

<hr style=3D"background:#333;background-image:linear-gradient(to right,#ccc=
,#333,#ccc);border:0;height:1px" height=3D"1">

<p dir=3D"auto">A Pecha Kucha is a lightning-talk presentation format, orig=
inating in Japan, where a speaker presents 20 image-only slides that are ea=
ch on the screen for 20 seconds and advance automatically.  With each talk =
lasting for 6:40, it has the feature of forcing presentations -- good or ba=
d -- to be focused and brief.  This is an unofficial event. Topics are enco=
uraged to be a IETF-related and satirical or controversial in some way, alt=
hough not mean-spirited.  Anyone can participate in this social event.  Vid=
eo from the Berlin, Seoul, and Chicago PKs can be found <a href=3D"http://s=
naggletooth.akam.ai" style=3D"color:#3983c4" target=3D"_blank">here</a>.</p=
>
</div>
</div>
</div>

<br></blockquote></div></div><div class=3D"gmail_extra"><div class=3D"gmail=
_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">____________________________________=
___________<br>
99attendees mailing list<br>
<a href=3D"mailto:99attendees@ietf.org" target=3D"_blank">99attendees@ietf.=
org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/99attendees" rel=3D"norefe=
rrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/99attendees</=
a><br>
<br></blockquote></div></div></blockquote></div>

--001a113f458ca72ad10554c72f4d--


From nobody Thu Jul 20 17:47:34 2017
Return-Path: <narellec@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 332DF12942F for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 17:47:32 -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=unavailable 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 XWvya61FxWkl for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 17:47:22 -0700 (PDT)
Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::233]) (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 53228129AD7 for <ietf@ietf.org>; Thu, 20 Jul 2017 17:47:16 -0700 (PDT)
Received: by mail-oi0-x233.google.com with SMTP id q4so40704793oif.1 for <ietf@ietf.org>; Thu, 20 Jul 2017 17:47:16 -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=Xw2K+Z/00gq6zomLV3ctILJkiAFP4SSBhFs/ayjIbJc=; b=OKmLwtYqvv5nhKQOBd1m6hF5f+TVTGbQpRBh7r4OG+NDYh8FPdUVpomj2gt/nsJvuv 914ONCp6RnUYbhJBbNNDSMR12+UdilSufcmywJikWkPAU+g0MVU5mfwvnpIe34GPBNUn 9/Ft5gwW0NZ3JJPxPAIIfeoqenhHatPfVgMnBuxVoxThtHWEzOuwiiP+A7BTjZRfOoti Nczp4PHVk2OG1VttaXr8S62lGmXv2cWYk/I1DcyfxjNF73BN0uQZUsn525doOy3Fwoo4 uMmSbi5QYlxOWNGm3kc5O4qTfbVL0uCi5EJkoBndTAeMNiC9pXHHzDBsj1nVfa1FoRab 3YWQ==
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=Xw2K+Z/00gq6zomLV3ctILJkiAFP4SSBhFs/ayjIbJc=; b=pr5qhLZFFGX77bcLR+s3MYQvXSNjVK8GLIMH3t8Uy50kXjkLql1Ku1oSCEixDnuMXY pedg42BFAQhVf7e7W3yaT9MyUCbyNdTWmLjjkXh26hbNIScwjig3QgCOp/6/AWGgSNGM yR1n8YSrJE5RLvHmS8SDZ3eMQh5t3yE99j+z4wP/IK1hKH79OzsXBYv79iOL743xjgxW Or35aQaEfMOYpFnsLioYM8FczUSS3B+rykWHD1DwX/wkgwUHWWOrRjP3J24fEGQaDww8 6vkZtQ3fTg1IYQXNMEe4Jx38BZIdjXVDgffpO+uNLKUUs3Lyr8eH3Y9qYWSIOTLjoY8y QbAA==
X-Gm-Message-State: AIVw11383ch6TaOgQeEbHL4xqcn5AQKZMFxpWGhWMiNvPCOsRsHnmZjb uQ+UgSEwmfX4npdhVGAPP4vPYGcV3g==
X-Received: by 10.202.85.18 with SMTP id j18mr950918oib.292.1500598035705; Thu, 20 Jul 2017 17:47:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.87.33 with HTTP; Thu, 20 Jul 2017 17:47:15 -0700 (PDT)
In-Reply-To: <2107809846.1308501.1500528537111@mail.yahoo.com>
References: <CAKKJt-ehdzREsf3QzGZ+JFOkMm-dGpSdGVFBUJE4BhqWweY+Og@mail.gmail.com> <08eb01d3006d$f0aa8a60$d1ff9f20$@olddog.co.uk> <CAKKJt-fhDgfi7UofBjmLo9xhHqjUe+tL8THs6yGYv3Cn9ETq0g@mail.gmail.com> <09d501d3009d$8b33f560$a19be020$@olddog.co.uk> <2107809846.1308501.1500528537111@mail.yahoo.com>
From: Narelle <narellec@gmail.com>
Date: Fri, 21 Jul 2017 10:47:15 +1000
Message-ID: <CACRMD1HxMO1zx0_Kp7Bo511FZ_O5YS-ezwN=tsTJ+8cWky_xCA@mail.gmail.com>
Subject: Re: Slides, eye charts, and a beg for readability
To: Lloyd Wood <lloyd.wood@yahoo.co.uk>
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>,  Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a113d3944de72360554c934ff"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BdYYH3GZ7Je6UHm4uMFNi2Twty0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 00:47:32 -0000

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

Font size, colour contrast, animations are all just some of the things that
go to good slideware so that people with vision impairments can use them.

There is a good guide to powerpoint accessibility generally here:
http://webaim.org/techniques/powerpoint/

It goes to adding alt tags, reading order and (briefly) to contrast in
colour etc.

As does this overview:
https://www.slidegenius.com/blog/making-your-powerpoint-accessible-for-the-visually-impaired

Frankly all our materials should take these things into account...
Usability by design goes to not just the technology but how we communicate
about the technology.

regards

-- 


Narelle Clark
narellec@gmail.com

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

<div dir=3D"ltr"><div><br></div>Font size, colour contrast, animations are =
all just some of the things that go to good slideware so that people with v=
ision impairments can use them.<br><br>There is a good guide to powerpoint =
accessibility generally here: <a href=3D"http://webaim.org/techniques/power=
point">http://webaim.org/techniques/powerpoint</a>/<br><br>It goes to addin=
g alt tags, reading order and (briefly) to contrast in colour etc.<br><br>A=
s does this overview: <a href=3D"https://www.slidegenius.com/blog/making-yo=
ur-powerpoint-accessible-for-the-visually-impaired/">https://www.slidegeniu=
s.com/blog/making-your-powerpoint-accessible-for-the-visually-impaired</a><=
br><br>Frankly all our materials should take these things into account... U=
sability by design goes to not just the technology but how we communicate a=
bout the technology.<br><br>regards<br><br>-- <br><br><br>Narelle Clark<br>=
<a href=3D"mailto:narellec@gmail.com">narellec@gmail.com</a></div>

--001a113d3944de72360554c934ff--


From nobody Thu Jul 20 18:46:41 2017
Return-Path: <shares@ndzh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA2481270A3; Thu, 20 Jul 2017 18:46:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.947
X-Spam-Level: 
X-Spam-Status: No, score=0.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, 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 1RK2kXzb7x9v; Thu, 20 Jul 2017 18:46:32 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (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 2775C126D73; Thu, 20 Jul 2017 18:46:32 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=31.133.153.78; 
From: "Susan Hares" <shares@ndzh.com>
To: "'Allison Mankin'" <allison.mankin@gmail.com>, "'Aaron Falk'" <aaron.falk@gmail.com>
Cc: "'IETF Discussion'" <ietf@ietf.org>, <99attendees@ietf.org>
References: <B1B773AE-8B9A-4DFF-8EF7-B0317A84C414@gmail.com> <CAP8yD=tMp33UWLzCXMrYOt7fC5aUEiR6n4LKK3kR+pVmQXw7pw@mail.gmail.com>
In-Reply-To: <CAP8yD=tMp33UWLzCXMrYOt7fC5aUEiR6n4LKK3kR+pVmQXw7pw@mail.gmail.com>
Subject: RE: [99attendees] Bad Attitude PechaKucha - logistics
Date: Thu, 20 Jul 2017 21:40:29 -0400
Message-ID: <008e01d301c2$563a4960$02aedc20$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_008F_01D301A0.CF2945A0"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQD+YchGHrdSBVXLTFfkqnx+knXWFADlrFq6o/+TqAA=
X-Authenticated-User: skh@ndzh.com 
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1D1GdvQac_5RDK65b_S8Xk09VoU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 01:46:34 -0000

This is a multipart message in MIME format.

------=_NextPart_000_008F_01D301A0.CF2945A0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

+1.

Sue

=20

From: 99attendees [mailto:99attendees-bounces@ietf.org] On Behalf Of =
Allison Mankin
Sent: Thursday, July 20, 2017 6:14 PM
To: Aaron Falk
Cc: IETF Discussion; 99attendees@ietf.org
Subject: Re: [99attendees] Bad Attitude PechaKucha - logistics

=20

This was so much fun.  Thank you, Aaron, for your sustained dedication =
to our Attitudes, and for walking the perfect hosting/heckling line.=20

Great talks by all too.

Allison


P.S. Alia's onto something:  Gamify the IETF!=20

=20

On 18 July 2017 at 13:42, Aaron Falk <aaron.falk@gmail.com> wrote:

Date: Thursday, July 20, 2017
Start Time: ~21:30
Location: Grand Ballroom
Cash Bar from 2100 - 2300

  _____ =20

A Pecha Kucha is a lightning-talk presentation format, originating in =
Japan, where a speaker presents 20 image-only slides that are each on =
the screen for 20 seconds and advance automatically. With each talk =
lasting for 6:40, it has the feature of forcing presentations -- good or =
bad -- to be focused and brief. This is an unofficial event. Topics are =
encouraged to be a IETF-related and satirical or controversial in some =
way, although not mean-spirited. Anyone can participate in this social =
event. Video from the Berlin, Seoul, and Chicago PKs can be found  =
<http://snaggletooth.akam.ai> here.


_______________________________________________
99attendees mailing list
99attendees@ietf.org
https://www.ietf.org/mailman/listinfo/99attendees

=20


------=_NextPart_000_008F_01D301A0.CF2945A0
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=3DGenerator content=3D"Microsoft Word 14 (filtered medium)"><!--[if =
!mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	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
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.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=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>+1.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'> <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Sue<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
99attendees [mailto:99attendees-bounces@ietf.org] <b>On Behalf Of =
</b>Allison Mankin<br><b>Sent:</b> Thursday, July 20, 2017 6:14 =
PM<br><b>To:</b> Aaron Falk<br><b>Cc:</b> IETF Discussion; =
99attendees@ietf.org<br><b>Subject:</b> Re: [99attendees] Bad Attitude =
PechaKucha - logistics<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><span =
style=3D'font-family:"Arial","sans-serif"'>This was so much fun.&nbsp; =
Thank you, Aaron, for your sustained dedication to our Attitudes, and =
for walking the perfect hosting/heckling line. <br><br>Great talks by =
all too.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial","sans-serif"'>Allison<o:p></o:p></span></p><=
/div><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial","sans-serif"'><br>P.S. Alia's onto =
something:&nbsp; Gamify the IETF! =
<o:p></o:p></span></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>On 18 =
July 2017 at 13:42, Aaron Falk &lt;<a =
href=3D"mailto:aaron.falk@gmail.com" =
target=3D"_blank">aaron.falk@gmail.com</a>&gt; =
wrote:<o:p></o:p></p><div><div><div><p><span =
style=3D'font-family:"Arial","sans-serif"'>Date: Thursday, July 20, =
2017<br>Start Time: ~21:30<br>Location: Grand Ballroom<br>Cash Bar from =
2100 - 2300<o:p></o:p></span></p><div class=3DMsoNormal align=3Dcenter =
style=3D'text-align:center'><span =
style=3D'font-family:"Arial","sans-serif"'><hr size=3D1 width=3D"100%" =
align=3Dcenter></span></div><p><span =
style=3D'font-family:"Arial","sans-serif"'>A Pecha Kucha is a =
lightning-talk presentation format, originating in Japan, where a =
speaker presents 20 image-only slides that are each on the screen for 20 =
seconds and advance automatically. With each talk lasting for 6:40, it =
has the feature of forcing presentations -- good or bad -- to be focused =
and brief. This is an unofficial event. Topics are encouraged to be a =
IETF-related and satirical or controversial in some way, although not =
mean-spirited. Anyone can participate in this social event. Video from =
the Berlin, Seoul, and Chicago PKs can be found <a =
href=3D"http://snaggletooth.akam.ai" target=3D"_blank"><span =
style=3D'color:#3983C4'>here</span></a>.<o:p></o:p></span></p></div></div=
></div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><br>______________________________________=
_________<br>99attendees mailing list<br><a =
href=3D"mailto:99attendees@ietf.org">99attendees@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/99attendees" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/99attendees</a><o=
:p></o:p></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_008F_01D301A0.CF2945A0--


From nobody Thu Jul 20 21:10:22 2017
Return-Path: <lyndon@orthanc.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD373126C22 for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 21:10:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 QtS4W6xFm455 for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 21:10:19 -0700 (PDT)
Received: from orthanc.ca (orthanc.ca [IPv6:2607:f2f8:abf8::2]) (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 9806312441E for <ietf@ietf.org>; Thu, 20 Jul 2017 21:10:19 -0700 (PDT)
Received: from minnie.hitronhub.home (S0106a84e3f81a003.vc.shawcable.net [24.80.126.119]) (authenticated bits=0) by orthanc.ca (8.15.2/8.15.2) with ESMTPSA id v6L4A8w7074522 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 20 Jul 2017 21:10:10 -0700 (PDT) (envelope-from lyndon@orthanc.ca)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: quick observation about remote participation registration
From: Lyndon Nerenberg <lyndon@orthanc.ca>
In-Reply-To: <30D585774FDAF7F5158A6A26@PSB>
Date: Thu, 20 Jul 2017 21:10:03 -0700
Cc: Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <4B7A0FD7-9088-4687-9C3A-F137E4873CE8@orthanc.ca>
References: <20170720125927.lbmtvwo3dncmoxmb@mx4.yitter.info> <30D585774FDAF7F5158A6A26@PSB>
To: John C Klensin <john@jck.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kEMfS7VG7_iLwYM0uLJ8ENPQ5qA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 04:10:21 -0000

> I would think that this should be even easier because, unless
> someone can think of a reason to not do so, the registration
> code for on-site registrations should simply work in Meetecho.
> Putting you through a second registration/ signup procedure when
> you are already registered for the meeting (and, in your case
> but less in Spencer's use of in-room Meetecho was slide viewer,
> likely in a hurry) seems like unreasonable bureaucracy.   If we
> need to keep a distinction between on-site and off-site remote
> participants, that distinction should be embedded into the
> registration codes, not require the user to pretend to be two
> people (which would actually distort the statistics).

Alternatively, why can't the existing www.ietf.org have a visible but =
not overpowering link out that invites non-participants to learn about =
the IETF and its objectives.  "New to the IETF? Learn About What We Do!" =
seems to convey the point, and can take the Internet non-Engineering =
Task Force people off to a forum more suited to their needs, while =
leaving the www.ietf.org website to serve the IETF.

I have to agree with the others who think 'beta' is a lot of wasted =
screen real estate.  We are not a marketing organization, so what the =
hell is a "featured internet draft?"  Why is this draft more important =
than any other i-d?  Oh, and a refresh says there is a "featured RFC" as =
well.  Really?

And if there is a link to the datatracker, or anything else of use, I =
sure can't find it on that page.

For the stated goals in the title graphic, I think it fails on all three =
accounts.  It does nothing for active participants, as an onramp it =
takes people nowhere, and it certainly explains nothing about the IETF.

If the IETF is really thinking of growing a Marketing Department, well =
...  But they can have a visible but unobtrusive link off the main page. =
 marketing.ietf.org can have all the graphics and javascript it wants.  =
That keeps it out of the way of the people doing IETF work, while =
serving the "marketing" needs of the IETF.  It certainly follows the =
model of most other entities on the Internet when it comes to promoting =
themselves.

--lyndon


From nobody Thu Jul 20 21:23:53 2017
Return-Path: <naiming@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42B2B1294A2; Thu, 20 Jul 2017 21:23:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_HTML_ATTACH=0.01, URIBL_BLOCKED=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 ZTC01yGLwjfa; Thu, 20 Jul 2017 21:23:36 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7A4F126C2F; Thu, 20 Jul 2017 21:23:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=27061; q=dns/txt; s=iport; t=1500611015; x=1501820615; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=TcNQc5y3bIMjAIOrMbXiov0q1Uy1qV6GDCQekqdctk4=; b=CuOq/kT7LMmyJQ1E/ZaEPfb/6m/HBc1n9WA+/0/jpfFmu5O2nGSGYP6S 4xW8y28TL76j2CYJ4+xOEebLL1WALwexVsH+Xb38HNPN4gVoRLxwQlmXN mYNRwqvjEy58UHTpWLWo7pd9DFDXv5qYCjlTMrarfoOkaM0AJrtxdn4An 4=;
X-Files: draft-ietf-dhc-relay-port-06-from-5.diff.html, ATT00001.txt : 17970,  616
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DJAABkgHFZ/4sNJK1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgy0tZIEUB44FkWeWBYIRLIM8gV8CGoNbPxgBAgEBAQEBAQFrKIUYAQE?= =?us-ascii?q?BAQIBIwpMBQsCAQYCGCAKAgICMCUCBA4FDooZCBCTWZ1kgiaLIwEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQ4PgyiFWYJ5hFSDKTCCMQEEilGMeoJghRYChCuCHYEBhxS?= =?us-ascii?q?FO4IMGT6EeYkVgUSVXgEfOIEKdRVJEgGER4I8dgGIeIEOAQEB?=
X-IronPort-AV: E=Sophos;i="5.40,387,1496102400";  d="txt'?html'217?scan'217,208,217";a="272659802"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 21 Jul 2017 04:23:34 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id v6L4NYMf024520 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 21 Jul 2017 04:23:34 GMT
Received: from xch-rcd-004.cisco.com (173.37.102.14) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 20 Jul 2017 23:23:33 -0500
Received: from xch-rcd-004.cisco.com ([173.37.102.14]) by XCH-RCD-004.cisco.com ([173.37.102.14]) with mapi id 15.00.1210.000; Thu, 20 Jul 2017 23:23:33 -0500
From: "Naiming Shen (naiming)" <naiming@cisco.com>
To: Ralf Weber <ralf.weber@nominum.com>
CC: "int-dir@ietf.org" <int-dir@ietf.org>, dhcwg <dhcwg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dhc-relay-port.all@ietf.org" <draft-ietf-dhc-relay-port.all@ietf.org>, "Enke Chen (enkechen)" <enkechen@cisco.com>
Subject: Re: Intdir early review of draft-ietf-dhc-relay-port-05
Thread-Topic: Intdir early review of draft-ietf-dhc-relay-port-05
Thread-Index: AQHTAVDdC/pmVM+g8UmmGrJI4+prW6JeA2gA
Date: Fri, 21 Jul 2017 04:23:33 +0000
Message-ID: <B560FD8D-FFF1-4D2E-947B-A1F1BD3AA6DA@cisco.com>
References: <150055249283.9589.17482424577250077220@ietfa.amsl.com>
In-Reply-To: <150055249283.9589.17482424577250077220@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.76.31]
Content-Type: multipart/mixed; boundary="_003_B560FD8DFFF14D2E947BA1F1BD3AA6DAciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/W6vdQaPB6J7fXcpaC5MjCYYLS9A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 04:23:38 -0000

--_003_B560FD8DFFF14D2E947BA1F1BD3AA6DAciscocom_
Content-Type: text/plain; charset="utf-8"
Content-ID: <5475957ECE1D27469F4A7C7C419AFE90@emea.cisco.com>
Content-Transfer-Encoding: base64

DQpIaSBSYWxmLA0KDQpUaGFua3MgZm9yIHlvdXIgcmV2aWV3IG9mIHRoaXMgZG9jdW1lbnQuIFlv
dXINCnN1Z2dlc3Rpb24gbWFrZXMgbG90IG9mIHNlbnNlLg0KSeKAmW0gZ29pbmcgdG8gYWRkIHRo
ZSBiZWxvdyBzZW50ZW5jZSBpbiB0aGUgc2VjdGlvbiA0Og0KDQrigJwuLiwgdG8gYWxsb3cgdGhl
IHN0YXRlbGVzcyBvcGVyYXRpb24gaW4gYSByZWxheSBjaGFpbiwg4oCm4oCdDQoNCnRvIG1ha2Ug
dGhlIG1vdGl2YXRpb24gY2xlYXIgZm9yIHRoaXMgZGhjcHY2IHJlbGF5IG9wdGlvbi4NCg0KdGhl
IHJmY2RpZmYgZmlsZSBpcyBhdHRhY2hlZC4NCg0KQ2hlZXJzLA0KLSBOYWltaW5nDQoNCg==

--_003_B560FD8DFFF14D2E947BA1F1BD3AA6DAciscocom_
Content-Type: text/html;
	name="draft-ietf-dhc-relay-port-06-from-5.diff.html"
Content-Description: draft-ietf-dhc-relay-port-06-from-5.diff.html
Content-Disposition: attachment;
	filename="draft-ietf-dhc-relay-port-06-from-5.diff.html"; size=17970;
	creation-date="Fri, 21 Jul 2017 04:23:33 GMT";
	modification-date="Fri, 21 Jul 2017 04:23:33 GMT"
Content-ID: <45E163995154834FA739A13B70635216@emea.cisco.com>
Content-Transfer-Encoding: base64

PCFET0NUWVBFIGh0bWwgUFVCTElDICItLy9XM0MvL0RURCBYSFRNTCAxLjAgVHJhbnNpdGlvbmFs
Ly9FTiIgImh0dHA6Ly93d3cudzMub3JnL1RSL3hodG1sMS9EVEQveGh0bWwxLXRyYW5zaXRpb25h
bC5kdGQiPiANCjwhLS0gR2VuZXJhdGVkIGJ5IHJmY2RpZmYgMS40MjogcmZjZGlmZiAgLS0+IA0K
PCEtLSA8IURPQ1RZUEUgaHRtbCBQVUJMSUMgIi0vL1czQy8vRFREIEhUTUwgNC4wMSBUcmFuc2l0
aW9uYWwiID4gLS0+DQo8IS0tIFN5c3RlbTogRGFyd2luIE5BSU1JTkctTS1EMkVVIDE2LjcuMCBE
YXJ3aW4gS2VybmVsIFZlcnNpb24gMTYuNy4wOiBUaHUgSnVuIDE1IDE3OjM2OjI3IFBEVCAyMDE3
OyByb290OnhudS0zNzg5LjcwLjE2fjIvUkVMRUFTRV9YODZfNjQgeDg2XzY0IC0tPiANCjwhLS0g
VXNpbmcgYXdrOiAvdXNyL2xvY2FsL2Jpbi9nYXdrOiBHTlUgQXdrIDQuMS4zLCBBUEk6IDEuMSAt
LT4gDQo8IS0tIFVzaW5nIGRpZmY6IC91c3IvYmluL2RpZmY6IGRpZmYgKEdOVSBkaWZmdXRpbHMp
IDIuOC4xIC0tPiANCjwhLS0gVXNpbmcgd2RpZmY6IC91c3IvbG9jYWwvYmluL3dkaWZmOiB3ZGlm
ZiAoR05VIHdkaWZmKSAxLjIuMiAtLT4gDQo8aHRtbD4gDQo8aGVhZD4gDQogIDxtZXRhIGh0dHAt
ZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWlzby04ODU5
LTEiIC8+IA0KICA8bWV0YSBodHRwLWVxdWl2PSJDb250ZW50LVN0eWxlLVR5cGUiIGNvbnRlbnQ9
InRleHQvY3NzIiAvPiANCiAgPHRpdGxlPkRpZmY6IGRyYWZ0LWlldGYtZGhjLXJlbGF5LXBvcnQt
MDUudHh0IC0gZHJhZnQtaWV0Zi1kaGMtcmVsYXktcG9ydC0wNi50eHQ8L3RpdGxlPiANCiAgPHN0
eWxlIHR5cGU9InRleHQvY3NzIj4gDQogICAgYm9keSAgICB7IG1hcmdpbjogMC40ZXg7IG1hcmdp
bi1yaWdodDogYXV0bzsgfSANCiAgICB0ciAgICAgIHsgfSANCiAgICB0ZCAgICAgIHsgd2hpdGUt
c3BhY2U6IHByZTsgZm9udC1mYW1pbHk6IG1vbm9zcGFjZTsgdmVydGljYWwtYWxpZ246IHRvcDsg
Zm9udC1zaXplOiAwLjg2ZW07fSANCiAgICB0aCAgICAgIHsgZm9udC1zaXplOiAwLjg2ZW07IH0g
DQogICAgLnNtYWxsICB7IGZvbnQtc2l6ZTogMC42ZW07IGZvbnQtc3R5bGU6IGl0YWxpYzsgZm9u
dC1mYW1pbHk6IFZlcmRhbmEsIEhlbHZldGljYSwgc2Fucy1zZXJpZjsgfSANCiAgICAubGVmdCAg
IHsgYmFja2dyb3VuZC1jb2xvcjogI0VFRTsgfSANCiAgICAucmlnaHQgIHsgYmFja2dyb3VuZC1j
b2xvcjogI0ZGRjsgfSANCiAgICAuZGlmZiAgIHsgYmFja2dyb3VuZC1jb2xvcjogI0NDRjsgfSAN
CiAgICAubGJsb2NrIHsgYmFja2dyb3VuZC1jb2xvcjogI0JGQjsgfSANCiAgICAucmJsb2NrIHsg
YmFja2dyb3VuZC1jb2xvcjogI0ZGODsgfSANCiAgICAuaW5zZXJ0IHsgYmFja2dyb3VuZC1jb2xv
cjogIzhGRjsgfSANCiAgICAuZGVsZXRlIHsgYmFja2dyb3VuZC1jb2xvcjogI0FDRjsgfSANCiAg
ICAudm9pZCAgIHsgYmFja2dyb3VuZC1jb2xvcjogI0ZGQjsgfSANCiAgICAuY29udCAgIHsgYmFj
a2dyb3VuZC1jb2xvcjogI0VFRTsgfSANCiAgICAubGluZWJyIHsgYmFja2dyb3VuZC1jb2xvcjog
I0FBQTsgfSANCiAgICAubGluZW5vIHsgY29sb3I6IHJlZDsgYmFja2dyb3VuZC1jb2xvcjogI0ZG
RjsgZm9udC1zaXplOiAwLjdlbTsgdGV4dC1hbGlnbjogcmlnaHQ7IHBhZGRpbmc6IDAgMnB4OyB9
IA0KICAgIC5lbGlwc2lzeyBiYWNrZ3JvdW5kLWNvbG9yOiAjQUFBOyB9IA0KICAgIC5sZWZ0IC5j
b250IHsgYmFja2dyb3VuZC1jb2xvcjogI0RERDsgfSANCiAgICAucmlnaHQgLmNvbnQgeyBiYWNr
Z3JvdW5kLWNvbG9yOiAjRUVFOyB9IA0KICAgIC5sYmxvY2sgLmNvbnQgeyBiYWNrZ3JvdW5kLWNv
bG9yOiAjOUQ5OyB9IA0KICAgIC5yYmxvY2sgLmNvbnQgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjREQ2
OyB9IA0KICAgIC5pbnNlcnQgLmNvbnQgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjMEREOyB9IA0KICAg
IC5kZWxldGUgLmNvbnQgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjOEFEOyB9IA0KICAgIC5zdGF0cywg
LnN0YXRzIHRkLCAuc3RhdHMgdGggeyBiYWNrZ3JvdW5kLWNvbG9yOiAjRUVFOyBwYWRkaW5nOiAy
cHggMDsgfSANCiAgPC9zdHlsZT4gDQo8L2hlYWQ+IA0KPGJvZHkgPiANCiAgPHRhYmxlIGJvcmRl
cj0iMCIgY2VsbHBhZGRpbmc9IjAiIGNlbGxzcGFjaW5nPSIwIj4gDQogIDx0ciBiZ2NvbG9yPSJv
cmFuZ2UiPjx0aD48L3RoPjx0aD4mbmJzcDtkcmFmdC1pZXRmLWRoYy1yZWxheS1wb3J0LTA1LnR4
dCZuYnNwOzwvdGg+PHRoPiA8L3RoPjx0aD4mbmJzcDtkcmFmdC1pZXRmLWRoYy1yZWxheS1wb3J0
LTA2LnR4dCZuYnNwOzwvdGg+PHRoPjwvdGg+PC90cj4gDQogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwv
dGQ+PC90cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij5OZXR3b3JraW5nIFdvcmtpbmcgR3JvdXAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIE4uIFNoZW48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij5OZXR3b3JraW5nIFdvcmtpbmcgR3JvdXAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIE4uIFNoZW48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgRS4gQ2hlbjwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgRS4gQ2hlbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+SW50ZW5kZWQgc3RhdHVzOiBTdGFuZGFyZHMgVHJh
Y2sgICAgICAgICAgICAgICAgICAgICAgICAgICBDaXNjbyBTeXN0ZW1zPC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+SW50ZW5kZWQgc3RhdHVzOiBTdGFuZGFyZHMgVHJhY2sgICAgICAg
ICAgICAgICAgICAgICAgICAgICBDaXNjbyBTeXN0ZW1zPC90ZD48dGQgY2xhc3M9ImxpbmVubyIg
dmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQ+PGEgbmFtZT0iZGlmZjAwMDEi
IC8+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48dGQgY2xhc3M9ImxibG9jayI+RXhwaXJlczogPHNwYW4gY2xhc3M9ImRlbGV0ZSI+T2N0
b2JlciAyNywgMjAxNyAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIEFwcmlsIDI1PC9z
cGFuPiwgMjAxNzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj5FeHBpcmVzOiA8c3Bh
biBjbGFzcz0iaW5zZXJ0Ij5KYW51YXJ5IDIxLCAyMDE4ICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgIEp1bHkgMjA8L3NwYW4+LCAyMDE3PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWdu
PSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgICAgICAgICAgICAgIEdlbmVyYWxpemVkIFVEUCBTb3VyY2UgUG9ydCBmb3IgREhDUCBS
ZWxheTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgIEdlbmVy
YWxpemVkIFVEUCBTb3VyY2UgUG9ydCBmb3IgREhDUCBSZWxheTwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAgICAgICAg
IGRyYWZ0LWlldGYtZGhjLXJlbGF5LXBvcnQtMDU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICAgICAgICAgICAgICAgICAgICAgZHJhZnQtaWV0Zi1kaGMtcmVsYXktcG9ydC0wNTwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWdu
PSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij5BYnN0cmFjdDwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPkFic3RyYWN0PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRo
aXMgZG9jdW1lbnQgcHJvcG9zZXMgYW4gZXh0ZW5zaW9uIHRvIHRoZSBESENQIHByb3RvY29scyB0
aGF0IGFsbG93czwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFRoaXMgZG9jdW1l
bnQgcHJvcG9zZXMgYW4gZXh0ZW5zaW9uIHRvIHRoZSBESENQIHByb3RvY29scyB0aGF0IGFsbG93
czwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgYSByZWxheSBhZ2VudCB0byByZWNlaXZlIHBhY2tldHMgZnJvbSBhIHNlcnZlciBvciBhbiB1
cHN0cmVhbSByZWxheTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGEgcmVsYXkg
YWdlbnQgdG8gcmVjZWl2ZSBwYWNrZXRzIGZyb20gYSBzZXJ2ZXIgb3IgYW4gdXBzdHJlYW0gcmVs
YXk8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PiAgIGFnZW50IG9uIGFueSBVRFAgcG9ydCwgbm90IGp1c3QgdGhlIGRlZmF1bHQgcG9ydCA2NyBm
b3IgSVB2NCBvcjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGFnZW50IG9uIGFu
eSBVRFAgcG9ydCwgbm90IGp1c3QgdGhlIGRlZmF1bHQgcG9ydCA2NyBmb3IgSVB2NCBvcjwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgZGVm
YXVsdCBwb3J0IDU0NyBmb3IgSVB2Ni48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4g
ICBkZWZhdWx0IHBvcnQgNTQ3IGZvciBJUHY2LjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+DQogICAgICA8dHIgYmdjb2xvcj0iZ3JheSIgPjx0ZD48
L3RkPjx0aD48YSBuYW1lPSJwYXJ0LWwyIiAvPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8
L3NtYWxsPjxlbT4gcGFnZSAxLCBsaW5lIDMzPC9lbT48L3RoPjx0aD4gPC90aD48dGg+PGEgbmFt
ZT0icGFydC1yMiIgLz48c21hbGw+c2tpcHBpbmcgdG8gY2hhbmdlIGF0PC9zbWFsbD48ZW0+IHBh
Z2UgMSwgbGluZSAzMzwvZW0+PC90aD48dGQ+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIEludGVybmV0
LURyYWZ0cyBhcmUgd29ya2luZyBkb2N1bWVudHMgb2YgdGhlIEludGVybmV0IEVuZ2luZWVyaW5n
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgSW50ZXJuZXQtRHJhZnRzIGFyZSB3
b3JraW5nIGRvY3VtZW50cyBvZiB0aGUgSW50ZXJuZXQgRW5naW5lZXJpbmc8L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRhc2sgRm9yY2Ug
KElFVEYpLiAgTm90ZSB0aGF0IG90aGVyIGdyb3VwcyBtYXkgYWxzbyBkaXN0cmlidXRlPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgVGFzayBGb3JjZSAoSUVURikuICBOb3RlIHRo
YXQgb3RoZXIgZ3JvdXBzIG1heSBhbHNvIGRpc3RyaWJ1dGU8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
IiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHdvcmtpbmcgZG9jdW1lbnRzIGFz
IEludGVybmV0LURyYWZ0cy4gIFRoZSBsaXN0IG9mIGN1cnJlbnQgSW50ZXJuZXQtPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgd29ya2luZyBkb2N1bWVudHMgYXMgSW50ZXJuZXQt
RHJhZnRzLiAgVGhlIGxpc3Qgb2YgY3VycmVudCBJbnRlcm5ldC08L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
IiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIERyYWZ0cyBpcyBhdCBodHRw
Oi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZHJhZnRzL2N1cnJlbnQvLjwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmlnaHQiPiAgIERyYWZ0cyBpcyBhdCBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5v
cmcvZHJhZnRzL2N1cnJlbnQvLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjwvdHI+DQogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBJbnRl
cm5ldC1EcmFmdHMgYXJlIGRyYWZ0IGRvY3VtZW50cyB2YWxpZCBmb3IgYSBtYXhpbXVtIG9mIHNp
eCBtb250aHM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBJbnRlcm5ldC1EcmFm
dHMgYXJlIGRyYWZ0IGRvY3VtZW50cyB2YWxpZCBmb3IgYSBtYXhpbXVtIG9mIHNpeCBtb250aHM8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
IGFuZCBtYXkgYmUgdXBkYXRlZCwgcmVwbGFjZWQsIG9yIG9ic29sZXRlZCBieSBvdGhlciBkb2N1
bWVudHMgYXQgYW55PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgYW5kIG1heSBi
ZSB1cGRhdGVkLCByZXBsYWNlZCwgb3Igb2Jzb2xldGVkIGJ5IG90aGVyIGRvY3VtZW50cyBhdCBh
bnk8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PiAgIHRpbWUuICBJdCBpcyBpbmFwcHJvcHJpYXRlIHRvIHVzZSBJbnRlcm5ldC1EcmFmdHMgYXMg
cmVmZXJlbmNlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgdGltZS4gIEl0IGlz
IGluYXBwcm9wcmlhdGUgdG8gdXNlIEludGVybmV0LURyYWZ0cyBhcyByZWZlcmVuY2U8L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIG1hdGVy
aWFsIG9yIHRvIGNpdGUgdGhlbSBvdGhlciB0aGFuIGFzICJ3b3JrIGluIHByb2dyZXNzLiI8L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBtYXRlcmlhbCBvciB0byBjaXRlIHRoZW0g
b3RoZXIgdGhhbiBhcyAid29yayBpbiBwcm9ncmVzcy4iPC90ZD48dGQgY2xhc3M9ImxpbmVubyIg
dmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0K
ICAgICAgPHRyPjx0ZD48YSBuYW1lPSJkaWZmMDAwMiIgLz48L3RkPjwvdHI+DQogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4g
ICBUaGlzIEludGVybmV0LURyYWZ0IHdpbGwgZXhwaXJlIG9uIDxzcGFuIGNsYXNzPSJkZWxldGUi
Pk9jdG9iZXIgMjcsIDIwMTc8L3NwYW4+LjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2Nr
Ij4gICBUaGlzIEludGVybmV0LURyYWZ0IHdpbGwgZXhwaXJlIG9uIDxzcGFuIGNsYXNzPSJpbnNl
cnQiPkphbnVhcnkgMjEsIDIwMTg8L3NwYW4+LjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij5Db3B5cmlnaHQgTm90aWNlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+Q29weXJp
Z2h0IE5vdGljZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+
DQogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFz
cz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBDb3B5cmlnaHQgKGMp
IDIwMTcgSUVURiBUcnVzdCBhbmQgdGhlIHBlcnNvbnMgaWRlbnRpZmllZCBhcyB0aGU8L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBDb3B5cmlnaHQgKGMpIDIwMTcgSUVURiBUcnVz
dCBhbmQgdGhlIHBlcnNvbnMgaWRlbnRpZmllZCBhcyB0aGU8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
IiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGRvY3VtZW50IGF1dGhvcnMuICBB
bGwgcmlnaHRzIHJlc2VydmVkLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGRv
Y3VtZW50IGF1dGhvcnMuICBBbGwgcmlnaHRzIHJlc2VydmVkLjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90
cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij4gICBUaGlzIGRvY3VtZW50IGlzIHN1YmplY3QgdG8gQkNQIDc4IGFuZCB0aGUg
SUVURiBUcnVzdCdzIExlZ2FsPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgVGhp
cyBkb2N1bWVudCBpcyBzdWJqZWN0IHRvIEJDUCA3OCBhbmQgdGhlIElFVEYgVHJ1c3QncyBMZWdh
bDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgUHJvdmlzaW9ucyBSZWxhdGluZyB0byBJRVRGIERvY3VtZW50czwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmlnaHQiPiAgIFByb3Zpc2lvbnMgUmVsYXRpbmcgdG8gSUVURiBEb2N1bWVudHM8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
IChodHRwOi8vdHJ1c3RlZS5pZXRmLm9yZy9saWNlbnNlLWluZm8pIGluIGVmZmVjdCBvbiB0aGUg
ZGF0ZSBvZjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIChodHRwOi8vdHJ1c3Rl
ZS5pZXRmLm9yZy9saWNlbnNlLWluZm8pIGluIGVmZmVjdCBvbiB0aGUgZGF0ZSBvZjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgcHVibGlj
YXRpb24gb2YgdGhpcyBkb2N1bWVudC4gIFBsZWFzZSByZXZpZXcgdGhlc2UgZG9jdW1lbnRzPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgcHVibGljYXRpb24gb2YgdGhpcyBkb2N1
bWVudC4gIFBsZWFzZSByZXZpZXcgdGhlc2UgZG9jdW1lbnRzPC90ZD48dGQgY2xhc3M9ImxpbmVu
byIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4NCiAgICAgIDx0ciBiZ2NvbG9yPSJncmF5
IiA+PHRkPjwvdGQ+PHRoPjxhIG5hbWU9InBhcnQtbDMiIC8+PHNtYWxsPnNraXBwaW5nIHRvIGNo
YW5nZSBhdDwvc21hbGw+PGVtPiBwYWdlIDQsIGxpbmUgNDE8L2VtPjwvdGg+PHRoPiA8L3RoPjx0
aD48YSBuYW1lPSJwYXJ0LXIzIiAvPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxs
PjxlbT4gcGFnZSA0LCBsaW5lIDQxPC9lbT48L3RoPjx0ZD48L3RkPjwvdHI+DQogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
ICAgYW5vdGhlciB1cHN0cmVhbSByZWxheSBhZ2VudCBkZXZpY2Ugb24gYW55IHZhbGlkIFVEUCBw
b3J0PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgYW5vdGhlciB1cHN0cmVh
bSByZWxheSBhZ2VudCBkZXZpY2Ugb24gYW55IHZhbGlkIFVEUCBwb3J0PC90ZD48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBhdmFpbGFibGUg
aW4gdGhlIHJlbGF5IHN5c3RlbSBpbmNsdWRpbmcgdGhlIERIQ1AgVURQIHBvcnQgNTQ3LjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIGF2YWlsYWJsZSBpbiB0aGUgcmVsYXkg
c3lzdGVtIGluY2x1ZGluZyB0aGUgREhDUCBVRFAgcG9ydCA1NDcuPC90ZD48dGQgY2xhc3M9Imxp
bmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBUaGUgZGVmYXVsdCBV
RFAgcG9ydCBpcyA1NDcgaWYgdGhlcmUgaXMgbm8gZXhwbGljaXQgY29uZmlndXJhdGlvbjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIFRoZSBkZWZhdWx0IFVEUCBwb3J0IGlz
IDU0NyBpZiB0aGVyZSBpcyBubyBleHBsaWNpdCBjb25maWd1cmF0aW9uPC90ZD48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBmb3IgdGhlIGdl
bmVyYWxpemVkIFVEUCBzb3VyY2UgcG9ydCBleHRlbnNpb24gZm9yIERIQ1AgcmVsYXkuPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgZm9yIHRoZSBnZW5lcmFsaXplZCBVRFAg
c291cmNlIHBvcnQgZXh0ZW5zaW9uIGZvciBESENQIHJlbGF5LjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90
cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij40LiAgUmVsYXkgU291cmNlIFBvcnQgU3ViLW9wdGlvbiBhbmQgT3B0aW9uPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+NC4gIFJlbGF5IFNvdXJjZSBQb3J0IFN1Yi1v
cHRpb24gYW5kIE9wdGlvbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3Rk
PjwvdHI+DQogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBBbHRob3Vn
aCBhIERIQ1Agc2VydmVyIGNhbiBpbXBsaWNpdGx5IGRldGVybWluZSB0aGUgVURQIHNvdXJjZSBw
b3J0PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgQWx0aG91Z2ggYSBESENQIHNl
cnZlciBjYW4gaW1wbGljaXRseSBkZXRlcm1pbmUgdGhlIFVEUCBzb3VyY2UgcG9ydDwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgd2hlbiBp
dCByZWNlaXZlcyBhIG1lc3NhZ2UgZnJvbSBhIHJlbGF5IGFnZW50LCB0aGlzIHN1Yi1vcHRpb24g
bWFrZXM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICB3aGVuIGl0IHJlY2VpdmVz
IGEgbWVzc2FnZSBmcm9tIGEgcmVsYXkgYWdlbnQsIHRoaXMgc3ViLW9wdGlvbiBtYWtlczwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgdGhl
IHJlcXVlc3QgZXhwbGljaXQgZm9yIHRoZSBzZXJ2ZXIgdG8gdXNlIGEgbm9uLURIQ1AgVURQIHBv
cnQgaW4gdGhlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgdGhlIHJlcXVlc3Qg
ZXhwbGljaXQgZm9yIHRoZSBzZXJ2ZXIgdG8gdXNlIGEgbm9uLURIQ1AgVURQIHBvcnQgaW4gdGhl
PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0
cj48dGQ+PGEgbmFtZT0iZGlmZjAwMDMiIC8+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgcmVwbHkg
bWVzc2FnZS4gIFdoZW4gSVB2NiBjYXNjYWRlZCByZWxheSBhZ2VudHMgYXJlIGludm9sdmVkLCB0
aGU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgcmVwbHkgbWVzc2FnZS4gIFdo
ZW4gSVB2NiBjYXNjYWRlZCByZWxheSBhZ2VudHMgYXJlIGludm9sdmVkLCA8c3BhbiBjbGFzcz0i
aW5zZXJ0Ij50bzwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90
ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48
dGQgY2xhc3M9ImxibG9jayI+ICAgZG93bnN0cmVhbSA8c3BhbiBjbGFzcz0iZGVsZXRlIj5ub24t
REhDUDwvc3Bhbj4gVURQIHBvcnQgbmVlZHMgdG8gYmUgcmVjb3JkZWQgdXNpbmcgdGhlIG9wdGlv
bi48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+
ICAgYWxsb3cgdGhlIHN0YXRlbGVzcyBvcGVyYXRpb24gaW4gYSByZWxheSBjaGFpbiw8L3NwYW4+
IHRoZSBkb3duc3RyZWFtIDxzcGFuIGNsYXNzPSJpbnNlcnQiPm5vbi08L3NwYW4+PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICBESENQPC9z
cGFuPiBVRFAgcG9ydCBuZWVkcyB0byBiZSByZWNvcmRlZCB1c2luZyB0aGUgb3B0aW9uLjwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWdu
PSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij40LjEuICBTb3VyY2UgUG9ydCBTdWItb3B0aW9uIGZv
ciBESENQdjQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij40LjEuICBTb3VyY2UgUG9y
dCBTdWItb3B0aW9uIGZvciBESENQdjQ8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
VGhlIFJlbGF5IEFnZW50ICJTb3VyY2UgUG9ydCBTdWItb3B0aW9uIiBpcyBhIG5ldyBvcHRpb24s
IGFuZCBpdCBpczwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFRoZSBSZWxheSBB
Z2VudCAiU291cmNlIFBvcnQgU3ViLW9wdGlvbiIgaXMgYSBuZXcgb3B0aW9uLCBhbmQgaXQgaXM8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
IHBhcnQgb2YgdGhlIHJlbGF5LWFnZW50LWluZm9ybWF0aW9uIG9wdGlvbiBmb3IgREhDUHY0IFtS
RkMzMDQ2XS48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBwYXJ0IG9mIHRoZSBy
ZWxheS1hZ2VudC1pbmZvcm1hdGlvbiBvcHRpb24gZm9yIERIQ1B2NCBbUkZDMzA0Nl0uPC90ZD48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249
InRvcCI+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRoZSBmb3JtYXQgb2YgdGhlICJTb3VyY2UgUG9y
dCBTdWItb3B0aW9uIiBpcyBzaG93biBiZWxvdzo8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICBUaGUgZm9ybWF0IG9mIHRoZSAiU291cmNlIFBvcnQgU3ViLW9wdGlvbiIgaXMgc2hv
d24gYmVsb3c6PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4N
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgICAgICAgICAgICstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKzwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAg
ICAgfCBTdWJPcHQgQ29kZSAgIHwgICAgICBMZW4gICAgICB8PC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgICAgICAgICAgfCBTdWJPcHQgQ29kZSAgIHwgICAgICBMZW4gICAgICB8
PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4NCg0KICAgICA8
dHI+PHRkPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij48L3RkPjx0ZD48L3RkPjwvdHI+DQogICAgIDx0ciBiZ2NvbG9yPSJncmF5Ij48dGggY29s
c3Bhbj0iNSIgYWxpZ249ImNlbnRlciI+PGEgbmFtZT0iZW5kIj4mbmJzcDtFbmQgb2YgY2hhbmdl
cy4gMyBjaGFuZ2UgYmxvY2tzLiZuYnNwOzwvYT48L3RoPjwvdHI+DQogICAgIDx0ciBjbGFzcz0i
c3RhdHMiPjx0ZD48L3RkPjx0aD48aT40IGxpbmVzIGNoYW5nZWQgb3IgZGVsZXRlZDwvaT48L3Ro
Pjx0aD48aT4gPC9pPjwvdGg+PHRoPjxpPjUgbGluZXMgY2hhbmdlZCBvciBhZGRlZDwvaT48L3Ro
Pjx0ZD48L3RkPjwvdHI+DQogICAgIDx0cj48dGQgY29sc3Bhbj0iNSIgYWxpZ249ImNlbnRlciIg
Y2xhc3M9InNtYWxsIj48YnIvPlRoaXMgaHRtbCBkaWZmIHdhcyBwcm9kdWNlZCBieSByZmNkaWZm
IDEuNDIuIFRoZSBsYXRlc3QgdmVyc2lvbiBpcyBhdmFpbGFibGUgZnJvbSA8YSBocmVmPSJodHRw
Oi8vd3d3LnRvb2xzLmlldGYub3JnL3Rvb2xzL3JmY2RpZmYvIiA+aHR0cDovL3Rvb2xzLmlldGYu
b3JnL3Rvb2xzL3JmY2RpZmYvPC9hPiA8L3RkPjwvdHI+DQogICA8L3RhYmxlPg0KICAgPC9ib2R5
Pg0KICAgPC9odG1sPg0K

--_003_B560FD8DFFF14D2E947BA1F1BD3AA6DAciscocom_
Content-Type: text/plain; name="ATT00001.txt"
Content-Description: ATT00001.txt
Content-Disposition: attachment; filename="ATT00001.txt"; size=616;
	creation-date="Fri, 21 Jul 2017 04:23:33 GMT";
	modification-date="Fri, 21 Jul 2017 04:23:33 GMT"
Content-ID: <CBD8A700882847428EAC260048182E7A@emea.cisco.com>
Content-Transfer-Encoding: base64

DQoNCj4gT24gSnVsIDIwLCAyMDE3LCBhdCA1OjA4IEFNLCBSYWxmIFdlYmVyIDxyYWxmLndlYmVy
QG5vbWludW0uY29tPiB3cm90ZToNCj4gDQo+IFJldmlld2VyOiBSYWxmIFdlYmVyDQo+IFJldmll
dyByZXN1bHQ6IFJlYWR5IHdpdGggTml0cw0KPiANCj4gTW9pbiENCj4gDQo+IEkgcmV2aWV3ZWQg
dGhpcyBkb2N1bWVudCBhbmQgSSdtIGdvb2Qgd2l0aCBpdC4gVGhlIG9ubHkgbWlub3IgcHVyZWx5
IGNvc21ldGljDQo+IG5vdGUgaXMgdGhhdCBpdCB0b29rIG1lIHNvbWUgdGltZSB0byB1bmRlcnN0
YW5kIHdoeSB5b3UgcmVjb3JkIHRoZSBwb3J0IGZvciB0aGUNCj4gSVB2NiByZWxheSBjaGFpbi4g
QWNjb3JkaW5nIHRvIGEgZGlzY3Vzc2lvbiBJIGhhZCB3aXRoIEJlcm5pZSB0aGF0IGlzIHRvIGJl
DQo+IGFibGUgdG8gaGF2ZSB0aGUgYWdlbnQgc3RhdGVsZXNzLiBNYXliZSBhZGQgdGhhdCB0byB0
aGUgbW90aXZhdGlvbiB3aHkgeW91DQo+IHN0b3JlIGl0IGluIHRoZSBwYWNrZXQgYXQgdGhlIGVu
ZCBvZiBzZWN0aW9uIDQgKCwgdG8gYWxsb3cgc3RhdGVsZXNzIG9wZXJhdGlvbg0KPiBpbiBhIHJl
bGF5IGNoYWluKQ0KPiANCj4gU28gbG9uZw0KPiAtUmFsZg0KPiANCj4gDQoNCg==

--_003_B560FD8DFFF14D2E947BA1F1BD3AA6DAciscocom_--


From nobody Thu Jul 20 21:53:30 2017
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83440127010 for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 21:53:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.4
X-Spam-Level: 
X-Spam-Status: No, score=-5.4 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, 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 4MgPS_sV_9_1 for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 21:53:26 -0700 (PDT)
Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) (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 2BD2C126C23 for <ietf@ietf.org>; Thu, 20 Jul 2017 21:53:26 -0700 (PDT)
Received: from pps.filterd (m0098399.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v6L4nict002802 for <ietf@ietf.org>; Fri, 21 Jul 2017 00:53:23 -0400
Received: from e31.co.us.ibm.com (e31.co.us.ibm.com [32.97.110.149]) by mx0a-001b2d01.pphosted.com with ESMTP id 2buaj38qev-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 21 Jul 2017 00:53:23 -0400
Received: from localhost by e31.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 20 Jul 2017 22:53:23 -0600
Received: from b03cxnp08027.gho.boulder.ibm.com (9.17.130.19) by e31.co.us.ibm.com (192.168.1.131) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 20 Jul 2017 22:53:20 -0600
Received: from b03ledav006.gho.boulder.ibm.com (b03ledav006.gho.boulder.ibm.com [9.17.130.237]) by b03cxnp08027.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v6L4rKVc58720318 for <ietf@ietf.org>; Thu, 20 Jul 2017 21:53:20 -0700
Received: from b03ledav006.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 2EC70C603E for <ietf@ietf.org>; Thu, 20 Jul 2017 22:53:20 -0600 (MDT)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b03ledav006.gho.boulder.ibm.com (Postfix) with ESMTPS id 089CBC6037 for <ietf@ietf.org>; Thu, 20 Jul 2017 22:53:19 -0600 (MDT)
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.15.2/8.12.5) with ESMTP id v6L4rIDJ023142 for <ietf@ietf.org>; Fri, 21 Jul 2017 00:53:19 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v6L4rIVn023124 for ietf@ietf.org; Fri, 21 Jul 2017 00:53:18 -0400
From: narten@us.ibm.com
Date: Fri, 21 Jul 2017 00:53:18 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-GCONF: 00
x-cbid: 17072104-8235-0000-0000-00000BF88B70
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00007397; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000214; SDB=6.00890605; UDB=6.00444976; IPR=6.00670772;  BA=6.00005482; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00016307; XFM=3.00000015; UTC=2017-07-21 04:53:21
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17072104-8236-0000-0000-00003CD9B2C1
Message-Id: <201707210453.v6L4rIVn023124@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-07-21_01:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=13 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1706020000 definitions=main-1707210076
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/J6FTbRZxikZBNVSwsnwHwnM8WPc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 04:53:28 -0000

Total of 115 messages in the last 7 days.
 
script run at: Fri Jul 21 00:53:13 EDT 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  6.09% |    7 |  7.34% |    96326 | ynir.ietf@gmail.com
  2.61% |    3 |  8.83% |   115937 | iab-chair@iab.org
  5.22% |    6 |  4.51% |    59149 | john-ietf@jck.com
  3.48% |    4 |  4.08% |    53581 | mellon@fugue.com
  4.35% |    5 |  3.13% |    41032 | mcr+ietf@sandelman.ca
  1.74% |    2 |  5.10% |    66977 | adrian@olddog.co.uk
  3.48% |    4 |  2.96% |    38805 | brian.e.carpenter@gmail.com
  2.61% |    3 |  2.90% |    38083 | jordi.palet@consulintel.es
  2.61% |    3 |  2.72% |    35697 | aaron.falk@gmail.com
  2.61% |    3 |  2.64% |    34661 | j.schoenwaelder@jacobs-university.de
  2.61% |    3 |  2.54% |    33331 | tjc@ecs.soton.ac.uk
  1.74% |    2 |  3.04% |    39883 | ford@isoc.org
  2.61% |    3 |  2.16% |    28324 | barryleiba@computer.org
  2.61% |    3 |  1.76% |    23105 | ajs@anvilwalrusden.com
  1.74% |    2 |  2.37% |    31160 | vaibhavsinghacads@gmail.com
  1.74% |    2 |  1.86% |    24414 | agmalis@gmail.com
  1.74% |    2 |  1.86% |    24344 | john_brzozowski@comcast.com
  1.74% |    2 |  1.63% |    21385 | rjsparks@nostrum.com
  1.74% |    2 |  1.57% |    20601 | chris.dearlove@baesystems.com
  1.74% |    2 |  1.46% |    19217 | spencerdawkins.ietf@gmail.com
  1.74% |    2 |  1.27% |    16655 | julian.reschke@gmx.de
  1.74% |    2 |  1.20% |    15683 | ietf@meetecho.com
  1.74% |    2 |  1.19% |    15618 | randy_presuhn@alumni.stanford.edu
  1.74% |    2 |  1.17% |    15351 | sm+ietf@elandsys.com
  1.74% |    2 |  1.07% |    14036 | alexey.melnikov@isode.com
  1.74% |    2 |  1.06% |    13890 | paul.hoffman@vpnc.org
  1.74% |    2 |  1.05% |    13716 | chair@ietf.org
  0.87% |    1 |  1.64% |    21545 | erosen@juniper.net
  0.87% |    1 |  1.55% |    20288 | kwatsen@juniper.net
  0.87% |    1 |  1.06% |    13851 | samitac.ietf@gmail.com
  0.87% |    1 |  1.03% |    13513 | sarikaya2012@gmail.com
  0.87% |    1 |  1.01% |    13301 | shares@ndzh.com
  0.87% |    1 |  1.01% |    13250 | akatlas@gmail.com
  0.87% |    1 |  0.97% |    12780 | olejacobsen@me.com
  0.87% |    1 |  0.88% |    11563 | narten@us.ibm.com
  0.87% |    1 |  0.84% |    11075 | allison.mankin@gmail.com
  0.87% |    1 |  0.80% |    10469 | blong@google.com
  0.87% |    1 |  0.76% |    10006 | morrowc.lists@gmail.com
  0.87% |    1 |  0.76% |     9999 | presnick@qti.qualcomm.com
  0.87% |    1 |  0.76% |     9983 | mnot@mnot.net
  0.87% |    1 |  0.76% |     9950 | sean@sn3rd.com
  0.87% |    1 |  0.73% |     9551 | tony@att.com
  0.87% |    1 |  0.72% |     9514 | narellec@gmail.com
  0.87% |    1 |  0.70% |     9209 | lloyd.wood@yahoo.co.uk
  0.87% |    1 |  0.70% |     9171 | mrex@sap.com
  0.87% |    1 |  0.66% |     8684 | mersue@gmail.com
  0.87% |    1 |  0.64% |     8359 | johnl@taugh.com
  0.87% |    1 |  0.63% |     8327 | nick@foobar.org
  0.87% |    1 |  0.63% |     8229 | rsk@gsp.org
  0.87% |    1 |  0.62% |     8181 | housley@vigilsec.com
  0.87% |    1 |  0.60% |     7815 | scott.brim@gmail.com
  0.87% |    1 |  0.59% |     7808 | dhc@dcrocker.net
  0.87% |    1 |  0.59% |     7744 | loa@pi.nu
  0.87% |    1 |  0.58% |     7642 | yoshiro.yoneya@jprs.co.jp
  0.87% |    1 |  0.58% |     7596 | sob@sobco.com
  0.87% |    1 |  0.58% |     7577 | john@jck.com
  0.87% |    1 |  0.54% |     7046 | cabo@tzi.org
  0.87% |    1 |  0.52% |     6816 | amorris@amsl.com
  0.87% |    1 |  0.51% |     6754 | mcr@sandelman.ca
  0.87% |    1 |  0.51% |     6729 | sbanks@encrypted.net
  0.87% |    1 |  0.48% |     6261 | nordmark@acm.org
  0.87% |    1 |  0.41% |     5387 | agenda@ietf.org
  0.87% |    1 |  0.40% |     5274 | joelja@bogus.com
  0.87% |    1 |  0.40% |     5235 | ralf.weber@nominum.com
  0.87% |    1 |  0.37% |     4857 | ve7jtb@ve7jtb.com
--------+------+--------+----------+------------------------
100.00% |  115 |100.00% |  1312300 | Total


From nobody Thu Jul 20 21:55:52 2017
Return-Path: <lyndon@orthanc.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F5E6131DB3 for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 21:55:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 el7hQIT1FyL9 for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 21:55:50 -0700 (PDT)
Received: from orthanc.ca (orthanc.ca [IPv6:2607:f2f8:abf8::2]) (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 1DA1D12EC12 for <ietf@ietf.org>; Thu, 20 Jul 2017 21:55:50 -0700 (PDT)
Received: from minnie.hitronhub.home (S0106a84e3f81a003.vc.shawcable.net [24.80.126.119]) (authenticated bits=0) by orthanc.ca (8.15.2/8.15.2) with ESMTPSA id v6L4tmSb074665 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Thu, 20 Jul 2017 21:55:49 -0700 (PDT) (envelope-from lyndon@orthanc.ca)
From: Lyndon Nerenberg <lyndon@orthanc.ca>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: beta web site critiques
Date: Thu, 20 Jul 2017 21:55:43 -0700
References: <20170720125927.lbmtvwo3dncmoxmb@mx4.yitter.info> <30D585774FDAF7F5158A6A26@PSB> <4B7A0FD7-9088-4687-9C3A-F137E4873CE8@orthanc.ca>
To: ietf@ietf.org
In-Reply-To: <4B7A0FD7-9088-4687-9C3A-F137E4873CE8@orthanc.ca>
Message-Id: <4AAD6806-5952-4D62-9B27-879E4446CE19@orthanc.ca>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XgxmfqgM4RrYpMG9LjdFxQddE4I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 04:55:51 -0000

> And if there is a link to the datatracker, or anything else of use, I =
sure can't find it on that page.

To invoke a wee bit of 3rd-party humour to make my point:

  https://www.xkcd.com/773/

--lyndon


From nobody Thu Jul 20 23:34:55 2017
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C3B71296CF for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 23:34:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 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_MED=-2.3, RP_MATCHES_RCVD=-0.001, 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=ecs.soton.ac.uk
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 CBtPOQZ1-Y8B for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 23:34:51 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEA31126D05 for <ietf@ietf.org>; Thu, 20 Jul 2017 23:34:50 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6L6YfMl016821; Fri, 21 Jul 2017 07:34:42 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v6L6YfMl016821
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1500618882; bh=yme/ao6yVzXjUTorNZRk30x8ZUg=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=BCYLjcXobUhXsS2Eis4zQB/DiuU6BkKr6Z2uJneOi4ASVh+TPF69/H3AGfjzxgV5i ly6PQLLcGLXf/nQPlvRZ1OD6gnDMTHzmUGIKoPOIqCZJ6Mk8rKmgQcE7/lTpApVqHP VlaLGoqhXf3/W85prXNqOvW96vQzE0ezlxZA4Qrg=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id y6K7Yf1100701237Kl ret-id none; Fri, 21 Jul 2017 07:34:42 +0100
Received: from [IPv6:2001:67c:1232:144:655b:1823:aeec:54b3] ([IPv6:2001:67c:1232:144:655b:1823:aeec:54b3]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6L6YYQw019224 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 21 Jul 2017 07:34:35 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: beta web site critiques
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <4AAD6806-5952-4D62-9B27-879E4446CE19@orthanc.ca>
Date: Fri, 21 Jul 2017 07:34:33 +0100
Cc: ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|f6e919a292c60050d7c2bc5a5508508ay6K7Yf03tjc|ecs.soton.ac.uk|CB6240CB-B185-4BB6-9912-ACC44C974DE7@ecs.soton.ac.uk>
References: <20170720125927.lbmtvwo3dncmoxmb@mx4.yitter.info> <30D585774FDAF7F5158A6A26@PSB> <4B7A0FD7-9088-4687-9C3A-F137E4873CE8@orthanc.ca> <4AAD6806-5952-4D62-9B27-879E4446CE19@orthanc.ca> <CB6240CB-B185-4BB6-9912-ACC44C974DE7@ecs.soton.ac.uk>
To: Lyndon Nerenberg <lyndon@orthanc.ca>
X-Mailer: Apple Mail (2.3273)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-ECS-MailScanner-SpamScore: s
X-smtpf-Report: sid=y6K7Yf110070123700; tid=y6K7Yf1100701237Kl; client=relay,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v6L6YfMl016821
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9LRjJznp0GWlwokr7XzAqNH32FY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 06:34:53 -0000

> On 21 Jul 2017, at 05:55, Lyndon Nerenberg <lyndon@orthanc.ca> wrote:
>=20
>> And if there is a link to the datatracker, or anything else of use, I =
sure can't find it on that page.
>=20
> To invoke a wee bit of 3rd-party humour to make my point:
>=20
>  https://www.xkcd.com/773/

That is something of a classic!

Tim=


From nobody Thu Jul 20 23:41:13 2017
Return-Path: <lyndon@orthanc.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D2A91250B8 for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 23:41:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 QoypJE2UJkzF for <ietf@ietfa.amsl.com>; Thu, 20 Jul 2017 23:41:11 -0700 (PDT)
Received: from orthanc.ca (orthanc.ca [IPv6:2607:f2f8:abf8::2]) (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 0F23D124D85 for <ietf@ietf.org>; Thu, 20 Jul 2017 23:41:11 -0700 (PDT)
Received: from minnie.hitronhub.home (S0106a84e3f81a003.vc.shawcable.net [24.80.126.119]) (authenticated bits=0) by orthanc.ca (8.15.2/8.15.2) with ESMTPSA id v6L6eTM9075059 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 20 Jul 2017 23:40:30 -0700 (PDT) (envelope-from lyndon@orthanc.ca)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: beta web site critiques
From: Lyndon Nerenberg <lyndon@orthanc.ca>
In-Reply-To: <EMEW3|f6e919a292c60050d7c2bc5a5508508ay6K7Yf03tjc|ecs.soton.ac.uk|CB6240CB-B185-4BB6-9912-ACC44C974DE7@ecs.soton.ac.uk>
Date: Thu, 20 Jul 2017 23:40:23 -0700
Cc: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <1EAB2C53-BDD6-4C46-B62E-2B4CB466147C@orthanc.ca>
References: <20170720125927.lbmtvwo3dncmoxmb@mx4.yitter.info> <30D585774FDAF7F5158A6A26@PSB> <4B7A0FD7-9088-4687-9C3A-F137E4873CE8@orthanc.ca> <4AAD6806-5952-4D62-9B27-879E4446CE19@orthanc.ca> <CB6240CB-B185-4BB6-9912-ACC44C974DE7@ecs.soton.ac.uk> <EMEW3|f6e919a292c60050d7c2bc5a5508508ay6K7Yf03tjc|ecs.soton.ac.uk|CB6240CB-B185-4BB6-9912-ACC44C974DE7@ecs.soton.ac.uk>
To: Tim Chown <tjc@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lA7iyQKqN2f-BFtDip5SdXccRmU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 06:41:13 -0000

> On Jul 20, 2017, at 11:34 PM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:
> 
> That is something of a classic!

It's also the Twitter version of Edward Tufte, apparently.


From nobody Fri Jul 21 00:44:11 2017
Return-Path: <mary.h.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40F8D12714F for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 00:44:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level: 
X-Spam-Status: No, score=-1.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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 LL4yiyTLY3Yy for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 00:44:08 -0700 (PDT)
Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002: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 C1899124217 for <ietf@ietf.org>; Fri, 21 Jul 2017 00:44:08 -0700 (PDT)
Received: by mail-yw0-x231.google.com with SMTP id x125so21764107ywa.0 for <ietf@ietf.org>; Fri, 21 Jul 2017 00:44:08 -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=BNlxoYM/O5O5nRlZofJrJfNlbbjrY0hOwvRmuHzg02Y=; b=QoFodfHkvfxMdAx24Crm6Z8iI3Ld+v3JR/T7KRqYkNn9b6LGJfGNPfPe9ciErzSPay +oiUjf40iKwKmLHRhWuGpIniFK9nofvNCb4I1U/UjaBLPb/+ysA6L/CZuTniaFq+rjs3 wpsFyjEboQmaySiGbEnPp+nw04zlPmB/D0JzzMQ2RZzDdlXNOecGSbYJ5G4AAJbHovYs X5h+YRR71iO5y/deXr+3/35fLjly/6Bjy5fOZCWvpfLZzCncSM+w6yn2NQCtOXhNHODe 9PjNqL2iWG1xEjrqv5hPt4SZG/3K1V4C2UfnlQHFlsoRe3ZokE9rRskcKB42tDBvDXap /2dw==
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=BNlxoYM/O5O5nRlZofJrJfNlbbjrY0hOwvRmuHzg02Y=; b=m23YGke83zFmuBPWpqN9jXDG9sfbgJdCTLlz4yOmkoEzogb0uQgGnSv42Lmisc/w/T f00mlozTbbB5vB1NVYlaSrZkQldOTWPg5xXwrQ12Xvih9WRCB9QwaplqgnLNUech1LlU 3uMCYDeklMV36pKN7xst8TMvjq+4aceD3zGK6XGhoezYs/Jo41uvSk4bthhv25Ubg5C6 spsJPVUmi20l5gtRE6rIHQRFIbZUNR3FmjMedL4qdrFY6N6rT7GsEYFBlJHt3QRq2z5z +ZBCmuMA5BCDFhs9oAXGaE63R7dGJrnZDMlVY047v731FhhoLjAOIS1+foSwjuTRe0pK qdPA==
X-Gm-Message-State: AIVw110bB72KjNRQkNRc2T/rlzSotZ/YjpzfRFzk4UzVcRLiNEJCgCE0 bz6r+LvwkmtPW7iQc2XWpNKpmcZ0nA==
X-Received: by 10.129.109.15 with SMTP id i15mr5300082ywc.459.1500623048108; Fri, 21 Jul 2017 00:44:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.189.193 with HTTP; Fri, 21 Jul 2017 00:44:07 -0700 (PDT)
In-Reply-To: <CACRMD1HxMO1zx0_Kp7Bo511FZ_O5YS-ezwN=tsTJ+8cWky_xCA@mail.gmail.com>
References: <CAKKJt-ehdzREsf3QzGZ+JFOkMm-dGpSdGVFBUJE4BhqWweY+Og@mail.gmail.com> <08eb01d3006d$f0aa8a60$d1ff9f20$@olddog.co.uk> <CAKKJt-fhDgfi7UofBjmLo9xhHqjUe+tL8THs6yGYv3Cn9ETq0g@mail.gmail.com> <09d501d3009d$8b33f560$a19be020$@olddog.co.uk> <2107809846.1308501.1500528537111@mail.yahoo.com> <CACRMD1HxMO1zx0_Kp7Bo511FZ_O5YS-ezwN=tsTJ+8cWky_xCA@mail.gmail.com>
From: Mary B <mary.h.barnes@gmail.com>
Date: Fri, 21 Jul 2017 02:44:07 -0500
Message-ID: <CABmDk8=y4ak6eE80Z2WqU302eDxh_uNgsq0gEmp4zSO1-y_HMQ@mail.gmail.com>
Subject: Re: Slides, eye charts, and a beg for readability
To: Narelle <narellec@gmail.com>
Cc: Lloyd Wood <lloyd.wood@yahoo.co.uk>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a114dde50b9cd250554cf0702"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bTd3psE4JrHXuyYYnf5w2CvYugQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 07:44:10 -0000

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

I also think one of the issues is the lighting in the meeting rooms.  I'm
in Barcelona/Athens and the lights are quite bright at the front of the
room which makes it much harder to see the slides.  Also, it looks like the
projector isn't the brightest - the slides have a yellowish tint and it's
not the slides themselves but the projector (although the screen may also
be contributing to that).

Mary.

On Thu, Jul 20, 2017 at 7:47 PM, Narelle <narellec@gmail.com> wrote:

>
> Font size, colour contrast, animations are all just some of the things
> that go to good slideware so that people with vision impairments can use
> them.
>
> There is a good guide to powerpoint accessibility generally here:
> http://webaim.org/techniques/powerpoint/
>
> It goes to adding alt tags, reading order and (briefly) to contrast in
> colour etc.
>
> As does this overview: https://www.slidegenius.com/
> blog/making-your-powerpoint-accessible-for-the-visually-impaired
>
> Frankly all our materials should take these things into account...
> Usability by design goes to not just the technology but how we communicate
> about the technology.
>
> regards
>
> --
>
>
> Narelle Clark
> narellec@gmail.com
>

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

<div dir=3D"ltr"><div>I also think one of the issues is the lighting in the=
 meeting rooms.=C2=A0 I&#39;m in Barcelona/Athens and the lights are quite =
bright at the front of the room which makes it much harder to see the slide=
s.=C2=A0 Also, it looks like the projector isn&#39;t the brightest - the sl=
ides have a yellowish tint and it&#39;s not the slides themselves but the p=
rojector (although the screen may also be contributing to that).<br><br></d=
iv>Mary. <br></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote=
">On Thu, Jul 20, 2017 at 7:47 PM, Narelle <span dir=3D"ltr">&lt;<a href=3D=
"mailto:narellec@gmail.com" target=3D"_blank">narellec@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"><div dir=3D"ltr"><div><br></d=
iv>Font size, colour contrast, animations are all just some of the things t=
hat go to good slideware so that people with vision impairments can use the=
m.<br><br>There is a good guide to powerpoint accessibility generally here:=
 <a href=3D"http://webaim.org/techniques/powerpoint" target=3D"_blank">http=
://webaim.org/techniques/<wbr>powerpoint</a>/<br><br>It goes to adding alt =
tags, reading order and (briefly) to contrast in colour etc.<br><br>As does=
 this overview: <a href=3D"https://www.slidegenius.com/blog/making-your-pow=
erpoint-accessible-for-the-visually-impaired/" target=3D"_blank">https://ww=
w.slidegenius.com/<wbr>blog/making-your-powerpoint-<wbr>accessible-for-the-=
visually-<wbr>impaired</a><br><br>Frankly all our materials should take the=
se things into account... Usability by design goes to not just the technolo=
gy but how we communicate about the technology.<br><br>regards<span class=
=3D"HOEnZb"><font color=3D"#888888"><br><br>-- <br><br><br>Narelle Clark<br=
><a href=3D"mailto:narellec@gmail.com" target=3D"_blank">narellec@gmail.com=
</a></font></span></div>
</blockquote></div><br></div>

--001a114dde50b9cd250554cf0702--


From nobody Fri Jul 21 01:22:55 2017
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36DF213169C for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 01:22:52 -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 n2FbEo3h2YZv for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 01:22:50 -0700 (PDT)
Received: from mail-yw0-x22b.google.com (mail-yw0-x22b.google.com [IPv6:2607:f8b0:4002:c05::22b]) (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 DE41B12EC51 for <ietf@ietf.org>; Fri, 21 Jul 2017 01:22:49 -0700 (PDT)
Received: by mail-yw0-x22b.google.com with SMTP id v193so21867111ywg.2 for <ietf@ietf.org>; Fri, 21 Jul 2017 01:22:49 -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=rNiVXEK5SZF5N8jV7yOQrlQZoh2FapvZu9vVcBC9jnM=; b=LJcuwGkjRXzZRqquz5T7myNlHX5Pe2JPDsCc4uoWEUqSUGkOMzGV/zrlpun4+JIxsu mh8l0F5oCz/ZgWOHqFlorcHYtDE7hFDSd11EqO6PgVzsF1hngnmUgdxdF0DGvgnATqY/ NREb9i10I+vWQfTrPL6XSbts8MXk5XYOPniewBuP4SOGZtErfrBMdp22HI/onSrvPIGF hkyfrZwAeKI8xP9cCdM4FGUvKbqV5+Caocr+uiUKF2/Fkjidd2UiSad4bP+cSJ5HNU/X s+DhjpAPZ41fkG+GNrakXjtVGbLJboai4quvncxbtf8q3I66DlyTrFMgPLmOSsEeD9gA Qc8Q==
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=rNiVXEK5SZF5N8jV7yOQrlQZoh2FapvZu9vVcBC9jnM=; b=KmY9lzbo0nSLJzxJztIbsEbEmaxncarvwsCCKv3484j3mKNt1GV54MQ4EVFUPAoUkr +HOHgJ/xLn6CLgLOc/V6fEIdY5S/SmzH8IPXAGueMfXkg3+opYtyvyph2qHmBWg5zjh+ zVEvB/4MZ2Ns8hN6DI8Td0VLEraL4OKgp2yL40DzD5tENpseJdpeDd2sp4d4o8czT/1G ftuKmCD9BKbXp67CK3+iBe15uEbpVErHL3jbFCglDHI3GeRQIMM3VeD5buY9Er3NAoRD hy9UoJQBchSrBJz0BuvSDu888K4l6eNYaDQUgufkmPQAgTngMvoR1B20wmFVFzWTQzp7 c2dw==
X-Gm-Message-State: AIVw112ee2DvFrGgGY1ivGHlRzboVKhSu1x6G37dkl+FXDDDacJPCCQD OfWCQEP5oVi4QeiS5GqrYvPfLCx2Cw==
X-Received: by 10.129.122.137 with SMTP id v131mr5437030ywc.130.1500625369144;  Fri, 21 Jul 2017 01:22:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.45.101 with HTTP; Fri, 21 Jul 2017 01:22:48 -0700 (PDT)
Received: by 10.37.45.101 with HTTP; Fri, 21 Jul 2017 01:22:48 -0700 (PDT)
In-Reply-To: <CAPv4CP8UGr_xLDYW=zKQUP6mXaWgQ67JM+-_NJOvCgfOhXU2hQ@mail.gmail.com>
References: <CAKKJt-ehdzREsf3QzGZ+JFOkMm-dGpSdGVFBUJE4BhqWweY+Og@mail.gmail.com> <CAPv4CP8UGr_xLDYW=zKQUP6mXaWgQ67JM+-_NJOvCgfOhXU2hQ@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Fri, 21 Jul 2017 10:22:48 +0200
Message-ID: <CAKKJt-et1SW5J_dU-Bfj=yCKtvVv+sSqzYqh1Sur=NgzA-Mghg@mail.gmail.com>
Subject: Re: Slides, eye charts, and a beg for readability
To: Scott Brim <scott.brim@gmail.com>
Cc: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c0a735011a56f0554cf9206"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SCXgPcTaqr_hhMoAbyDPdvv9FBs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 08:22:52 -0000

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

Hi, Scott,

On Jul 19, 2017 6:04 PM, "Scott Brim" <scott.brim@gmail.com> wrote:

Can't you just sit in front?


"Does not scale" ;-)

I see that several of us are griping in this thread, which is what one
would expect, given the nature of this mailing list.

I'm not hearing people saying, "I never have problems, must be you", which
I interpret as the visual equivalent of "if the music is too loud, you're
too old".

So, I'll probably bring this up on the working group chairs mailing list,
for their discussion and possible action.

Thanks, everyone, for your thoughts.

Spencer

Spencer

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

<div dir=3D"auto"><div>Hi, Scott,<br><div class=3D"gmail_extra"><br><div cl=
ass=3D"gmail_quote">On Jul 19, 2017 6:04 PM, &quot;Scott Brim&quot; &lt;<a =
href=3D"mailto:scott.brim@gmail.com">scott.brim@gmail.com</a>&gt; wrote:<br=
 type=3D"attribution"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"auto">Can&#39;t =
you just sit in front?=C2=A0</div>
</blockquote></div><br></div></div><div class=3D"gmail_extra" dir=3D"auto">=
&quot;Does not scale&quot; ;-)</div><div class=3D"gmail_extra" dir=3D"auto"=
><br></div><div class=3D"gmail_extra" dir=3D"auto">I see that several of us=
 are griping in this thread, which is what one would expect, given the natu=
re of this mailing list.=C2=A0</div><div class=3D"gmail_extra" dir=3D"auto"=
><br></div><div class=3D"gmail_extra" dir=3D"auto">I&#39;m not hearing peop=
le saying, &quot;I never have problems, must be you&quot;, which I interpre=
t as the visual equivalent of &quot;if the music is too loud, you&#39;re to=
o old&quot;.</div><div class=3D"gmail_extra" dir=3D"auto"><br></div><div cl=
ass=3D"gmail_extra" dir=3D"auto">So, I&#39;ll probably bring this up on the=
 working group chairs mailing list, for their discussion and possible actio=
n.</div><div class=3D"gmail_extra" dir=3D"auto"><br></div><div class=3D"gma=
il_extra" dir=3D"auto">Thanks, everyone, for your thoughts.</div><div class=
=3D"gmail_extra" dir=3D"auto"><br></div><div class=3D"gmail_extra" dir=3D"a=
uto">Spencer</div><div class=3D"gmail_extra" dir=3D"auto"><br></div><div cl=
ass=3D"gmail_extra" dir=3D"auto">Spencer</div></div>

--94eb2c0a735011a56f0554cf9206--


From nobody Fri Jul 21 01:32:24 2017
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 727F912EB2B for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 01:32:22 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=yitter.info header.b=KOv8U39x; dkim=pass (1024-bit key) header.d=yitter.info header.b=ICkjmo1z
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 qJNogTnD5lA2 for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 01:32:21 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FC23129AA0 for <ietf@ietf.org>; Fri, 21 Jul 2017 01:32:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 6FB72BD996 for <ietf@ietf.org>; Fri, 21 Jul 2017 08:32:20 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1500625940; bh=t/wan3+mza3h3DMsBkdGXGkmPCdfVJaMMSfl/jZS4mA=; h=Date:From:To:Subject:References:In-Reply-To:From; b=KOv8U39x/FjVzo3yAbLbTX+jF4TivHSgRq/oL22j4i75e0lAilBu4wDbpclIm5kuA S593AJ5ObbbnTZiai1UFYip5xBCVj5p6y6rr9oMkPMXWjbgT52hWfjOJGs55ru2iU/ XP6Zzrt2gUC9IXkDVHKir2Yz/NfHps7FdUHC29pQ=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dO9FWscmFoHn for <ietf@ietf.org>; Fri, 21 Jul 2017 08:32:18 +0000 (UTC)
Date: Fri, 21 Jul 2017 04:32:16 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1500625938; bh=t/wan3+mza3h3DMsBkdGXGkmPCdfVJaMMSfl/jZS4mA=; h=Date:From:To:Subject:References:In-Reply-To:From; b=ICkjmo1zBMbn+XfsloY9pLgbJ3zGkTNARqIVQOvlluCeVLYnNHpzJ7Lm3mZYGK6SN b4TAUNQufZdBKr2RZzSUkGanpKJJRiJ5Ei3eBB9hvRrOHh04hq1oEQqKjbSTxHKeDe Q+JxdO4mo/xYUf4Y89fNnDCmS4RwwdqkvUO83+iA=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Revamp of the www.ietf.org website
Message-ID: <20170721083215.a2qdgfrpg2jf6irq@mx4.yitter.info>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6394482@GLKXM0002V.GREENLNK.net> <39D1C0A9-DB43-42DD-BD3F-7D636856ECEF@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <39D1C0A9-DB43-42DD-BD3F-7D636856ECEF@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/K8pR_6PDXlhw2Jj3_rZYstnvrZ4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 08:32:22 -0000

Dear colleagues,

On Tue, Jul 18, 2017 at 11:13:10AM +0200, Yoav Nir wrote:
> The new site is focused not on the existing people active in the IETF. It’s focused on the general public.  The place where work gets done these days is datatracker.
> 

I have had a look at the beta site, and it seems to me that we have at
least three possible audiences:

    1.  People who wonder what an IETF is and how it might be useful
    to them.  That actually is an important function of a website, and
    despite the arguments about how the IETF isn't about marketing
    organization (and the xkcd observations about university websites)
    we cannot ignore this function.  To some extent, we are competing
    with other ways of developing the Internet -- "living standards",
    code as standard, multilateral standards bodies, &c -- and if we
    think our way is good for some cases we do in fact need to market
    that.  I think the beta site is obviously better at that than our
    current site, which appears to be designed with a MEMBERS ONLY
    sign on the front.  We are the hardest club to join given that we
    don't have membership. I think the beta site is trying to make
    that burden a little less, and I believe it is a good thing.

    2.  People who already are familiar with the IETF and are working
    here.  The beta site says it's supposed to be the "new front
    door".  I don't know about all of you, but in my own house I also
    know how to enter by the other doors.  Maybe we just need to use a
    different entrance?

    3.  People whose connectivity makes the more graphically intense
    and somewhat larger site less useful.  I think it would be useful
    to analyse the extent to which this is a real problem, and whether
    the trade-off is adequate for the particular use case we have in
    mind.  After all, loading this (still not huge) web page is hardly
    the most bandwidth-intensive thing a plausible IETF participant is
    likely to do.  Moreover, it's not clear whether the problem in
    this case is slow backhaul links or slow local/last-mile links; if
    it's the latter, more IXes (and CDNs) are likely good enough
    mitigations.  This seems like an issue that could use some
    empirical data, but I am not sure how to get it.  Perhaps the
    participants of GAIA would hae some ideas.

I appreciate the effort to make these changes in public with lots of
consultation: I know how much harder it is to run a project this way,
but I think it's a good sign that the tools are as usual being
developed this way.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Fri Jul 21 01:46:23 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E49E312EB2B for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 01:46:21 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 O0kx84mCA6mG for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 01:46:20 -0700 (PDT)
Received: from mail-pg0-x233.google.com (mail-pg0-x233.google.com [IPv6:2607:f8b0:400e:c05::233]) (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 77621129B55 for <ietf@ietf.org>; Fri, 21 Jul 2017 01:46:20 -0700 (PDT)
Received: by mail-pg0-x233.google.com with SMTP id y129so26003907pgy.4 for <ietf@ietf.org>; Fri, 21 Jul 2017 01:46:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xJ2TjuEWnzBmKG3PV3ErDWFAbZ0OEnJ8H/Nrc81m7SM=; b=HKsGdoFBcD6QSpAu9iKM1ahhZV8qW/bHjwRMQ6EChMtJlPTohFVSL3t90O1sYsMvQB R9OTYNPEx6CVAIOkLYjT3g1k7cHIZ8hk5t6LxQUYghyCchglsNO/Eovt2JDEXkAqmpX7 +f8jEcEepmRRXrPyerxBVPraurOzNBXwfvhahE5OoGZMOPkDUDAaqg2f4smD1FCbV+ft SU13tHpK2gal5E17niodmVuvUt6SEmdINkhJB4pV9/BYHuRxCd71XG9zzLNm2w5U8WoS AlyQtOG5DRYps/VbTvPRgokVp3ddyNFe3Fm0rD9am5k0Aqg1yCKJ2bLqQB2tGfLh/Y9u WR9A==
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=xJ2TjuEWnzBmKG3PV3ErDWFAbZ0OEnJ8H/Nrc81m7SM=; b=mFKfdJl10IWHlw/nB/3WJY51iY4Dflh2zvEzt2IvoNUfYRYClt295IRX5sWBORWPNQ ucNnJ/dcordl4D8REfrp3YEg0DuSd8MxJt1TuYXrMt+M9u0C4suLJBnZWUJuuj98zHD6 00oK2hHM1OZuslrh5YOiWr9nGAZ9NOuNhpKn1d27LqjOx8SLpLMsdLJNHGSUmOT/qNK8 WaRIS9E8WtTBPgx4qrhWLrjTZ43R0rQDZ4aq0KdEM5Cly8ApLtf3JJTfdygLBaqNB8+n KohuaZblDSld45/SY3D0Fg5Vzjo2mjBQgP1rTiPb5oS4XdD5TnSSsqUr2dvEEDibu88r HbjQ==
X-Gm-Message-State: AIVw110kXc3T5c6kQZRr5O+zijEC4qTLwBcwpnetaJF1JC2R8k3vo6EL QUAgg912KJJRRXspgvHMq1KMgoSeyyOS
X-Received: by 10.99.44.70 with SMTP id s67mr6596271pgs.310.1500626779917; Fri, 21 Jul 2017 01:46:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.181.130 with HTTP; Fri, 21 Jul 2017 01:45:39 -0700 (PDT)
In-Reply-To: <CAKKJt-et1SW5J_dU-Bfj=yCKtvVv+sSqzYqh1Sur=NgzA-Mghg@mail.gmail.com>
References: <CAKKJt-ehdzREsf3QzGZ+JFOkMm-dGpSdGVFBUJE4BhqWweY+Og@mail.gmail.com> <CAPv4CP8UGr_xLDYW=zKQUP6mXaWgQ67JM+-_NJOvCgfOhXU2hQ@mail.gmail.com> <CAKKJt-et1SW5J_dU-Bfj=yCKtvVv+sSqzYqh1Sur=NgzA-Mghg@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Fri, 21 Jul 2017 10:45:39 +0200
Message-ID: <CAPt1N1mOhZHCy=jJOrPyTz3-qy3KP0Mvrg+6Qj+Hpid4bq1-jw@mail.gmail.com>
Subject: Re: Slides, eye charts, and a beg for readability
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: Scott Brim <scott.brim@gmail.com>, IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a11459e8c2863a60554cfe607"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oQDu05GhbK6tUjaUeVjsr0Tpf10>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 08:46:22 -0000

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

FWIW, presbyopia doesn't make it difficult to read things that are
distant.  What does that is myopia.   I've had myopia since I was a kid.
There is just a limit to how much we can cram onto a slide, and it's
actually really difficult to know what that limit is when you are
_preparing_ the slides.

I suspect there is standards work to be done here.   E.g., is it the case
that the relative size of the screen when seen from the back of small rooms
is the same as from the back of large rooms?   If not, can we fix?   Can we
give people a suggestion as to what size fonts will be legible to a person
with corrected vision from the back of the room in the worst case?   I
think this would have to be part of the mtgvenue work.

I say this slightly tongue-in-cheek, but it's a real problem that I really
had to think about when preparing my slides.   I was not able to come up
with a definite answer.   I don't know how well I did, to be honest, but I
did increase the font size above the default, which seemed pretty
eye-chart-ish to me.

On Fri, Jul 21, 2017 at 10:22 AM, Spencer Dawkins at IETF <
spencerdawkins.ietf@gmail.com> wrote:

> Hi, Scott,
>
> On Jul 19, 2017 6:04 PM, "Scott Brim" <scott.brim@gmail.com> wrote:
>
> Can't you just sit in front?
>
>
> "Does not scale" ;-)
>
> I see that several of us are griping in this thread, which is what one
> would expect, given the nature of this mailing list.
>
> I'm not hearing people saying, "I never have problems, must be you", which
> I interpret as the visual equivalent of "if the music is too loud, you're
> too old".
>
> So, I'll probably bring this up on the working group chairs mailing list,
> for their discussion and possible action.
>
> Thanks, everyone, for your thoughts.
>
> Spencer
>
> Spencer
>

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

<div dir=3D"ltr">FWIW, presbyopia doesn&#39;t make it difficult to read thi=
ngs that are distant.=C2=A0 What does that is myopia. =C2=A0 I&#39;ve had m=
yopia since I was a kid. =C2=A0 There is just a limit to how much we can cr=
am onto a slide, and it&#39;s actually really difficult to know what that l=
imit is when you are _preparing_ the slides.<div><br></div><div>I suspect t=
here is standards work to be done here. =C2=A0 E.g., is it the case that th=
e relative size of the screen when seen from the back of small rooms is the=
 same as from the back of large rooms? =C2=A0 If not, can we fix? =C2=A0 Ca=
n we give people a suggestion as to what size fonts will be legible to a pe=
rson with corrected vision from the back of the room in the worst case? =C2=
=A0 I think this would have to be part of the mtgvenue work.</div><div><br>=
</div><div>I say this slightly tongue-in-cheek, but it&#39;s a real problem=
 that I really had to think about when preparing my slides. =C2=A0 I was no=
t able to come up with a definite answer. =C2=A0 I don&#39;t know how well =
I did, to be honest, but I did increase the font size above the default, wh=
ich seemed pretty eye-chart-ish to me.</div></div><div class=3D"gmail_extra=
"><br><div class=3D"gmail_quote">On Fri, Jul 21, 2017 at 10:22 AM, Spencer =
Dawkins at IETF <span dir=3D"ltr">&lt;<a href=3D"mailto:spencerdawkins.ietf=
@gmail.com" target=3D"_blank">spencerdawkins.ietf@gmail.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"><div dir=3D"auto"><div>Hi, Scott,<=
br><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Jul 19, 201=
7 6:04 PM, &quot;Scott Brim&quot; &lt;<a href=3D"mailto:scott.brim@gmail.co=
m" target=3D"_blank">scott.brim@gmail.com</a>&gt; wrote:<br type=3D"attribu=
tion"><blockquote class=3D"m_-4484669999429758106quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"auto">Can&=
#39;t you just sit in front?=C2=A0</div>
</blockquote></div><br></div></div><div class=3D"gmail_extra" dir=3D"auto">=
&quot;Does not scale&quot; ;-)</div><div class=3D"gmail_extra" dir=3D"auto"=
><br></div><div class=3D"gmail_extra" dir=3D"auto">I see that several of us=
 are griping in this thread, which is what one would expect, given the natu=
re of this mailing list.=C2=A0</div><div class=3D"gmail_extra" dir=3D"auto"=
><br></div><div class=3D"gmail_extra" dir=3D"auto">I&#39;m not hearing peop=
le saying, &quot;I never have problems, must be you&quot;, which I interpre=
t as the visual equivalent of &quot;if the music is too loud, you&#39;re to=
o old&quot;.</div><div class=3D"gmail_extra" dir=3D"auto"><br></div><div cl=
ass=3D"gmail_extra" dir=3D"auto">So, I&#39;ll probably bring this up on the=
 working group chairs mailing list, for their discussion and possible actio=
n.</div><div class=3D"gmail_extra" dir=3D"auto"><br></div><div class=3D"gma=
il_extra" dir=3D"auto">Thanks, everyone, for your thoughts.</div><div class=
=3D"gmail_extra" dir=3D"auto"><br></div><div class=3D"gmail_extra" dir=3D"a=
uto">Spencer</div><span class=3D"HOEnZb"><font color=3D"#888888"><div class=
=3D"gmail_extra" dir=3D"auto"><br></div><div class=3D"gmail_extra" dir=3D"a=
uto">Spencer</div></font></span></div>
</blockquote></div><br></div>

--001a11459e8c2863a60554cfe607--


From nobody Fri Jul 21 01:46:53 2017
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BCA2131CE6 for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 01:46:51 -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 eGcTmtD1IQCb for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 01:46:49 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96ACE131A7E for <ietf@ietf.org>; Fri, 21 Jul 2017 01:46:49 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [IPv6:2001:67c:370:1998:a11:96ff:fe01:81e0]) by relay.sandelman.ca (Postfix) with ESMTPS id 322571F8F6 for <ietf@ietf.org>; Fri, 21 Jul 2017 08:46:48 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 5E0D81626; Fri, 21 Jul 2017 10:46:38 +0200 (CEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
Subject: Re: More and more virtual interims
In-reply-to: <3773E2A5945F3A70DE47C0AB@PSB>
References: <876859E45DFE49F23C5AD313@PSB> <BA5AEE60-90FA-4668-8D6F-5906723AA6C9@gmail.com> <3773E2A5945F3A70DE47C0AB@PSB>
Comments: In-reply-to John C Klensin <john-ietf@jck.com> message dated "Wed, 19 Jul 2017 17:09:59 -0400."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 21 Jul 2017 10:46:38 +0200
Message-ID: <29692.1500626798@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iWS0d1IhXZuUE1vlTwNJs4p-TKE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 08:46:51 -0000

--=-=-=
Content-Type: text/plain


John C Klensin <john-ietf@jck.com> wrote:
    jk> (1) We have usually thought that the IETF is at its best when the
    jk> vast majority of participants are designers, implementers, and people
    jk> with primary product responsibility rather than, at the other
    jk> extreme, professional standardizers.  For at least some
    jk> organizations, having to commit regular blocks of time (or very long
    jk> blocks of time) to specific standards work will trigger the same
    jk> sorts of "are those people too valuable to do this or can we commit
    jk> fewer or less valuable people" reviews that are sometimes triggered
    jk> by meetings in resorts or other exotic and/or other places that are
    jk> perceived as exceptionally expensive or attractive to tourists.

    yn> Note that this is about virtual interim meetings, or as non-IETF
    yn> people call them - conference calls. Blocking out one or two hours
    yn> every two to three weeks is not that big a deal to employers. There is
    yn> no travel approval, no flight, no hotel, no several day absence, no
    yn> expense report. It's a phone call (or Webex or some kind of WebRTC
    yn> thing). This is nothing compared to a F2F meeting, where I'm gone for
    yn> 5 days and have probably spent a total of one more day on all the
    yn> stuff around that.

I was also surprised that John would connect use of conference calls with
a move towards "professional" (really really really large 'airquotes' from
me here) standards people.  (It surprised me greatly, but I generally try to
stay away from organizations where these so-called-professionals nest)

I think that we are now at a very happy mid-point where it is really easy
in a number of WGs where new people can join calls (and yes John, email lists)
in many cases, essentially without any permission from management.  I think
that leads to a much easier transition to when the person asks for actual
travel: they are more likely to be truly active contributors, with real
active drafts.

I think the critical thing is that virtual interims are well minuted to
emails, in a timely fashion, and that the technolog is accessible.

To the extent that webex has been used in the past as a cheap conference
call system (where many participants use the computer access, but until 2
months ago, that feature was available on only few platforms) it has been
okay.  Slides were distributed in advance and no assumption about screen
sharing was made.  Some groups have, however, overused this and excluded
people with non-legacy desktops or who have unmutable corporate firewall
policies.   I have cried foul over a few years, but it appears that webex's
webrtc system seems to be more fully deployed.  appear.in has worked well,
even sometimes through corporate firewalls.  JITSI(.tools.ietf.org) has
sadly, not be as resilient.

My request to the IESG is to clearly ask the IAOC to get a real SLA
on the use of a single consensus tool.  That we write a BCP about what
ports it uses, such that an IETF contributor can say, "Dear IT, please
enable RFCxxxx access for me"

    yn> FWIW, I also believe that, as we get better at interim meetings,
    yn> conference calls, etc., we should be able to consider cutting back
    yn> week-long f2f meetings to maybe two per year rather than three, with
    yn> the advantages again being the ones you cite.

I also have this goal.  I suggest however that we initially approach
this differently: that we consider that we could cut back the length of
the week (with fewer simultaenous tracks), because many groups will have had
a virtual interim in the 3-4 weeks prior to the meeting.

This also means changing the ID submission deadlines, perhaps making them
under control of WG chairs rather than global.

    jk> Your points about cross-fertilization and English stand, but a virtual
    jk> interim is a far cheaper way (for all participants and their
    jk> employers) to get a 1- or 2-hour slot for a WG meeting.

    yn> Agreed.  What I'm trying to push on a bit is the assumption that I
    yn> thought I heard during the plenary, i.e., that interim meetings, in
    yn> quantity, should be encouraged as a better way to do work than email
    yn> and occasional "everyone gets together" IETF plenaries.  It is, to me,
    yn> a matter of finding and keeping the right balance, rather than going
    yn> overboard on any one approach.

My experience is that the virtual interm meetings *reinforce* the use of
email, while our in-person meetings often do the opposite :-)

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [






--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJZcb9uAAoJEJVM4Vb9/EKQxswH/0bnn2NlCjFnCEX+9Rg/NaFx
NHftn/g4DMLcmbUmS75AiKbpjVukOd+re+rNH5FSpFbNUMPgMNforbfzQAhF5KlJ
vQZ4vyZSqhIGMpv+P03fePjfMvkDRKZQD+G1ZlHXzQTDlkLEgZTwd+/Y5va5qjBQ
bsQX/TR6RSOJOS7BdhdqoB6zFQe4yqdAHdoRYnSbkFz6+aMFBs0RJp35r+BE67vO
/SfpL/rSzPPA+ZvCLMFOvwDfAAvpAaGU5Ul1qXUseST6Qlthg0zC8KgfRr1qJdgY
tDIHXkXct19x2Zr3AxagITYU9UDSvpvx64pHKLIPAb2KLdFnpJ+Rcs6RBjCk3uY=
=9n9m
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Jul 21 02:00:27 2017
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD685129AAD for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 02:00:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 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_MED=-2.3, RP_MATCHES_RCVD=-0.001, 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=ecs.soton.ac.uk
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 ztpGtod91jDr for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 02:00:23 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80F05127869 for <ietf@ietf.org>; Fri, 21 Jul 2017 02:00:23 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6L8xUUn017682; Fri, 21 Jul 2017 09:59:35 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v6L8xUUn017682
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1500627590; bh=3EiyYJSQx8Vq5j52vw0Oui/CEkY=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=pyw5vsacXriM4Y86Og+LFGm+DIWLPYXFFWQZa6Lfqqu2AEg9SWqrB0m5H8d+u7ofO 3Snt5zeVyS6mUucz4LEs7J3et28POqt3y/jhbQdEWvw/VTxM/T6OiwlNq32k1hdjAY NCJIEE/xmbSxkIhdPOoqFUZYQ84mv9tDYVmrQoKg=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id y6K9xU1100702652Ow ret-id none; Fri, 21 Jul 2017 09:59:50 +0100
Received: from [IPv6:2001:67c:370:128:100a:c260:3dab:521a] ([IPv6:2001:67c:370:128:100a:c260:3dab:521a]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6L8xQdo032287 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 21 Jul 2017 09:59:26 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Slides, eye charts, and a beg for readability
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <CAPt1N1mOhZHCy=jJOrPyTz3-qy3KP0Mvrg+6Qj+Hpid4bq1-jw@mail.gmail.com>
Date: Fri, 21 Jul 2017 09:59:26 +0100
Cc: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, IETF discussion list <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|e9fcaf1e4e0ff5b5d21984c238f2caf0y6K9xU03tjc|ecs.soton.ac.uk|00A42324-8DD5-41B8-B2DB-BE4B8E8519DD@ecs.soton.ac.uk>
References: <CAKKJt-ehdzREsf3QzGZ+JFOkMm-dGpSdGVFBUJE4BhqWweY+Og@mail.gmail.com> <CAPv4CP8UGr_xLDYW=zKQUP6mXaWgQ67JM+-_NJOvCgfOhXU2hQ@mail.gmail.com> <CAKKJt-et1SW5J_dU-Bfj=yCKtvVv+sSqzYqh1Sur=NgzA-Mghg@mail.gmail.com> <CAPt1N1mOhZHCy=jJOrPyTz3-qy3KP0Mvrg+6Qj+Hpid4bq1-jw@mail.gmail.com> <00A42324-8DD5-41B8-B2DB-BE4B8E8519DD@ecs.soton.ac.uk>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3273)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=y6K9xU110070265200; tid=y6K9xU1100702652Ow; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v6L8xUUn017682
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YCvqwT81x5ZII8MO6gHnJ_g-Ur4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 09:00:26 -0000

> On 21 Jul 2017, at 09:45, Ted Lemon <mellon@fugue.com> wrote:
>=20
> FWIW, presbyopia doesn't make it difficult to read things that are =
distant.  What does that is myopia.   I've had myopia since I was a kid. =
  There is just a limit to how much we can cram onto a slide, and it's =
actually really difficult to know what that limit is when you are =
_preparing_ the slides.
>=20
> I suspect there is standards work to be done here.   E.g., is it the =
case that the relative size of the screen when seen from the back of =
small rooms is the same as from the back of large rooms?   If not, can =
we fix?   Can we give people a suggestion as to what size fonts will be =
legible to a person with corrected vision from the back of the room in =
the worst case?   I think this would have to be part of the mtgvenue =
work.
>=20
> I say this slightly tongue-in-cheek, but it's a real problem that I =
really had to think about when preparing my slides.   I was not able to =
come up with a definite answer.   I don't know how well I did, to be =
honest, but I did increase the font size above the default, which seemed =
pretty eye-chart-ish to me.

Perhaps we can pull together a page somewhere within the IETF online =
material giving guidance to authors, and perhaps examples of good decks, =
through people nominating them to be archived as such.  Then if we also =
get the in-roo projection systems right, we should head towards a better =
place.  I did notice the screen in Barcelona this week was =E2=80=9Cwavy=E2=
=80=9D so all the text was equally wavy; far from ideal.

I=E2=80=99ve seen quite a few good examples this week, one being =
Stuart=E2=80=99s deck for DNS-SD, though we only have the non-animated =
PDF version online
=
https://www.ietf.org/proceedings/99/slides/slides-99-dnssd-dns-sd-update-a=
nd-new-work-items-00.pdf

There is also the question of accessibility of decks and other meeting =
materials content. Animations such as the above probably aren=E2=80=99t =
so good there.

Tim

> On Fri, Jul 21, 2017 at 10:22 AM, Spencer Dawkins at IETF =
<spencerdawkins.ietf@gmail.com> wrote:
> Hi, Scott,
>=20
> On Jul 19, 2017 6:04 PM, "Scott Brim" <scott.brim@gmail.com> wrote:
> Can't you just sit in front?=20
>=20
> "Does not scale" ;-)
>=20
> I see that several of us are griping in this thread, which is what one =
would expect, given the nature of this mailing list.=20
>=20
> I'm not hearing people saying, "I never have problems, must be you", =
which I interpret as the visual equivalent of "if the music is too loud, =
you're too old".
>=20
> So, I'll probably bring this up on the working group chairs mailing =
list, for their discussion and possible action.
>=20
> Thanks, everyone, for your thoughts.
>=20
> Spencer
>=20
> Spencer
>=20


From nobody Fri Jul 21 02:27:02 2017
Return-Path: <alejandroacostaalamo@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01A3F13147E for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 02:27:00 -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 sWpVGMLtD-MN for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 02:26:54 -0700 (PDT)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (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 72745131C19 for <ietf@ietf.org>; Fri, 21 Jul 2017 02:26:49 -0700 (PDT)
Received: by mail-wm0-x233.google.com with SMTP id e131so8871065wme.0 for <ietf@ietf.org>; Fri, 21 Jul 2017 02:26:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=cs1jzsdxGt5Q795EPZULikbwwdQK0d7BcZ5xvx8QlaY=; b=jZzOM+1VfXbSJHPSQOjUQk2v5ty+K+YNGEbFAwtzL5eMlUg8iKdxD1akSKlO3GYgHf DFxQVIpNIFFAbwMU1h27YG4vCAuOVppauYItZkuHm01EfEo/ElxMPQC/+Hm7XleH7iyv ZR8Ggq1YPfhZYuSXNuPR743mBML6I4GRVbyuDUk1g6lLVOctcEG0TRw7QDERUZFY+hav aoT79M1z9GM8yytMKtisV+wihigw6gVLiLPxJ5dfgrcXiQmg16qEzQ/M3UlJJ2ivcDRm mUalsmKI17m+OT6dHSN9UwBMgaYK90ZDgChWTfFGz6Rn1l6nIBSP1ecnQuEYbM52BAS0 IFZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=cs1jzsdxGt5Q795EPZULikbwwdQK0d7BcZ5xvx8QlaY=; b=VtTHcpySAJOojVW+3MSYlLJBVa+lWLqdDUcUL3icbbMhWF7Uw7IvPGXDgnn2SeRtuL fHRKOEvdOVKCC340xCg5v1PdObI6fujQpa+OgZmr4oDz4cUstpafMz6OWBvnZVyOHIFd eKRpYdo4ZMh3CH0KwRHJQjQIS9L5RHytGRJQI/iVoJmc+8gTZxZOjAhwZmh7Kmd9iLJW yvqJHnr1qWoGSSj3BfQv2YJDTY/GjV0Lri82X4uC6LdAxuLWYdjIafXJNX5abfc7vR2C MrvWBcX+4vvlxlWuTgLFQEAX6BM8/huO0Nyy9437T8u9imWJ0nk2chgaDPgjZIED4wCU JLyg==
X-Gm-Message-State: AIVw110rfKZwXAij2oPxtO/7YL1blg/dd6nty+nYeyXiIfGVoZVJdf58 E+4qrROZyB+AYIxJ+x8=
X-Received: by 10.28.146.209 with SMTP id u200mr4609764wmd.38.1500629207795; Fri, 21 Jul 2017 02:26:47 -0700 (PDT)
Received: from ?IPv6:2a00:23c4:a70c:d600:55d7:75df:5130:c124? ([2a00:23c4:a70c:d600:55d7:75df:5130:c124]) by smtp.gmail.com with ESMTPSA id 66sm801109wmj.29.2017.07.21.02.26.46 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Jul 2017 02:26:47 -0700 (PDT)
Subject: Re: beta web site critiques
To: ietf@ietf.org
References: <20170720125927.lbmtvwo3dncmoxmb@mx4.yitter.info> <30D585774FDAF7F5158A6A26@PSB> <4B7A0FD7-9088-4687-9C3A-F137E4873CE8@orthanc.ca> <4AAD6806-5952-4D62-9B27-879E4446CE19@orthanc.ca>
From: Alejandro Acosta <alejandroacostaalamo@gmail.com>
Message-ID: <ba387eb9-091e-0b4c-49d4-28b196fbf901@gmail.com>
Date: Fri, 21 Jul 2017 10:26:45 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <4AAD6806-5952-4D62-9B27-879E4446CE19@orthanc.ca>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Content-Language: es-ES
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gbkW8EjUUAuo4aV51eauyi9uTQI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 09:27:00 -0000

Haha, excellent.


El 21/7/17 a las 5:55 a.m., Lyndon Nerenberg escribió:
>> And if there is a link to the datatracker, or anything else of use, I sure can't find it on that page.
> To invoke a wee bit of 3rd-party humour to make my point:
>
>   https://www.xkcd.com/773/
>
> --lyndon
>


From nobody Fri Jul 21 02:47:10 2017
Return-Path: <amorris@amsl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7C5712EB2B; Fri, 21 Jul 2017 02:47:08 -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, RP_MATCHES_RCVD=-0.001, 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 Ym_Bg1RquAQa; Fri, 21 Jul 2017 02:47:07 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D25E3129B40; Fri, 21 Jul 2017 02:47:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id B3E9F1CA6D9; Fri, 21 Jul 2017 02:46:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id guwYglj8gw5W; Fri, 21 Jul 2017 02:46:56 -0700 (PDT)
Received: from [IPv6:2001:67c:370:128:34f9:a24:2ec1:90c6] (unknown [IPv6:2001:67c:370:128:34f9:a24:2ec1:90c6]) by c8a.amsl.com (Postfix) with ESMTPSA id 2905B1CA6D8; Fri, 21 Jul 2017 02:46:56 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: IETF 100 Registration Opening Delayed Until Wednesday, 26 July at 07:00 PDT (14:00 UTC)
From: Alexa Morris <amorris@amsl.com>
In-Reply-To: <150062920623.10991.15657052844940226623.idtracker@ietfa.amsl.com>
Date: Fri, 21 Jul 2017 11:47:05 +0200
Cc: IETF Announcement List <ietf-announce@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <86B85671-4152-47DE-A551-F029B58BC546@amsl.com>
References: <150062920623.10991.15657052844940226623.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LLHsUL4KmqtXr5aJQRwUYvx0HGc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 09:47:09 -0000

The time and date link was incorrect in the message below. Correct link =
is: https://timeanddate.com/s/3ax6.

Alexa

> On Jul 21, 2017, at 11:26 AM, IETF Secretariat =
<ietf-secretariat@ietf.org> wrote:
>=20
> Registration for IETF 100 in Singapore has been postponed until =
Wednesday of next week due to issues with the main venue hotel =
reservation system that are beyond our control.=20
>=20
> New date: Wednesday, 26 July=20
> New time: 07:00 PDT (14:00 UTC)
>=20
> Worldwide times at https://timeanddate.com/s/37rk. An announcement =
opening registration and hotel reservations will be made at 07:00 PDT on =
26 July.
>=20
> Letters of Invitation may be requested during registration.
>=20
> - IETF Secretariat
>=20


From nobody Fri Jul 21 02:59:12 2017
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBA48129AA0 for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 02:59:10 -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, RP_MATCHES_RCVD=-0.001, 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=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 E2-u8dkRYdx6 for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 02:59:09 -0700 (PDT)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 64396127869 for <ietf@ietf.org>; Fri, 21 Jul 2017 02:59:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1500631148; d=isode.com; s=june2016; i=@isode.com; bh=q7cSn1bGT/LooF++KulkC9Uc3CL8weCuQCDODR3Spw4=; 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=g7929R9z/vve2H8zx5eF/cBwy95Tm4I7GnstoEqhPI6BKxxoT2tfY8oZlmcudYbdx4wIua +iGhwoaZsVnMHu/eWlRIfTPKaL89wEAdp/L5PYUrmD7Ol49Lg44gDgmHIYyl1dLw5BPhSQ zjDFAYwm2MRtma/PsZj1hQsYQVBe588=;
Received: from [31.133.129.198] (dhcp-81c6.meeting.ietf.org [31.133.129.198])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <WXHQawBf=ouv@statler.isode.com>; Fri, 21 Jul 2017 10:59:08 +0100
Subject: Re: [Json] draft-ietf-jsonbis-rfc7159bis-03: recommendation to use UTF-8
To: Barry Leiba <barryleiba@computer.org>, Pete Resnick <presnick@qti.qualcomm.com>
References: <596CE6E3.3070808@isode.com> <92698d15-6557-8bb1-aad0-a0965e779e71@gmx.de> <668A56FD-4B89-472C-9E4C-BE5C0E6921F9@isode.com> <6a42a587-f09c-14bc-847b-7882c8f3e9f7@gmx.de> <CAC4RtVC0fBbw-YiifN5p-gPLxHYRB0jkSumankTTcY+KbyTasw@mail.gmail.com> <28D32024-5E4C-44C7-A54A-049BA97289CE@qti.qualcomm.com> <CAC4RtVB2dYSJXiozoR6=Zds73bEbiGpDsj_W+mbpJhqQNU5S5g@mail.gmail.com>
Cc: Julian Reschke <julian.reschke@gmx.de>, "ietf@ietf.org" <ietf@ietf.org>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <5971D06E.5060701@isode.com>
Date: Fri, 21 Jul 2017 10:59:10 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <CAC4RtVB2dYSJXiozoR6=Zds73bEbiGpDsj_W+mbpJhqQNU5S5g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EH_6TW2bOROax1a6MBo0MxQJQcY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 09:59:11 -0000

Just to close the loop on this: the new version of the draft that
includes all RFC Editor notes was posted.

I will let this be reviewed in the WG for a couple of days and I will
reissue the approval announcement for -04.

I am also keeping track of further clarifications and these can be done
in AUTH48. I will make sure the WG is aware of any changes.

On 18/07/2017 12:27, Barry Leiba wrote:
> I hadn't thought of it as an appeal, but I do think the current
> document state should be "Approved, Announcement to be Sent" with a
> substate of "Revised I-D Needed".  If an appeal is what's needed to
> change that, then... yeah, sure.
>=20
> Barry
>=20
> On Tue, Jul 18, 2017 at 1:18 PM, Pete Resnick <presnick@qti.qualcomm.com> =
wrote:
>> Alexey,
>>
>> I believe Julian and Barry's notes constitute an appeal of the Protocol
>> Action, and I think they're probably right. Please rescind it, publish th=
e
>> new draft, and give people a bit to review. No need for another formal LC=
,
>> but doing this in a note to the RFC Editor isn't kosher.
>>
>> pr
>>
>>
>> On 18 Jul 2017, at 13:04, Barry Leiba wrote:
>>
>>> I have to agree with Julian here: this is not a change that's
>>> appropriate to do in an RFC Editor note.  The change is probably fine,
>>> but draft revisions are cheap and it's easy enough to post a revised
>>> I-D to make sure we can all see the final version in context.
>>>
>>> Thanks,
>>> Barry
>>>
>>>
>>> On Tue, Jul 18, 2017 at 10:19 AM, Julian Reschke <julian.reschke@gmx.de>
>>> wrote:
>>>>
>>>> On 2017-07-18 10:05, Alexey Melnikov wrote:
>>>>>
>>>>>
>>>>> Hi Julian,
>>>>>
>>>>>> On 18 Jul 2017, at 08:52, Julian Reschke <julian.reschke@gmx.de> wrot=
e:
>>>>>>
>>>>>>> On 2017-07-17 18:33, Alexey Melnikov wrote:
>>>>>>> Hi,
>>>>>>> The JSONBIS WG decided to update recommendation on Unicode encoding =
to
>>>>>>> be UTF-8. (For details see the RFC Editor's notes in the approval
>>>>>>> message that will be sent out shortly.) This took a bit of time to
>>>>>>> debate in the WG, so the document approval took a bit longer than
>>>>>>> originally expected.
>>>>>>> Best Regards,
>>>>>>> Alexey, as the responsible AD
>>>>>>
>>>>>>
>>>>>>
>>>>>> The last WG mail related to this topic is over 2 months old, and I
>>>>>> don't
>>>>>> see any declaration of consensus.
>>>>>>
>>>>>> It would be good if the chair would send a summary about what's going
>>>>>> on
>>>>>> to the WG mailing list before anything gets finalized.
>>>>>>
>>>>>> (I note that
>>>>>> <https://datatracker.ietf.org/doc/draft-ietf-jsonbis-rfc7159bis/> has
>>>>>> been
>>>>>> saying "Revised ID Needed" for 48 days, and I was under the assumptio=
n
>>>>>> that
>>>>>> there'd be indeed a revised ID).
>>>>>
>>>>>
>>>>>
>>>>> I just posted a message on this: this is approved with updated RFC
>>>>> Editor
>>>>> notes. See the approval message once it is sent.
>>>>> ...
>>>>
>>>>
>>>>
>>>> This is not how it's supposed to work. Please have a new I-D posted and
>>>> get
>>>> people to review the changes in context. This is a *very* important pie=
ce
>>>> of
>>>> standards work - we need to make sure it meets quality standards.
>>>>
>>>> From a quick glance at
>>>>
>>>> <https://datatracker.ietf.org/doc/draft-ietf-jsonbis-rfc7159bis/writeup=
/>, I
>>>> already note that the appendix "Changes from RFC 7159" is now incomplet=
e.
>>>>
>>>> Best regards, Julian
>>>>
>>>> _______________________________________________
>>>> json mailing list
>>>> json@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/json
>>
>>
>> _______________________________________________
>> json mailing list
>> json@ietf.org
>> https://www.ietf.org/mailman/listinfo/json


From nobody Fri Jul 21 03:46:42 2017
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64AFF129B3A for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 03:46:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 Dd1HT-6E_JnV for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 03:46:36 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-he1eur01on0135.outbound.protection.outlook.com [104.47.0.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63E47127337 for <ietf@ietf.org>; Fri, 21 Jul 2017 03:46:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=L34u/QmyVOiC423ufraenOtP4BL7X3+EWs6zI2D+TKs=; b=hHpzLMR1j9r1UGYMPJG0UqqITAbGq7NHBH5chIZWzkSmNHkg7IjvreV7m6KJLtrqcNWoGN0j8187mlJlgeVyPfvu8/kz7n2/JqiQczR2sKwUu6Vg8XhYa98wrlh+geMBYElSlpYNDGF49Js8JQ71LuvclpT1lu7zpBg7q0cwd3M=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=daedulus@btconnect.com; 
Received: from pc6 (86.149.101.4) by HE1PR07MB1563.eurprd07.prod.outlook.com (2a01:111:e400:7a2d::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1282.4; Fri, 21 Jul 2017 10:46:33 +0000
Message-ID: <056701d3020e$08b73b20$4001a8c0@gateway.2wire.net>
From: "tom p." <daedulus@btconnect.com>
To: <ietf@ietf.org>, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
References: <25188.1500378842@dooku.sandelman.ca> <3d294725-7d22-ef24-7c57-120d9418acc7@gmail.com>
Subject: Re: the terms "priority" and "precedence"
Date: Fri, 21 Jul 2017 11:10:44 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [86.149.101.4]
X-ClientProxiedBy: VI1PR09CA0054.eurprd09.prod.outlook.com (2603:10a6:802:28::22) To HE1PR07MB1563.eurprd07.prod.outlook.com (2a01:111:e400:7a2d::13)
X-MS-Office365-Filtering-Correlation-Id: 1920a16e-b263-44a4-b26f-08d4d025c12d
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(300000503095)(300135400095)(201703131423075)(201703031133081)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:HE1PR07MB1563; 
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1563; 3:2oKXUp9chCODtg0vrWAsMT+ZXTkX95urVXKG8INhvME5GDJCY9Ge1cr0HgmlmQOZFEw0+uL34V82nQAiclqg2tbxYpD7qDKfd5djgc4bPgZyi8NU2iyiRBf5b6BMAcY3Ffe16jFJXUcJ5EVSHacBKhp8yjuPPZm0D0Wy0EprBUaEV97chj5m6/zjWup2OYB1yJGnKCuNNUwsiO/SiVK/Z7aw0saEMG/VRP8fNLOXvMU8vKcd4AgP4F60GTEZ7LYg68hIWs6Skh+JOSlrhrx/gkI4xKi/HaWF6Ifx3edsTfmOynEJjj/yatHdEp7P77kKZisz+SdJA/pDr1zAn6kWg+/8o+WIZ5LTyOOc+B3JtJnqGp5KOofd1axqYfEYN4Ghhb0RybxX+0ri3Q3z2aepSgBnUhMuoTZZYFA1MUbPOEc/IQNPvbhpN4JAUtnbAdfIuVH3LHRcJCJBvBwfmTRIIjECXy7cYVaEH/mWdHjvhIJ5uINvdqQpdfFfnrEvjRwYLLMjmPqeIcgOsqqJQwQQhQDECJ2VVwUcJUSABvPTYz7dcELmzwUik/1ScPPxWrxHhlC68KvrtWCNy4EtcPLvTkeKlCmBqKu2fUN0RdtX6fGkEkxww3JZvZu7jjh5PobHhYahFhD+8P7rTtv2wAQevEgca2nNpjO5UXCxixODtrYxMi4sIdjD9T/JRAyZmFqzd91+gAG5r//RHUolhlBIFNB/jlYAPyc90+AO/XrnuVc=
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: HE1PR07MB1563:
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1563; 25:MSdUCtfL5inHqzoiPAvKFm2xM41fI9q9dciM3rP8BtYKwMj0U95ea5kEymJy/Foai4AkSmAfSJ/S6zuqqkyf2vpstrunA3DIpnLirlngGOFYTrhswpEKx0sMtfIUBQeUcelibO7CGtFadKj+ADlmn1aKqH/wDlfYLvBtwwARFtZMH+LGujMXpvquZ6qzCdnFkB8pf0nuk3NdDeLDc9oUWNGVg7btHXkEPih5eVa5FNDy2py/yaWaAS2f2d6T7iscJbdJoPbFrEeJQ1U6DAtEo1KD15+c8nPCutbuiI7K4ecFa9G3Gp+FOIHfzb9uqbJt13WonJNLCGxthS4NmjoOdiBXXMNb+cLi0GUHCeYMJsZzMgziFYdEJ2qD3/us+xS6tAPXhGom6yaT4LZh6dMuGSxu90ZWVUmCViX5u4AtJdQM1HK1ecItBPP3TPMHJOPnM6PFUYxm82VS6Ci3Bd5m9IivxQsevvSB+3GrWgNCm/1CLYo6DSKU0rZK1G1rVi5clzZWqqK+S4mhCNGsy8BsxBHQQmfd+CAaEPCQvS/3Rptg3qBxWby0uTp/5eY/s5nHKyzVnM+WsvtK8YZQ371CaU7z80JrsRWErfWAqRkabladxENBloBg0tioI51Mi43VIuyhiKGUbjGBR7YFuAAad+kuTqv71E0Ie05mBISibokMqCyhUKnVerejBY2QJDHuIIizf27a+Ycw1X0FED1eU/5OV3YTedn+aZmYStJ6JXz4/rZbsSBluIBAeGr0FaSP/OVzWHimmZog6I/k6Rhdj2gGa5d0FJZrvl6VBjVjJ9qJJCiFiX3VDQs/Nsm847A7FF4p1sP2otCaseC3xe1YH1+Xy/zTC4WSlKND1atEQpokENgsk/HzbyVb/FLMx8mQ/7x8bB7X0Eq7JdSQKb8CmYM4K98z69E9EWszJJNU4Rg=
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1563; 31:oAGFf0XkQilzoJxNRNDNUo/0mkvZxBIwiEA4Hfw3l2tQRJcyBpVPc/dLQVjWmUsFrAUzhk45shi8sJnkHezJdjupxOxXXLe60vr+osfzuHRUQf3WWnTzlKXEcRL8P9mmaj6IKQXdBnWxJXZEh+iOFo+p1yfJeTx/cifUxuq1qYhINXX+Hivy9S8Rw5+sM3lAkjidG7MkMWmywpoh4Nne+oIVslbHUhU8oCewQcPEzI8jO/O3R32yEfLkETdXiIn5k0YLXh33PHwXUQ4AABgyXZ8TcVTumfO7vwic7VywKccpxyWAnf4r/GmskLpAFQBae/E4ODCUnlT8ZoYyyLlbPswpUvw5DNvmQzXsgqK6uYFBL9uHMMKII6X7ZEL9AE6LlUTiIWxgjNz3jBp5XLUOS5NLpPFGj873GcEzXI2ayoT2zbLhP87Y+SeVLEXPEiybiyuJB+RULZZTLOHSgIWY+gjMLWQGBvKljvvLPNQbeiQXrd/bFtGRccV6oWdY9x1tgAnF3uZsC1nIbvmbhOCkwmVea2QsgJJdTwGiFStEu58OaaCkt0X/xNeBdmIRACezSGkRjTWbE+7T3PouMzNv68GKO9VAsS7cPhqLszhiIsu8yRXdR/sd2cgCoAgtJd+VZbh4LZTUmaP5w4Z8TvjeL+27nvNtaR6qjxi5t/cT5PBpxCxVJS5ltXrzFe+hd+5BiyBCkki8tFaimG/WtyQbXQ==
X-Exchange-Antispam-Report-Test: UriScan:;
X-Microsoft-Antispam-PRVS: <HE1PR07MB1563FF06F4B47E570730327AC6A40@HE1PR07MB1563.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(5005006)(8121501046)(3002001)(93006095)(93001095)(100000703101)(100105400095)(10201501046)(6041248)(20161123555025)(20161123562025)(20161123558100)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123560025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:HE1PR07MB1563; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:HE1PR07MB1563; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtIRTFQUjA3TUIxNTYzOzQ6RmN4Wk5xOEFlYWhQVDFUZ3hnVUhydU5KcXVu?= =?utf-8?B?bllnSjRJVlljTkROWG9KdEdPMnBhL1FkbWhpa1FnRmorbG5GWlhmeGZEalBz?= =?utf-8?B?Z2VLUU5tUmFCRXhtVzhTWTV0djJncnJnK0xhZHNaRmJPNnZZNi9Lczd1b1JU?= =?utf-8?B?NStaakZCbWxlT25sbTJGUDFsdnZ0RTRESVZEYjZndlBVeEFrOHlUU0hzY0V4?= =?utf-8?B?cUhva05qdzZ1ZkhXK1ZTTGJzM2FmQVAzYjZ2dkpaZmFxUVpNVng2Sm1ZdzBC?= =?utf-8?B?R0lGbU9lV0UzSk1Ib2Zoa0xxQy9rYVlPdkNtVEp6aWV3b3dOQ2k0RlgvdGxZ?= =?utf-8?B?RU1jd0NZdWxwek1WR0ZtZExsNU9Xd1JuSHM4RHpva0VTZElCNFl5OTZwU0hL?= =?utf-8?B?ME9Fck1mR0xkQ3RETVQvSXM5Q0xTaTVPU0psdlNvYXNRUkFwTG5nYk1XQXVF?= =?utf-8?B?RzlmeFlVQ09MVGs1YStpa1ZaOGIyeXhLQzFITmpRZ2VzMUxiM096MWFHNm1Z?= =?utf-8?B?R2xxcUptaDYyUjZYUHhkNFVZTTFHaTgyZ01OeEowSitNcXlqbEVwcU80VzlM?= =?utf-8?B?OUFBUzBnekI2dVJyMnhIaFF0ODNlVVgrV3ZYaC9Ha0Z1blZxSWdvRzFZZGRj?= =?utf-8?B?MWJNaCsyczI3ZEdNeTljd2trZmdPVVJSd1I0YmtIVU5ZUytYQWlSakFVRzkw?= =?utf-8?B?Vkxma2QxN1pJaXhYOVhLbzJuTUR3dGJSbDk0TnkxTEQ4MXh5WmNuUDlFRHRx?= =?utf-8?B?aitCYjRuTFhwekpQa0xwSVUxdjNwdUdEYUF1Z2w4T1l6L2lLYkczalBjeTV6?= =?utf-8?B?YnJVcnlDY01sdmMxd2lpOG9UcjJodjdZc2JaRVhTUXhuTGh1Nm9rRndLZ29Y?= =?utf-8?B?ZzhwYmV0U3laVEJDSUhwcmYxN2FzdGgwMjMxTHU5dXdiOCtxSW1Nb05nSFdy?= =?utf-8?B?M0FsRmxoVVVLSUpsUzVCNFc5U09kMXA3eHJQbGxpSyt3Skh1QVJpU1NkNFJ1?= =?utf-8?B?UWVwTkJpY090ZjF2Ni9Wa2szYmNCRXVIdW01UjNHTVJEOVBaZWwvNUxjS0JR?= =?utf-8?B?Vzd1UGcrMEI4cGNkTmNBZXpielpkbnlxWTg4S1VKTnU1SEFLTGZ5azRrS1ky?= =?utf-8?B?NUhwSzIyYnJRa1ZUeU15QXlFYzd0dmhVTXpuZFNzU29Za2s1NWtwR3BOYnBz?= =?utf-8?B?c09YdEFUeStiQVY0WkpnVjJyYTRlak9XcE82OGlSZmhsYVJzQVhpOWpnY3V3?= =?utf-8?B?VlR6K1A2dTRmazI1VlRsNk5DUkk0UklRMmNNc1BFT1lrbmliTm9tbEFEcW5u?= =?utf-8?B?U1U5NWd0K0ErVVBxL1Z0bWtWZytnaEJXZWJ2cFR4a05GeHFUOGFJcUJHaktk?= =?utf-8?B?WXYxaWptMGRGeHBqWXluODI0eEdVbUVZRi9iQ2JIdzhRaEtRU2RGZG5KQnJ2?= =?utf-8?B?bEp4c2NmNEk5MkpuL3RjSThBdGZBMHFKYllPMkx2dUtYaU1yQlRnWkNxaEVZ?= =?utf-8?Q?K8MzbHooi91ctYnb8SdqLiZ6B3fyE0u4sLjDkIvagfJLj?=
X-Forefront-PRVS: 0375972289
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(7370300001)(6009001)(39450400003)(39840400002)(39850400002)(39860400002)(39400400002)(39410400002)(13464003)(24454002)(199003)(377454003)(189002)(50466002)(68736007)(2906002)(97736004)(81156014)(84392002)(189998001)(44736005)(6486002)(23676002)(81166006)(7350300001)(8676002)(6306002)(53936002)(9686003)(86362001)(50986999)(38730400002)(229853002)(6246003)(4720700003)(6496005)(6666003)(53546010)(5660300001)(81816999)(7736002)(3846002)(76176999)(81686999)(305945005)(25786009)(116806002)(1456003)(50226002)(478600001)(230700001)(42186005)(5820100001)(966005)(6116002)(1556002)(47776003)(33646002)(62236002)(44716002)(106356001)(101416001)(105586002)(61296003)(66066001)(14496001)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR07MB1563; H:pc6; FPR:; SPF:None; PTR:InfoNoRecords; A:0; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtIRTFQUjA3TUIxNTYzOzIzOmJCendvV3lHMDYvQTdIK2R3TmFDN2twT05m?= =?utf-8?B?L1hXN0V0N0M2MGxjQkFuVFNVemZjNVVqSUkzZ3ZmRjZWVDBaRE85Z0c4cmIr?= =?utf-8?B?V3FkRUxqbDY0SVVrS0RSa3hhTUF5YnNOdDgzZlhXTzZEZmwyWlcxaFdiUjg0?= =?utf-8?B?WEhKRERzZnZQdkhma0VBaDM0R2E0cjYxdUZ6SGFPMmJlOFlubXFXNjdObEl0?= =?utf-8?B?T2ExcTdPT0FSdWpUVXVjbzlDVjgrWUNXQXh3SWROTmdOeDdpS1VmZEx1a2F6?= =?utf-8?B?cWpZZWdRa01aNVFCZmhidEh6UE5UL29WeGV0OXVpdXdXOXBNMjZ1Y0I4a2hC?= =?utf-8?B?SHR2S0xDK3p1bFYybVVwOEhKZU5pcE1rN2VKR0JWZVZLNVRaSDBGdDl5VHhJ?= =?utf-8?B?Rk5mTFpsWk9jQ3pvS1c4L0lqK3c1VG5tUkM3VlByMlhEQm52THIwa0twcWVx?= =?utf-8?B?ajRJaWRWb0VscmxidzV0Kzd1YUhzZXlybStUMi9tc2NGQllpQ1VmME9keStK?= =?utf-8?B?QTc1YWdvZWZEbEYvcVJ3b0w2MGYvYnlldmVJcmZZMGswMFdTVWpZaWpSZlYw?= =?utf-8?B?OG9MN2d2OHgwdisyMWxIeE1IQWYxRDRLQnUxMkJUMzhJeGVkWVhRdXBEdG8v?= =?utf-8?B?NWJGTVlsVFZyS3NZeVphSFU5VzBHRmE4bUI0KzlEWWR1a21HWW5ZdVZoZlBS?= =?utf-8?B?WHBiTkRMV1dNK2tCc1dQa2E2R1UyY1RqaWZORHVPazBORU4wUlY0OFNQRmsr?= =?utf-8?B?aFYwU3ZpeHFDcE9CTFZXaXc0c0w5TTd2cDhkbjAwdCtrVkwwNEI4Y2NMTkxx?= =?utf-8?B?bndxUHBHNzNwTjQxUmxtckhvNmM1UjNMVHNpVHdWMy9vTHdYTXFlYWt0c2or?= =?utf-8?B?VnV0cG5MTDF1dWEyVnovYVI5OThQaTF2Q2NiVnI5c3hzTlRCQkY2dkppRHNr?= =?utf-8?B?cU1oN1o1b3FVeXBqN3pQYVZsYi8xazBmWHd1VlY5blpyYXNEcVVNZWhYcEtF?= =?utf-8?B?cnMxMmVYTW4xVnc1OHVFSlBlK1FoaE9aRTNsOUN0UjdYYUNldVJxTDhBVEV1?= =?utf-8?B?RnR3Y3ZvaVpiOGVZL1RBWGNIQzZlaTNWZTVPR1YzYlJualcrNHZmWXZLL0dn?= =?utf-8?B?QkRtRERuSzQ2UXVubnArdmdMT3FNMmdDQjFzTkJjd0o1aURGb1k2YWlIOS80?= =?utf-8?B?TkdRaUdkbXJnNzU2b0wxeXV4ZXJPWFo2Y0tPdEx1SVpETTcwTUZKcFhDSStM?= =?utf-8?B?TzMxYlRRRGJvLzMxdUNLcndxckdMdnhkQ0FMTkhjM2x3MWxLRzR3SlhZY3hN?= =?utf-8?B?N2QrSkpOSVg0MzMwRHZkNVhNVDBuVWFHMDA1MHpRU2VvcWx5dzhlaDZzQWVr?= =?utf-8?B?SUoybUxlMEZJd0ozSXVFQXZtRVVPb01YTzlEYTZRYk1SK1RBWGRkNW9MUzdp?= =?utf-8?B?cmdTUEZoQ28ra1gwWkZKb3UrL3NJOFlhQUx5RitGZ1ErLy9TUU5vS2t4OWR0?= =?utf-8?B?cXRFUHYvQ09FYlRLcWt0TW9IYUQ4MnBLSkhBS3V6SVBZdGYraWJGdHNDOXJP?= =?utf-8?B?d1I2Z2s0VE9hSFZMVC9oUFREaWJkdll6Zjh0cXNYdVk3T1YzRUwxdktqMUt3?= =?utf-8?B?T2FSbEI1S1dvRmMzYnRSVUZhMjFTcEVIb29pYjJRaXQ3ZnlXYWdibDkyQWVJ?= =?utf-8?B?aGovYjRmN3liRHpkbWprTW9PQThlSUw5NWZmaTJOTU4vd2x1Q3VFMEZyMVkx?= =?utf-8?B?TnB5aWM4dzlickppR3FiNzRqa2ZmN0lKZ0wrQzFyUlJDb3BSYldaeFFJSDdR?= =?utf-8?B?aXMyVWpTcmtCRHJtaFV5QnZoMStJa0ZGVDJnazJ6QXZMZW45N1A1VU9ibVNS?= =?utf-8?B?bDE4dDBlakg1dk56N3VqTU9WMWptRVpxRTJzM0VuUk9TOXhvN0UwVVRaVXRq?= =?utf-8?B?WHlGRVViVlllOHV1NmlVRlgxVHpKMFUrRW1qOUtvajV5cjJpSlIwVWhudk1L?= =?utf-8?B?RTNJL2YxS0xUUkQ2SEtNOFNTUkkxVjBiaG14VWZ1bUlSenFWOWNEd0lpaXc3?= =?utf-8?B?SUJyVGY3Ly9yU2JvWTJ5K1NjV3hEbGdTMklTeUI1dXRqUHU0MEtTQkE2dE9p?= =?utf-8?B?NjFFTngvbDdKOGJLV2Vxc3Y3eXlpY3ZxY0RicjJOeGdDVmQ4clFzR0orc2Vx?= =?utf-8?Q?XWpkF/+I5KTvVkAinP2Y8EySE2rIJ6kW0ntXqpWEs0=3D?=
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtIRTFQUjA3TUIxNTYzOzY6emdzM0l6RTgvZlZjZHlvZm9WNHBxMlp3MEdP?= =?utf-8?B?MUFyQWdURFlTOG53c3A3RmtLWnZxUlJFcUhuaE9YMHFVMFprWk10RUdyUkVh?= =?utf-8?B?cmYwWjduY2tpVVNuQ2NMVEJUek1BVzJnNE9nVDJJQTdyQVIwVnlTNHczOCtj?= =?utf-8?B?ZGNFa2tKWW5idGhYd3FvMnlYSFFhRVh2ZHJlRXBiM0Uva2sxMkYrMzEybGNK?= =?utf-8?B?U0FKd2k4WjlQWnY4V213czBXSUFqQVpqMFZVVDZWWHlkaGRUemtzZ2VHeHdR?= =?utf-8?B?UVN5ZkdiVzczbzhwdEJUNDc5bnZQZU45MTcwWlR6czhUUjArRjB3SzB1Ti9K?= =?utf-8?B?UUdTYS96OFl4cVZCemptQXljS0lBT2FRMXlJVndqTXQxdmlEckF1b1lNYWdV?= =?utf-8?B?bVNoNi9EYkJpeWtKK29HTU1HNG1BWnBRRWUwSmlsR3BGRVFEYlQxTlYrejRS?= =?utf-8?B?N2lzN3dWeHNFV1V2am5OQWp2aWtRQ3Urc2dPZEZaV3BCTXEwcEZra2V2WjNH?= =?utf-8?B?REtkdThFWDRyR3Zhc1R0VW9nd3dBTmNKL003SE1QZk5tTlE5VFcvc05Bb2lk?= =?utf-8?B?NGxSOExyWllPd01jRzVUMS85Uy9Gb3VtVjNPOVVDc2JvTEpKWGNVbDFhTk1Z?= =?utf-8?B?bEVaam5Ta2hIOHRMakhicE9GTE1CQXYzdXFNZkhwcmRZSU9QK1AzNDBMaS9s?= =?utf-8?B?MHdQU1RMZkFna2VHMGh3SzRxcU1TK05sdkhUdWlCdC9VVFRvcU91RXBsdTFM?= =?utf-8?B?czBudHNXeGtOMUxnVmFhWDNIOUR0ZnNFcFdpVjd2SVRvTjkrZStiYWc0M3BX?= =?utf-8?B?NEZpaldBWjFkRmRTajhSV0NhcURsOE1hT25DVkwzWi83Z1duZXNQUjJxTkts?= =?utf-8?B?dW9iTzQ4RjRzYlRqaE9TVk03Tk0zamcxN2tsbTR2K2NuRnpKWHRMNkJld0U2?= =?utf-8?B?WVVDSkN1L0dHNysxVVlZUUhQSUZTZmF4UGZZL3ZCWXphclJtQWVJWHVKZm1v?= =?utf-8?B?bmRhcjh0bzZZWGcrQ0VYRlB0RkxneE5kM2lUUWgva1lLQko4cDBocThVTk9F?= =?utf-8?B?WFB0YXhDZEpLYXNuSHNub3hRQjlLcktPdWhWQzVhU0FQZmV3QXNSRnRxVW1B?= =?utf-8?B?WWdUQWRvUjV4Zzl5UnM3Rzk1dlRWaTQ4M2oxa0Z3MUJ4RUxVeXM3SGNmeGJ5?= =?utf-8?B?WSs5eXNmQzFQdlQ3Y0tJci8yM0RwOWN0TUtBQVcvZStPQXJoOG9IZ09xcjZH?= =?utf-8?B?SzZEcHF6c0hta01yOVNVTzZ6M01sSDNiN0pkVVRyQUlranhUQU9YWnVGU1k2?= =?utf-8?Q?bl0WY7aXlbL81/opcQIhrcwiOCei4tE=3D?=
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1563; 5:qOAF/fWAHlkHmIFE9JG9I1d4So7fq2Yv0wg486XJtJeEFNXAZj29fwh8yuJTqAFUK20loIvNSHqfirSJMlcu4wzetd04OXwo0Wrf0IcGu5C6+2H52w1BONz+WkyWgVY5Bwi8OemMmtbjNX/QK67JJQi+IusALBuGPag9k2BA0QAX7NRKCo2Vwc+vyjWUJT8VggPKWm/zNaDH6TWM7UA4Rw53Lz+gnPO9eeMT53fRdK9rEHk7PaX5xZ8coM5XgZmFnykxsrIVFTXmQ9Jh5uHlupKYPmLC3g71wt4GimgRYhPLjAiKXaeW9AQvbe6YcsPSFYxCoK2CJwlVyfvH4Qrm5GQAIoiwc+qVd76rmlpnVxgi07RCx81RC6itohH5UYdZsnqmp2I4SH2hkJyD8jqJZg2KikZXLebukt7w7luHi5lL4Fp2V2ieC6uA33Fq7Am68HUjmQOIdpvuWgpP0WhEV1nrxYMKHT75pSC4f1spKTSZWtB0eVq3yxh+XXHgUGmj; 24:ZQG2j9/2P978ELt+QDBLrQofo4BYDXvC7CxrBDBtrvCo3PvvOuz4ukxrBdVpAxVUnD5+ttmjigHxa04c9j8IQ+jKA8F49/lBVS8I7jtQkcE=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1563; 7:yJXwn9r88OVdxWAvzgKa08k+D+rfbSIPn2EXx84jrIsSfM+Es+UPALkDMKHoIEc1o87j1YyEQ+ZsmY1N5xLu6/+zp4JC86OIncnhoRqDbSTFr6cSzmlVDUm4j4VeVlj1tVS582Yv7L++O05Io4LI8IX4kaJep21yDhiZw92xJ612IAepkHChxcJIw9jGTyPQnD9sU3P1M7uItCLRiv6jNtov7ExRi/j9TPacSob3omMETVqus8c67fVCtvtrOtp1aqjmeVpxaqzwn8L4nbvyaT586j1csWCgE80NwitB2Bac2yNHj7WMQvhGFt2as2cVUUIOs6H/FPBG6ZMVYHsuEm2NYnJES/pk8GCs+4xtgwR2TXYSIE1MFomp6H93npka0j6O/MYqEWoXOu0AkIQVgMYKYZPZ9+eTEky6Ri476lvSG2wnB9my2//ZkPoXXdzgQ04W9mWECgrxa4S+dta4Nhqil4zozgvRmih24fv4OBSF3rOG219Tm1CFU+MU6v1XCQuj7PbbhD4ez7htKL/tb/ptVhqZGvOF06r+rCBcSFlmsLey5aXDH2P0cnhnXcZfiBGsGP9Ua9lfEecGDJgPc64guOFndip7JLqZXlwQqY0xkTsAylEG1i3iPUJXsM+6nhhjt6apNVrZhKWrebcsgOQFgZYHZW064+BmPKhplNGC4PNGXd50ZjF4Uupedhd4Hd/CKvzPXhuX+vben21/1j6f8TMKwe/Zrl/tcChvB3AL6PbGa+z1bjh29k0CvXffaCuF3ir1jk+WyfMePUFR5K8hDAsXA2M6RoeDgECTGd8=
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 21 Jul 2017 10:46:33.4852 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB1563
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BP3lAguCuzlTa_QLoG09PXVXthg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 10:46:39 -0000

Michael

I agree with Brian that priority and precedence are different.

For me, priority is something that can be ordered, a number, perhaps a
character or a string of characters, unbounded but where I cannot tell
whether higher or lower is better without being told.

Precedence is more binary, one or a group coming before another one or
group.  I note however that my dictionary also gives a definition of
precedence as a form of priority:-)

Tom Petch


----- Original Message -----
From: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
To: <ietf@ietf.org>
Sent: Tuesday, July 18, 2017 9:53 PM
Subject: Re: the terms "priority" and "precedence"


> On 18/07/2017 23:54, Michael Richardson wrote:
> >
> > We have many places in protocols where we want to express some
ordering of
> > pieces of information.  We call these fields priority or precedence
or
>
> Just a side note: in the design of diffserv we paid a lot of attention
> to that choice of words. You might care to read section 4.2.1 of
RFC2474,
> which could be summarised as precedence != priority. I think there is
> quite some subtlety in this area, and not so much randomness in the
choices.
>
>    Brian
>
> > sometimes other things.  Give encode things as numbers.
> >
> > DNS's MX record has a "preference", in which lower numbers are
better.
> > BGP has a LOCAL_PREF, in which higher numbers are better.
> > RAs have PreferenceLevel, in which higher numbers are better.
> > ROLL has "rank", in which lower numbers mean closer to the root.
> > OSPF has such numbers, which I forget at the moment.
> >
> > Is there any consistent usage where preference is a term used when
> > higher numbers are better and priority when lower numbers are
better?
> > Does the RFC-editor have any suggestions?  Or is it really all
random.
> >
> > --
> > ]               Never tell me the odds!                 | ipv6 mesh
networks [
> > ]   Michael Richardson, Sandelman Software Works        | network
architect  [
> > ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on
rails    [
> >
> >
> >
> > --
> > Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> >  -= IPv6 IoT consulting =-
> >
> >
> >
>


From nobody Fri Jul 21 04:01:11 2017
Return-Path: <rsalz@akamai.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6C2912F274 for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 04:01:10 -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); dkim=pass (2048-bit key) header.d=akamai.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 JLVHZsTJ4i9C for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 04:01:09 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (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 9D47212ECF0 for <ietf@ietf.org>; Fri, 21 Jul 2017 04:01:04 -0700 (PDT)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1]) by m0050102.ppops.net-00190b01. (8.16.0.21/8.16.0.21) with SMTP id v6LAvX1Z015616 for <ietf@ietf.org>; Fri, 21 Jul 2017 12:01:02 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=jan2016.eng; bh=vgW8jwLGGa0nI0SV9YX9ZgPweqa3j9bep4TRO/UY/ow=; b=k1p+GwogOFi7jeXLgawm4ynA40xjVMkSMoWNIkelXTM3dj8sNXNywhsGZuDeihUFHWdR isFyvsMEzUQzf52W7+PyVoE+hyWdCWrBQVSDxzTX8mbaUgTNwgAV+Fkn2v3qlP7Sc+U7 n4v38AlzVMpS9i25PaFvxVV4DLvqMATLHmGyUTWWfo0BWcOES93dTRP7j6k5i+t6fMKS m1uQU7qnjMfDpDVdqv2b0U0Foyy7Orn3nVtobpvg2flsTYCZAUpCVxCBszEvZb06Cveq uewvc8pynZK8WTOAJ2ps+GnMprrWlr1vnxnsUpPK6hltN2/NW2aHWoNG6RMy5rSLW0Dv Tg== 
Received: from prod-mail-ppoint1 (a184-51-33-18.deploy.static.akamaitechnologies.com [184.51.33.18] (may be forged)) by m0050102.ppops.net-00190b01. with ESMTP id 2btxg53wmw-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 21 Jul 2017 12:01:02 +0100
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.16.0.17/8.16.0.17) with SMTP id v6LB11QQ012114 for <ietf@ietf.org>; Fri, 21 Jul 2017 07:01:01 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.33]) by prod-mail-ppoint1.akamai.com with ESMTP id 2bqecuku46-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 21 Jul 2017 07:01:01 -0400
Received: from USMA1EX-DAG1MB5.msg.corp.akamai.com (172.27.123.105) by usma1ex-dag3mb4.msg.corp.akamai.com (172.27.123.56) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Fri, 21 Jul 2017 04:00:57 -0700
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb5.msg.corp.akamai.com (172.27.123.105) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Fri, 21 Jul 2017 07:00:57 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1263.000; Fri, 21 Jul 2017 07:00:57 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: IETF 100 Registration Opening Delayed Until Wednesday, 26 July at 07:00 PDT (14:00 UTC)
Thread-Topic: IETF 100 Registration Opening Delayed Until Wednesday, 26 July at 07:00 PDT (14:00 UTC)
Thread-Index: AQHTAgN+0fBv387C4Ei67GCZ4LbxnaJeS6aA///RhNA=
Date: Fri, 21 Jul 2017 11:00:56 +0000
Message-ID: <e5f8f90c37f748378128bfe29bf0794f@usma1ex-dag1mb1.msg.corp.akamai.com>
References: <150062920623.10991.15657052844940226623.idtracker@ietfa.amsl.com> <86B85671-4152-47DE-A551-F029B58BC546@amsl.com>
In-Reply-To: <86B85671-4152-47DE-A551-F029B58BC546@amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.152.111]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-07-21_05:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1706020000 definitions=main-1707210174
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-07-21_05:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default 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-1706020000 definitions=main-1707210172
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/N37LTchYT7UjnxWD73cYV02hMyk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 11:01:10 -0000

I volunteer to be a speed mentor :)

-- =20
Senior Architect, Akamai Technologies
Member, OpenSSL Dev Team
IM: richsalz@jabber.at Twitter: RichSalz

> -----Original Message-----
> From: Alexa Morris [mailto:amorris@amsl.com]
> Sent: Friday, July 21, 2017 11:47 AM
> To: ietf@ietf.org
> Cc: IETF Announcement List <ietf-announce@ietf.org>
> Subject: Re: IETF 100 Registration Opening Delayed Until Wednesday, 26 Ju=
ly
> at 07:00 PDT (14:00 UTC)
>=20
> The time and date link was incorrect in the message below. Correct link i=
s:
> https://timeanddate.com/s/3ax6.
>=20
> Alexa
>=20
> > On Jul 21, 2017, at 11:26 AM, IETF Secretariat <ietf-secretariat@ietf.o=
rg>
> wrote:
> >
> > Registration for IETF 100 in Singapore has been postponed until Wednesd=
ay
> of next week due to issues with the main venue hotel reservation system
> that are beyond our control.
> >
> > New date: Wednesday, 26 July
> > New time: 07:00 PDT (14:00 UTC)
> >
> > Worldwide times at https://timeanddate.com/s/37rk. An announcement
> opening registration and hotel reservations will be made at 07:00 PDT on =
26
> July.
> >
> > Letters of Invitation may be requested during registration.
> >
> > - IETF Secretariat
> >


From nobody Fri Jul 21 04:17:42 2017
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1808B12ECCB for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 04:17:41 -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 oZpbMUTndpGY for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 04:17:39 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC3AC129B7F for <ietf@ietf.org>; Fri, 21 Jul 2017 04:17:39 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [IPv6:2001:67c:1232:144:a11:96ff:fe01:81e0]) by relay.sandelman.ca (Postfix) with ESMTPS id DDA9D1F8F6; Fri, 21 Jul 2017 11:17:35 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id D21DB1638; Fri, 21 Jul 2017 13:17:25 +0200 (CEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
cc: ietf@ietf.org
Subject: Re: More and more virtual interims
In-reply-to: <20170720131527.e4bcjsry623leeih@mx4.yitter.info>
References: <876859E45DFE49F23C5AD313@PSB> <20170720131527.e4bcjsry623leeih@mx4.yitter.info>
Comments: In-reply-to Andrew Sullivan <ajs@anvilwalrusden.com> message dated "Thu, 20 Jul 2017 09:15:28 -0400."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 21 Jul 2017 13:17:25 +0200
Message-ID: <6824.1500635845@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1GO_aWL-bFBkfylYZHFTzvU55cY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 11:17:41 -0000

--=-=-=
Content-Type: text/plain


Andrew Sullivan <ajs@anvilwalrusden.com> wrote:
    > Maybe what we need is not more virtual interims, but more time boxes.
    > This would do nothing for controversy that needs rapid interaction,
    > but it might meet the test of "faster progress".

Can you explain "time boxes" here?

    > One way to do that would be to set document sprint dates in advance,
    > and for chairs to reserve discussion of this or that other topic at
    > ome time.  Have any WGs tried this recently?

This sounds a bit like a design team meeting to me.


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJZceLFAAoJEJVM4Vb9/EKQyn8IAKf0QmgK8s8qFG5M5Ri7BOjn
cNanBaX4ksdne0XOYIseVlhoRLElKmbCUBH7/dhr56XWrtIPNMlw5WR4BNAbYrut
bH6d+r4BYW7S9WmKVcHwQfvw3XRTNuFXeymIsKGPSmbcOU1W56SP2gz4BuOgFb6l
1vNf19khCsrrO+8pZzBQ0lQYR6A9rHZuF8Ug1cwuxH/KDpxt0PMjV2cYagK8rdCW
MhixhtTqkDCeUmxUi2o3zcfI7vByX48sd/pDBZ3yvkgoKwd1gdeTgW36KV9e2CRO
lc6cLTfeW4BuROrSBsX+z6DqUivDaql+LBWWzjywgdEydddgmlbcnw9OuwPTZtM=
=VXYU
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Jul 21 05:21:17 2017
Return-Path: <akatlas@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75100131C0F for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 05:21: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 3biHcTOrVEU0 for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 05:21:15 -0700 (PDT)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (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 A6C2E131B69 for <ietf@ietf.org>; Fri, 21 Jul 2017 05:21:14 -0700 (PDT)
Received: by mail-wm0-x233.google.com with SMTP id w126so11413534wme.0 for <ietf@ietf.org>; Fri, 21 Jul 2017 05:21:14 -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=oi0qIWHQsr75kYplf68FSFgp9F1/QTXX23nLb/s0I48=; b=uSbHUtBb6YG5pcDNNkKfngT0Z8FGYhwpzQr6BFdaebjSCIHLICZxsrL8HE8V929yl+ 9tILMLz3RFWow8pNni5bZoOHhk2wDOwZdxIkRZ+la5EcasXHtuqhA22C28UUXS2DPc93 6EbmNj/WbVg0Ih0QEyLP0lwJ1gVANNUA4hsEK767cjuJ9VLuYiNTg+Tf53TzKNRZiI3Q B+YzJpXCImJKuDpPt41c6A2h4VuPKIUvYq1yP4iP/WCVKY18WvmiZ0i52f6fBCTJEmCx PJMbhAB7j/vVLHeUlagwCJ/2fyhUULWjjaEgCrqMZ20auSjRS1Q/VcXrhrDSNtgqD14G Tp9Q==
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=oi0qIWHQsr75kYplf68FSFgp9F1/QTXX23nLb/s0I48=; b=Ja7WfcM37Y4bKk5lA+Lvz86g4Nj8DGlbdbcczJG9RN/btJrFWmRiXMGj2G2U0ah5mR k7qiyxokpI8y1uxVAdmSBr3zvL0V3UrUmG/8KHoPN6Gx/OEwbIonbz2ZDtPspZScWFJU EXnCZxZv3PmkbVZqHmYlKckX8dQod467cIasu10wgHaLOB9Jb6S5vArqiNISh5M/reXy 4RII4qZXaVdeNyqVwqgPt9GMw3Iq5XjmdxJ86o/vl458MSe0fZZV7c52KVwNOxF7EWxX qMrY4beI6at4Jgh0Vj02EWFst27bjG3EJGP3JI8bBfNom1jGu8yiMlD/0pV0/D9JuuWt HGGg==
X-Gm-Message-State: AIVw1109PfneiYW44BUVbi52EApegIaDXfxvSSnzgV3rXPA1xFhMXaFv nt5hR1sXd3pGBt2I2EBs+gm/4afUMkqR
X-Received: by 10.28.161.3 with SMTP id k3mr4990267wme.155.1500639673059; Fri, 21 Jul 2017 05:21:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.183.1 with HTTP; Fri, 21 Jul 2017 05:21:12 -0700 (PDT)
In-Reply-To: <6824.1500635845@dooku.sandelman.ca>
References: <876859E45DFE49F23C5AD313@PSB> <20170720131527.e4bcjsry623leeih@mx4.yitter.info> <6824.1500635845@dooku.sandelman.ca>
From: Alia Atlas <akatlas@gmail.com>
Date: Fri, 21 Jul 2017 08:21:12 -0400
Message-ID: <CAG4d1reoa5aWacyeCeDC05UhEZsO=j02X2yDm3ghe7GnS2T0rA@mail.gmail.com>
Subject: Re: More and more virtual interims
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: Andrew Sullivan <ajs@anvilwalrusden.com>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a114ed608a618ed0554d2e67c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/203rfta6Y9WuChM556T6UWQsWI0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 12:21:16 -0000

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

Michael,

At least my read of the suggestion is a bit of an expansion of what we do
with WG Adoption and
WG Last Call - where the mailing list "focuses" on a particular draft or
topic for a week or two.
MPLS has had some success with this tactic in the past.  It is the
alternative that I encouraged
and suggested to the RTG WG Chairs - but got many fewer takers on it.  I'd
love to see more
WGs experiment with this because it does resolve the time-zone & day-job
meeting conflicts issues.

Regards,
Alia

On Fri, Jul 21, 2017 at 7:17 AM, Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Andrew Sullivan <ajs@anvilwalrusden.com> wrote:
>     > Maybe what we need is not more virtual interims, but more time boxes.
>     > This would do nothing for controversy that needs rapid interaction,
>     > but it might meet the test of "faster progress".
>
> Can you explain "time boxes" here?
>
>     > One way to do that would be to set document sprint dates in advance,
>     > and for chairs to reserve discussion of this or that other topic at
>     > ome time.  Have any WGs tried this recently?
>
> This sounds a bit like a design team meeting to me.
>
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
>

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

<div dir=3D"ltr">Michael,<div><br></div><div>At least my read of the sugges=
tion is a bit of an expansion of what we do with WG Adoption and=C2=A0</div=
><div>WG Last Call - where the mailing list &quot;focuses&quot; on a partic=
ular draft or topic for a week or two.</div><div>MPLS has had some success =
with this tactic in the past.=C2=A0 It is the alternative that I encouraged=
</div><div>and suggested to the RTG WG Chairs - but got many fewer takers o=
n it.=C2=A0 I&#39;d love to see more</div><div>WGs experiment with this bec=
ause it does resolve the time-zone &amp; day-job meeting conflicts issues.<=
/div><div><br></div><div>Regards,</div><div>Alia</div></div><div class=3D"g=
mail_extra"><br><div class=3D"gmail_quote">On Fri, Jul 21, 2017 at 7:17 AM,=
 Michael Richardson <span dir=3D"ltr">&lt;<a href=3D"mailto:mcr+ietf@sandel=
man.ca" target=3D"_blank">mcr+ietf@sandelman.ca</a>&gt;</span> wrote:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex"><span class=3D""><br>
Andrew Sullivan &lt;<a href=3D"mailto:ajs@anvilwalrusden.com">ajs@anvilwalr=
usden.com</a>&gt; wrote:<br>
=C2=A0 =C2=A0 &gt; Maybe what we need is not more virtual interims, but mor=
e time boxes.<br>
=C2=A0 =C2=A0 &gt; This would do nothing for controversy that needs rapid i=
nteraction,<br>
=C2=A0 =C2=A0 &gt; but it might meet the test of &quot;faster progress&quot=
;.<br>
<br>
</span>Can you explain &quot;time boxes&quot; here?<br>
<span class=3D""><br>
=C2=A0 =C2=A0 &gt; One way to do that would be to set document sprint dates=
 in advance,<br>
=C2=A0 =C2=A0 &gt; and for chairs to reserve discussion of this or that oth=
er topic at<br>
=C2=A0 =C2=A0 &gt; ome time.=C2=A0 Have any WGs tried this recently?<br>
<br>
</span>This sounds a bit like a design team meeting to me.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
--<br>
Michael Richardson &lt;<a href=3D"mailto:mcr%2BIETF@sandelman.ca">mcr+IETF@=
sandelman.ca</a>&gt;, Sandelman Software Works<br>
=C2=A0-=3D IPv6 IoT consulting =3D-<br>
<br>
<br>
<br>
</div></div></blockquote></div><br></div>

--001a114ed608a618ed0554d2e67c--


From nobody Fri Jul 21 06:21:45 2017
Return-Path: <borje.ohlman@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E854012F24E for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 06:21:43 -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 BFOpqlmgIjxx for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 06:21:42 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (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 32A39131DFB for <ietf@ietf.org>; Fri, 21 Jul 2017 06:21:41 -0700 (PDT)
X-AuditID: c1b4fb2d-c3b2c9c000005f66-9d-5971ffe41e05
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 45.C3.24422.4EFF1795; Fri, 21 Jul 2017 15:21:40 +0200 (CEST)
Received: from ESESSMB110.ericsson.se ([169.254.10.145]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0352.000; Fri, 21 Jul 2017 15:21:39 +0200
From: =?utf-8?B?QsO2cmplIE9obG1hbg==?= <borje.ohlman@ericsson.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: IETF 100 Registration Opening Delayed Until Wednesday, 26 July at 07:00 PDT (14:00 UTC)
Thread-Topic: IETF 100 Registration Opening Delayed Until Wednesday, 26 July at 07:00 PDT (14:00 UTC)
Thread-Index: AQHTAgOJwp0KQSmzlUK6A82NruKGB6JeIwIA
Date: Fri, 21 Jul 2017 13:21:38 +0000
Message-ID: <FE2360A9-61C9-47B2-8F0E-3A8DB1EBFA52@ericsson.com>
References: <150062920623.10991.15657052844940226623.idtracker@ietfa.amsl.com>
In-Reply-To: <150062920623.10991.15657052844940226623.idtracker@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.150]
Content-Type: text/plain; charset="utf-8"
Content-ID: <0DA969C8C0FFC04DB71808668B913638@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrNLMWRmVeSWpSXmKPExsUyM2K7qO6T/4WRBss281o82zifxYHRY8mS n0wBjFFcNimpOZllqUX6dglcGZ0PVrAVvGKvmDPvOksD4wX2LkZODgkBE4krD5ewdTFycQgJ HGGUmPr2BQuEs5RRouF0BxtIFZuAk8Sy80/BOkQElCUOzLzBCmILC6RJnLh5BCqeLvFozwMW CNtI4mrjH7A4i4CqxM07KxhBbF4Be4ltD18zg9hCAn4Sa5f+BpvPKeAv0TXjNBOIzSggK/Gl cTVYDbOAuMStJ/OZIC4VkFiy5zwzhC0q8fLxP1YIW0lixfZLQPM5gOo1Jdbv0ocwrSVWzDaA mKIoMaX7ITvEBYISJ2c+YZnAKDoLyYJZCM2zEJpnIWmehaR5ASPrKkbR4tTi4tx0I2O91KLM 5OLi/Dy9vNSSTYzAKDm45bfuDsbVrx0PMQpwMCrx8MZ8KowUYk0sK67MPcQowcGsJMIr9AUo xJuSWFmVWpQfX1Sak1p8iFGag0VJnNdh34UIIYH0xJLU7NTUgtQimCwTB6dUA6Oih0V6+PfX Bx9ePFp1+cONj2tNNr7gTZzdvdf9zE9hQdsrm3zzKwKEa/YHC9csTSxc8sgq5OhbSdFnEmXC QUFb6tmfpYlOPrW37KG7SGj6s52lSW3ukx0d1h/qt2L6p3HynzDTy1Wf153+qHBoFbtqm7qg fMabXbeyvm/uNOEL2NdzdKpzYa0SS3FGoqEWc1FxIgD0pp7MjgIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mcCsYvAPNcLKu-XD0Kc4vX1wqgo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 13:21:44 -0000

SGksDQoNCkp1c3QgRllJLCB0aGUgbGluayBpbiB0aGUgZW1haWwgcG9pbnRzIGF0IHRoZSB0aW1l
IGZvciB0aGUgSUVURi05OSBQcmFndWUgcmVnaXN0cmF0aW9uIG9wZW5pbmcgdGltZeKApg0KDQpC
ZXN0IHJlZ2FyZHMsDQoJCQlCw7ZyamUNCg0KPiBPbiAyMSBKdWwgMjAxNywgYXQgMTE6MjYsIElF
VEYgU2VjcmV0YXJpYXQgPGlldGYtc2VjcmV0YXJpYXRAaWV0Zi5vcmc+IHdyb3RlOg0KPiANCj4g
UmVnaXN0cmF0aW9uIGZvciBJRVRGIDEwMCBpbiBTaW5nYXBvcmUgaGFzIGJlZW4gcG9zdHBvbmVk
IHVudGlsIFdlZG5lc2RheSBvZiBuZXh0IHdlZWsgZHVlIHRvIGlzc3VlcyB3aXRoIHRoZSBtYWlu
IHZlbnVlIGhvdGVsIHJlc2VydmF0aW9uIHN5c3RlbSB0aGF0IGFyZSBiZXlvbmQgb3VyIGNvbnRy
b2wuIA0KPiANCj4gTmV3IGRhdGU6IFdlZG5lc2RheSwgMjYgSnVseSANCj4gTmV3IHRpbWU6IDA3
OjAwIFBEVCAoMTQ6MDAgVVRDKQ0KPiANCj4gV29ybGR3aWRlIHRpbWVzIGF0IGh0dHBzOi8vdGlt
ZWFuZGRhdGUuY29tL3MvMzdyay4gQW4gYW5ub3VuY2VtZW50IG9wZW5pbmcgcmVnaXN0cmF0aW9u
IGFuZCBob3RlbCByZXNlcnZhdGlvbnMgd2lsbCBiZSBtYWRlIGF0IDA3OjAwIFBEVCBvbiAyNiBK
dWx5Lg0KPiANCj4gTGV0dGVycyBvZiBJbnZpdGF0aW9uIG1heSBiZSByZXF1ZXN0ZWQgZHVyaW5n
IHJlZ2lzdHJhdGlvbi4NCj4gDQo+IC0gSUVURiBTZWNyZXRhcmlhdA0KPiANCg0K


From nobody Fri Jul 21 06:47:06 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58031131723 for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 06:47:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 u0QmRstmjMD0 for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 06:47:04 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED0681317E3 for <ietf@ietf.org>; Fri, 21 Jul 2017 06:47:03 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dYYGh-0002vd-43; Fri, 21 Jul 2017 09:46:59 -0400
Date: Fri, 21 Jul 2017 09:46:52 -0400
From: John C Klensin <john-ietf@jck.com>
To: Alia Atlas <akatlas@gmail.com>
cc: Michael Richardson <mcr+ietf@sandelman.ca>, IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: More and more virtual interims
Message-ID: <67DAB214201CAC8946223A61@PSB>
In-Reply-To: <CAG4d1reoa5aWacyeCeDC05UhEZsO=j02X2yDm3ghe7GnS2T0rA@mail.gmail.com>
References: <876859E45DFE49F23C5AD313@PSB> <20170720131527.e4bcjsry623leeih@mx4.yitter.info> <6824.1500635845@dooku.sandelman.ca> <CAG4d1reoa5aWacyeCeDC05UhEZsO=j02X2yDm3ghe7GnS2T0rA@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Q4RSH-6ANF6bqVdDS7bK-tTfIVI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 13:47:05 -0000

--On Friday, July 21, 2017 08:21 -0400 Alia Atlas
<akatlas@gmail.com> wrote:

> Michael,
> 
> At least my read of the suggestion is a bit of an expansion of
> what we do with WG Adoption and
> WG Last Call - where the mailing list "focuses" on a
> particular draft or topic for a week or two.
> MPLS has had some success with this tactic in the past.  It is
> the alternative that I encouraged
> and suggested to the RTG WG Chairs - but got many fewer takers
> on it.  I'd love to see more
> WGs experiment with this because it does resolve the time-zone
> & day-job meeting conflicts issues.

Alia,

I've seen variations on that approach work very well in some
applications and procedure-related WGs too.  I've also seen it
fail spectacularly in other WGs.   I think the difference is, at
least in part, that requests from WG leadership that the WG
focus completely on a single topic or small cluster of topics
for a while works well with WGs that are, themselves, narrowly
focused, with drafts that cover different aspects of the same
topic and the expectation that the WG's work is close-ended,
i.e., that the WG will be terminated when that work is complete,
rather than expanding or rechartering to take on more work.  At
the other extreme, if a WG includes multiple topics or subtopics
with different clusters of interested participants, I won't say
it is impossible, but probably a separate list should be
considered if it is necessary to concentrate for a while on one
specific topic or draft.

best,
   john





From nobody Fri Jul 21 09:44:43 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65BF213146C for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 09:44:41 -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, RP_MATCHES_RCVD=-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 y0Bo0B9Aa2oR for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 09:44:39 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A858F126D46 for <ietf@ietf.org>; Fri, 21 Jul 2017 09:44:39 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dYb2b-0008vv-HY; Fri, 21 Jul 2017 12:44:37 -0400
Date: Fri, 21 Jul 2017 12:44:30 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ted Lemon <mellon@fugue.com>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
cc: IETF discussion list <ietf@ietf.org>
Subject: Re: Slides, eye charts, and a beg for readability
Message-ID: <C792101ECBC3FA12C656DFF2@PSB>
In-Reply-To: <CAPt1N1mOhZHCy=jJOrPyTz3-qy3KP0Mvrg+6Qj+Hpid4bq1-jw@mail.gmail.com>
References: <CAKKJt-ehdzREsf3QzGZ+JFOkMm-dGpSdGVFBUJE4BhqWweY+Og@mail.gmail.com> <CAPv4CP8UGr_xLDYW=zKQUP6mXaWgQ67JM+-_NJOvCgfOhXU2hQ@mail.gmail.c om> <CAKKJt-et1SW5J_dU-Bfj=yCKtvVv+sSqzYqh1Sur=NgzA-Mghg@mail.gmail.com> <CAPt1N1mOhZHCy=jJOrPyTz3-qy3KP0Mvrg+6Qj+Hpid4bq1-jw@mail.gmail.c om>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wptJT0HbgyJewceFd22o8eOVdEA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 16:44:41 -0000

--On Friday, July 21, 2017 10:45 +0200 Ted Lemon
<mellon@fugue.com> wrote:

> FWIW, presbyopia doesn't make it difficult to read things that
> are distant.  What does that is myopia.   I've had myopia
> since I was a kid. There is just a limit to how much we can
> cram onto a slide, and it's actually really difficult to know
> what that limit is when you are _preparing_ the slides.

Ted, in the last several years, I've gotten a rather
comprehensive set of personal lessons in things that can go
wrong with vision.  More than presbyopia can be age-related or
at least have age as significant risk factors.   I hope no one
else in this community finds out first-hand about any of the
others, but they are out there.   My knowledge is still
incomplete and I hope to never complete it, at least in the same
way).    For those reasons and reasons that relate more closely
to our policies about treating each other professionally and
with respect, I suggest that, if someone says they can't see
something, I think we need to take them at their word and start
figuring out what to do about it rather than probing diagnoses
or terminology.  

Narelle's note is very helpful in that regard: While, if slides
are simple black type on white backgrounds, type size and choice
of type styles are usually the major readability issues, there
are, as she says, others (and good choices of style and contrast
can mitigate size issues to a certain extent).  Contrast and
glare are, as Nary more or less pointed out, are room
environmental factors over which presentation designers usually
have little control (if one wanted a way to overconstrain site
selection very quickly, take specific requirements about that to
MTGVENUE although we often have control over dimmers and whether
spotlights are on or off and probably don't take enough
advantage of it).

> I suspect there is standards work to be done here.   E.g., is
> it the case that the relative size of the screen when seen
> from the back of small rooms is the same as from the back of
> large rooms? 
>...

There has actually been a good deal of research work, whether
"standards" or not, done on this.   The links in Narelle's note
are a reasonably starting point (I would have suggested others,
but they are no better, just different).  For more general
discussions about avoiding clutter and distractions that
interfere with rapid and accurate understanding, see Ed Tufte's
work (what works well for the somewhat visually impaired does
not always correlate with clutter reduction, but they are often
linked).  However, a warning: Tufte has often made comments to
the effect that Powerpoint should be treated as a disease.

> I say this slightly tongue-in-cheek, but it's a real problem
> that I really had to think about when preparing my slides.   I
> was not able to come up with a definite answer.   I don't know
> how well I did, to be honest, but I did increase the font size
> above the default, which seemed pretty eye-chart-ish to me.

In my experience, even thinking about the issues is a huge step
forward and improves the results.   If one is composing slides
on a typical laptop screen and one has roughly normal vision,
simply stepping away and trying to see if they those slide be
read and understood from two or three meters away can be very
instructive.  Again, it is possible to do much better than
thinking plus that test will yield, but they are big steps.

   john

p.s. I've been thinking about a room setup in which 300-500
people could all sit AT the front.  It is actually an
interesting design exercise even though I don't think I've ever
seen a meeting space in which rows of seats are arranged above
each rather than front to back (a few opera house might come
close, but AFAIK we haven't considered those for meeting venues
yet.  :-)


From nobody Fri Jul 21 10:21:21 2017
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88DDB131898 for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 10:21:19 -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 Ot8oId7GGPJX for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 10:21:18 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66946127601 for <ietf@ietf.org>; Fri, 21 Jul 2017 10:21:10 -0700 (PDT)
Received: from dooku.sandelman.ca (ip-94-113-76-12.net.upcbroadband.cz [94.113.76.12]) by relay.sandelman.ca (Postfix) with ESMTPS id 53E8E1F8F6; Fri, 21 Jul 2017 17:21:08 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 006411673; Fri, 21 Jul 2017 19:20:56 +0200 (CEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Alia Atlas <akatlas@gmail.com>
cc: Andrew Sullivan <ajs@anvilwalrusden.com>, IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: More and more virtual interims
In-reply-to: <CAG4d1reoa5aWacyeCeDC05UhEZsO=j02X2yDm3ghe7GnS2T0rA@mail.gmail.com>
References: <876859E45DFE49F23C5AD313@PSB> <20170720131527.e4bcjsry623leeih@mx4.yitter.info> <6824.1500635845@dooku.sandelman.ca> <CAG4d1reoa5aWacyeCeDC05UhEZsO=j02X2yDm3ghe7GnS2T0rA@mail.gmail.com>
Comments: In-reply-to Alia Atlas <akatlas@gmail.com> message dated "Fri, 21 Jul 2017 08:21:12 -0400."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 21 Jul 2017 19:20:56 +0200
Message-ID: <25084.1500657656@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CkVomBm060mW5wvoL914wgaMbBY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 17:21:19 -0000

--=-=-=
Content-Type: text/plain


Alia Atlas <akatlas@gmail.com> wrote:
    > At least my read of the suggestion is a bit of an expansion of what we do
    > with WG Adoption and
    > WG Last Call - where the mailing list "focuses" on a particular draft or
    > topic for a week or two.

I think it can only work for a list/WG which has a too much activity
(in too many directions).  For a WG which has gone quiet because people
are busy/bored/etc.  I'm not sure that such a deadline can really help.

But, it's worth doing more experiments!
I'd love to be proven wrong.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJZcjf4AAoJEJVM4Vb9/EKQs1oH/0YqF4kjNAaH78b6xiDXd0TK
NFtqvW/EdGGC5vWXV4ErtUTdnJgVnWS6UWH1WweLPsxulZOUYmGhrS1bTChjm3WJ
Zpo0KH40P7AxQZsjen61wcrIUnGetuqhyK4m+0I16yuDfaoDNG3I5oDnA/Hkfv6v
UaR0v9eNHZ3RM3D8/cEgiLjgjWOVq+0dd9LNWoTLAfO6GpLdPKupr19/oOVG7L5d
rGMLohqLqf+TcJsayJX2djKLLl2PYJbpRs7Bjc3XFKH1tiJaRTGVrd4n5QzPTyXO
dkR7woG0xPPEV2uKrdOmm0nMeors+DxWERLTu8lfTNnKPB/XQxJOUYJLxYFoOIs=
=d8eh
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Jul 21 10:42:28 2017
Return-Path: <randy_presuhn@alumni.stanford.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1BDD131C1A for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 10:42:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 H5Kj-LyKWta9 for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 10:42:25 -0700 (PDT)
Received: from mail-pg0-f41.google.com (mail-pg0-f41.google.com [74.125.83.41]) (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 6A01A129B15 for <ietf@ietf.org>; Fri, 21 Jul 2017 10:42:25 -0700 (PDT)
Received: by mail-pg0-f41.google.com with SMTP id k14so31580149pgr.0 for <ietf@ietf.org>; Fri, 21 Jul 2017 10:42:25 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=BV7+J0+RocDNfIDkaTMuo5inhUkyJY2JbHMZzlcCRPc=; b=M/ja3w6m1IL9jn5UZCHyt0uIjAFqNmdnjM7IW61EOSSx2p7RHsg0KT0g7Rr5St2xpL Xz5Hd6VPDJ1aKFvhG0Sw6TsyzXW2tqcP6Gig+sZ2LPa+x+N6oq/x/Pp3PvmzR3zfu2om YIpczQb9lvRAQ7IZen4UEYWtnRKWsJoco8DY7x0x0c61IIl7JsD8RtJff2Zj5RUUscw4 jrqmlMs8hiaEgoPaEP9E/10lj19nOIRCdb1xKA0Ds7qjB4KuDrvGk9gCEi76i1m88AO8 lEcTbHMnHFK1fbzsgHpJLwtam61iBCySGOgXqDvRMA5iulEZOYBmh7Aw9Uz40KpyLJag mIEA==
X-Gm-Message-State: AIVw112Ox7Kq5/ivXDcaqyxKyLPEOR2Y3YrCbxVFvHrKnv4GafCNPCM+ 3od0T0jFg0PIe2gPyB6ObA==
X-Received: by 10.99.147.9 with SMTP id b9mr8130664pge.393.1500658944622; Fri, 21 Jul 2017 10:42:24 -0700 (PDT)
Received: from [192.168.1.113] (c-24-130-218-233.hsd1.ca.comcast.net. [24.130.218.233]) by smtp.gmail.com with ESMTPSA id k127sm9918923pfc.75.2017.07.21.10.42.23 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Jul 2017 10:42:24 -0700 (PDT)
Subject: Re: Slides, eye charts, and a beg for readability
To: IETF Mailing List <ietf@ietf.org>
References: <CAKKJt-ehdzREsf3QzGZ+JFOkMm-dGpSdGVFBUJE4BhqWweY+Og@mail.gmail.com> <CAPv4CP8UGr_xLDYW=zKQUP6mXaWgQ67JM+-_NJOvCgfOhXU2hQ@mail.gmail.com> <CAKKJt-et1SW5J_dU-Bfj=yCKtvVv+sSqzYqh1Sur=NgzA-Mghg@mail.gmail.com> <CAPt1N1mOhZHCy=jJOrPyTz3-qy3KP0Mvrg+6Qj+Hpid4bq1-jw@mail.gmail.com>
From: Randy Presuhn <randy_presuhn@alumni.stanford.edu>
Message-ID: <32ff9f88-303f-3e82-25b4-c89b9934199b@alumni.stanford.edu>
Date: Fri, 21 Jul 2017 10:42:27 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CAPt1N1mOhZHCy=jJOrPyTz3-qy3KP0Mvrg+6Qj+Hpid4bq1-jw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8_OB2QzZrHilP1X0P0-tO0BSwg0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 17:42:27 -0000

Hi -

On 7/21/2017 1:45 AM, Ted Lemon wrote:
> FWIW, presbyopia doesn't make it difficult to read things that are 
> distant.

Did you double-check with an optometrist?
It can, and I have the trifocals to prove it.

One can have an eye shaped to be rather
far-sighted (at-rest focus beyond infinity)
but also have sufficient strength and flexibility
to pass as 20/20 or better.  With presbyopia, that
eye is stuck focused past infinity, so no distance
is clear without correction.  Welcome to my world.

Randy


From nobody Fri Jul 21 10:44:36 2017
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72D20131A7D for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 10:44:35 -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 bsz_W7x-dZX3 for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 10:44:33 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A064129B15 for <ietf@ietf.org>; Fri, 21 Jul 2017 10:44:33 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [IPv6:2001:0:53aa:64c:101a:651b:a18e:b3f3]) by relay.sandelman.ca (Postfix) with ESMTPS id D545D1F8F6 for <ietf@ietf.org>; Fri, 21 Jul 2017 17:44:30 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 01E1F1673; Fri, 21 Jul 2017 19:44:04 +0200 (CEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IETF discussion list <ietf@ietf.org>
Subject: Re: Slides, eye charts, and a beg for readability
In-reply-to: <C792101ECBC3FA12C656DFF2@PSB>
References: <CAKKJt-ehdzREsf3QzGZ+JFOkMm-dGpSdGVFBUJE4BhqWweY+Og@mail.gmail.com> <CAPv4CP8UGr_xLDYW=zKQUP6mXaWgQ67JM+-_NJOvCgfOhXU2hQ@mail.gmail.c om> <CAKKJt-et1SW5J_dU-Bfj=yCKtvVv+sSqzYqh1Sur=NgzA-Mghg@mail.gmail.com> <CAPt1N1mOhZHCy=jJOrPyTz3-qy3KP0Mvrg+6Qj+Hpid4bq1-jw@mail.gmail.c om> <C792101ECBC3FA12C656DFF2@PSB>
Comments: In-reply-to John C Klensin <john-ietf@jck.com> message dated "Fri, 21 Jul 2017 12:44:30 -0400."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 21 Jul 2017 19:44:04 +0200
Message-ID: <27513.1500659044@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vKIXOwg6O1xGchEDl5B-h0Y3DV4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 17:44:35 -0000

--=-=-=
Content-Type: text/plain


John C Klensin <john-ietf@jck.com> wrote:
    > can mitigate size issues to a certain extent).  Contrast and
    > glare are, as Nary more or less pointed out, are room
    > environmental factors over which presentation designers usually

for instance, Karlin I/II was silly.
The Karlin II side couldn't be seen by the chairs due to pillars.
Still, it would have been small to have just Karlin I.

    > p.s. I've been thinking about a room setup in which 300-500
    > people could all sit AT the front.  It is actually an

My suggestion is to remove 1/3 of the chairs and put more space between the
rows.   We could also just have a few stacks of chairs available.
We *RARELY* fill every chair in the room, usually many chairs go unused
because of difficulty in stepping over people.   When we *DO* fill every
chair (for an unexpectedly popular BOF), we also overflow out of the room and
onto the floor.

That way, more people could sit closer.
Many times, I've wanted to just remove the back 5 rows of chairs to
force people to sit closer...

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJZcj1kAAoJEJVM4Vb9/EKQLQ0IAJcLszkTeowF3QZFD40Wtq27
apTSC9P+0U35kEgqbCGkNMdLyXxzo6/OQzON5Lw/D/ors0so0CvgU8zIAy/yQFme
/kZsXBF4IRAftSQuhzhr077wordV3+JSTmF7flF5y18hCGpYObzrmRh6+yhSscpZ
Pb918y0TsSSAw4J9SA8T4w1trnllwCOpc0NY5No+wMxAXm8ZFR6a+MBz4DxVnAHE
pmeZRe38yml4NqgSTK3XRDCdTCy0ZcDN3aBIrlEju05FVCB8DHKPhw/CM82a4qbR
hjA6EnzKUWpIDBU9CJmbeaiIigpMBtZe4NuH9yZamWpeDuX1uUqrwF79/z2DisY=
=dJZ/
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Jul 21 12:19:16 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70C691318A3 for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 12:19:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 J9_lDp2Be30a for <ietf@ietfa.amsl.com>; Fri, 21 Jul 2017 12:19:12 -0700 (PDT)
Received: from mail-pf0-x234.google.com (mail-pf0-x234.google.com [IPv6:2607:f8b0:400e:c00::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 AFC4112F257 for <ietf@ietf.org>; Fri, 21 Jul 2017 12:19:12 -0700 (PDT)
Received: by mail-pf0-x234.google.com with SMTP id o88so27209876pfk.3 for <ietf@ietf.org>; Fri, 21 Jul 2017 12:19:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=djQsygRD5qN5EPGZmDylDC7NSTLVcLu1yiXApPTA+Q4=; b=TPL1xjWZBBwmzKE4EV8TUZmvoGVCGxkB6/KXnPw2rtYkPttzKJetAlMe94Pbf8ofkJ rrV5eJwH7MVilV+VcNGavnCtPdxu6OP2SLK5iyLbJ1yGS5jSdB2cvV23JlTG0LYjiuVs rXTdvYw+wnykHuCDqMQ/wOQiZt/CjyXCxCeFm8g74a6sC9gaAV90B4lvGzeNrvNg8O2M oe01WjprZ6B14IXv95ERISbnTImaazFuas5tFlf0BN67tAwC96FUkKYmQ4TInhTfohUW HspX2liiUthP/mkUzKFNT9vlKuldsBDfvm0Uzo0z0aXV/74+THXL95bymQ+vqt/odftD NfGg==
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=djQsygRD5qN5EPGZmDylDC7NSTLVcLu1yiXApPTA+Q4=; b=K1QIgGxdvrHQO9W0740RJyBwOYViufvj8u83/sn+fP2isIFBS2AnRqkaKj9g7DU5nu zEX58SktdopltNs/eiedWacDbwkF0Bz41H/0lrx83hf+LHeRScButHv2wqpz8HZhybrS fDW7YHstyhWhA8fCZl3a8aYQD6Rf+BcBdmUVq/Hy0rrXxEgt4H2VzdnejlP+qga4wpw0 U80bypG0dz9WoVPoaBKGFF77MHwDJCm7AsZu/4eQTslmDNnRK7c1XWppcQg3z8spWg6j hP91bQPurnvKr1fdKBYmWIgK/bjf57zKCVQzHFS3GBCMX72+FKy0OQAc5M6D7/XeLY/7 jZ2Q==
X-Gm-Message-State: AIVw113G84SPcu3ri6H/3zZwEpZYOyJ0vTqOu2to6PfYUCnsAmZI+3qe Dh5dDhR6x3Lt+g1L5Fx8r6jzMpkBrxlW
X-Received: by 10.99.107.193 with SMTP id g184mr8323629pgc.167.1500664752127;  Fri, 21 Jul 2017 12:19:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.181.130 with HTTP; Fri, 21 Jul 2017 12:18:31 -0700 (PDT)
In-Reply-To: <27513.1500659044@dooku.sandelman.ca>
References: <CAKKJt-ehdzREsf3QzGZ+JFOkMm-dGpSdGVFBUJE4BhqWweY+Og@mail.gmail.com> <CAKKJt-et1SW5J_dU-Bfj=yCKtvVv+sSqzYqh1Sur=NgzA-Mghg@mail.gmail.com> <C792101ECBC3FA12C656DFF2@PSB> <27513.1500659044@dooku.sandelman.ca>
From: Ted Lemon <mellon@fugue.com>
Date: Fri, 21 Jul 2017 21:18:31 +0200
Message-ID: <CAPt1N1=+WOuTpAQiECjywO0MELuVmk3YdZjRox-6Xxa7t=Ewiw@mail.gmail.com>
Subject: Re: Slides, eye charts, and a beg for readability
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c14088a7a58340554d8bdc4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fyeL_476MN0YNIeCsuQPF1Jt09k>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 19:19:14 -0000

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

Thanks all for the schooling on what I have to look forward to.   I thought
presbyopia sucked.   Also thanks for the advice about standing back from
the laptop screen, John--I will try that next IETF.

On Fri, Jul 21, 2017 at 7:44 PM, Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> John C Klensin <john-ietf@jck.com> wrote:
>     > can mitigate size issues to a certain extent).  Contrast and
>     > glare are, as Nary more or less pointed out, are room
>     > environmental factors over which presentation designers usually
>
> for instance, Karlin I/II was silly.
> The Karlin II side couldn't be seen by the chairs due to pillars.
> Still, it would have been small to have just Karlin I.
>
>     > p.s. I've been thinking about a room setup in which 300-500
>     > people could all sit AT the front.  It is actually an
>
> My suggestion is to remove 1/3 of the chairs and put more space between the
> rows.   We could also just have a few stacks of chairs available.
> We *RARELY* fill every chair in the room, usually many chairs go unused
> because of difficulty in stepping over people.   When we *DO* fill every
> chair (for an unexpectedly popular BOF), we also overflow out of the room
> and
> onto the floor.
>
> That way, more people could sit closer.
> Many times, I've wanted to just remove the back 5 rows of chairs to
> force people to sit closer...
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
>

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

<div dir=3D"ltr">Thanks all for the schooling on what I have to look forwar=
d to. =C2=A0 I thought presbyopia sucked. =C2=A0 Also thanks for the advice=
 about standing back from the laptop screen, John--I will try that next IET=
F.</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, J=
ul 21, 2017 at 7:44 PM, Michael Richardson <span dir=3D"ltr">&lt;<a href=3D=
"mailto:mcr+ietf@sandelman.ca" target=3D"_blank">mcr+ietf@sandelman.ca</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"><span class=3D""><br>
John C Klensin &lt;<a href=3D"mailto:john-ietf@jck.com">john-ietf@jck.com</=
a>&gt; wrote:<br>
=C2=A0 =C2=A0 &gt; can mitigate size issues to a certain extent).=C2=A0 Con=
trast and<br>
=C2=A0 =C2=A0 &gt; glare are, as Nary more or less pointed out, are room<br=
>
=C2=A0 =C2=A0 &gt; environmental factors over which presentation designers =
usually<br>
<br>
</span>for instance, Karlin I/II was silly.<br>
The Karlin II side couldn&#39;t be seen by the chairs due to pillars.<br>
Still, it would have been small to have just Karlin I.<br>
<span class=3D""><br>
=C2=A0 =C2=A0 &gt; p.s. I&#39;ve been thinking about a room setup in which =
300-500<br>
=C2=A0 =C2=A0 &gt; people could all sit AT the front.=C2=A0 It is actually =
an<br>
<br>
</span>My suggestion is to remove 1/3 of the chairs and put more space betw=
een the<br>
rows.=C2=A0 =C2=A0We could also just have a few stacks of chairs available.=
<br>
We *RARELY* fill every chair in the room, usually many chairs go unused<br>
because of difficulty in stepping over people.=C2=A0 =C2=A0When we *DO* fil=
l every<br>
chair (for an unexpectedly popular BOF), we also overflow out of the room a=
nd<br>
onto the floor.<br>
<br>
That way, more people could sit closer.<br>
Many times, I&#39;ve wanted to just remove the back 5 rows of chairs to<br>
force people to sit closer...<br>
<br>
--<br>
Michael Richardson &lt;<a href=3D"mailto:mcr%2BIETF@sandelman.ca">mcr+IETF@=
sandelman.ca</a>&gt;, Sandelman Software Works<br>
=C2=A0-=3D IPv6 IoT consulting =3D-<br>
<br>
<br>
<br>
</blockquote></div><br></div>

--94eb2c14088a7a58340554d8bdc4--


From nobody Sat Jul 22 09:20:00 2017
Return-Path: <lee@asgard.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AF2F126C0F for <ietf@ietfa.amsl.com>; Sat, 22 Jul 2017 09:19:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.398
X-Spam-Level: 
X-Spam-Status: No, score=-5.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8] 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 WzWlJ6unE13S for <ietf@ietfa.amsl.com>; Sat, 22 Jul 2017 09:19:57 -0700 (PDT)
Received: from atl4mhob12.registeredsite.com (atl4mhob12.registeredsite.com [209.17.115.50]) (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 E2AD8120725 for <ietf@ietf.org>; Sat, 22 Jul 2017 09:19:56 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.204]) by atl4mhob12.registeredsite.com (8.14.4/8.14.4) with ESMTP id v6MGJslS015454 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf@ietf.org>; Sat, 22 Jul 2017 12:19:54 -0400
Received: (qmail 28182 invoked by uid 0); 22 Jul 2017 16:19:54 -0000
X-TCPREMOTEIP: 70.196.7.242
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?100.95.51.157?) (lee@asgard.org@70.196.7.242) by 0 with ESMTPA; 22 Jul 2017 16:19:54 -0000
Content-Type: multipart/alternative; boundary=Apple-Mail-BB9EAA6D-1E29-4090-998C-8FCC656B056A
Mime-Version: 1.0 (1.0)
Subject: Re: Slides, eye charts, and a beg for readability
From: Lee Howard <lee@asgard.org>
X-Mailer: iPhone Mail (14F89)
In-Reply-To: <CAKKJt-et1SW5J_dU-Bfj=yCKtvVv+sSqzYqh1Sur=NgzA-Mghg@mail.gmail.com>
Date: Sat, 22 Jul 2017 18:19:51 +0200
Cc: Scott Brim <scott.brim@gmail.com>, IETF discussion list <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <DDAEF38E-E303-4091-B84C-BDDFA5F059D1@asgard.org>
References: <CAKKJt-ehdzREsf3QzGZ+JFOkMm-dGpSdGVFBUJE4BhqWweY+Og@mail.gmail.com> <CAPv4CP8UGr_xLDYW=zKQUP6mXaWgQ67JM+-_NJOvCgfOhXU2hQ@mail.gmail.com> <CAKKJt-et1SW5J_dU-Bfj=yCKtvVv+sSqzYqh1Sur=NgzA-Mghg@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HWnrSxeaRr39jUcuiMyJd0MSE6U>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Jul 2017 16:19:58 -0000

--Apple-Mail-BB9EAA6D-1E29-4090-998C-8FCC656B056A
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

I have a talk for the EDU team on presentation skills a couple of years ago,=
 and included short, easy notes on slides. Find it on their page.=20

Document authors don't reliably send in slides ahead of time, even with badg=
ering. They're volunteers; the only thing chairs could do would be threaten t=
o yank their slot, which weakens the WG's work.=20

Similarly, authors aren't generally bothering to look for advice on how the i=
mprove their slides. Resources exist. Rather, they write notes on pages and c=
onsider it done.=20

I think all we can really do is complain about it so this meeting's presente=
rs hear about it and do better next time.=20

Lee

Sent from my iPhone

> On Jul 21, 2017, at 10:22 AM, Spencer Dawkins at IETF <spencerdawkins.ietf=
@gmail.com> wrote:
>=20
> Hi, Scott,
>=20
> On Jul 19, 2017 6:04 PM, "Scott Brim" <scott.brim@gmail.com> wrote:
> Can't you just sit in front?=20
>=20
> "Does not scale" ;-)
>=20
> I see that several of us are griping in this thread, which is what one wou=
ld expect, given the nature of this mailing list.=20
>=20
> I'm not hearing people saying, "I never have problems, must be you", which=
 I interpret as the visual equivalent of "if the music is too loud, you're t=
oo old".
>=20
> So, I'll probably bring this up on the working group chairs mailing list, f=
or their discussion and possible action.
>=20
> Thanks, everyone, for your thoughts.
>=20
> Spencer
>=20
> Spencer

--Apple-Mail-BB9EAA6D-1E29-4090-998C-8FCC656B056A
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=3D=
utf-8"></head><body dir=3D"auto"><div>I have a talk for the EDU team on pres=
entation skills a couple of years ago, and included short, easy notes on sli=
des. Find it on their page.&nbsp;</div><div id=3D"AppleMailSignature"><br></=
div><div id=3D"AppleMailSignature">Document authors don't reliably send in s=
lides ahead of time, even with badgering. They're volunteers; the only thing=
 chairs could do would be threaten to yank their slot, which weakens the WG'=
s work.&nbsp;</div><div id=3D"AppleMailSignature"><br></div><div id=3D"Apple=
MailSignature">Similarly, authors aren't generally bothering to look for adv=
ice on how the improve their slides. Resources exist. Rather, they write not=
es on pages and consider it done.&nbsp;</div><div id=3D"AppleMailSignature">=
<br></div><div id=3D"AppleMailSignature">I think all we can really do is com=
plain about it so this meeting's presenters hear about it and do better next=
 time.&nbsp;</div><div id=3D"AppleMailSignature"><br></div><div id=3D"AppleM=
ailSignature">Lee<br><br>Sent from my iPhone</div><div><br>On Jul 21, 2017, a=
t 10:22 AM, Spencer Dawkins at IETF &lt;<a href=3D"mailto:spencerdawkins.iet=
f@gmail.com">spencerdawkins.ietf@gmail.com</a>&gt; wrote:<br><br></div><bloc=
kquote type=3D"cite"><div><div dir=3D"auto"><div>Hi, Scott,<br><div class=3D=
"gmail_extra"><br><div class=3D"gmail_quote">On Jul 19, 2017 6:04 PM, "Scott=
 Brim" &lt;<a href=3D"mailto:scott.brim@gmail.com">scott.brim@gmail.com</a>&=
gt; wrote:<br type=3D"attribution"><blockquote class=3D"quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"auto"=
>Can't you just sit in front?&nbsp;</div>
</blockquote></div><br></div></div><div class=3D"gmail_extra" dir=3D"auto">"=
Does not scale" ;-)</div><div class=3D"gmail_extra" dir=3D"auto"><br></div><=
div class=3D"gmail_extra" dir=3D"auto">I see that several of us are griping i=
n this thread, which is what one would expect, given the nature of this mail=
ing list.&nbsp;</div><div class=3D"gmail_extra" dir=3D"auto"><br></div><div c=
lass=3D"gmail_extra" dir=3D"auto">I'm not hearing people saying, "I never ha=
ve problems, must be you", which I interpret as the visual equivalent of "if=
 the music is too loud, you're too old".</div><div class=3D"gmail_extra" dir=
=3D"auto"><br></div><div class=3D"gmail_extra" dir=3D"auto">So, I'll probabl=
y bring this up on the working group chairs mailing list, for their discussi=
on and possible action.</div><div class=3D"gmail_extra" dir=3D"auto"><br></d=
iv><div class=3D"gmail_extra" dir=3D"auto">Thanks, everyone, for your though=
ts.</div><div class=3D"gmail_extra" dir=3D"auto"><br></div><div class=3D"gma=
il_extra" dir=3D"auto">Spencer</div><div class=3D"gmail_extra" dir=3D"auto">=
<br></div><div class=3D"gmail_extra" dir=3D"auto">Spencer</div></div>
</div></blockquote></body></html>=

--Apple-Mail-BB9EAA6D-1E29-4090-998C-8FCC656B056A--


From nobody Sat Jul 22 10:24:58 2017
Return-Path: <naiming@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E661B1319B4; Sat, 22 Jul 2017 10:24:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.012
X-Spam-Level: 
X-Spam-Status: No, score=-14.012 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_HTML_ATTACH=0.01, 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 hRpxvVl1i5eE; Sat, 22 Jul 2017 10:24:54 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 412E112EBF9; Sat, 22 Jul 2017 10:24:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=33760; q=dns/txt; s=iport; t=1500744294; x=1501953894; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Nf7M0PF1SqWzuA9+wfp+PuAC3UgHKnI2R2WWA0r6Bq0=; b=fOyH9AXaUTZrD9UNlnjg3flqmU8252rtlnd0SWQr08DgGdjNLDQdo9qy fKSY2tHjHQIobTTpgWRKXBzIx/sP7Q4ncN5zPNEk02dT5/N2BoGcZewCu ZnTdVHmjtr7zT6bgcGbW0DjaaG/T4rfftwnva+bCqiX4c+kQQglfG2rEm Y=;
X-Files: draft-ietf-dhc-relay-port-06-from-5.diff.html, ATT00001.htm : 19135,  2115
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BlAQD5iHNZ/5RdJa1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgm8+LWSBFAeOBZFDkHuFLIISLIM8gV8Cg34/GAECAQEBAQEBAWsohRk?= =?us-ascii?q?GeRACAQYCBEICMCUCBA4FDoohEJAYoAqLLQEBAQEBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?Q4PgyiFWQuCboRVg1mCMQEEl02CNyyFHgKELoIdgQGHFYU7ggwZPoR5iRaBRZV?= =?us-ascii?q?jAR84gQp1FUkSAYRHgjx2iFKBDgEBAQ?=
X-IronPort-AV: E=Sophos;i="5.40,397,1496102400";  d="htm'217?html'217,217?scan'217,217,208,217";a="55297898"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Jul 2017 17:24:52 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id v6MHOp5U005205 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 22 Jul 2017 17:24:52 GMT
Received: from xch-rcd-004.cisco.com (173.37.102.14) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sat, 22 Jul 2017 12:24:51 -0500
Received: from xch-rcd-004.cisco.com ([173.37.102.14]) by XCH-RCD-004.cisco.com ([173.37.102.14]) with mapi id 15.00.1210.000; Sat, 22 Jul 2017 12:24:50 -0500
From: "Naiming Shen (naiming)" <naiming@cisco.com>
To: Ralf Weber <ralf.weber@nominum.com>
CC: "int-dir@ietf.org" <int-dir@ietf.org>, dhcwg <dhcwg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dhc-relay-port.all@ietf.org" <draft-ietf-dhc-relay-port.all@ietf.org>, "Enke Chen (enkechen)" <enkechen@cisco.com>
Subject: Re: Intdir early review of draft-ietf-dhc-relay-port-05
Thread-Topic: Intdir early review of draft-ietf-dhc-relay-port-05
Thread-Index: AQHTAVDdC/pmVM+g8UmmGrJI4+prW6JeA2gAgAJsn4A=
Date: Sat, 22 Jul 2017 17:24:50 +0000
Message-ID: <A5E26208-902E-4101-9542-B5896342396E@cisco.com>
References: <150055249283.9589.17482424577250077220@ietfa.amsl.com> <B560FD8D-FFF1-4D2E-947B-A1F1BD3AA6DA@cisco.com>
In-Reply-To: <B560FD8D-FFF1-4D2E-947B-A1F1BD3AA6DA@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.58.222]
Content-Type: multipart/mixed; boundary="_005_A5E26208902E41019542B5896342396Eciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/91eSgR-WU1gCTtlggynUR2eoa7s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Jul 2017 17:24:57 -0000

--_005_A5E26208902E41019542B5896342396Eciscocom_
Content-Type: multipart/alternative;
	boundary="_000_A5E26208902E41019542B5896342396Eciscocom_"

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


Changed again of the paragraph in section 4 to below, thanks
to Ted who offerred the text:

   Relay agents do not maintain state.  To return a message to its
   source, the relay agent must include all the required information in
   the Relay-Forward message.  When a relay in a sequence of cascaded
   relays does not use the standard source port, that source port must
   be included along with the source address.  This option allows the
   relay agent to do so.

rfcdiff attached.

Cheers,
- Naiming


--_000_A5E26208902E41019542B5896342396Eciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <9B99B8F66F3E3B458E0CD0CE50AB3A87@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;" class=3D"">
<div class=3D""><br class=3D"">
</div>
Changed again of the paragraph in section 4 to below, thanks
<div class=3D"">to Ted who offerred the text:</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">
<div style=3D"margin: 0px; font-size: 14px; line-height: normal; font-famil=
y: Menlo; background-color: rgb(255, 255, 255);" class=3D"">
<span style=3D"font-variant-ligatures: no-common-ligatures" class=3D"">&nbs=
p; &nbsp;Relay agents do not maintain state.&nbsp; To return a message to i=
ts</span></div>
<div style=3D"margin: 0px; font-size: 14px; line-height: normal; font-famil=
y: Menlo; background-color: rgb(255, 255, 255);" class=3D"">
<span style=3D"font-variant-ligatures: no-common-ligatures" class=3D"">&nbs=
p;&nbsp; source, the relay agent must include all the required information =
in</span></div>
<div style=3D"margin: 0px; font-size: 14px; line-height: normal; font-famil=
y: Menlo; background-color: rgb(255, 255, 255);" class=3D"">
<span style=3D"font-variant-ligatures: no-common-ligatures" class=3D"">&nbs=
p;&nbsp; the Relay-Forward message.&nbsp; When a relay in a sequence of cas=
caded</span></div>
<div style=3D"margin: 0px; font-size: 14px; line-height: normal; font-famil=
y: Menlo; background-color: rgb(255, 255, 255);" class=3D"">
<span style=3D"font-variant-ligatures: no-common-ligatures" class=3D"">&nbs=
p;&nbsp; relays does not use the standard source port, that source port mus=
t</span></div>
<div style=3D"margin: 0px; font-size: 14px; line-height: normal; font-famil=
y: Menlo; background-color: rgb(255, 255, 255);" class=3D"">
<span style=3D"font-variant-ligatures: no-common-ligatures" class=3D"">&nbs=
p;&nbsp; be included along with the source address.&nbsp; This option allow=
s the</span></div>
<div style=3D"margin: 0px; font-size: 14px; line-height: normal; font-famil=
y: Menlo; background-color: rgb(255, 255, 255);" class=3D"">
<span style=3D"font-variant-ligatures: no-common-ligatures" class=3D"">&nbs=
p;&nbsp; relay agent to do so.</span></div>
</div>
<div class=3D""><span style=3D"font-variant-ligatures: no-common-ligatures"=
 class=3D""><br class=3D"">
</span></div>
<div class=3D"">rfcdiff attached.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Cheers,</div>
<div class=3D"">- Naiming</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D""></div>
</body>
</html>

--_000_A5E26208902E41019542B5896342396Eciscocom_--

--_005_A5E26208902E41019542B5896342396Eciscocom_
Content-Type: text/html;
	name="draft-ietf-dhc-relay-port-06-from-5.diff.html"
Content-Description: draft-ietf-dhc-relay-port-06-from-5.diff.html
Content-Disposition: attachment;
	filename="draft-ietf-dhc-relay-port-06-from-5.diff.html"; size=19135;
	creation-date="Sat, 22 Jul 2017 17:24:50 GMT";
	modification-date="Sat, 22 Jul 2017 17:24:50 GMT"
Content-ID: <CDEEF9BE4FDB9C4085618F7A74175BE6@emea.cisco.com>
Content-Transfer-Encoding: base64

PCFET0NUWVBFIGh0bWwgUFVCTElDICItLy9XM0MvL0RURCBYSFRNTCAxLjAgVHJhbnNpdGlvbmFs
Ly9FTiIgImh0dHA6Ly93d3cudzMub3JnL1RSL3hodG1sMS9EVEQveGh0bWwxLXRyYW5zaXRpb25h
bC5kdGQiPiANCjwhLS0gR2VuZXJhdGVkIGJ5IHJmY2RpZmYgMS40MjogcmZjZGlmZiAgLS0+IA0K
PCEtLSA8IURPQ1RZUEUgaHRtbCBQVUJMSUMgIi0vL1czQy8vRFREIEhUTUwgNC4wMSBUcmFuc2l0
aW9uYWwiID4gLS0+DQo8IS0tIFN5c3RlbTogRGFyd2luIE5BSU1JTkctTS1EMkVVIDE2LjcuMCBE
YXJ3aW4gS2VybmVsIFZlcnNpb24gMTYuNy4wOiBUaHUgSnVuIDE1IDE3OjM2OjI3IFBEVCAyMDE3
OyByb290OnhudS0zNzg5LjcwLjE2fjIvUkVMRUFTRV9YODZfNjQgeDg2XzY0IC0tPiANCjwhLS0g
VXNpbmcgYXdrOiAvdXNyL2xvY2FsL2Jpbi9nYXdrOiBHTlUgQXdrIDQuMS4zLCBBUEk6IDEuMSAt
LT4gDQo8IS0tIFVzaW5nIGRpZmY6IC91c3IvYmluL2RpZmY6IGRpZmYgKEdOVSBkaWZmdXRpbHMp
IDIuOC4xIC0tPiANCjwhLS0gVXNpbmcgd2RpZmY6IC91c3IvbG9jYWwvYmluL3dkaWZmOiB3ZGlm
ZiAoR05VIHdkaWZmKSAxLjIuMiAtLT4gDQo8aHRtbD4gDQo8aGVhZD4gDQogIDxtZXRhIGh0dHAt
ZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWlzby04ODU5
LTEiIC8+IA0KICA8bWV0YSBodHRwLWVxdWl2PSJDb250ZW50LVN0eWxlLVR5cGUiIGNvbnRlbnQ9
InRleHQvY3NzIiAvPiANCiAgPHRpdGxlPkRpZmY6IGRyYWZ0LWlldGYtZGhjLXJlbGF5LXBvcnQt
MDUudHh0IC0gZHJhZnQtaWV0Zi1kaGMtcmVsYXktcG9ydC0wNi50eHQ8L3RpdGxlPiANCiAgPHN0
eWxlIHR5cGU9InRleHQvY3NzIj4gDQogICAgYm9keSAgICB7IG1hcmdpbjogMC40ZXg7IG1hcmdp
bi1yaWdodDogYXV0bzsgfSANCiAgICB0ciAgICAgIHsgfSANCiAgICB0ZCAgICAgIHsgd2hpdGUt
c3BhY2U6IHByZTsgZm9udC1mYW1pbHk6IG1vbm9zcGFjZTsgdmVydGljYWwtYWxpZ246IHRvcDsg
Zm9udC1zaXplOiAwLjg2ZW07fSANCiAgICB0aCAgICAgIHsgZm9udC1zaXplOiAwLjg2ZW07IH0g
DQogICAgLnNtYWxsICB7IGZvbnQtc2l6ZTogMC42ZW07IGZvbnQtc3R5bGU6IGl0YWxpYzsgZm9u
dC1mYW1pbHk6IFZlcmRhbmEsIEhlbHZldGljYSwgc2Fucy1zZXJpZjsgfSANCiAgICAubGVmdCAg
IHsgYmFja2dyb3VuZC1jb2xvcjogI0VFRTsgfSANCiAgICAucmlnaHQgIHsgYmFja2dyb3VuZC1j
b2xvcjogI0ZGRjsgfSANCiAgICAuZGlmZiAgIHsgYmFja2dyb3VuZC1jb2xvcjogI0NDRjsgfSAN
CiAgICAubGJsb2NrIHsgYmFja2dyb3VuZC1jb2xvcjogI0JGQjsgfSANCiAgICAucmJsb2NrIHsg
YmFja2dyb3VuZC1jb2xvcjogI0ZGODsgfSANCiAgICAuaW5zZXJ0IHsgYmFja2dyb3VuZC1jb2xv
cjogIzhGRjsgfSANCiAgICAuZGVsZXRlIHsgYmFja2dyb3VuZC1jb2xvcjogI0FDRjsgfSANCiAg
ICAudm9pZCAgIHsgYmFja2dyb3VuZC1jb2xvcjogI0ZGQjsgfSANCiAgICAuY29udCAgIHsgYmFj
a2dyb3VuZC1jb2xvcjogI0VFRTsgfSANCiAgICAubGluZWJyIHsgYmFja2dyb3VuZC1jb2xvcjog
I0FBQTsgfSANCiAgICAubGluZW5vIHsgY29sb3I6IHJlZDsgYmFja2dyb3VuZC1jb2xvcjogI0ZG
RjsgZm9udC1zaXplOiAwLjdlbTsgdGV4dC1hbGlnbjogcmlnaHQ7IHBhZGRpbmc6IDAgMnB4OyB9
IA0KICAgIC5lbGlwc2lzeyBiYWNrZ3JvdW5kLWNvbG9yOiAjQUFBOyB9IA0KICAgIC5sZWZ0IC5j
b250IHsgYmFja2dyb3VuZC1jb2xvcjogI0RERDsgfSANCiAgICAucmlnaHQgLmNvbnQgeyBiYWNr
Z3JvdW5kLWNvbG9yOiAjRUVFOyB9IA0KICAgIC5sYmxvY2sgLmNvbnQgeyBiYWNrZ3JvdW5kLWNv
bG9yOiAjOUQ5OyB9IA0KICAgIC5yYmxvY2sgLmNvbnQgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjREQ2
OyB9IA0KICAgIC5pbnNlcnQgLmNvbnQgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjMEREOyB9IA0KICAg
IC5kZWxldGUgLmNvbnQgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjOEFEOyB9IA0KICAgIC5zdGF0cywg
LnN0YXRzIHRkLCAuc3RhdHMgdGggeyBiYWNrZ3JvdW5kLWNvbG9yOiAjRUVFOyBwYWRkaW5nOiAy
cHggMDsgfSANCiAgPC9zdHlsZT4gDQo8L2hlYWQ+IA0KPGJvZHkgPiANCiAgPHRhYmxlIGJvcmRl
cj0iMCIgY2VsbHBhZGRpbmc9IjAiIGNlbGxzcGFjaW5nPSIwIj4gDQogIDx0ciBiZ2NvbG9yPSJv
cmFuZ2UiPjx0aD48L3RoPjx0aD4mbmJzcDtkcmFmdC1pZXRmLWRoYy1yZWxheS1wb3J0LTA1LnR4
dCZuYnNwOzwvdGg+PHRoPiA8L3RoPjx0aD4mbmJzcDtkcmFmdC1pZXRmLWRoYy1yZWxheS1wb3J0
LTA2LnR4dCZuYnNwOzwvdGg+PHRoPjwvdGg+PC90cj4gDQogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwv
dGQ+PC90cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij5OZXR3b3JraW5nIFdvcmtpbmcgR3JvdXAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIE4uIFNoZW48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij5OZXR3b3JraW5nIFdvcmtpbmcgR3JvdXAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIE4uIFNoZW48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgRS4gQ2hlbjwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgRS4gQ2hlbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+SW50ZW5kZWQgc3RhdHVzOiBTdGFuZGFyZHMgVHJh
Y2sgICAgICAgICAgICAgICAgICAgICAgICAgICBDaXNjbyBTeXN0ZW1zPC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+SW50ZW5kZWQgc3RhdHVzOiBTdGFuZGFyZHMgVHJhY2sgICAgICAg
ICAgICAgICAgICAgICAgICAgICBDaXNjbyBTeXN0ZW1zPC90ZD48dGQgY2xhc3M9ImxpbmVubyIg
dmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQ+PGEgbmFtZT0iZGlmZjAwMDEi
IC8+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48dGQgY2xhc3M9ImxibG9jayI+RXhwaXJlczogPHNwYW4gY2xhc3M9ImRlbGV0ZSI+T2N0
b2JlciAyNywgMjAxNyAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIEFwcmlsIDI1PC9z
cGFuPiwgMjAxNzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj5FeHBpcmVzOiA8c3Bh
biBjbGFzcz0iaW5zZXJ0Ij5KYW51YXJ5IDIzLCAyMDE4ICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgIEp1bHkgMjI8L3NwYW4+LCAyMDE3PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWdu
PSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgICAgICAgICAgICAgIEdlbmVyYWxpemVkIFVEUCBTb3VyY2UgUG9ydCBmb3IgREhDUCBS
ZWxheTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgIEdlbmVy
YWxpemVkIFVEUCBTb3VyY2UgUG9ydCBmb3IgREhDUCBSZWxheTwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAgICAgICAg
IGRyYWZ0LWlldGYtZGhjLXJlbGF5LXBvcnQtMDU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICAgICAgICAgICAgICAgICAgICAgZHJhZnQtaWV0Zi1kaGMtcmVsYXktcG9ydC0wNTwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWdu
PSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij5BYnN0cmFjdDwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPkFic3RyYWN0PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRo
aXMgZG9jdW1lbnQgcHJvcG9zZXMgYW4gZXh0ZW5zaW9uIHRvIHRoZSBESENQIHByb3RvY29scyB0
aGF0IGFsbG93czwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFRoaXMgZG9jdW1l
bnQgcHJvcG9zZXMgYW4gZXh0ZW5zaW9uIHRvIHRoZSBESENQIHByb3RvY29scyB0aGF0IGFsbG93
czwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgYSByZWxheSBhZ2VudCB0byByZWNlaXZlIHBhY2tldHMgZnJvbSBhIHNlcnZlciBvciBhbiB1
cHN0cmVhbSByZWxheTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGEgcmVsYXkg
YWdlbnQgdG8gcmVjZWl2ZSBwYWNrZXRzIGZyb20gYSBzZXJ2ZXIgb3IgYW4gdXBzdHJlYW0gcmVs
YXk8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PiAgIGFnZW50IG9uIGFueSBVRFAgcG9ydCwgbm90IGp1c3QgdGhlIGRlZmF1bHQgcG9ydCA2NyBm
b3IgSVB2NCBvcjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGFnZW50IG9uIGFu
eSBVRFAgcG9ydCwgbm90IGp1c3QgdGhlIGRlZmF1bHQgcG9ydCA2NyBmb3IgSVB2NCBvcjwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgZGVm
YXVsdCBwb3J0IDU0NyBmb3IgSVB2Ni48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4g
ICBkZWZhdWx0IHBvcnQgNTQ3IGZvciBJUHY2LjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+DQogICAgICA8dHIgYmdjb2xvcj0iZ3JheSIgPjx0ZD48
L3RkPjx0aD48YSBuYW1lPSJwYXJ0LWwyIiAvPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8
L3NtYWxsPjxlbT4gcGFnZSAxLCBsaW5lIDMzPC9lbT48L3RoPjx0aD4gPC90aD48dGg+PGEgbmFt
ZT0icGFydC1yMiIgLz48c21hbGw+c2tpcHBpbmcgdG8gY2hhbmdlIGF0PC9zbWFsbD48ZW0+IHBh
Z2UgMSwgbGluZSAzMzwvZW0+PC90aD48dGQ+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIEludGVybmV0
LURyYWZ0cyBhcmUgd29ya2luZyBkb2N1bWVudHMgb2YgdGhlIEludGVybmV0IEVuZ2luZWVyaW5n
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgSW50ZXJuZXQtRHJhZnRzIGFyZSB3
b3JraW5nIGRvY3VtZW50cyBvZiB0aGUgSW50ZXJuZXQgRW5naW5lZXJpbmc8L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRhc2sgRm9yY2Ug
KElFVEYpLiAgTm90ZSB0aGF0IG90aGVyIGdyb3VwcyBtYXkgYWxzbyBkaXN0cmlidXRlPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgVGFzayBGb3JjZSAoSUVURikuICBOb3RlIHRo
YXQgb3RoZXIgZ3JvdXBzIG1heSBhbHNvIGRpc3RyaWJ1dGU8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
IiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHdvcmtpbmcgZG9jdW1lbnRzIGFz
IEludGVybmV0LURyYWZ0cy4gIFRoZSBsaXN0IG9mIGN1cnJlbnQgSW50ZXJuZXQtPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgd29ya2luZyBkb2N1bWVudHMgYXMgSW50ZXJuZXQt
RHJhZnRzLiAgVGhlIGxpc3Qgb2YgY3VycmVudCBJbnRlcm5ldC08L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
IiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIERyYWZ0cyBpcyBhdCBodHRw
Oi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZHJhZnRzL2N1cnJlbnQvLjwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmlnaHQiPiAgIERyYWZ0cyBpcyBhdCBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5v
cmcvZHJhZnRzL2N1cnJlbnQvLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjwvdHI+DQogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBJbnRl
cm5ldC1EcmFmdHMgYXJlIGRyYWZ0IGRvY3VtZW50cyB2YWxpZCBmb3IgYSBtYXhpbXVtIG9mIHNp
eCBtb250aHM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBJbnRlcm5ldC1EcmFm
dHMgYXJlIGRyYWZ0IGRvY3VtZW50cyB2YWxpZCBmb3IgYSBtYXhpbXVtIG9mIHNpeCBtb250aHM8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
IGFuZCBtYXkgYmUgdXBkYXRlZCwgcmVwbGFjZWQsIG9yIG9ic29sZXRlZCBieSBvdGhlciBkb2N1
bWVudHMgYXQgYW55PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgYW5kIG1heSBi
ZSB1cGRhdGVkLCByZXBsYWNlZCwgb3Igb2Jzb2xldGVkIGJ5IG90aGVyIGRvY3VtZW50cyBhdCBh
bnk8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PiAgIHRpbWUuICBJdCBpcyBpbmFwcHJvcHJpYXRlIHRvIHVzZSBJbnRlcm5ldC1EcmFmdHMgYXMg
cmVmZXJlbmNlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgdGltZS4gIEl0IGlz
IGluYXBwcm9wcmlhdGUgdG8gdXNlIEludGVybmV0LURyYWZ0cyBhcyByZWZlcmVuY2U8L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIG1hdGVy
aWFsIG9yIHRvIGNpdGUgdGhlbSBvdGhlciB0aGFuIGFzICJ3b3JrIGluIHByb2dyZXNzLiI8L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBtYXRlcmlhbCBvciB0byBjaXRlIHRoZW0g
b3RoZXIgdGhhbiBhcyAid29yayBpbiBwcm9ncmVzcy4iPC90ZD48dGQgY2xhc3M9ImxpbmVubyIg
dmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0K
ICAgICAgPHRyPjx0ZD48YSBuYW1lPSJkaWZmMDAwMiIgLz48L3RkPjwvdHI+DQogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4g
ICBUaGlzIEludGVybmV0LURyYWZ0IHdpbGwgZXhwaXJlIG9uIDxzcGFuIGNsYXNzPSJkZWxldGUi
Pk9jdG9iZXIgMjcsIDIwMTc8L3NwYW4+LjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2Nr
Ij4gICBUaGlzIEludGVybmV0LURyYWZ0IHdpbGwgZXhwaXJlIG9uIDxzcGFuIGNsYXNzPSJpbnNl
cnQiPkphbnVhcnkgMjMsIDIwMTg8L3NwYW4+LjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij5Db3B5cmlnaHQgTm90aWNlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+Q29weXJp
Z2h0IE5vdGljZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+
DQogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFz
cz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBDb3B5cmlnaHQgKGMp
IDIwMTcgSUVURiBUcnVzdCBhbmQgdGhlIHBlcnNvbnMgaWRlbnRpZmllZCBhcyB0aGU8L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBDb3B5cmlnaHQgKGMpIDIwMTcgSUVURiBUcnVz
dCBhbmQgdGhlIHBlcnNvbnMgaWRlbnRpZmllZCBhcyB0aGU8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
IiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGRvY3VtZW50IGF1dGhvcnMuICBB
bGwgcmlnaHRzIHJlc2VydmVkLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGRv
Y3VtZW50IGF1dGhvcnMuICBBbGwgcmlnaHRzIHJlc2VydmVkLjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90
cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij4gICBUaGlzIGRvY3VtZW50IGlzIHN1YmplY3QgdG8gQkNQIDc4IGFuZCB0aGUg
SUVURiBUcnVzdCdzIExlZ2FsPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgVGhp
cyBkb2N1bWVudCBpcyBzdWJqZWN0IHRvIEJDUCA3OCBhbmQgdGhlIElFVEYgVHJ1c3QncyBMZWdh
bDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgUHJvdmlzaW9ucyBSZWxhdGluZyB0byBJRVRGIERvY3VtZW50czwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmlnaHQiPiAgIFByb3Zpc2lvbnMgUmVsYXRpbmcgdG8gSUVURiBEb2N1bWVudHM8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
IChodHRwOi8vdHJ1c3RlZS5pZXRmLm9yZy9saWNlbnNlLWluZm8pIGluIGVmZmVjdCBvbiB0aGUg
ZGF0ZSBvZjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIChodHRwOi8vdHJ1c3Rl
ZS5pZXRmLm9yZy9saWNlbnNlLWluZm8pIGluIGVmZmVjdCBvbiB0aGUgZGF0ZSBvZjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgcHVibGlj
YXRpb24gb2YgdGhpcyBkb2N1bWVudC4gIFBsZWFzZSByZXZpZXcgdGhlc2UgZG9jdW1lbnRzPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgcHVibGljYXRpb24gb2YgdGhpcyBkb2N1
bWVudC4gIFBsZWFzZSByZXZpZXcgdGhlc2UgZG9jdW1lbnRzPC90ZD48dGQgY2xhc3M9ImxpbmVu
byIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4NCiAgICAgIDx0ciBiZ2NvbG9yPSJncmF5
IiA+PHRkPjwvdGQ+PHRoPjxhIG5hbWU9InBhcnQtbDMiIC8+PHNtYWxsPnNraXBwaW5nIHRvIGNo
YW5nZSBhdDwvc21hbGw+PGVtPiBwYWdlIDQsIGxpbmUgMzg8L2VtPjwvdGg+PHRoPiA8L3RoPjx0
aD48YSBuYW1lPSJwYXJ0LXIzIiAvPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxs
PjxlbT4gcGFnZSA0LCBsaW5lIDM4PC9lbT48L3RoPjx0ZD48L3RkPjwvdHI+DQogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
cGFyYWdyYXBoLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHBhcmFncmFwaC48
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZh
bGlnbj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgQSBESENQIHJlbGF5IGFnZW50IGNh
biBsaXN0ZW4gZm9yIERIQ1AgbWVzc2FnZXMgZnJvbSBhIHNlcnZlciBvcjwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIEEgREhDUCByZWxheSBhZ2VudCBjYW4gbGlzdGVuIGZv
ciBESENQIG1lc3NhZ2VzIGZyb20gYSBzZXJ2ZXIgb3I8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxp
Z249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIGFub3RoZXIgdXBzdHJlYW0gcmVs
YXkgYWdlbnQgZGV2aWNlIG9uIGFueSB2YWxpZCBVRFAgcG9ydDwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgICAgIGFub3RoZXIgdXBzdHJlYW0gcmVsYXkgYWdlbnQgZGV2aWNlIG9u
IGFueSB2YWxpZCBVRFAgcG9ydDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjwvdHI+DQogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgYXZhaWxhYmxlIGluIHRoZSByZWxheSBzeXN0ZW0gaW5j
bHVkaW5nIHRoZSBESENQIFVEUCBwb3J0IDU0Ny48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICAgICBhdmFpbGFibGUgaW4gdGhlIHJlbGF5IHN5c3RlbSBpbmNsdWRpbmcgdGhlIERI
Q1AgVURQIHBvcnQgNTQ3LjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3Rk
PjwvdHI+DQogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgICAgVGhlIGRlZmF1bHQgVURQIHBvcnQgaXMgNTQ3IGlmIHRoZXJl
IGlzIG5vIGV4cGxpY2l0IGNvbmZpZ3VyYXRpb248L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICAgICBUaGUgZGVmYXVsdCBVRFAgcG9ydCBpcyA1NDcgaWYgdGhlcmUgaXMgbm8gZXhw
bGljaXQgY29uZmlndXJhdGlvbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjwvdHI+DQogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgZm9yIHRoZSBnZW5lcmFsaXplZCBVRFAgc291cmNlIHBv
cnQgZXh0ZW5zaW9uIGZvciBESENQIHJlbGF5LjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgICAgIGZvciB0aGUgZ2VuZXJhbGl6ZWQgVURQIHNvdXJjZSBwb3J0IGV4dGVuc2lvbiBm
b3IgREhDUCByZWxheS48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48
L3RyPg0KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQg
Y2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+NC4gIFJlbGF5IFNv
dXJjZSBQb3J0IFN1Yi1vcHRpb24gYW5kIE9wdGlvbjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPjQuICBSZWxheSBTb3VyY2UgUG9ydCBTdWItb3B0aW9uIGFuZCBPcHRpb248L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+PHRkPjxhIG5hbWU9ImRpZmYwMDAzIiAvPjwvdGQ+
PC90cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRk
IGNsYXNzPSJsYmxvY2siPiAgIDxzcGFuIGNsYXNzPSJkZWxldGUiPkFsdGhvdWdoIGEgREhDUCBz
ZXJ2ZXIgY2FuIGltcGxpY2l0bHkgZGV0ZXJtaW5lIHRoZSBVRFAgc291cmNlIHBvcnQ8L3NwYW4+
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIDxzcGFuIGNsYXNzPSJpbnNlcnQi
PlJlbGF5IGFnZW50cyBkbyBub3QgbWFpbnRhaW4gc3RhdGUuICBUbyByZXR1cm48L3NwYW4+IGEg
bWVzc2FnZSA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij50byBpdHM8L3NwYW4+PC90ZD48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNsYXNzPSJk
ZWxldGUiPiAgIHdoZW4gaXQgcmVjZWl2ZXM8L3NwYW4+IGEgbWVzc2FnZSA8c3BhbiBjbGFzcz0i
ZGVsZXRlIj5mcm9tIGE8L3NwYW4+IHJlbGF5IDxzcGFuIGNsYXNzPSJkZWxldGUiPmFnZW50LCB0
aGlzIHN1Yi1vcHRpb24gbWFrZXM8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxv
Y2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgIHNvdXJjZSwgdGhlPC9zcGFuPiByZWxheSA8c3Bh
biBjbGFzcz0iaW5zZXJ0Ij5hZ2VudCBtdXN0IGluY2x1ZGUgYWxsPC9zcGFuPiB0aGUgPHNwYW4g
Y2xhc3M9Imluc2VydCI+cmVxdWlyZWQgaW5mb3JtYXRpb248L3NwYW4+IGluPC90ZD48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNsYXNz
PSJkZWxldGUiPiAgIHRoZSByZXF1ZXN0IGV4cGxpY2l0IGZvcjwvc3Bhbj4gdGhlIDxzcGFuIGNs
YXNzPSJkZWxldGUiPnNlcnZlciB0byB1c2UgYSBub24tREhDUCBVRFAgcG9ydDwvc3Bhbj4gaW4g
dGhlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIHRoZSA8c3BhbiBjbGFzcz0i
aW5zZXJ0Ij5SZWxheS1Gb3J3YXJkPC9zcGFuPiBtZXNzYWdlLiAgV2hlbiA8c3BhbiBjbGFzcz0i
aW5zZXJ0Ij5hPC9zcGFuPiByZWxheSA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5pbiBhIHNlcXVlbmNl
IG9mIGNhc2NhZGVkPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjwvdHI+DQogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3Rk
Pjx0ZCBjbGFzcz0ibGJsb2NrIj4gICA8c3BhbiBjbGFzcz0iZGVsZXRlIj5yZXBseTwvc3Bhbj4g
bWVzc2FnZS4gIFdoZW4gPHNwYW4gY2xhc3M9ImRlbGV0ZSI+SVB2NiBjYXNjYWRlZDwvc3Bhbj4g
cmVsYXkgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+YWdlbnRzIGFyZSBpbnZvbHZlZCw8L3NwYW4+IHRo
ZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4g
ICByZWxheXMgZG9lcyBub3QgdXNlPC9zcGFuPiB0aGUgPHNwYW4gY2xhc3M9Imluc2VydCI+c3Rh
bmRhcmQgc291cmNlIHBvcnQsIHRoYXQgc291cmNlPC9zcGFuPiBwb3J0IDxzcGFuIGNsYXNzPSJp
bnNlcnQiPm11c3Q8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwv
dGQ+PC90cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+
PHRkIGNsYXNzPSJsYmxvY2siPiAgIDxzcGFuIGNsYXNzPSJkZWxldGUiPmRvd25zdHJlYW0gbm9u
LURIQ1AgVURQPC9zcGFuPiBwb3J0IDxzcGFuIGNsYXNzPSJkZWxldGUiPm5lZWRzIHRvPC9zcGFu
PiBiZSA8c3BhbiBjbGFzcz0iZGVsZXRlIj5yZWNvcmRlZCB1c2luZzwvc3Bhbj4gdGhlIDxzcGFu
IGNsYXNzPSJkZWxldGUiPm9wdGlvbi48L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
YmxvY2siPiAgIGJlIDxzcGFuIGNsYXNzPSJpbnNlcnQiPmluY2x1ZGVkIGFsb25nIHdpdGggdGhl
IHNvdXJjZSBhZGRyZXNzLiAgVGhpcyBvcHRpb24gYWxsb3dzPC9zcGFuPiB0aGU8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIDxzcGFuIGNsYXNzPSJpbnNlcnQiPnJlbGF5IGFn
ZW50IHRvIGRvIHNvLjwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+NC4xLiAg
U291cmNlIFBvcnQgU3ViLW9wdGlvbiBmb3IgREhDUHY0PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+NC4xLiAgU291cmNlIFBvcnQgU3ViLW9wdGlvbiBmb3IgREhDUHY0PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRoZSBSZWxheSBBZ2VudCAiU291cmNlIFBvcnQgU3Vi
LW9wdGlvbiIgaXMgYSBuZXcgb3B0aW9uLCBhbmQgaXQgaXM8L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICBUaGUgUmVsYXkgQWdlbnQgIlNvdXJjZSBQb3J0IFN1Yi1vcHRpb24iIGlz
IGEgbmV3IG9wdGlvbiwgYW5kIGl0IGlzPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBwYXJ0IG9mIHRoZSByZWxheS1hZ2VudC1pbmZvcm1h
dGlvbiBvcHRpb24gZm9yIERIQ1B2NCBbUkZDMzA0Nl0uPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgcGFydCBvZiB0aGUgcmVsYXktYWdlbnQtaW5mb3JtYXRpb24gb3B0aW9uIGZv
ciBESENQdjQgW1JGQzMwNDZdLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjwvdHI+DQogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4NCiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBUaGUg
Zm9ybWF0IG9mIHRoZSAiU291cmNlIFBvcnQgU3ViLW9wdGlvbiIgaXMgc2hvd24gYmVsb3c6PC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgVGhlIGZvcm1hdCBvZiB0aGUgIlNvdXJj
ZSBQb3J0IFN1Yi1vcHRpb24iIGlzIHNob3duIGJlbG93OjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjwvdHI+DQogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZh
bGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4N
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICAgICAgICAgICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSs8L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICArLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSs8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90
ZD48L3RyPg0KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgIHwgU3ViT3B0IENvZGUgICB8ICAgICAgTGVuICAg
ICAgfDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgIHwgU3ViT3B0
IENvZGUgICB8ICAgICAgTGVuICAgICAgfDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjwvdHI+DQoNCiAgICAgPHRyPjx0ZD48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQ+PC90ZD48L3RyPg0KICAgICA8
dHIgYmdjb2xvcj0iZ3JheSI+PHRoIGNvbHNwYW49IjUiIGFsaWduPSJjZW50ZXIiPjxhIG5hbWU9
ImVuZCI+Jm5ic3A7RW5kIG9mIGNoYW5nZXMuIDMgY2hhbmdlIGJsb2Nrcy4mbmJzcDs8L2E+PC90
aD48L3RyPg0KICAgICA8dHIgY2xhc3M9InN0YXRzIj48dGQ+PC90ZD48dGg+PGk+NyBsaW5lcyBj
aGFuZ2VkIG9yIGRlbGV0ZWQ8L2k+PC90aD48dGg+PGk+IDwvaT48L3RoPjx0aD48aT44IGxpbmVz
IGNoYW5nZWQgb3IgYWRkZWQ8L2k+PC90aD48dGQ+PC90ZD48L3RyPg0KICAgICA8dHI+PHRkIGNv
bHNwYW49IjUiIGFsaWduPSJjZW50ZXIiIGNsYXNzPSJzbWFsbCI+PGJyLz5UaGlzIGh0bWwgZGlm
ZiB3YXMgcHJvZHVjZWQgYnkgcmZjZGlmZiAxLjQyLiBUaGUgbGF0ZXN0IHZlcnNpb24gaXMgYXZh
aWxhYmxlIGZyb20gPGEgaHJlZj0iaHR0cDovL3d3dy50b29scy5pZXRmLm9yZy90b29scy9yZmNk
aWZmLyIgPmh0dHA6Ly90b29scy5pZXRmLm9yZy90b29scy9yZmNkaWZmLzwvYT4gPC90ZD48L3Ry
Pg0KICAgPC90YWJsZT4NCiAgIDwvYm9keT4NCiAgIDwvaHRtbD4NCg==

--_005_A5E26208902E41019542B5896342396Eciscocom_
Content-Type: text/html; name="ATT00001.htm"
Content-Description: ATT00001.htm
Content-Disposition: attachment; filename="ATT00001.htm"; size=2115;
	creation-date="Sat, 22 Jul 2017 17:24:50 GMT";
	modification-date="Sat, 22 Jul 2017 17:24:50 GMT"
Content-ID: <043103185A8A044BA1FC32E34C20E3EB@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0
L2h0bWwgY2hhcnNldD11dGYtOCI+PC9oZWFkPjxib2R5IHN0eWxlPSJ3b3JkLXdyYXA6IGJyZWFr
LXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJyZWFrOiBhZnRl
ci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPjxkaXYgY2xhc3M9IiI+PC9kaXY+PGRpdiBjbGFzcz0i
Ij48YnIgY2xhc3M9IiI+PGRpdj48YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj48ZGl2
IGNsYXNzPSIiPk9uIEp1bCAyMCwgMjAxNywgYXQgOToyMyBQTSwgTmFpbWluZyBTaGVuIChuYWlt
aW5nKSAmbHQ7PGEgaHJlZj0ibWFpbHRvOm5haW1pbmdAY2lzY28uY29tIiBjbGFzcz0iIj5uYWlt
aW5nQGNpc2NvLmNvbTwvYT4mZ3Q7IHdyb3RlOjwvZGl2PjxiciBjbGFzcz0iQXBwbGUtaW50ZXJj
aGFuZ2UtbmV3bGluZSI+PGRpdiBjbGFzcz0iIj48ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj5I
aSBSYWxmLDxiciBjbGFzcz0iIj48YnIgY2xhc3M9IiI+VGhhbmtzIGZvciB5b3VyIHJldmlldyBv
ZiB0aGlzIGRvY3VtZW50LiBZb3VyPGJyIGNsYXNzPSIiPnN1Z2dlc3Rpb24gbWFrZXMgbG90IG9m
IHNlbnNlLjxiciBjbGFzcz0iIj5J4oCZbSBnb2luZyB0byBhZGQgdGhlIGJlbG93IHNlbnRlbmNl
IGluIHRoZSBzZWN0aW9uIDQ6PGJyIGNsYXNzPSIiPjxiciBjbGFzcz0iIj7igJwuLiwgdG8gYWxs
b3cgdGhlIHN0YXRlbGVzcyBvcGVyYXRpb24gaW4gYSByZWxheSBjaGFpbiwg4oCm4oCdPGJyIGNs
YXNzPSIiPjxiciBjbGFzcz0iIj50byBtYWtlIHRoZSBtb3RpdmF0aW9uIGNsZWFyIGZvciB0aGlz
IGRoY3B2NiByZWxheSBvcHRpb24uPGJyIGNsYXNzPSIiPjxiciBjbGFzcz0iIj50aGUgcmZjZGlm
ZiBmaWxlIGlzIGF0dGFjaGVkLjxiciBjbGFzcz0iIj48YnIgY2xhc3M9IiI+Q2hlZXJzLDxiciBj
bGFzcz0iIj4tIE5haW1pbmc8YnIgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPjxzcGFuIGlkPSJjaWQ6
NDVFMTYzOTk1MTU0ODM0RkE3MzlBMTNCNzA2MzUyMTZAZW1lYS5jaXNjby5jb20iPiZsdDtkcmFm
dC1pZXRmLWRoYy1yZWxheS1wb3J0LTA2LWZyb20tNS5kaWZmLmh0bWwmZ3Q7PC9zcGFuPjxiciBj
bGFzcz0iIj48YnIgY2xhc3M9IiI+PGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+T24g
SnVsIDIwLCAyMDE3LCBhdCA1OjA4IEFNLCBSYWxmIFdlYmVyICZsdDs8YSBocmVmPSJtYWlsdG86
cmFsZi53ZWJlckBub21pbnVtLmNvbSIgY2xhc3M9IiI+cmFsZi53ZWJlckBub21pbnVtLmNvbTwv
YT4mZ3Q7IHdyb3RlOjxiciBjbGFzcz0iIj48YnIgY2xhc3M9IiI+UmV2aWV3ZXI6IFJhbGYgV2Vi
ZXI8YnIgY2xhc3M9IiI+UmV2aWV3IHJlc3VsdDogUmVhZHkgd2l0aCBOaXRzPGJyIGNsYXNzPSIi
PjxiciBjbGFzcz0iIj5Nb2luITxiciBjbGFzcz0iIj48YnIgY2xhc3M9IiI+SSByZXZpZXdlZCB0
aGlzIGRvY3VtZW50IGFuZCBJJ20gZ29vZCB3aXRoIGl0LiBUaGUgb25seSBtaW5vciBwdXJlbHkg
Y29zbWV0aWM8YnIgY2xhc3M9IiI+bm90ZSBpcyB0aGF0IGl0IHRvb2sgbWUgc29tZSB0aW1lIHRv
IHVuZGVyc3RhbmQgd2h5IHlvdSByZWNvcmQgdGhlIHBvcnQgZm9yIHRoZTxiciBjbGFzcz0iIj5J
UHY2IHJlbGF5IGNoYWluLiBBY2NvcmRpbmcgdG8gYSBkaXNjdXNzaW9uIEkgaGFkIHdpdGggQmVy
bmllIHRoYXQgaXMgdG8gYmU8YnIgY2xhc3M9IiI+YWJsZSB0byBoYXZlIHRoZSBhZ2VudCBzdGF0
ZWxlc3MuIE1heWJlIGFkZCB0aGF0IHRvIHRoZSBtb3RpdmF0aW9uIHdoeSB5b3U8YnIgY2xhc3M9
IiI+c3RvcmUgaXQgaW4gdGhlIHBhY2tldCBhdCB0aGUgZW5kIG9mIHNlY3Rpb24gNCAoLCB0byBh
bGxvdyBzdGF0ZWxlc3Mgb3BlcmF0aW9uPGJyIGNsYXNzPSIiPmluIGEgcmVsYXkgY2hhaW4pPGJy
IGNsYXNzPSIiPjxiciBjbGFzcz0iIj5TbyBsb25nPGJyIGNsYXNzPSIiPi1SYWxmPGJyIGNsYXNz
PSIiPjxiciBjbGFzcz0iIj48YnIgY2xhc3M9IiI+PC9ibG9ja3F1b3RlPjxiciBjbGFzcz0iIj48
L2Rpdj48L2Rpdj48L2Jsb2NrcXVvdGU+PC9kaXY+PGJyIGNsYXNzPSIiPjwvZGl2PjwvYm9keT48
L2h0bWw+

--_005_A5E26208902E41019542B5896342396Eciscocom_--


From nobody Sat Jul 22 13:09:24 2017
Return-Path: <john@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D417112F257 for <ietf@ietfa.amsl.com>; Sat, 22 Jul 2017 13:09:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 8f_KFcYC0_Wk for <ietf@ietfa.amsl.com>; Sat, 22 Jul 2017 13:09:21 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D896127342 for <ietf@ietf.org>; Sat, 22 Jul 2017 13:09:21 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john@jck.com>) id 1dZ0iF-000BQR-F4; Sat, 22 Jul 2017 16:09:19 -0400
Date: Sat, 22 Jul 2017 16:09:13 -0400
From: John C Klensin <john@jck.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
Subject: Re: Revamp of the www.ietf.org website
Message-ID: <3647784F602278ECCBB767BC@PSB>
In-Reply-To: <20170721083215.a2qdgfrpg2jf6irq@mx4.yitter.info>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6394482@GLKXM0002V.GREENLNK.net> <39D1C0A9-DB43-42DD-BD3F-7D636856ECEF@gmail.com> <20170721083215.a2qdgfrpg2jf6irq@mx4.yitter.info>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/n2CBhIrvuMrw0U64pFzMmOSwCrQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Jul 2017 20:09:23 -0000

Andrew,

I very much agree on categories.  My thought had been that, if
we construct an easily-accessed and easily-remembered page for
the second group with a minimum of decoration, images, etc., it
would largely deal with the third issue as a side effect, but
that is probably worth more consideration.

And yes to the effort and consultation -- much appreciated.

   john


--On Friday, July 21, 2017 04:32 -0400 Andrew Sullivan
<ajs@anvilwalrusden.com> wrote:

> Dear colleagues,
> 
> On Tue, Jul 18, 2017 at 11:13:10AM +0200, Yoav Nir wrote:
>> The new site is focused not on the existing people active in
>> the IETF. It's focused on the general public.  The place
>> where work gets done these days is datatracker.
>> 
> 
> I have had a look at the beta site, and it seems to me that we
> have at least three possible audiences:
> 
>     1.  People who wonder what an IETF is and how it might be
> useful     to them.  That actually is an important function of
> a website, and     despite the arguments about how the IETF
> isn't about marketing     organization (and the xkcd
> observations about university websites)     we cannot ignore
> this function.  To some extent, we are competing     with
> other ways of developing the Internet -- "living standards",
> code as standard, multilateral standards bodies, &c -- and if
> we     think our way is good for some cases we do in fact need
> to market     that.  I think the beta site is obviously better
> at that than our     current site, which appears to be
> designed with a MEMBERS ONLY     sign on the front.  We are
> the hardest club to join given that we     don't have
> membership. I think the beta site is trying to make     that
> burden a little less, and I believe it is a good thing.
> 
>     2.  People who already are familiar with the IETF and are
> working     here.  The beta site says it's supposed to be the
> "new front     door".  I don't know about all of you, but in
> my own house I also     know how to enter by the other doors.
> Maybe we just need to use a     different entrance?
> 
>     3.  People whose connectivity makes the more graphically
> intense     and somewhat larger site less useful.  I think it
> would be useful     to analyse the extent to which this is a
> real problem, and whether     the trade-off is adequate for
> the particular use case we have in     mind.  After all,
> loading this (still not huge) web page is hardly     the most
> bandwidth-intensive thing a plausible IETF participant is
> likely to do.  Moreover, it's not clear whether the problem in
>     this case is slow backhaul links or slow local/last-mile
> links; if     it's the latter, more IXes (and CDNs) are likely
> good enough     mitigations.  This seems like an issue that
> could use some     empirical data, but I am not sure how to
> get it.  Perhaps the     participants of GAIA would hae some
> ideas.
> 
> I appreciate the effort to make these changes in public with
> lots of consultation: I know how much harder it is to run a
> project this way, but I think it's a good sign that the tools
> are as usual being developed this way.
> 
> Best regards,
> 
> A





From nobody Sat Jul 22 13:10:19 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FEBD13192B for <ietf@ietfa.amsl.com>; Sat, 22 Jul 2017 13:10:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 qvGh2Z6Y-gjn for <ietf@ietfa.amsl.com>; Sat, 22 Jul 2017 13:10:16 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23284127342 for <ietf@ietf.org>; Sat, 22 Jul 2017 13:10:16 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dZ0j9-000BQc-6t; Sat, 22 Jul 2017 16:10:15 -0400
Date: Sat, 22 Jul 2017 16:10:09 -0400
From: John C Klensin <john-ietf@jck.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
Subject: Re: Revamp of the www.ietf.org website
Message-ID: <ED4162A81564A8647B538005@PSB>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EEqakrJEquKlmlMHkWBcChkcdwA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Jul 2017 20:10:17 -0000

(sorry, sent from wrong address)

Andrew,

I very much agree on categories.  My thought had been that, if
we construct an easily-accessed and easily-remembered page for
the second group with a minimum of decoration, images, etc., it
would largely deal with the third issue as a side effect, but
that is probably worth more consideration.

And yes to the effort and consultation -- much appreciated.

   john


--On Friday, July 21, 2017 04:32 -0400 Andrew Sullivan
<ajs@anvilwalrusden.com> wrote:

> Dear colleagues,
> 
> On Tue, Jul 18, 2017 at 11:13:10AM +0200, Yoav Nir wrote:
>> The new site is focused not on the existing people active in
>> the IETF. It's focused on the general public.  The place
>> where work gets done these days is datatracker.
>> 
> 
> I have had a look at the beta site, and it seems to me that we
> have at least three possible audiences:
> 
>     1.  People who wonder what an IETF is and how it might be
> useful     to them.  That actually is an important function of
> a website, and     despite the arguments about how the IETF
> isn't about marketing     organization (and the xkcd
> observations about university websites)     we cannot ignore
> this function.  To some extent, we are competing     with
> other ways of developing the Internet -- "living standards",
> code as standard, multilateral standards bodies, &c -- and if
> we     think our way is good for some cases we do in fact need
> to market     that.  I think the beta site is obviously better
> at that than our     current site, which appears to be
> designed with a MEMBERS ONLY     sign on the front.  We are
> the hardest club to join given that we     don't have
> membership. I think the beta site is trying to make     that
> burden a little less, and I believe it is a good thing.
> 
>     2.  People who already are familiar with the IETF and are
> working     here.  The beta site says it's supposed to be the
> "new front     door".  I don't know about all of you, but in
> my own house I also     know how to enter by the other doors.
> Maybe we just need to use a     different entrance?
> 
>     3.  People whose connectivity makes the more graphically
> intense     and somewhat larger site less useful.  I think it
> would be useful     to analyse the extent to which this is a
> real problem, and whether     the trade-off is adequate for
> the particular use case we have in     mind.  After all,
> loading this (still not huge) web page is hardly     the most
> bandwidth-intensive thing a plausible IETF participant is
> likely to do.  Moreover, it's not clear whether the problem in
>     this case is slow backhaul links or slow local/last-mile
> links; if     it's the latter, more IXes (and CDNs) are likely
> good enough     mitigations.  This seems like an issue that
> could use some     empirical data, but I am not sure how to
> get it.  Perhaps the     participants of GAIA would hae some
> ideas.
> 
> I appreciate the effort to make these changes in public with
> lots of consultation: I know how much harder it is to run a
> project this way, but I think it's a good sign that the tools
> are as usual being developed this way.
> 
> Best regards,
> 
> A





From nobody Sat Jul 22 13:45:34 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44A28129B25 for <ietf@ietfa.amsl.com>; Sat, 22 Jul 2017 13:45:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 Ix-ypNFcJQDs for <ietf@ietfa.amsl.com>; Sat, 22 Jul 2017 13:45:32 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC8D9126C23 for <ietf@ietf.org>; Sat, 22 Jul 2017 13:45:31 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dZ1HE-000BTP-TP; Sat, 22 Jul 2017 16:45:28 -0400
Date: Sat, 22 Jul 2017 16:45:23 -0400
From: John C Klensin <john-ietf@jck.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>, Brian E Carpenter <brian.e.carpenter@gmail.com>
cc: IETF <ietf@ietf.org>
Subject: Re: Revamp of the www.ietf.org website
Message-ID: <BA491E8D7A457034C73B16BE@PSB>
In-Reply-To: <EMEW3|81bdfca5ec289a124bb7f95d39e55fbey6HB2Y03tjc|ecs.soton.ac.uk|999909C7-70EE-44BD-AC4E-4F07F14E56A4@ecs.soton.ac.uk>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <c9c759cd-2d56-1367-4e42-644b83f46f13@gmail.com> <999909C7-70EE-44BD-AC4E-4F07F14E56A4@ecs.soton.ac.uk> <EMEW3|81bdfca5ec289a124bb7f95d39e55fbey6HB2Y03tjc|ecs.soton.ac.uk|999909C7-70EE-44BD-AC4E-4F07F14E56A4@ecs.soton.ac.uk>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RiGrFoQIRf6QK7xARnsePHKeLv4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Jul 2017 20:45:33 -0000

--On Tuesday, July 18, 2017 11:02 +0100 Tim Chown
<tjc@ecs.soton.ac.uk> wrote:

>> I mention that here because I think it's a very general
>> point. I've entered tickets for some details, and I would
>> encourage everybody to do that, because inevitably there will
>> be errors in content conversion, and the more eyes looking
>> for them, the better.
> 
> The response I got was basically "come and discuss it in
> person in Prague" - the new site designer(s) are here, near
> the registration desk.  It's not clear what feedback is
> sticking, or not :)

Especially for a web page that has to be used by the entire
participant community to do work (independent of whatever other
functions it serves), I am increasingly convinced that we need a
front/home page that is basically and index, which nothing but
(maybe slightly annotated) links.  If we need to have a
marketing- or PR-oriented page (I can see the argument for it
but am not sure I'm convinced), the participant-oriented page
might be at partcipant.ietf.org or even useful.ietf.org, either
of which would pass an "easy to remember" test.

Drawing comments in some other notes together, I think the
criteria for that page should be ability to be rendered in a
single panel on a normal screen (i.e., no scrolling required)
and should strive for zero images and dynamic content or a least
rendering well in a text-only browser.

I don't think the current Datatracker page does that job.
Because it is basically a search page with a sidebar, its use of
screen real estate is very poor for a index-like or
dispatching-like home page (including requiring scrolling) and
when, for example, I'm looking for the membership list and
contact info for the IESG, unlike the sidebar on the current
IETF home page, I have to know to scroll to the bottom, find the
"IESG" link, and then use it to pull up a page than then permits
me to get the the Member list.  IMO, that is a scrolling effort
and several clicks too many.

That is not a criticism of the Datatracker page as such -- I
think it is rather good for its purpose -- only the notion that,
as it currently stands, it is a good approximation to an ideal
home page for getting work done.

Finally, our usual assumption is that the participant list for
the IETF is the union of the number of people who attend
meetings, plus many of most of those on the IETF discussion
list, plus many or most of those on all of the active WG and
former WG lists.  That is a very large number compared to the
set of people who happen to be present in person at give f2f
IETF meeting.  My guess is that even the number of people who,
in the course of a year, contribute to at least one WG mailing
list, review at least one document, or author an I-D is many
times larger than physical meeting attendance.    If I am right
about that, if "come and discuss it in person in Prague" was
actually a response, it is fairly insulting to most of the
community as well as a violation of the spirit of our "decide on
the mailing list" rules.  So I hope that Tim misinterpreted the
response he got and that, whoever the "new site designer(s)"
are, they are following comments on this list very carefully.

    john




From nobody Sat Jul 22 13:51:49 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D3B71318A3 for <ietf@ietfa.amsl.com>; Sat, 22 Jul 2017 13:51:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 Rr-GXqNZ2BGB for <ietf@ietfa.amsl.com>; Sat, 22 Jul 2017 13:51:47 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CC07126C23 for <ietf@ietf.org>; Sat, 22 Jul 2017 13:51:47 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dZ1NJ-000BUP-8P; Sat, 22 Jul 2017 16:51:45 -0400
Date: Sat, 22 Jul 2017 16:51:39 -0400
From: John C Klensin <john-ietf@jck.com>
To: Lee Howard <lee@asgard.org>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
cc: IETF discussion list <ietf@ietf.org>
Subject: Re: Slides, eye charts, and a beg for readability
Message-ID: <41AD9687612065024F02A45A@PSB>
In-Reply-To: <DDAEF38E-E303-4091-B84C-BDDFA5F059D1@asgard.org>
References: <CAKKJt-ehdzREsf3QzGZ+JFOkMm-dGpSdGVFBUJE4BhqWweY+Og@mail.gmail.com> <CAPv4CP8UGr_xLDYW=zKQUP6mXaWgQ67JM+-_NJOvCgfOhXU2hQ@mail.gmail.c om> <CAKKJt-et1SW5J_dU-Bfj=yCKtvVv+sSqzYqh1Sur=NgzA-Mghg@mail.gmail.com> <DDAEF38E-E303-4091-B84C-BDDFA5F059D1@asgard.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bTSFlE-9GWmxguaPhfit6OFeIz0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Jul 2017 20:51:48 -0000

Lee,

I agree, with two qualifications:

(1) That this can be difficult and often doesn't work doesn't
mean we should not try.  To me, that means making sure good
advice is available (even if we have to repeat this thread every
few years and/or add an explicit link about the importance of
good materials and how to make them to the meetings page or even
ubiquitous pester-ware documents like the Note Well).   It may
even be worth encouraging WG Chairs to badger people even if it
doesn't always work.

(2) Because this really is a [dis?]ability issue for some of us,
perhaps it is time for the community to start treating people
who can't be bothered to make slides readable or to submit
materials in advance as being a community problem and make them
candidates for advice and education by the ombusdteam.   I don't
think "unreadable slides" fall into the same category referred
to in some cultures as putting stumbling blocks in the path of
the blind, but it would seem to trend in the same direction.

best,
    john


--On Saturday, July 22, 2017 18:19 +0200 Lee Howard
<lee@asgard.org> wrote:

> I have a talk for the EDU team on presentation skills a couple
> of years ago, and included short, easy notes on slides. Find
> it on their page. 
> 
> Document authors don't reliably send in slides ahead of time,
> even with badgering. They're volunteers; the only thing chairs
> could do would be threaten to yank their slot, which weakens
> the WG's work. 
> 
> Similarly, authors aren't generally bothering to look for
> advice on how the improve their slides. Resources exist.
> Rather, they write notes on pages and consider it done. 
> 
> I think all we can really do is complain about it so this
> meeting's presenters hear about it and do better next time. 





From nobody Sat Jul 22 15:09:42 2017
Return-Path: <aaron.falk@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 828DA128961; Sat, 22 Jul 2017 15:09:35 -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, FREEMAIL_FROM=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 Z6tQVf02HoXz; Sat, 22 Jul 2017 15:09:34 -0700 (PDT)
Received: from mail-qk0-x22d.google.com (mail-qk0-x22d.google.com [IPv6:2607:f8b0:400d:c09::22d]) (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 EC8111200FC; Sat, 22 Jul 2017 15:09:33 -0700 (PDT)
Received: by mail-qk0-x22d.google.com with SMTP id f67so13591858qkc.0; Sat, 22 Jul 2017 15:09:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=75zdtr0vy0m4DKfY0PEhJWQlAI/BKzwJobSk4BeHW80=; b=hb/wVwQbZCrkQtGSoMEyZ3WHznV0gL8l//q+O0D/VjYqlrmblaa8EmXiRQ04Hsrwza QnBzvyIjJGE6njbsaJanqhJofV2Qt/FGuS2C3CWFe+Wl33d3MbQxZ3vDJyaYTso7VCT3 ZKY+p3VWjmggtQqsrObUFuLp+gVN053XIkN/qSCxzV3P6c7OqWXAKqCjaUq2CDgFSM2F NClKuiunMR6tSBxfQekeOsS4a55C8OgDiuNNfyTV6PnfOFuo/i6tixhyd2YbWi20M9FR 7VQSJfJ/X/l9TqngvRdCACNx4IpppJ4uTbjTSIys9uqRIii3QtIZHXzs+OWwj7zTqDHC mILA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=75zdtr0vy0m4DKfY0PEhJWQlAI/BKzwJobSk4BeHW80=; b=RttjxET4zs/VkgrxSQbl9zvsnPT9SoxbpqV+dKAy8shqsh8T1rM0kz+Dp+PT3xq07u frdPCh69ZkeRMbud9EWq1Uaqfsuan5GlVGPK0bChsUgat8aDejxo038qAkiqQpEM98wp VT36ILgcdO7Jm4Po7hQq2bMQHgS/8dE4WUHHfFvpHuNAxaSUPwNXeTtrGx8kuGmXhs32 ULimJ0Vg5KEWWZ+c2srxyIdc8zWsB1ffNnysu759Ley3ni2wR+UfXr1iwuLm6+7u3fX3 Pnc0GbcsHW/8v3o+VUIKDd+vc9M5SmdIWPem9ZQhJu22UK58x5m2tq6hw4pIIvMq9mcG lMPg==
X-Gm-Message-State: AIVw113LtRqTW/gx74T6tKIT1EzkKpdfM+Uq1x5sRmQo2E2g6sZkTSXv OfZlQMIZIF7F9KUIZOQ=
X-Received: by 10.55.53.2 with SMTP id c2mr7099585qka.41.1500761372906; Sat, 22 Jul 2017 15:09:32 -0700 (PDT)
Received: from [172.19.41.13] ([2601:184:4980:a321:a800:83a7:884:ab3e]) by smtp.gmail.com with ESMTPSA id y3sm5432534qkd.36.2017.07.22.15.09.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 22 Jul 2017 15:09:32 -0700 (PDT)
From: "Aaron Falk" <aaron.falk@gmail.com>
To: "IETF Discussion" <ietf@ietf.org>, "99 Attemdees" <99attendees@ietf.org>
Cc: "Tero Kivinen" <kivinen@iki.fi>
Subject: Prague Bad Attitude PechaKucha video
Date: Sat, 22 Jul 2017 18:09:31 -0400
Message-ID: <67311B3E-2908-4701-AF43-366FD5868B0A@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; markup=markdown
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5356)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tV_g2Z75hcx_AAyHQ8F-xO6K9_0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Jul 2017 22:09:36 -0000

http://snaggletooth.akam.ai/Prague-videos/

Thanks to Tero for the video prep!

Thanks to the speakers for some great talks!

—aaron


From nobody Sun Jul 23 04:07:53 2017
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D8CEC129B4C; Sun, 23 Jul 2017 04:07:39 -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-curdle-cms-ecdh-new-curves.all@ietf.org, curdle@ietf.org, ietf@ietf.org
Subject: Genart telechat review of draft-ietf-curdle-cms-ecdh-new-curves-09
X-Test-IDTracker: no
X-IETF-IDTracker: 6.57.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150080805984.31280.7261458746599663122@ietfa.amsl.com>
Date: Sun, 23 Jul 2017 04:07:39 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hTPf_3c1kaIw-KAhkYTFZsCV9wo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Jul 2017 11:07:40 -0000

Reviewer: Roni Even
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-cms-ecdh-new-curves-09
Reviewer: Roni Even
Review Date: 2017-07-23
IETF LC End Date: 2017-05-28
IESG Telechat date: 2017-08-17

Summary: The document is ready for publication as standard track RFC.

Major issues:

Minor issues:

Nits/editorial comments: 



From nobody Sun Jul 23 13:41:29 2017
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CB775129B5B; Sun, 23 Jul 2017 13:41:28 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jouni Korhonen <jouni.nospam@gmail.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-curdle-cms-eddsa-signatures.all@ietf.org, curdle@ietf.org, ietf@ietf.org
Subject: Genart last call review of draft-ietf-curdle-cms-eddsa-signatures-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.57.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150084248880.31306.450946335865671294@ietfa.amsl.com>
Date: Sun, 23 Jul 2017 13:41:28 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3ftt8T95zRIAznECmDBwuFurSWo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Jul 2017 20:41:29 -0000

Reviewer: Jouni Korhonen
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-cms-eddsa-signatures-??
Reviewer: Jouni Korhonen
Review Date: 2017-07-23
IETF LC End Date: 2017-07-25
IESG Telechat date: Not scheduled for a telechat

Summary: Ready to ship. Good that Proto Write-up took care of explaining
downrefs.

Major issues: None.

Minor issues: None.

Nits/editorial comments:  I just have one question whether the use of RFC2119
language in Section 5 Security Considerations is intentional? I mean here that
sometimes e.g. "must" is in lower case and sometimes other keywords are in
upper case e.g. "SHOULD NOT".



From nobody Sun Jul 23 18:35:16 2017
Return-Path: <narellec@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A67E1300CE for <ietf@ietfa.amsl.com>; Sun, 23 Jul 2017 18:35:15 -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, FREEMAIL_FROM=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 ItkpDCciSjzc for <ietf@ietfa.amsl.com>; Sun, 23 Jul 2017 18:35:14 -0700 (PDT)
Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::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 271F112FB9C for <ietf@ietf.org>; Sun, 23 Jul 2017 18:35:14 -0700 (PDT)
Received: by mail-oi0-x22e.google.com with SMTP id x3so9330719oia.1 for <ietf@ietf.org>; Sun, 23 Jul 2017 18:35:14 -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:content-transfer-encoding; bh=SEuX541C2uRbwVahQC0zwCOK5BvuNSnWdHQv+keZpVs=; b=qgR6JaFrct+3Eazck+Z/MtAO2P+0IbTpR2hRbNTiqxKhLM45o2QSi/FQj3NsKkl0Kh RPh+6lsfWGEg/UL80kX6RV9SOTT7PG3C7P6w1kiCI3PCaHaQ6VDWa0s0BReJWeAOsjyh uip/WM4/2QMY3AE36PnNhflfGsyZZcg+3xLKjygAeIBtHVwaIJB+R+4AcBLR3M3rtAQb dKVV6KSnrEyl5j50Q+SI7jePtFq6hlJb+kQQ+HFqQj/V6rGUTQVmzbq+MTbPU7+JtyFk 12UBO+ToNqfCtf+KMoKEQDhwISyfYOn9hJiBPoWawHorqmPFTQLG9QAfO8L2SiUlEL7K S1KA==
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:content-transfer-encoding; bh=SEuX541C2uRbwVahQC0zwCOK5BvuNSnWdHQv+keZpVs=; b=neFIzfa+58TMCZMc8vYUz16Oqgu1/VhuPrELYwQyRoYENfJ4hdvwyhRsmxIPOHL0T2 ybP8QmAi39GbUSC3MRZ0itVSTBHpAgKEbxdm7LZoC1tuO8eeqTGz1Z5mOWEWF7nBBwqO JtIOFgMo2Ak7JsAjaHb/YAy2E+h0ZemzZUqWp1c839tWx0evI6B6SbmgWjY3bLTf+dhf K5aDC4ENJ9g55WiGi+RlpZev9TyBavayBASGtTrG/d3z2au/+xceI+WB8NdSnQWu7Ag+ N3SAVWCEyDfk21jq5yv5he6hqokIlfzwt8Wcf4eJtQaCVUqHvBDwuWh4e87uAvnVDtHV DhGg==
X-Gm-Message-State: AIVw110sgE5XNBEBT1/laDJwZlLLGy5AXgmukUMPjHR/MnReYXr95fEs GEfeAAHQVS/omWvBHbq53vDAxffP6Q==
X-Received: by 10.202.220.195 with SMTP id t186mr5700790oig.111.1500860113579;  Sun, 23 Jul 2017 18:35:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.87.33 with HTTP; Sun, 23 Jul 2017 18:35:13 -0700 (PDT)
In-Reply-To: <41AD9687612065024F02A45A@PSB>
References: <CAKKJt-ehdzREsf3QzGZ+JFOkMm-dGpSdGVFBUJE4BhqWweY+Og@mail.gmail.com> <CAKKJt-et1SW5J_dU-Bfj=yCKtvVv+sSqzYqh1Sur=NgzA-Mghg@mail.gmail.com> <DDAEF38E-E303-4091-B84C-BDDFA5F059D1@asgard.org> <41AD9687612065024F02A45A@PSB>
From: Narelle <narellec@gmail.com>
Date: Mon, 24 Jul 2017 11:35:13 +1000
Message-ID: <CACRMD1GY7O+CMNXi_QwHY3WVYjfuqRbj-PTaq+tP7BisLEYuLw@mail.gmail.com>
Subject: Re: Slides, eye charts, and a beg for readability
To: John C Klensin <john-ietf@jck.com>
Cc: Lee Howard <lee@asgard.org>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>,  IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UiVZ48Bo3T2N7WUnFPGQHvK_HGE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jul 2017 01:35:15 -0000

I'm giving a preso at an upcoming major IEEE conference and they run
training for their speakers, distribute a training pack and template.
Amongst all of that was this guidance:

"=E2=80=A2 10/20/30 Rule
=E2=80=A2 (10 slides - 20 minutes presentation - 30pts font)"

Now it wasn't perfect either and we also had the accessibility
conversation about the colours chosen in the template.

This is just FYI - I'm not expecting the equivalent but food for thought.



--=20


Narelle
narellec@gmail.com


From nobody Sun Jul 23 19:40:13 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15B59131794 for <ietf@ietfa.amsl.com>; Sun, 23 Jul 2017 19:40:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 PHOXgBZaaafi for <ietf@ietfa.amsl.com>; Sun, 23 Jul 2017 19:40:10 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79A75126B7F for <ietf@ietf.org>; Sun, 23 Jul 2017 19:40:10 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dZTI0-000DpQ-43; Sun, 23 Jul 2017 22:40:08 -0400
Date: Sun, 23 Jul 2017 22:40:01 -0400
From: John C Klensin <john-ietf@jck.com>
To: Narelle <narellec@gmail.com>
cc: Lee Howard <lee@asgard.org>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, IETF discussion list <ietf@ietf.org>
Subject: Re: Slides, eye charts, and a beg for readability
Message-ID: <E7D111F0A2CCE3609B8555D5@PSB>
In-Reply-To: <CACRMD1GY7O+CMNXi_QwHY3WVYjfuqRbj-PTaq+tP7BisLEYuLw@mail.gmail.com>
References: <CAKKJt-ehdzREsf3QzGZ+JFOkMm-dGpSdGVFBUJE4BhqWweY+Og@mail.gmail.com> <CAKKJt-et1SW5J_dU-Bfj=yCKtvVv+sSqzYqh1Sur=NgzA-Mghg@mail.gmail.c om> <DDAEF38E-E303-4091-B84C-BDDFA5F059D1@asgard.org> <41AD9687612065024F02A45A@PSB> <CACRMD1GY7O+CMNXi_QwHY3WVYjfuqRbj-PTaq+tP7BisLEYuLw@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/afRKzZcbCTTEeaR1EUmrfSahaVA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jul 2017 02:40:12 -0000

--On Monday, July 24, 2017 11:35 +1000 Narelle
<narellec@gmail.com> wrote:

> I'm giving a preso at an upcoming major IEEE conference and
> they run training for their speakers, distribute a training
> pack and template. Amongst all of that was this guidance:
>=20
> "=E2=80=A2 10/20/30 Rule
> =E2=80=A2 (10 slides - 20 minutes presentation - 30pts font)"
>=20
> Now it wasn't perfect either and we also had the accessibility
> conversation about the colours chosen in the template.
>=20
> This is just FYI - I'm not expecting the equivalent but food
> for thought.

Narelle,

Thanks. IMO helpful.  As another guideline/ rule of thumb, I've
often been told that, if any given slide takes appreciably less
than one minute or more than two to present, something is
probably wrong.  At the lower bound, one is running the slides
too rapidly for the audience to see, read, and absorb what is on
them.  At the upper one, there is probably too much information
(or too much clutter or other "stuff") on the slide.   The
relationship between that rule and "10 slides - 20 minutes
presentation" is probably not a coincidence.  Personally, I
prefer to put less on each slide and run them a little faster --
I would have said 10 slides and 12 to 15 minute presentation --
but it is a bit of a matter of taste, audience, speaking speed
and clarity, etc.

On the other hand, if one treats a more or less standard A4 or
8.5x11 page in landscape orientation as the baseline, 30 point
type allows, depending on the leading (or inter-line spacing)
about 18 lines on the slide.  That would generally be too much,
not because of the type size, but because it allows too much
material to be squeezed in.

best,
    john






From nobody Mon Jul 24 02:10:30 2017
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 104D7131C76 for <ietf@ietfa.amsl.com>; Mon, 24 Jul 2017 02:10:29 -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 fcKdShVnfNlU for <ietf@ietfa.amsl.com>; Mon, 24 Jul 2017 02:10:22 -0700 (PDT)
Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::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 DBADE131C6C for <ietf@ietf.org>; Mon, 24 Jul 2017 02:10:20 -0700 (PDT)
Received: by mail-yw0-x235.google.com with SMTP id h189so19395152ywf.2 for <ietf@ietf.org>; Mon, 24 Jul 2017 02:10:20 -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=23m2SHLltrlHzvf2Egtc4mpB1xBJk8y0XqK7OoNhFMg=; b=UCivQeupeLFGF/sIu27UBwVm+OrYIqlgeRJCWYvU73DWCbPXhbAVuRlLkTuGABEqjt La7wJ4ePkjJGyJMLt8ebrAXChWfPQz6PrxLLO1Dfifj0h+pFFSc1/v5ewoG+L7a59IR/ QLXxd2kj8sA8wtnfEkEKcOXvsuHiTniS72G23bnCUFdOBHw/akyTjPHwUpdjAoaKl0xf zzJOMQYk6SUq1g/zVFuYqz1u7zV6ObjOzVs8IV/CFVXO0zaSgsN6ffgZlUCXCnigmn1/ X11MxOr0/4ZW/hN9MuaUmE09+w5Skih52JOtnXaeLY1SxBRO9ufvt5aOWq41f1ElqzRS P93w==
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=23m2SHLltrlHzvf2Egtc4mpB1xBJk8y0XqK7OoNhFMg=; b=t5fLq6Mb3swplE0j7SNjFut+yqBSYBO7g8l9OeZg/PILT/ZsyAYIUS/i437U557fWG PypRvMgtROJlO+pdSkTDYej2oEkEiOjQNET6khL9hH6e0lQo8TW7fMOPbUZsREd5xTJL keG4yaUCx9MgJPD9MdFyXVMitAoVHe8ayjBMDueeUSlpjFoLwMTIL7WRAIrD9/UGU3ld lFLoOgEziNY4kzG39xOoXHOrk1gxhgWixgMmlM3alsaLJ1d4q1rrLR83u0MqcMI8897Z cqtFxjSiP7pLEaLimY5DDrhXydDlF1YmFXMW9jQvY1HbaWCDZ2nIs4Ktu/kHVPC0ZaW0 UqgQ==
X-Gm-Message-State: AIVw110tIFjuJekewUptYNBqU74R6NxofZGKWEqwuLedW9Ft6Dg3npaI i9W3DdQqvjuCzFBBN/YaFrszdSNdhA==
X-Received: by 10.129.96.85 with SMTP id u82mr5629116ywb.57.1500887419984; Mon, 24 Jul 2017 02:10:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.202.69 with HTTP; Mon, 24 Jul 2017 02:10:19 -0700 (PDT)
Received: by 10.37.202.69 with HTTP; Mon, 24 Jul 2017 02:10:19 -0700 (PDT)
In-Reply-To: <04dbc05e-1c6b-d62c-8d21-6591b3f2d4d5@meetecho.com>
References: <20170720125927.lbmtvwo3dncmoxmb@mx4.yitter.info> <30D585774FDAF7F5158A6A26@PSB> <04dbc05e-1c6b-d62c-8d21-6591b3f2d4d5@meetecho.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 24 Jul 2017 04:10:19 -0500
Message-ID: <CAKKJt-fiG=1hLxDjzBneR0TvDt86ckNNZp=MCZCutXMBOXK4Dg@mail.gmail.com>
Subject: Re: quick observation about remote participation registration
To: Meetecho IETF support <ietf@meetecho.com>
Cc: ietf@ietf.org, Andrew Sullivan <ajs@anvilwalrusden.com>, John C Klensin <john@jck.com>
Content-Type: multipart/alternative; boundary="001a11471de284393605550c9509"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XvPndjaSuFrr84xBDwcbMPzikZs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jul 2017 09:10:29 -0000

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

On Jul 20, 2017 10:47, "Meetecho IETF support" <ietf@meetecho.com> wrote:

the registration code for on-site registrations should simply work in
> Meetecho.
>

It does indeed. Each registered participant (either on-site or remote) can
access Meetecho through their Registration ID.


And this is probably a good place to offer a HUGE thank you for making
"remember me" work for all sessions.

IIRC, it was previously remembering me for the second session of TSVWG, but
I had to provide my registration number for every working group, so I was
only remembered for working groups that had multiple sessions.

In addition to the usages others have mentioned, I'm now routinely doing
Meetecho from the back of the room in a session where I'm sitting, because
the slides are much easier to read, so this was a bigger win for me than
lots of people might guess.

So, thanks much!

Spencer, who has 20/20 vision but sits in the back of some very long,
skinny rooms ...

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

<div dir=3D"auto"><br><div class=3D"gmail_extra" dir=3D"auto"><br><div clas=
s=3D"gmail_quote">On Jul 20, 2017 10:47, &quot;Meetecho IETF support&quot; =
&lt;<a href=3D"mailto:ietf@meetecho.com">ietf@meetecho.com</a>&gt; wrote:<b=
r type=3D"attribution"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"quoted-text">=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
the registration code for on-site registrations should simply work in<br>
Meetecho.<br>
</blockquote>
<br></div>
It does indeed. Each registered participant (either on-site or remote) can =
access Meetecho through their Registration ID.<br></blockquote></div></div>=
<div dir=3D"auto"><br></div><div dir=3D"auto">And this is probably a good p=
lace to offer a HUGE thank you for making &quot;remember me&quot; work for =
all sessions.</div><div dir=3D"auto"><br></div><div dir=3D"auto">IIRC, it w=
as previously remembering me for the second session of TSVWG, but I had to =
provide my registration number for every working group, so I was only remem=
bered for working groups that had multiple sessions.</div><div dir=3D"auto"=
><br></div><div dir=3D"auto">In addition to the usages others have mentione=
d, I&#39;m now routinely doing Meetecho from the back of the room in a sess=
ion where I&#39;m sitting, because the slides are much easier to read, so t=
his was a bigger win for me than lots of people might guess.</div><div dir=
=3D"auto"><br></div><div dir=3D"auto">So, thanks much!</div><div dir=3D"aut=
o"><br></div><div dir=3D"auto">Spencer, who has 20/20 vision but sits in th=
e back of some very long, skinny rooms ...</div><div class=3D"gmail_extra" =
dir=3D"auto"><div class=3D"gmail_quote"><blockquote class=3D"quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"></blockq=
uote></div></div></div>

--001a11471de284393605550c9509--


From nobody Mon Jul 24 09:18:24 2017
Return-Path: <bew@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC07E131E86; Mon, 24 Jul 2017 09:18:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 DLkCvlfBmd_H; Mon, 24 Jul 2017 09:18:14 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 060D6131E7B; Mon, 24 Jul 2017 09:18:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12298; q=dns/txt; s=iport; t=1500913093; x=1502122693; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Z/R+nurg7fXHB8+6zug7NqZLIrc50GSzqeRw1Q4JDfg=; b=VfvdL8BBZHTg17jFbnfxp97Nus+GUYZOAhocg1C4CDH4By7vMGaTfrXy FZPiAsfQIMMa6P+JWgcnN+ucKN8W+/xHuve5tkb6D4RefZofFSY3dxk6H Tgdq2SgN0CmgGkLiyGph1NTaCiVPbEIpPKBKgkjydfn53Kby/pwAU726x Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AgAQBaHXZZ/5BdJa1ZAxoBAQEBAgEBA?= =?us-ascii?q?QEIAQEBAYJva2SBFAeOBZFFIogviCqFLIISLIUbAhqDTj8YAQIBAQEBAQEBayi?= =?us-ascii?q?FGQYjVhACAQgOBisDAgICHxEUEQIEDgWJS0wDFRCvPoImhzENg3UBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEYBYMohS4rC4JugleBZRIBMwkBJoJMMIIxBZdNh0U8Aod?= =?us-ascii?q?Mh2CEcAyCAIVQiluMEIlTAR84fwt1FVsBhwN2AYcxgSOBDgEBAQ?=
X-IronPort-AV: E=Sophos;i="5.40,407,1496102400";  d="scan'208,217";a="276909200"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Jul 2017 16:18:13 +0000
Received: from XCH-RTP-005.cisco.com (xch-rtp-005.cisco.com [64.101.220.145]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id v6OGICiA031466 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 24 Jul 2017 16:18:13 GMT
Received: from xch-rtp-001.cisco.com (64.101.220.141) by XCH-RTP-005.cisco.com (64.101.220.145) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 24 Jul 2017 12:18:12 -0400
Received: from xch-rtp-001.cisco.com ([64.101.220.141]) by XCH-RTP-001.cisco.com ([64.101.220.141]) with mapi id 15.00.1210.000; Mon, 24 Jul 2017 12:18:12 -0400
From: "Brian Weis (bew)" <bew@cisco.com>
To: Roni Even <ron.even.tlv@gmail.com>
CC: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-weis-gdoi-rekey-ack.all@ietf.org" <draft-weis-gdoi-rekey-ack.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Genart last call review of draft-weis-gdoi-rekey-ack-05
Thread-Topic: Genart last call review of draft-weis-gdoi-rekey-ack-05
Thread-Index: AQHS7lLEWzV9+32PME2mgt0Y86IjKaJjlp+A
Date: Mon, 24 Jul 2017 16:18:12 +0000
Message-ID: <E925AA3C-78E8-4081-9FC7-D2C46725A8F3@cisco.com>
References: <149846423732.31797.4914828028458689510@ietfa.amsl.com>
In-Reply-To: <149846423732.31797.4914828028458689510@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.32.172.69]
Content-Type: multipart/alternative; boundary="_000_E925AA3C78E840819FC7D2C46725A8F3ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ziZbERRNxTTVVpbnwu27jBTeHCc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jul 2017 16:18:16 -0000

--_000_E925AA3C78E840819FC7D2C46725A8F3ciscocom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgUm9uaSwNCg0KVGhhbmtzIGZvciB5b3VyIGhlbHBmdWwgcmV2aWV3Lg0KDQpPbiBKdW4gMjYs
IDIwMTcsIGF0IDE6MDMgQU0sIFJvbmkgRXZlbiA8cm9uLmV2ZW4udGx2QGdtYWlsLmNvbTxtYWls
dG86cm9uLmV2ZW4udGx2QGdtYWlsLmNvbT4+IHdyb3RlOg0KDQpSZXZpZXdlcjogUm9uaSBFdmVu
DQpSZXZpZXcgcmVzdWx0OiBBbG1vc3QgUmVhZHkNCg0KSSBhbSB0aGUgYXNzaWduZWQgR2VuLUFS
VCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gVGhlIEdlbmVyYWwgQXJlYQ0KUmV2aWV3IFRlYW0g
KEdlbi1BUlQpIHJldmlld3MgYWxsIElFVEYgZG9jdW1lbnRzIGJlaW5nIHByb2Nlc3NlZA0KYnkg
dGhlIElFU0cgZm9yIHRoZSBJRVRGIENoYWlyLiAgUGxlYXNlIHRyZWF0IHRoZXNlIGNvbW1lbnRz
IGp1c3QNCmxpa2UgYW55IG90aGVyIGxhc3QgY2FsbCBjb21tZW50cy4NCg0KRm9yIG1vcmUgaW5m
b3JtYXRpb24sIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KDQo8aHR0cHM6Ly90cmFjLmlldGYub3Jn
L3RyYWMvZ2VuL3dpa2kvR2VuQXJ0ZmFxPi4NCg0KRG9jdW1lbnQ6IGRyYWZ0LXdlaXMtZ2RvaS1y
ZWtleS1hY2stPz8NClJldmlld2VyOiBSb25pIEV2ZW4NClJldmlldyBEYXRlOiAyMDE3LTA2LTI2
DQpJRVRGIExDIEVuZCBEYXRlOiAyMDE3LTA3LTE3DQpJRVNHIFRlbGVjaGF0IGRhdGU6IE5vdCBz
Y2hlZHVsZWQgZm9yIGEgdGVsZWNoYXQNCg0KU3VtbWFyeToNClRoZSBkb2N1bWVudCBpcyBhbG1v
c3QgcmVhZHkgZm9yIHB1YmxpY2F0aW9uIGFzIHN0YW5kYXJkIHRyYWNrIGRvY3VtZW50DQpNYWpv
ciBpc3N1ZXM6DQoNCk1pbm9yIGlzc3VlczoNCg0KMS4gSW4gc2VjdGlvbiAyIGl0IHNheXMgIkEg
R00gIHJlY2VpdmluZyB0aGUgS0VLX0FDS19SRVFVRVNURUQgYXR0cmlidXRlIGNhbg0KY2hvb3Nl
IHRvIGlnbm9yZSBpdCwgdGh1cyBhcHBlYXJpbmcgYXMgaWYgaXQgZG9lcyBub3Qgc3VwcG9ydCB0
aGUNCktFS19BQ0tfUkVRVUVTVEVEICBhdHRyaWJ1dGUuIi4gQW55IHJlYXNvbiBmb3IgdGhlIEdN
IHRvIGlnbm9yZSB0aGUgbWVzc2FnZT8gMi4NCkluIHNlY3Rpb24gNCBhbmQgc2VjdGlvbiA2IGl0
IHNheXMgdGhlIHRoZSBHTSBTSE9VTEQgc2VuZCBhbiBhY2tub3dsZWRnZW1lbnQNCm1lc3NhZ2Uu
IElzIHRoZXJlIGEgY2FzZSB3aGVuIHRoZSBHTSBzaG91bGQgbm90IHNlbmQgYW5kIGlmIG5vdCB3
aHkgaXMgdGhpcyBhDQpTSE9VTEQgYW5kIG5vdCBhIE1VU1Q/DQoNCkFmdGVyIGNvbmZlcnJpbmcs
IHRoZSBhdXRob3JzIGJlbGlldmUgdGhhdCB0aGUgcmVhbCByZWFzb24gZm9yIGEgR00gdG8gaWdu
b3JlIEtFS19BQ0tfUkVRVUVTVEVEDQppcyBiZWNhdXNlIHRoZXkgZG8gbm90IHN1cHBvcnQgaXQu
IEFzIHN1Y2gsIHdl4oCZdmUgYWRqdXN0ZWQgdGhlIHdvcmRpbmcgaW4gc2V2ZXJhbCBwbGFjZXMg
dG8gc2F5IHRoaXMuDQpBbmQgd2l0aCB0aGF0IHdvcmRpbmcgIGl0IG1ha2VzIHNlbnNlIGZvciB0
aGUgU0hPVUxEIHRvIGJlY29tZSBhIE1VU1QuDQoNCjMuICBJbiBzZWN0aW9uIDYgIkEgbm9uLXJl
Y2VpcHQgb2YgYW4gQWNrbm93bGVkZ2VtZW50IGlzDQphbiBpbmRpY2F0aW9uIHRoYXQgYSBHTSBp
cyAgZWl0aGVyIHVuYWJsZSBvciB1bndpbGxpbmcgIHRvIHJlc3BvbmQiLiAgV2hhdA0KYWJvdXQg
aWYgdGhlIEFja25vd2xlZGdlbWVudCBtZXNzYWdlIHdhcyBsb3N0PyBBbnkgcmVsaWFiaWxpdHkg
cHJvY2VkdXJlPw0KDQpXZeKAmXZlIGNsYXJpZmllZCB0aGF0IHJlbGlhYmlsaXR5IGlzIG1vc3Qg
bGlrZWx5IHRvIGNvbWUgZnJvbSB0cmFuc21pdHRpbmcgdGhlIEdST1VQS0VZLVBVU0ggbWVzc2Fn
ZQ0Kc2V2ZXJhbCB0aW1lcy4gVGhpcyBjb21lcyBmcm9tIGEgcmVjb21tZW5kYXRpb24gaW4gUkZD
IDQwNDYsIGFuZCB3ZeKAmXZlIG1hZGUgdGhpcyBtb3JlIGV4cGxpY2l0Lg0KDQogICAgICBUaGUg
R0NLUyBNQVkgYmUgY29uZmlndXJlZCB3aXRoIGFkZGl0aW9uYWwgcG9saWN5IGFjdGlvbnMgc3Vj
aCBhcw0KICAgICAgdHJhbnNtaXR0aW5nIHRoZSBHUk9VUEtFWS1QVVNIIG1lc3NhZ2Ugc2V2ZXJh
bCB0aW1lcyBpbiBhIHNob3J0DQogICAgICBwZXJpb2Qgb2YgdGltZSAoYXMgc3VnZ2VzdGVkIGlu
IFtSRkM0MDQ2XSksIHdoaWNoIG1pdGlnYXRlcyBhDQogICAgICBwYWNrZXQgbG9zcyBvZiBlaXRo
ZXIgdGhlIEdST1VQS0VZLVBVU0ggbWVzc2FnZSBvciBhbg0KICAgICAgQWNrbm93bGVkZ2VtZW50
IG1lc3NhZ2UuDQoNCg0KTml0cy9lZGl0b3JpYWwgY29tbWVudHM6DQoNCjEuIEluIHNlY3Rpb24g
NiAiQWxzbyBhIEdNIG1heSBiZSAgd2lsbGluZyBvciBhYmxlIHRvIHJlc3BvbmQgd2l0aCBhbg0K
R1JPVVBLRVktUFVTSCBBQ0sgIiAuIEkgY2Fubm90IHBhcnNlIHRoaXMgc2VudGVuY2UgaW4gdGhl
IGNvbnRleHQgb2YgdGhlIHNlY3Rpb24NCg0KVGhlcmUgd2FzIGEg4oCcbm904oCdIG1pc3Npbmcu
IFRoZSBzZW50ZW5jZSBub3cgcmVhZHMNCg0KICAgQWxzbyBhIEdNIG1heSBub3QgYmUgYWJsZSB0
byByZXNwb25kIHdpdGggYW4gR1JPVVBLRVktUFVTSCBBQ0suDQoNCkxldCB1cyBrbm93IGlmIHRo
ZXNlIGRvbuKAmXQgc3VmZmljaWVudGx5IGFkZHJlc3MgeW91ciBwb2ludHMuDQoNClRoYW5rcywN
CkJyaWFuDQotLQ0KQnJpYW4gV2Vpcw0KU2VjdXJpdHksIENTRywgQ2lzY28gU3lzdGVtcw0KVGVs
ZXBob25lOiArMSA0MDggNTI2IDQ3OTYNCkVtYWlsOiBiZXdAY2lzY28uY29tPG1haWx0bzpiZXdA
Y2lzY28uY29tPg0KDQo=

--_000_E925AA3C78E840819FC7D2C46725A8F3ciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <7FCD203DDF0F5346B94334D00D684148@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KSGkgUm9uaSwNCjxkaXYgY2xhc3M9
IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPlRoYW5rcyBmb3IgeW91ciBo
ZWxwZnVsIHJldmlldy48L2Rpdj4NCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPGRpdj4N
CjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj5PbiBKdW4g
MjYsIDIwMTcsIGF0IDE6MDMgQU0sIFJvbmkgRXZlbiAmbHQ7PGEgaHJlZj0ibWFpbHRvOnJvbi5l
dmVuLnRsdkBnbWFpbC5jb20iIGNsYXNzPSIiPnJvbi5ldmVuLnRsdkBnbWFpbC5jb208L2E+Jmd0
OyB3cm90ZTo8L2Rpdj4NCjxiciBjbGFzcz0iQXBwbGUtaW50ZXJjaGFuZ2UtbmV3bGluZSI+DQo8
ZGl2IGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj5SZXZpZXdlcjogUm9uaSBFdmVuPGJyIGNsYXNz
PSIiPg0KUmV2aWV3IHJlc3VsdDogQWxtb3N0IFJlYWR5PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNz
PSIiPg0KSSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4g
VGhlIEdlbmVyYWwgQXJlYTxiciBjbGFzcz0iIj4NClJldmlldyBUZWFtIChHZW4tQVJUKSByZXZp
ZXdzIGFsbCBJRVRGIGRvY3VtZW50cyBiZWluZyBwcm9jZXNzZWQ8YnIgY2xhc3M9IiI+DQpieSB0
aGUgSUVTRyBmb3IgdGhlIElFVEYgQ2hhaXIuICZuYnNwO1BsZWFzZSB0cmVhdCB0aGVzZSBjb21t
ZW50cyBqdXN0PGJyIGNsYXNzPSIiPg0KbGlrZSBhbnkgb3RoZXIgbGFzdCBjYWxsIGNvbW1lbnRz
LjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCkZvciBtb3JlIGluZm9ybWF0aW9uLCBwbGVh
c2Ugc2VlIHRoZSBGQVEgYXQ8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQombHQ7PGEgaHJl
Zj0iaHR0cHM6Ly90cmFjLmlldGYub3JnL3RyYWMvZ2VuL3dpa2kvR2VuQXJ0ZmFxIiBjbGFzcz0i
Ij5odHRwczovL3RyYWMuaWV0Zi5vcmcvdHJhYy9nZW4vd2lraS9HZW5BcnRmYXE8L2E+Jmd0Oy48
YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpEb2N1bWVudDogZHJhZnQtd2Vpcy1nZG9pLXJl
a2V5LWFjay0/PzxiciBjbGFzcz0iIj4NClJldmlld2VyOiBSb25pIEV2ZW48YnIgY2xhc3M9IiI+
DQpSZXZpZXcgRGF0ZTogMjAxNy0wNi0yNjxiciBjbGFzcz0iIj4NCklFVEYgTEMgRW5kIERhdGU6
IDIwMTctMDctMTc8YnIgY2xhc3M9IiI+DQpJRVNHIFRlbGVjaGF0IGRhdGU6IE5vdCBzY2hlZHVs
ZWQgZm9yIGEgdGVsZWNoYXQ8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpTdW1tYXJ5Ojxi
ciBjbGFzcz0iIj4NClRoZSBkb2N1bWVudCBpcyBhbG1vc3QgcmVhZHkgZm9yIHB1YmxpY2F0aW9u
IGFzIHN0YW5kYXJkIHRyYWNrIGRvY3VtZW50PGJyIGNsYXNzPSIiPg0KTWFqb3IgaXNzdWVzOjxi
ciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCk1pbm9yIGlzc3Vlczo8YnIgY2xhc3M9IiI+DQo8
YnIgY2xhc3M9IiI+DQoxLiBJbiBzZWN0aW9uIDIgaXQgc2F5cyAmcXVvdDtBIEdNICZuYnNwO3Jl
Y2VpdmluZyB0aGUgS0VLX0FDS19SRVFVRVNURUQgYXR0cmlidXRlIGNhbjxiciBjbGFzcz0iIj4N
CmNob29zZSB0byBpZ25vcmUgaXQsIHRodXMgYXBwZWFyaW5nIGFzIGlmIGl0IGRvZXMgbm90IHN1
cHBvcnQgdGhlPGJyIGNsYXNzPSIiPg0KS0VLX0FDS19SRVFVRVNURUQgJm5ic3A7YXR0cmlidXRl
LiZxdW90Oy4gQW55IHJlYXNvbiBmb3IgdGhlIEdNIHRvIGlnbm9yZSB0aGUgbWVzc2FnZT8gMi48
YnIgY2xhc3M9IiI+DQpJbiBzZWN0aW9uIDQgYW5kIHNlY3Rpb24gNiBpdCBzYXlzIHRoZSB0aGUg
R00gU0hPVUxEIHNlbmQgYW4gYWNrbm93bGVkZ2VtZW50PGJyIGNsYXNzPSIiPg0KbWVzc2FnZS4g
SXMgdGhlcmUgYSBjYXNlIHdoZW4gdGhlIEdNIHNob3VsZCBub3Qgc2VuZCBhbmQgaWYgbm90IHdo
eSBpcyB0aGlzIGE8YnIgY2xhc3M9IiI+DQpTSE9VTEQgYW5kIG5vdCBhIE1VU1Q/IDwvZGl2Pg0K
PC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2PjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdj4N
CjxkaXY+QWZ0ZXIgY29uZmVycmluZywgdGhlIGF1dGhvcnMgYmVsaWV2ZSB0aGF0IHRoZSByZWFs
IHJlYXNvbiBmb3IgYSBHTSB0byBpZ25vcmUgS0VLX0FDS19SRVFVRVNURUQ8L2Rpdj4NCjxkaXY+
aXMgYmVjYXVzZSB0aGV5IGRvIG5vdCBzdXBwb3J0IGl0LiBBcyBzdWNoLCB3ZeKAmXZlIGFkanVz
dGVkIHRoZSB3b3JkaW5nIGluIHNldmVyYWwgcGxhY2VzIHRvIHNheSB0aGlzLiZuYnNwOzwvZGl2
Pg0KPGRpdj5BbmQgd2l0aCB0aGF0IHdvcmRpbmcgJm5ic3A7aXQgbWFrZXMgc2Vuc2UgZm9yIHRo
ZSBTSE9VTEQgdG8gYmVjb21lIGEgTVVTVC48L2Rpdj4NCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNz
PSIiPg0KPC9kaXY+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPg0K
PGRpdiBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+My4gJm5ic3A7SW4gc2VjdGlvbiA2ICZxdW90
O0Egbm9uLXJlY2VpcHQgb2YgYW4gQWNrbm93bGVkZ2VtZW50IGlzPGJyIGNsYXNzPSIiPg0KYW4g
aW5kaWNhdGlvbiB0aGF0IGEgR00gaXMgJm5ic3A7ZWl0aGVyIHVuYWJsZSBvciB1bndpbGxpbmcg
Jm5ic3A7dG8gcmVzcG9uZCZxdW90Oy4gJm5ic3A7V2hhdDxiciBjbGFzcz0iIj4NCmFib3V0IGlm
IHRoZSBBY2tub3dsZWRnZW1lbnQgbWVzc2FnZSB3YXMgbG9zdD8gQW55IHJlbGlhYmlsaXR5IHBy
b2NlZHVyZT88YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRp
dj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXY+V2XigJl2ZSBjbGFyaWZpZWQgdGhhdCByZWxp
YWJpbGl0eSBpcyBtb3N0IGxpa2VseSB0byBjb21lIGZyb20gdHJhbnNtaXR0aW5nIHRoZSBHUk9V
UEtFWS1QVVNIIG1lc3NhZ2U8L2Rpdj4NCjxkaXY+c2V2ZXJhbCB0aW1lcy4gVGhpcyBjb21lcyBm
cm9tIGEgcmVjb21tZW5kYXRpb24gaW4gUkZDIDQwNDYsIGFuZCB3ZeKAmXZlIG1hZGUgdGhpcyBt
b3JlIGV4cGxpY2l0LjwvZGl2Pg0KPGRpdj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXY+DQo8
ZGl2IHN0eWxlPSJtYXJnaW46IDBweDsgZm9udC1zaXplOiAxMXB4OyBsaW5lLWhlaWdodDogbm9y
bWFsOyBmb250LWZhbWlseTogTWVubG87IGJhY2tncm91bmQtY29sb3I6IHJnYigyNTUsIDI1NSwg
MjU1KTsiIGNsYXNzPSIiPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgVGhlJm5ic3A7R0NLUyBNQVkg
YmUgY29uZmlndXJlZCB3aXRoIGFkZGl0aW9uYWwgcG9saWN5IGFjdGlvbnMgc3VjaCBhczwvZGl2
Pg0KPGRpdiBzdHlsZT0ibWFyZ2luOiAwcHg7IGZvbnQtc2l6ZTogMTFweDsgbGluZS1oZWlnaHQ6
IG5vcm1hbDsgZm9udC1mYW1pbHk6IE1lbmxvOyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2IoMjU1LCAy
NTUsIDI1NSk7IiBjbGFzcz0iIj4NCjxzcGFuIHN0eWxlPSJmb250LXZhcmlhbnQtbGlnYXR1cmVz
OiBuby1jb21tb24tbGlnYXR1cmVzIiBjbGFzcz0iIj4mbmJzcDsgJm5ic3A7ICZuYnNwOyB0cmFu
c21pdHRpbmcgdGhlIEdST1VQS0VZLVBVU0ggbWVzc2FnZSBzZXZlcmFsIHRpbWVzIGluIGEgc2hv
cnQ8L3NwYW4+PC9kaXY+DQo8ZGl2IHN0eWxlPSJtYXJnaW46IDBweDsgZm9udC1zaXplOiAxMXB4
OyBsaW5lLWhlaWdodDogbm9ybWFsOyBmb250LWZhbWlseTogTWVubG87IGJhY2tncm91bmQtY29s
b3I6IHJnYigyNTUsIDI1NSwgMjU1KTsiIGNsYXNzPSIiPg0KPHNwYW4gc3R5bGU9ImZvbnQtdmFy
aWFudC1saWdhdHVyZXM6IG5vLWNvbW1vbi1saWdhdHVyZXMiIGNsYXNzPSIiPiZuYnNwOyAmbmJz
cDsgJm5ic3A7IHBlcmlvZCBvZiB0aW1lIChhcyBzdWdnZXN0ZWQgaW4gW1JGQzQwNDZdKSwgd2hp
Y2ggbWl0aWdhdGVzIGE8L3NwYW4+PC9kaXY+DQo8ZGl2IHN0eWxlPSJtYXJnaW46IDBweDsgZm9u
dC1zaXplOiAxMXB4OyBsaW5lLWhlaWdodDogbm9ybWFsOyBmb250LWZhbWlseTogTWVubG87IGJh
Y2tncm91bmQtY29sb3I6IHJnYigyNTUsIDI1NSwgMjU1KTsiIGNsYXNzPSIiPg0KPHNwYW4gc3R5
bGU9ImZvbnQtdmFyaWFudC1saWdhdHVyZXM6IG5vLWNvbW1vbi1saWdhdHVyZXMiIGNsYXNzPSIi
PiZuYnNwOyAmbmJzcDsgJm5ic3A7IHBhY2tldCBsb3NzIG9mIGVpdGhlciB0aGUgR1JPVVBLRVkt
UFVTSCBtZXNzYWdlIG9yIGFuPC9zcGFuPjwvZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luOiAwcHg7
IGZvbnQtc2l6ZTogMTFweDsgbGluZS1oZWlnaHQ6IG5vcm1hbDsgZm9udC1mYW1pbHk6IE1lbmxv
OyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2IoMjU1LCAyNTUsIDI1NSk7IiBjbGFzcz0iIj4NCjxzcGFu
IHN0eWxlPSJmb250LXZhcmlhbnQtbGlnYXR1cmVzOiBuby1jb21tb24tbGlnYXR1cmVzIiBjbGFz
cz0iIj4mbmJzcDsgJm5ic3A7ICZuYnNwOyBBY2tub3dsZWRnZW1lbnQgbWVzc2FnZS4mbmJzcDs8
L3NwYW4+PC9kaXY+DQo8L2Rpdj4NCjxkaXY+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8YmxvY2tx
dW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSIi
PjxiciBjbGFzcz0iIj4NCk5pdHMvZWRpdG9yaWFsIGNvbW1lbnRzOjxiciBjbGFzcz0iIj4NCjxi
ciBjbGFzcz0iIj4NCjEuIEluIHNlY3Rpb24gNiAmcXVvdDtBbHNvIGEgR00gbWF5IGJlICZuYnNw
O3dpbGxpbmcgb3IgYWJsZSB0byByZXNwb25kIHdpdGggYW48YnIgY2xhc3M9IiI+DQpHUk9VUEtF
WS1QVVNIIEFDSyAmcXVvdDsgLiBJIGNhbm5vdCBwYXJzZSB0aGlzIHNlbnRlbmNlIGluIHRoZSBj
b250ZXh0IG9mIHRoZSBzZWN0aW9uPGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxv
Y2txdW90ZT4NCjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdj5UaGVyZSB3YXMgYSDigJxub3Ti
gJ0gbWlzc2luZy4gVGhlIHNlbnRlbmNlIG5vdyByZWFkczwvZGl2Pg0KPGRpdj48YnIgY2xhc3M9
IiI+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJtYXJnaW46IDBweDsgZm9udC1zaXplOiAx
MXB4OyBsaW5lLWhlaWdodDogbm9ybWFsOyBmb250LWZhbWlseTogTWVubG87IGJhY2tncm91bmQt
Y29sb3I6IHJnYigyNTUsIDI1NSwgMjU1KTsiIGNsYXNzPSIiPg0KPHNwYW4gc3R5bGU9ImZvbnQt
dmFyaWFudC1saWdhdHVyZXM6IG5vLWNvbW1vbi1saWdhdHVyZXMiIGNsYXNzPSIiPiZuYnNwOyAm
bmJzcDtBbHNvIGEgR00gbWF5IG5vdCBiZSZuYnNwOzwvc3Bhbj5hYmxlIHRvIHJlc3BvbmQgd2l0
aCBhbiBHUk9VUEtFWS1QVVNIIEFDSy48L2Rpdj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj48YnIg
Y2xhc3M9IndlYmtpdC1ibG9jay1wbGFjZWhvbGRlciI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+
TGV0IHVzIGtub3cgaWYgdGhlc2UgZG9u4oCZdCBzdWZmaWNpZW50bHkgYWRkcmVzcyB5b3VyIHBv
aW50cy48L2Rpdj4NCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNs
YXNzPSIiPlRoYW5rcyw8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+QnJpYW48L2Rpdj4NCjxkaXYgY2xh
c3M9IiI+LS0mbmJzcDs8YnIgY2xhc3M9IiI+DQpCcmlhbiBXZWlzPGJyIGNsYXNzPSIiPg0KU2Vj
dXJpdHksIENTRywgQ2lzY28gU3lzdGVtczxiciBjbGFzcz0iIj4NClRlbGVwaG9uZTogJiM0Mzsx
IDQwOCA1MjYgNDc5NjxiciBjbGFzcz0iIj4NCkVtYWlsOiA8YSBocmVmPSJtYWlsdG86YmV3QGNp
c2NvLmNvbSIgY2xhc3M9IiI+YmV3QGNpc2NvLmNvbTwvYT4gPC9kaXY+DQo8YnIgY2xhc3M9IiI+
DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_E925AA3C78E840819FC7D2C46725A8F3ciscocom_--


From nobody Mon Jul 24 09:46:41 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BDFD131EA4; Mon, 24 Jul 2017 09:46:40 -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-nottingham-rfc5988bis.all@ietf.org, ietf@ietf.org
Subject: Genart telechat review of draft-nottingham-rfc5988bis-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.57.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150091480039.32033.9560029294818045836@ietfa.amsl.com>
Date: Mon, 24 Jul 2017 09:46:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JoCI-TTi-Z2IwRojA8MKXarP4bU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jul 2017 16:46:40 -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 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-nottingham-rfc5988bis-07
Reviewer: Stewart Bryant
Review Date: 2017-07-24
IETF LC End Date: 2017-05-26
IESG Telechat date: 2017-08-03

Summary: Ready except for some confusing IANA text - please see below.

Major issues: None

Minor issues: None

Nits/editorial comments: 

I find the following text very confusing:

   IANA will direct any incoming requests regarding the registry to this
   document and, if defined, the processes established by the expert(s);
   typically, this will mean referring them to the registry Web page.
   Note that the expert(s) are allowed (as per Section 2.1.1.1) to
   define additional fields to be collected in the registry.

You cannot direct a request to a document, and I am not sure you collect things
in registry. It would be useful to take another look at the above text.





From nobody Mon Jul 24 13:56:45 2017
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6B52129AF9 for <ietf@ietfa.amsl.com>; Mon, 24 Jul 2017 13:56:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-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=yitter.info header.b=Aw8yiTbc; dkim=pass (1024-bit key) header.d=yitter.info header.b=eA0HD4Z+
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 0xvT8fo2C9Wg for <ietf@ietfa.amsl.com>; Mon, 24 Jul 2017 13:56:42 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23786131F20 for <ietf@ietf.org>; Mon, 24 Jul 2017 13:56:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id D0F18BE6F3 for <ietf@ietf.org>; Mon, 24 Jul 2017 20:56:09 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1500929769; bh=CP6vBISDaCFBjxV0JjNxCTzPZ/0n17MxHCVinzZGLwQ=; h=Date:From:To:Subject:References:In-Reply-To:From; b=Aw8yiTbcGOURD6IBv6Z9uIunR8B6L6ZblMzLV7u1vS8/fpd1K7chYLQ2+PA2dffqv /F18mbbzGdn40V/Nfxr0XBxmy4XNIDr3TxLZ2+a4wWDoGMySprOpdIo9U05AjMO5Zb GwG+FZbNQCzRyG7yK7DKn5eX7Sa6n6CjXS6FGvcE=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GF6UIoqfWtn4 for <ietf@ietf.org>; Mon, 24 Jul 2017 20:56:08 +0000 (UTC)
Date: Mon, 24 Jul 2017 16:56:08 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1500929768; bh=CP6vBISDaCFBjxV0JjNxCTzPZ/0n17MxHCVinzZGLwQ=; h=Date:From:To:Subject:References:In-Reply-To:From; b=eA0HD4Z+xF17PnIK/nTZC+BjzKu8hNR35lmmAgdWxZORtvbYRFo9YT7msqgmJWXCA hG9YTObaKSL9RvDvO4xbwnzuMV9GNXqAlSc6YkreBYHPvjwlXfhJ6vNok3X3OmZuR1 rG8O0jlQsnpMIfEkauJsXW/cJ9KMws7Njp1c4psg=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: More and more virtual interims
Message-ID: <20170724205608.gasg56ifeqz3wlci@mx4.yitter.info>
References: <876859E45DFE49F23C5AD313@PSB> <20170720131527.e4bcjsry623leeih@mx4.yitter.info> <6824.1500635845@dooku.sandelman.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6824.1500635845@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fNc5CKthH-cM9Rl3jo0vV-skESg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jul 2017 20:56:44 -0000

On Fri, Jul 21, 2017 at 01:17:25PM +0200, Michael Richardson wrote:
> 
> Can you explain "time boxes" here?

"Time box" is the (admittedly inelegant) jargon that proponents of
certain agile software development methodologies use to describe a
period in which active development + other stuff happens.  This is
sometimes called the "sprint", but it's not only that of course since
that's usually coding and such like.  The whole group does all the
stuff it does for a period inside the "time box".  This is often a
period of two or three weeks, though I've seen groups that do as much
as six. The idea is that, within the period in question, a group
focusses only on certain things and everything else is set aside.

Setting the jargon aside for a moment, the point is that instead of
having a WG interim in which everyone has to interrupt their circadian
rhythm, the WG instead decides that (say) the WG is going to hammer
out the issues on $draft between (say) Tues and Thurs of next week.
The jabber room is open and active and issues are rapidly taken up
from the tracker and knocked down, and then an interim consensus call
can be done on (say) Friday.  There could also be some sort of voice
channel up and available, I suppose, if people wanted to join it _ad
hoc_ to sort something out. It's more async and therefore there'll be
more mail and jabber back and forth, and maybe someone will come to
the discussion later and be annoyed that his or her deathless prose was
mangled, but it's still a way of working rapidly but async in keeping
with the geographic distribution.  I have seen free software projects
have success with this sort of thing, so it is possible to do it,
though it requires that all participants rely really a lot on the
principle of charity and are super polite and nice in their emails.
So it might not work here.  But it might be worth a go to see whether
it could produce results.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Mon Jul 24 14:02:54 2017
Return-Path: <linuxwolf+ietf@outer-planes.net>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 61F18131F20; Mon, 24 Jul 2017 14:02:39 -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
Subject: Genart last call review of draft-ietf-curdle-ssh-ext-info-10
X-Test-IDTracker: no
X-IETF-IDTracker: 6.57.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150093015937.32021.12465797358778837950@ietfa.amsl.com>
Date: Mon, 24 Jul 2017 14:02:39 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CfXE2iRAqt61aBVyqBESgRhrj3s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jul 2017 21:02:39 -0000

Reviewer: Matthew Miller
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-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

Summary:

This document is ready with an issue.

I found this document very coherent and easy to follow.

Major issues:

Minor issues:

My only issue borders on nit, but sided with nit as I can see it
potentially causing confusion for an implementer in the future.

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.

Nits/editorial comments:

* RFC 5226 is referenced by this document, but is obsoleted by RFC 8126.



From nobody Mon Jul 24 14:03:37 2017
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF128131F20 for <ietf@ietfa.amsl.com>; Mon, 24 Jul 2017 14:03:34 -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] 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 Fu9B3iD2YBIU for <ietf@ietfa.amsl.com>; Mon, 24 Jul 2017 14:03:33 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 918B2129AA8 for <ietf@ietf.org>; Mon, 24 Jul 2017 14:03:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 7EB8C300572 for <ietf@ietf.org>; Mon, 24 Jul 2017 16:58:00 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id tRpOMP4SUGK4 for <ietf@ietf.org>; Mon, 24 Jul 2017 16:57:58 -0400 (EDT)
Received: from a860b60074bd.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id A719F300288; Mon, 24 Jul 2017 16:57:58 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Genart last call review of draft-ietf-curdle-cms-eddsa-signatures-06
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <150084248880.31306.450946335865671294@ietfa.amsl.com>
Date: Mon, 24 Jul 2017 16:57:58 -0400
Cc: IETF Gen-ART <gen-art@ietf.org>, curdle <curdle@ietf.org>, IETF <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <88C7C6F9-FBD3-402A-B174-02C44D9D0092@vigilsec.com>
References: <150084248880.31306.450946335865671294@ietfa.amsl.com>
To: Jouni Korhonen <jouni.nospam@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1jI5FOW4OFWJ9C15whxABVd-7mM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jul 2017 21:03:35 -0000

Jouni:

Thanks for the review.

> Reviewer: Jouni Korhonen
> Review result: Ready
>=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-cms-eddsa-signatures-??
> Reviewer: Jouni Korhonen
> Review Date: 2017-07-23
> IETF LC End Date: 2017-07-25
> IESG Telechat date: Not scheduled for a telechat
>=20
> Summary: Ready to ship. Good that Proto Write-up took care of =
explaining
> downrefs.
>=20
> Major issues: None.
>=20
> Minor issues: None.
>=20
> Nits/editorial comments:  I just have one question whether the use of =
RFC2119
> language in Section 5 Security Considerations is intentional? I mean =
here that
> sometimes e.g. "must" is in lower case and sometimes other keywords =
are in
> upper case e.g. "SHOULD NOT".

Looking through the paragraphs in Section 5...

Paragraph 1: The use of "must" and "may" are intentional.  These are =
needed for security, but they do not impact interoperability.

Paragraph 2: The use of "may" is intentional.  It is a statement about =
what an attacker may do; it has no impact on interoperability.

Paragraph 4: It uses "SHOULD NOT"

Paragraph 5: In my edit buffer, I have changed "should" to "SHOULD".

Russ


From nobody Mon Jul 24 16:14:09 2017
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FCCE127078; Mon, 24 Jul 2017 16:14:08 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Ines Robles <mariainesrobles@googlemail.com>
To: <rtg-dir@ietf.org>
Cc: i2rs@ietf.org, ietf@ietf.org, draft-ietf-i2rs-yang-network-topo.all@ietf.org, rtg-ads@ietf.org
Subject: Rtgdir last call review of draft-ietf-i2rs-yang-network-topo-14
X-Test-IDTracker: no
X-IETF-IDTracker: 6.57.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150093804800.26111.1394410974752858089@ietfa.amsl.com>
Date: Mon, 24 Jul 2017 16:14:08 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/a_zcEhehp-37FJe_XgMqoPw-OpE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jul 2017 23:14:08 -0000

Reviewer: Ines Robles
Review result: Has Issues

Hello,

I have been selected as the Routing Directorate reviewer for this draft. The
Routing Directorate seeks to review all routing or routing-related drafts as
they pass through IETF last call and IESG review, and sometimes on special
request. The purpose of the review is to provide assistance to the Routing ADs.
For more information about the Routing Directorate, please see
​http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir

Although these comments are primarily for the use of the Routing ADs, it would
be helpful if you could consider them along with any other IETF Last Call
comments that you receive, and strive to resolve them through discussion or by
updating the draft.

Document: draft-ietf-i2rs-yang-network-topo-14.txt
Reviewer: Ines Robles
Review Date: 07-25-2017
Intended status: Standards Track

Summary:
I have some minor concerns about this document that I think should be resolved
before publication.

Comments:

I believe the draft is technically good. This document is well written and
clear to understand. The figures are clear and helpful.

Major Issues:

No major issues found.

Minor Issues:

Since this document specifies a data model, I would include some text related
to the Information Model [RFC 3444]. How would it be in this context?

1- Section 1

  1.a following Figure 1 (Page 4):

    I would add in the figure the corresponding section that explain the
    module. e.g. Abstract Network Model, I would add in the figure "Abstract
    (base) Network Model" and "section 4.1". The same for "Abstract Topology
    Model", should it be section 4.2?

  1.b -following Figure 2 (Page 5):

      1.b.1- " X1 and X2 - mapping onto... ",  I think it would be "X1 and X3
      mapping onto..."

      1.b.2- " a single L3 network element", I would add in this case (Y2) "a
      single L3 (Y2) network element", the same for "The figure shows a single
      "L3" network element mapped onto multiple "Optical" network elements.", I
      would add "The figure shows a single "L3" network element (Y2) mapped
      onto multiple "Optical" network elements [Z] and [Z1]."

      1.b.3- I would expand ROADMs --> Reconfigurable Optical Add/Drop
      Multiplexers (ROADMs)

2- Section 2:

  2.1- I would add a reference to RFC 6020, since the document uses terminology
  e.g container, augment, etc. which are defined in 6020. Even if this RFC is
  mentioned in the normative reference, still I would add it here as well.

3- Section 3:

  3.1-  ReST is mentioned here but not in the rest of the draft, is this
  correct?

Nits:

1- Pag. 18: is that correct?: "(a string is a string is a string)"

2- pag. 34: I would expand NMS -> NMS (Network Management System)

3- pag. 34: I would add a definition about TE Topology : "TE-Topology: The TE
Topology is a schematic arrangement of TE nodes
   and TE links in a given TED. It forms the basis for a graph suitable
   for TE path computations."
   [https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-12]

4- pag. 34: topoogical -> topological

5- pag 35: "uber-network device" -> over-network device?

Thanks,

Ines.



From nobody Mon Jul 24 16:45:33 2017
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADDDB124C27; Mon, 24 Jul 2017 16:45:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 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_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=mnot.net header.b=W/ZsqHmg; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=nSTMahvI
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 nyJIoMP3U_Cj; Mon, 24 Jul 2017 16:45:28 -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 BFF5F126C23; Mon, 24 Jul 2017 16:45:25 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 391EA2232E; Mon, 24 Jul 2017 19:45:25 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Mon, 24 Jul 2017 19:45:25 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; 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=64zN/CeIPkEELJO45y DMCUmdet+6/iQ94xpEaq7iAyI=; b=W/ZsqHmgDsCMoaqWa2fM03zqME4DUIdDoR c5xks7Og/byiww0iU8Is8Q+OfHoKn5UeATXLTvJiTBQ3xsaUWZYuDhDW+Tjm4a5g jde6+d08tf/uhqYgjGb4LkWOvc8tV/3rEBYPvdynYcVecSwJlPzxlONu+6g4wlI9 eHjL1pxgRBdDpZZpQKS9wQ8WCv13xcga+/BYSNEoMhQZb6wxaZk13XD6t3R97jEl EFx28vbD8PWoK/ZnMFadZSy8FWQF5b2jVy+PwuYHVSiw1vjdpOodkZBOUlvfx3DL uvx12hcbf3XQ4dKwWrFlNmWIZ/ol5Kp+5f9yW+C6nKn9Q1Rpcc0A==
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=64zN/CeIPkEELJO45yDMCUmdet+6/iQ94xpEaq7iAyI=; b=nSTMahvI f5QAOHE2/rMdIPwhjDm6x4PrmX+pPNqX861O3DvAlVBSA32BfbiiY9bHQjr/ianY bMzfIB44alJXeIIYjhAQbyx7hQ7g0UslzURiFBKJDejV0oo25fY98qJnKC49YfYm gOuHsNdvYOuMRZsFC0vq94PgSd9k4SYrjV6VVJOtcWrRX70TwhWWSiHLPin6hCUK vAuEO4aIsnpfDv+hi1CbcL/YIEtL2QrvBLMmkhSBKitG18o/FHgSGSAdsnVHYpPI CS4Q1Q6k4llcns1AqqkVnt5VqrYxg44uyGEvgyM2zDYck3gooYVyK4pKPCEuhBOX lo/VkMHzq+thog==
X-ME-Sender: <xms:lYZ2WWFChQCa2iP0Qw3_q30rgt_rIcg885TH_h7WMczc7mZRc11YUw>
X-Sasl-enc: TyuHwUf6PY4ihw5t2KDiY9a1vDWS7UyQ/2Lu/bWiD2fd 1500939924
Received: from [192.168.1.18] (cpe-124-188-19-231.hdbq1.win.bigpond.net.au [124.188.19.231]) by mail.messagingengine.com (Postfix) with ESMTPA id B8A7B7E2DE; Mon, 24 Jul 2017 19:45:23 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Genart telechat review of draft-nottingham-rfc5988bis-07
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <150091480039.32033.9560029294818045836@ietfa.amsl.com>
Date: Tue, 25 Jul 2017 09:45:22 +1000
Cc: gen-art@ietf.org, draft-nottingham-rfc5988bis.all@ietf.org, ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <6B30F79C-81F8-4D68-8998-38305995B7AE@mnot.net>
References: <150091480039.32033.9560029294818045836@ietfa.amsl.com>
To: Stewart Bryant <stewart.bryant@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XxvRuSswHmrJnRL5kdap-FtarL8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jul 2017 23:45:32 -0000

Hi Stewart,

Thanks for that. That part of IANA considerations is gone, after some =
consultation with IANA in Prague.

Cheers,


> On 25 Jul 2017, at 2:46 am, Stewart Bryant <stewart.bryant@gmail.com> =
wrote:
>=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 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-nottingham-rfc5988bis-07
> Reviewer: Stewart Bryant
> Review Date: 2017-07-24
> IETF LC End Date: 2017-05-26
> IESG Telechat date: 2017-08-03
>=20
> Summary: Ready except for some confusing IANA text - please see below.
>=20
> Major issues: None
>=20
> Minor issues: None
>=20
> Nits/editorial comments:=20
>=20
> I find the following text very confusing:
>=20
>   IANA will direct any incoming requests regarding the registry to =
this
>   document and, if defined, the processes established by the =
expert(s);
>   typically, this will mean referring them to the registry Web page.
>   Note that the expert(s) are allowed (as per Section 2.1.1.1) to
>   define additional fields to be collected in the registry.
>=20
> You cannot direct a request to a document, and I am not sure you =
collect things
> in registry. It would be useful to take another look at the above =
text.
>=20
>=20
>=20
>=20

--
Mark Nottingham   https://www.mnot.net/


From nobody Mon Jul 24 18:13:34 2017
Return-Path: <volz@cisco.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D915D1201F8; Mon, 24 Jul 2017 18:13:26 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Bernie Volz <volz@cisco.com>
To: <int-dir@ietf.org>
Cc: lwip@ietf.org, ietf@ietf.org, draft-ietf-lwig-energy-efficient.all@ietf.org
Subject: Intdir early review of draft-ietf-lwig-energy-efficient-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.57.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150094520677.26176.17525876529879529582@ietfa.amsl.com>
Date: Mon, 24 Jul 2017 18:13:26 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JJQhY14E0ATp1gpHPKJ5iYVEe8I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jul 2017 01:13:27 -0000

Reviewer: Bernie Volz
Review result: Ready with Nits

I am an assigned INT directorate early reviewer for
draft-ietf-lwig-energy-efficient-07. These comments were written primarily for
the benefit of the Internet Area Directors.

Document editors and shepherd(s) should treat these comments just like they
would treat comments from any other IETF contributors and resolve them along
with any other comments that have been received. For more details on the INT
Directorate, see http://www.ietf.org/iesg/directorate.html.

I found the document's information interesting, and it is document that is
benefical to the IETF community in understanding the impact energy savings
techniques (mostly related to radios for wireless communication) can have on
protocols (both at lower and higher layers). It is going for Informational
status, which I think is appropriate for this document.

All my comments are fairly minor nits.

In section 1, "Only few efforts focused on" should likely be "Only few efforts
have focused on"? (Add have)

In section 1.1, I think this section can be removed as there are no uses of the
RFC 2119 keywords.

In section 2, there are a few technologies listed here that might use
references; some do appear later but not all. It is usually a good question as
to where references are best added since this is overview material. Those
without any references are ITU-T G.9959 and MS/TP-BACnet.

Also in Figure 2, it is too bad that some power value for listening (when not
"actively" expecting a packet) isn't included since there is a claim that this
can use more energy than transmitting, but it would also be a uJ/<time> which
is unlike the others. Though perhaps indicating a "listening (for X ms)" entry
could work? Anyway, not a big issue.

In section 3, I presume everyone knows what MAC is
(draft-bormann-lwig-7228bis-01 does not define it). Also, might be good to
indicate what RDC is as it is just used (in the MAC and Radio Duty Cycling
section, so pretty obvious likely).

Also in section 3, "take great care of the problem" is a bit strange wording.
Perhaps "are at work on the problem"? Or something like that? And, "can work
perfectly with them" would certainly be great, it may be a stretch of goal -
"can work well with them" may be better?

In section 3.2, "contributes to the packet overall delay" should be
"contributes to the packet's overall delay" ('s).

In section 3.3, "in some services this kind of networks, such as over-the-air"
could be "for some services, such as over-the-air". I think for is better than
in and not sure "these kinds of networks" (instead of this kind of networks) is
really needed?

Also, in this section, "that can achieved when" should be "that can be achieved
when".

In section 3.5.1, "extended sleep modes, traffic filtering" should likely be
"extended sleep modes, and traffic filtering". (You may or may not prefer the
last comma in a list, but the "and" should be there).

And, in this section, in "upper layer protocols knows such capabilities
provided" likely should be "upper layer protocols know such capabilities are
provided".

And, in this section, I don't think you need to define (STA) in several places;
once (first time) should be sufficient?

And, in this section, "by not forwarding individually addressed frames
addresses to" perhaps this should drop "individually addressed"? But perhaps
I'm not understanding why it is needed?

And, "Upper layer protocols would better synchronize" perhaps could be "Upper
layer protocols would best synchronize"? Or just "Upper layer protocols should
synchronize"?

In section 3.5.3, perhaps insert spaces between the 6LoWPAN references to make
the formatting more flexible?

And, in this section, should TDMA be defined (again a fairly common term, but
not in draft-bormann-lwig-7228bis-01.

In section 3.5.4, I think you would want to use "connectionless" instead of
"connection less"?

And, in this section, "data transfer reliability significant" should be "data
transfer reliability significantly"?

In section 4, "So they are quite ignorant" it isn't exactly clear what "they"
are. Replace with "So higher level protocols are quite ignorant"?

And, "but both the sender and receiver should spend" should likely be "but both
the sender and receive will spend"?

In section 6.2, a reference for oneM2M (perhaps to www.onem2m.org) could be
added?

In section 9, the "Thank Ted Lemon, Joel Jaeggli, and efforts to initiate this
facilities" sounds more like notes than actual text? Perhaps something like
"Thanks to Ted Lemon and Joel Jaeglli for initiating and facilitating this
editing session."?

In section 12.1, for the EN300 reference, there are double quotes that probably
aren't needed (single would do)?

Finally, thanks for writing the document!

- Bernie Volz



From nobody Tue Jul 25 01:14:26 2017
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E88FC131891 for <ietf@ietfa.amsl.com>; Tue, 25 Jul 2017 01:14:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 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_MED=-2.3, RP_MATCHES_RCVD=-0.001, 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=ecs.soton.ac.uk
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 qirbflBxZz7l for <ietf@ietfa.amsl.com>; Tue, 25 Jul 2017 01:14:22 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32FEF127978 for <ietf@ietf.org>; Tue, 25 Jul 2017 01:14:20 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6P8DmZv015119; Tue, 25 Jul 2017 09:13:48 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v6P8DmZv015119
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1500970429; bh=TCAEV13VO2DozMDmwZKiPHUdmeQ=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=zVwLkP9TWCyqNmebE14f260uwpquSSyb9hAHZyYsY6yZvXfHpc56n7BygGnmQXU33 4KKae9IzQ4Vi7gqXT462GiLf3rSBBgNmQzPgEt2myT1dhcAKCA5RGAjU8NMlXkUwsO C1bcq8Lga//uB3IdlP1+E2X4TBRaMSlPjA7FyMEg=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id y6O9Dg2564502172gd ret-id none; Tue, 25 Jul 2017 09:13:49 +0100
Received: from [10.1.11.98] (firewall-lho-ext.management.janet.ac.uk [194.82.140.195]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6P8Dcfr027851 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 25 Jul 2017 09:13:39 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: More and more virtual interims
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <20170724205608.gasg56ifeqz3wlci@mx4.yitter.info>
Date: Tue, 25 Jul 2017 09:13:39 +0100
Cc: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Message-ID: <EMEW3|267b8d664653f9dccfa2dd841800e9d6y6O9Dg03tjc|ecs.soton.ac.uk|AA39F093-6491-45D9-81BE-644E30BC3903@ecs.soton.ac.uk>
References: <876859E45DFE49F23C5AD313@PSB> <20170720131527.e4bcjsry623leeih@mx4.yitter.info> <6824.1500635845@dooku.sandelman.ca> <20170724205608.gasg56ifeqz3wlci@mx4.yitter.info> <AA39F093-6491-45D9-81BE-644E30BC3903@ecs.soton.ac.uk>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.3273)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=y6O9Dg256450217200; tid=y6O9Dg2564502172gd; client=relay,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v6P8DmZv015119
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NFnFtIR-fkD_2sIzwFcKFT7cDuE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jul 2017 08:14:25 -0000

> On 24 Jul 2017, at 21:56, Andrew Sullivan <ajs@anvilwalrusden.com> wrote:
> 
> On Fri, Jul 21, 2017 at 01:17:25PM +0200, Michael Richardson wrote:
>> 
>> Can you explain "time boxes" here?
> 
> "Time box" is the (admittedly inelegant) jargon that proponents of
> certain agile software development methodologies use to describe a
> period in which active development + other stuff happens.  This is
> sometimes called the "sprint", but it's not only that of course since
> that's usually coding and such like.  The whole group does all the
> stuff it does for a period inside the "time box".  This is often a
> period of two or three weeks, though I've seen groups that do as much
> as six. The idea is that, within the period in question, a group
> focusses only on certain things and everything else is set aside.
> 
> Setting the jargon aside for a moment, the point is that instead of
> having a WG interim in which everyone has to interrupt their circadian
> rhythm, the WG instead decides that (say) the WG is going to hammer
> out the issues on $draft between (say) Tues and Thurs of next week.
> The jabber room is open and active and issues are rapidly taken up
> from the tracker and knocked down, and then an interim consensus call
> can be done on (say) Friday.  There could also be some sort of voice
> channel up and available, I suppose, if people wanted to join it _ad
> hoc_ to sort something out. It's more async and therefore there'll be
> more mail and jabber back and forth, and maybe someone will come to
> the discussion later and be annoyed that his or her deathless prose was
> mangled, but it's still a way of working rapidly but async in keeping
> with the geographic distribution.  I have seen free software projects
> have success with this sort of thing, so it is possible to do it,
> though it requires that all participants rely really a lot on the
> principle of charity and are super polite and nice in their emails.
> So it might not work here.  But it might be worth a go to see whether
> it could produce results.

Nice idea, and as you say it should help with the time zone issue.

Worth an experiment...

Tim


From nobody Tue Jul 25 09:52:29 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A88EE131E01; Tue, 25 Jul 2017 09:52:16 -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: i2rs@ietf.org, ietf@ietf.org, draft-ietf-i2rs-yang-network-topo.all@ietf.org
Subject: Genart last call review of draft-ietf-i2rs-yang-network-topo-14
X-Test-IDTracker: no
X-IETF-IDTracker: 6.57.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150100153667.26268.4094509639712323654@ietfa.amsl.com>
Date: Tue, 25 Jul 2017 09:52:16 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VBsIJNNVZBPgaOpO8_gX69Mx9QY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jul 2017 16:52:17 -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-ietf-i2rs-yang-network-topo-14
Reviewer: Stewart Bryant
Review Date: 2017-07-25
IETF LC End Date: 2016-12-19
IESG Telechat date: Not scheduled for a telechat

Summary: Ready with a few minor English nits remaining.

Major issues: None

Minor issues: None

Nits/editorial comments: 

I notice that a number of the editorial comments in 

https://datatracker.ietf.org/doc/review-ietf-i2rs-yang-network-topo-09-genart-lc-bryant-2016-12-12/

were not addressed, but I am sure the RFC Editor will pick them up.

I notice that RFC7952 is in the reference list but not called out in the text.



From nobody Tue Jul 25 10:29:19 2017
Return-Path: <shares@ndzh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F237131E66; Tue, 25 Jul 2017 10:29:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Level: 
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, 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 ZvEPNc4n1tFb; Tue, 25 Jul 2017 10:29:02 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (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 7A2A9131E68; Tue, 25 Jul 2017 10:28:59 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=70.194.2.203; 
From: "Susan Hares" <shares@ndzh.com>
To: "'Stewart Bryant'" <stewart.bryant@gmail.com>, <gen-art@ietf.org>
Cc: <i2rs@ietf.org>, <ietf@ietf.org>, <draft-ietf-i2rs-yang-network-topo.all@ietf.org>
References: <150100153667.26268.4094509639712323654@ietfa.amsl.com>
In-Reply-To: <150100153667.26268.4094509639712323654@ietfa.amsl.com>
Subject: RE: [i2rs] Genart last call review of draft-ietf-i2rs-yang-network-topo-14
Date: Tue, 25 Jul 2017 13:22:52 -0400
Message-ID: <01b501d3056a$a5daf9a0$f190ece0$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHl6lR3K2dOVNakqJaIEZLH9x1aSqI/AHYw
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eFLsiwoUNimD7HYPLwqbZbt1LTc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jul 2017 17:29:05 -0000

Stewart: 

Thank you for your review!  To come back from IETF and immediately complete
your review shows awesome dedication!

Cheerily, Sue Hares

-----Original Message-----
From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Stewart Bryant
Sent: Tuesday, July 25, 2017 12:52 PM
To: gen-art@ietf.org
Cc: i2rs@ietf.org; ietf@ietf.org;
draft-ietf-i2rs-yang-network-topo.all@ietf.org
Subject: [i2rs] Genart last call review of
draft-ietf-i2rs-yang-network-topo-14

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-ietf-i2rs-yang-network-topo-14
Reviewer: Stewart Bryant
Review Date: 2017-07-25
IETF LC End Date: 2016-12-19
IESG Telechat date: Not scheduled for a telechat

Summary: Ready with a few minor English nits remaining.

Major issues: None

Minor issues: None

Nits/editorial comments: 

I notice that a number of the editorial comments in 

https://datatracker.ietf.org/doc/review-ietf-i2rs-yang-network-topo-09-genar
t-lc-bryant-2016-12-12/

were not addressed, but I am sure the RFC Editor will pick them up.

I notice that RFC7952 is in the reference list but not called out in the
text.


_______________________________________________
i2rs mailing list
i2rs@ietf.org
https://www.ietf.org/mailman/listinfo/i2rs


From nobody Tue Jul 25 10:30:31 2017
Return-Path: <shares@ndzh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19CD6131E6B; Tue, 25 Jul 2017 10:30:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Level: 
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, 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 RfYOiyCKZliy; Tue, 25 Jul 2017 10:30:15 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (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 3E7C6131E68; Tue, 25 Jul 2017 10:30:15 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=70.194.2.203; 
From: "Susan Hares" <shares@ndzh.com>
To: "'Ines Robles'" <mariainesrobles@googlemail.com>, <rtg-dir@ietf.org>
Cc: <rtg-ads@ietf.org>, <i2rs@ietf.org>, <ietf@ietf.org>, <draft-ietf-i2rs-yang-network-topo.all@ietf.org>
References: <150093804800.26111.1394410974752858089@ietfa.amsl.com>
In-Reply-To: <150093804800.26111.1394410974752858089@ietfa.amsl.com>
Subject: RE: [i2rs] Rtgdir last call review of draft-ietf-i2rs-yang-network-topo-14
Date: Tue, 25 Jul 2017 13:24:08 -0400
Message-ID: <01b701d3056a$d381fca0$7a85f5e0$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIJ6YKanmEFADbnMl9M4liTZ2TQpaH3Alyw
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/saAKstp8KaNBDL-yZtgZBwDNn5A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jul 2017 17:30:17 -0000

Ines:

Getting this review on the Monday after IETF shows what a diligent =
reviewer you are.  The authors will be responding shortly.=20

Cheerily,=20
Sue Hares=20

-----Original Message-----
From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Ines Robles
Sent: Monday, July 24, 2017 7:14 PM
To: rtg-dir@ietf.org
Cc: rtg-ads@ietf.org; i2rs@ietf.org; ietf@ietf.org; =
draft-ietf-i2rs-yang-network-topo.all@ietf.org
Subject: [i2rs] Rtgdir last call review of =
draft-ietf-i2rs-yang-network-topo-14

Reviewer: Ines Robles
Review result: Has Issues

Hello,

I have been selected as the Routing Directorate reviewer for this draft. =
The Routing Directorate seeks to review all routing or routing-related =
drafts as they pass through IETF last call and IESG review, and =
sometimes on special request. The purpose of the review is to provide =
assistance to the Routing ADs.
For more information about the Routing Directorate, please see =
=E2=80=8Bhttp://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir

Although these comments are primarily for the use of the Routing ADs, it =
would be helpful if you could consider them along with any other IETF =
Last Call comments that you receive, and strive to resolve them through =
discussion or by updating the draft.

Document: draft-ietf-i2rs-yang-network-topo-14.txt
Reviewer: Ines Robles
Review Date: 07-25-2017
Intended status: Standards Track

Summary:
I have some minor concerns about this document that I think should be =
resolved before publication.

Comments:

I believe the draft is technically good. This document is well written =
and clear to understand. The figures are clear and helpful.

Major Issues:

No major issues found.

Minor Issues:

Since this document specifies a data model, I would include some text =
related to the Information Model [RFC 3444]. How would it be in this =
context?

1- Section 1

  1.a following Figure 1 (Page 4):

    I would add in the figure the corresponding section that explain the
    module. e.g. Abstract Network Model, I would add in the figure =
"Abstract
    (base) Network Model" and "section 4.1". The same for "Abstract =
Topology
    Model", should it be section 4.2?

  1.b -following Figure 2 (Page 5):

      1.b.1- " X1 and X2 - mapping onto... ",  I think it would be "X1 =
and X3
      mapping onto..."

      1.b.2- " a single L3 network element", I would add in this case =
(Y2) "a
      single L3 (Y2) network element", the same for "The figure shows a =
single
      "L3" network element mapped onto multiple "Optical" network =
elements.", I
      would add "The figure shows a single "L3" network element (Y2) =
mapped
      onto multiple "Optical" network elements [Z] and [Z1]."

      1.b.3- I would expand ROADMs --> Reconfigurable Optical Add/Drop
      Multiplexers (ROADMs)

2- Section 2:

  2.1- I would add a reference to RFC 6020, since the document uses =
terminology
  e.g container, augment, etc. which are defined in 6020. Even if this =
RFC is
  mentioned in the normative reference, still I would add it here as =
well.

3- Section 3:

  3.1-  ReST is mentioned here but not in the rest of the draft, is this
  correct?

Nits:

1- Pag. 18: is that correct?: "(a string is a string is a string)"

2- pag. 34: I would expand NMS -> NMS (Network Management System)

3- pag. 34: I would add a definition about TE Topology : "TE-Topology: =
The TE Topology is a schematic arrangement of TE nodes
   and TE links in a given TED. It forms the basis for a graph suitable
   for TE path computations."
   [https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-12]

4- pag. 34: topoogical -> topological

5- pag 35: "uber-network device" -> over-network device?

Thanks,

Ines.


_______________________________________________
i2rs mailing list
i2rs@ietf.org
https://www.ietf.org/mailman/listinfo/i2rs


From nobody Tue Jul 25 10:48:48 2017
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DED5131E80 for <ietf@ietfa.amsl.com>; Tue, 25 Jul 2017 10:48:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.503
X-Spam-Level: 
X-Spam-Status: No, score=-14.503 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_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 oOsSSJfDQBOg for <ietf@ietfa.amsl.com>; Tue, 25 Jul 2017 10:48:46 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D859F131E6B for <ietf@ietf.org>; Tue, 25 Jul 2017 10:48:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3754; q=dns/txt; s=iport; t=1501004926; x=1502214526; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=5YsF9Y00ibC3rAuenpscVRUpdzbKkeZdd7Jmc1y1TeA=; b=Boe7ma1xaxJTktHzkg3MqQSeQ5Gg/3bT9OYaojqzousffgW2SfnVAiTi m2MpSw1ga38MMO7X0cMErX9gihRjLgVzPsBeF5jpgT9H94o8K6fwbgMVf nPBjv4dSxVTccGE+iYP1HXsxmPuolZkzS1y3v9jdpyaTuEvPCeP+8P7x0 0=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DiAQBCg3dZ/xbLJq1dGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBlFGQdZgYB4IFgzsCg3oUAQIBAQEBAQEBayiFGQEFI2YLDgoqAgJXBgE?= =?us-ascii?q?MCAEBiiuxU4Imi0kBAQEBAQUBAQEBAQETD4MohVmCeYRTAQGDMYJhAQSfV4Qwg?= =?us-ascii?q?h6NUYsxhwiVaTYhgQoyIQgcFYdkPoc6gjEBAQE?=
X-IronPort-AV: E=Sophos;i="5.40,411,1496102400";  d="asc'?scan'208";a="654515553"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Jul 2017 17:48:41 +0000
Received: from [10.61.244.22] ([10.61.244.22]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v6PHmeCM001177; Tue, 25 Jul 2017 17:48:41 GMT
Subject: Re: More and more virtual interims
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
References: <876859E45DFE49F23C5AD313@PSB> <20170720131527.e4bcjsry623leeih@mx4.yitter.info> <6824.1500635845@dooku.sandelman.ca> <20170724205608.gasg56ifeqz3wlci@mx4.yitter.info>
From: Eliot Lear <lear@cisco.com>
Message-ID: <a4f995ec-09b9-ef88-4d1e-c8ccb8d54910@cisco.com>
Date: Tue, 25 Jul 2017 19:48:41 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <20170724205608.gasg56ifeqz3wlci@mx4.yitter.info>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Og93MMvIHgVgopofRV8FwvCGvmlrw3cl4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vD5rGtgJLCvuSIzkdwJPpjQlWeM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jul 2017 17:48:48 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--Og93MMvIHgVgopofRV8FwvCGvmlrw3cl4
Content-Type: multipart/mixed; boundary="Bn9MEXIeDoj2C5quETno5oEVsgmq42Cdd";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
Message-ID: <a4f995ec-09b9-ef88-4d1e-c8ccb8d54910@cisco.com>
Subject: Re: More and more virtual interims
References: <876859E45DFE49F23C5AD313@PSB>
 <20170720131527.e4bcjsry623leeih@mx4.yitter.info>
 <6824.1500635845@dooku.sandelman.ca>
 <20170724205608.gasg56ifeqz3wlci@mx4.yitter.info>
In-Reply-To: <20170724205608.gasg56ifeqz3wlci@mx4.yitter.info>

--Bn9MEXIeDoj2C5quETno5oEVsgmq42Cdd
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US

This sounds like something to try, even as an alternative to a f2f interi=
m.


On 7/24/17 10:56 PM, Andrew Sullivan wrote:
> On Fri, Jul 21, 2017 at 01:17:25PM +0200, Michael Richardson wrote:
>> Can you explain "time boxes" here?
> "Time box" is the (admittedly inelegant) jargon that proponents of
> certain agile software development methodologies use to describe a
> period in which active development + other stuff happens.  This is
> sometimes called the "sprint", but it's not only that of course since
> that's usually coding and such like.  The whole group does all the
> stuff it does for a period inside the "time box".  This is often a
> period of two or three weeks, though I've seen groups that do as much
> as six. The idea is that, within the period in question, a group
> focusses only on certain things and everything else is set aside.
>
> Setting the jargon aside for a moment, the point is that instead of
> having a WG interim in which everyone has to interrupt their circadian
> rhythm, the WG instead decides that (say) the WG is going to hammer
> out the issues on $draft between (say) Tues and Thurs of next week.
> The jabber room is open and active and issues are rapidly taken up
> from the tracker and knocked down, and then an interim consensus call
> can be done on (say) Friday.  There could also be some sort of voice
> channel up and available, I suppose, if people wanted to join it _ad
> hoc_ to sort something out. It's more async and therefore there'll be
> more mail and jabber back and forth, and maybe someone will come to
> the discussion later and be annoyed that his or her deathless prose was=

> mangled, but it's still a way of working rapidly but async in keeping
> with the geographic distribution.  I have seen free software projects
> have success with this sort of thing, so it is possible to do it,
> though it requires that all participants rely really a lot on the
> principle of charity and are super polite and nice in their emails.
> So it might not work here.  But it might be worth a go to see whether
> it could produce results.
>
> Best regards,
>
> A
>



--Bn9MEXIeDoj2C5quETno5oEVsgmq42Cdd--

--Og93MMvIHgVgopofRV8FwvCGvmlrw3cl4
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

iQEcBAEBCAAGBQJZd4R5AAoJEIe2a0bZ0noz5+YH/1PX2rDYiw/IRQHb7wJqHGms
ERAkgpqV8w3WRQaS+tmYdceN1zDreWCY37a1X86v65PXQYYOOPL8AG2K7yjHg50l
nbaZYI1JQzf6LrvHvcgYGo2TQViOuJ1zGufu7fciqAHWIjlTz234So+HKJD3ekvk
C1mKRp+yEn00krLjSWEz5ix/z3K1JzvrNlzJ7f15k4T8xMFXBCvRsr65KK7gaBzt
7K0nciO6WLV/3iuuv1sVVAgE9lnMnasfRraE1tBsD2HVcTJHcart4y1u+6wZ/wqt
tWzee6hM5s4zUTYUptkvihSeasc5Ux2IA/DV+V3V4UyGfL5/uFANz78y2K5oeqw=
=X8+g
-----END PGP SIGNATURE-----

--Og93MMvIHgVgopofRV8FwvCGvmlrw3cl4--


From nobody Tue Jul 25 10:59:26 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E00DF131E90; Tue, 25 Jul 2017 10:59:10 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Pete Resnick <presnick@qti.qualcomm.com>
To: <gen-art@ietf.org>
Cc: curdle@ietf.org, ietf@ietf.org, draft-ietf-curdle-ssh-dh-group-exchange.all@ietf.org
Subject: Genart last call review of draft-ietf-curdle-ssh-dh-group-exchange-05
X-Test-IDTracker: no
X-IETF-IDTracker: 6.57.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150100555089.26234.7716617823296361972@ietfa.amsl.com>
Date: Tue, 25 Jul 2017 10:59:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AuV0ODyB86zqDLcF4U90ONA0Gnc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jul 2017 17:59:11 -0000

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 Tue Jul 25 14:06:37 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B9C90131F2A; Tue, 25 Jul 2017 14:06:36 -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: draft-ietf-ippm-model-based-metrics.all@ietf.org, ietf@ietf.org, ippm@ietf.org
Subject: Genart telechat review of draft-ietf-ippm-model-based-metrics-11
X-Test-IDTracker: no
X-IETF-IDTracker: 6.57.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150101679673.26268.16147768864334508872@ietfa.amsl.com>
Date: Tue, 25 Jul 2017 14:06:36 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WWTpfl0asuj2JPH4eNKWwkqAnzk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jul 2017 21:06:37 -0000

Reviewer: Robert Sparks
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-ippm-model-based-metrics-11
Reviewer: Robert Sparks
Review Date: 2017-07-25
IETF LC End Date: 2017-03-14
IESG Telechat date: 2017-08-03

Summary: Ready with nits

Thanks for addressing the comments in my review of -10.
In the revision (as a side-effect of removing the dependency on 2119, I
suspect) you removed the classification of normative vs informative references.
I think you mean that all of these references are Informative. (The document
would have a References section, with one "Informative References" subsection).



From nobody Tue Jul 25 14:36:37 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 75B961252BA; Tue, 25 Jul 2017 14:36:22 -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: ietf@ietf.org, dmm@ietf.org, draft-ietf-dmm-mag-multihoming.all@ietf.org
Subject: Genart telechat review of draft-ietf-dmm-mag-multihoming-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.57.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150101858235.26256.6969152365134554054@ietfa.amsl.com>
Date: Tue, 25 Jul 2017 14:36:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/G-3ePqHbNzKA8xC8v1Bu-B-rKUI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jul 2017 21:36:23 -0000

Reviewer: Robert Sparks
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-dmm-mag-multihoming-04
Reviewer: Robert Sparks
Review Date: 2017-07-25
IETF LC End Date: 2017-06-16
IESG Telechat date: 2017-08-03

Summary: Ready with nits that should be addressed before publication as Proposed Standard

Thanks for addressing most of the points in my review of -03.

There are still a couple of things that I think need attention:

* In the second bullet of section 3.2 there is a sentence that does not make sense.
   Look at "or at When operating" in this sentence:
    "Packet distribution can be done
      either at the transport level, e.g. using MPTCP or at When
      operating at the IP packet level, different packets distribution
      algorithms are possible."

* I still find the definitions of Interface Label and Binding Identifier confusing.
   I suspect they _both_ need to be carefully rewritten to make sure they are
   definitions of the terms, and not descriptions of the interactions of the two
   fields. Why is the Interface Label definition talking so much about binding?
   As currently written, that last sentence of the Binding Identifier
   definition says  the document says the mobile access gateway assigns
   a single unique binding identifier for each of its interfaces. 








From nobody Tue Jul 25 15:24:33 2017
Return-Path: <denisbider.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF28F131F8A; Tue, 25 Jul 2017 15:24:31 -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 z6m7J84vvHSM; Tue, 25 Jul 2017 15:24:29 -0700 (PDT)
Received: from mail-yw0-x22b.google.com (mail-yw0-x22b.google.com [IPv6:2607:f8b0:4002:c05::22b]) (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 F28FD131F90; Tue, 25 Jul 2017 15:24:25 -0700 (PDT)
Received: by mail-yw0-x22b.google.com with SMTP id i6so43306459ywb.1; Tue, 25 Jul 2017 15:24:25 -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=w+g6RDD4CGjnId1yU8EOpEQzAP+YoQg0nJSXL562mb4=; b=kquKt1vZHK4F2C7I8zEzEy9RZ1PtBpzHZv3mF0G72/K4mF4+IxIfsr1QQgRq8Ovo1z TCycigms3ED8InQQYMEQigxAOpaU8mBbomCixfzl3msECnpVFG04jbbOwKMF+mSFMsYg 0WQ0rvJKHiD2FpLL4O8DRZ/uAjsS0DCjPAjcX/Fpfks5iEoCedRQ/x3IP2H3GHpddYcI DCMwudlTxa7mG9ydYxvsYVidrFhkwZsR6M8x1bWin5Uo+caJNCM+kXoRJ4qPJ0sXdAEc eTKlo0tWWS2ctRmx5RIKv3llH6gdErLDw6bn9URDVhKDHsNeFwlEhTYCG713U0a4zM42 6rZQ==
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=w+g6RDD4CGjnId1yU8EOpEQzAP+YoQg0nJSXL562mb4=; b=uA1GZ+ZnuvD8sHvl3yoInq5cYVEK9sF96s2lRHeu0fS83Ki9MTp4UANZ5fUoEbIeFF grogtlTuyEDghjSz+MRRmqxVrfZJ2WJozrj32Ws0lgAF4aIY7L7EbpsUnHTRiCBeXrJx 63Zo9MnWauuh2Z4k4pGZYmuid+Fl0tvazeANUrUsHpHz299EJndhHWIh8s7sDT5gqfuq QS4xxZ43J4xZwBngrrCHeRb+DaH7W6eFW3rW8Hlfxiz6QkvtRBwzz7itRB/3zmf/Mp95 StoUYivieHPoKcgiWE9aQAKa78YsG/vXgnnrA+8PVibp6FBKSj4O994YVcgKIir1jAVn aPFA==
X-Gm-Message-State: AIVw111qr865dLvgZuDYQcd8+Q2AGRIB6WzlCmCMSQWhyAURneIRlnGQ fWyAoWf3rlgCX29ItUfAiT8mybuOmQ==
X-Received: by 10.37.126.193 with SMTP id z184mr14746551ybc.20.1501021465200;  Tue, 25 Jul 2017 15:24:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.42.200 with HTTP; Tue, 25 Jul 2017 15:24:24 -0700 (PDT)
In-Reply-To: <150093015937.32021.12465797358778837950@ietfa.amsl.com>
References: <150093015937.32021.12465797358778837950@ietfa.amsl.com>
From: denis bider <denisbider.ietf@gmail.com>
Date: Tue, 25 Jul 2017 16:24:24 -0600
Message-ID: <CADPMZDCE+m+_QA7s6vdFOw-7uF4cfV4g8_U07fb-Ydur30OR5g@mail.gmail.com>
Subject: Re: [Curdle] Genart last call review of draft-ietf-curdle-ssh-ext-info-10
To: Matthew Miller <linuxwolf+ietf@outer-planes.net>
Cc: gen-art@ietf.org, curdle <curdle@ietf.org>, ietf@ietf.org,  draft-ietf-curdle-ssh-ext-info.all@ietf.org
Content-Type: multipart/alternative; boundary="001a114bb09a3bd60d05552bcbd9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QxcgWdtKstfHgQ8KmmX96GygSQ8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jul 2017 22:24:32 -0000

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

Good catch. I believe this refers to the following paragraph:

"If an extension requires both the client and the server to include it in
order for the extension to take effect, the relative position of the
extension-name in each EXT_INFO message is irrelevant."

I have drafted the following new wording:

"Unless a particular extension's specification indicates differently; then,
if an extension requires both the client and the server to include it in
order for the extension to take effect; implementers MUST use a default
assumption that the relative position of the extension-name in each
EXT_INFO message is irrelevant with respect to whether the extension takes
effect."

The purpose of this wording is to:

- Provide a sensible default, which is that in the absence of specific
knowledge, order of extension names does not matter.

- Allow for deviations in special cases where there is specific knowledge.

For example, extension "foo-linux" could be specified, but after some years
of use, it's observed that it works well for its main purpose, but is not
ideal for a server on Windows. Therefore, extension "foo-windows" is
specified, which works well when the server is Windows, but not as well
when it's Linux.

In this case, an implementation that supports "foo-linux" only would be
ignorant of anything else, and would use the default rule (order of
extension names does not matter). However, an implementation that supports
"foo-windows" could implement only that, or both "foo-linux" and
"foo-windows". The specification for "foo-windows" could indicate that when
both are supported, the first one listed by the server (or in other cases,
by the client) is used.

Allowing for such an extension-defined special case would allow a Linux
server to advertise extensions [... "foo-linux", ..., "foo-windows", ...],
preferring "foo-linux", but supporting the less appropriate "foo-windows"
mechanism as well. Whereas, a Windows server could advertise [...
"foo-windows", ..., "foo-linux", ...], preferring "foo-windows", but
supporting the less appropriate "foo-linux" mechanism as well.

Does this work?

If there are no objections, I'll upload a -11 draft version with this new
wording.



On Mon, Jul 24, 2017 at 3:02 PM, Matthew Miller <
linuxwolf+ietf@outer-planes.net> wrote:

> Reviewer: Matthew Miller
> 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-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
>
> Summary:
>
> This document is ready with an issue.
>
> I found this document very coherent and easy to follow.
>
> Major issues:
>
> Minor issues:
>
> My only issue borders on nit, but sided with nit as I can see it
> potentially causing confusion for an implementer in the future.
>
> 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.
>
> Nits/editorial comments:
>
> * RFC 5226 is referenced by this document, but is obsoleted by RFC 8126.
>
>
> _______________________________________________
> Curdle mailing list
> Curdle@ietf.org
> https://www.ietf.org/mailman/listinfo/curdle
>

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

<div dir=3D"ltr">Good catch. I believe this refers to the following paragra=
ph:<div><br></div><div><div>&quot;If an extension requires both the client =
and the server to include it in order for the extension to take effect, the=
 relative position of the extension-name in each EXT_INFO message is irrele=
vant.&quot;</div></div><div><br></div><div>I have drafted the following new=
 wording:</div><div><br></div><div>&quot;Unless a particular extension&#39;=
s specification indicates differently; then, if an extension requires both =
the client and the server to include it in order for the extension to take =
effect; implementers MUST use a default assumption that the relative positi=
on of the extension-name in each EXT_INFO message is irrelevant with respec=
t to whether the extension takes effect.&quot;</div><div><br></div><div>The=
 purpose of this wording is to:</div><div><br></div><div>- Provide a sensib=
le default, which is that in the absence of specific knowledge, order of ex=
tension names does not matter.</div><div><br></div><div>- Allow for deviati=
ons in special cases where there is specific knowledge.</div><div><br></div=
><div>For example, extension &quot;foo-linux&quot; could be specified, but =
after some years of use, it&#39;s observed that it works well for its main =
purpose, but is not ideal for a server on Windows. Therefore, extension &qu=
ot;foo-windows&quot; is specified, which works well when the server is Wind=
ows, but not as well when it&#39;s Linux.</div><div><br></div><div>In this =
case, an implementation that supports &quot;foo-linux&quot; only would be i=
gnorant of anything else, and would use the default rule (order of extensio=
n names does not matter). However, an implementation that supports &quot;fo=
o-windows&quot; could implement only that, or both &quot;foo-linux&quot; an=
d &quot;foo-windows&quot;. The specification for &quot;foo-windows&quot; co=
uld indicate that when both are supported, the first one listed by the serv=
er (or in other cases, by the client) is used.</div><div><br></div><div>All=
owing for such an extension-defined special case would allow a Linux server=
 to advertise extensions [... &quot;foo-linux&quot;, ..., &quot;foo-windows=
&quot;, ...], preferring &quot;foo-linux&quot;, but supporting the less app=
ropriate &quot;foo-windows&quot; mechanism as well. Whereas, a Windows serv=
er could advertise [... &quot;foo-windows&quot;, ..., &quot;foo-linux&quot;=
, ...], preferring &quot;foo-windows&quot;, but supporting the less appropr=
iate &quot;foo-linux&quot; mechanism as well.</div><div><br></div><div>Does=
 this work?</div><div><br></div><div>If there are no objections, I&#39;ll u=
pload a -11 draft version with this new wording.</div><div><br></div><div><=
br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On=
 Mon, Jul 24, 2017 at 3:02 PM, Matthew Miller <span dir=3D"ltr">&lt;<a href=
=3D"mailto:linuxwolf+ietf@outer-planes.net" target=3D"_blank">linuxwolf+iet=
f@outer-planes.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
Reviewer: Matthew Miller<br>
Review result: Ready with Issues<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-curdle-ssh-ext-<wbr>info-10<br>
Reviewer: Matthew Miller<br>
Review Date: 2017-07-24<br>
IETF LC End Date: 2017-07-30<br>
IESG Telechat date: N/A<br>
<br>
Summary:<br>
<br>
This document is ready with an issue.<br>
<br>
I found this document very coherent and easy to follow.<br>
<br>
Major issues:<br>
<br>
Minor issues:<br>
<br>
My only issue borders on nit, but sided with nit as I can see it<br>
potentially causing confusion for an implementer in the future.<br>
<br>
Section 2.5. &quot;Interpretation of Extension Names and Values&quot; expli=
citly<br>
states in the second paragraph a condition where the relative order of<br>
extension-names in an EXT_INFO message is irrelevant.=C2=A0 However, the re=
st<br>
of the section seems to imply to me that relative order is not important;<b=
r>
so to explicitly call out a scenario seems to imply that relative order<br>
*is* relevant/important, sometimes.=C2=A0 If relative order is expected to =
be<br>
important most of the time, I think it helpful to explicitly state that<br>
and give a rationale for it.<br>
<br>
Nits/editorial comments:<br>
<br>
* RFC 5226 is referenced by this document, but is obsoleted by RFC 8126.<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>

--001a114bb09a3bd60d05552bcbd9--


From nobody Tue Jul 25 22:22:30 2017
Return-Path: <rpelletier@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F818131F07 for <ietf@ietfa.amsl.com>; Tue, 25 Jul 2017 22:22:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.802
X-Spam-Level: 
X-Spam-Status: No, score=-4.802 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.org
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 GeLE9xeqFDhe for <ietf@ietfa.amsl.com>; Tue, 25 Jul 2017 22:22:25 -0700 (PDT)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02on0071.outbound.protection.outlook.com [104.47.37.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F583124D68 for <ietf@ietf.org>; Tue, 25 Jul 2017 22:22:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.org; s=selector1;  h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=RRKaOrewz0mEYGGj++cZPkb0kMMvOfzm65niqoC91AY=; b=HxcqwAj09Cz5dTNUGs4GqHl4W49CMjOYKaVXzVxsfKTTUsce/Ie9mMlLjZVd7U22RKqzDLlXlwI4tDGbjBtM8W3DP7WDtPE6jZGWL/IMyDb5jBobyUUBn+jEf7L5TP3CiJXjsIEUMLZ1rRcHVT9TWvZ/dpzVRqDBoafAurLhCKE=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=rpelletier@isoc.org; 
Received: from [192.168.1.3] (80.116.45.233) by BN6PR06MB3444.namprd06.prod.outlook.com (10.175.131.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1304.14; Wed, 26 Jul 2017 05:22:22 +0000
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Revamp of the www.ietf.org website
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <20170721083215.a2qdgfrpg2jf6irq@mx4.yitter.info>
Date: Wed, 26 Jul 2017 07:22:13 +0200
Cc: IETF Discussion <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B5AD9DB5-A261-4924-98F4-0D5945E68366@isoc.org>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6394482@GLKXM0002V.GREENLNK.net> <39D1C0A9-DB43-42DD-BD3F-7D636856ECEF@gmail.com> <20170721083215.a2qdgfrpg2jf6irq@mx4.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.3273)
X-Originating-IP: [80.116.45.233]
X-ClientProxiedBy: AM3PR07CA0083.eurprd07.prod.outlook.com (10.165.222.17) To BN6PR06MB3444.namprd06.prod.outlook.com (10.175.131.135)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 3a9a5c60-6eb9-409d-953e-08d4d3e64bd3
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(300000503095)(300135400095)(201703131423075)(201703031133081)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:BN6PR06MB3444; 
X-Microsoft-Exchange-Diagnostics: 1; BN6PR06MB3444; 3:l8mi425YzpBHBYnQ8WZz1kve2JHzEZru5HBWZTPzha1L/C3W+JgJ00oLuuzAsyV4Mc/jYOnGDeXWCUuL7GlQzgtekjUjXXdUIJAsr3XeHFeyKzvZbus05MbQMEbMLKarE5mWiUKCpyj5vPE9mIEisWi+PqQrLl7dw4DS0USJ2Mx3dIJ/PLleM0hAPdNPh2BFEeeFY4Yts3dBF8FcgxM4Cz9gC9qPKPMX/72j3SNkCqxo/KmsjhkIg1f7vsWrCt+8P73xHo0b0wg8+GXS45IJr+OVixfIH8bK0WY0Oi3hNRBQpJTMqvkO9U0EdNb390DJJudIbBLkyWYbGD36FY4UjQ0KNYf9lGderThxke60XJl7YJemMY0YwUrffQvATwe0q8WWOeDMXqlv/J02c4xn5KE8Jn9xPG5rwMDDlO60HPKhrCfNXn2OEAeK67yJdBFRLm16/5EiYgiGYR+Ot9TTt8BOLy2zL/GCyCYA2/aZSAR7SrDnaU0c54xukfmZ8fV9ULZSOYugn+kmGDh+2Xi5Y7uKxVhX91T8gkKDve8qkyMZM1zhDmkiGIUE5zybSWQ0gPk+Q0gDxM2sG46v1tjZqNfP4eGJBtkfv9TL/xDsoC3muAlg7aC1N4Ey8Tufug427cKhATRobywgbZRg8Ro3C1yj47iLehw7kE7HY1l3Fn6BV77o1HR2pVMU9FEvpeSPNZBPDYyJHxUoY+lIliLPgqQiIfKLSKoVVcSC8yqHzyY=
X-MS-TrafficTypeDiagnostic: BN6PR06MB3444:
X-Microsoft-Exchange-Diagnostics: 1; BN6PR06MB3444; 25:bOL839HDvImZ0bmxqodVXM9cW1P8XgsBByy1aB6I+Ijq1Wq6kfk3H08WUP1g9Hx/HM5BF4rRStkcAZyvvl/PD4yMDygj+gTFIlBBqQDvKWrgIuONnStFe2h6sRa52WOfJQMqJ32Q68qevH3UsE/1hOJ6/dsJSbdC8KzXWeNF9cao6u9dBRw3ci+lkLlEE7qNT+WL2WjaTORTG7FitwWJJ+w7HUkzRHF6e8LZ2+mLYG4hpKPxcWNCyrdA9NXGRoi192ybQheAey7UtKdHzIRpnr6o3wLdbcM12uo0fKQoqxR1cikL4muAAyDGJc3i45GnOrp1QfdbzkRDOMYGRw3KQT1dT6qhRpgNmg49zm+/qxn2ZTwxRtJh2wmHBLxiPkS17VFIXFXWiqgTiGLXBRxDwBNC++CAH9EDz4Foe1f+eCOC//zKrIs0HVX0yfPfEBlOJkfhPmmhqkwVD61v5l8BK61D7vTw5fGiNebG3AMboaaAFBR9kBpZCn0SnCVY5nHLy3I7tm3NAubcLapWWJFVJSgXT3cT+xpumPzqVQJeiAXpeQt7TTk+dwixpqcMN3Qq0+5o6o/FTycFDWeRnFmRupWID0BQs/LTVW2rRLuuVR09b0k21Pb09i3qcnJpeS8KSBruDNe2M3zImJvAbc7sChrFE+swPXnWzYZZPTJxZ58dYpSnd2B39SGane8XAAhFalXZS84muvbS4RjBeGJFvYKF1bBp1pMcKnMXXIgVaTO37oIdGGsmKwdhC1tstcmvDxC20Rhg22H9uGM977LmCudCTGqZk80XmJOScS9xXHJmm461fu7UB8Y4eTXbsJHRcT08BR+nMIgo7qNrudE4dD4dKk5sm/BCLbG4O5wfUW5Emi1z8OYzvekNtXe2mLsOwt1c8AL6swdVFo/GbbwoHEfeKf7P1VV2+OCR3uJRwqo=
X-Microsoft-Exchange-Diagnostics: 1; BN6PR06MB3444; 31:VOFaRZaO1ShKq/h9nV0pYMV+ZiXCTOcn8WzktZo7HjW1EiwkZGskgYiCn3cIvPV9jMXzfnl2o6AzjtAY/cST+NS545z/JjF137Vcu2FuxgsS4sd9QK0FfkUTo3jLXIOfaJwrEGNm8Y6UjOc8pvVy7a7RyuSXixyv5POqLaowJKv7MHfEi3KNkT+tlT7ueb770sXHzJnU7yIQ1uKKsodsDBdausyXqvJF47H2T1Xa2CYuRN2F+xV0DzLB8ZKyCDBTmaZQhYmUoqgAsbJJDUP7e1Gbth8WyHIRgQYDYVvZtxSFMnrW4yl051TmWA3mTUbGmP7avSYcrRo0am7Lk/cuGSxEz7UEL2TTXS66cmiRl4gy80Sni95qhWsJw+JB7jgz1PuIqLj8l/b4nIAmstx7JCuSopfuURFI2GQxZ0L0//mhRXkZs2Dy5JGULX68FjdhYjuu3suhOxIPMrlCQiR8JC1++61dm456OeLblLoIz+h81HDyQWcd61ejSvw28gwTKxqEGwrvHv+Cp3OlEMB5XZ3JRHJltq6KhMD9FdvGlQsBUmDOyzJr4lUSuzT7ZyO8GHOb+Lx7v+FBdIKcvwM38mzklm6tdXu3LDztJJyrmoEOEUtBon63dmScgaFdRC6eD5eDsrIxS+y+mXzEu48V6ZNhD6/jWp7QngDYQ+mwlqjtyte01tc9CnYBzija11inqvtemlXii4JRzSHhveM5nA==
X-Microsoft-Exchange-Diagnostics: 1; BN6PR06MB3444; 20:qc7HsdTi5IKV6sGaYY9VHOZTMTNl2QsKlFuS0pATtRU0qezyOO9zFCptLcIi/orle7Z6lDanj5k+WRLa91RgqQtpBpjsZ5io24p2EOP/o18GhRfUaUnPaE6R1oa71IHf5z/V0/3pPvN/EzVl2NA5IIGw4EvwiG7obj71k1Pmo00+pr5Mod1Y7l4tfEediKAKq4oCtLoaGkxQc5ZyUGTJ8TK8V0kcLMkkLhtaOiJ6LA0/3POlwJg7wbavTSdNuG5wHGEiOzJxDf3wJf7FisiCxmVRMWahRa592WW5ntCrx4a4KSc5p9g0jMJAwLGgqohOAgRS01Ua6FpUOoq4nJdFdTjOVs7DRle8+QUsyxaUh8LumbBp8K3zs4D0M77R7tagpy/Xg6mgvX4Ct3yFhYFFFYRH4CuUrf7TQIaVIEjIRBo3gYYGfafzPb7IKkfJzBMiT/yb7a2RhapduRHS79sUIE8TJh+O/4tfmEJQUbd+yw0tsIEd0/V/XTdO+IPEBzlO
X-Exchange-Antispam-Report-Test: UriScan:;
X-Microsoft-Antispam-PRVS: <BN6PR06MB344405CC6705DFF8737A566DB0B90@BN6PR06MB3444.namprd06.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(5005006)(8121501046)(10201501046)(100000703101)(100105400095)(93006095)(93001095)(3002001)(6041248)(20161123560025)(20161123564025)(20161123555025)(20161123558100)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BN6PR06MB3444; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BN6PR06MB3444; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtCTjZQUjA2TUIzNDQ0OzQ6UUlXTFJlc2czZEJiNlFXNUp2RUVxNTZBYUpy?= =?utf-8?B?bFhUYWcwb3lzU0szckl6c2hJNnF4UmhFMGkrS2c0ZERqZlRNQVgwaWRnbitt?= =?utf-8?B?R2JDSVhYL1paRGRXRmhoRG80dTd6cFNwb1ZxdWR1bVpTcjRsT215L1hjWjVL?= =?utf-8?B?VlpTZTFVZmk2MXVTK243U3VseStwMUVNalY5LzEyS1dSNEZ0WWlRbGVFNCtz?= =?utf-8?B?dm5JKytvanJYNGtHbUxiZUc5ZGRyb2JlSzl1VFlCNDlWcCtWRmducnREMTVy?= =?utf-8?B?bE5YWkkzQXVHOXhyS0JVdU1pRlYxT2ZWbUJvWjc3NTZON2ErWWU1bUxUaFhu?= =?utf-8?B?WCtza2ZvUktuV0MwQlorOTd2dlprcnFOWHYzUjE2UzlWQWhaS1F1ak03VnFy?= =?utf-8?B?dlpTMTNBS0RJdW81bDJyUDkxZHZRdFhkM3BMM1ZZdzN2dGRyZEJubE1LREdv?= =?utf-8?B?eUhZRlFKYUc1ZXVCT3g5NHJVeVR0ejRDOGRuZzI5b2NKNnpiaGFZR3JzQWpR?= =?utf-8?B?ZEJSbjFwd3pWblNWY0JaaEE2djVBTG1mRVBHa1RIR1lpMWRZNFpCdUlyQ3dp?= =?utf-8?B?aWVvNG1mWi9JMlFwZGpPbzBRaFBvUjlEcW5KT3RRRktzM3RLcHhqaCt0T2li?= =?utf-8?B?VFdncVZSWU85K0JpdGV2cnl6ellLbDYvbUs5b3IrS2pGMnhPR0I5TllRSm5H?= =?utf-8?B?OW9oRDFsRUdUa3hJSkw4S2ZoVmtYRVJNZitRczYyOWZ3cC9LRHZnY0pEcS8y?= =?utf-8?B?aGEySytuMG1FbmFtbk5hdm5IdFBWQzVpRXhUZEsyVnNGajZqL3ozclhxVE0v?= =?utf-8?B?a2JHQW1XdnpVMjJwMld1YllGdDY0Zk5zQ1U1OUhPV0gvc0tnOFhRMk5jYXRq?= =?utf-8?B?QWlQK3FER3dxek01Vy9lc3ZXYnFVd1dpem5qMnNBcE8zQzVJaTlvbzdPT1VB?= =?utf-8?B?b0p2SUlXVDhGNUV4bGt5S2FwTExDb0ZERWo1bi9wcTJ1K1V0NXF2RHdLRCt1?= =?utf-8?B?NnJxaWZ4WWRpRVltNjJ6U2VXNENFZURmZTR2d2tDaFRhVXFVWEJJaDM2c1FH?= =?utf-8?B?ajJZWVVqS3IrVlc0b0xMcXl5aE9sYnptd2RNVzhQYXlKVmhuREhuUW9FcHpZ?= =?utf-8?B?bjVZdkpuUVc3UGJCOWh6dld5Nk5uUVI5Q0lkaUZTWDZtWjdsVDNGSnNWUVNr?= =?utf-8?B?ODkvcExuUG15dzFsT0k5R3VEcEkxY1pnK1IyQVZJQTNCU2ZrWXN0S2dBNTI2?= =?utf-8?B?MnNZdk5kTHErSUVWT25nYkVuUU1Mc3R5V3JKSnZsV1FnSmdoSGRmQkNUV0lY?= =?utf-8?B?VHBYYjZheVpTY3dEZTlLSUpFRmRGenpMZlZuSXNhSGVWQTFTQ1U3b3JNcXBH?= =?utf-8?B?eC9XOG01dkE5MzZSVW5teTlueGxsUWtaMFRFQU5WZndjVkhaSTRrZkNDczg2?= =?utf-8?B?WmpKQ2k0NlBha1QrWUVQbDB4L0pHSFpQWVVjQSt5bGM5RVNqaTA2ajRoK0w3?= =?utf-8?Q?Q3y7QBFx9ZuUoso1Uuxql4Hw26cnaIV8OPI1QVmAhAZ16?=
X-Forefront-PRVS: 038002787A
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(7370300001)(4630300001)(6049001)(6009001)(39410400002)(39400400002)(39450400003)(39830400002)(189002)(24454002)(199003)(377454003)(50466002)(110136004)(4326008)(6486002)(2950100002)(38730400002)(6916009)(7736002)(90366009)(77096006)(53546010)(478600001)(6246003)(117156002)(97736004)(305945005)(413944005)(6666003)(229853002)(2906002)(25786009)(50226002)(68736007)(81166006)(5660300001)(81156014)(23676002)(53936002)(8746002)(7350300001)(8676002)(42186005)(33656002)(3846002)(105586002)(6116002)(47776003)(86362001)(101416001)(106356001)(50986999)(76176999)(57306001)(93886004)(189998001)(36756003)(66066001)(83716003)(82746002)(163123001); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR06MB3444; H:[192.168.1.3]; FPR:; SPF:None;  PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Received-SPF: None (protection.outlook.com: isoc.org does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtCTjZQUjA2TUIzNDQ0OzIzOnV3SnNmWHF4QW5QOFl3ZlhCWVM5WlQwdGxN?= =?utf-8?B?ZFdJUldjTlgxZm1HZy94bngvWFltSG1VRGh1UGE3ancrL0puR2tLZC9ydGph?= =?utf-8?B?R1FIaVJIMUs1WjYxb3EraTR5bnFWNnA3b0RySS8vaC9iYkxXQlMxSWhOTTVp?= =?utf-8?B?UEtRR1h5UFpUenU2WjBHb2hLUGFwTjJzNTVCWmhiOTg0WjhJNVlYNDNEVy9U?= =?utf-8?B?V1BCdHd5R2ZSenVUWUNYT1JSMmxjWjRPNlpNTTREYmVmV2ZOazI4MGczQko2?= =?utf-8?B?NUFOK3NKaVB0VHJxVWdkQXNWTVYyRzhRLy9YMFlkaTRDUHJOVUdJa0o0ejhs?= =?utf-8?B?cmNkbHVsNlZVOStudzRIVmxFYlZqVU9KQk94OGlPeXRLUWR2b2tqa0pjbm5x?= =?utf-8?B?cmMzZ3B3bmU2VWVJTEN2akZZOGFpQ09QTjhmcXNDaklRY0xHakpWSWhPblJv?= =?utf-8?B?bWdRQWV2SGlqcU9WSVVEbUlhMTJrQ0t2OU0reWVHa2xzUC9zMUhDdktIQUw5?= =?utf-8?B?SmpLQS9yMy9oOGdMRU5jeVAwOVFRRVFRUFR4RDJZa25xNndUWllRdTZ2aWZR?= =?utf-8?B?b0kyb1drZ0hweHRRTkEzZjB2NXdKc3dQWmdWakJPWGN6Y0tvcEtHRkpDSGpI?= =?utf-8?B?SklKcmRyOE1jR1FkTEFmbXZwWTNXazhwWS9zdzhoYldiU2cwQ0liRnF6UEln?= =?utf-8?B?WTJiVWNXMitLR2puaDA5Q3h6cEdIaUh3blVaVWordzlYdUtVVFVFeDV3UFJ1?= =?utf-8?B?emhBTXJWOWhYbFRkbStHSlR6QmxiV2FURE9tVVJaTHhJWlRkbWhpUVpkKzJI?= =?utf-8?B?RUVWcThhME8zWWplUmlNelhQbXdKTXlXRUpLSjlXYVJRQ2NNQWNHMFhXdlk0?= =?utf-8?B?a1Nwa01qQkc4bWU2RGxObDVlbkdBbTNFYmlxWmJKUTd2YTQ5T0VsVjBEajIz?= =?utf-8?B?Zld6SkRoWGZvRTlJTmg5cU0xT282aS81aUZjSlBZWTMxMlhyclA4ZlR5UlYv?= =?utf-8?B?c1hGVUs0dGMrOXczQ25tT0xVZGtxNzlGMmpXMDRTVVNmbDBaRUN4ajZlSWh6?= =?utf-8?B?alJicmFoMkgxT0lIcDZOQmxYWU5QUFk4clVJeFdJK0pHNzBMQ3MwNU5STkhI?= =?utf-8?B?cDd6dTNSQlNIclpYMm83cklUcy9PM1RVeG9idzBNcnhKLzc0d0hWWk1TN3Q5?= =?utf-8?B?TXZ1Uk9Uai91R0YzWkUxWjBmOEV5WXN0QmF2MXYrL1luRnltTUt1amQ0bzZa?= =?utf-8?B?ZXdWZDIwa3NOaUZWQWVqU0ZhVWhhcjZyQmFnUFZ0NUNsMUEwWG5OYlZsRW1Q?= =?utf-8?B?TmlmZjhWMXU0SHVaZE5QWi9nZ3J3NjZPb1RHelVQREE1Z2c1cnkrNE1zdUpi?= =?utf-8?B?MXZsRUxhRUlKRnpZWmNkejhRNlp4dzlYcTVqVDV6b3JibmNwVVk2cDc2UWpF?= =?utf-8?B?amNBYWgrUVl6OXZXWXhoZlY2Y3NJRDhOUnVCL0dUMjdmMnE1THlPRWlxVytz?= =?utf-8?B?Sm9VbnlSbVlkb0JEUjh5QmFFcFNJQi90K29jZENWamVMMXQyVUwyTXFvQjcr?= =?utf-8?B?MHZLb25QcHVwUUQ4NUVSZ1F4dUlrK2d2STBydDBKSjNFT0U2ZWszS1BVTWN1?= =?utf-8?B?cDRkRnYvUUtBRWIzTVBEcmNaVXV4WmN3bkQyQm1ZMFpKdlBpbFc4NjNFREUr?= =?utf-8?B?Z3JJaWdrbWtrNHg4NzJ5RG1YSk9ML0t6SCtYc2gyU04wbm92Zk1qbU9WdkpM?= =?utf-8?B?aW9pVHhUL0hoM05Zc2RyOS90TDhYZUE5eFgyTndGZmdxeVVuZFBNTEpqdXJY?= =?utf-8?B?Vk5OT0Jsbko5Q0dyL1E3cnFWYmxjdWs3cjBTbmVaaXFTMjI5Wm5pNUc0Y1Jv?= =?utf-8?B?ZG9TMUVReUNoUGpQbTRhTUNGaHMxRThRTjRIN2NpVDZ5TC94bFpRYzB6RWw3?= =?utf-8?B?MUcrNEJlTExXaGUraHR1dSs1U2xaQjUvb2JiTVRlREdMS1VPbnNVa3p5ejBZ?= =?utf-8?B?WjJCeEtwWUNXZDRVNDNYUUY3cXRwTEFRdHZJQT09?=
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtCTjZQUjA2TUIzNDQ0OzY6QjJwaGZMSy9hWVpPbk5oZ1pHL0F5YXBlL1o3?= =?utf-8?B?ZVh5UGY3cUZUZWN1QWI5dGdlRXVULzRscWhEcUplcGZMOG5xeHk3aU8wc1V3?= =?utf-8?B?SU5YTTAwUmJYbnord3BraDBaTkV3OFplZFJjMStWbkd6SStBTTdTZjlnQ2dJ?= =?utf-8?B?S252MkI0bXFuc0JUait4OFNPY3FqUFdrRjdvS2UvWWFhQWQyMGNnbGYxcFA1?= =?utf-8?B?WkxEc3VVWVFFcHYraGhZbWR5M2pkM1h0VTN5VUJtMFhNZHZZdnFpQzV1andR?= =?utf-8?B?NnlLWWd5b2J5eUhZTG8wVVY2VmQwejdxVHB1WXFSbkl2R2RjRGdkV1BzT2tB?= =?utf-8?B?MTBQSE9nZDUrVGl3TjZxS0NzVUlJSEhBUUxWOU9hSjdJdE1DR3JZY0hqd1ZF?= =?utf-8?B?eUtUckFYeE5vWDhrbi9PeE02OXpWZE9NNWYyOXR2aGRNaC9MSzczcDNNWWsy?= =?utf-8?B?SXZnZE41N1VSRWlPMDNUZkVIYU03VjIyNzRyVys3ZlNYTFJUTGsvNllNM3Ju?= =?utf-8?B?aUlLdDF5V3daajlVREQxcHZoNjVZMWVkZ2o1d21SaGxQdUpwOHNnNHVXc2xQ?= =?utf-8?B?N2JmNUlEdkFPYlpSb29hOHJtMmM2WEFBdEpaaVdOc2Q0R3E3TUkxUDRlMytD?= =?utf-8?B?TTFBdEVoNzF1NmYxM1B0VFJrME13SC9LVnNtQzQrM2J4RkszaERESzhyWEVw?= =?utf-8?B?aFVHdHhHeGpqYjA5cFhJMVFZSm1Lam8rZW9CRnhyZHN3cXJBd2E5cm5yaTlp?= =?utf-8?B?a3R5V3BsYUpjSHlMQWtZSWNNSjdSUUJ0blNZWEptMlBwek9mb2swT3ZwQ0dv?= =?utf-8?B?ME5KRS96eHRnSWhNbGZCUzhmMUpPaGc4NitFa21aZi9RbVBGa0Flb1UvaldV?= =?utf-8?B?Y0hHZHA2cDd0RXkreklTaDJCSHA1cGkxQ2ZBN0NsOGZPNGhGR3BRSUt4c25j?= =?utf-8?B?blVHbHlDa0lJWEpldjRvb0lScmkvQ3d5Y1ZKaXdTN2gwVnlBQ1h3WlpJbUUw?= =?utf-8?B?MGJucEpPMHdORC9HeTNhaElvUm5RL0s2V2t3RjFhdVRpNmZBbkMwV28xT1VK?= =?utf-8?B?RjBBc1RCdU9leEgwdk1HY2thcGxmdGw5NGdHQlZYMFIxTE9LQkY4cnRHNXRG?= =?utf-8?B?N0hTNFpkeHhhV24wNSt2akFRcjlaaDF1VDZVa0p0cHUzWUZGQ3BSelJXWmR5?= =?utf-8?B?bzBoUXpIY2hwa01GaU14cE9ZVFo3U3hvK3BhajFSODZPRE1oK293UHRwcnBW?= =?utf-8?B?NU9BVk5FcUE1MFBPTnZsaFVuc1g2Z1JZeTRPZkdITnlPb1pEWXpuWk1CRzZu?= =?utf-8?Q?+nIJeWjTJywV7xtR0kAH8nWNEfYHgNE=3D?=
X-Microsoft-Exchange-Diagnostics: 1; BN6PR06MB3444; 5:05rObKg0sdpDhS255PjJOoYjY7hsx0KEI1VgaC/4RrEksZ0pCzqdV1YqGXFz6VYcUuvC4VQM0WsMawO++04CU84aagwLZiGeXpzX60Hdty2nFEfilWTGq9qGlNMfQP5PXaODR0er9zIqklNFZKzPazivYTlqxau7a6P0QnIFk+DVIgzNYgRNyh8zZAkPaUxZjWUIKVQK37CgJ1d4IV5aw5WntdmeL4OCw/f1oYvxRF1+Oj7cl8ONXfJ71WFCwCkedhvCmnX6d5nKMTenwYXoWekJzw0mAGyZHYqPhmFSrU7DI2B/UP85EOneBc3la9jwFNEVlORh/9T9k0Rhu63WbnX921pM1GBOIHIrY3SgceLSACAnlTG2OeU+kCaYCKweUBphFWZcGQioO3NIEz6alnBieb63KoUk3s3CppG3mQbdaqxZ9B6CFlJ86EFMBpwtznc6BLPmv1j9AWnUnoC0etzJl3sqNWKpiK5CNASN0HGDhPKTzh8+M+0mW+UtBqhk; 24:lr+k9g47qd/WJWK9qwkHNvFYE1qHeE4X/eXJbmGGA16v7EUPUQgYpHHpSL3FGrGeyQrB0ysAQVEF14LRGVXrZzqGoLQ5IpfFw3Ut2BZltSw=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; BN6PR06MB3444; 7:cZ64eLypbIiWH8gd1lA0RDsPPrdcA/TNXHivWxvy9V45nulJ1RKjtjWitsXjSzMnScstJieRUv86ctnrmqv6vKUU4neN8XaKgIXwt5NYPc+/3O4MoqvEcZ0zncakrbrh/7E6a1BI4Aisx0H0VTmXFr1By/b+KO/zbZvqGPXCOPkzF0SxfQIbSnCgeIzjdnxIMnjDCBDm0V+bf3NCjXzma8Km0vx9WmdY6AxQ1vj8635ifFbujv1Mt2VwkVw95NsvxsKMyHidUi3zB+6hNo4yiYdV2CRBUuGuOnnnKoiichGkxFZedlHP9Mt6XZA+3AtDqGy9qRl3WkkwO+sCv2I3ZFzZ+Uwam7sehn9OuVmUKy6wMT5GrjfV+XJAdfqoPS2xbXCOuPh34MRu+WGHdZtCYNZaU4HhoSUCWmLtiXAuyjo+Hz/Mio3JHQI2f8fl+jMh0twPlgQiFmsva4jL4cBQ80YfwCRYWr3DwxnD8O94ISgIycMc2bC7gBgV5N/d09n8xr3PFWRTIoHhTLm6/4iYZrQ7Uc+UFAB5+Dz/66IZhXx63xkzrv78sdyUxNCJr/HzLZhiIvmhKTTpaRNLk0pvFeoIUBqx4k9Co9OULYrRO6jTma6Cm6rFjt5VIvg9SwynvtokTIdPJM2U81reoNWaxKtgXS9lSSLWwGceW24jJ9pDm1htaJpr9JjHIB1Uzja5nV3YUsUzbzkvlshEF2o1jrPK5nD3nONgwOOY/SHWGqLkKEu4qrcf5+ilkzXvoIGv79+tE25ed3cv9ICazSEx+qH0+P7jM71cCWPSV5bi524=
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 26 Jul 2017 05:22:22.5897 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR06MB3444
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/u7CVY_l9r8FXvy3-bSs07Pw5YLo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 05:22:28 -0000

+ 1

Ray

> On Jul 21, 2017, at 10:32 AM, Andrew Sullivan <ajs@anvilwalrusden.com> =
wrote:
>=20
> Dear colleagues,
>=20
> On Tue, Jul 18, 2017 at 11:13:10AM +0200, Yoav Nir wrote:
>> The new site is focused not on the existing people active in the =
IETF. It=E2=80=99s focused on the general public.  The place where work =
gets done these days is datatracker.
>>=20
>=20
> I have had a look at the beta site, and it seems to me that we have at
> least three possible audiences:
>=20
>    1.  People who wonder what an IETF is and how it might be useful
>    to them.  That actually is an important function of a website, and
>    despite the arguments about how the IETF isn't about marketing
>    organization (and the xkcd observations about university websites)
>    we cannot ignore this function.  To some extent, we are competing
>    with other ways of developing the Internet -- "living standards",
>    code as standard, multilateral standards bodies, &c -- and if we
>    think our way is good for some cases we do in fact need to market
>    that.  I think the beta site is obviously better at that than our
>    current site, which appears to be designed with a MEMBERS ONLY
>    sign on the front.  We are the hardest club to join given that we
>    don't have membership. I think the beta site is trying to make
>    that burden a little less, and I believe it is a good thing.
>=20
>    2.  People who already are familiar with the IETF and are working
>    here.  The beta site says it's supposed to be the "new front
>    door".  I don't know about all of you, but in my own house I also
>    know how to enter by the other doors.  Maybe we just need to use a
>    different entrance?
>=20
>    3.  People whose connectivity makes the more graphically intense
>    and somewhat larger site less useful.  I think it would be useful
>    to analyse the extent to which this is a real problem, and whether
>    the trade-off is adequate for the particular use case we have in
>    mind.  After all, loading this (still not huge) web page is hardly
>    the most bandwidth-intensive thing a plausible IETF participant is
>    likely to do.  Moreover, it's not clear whether the problem in
>    this case is slow backhaul links or slow local/last-mile links; if
>    it's the latter, more IXes (and CDNs) are likely good enough
>    mitigations.  This seems like an issue that could use some
>    empirical data, but I am not sure how to get it.  Perhaps the
>    participants of GAIA would hae some ideas.
>=20
> I appreciate the effort to make these changes in public with lots of
> consultation: I know how much harder it is to run a project this way,
> but I think it's a good sign that the tools are as usual being
> developed this way.
>=20
> Best regards,
>=20
> A
>=20
> --=20
> Andrew Sullivan
> ajs@anvilwalrusden.com
>=20


From nobody Tue Jul 25 23:51:47 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A64E131CDE for <ietf@ietfa.amsl.com>; Tue, 25 Jul 2017 23:51:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 aWdaaPmbe-4K for <ietf@ietfa.amsl.com>; Tue, 25 Jul 2017 23:51:43 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 8BA0812EC3F for <ietf@ietf.org>; Tue, 25 Jul 2017 23:51:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id B3B462CFE6; Wed, 26 Jul 2017 09:51:41 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mb62H7P9JBEL; Wed, 26 Jul 2017 09:51:41 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:1829::130]) by p130.piuha.net (Postfix) with ESMTP id 7284D2CFDF; Wed, 26 Jul 2017 09:51:40 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Subject: Re: Revamp of the www.ietf.org website
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_6DB92548-C872-4582-ACDC-FFC1A8C4F3D7"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <B5AD9DB5-A261-4924-98F4-0D5945E68366@isoc.org>
Date: Tue, 25 Jul 2017 23:51:39 -0700
Cc: IETF Discussion <ietf@ietf.org>
Message-Id: <D3576F2D-4D8F-4FAA-9E6E-80D2E08FE5A8@piuha.net>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6394482@GLKXM0002V.GREENLNK.net> <39D1C0A9-DB43-42DD-BD3F-7D636856ECEF@gmail.com> <20170721083215.a2qdgfrpg2jf6irq@mx4.yitter.info> <B5AD9DB5-A261-4924-98F4-0D5945E68366@isoc.org>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/u-V4JAmlyEAZh6L72x0i56FQG8o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 06:51:46 -0000

--Apple-Mail=_6DB92548-C872-4582-ACDC-FFC1A8C4F3D7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

FWIW, I also agree with Andrew.

But I had an added comment about the front or other entrances.
If I look at the current IETF website, I don=92t think it would be too
hard for the =93front door=94 to be an entrance for everybody. Most
of us don=92t need an explanation of what the IETF is or the like,
but even on the current website, there aren=92t too many things
that I normally click. I click on the =93next meeting=94, =93next =
meeting=92s
agenda=94 a *lot*. I don=92t remember if the datatracker is hiding
somewhere on the current website, but I certainly go to the
datatracker a lot. I also go to the WG list quite often, to
look up something that I don=92t remember from an unfamiliar
area etc. I click on the blog now and then. But that=92s about
it.

If those things were one click from the new web site=85
and the rest would be neatly organised, that would certainly
do it for me. I don=92t see how adding those to the otherwise
more =93information about the IETF=94 website would be hard.

For added bonus, maybe the most recent last
call / most recent blog article / most recent call for
hotel reservations opening or the like were to be also
displayed, the front door would give me an added
benefit of possibly stumbling on information that I
needed.

Jari


--Apple-Mail=_6DB92548-C872-4582-ACDC-FFC1A8C4F3D7
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJZeDv8AAoJEM80gCTQU46qO7MP/0vpW0r2jL/5zLebhUfe84dM
xBsUcXYiTwmeOK4xmFz2epsZGg1sNN76eJ+1WVNWaJvMCTDtDkdbM5m4OS5FvxDh
VSBvtKsy7ejY0oUcLGCkaxousXe3xxBo9Sp2mAwW8PpKnRxqI6Y4XsCRzf4Dvp6x
AVVyBP4OctsjeG8dZLlA8GePCrkexiusOCVLSyfBPFCc5G3vzE3Mzk194zCVfZgH
SNMhKqjhT17FokGDzSrRl/K3+1r24zXIyz9BM2SXEF1TXCIGwssPOyao66+uNWBb
Nu/1bJFmkzlyUVGPraPkS926CiTVt7R6NjKZ5IXGHLQezhlpldTPkwg5oVroq4h4
AQj9KjKzar6Jg4cDFbUhZQWmisdq1lISA0XyFXYU9DWcK90kw6dqEQU1FqTShNCn
48yFrr31VMXXUIvp41TakjYM4EAFFS3T7qUyPIBAUV6X+PkU4QplDcAHOrD7svPb
l+V8vIgWNCrHf37g0xE4q+oz71391PsFKTlJ7urTkrQZDdwKcUOVK1AXiUsEr/He
KSyKQxVyg54lrZtbAHKFIiZvcHcyW1+OIjYiBZch7eJ2iUHk87xbNw5Y4uUkmeU7
ce4IhHsjrG/A4xc5O9/6jmUQ0tx2U/G+MJT2DbKcEnBMlu3h/d/DxpoVWVbuA0Mn
7ryi1agjqhttz1TnOFPJ
=jQgM
-----END PGP SIGNATURE-----

--Apple-Mail=_6DB92548-C872-4582-ACDC-FFC1A8C4F3D7--


From nobody Wed Jul 26 01:45:56 2017
Return-Path: <lhotka@nic.cz>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 28182131FD6; Wed, 26 Jul 2017 01:45:48 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ladislav Lhotka <lhotka@nic.cz>
To: <yang-doctors@ietf.org>
Cc: i2rs@ietf.org, ietf@ietf.org, draft-ietf-i2rs-yang-l3-topology.all@ietf.org
Subject: Yangdoctors early review of draft-ietf-i2rs-yang-l3-topology-10
X-Test-IDTracker: no
X-IETF-IDTracker: 6.57.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150105874813.26401.2245891817517041568@ietfa.amsl.com>
Date: Wed, 26 Jul 2017 01:45:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/S0XtdWo6XEW9NshzOIs7ZhWuirY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 08:45:48 -0000

Reviewer: Ladislav Lhotka
Review result: Ready with Issues

This YANG module and I-D belong to an extensible suite of data models
addressing multi-layered network topology. It is an interesting, even
if somewhat atypical, application of YANG.

The entire network topology suite seems well thought out, and it is
apparent that the document has already undergone several rounds of
discussions and iterations. It is also positive that the document
deals with possible overlaps with other YANG modules such as
ietf-interfaces or ietf-hardware. Of course, an ultimate acid test of
the network topology suite will come with applications to real-life
network.

My review below raises several issues that need to be addressed
(especially #1). Some of them are related to design decisions
described in draft-ietf-i2rs-yang-network-topo. Apart from that, I
believe the document is ready to be published.

*** Comments to draft-ietf-i2rs-yang-network-topo-14:

1. With YANG 1.1, the network type information looks like a perfect
   candidate for identities (with multiple inheritance). Instead, it
   is modelled with presence containers, which is cumbersome and
   redundant. I don't see any reasons for doing so, if there are any,
   then they should be explained in sec. 4.4.8.

2. The document defines "supporting network" and then says "A
   supporting network is in effect an underlay network." In the
   subsequent text "underlay network" is used almost exclusively. So
   perhaps the term "supporting network" should be dropped altogether?

3. The text should be better aligned with the terminology of
   draft-ietf-netmod-revised-datastores. In particular,
   "system-controlled" should be used instead of "server-provided".

4. Is it necessary to use URIs for identifying all objects in the
   data model. URIs are difficult to use, so applications are likely
   to introduce some abbreviations and keep an internal mapping, which
   could cause problems, e.g. when matching objects in notifications
   with a GUI representation. In my view, it should be sufficient to
   use URIs for network-id and plain strings for other IDs, because
   all other objects are encapsulated inside a network, so their name
   conflicts shouldn't matter.

*** Comments to draft-ietf-i2rs-yang-l3-topology-10

5. The type of "router-id" should be "yang:dotted-quad" and not
   "inet:ip-address" because the latter means both IPv4 and IPv6
   address, possibly also with a zone index.

6. Both prefix and link attributes include the "metric" parameter. It
   should be explained what they mean. In the context of ietf-routing
   the option of including "metric" as a general route parameter was
   discussed and finally rejected because different routing protocol use
   metrics with different semantics and properties. I wonder if it is
   the same case here. 

*** Formal issues and typos

7. Both documents should refer to draft-ietf-netmod-yang-tree-diagrams
   rather than describe the notation of tree diagrams in the text.

8. Sec. 7 in draft-ietf-i2rs-yang-l3-topology-10: s/moodel/model/



From nobody Wed Jul 26 02:23:55 2017
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED3B61318A2 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 02:23:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level: 
X-Spam-Status: No, score=-4.302 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_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
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 C3LPHNFzu4Nt for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 02:23:50 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8FCCF129B30 for <ietf@ietf.org>; Wed, 26 Jul 2017 02:23:49 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6Q9McnV011877; Wed, 26 Jul 2017 10:22:43 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v6Q9McnV011877
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1501060978; bh=MCOZhXyy2wLkLwidhW+6SxO6wrY=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=BfnXwSh8XdlkAdTEA4M/+2GfRdvY1VogX9Ig+Fi0aI9wR5hLZ1/Ic3cPZmghV7VPu N/Oqe1EkHV/U/i3nq6CftBICgRops72w546QaqtohUNmEwwvlmtEyYxau+eMxYFvfS Pckn0MgDZbo1BP9WAD8aiMLYTRiWwLsGFuQrNrBQ=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id y6PAMX1133802875OO ret-id none; Wed, 26 Jul 2017 10:22:58 +0100
Received: from 20010a88d51011.ipv6.customer.clara.net (20010a88d51011.ipv6.customer.clara.net [IPv6:2001:a88:d510:1101:3c4c:7665:1a1:1e34] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6Q9MQaR003486 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Jul 2017 10:22:26 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Revamp of the www.ietf.org website
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <D3576F2D-4D8F-4FAA-9E6E-80D2E08FE5A8@piuha.net>
Date: Wed, 26 Jul 2017 10:22:27 +0100
Cc: Andrew Sullivan <ajs@anvilwalrusden.com>, IETF Discussion <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|93a21cfe95bdba7176c7d3d313daf9d5y6PAMX03tjc|ecs.soton.ac.uk|28C0B89A-73A1-4CC3-8903-822D07F2383F@ecs.soton.ac.uk>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6394482@GLKXM0002V.GREENLNK.net> <39D1C0A9-DB43-42DD-BD3F-7D636856ECEF@gmail.com> <20170721083215.a2qdgfrpg2jf6irq@mx4.yitter.info> <B5AD9DB5-A261-4924-98F4-0D5945E68366@isoc.org> <D3576F2D-4D8F-4FAA-9E6E-80D2E08FE5A8@piuha.net> <28C0B89A-73A1-4CC3-8903-822D07F2383F@ecs.soton.ac.uk>
To: Arkko Jari <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.3273)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=y6PAMX113380287500; tid=y6PAMX1133802875OO; client=relay,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v6Q9McnV011877
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/velbKSRQpoCSmUkM7iSFOUGCpx0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 09:23:53 -0000

Hi,

> On 26 Jul 2017, at 07:51, Jari Arkko <jari.arkko@piuha.net> wrote:
>=20
> FWIW, I also agree with Andrew.
>=20
> But I had an added comment about the front or other entrances.
> If I look at the current IETF website, I don=E2=80=99t think it would =
be too
> hard for the =E2=80=9Cfront door=E2=80=9D to be an entrance for =
everybody. Most
> of us don=E2=80=99t need an explanation of what the IETF is or the =
like,
> but even on the current website, there aren=E2=80=99t too many things
> that I normally click. I click on the =E2=80=9Cnext meeting=E2=80=9D, =
=E2=80=9Cnext meeting=E2=80=99s
> agenda=E2=80=9D a *lot*. I don=E2=80=99t remember if the datatracker =
is hiding
> somewhere on the current website, but I certainly go to the
> datatracker a lot. I also go to the WG list quite often, to
> look up something that I don=E2=80=99t remember from an unfamiliar
> area etc. I click on the blog now and then. But that=E2=80=99s about
> it.

Mentally I have already retreated from beta.ietf.org as a useful page =
for a participant. But I can accept that; the current page is =
unwelcoming or an =E2=80=9Coutsider=E2=80=9D, and we could use a better =
public =E2=80=9Cface=E2=80=9D.

> If those things were one click from the new web site=E2=80=A6
> and the rest would be neatly organised, that would certainly
> do it for me. I don=E2=80=99t see how adding those to the otherwise
> more =E2=80=9Cinformation about the IETF=E2=80=9D website would be =
hard.

Well, if it=E2=80=99s =E2=80=9Cone click away=E2=80=9D, participants =
will just bookmark or go directly to that page, and not www.ietf.org. I =
know I will.  Just like I sometimes also go directly to the datatracker.=20=


> For added bonus, maybe the most recent last
> call / most recent blog article / most recent call for
> hotel reservations opening or the like were to be also
> displayed, the front door would give me an added
> benefit of possibly stumbling on information that I
> needed.

Put all that on a one screen, participant oriented =E2=80=9Cindex=E2=80=9D=
 page that we can go directly to.  Leave www.ietf.org to be the public =
shop window.

Tim


From nobody Wed Jul 26 02:40:41 2017
Return-Path: <prvs=1380c4bcea=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39736131897 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 02:40:40 -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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
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 9kV-H0RaWDmE for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 02:40:37 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F8491287A5 for <ietf@ietf.org>; Wed, 26 Jul 2017 02:40:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1501062035; x=1501666835; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=j1PinELqr9mtkpoWJb6Cd1jMW YRT26/9q6GjhrF+hfE=; b=a3nfxs2v3Njcjw0ZVvEGoSn452JCwIe2zEux0qaOK ICc2BDROB3xodKcqIRbxAFtUjjoZ/2ZEGbNixWnbaYBVtVwwy3QA7L0iX+S6AAPs IPOPXKrYi3aNvhEqdAWzzNvfUq/4HizhnhJXubZhmOgcYAntY1QpUlH/sMvNcWfC YE=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=Y64U07fHHEFYWZC4Tbrfwm0QU/uCqIVwB54DN+Wgq0cA9WAVAzpb5ggrQt/t CrVv4NwH3wVHEBhuGI2AnnRcqVcoDHfVEH//jj00LD4HvTe/7/GQ1YAyE kdUoYYcwX4Oei6OBuizisCr0LkB1oMQl8h4u4XjgI7AwR3GiWFu/40=;
X-MDAV-Processed: mail.consulintel.es, Wed, 26 Jul 2017 11:40:35 +0200
X-Spam-Processed: mail.consulintel.es, Wed, 26 Jul 2017 11:40:34 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005487057.msg for <ietf@ietf.org>; Wed, 26 Jul 2017 11:40:34 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170726:md50005487057::y6t/BL3g8ZiTgpim:000020J0
X-Return-Path: prvs=1380c4bcea=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.24.1.170721
Date: Wed, 26 Jul 2017 11:40:30 +0200
Subject: Re: Revamp of the www.ietf.org website
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IETF Discussion <ietf@ietf.org>
Message-ID: <B98EF5DC-4932-460A-9D25-20CAC5CB0744@consulintel.es>
Thread-Topic: Revamp of the www.ietf.org website
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6394482@GLKXM0002V.GREENLNK.net> <39D1C0A9-DB43-42DD-BD3F-7D636856ECEF@gmail.com> <20170721083215.a2qdgfrpg2jf6irq@mx4.yitter.info> <B5AD9DB5-A261-4924-98F4-0D5945E68366@isoc.org> <D3576F2D-4D8F-4FAA-9E6E-80D2E08FE5A8@piuha.net> <28C0B89A-73A1-4CC3-8903-822D07F2383F@ecs.soton.ac.uk> <EMEW3|93a21cfe95bdba7176c7d3d313daf9d5y6PAMX03tjc|ecs.soton.ac.uk|28C0B89A-73A1-4CC3-8903-822D07F2383F@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|93a21cfe95bdba7176c7d3d313daf9d5y6PAMX03tjc|ecs.soton.ac.uk|28C0B89A-73A1-4CC3-8903-822D07F2383F@ecs.soton.ac.uk>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1HX3QEDuBH-GQWKSUH1z6FRRhHg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 09:40:40 -0000

I think we need to have a =E2=80=9Cnice=E2=80=9D and attractive =E2=80=9Cpu=
blic face=E2=80=9D for anyone NOT being an actual participant, and in gener=
al I like the beta (adding the social networks thing that I already mention=
 in a previous email).

I also agree that most of the frequent =E2=80=9Cparticipants/contributors=
=E2=80=9D, often go directly to the page they want (bookmarks or just start=
 typing =E2=80=9Cdatatra =E2=80=A6=E2=80=9D in the URL space, or go to the =
home and click =E2=80=9Cnext meeting=E2=80=9D or whatever.

I think there are several ways to do that, for example (just to mention a f=
ew) and they can be combined easily:

1) The beta =E2=80=9Ctools=E2=80=9D section can have more =E2=80=9Cdirect=
=E2=80=9D links (may be instead of Tools rename it to =E2=80=9Cfrequent sec=
tions=E2=80=9D or something similar) to actual subdomains such as datatrack=
er, blog, rfc-editor, email archive, iesg, iab, irtf, iaoc, ipr, liaisons, =
secretariat, etc.
2) Have a =E2=80=9Ccustomize=E2=80=9D section so you can choose what is you=
r =E2=80=9Cdefault=E2=80=9D entry page.
3) Have a =E2=80=9Ccustomize=E2=80=9D section so you can choose your =E2=80=
=9Cpreferred=E2=80=9D home page and default =E2=80=9Ctop=E2=80=9D links / m=
enu.
4) Use cookies or something else to remember what was your last visit.
5) etc

It should not be a big issue for an existing participant to =E2=80=9Cadjust=
=E2=80=9D the first time the beta is moved to production, to adjust what he=
 prefers to get, but definitively our front door should be nice for anyone =
contacting IETF for a first time or non-frequently visitors.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Tim Chown <tjc@ecs.soton.ac.u=
k>
Responder a: <tjc@ecs.soton.ac.uk>
Fecha: mi=C3=A9rcoles, 26 de julio de 2017, 11:24
Para: Arkko Jari <jari.arkko@piuha.net>
CC: IETF Discussion <ietf@ietf.org>
Asunto: Re: Revamp of the www.ietf.org website

    Hi,
   =20
    > On 26 Jul 2017, at 07:51, Jari Arkko <jari.arkko@piuha.net> wrote:
    >=20
    > FWIW, I also agree with Andrew.
    >=20
    > But I had an added comment about the front or other entrances.
    > If I look at the current IETF website, I don=E2=80=99t think it would=
 be too
    > hard for the =E2=80=9Cfront door=E2=80=9D to be an entrance for every=
body. Most
    > of us don=E2=80=99t need an explanation of what the IETF is or the li=
ke,
    > but even on the current website, there aren=E2=80=99t too many things
    > that I normally click. I click on the =E2=80=9Cnext meeting=E2=80=9D,=
 =E2=80=9Cnext meeting=E2=80=99s
    > agenda=E2=80=9D a *lot*. I don=E2=80=99t remember if the datatracker =
is hiding
    > somewhere on the current website, but I certainly go to the
    > datatracker a lot. I also go to the WG list quite often, to
    > look up something that I don=E2=80=99t remember from an unfamiliar
    > area etc. I click on the blog now and then. But that=E2=80=99s about
    > it.
   =20
    Mentally I have already retreated from beta.ietf.org as a useful page f=
or a participant. But I can accept that; the current page is unwelcoming or=
 an =E2=80=9Coutsider=E2=80=9D, and we could use a better public =E2=80=9Cf=
ace=E2=80=9D.
   =20
    > If those things were one click from the new web site=E2=80=A6
    > and the rest would be neatly organised, that would certainly
    > do it for me. I don=E2=80=99t see how adding those to the otherwise
    > more =E2=80=9Cinformation about the IETF=E2=80=9D website would be ha=
rd.
   =20
    Well, if it=E2=80=99s =E2=80=9Cone click away=E2=80=9D, participants wi=
ll just bookmark or go directly to that page, and not www.ietf.org. I know =
I will.  Just like I sometimes also go directly to the datatracker.=20
   =20
    > For added bonus, maybe the most recent last
    > call / most recent blog article / most recent call for
    > hotel reservations opening or the like were to be also
    > displayed, the front door would give me an added
    > benefit of possibly stumbling on information that I
    > needed.
   =20
    Put all that on a one screen, participant oriented =E2=80=9Cindex=E2=80=
=9D page that we can go directly to.  Leave www.ietf.org to be the public s=
hop window.
   =20
    Tim
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Wed Jul 26 03:31:11 2017
Return-Path: <swmike@swm.pp.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 715F1129B7A for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 03:31:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level: 
X-Spam-Status: No, score=-4.302 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_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 dH7BRT_uhMQF for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 03:30:58 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (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 A9A97131C27 for <ietf@ietf.org>; Wed, 26 Jul 2017 03:30:58 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 8E2AEA2; Wed, 26 Jul 2017 12:30:55 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1501065055; bh=MaU6l7TjPiy+I8GIRfsJhNRCmVymy1nT/041b06NgSU=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=r9/UY7XjIKktecD2HyXOfcgUIX3oSiNYFKH9b/9AVl4L//rsoZNBlmEYJgjQOrlvn 1yTUrvCT4I3Q32lA5ZPuYQv1YkUWjLcV2lHHW8STUM90QOoLfjeq9OsxTvoQXi+QvY BRBJm4ME7Pm3t6mgVj3yxbJKq/Ka5ly13DwHQckE=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 89498A1; Wed, 26 Jul 2017 12:30:55 +0200 (CEST)
Date: Wed, 26 Jul 2017 12:30:55 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Russ Housley <housley@vigilsec.com>
cc: IETF <ietf@ietf.org>
Subject: Re: Revamp of the www.ietf.org website
In-Reply-To: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com>
Message-ID: <alpine.DEB.2.02.1707261214090.29742@uplift.swm.pp.se>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FPIxJtU3YasoX3MKua5cJSLZvno>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 10:31:01 -0000

On Sat, 15 Jul 2017, Russ Housley wrote:

> Please take a look. We will be tracking issues that need addressing at:
>
>   https://github.com/ietf/www.ietf.org/issues

The new page follows the tragic becoming-common-everywhere of using font 
size that is way too big. In Chrome on MacOS the old page looks great, 
font size is perfect, lots of information.

The new one, I need to use my CSS plugin to bring it down to 75% or less 
before it even starts to become remotely useful.

If I go to for instance:

https://beta.ietf.org/about/who/

There is a useful "about" list of articles to the right. If I click on 
some of those, I get a similar page with the same list of articles, some 
other items in that list doesn't contain this.

Same thing at https://beta.ietf.org/standards/rfcs/

I also chime in with earlier comments about scrolling and lack of 
information. If the new IETF page is going to be this devoid of 
information collected in a single place, where is my "expert mode" button? 
The left list of things on the old web page was excellent.

The current page seems to be all about introducing new people to the IETF. 
This is great, but I know a lot of this already, and I want a good, dense, 
overview page of everything available.

If I go to https://beta.ietf.org/how/meetings/upcoming/99/ this seems to 
be close to what I need, but I just HATE the extra step of clicking on 
"Agendas and Meeting materials" to have a submeny float out (slowly) and 
then I have to click again. I don't like text moving around, especially 
not scrolling around, in its own little thingies.

Old work flow:

Go to http://ietf.org. Press meeting link. Press agenda (html). Boom, 
done.

New work flow:

Go to http://beta.ietf.org (wait noticably longer for page to load). Press 
tools. Watch popup. Press "IETF99 Prague". Wait. Scroll. Press "Agendas 
and Meeting materials". Watch animation. Press "Agenda (HTML)". Done.

So while the new web page looks nicer and probably is a lot less daunting 
to newcomers, it's a considerably worse tool to actually get to 
information you need.

So if this is going to become the new web page, can I please at least have 
a densely packed "expert mode" page with all the links densly packed, just 
like the old page. Please?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Wed Jul 26 05:46:06 2017
Return-Path: <shares@ndzh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89624131C95; Wed, 26 Jul 2017 05:46:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.945
X-Spam-Level: 
X-Spam-Status: No, score=0.945 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845] 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 W9G3Tcrcuva5; Wed, 26 Jul 2017 05:46:02 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (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 863F1131C8E; Wed, 26 Jul 2017 05:45:59 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=70.194.20.65; 
From: "Susan Hares" <shares@ndzh.com>
To: "'Ladislav Lhotka'" <lhotka@nic.cz>, <yang-doctors@ietf.org>
Cc: <i2rs@ietf.org>, <ietf@ietf.org>, <draft-ietf-i2rs-yang-l3-topology.all@ietf.org>
References: <150105874813.26401.2245891817517041568@ietfa.amsl.com>
In-Reply-To: <150105874813.26401.2245891817517041568@ietfa.amsl.com>
Subject: RE: Yangdoctors early review of draft-ietf-i2rs-yang-l3-topology-10
Date: Wed, 26 Jul 2017 08:39:50 -0400
Message-ID: <00a001d3060c$46a59fb0$d3f0df10$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGgyIYTdDwZMCgA10mmEvcrPTJMKaLKh05w
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hpjSLQxtNKNeMxMnvEpZYYflBNM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 12:46:05 -0000

Lada:

Thank you for reviewing the draft with such a careful eye to now and the =
future.  Please look for a response from Alex within a few days, .

Sue=20

-----Original Message-----
From: Ladislav Lhotka [mailto:lhotka@nic.cz]=20
Sent: Wednesday, July 26, 2017 4:46 AM
To: yang-doctors@ietf.org
Cc: i2rs@ietf.org; ietf@ietf.org; =
draft-ietf-i2rs-yang-l3-topology.all@ietf.org
Subject: Yangdoctors early review of draft-ietf-i2rs-yang-l3-topology-10

Reviewer: Ladislav Lhotka
Review result: Ready with Issues

This YANG module and I-D belong to an extensible suite of data models =
addressing multi-layered network topology. It is an interesting, even if =
somewhat atypical, application of YANG.

The entire network topology suite seems well thought out, and it is =
apparent that the document has already undergone several rounds of =
discussions and iterations. It is also positive that the document deals =
with possible overlaps with other YANG modules such as ietf-interfaces =
or ietf-hardware. Of course, an ultimate acid test of the network =
topology suite will come with applications to real-life network.

My review below raises several issues that need to be addressed =
(especially #1). Some of them are related to design decisions described =
in draft-ietf-i2rs-yang-network-topo. Apart from that, I believe the =
document is ready to be published.

*** Comments to draft-ietf-i2rs-yang-network-topo-14:

1. With YANG 1.1, the network type information looks like a perfect
   candidate for identities (with multiple inheritance). Instead, it
   is modelled with presence containers, which is cumbersome and
   redundant. I don't see any reasons for doing so, if there are any,
   then they should be explained in sec. 4.4.8.

2. The document defines "supporting network" and then says "A
   supporting network is in effect an underlay network." In the
   subsequent text "underlay network" is used almost exclusively. So
   perhaps the term "supporting network" should be dropped altogether?

3. The text should be better aligned with the terminology of
   draft-ietf-netmod-revised-datastores. In particular,
   "system-controlled" should be used instead of "server-provided".

4. Is it necessary to use URIs for identifying all objects in the
   data model. URIs are difficult to use, so applications are likely
   to introduce some abbreviations and keep an internal mapping, which
   could cause problems, e.g. when matching objects in notifications
   with a GUI representation. In my view, it should be sufficient to
   use URIs for network-id and plain strings for other IDs, because
   all other objects are encapsulated inside a network, so their name
   conflicts shouldn't matter.

*** Comments to draft-ietf-i2rs-yang-l3-topology-10

5. The type of "router-id" should be "yang:dotted-quad" and not
   "inet:ip-address" because the latter means both IPv4 and IPv6
   address, possibly also with a zone index.

6. Both prefix and link attributes include the "metric" parameter. It
   should be explained what they mean. In the context of ietf-routing
   the option of including "metric" as a general route parameter was
   discussed and finally rejected because different routing protocol use
   metrics with different semantics and properties. I wonder if it is
   the same case here.=20

*** Formal issues and typos

7. Both documents should refer to draft-ietf-netmod-yang-tree-diagrams
   rather than describe the notation of tree diagrams in the text.

8. Sec. 7 in draft-ietf-i2rs-yang-l3-topology-10: s/moodel/model/




From nobody Wed Jul 26 07:00:23 2017
Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B489E129562; Wed, 26 Jul 2017 07:00:21 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: ietf@ietf.org
Subject: IETF 100 Registration and Hotel Reservations Open!
X-Test-IDTracker: no
X-IETF-IDTracker: 6.57.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: agenda@ietf.org
Message-ID: <150107762165.23133.6738319854502205219.idtracker@ietfa.amsl.com>
Date: Wed, 26 Jul 2017 07:00:21 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cMzd0bDR8z4SxK6-X2FhwcJ2Wpk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 14:00:22 -0000

IETF 100 
Singapore
November 11-17, 2017
Host: Cisco

IETF 100 Information: https://ietf.org/meeting/100/index.html
Register online at: https://ietf.org/meeting/register.html

1.  Registration
2.  Visas & Letters of Invitation
3.  Accommodations

1. Registration:
	A. Early-Bird Registration: USD 700.00, if paid in full prior to 23:59 UTC 2017-11-03
	B. After Early-Bird cutoff: USD 875.00
	C. Full-time Student Registrations: USD 150.00 (with proper ID)
	D. One Day Pass Registration: USD 375.00
	E. Registration Cancellation   
	Cutoff for registration cancellation is Monday, 06 November 2017 at UTC 23:59. 
	Cancellations are subject to a 10% (ten percent) cancellation fee if requested by 
	that date and time.
	F. Online Registration and Payment ends Friday, 10 November, 2017, 17:00 local Singapore time
	G. On-site Registration begins on Sunday, 12 November 2017 at 10:00 local Singapore time.

2. Visas & Letters of Invitation:

	Letters of invitation are available through the registration
	system. Once you register for IETF 100 you may request a local
	letter of invitation through a link in your confirmation email or
	the self-service portal. 

3.  Accommodations:
	
NOTE: Breakfast will NOT be provided by the IETF for this meeting.

	1. Swissotel "The Stamford" Singapore - Meeting Venue (Headquarters Hotel, block of 330 rooms)
	Room Rate:  $213 (single) $242 (single with breakfast) $213 (double) $264 (double with breakfast) USD. Room Rates include in-room high-speed Internet access and complimentary access to in-house Health Club (includes pool and fitness room). Breakfast is conditional upon reservation type.
	Service charge of 10% and GST of 7% (taxes subject to change) are excluded from the above rates.
	Reservation Cutoff Date: 30 October 2017
	Cancel with No Penalty: 48 hours prior to arrival
	Distance to Meeting Venue: N/A
	More detail at: http://www.ietf.org/meeting/100/hotel.html
	Reservations: https://aws.passkey.com/event/49212203/owner/1452331/home
	
	2. Fairmont Singapore - Meeting Venue (#2 Headquarters Hotel, block of 270 rooms)
	Room Rate:  $235 (single) $256 (single with breakfast) $235 (double) $278 (double with breakfast) USD. Room Rates include in-room high-speed Internet access and complimentary access to in-house Health Club (includes pool and fitness room). Breakfast is conditional upon reservation type.
	Service charge of 10% and GST of 7% (taxes subject to change) are excluded from the above rates.
	Reservation Cutoff Date: 30 October 2017
	Cancel with No Penalty: 48 hours prior to arrival
	Distance to Meeting Venue: 85 meters
	More detail at: http://www.ietf.org/meeting/100/hotel.html
	Reservations: https://aws.passkey.com/event/49212200/owner/61518/home
	
	Overflow Hotels:
	
	3. Carlton - (#1 Overflow Hotel, block of 150 rooms)
	Room Rate:  $180 (single with breakfast) $194 (double with breakfast) USD. Room Rates include daily buffet breakfast and High Speed Broadband access.
	Service charge of 10% and GST of 7% (taxes subject to change) are excluded from the above rates.
	Reservation Cutoff Date: 10 October 2017
	Cancellation: In the event of NO-Show on the day of arrival, Postponement, Cancellation or Shortening of Stay, the respective guest will be billed for the entire duration of stay for each room blocked.
	Distance to Meeting Venue: 200 meters
	More detail at: http://www.ietf.org/meeting/100/hotel.html
	Reservations: https://www.yourreservation.net/tb3/index.cfm?bf=HASINCHS&iataNumber=WHIETG06&rateAccessCode=*G06$&plprun=1&_=1501016071199
	
	4. Grand Pacific - (#2 Overflow Hotel, block of 70 rooms)
	Room Rate:  $125 (single prior to 2017/10/12) $132 (single after 2017/10/13) $139 (double prior to 2017/10/12) $147 (double after 2017/10/13) USD. Room Rates include daily breakfast and wifi. 
	Service charge of 10% and GST of 7% (taxes subject to change) are excluded from the above rates.
	Reservation Cutoff Date: 12 October 2017 (after this, rates increase)
	Cancellation: Should there be a last minute cancellation for confirmed individual reservations within 48 hours prior scheduled arrival, a room charge equivalent to the full length of stay booked will be leived as cancellation charge. Should there be a no-show for confirmed reservations, a no show charge will be equivalent to the full length of stay.
	Distance to Meeting Venue: 500 meters
	More detail at: http://www.ietf.org/meeting/100/hotel.html
	Reservations: https://reservations.travelclick.com/10798?groupID=1973310&hotelID=10798#/guestsandrooms
	
	5. Grand Park City Hall - (#3 Overflow Hotel, block of 60 rooms)
	Room Rate:  $187 (single) $201 (double) USD. Room Rates includes daily breakfast and unlimited usage of internet facilities.
	Service charge of 10% and GST of 7% (taxes subject to change) are excluded from the above rates.
	Reservation Cutoff Date: 12 October 2017 
	Cancel with No Penalty: Cancellation received after 12 noon (local time) 21 days prior to arrival or failure to show-up will result in a first night room charge plus taxes to the credit card.
	Distance to Meeting Venue: 550 meters
	More detail at: http://www.ietf.org/meeting/100/hotel.html
	Reservations: https://gc.synxis.com/rez.aspx?hotel=26662&Chain=10265&template=RBE&shell=RBE_GrandPark&locale=en-US&promo=IETF100
	
	6. Novotel - (#4 Overflow Hotel, block of 50 rooms)
	Room Rate:  $169 (standard room) USD. Room Rates include daily breakfast and internet access.
	Service charge of 10% and GST of 7% (taxes subject to change) are excluded from the above rates.
	Reservation Cutoff Date: 21 October 2017 
	Cancellation: Up to 15 days before the event the penalty fees shall be equal to the deposit amount paid (1night or 1 day delegate rate). Between 14 days and the event date, the penalty fees shall be equal to 100% of the individual total amount booked. In case of no show: deposits are not refunded.
	Distance to Meeting Venue: 1.4 kilometers
	More detail at: http://www.ietf.org/meeting/100/hotel.html
	Reservations: https://secure.accorhotels.com/store/index.html#/en/room-date?dateIn=2017-11-10&children=&offerLocation=&nights=1&adults=1&tksToHighlight=IETF&offerId=&hotelCode=5993&domainId=https://www.accorhotels.com
	
	7. Peninsula Excelsior Hotel - (#5 Overflow Hotel, block of 100 rooms)
	Room Rate:  $132 (single) USD $147 (double) USD. Room Rates include daily breakfast and internet access.
	Service charge of 10% and GST of 7% (taxes subject to change) are excluded from the above rates.
	Reservation Cutoff Date: 3 November 2017 
	Cancellation: There will be a one night non-refundable deposit that will be forfeited for any reservation of each event.
	Distance to Meeting Venue: 650 meters
	More detail at: http://www.ietf.org/meeting/100/hotel.html
	Reservations: http://www.peninsulaexcelsior.com.sg/?cp=IETF100EVENT


From nobody Wed Jul 26 07:15:29 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EC73131CAF for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 07:15:27 -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, 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=fugue-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 N0xXw9aT2x08 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 07:15:25 -0700 (PDT)
Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::22c]) (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 4F02B131C9E for <ietf@ietf.org>; Wed, 26 Jul 2017 07:15:25 -0700 (PDT)
Received: by mail-qk0-x22c.google.com with SMTP id u139so24823851qka.1 for <ietf@ietf.org>; Wed, 26 Jul 2017 07:15:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=wk4SVHUFy/P/1gMVgC71sALkCb4kFcB89UdvcJHQLb8=; b=HW8hncX+FXXalDvfItmCLAb8sKPxq4UX9mIS0B/arfPSkvepSMrPR+D1ewkZDidGQ/ HkSROFjRafGUdJbcXSUlX/Yt1wJNnoB2Zm/DFLwCc5bpkQp9hncw4xEmYPuVWkq+ckwf ILWbYNa+tR6qbVc8EoQ9fu/4I0dUKrtUN4Ox3UNM9SaB+6g56LQMqWGdlNT+a/yNGjNr iNmuHOQCvGK3h4PFDtZT2ZmYzSc7Yn+xX76V2ILwspevsg/QVGVG3QkdTJcB6yjgoPvb J4BDCWPn/GmkwYSVIOpY60ZWJsnh55eG5eXZqGhFsvxqIhDWir4jjeCDRAJO6mS1sNlD KfaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=wk4SVHUFy/P/1gMVgC71sALkCb4kFcB89UdvcJHQLb8=; b=tMB/eo14cvtDF0v1VxJ2AkBM1pOkxlysDX9K2lPMlDiWXP9jSqoAPR3ECvht3QlWoc SBubSOI6Ks8Jj6NtSn3/zzSBlec8mSx7ph9I4B6x+I7ZJZewPbdGQC+TKkgfWGTLW7n/ OvefH6sxMzvpkRUKIT1rG2sDWoulgyAZBrXpTKEmpOMrBv51dzEVs9IccIPzdxhxD3Uc S2JDB7HmPDB8Bh8dhB9my/i4ggxFrJsh0AXCVfeFa78jGPRgZavRVTw9+zA6kn4XD8pN RWMUULA9M0wWuCEriwg8mxmqGxcunlxnBEej62HEvP6Vms13XSdfGFQ/7jdeg4vq7fVT 2f9Q==
X-Gm-Message-State: AIVw112NINgZlDKBWSW71FCNtjidd1T7WbRNiXUU6kTsTWbJuXpKyqVQ F3xEN8VIWHCjBq/HTwgwJA==
X-Received: by 10.55.143.134 with SMTP id r128mr1347548qkd.129.1501078524290;  Wed, 26 Jul 2017 07:15:24 -0700 (PDT)
Received: from macbook-pro-6.w50.lede.home (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id u67sm11366687qkd.67.2017.07.26.07.15.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Jul 2017 07:15:23 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <A592F759-4791-48F3-BFD1-6A33A3F7F051@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_7A5C460B-EA76-4892-ABF2-E3EA4617FAFE"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Revamp of the www.ietf.org website
Date: Wed, 26 Jul 2017 10:15:22 -0400
In-Reply-To: <alpine.DEB.2.02.1707261214090.29742@uplift.swm.pp.se>
Cc: Russ Housley <housley@vigilsec.com>, IETF <ietf@ietf.org>
To: Mikael Abrahamsson <swmike@swm.pp.se>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <alpine.DEB.2.02.1707261214090.29742@uplift.swm.pp.se>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GqHrl4LBscmgKFXcbpT8g6xK6u8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 14:15:27 -0000

--Apple-Mail=_7A5C460B-EA76-4892-ABF2-E3EA4617FAFE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jul 26, 2017, at 6:30 AM, Mikael Abrahamsson <swmike@swm.pp.se> =
wrote:
> The new page follows the tragic becoming-common-everywhere of using =
font size that is way too big. In Chrome on MacOS the old page looks =
great, font size is perfect, lots of information.

You are fortunate to have such good eyesight.   For my eyes, the new =
fonts are a huge improvement.   The fonts on the old IETF web site are =
legible, but really too small, and the information density is too high, =
so that it requires a close look to sort out what one needs from among =
the things one doesn't.

The goal of a web page isn't to put as much information as possible on =
one page.   It's to communicate effectively.   I don't claim to be an =
expert on what it means to communicate effectively, but in fact looking =
at the main page, the only real problem I see is that the responsive =
design allows the main image to be too large, and this produces the =
"have to scroll" effect that people have complained about.   That image =
is way too big for the page.   It sort of works on a 1080p display, =
because there's room for all the content despite the huge image, but it =
would be better to reduce it to about half its presented height in all =
the other responsive sizes (no more than a quarter of the screen =
height).

On the other hand, the tools pulldown has the exact three things I am =
most interested in when I personally go to the IETF web site: a link to =
the datatracker, a link to the current meeting, and, well, okay, I never =
search the mailing list archive that way, but it would be great if that =
were swapped out for a link to the meeting agenda for the current =
meeting.


--Apple-Mail=_7A5C460B-EA76-4892-ABF2-E3EA4617FAFE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jul 26, 2017, at 6:30 AM, Mikael Abrahamsson &lt;<a =
href=3D"mailto:swmike@swm.pp.se" class=3D"">swmike@swm.pp.se</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">The new page =
follows the tragic becoming-common-everywhere of using font size that is =
way too big. In Chrome on MacOS the old page looks great, font size is =
perfect, lots of information.</span><br style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""></div></blockquote></div><br class=3D""><div class=3D"">You =
are fortunate to have such good eyesight. &nbsp; For my eyes, the new =
fonts are a huge improvement. &nbsp; The fonts on the old IETF web site =
are legible, but really too small, and the information density is too =
high, so that it requires a close look to sort out what one needs from =
among the things one doesn't.</div><div class=3D""><br =
class=3D""></div><div class=3D"">The goal of a web page isn't to put as =
much information as possible on one page. &nbsp; It's to communicate =
effectively. &nbsp; I don't claim to be an expert on what it means to =
communicate effectively, but in fact looking at the main page, the only =
real problem I see is that the responsive design allows the main image =
to be too large, and this produces the "have to scroll" effect that =
people have complained about. &nbsp; That image is way too big for the =
page. &nbsp; It sort of works on a 1080p display, because there's room =
for all the content despite the huge image, but it would be better to =
reduce it to about half its presented height in all the other responsive =
sizes (no more than a quarter of the screen height).</div><div =
class=3D""><br class=3D""></div><div class=3D"">On the other hand, the =
tools pulldown has the exact three things I am most interested in when I =
personally go to the IETF web site: a link to the datatracker, a link to =
the current meeting, and, well, okay, I never search the mailing list =
archive that way, but it would be great if that were swapped out for a =
link to the meeting agenda for the current meeting.</div><div =
class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_7A5C460B-EA76-4892-ABF2-E3EA4617FAFE--


From nobody Wed Jul 26 08:05:48 2017
Return-Path: <ludwig@clemm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03B32131CCE; Wed, 26 Jul 2017 08:05:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.421
X-Spam-Level: 
X-Spam-Status: No, score=-1.421 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_HELO_PASS=-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 tBotZvw5sSIT; Wed, 26 Jul 2017 08:05:44 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.197]) (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 2503512EC4B; Wed, 26 Jul 2017 08:05:43 -0700 (PDT)
Received: from LAPTOPR7T053C2 ([73.71.191.170]) by mrelay.perfora.net (mreueus001 [74.208.5.2]) with ESMTPSA (Nemesis) id 0Lu5Nw-1dkiuo26ac-011SBw;  Wed, 26 Jul 2017 17:05:24 +0200
From: "Alexander Clemm" <ludwig@clemm.org>
To: "'Susan Hares'" <shares@ndzh.com>, "'Ladislav Lhotka'" <lhotka@nic.cz>, <yang-doctors@ietf.org>
Cc: <i2rs@ietf.org>, <ietf@ietf.org>, <draft-ietf-i2rs-yang-l3-topology.all@ietf.org>
References: <150105874813.26401.2245891817517041568@ietfa.amsl.com> <00a001d3060c$46a59fb0$d3f0df10$@ndzh.com>
In-Reply-To: <00a001d3060c$46a59fb0$d3f0df10$@ndzh.com>
Subject: RE: [i2rs] Yangdoctors early review of draft-ietf-i2rs-yang-l3-topology-10
Date: Wed, 26 Jul 2017 08:05:22 -0700
Message-ID: <00d801d30620$9bdabc40$d39034c0$@clemm.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQGgyIYTdDwZMCgA10mmEvcrPTJMKQHDDQmJoryT4pA=
Content-Language: en-us
X-Provags-ID: V03:K0:TTGj6OEAkjE2b4wnEJKt27UfFNsSrq2nZgWAWHS2uVeE8Pq6cXw VBjQvLYUvlbCDJnmHjpj7UWwaKaqes9qsnHlZuH2SGqYDcV0unyFfm1EI2S53CgGjV/F14C zxqHVLWJrTkRwI+fc50iouH8tms/3GViCY7c91YC1s81UeSpf2gXGcRzD1nlW4S6jVkSAaJ MZtN+v0voszzKlsm1n7xw==
X-UI-Out-Filterresults: notjunk:1;V01:K0:+EVNTqawu88=:9Vrhz3tvvO/tdg2MRYdVDe sH9+VyadfzlSmhd6FS/u7HyubGjTryy9QyjpmYtHL8htMXDQmRDqsyD/BjdKj4O9lRUGK8Fmb MmCV7SImEVS4k684jXoUQ7keJH1rC+C/G1Yopgnf1boZAqLTnW4DEI+pbfj7KrqwX2ao5f41R DZ25vhg5hqzjc/QaURzpuDFI5UjL/KZ+EUe2GROJpfeWxcyLmdrkROVbKTWHGcBcdbyOJMZ2m bT9OofUZ6iRlvuz/Xu9o74ed++6PlV6h0Ef/Bcuz46DAxQ9p4ABM8Tt35+DMgFe2b4w8BgnlO nXb9cqD+0V421sfaxVLmAm2Xa7PIFsKlp+3U8Uz8P0EXa0v81D6p0lmZaAgXPgbCljj7a3/2r rhb/ZTyofV8Rgcq9qOZnCgvkGSLqHdTRYzwPvS+MVip16/zdv+79UTEw8WatnidKH9Ij4AChD 5RSldNbsDTwxJHLPOAHFlvIfk5YzY3E4jqPJkhXsq6si8vhmUNxX1d4QVaHhDam9c++Qj2wr8 kyqjMY1me26WIN3ZZlYf8PHF13LLBvJyb+x6Ds68AXPGEqcaCYAOnXZrkGbjf/CaOSoPHZC1d MBN3IpRlhWEKKZ4IzKKVSqEuAHS/2VMurfrSnrZjnB3Kgx5yKrXlqTq7J7qCMGHZN1A2hiVCV thStbb4B5HeQ/TuUH7GF6a6sF4+XA2FNZy2q04w2QD5QdA5t5r498yPrk0e18ESzQSHdWgJNp HHwOvl3+yb5TR6u8NLZDBXbTlT6NQ21XY5iBPdickdCvXlRp1Ji6CUmIfbY=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WiBoEiADdBu3Pe_4vHuswSo0Cso>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 15:05:46 -0000

Hello Lada,

Thank you very much for your detailed review.   Will plan to update the
draft over the coming two weeks or so (as I may be taking a few days off).
Most of the comments should be reasonably straightforward to accommodate.
However, I do have comments regarding #1 and #4.  

On #1 (presence containers vs identities).  Unless you feel very strongly
about this, we would prefer to keep this as is, not revert to identities.
This node is subject to quite a few "when" condition checks (when it comes
to topology-specific augmentations) which are very simple this way.
Changing this makes the conditions more complex and has ripple effects
through dependant modules.  Note that a topology can have multiple types; a
single leaf with identity would not be sufficient, it would need to be a
leaf-list.  On #4, (URIs) we had multiple discussions in the past but have
always come back to that; I would prefer to not change this at this point.
Please note that the model is implemented and deployed today, e.g. in Open
Daylight.  
 
Thanks
--- Alex

-----Original Message-----
From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Wednesday, July 26, 2017 5:40 AM
To: 'Ladislav Lhotka' <lhotka@nic.cz>; yang-doctors@ietf.org
Cc: i2rs@ietf.org; ietf@ietf.org;
draft-ietf-i2rs-yang-l3-topology.all@ietf.org
Subject: Re: [i2rs] Yangdoctors early review of
draft-ietf-i2rs-yang-l3-topology-10

Lada:

Thank you for reviewing the draft with such a careful eye to now and the
future.  Please look for a response from Alex within a few days, .

Sue 

-----Original Message-----
From: Ladislav Lhotka [mailto:lhotka@nic.cz] 
Sent: Wednesday, July 26, 2017 4:46 AM
To: yang-doctors@ietf.org
Cc: i2rs@ietf.org; ietf@ietf.org;
draft-ietf-i2rs-yang-l3-topology.all@ietf.org
Subject: Yangdoctors early review of draft-ietf-i2rs-yang-l3-topology-10

Reviewer: Ladislav Lhotka
Review result: Ready with Issues

This YANG module and I-D belong to an extensible suite of data models
addressing multi-layered network topology. It is an interesting, even if
somewhat atypical, application of YANG.

The entire network topology suite seems well thought out, and it is apparent
that the document has already undergone several rounds of discussions and
iterations. It is also positive that the document deals with possible
overlaps with other YANG modules such as ietf-interfaces or ietf-hardware.
Of course, an ultimate acid test of the network topology suite will come
with applications to real-life network.

My review below raises several issues that need to be addressed (especially
#1). Some of them are related to design decisions described in
draft-ietf-i2rs-yang-network-topo. Apart from that, I believe the document
is ready to be published.

*** Comments to draft-ietf-i2rs-yang-network-topo-14:

1. With YANG 1.1, the network type information looks like a perfect
   candidate for identities (with multiple inheritance). Instead, it
   is modelled with presence containers, which is cumbersome and
   redundant. I don't see any reasons for doing so, if there are any,
   then they should be explained in sec. 4.4.8.

2. The document defines "supporting network" and then says "A
   supporting network is in effect an underlay network." In the
   subsequent text "underlay network" is used almost exclusively. So
   perhaps the term "supporting network" should be dropped altogether?

3. The text should be better aligned with the terminology of
   draft-ietf-netmod-revised-datastores. In particular,
   "system-controlled" should be used instead of "server-provided".

4. Is it necessary to use URIs for identifying all objects in the
   data model. URIs are difficult to use, so applications are likely
   to introduce some abbreviations and keep an internal mapping, which
   could cause problems, e.g. when matching objects in notifications
   with a GUI representation. In my view, it should be sufficient to
   use URIs for network-id and plain strings for other IDs, because
   all other objects are encapsulated inside a network, so their name
   conflicts shouldn't matter.

*** Comments to draft-ietf-i2rs-yang-l3-topology-10

5. The type of "router-id" should be "yang:dotted-quad" and not
   "inet:ip-address" because the latter means both IPv4 and IPv6
   address, possibly also with a zone index.

6. Both prefix and link attributes include the "metric" parameter. It
   should be explained what they mean. In the context of ietf-routing
   the option of including "metric" as a general route parameter was
   discussed and finally rejected because different routing protocol use
   metrics with different semantics and properties. I wonder if it is
   the same case here. 

*** Formal issues and typos

7. Both documents should refer to draft-ietf-netmod-yang-tree-diagrams
   rather than describe the notation of tree diagrams in the text.

8. Sec. 7 in draft-ietf-i2rs-yang-l3-topology-10: s/moodel/model/



_______________________________________________
i2rs mailing list
i2rs@ietf.org
https://www.ietf.org/mailman/listinfo/i2rs


From nobody Wed Jul 26 08:07:33 2017
Return-Path: <ludwig@clemm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 999E7131C91; Wed, 26 Jul 2017 08:07:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.421
X-Spam-Level: 
X-Spam-Status: No, score=-1.421 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_HELO_PASS=-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 djE7b8IIPZJv; Wed, 26 Jul 2017 08:07:30 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.197]) (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 04950131CD1; Wed, 26 Jul 2017 08:07:29 -0700 (PDT)
Received: from LAPTOPR7T053C2 ([73.71.191.170]) by mrelay.perfora.net (mreueus001 [74.208.5.2]) with ESMTPSA (Nemesis) id 0Ma46L-1dIb0O2rMt-00LptV;  Wed, 26 Jul 2017 17:07:15 +0200
From: "Alexander Clemm" <ludwig@clemm.org>
To: "'Susan Hares'" <shares@ndzh.com>, "'Stewart Bryant'" <stewart.bryant@gmail.com>, <gen-art@ietf.org>
Cc: <i2rs@ietf.org>, <ietf@ietf.org>, <draft-ietf-i2rs-yang-network-topo.all@ietf.org>
References: <150100153667.26268.4094509639712323654@ietfa.amsl.com> <01b501d3056a$a5daf9a0$f190ece0$@ndzh.com>
In-Reply-To: <01b501d3056a$a5daf9a0$f190ece0$@ndzh.com>
Subject: RE: [i2rs] Genart last call review of draft-ietf-i2rs-yang-network-topo-14
Date: Wed, 26 Jul 2017 08:07:14 -0700
Message-ID: <00e201d30620$de1f7500$9a5e5f00$@clemm.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHl6lR3K2dOVNakqJaIEZLH9x1aSgFGJ73uojY7xsA=
Content-Language: en-us
X-Provags-ID: V03:K0:pw+nGei/oJx07n01iOj2BWNwF/BS9cUlFJpYEfoRfmQlVEwFa07 PQ1w/EilU5CupyzCvnqysWmviskWcxehGrTgjHxX0vtFr5nI1Ygvvtkccy0rPQsimRSYb6N K/euN++eQ9xnnsD+opv+1ukPaaWifZ6zyTaeRs3fRKAUDoj5Szu8qglbZheWEW6kJq0PURW GNKLQqORTyDGhidppXM2w==
X-UI-Out-Filterresults: notjunk:1;V01:K0:L8ssCrSbLKo=:kqHhx9T+qp5AbPp7HBZlRI fjomelLnvyFCMUlE9hibaRPQyNFMi5MhsEucO0XvYgQtDhHfJo+vRl8s9AMW/2BW65DXFjz+e tJTdEJZc2wVLh8hPno9AhR9ysJIwyB13XBw0C5O1EPsE/Tn87FlbIwtliHQ4SP9gWqRjtWsmS N2VrTj3fgDkUS7XM81WX8bx3wKmD42aZQ2ox2enz/UEQArg009X+doNQ9qYBnqkDQAzmLVBu9 GlTzRQebBuQ8AYrR7kLkywTcJior7YAOxkSnAYRHMhqEii+ZvkRX9T5NWR5uw0Qolh7NSZYJ/ 50IG/5NINyJW/15+MeW2hZDJH17Hl5+/KYoLCgjrCI6wmPUIZBrzyg8V1MoPQz0zcDkq/4eYh orl4s67rwG9hIoIxwk9QzyIpFopBExmZEBX0CnQSxvG9MXH9jPqYK6xUFb2+DCxAVLUGP83pU cdxPiUVgDm6FlN1xk6v5lMRRVh0iyk7B+i9IkUjqnHLsy1lleUttIudVWdz+TtpcenUNs0e1e AZaIXHeDQDv+K1A2vCz83cVzef+PK5ZhJ4yOlKBqupiDcdmxdXrrjcXlJ1ZRosrJOVMG5+PN4 SF/BoyaUKfmi2LQZa6hdfl2exnHe0B+4wgdiNfQ4WdIPrF7+aXuuEG/oF6WHwWoHfCX5xwgB9 V7IGVaz7wG9Xenmn4COcfJFMa4mQewK8aDTxAUcHDAB0kmOnZ1NLGv8733auz/gD5EenezOn6 SpLiMnVbqAzW1tBETtbq/PH8j3WCK1BGK8mfP27iHf0sMQcAri4GvdvATxc=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9kYkaVWC0IGu0es4nw8JqmjzQT0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 15:07:31 -0000

Thank you, Stewart!

--- Alex

-----Original Message-----
From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Tuesday, July 25, 2017 10:23 AM
To: 'Stewart Bryant' <stewart.bryant@gmail.com>; gen-art@ietf.org
Cc: i2rs@ietf.org; ietf@ietf.org;
draft-ietf-i2rs-yang-network-topo.all@ietf.org
Subject: Re: [i2rs] Genart last call review of
draft-ietf-i2rs-yang-network-topo-14

Stewart: 

Thank you for your review!  To come back from IETF and immediately complete
your review shows awesome dedication!

Cheerily, Sue Hares

-----Original Message-----
From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Stewart Bryant
Sent: Tuesday, July 25, 2017 12:52 PM
To: gen-art@ietf.org
Cc: i2rs@ietf.org; ietf@ietf.org;
draft-ietf-i2rs-yang-network-topo.all@ietf.org
Subject: [i2rs] Genart last call review of
draft-ietf-i2rs-yang-network-topo-14

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-ietf-i2rs-yang-network-topo-14
Reviewer: Stewart Bryant
Review Date: 2017-07-25
IETF LC End Date: 2016-12-19
IESG Telechat date: Not scheduled for a telechat

Summary: Ready with a few minor English nits remaining.

Major issues: None

Minor issues: None

Nits/editorial comments: 

I notice that a number of the editorial comments in 

https://datatracker.ietf.org/doc/review-ietf-i2rs-yang-network-topo-09-genar
t-lc-bryant-2016-12-12/

were not addressed, but I am sure the RFC Editor will pick them up.

I notice that RFC7952 is in the reference list but not called out in the
text.


_______________________________________________
i2rs mailing list
i2rs@ietf.org
https://www.ietf.org/mailman/listinfo/i2rs

_______________________________________________
i2rs mailing list
i2rs@ietf.org
https://www.ietf.org/mailman/listinfo/i2rs


From nobody Wed Jul 26 08:09:14 2017
Return-Path: <ludwig@clemm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 611D7131CDD; Wed, 26 Jul 2017 08:09:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level: 
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_SPAM=0.5, SPF_HELO_PASS=-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 BxcPdi_7JJQh; Wed, 26 Jul 2017 08:09:03 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.196]) (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 87ECA1317B1; Wed, 26 Jul 2017 08:09:03 -0700 (PDT)
Received: from LAPTOPR7T053C2 ([73.71.191.170]) by mrelay.perfora.net (mreueus003 [74.208.5.2]) with ESMTPSA (Nemesis) id 0MS31o-1d8NlS0MTC-00TDul;  Wed, 26 Jul 2017 17:08:48 +0200
From: "Alexander Clemm" <ludwig@clemm.org>
To: "'Susan Hares'" <shares@ndzh.com>, "'Ines Robles'" <mariainesrobles@googlemail.com>, <rtg-dir@ietf.org>
Cc: <rtg-ads@ietf.org>, <i2rs@ietf.org>, <ietf@ietf.org>, <draft-ietf-i2rs-yang-network-topo.all@ietf.org>
References: <150093804800.26111.1394410974752858089@ietfa.amsl.com> <01b701d3056a$d381fca0$7a85f5e0$@ndzh.com>
In-Reply-To: <01b701d3056a$d381fca0$7a85f5e0$@ndzh.com>
Subject: RE: [i2rs] Rtgdir last call review of draft-ietf-i2rs-yang-network-topo-14
Date: Wed, 26 Jul 2017 08:08:46 -0700
Message-ID: <00e801d30621$15337e60$3f9a7b20$@clemm.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQIJ6YKanmEFADbnMl9M4liTZ2TQpQGp+91ZoesfCjA=
Content-Language: en-us
X-Provags-ID: V03:K0:RA2jT/UOTq/+N1GWqr3OQAqquADGZGZFuQKwc3blcbx36XfQbji LcRUQkDUcS5ARXe7GJVldlWlDRRNr5l98iFi55krRa4YPmzuHTqRy6U04176x/L6XPA0Z8n 8gK7C819NvQgGJE7Fib4q6Q7yofxj6MUa0Qeo8VIDSDlXQMvWmJD5Qx6fK0+QjChshHvnWl q8JO0XMhfb3cT1I5vq1Qw==
X-UI-Out-Filterresults: notjunk:1;V01:K0:zgtyIl9YtMM=:1XAROVHJzWnq9Fx+4QSf0w tRRNHpBVJyZM04CGZUhs3gK4nzeFJHcSmb7uusT2K7spET2jzbsYZAH98S5SODJ5Xak6QNGV/ rx3AZvyjuOya0EJ70auBoKO52pgLa8YdrKYoWNx36/tW1MidmX3hItaZXyuOfh89iXQPSc8J1 a3f5T9IenEUY0SjhHSpX61EAOtVoU/tdA8oVbGF9tXy46um3o3rh+UjVkNM77119zWGQ/yP6A 09jYggGNbVzBxn1uvznqfaF1+USuB+R4Q9ivmqSSRFMU7JjiD6kopE7Zg49LB1utXGtF9HrOw HXbkNYoc6fdXb5xEP7TwAh0nwivRLZebzTKQSI+boO9Gw2RvBdnPAPmJElvi3GnbMwVUntl76 4ts0+fseXuyhNujc9tc5HWp4m7tgVwIkyLKb6gw/9SQIx1yJBJtrDWBThFCCPS9B/JTPRfhmM A33H0OrvZBMwVPsB14cGWbH6JHCHNpBvcMfXXBN4Yl1s2TiIgmNVyUeKxqWypCacIdix/cdRh pMQzsfEjsRmJkCG9YScUcTpbyLp2cWKTY/WiRlC4itaXX0F42zkrLMYh2Fugr2lXq5tqW9Uof E9X/vNCII3XtOVXNMTJWAAs4w1KE1uYVgX5R2COuKaQHAWAW74c5Bp0sCxO+z8A3TzUabeuEJ EaAcZc871fPaeHZBYKOXu7OAa+eLbz3K4Qve64MmRrb8W9YIISj7axOj9hehT+hw3Fmibfd40 Wj7GTFidMKb/+b4zjAUCSfySOgREaYtFmXgXfCdeVN5hc+QNNY0InUvFUDw=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qLLufXT2ItPQr4l_c67VHE3VjrU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 15:09:06 -0000

Ines,=20

Thank you for your review!  We will be updating the document soon. =20

Kind regards
--- Alex

-----Original Message-----
From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Tuesday, July 25, 2017 10:24 AM
To: 'Ines Robles' <mariainesrobles@googlemail.com>; rtg-dir@ietf.org
Cc: rtg-ads@ietf.org; i2rs@ietf.org; ietf@ietf.org; =
draft-ietf-i2rs-yang-network-topo.all@ietf.org
Subject: Re: [i2rs] Rtgdir last call review of =
draft-ietf-i2rs-yang-network-topo-14

Ines:

Getting this review on the Monday after IETF shows what a diligent =
reviewer you are.  The authors will be responding shortly.=20

Cheerily,=20
Sue Hares=20

-----Original Message-----
From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Ines Robles
Sent: Monday, July 24, 2017 7:14 PM
To: rtg-dir@ietf.org
Cc: rtg-ads@ietf.org; i2rs@ietf.org; ietf@ietf.org; =
draft-ietf-i2rs-yang-network-topo.all@ietf.org
Subject: [i2rs] Rtgdir last call review of =
draft-ietf-i2rs-yang-network-topo-14

Reviewer: Ines Robles
Review result: Has Issues

Hello,

I have been selected as the Routing Directorate reviewer for this draft. =
The Routing Directorate seeks to review all routing or routing-related =
drafts as they pass through IETF last call and IESG review, and =
sometimes on special request. The purpose of the review is to provide =
assistance to the Routing ADs.
For more information about the Routing Directorate, please see =
=E2=80=8Bhttp://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir

Although these comments are primarily for the use of the Routing ADs, it =
would be helpful if you could consider them along with any other IETF =
Last Call comments that you receive, and strive to resolve them through =
discussion or by updating the draft.

Document: draft-ietf-i2rs-yang-network-topo-14.txt
Reviewer: Ines Robles
Review Date: 07-25-2017
Intended status: Standards Track

Summary:
I have some minor concerns about this document that I think should be =
resolved before publication.

Comments:

I believe the draft is technically good. This document is well written =
and clear to understand. The figures are clear and helpful.

Major Issues:

No major issues found.

Minor Issues:

Since this document specifies a data model, I would include some text =
related to the Information Model [RFC 3444]. How would it be in this =
context?

1- Section 1

  1.a following Figure 1 (Page 4):

    I would add in the figure the corresponding section that explain the
    module. e.g. Abstract Network Model, I would add in the figure =
"Abstract
    (base) Network Model" and "section 4.1". The same for "Abstract =
Topology
    Model", should it be section 4.2?

  1.b -following Figure 2 (Page 5):

      1.b.1- " X1 and X2 - mapping onto... ",  I think it would be "X1 =
and X3
      mapping onto..."

      1.b.2- " a single L3 network element", I would add in this case =
(Y2) "a
      single L3 (Y2) network element", the same for "The figure shows a =
single
      "L3" network element mapped onto multiple "Optical" network =
elements.", I
      would add "The figure shows a single "L3" network element (Y2) =
mapped
      onto multiple "Optical" network elements [Z] and [Z1]."

      1.b.3- I would expand ROADMs --> Reconfigurable Optical Add/Drop
      Multiplexers (ROADMs)

2- Section 2:

  2.1- I would add a reference to RFC 6020, since the document uses =
terminology
  e.g container, augment, etc. which are defined in 6020. Even if this =
RFC is
  mentioned in the normative reference, still I would add it here as =
well.

3- Section 3:

  3.1-  ReST is mentioned here but not in the rest of the draft, is this
  correct?

Nits:

1- Pag. 18: is that correct?: "(a string is a string is a string)"

2- pag. 34: I would expand NMS -> NMS (Network Management System)

3- pag. 34: I would add a definition about TE Topology : "TE-Topology: =
The TE Topology is a schematic arrangement of TE nodes
   and TE links in a given TED. It forms the basis for a graph suitable
   for TE path computations."
   [https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-12]

4- pag. 34: topoogical -> topological

5- pag 35: "uber-network device" -> over-network device?

Thanks,

Ines.


_______________________________________________
i2rs mailing list
i2rs@ietf.org
https://www.ietf.org/mailman/listinfo/i2rs

_______________________________________________
i2rs mailing list
i2rs@ietf.org
https://www.ietf.org/mailman/listinfo/i2rs


From nobody Wed Jul 26 08:24:32 2017
Return-Path: <swmike@swm.pp.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B907131CDC for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 08:24:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level: 
X-Spam-Status: No, score=-4.302 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_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 ri208qHe21ZP for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 08:24:28 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (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 74FF113167B for <ietf@ietf.org>; Wed, 26 Jul 2017 08:24:28 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id D4B06A2; Wed, 26 Jul 2017 17:24:25 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1501082665; bh=0+kGdEHac4kOXKwR8H8EnK53LwWJuQ9eC+NiX9TKCr4=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=ZIqJQiP64ZVNoVKc2KBfjMVKGUu37lfUXmzBY6ta3q2ucVc29d8cix+S5PIE3/WBQ S0GJqqc4P1PyLTTlgOWcD+dfPp41HHtDqABU6MyK5JCmh/pp2rUwswluoHscY1Y19z 9JmhS5BVjdfvH0vE+ccMHIP3fwV8bUW8IwHWX9VM=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id D2E7AA1; Wed, 26 Jul 2017 17:24:25 +0200 (CEST)
Date: Wed, 26 Jul 2017 17:24:25 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ted Lemon <mellon@fugue.com>
cc: Russ Housley <housley@vigilsec.com>, IETF <ietf@ietf.org>
Subject: Re: Revamp of the www.ietf.org website
In-Reply-To: <A592F759-4791-48F3-BFD1-6A33A3F7F051@fugue.com>
Message-ID: <alpine.DEB.2.02.1707261649140.29742@uplift.swm.pp.se>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <alpine.DEB.2.02.1707261214090.29742@uplift.swm.pp.se> <A592F759-4791-48F3-BFD1-6A33A3F7F051@fugue.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CMf8Bo8ekTU8WyYBMe24lfmbQwA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 15:24:31 -0000

On Wed, 26 Jul 2017, Ted Lemon wrote:

> You are fortunate to have such good eyesight.  For my eyes, the new 
> fonts are a huge improvement.  The fonts on the old IETF web site are 
> legible, but really too small, and the information density is too high, 
> so that it requires a close look to sort out what one needs from among 
> the things one doesn't.

Yes, I have good eyesight. I set my default appearence that is comfortable 
for me. I expect all applications and web sites to follow that. If I had 
worse eye sight, I would set the default so the text was rendered in 
larger font size on my screen.

Screenshot from my screen:

http://imgur.com/a/iJCLV

This is with the CSS scaling turned off, so it's rendered with default 
font size. The old IETF website is approximately in between the font size 
of the "about mac" window text, and the MacOS menu text. The new 
beta.ietf.org web site is significantly larger in font size and row 
spacing compared to the other windows.

It's not the work of web site developers to cater for people with bad 
eyesight, it's the job of operating system developers to give people the 
possibility to set default settings that fit each and every one, and then 
it's up to the browser to give the user the default font size that user 
has chosen. If some web sites start to increase the web site "because 
there might be some people with bad eyesight out there who have chosen 
small font sizes in their OS", this is going to be a race with increasing 
font sizes in absurdum.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Wed Jul 26 09:07:40 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8B82131CEE for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 09:07:36 -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 e-xdHEgeTjCQ for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 09:07:34 -0700 (PDT)
Received: from mail-wm0-x242.google.com (mail-wm0-x242.google.com [IPv6:2a00:1450:400c:c09::242]) (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 62F55131CE2 for <ietf@ietf.org>; Wed, 26 Jul 2017 09:07:34 -0700 (PDT)
Received: by mail-wm0-x242.google.com with SMTP id t138so1603618wmt.4 for <ietf@ietf.org>; Wed, 26 Jul 2017 09:07:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=kmnq2R52l7u42fxnwfQmV1OrjKocmn+ZrIt88rKbRms=; b=T3EiHSrdyxQLYzRK7eylAqXqzLJ0avf8IQCbtDGWXYF75qxl+K8T3QwQru+NIjg8kZ wy1pkhIJIzB5GvT70Wrlk1Lk2twPO4n7Mf89zcroRYtztuRbVdYls1xpWs3/LpmjZQbG GKQEn5w8+DZklPAVG4PY2tMN3kdhoVE4tv9mxKKA2qYyusy5dnOjz8WtvamTt4q9rhzn QRlUmR4pU9jgb2aII2RT9+0KvU/aiE49qi4/k0UDv+4iDf9XFbu9jf4dwt87+1L0g8U3 utYgHMypNy3oZO+UKx8iwRrxChPN2K8xHWovWr9BI56e/1qPregUMd9BNrkkoknXwwE4 aseQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=kmnq2R52l7u42fxnwfQmV1OrjKocmn+ZrIt88rKbRms=; b=fWW7e/LTSxCyEgWbx5cphszqfR96OQK/1WVz3n3U1MfEkUxz1TKET0pKQBrSz7rX4s m+tp2bbYkVcXPPLO/2HOdObnxH8rSCgvOW9PdRcWk69z3DOy60IWvsmBKJaJJ4kGZGtD LwoBRfOnK5isZYGOGim7IpzuKEG1ilE6jO/t7mPKEue2Ey9LuJM+aoFctomCBN+X29O+ 3xTL4n2dZ0yGfBcjrlsNuISpbObOEDW4xv1C4slUzU58h0p48156aIHUrqbhQi46TlPh EPoulqFsboG847Y1E3kQuvVb/X8tIdPOtCBrQzORrp82C9e1WHKRDtapoHFIKTwDGxB7 ywgw==
X-Gm-Message-State: AIVw112ijUzBZOKGdmFLR5fEoiCpAkZGq7g0aT5sk8VMnmvix8yrAWxN AMxnPTiwzvl89elglR0=
X-Received: by 10.28.65.138 with SMTP id o132mr1197267wma.81.1501085252618; Wed, 26 Jul 2017 09:07:32 -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 h1sm17775165wrb.25.2017.07.26.09.07.31 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Jul 2017 09:07:32 -0700 (PDT)
Subject: Re: IETF 100 Registration and Hotel Reservations Open!
To: ietf@ietf.org
References: <150107762165.23133.6738319854502205219.idtracker@ietfa.amsl.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <6b56520c-8a19-85a4-c1af-5cb3d55eacdc@gmail.com>
Date: Wed, 26 Jul 2017 17:07:30 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <150107762165.23133.6738319854502205219.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bAeo3c8k04k_zFrsGEboFwgznGE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 16:07:37 -0000

Like a lot of people I booked a room in one of the HQ hotels immediately 
this came into my inbox, but I understand that others are reporting that 
the are all sold.

I wonder if we need a ballot system for the HQ hotels?

- Stewart



From nobody Wed Jul 26 09:14:09 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0EDF131CF6 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 09:14:08 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 dUpBXr4tCpTo for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 09:14:06 -0700 (PDT)
Received: from mail-qt0-x229.google.com (mail-qt0-x229.google.com [IPv6:2607:f8b0:400d:c0d::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 C1DC6131CF5 for <ietf@ietf.org>; Wed, 26 Jul 2017 09:14:06 -0700 (PDT)
Received: by mail-qt0-x229.google.com with SMTP id s6so58706708qtc.1 for <ietf@ietf.org>; Wed, 26 Jul 2017 09:14:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=tITVth+OZSZonm740T5akmbST+kuDERK76qer5CiIbA=; b=OfH+QPRG38BCTSBBNLISMNpCg+bGTQJYDBXGQnF0PJZ+2HdiyYvxfQGh8Lw+zsRn9e dZklixV3EAhqLoMe+Ayx+QqnbWlLSkN4yWoDRFM5PIfF+jLh8+HME7bihu/KTbfL9Q5l nUAwYoEkAhUBQxI17suOhJT4AyANa5Ejt5QwO1nAR8LPfb8l+B/CntFlSyG/+fQueDDq eQht0NQQH8xDL2sbSn/u7MQNGUxwnNLjhQtzQ+ABzPnx844DSNnTSfFFLe+BFjAonMA8 2UAGiUDnxSms8d8RAnvTj1/1ZGLR8M+HHVtMGx2zLR4Sevk971I/YpZdJRcSPgj9E9gy gTcw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=tITVth+OZSZonm740T5akmbST+kuDERK76qer5CiIbA=; b=OD8z/WuhbctDFiuIOAnByLglX/+Wnc9z2+9u5A5iVQGsYXwmDq/BXHgd9/8VZwvwlN cAVgNWVu6T+ymEIowjqFK4xL91gbfGcG6ViOTLvAeVhEauDvfnZL0KxMvjUkc+6ws7kt AO8NLWoGgkrE3TSkln4l8xpSnOJ6rRF7pQ0VCcY17DXS1MVbmfdrS73t3DYRrKsqKaYP nD0+6diUnu9j9cDIYCpqXoC5rYgitp32S18h3g4Yagc+6WTRBAbwU/XaJ1FDbRG3t5cR 1jT/j9ZN8ubSC8vsGLDh8ONFyv86tJiAQoXivU9D+KXd81l0LZwqPoHz4hvbl3oW2KJ7 Dwdw==
X-Gm-Message-State: AIVw111XRW1VjDXiExxP6roGo2cT2ObqjFVpzXa1Na/MRWLbGlb6nM/+ qFNH/Zf6VTv3E2dq
X-Received: by 10.200.38.74 with SMTP id v10mr2089951qtv.95.1501085645511; Wed, 26 Jul 2017 09:14:05 -0700 (PDT)
Received: from macbook-pro-6.w50.lede.home (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id q49sm2716899qte.94.2017.07.26.09.14.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Jul 2017 09:14:04 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <DCAD3478-067F-450A-AF3D-0D32B9C4ABC1@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E6059B9C-6388-43F3-8D00-38A4CF48907D"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: IETF 100 Registration and Hotel Reservations Open!
Date: Wed, 26 Jul 2017 12:14:03 -0400
In-Reply-To: <6b56520c-8a19-85a4-c1af-5cb3d55eacdc@gmail.com>
Cc: ietf@ietf.org
To: Stewart Bryant <stewart.bryant@gmail.com>
References: <150107762165.23133.6738319854502205219.idtracker@ietfa.amsl.com> <6b56520c-8a19-85a4-c1af-5cb3d55eacdc@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NB-D1x4BeQEoCFrUF8EY2TF4pR4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 16:14:09 -0000

--Apple-Mail=_E6059B9C-6388-43F3-8D00-38A4CF48907D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Jul 26, 2017, at 12:07 PM, Stewart Bryant <stewart.bryant@gmail.com> =
wrote:
> I wonder if we need a ballot system for the HQ hotels?

Right now the system rewards those who are most attuned to the timing of =
the hotel announcement.   I actually have a filter in my email that =
notifies me when the announcement comes out.

I think it can definitely be argued that this is the wrong way to do =
things=E2=80=94I don't see it as being a particularly fair outcome that =
those IETF participants who are most proactive about signing up always =
tend to win.   Suppose everyone who cares about this were as proactive =
as I am.   Then it would just be a little bit more random who happened =
to win.

So, in principle, a lottery would be better, and maybe you get extra =
tickets if you lost last time (not sure how to make that work, but maybe =
some of the crypto wizards do).   The problem with this is that it's a =
_lot_ more tooling work for the secretariat.   I would hazard a guess =
that this is why it hasn't happened yet.

I don't think it's actually realistic to try to solve this problem.   =
But it does suck.   I suppose those of us who tend to win most often =
could voluntarily delay our registrations, but I doubt we could get =
sufficiently universal cooperation to achieve fairness.=

--Apple-Mail=_E6059B9C-6388-43F3-8D00-38A4CF48907D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jul 26, 2017, at 12:07 PM, Stewart Bryant &lt;<a =
href=3D"mailto:stewart.bryant@gmail.com" =
class=3D"">stewart.bryant@gmail.com</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">I wonder if we need a ballot system for =
the HQ hotels?</span><br style=3D"font-family: Menlo-Regular; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""></div></blockquote></div><br =
class=3D""><div class=3D"">Right now the system rewards those who are =
most attuned to the timing of the hotel announcement. &nbsp; I actually =
have a filter in my email that notifies me when the announcement comes =
out.</div><div class=3D""><br class=3D""></div><div class=3D"">I think =
it can definitely be argued that this is the wrong way to do things=E2=80=94=
I don't see it as being a particularly fair outcome that those IETF =
participants who are most proactive about signing up always tend to win. =
&nbsp; Suppose everyone who cares about this were as proactive as I am. =
&nbsp; Then it would just be a little bit more random who happened to =
win.</div><div class=3D""><br class=3D""></div><div class=3D"">So, in =
principle, a lottery would be better, and maybe you get extra tickets if =
you lost last time (not sure how to make that work, but maybe some of =
the crypto wizards do). &nbsp; The problem with this is that it's a =
_lot_ more tooling work for the secretariat. &nbsp; I would hazard a =
guess that this is why it hasn't happened yet.</div><div class=3D""><br =
class=3D""></div><div class=3D"">I don't think it's actually realistic =
to try to solve this problem. &nbsp; But it does suck. &nbsp; I suppose =
those of us who tend to win most often could voluntarily delay our =
registrations, but I doubt we could get sufficiently universal =
cooperation to achieve fairness.</div></body></html>=

--Apple-Mail=_E6059B9C-6388-43F3-8D00-38A4CF48907D--


From nobody Wed Jul 26 09:50:19 2017
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14B5C1320BA for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 09:50:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level: 
X-Spam-Status: No, score=-4.302 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_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
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 twFv5aUrAwIP for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 09:50:16 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED6A5131D28 for <ietf@ietf.org>; Wed, 26 Jul 2017 09:50:15 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6QGnmet022546; Wed, 26 Jul 2017 17:49:53 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v6QGnmet022546
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1501087799; bh=cbA2TgoSv7nyD2RBd/k0NkGRJhA=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=jezSbimX9lrYDxsQPOSaubmcOD30U+729dFJUSLSuEOmZWkGpHJ6CreJOmf3E7nnB tOxsbORZ3zWncm5QGk1Di9/CKyXviQVRottpIjchL9c8lXmHM39/PYnMNRPxHTgI0j UY1+LSfM5Y0/FgSlM1B65+/B3PUPg2D9HKfAZClM=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id y6PHnm1133808654nL ret-id none; Wed, 26 Jul 2017 17:49:59 +0100
Received: from 20010a88d51011.ipv6.customer.clara.net (20010a88d51011.ipv6.customer.clara.net [IPv6:2001:a88:d510:1101:75b2:2069:32a0:8c99] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6QGnh6c031665 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Jul 2017 17:49:43 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: IETF 100 Registration and Hotel Reservations Open!
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <DCAD3478-067F-450A-AF3D-0D32B9C4ABC1@fugue.com>
Date: Wed, 26 Jul 2017 17:49:42 +0100
Cc: Stewart Bryant <stewart.bryant@gmail.com>, ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|ebe142dc295fa56fb1b6505bd073e8a9y6PHnm03tjc|ecs.soton.ac.uk|4AE3A6AD-AFF1-4236-A2EF-0A0261A01812@ecs.soton.ac.uk>
References: <150107762165.23133.6738319854502205219.idtracker@ietfa.amsl.com> <6b56520c-8a19-85a4-c1af-5cb3d55eacdc@gmail.com> <DCAD3478-067F-450A-AF3D-0D32B9C4ABC1@fugue.com> <4AE3A6AD-AFF1-4236-A2EF-0A0261A01812@ecs.soton.ac.uk>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3273)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-ECS-MailScanner-SpamScore: s
X-smtpf-Report: sid=y6PHnm113380865400; tid=y6PHnm1133808654nL; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v6QGnmet022546
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mh2wycyajSYkaa9W5U5p4uGLgZY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 16:50:18 -0000

> On 26 Jul 2017, at 17:14, Ted Lemon <mellon@fugue.com> wrote:
>=20
> On Jul 26, 2017, at 12:07 PM, Stewart Bryant =
<stewart.bryant@gmail.com> wrote:
>> I wonder if we need a ballot system for the HQ hotels?
>=20
> Right now the system rewards those who are most attuned to the timing =
of the hotel announcement.   I actually have a filter in my email that =
notifies me when the announcement comes out.
>=20
> I think it can definitely be argued that this is the wrong way to do =
things=E2=80=94I don't see it as being a particularly fair outcome that =
those IETF participants who are most proactive about signing up always =
tend to win.   Suppose everyone who cares about this were as proactive =
as I am.   Then it would just be a little bit more random who happened =
to win.
>=20
> So, in principle, a lottery would be better, and maybe you get extra =
tickets if you lost last time (not sure how to make that work, but maybe =
some of the crypto wizards do).   The problem with this is that it's a =
_lot_ more tooling work for the secretariat.   I would hazard a guess =
that this is why it hasn't happened yet.
>=20
> I don't think it's actually realistic to try to solve this problem.   =
But it does suck.   I suppose those of us who tend to win most often =
could voluntarily delay our registrations, but I doubt we could get =
sufficiently universal cooperation to achieve fairness.

In Singapore the second hotel is 85 metres away, the third is 200m, the =
fourth and fifth 500m, which is rather better than alternatives for many =
venues.  One of the 500m hotels is half the room rate of the main venue. =
 There=E2=80=99s more hotels being used, with the rooms spread more =
thinly between them.  The quick =E2=80=9Csell out=E2=80=9D of rooms may =
be because the main venue had only 160 rooms for the Saturday night =
before the meeting started, but 300+ for other nights.

If we can give such diversity in options for all meetings, assisted by =
local knowledge, that would help alleviate problems, as would giving =
some priority to those with genuine reasons to be on-site.

I note that it seems the IETF organisers organise around 700 or so rooms =
for us, so I assume 500 or so attendees found their own accommodation.  =
Presumably that 700 figure is based on past take-up of those rooms.

Tim=


From nobody Wed Jul 26 09:58:41 2017
Return-Path: <akatlas@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F01C7131D69 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 09:58:39 -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 DPQjKvMz1cgb for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 09:58:37 -0700 (PDT)
Received: from mail-wr0-x22f.google.com (mail-wr0-x22f.google.com [IPv6:2a00:1450:400c:c0c::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 7D8FF126C2F for <ietf@ietf.org>; Wed, 26 Jul 2017 09:58:37 -0700 (PDT)
Received: by mail-wr0-x22f.google.com with SMTP id 12so134283237wrb.1 for <ietf@ietf.org>; Wed, 26 Jul 2017 09:58:37 -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=2EHOkRZ8ZNmaA3MnnwncB9ep0XESHo0HYlvfaA5FAxg=; b=bflE2d/cPUdEWadGgbAYG1FKAl1N3TVFdx5n0yp57dDDWuGxYbU9xEqiL+e0d6106W 9FnKqott3Shxd1voSNpnHX2MLzFu02UkjOcGKAGLb4xng1AWDkRz082rTWwXm18QUNTR H98BwR429HzNzpakjK+Xc5EtTpv32UMx+XvNHQmy+i/ZiSBOhSN9K3d8/n/9CZTZ2bQ4 QxjPZCBJ1yfkCab6oLb4CghRor1fTL33XXF6OAQF5WMhX9Us2IOgt85HghL0kU53ODEP 9pZod2W1oJ0X78IFHhWj2n/xSvqnLSmfyru/FgEBIIKIfDNh1rt11HZ+Y4h9hp47jY5p 0hiQ==
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=2EHOkRZ8ZNmaA3MnnwncB9ep0XESHo0HYlvfaA5FAxg=; b=WpxduDWWgC5usJx34ECjqqiWX7mvSd6zwNMwgJ119aCuLQ8n653qSg/G8Zm/p2g35D TnAGwlzdcEQWgelzRhcGhmuo8P4u1nutb9Pbo8Lva67U+vyEm5lFpdoEqL9Ux515P/Ed kX4N5f+G4fmpwt1RlzXfdfyzxFPwHWPK5Sn6PN3pTye+0GqCCFEomSlqzV1xj+XrIaxT TitpX3oBE2ZTUCUByBswnpCA/HWOy90F5/VfykeFSauQTmb3nY65D9ISU34Ok45F4hX4 HWK4MpfOFodEV8t/uo7KPuYAh3J86MQYvhzKtyw1TKCDOZZtkMTteHath9cjyKhBXpLA CoxA==
X-Gm-Message-State: AIVw112j/RfhVZpKvDaXe55RTt2WImiPt1PMSQfGOHgUIpiddOwwkNDC 616yc3C+sQdNOZVxHFhdxDjVBUe7Iw==
X-Received: by 10.223.165.23 with SMTP id i23mr1375402wrb.35.1501088315714; Wed, 26 Jul 2017 09:58:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.183.1 with HTTP; Wed, 26 Jul 2017 09:58:34 -0700 (PDT)
In-Reply-To: <DCAD3478-067F-450A-AF3D-0D32B9C4ABC1@fugue.com>
References: <150107762165.23133.6738319854502205219.idtracker@ietfa.amsl.com> <6b56520c-8a19-85a4-c1af-5cb3d55eacdc@gmail.com> <DCAD3478-067F-450A-AF3D-0D32B9C4ABC1@fugue.com>
From: Alia Atlas <akatlas@gmail.com>
Date: Wed, 26 Jul 2017 12:58:34 -0400
Message-ID: <CAG4d1rcEP0wWfZ=YLb9g3Txoxkz9-vMaeuOc8ksdZM0u1X_btg@mail.gmail.com>
Subject: Re: IETF 100 Registration and Hotel Reservations Open!
To: Ted Lemon <mellon@fugue.com>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="f403045f20e6d5b7ce05553b5bbc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aJHSdPdiHTgsuin_6Gp89gNkpd8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 16:58:40 -0000

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

At the bof before mtgvenue, the idea of requiring an IETF registration to
get a hotel room in the block did come up.  I think it requires some
improvement and thought - but that seems like a possible direction to
minimize some of the opportunistic early reservation.

On the other hand, having more options for folks to reserve at with
different prices and less network benefit from being in the main hotel is
helpful.

Regards,
Alia

On Wed, Jul 26, 2017 at 12:14 PM, Ted Lemon <mellon@fugue.com> wrote:

> On Jul 26, 2017, at 12:07 PM, Stewart Bryant <stewart.bryant@gmail.com>
> wrote:
>
> I wonder if we need a ballot system for the HQ hotels?
>
>
> Right now the system rewards those who are most attuned to the timing of
> the hotel announcement.   I actually have a filter in my email that
> notifies me when the announcement comes out.
>
> I think it can definitely be argued that this is the wrong way to do
> things=E2=80=94I don't see it as being a particularly fair outcome that t=
hose IETF
> participants who are most proactive about signing up always tend to win.
> Suppose everyone who cares about this were as proactive as I am.   Then i=
t
> would just be a little bit more random who happened to win.
>
> So, in principle, a lottery would be better, and maybe you get extra
> tickets if you lost last time (not sure how to make that work, but maybe
> some of the crypto wizards do).   The problem with this is that it's a
> _lot_ more tooling work for the secretariat.   I would hazard a guess tha=
t
> this is why it hasn't happened yet.
>
> I don't think it's actually realistic to try to solve this problem.   But
> it does suck.   I suppose those of us who tend to win most often could
> voluntarily delay our registrations, but I doubt we could get sufficientl=
y
> universal cooperation to achieve fairness.
>

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

<div dir=3D"ltr">At the bof before mtgvenue, the idea of requiring an IETF =
registration to get a hotel room in the block did come up.=C2=A0 I think it=
 requires some improvement and thought - but that seems like a possible dir=
ection to minimize some of the opportunistic early reservation.<div><br></d=
iv><div>On the other hand, having more options for folks to reserve at with=
 different prices and less network benefit from being in the main hotel is =
helpful.</div><div><br></div><div>Regards,</div><div>Alia</div></div><div c=
lass=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Jul 26, 2017 at=
 12:14 PM, Ted Lemon <span dir=3D"ltr">&lt;<a href=3D"mailto:mellon@fugue.c=
om" target=3D"_blank">mellon@fugue.com</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex"><div style=3D"word-wrap:break-word"><span class=3D"">On=
 Jul 26, 2017, at 12:07 PM, Stewart Bryant &lt;<a href=3D"mailto:stewart.br=
yant@gmail.com" target=3D"_blank">stewart.bryant@gmail.com</a>&gt; wrote:<d=
iv><blockquote type=3D"cite"><div><span style=3D"font-family:Menlo-Regular;=
font-size:18px;font-style:normal;font-variant-caps:normal;font-weight:norma=
l;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:non=
e;white-space:normal;word-spacing:0px;float:none;display:inline!important">=
I wonder if we need a ballot system for the HQ hotels?</span><br style=3D"f=
ont-family:Menlo-Regular;font-size:18px;font-style:normal;font-variant-caps=
:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;white-space:normal;word-spacing:0px"></div></blo=
ckquote></div><br></span><div>Right now the system rewards those who are mo=
st attuned to the timing of the hotel announcement. =C2=A0 I actually have =
a filter in my email that notifies me when the announcement comes out.</div=
><div><br></div><div>I think it can definitely be argued that this is the w=
rong way to do things=E2=80=94I don&#39;t see it as being a particularly fa=
ir outcome that those IETF participants who are most proactive about signin=
g up always tend to win. =C2=A0 Suppose everyone who cares about this were =
as proactive as I am. =C2=A0 Then it would just be a little bit more random=
 who happened to win.</div><div><br></div><div>So, in principle, a lottery =
would be better, and maybe you get extra tickets if you lost last time (not=
 sure how to make that work, but maybe some of the crypto wizards do). =C2=
=A0 The problem with this is that it&#39;s a _lot_ more tooling work for th=
e secretariat. =C2=A0 I would hazard a guess that this is why it hasn&#39;t=
 happened yet.</div><div><br></div><div>I don&#39;t think it&#39;s actually=
 realistic to try to solve this problem. =C2=A0 But it does suck. =C2=A0 I =
suppose those of us who tend to win most often could voluntarily delay our =
registrations, but I doubt we could get sufficiently universal cooperation =
to achieve fairness.</div></div></blockquote></div><br></div>

--f403045f20e6d5b7ce05553b5bbc--


From nobody Wed Jul 26 10:16:33 2017
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B26151320D2 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 10:16:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, 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 Xxop0qMKcg8f for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 10:16:29 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D530131D69 for <ietf@ietf.org>; Wed, 26 Jul 2017 10:16:29 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 5EA24E219 for <ietf@ietf.org>; Wed, 26 Jul 2017 13:17:56 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 21DEE8070B for <ietf@ietf.org>; Wed, 26 Jul 2017 13:16:28 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
Subject: Re: IETF 100 Registration and Hotel Reservations Open!
In-Reply-To: <150107762165.23133.6738319854502205219.idtracker@ietfa.amsl.com>
References: <150107762165.23133.6738319854502205219.idtracker@ietfa.amsl.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Wed, 26 Jul 2017 13:16:28 -0400
Message-ID: <3129.1501089388@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/f8Htzn8b9Sm2PCghsjt0QDZHnk4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 17:16:32 -0000

--=-=-=
Content-Type: text/plain

IETF Secretariat <ietf-secretariat@ietf.org> wrote:
    > IETF 100 Information: https://ietf.org/meeting/100/index.html
    > Register online at: https://ietf.org/meeting/register.html

Any reason the remote participation registration form can not open at the
same time?

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAll4zmsACgkQgItw+93Q
3WVkkQf+JxgrvqLBCGvlx4thbHLK2mxc8iRFW00OmfruvwBUjNjnYnBX4bRsyTY8
Fb81BdGggNdyrLAdoxkXfTq/Z+LeAt5U3Kpyl0p86B7P9PmyStQsbYArZcFtyeEu
RlSXNrqNhh0W6R0UZm/ckPFzDTvn/vpKj13ouz1RsuaUO6Rg9v28foGPQ34TdgWa
K6fV2e+OTCxDxo18FtXEzlbxHRw/s9HCbowstt/MwbAK6a31e4mYrsjSmnAhm7g9
Tc9aFLQ0SAxglcvWrYiCCBjiBygKhY1n8JJySQLxzLwX1GivgtswRdxO3YPy8vtj
tdJbYAZApF5v+k3sRZhYMyZmQYTWgw==
=GsXU
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Jul 26 10:22:00 2017
Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 794D01320E4; Wed, 26 Jul 2017 10:21:57 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: ietf@ietf.org
Subject: Announcement on IETF 100 Hotel Reservations
X-Test-IDTracker: no
X-IETF-IDTracker: 6.57.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: agenda@ietf.org
Message-ID: <150108971740.23120.257371533321943899.idtracker@ietfa.amsl.com>
Date: Wed, 26 Jul 2017 10:21:57 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Y9zY_kiJnpuOoGsHsU0xnx85Ee8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 17:21:58 -0000

Hello IETFers,

We are happy to see the excitement from the community for IETF 100 in November! At this point, there are sold out dates at both the Swissotel and Fairmont. The Fairmont has no available room nights on November 9th, 10th and 18th, and the Swissotel fully booked on November 10th, 11th and 17th. We are working to add room nights on these dates as soon as possible. Because of the time zone difference there may be a delay in adding room nights to these dates. We apologize for any inconvenience. If you have any further questions or concerns please contact agenda@ietf.org. We will update the community as soon as we can. Please also reference the IETF 100 hotels page https://www.ietf.org/meeting/100/hotel.html for information regarding our overflow hotels.


Best Regards,
IETF Secretariat


From nobody Wed Jul 26 10:47:34 2017
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EAA3131DF9 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 10:47:32 -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, FREEMAIL_FROM=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 C0uz7LVMnSua for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 10:47:27 -0700 (PDT)
Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::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 61F8A131D2E for <ietf@ietf.org>; Wed, 26 Jul 2017 10:47:27 -0700 (PDT)
Received: by mail-wm0-x231.google.com with SMTP id c184so85257697wmd.0 for <ietf@ietf.org>; Wed, 26 Jul 2017 10:47:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=EnDZay8q2nJuj+++bgTWfqMGUzeSgVWjAkI+2QOYmok=; b=HBvvUk9PqGFpYrA97yVao3vFN5dSGAgB9qSVElTuNoT/O+1dUhkwEOeYJ6UH1FSmwK zO3u5bfXj6btTtdexinNC/SdvR9pUFslfoBh0ZYSoYE3LMz3fCf4VeQ3oZ2YEG5ONuGd BZnmuCyCgPtbKnGPR4R6oW3nDiJG/1qvmrbJeYcihswzRjYmvz+3OruFICKWJAZD8hK5 KUAcNgC+JUFmfrkAWzuVmEqciRHKg/q1DCmC3U6ardF+rde6264irKD79dqGr2N3QE50 CjgrLxkhjvZdKceapH/G4m3iC+Jl6v2207Hagw0igYV2n0oRlfpOm5z4Y9LNj+wG42dl Z8jQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=EnDZay8q2nJuj+++bgTWfqMGUzeSgVWjAkI+2QOYmok=; b=SfFtKZmOVSkkvKwhv7p0fQxHqg/5NyPV32T+NdEphkX68PhqUsC7erzPNpsipfIlSn 0zPhlJ36WQGYmxiQN+HMa3pi8pwWkFSar0/Ka3EzVA53jGcXu7nVjE1ZA2mPTKy2m5fC 0WcP/h0jhEGuDSj8qosDVo4tMsTrDh8wHTGjZSMQQ3Djt0qX2JCB25cvMbQS/eY3Oy/W KVIul4IN2GasiPwPFQZ49rp5RZR2TDmMgPgJfq2b9dzHb/D14zDZDCvNC5jqLoEAiI2f +SniyuLlFjT7PrxubroZvKrOuhdoRuRxDj1RhWcae3f4vMKLVQaZ8ehkxApy35XG0AXD nkeA==
X-Gm-Message-State: AIVw113h6AbYkeaTMqrIROlivW580LKsjbOhjxXZIU0L4L2IwaIgXuZo Ud2d3JEXMqU348hsOVI=
X-Received: by 10.28.49.3 with SMTP id x3mr1361750wmx.39.1501091245618; Wed, 26 Jul 2017 10:47:25 -0700 (PDT)
Received: from ?IPv6:2601:647:4d01:db10:bc91:2c1d:5a3f:3eb4? ([2601:647:4d01:db10:bc91:2c1d:5a3f:3eb4]) by smtp.gmail.com with ESMTPSA id v2sm10906825wra.2.2017.07.26.10.47.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Jul 2017 10:47:24 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <EF2F4195-A97F-46CB-B2D2-DB7A5E11874F@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_C911AC49-1A49-4A8F-8A6B-9B984EA99BB9"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Announcement on IETF 100 Hotel Reservations
Date: Wed, 26 Jul 2017 10:47:20 -0700
In-Reply-To: <150108971740.23120.257371533321943899.idtracker@ietfa.amsl.com>
Cc: Bob Hinden <bob.hinden@gmail.com>
To: IETF <ietf@ietf.org>
References: <150108971740.23120.257371533321943899.idtracker@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iTbr1Y2OFgWaTjL4Zpd8jqxcfwc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 17:47:32 -0000

--Apple-Mail=_C911AC49-1A49-4A8F-8A6B-9B984EA99BB9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Thanks.

I was able to find a room at the Fairmont by trimming my dates on both =
ends.  My flight arrives a little after midnight, I had hoped to get a =
room for the night before to not have to wait until 3pm checkin.  =
However, I note that there are transit hotels in the airport, this might =
make sense to get some sleep after I arrive.

Hope this is helpful to others.

Bob

> On Jul 26, 2017, at 10:21 AM, IETF Secretariat =
<ietf-secretariat@ietf.org> wrote:
>=20
> Hello IETFers,
>=20
> We are happy to see the excitement from the community for IETF 100 in =
November! At this point, there are sold out dates at both the Swissotel =
and Fairmont. The Fairmont has no available room nights on November 9th, =
10th and 18th, and the Swissotel fully booked on November 10th, 11th and =
17th. We are working to add room nights on these dates as soon as =
possible. Because of the time zone difference there may be a delay in =
adding room nights to these dates. We apologize for any inconvenience. =
If you have any further questions or concerns please contact =
agenda@ietf.org. We will update the community as soon as we can. Please =
also reference the IETF 100 hotels page =
https://www.ietf.org/meeting/100/hotel.html for information regarding =
our overflow hotels.
>=20
>=20
> Best Regards,
> IETF Secretariat
>=20


--Apple-Mail=_C911AC49-1A49-4A8F-8A6B-9B984EA99BB9
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJZeNWpAAoJEK7rdBF357uorYQIAKC/+Wetwq1O5sOKHyYQQwbB
VRVD8bJn/Lan+lbmtC5AbgKCcUXd3lpZxP/VnZ0WmO51Hrfbjhu+No7Nuvb2KuSP
v4A31a+77VMSxzylET0rYXflnS79+usIeXyV/p/sR3IsGJ/+JQAMhEXKfxb9OJHQ
2GRv8ggM1JLsGKUNB8N966lCQgL8Bdtg2stuNzKxE3C9KJ2M6hM/O4sdNVmmiCc4
S306PKYEQKoo3CfjZYATb2UAOXq4zcAuekw0E+KhzqqlYAxamSeZstiEIyAxIc00
EbFNAE2Zu3RAmbyuK05gR5PXJ8+W8vBNEw++YGMYTU4JASquVeP42UHFQBswT90=
=NUKt
-----END PGP SIGNATURE-----

--Apple-Mail=_C911AC49-1A49-4A8F-8A6B-9B984EA99BB9--


From nobody Wed Jul 26 11:32:40 2017
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F35F6131C8D for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 11:32:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.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 0isEOtQfLStz for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 11:32:37 -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 2C3B6131DAF for <ietf@ietf.org>; Wed, 26 Jul 2017 11:32:36 -0700 (PDT)
Received: from resomta-ch2-02v.sys.comcast.net ([69.252.207.98]) by resqmta-ch2-03v.sys.comcast.net with ESMTP id aR6Gd4lHOOZSqaR6pddJaS; Wed, 26 Jul 2017 18:32:35 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1501093955; bh=HIIKgR3bqJW3nNR/u24YZKUvjNrWxLbhHedKGRHCFLE=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=P9A6mn0gtwJuBqmz4OoLHc0FA9YZ8k90C6ttG1uveYZv/0SpheUyBSFsW3uQ2jrH1 wmrh2lFnzpRkImNrt2iovzELE6i/fzV42u3yzXFyIrE1DsCBDC59h01Mv5a4OH29pb WSIknXsL3emlLge3PCmRnRHkBkJIT/T5bQ/kFHxyUBCSf4Jc1IiyJx7olrNIxtbVv4 z7vVj6dRXqa/j7ibCFlroDWHZ8/g7kzPFjzHAt7XT9olMKQpbwKDAGnYbF/ftYtZrS eSY91/AlUD6PulA8EXWsoJUS0KZOmiZyy4RKhP/swlsJKBN3zRwg+hefS/JcY7TAoq tnP/JK97VspQQ==
Received: from [IPv6:2601:152:4400:dbdc:e86f:a899:cdda:3127] ([IPv6:2601:152:4400:dbdc:e86f:a899:cdda:3127]) by resomta-ch2-02v.sys.comcast.net with SMTP id aR6odM06xnYL2aR6pdTk5X; Wed, 26 Jul 2017 18:32:35 +0000
Subject: Re: Announcement on IETF 100 Hotel Reservations
To: ietf@ietf.org
References: <150108971740.23120.257371533321943899.idtracker@ietfa.amsl.com> <EF2F4195-A97F-46CB-B2D2-DB7A5E11874F@gmail.com>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <100a6ef1-1b1a-9123-398f-1883a167c5e1@comcast.net>
Date: Wed, 26 Jul 2017 14:32:34 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <EF2F4195-A97F-46CB-B2D2-DB7A5E11874F@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-CMAE-Envelope: MS4wfJDrKTBYyVFNUJbuvV1BUW01FpCws/IRHG1pZbkVvmgFnAAK885JRkJhpk25RjG2oVXH9vWYKAwaLFoppSTRVWEiVMeSwUS0opwRp7TEPm9ay8o9Bg1b +oWScFhnDZOoNExTPqqwsuQVLzyPRhGRWvdB/vTna3L+6/NbGCfK/tpG+Qs2fLsohByZWdKLOZvTTg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fPDK7ol2dDor7uqEOtblh8co2Pw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 18:32:39 -0000

On 7/26/2017 1:47 PM, Bob Hinden wrote:
> I had hoped to get a room for the night before to not have to wait until 3pm checkin.  However, I note that there are transit hotels in the airport, this might make sense to get some sleep after I arrive.

Try this  maybe: 
http://www.changiairport.com/en/airport-experience/attractions-and-services/pay-per-use-lounges.html 
- the T3 Haven lounge


From nobody Wed Jul 26 11:48:06 2017
Return-Path: <olejacobsen@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0407131C51 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 11:48:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.722
X-Spam-Level: 
X-Spam-Status: No, score=-2.722 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_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=me.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 LGLUj_ulMYg5 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 11:48:02 -0700 (PDT)
Received: from mr11p00im-asmtp002.me.com (mr11p00im-asmtp002.me.com [17.110.69.253]) (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 C252312426E for <ietf@ietf.org>; Wed, 26 Jul 2017 11:48:02 -0700 (PDT)
Received: from process-dkim-sign-daemon.mr11p00im-asmtp002.me.com by mr11p00im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OTP00400NBV6X00@mr11p00im-asmtp002.me.com> for ietf@ietf.org; Wed, 26 Jul 2017 18:47:42 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017; t=1501094862; bh=9Jrbr0yrSqo153/+kOWwnXQc+X67KCkbLUnOcLluqmk=; h=Date:From:To:Subject:Message-id:MIME-version:Content-type; b=0rzOHEii4Qn1FyjA0XUhUSRsFcrksyvSBotAngjmducRUNOQXqWHdEj6RbmpFZ5A7 CKswuNQ1gqj2XjSBTeR92zRCitsG/7ZL0/FMV+1lgMpp5GAEbyiuhNxKqhfPyY4dEO DbOCOHRv4Vfs9nPWwYGYFGCRw5gyXjSwXUILaA7AyvsaFRxjCVsV2wfDgMi/BysNfG Lts1b/C0ER4C0LGuqYner++lvLrnH6/sqYb0pAVpxV1rb6S5Ll+pkGPHtCx1686HYW SFVlwToGVKB/CuOjMzErYx0QHeBaCnzvP41rn7spe3GdqUQSZYV8pzVprSQzAt2RyU 92OsmHFjijS8g==
Received: from icloud.com ([127.0.0.1]) by mr11p00im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OTP007AFO7FWE10@mr11p00im-asmtp002.me.com> for ietf@ietf.org; Wed, 26 Jul 2017 18:47:40 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-07-26_08:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1701120000 definitions=main-1707260272
Date: Wed, 26 Jul 2017 11:47:39 -0700 (PDT)
From: Ole Jacobsen <olejacobsen@me.com>
Reply-to: Ole Jacobsen <olejacobsen@me.com>
To: The IETF <ietf@ietf.org>
Subject: Re: Announcement on IETF 100 Hotel Reservations
In-reply-to: <100a6ef1-1b1a-9123-398f-1883a167c5e1@comcast.net>
Message-id: <alpine.OSX.2.01.1707261133380.78919@rabdullah.local>
References: <150108971740.23120.257371533321943899.idtracker@ietfa.amsl.com> <EF2F4195-A97F-46CB-B2D2-DB7A5E11874F@gmail.com> <100a6ef1-1b1a-9123-398f-1883a167c5e1@comcast.net>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_8ZhroUa3HUa1HIpZdXQwQE1D4k>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 18:48:05 -0000

As a relatively frequent visitor to Singapore, let me just add:

* There are LOTS of hotels in town, you can most likely find one in 
  your favorite price range and hotel group. Hilton, Hyatt, Marriott,
  Intercontinental, etc, all can be found in Singapore.

* Singapore has a very comprehensive public transport system:

https://www.lta.gov.sg/content/ltaweb/en/public-transport/mrt-and-lrt-trains/train-system-map.html

* If you arrive very late and you are tired, I'd recommend taking a 
  taxi to your hotel. The rates are not very high compared to many 
  places in the world, even at the "night tariff."

* The ride from Changi to the center of Singapore takes about 20 
  minutes.

* It is always hot and humid in Singapore, see:

http://www.holiday-weather.com/singapore/averages/


Ole


Ole J. Jacobsen
Editor and Publisher
The Internet Protocol Journal
Office:  +1 415-550-9433
Cell:    +1 415-370-4628
Docomo:  090 3337-9311
Web: protocoljournal.org
E-mail: olejacobsen@me.com





From nobody Wed Jul 26 12:28:19 2017
Return-Path: <linuxwolf+ietf@outer-planes.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52AEC12EC13 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 12:28:18 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=outer-planes-net.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 DIr7t47OKFws for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 12:28:15 -0700 (PDT)
Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::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 9691B131CCA for <ietf@ietf.org>; Wed, 26 Jul 2017 12:28:15 -0700 (PDT)
Received: by mail-it0-x232.google.com with SMTP id v205so22334890itf.1 for <ietf@ietf.org>; Wed, 26 Jul 2017 12:28:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outer-planes-net.20150623.gappssmtp.com; s=20150623; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to; bh=Y67tEcVfovZOllt8gfOO4/0HMNygfcK22XRnyViv8js=; b=sl66Uk9k1vcPN8ih5xP+TdKHHYJQsu29nxRrvBUQb3JUMUCYvW6Vmsc2GL+Y9rh4KL xb+nYNZPqr87zXKUhWT6V0HMmOhjREF1R4gkR8yJqSVxWdwZwCtDfSeyXk3uX5JTm/ui 7WJCcHIPWmufkNP7sgaK4X6BJKHeovebfEk4R42exK8PajfWahd/oCFBo5+a1rgxiy89 zQZVlkpij+59nDoYmg+Z5LQtLjfrX3d4XMnhk+K9g3utyQo7En++o0ubfE1D4o6/Nwv1 P+m2D12Aw0h8svQodlAhpYsjH0SoIYxhrCS19KhWzDT27ynas1VlO+nUvu71FRoAt0Bt /DDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to; bh=Y67tEcVfovZOllt8gfOO4/0HMNygfcK22XRnyViv8js=; b=gFXKry1FgW9oH3xvmUENHYtZrjS05YNRonH6pA5+m1/0ybOqjDyWDJR516BtuJxOXF vGRcqqmghfIjQYMz8TQpXdF1i9nUJ46c/MBZfxNKr0+JqIo9Ygn8/yspVeGGzVmYP8RD D1aMshHIHQoXG0dG2Z9diwA0u7vv5bGnZTXKTqotFjaltuk0LDRgjNEtWkUY1cGFXRo7 33lo0IqnN04Yh2tDZlhfFTgLsdcUABOX5lIcJgdpj9Y4gSjJxvnLDXeaX93jonsBKJNQ 9bjBfr1eUVMTwG2p9GewQGFsbnzunEXfuPzneHObPVy9wHVnBGfD9aHOlrAVCKnsXQyu myRg==
X-Gm-Message-State: AIVw1121tmBqh4UxcnriDyqayune/n3hvQ4dMDnZSuZxErjYLqGoepCa 56EHkQlfg/ShaRpt
X-Received: by 10.36.196.67 with SMTP id v64mr2232518itf.89.1501097294870; Wed, 26 Jul 2017 12:28:14 -0700 (PDT)
Received: from [192.168.29.239] (c-73-217-32-196.hsd1.co.comcast.net. [73.217.32.196]) by smtp.gmail.com with ESMTPSA id 202sm327960itx.24.2017.07.26.12.28.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Jul 2017 12:28:14 -0700 (PDT)
Sender: Matthew Miller <linuxwolf@outer-planes.net>
Subject: Re: [Curdle] Genart last call review of draft-ietf-curdle-ssh-ext-info-10
To: denis bider <denisbider.ietf@gmail.com>
Cc: gen-art@ietf.org, curdle <curdle@ietf.org>, ietf@ietf.org, draft-ietf-curdle-ssh-ext-info.all@ietf.org
References: <150093015937.32021.12465797358778837950@ietfa.amsl.com> <CADPMZDCE+m+_QA7s6vdFOw-7uF4cfV4g8_U07fb-Ydur30OR5g@mail.gmail.com>
From: "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>
Message-ID: <1eef6165-9b5b-c354-dffe-5df1e98098fa@outer-planes.net>
Date: Wed, 26 Jul 2017 13:28:12 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:55.0) Gecko/20100101 Thunderbird/55.0
MIME-Version: 1.0
In-Reply-To: <CADPMZDCE+m+_QA7s6vdFOw-7uF4cfV4g8_U07fb-Ydur30OR5g@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="8Gn9vxRJp6ejRsiLo3n6QEq1slDGSLWpi"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ywxIFGmydmbG0BlCaEPhcZLjZfc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 19:28:18 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--8Gn9vxRJp6ejRsiLo3n6QEq1slDGSLWpi
Content-Type: multipart/mixed; boundary="T8urOObO966rGt9CNOsknGPRejclqAA4F";
 protected-headers="v1"
From: "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>
To: denis bider <denisbider.ietf@gmail.com>
Cc: gen-art@ietf.org, curdle <curdle@ietf.org>, ietf@ietf.org,
 draft-ietf-curdle-ssh-ext-info.all@ietf.org
Message-ID: <1eef6165-9b5b-c354-dffe-5df1e98098fa@outer-planes.net>
Subject: Re: [Curdle] Genart last call review of
 draft-ietf-curdle-ssh-ext-info-10
References: <150093015937.32021.12465797358778837950@ietfa.amsl.com>
 <CADPMZDCE+m+_QA7s6vdFOw-7uF4cfV4g8_U07fb-Ydur30OR5g@mail.gmail.com>
In-Reply-To: <CADPMZDCE+m+_QA7s6vdFOw-7uF4cfV4g8_U07fb-Ydur30OR5g@mail.gmail.com>

--T8urOObO966rGt9CNOsknGPRejclqAA4F
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Thanks very much for the response, Denis.

I think I understand the intent here, but I'm not sure this new text is
enough to mitigate some future conflict.  I'm also concerned that it
completely ignores the one-party extensions (e.g., an extension included
in the EXT_INFO by only the client or the server, but not both), and
what the impact is holistically.  Looking at the one-party extensions
defined herein, I can't see how their order matters; but does that mean
the order will never matter?

In writing this reply, I wondered if it's better for the order to always
be irrelevant; an implementation might be allowed to hint its preferred
order in the EXT_INFO, but implementations are still free to do whatever
makes sense to them within the bounds of the relevant extension
definitions.  If an extension ought to take precedence over another,
make it clear in its specification that it SHOULD (or MUST) be dealt
with before (or after) others.

Does that make sense?


- m&m

Matthew A. Miller

On 17/07/25 16:24, denis bider wrote:
> Good catch. I believe this refers to the following paragraph:
>=20
> "If an extension requires both the client and the server to include it
> in order for the extension to take effect, the relative position of the=

> extension-name in each EXT_INFO message is irrelevant."
>=20
> I have drafted the following new wording:
>=20
> "Unless a particular extension's specification indicates differently;
> then, if an extension requires both the client and the server to includ=
e
> it in order for the extension to take effect; implementers MUST use a
> default assumption that the relative position of the extension-name in
> each EXT_INFO message is irrelevant with respect to whether the
> extension takes effect."
>=20
> The purpose of this wording is to:
>=20
> - Provide a sensible default, which is that in the absence of specific
> knowledge, order of extension names does not matter.
>=20
> - Allow for deviations in special cases where there is specific knowled=
ge.
>=20
> For example, extension "foo-linux" could be specified, but after some
> years of use, it's observed that it works well for its main purpose, bu=
t
> is not ideal for a server on Windows. Therefore, extension "foo-windows=
"
> is specified, which works well when the server is Windows, but not as
> well when it's Linux.
>=20
> In this case, an implementation that supports "foo-linux" only would be=

> ignorant of anything else, and would use the default rule (order of
> extension names does not matter). However, an implementation that
> supports "foo-windows" could implement only that, or both "foo-linux"
> and "foo-windows". The specification for "foo-windows" could indicate
> that when both are supported, the first one listed by the server (or in=

> other cases, by the client) is used.
>=20
> Allowing for such an extension-defined special case would allow a Linux=

> server to advertise extensions [... "foo-linux", ..., "foo-windows",
> ...], preferring "foo-linux", but supporting the less appropriate
> "foo-windows" mechanism as well. Whereas, a Windows server could
> advertise [... "foo-windows", ..., "foo-linux", ...], preferring
> "foo-windows", but supporting the less appropriate "foo-linux" mechanis=
m
> as well.
>=20
> Does this work?
>=20
> If there are no objections, I'll upload a -11 draft version with this
> new wording.
>=20
>=20
>=20
> On Mon, Jul 24, 2017 at 3:02 PM, Matthew Miller
> <linuxwolf+ietf@outer-planes.net
> <mailto:linuxwolf+ietf@outer-planes.net>> wrote:
>=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.=C2=A0 Please treat these comments j=
ust
>     like any other last call comments.
>=20
>     For more information, please see the FAQ at
>=20
>     <https://trac.ietf.org/trac/gen/wiki/GenArtfaq
>     <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" explici=
tly
>     states in the second paragraph a condition where the relative order=
 of
>     extension-names in an EXT_INFO message is irrelevant.=C2=A0 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 o=
rder
>     *is* relevant/important, sometimes.=C2=A0 If relative order is expe=
cted 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
>     _______________________________________________
>     Curdle mailing list
>     Curdle@ietf.org <mailto:Curdle@ietf.org>
>     https://www.ietf.org/mailman/listinfo/curdle
>     <https://www.ietf.org/mailman/listinfo/curdle>
>=20
>=20


--T8urOObO966rGt9CNOsknGPRejclqAA4F--

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

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJZeO1NAAoJEOz0ck4QngW7+XwH/RQTYuE2WjpH9eALQH3ZTa4s
qJpjNYwl+HaNyd1MWySuYDGOLQzWModVTAsOKhSC1uCMhhyIz508XzdwaoVaEOg/
67dMv1NwzPeU6ggvuww4iyFSl7PKu9jhkBzD5Xd3LMWNtKQvL36HAyDVOC3omu55
6xBt/B30OCXdmIDQG8N/orcexlhDk8In60C07HD9psNY81IFIDrZPLYx5+grZSbX
rWRXc38CVFQz42rOjWccFUeMq7tbEmQkfbrnkq02cc0JUWhRDXzXNhJu0L+aF4ll
8c1kiG641VyCFNmFgac4ZOV4iG9YMNuttQxkzQ7kjp2YTEY2Q7QF4hvZu7TkI2g=
=7D6i
-----END PGP SIGNATURE-----

--8Gn9vxRJp6ejRsiLo3n6QEq1slDGSLWpi--


From nobody Wed Jul 26 14:25:55 2017
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 083C1126B6D for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 14:25:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.421
X-Spam-Level: 
X-Spam-Status: No, score=-6.421 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, 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 vDkpgNLdmlia for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 14:25:53 -0700 (PDT)
Received: from smtpde02.smtp.sap-ag.de (smtpde02.smtp.sap-ag.de [155.56.68.140]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 601BC12420B for <ietf@ietf.org>; Wed, 26 Jul 2017 14:25:53 -0700 (PDT)
Received: from mail07.wdf.sap.corp (mail04.sap.corp [194.39.131.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtpde02.smtp.sap-ag.de (Postfix) with ESMTPS id 3xHp7M6hzxz25Bk; Wed, 26 Jul 2017 23:25:51 +0200 (CEST)
X-purgate-ID: 152705::1501104351-00000861-43A4130A/0/0
X-purgate-size: 1333
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate-type: clean
X-SAP-SPAM-Status: clean
Received: from ld9781.wdf.sap.corp (ld9781.wdf.sap.corp [10.21.82.193]) by mail07.wdf.sap.corp (Postfix) with ESMTP id 3xHp7M42wwzGnyd; Wed, 26 Jul 2017 23:25:51 +0200 (CEST)
Received: by ld9781.wdf.sap.corp (Postfix, from userid 10159) id 85E0F1A6CB; Wed, 26 Jul 2017 23:25:51 +0200 (CEST)
Subject: Re: Revamp of the www.ietf.org website
In-Reply-To: <alpine.DEB.2.02.1707261649140.29742@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Date: Wed, 26 Jul 2017 23:25:51 +0200 (CEST)
CC: Ted Lemon <mellon@fugue.com>, IETF <ietf@ietf.org>
Reply-To: mrex@sap.com
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20170726212551.85E0F1A6CB@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XXcX-IIHxFylGlLWJa0mU-W8UNY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 21:25:55 -0000

Mikael Abrahamsson wrote:
> 
> Screenshot from my screen:
> 
> http://imgur.com/a/iJCLV

Here is what the sites look like on my mobile phone:

https://beta.ietf.org  ->  http://imgur.com/a/gFJLe

https://www.ietf.org   ->  http://imgur.com/a/iguEO


For me, the https://beta.ietf.org, besides wasting a considerable
amount of my monthly data volume, is pretty much completely useless,
whereas the old site comes up quickly, in an extremely familiar fashion,
and I can easily and quickly zoom into my area of interest.


The https://beta.ietf.org is like a toddler coming into a big
ballroom in search for his parents.  He can not see over tables,
so he has to run through the entire room around every table to
check all the chairs for his parents.


As an (6"4) adult, I'm more used to looking into a room,
glancing over all tables without _having_ to run through
the room.   The https://beta.ietf.org is forcing the
poor toddlers perspective of the world on me, forces
me to run through every passage and corner of a poorly
readable graphical maze, having to pick up every stone
and look below for what I'm interested in, making me
wait for the slowly loading page, wasting my mobile
internet volume, and wasting my time trying to discover
what is new or (ir)relevant.


:-(((((((


-Martin


From nobody Wed Jul 26 15:32:58 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D734D131E89 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 15:32:56 -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 FC2zBh4hEgzj for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 15:32:55 -0700 (PDT)
Received: from mail-pg0-x232.google.com (mail-pg0-x232.google.com [IPv6:2607:f8b0:400e:c05::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 0413B131E8C for <ietf@ietf.org>; Wed, 26 Jul 2017 15:32:55 -0700 (PDT)
Received: by mail-pg0-x232.google.com with SMTP id 123so89743180pgj.1 for <ietf@ietf.org>; Wed, 26 Jul 2017 15:32:55 -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=MwvUk6MgeF8sIdq/7EUBsng2zE8R3B1Fe6wTr0KGo3A=; b=W3jFzhk0G6uywPuHLAAmrzyBi3HwmC+HSRKKauzZ+Rsf9tbNNkU6PhNkQuZrYfm7xc oCMLLTnlx2QqV7DuzehlPu6YB1CJjwTkHBinu0gViBs/myVMd8c+21alaiIF0iVFfas7 cIoCIYYyGrl+i3Pqx6Y1Zqk654wCLOpMJwAVJWk/yhIMhXUbUbBuB9ZAXqREJOvFJ1C3 TZpwIfv8eAIh9DQEDENIDgsfYbRU+H8SWSyPxBHfJHYzkeEvpnJOBa8/93OkvpZFX2DH R9sQEwOIdDgc6BeJwh4l6LOTDoA7ASuO4s2hhpc6fv5gpOa4XU6a3VDA676gbCooqov1 WHOg==
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=MwvUk6MgeF8sIdq/7EUBsng2zE8R3B1Fe6wTr0KGo3A=; b=h9HDOnAmjCgvS6MDDhcTbXkJ83MW15f/hQNj7nbCU+rR2t+cWvX9dSkOnFd0ikst6I iSIn5Hmf+VIUirmWdkh6LeHcr9l48xicYV/WlZRewagKoNt09FQ55ya+PGpZghvow5MJ t4BjTBPpPaKERV7rLBdAlIeSHjJcCBwJhCmnGdECObqLMVry+xQNHmPLRuj3f36GnQJ3 QAfMNulMPdEBclX67Go+ophSwb9CZSL/I8wlzcudO1vMDH1NG98eB4O49xcr9hIC4iV+ J99PuJG5/SplZYiaRpeRmp5kiyv+EVKoCyuJhdmdDUcpXmUF2EU7/DjcVUjccYrDU0yv UDnw==
X-Gm-Message-State: AIVw111gnuGGWp4YFBPHWCTzxoBKE6OW+Z3yB1E6VSX7UqOlkNwYchlx ny1FO2gTpXVUcZOQ
X-Received: by 10.99.53.75 with SMTP id c72mr2248612pga.397.1501108374339; Wed, 26 Jul 2017 15:32:54 -0700 (PDT)
Received: from ?IPv6:2406:e007:4a2d:1:28cc:dc4c:9703:6781? ([2406:e007:4a2d:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id e5sm36143187pfd.41.2017.07.26.15.32.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Jul 2017 15:32:53 -0700 (PDT)
Subject: The index page [Revamp of the www.ietf.org website]
To: Tim Chown <tjc@ecs.soton.ac.uk>, Arkko Jari <jari.arkko@piuha.net>
Cc: IETF Discussion <ietf@ietf.org>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6394482@GLKXM0002V.GREENLNK.net> <39D1C0A9-DB43-42DD-BD3F-7D636856ECEF@gmail.com> <20170721083215.a2qdgfrpg2jf6irq@mx4.yitter.info> <B5AD9DB5-A261-4924-98F4-0D5945E68366@isoc.org> <D3576F2D-4D8F-4FAA-9E6E-80D2E08FE5A8@piuha.net> <28C0B89A-73A1-4CC3-8903-822D07F2383F@ecs.soton.ac.uk> <EMEW3|93a21cfe95bdba7176c7d3d313daf9d5y6PAMX03tjc|ecs.soton.ac.uk|28C0B89A-73A1-4CC3-8903-822D07F2383F@ecs.soton.ac.uk>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <04052cf6-11de-193d-7bc5-c3926182ca0a@gmail.com>
Date: Thu, 27 Jul 2017 10:32:56 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <EMEW3|93a21cfe95bdba7176c7d3d313daf9d5y6PAMX03tjc|ecs.soton.ac.uk|28C0B89A-73A1-4CC3-8903-822D07F2383F@ecs.soton.ac.uk>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qXZD8YUb25uzjAn_BMDO7rH3Qak>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 22:32:57 -0000

On 26/07/2017 21:22, Tim Chown wrote:
=2E..
> Well, if it=E2=80=99s =E2=80=9Cone click away=E2=80=9D, participants wi=
ll just bookmark or go directly to that page, and not www.ietf.org. I kno=
w I will.  Just like I sometimes also go directly to the datatracker.=20
>=20
>> For added bonus, maybe the most recent last
>> call / most recent blog article / most recent call for
>> hotel reservations opening or the like were to be also
>> displayed, the front door would give me an added
>> benefit of possibly stumbling on information that I
>> needed.
>=20
> Put all that on a one screen, participant oriented =E2=80=9Cindex=E2=80=
=9D page that we can go directly to.  Leave www.ietf.org to be the public=
 shop window.

I seem to see a lot of people saying roughly the same thing: we need
an index page for active participants which is
  - static content only
  - very low on graphics
  - a typical font size (legible but not enormous)
  - displays in several columns on a laptop/desktop screen
  - displays in one column on a smartphone**
  - has links to the stuff we use daily

** which possiibly means making two versions.

And for me the exemplar is still https://www.ietf.org/content.html,
updated with links to the new site.

    Brian


From nobody Wed Jul 26 15:59:53 2017
Return-Path: <ggm@algebras.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 419CB131EA7 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 15:59:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=algebras-org.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 HUdQ4lMm0bz0 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 15:59:49 -0700 (PDT)
Received: from mail-ua0-x22b.google.com (mail-ua0-x22b.google.com [IPv6:2607:f8b0:400c:c08::22b]) (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 22399131EAA for <ietf@ietf.org>; Wed, 26 Jul 2017 15:59:49 -0700 (PDT)
Received: by mail-ua0-x22b.google.com with SMTP id k43so91542562uaf.3 for <ietf@ietf.org>; Wed, 26 Jul 2017 15:59:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=algebras-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=C9O0AGy9FWbLZ141kk7xn5C1Nm1Du4dMRhDSRz6svHU=; b=s2IhOq4fE9aF+uEZ1KTN6Nh0DkuYL20zeEIraLfuiyblTxXKylQtRW9TEAN4GRtfsY ENXHjiwqhuMv1QEqRdEMtF6Y976SKz4sV14dPan8TtZW2pW3+SWnGvyI3Voim+7b7vFI w+Ooj2wwu02HeJ3DMz88YDaKsKsAgOuxhWjZvgDwzph5TZ7RBM/czwU8/FRyHJVy/fph Lwh9LPKMPCzi6tu1RLuoRFEp2TN+IfBKg0qs2kn4e22ngGRJlFZIEend2PsHVaD+o64m 1QdTzQsyG5UQ7jf8mV8SzSfWZgm7vO/EntN6+qxCIIUpLwEkf2L8TBOBtUTKN4cafngx sMyw==
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; bh=C9O0AGy9FWbLZ141kk7xn5C1Nm1Du4dMRhDSRz6svHU=; b=LSZu/10/TDnWCGYFmuOGxSxw8kxa5itfQY9HsOdbECY2WPMBoZSHcKzDRANtyBjmCM zVl8I/cGxywc+h7FblogPzKG6PcAo8cV5/OGaR5TZ+iozdeXMdSkIXgxmHuT9CUazDTN jTa+ZWIV9daxMXnufIAGVk28+hYjpne7xjjfLb7mN39wV5FlEL5LaniGVXljeM/+ZCpe vUHI8mdfQUw4v41Zzj8hXMtukwQObBnc+OpmPXLjfOS4TbG6UQl5IjtHSOb3oXdULMwb lKvXFsVbnX8O7X0GLF/akballIN3T3IZjK/mBxyZEaJAioBpbI7bW2s3hb3jDmontojw q2Yw==
X-Gm-Message-State: AIVw111NYJANNTdX49odfx5JvtwXxKy2PTUwG4c2cD0gQ4Cj57/0Aq5A QZI3iG43mPR9SBg8shGXHm9NSe2925O1N/E=
X-Received: by 10.159.56.217 with SMTP id w25mr1478257uaf.115.1501109987797; Wed, 26 Jul 2017 15:59:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.68.87 with HTTP; Wed, 26 Jul 2017 15:59:47 -0700 (PDT)
X-Originating-IP: [2001:dc0:2001:210:8de4:97b6:117e:2210]
In-Reply-To: <20170726212551.85E0F1A6CB@ld9781.wdf.sap.corp>
References: <alpine.DEB.2.02.1707261649140.29742@uplift.swm.pp.se> <20170726212551.85E0F1A6CB@ld9781.wdf.sap.corp>
From: George Michaelson <ggm@algebras.org>
Date: Thu, 27 Jul 2017 08:59:47 +1000
Message-ID: <CAKr6gn2Bkbe9tY2J7d+=+HxWKQZ4FPFanUsh7EphkqhTq7D4kQ@mail.gmail.com>
Subject: Re: Revamp of the www.ietf.org website
To: IETF <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0E3WU46MN_plYmftwZ9xDsUFBJ4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 22:59:52 -0000

I think there is a stylistic cliff in website design. One kind, the
older kind, uses a simple model of HTML which could be made more
overtly structured (use of id= tags) to make machine processing
simpler, but is in design and intent, a single load.
 * Its highly cacheable.
 * It makes little or no use of client-side drivers to direct
point-and-click because embedded URLs are literals, not
machine-generated on the fly.
 * It trivially meets vision impaired or voice-translation goals.
 * It trivially can be translated

It has one major drawback: a lot of people think its ugly.

The newer kind, the responsive reactive javascript kind, is far
simpler to navigate for anyone used to that template driven design, it
has a number of behaviours which in CHI terms a lot of people are
clued into and will react well to. It looks nice.

I think we've got ourselves caught on a cusp. The older kind suits
people who want to use the IETF web to conduct work, are in the
system, and have little concern for aesthetics. I think most of this
is met by the datatracker and like sites. That said, its a pain to
have to move to a different URL to get this kind of outcome for anyone
who is using the current site.

The new one is better suited to a world where we're trying to sell
something, or convince somebody. I can't help feeling this is one of
those 'what were we fighting for?' moments, if we feel we have to
adopt an aesthetic, distinct from operate a portal in our own
interest.

Do I think its possible we could use more modern responsive, js
enabled, template driven methods to update a website we run for our
own interest? I am not sure. I note that the things which I actually
USE on a day-to-day level like gitlabs, github, have really low levels
of use of this kind of feature to conduct work, and mostly it relates
to user-administration or introspection functions, of the site itself:
the primary role, to catalog and list artifacts under change and track
their differences and submissions, is pretty bereft of markup of THIS
kind. It has other markup, colorizing, denotation of state, which is
obviously using CSS and JS somehow.

isn't that actually close to what we want? Aren't we actually closer
to github, a wiki, and a calendar, than anything else?

On Thu, Jul 27, 2017 at 7:25 AM, Martin Rex <mrex@sap.com> wrote:
> Mikael Abrahamsson wrote:
>>
>> Screenshot from my screen:
>>
>> http://imgur.com/a/iJCLV
>
> Here is what the sites look like on my mobile phone:
>
> https://beta.ietf.org  ->  http://imgur.com/a/gFJLe
>
> https://www.ietf.org   ->  http://imgur.com/a/iguEO
>
>
> For me, the https://beta.ietf.org, besides wasting a considerable
> amount of my monthly data volume, is pretty much completely useless,
> whereas the old site comes up quickly, in an extremely familiar fashion,
> and I can easily and quickly zoom into my area of interest.
>
>
> The https://beta.ietf.org is like a toddler coming into a big
> ballroom in search for his parents.  He can not see over tables,
> so he has to run through the entire room around every table to
> check all the chairs for his parents.
>
>
> As an (6"4) adult, I'm more used to looking into a room,
> glancing over all tables without _having_ to run through
> the room.   The https://beta.ietf.org is forcing the
> poor toddlers perspective of the world on me, forces
> me to run through every passage and corner of a poorly
> readable graphical maze, having to pick up every stone
> and look below for what I'm interested in, making me
> wait for the slowly loading page, wasting my mobile
> internet volume, and wasting my time trying to discover
> what is new or (ir)relevant.
>
>
> :-(((((((
>
>
> -Martin
>


From nobody Wed Jul 26 16:33:25 2017
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B00D131EE1 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 16:33:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level: 
X-Spam-Status: No, score=-4.302 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_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
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 Le6QDIsm0EvX for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 16:33:16 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BC3F131EE2 for <ietf@ietf.org>; Wed, 26 Jul 2017 16:33:16 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6QNWxKj010550; Thu, 27 Jul 2017 00:32:59 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v6QNWxKj010550
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1501111979; bh=TiAQRck5fdrK4BKdu/YvBePf7NY=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=qgsuyob/eVlM1g8YWlKPRG4OmXvv3lCmNzKPFE4j0Y9MdwSJ0x6poLzxtKBza5MBD 05o/jAoJ7Ph/lXAaWheaM+P9QIqXjFvScDd7etgHkgMylJCFNNgYe8vwzAndd99e+A f0DnVbK2Rqurlxo5TxW/wWczaT+RJfoNT8C3m81M=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id y6Q0Wx1133811961yg ret-id none; Thu, 27 Jul 2017 00:32:59 +0100
Received: from 20010a88d51011.ipv6.customer.clara.net (20010a88d51011.ipv6.customer.clara.net [IPv6:2001:a88:d510:1101:75b2:2069:32a0:8c99] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6QNWrF4005769 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Jul 2017 00:32:54 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: The index page [Revamp of the www.ietf.org website]
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <04052cf6-11de-193d-7bc5-c3926182ca0a@gmail.com>
Date: Thu, 27 Jul 2017 00:32:53 +0100
Cc: Arkko Jari <jari.arkko@piuha.net>, IETF Discussion <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|b536356ced6bc10f3c2876d5af92c499y6Q0Wx03tjc|ecs.soton.ac.uk|B0F00265-66C0-4F84-A647-D111348BC010@ecs.soton.ac.uk>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6394482@GLKXM0002V.GREENLNK.net> <39D1C0A9-DB43-42DD-BD3F-7D636856ECEF@gmail.com> <20170721083215.a2qdgfrpg2jf6irq@mx4.yitter.info> <B5AD9DB5-A261-4924-98F4-0D5945E68366@isoc.org> <D3576F2D-4D8F-4FAA-9E6E-80D2E08FE5A8@piuha.net> <28C0B89A-73A1-4CC3-8903-822D07F2383F@ecs.soton.ac.uk> <EMEW3|93a21cfe95bdba7176c7d3d313daf9d5y6PAMX03tjc|ecs.soton.ac.uk|28C0B89A-73A1-4CC3-8903-822D07F2383F@ecs.soton.ac.uk> <04052cf6-11de-193d-7bc5-c3926182ca0a@gmail.com> <B0F00265-66C0-4F84-A647-D111348BC010@ecs.soton.ac.uk>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3273)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=y6Q0Wx113381196100; tid=y6Q0Wx1133811961yg; client=relay,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v6QNWxKj010550
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zJQVNBJLsB2Dx4vF3f0JBQnE_98>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jul 2017 23:33:23 -0000

> On 26 Jul 2017, at 23:32, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>=20
> On 26/07/2017 21:22, Tim Chown wrote:
> ...
>> Well, if it=E2=80=99s =E2=80=9Cone click away=E2=80=9D, participants =
will just bookmark or go directly to that page, and not www.ietf.org. I =
know I will.  Just like I sometimes also go directly to the datatracker.=20=

>>=20
>>> For added bonus, maybe the most recent last
>>> call / most recent blog article / most recent call for
>>> hotel reservations opening or the like were to be also
>>> displayed, the front door would give me an added
>>> benefit of possibly stumbling on information that I
>>> needed.
>>=20
>> Put all that on a one screen, participant oriented =E2=80=9Cindex=E2=80=
=9D page that we can go directly to.  Leave www.ietf.org to be the =
public shop window.
>=20
> I seem to see a lot of people saying roughly the same thing: we need
> an index page for active participants which is
>  - static content only
>  - very low on graphics
>  - a typical font size (legible but not enormous)
>  - displays in several columns on a laptop/desktop screen
>  - displays in one column on a smartphone**
>  - has links to the stuff we use daily
>=20
> ** which possiibly means making two versions.
>=20
> And for me the exemplar is still https://www.ietf.org/content.html,
> updated with links to the new site.

Yes, that page is a great example.=20

Tim=


From nobody Wed Jul 26 17:40:29 2017
Return-Path: <narellec@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9173E131F16 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 17:40:28 -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 Vqool0DptoPp for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 17:40:26 -0700 (PDT)
Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (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 7FECD131F0B for <ietf@ietf.org>; Wed, 26 Jul 2017 17:40:26 -0700 (PDT)
Received: by mail-oi0-x22c.google.com with SMTP id x3so90404203oia.1 for <ietf@ietf.org>; Wed, 26 Jul 2017 17:40:26 -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:content-transfer-encoding; bh=RhEnsex84gmBHMyQpRUYvwPd7KnxB5jUJohBy+udsZw=; b=t1mCpnnf6O64VoKfS3itZIUJSXwddPgFvVK7gyADd04jk8HdWNm4UmeZPDtTc6HVad 00jU/C1OuD3t2QmrC9UKzo53ObHI3DscMfgOAo9Tbi0pOWo3xenCtFV0yw2dRxWSXzyy svyxGemcKFwE+4pUsN1OoW3K4zrvAqTROAOaI6fFcQSfUfORtQb6e5N1UMqjaJXAnljZ INVRkiCPYfUhnlq03E79I7sGPTBE0D54oJ91VU4gcLABmtGZMuyEw3ZSyHxTHfAFCmoq Ftikbv/o00UvnaktfjKpqjDpIobTTpzX8LUuVMYS+J5kn1VRAjIxfdmKChctecUQx1Se xqOw==
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:content-transfer-encoding; bh=RhEnsex84gmBHMyQpRUYvwPd7KnxB5jUJohBy+udsZw=; b=FPi4MwqOxFbzW/6YkInsJiVrAFDgQaE+/06zdjHDNCrU906tWGIuegoc459ekHl/yR 4ZieAtZyp+eCpHmbg2RpJkElD7VLOrSk6WKhqUXhDrTSukxuvmKN5P7iktDFM0uNuLUg 1+t7qfvqx8u0girFOnYEOJJ0KD4DaqFineB28WkEFSMw6NWPOLCP8QucreSdv4gs8BKe +u+UituvjgCB8S/dhn2t3yeMe9E80rxBHaPClRter98ARZWIKAiU/JPFjekML7NR6E5L XyZM559R2Q/GbgsyPw6J1BtQrfo4/J9Tuiz+KCHeBufPYy1kvkQhY2yU2QyfyRSh0nMv vUwA==
X-Gm-Message-State: AIVw110zZioNTVipiLl95KgbLMIHw8gcTr3g9sOJQzSTpi+fNRtveF+E e5vkulBSrRuAEeIUezEozW7qctaFnLHs
X-Received: by 10.202.205.209 with SMTP id d200mr2233944oig.321.1501116025804;  Wed, 26 Jul 2017 17:40:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.87.33 with HTTP; Wed, 26 Jul 2017 17:40:25 -0700 (PDT)
In-Reply-To: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com>
From: Narelle <narellec@gmail.com>
Date: Thu, 27 Jul 2017 10:40:25 +1000
Message-ID: <CACRMD1ExqqtZm2V5ou_8Qg3VTZgEnBAb5HzQzRVw7mFgxrQeCg@mail.gmail.com>
Subject: Re: Revamp of the www.ietf.org website
To: Russ Housley <housley@vigilsec.com>
Cc: IETF <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2Sw8zXHll9kfTbUwkkjt2ibSHmo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 00:40:29 -0000

Thanks Russ and team
I'm sure a huge amount of work has gone into this and I imagine you
have done the obvious traffic analysis to determine where the most
frequently accessed information needs to be.

I asked my accessibility expert to have a quick look and a blind user
to check it. The latter observed that he didn't find any obvious
issues (great! he uses a fairly current Jaws which is the dominant
screen reader), but my developer and site manager was more critical:

--- begin comments ----

Without going into a full accessibility check;

The navigation is a bit all over the place visually.  Using keyboard
it goes from IETF logo to the other side of the screen for News &
Blog, to Contact, skips search,  then goes to tools, then goes back to
the other side of the screen for  About, etc, etc.  I couldn=E2=80=99t see =
how
to get into the submenus using only key-strokes.

Images don=E2=80=99t seem to have Alt text or Titles.

The link colour, Light blue (#1BAEDD), is not WCAG 2.0AA compliant.

No breadcrumbs.

I could probably find another hundred things but I think the basic
message is that it hasn=E2=80=99t been designed with WCAG in mind.

Putting the non-compliance to WCAG aside, it=E2=80=99s a pretty standard ru=
n
of the mill site.  I don=E2=80=99t see anything that stands out as needing
massive adjustment. Although, the choice of images is pretty boring.

----- end coments ---

There are some very good accessible CSS, joomla etc templates around.
We have implemented one at accan.org.au and while this is a site for a
very different purpose, note the accessibility menu (top right from a
desktop, top line from a mobile) that allows resetting to
mobile/desktop, night mode, text size and contrast. This is a really
useful feature for accessibility and allows people a lot of useful
control.

Note also all our images have alt tags, and all documents are
available in an accessible marked up form.

Some of that can be time consuming for humans, but until image
recognition goes commodity, that's what is needed.


regards


Narelle


On Sat, Jul 15, 2017 at 7:21 PM, Russ Housley <housley@vigilsec.com> wrote:
> I am pleased to report that there has been a lot of progress on the proje=
ct to revamp of the www.ietf.org website. The updated website will be the =
=E2=80=9Cfront door=E2=80=9D for the IETF, not only for for active IETF par=
ticipants, but also provides an onramp for potential participants, and help=
s explain the work of the IETF to people who are not directly involved in d=
eveloping Internet standards. The complete Scope of Work for the project is=
 available at:
>
>    https://iaoc.ietf.org/documents/IETF-Website-SOW-20140604-Final.pdf
>
> Based on recent feedback, including the demo table at IETF 98, the initia=
l design and features of the website have been improved in many ways. For e=
xample, in response to the feedback provided, there is now a single page th=
at provides links to tools and resources commonly used by active IETF parti=
cipants.
>
> The project is now entering the next phase of the website development. Th=
e goal for this phase is to gather input more broadly. While there are stil=
l a few features to be implemented and some content still needs to be fine =
tuned, the general organization and the look-and-feel of the website has be=
en implemented based on the initial research and input received to date. Of=
 course, there will be some additional significant work before the site is =
ready for production; for example, before the website is final, we will imp=
lement methods to ensure that well-known URLs continue to work as expected.
>
> The site is now accessible at:
>
>    https://beta.ietf.org
>
> Please take a look. We will be tracking issues that need addressing at:
>
>    https://github.com/ietf/www.ietf.org/issues
>
> Feedback can also be emailed directly to: webmaster@ietf.org
>
> At IETF 99 in Prague, there will be a table near meeting registration to =
demonstrate the beta website with =E2=80=9Coffice hours" posted on a sign b=
y the table. Please stop by if you are in Prague!  The office hours will be=
 at least:
>
>    Monday, July 17, 08:30-09:30 and 17:15-17:45
>
>    Tuesday, July 18, 08:30-09:30
>
>    Wednesday, July 19, 08:30-9:30
>
>    Friday, July 12, 08:30-9:30
>
> Thanks,
> Russ Housley
> IETF Website Revamp Project Manager



--=20


Narelle
narellec@gmail.com


From nobody Wed Jul 26 17:50:46 2017
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 099ED131F1B for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 17:50:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 TRePXeXF1KwJ for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 17:50:44 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (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 685DA131F22 for <ietf@ietf.org>; Wed, 26 Jul 2017 17:50:44 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id 8481C24AE16; Thu, 27 Jul 2017 00:50:34 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 58C07160070; Thu, 27 Jul 2017 00:50:39 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 45CD116006E; Thu, 27 Jul 2017 00:50:39 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id sXfVY5UOLWfy; Thu, 27 Jul 2017 00:50:39 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id E3B6A16004C; Thu, 27 Jul 2017 00:50:38 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 5D0C78013DB1; Thu, 27 Jul 2017 10:50:36 +1000 (AEST)
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: ietf@ietf.org
From: Mark Andrews <marka@isc.org>
References: <150107762165.23133.6738319854502205219.idtracker@ietfa.amsl.com> <3129.1501089388@obiwan.sandelman.ca>
Subject: Re: IETF 100 Registration and Hotel Reservations Open!
In-reply-to: Your message of "Wed, 26 Jul 2017 13:16:28 -0400." <3129.1501089388@obiwan.sandelman.ca>
Date: Thu, 27 Jul 2017 10:50:36 +1000
Message-Id: <20170727005036.5D0C78013DB1@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/m1znqfwoMp8fLQYwb-hliss-m58>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 00:50:46 -0000

In message <3129.1501089388@obiwan.sandelman.ca>, Michael Richardson writes:
> IETF Secretariat <ietf-secretariat@ietf.org> wrote:
>     > IETF 100 Information: https://ietf.org/meeting/100/index.html
>     > Register online at: https://ietf.org/meeting/register.html
> 
> Any reason the remote participation registration form can not open at the
> same time?
 
It appears to be half there.  Registration type on the main
registration page has a link to
https://www.ietf.org/registration/ietf100/remotereg.py but when you
hit "Submit Registration" it returns to the main registration page
for conformation with the "Full Rate Registration" radio box checked.

Mark

> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Wed Jul 26 17:59:49 2017
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9017131F26 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 17:59:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.88
X-Spam-Level: 
X-Spam-Status: No, score=-5.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 3od08j60IepH for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 17:59:47 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (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 78A6F131F23 for <ietf@ietf.org>; Wed, 26 Jul 2017 17:59:47 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 344933493A5; Thu, 27 Jul 2017 00:59:45 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 25B99160070; Thu, 27 Jul 2017 00:59:45 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 0640616006E; Thu, 27 Jul 2017 00:59:45 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id cCUhDJxgbNAo; Thu, 27 Jul 2017 00:59:44 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id AD33D16004C; Thu, 27 Jul 2017 00:59:44 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id E2B0C8014029; Thu, 27 Jul 2017 10:59:42 +1000 (AEST)
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, ietf@ietf.org
From: Mark Andrews <marka@isc.org>
References: <150107762165.23133.6738319854502205219.idtracker@ietfa.amsl.com> <3129.1501089388@obiwan.sandelman.ca> <20170727005036.5D0C78013DB1@rock.dv.isc.org>
Subject: Re: IETF 100 Registration and Hotel Reservations Open!
In-reply-to: Your message of "Thu, 27 Jul 2017 10:50:36 +1000." <20170727005036.5D0C78013DB1@rock.dv.isc.org>
Date: Thu, 27 Jul 2017 10:59:42 +1000
Message-Id: <20170727005942.E2B0C8014029@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UzM5MJU3qsYjoCcYq-Cyt0d6HBY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 00:59:49 -0000

I've opened a ticket for this.

In message <20170727005036.5D0C78013DB1@rock.dv.isc.org>, Mark Andrews writes:
> 
> In message <3129.1501089388@obiwan.sandelman.ca>, Michael Richardson writes:
> > IETF Secretariat <ietf-secretariat@ietf.org> wrote:
> >     > IETF 100 Information: https://ietf.org/meeting/100/index.html
> >     > Register online at: https://ietf.org/meeting/register.html
> > 
> > Any reason the remote participation registration form can not open at the
> > same time?
>  
> It appears to be half there.  Registration type on the main
> registration page has a link to
> https://www.ietf.org/registration/ietf100/remotereg.py but when you
> hit "Submit Registration" it returns to the main registration page
> for conformation with the "Full Rate Registration" radio box checked.
> 
> Mark
> 
> > --
> > Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> >  -= IPv6 IoT consulting =-
> -- 
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Wed Jul 26 18:03:12 2017
Return-Path: <lyndon@orthanc.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13A62131F28 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 18:03:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 pcLFNFQ6Kty8 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 18:03:06 -0700 (PDT)
Received: from orthanc.ca (orthanc.ca [IPv6:2607:f2f8:abf8::2]) (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 4457C131F24 for <ietf@ietf.org>; Wed, 26 Jul 2017 18:03:06 -0700 (PDT)
Received: from minnie.hitronhub.home (S0106a84e3f81a003.vc.shawcable.net [24.80.126.119]) (authenticated bits=0) by orthanc.ca (8.15.2/8.15.2) with ESMTPSA id v6R134s2046683 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Wed, 26 Jul 2017 18:03:05 -0700 (PDT) (envelope-from lyndon@orthanc.ca)
From: Lyndon Nerenberg <lyndon@orthanc.ca>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: the web site re-design
Message-Id: <CA404037-1A8E-486D-9D8C-FED25427688E@orthanc.ca>
Date: Wed, 26 Jul 2017 18:02:59 -0700
To: ietf@ietf.org
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/60nxIqrVjvxgTM1TqeQRwb6qDjM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 01:03:11 -0000

There is a lot of anecdotal commentary that www.ietf.org needs a =
re-design.  Why don't the people proposing this need write an I-D =
describing the need for this, and back it up with factual, not =
anecdotal, evidence.

--lyndon


From nobody Wed Jul 26 18:05:36 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D972131F30 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 18:05:34 -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 6Wv1QgPaeiLl for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 18:05:33 -0700 (PDT)
Received: from mail-pf0-x22a.google.com (mail-pf0-x22a.google.com [IPv6:2607:f8b0:400e:c00::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 516C9131F2B for <ietf@ietf.org>; Wed, 26 Jul 2017 18:05:33 -0700 (PDT)
Received: by mail-pf0-x22a.google.com with SMTP id q85so77121297pfq.1 for <ietf@ietf.org>; Wed, 26 Jul 2017 18:05:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=2LSsYVmNXPsifvMmidayFLrB7ZsPeMvBaDQUPomzVD8=; b=uLhI6HVS+0w/d7bkSHbSH5iW+H1kLG0h/8CO5N1p+OUsve6vSGeCPvf7d7l9oYdnvM HLOOK+6kX1xyyK5dpcXf7rtIK4rR1b0Bfpvi29hJc7EOF6Nch5VBIU54NWwNt0W5mF2F n2n3gXwXKlkDQtx73CYiPaQuZ0Y+RfQnuxizSknE6auqbHSZaNy/TjCa9mFJsf4ovnjf AKWVZdJx7ya5jUmngRV5HxXFB2Q96wUA9tcTCEM1a1y6l9RQJYwSxQLQGl1C0rjq7/9B l8l+75K98Lsep6c/Um1OS6af/YKwQ8fJcVubVf+zAv4Tzn76TNs1gjiVGMLyepqnxPHV zaEw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=2LSsYVmNXPsifvMmidayFLrB7ZsPeMvBaDQUPomzVD8=; b=LOD8JrG0QDWogLoNWZm1LmW77cqqy3refoQAv1BTa9sMugD0daLMk2cyXxE9a8CPcc +S0p9uyL8XvjpYra7D52yNvxedNbENqUE2weuHsoBksq5gIoNY9CkLuFwGC+IkoUXf/v kZ3ghRztDd7ciWCDxLedddf5m43Hw9nVT9VDKt1qiECy+jb39c23obu/1SqkPJbFas6V LZZiQcj+mc5ntJLlwxeYBgsKhMDTPf04dDns+77YgwxngE4d+W0WVWEbCVv85Z0wTzi8 87Te7daZlTGnrVj+iNFdGuJOiEzwVrSSAzsZdLzgxQ11BeEbyzHixF1F4Ktn1Rxn+P8I 3ReQ==
X-Gm-Message-State: AIVw111T5r4FhyWfOub9ElC1kHVbRXjMtj8SLvDnTgA8Lfjh67smAfEx EFwHjfgWdglv+xIe
X-Received: by 10.84.209.232 with SMTP id y95mr2629067plh.391.1501117532669; Wed, 26 Jul 2017 18:05:32 -0700 (PDT)
Received: from ?IPv6:2406:e007:4a2d:1:28cc:dc4c:9703:6781? ([2406:e007:4a2d:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id j20sm35881216pfk.73.2017.07.26.18.05.31 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Jul 2017 18:05:32 -0700 (PDT)
Subject: Re: Revamp of the www.ietf.org website
To: ietf@ietf.org
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <CACRMD1ExqqtZm2V5ou_8Qg3VTZgEnBAb5HzQzRVw7mFgxrQeCg@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <16a1559c-79a9-04d5-b6d1-39d2e466472a@gmail.com>
Date: Thu, 27 Jul 2017 13:05:36 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CACRMD1ExqqtZm2V5ou_8Qg3VTZgEnBAb5HzQzRVw7mFgxrQeCg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/djf7xTCk75w8UbplI8TQ3lB3PIw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 01:05:35 -0000

On 27/07/2017 12:40, Narelle wrote:
> Thanks Russ and team
> I'm sure a huge amount of work has gone into this and I imagine you
> have done the obvious traffic analysis to determine where the most
> frequently accessed information needs to be.
> 
> I asked my accessibility expert to have a quick look and a blind user
> to check it. The latter observed that he didn't find any obvious
> issues (great! he uses a fairly current Jaws which is the dominant
> screen reader), but my developer and site manager was more critical:
> 
> --- begin comments ----
...
> Although, the choice of images is pretty boring.

That is definitely a plus point (and I'm not joking, not even slightly).

    Brian


From nobody Wed Jul 26 18:10:24 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2C1E126C23 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 18:10: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, 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 VtOG_cqQa7E2 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 18:10:21 -0700 (PDT)
Received: from mail-pf0-x230.google.com (mail-pf0-x230.google.com [IPv6:2607:f8b0:400e:c00::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 8EDC3124C27 for <ietf@ietf.org>; Wed, 26 Jul 2017 18:10:21 -0700 (PDT)
Received: by mail-pf0-x230.google.com with SMTP id d67so9232400pfc.0 for <ietf@ietf.org>; Wed, 26 Jul 2017 18:10:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=8aBMDe38YjV5HSP5bI93ItFqGfBHw54Y8x3qtFX0sbs=; b=UOFkXQZ/+hYzUnM8qRiFxo71OBid99RSMTYVSH4wx3DGgLbc2UttwKU3l9vWWwny+f U1gte3wIFEC54Smnq1f3MY2Cy+OSqN2bUXQGZB2qjIf9Rk7jqZ5Kwyo73BPyjJ/VZv51 I83Ia3qXA9Cw7TG5cWW80BMm8WDBoqfrr/ezbGHlQW86Lgj+9O6HyhaQy/4w2cmF37Yb dDa+OaKak5mF7pV/0PJZq89a2aXxgzN/d+MNzOjM32F2yCWHLkY0GZ41FAnis39A5Rs0 pbRi8ZCyYbEGarFIaNRjdCDtAFfUGOFj7zkH3yGfZwu2Rdtikd1NbCTyr2A/6u0iBI8f lHaw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=8aBMDe38YjV5HSP5bI93ItFqGfBHw54Y8x3qtFX0sbs=; b=VahA8voNdVHNVFLwz9AWKarOvaqBtKGbWY1b+zrWfNu57ePipFYgFE5bv/gcosANV7 ShK/kNbQcRVbNZzQwLsidB9Ilep/h2l5nmTo2RYT60wKl896eV+0eCweh/EAUR7bgvbh 4EJG+MWHkqsBII95B11D7LiDR+dZIYg835HfLrjWk6MkhrU68sx1/5aQG0srjs13/yBx d8gipAppZRkC0u+symbsURXoRhTMyIpZslLTQUsxuTuomkZ+99ouUHvBsfHAVgugEgOd wKd15ygcTAVx3zTA9kwqbl4hfZRkgPjVPJvCf0bovGjkeZy4DArbpDOtytpRPlIPGnXY 74yg==
X-Gm-Message-State: AIVw113sNatYDJDn51za4aPeG7TkzXEGyi65qUK6AuaiXhVfYvD3hLLt m0qyM7VCUwyXFP6N
X-Received: by 10.84.167.2 with SMTP id c2mr2724956plb.370.1501117820750; Wed, 26 Jul 2017 18:10:20 -0700 (PDT)
Received: from ?IPv6:2406:e007:4a2d:1:28cc:dc4c:9703:6781? ([2406:e007:4a2d:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id p8sm19858947pfj.101.2017.07.26.18.10.19 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Jul 2017 18:10:20 -0700 (PDT)
Subject: Re: the web site re-design
To: ietf@ietf.org
References: <CA404037-1A8E-486D-9D8C-FED25427688E@orthanc.ca>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <5f979518-4abf-dddf-a7f7-67cd1350a1e0@gmail.com>
Date: Thu, 27 Jul 2017 13:10:24 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CA404037-1A8E-486D-9D8C-FED25427688E@orthanc.ca>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nthP21T5Md4GrZk4yy8Kzxvm92w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 01:10:23 -0000

On 27/07/2017 13:02, Lyndon Nerenberg wrote:
> There is a lot of anecdotal commentary that www.ietf.org needs a re-design.  Why don't the people proposing this need write an I-D describing the need for this, and back it up with factual, not anecdotal, evidence.

That was actually done a long time ago. (Not an I-D, but a requirements document, which
I'm sure can still be found somewhere). beta.ietf.org is output from that process.

     Brian


From nobody Wed Jul 26 18:13:17 2017
Return-Path: <lyndon@orthanc.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42A6D131F2C for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 18:13:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 Meo2iBVl4E8W for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 18:13:13 -0700 (PDT)
Received: from orthanc.ca (orthanc.ca [IPv6:2607:f2f8:abf8::2]) (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 EDFBD126C23 for <ietf@ietf.org>; Wed, 26 Jul 2017 18:13:12 -0700 (PDT)
Received: from minnie.hitronhub.home (S0106a84e3f81a003.vc.shawcable.net [24.80.126.119]) (authenticated bits=0) by orthanc.ca (8.15.2/8.15.2) with ESMTPSA id v6R1DAaI046738 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 26 Jul 2017 18:13:11 -0700 (PDT) (envelope-from lyndon@orthanc.ca)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: the web site re-design
From: Lyndon Nerenberg <lyndon@orthanc.ca>
In-Reply-To: <5f979518-4abf-dddf-a7f7-67cd1350a1e0@gmail.com>
Date: Wed, 26 Jul 2017 18:13:05 -0700
Cc: ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <CCB50FC9-75E2-4229-9265-7FC53635D373@orthanc.ca>
References: <CA404037-1A8E-486D-9D8C-FED25427688E@orthanc.ca> <5f979518-4abf-dddf-a7f7-67cd1350a1e0@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iQFngxtJ9iAoEWk_LwB7Y5AiOKg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 01:13:14 -0000

 done a long time ago. (Not an I-D, but a requirements document, which
> I'm sure can still be found somewhere). beta.ietf.org is output from =
that process.

If that exists, can we have it linked to prominently on the beta site's =
home page?  And have the document's status clarified?

--lyndon



From nobody Wed Jul 26 18:19:35 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43808131F28 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 18:19:34 -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 V4ev5SuPf0L6 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 18:19:32 -0700 (PDT)
Received: from mail-pg0-x229.google.com (mail-pg0-x229.google.com [IPv6:2607:f8b0:400e: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 7D493124C27 for <ietf@ietf.org>; Wed, 26 Jul 2017 18:19:32 -0700 (PDT)
Received: by mail-pg0-x229.google.com with SMTP id v190so91058402pgv.2 for <ietf@ietf.org>; Wed, 26 Jul 2017 18:19:32 -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=4y3ZfRj9YbWJuWd7wynXV4GbrCzqORL2EjXkydmOFm8=; b=FX1t2qNqbnW8cIbxgcoP6Kc7IUoFsKbw+goTflFRnCOjQYWA/0Kl2wOpCpG/bzn3KF VPu4wkU4+tdNxnotZUu1QjKG3u7UM4/VuQ970mgPw5Zi3sZY5sn1nDmbN1jQ58KO6XKa +m8DvTCRELLZugIc4A6Xj7kr7GElQ7yAEK2bG2YS6IG7ID0LDW2Xd2Toq2+FN5Wg88Qo 05ohpsgcmBYThk+w2Q5NHLSyeBTdXpYnuDGAKUXJNTD0k6KTN0JWkwxzEyrfybpzRFFa C2btmxG/V7izCXq2O9LhGICS6ddNfcPU4a2a9k7ZxrXj8atSjNKuZRMb3raVtEgzYffq chjA==
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=4y3ZfRj9YbWJuWd7wynXV4GbrCzqORL2EjXkydmOFm8=; b=c5lnl7YXe/Zsh4SS56OZnUrZXcIv+J+qAlvqFY9kpiMHJGrFCOdnvfF9IifJzqMz3q oaEGgkDosftIrzMlWTzl6Upa7yRpDbfRdEl6/qyyhk3cH3Gzm9lxTLzDQ0yXb4zP2+lW 6k8X0ZKojo3bzK5OvVoYSvl1xP31MpFUyH4sT8pwAAQ6jngLtMas6+zyxtoF4NFBwJBs O+1+Xnq5zTTdCJlmh3m08QdIriQf5HClicxDBE8q0iOXfyDCL8CEy4Hi1S32F5Drvk3b mYxkvsMg+pteRMWr4tK3WrZ2Uf7QsXE3RceIGN83GPERWvmx219Pd/jAMa+HrsWjtUTP b7Gw==
X-Gm-Message-State: AIVw112rNW12Y6lFVjvQO5IaL6MJfyVkR1kn4sXRcgfT0k1dYRtRq95S 1VRN4wqmbtwTyCJu
X-Received: by 10.99.133.73 with SMTP id u70mr2481442pgd.235.1501118371808; Wed, 26 Jul 2017 18:19:31 -0700 (PDT)
Received: from ?IPv6:2406:e007:4a2d:1:28cc:dc4c:9703:6781? ([2406:e007:4a2d:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id e5sm36404499pfd.41.2017.07.26.18.19.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Jul 2017 18:19:31 -0700 (PDT)
Subject: Re: the web site re-design
To: Lyndon Nerenberg <lyndon@orthanc.ca>
Cc: ietf@ietf.org
References: <CA404037-1A8E-486D-9D8C-FED25427688E@orthanc.ca> <5f979518-4abf-dddf-a7f7-67cd1350a1e0@gmail.com> <CCB50FC9-75E2-4229-9265-7FC53635D373@orthanc.ca>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <55010f7f-15c5-eb62-87e7-5db241db70d6@gmail.com>
Date: Thu, 27 Jul 2017 13:19:35 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CCB50FC9-75E2-4229-9265-7FC53635D373@orthanc.ca>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/n0lODsOYvAuuteac8IIxdZZOwxw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 01:19:34 -0000

I'm sure Russ will respond but I found this with 2 clicks:

https://iaoc.ietf.org/projects.html

Regards
   Brian

On 27/07/2017 13:13, Lyndon Nerenberg wrote:
>  done a long time ago. (Not an I-D, but a requirements document, which
>> I'm sure can still be found somewhere). beta.ietf.org is output from that process.
> 
> If that exists, can we have it linked to prominently on the beta site's home page?  And have the document's status clarified?
> 
> --lyndon
> 
> 
> 


From nobody Wed Jul 26 18:29:00 2017
Return-Path: <lyndon@orthanc.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C653F131F35 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 18:28:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 lqfSN_OQ2pub for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 18:28:57 -0700 (PDT)
Received: from orthanc.ca (orthanc.ca [IPv6:2607:f2f8:abf8::2]) (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 91619131F34 for <ietf@ietf.org>; Wed, 26 Jul 2017 18:28:57 -0700 (PDT)
Received: from minnie.hitronhub.home (S0106a84e3f81a003.vc.shawcable.net [24.80.126.119]) (authenticated bits=0) by orthanc.ca (8.15.2/8.15.2) with ESMTPSA id v6R1StLH046811 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 26 Jul 2017 18:28:56 -0700 (PDT) (envelope-from lyndon@orthanc.ca)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: the web site re-design
From: Lyndon Nerenberg <lyndon@orthanc.ca>
In-Reply-To: <55010f7f-15c5-eb62-87e7-5db241db70d6@gmail.com>
Date: Wed, 26 Jul 2017 18:28:50 -0700
Cc: ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <3994B7B4-86A0-4CAE-BB30-1EBFC2BAADDF@orthanc.ca>
References: <CA404037-1A8E-486D-9D8C-FED25427688E@orthanc.ca> <5f979518-4abf-dddf-a7f7-67cd1350a1e0@gmail.com> <CCB50FC9-75E2-4229-9265-7FC53635D373@orthanc.ca> <55010f7f-15c5-eb62-87e7-5db241db70d6@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fwtgT1N6DfVygR8Bnc91pmR36_0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 01:28:59 -0000

> On Jul 26, 2017, at 6:19 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>=20
> I'm sure Russ will respond but I found this with 2 clicks:

My DuckDuckGo fu fails.  The "Scope of Work" and "User Research" links =
have a lot of good information behind them, and should be made very =
prominent on the beta site.

--lyndon


From nobody Wed Jul 26 20:09:34 2017
Return-Path: <denisbider.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 286F3124BE8; Wed, 26 Jul 2017 20:09:23 -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 LHPVzlwvB3KU; Wed, 26 Jul 2017 20:09:21 -0700 (PDT)
Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002: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 D88B112711E; Wed, 26 Jul 2017 20:09:20 -0700 (PDT)
Received: by mail-yw0-x236.google.com with SMTP id l82so40769043ywc.2; Wed, 26 Jul 2017 20:09:20 -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=i4nqD/Hf0VXTis24YtlGqh9ZwQrKatGgfP76M7+ubo8=; b=OFc8Gr3QMEh1O7S1U9YvTFLrGNmDS7Cn1npOEEd+cULR+oljssLULCsrHibb7+G4Bv YxSyTlf1PICfwDdGvQwOJ9SlYCaq6/caVbnCPVsstVEq0q+Ks923D/a9UO89hDl1vHp8 7CN0F/bGfJvYZPBSoF3LkEZTklotGbkiqxOK90u2XFoZegIWWJi2BMdkfoNHa2YlT2Tp Ifp39PMxweT9zeIomP6zLGk9g5yp+joW/QChQno67MJxBaJvjHqkEObesMKGltWBzc30 6dtonJ6ibOx5CwPzx7lUcdVxFKVi74gPe76OlwvIVilY4PKr1s1Wf9aKv30RVlWcAffl jX4g==
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=i4nqD/Hf0VXTis24YtlGqh9ZwQrKatGgfP76M7+ubo8=; b=Fmyv8HQsZtFxKsstghdhIuYjKGeDaqbhhM3YFz0N7EH4N3Y//Nm+fMXya7Zn0Bovw/ aVPSLZdnEWpzxtJkO0kypIdyrC1j/cUVnKqWs/+qk7FRY0nlHhxoLR1OiFCeyJUGYF1m MbR7WUvmHpP1btznAZ1zkrufuwggmgW3W3gl+K1prKg9xXWinp+AFi9rE/H5Czr6Rvv6 DGjiUGK4vZgYkTfjvpijPouBnTdB4KmbXRy3Xq08wL4X2wOPSjrn1wLAWWrGd0GYsJID mFi6L7weQseHPvG9NTMSCeDlOxFDX9obl3qmyzbTAdxYA3UuqMwAG0mnJnOraGiFUCBw Dq8Q==
X-Gm-Message-State: AIVw1121EUqVwGIjnTJ56dr+Em1RSlT/vXklngzLZFCT9PiepaMeawXf Ps4KGKoDKYjI5MG9dT8ye7p5erYpQA==
X-Received: by 10.37.0.195 with SMTP id 186mr2578406yba.46.1501124960090; Wed, 26 Jul 2017 20:09:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.42.200 with HTTP; Wed, 26 Jul 2017 20:09:19 -0700 (PDT)
In-Reply-To: <1eef6165-9b5b-c354-dffe-5df1e98098fa@outer-planes.net>
References: <150093015937.32021.12465797358778837950@ietfa.amsl.com> <CADPMZDCE+m+_QA7s6vdFOw-7uF4cfV4g8_U07fb-Ydur30OR5g@mail.gmail.com> <1eef6165-9b5b-c354-dffe-5df1e98098fa@outer-planes.net>
From: denis bider <denisbider.ietf@gmail.com>
Date: Wed, 26 Jul 2017 21:09:19 -0600
Message-ID: <CADPMZDDjQoHc9yoYb7sSTa2r7e71DSMdqQ7OEH7neWU0ygKzNw@mail.gmail.com>
Subject: Re: [Curdle] Genart last call review of draft-ietf-curdle-ssh-ext-info-10
To: "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>
Cc: gen-art@ietf.org, curdle <curdle@ietf.org>, ietf@ietf.org,  draft-ietf-curdle-ssh-ext-info.all@ietf.org
Content-Type: multipart/alternative; boundary="001a113cf650028e01055543e495"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5uFUjtqg4qs_TkdCVxvIuI6pAmM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 03:09:23 -0000

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

Hello Matthew,

I'm not sure if I know how to address this better than with the language so
far proposed.

Perhaps one choice would be to simply remove this paragraph. However, the
reason it was added was because an earlier reviewer (I'm not sure of the
details at this time) raised the question about whether extension
negotiation works like it does for algorithm lists, such as in e.g.
SSH_MSG_KEXINIT. In that case, multiple algorithms are enumerated by both
sides, and only one is chosen that (1) is enumerated by both sides, and (2)
is the first of those to be enumerated by the client. The main purpose of
this paragraph has been to clarify that extension negotiation does not work
that way in EXT_INFO.

What language would you propose? Is there some simple language that would
do? How about this?

"An extension may dictate, where it is specified, that in order to take
effect, both parties must include it in its EXT_INFO; or it may be
sufficient that only one party does; or more complex rules may be
specified."


On Wed, Jul 26, 2017 at 1:28 PM, Matthew A. Miller <
linuxwolf+ietf@outer-planes.net> wrote:

> Thanks very much for the response, Denis.
>
> I think I understand the intent here, but I'm not sure this new text is
> enough to mitigate some future conflict.  I'm also concerned that it
> completely ignores the one-party extensions (e.g., an extension included
> in the EXT_INFO by only the client or the server, but not both), and
> what the impact is holistically.  Looking at the one-party extensions
> defined herein, I can't see how their order matters; but does that mean
> the order will never matter?
>
> In writing this reply, I wondered if it's better for the order to always
> be irrelevant; an implementation might be allowed to hint its preferred
> order in the EXT_INFO, but implementations are still free to do whatever
> makes sense to them within the bounds of the relevant extension
> definitions.  If an extension ought to take precedence over another,
> make it clear in its specification that it SHOULD (or MUST) be dealt
> with before (or after) others.
>
> Does that make sense?
>
>
> - m&m
>
> Matthew A. Miller
>
> On 17/07/25 16:24, denis bider wrote:
> > Good catch. I believe this refers to the following paragraph:
> >
> > "If an extension requires both the client and the server to include it
> > in order for the extension to take effect, the relative position of the
> > extension-name in each EXT_INFO message is irrelevant."
> >
> > I have drafted the following new wording:
> >
> > "Unless a particular extension's specification indicates differently;
> > then, if an extension requires both the client and the server to include
> > it in order for the extension to take effect; implementers MUST use a
> > default assumption that the relative position of the extension-name in
> > each EXT_INFO message is irrelevant with respect to whether the
> > extension takes effect."
> >
> > The purpose of this wording is to:
> >
> > - Provide a sensible default, which is that in the absence of specific
> > knowledge, order of extension names does not matter.
> >
> > - Allow for deviations in special cases where there is specific
> knowledge.
> >
> > For example, extension "foo-linux" could be specified, but after some
> > years of use, it's observed that it works well for its main purpose, but
> > is not ideal for a server on Windows. Therefore, extension "foo-windows"
> > is specified, which works well when the server is Windows, but not as
> > well when it's Linux.
> >
> > In this case, an implementation that supports "foo-linux" only would be
> > ignorant of anything else, and would use the default rule (order of
> > extension names does not matter). However, an implementation that
> > supports "foo-windows" could implement only that, or both "foo-linux"
> > and "foo-windows". The specification for "foo-windows" could indicate
> > that when both are supported, the first one listed by the server (or in
> > other cases, by the client) is used.
> >
> > Allowing for such an extension-defined special case would allow a Linux
> > server to advertise extensions [... "foo-linux", ..., "foo-windows",
> > ...], preferring "foo-linux", but supporting the less appropriate
> > "foo-windows" mechanism as well. Whereas, a Windows server could
> > advertise [... "foo-windows", ..., "foo-linux", ...], preferring
> > "foo-windows", but supporting the less appropriate "foo-linux" mechanism
> > as well.
> >
> > Does this work?
> >
> > If there are no objections, I'll upload a -11 draft version with this
> > new wording.
> >
> >
> >
> > On Mon, Jul 24, 2017 at 3:02 PM, Matthew Miller
> > <linuxwolf+ietf@outer-planes.net
> > <mailto:linuxwolf+ietf@outer-planes.net>> wrote:
> >
> >     Reviewer: Matthew Miller
> >     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
> >     <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>>.
> >
> >     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
> >
> >     Summary:
> >
> >     This document is ready with an issue.
> >
> >     I found this document very coherent and easy to follow.
> >
> >     Major issues:
> >
> >     Minor issues:
> >
> >     My only issue borders on nit, but sided with nit as I can see it
> >     potentially causing confusion for an implementer in the future.
> >
> >     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.
> >
> >     Nits/editorial comments:
> >
> >     * RFC 5226 is referenced by this document, but is obsoleted by RFC
> 8126.
> >
> >
> >     _______________________________________________
> >     Curdle mailing list
> >     Curdle@ietf.org <mailto:Curdle@ietf.org>
> >     https://www.ietf.org/mailman/listinfo/curdle
> >     <https://www.ietf.org/mailman/listinfo/curdle>
> >
> >
>
>

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

<div dir=3D"ltr">Hello Matthew,<div><br></div><div>I&#39;m not sure if I kn=
ow how to address this better than with the language so far proposed.</div>=
<div><br></div><div>Perhaps one choice would be to simply remove this parag=
raph. However, the reason it was added was because an earlier reviewer (I&#=
39;m not sure of the details at this time) raised the question about whethe=
r extension negotiation works like it does for algorithm lists, such as in =
e.g. SSH_MSG_KEXINIT. In that case, multiple algorithms are enumerated by b=
oth sides, and only one is chosen that (1) is enumerated by both sides, and=
 (2) is the first of those to be enumerated by the client. The main purpose=
 of this paragraph has been to clarify that extension negotiation does not =
work that way in EXT_INFO.</div><div><br></div><div>What language would you=
 propose? Is there some simple language that would do? How about this?</div=
><div><br></div><div>&quot;An extension may dictate, where it is specified,=
 that in order to take effect, both parties must include it in its EXT_INFO=
; or it may be sufficient that only one party does; or more complex rules m=
ay be specified.&quot;</div><div><br></div></div><div class=3D"gmail_extra"=
><br><div class=3D"gmail_quote">On Wed, Jul 26, 2017 at 1:28 PM, Matthew A.=
 Miller <span dir=3D"ltr">&lt;<a href=3D"mailto:linuxwolf+ietf@outer-planes=
.net" target=3D"_blank">linuxwolf+ietf@outer-planes.net</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">Thanks very much for the response, Den=
is.<br>
<br>
I think I understand the intent here, but I&#39;m not sure this new text is=
<br>
enough to mitigate some future conflict.=C2=A0 I&#39;m also concerned that =
it<br>
completely ignores the one-party extensions (e.g., an extension included<br=
>
in the EXT_INFO by only the client or the server, but not both), and<br>
what the impact is holistically.=C2=A0 Looking at the one-party extensions<=
br>
defined herein, I can&#39;t see how their order matters; but does that mean=
<br>
the order will never matter?<br>
<br>
In writing this reply, I wondered if it&#39;s better for the order to alway=
s<br>
be irrelevant; an implementation might be allowed to hint its preferred<br>
order in the EXT_INFO, but implementations are still free to do whatever<br=
>
makes sense to them within the bounds of the relevant extension<br>
definitions.=C2=A0 If an extension ought to take precedence over another,<b=
r>
make it clear in its specification that it SHOULD (or MUST) be dealt<br>
with before (or after) others.<br>
<br>
Does that make sense?<br>
<br>
<br>
- m&amp;m<br>
<br>
Matthew A. Miller<br>
<div><div class=3D"h5"><br>
On 17/07/25 16:24, denis bider wrote:<br>
&gt; Good catch. I believe this refers to the following paragraph:<br>
&gt;<br>
&gt; &quot;If an extension requires both the client and the server to inclu=
de it<br>
&gt; in order for the extension to take effect, the relative position of th=
e<br>
&gt; extension-name in each EXT_INFO message is irrelevant.&quot;<br>
&gt;<br>
&gt; I have drafted the following new wording:<br>
&gt;<br>
&gt; &quot;Unless a particular extension&#39;s specification indicates diff=
erently;<br>
&gt; then, if an extension requires both the client and the server to inclu=
de<br>
&gt; it in order for the extension to take effect; implementers MUST use a<=
br>
&gt; default assumption that the relative position of the extension-name in=
<br>
&gt; each EXT_INFO message is irrelevant with respect to whether the<br>
&gt; extension takes effect.&quot;<br>
&gt;<br>
&gt; The purpose of this wording is to:<br>
&gt;<br>
&gt; - Provide a sensible default, which is that in the absence of specific=
<br>
&gt; knowledge, order of extension names does not matter.<br>
&gt;<br>
&gt; - Allow for deviations in special cases where there is specific knowle=
dge.<br>
&gt;<br>
&gt; For example, extension &quot;foo-linux&quot; could be specified, but a=
fter some<br>
&gt; years of use, it&#39;s observed that it works well for its main purpos=
e, but<br>
&gt; is not ideal for a server on Windows. Therefore, extension &quot;foo-w=
indows&quot;<br>
&gt; is specified, which works well when the server is Windows, but not as<=
br>
&gt; well when it&#39;s Linux.<br>
&gt;<br>
&gt; In this case, an implementation that supports &quot;foo-linux&quot; on=
ly would be<br>
&gt; ignorant of anything else, and would use the default rule (order of<br=
>
&gt; extension names does not matter). However, an implementation that<br>
&gt; supports &quot;foo-windows&quot; could implement only that, or both &q=
uot;foo-linux&quot;<br>
&gt; and &quot;foo-windows&quot;. The specification for &quot;foo-windows&q=
uot; could indicate<br>
&gt; that when both are supported, the first one listed by the server (or i=
n<br>
&gt; other cases, by the client) is used.<br>
&gt;<br>
&gt; Allowing for such an extension-defined special case would allow a Linu=
x<br>
&gt; server to advertise extensions [... &quot;foo-linux&quot;, ..., &quot;=
foo-windows&quot;,<br>
&gt; ...], preferring &quot;foo-linux&quot;, but supporting the less approp=
riate<br>
&gt; &quot;foo-windows&quot; mechanism as well. Whereas, a Windows server c=
ould<br>
&gt; advertise [... &quot;foo-windows&quot;, ..., &quot;foo-linux&quot;, ..=
.], preferring<br>
&gt; &quot;foo-windows&quot;, but supporting the less appropriate &quot;foo=
-linux&quot; mechanism<br>
&gt; as well.<br>
&gt;<br>
&gt; Does this work?<br>
&gt;<br>
&gt; If there are no objections, I&#39;ll upload a -11 draft version with t=
his<br>
&gt; new wording.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; On Mon, Jul 24, 2017 at 3:02 PM, Matthew Miller<br>
&gt; &lt;<a href=3D"mailto:linuxwolf%2Bietf@outer-planes.net">linuxwolf+iet=
f@outer-planes.<wbr>net</a><br>
</div></div><div><div class=3D"h5">&gt; &lt;mailto:<a href=3D"mailto:linuxw=
olf%2Bietf@outer-planes.net">linuxwolf+ietf@outer-<wbr>planes.net</a>&gt;&g=
t; wrote:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Reviewer: Matthew Miller<br>
&gt;=C2=A0 =C2=A0 =C2=A0Review result: Ready with Issues<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0I am the assigned Gen-ART reviewer for this draft. =
The General Area<br>
&gt;=C2=A0 =C2=A0 =C2=A0Review Team (Gen-ART) reviews all IETF documents be=
ing processed<br>
&gt;=C2=A0 =C2=A0 =C2=A0by the IESG for the IETF Chair.=C2=A0 Please treat =
these comments just<br>
&gt;=C2=A0 =C2=A0 =C2=A0like any other last call comments.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0For more information, please see the FAQ at<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/=
GenArtfaq" rel=3D"noreferrer" target=3D"_blank">https://trac.ietf.org/trac/=
<wbr>gen/wiki/GenArtfaq</a><br>
&gt;=C2=A0 =C2=A0 =C2=A0&lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/=
GenArtfaq" rel=3D"noreferrer" target=3D"_blank">https://trac.ietf.org/trac/=
<wbr>gen/wiki/GenArtfaq</a>&gt;&gt;.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Document: draft-ietf-curdle-ssh-ext-<wbr>info-10<br=
>
&gt;=C2=A0 =C2=A0 =C2=A0Reviewer: Matthew Miller<br>
&gt;=C2=A0 =C2=A0 =C2=A0Review Date: 2017-07-24<br>
&gt;=C2=A0 =C2=A0 =C2=A0IETF LC End Date: 2017-07-30<br>
&gt;=C2=A0 =C2=A0 =C2=A0IESG Telechat date: N/A<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Summary:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0This document is ready with an issue.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0I found this document very coherent and easy to fol=
low.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Major issues:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Minor issues:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0My only issue borders on nit, but sided with nit as=
 I can see it<br>
&gt;=C2=A0 =C2=A0 =C2=A0potentially causing confusion for an implementer in=
 the future.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Section 2.5. &quot;Interpretation of Extension Name=
s and Values&quot; explicitly<br>
&gt;=C2=A0 =C2=A0 =C2=A0states in the second paragraph a condition where th=
e relative order of<br>
&gt;=C2=A0 =C2=A0 =C2=A0extension-names in an EXT_INFO message is irrelevan=
t.=C2=A0 However, the rest<br>
&gt;=C2=A0 =C2=A0 =C2=A0of the section seems to imply to me that relative o=
rder is not<br>
&gt;=C2=A0 =C2=A0 =C2=A0important;<br>
&gt;=C2=A0 =C2=A0 =C2=A0so to explicitly call out a scenario seems to imply=
 that relative order<br>
&gt;=C2=A0 =C2=A0 =C2=A0*is* relevant/important, sometimes.=C2=A0 If relati=
ve order is expected to be<br>
&gt;=C2=A0 =C2=A0 =C2=A0important most of the time, I think it helpful to e=
xplicitly state that<br>
&gt;=C2=A0 =C2=A0 =C2=A0and give a rationale for it.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Nits/editorial comments:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0* RFC 5226 is referenced by this document, but is o=
bsoleted by RFC 8126.<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0______________________________<wbr>________________=
_<br>
&gt;=C2=A0 =C2=A0 =C2=A0Curdle mailing list<br>
</div></div>&gt;=C2=A0 =C2=A0 =C2=A0<a href=3D"mailto:Curdle@ietf.org">Curd=
le@ietf.org</a> &lt;mailto:<a href=3D"mailto:Curdle@ietf.org">Curdle@ietf.o=
rg</a>&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0<a href=3D"https://www.ietf.org/mailman/listinfo/cu=
rdle" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<wb=
r>listinfo/curdle</a><br>
&gt;=C2=A0 =C2=A0 =C2=A0&lt;<a href=3D"https://www.ietf.org/mailman/listinf=
o/curdle" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman=
/<wbr>listinfo/curdle</a>&gt;<br>
&gt;<br>
&gt;<br>
<br>
</blockquote></div><br></div>

--001a113cf650028e01055543e495--


From nobody Wed Jul 26 20:24:55 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47C04131CA3 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 20:24:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 ZyrFH-GF_kdZ for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 20:24:52 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 32169129ADA for <ietf@ietf.org>; Wed, 26 Jul 2017 20:24:52 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1daZPu-0003tJ-Cb; Thu, 27 Jul 2017 03:24:50 +0000
Date: Thu, 27 Jul 2017 12:24:48 +0900
Message-ID: <m2o9s6lfy7.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Bob Hinden <bob.hinden@gmail.com>
Cc: IETF <ietf@ietf.org>
Subject: Re: Announcement on IETF 100 Hotel Reservations
In-Reply-To: <EF2F4195-A97F-46CB-B2D2-DB7A5E11874F@gmail.com>
References: <150108971740.23120.257371533321943899.idtracker@ietfa.amsl.com> <EF2F4195-A97F-46CB-B2D2-DB7A5E11874F@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/utcrs_C7ZFBHJ66K8SNM0EO0j-k>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 03:24:53 -0000

> I note that there are transit hotels in the airport, this might make
> sense to get some sleep after I arrive.

i have used the changi transit hotels a fair bit.  they're functional.
be sure to visit the butterfly garden!

randy


From nobody Wed Jul 26 20:52:13 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36F08129AA8 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 20:52:11 -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 fDSYqwtx4bK0 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 20:52:09 -0700 (PDT)
Received: from mail-pg0-x242.google.com (mail-pg0-x242.google.com [IPv6:2607:f8b0:400e:c05::242]) (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 4A487124BE8 for <ietf@ietf.org>; Wed, 26 Jul 2017 20:52:09 -0700 (PDT)
Received: by mail-pg0-x242.google.com with SMTP id 123so8602115pgj.0 for <ietf@ietf.org>; Wed, 26 Jul 2017 20:52:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=to:from:subject:organization:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=ZYxsx/e/PH0hdPs8Aellz6O2UmFd4ea5Zqsm6L3AhiU=; b=RS8EbTiGmuNHK8E2VuP2fz1IUUccVu1TUXAjyW0b1PKxAw5cfCRBPRCFsa9TlGzf7t knRWpnT+lMrwBLNLFsHc1Lo30blJMUQ24OEmG6pU03TaYN9yMEO6a024BRVpqeBnVDmi 1HRQAjC8OZeLTWz99XhwADVU7Thbuf+uOkK4QSQiPx2+tvr2yuokQhK9DHACCmN3uGMr 6i0Bbc+FNuuHfP026vV4BmDJdDErUkA0OkBZbhg+0aLW+hYN4+LvWwMlFCGi1NjhqGb3 fLnsquQ95Mr/f3koARxBh74ADzjquOK7MlZpSmb3ZfAmfyr1WkavAGgYYx0/CmgP0RfO CsVA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:organization:message-id:date :user-agent:mime-version:content-language:content-transfer-encoding; bh=ZYxsx/e/PH0hdPs8Aellz6O2UmFd4ea5Zqsm6L3AhiU=; b=FlsQLBMo17qkFQZziahpqPH5isQ7abwfyos/g0ueZZTGnKAt+bFLQ7ttLA+BGjYxXU oGFyyfscqcYl7uCzgOjBV2x7BPFtbMVVktPGYT1NPiZCjdJlWj/L0lFnooUqJgHWTUOj 9RW9TDh+7hswWDldPJfNdG3NLjjo0GEKZKgP5PK4SHAiocEw49Jq24LKf7zvabPLZ+It fsSPsevyNpTE54cwRbFiOqLxTJ6v3BgnG9925XX3NB6AolDKGXlSEWyMuswMRMmqnEOI qptvN5YXFplfcH8r627GdgXRL7xP+22U42MpCLQOyXvdwJ66iY1R1fYVMgA4t3aNdBSd PZqA==
X-Gm-Message-State: AIVw112hk4giwqJOFgfMqBiyMIIeirXZPr6dK6AGhOKFtMA3sYGknAkv XUEDeyaz1CnL9OE0
X-Received: by 10.98.97.66 with SMTP id v63mr2836700pfb.230.1501127528498; Wed, 26 Jul 2017 20:52:08 -0700 (PDT)
Received: from ?IPv6:2406:e007:4a2d:1:28cc:dc4c:9703:6781? ([2406:e007:4a2d:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id z15sm31844672pfl.125.2017.07.26.20.52.07 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Jul 2017 20:52:08 -0700 (PDT)
To: IETF discussion list <ietf@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Visiting Singapore/Customs Clearance
Organization: University of Auckland
Message-ID: <73ae5759-32a7-38fb-3232-9630a4dd6faa@gmail.com>
Date: Thu, 27 Jul 2017 15:52:11 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MbonYxDHJh9QcXLAcAoWoAvByRQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 03:52:11 -0000

https://www.ica.gov.sg/page.aspx?pageid=98 says:

Controlled Goods
The items listed below require an import license or authorization from the relevant controlling authorities for their entry into Singapore.
...
Pre-recorded cartridges and cassettes
Newspapers, books and magazines
Films, video tapes/discs, laser discs
CD-ROM and video games
...

Good to see they have deployed https, but does that restriction cover
items for personal use? I have this strange habit of bringing a book
to read on a long flight.

    Brian


From nobody Wed Jul 26 21:16:04 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1801E1267BB for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 21:16:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Du5nJx9bayNI for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 21:16:02 -0700 (PDT)
Received: from miucha.iecc.com (w6.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3C51124BE8 for <ietf@ietf.org>; Wed, 26 Jul 2017 21:16:01 -0700 (PDT)
Received: (qmail 16621 invoked from network); 27 Jul 2017 04:16:00 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 27 Jul 2017 04:16:00 -0000
Date: 27 Jul 2017 04:15:38 -0000
Message-ID: <20170727041538.1279.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: IETF 100 hotel rate cheat sheet
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zq0kxfATdy67X5WFzPHAYrueEAk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 04:16:03 -0000

For those of us who care about hotel rates, here's what I found by
some pointing and clicking.  The rates are SGD per night, not
including tax and such.  Prepaid rates are non-refundable, although I
expect you could sell the room to someone else.

Same building as the conference:

Swissotel  290, breakfast 40 extra (wow)
Fairmont   320, breakfast 30 extra

Other places

Carlson    245
Grand Pacific 155 prepaid, 175 prepaid w/ breakfast, 200 normal
Grand Park 255
Novotel 215 prepaid w/ breakfast, 218 normal w/o breakfast
Peninsula Excelsior 180 w/ breakfast and a cell phone.  One night nonrefundable deposit.

R's,
John


From nobody Wed Jul 26 21:22:57 2017
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9F2F126DD9 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 21:22:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 YEGqg0w6HNVB for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 21:22:54 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (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 2141E124BE8 for <ietf@ietf.org>; Wed, 26 Jul 2017 21:22:54 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 933983493BB; Thu, 27 Jul 2017 04:22:50 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 6ED3616004C; Thu, 27 Jul 2017 04:22:50 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 5A98316006A; Thu, 27 Jul 2017 04:22:50 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id uAnCmrq-PTrr; Thu, 27 Jul 2017 04:22:50 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 0CE8316004C; Thu, 27 Jul 2017 04:22:50 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 52132801AF58; Thu, 27 Jul 2017 14:22:46 +1000 (AEST)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: IETF discussion list <ietf@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <73ae5759-32a7-38fb-3232-9630a4dd6faa@gmail.com>
Subject: Re: Visiting Singapore/Customs Clearance
In-reply-to: Your message of "Thu, 27 Jul 2017 15:52:11 +1200." <73ae5759-32a7-38fb-3232-9630a4dd6faa@gmail.com>
Date: Thu, 27 Jul 2017 14:22:46 +1000
Message-Id: <20170727042246.52132801AF58@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4biJFwKeIV1Zs2pgPXptA41FHPk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 04:22:56 -0000

In message <73ae5759-32a7-38fb-3232-9630a4dd6faa@gmail.com>, Brian E Carpenter 
writes:
> https://www.ica.gov.sg/page.aspx?pageid=98 says:
> 
> Controlled Goods
> The items listed below require an import license or authorization from the re
> levant controlling authorities for their entry into Singapore.
> ...
> Pre-recorded cartridges and cassettes
> Newspapers, books and magazines
> Films, video tapes/discs, laser discs
> CD-ROM and video games
> ...
> 
> Good to see they have deployed https, but does that restriction cover
> items for personal use? I have this strange habit of bringing a book
> to read on a long flight.
> 
>     Brian

I would be more worried about

	Telecommunication and radio communication equipments 

as it covers mobile phones, laptops, etc.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Wed Jul 26 22:26:22 2017
Return-Path: <gem@rellim.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B22C126BFD for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 22:26:21 -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, RP_MATCHES_RCVD=-0.001, 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=rellim.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 OWmp4DNV86vA for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 22:26:19 -0700 (PDT)
Received: from spidey.rellim.com (rellim.com [IPv6:2001:470:e815::19]) (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 564DA126557 for <ietf@ietf.org>; Wed, 26 Jul 2017 22:26:19 -0700 (PDT)
Received: from spidey.rellim.com (rellim.com [IPv6:2001:470:e815:0:0:0:0:19]) (authenticated bits=0) by spidey.rellim.com (8.15.2/8.15.2) with ESMTPSA id v6R5QDHS022353 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <ietf@ietf.org>; Wed, 26 Jul 2017 22:26:18 -0700
DKIM-Filter: OpenDKIM Filter v2.10.3 spidey.rellim.com v6R5QDHS022353
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=rellim.com; s=kong; t=1501133178; bh=jSTQttTrXYix+rEK4riYf3lxswz30cJITg803uNyhJs=; h=Date:From:To:Subject:In-Reply-To:References; b=o2/wkE2WwKqyiAEsPhrPfWsnu6fz9SqBioo3Fdh/Vi5xH2oNm53JumOmFQgIppcHs fXgOkVotAUCzZ/HTwlnnJtD7AhBWZMGRRvF8fsJDB1dcgUUxQjzpCFBPiqPUCzuMFG rRkoDXZFPPWUH1VxW9X00Fvh5ligvQAHd5n7kkrk=
Date: Wed, 26 Jul 2017 22:26:02 -0700
From: "Gary E. Miller" <gem@rellim.com>
To: IETF discussion list <ietf@ietf.org>
Subject: Re: Visiting Singapore/Customs Clearance
Message-ID: <20170726222602.72dc27ab@spidey.rellim.com>
In-Reply-To: <73ae5759-32a7-38fb-3232-9630a4dd6faa@gmail.com>
References: <73ae5759-32a7-38fb-3232-9630a4dd6faa@gmail.com>
Organization: Rellim
X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/2fGRe=QatLq+X0D8PQnQuK1"; protocol="application/pgp-signature"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (spidey.rellim.com [IPv6:2001:470:e815:0:0:0:0:19]); Wed, 26 Jul 2017 22:26:18 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CjTLUvBt2disfC53UzVog5Jaoto>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 05:26:21 -0000

--Sig_/2fGRe=QatLq+X0D8PQnQuK1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Yo Brian!

On Thu, 27 Jul 2017 15:52:11 +1200
Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:

> https://www.ica.gov.sg/page.aspx?pageid=3D98 says:
...
> Good to see they have deployed https, but does that restriction cover
> items for personal use? I have this strange habit of bringing a book
> to read on a long flight.

I've cleared customs in Singapore dozens of times.  They are pretty laid
back about the normal things travelers carry.  I fear USA customs much
more.

But they are NOT laid back about drugs.  Do not carry any but the most
benign of OTC drugs, unless they are in a proper prescription bottle.

30 grams of morphine will get you a death sentence.  Usually just
90 days after you are caught.

I'd also leave the weapons at home.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
	gem@rellim.com  Tel:+1 541 382 8588

	    Veritas liberabit vos. -- Quid est veritas?
    "If you can=E2=80=99t measure it, you can=E2=80=99t improve it." - Lord=
 Kelvin

--Sig_/2fGRe=QatLq+X0D8PQnQuK1
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEENqCjEoytAEAuFCk8DQ7ZSUHRedgFAll5eWoACgkQDQ7ZSUHR
edib+wf+NW6DrQGWcMMD5/BDK9bE7oE+4BJ3C9Ji1e2wFGjDSBW1UAechctlPOot
9wBe89IthDr23fK9wR3bIvi9jkF5V0QoJaO6h9AR1RCInVDjJeEMf9//FDwrpS2K
NeXBoTnLs/r+2ukc0/FclTBO7yyPHr+aBF2U3rxXEJKe2nJAgU8t7qWd27Z66u5+
7DShx3NEE1yNRGQrbGcfRucstsGCXGil94QmAH6BURplbnKQtKB9ihLtmpGmQabg
vXhmIgwj8UsU24+Raj45d7hjA1uV96zL/ykZMby7ivPRM3S64ez+fBR4Akxmqfja
J7T1arr0vv3u5j6YEtW1tjdDVmwZYA==
=HJxu
-----END PGP SIGNATURE-----

--Sig_/2fGRe=QatLq+X0D8PQnQuK1--


From nobody Wed Jul 26 23:36:52 2017
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06A03132032 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 23:36:49 -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 K4pJfNLrk7X4 for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 23:36:47 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 9AAC0120227 for <ietf@ietf.org>; Wed, 26 Jul 2017 23:36:42 -0700 (PDT)
X-AuditID: c1b4fb3a-803ff70000001b2f-a9-597989f86182
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 79.69.06959.8F989795; Thu, 27 Jul 2017 08:36:40 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.91]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0352.000; Thu, 27 Jul 2017 08:36:40 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Gary E. Miller" <gem@rellim.com>
CC: IETF discussion list <ietf@ietf.org>
Subject: Re: Visiting Singapore/Customs Clearance
Thread-Topic: Visiting Singapore/Customs Clearance
Thread-Index: AQHTBovE9l4DbXvT9U6nPc+ZbnYbF6JnAw0AgAATugA=
Date: Thu, 27 Jul 2017 06:36:39 +0000
Message-ID: <7DC36587-F486-4A1F-A860-056D1A4262D0@ericsson.com>
References: <73ae5759-32a7-38fb-3232-9630a4dd6faa@gmail.com> <20170726222602.72dc27ab@spidey.rellim.com>
In-Reply-To: <20170726222602.72dc27ab@spidey.rellim.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Content-Type: multipart/signed; boundary="Apple-Mail-02D571D2-732B-4604-8618-908DFD57A576"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrIIsWRmVeSWpSXmKPExsUyM2K7qO6PzspIg90vDS3ev1zGbvFs43wW ByaPJUt+MnkseLSBKYApissmJTUnsyy1SN8ugStj8twdjAW/sioeLuphaWB8kd7FyMkhIWAi cfnVf/YuRi4OIYEjjBLbV/SxgySEBBYzSizfVdXFyMHBJmAh0f1PGyQsIqAqsfTOCyYQm1lA Q6Lv7Ec2EFtYwFCi+fJERogaI4lZFy4yQdhWEke6GllAbBag3n9fj4DV8wrYSyx91MoEsSpL ordvIlgNJ9CqpfN6weKMAmIS30+tgdolLnHryXwmiJtFJB5ePM0GYYtKvHz8jxXkfmaByYwS S04/ZIZYIChxcuYTlgmMwrOQ9M9CVjcLSR1EUbzE7EknmCBseYntb+cwQ9iaEvu7l0PVKEpM 6X7IPgsaAJ3fJrJiiltLzPh1kA3CNpV4ffQjI7KaBYw8qxhFi1OLi3PTjYz0Uosyk4uL8/P0 8lJLNjECI/fglt9WOxgPPnc8xCjAwajEwzu1tTJSiDWxrLgy9xCjCtCcRxtWX2CUYsnLz0tV EuFlagZK86YkVlalFuXHF5XmpBYfYpTmYFES53XYdyFCSCA9sSQ1OzW1ILUIJsvEwSnVwGgc Zxn1s/OiqfaX1kceZ/dNLk3Ymxr/rvbK9nle3/6wMes3f7/6bUtlyiyzx+LL0v4butyMYjyb ftD03zFWJ59Vs9n/up6brMUeO22JyKd52kr7ri987r1f++62sL/fii5eSn/M9/7P679G0iIS bJW7PNhzPp8RDtjA+PY5zzLPdUkef1dvyPinxFKckWioxVxUnAgAcCoNJ+QCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gN6Ifd5h6uy2I2N8yB2Kj1FK5rU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 06:36:49 -0000

--Apple-Mail-02D571D2-732B-4604-8618-908DFD57A576
Content-Type: multipart/alternative;
	boundary=Apple-Mail-FF382796-6691-472B-BADA-F940DCCCB6A9
Content-Transfer-Encoding: 7bit


--Apple-Mail-FF382796-6691-472B-BADA-F940DCCCB6A9
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: base64

SW4gYWRkaXRpb24gdG8gZ3VucywgdGhlcmUgaXMgYWxzbyBhIGJhbiBvbiBndW1zLg0KDQpodHRw
czovL2VuLm0ud2lraXBlZGlhLm9yZy93aWtpL0NoZXdpbmdfZ3VtX2Jhbl9pbl9TaW5nYXBvcmUN
Cg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0KDQpTZW50IGZyb20gbXkgaVBob25lDQoNCj4gT24g
MjcgSnVsIDIwMTcsIGF0IDguMjYsIEdhcnkgRS4gTWlsbGVyIDxnZW1AcmVsbGltLmNvbT4gd3Jv
dGU6DQo+IA0KPiBZbyBCcmlhbiENCj4gDQo+IE9uIFRodSwgMjcgSnVsIDIwMTcgMTU6NTI6MTEg
KzEyMDANCj4gQnJpYW4gRSBDYXJwZW50ZXIgPGJyaWFuLmUuY2FycGVudGVyQGdtYWlsLmNvbT4g
d3JvdGU6DQo+IA0KPj4gaHR0cHM6Ly93d3cuaWNhLmdvdi5zZy9wYWdlLmFzcHg/cGFnZWlkPTk4
IHNheXM6DQo+IC4uLg0KPj4gR29vZCB0byBzZWUgdGhleSBoYXZlIGRlcGxveWVkIGh0dHBzLCBi
dXQgZG9lcyB0aGF0IHJlc3RyaWN0aW9uIGNvdmVyDQo+PiBpdGVtcyBmb3IgcGVyc29uYWwgdXNl
PyBJIGhhdmUgdGhpcyBzdHJhbmdlIGhhYml0IG9mIGJyaW5naW5nIGEgYm9vaw0KPj4gdG8gcmVh
ZCBvbiBhIGxvbmcgZmxpZ2h0Lg0KPiANCj4gSSd2ZSBjbGVhcmVkIGN1c3RvbXMgaW4gU2luZ2Fw
b3JlIGRvemVucyBvZiB0aW1lcy4gIFRoZXkgYXJlIHByZXR0eSBsYWlkDQo+IGJhY2sgYWJvdXQg
dGhlIG5vcm1hbCB0aGluZ3MgdHJhdmVsZXJzIGNhcnJ5LiAgSSBmZWFyIFVTQSBjdXN0b21zIG11
Y2gNCj4gbW9yZS4NCj4gDQo+IEJ1dCB0aGV5IGFyZSBOT1QgbGFpZCBiYWNrIGFib3V0IGRydWdz
LiAgRG8gbm90IGNhcnJ5IGFueSBidXQgdGhlIG1vc3QNCj4gYmVuaWduIG9mIE9UQyBkcnVncywg
dW5sZXNzIHRoZXkgYXJlIGluIGEgcHJvcGVyIHByZXNjcmlwdGlvbiBib3R0bGUuDQo+IA0KPiAz
MCBncmFtcyBvZiBtb3JwaGluZSB3aWxsIGdldCB5b3UgYSBkZWF0aCBzZW50ZW5jZS4gIFVzdWFs
bHkganVzdA0KPiA5MCBkYXlzIGFmdGVyIHlvdSBhcmUgY2F1Z2h0Lg0KPiANCj4gSSdkIGFsc28g
bGVhdmUgdGhlIHdlYXBvbnMgYXQgaG9tZS4NCj4gDQo+IFJHRFMNCj4gR0FSWQ0KPiAtLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0NCj4gR2FyeSBFLiBNaWxsZXIgUmVsbGltIDEwOSBOVyBXaWxtaW5ndG9uIEF2
ZS4sIFN1aXRlIEUsIEJlbmQsIE9SIDk3NzAzDQo+ICAgIGdlbUByZWxsaW0uY29tICBUZWw6KzEg
NTQxIDM4MiA4NTg4DQo+IA0KPiAgICAgICAgVmVyaXRhcyBsaWJlcmFiaXQgdm9zLiAtLSBRdWlk
IGVzdCB2ZXJpdGFzPw0KPiAgICAiSWYgeW91IGNhbuKAmXQgbWVhc3VyZSBpdCwgeW91IGNhbuKA
mXQgaW1wcm92ZSBpdC4iIC0gTG9yZCBLZWx2aW4NCg==

--Apple-Mail-FF382796-6691-472B-BADA-F940DCCCB6A9
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iY29udGVudC10eXBlIiBjb250ZW50PSJ0ZXh0
L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPjwvaGVhZD48Ym9keSBkaXI9ImF1dG8iPjxkaXY+SW4gYWRk
aXRpb24gdG8gZ3VucywgdGhlcmUgaXMgYWxzbyBhIGJhbiBvbiBndW1zLjwvZGl2PjxkaXYgaWQ9
IkFwcGxlTWFpbFNpZ25hdHVyZSI+PGJyPjwvZGl2PjxkaXYgaWQ9IkFwcGxlTWFpbFNpZ25hdHVy
ZSI+PGEgaHJlZj0iaHR0cHM6Ly9lbi5tLndpa2lwZWRpYS5vcmcvd2lraS9DaGV3aW5nX2d1bV9i
YW5faW5fU2luZ2Fwb3JlIj5odHRwczovL2VuLm0ud2lraXBlZGlhLm9yZy93aWtpL0NoZXdpbmdf
Z3VtX2Jhbl9pbl9TaW5nYXBvcmU8L2E+PC9kaXY+PGRpdiBpZD0iQXBwbGVNYWlsU2lnbmF0dXJl
Ij48YnI+PC9kaXY+PGRpdiBpZD0iQXBwbGVNYWlsU2lnbmF0dXJlIj5SZWdhcmRzLDwvZGl2Pjxk
aXYgaWQ9IkFwcGxlTWFpbFNpZ25hdHVyZSI+PGJyPjwvZGl2PjxkaXYgaWQ9IkFwcGxlTWFpbFNp
Z25hdHVyZSI+Q2hyaXN0ZXI8L2Rpdj48ZGl2IGlkPSJBcHBsZU1haWxTaWduYXR1cmUiPjxicj48
YnI+U2VudCBmcm9tIG15IGlQaG9uZTwvZGl2PjxkaXY+PGJyPk9uIDI3IEp1bCAyMDE3LCBhdCA4
LjI2LCBHYXJ5IEUuIE1pbGxlciAmbHQ7PGEgaHJlZj0ibWFpbHRvOmdlbUByZWxsaW0uY29tIj5n
ZW1AcmVsbGltLmNvbTwvYT4mZ3Q7IHdyb3RlOjxicj48YnI+PC9kaXY+PGJsb2NrcXVvdGUgdHlw
ZT0iY2l0ZSI+PGRpdj48c3Bhbj5ZbyBCcmlhbiE8L3NwYW4+PGJyPjxzcGFuPjwvc3Bhbj48YnI+
PHNwYW4+T24gVGh1LCAyNyBKdWwgMjAxNyAxNTo1MjoxMSArMTIwMDwvc3Bhbj48YnI+PHNwYW4+
QnJpYW4gRSBDYXJwZW50ZXIgJmx0OzxhIGhyZWY9Im1haWx0bzpicmlhbi5lLmNhcnBlbnRlckBn
bWFpbC5jb20iPmJyaWFuLmUuY2FycGVudGVyQGdtYWlsLmNvbTwvYT4mZ3Q7IHdyb3RlOjwvc3Bh
bj48YnI+PHNwYW4+PC9zcGFuPjxicj48YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48c3Bhbj48YSBo
cmVmPSJodHRwczovL3d3dy5pY2EuZ292LnNnL3BhZ2UuYXNweD9wYWdlaWQ9OTgiPmh0dHBzOi8v
d3d3LmljYS5nb3Yuc2cvcGFnZS5hc3B4P3BhZ2VpZD05ODwvYT4gc2F5czo8L3NwYW4+PGJyPjwv
YmxvY2txdW90ZT48c3Bhbj4uLi48L3NwYW4+PGJyPjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPjxz
cGFuPkdvb2QgdG8gc2VlIHRoZXkgaGF2ZSBkZXBsb3llZCBodHRwcywgYnV0IGRvZXMgdGhhdCBy
ZXN0cmljdGlvbiBjb3Zlcjwvc3Bhbj48YnI+PC9ibG9ja3F1b3RlPjxibG9ja3F1b3RlIHR5cGU9
ImNpdGUiPjxzcGFuPml0ZW1zIGZvciBwZXJzb25hbCB1c2U/IEkgaGF2ZSB0aGlzIHN0cmFuZ2Ug
aGFiaXQgb2YgYnJpbmdpbmcgYSBib29rPC9zcGFuPjxicj48L2Jsb2NrcXVvdGU+PGJsb2NrcXVv
dGUgdHlwZT0iY2l0ZSI+PHNwYW4+dG8gcmVhZCBvbiBhIGxvbmcgZmxpZ2h0Ljwvc3Bhbj48YnI+
PC9ibG9ja3F1b3RlPjxzcGFuPjwvc3Bhbj48YnI+PHNwYW4+SSd2ZSBjbGVhcmVkIGN1c3RvbXMg
aW4gU2luZ2Fwb3JlIGRvemVucyBvZiB0aW1lcy4gJm5ic3A7VGhleSBhcmUgcHJldHR5IGxhaWQ8
L3NwYW4+PGJyPjxzcGFuPmJhY2sgYWJvdXQgdGhlIG5vcm1hbCB0aGluZ3MgdHJhdmVsZXJzIGNh
cnJ5LiAmbmJzcDtJIGZlYXIgVVNBIGN1c3RvbXMgbXVjaDwvc3Bhbj48YnI+PHNwYW4+bW9yZS48
L3NwYW4+PGJyPjxzcGFuPjwvc3Bhbj48YnI+PHNwYW4+QnV0IHRoZXkgYXJlIE5PVCBsYWlkIGJh
Y2sgYWJvdXQgZHJ1Z3MuICZuYnNwO0RvIG5vdCBjYXJyeSBhbnkgYnV0IHRoZSBtb3N0PC9zcGFu
Pjxicj48c3Bhbj5iZW5pZ24gb2YgT1RDIGRydWdzLCB1bmxlc3MgdGhleSBhcmUgaW4gYSBwcm9w
ZXIgcHJlc2NyaXB0aW9uIGJvdHRsZS48L3NwYW4+PGJyPjxzcGFuPjwvc3Bhbj48YnI+PHNwYW4+
MzAgZ3JhbXMgb2YgbW9ycGhpbmUgd2lsbCBnZXQgeW91IGEgZGVhdGggc2VudGVuY2UuICZuYnNw
O1VzdWFsbHkganVzdDwvc3Bhbj48YnI+PHNwYW4+OTAgZGF5cyBhZnRlciB5b3UgYXJlIGNhdWdo
dC48L3NwYW4+PGJyPjxzcGFuPjwvc3Bhbj48YnI+PHNwYW4+SSdkIGFsc28gbGVhdmUgdGhlIHdl
YXBvbnMgYXQgaG9tZS48L3NwYW4+PGJyPjxzcGFuPjwvc3Bhbj48YnI+PHNwYW4+UkdEUzwvc3Bh
bj48YnI+PHNwYW4+R0FSWTwvc3Bhbj48YnI+PHNwYW4+LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPC9zcGFu
Pjxicj48c3Bhbj5HYXJ5IEUuIE1pbGxlciBSZWxsaW0gMTA5IE5XIFdpbG1pbmd0b24gQXZlLiwg
U3VpdGUgRSwgQmVuZCwgT1IgOTc3MDM8L3NwYW4+PGJyPjxzcGFuPiAmbmJzcDsgJm5ic3A7PGEg
aHJlZj0ibWFpbHRvOmdlbUByZWxsaW0uY29tIj5nZW1AcmVsbGltLmNvbTwvYT4gJm5ic3A7VGVs
OisxIDU0MSAzODIgODU4ODwvc3Bhbj48YnI+PHNwYW4+PC9zcGFuPjxicj48c3Bhbj4gJm5ic3A7
ICZuYnNwOyAmbmJzcDsmbmJzcDsmbmJzcDtWZXJpdGFzIGxpYmVyYWJpdCB2b3MuIC0tIFF1aWQg
ZXN0IHZlcml0YXM/PC9zcGFuPjxicj48c3Bhbj4gJm5ic3A7Jm5ic3A7Jm5ic3A7IklmIHlvdSBj
YW7igJl0IG1lYXN1cmUgaXQsIHlvdSBjYW7igJl0IGltcHJvdmUgaXQuIiAtIExvcmQgS2Vsdmlu
PC9zcGFuPjxicj48L2Rpdj48L2Jsb2NrcXVvdGU+PC9ib2R5PjwvaHRtbD4=

--Apple-Mail-FF382796-6691-472B-BADA-F940DCCCB6A9--

--Apple-Mail-02D571D2-732B-4604-8618-908DFD57A576
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIR8zCCBTgw
ggMgoAMCAQICEQCVvhag9y5G8Xs5gnL6i82WMA0GCSqGSIb3DQEBBQUAMDcxFDASBgNVBAoMC1Rl
bGlhU29uZXJhMR8wHQYDVQQDDBZUZWxpYVNvbmVyYSBSb290IENBIHYxMB4XDTA3MTAxODEyMDA1
MFoXDTMyMTAxODEyMDA1MFowNzEUMBIGA1UECgwLVGVsaWFTb25lcmExHzAdBgNVBAMMFlRlbGlh
U29uZXJhIFJvb3QgQ0EgdjEwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQDCvusn8CGj
82kmVX6dxVUWkVz97yG/U4B6LdKRjGMx8Owk8MOl0nJ8EG30N7fl5nx56oy1gouuSLasANxldewq
TV/Bh/UgZSuBqEc+iSOVMBaQf+hXB0jnGa6/RWexNxsGKv7e+ax9g/teuuSPl2e+S46NZAdXOFVp
NDY9E0jvT+LTZh6kzxq3XjYz1LQGvRgB/XeEUABF9Yxd6CO8fv414e1Qe6kwjRnTCY5oZ12/PJcY
U7spYsXKXnLBx5bU2y2gtB9pA+zq4lDxDDzwrPNTLfAc9e1sOTlzgBbIUrAjzeA+3N08R6C7NYri
mGiLvuW/cu7S+qXtEu38mBipJnbcKEsQIBzTfxZ3Le1vgPdJu1MFu11ox9TIdRY/iVqL9xdH1Ezx
0ol5Pk09mKhh3joe0vheA+DByRyM041N05U2szdfY2ObMxTwLSZrU3yJjDLCbuw9IQA5yaFo4lCD
LrA6K/M2oKwv5G9hwlEJOT6LU7m7Z9rcU7l2WTadQ+Ug4D0yYIUiUbfHM7vdFS+keKYHe4FGNgSG
3Xk1x5UsO7CjFzXlcx+0XFnv2uoQZXt60H+fs7QqNztwi5tbuSu37LJREpdTKVrU8BIQ3E8CuxKS
L2LUP2lDfA3W/Fh1AYidWBZL3rqQ/0cBiQZq9l+ykGqzAqYCiL+zR34q2dX6aHg1TQIDAQABoz8w
PTAPBgNVHRMBAf8EBTADAQH/MAsGA1UdDwQEAwIBBjAdBgNVHQ4EFgQU8I9ZOACz9Y+algzV6/p7
qhfoExIwDQYJKoZIhvcNAQEFBQADggIBAL7kXGJOJPQMCP/w0wxo5JNJIj9EJ2+7bd6DZs6ozA38
9ZoG5XcUkeudQXuZKoTl//whwV3w5B9Xt3WpoV8CJv/Xx/dO3k/49xxGwHpPQCwiNfAZsdBrZyyw
qODAQDc19oRcXOOvQnj+p8kNUOoNhHb2Ue+DU8Z6/w5WSS6PetYM5idU400KYHJizZEH1qW/yJlr
7cQZ5qtMETjFbzHibknIP3aAJgMmKeA29vYgU+MXcDQXnWNoHmvsw02GuBMwL11GDUdD1RuqWQ65
XI0GSK10h1/H/DFUQRPixyEOnuAeDeHAe0OFkMWKWMZlCnhX8sYjDwHZIEveD/uShXUqXHONbXsl
kcruRa4GSwDM07FZUNo6iDspQ0ZelytUzlNvjUrnlvq/cQ5Ci3z9KKDQSMraxIFMu6JzkybI6wzW
Joi2wCTPu71b63V96QiOhjMseXcJaaWJ/LNwkId2j9Miu0LOvXMLICYq0Js9cB4kbM2HdqkXlrfP
DZL7jhipmEnRnv5gRHIhuRntwvUx8TlIiJAkdVQWrc70+GkUZDn7o7i6cEDHJxy/xFZT+mNl0PMc
Dhb1a4ZYTRjU5A2OpZ1bkdx2JFA/xir72bectdbm0NnoGYsVcUitt+rYWYjUkL8Ws9nprFlhVMgc
usrByuG5IEyPOpOJpaDMv9P2daR1lm1WMIIF+TCCA+GgAwIBAgIQMQ1yPcGTNYDzhYWhrkFQyDAN
BgkqhkiG9w0BAQUFADA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwg
SW5kaXZpZHVhbCBDQSB2MjAeFw0xNDExMDQxMjI4MTlaFw0xNzExMDQxMjI4MThaMG8xETAPBgNV
BAoMCEVyaWNzc29uMRowGAYDVQQDDBFDaHJpc3RlciBIb2xtYmVyZzEtMCsGCSqGSIb3DQEJARYe
Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tMQ8wDQYDVQQFEwZMTUZDSEgwggEiMA0GCSqG
SIb3DQEBAQUAA4IBDwAwggEKAoIBAQCMb7fHWIV9CIFYYov86NR/6ibdVV0I+ZqVLE21zQB7otFv
6DTKlVXE7iiC4HCvMhlGkg3/qFmAhAti5Z1Z7+5eEMEIP5JJEZ7fMm6BME33Bkdgg4EfJrq4FUG2
8Hw2//0qx3jZWvK2W751AmEuUJ5nkZ6F00GnzJmOhbveadC8E5keqwow9ria0/WazHiK3wxzjban
oQaZIA+oCKj5YyCv8cCTaSk4pEAbXwxthJ97BaZPahsnb4EZEP08gxR5IE9NRi47Eqh6LtBjiWpa
B42EmCEBxc2uIQ87tlJ0e2SvCo74rqxndXtUeaWauMjjt4DnhJdiXZY244D5J1gWssRFAgMBAAGj
ggHEMIIBwDBIBgNVHR8EQTA/MD2gO6A5hjdodHRwOi8vY3JsLnRydXN0LnRlbGlhLmNvbS9lcmlj
c3Nvbm5saW5kaXZpZHVhbGNhdjIuY3JsMIGCBggrBgEFBQcBAQR2MHQwKAYIKwYBBQUHMAGGHGh0
dHA6Ly9vY3NwMi50cnVzdC50ZWxpYS5jb20wSAYIKwYBBQUHMAKGPGh0dHA6Ly9jYS50cnVzdC50
ZWxpYXNvbmVyYS5jb20vZXJpY3Nzb25ubGluZGl2aWR1YWxjYXYyLmNlcjApBgNVHREEIjAggR5j
aHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20wVQYDVR0gBE4wTDBKBgwrBgEEAYIPAgMBARIw
OjA4BggrBgEFBQcCARYsaHR0cHM6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNvbS9D
UFMwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMCMB0GA1UdDgQWBBRUo03/DrRAW2xpMmhN
2uGkvDgx6jAfBgNVHSMEGDAWgBSxDcrURrevhgLDL28Gyg52cX9LNzAOBgNVHQ8BAf8EBAMCBaAw
DQYJKoZIhvcNAQEFBQADggIBALbwqG5inhl/xPxsuQWcH7GOUZIPAw0JlKltVQ/TlsF7ig0J1iyz
ao6GsXItJ9H3WZPrCy5EQchJm7qcn2kKX8OGb+Yr53FisLR2gx+qkrQMDOdix9Was0cvIjDWjAQn
EZbxz/a+dzdAP0TrwNvD8282bIy0fCt/3uoBfzMnvQG+4wG018bDunc+NCj1FkSKkSRb9fP2Z2li
65pfJcxtGIfb5zsXJZG4Gtbe0/hxlj3NccjB/zVPO7PQ+lnWmxtOiJQ2loA+62vQreUQr328XK4I
HFnoU+zXiVfUN2urvvirQH7Ha70TBMa20J8Nn2aEvY6QYMEQJhAiVmNTiv4EGGv5heX5vb8yaj7p
r4YIvb6D0r+pwpvfEE8YhAEWJgCZP7k5zQwhrpuSF/s+wEruXo59sq9bOCefghktc5fwDu8ved98
cifRPUnuT/c5slJJ8LjFn8d+LnGklUdFA9kLjIJVVx+TM4D/OTaRG+mPFbY2pTyR0V84PG7HLeku
pNsFzcme7IBkQ+1zkb9hjz6pyiodf6rh7ph+8XHWNgzbC5PdGCANg8fVWrxqqOoEzvcUcPMy6XXJ
s0JWhWas8mJdHq2kGDDEpA7BbBatmtEqziXRnYGJeQK3eMDXXtmOeBSA4y7YZ47y+CxvbknSQ5dy
ghwkEq+a7ORPGVjsjtWJYJ6dMIIGtjCCBJ6gAwIBAgIRAKAMy8ybmZjs4jpw9HzBwFkwDQYJKoZI
hvcNAQEFBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmExHzAdBgNVBAMMFlRlbGlhU29uZXJhIFJv
b3QgQ0EgdjEwHhcNMTQwNTI3MDc0NjIxWhcNMjQwNTI3MDc0NjIxWjA6MREwDwYDVQQKDAhFcmlj
c3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MjCCAiIwDQYJKoZIhvcN
AQEBBQADggIPADCCAgoCggIBANq6U+tfSJZTn4k46qN13HgaeXXsMmGSWShc6A5IEyFboXMZW3lF
Hso+/6uO3ZilvB2ipZJhrhU+RL/va+5Chay/PZq9ZZeE9N03OsHfOzlwk7uwojJ34tHLiX/yQori
I+b5DXxfIYXTFO5zlZLdaIxJwlLEQp0g4/zF6EGtodlpusaH07FAcLiIEeTMPRgXcn+8GoFOvtuV
HNh/WHePlrupUgcI9/P54ITXvmZF6xcNBEjsu8yJm1VqqK0GXSgAmInJ4Ga8S6ME2wgSBRDolxAU
bmfLQRrMvLC/tyXBvuLO8uChdzpIWt3QPtMYm2R2V1Um0zANhenIUwYCKNPq5/yHaS48jCsOBAU0
TIhBnirnZmlEbC6ALqwzGAcQMaMD8LFf1oLlWLUQxEmI4YXqBXdP5XnIcMdIEF5BtUBebzBJMMF9
dDB2uj8BeoRPSYbpGl7irYUYFpq4TyocQ7qpHdYASC+NV8VTaTrFnHWqa/CGRdp3GHpkgxfOBvpa
mOK8udHQYQo2uA3YNd2+j7p4C3jkGG+Z6RrZOskPEwtaIHLxBiA141dhCy5EScOyNajrAXQupsDn
vr2ib2ef+4nObPFvedPWIe57lyj0n3e1rTqTGIBIe9wjNnAA6MqeaTS9HchPtBvOrah/cTWzXzGj
wMz0P3UJqTQ2r5EAu12/W5kpAgMBAAGjggG4MIIBtDCBigYIKwYBBQUHAQEEfjB8MC0GCCsGAQUF
BzABhiFodHRwOi8vb2NzcC50cnVzdC50ZWxpYXNvbmVyYS5jb20wSwYIKwYBBQUHMAKGP2h0dHA6
Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNvbS90ZWxpYXNvbmVyYXJvb3RjYXYxLmNl
cjASBgNVHRMBAf8ECDAGAQH/AgEAMFUGA1UdIAROMEwwSgYMKwYBBAGCDwIDAQECMDowOAYIKwYB
BQUHAgEWLGh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYXNvbmVyYS5jb20vQ1BTMEsGA1Ud
HwREMEIwQKA+oDyGOmh0dHA6Ly9jcmwtMy50cnVzdC50ZWxpYXNvbmVyYS5jb20vdGVsaWFzb25l
cmFyb290Y2F2MS5jcmwwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA4GA1UdDwEB/wQE
AwIBBjAdBgNVHQ4EFgQUsQ3K1Ea3r4YCwy9vBsoOdnF/SzcwHwYDVR0jBBgwFoAU8I9ZOACz9Y+a
lgzV6/p7qhfoExIwDQYJKoZIhvcNAQEFBQADggIBAG4HIGyvrHc9kEKyYZtxJn9cv7S2dUxuUieg
mAvUGHc+JGJyB2jyX7py9an8CsHAxg3BI3Ku9j0h7DJpXyfrlzmg36XYkNS7Ot0A1UqdjGFrtnII
SI+Zj3ywHZudmDF8ktdBihHAjuk47B/Kg/Z8JhUJ37GGx/KxiIiXg5HMTdOl6mlDbJaTIEGagdRc
mH3u57r5snZ+qdVSg5UxWdhgS2+zPru/vDbPd+91zLTj9GejKXFJ6fEAOLW1j2IjJ0cyDI67d1/O
zFTwCK8wYbhopK2wJ9QTKDQuWRuGoyt2d6yzd7WoAS55JE0BIt+kXDJGbOaK42H2ifO6ERHbJiEr
/oh4KzgdAes+GRjwlSaG2Z0va4Ss5lY6zfwVCEZYdZcjSDpKB0M5tTQYQeO7QyQPOI6Gb4FXA9ko
3sHvAPs4+Pq+UtWjp3y8sYr1vLCER9ePEsgLdCG27mUk9OAijkG6n5oEGOIn+70F+qvKpmm52dZ8
b7DELfbuuk0CrY4p0WxH3bBt6FJkPeZJIB6YNXAYHZi7RcdBjLJh+lawbIYTJFIcoWFHAl0g0/NY
sjz3DLhZz4+CrJ6SQSYmp7qDhdJAWPiaq3C+qE/h2DZAJwoz9uHrZHB8zsZ5JL8sUZ7zgqYmNMN+
9PxzasrycTJn96Y63AIZdDq1kIHIw0vF4PBTVMZtMYICljCCApICAQEwTjA6MREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MgIQMQ1yPcGTNYDz
hYWhrkFQyDAJBgUrDgMCGgUAoIIBHTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0xNzA3MjcwNjM2MzhaMCMGCSqGSIb3DQEJBDEWBBR5Az+ljGXoHQq1+LSkG1zFbMUm
ZTBdBgkrBgEEAYI3EAQxUDBOMDoxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQDDBxFcmljc3Nv
biBOTCBJbmRpdmlkdWFsIENBIHYyAhAxDXI9wZM1gPOFhaGuQVDIMF8GCyqGSIb3DQEJEAILMVCg
TjA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBD
QSB2MgIQMQ1yPcGTNYDzhYWhrkFQyDANBgkqhkiG9w0BAQEFAASCAQB2JYlWwrkPvR5XiFj5mwuF
4yecms76H8Ib1kEMMsdqLFfHkJqUJ8EmB/1NYuvJ/sb3dBITga+km/Yrkg9B/CD1C+w3fxN7s3FP
9YEavxSBDSLqR3+vJwqzfwx6ZYUyknH46y80IhCMcJRAEzMy4vA0Kcm3tJh+laFCCysCeHox0ObQ
sFj7FQpE1yAKj9Fl27wl70KZ29q5Ql1QknFc722IhHqjzDCviiLkHSJhx6vuKmzARxSCJ3CHlqP2
080w2DARB3YGidKazY4yIB6PWT/REWYVUMRW+/LkcjTLlBAL342q61DVn2ajCaRTpY6so4H1MN45
BdHpxyRctIznKS0aAAAAAAAA

--Apple-Mail-02D571D2-732B-4604-8618-908DFD57A576--


From nobody Thu Jul 27 02:39:50 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 249DD131FB6 for <ietf@ietfa.amsl.com>; Thu, 27 Jul 2017 02:39:49 -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 0Ee0BaMBttd6 for <ietf@ietfa.amsl.com>; Thu, 27 Jul 2017 02:39:47 -0700 (PDT)
Received: from mail-wr0-x22f.google.com (mail-wr0-x22f.google.com [IPv6:2a00:1450:400c:c0c::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 CA4A81200ED for <ietf@ietf.org>; Thu, 27 Jul 2017 02:39:46 -0700 (PDT)
Received: by mail-wr0-x22f.google.com with SMTP id v105so111059952wrb.0 for <ietf@ietf.org>; Thu, 27 Jul 2017 02:39:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=LIF1IfdUECFEbkkk/NO30p2mLPGrL49OthA79IM6vts=; b=XoaAyhLMYcaVr8YOydCxkRCy+AYjWsYfLxOwa0ZM5AFUxW6F019sk3uNEK4a+EonAC Eck1/bvGH2hc5ckcE4QuAgADlS9sydyHreANOn/JcIaQG1OkVOXdgs90+AD17xylHGAQ 9Axcmqo47QiTLO+R/z6rbc9OXi8R8D9Un7Nof8DnV4WukGILXirGZEtgJiynll4qAVcy j4xhb8nR7anYkX9O1svtr0IRL3met3ZDtB/6Xq38l2FmvPIwLzEZs0aEAtTAes/K15Qq XA5zTFLDCQhRJ0FhlVWkp1Z5ZPtND3+U7IcsJiCnmD3T5qJ6QlZk2HAwUndPtC8knuvN UYJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=LIF1IfdUECFEbkkk/NO30p2mLPGrL49OthA79IM6vts=; b=pRqnGa47Yp2UMHxS1nhz1bXn3gRqcyS0Utjo8S1uANAq2iB9vFo1JOb4O83CbpLgNJ fYtYD5oquFdmpoQTlDfI/p4ntRYvoZ07Wa06g3KRwLjH4NW7uybXbdcoVGlPkNgyp77e /4xKRswxCo8Jpwp8dYCYeCz9BPVlTSFBh5ARCd3adI6Vd2CUC5BowgOoDc+QYbJLehcr xEgtI2x7dXCMhMXSeDe7I5U2YKqa6zNqOmn9cU2d1fQlt1I/Z19aGjiGuccxvqfSzeGM wcZyt80BM51YPxmrdEiXmcsi+adoHhm9ExoSen6MqwbBM2R69w4KdGlrY4X+08pPmSMY 9wOw==
X-Gm-Message-State: AIVw113eRgVzT39hvKxMaHpnyMLiSeKosPXV8ji1eeHNen0NjVE4XBG6 Of1PVo8DTCPor4q00Hw=
X-Received: by 10.223.163.90 with SMTP id d26mr3387048wrb.82.1501148385204; Thu, 27 Jul 2017 02:39:45 -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 l143sm1787902wmg.46.2017.07.27.02.39.44 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 27 Jul 2017 02:39:44 -0700 (PDT)
Subject: Re: The index page [Revamp of the www.ietf.org website]
To: ietf@ietf.org
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6394482@GLKXM0002V.GREENLNK.net> <39D1C0A9-DB43-42DD-BD3F-7D636856ECEF@gmail.com> <20170721083215.a2qdgfrpg2jf6irq@mx4.yitter.info> <B5AD9DB5-A261-4924-98F4-0D5945E68366@isoc.org> <D3576F2D-4D8F-4FAA-9E6E-80D2E08FE5A8@piuha.net> <28C0B89A-73A1-4CC3-8903-822D07F2383F@ecs.soton.ac.uk> <EMEW3|93a21cfe95bdba7176c7d3d313daf9d5y6PAMX03tjc|ecs.soton.ac.uk|28C0B89A-73A1-4CC3-8903-822D07F2383F@ecs.soton.ac.uk> <04052cf6-11de-193d-7bc5-c3926182ca0a@gmail.com> <B0F00265-66C0-4F84-A647-D111348BC010@ecs.soton.ac.uk> <EMEW3|b536356ced6bc10f3c2876d5af92c499y6Q0Wx03tjc|ecs.soton.ac.uk|B0F00265-66C0-4F84-A647-D111348BC010@ecs.soton.ac.uk>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <2a3563de-92d0-de81-b83d-4b8a6209fbc3@gmail.com>
Date: Thu, 27 Jul 2017 10:39:42 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <EMEW3|b536356ced6bc10f3c2876d5af92c499y6Q0Wx03tjc|ecs.soton.ac.uk|B0F00265-66C0-4F84-A647-D111348BC010@ecs.soton.ac.uk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oBCu765xCOAI0YlnAgmuu_DleVc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 09:39:49 -0000

On 27/07/2017 00:32, Tim Chown wrote:
>> On 26 Jul 2017, at 23:32, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>
>> On 26/07/2017 21:22, Tim Chown wrote:
>> ...
>>> Well, if it’s “one click away”, participants will just bookmark or go directly to that page, and not www.ietf.org. I know I will.  Just like I sometimes also go directly to the datatracker.
>>>
>>>> For added bonus, maybe the most recent last
>>>> call / most recent blog article / most recent call for
>>>> hotel reservations opening or the like were to be also
>>>> displayed, the front door would give me an added
>>>> benefit of possibly stumbling on information that I
>>>> needed.
>>> Put all that on a one screen, participant oriented “index” page that we can go directly to.  Leave www.ietf.org to be the public shop window.
>> I seem to see a lot of people saying roughly the same thing: we need
>> an index page for active participants which is
>>   - static content only
>>   - very low on graphics
>>   - a typical font size (legible but not enormous)
>>   - displays in several columns on a laptop/desktop screen
>>   - displays in one column on a smartphone**
>>   - has links to the stuff we use daily
>>
>> ** which possiibly means making two versions.
>>
>> And for me the exemplar is still https://www.ietf.org/content.html,
>> updated with links to the new site.
> Yes, that page is a great example.
>
> Tim

Indeed, as a tool to do the job this and the original page are far 
better than the PR centric new version.

As an introduction to the IETF they are better since I don't have to go 
exploring bits of the page to find out what might be their.

- Stewart


From nobody Thu Jul 27 05:13:21 2017
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F788131FF6 for <ietf@ietfa.amsl.com>; Thu, 27 Jul 2017 05:13:20 -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 LhDvtkVtxJfi for <ietf@ietfa.amsl.com>; Thu, 27 Jul 2017 05:13:18 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (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 52474131FF5 for <ietf@ietf.org>; Thu, 27 Jul 2017 05:13:18 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id a9so104927998oih.0 for <ietf@ietf.org>; Thu, 27 Jul 2017 05:13:18 -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=xC7jm///uf4lNnhKKAb8xws8EK801gb7hoeF1+aIl5w=; b=W5gJpI0NsvN91HsDJFFZ+/nYD2iWMG6vmDPMsW9Ace0Oa8ML99+QFWroEyOLr2c1WD aLGcOrvMCOQ/fcIPbF/73lYrXdBW+xJGn4FMtEZA4kBBYuvmPCFirTufKznspxTMRoD+ vupc4CWYF6qqURvF/hkh+uVIb5s6sJdHA0RJtbHdWDVbWgJI0nTuf6keeoD+KTAo3U0R nF5HgxsyBXw43G2W7+OHqo7cgVe654uGaMCRLennA5wyoy7WmwPvS6+4E6vth9PU+nhE UTaJFrEpgbWYBRGWdNjk00v7vR5+mQkyq1iSHKUoZVz6SST4puJ6dBa6omI/yZBnDgDp vxCA==
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=xC7jm///uf4lNnhKKAb8xws8EK801gb7hoeF1+aIl5w=; b=SiluNBr7xi+qe5OnX3lbW62BZdcl/R52zA4cLYy/LCbM1tlsF75SrVjzxnxkQPixoA WI3vDwvZoB3sjmkn2QD3ibFkajtc1aW/DG/jRO/fa7njsxPELpkVLVIjoCGxHIS//bIh PY/NAFRYHmz8Ik/6iYNxTuRshHbVuciy8OInxtccJJY0gu8Gvc7KPGxErsTundlHd0GO SH7v/nhe/1QYxIM9fiB5lXs+rzSJXyH3jLAxbDYTL9jfmOIuCQ1ojXgz0yRlszQuGrOH QGG53eIN8b2BU8RNusGKoFzmzM15ChVpamvqFx2Qz0gzH6mvDvCiu69fi7xkwvAE88Rb X6rg==
X-Gm-Message-State: AIVw113SI8cOOrVT6ewvuSiZSqilA+ik2MWBj8Y3xWOuE77/X2uthbjR z3lNF31xrM3AvY1lm/BsSCY8QEgn0w==
X-Received: by 10.202.102.74 with SMTP id a71mr3406008oic.296.1501157597631; Thu, 27 Jul 2017 05:13:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.232.34 with HTTP; Thu, 27 Jul 2017 05:12:57 -0700 (PDT)
In-Reply-To: <EMEW3|b536356ced6bc10f3c2876d5af92c499y6Q0Wx03tjc|ecs.soton.ac.uk|B0F00265-66C0-4F84-A647-D111348BC010@ecs.soton.ac.uk>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6394482@GLKXM0002V.GREENLNK.net> <39D1C0A9-DB43-42DD-BD3F-7D636856ECEF@gmail.com> <20170721083215.a2qdgfrpg2jf6irq@mx4.yitter.info> <B5AD9DB5-A261-4924-98F4-0D5945E68366@isoc.org> <D3576F2D-4D8F-4FAA-9E6E-80D2E08FE5A8@piuha.net> <28C0B89A-73A1-4CC3-8903-822D07F2383F@ecs.soton.ac.uk> <EMEW3|93a21cfe95bdba7176c7d3d313daf9d5y6PAMX03tjc|ecs.soton.ac.uk|28C0B89A-73A1-4CC3-8903-822D07F2383F@ecs.soton.ac.uk> <B0F00265-66C0-4F84-A647-D111348BC010@ecs.soton.ac.uk> <04052cf6-11de-193d-7bc5-c3926182ca0a@gmail.com> <EMEW3|b536356ced6bc10f3c2876d5af92c499y6Q0Wx03tjc|ecs.soton.ac.uk|B0F00265-66C0-4F84-A647-D111348BC010@ecs.soton.ac.uk>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Thu, 27 Jul 2017 08:12:57 -0400
Message-ID: <CAA=duU02F8aEnXcTTnvCKmCrdJ8zygwVqdibyzHXJoS2MmTsUw@mail.gmail.com>
Subject: Re: The index page [Revamp of the www.ietf.org website]
To: Tim Chown <tjc@ecs.soton.ac.uk>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a1141012c5bdab105554b7d6f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/smheHfm07WYfojZMeNvY3W_i3DM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 12:13:20 -0000

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

> And for me the exemplar is still https://www.ietf.org/content.html,
> updated with links to the new site.

I also like the content page, but I find that most (but not all) of the
links are duplicated between the left and right parts of the page, but
there are some that are unique to each, so you have to search both sides. I
would prefer a single set of links, perhaps formatted like the right side
of the page, that=E2=80=99s a complete union of the two sides.

Cheers,
Andy

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

<div dir=3D"ltr"><span class=3D"gmail-im" style=3D"font-size:12.80000019073=
4863px">&gt; And for me the exemplar is still=C2=A0<a href=3D"https://www.i=
etf.org/content.html" rel=3D"noreferrer" target=3D"_blank">https://www.ietf=
.org/content.<wbr>html</a>,<br>&gt; updated with links to the new site.<br>=
<br></span><div><span style=3D"font-size:12.800000190734863px">I also like =
the content page, but I find that most (but not all) of the links are dupli=
cated between the left and right parts of the page, but there are some that=
 are unique to each, so you have to search both sides. I would prefer a sin=
gle set of=C2=A0links, perhaps formatted like the right side of the page, t=
hat=E2=80=99s a complete union of the two sides.</span></div><div><span sty=
le=3D"font-size:12.800000190734863px"><br></span></div><div><span style=3D"=
font-size:12.800000190734863px">Cheers,</span></div><div><span style=3D"fon=
t-size:12.800000190734863px">Andy</span></div><div><span style=3D"font-size=
:12.800000190734863px"><br></span></div></div>

--001a1141012c5bdab105554b7d6f--


From nobody Thu Jul 27 06:19:40 2017
Return-Path: <mary.h.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FE76132140 for <ietf@ietfa.amsl.com>; Thu, 27 Jul 2017 06:19:39 -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 vK9zaiJ_nu8A for <ietf@ietfa.amsl.com>; Thu, 27 Jul 2017 06:19:37 -0700 (PDT)
Received: from mail-yw0-x230.google.com (mail-yw0-x230.google.com [IPv6:2607:f8b0:4002: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 70AF1132017 for <ietf@ietf.org>; Thu, 27 Jul 2017 06:19:37 -0700 (PDT)
Received: by mail-yw0-x230.google.com with SMTP id u207so44551104ywc.3 for <ietf@ietf.org>; Thu, 27 Jul 2017 06:19:37 -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=d84cFvHKFhDHtyl3TzfwBH1WsESSEFxokxaHi7iqYL4=; b=uQbr34bb+7dOmwg3bAIkSaWQdkZWkLMC4NtPArUs7XqaGBvJh4X/9CjHo7EoniKjgP 3pt6LKAwAe6yUo7XGVtvUMCVEUgczPuDiG/odirYjPFV+gPF+lRMEPvMKfZzT0i0je+5 J2uqKx8JknC4CdzEyoic0AG/DcNLsth7G7zVa6OQbWaeDU5JI6WOOLJW2FIijsLbj6fd iWalQ57J22s/hk9c98ncWBihQi2PX9D0/4PSUFFDMQWd3favVIBqpQLUq3FLhWIaN8Cg Lv9A9OaOwLUPU6PfmK8fRV/abDafZvW9yuEpX+BPdf2piMdG7w2t5xjGR+sSGKrHzr6G FC/Q==
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=d84cFvHKFhDHtyl3TzfwBH1WsESSEFxokxaHi7iqYL4=; b=jN6ck0vGKr6rhLTOkd4VdUfZC9D52/8KO8rZ+LvIafllkMEUErc//VvRfMJq7jHtbs fHWimhDmMv1YOpOSgXe8lolAAwqwwfEEx6MMlCXW/uOh8pJPeJnVCpXGks4pOQ45GAOw zTj55XDM1ckhxyhC69bMaYDdttVJDNnFEttK4FhPCCHO0h3bq5CjSh5HgoCuUIu24+zo Up4NzLFGsV5xeVkwJ0ZT1Nr2/lQ+54NUXhmCkA7rhs1WDRvY9f8lsODhmUkDRw+O4g6n dkLiPCAfjgYg/3rwoGLo+N/Ak7sMgfu2/D21oYhUol+pc/V9CNAzUPXco7ULQiIWmpyu 7uUg==
X-Gm-Message-State: AIVw113APccQ8c2x+kst/YhnFGXiwyCL05GJtt2IQ5/eObtGew5cR1UG IWSR+nRgOXsSDtfL92Jp4jhL++8Kwx4K
X-Received: by 10.129.112.150 with SMTP id l144mr3498143ywc.272.1501161576577;  Thu, 27 Jul 2017 06:19:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.189.193 with HTTP; Thu, 27 Jul 2017 06:19:35 -0700 (PDT)
In-Reply-To: <20170726222602.72dc27ab@spidey.rellim.com>
References: <73ae5759-32a7-38fb-3232-9630a4dd6faa@gmail.com> <20170726222602.72dc27ab@spidey.rellim.com>
From: Mary B <mary.h.barnes@gmail.com>
Date: Thu, 27 Jul 2017 08:19:35 -0500
Message-ID: <CABmDk8m3V7dPi-qNn3sig89_keOaepo29_GAyEr+__MjUrLLHA@mail.gmail.com>
Subject: Re: Visiting Singapore/Customs Clearance
To: "Gary E. Miller" <gem@rellim.com>
Cc: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c0a9aba85bfce05554c6a66"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RgZxZAZaXprT68Zb6emzZgZWkOs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 13:19:40 -0000

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

So, according to that webpage, if you have prescription medicines, you MUST
go through the redline.  And, does anyone know where to find the list of
products that require prescriptions in Singapore per the following?

If you need to take medicines which may only be obtained through
prescription under the Singapore laws, especially sleeping pills,
depressants, stimulants, etc, please carry with you a prescription from a
physician confirming that these medicines are required for your physical
well-being. There are severe penalties for the illegal possession of such
medicines.

It seems I'll need a rather long visit with my doctor before traveling to
get prescriptions from my doc for all of my supplements, as well.
Although, I guess my best bet is to just buy what I can when I get there -
it looks like they have a lot of supplement stores, including a GNC.  I've
never been stopped, but I can't imagine what they'd think of my little
containers of white amino acid powders.

Do they xray your luggage when you enter the country?

Mary.


On Thu, Jul 27, 2017 at 12:26 AM, Gary E. Miller <gem@rellim.com> wrote:

> Yo Brian!
>
> On Thu, 27 Jul 2017 15:52:11 +1200
> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>
> > https://www.ica.gov.sg/page.aspx?pageid=3D98 says:
> ...
> > Good to see they have deployed https, but does that restriction cover
> > items for personal use? I have this strange habit of bringing a book
> > to read on a long flight.
>
> I've cleared customs in Singapore dozens of times.  They are pretty laid
> back about the normal things travelers carry.  I fear USA customs much
> more.
>
> But they are NOT laid back about drugs.  Do not carry any but the most
> benign of OTC drugs, unless they are in a proper prescription bottle.
>
> 30 grams of morphine will get you a death sentence.  Usually just
> 90 days after you are caught.
>
> I'd also leave the weapons at home.
>
> RGDS
> GARY
> ------------------------------------------------------------
> ---------------
> Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
>         gem@rellim.com  Tel:+1 541 382 8588
>
>             Veritas liberabit vos. -- Quid est veritas?
>     "If you can=E2=80=99t measure it, you can=E2=80=99t improve it." - Lo=
rd Kelvin
>

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

<div dir=3D"ltr">So, according to that webpage, if you have prescription me=
dicines, you MUST go through the redline.=C2=A0 And, does anyone know where=
 to find the list of products that require prescriptions in Singapore per t=
he following? =C2=A0=C2=A0<div><br></div><div><span style=3D"color:rgb(51,5=
1,51);font-family:Arial,Verdana,san-serif;font-size:12px;background-color:r=
gb(222,232,252)">If you need to take medicines which may only be obtained t=
hrough prescription under the Singapore laws, especially sleeping pills, de=
pressants, stimulants, etc, please carry with you a prescription from a phy=
sician confirming that these medicines are required for your physical well-=
being.=C2=A0</span><span style=3D"border:0px;font-family:Arial,Verdana,san-=
serif;font-size:12px;outline:0px;margin:0px;padding:0px;color:rgb(51,51,51)=
;background-color:rgb(222,232,252);text-decoration-line:underline">There ar=
e severe penalties for the illegal possession of such medicines.</span><spa=
n style=3D"color:rgb(51,51,51);font-family:Arial,Verdana,san-serif;font-siz=
e:12px;background-color:rgb(222,232,252)">=C2=A0</span><br></div><div><span=
 style=3D"color:rgb(51,51,51);font-family:Arial,Verdana,san-serif;font-size=
:12px;background-color:rgb(222,232,252)"><br></span></div><div>It seems I&#=
39;ll need a rather long visit with my doctor before traveling to get presc=
riptions from my doc for all of my supplements, as well.=C2=A0 Although, I =
guess my best bet is to just buy what I can when I get there - it looks lik=
e they have a lot of supplement stores, including a GNC.=C2=A0 I&#39;ve nev=
er been stopped, but I can&#39;t imagine what they&#39;d think of my little=
 containers of white amino acid powders. =C2=A0=C2=A0<br></div><div><br></d=
iv><div>Do they xray your luggage when you enter the country? =C2=A0</div><=
div><br></div><div>Mary.=C2=A0</div><div><br></div><div><br></div><div clas=
s=3D"gmail_extra"><div class=3D"gmail_quote">On Thu, Jul 27, 2017 at 12:26 =
AM, Gary E. Miller <span dir=3D"ltr">&lt;<a href=3D"mailto:gem@rellim.com" =
target=3D"_blank">gem@rellim.com</a>&gt;</span> wrote:<br><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">Yo Brian!<br>
<br>
On Thu, 27 Jul 2017 15:52:11 +1200<br>
Brian E Carpenter &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">brian.=
e.carpenter@gmail.com</a>&gt; wrote:<br>
<span class=3D"gmail-"><br>
&gt; <a href=3D"https://www.ica.gov.sg/page.aspx?pageid=3D98" rel=3D"norefe=
rrer" target=3D"_blank">https://www.ica.gov.sg/page.<wbr>aspx?pageid=3D98</=
a> says:<br>
...<br>
&gt; Good to see they have deployed https, but does that restriction cover<=
br>
&gt; items for personal use? I have this strange habit of bringing a book<b=
r>
&gt; to read on a long flight.<br>
<br>
</span>I&#39;ve cleared customs in Singapore dozens of times.=C2=A0 They ar=
e pretty laid<br>
back about the normal things travelers carry.=C2=A0 I fear USA customs much=
<br>
more.<br>
<br>
But they are NOT laid back about drugs.=C2=A0 Do not carry any but the most=
<br>
benign of OTC drugs, unless they are in a proper prescription bottle.<br>
<br>
30 grams of morphine will get you a death sentence.=C2=A0 Usually just<br>
90 days after you are caught.<br>
<br>
I&#39;d also leave the weapons at home.<br>
<br>
RGDS<br>
GARY<br>
------------------------------<wbr>------------------------------<wbr>-----=
----------<br>
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:gem@rellim.com">gem@rellim.co=
m</a>=C2=A0 Tel:<a href=3D"tel:%2B1%20541%20382%208588" value=3D"+154138285=
88">+1 541 382 8588</a><br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Veritas liberabit vos. -- Quid es=
t veritas?<br>
=C2=A0 =C2=A0 &quot;If you can=E2=80=99t measure it, you can=E2=80=99t impr=
ove it.&quot; - Lord Kelvin<br>
</blockquote></div><br></div></div>

--94eb2c0a9aba85bfce05554c6a66--


From nobody Thu Jul 27 06:34:04 2017
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CA6313201D for <ietf@ietfa.amsl.com>; Thu, 27 Jul 2017 06:34:02 -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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, 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=comcast.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 H8sAqbDJYogq for <ietf@ietfa.amsl.com>; Thu, 27 Jul 2017 06:34:00 -0700 (PDT)
Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:39]) (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 666DC131D32 for <ietf@ietf.org>; Thu, 27 Jul 2017 06:34:00 -0700 (PDT)
Received: from resomta-ch2-07v.sys.comcast.net ([69.252.207.103]) by resqmta-ch2-07v.sys.comcast.net with ESMTP id aiv0dBcu48biCaivPdVDiq; Thu, 27 Jul 2017 13:33:59 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1501162439; bh=mhENKjjNBrBGeGC5/GxH1T/z7WCYYgQ0IycAWjg1+kY=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=fzD+UvlpPsm1ouUUcFAGhw8IoO8UAChzYfit/qUe9P9PBd0n+ued12D3WCKSNixYq tE/YxPoro4g3a3ZC6sxhV5Ng/hbljPSHUthC1dJDgV/mRv8GdpCbGJo662tyHLx7wC kzc6I5B+axuA9S9C/ke/FGscgYSA7IA3adfKnCGAcw29IiWuvyMmWQRooskAK4GmuH 1No8Cd9pGyeKQskNzOAdoQaR8FBMYKf4bkxjjL1NEHcYkd1IOzjCspeWG6AEu0ylqX 8VEJ7zVTYk0G/2GF+lgutFNDvSlqg5un/MJh+p+VG5RWuMJ/m/9Vrg+ga80xXI6HXK IHUw7CXPVtOmA==
Received: from [IPv6:2601:152:4400:dbdc:114b:8b28:df0:b6f0] ([IPv6:2601:152:4400:dbdc:114b:8b28:df0:b6f0]) by resomta-ch2-07v.sys.comcast.net with SMTP id aivNd13jaDWJJaivOdkWWi; Thu, 27 Jul 2017 13:33:59 +0000
Content-Type: multipart/alternative; boundary=Apple-Mail-DA20DBFA-8537-4754-A9A4-EA2B7D39E675
Mime-Version: 1.0 (1.0)
Subject: Re: Visiting Singapore/Customs Clearance
From: Mike StJohns <mstjohns@comcast.net>
X-Mailer: iPad Mail (14G60)
In-Reply-To: <CABmDk8m3V7dPi-qNn3sig89_keOaepo29_GAyEr+__MjUrLLHA@mail.gmail.com>
Date: Thu, 27 Jul 2017 09:33:57 -0400
Cc: "Gary E. Miller" <gem@rellim.com>, IETF discussion list <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <4C169449-D1E2-4F9C-8163-CF3B5A067772@comcast.net>
References: <73ae5759-32a7-38fb-3232-9630a4dd6faa@gmail.com> <20170726222602.72dc27ab@spidey.rellim.com> <CABmDk8m3V7dPi-qNn3sig89_keOaepo29_GAyEr+__MjUrLLHA@mail.gmail.com>
To: Mary B <mary.h.barnes@gmail.com>
X-CMAE-Envelope: MS4wfHRc3qSuOAtURfnHF3lFNoplv4Mptlmlewk0txurbfICZvoQni8wonkRnATJdrpw3PGPK/w9aCyKR7JYyebB3KRVAIrVrkfx1tKP75VXP3bhkc+xV75y H32dIImqjr1TxJyPiWQIBmrec37wl411LVumYnvGSHhVP4BR2/SVQOWwWCXIckXB9CfMtA8K6njNORcBWmFRXjVZn0gW6rQvmcHWhKdWfEvKv3nDa3uH/xvT hldwdr6I90KgGOHDRN7fJA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/h7i8-k4CcLsU9EBNeC6wu55v2Jc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 13:34:03 -0000

--Apple-Mail-DA20DBFA-8537-4754-A9A4-EA2B7D39E675
Content-Type: text/plain;
	charset=euc-kr
Content-Transfer-Encoding: quoted-printable

http://www.hsa.gov.sg/content/hsa/en/Health_Products_Regulation/Consumer_Inf=
ormation/Personal_Import_Regulations/bringing_personal_medication_into_Singa=
pore.html

This might help.  There's an appendix A that lists specific drugs and a requ=
irement for pre-approval and they'll send you a license to bring it in. Ambi=
en  is on that list for example. =20

Mike

Sent from my iPad

> On Jul 27, 2017, at 09:19, Mary B <mary.h.barnes@gmail.com> wrote:
>=20
> So, according to that webpage, if you have prescription medicines, you MUS=
T go through the redline.  And, does anyone know where to find the list of p=
roducts that require prescriptions in Singapore per the following?  =20
>=20
> If you need to take medicines which may only be obtained through prescript=
ion under the Singapore laws, especially sleeping pills, depressants, stimul=
ants, etc, please carry with you a prescription from a physician confirming t=
hat these medicines are required for your physical well-being. There are sev=
ere penalties for the illegal possession of such medicines.=20
>=20
> It seems I'll need a rather long visit with my doctor before traveling to g=
et prescriptions from my doc for all of my supplements, as well.  Although, I=
 guess my best bet is to just buy what I can when I get there - it looks lik=
e they have a lot of supplement stores, including a GNC.  I've never been st=
opped, but I can't imagine what they'd think of my little containers of whit=
e amino acid powders.  =20
>=20
> Do they xray your luggage when you enter the country? =20
>=20
> Mary.=20
>=20
>=20
>> On Thu, Jul 27, 2017 at 12:26 AM, Gary E. Miller <gem@rellim.com> wrote:
>> Yo Brian!
>>=20
>> On Thu, 27 Jul 2017 15:52:11 +1200
>> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>=20
>> > https://www.ica.gov.sg/page.aspx?pageid=3D98 says:
>> ...
>> > Good to see they have deployed https, but does that restriction cover
>> > items for personal use? I have this strange habit of bringing a book
>> > to read on a long flight.
>>=20
>> I've cleared customs in Singapore dozens of times.  They are pretty laid
>> back about the normal things travelers carry.  I fear USA customs much
>> more.
>>=20
>> But they are NOT laid back about drugs.  Do not carry any but the most
>> benign of OTC drugs, unless they are in a proper prescription bottle.
>>=20
>> 30 grams of morphine will get you a death sentence.  Usually just
>> 90 days after you are caught.
>>=20
>> I'd also leave the weapons at home.
>>=20
>> RGDS
>> GARY
>> -------------------------------------------------------------------------=
--
>> Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
>>         gem@rellim.com  Tel:+1 541 382 8588
>>=20
>>             Veritas liberabit vos. -- Quid est veritas?
>>     "If you can=A1=AFt measure it, you can=A1=AFt improve it." - Lord Kel=
vin
>=20

--Apple-Mail-DA20DBFA-8537-4754-A9A4-EA2B7D39E675
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=3D=
utf-8"></head><body dir=3D"auto"><div><a href=3D"http://www.hsa.gov.sg/conte=
nt/hsa/en/Health_Products_Regulation/Consumer_Information/Personal_Import_Re=
gulations/bringing_personal_medication_into_Singapore.html">http://www.hsa.g=
ov.sg/content/hsa/en/Health_Products_Regulation/Consumer_Information/Persona=
l_Import_Regulations/bringing_personal_medication_into_Singapore.html</a></d=
iv><div id=3D"AppleMailSignature"><br></div><div id=3D"AppleMailSignature">T=
his might help. &nbsp;There's an appendix A that lists specific drugs and a r=
equirement for pre-approval and they'll send you a license to bring it in. A=
mbien &nbsp;is on that list for example. &nbsp;</div><div id=3D"AppleMailSig=
nature"><br></div><div id=3D"AppleMailSignature">Mike<br><br>Sent from my iP=
ad</div><div><br>On Jul 27, 2017, at 09:19, Mary B &lt;<a href=3D"mailto:mar=
y.h.barnes@gmail.com">mary.h.barnes@gmail.com</a>&gt; wrote:<br><br></div><b=
lockquote type=3D"cite"><div><div dir=3D"ltr">So, according to that webpage,=
 if you have prescription medicines, you MUST go through the redline.&nbsp; A=
nd, does anyone know where to find the list of products that require prescri=
ptions in Singapore per the following? &nbsp;&nbsp;<div><br></div><div><span=
 style=3D"color:rgb(51,51,51);font-family:Arial,Verdana,san-serif;font-size:=
12px;background-color:rgb(222,232,252)">If you need to take medicines which m=
ay only be obtained through prescription under the Singapore laws, especiall=
y sleeping pills, depressants, stimulants, etc, please carry with you a pres=
cription from a physician confirming that these medicines are required for y=
our physical well-being.&nbsp;</span><span style=3D"border:0px;font-family:A=
rial,Verdana,san-serif;font-size:12px;outline:0px;margin:0px;padding:0px;col=
or:rgb(51,51,51);background-color:rgb(222,232,252);text-decoration-line:unde=
rline">There are severe penalties for the illegal possession of such medicin=
es.</span><span style=3D"color:rgb(51,51,51);font-family:Arial,Verdana,san-s=
erif;font-size:12px;background-color:rgb(222,232,252)">&nbsp;</span><br></di=
v><div><span style=3D"color:rgb(51,51,51);font-family:Arial,Verdana,san-seri=
f;font-size:12px;background-color:rgb(222,232,252)"><br></span></div><div>It=
 seems I'll need a rather long visit with my doctor before traveling to get p=
rescriptions from my doc for all of my supplements, as well.&nbsp; Although,=
 I guess my best bet is to just buy what I can when I get there - it looks l=
ike they have a lot of supplement stores, including a GNC.&nbsp; I've never b=
een stopped, but I can't imagine what they'd think of my little containers o=
f white amino acid powders. &nbsp;&nbsp;<br></div><div><br></div><div>Do the=
y xray your luggage when you enter the country? &nbsp;</div><div><br></div><=
div>Mary.&nbsp;</div><div><br></div><div><br></div><div class=3D"gmail_extra=
"><div class=3D"gmail_quote">On Thu, Jul 27, 2017 at 12:26 AM, Gary E. Mille=
r <span dir=3D"ltr">&lt;<a href=3D"mailto:gem@rellim.com" target=3D"_blank">=
gem@rellim.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">Yo Brian!<br>
<br>
On Thu, 27 Jul 2017 15:52:11 +1200<br>
Brian E Carpenter &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">brian.e=
.carpenter@gmail.com</a>&gt; wrote:<br>
<span class=3D"gmail-"><br>
&gt; <a href=3D"https://www.ica.gov.sg/page.aspx?pageid=3D98" rel=3D"norefer=
rer" target=3D"_blank">https://www.ica.gov.sg/page.<wbr>aspx?pageid=3D98</a>=
 says:<br>
...<br>
&gt; Good to see they have deployed https, but does that restriction cover<b=
r>
&gt; items for personal use? I have this strange habit of bringing a book<br=
>
&gt; to read on a long flight.<br>
<br>
</span>I've cleared customs in Singapore dozens of times.&nbsp; They are pre=
tty laid<br>
back about the normal things travelers carry.&nbsp; I fear USA customs much<=
br>
more.<br>
<br>
But they are NOT laid back about drugs.&nbsp; Do not carry any but the most<=
br>
benign of OTC drugs, unless they are in a proper prescription bottle.<br>
<br>
30 grams of morphine will get you a death sentence.&nbsp; Usually just<br>
90 days after you are caught.<br>
<br>
I'd also leave the weapons at home.<br>
<br>
RGDS<br>
GARY<br>
------------------------------<wbr>------------------------------<wbr>------=
---------<br>
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703<br>
&nbsp; &nbsp; &nbsp; &nbsp; <a href=3D"mailto:gem@rellim.com">gem@rellim.com=
</a>&nbsp; Tel:<a href=3D"tel:%2B1%20541%20382%208588" value=3D"+15413828588=
">+1 541 382 8588</a><br>
<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Veritas liberabit vos. -- Quid est=
 veritas?<br>
&nbsp; &nbsp; "If you can=E2=80=99t measure it, you can=E2=80=99t improve it=
." - Lord Kelvin<br>
</blockquote></div><br></div></div>
</div></blockquote></body></html>=

--Apple-Mail-DA20DBFA-8537-4754-A9A4-EA2B7D39E675--


From nobody Thu Jul 27 06:49:29 2017
Return-Path: <mary.h.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A10FB131CA0 for <ietf@ietfa.amsl.com>; Thu, 27 Jul 2017 06:49:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.215
X-Spam-Level: 
X-Spam-Status: No, score=-1.215 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DRUGS_ANXIETY=1.483, 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 6QcIu9QNSLWs for <ietf@ietfa.amsl.com>; Thu, 27 Jul 2017 06:49:25 -0700 (PDT)
Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::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 749B0120721 for <ietf@ietf.org>; Thu, 27 Jul 2017 06:49:25 -0700 (PDT)
Received: by mail-yw0-x22e.google.com with SMTP id u207so45074511ywc.3 for <ietf@ietf.org>; Thu, 27 Jul 2017 06:49:25 -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=tc7PFzWkMytHmPJ4gelHiX5sG8Qmx9U41stEysmVBfI=; b=vKE5CMXxUBjbPAr9Inz3mZ3biknCL/N4mowJ297cZ7CsTFs4fFenlESkvoaqQWGpgA HxZPKqvM6/G8vbqkeVkjQtsvCitYp9Zu7BZEGASlX6kt1AsW8zmsdICvxfr5fkl8iL0T LEKEBM18G1W8kxtc+1G0C88XxRAh5fwNjXVcxXD8qGABllC+A+ZJVbq/VKTYurT6EHGZ MWYrYr8rNzLD2YweU4k4DzFqAwHYttvEojJ9qyFynLg/IH5IvYIBcudsgDffUQ6uswW2 k9QUaMNxBPO0VnDpL+VEZ9ziwijorWpl362awafsagChYr02ULp9HHI7RY+M+4ZiUnQp 0dgA==
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=tc7PFzWkMytHmPJ4gelHiX5sG8Qmx9U41stEysmVBfI=; b=fJqcx40OjaBHZ0zBByQwws7DiETgPbPyHJNMCGKZpaq4B9shEnrtwmTBFjce3THl+g mOqs+L8UkyIQokTjdd8oqDlvy2h4S3xkgw5Aq5j3WjK24x3ULSjnHC2PIkceHQN0jmT5 QUS4B1PF6unJ3tST2OiCYpHvqeeCH6c7cA1etcJjAvMP0IsnUK1wCBjbwcwaJs32LzbZ rffr7vPE3q2vRe2Hby7iS4Z4wsy2iAniCrZxWsLL3EtCDt9D5fYoiKOKVemHalO7XMCg 6bBpW9iUwqUht3XiJmng/gDCWsYJDzxLP17KZk10kO8fkBAPpGK5x13CtjnaZYca3klm Mtsw==
X-Gm-Message-State: AIVw112Oud+zupWv78Hw2SFnSt1FQQYKhZELtJDKXQe3+Q4XDjhG2N/C +3A8tWtsZ/bGWOIbrqHSNcuJuGCncA==
X-Received: by 10.37.234.4 with SMTP id p4mr3568076ybd.201.1501163364631; Thu, 27 Jul 2017 06:49:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.189.193 with HTTP; Thu, 27 Jul 2017 06:49:23 -0700 (PDT)
In-Reply-To: <4C169449-D1E2-4F9C-8163-CF3B5A067772@comcast.net>
References: <73ae5759-32a7-38fb-3232-9630a4dd6faa@gmail.com> <20170726222602.72dc27ab@spidey.rellim.com> <CABmDk8m3V7dPi-qNn3sig89_keOaepo29_GAyEr+__MjUrLLHA@mail.gmail.com> <4C169449-D1E2-4F9C-8163-CF3B5A067772@comcast.net>
From: Mary B <mary.h.barnes@gmail.com>
Date: Thu, 27 Jul 2017 08:49:23 -0500
Message-ID: <CABmDk8kWr_NSh_r2JCeVST929UJVXFwPPkxAf9+k6_PBuQmmsw@mail.gmail.com>
Subject: Re: Visiting Singapore/Customs Clearance
To: Mike StJohns <mstjohns@comcast.net>
Cc: "Gary E. Miller" <gem@rellim.com>, IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="f403045dc77c1958d405554cd57e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aOViZkuKdKr5Fzl4maNNMPTuAY4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 13:49:27 -0000

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

Yeah, I just came across that page.   Valium is also on that list - we
might have a lot of wide awake, anxious people at this meeting ;)     That
page also mentions that Pseudoephedrine has limitations - lots of people
take that for allergies, but I guess that amount is similar to US
restrictions for buying at the pharmacy.

And, this would be important for folks traveling CPAPs:
http://www.hsa.gov.sg/content/hsa/en/Health_Products_Regulation/Consumer_In=
formation/Personal_Import_Regulations/bringing_medical_devices_for_personal=
_use_into_Singapore.html

In particular, it notes that you need an email approving the device:
"Please obtain the necessary approvals for the import of medical devices
for personal use, before commencing travel. You are not required to declare
your medical devices on your arrival in Singapore. However, as Customs
Officers may perform routine checks, please have all the supporting
documents and the approved acknowledgement email for the import of medical
devices for personal use, ready with you for inspection when requested.:"

And, this looks like the list of what they consider medical devices:
https://eservice.hsa.gov.sg/medics/md/mdEnquiry.do?action=3DgetAllDevices

It includes things like blood sugar monitoring devices.

Although, looking at various discussions, it does seem like it's not that
big of a deal and that you just need to have paperwork if asked.

Regards,
Mary

On Thu, Jul 27, 2017 at 8:33 AM, Mike StJohns <mstjohns@comcast.net> wrote:

> http://www.hsa.gov.sg/content/hsa/en/Health_Products_Regulation/Consumer_
> Information/Personal_Import_Regulations/bringing_personal_
> medication_into_Singapore.html
>
> This might help.  There's an appendix A that lists specific drugs and a
> requirement for pre-approval and they'll send you a license to bring it i=
n.
> Ambien  is on that list for example.
>
> Mike
>
> Sent from my iPad
>
> On Jul 27, 2017, at 09:19, Mary B <mary.h.barnes@gmail.com> wrote:
>
> So, according to that webpage, if you have prescription medicines, you
> MUST go through the redline.  And, does anyone know where to find the lis=
t
> of products that require prescriptions in Singapore per the following?
>
> If you need to take medicines which may only be obtained through
> prescription under the Singapore laws, especially sleeping pills,
> depressants, stimulants, etc, please carry with you a prescription from a
> physician confirming that these medicines are required for your physical
> well-being. There are severe penalties for the illegal possession of such
> medicines.
>
> It seems I'll need a rather long visit with my doctor before traveling to
> get prescriptions from my doc for all of my supplements, as well.
> Although, I guess my best bet is to just buy what I can when I get there =
-
> it looks like they have a lot of supplement stores, including a GNC.  I'v=
e
> never been stopped, but I can't imagine what they'd think of my little
> containers of white amino acid powders.
>
> Do they xray your luggage when you enter the country?
>
> Mary.
>
>
> On Thu, Jul 27, 2017 at 12:26 AM, Gary E. Miller <gem@rellim.com> wrote:
>
>> Yo Brian!
>>
>> On Thu, 27 Jul 2017 15:52:11 +1200
>> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>
>> > https://www.ica.gov.sg/page.aspx?pageid=3D98 says:
>> ...
>> > Good to see they have deployed https, but does that restriction cover
>> > items for personal use? I have this strange habit of bringing a book
>> > to read on a long flight.
>>
>> I've cleared customs in Singapore dozens of times.  They are pretty laid
>> back about the normal things travelers carry.  I fear USA customs much
>> more.
>>
>> But they are NOT laid back about drugs.  Do not carry any but the most
>> benign of OTC drugs, unless they are in a proper prescription bottle.
>>
>> 30 grams of morphine will get you a death sentence.  Usually just
>> 90 days after you are caught.
>>
>> I'd also leave the weapons at home.
>>
>> RGDS
>> GARY
>> ------------------------------------------------------------
>> ---------------
>> Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
>>         gem@rellim.com  Tel:+1 541 382 8588
>>
>>             Veritas liberabit vos. -- Quid est veritas?
>>     "If you can=E2=80=99t measure it, you can=E2=80=99t improve it." - L=
ord Kelvin
>>
>
>

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

<div dir=3D"ltr">Yeah, I just came across that page. =C2=A0 Valium is also =
on that list - we might have a lot of wide awake, anxious people at this me=
eting ;) =C2=A0 =C2=A0 That page also mentions that Pseudoephedrine has lim=
itations=C2=A0- lots of people take that for allergies, but I guess that am=
ount is similar to US restrictions for buying at the pharmacy.<div><br></di=
v><div>And, this would be important for folks traveling CPAPs:=C2=A0</div><=
div><a href=3D"http://www.hsa.gov.sg/content/hsa/en/Health_Products_Regulat=
ion/Consumer_Information/Personal_Import_Regulations/bringing_medical_devic=
es_for_personal_use_into_Singapore.html">http://www.hsa.gov.sg/content/hsa/=
en/Health_Products_Regulation/Consumer_Information/Personal_Import_Regulati=
ons/bringing_medical_devices_for_personal_use_into_Singapore.html</a><br></=
div><div><br></div><div>In particular, it notes that you need an email appr=
oving the device:</div><div><span style=3D"color:rgb(107,107,107);font-fami=
ly:Arial,Helvetica,sans-serif;font-size:14px">&quot;Please obtain the neces=
sary approvals for the import of medical devices for personal use, before c=
ommencing travel. You are not required to declare your medical devices on y=
our arrival in Singapore. However, as Customs Officers may perform routine =
checks, please have all the supporting documents and the approved acknowled=
gement email for the import of medical devices for personal use, ready with=
 you for inspection when requested.:&quot;=C2=A0</span><br></div><div><span=
 style=3D"color:rgb(107,107,107);font-family:Arial,Helvetica,sans-serif;fon=
t-size:14px"><br></span></div><div>And, this looks like the list of what th=
ey consider medical devices:=C2=A0<br></div><div><a href=3D"https://eservic=
e.hsa.gov.sg/medics/md/mdEnquiry.do?action=3DgetAllDevices">https://eservic=
e.hsa.gov.sg/medics/md/mdEnquiry.do?action=3DgetAllDevices</a><br></div><di=
v><br></div><div>It includes things like blood sugar monitoring devices. =
=C2=A0</div><div><br></div><div>Although, looking at various discussions, i=
t does seem like it&#39;s not that big of a deal and that you just need to =
have paperwork if asked. =C2=A0</div><div><br></div><div>Regards,</div><div=
>Mary</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Thu, Jul 27, 2017 at 8:33 AM, Mike StJohns <span dir=3D"ltr">&lt;<a href=
=3D"mailto:mstjohns@comcast.net" target=3D"_blank">mstjohns@comcast.net</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"auto"><div=
><a href=3D"http://www.hsa.gov.sg/content/hsa/en/Health_Products_Regulation=
/Consumer_Information/Personal_Import_Regulations/bringing_personal_medicat=
ion_into_Singapore.html" target=3D"_blank">http://www.hsa.gov.sg/content/<w=
br>hsa/en/Health_Products_<wbr>Regulation/Consumer_<wbr>Information/Persona=
l_Import_<wbr>Regulations/bringing_personal_<wbr>medication_into_Singapore.=
html</a></div><div id=3D"m_4010564520955271594AppleMailSignature"><br></div=
><div id=3D"m_4010564520955271594AppleMailSignature">This might help.=C2=A0=
 There&#39;s an appendix A that lists specific drugs and a requirement for =
pre-approval and they&#39;ll send you a license to bring it in. Ambien =C2=
=A0is on that list for example. =C2=A0</div><div id=3D"m_401056452095527159=
4AppleMailSignature"><br></div><div id=3D"m_4010564520955271594AppleMailSig=
nature">Mike<br><br>Sent from my iPad</div><div><div class=3D"h5"><div><br>=
On Jul 27, 2017, at 09:19, Mary B &lt;<a href=3D"mailto:mary.h.barnes@gmail=
.com" target=3D"_blank">mary.h.barnes@gmail.com</a>&gt; wrote:<br><br></div=
><blockquote type=3D"cite"><div><div dir=3D"ltr">So, according to that webp=
age, if you have prescription medicines, you MUST go through the redline.=
=C2=A0 And, does anyone know where to find the list of products that requir=
e prescriptions in Singapore per the following? =C2=A0=C2=A0<div><br></div>=
<div><span style=3D"color:rgb(51,51,51);font-family:Arial,Verdana,san-serif=
;font-size:12px;background-color:rgb(222,232,252)">If you need to take medi=
cines which may only be obtained through prescription under the Singapore l=
aws, especially sleeping pills, depressants, stimulants, etc, please carry =
with you a prescription from a physician confirming that these medicines ar=
e required for your physical well-being.=C2=A0</span><span style=3D"border:=
0px;font-family:Arial,Verdana,san-serif;font-size:12px;outline:0px;margin:0=
px;padding:0px;color:rgb(51,51,51);background-color:rgb(222,232,252);text-d=
ecoration-line:underline">There are severe penalties for the illegal posses=
sion of such medicines.</span><span style=3D"color:rgb(51,51,51);font-famil=
y:Arial,Verdana,san-serif;font-size:12px;background-color:rgb(222,232,252)"=
>=C2=A0</span><br></div><div><span style=3D"color:rgb(51,51,51);font-family=
:Arial,Verdana,san-serif;font-size:12px;background-color:rgb(222,232,252)">=
<br></span></div><div>It seems I&#39;ll need a rather long visit with my do=
ctor before traveling to get prescriptions from my doc for all of my supple=
ments, as well.=C2=A0 Although, I guess my best bet is to just buy what I c=
an when I get there - it looks like they have a lot of supplement stores, i=
ncluding a GNC.=C2=A0 I&#39;ve never been stopped, but I can&#39;t imagine =
what they&#39;d think of my little containers of white amino acid powders. =
=C2=A0=C2=A0<br></div><div><br></div><div>Do they xray your luggage when yo=
u enter the country? =C2=A0</div><div><br></div><div>Mary.=C2=A0</div><div>=
<br></div><div><br></div><div class=3D"gmail_extra"><div class=3D"gmail_quo=
te">On Thu, Jul 27, 2017 at 12:26 AM, Gary E. Miller <span dir=3D"ltr">&lt;=
<a href=3D"mailto:gem@rellim.com" target=3D"_blank">gem@rellim.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">Yo Brian=
!<br>
<br>
On Thu, 27 Jul 2017 15:52:11 +1200<br>
Brian E Carpenter &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=
=3D"_blank">brian.e.carpenter@gmail.com</a>&gt; wrote:<br>
<span class=3D"m_4010564520955271594gmail-"><br>
&gt; <a href=3D"https://www.ica.gov.sg/page.aspx?pageid=3D98" rel=3D"norefe=
rrer" target=3D"_blank">https://www.ica.gov.sg/page.as<wbr>px?pageid=3D98</=
a> says:<br>
...<br>
&gt; Good to see they have deployed https, but does that restriction cover<=
br>
&gt; items for personal use? I have this strange habit of bringing a book<b=
r>
&gt; to read on a long flight.<br>
<br>
</span>I&#39;ve cleared customs in Singapore dozens of times.=C2=A0 They ar=
e pretty laid<br>
back about the normal things travelers carry.=C2=A0 I fear USA customs much=
<br>
more.<br>
<br>
But they are NOT laid back about drugs.=C2=A0 Do not carry any but the most=
<br>
benign of OTC drugs, unless they are in a proper prescription bottle.<br>
<br>
30 grams of morphine will get you a death sentence.=C2=A0 Usually just<br>
90 days after you are caught.<br>
<br>
I&#39;d also leave the weapons at home.<br>
<br>
RGDS<br>
GARY<br>
------------------------------<wbr>------------------------------<wbr>-----=
----------<br>
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:gem@rellim.com" target=3D"_bl=
ank">gem@rellim.com</a>=C2=A0 Tel:<a href=3D"tel:%2B1%20541%20382%208588" v=
alue=3D"+15413828588" target=3D"_blank">+1 541 382 8588</a><br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Veritas liberabit vos. -- Quid es=
t veritas?<br>
=C2=A0 =C2=A0 &quot;If you can=E2=80=99t measure it, you can=E2=80=99t impr=
ove it.&quot; - Lord Kelvin<br>
</blockquote></div><br></div></div>
</div></blockquote></div></div></div></blockquote></div><br></div>

--f403045dc77c1958d405554cd57e--


From nobody Thu Jul 27 06:59:15 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEF6E13202A for <ietf@ietfa.amsl.com>; Thu, 27 Jul 2017 06:59:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 1_CD7t1z_6uN for <ietf@ietfa.amsl.com>; Thu, 27 Jul 2017 06:59:12 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC89E131C8F for <ietf@ietf.org>; Thu, 27 Jul 2017 06:59:12 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dajJm-000OE8-H5; Thu, 27 Jul 2017 09:59:10 -0400
Date: Thu, 27 Jul 2017 09:59:02 -0400
From: John C Klensin <john-ietf@jck.com>
To: Mary B <mary.h.barnes@gmail.com>, "Gary E. Miller" <gem@rellim.com>
cc: IETF discussion list <ietf@ietf.org>
Subject: Re: Visiting Singapore/Customs Clearance
Message-ID: <C0E33544688BD6D801D91CEC@PSB>
In-Reply-To: <CABmDk8m3V7dPi-qNn3sig89_keOaepo29_GAyEr+__MjUrLLHA@mail.gmail.com>
References: <73ae5759-32a7-38fb-3232-9630a4dd6faa@gmail.com> <20170726222602.72dc27ab@spidey.rellim.com> <CABmDk8m3V7dPi-qNn3sig89_keOaepo29_GAyEr+__MjUrLLHA@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IVU4lqB_Ujulp9HfhsRa2TOuygw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 13:59:15 -0000

--On Thursday, July 27, 2017 08:19 -0500 Mary B
<mary.h.barnes@gmail.com> wrote:

> So, according to that webpage, if you have prescription
> medicines, you MUST go through the redline.  And, does anyone
> know where to find the list of products that require
> prescriptions in Singapore per the following?

I've taken the precaution of doing that but, at least in my
experience, they tend to treat your being willing to disclose
and having a pile of documentation as a sign of good intent and
weave one through so that the different in time to get through
the red versus green lines is trivial -- they are both fairly
efficient and laid back, especially when compared to the USA.
Of course, there is no counting on that for any given day or
person.

>...
> It seems I'll need a rather long visit with my doctor before
> traveling to get prescriptions from my doc for all of my
> supplements, as well. Although, I guess my best bet is to just
> buy what I can when I get there - it looks like they have a
> lot of supplement stores, including a GNC.  I've never been
> stopped, but I can't imagine what they'd think of my little
> containers of white amino acid powders.

That is more or less what I've done, trying to confine what I
carry with me to the absolute minimum of prescription materials.
I haven't looked at the Singapore rules in years (and these
things do change), but I note that many formulations of, e.g.,
OTC decongestants and cough syrups in the US contain enough
quantity of members of the epinephrine family to be considered
powerful drugs in some countries, powerful enough to require not
only prescriptions but signatures of at least three physicians
(I'm exaggerating, but it has felt like that when I innocently
tried obtain an additional supply.  Of course, the same problem
applies in the other direction with things being OTC in some
places but requiring prescriptions in the US.     I'm a bit
surprised you haven't encountered the situation before.

> Do they xray your luggage when you enter the country?

Every country has the right to do that.  Some do so, some do
selectively, some usually don't, etc.  None of them are likely
to give you an easily-interpreted and unambiguous answer about
either xrays or opening and hand-searching.  I've found it most
efficient to just assume "yes" and decide what to pack, how to
pack it, and which line to go through on that basis.

I've been through customs and immigration in Singapore multiple
times, although not nearly as many or as often as Ole.  In
general, I've found them not much different from most other
places.  I have found two exceptions striking: They are
extremely professional and courteous, at least as long as one
treats them and their need to do their jobs with respect.  I've
never encountered someone who was having a bad day, felt it was
ok to take that out on travelers, and who I suspect was going to
have a similar bad day every day that month.  The other
exception is that they are really, really, serious about their
banned substances rules, including their anti-drug policy.  If
someone shows up with, e.g., opioid pain medication and without
extensive and convincing documentation, one is likely to be in
for some rather intense interviews and questioning,   The Rx
should specify what dosages you are expected to take and I
recommend not showing with a pill more than is needed for the
duration of the stay.   But that is really not an unreasonable
approach anywhere.

    john





From nobody Thu Jul 27 07:05:58 2017
Return-Path: <olejacobsen@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 606D913201C for <ietf@ietfa.amsl.com>; Thu, 27 Jul 2017 07:05:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.218
X-Spam-Level: 
X-Spam-Status: No, score=-1.218 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DRUGS_ANXIETY=1.483, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, 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=me.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 7zRf6pRKtNaA for <ietf@ietfa.amsl.com>; Thu, 27 Jul 2017 07:05:54 -0700 (PDT)
Received: from mr11p00im-asmtp004.me.com (mr11p00im-asmtp004.me.com [17.110.69.135]) (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 5D3AB13202E for <ietf@ietf.org>; Thu, 27 Jul 2017 07:05:45 -0700 (PDT)
Received: from process-dkim-sign-daemon.mr11p00im-asmtp004.me.com by mr11p00im-asmtp004.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OTR003005SQ9B00@mr11p00im-asmtp004.me.com> for ietf@ietf.org; Thu, 27 Jul 2017 14:05:45 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017; t=1501164344; bh=ezs9nbScEPRCd8qNYd+4T+ho9tHHuiMTgSgTwMqG5rE=; h=Date:From:To:Subject:Message-id:MIME-version:Content-type; b=XCTRk+HFMYp/7DO1o9UlDk1YZDcaBLoCOcj+87F8f0bRKJO3LP2uNYKPfuShZhxj7 /YGVP5ZYWceVXVUuYsFkY3CD/qpB0gtM1FGSAImM9FwEQsK/PfrRdcBVf/Igq6Qo23 XvQMRK56sWba159Qr5zfZoNWEGgd+OYrhHpyJ9kg62zSBvn6sbJeStlP+LoLSyPdlG iYg+7XWtdFfaJE9ZljaDghlnfOJqBBDlHUWqFVLHKi81YaxQw6AO0tUpm1eHHCbM4i t5V3uUEPqjbBEMp/9J9L+2ROPttsKiJNROSNq5DjDSgZsacs0lvzxTuq2LroqVktEI tj5pUMgkzSjVA==
Received: from icloud.com ([127.0.0.1]) by mr11p00im-asmtp004.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OTR00GLY5TFF700@mr11p00im-asmtp004.me.com>; Thu, 27 Jul 2017 14:05:40 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-07-27_07:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1701120000 definitions=main-1707270222
Date: Thu, 27 Jul 2017 07:05:39 -0700 (PDT)
From: Ole Jacobsen <olejacobsen@me.com>
Reply-to: Ole Jacobsen <olejacobsen@me.com>
To: Mary B <mary.h.barnes@gmail.com>
Cc: Mike StJohns <mstjohns@comcast.net>, "Gary E. Miller" <gem@rellim.com>, IETF discussion list <ietf@ietf.org>
Subject: Re: Visiting Singapore/Customs Clearance
In-reply-to: <CABmDk8kWr_NSh_r2JCeVST929UJVXFwPPkxAf9+k6_PBuQmmsw@mail.gmail.com>
Message-id: <alpine.OSX.2.01.1707270651160.78919@rabdullah.local>
References: <73ae5759-32a7-38fb-3232-9630a4dd6faa@gmail.com> <20170726222602.72dc27ab@spidey.rellim.com> <CABmDk8m3V7dPi-qNn3sig89_keOaepo29_GAyEr+__MjUrLLHA@mail.gmail.com> <4C169449-D1E2-4F9C-8163-CF3B5A067772@comcast.net> <CABmDk8kWr_NSh_r2JCeVST929UJVXFwPPkxAf9+k6_PBuQmmsw@mail.gmail.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-version: 1.0
Content-type: MULTIPART/MIXED; BOUNDARY="140733193388032-1110769531-1501163926=:78919"
Content-id: <alpine.OSX.2.01.1707270658570.78919@rabdullah.local>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/g4_ug4Ebe9TK-wQpMHwXjvlDYk8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 14:05:56 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--140733193388032-1110769531-1501163926=:78919
Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-7
Content-Transfer-Encoding: 8BIT
Content-ID: <alpine.OSX.2.01.1707270658571.78919@rabdullah.local>


Folks,

Luggage is not X-rayed upon entry into Singapore.

I've travelled with a CPAP machine to Singapore on many occasions, no 
issues whatsoever.(And at least my machine has a sticker that says
"Medical Device").

Ditto for medication, nobody has ever asked for paperwork, original 
bottles or whatever.

Never heard of anyone having problems with this.

Illegal drugs are of course a different matter. The landing card has 
the following text in RED ink:

         WARNING
DEATH FOR DRUG TRAFFICKERS
    UNDER SINGAPORE LAW

(It's the only text in red unless you count the check boxes
and their legend).

Good news for Mary and others: There is a fairly large grocery store 
right below the venue. A large food court too.

A happy geek would not have to leave the venue for an entire week, and 
there are ways to leave (underground) without having to expose 
yourself to the outside :-) But geeks should take at least an hour
or so to visit Sim Lim Center and Mustafas. Trust me.

Ole


Ole J. Jacobsen
Editor and Publisher
The Internet Protocol Journal
Office:  +1 415-550-9433
Cell:    +1 415-370-4628
Docomo:  090 3337-9311
Web: protocoljournal.org
E-mail: olejacobsen@me.com




On Thu, 27 Jul 2017, Mary B wrote:

> Yeah, I just came across that page.   Valium is also on that list - we
> might have a lot of wide awake, anxious people at this meeting ;)     That
> page also mentions that Pseudoephedrine has limitations - lots of people
> take that for allergies, but I guess that amount is similar to US
> restrictions for buying at the pharmacy.
> 
> And, this would be important for folks traveling CPAPs:
> http://www.hsa.gov.sg/content/hsa/en/Health_Products_Regulation/Consumer_Information/Personal_Import_Regulations/bringing_medical_devices_for_personal_use_into_Singapore.html
> 
> In particular, it notes that you need an email approving the device:
> "Please obtain the necessary approvals for the import of medical devices
> for personal use, before commencing travel. You are not required to declare
> your medical devices on your arrival in Singapore. However, as Customs
> Officers may perform routine checks, please have all the supporting
> documents and the approved acknowledgement email for the import of medical
> devices for personal use, ready with you for inspection when requested.:"
> 
> And, this looks like the list of what they consider medical devices:
> https://eservice.hsa.gov.sg/medics/md/mdEnquiry.do?action=getAllDevices
> 
> It includes things like blood sugar monitoring devices.
> 
> Although, looking at various discussions, it does seem like it's not that
> big of a deal and that you just need to have paperwork if asked.
> 
> Regards,
> Mary
> 
> On Thu, Jul 27, 2017 at 8:33 AM, Mike StJohns <mstjohns@comcast.net> wrote:
> 
> > http://www.hsa.gov.sg/content/hsa/en/Health_Products_Regulation/Consumer_
> > Information/Personal_Import_Regulations/bringing_personal_
> > medication_into_Singapore.html
> >
> > This might help.  There's an appendix A that lists specific drugs and a
> > requirement for pre-approval and they'll send you a license to bring it in.
> > Ambien  is on that list for example.
> >
> > Mike
> >
> > Sent from my iPad
> >
> > On Jul 27, 2017, at 09:19, Mary B <mary.h.barnes@gmail.com> wrote:
> >
> > So, according to that webpage, if you have prescription medicines, you
> > MUST go through the redline.  And, does anyone know where to find the list
> > of products that require prescriptions in Singapore per the following?
> >
> > If you need to take medicines which may only be obtained through
> > prescription under the Singapore laws, especially sleeping pills,
> > depressants, stimulants, etc, please carry with you a prescription from a
> > physician confirming that these medicines are required for your physical
> > well-being. There are severe penalties for the illegal possession of such
> > medicines.
> >
> > It seems I'll need a rather long visit with my doctor before traveling to
> > get prescriptions from my doc for all of my supplements, as well.
> > Although, I guess my best bet is to just buy what I can when I get there -
> > it looks like they have a lot of supplement stores, including a GNC.  I've
> > never been stopped, but I can't imagine what they'd think of my little
> > containers of white amino acid powders.
> >
> > Do they xray your luggage when you enter the country?
> >
> > Mary.
> >
> >
> > On Thu, Jul 27, 2017 at 12:26 AM, Gary E. Miller <gem@rellim.com> wrote:
> >
> >> Yo Brian!
> >>
> >> On Thu, 27 Jul 2017 15:52:11 +1200
> >> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> >>
> >> > https://www.ica.gov.sg/page.aspx?pageid=98 says:
> >> ...
> >> > Good to see they have deployed https, but does that restriction cover
> >> > items for personal use? I have this strange habit of bringing a book
> >> > to read on a long flight.
> >>
> >> I've cleared customs in Singapore dozens of times.  They are pretty laid
> >> back about the normal things travelers carry.  I fear USA customs much
> >> more.
> >>
> >> But they are NOT laid back about drugs.  Do not carry any but the most
> >> benign of OTC drugs, unless they are in a proper prescription bottle.
> >>
> >> 30 grams of morphine will get you a death sentence.  Usually just
> >> 90 days after you are caught.
> >>
> >> I'd also leave the weapons at home.
> >>
> >> RGDS
> >> GARY
> >> ------------------------------------------------------------
> >> ---------------
> >> Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
> >>         gem@rellim.com  Tel:+1 541 382 8588
> >>
> >>             Veritas liberabit vos. -- Quid est veritas?
> >>     "If you can¢t measure it, you can¢t improve it." - Lord Kelvin
> >>
> >
> >
> 
--140733193388032-1110769531-1501163926=:78919--


From nobody Thu Jul 27 07:48:30 2017
Return-Path: <charlie.perkins@huawei.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B4012127ABE; Thu, 27 Jul 2017 07:48:27 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Charles Perkins <charlie.perkins@huawei.com>
To: <Iot-dir@ietf.org>
Cc: lwip@ietf.org, ietf@ietf.org, draft-ietf-lwig-energy-efficient.all@ietf.org, charliep@computer.org
Subject: Iotdir early review of draft-ietf-lwig-energy-efficient-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.57.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150116690760.11487.2065170484353080456@ietfa.amsl.com>
Date: Thu, 27 Jul 2017 07:48:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ju3TnvKWrRPZPNXkePnBJOwTPE8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 14:48:28 -0000

Reviewer: Charles Perkins
Review result: On the Right Track

[Please excuse if this is a duplicate.  I got an error from datatracker on my first attempt.]

Overall comments:

I think that some important techniques for energy efficiency deserve mention
or significant enlargement:

- Packet bundling
- Data aggregation
- Power management / range reduction
- Fragmentation is more energy-efficient at lower layers than at higher layers
- Compression, on the other hand, is more efficient at higher layers,
  particularly before encryption.

The document needs a concise statement of purpose.  Maybe insert the
following after the first paragraph of the Introduction:

   In this document we describe techniques that are in common use at Layer 2	
   and at Layer 3, and we indicate the need for higher-layer awareness of	
   lower-layer features.

Also in the introduction, some discussion is needed about cross-layer design.
Is cross-layer design in scope for the [lwig] Working Group?

In figure 1 and elsewhere, it should not be assumed that RPL is the only
choice for routing in energy-efficient networks.  So, for instance,
"RPL" could be replaced by "RTG" in Figure 1.

Shouldn't there be an entry for synchronized reception in Figure 2?  Isn't
Figure 2 actually a table, and thus should be labeled Table 1?

Section 3.3 (Throughput) does not seem to add much if anything to the
discussion.  The conclusion about the trade-off is quite obvious.

Particularly in section 3.5.2, but also elsewhere, some examples would
be very helpful.

Section 6.3 (CoAP timers) seems to be only about one timer.
Are there more?  What about interactions with TCP timers, etc.?

Section 7 should be entitled "Summary and Conclusions".
In section 7, it would be nice to offer cross references for each
conclusion, referring the reader to the relevant section of the document.
Each conclusion should follow from some previous section of the document.
Unfortunately that currently isn't quite the case.

The citation [Announcementlayer] does not appear in the body of the article.

There are weird line breaks appearing at certain random points in the
document.

I have editorial suggestions and corrections which I will
supply as an rfcdiff file under separate email.

Regards,
Charlie P.


From nobody Thu Jul 27 08:32:23 2017
Return-Path: <lenny@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 719C4131CBE for <ietf@ietfa.amsl.com>; Thu, 27 Jul 2017 08:32:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level: 
X-Spam-Status: No, score=-2.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, 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=juniper.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 L-MFnF-b50rv for <ietf@ietfa.amsl.com>; Thu, 27 Jul 2017 08:32:19 -0700 (PDT)
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-by2nam03on0130.outbound.protection.outlook.com [104.47.42.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46501131C11 for <ietf@ietf.org>; Thu, 27 Jul 2017 08:32:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=d85xCqc2F2N2YUJ14KrAsRp2+EuPATLHzgYjhCY60K8=; b=F2lduZ+rGJff99iKeZzV0t4SgRwJ3Gi356hs/bkhxYQDoHrzBfhTsUbh/3vv4sx6ghrEuthd6x4n3kJaS98H/EP7ip4fQvc70tMYR6vM9KwfrLX07ZuYtx91zLnaItETgTnN/5rYQcoGoSe2xZtz497soR+1EYvXh/qd/4ZGSd4=
Received: from BN3PR05CA0031.namprd05.prod.outlook.com (10.174.64.41) by BN6PR05MB3314.namprd05.prod.outlook.com (10.174.95.37) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1304.10; Thu, 27 Jul 2017 15:32:18 +0000
Received: from DM3NAM05FT031.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e51::200) by BN3PR05CA0031.outlook.office365.com (2603:10b6:400::41) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1240.6 via Frontend Transport; Thu, 27 Jul 2017 15:32:18 +0000
Authentication-Results: spf=softfail (sender IP is 66.129.239.15) smtp.mailfrom=juniper.net; ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=fail action=none header.from=juniper.net;
Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.15 as permitted sender)
Received: from P-EMFE01C-SAC.jnpr.net (66.129.239.15) by DM3NAM05FT031.mail.protection.outlook.com (10.152.98.143) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384) id 15.1.1282.16 via Frontend Transport; Thu, 27 Jul 2017 15:32:17 +0000
Received: from svl-jtac-lnx02.juniper.net (172.17.28.215) by P-EMFE01C-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server id 14.3.123.3; Thu, 27 Jul 2017 08:32:18 -0700
Received: by svl-jtac-lnx02.juniper.net (Postfix, from userid 1709)	id 84F31481EE2; Thu, 27 Jul 2017 08:32:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by svl-jtac-lnx02.juniper.net (Postfix) with ESMTP id 83F094801C5	for <ietf@ietf.org>; Thu, 27 Jul 2017 08:32:17 -0700 (PDT)
Date: Thu, 27 Jul 2017 08:32:17 -0700
From: Leonard Giuliano <lenny@juniper.net>
X-X-Sender: lenny@svl-jtac-lnx02
To: <ietf@ietf.org>
Subject: Re: Next steps in IETF list email archiving
In-Reply-To: <63dd5451-73ac-9cc9-5d3a-4501aff9a285@nostrum.com>
Message-ID: <alpine.DEB.2.02.1707270820520.9841@svl-jtac-lnx02>
References: <fe950cd9-bea8-7831-046d-2f48eaaeafb9@nostrum.com> <63dd5451-73ac-9cc9-5d3a-4501aff9a285@nostrum.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-HT: Tenant
X-Forefront-Antispam-Report: CIP:66.129.239.15; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(39840400002)(39860400002)(39450400003)(39850400002)(39410400002)(39400400002)(2980300002)(199003)(189002)(53936002)(50466002)(189998001)(76506005)(2351001)(46386002)(356003)(57986006)(106466001)(81166006)(105596002)(81156014)(45336002)(8676002)(46406003)(5005980100005)(626005)(47776003)(8936002)(90966002)(68736007)(9686003)(6266002)(38730400002)(110136004)(6246003)(2810700001)(3240700002)(97736004)(4001350100001)(229853002)(69596002)(2950100002)(478600001)(77096006)(76176999)(6916009)(23726003)(5660300001)(2906002)(7126002)(54356999)(50986999)(305945005)(33716001)(83506001)(86362001)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN6PR05MB3314; H:P-EMFE01C-SAC.jnpr.net; FPR:;  SPF:SoftFail; PTR:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; DM3NAM05FT031; 1:XAk4kxtdhhyxWoXEYu24OU6j7O4bpjcXn8RAbIFA/VBmvU7tm+gIJgRpFZ3TfzFLS/8o9PSGkR7iQuM458KGbHZRJ/JhY90JH2ayIt8aUJVYcbtglRdxOfpLGFw9RKK7xo9kvOZZlXSbk9G5DAlQ7FbcvSVkKc7lw0Jcma8F2R6FtJqKZLccuOeq2gSupsTdW7JZTqpAUqP9VrP1pjplOL8W+E1D1hSXkSfB2wj5oQILGLDa+qbEgTZ+UKtd9Xis5FapKNVpN88BRRtdUHALsIPa1xYEFakylhyHXZxAt5AuV1UnmaZ3K3LWCdxX4vZdWd993bJjUFnU7EnuSt80WZ05p2wdBTL4hM9OvNSVry/wNGwdXCLybSNExXt/llQKnVViOcgfaR/MpefOWfIJMyMI6LC77VFoFyYIfUWDbppdfZn1fLzRBbcBb+vsNB9M4zdYlyUBwyLdp39SLOKAkZuTf3fkgxzc2pVzl4qQcMjiWl0OQy4ls5/HAj7wbSksTy1G94D366iiAxpMgRPWDnglCHgwwWUQPoAfaiZdpz+1IH7Gt0wBWSTwjFdqAe2WP+dvFXXNLxNUQZ1jSv94197CK6rZ+4F0Oz3K74DKmVbhQ2Oh7qzwMgCrQlUPbe3xHc/6zUcs2rVkz9EJGl6RHvpaLPjSHz0saMSGa0c8AAFeE8/2ja46mrIMZYmZoPl4x204l9I0L2Av7TyhiIFY3DiQ/Fj3Ur9LT62RywFApBz+LL6JQfTjkeWfgY3hvb7Sz5aE13NWwvGQKs0AXXwVgbRdeC8IRznUw9723LDoIvqKWpNEihIPrcijNU2Jdbih3HO21DTUyW42htXbLi3rxg==
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 8b2fdcce-76a0-448f-cd5f-08d4d504aa5a
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(300000503095)(300135400095)(2017052603031)(201703131423075)(201703031133081)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:BN6PR05MB3314; 
X-Microsoft-Exchange-Diagnostics: 1; BN6PR05MB3314; 3:RNN6Ydc9U4o4dv1g7uL3PBXXjPJMTxfSw4XnSaYHa3QSfbNz/+lKmfZglLbEXrj4oPzUI5TivrTecOH9Vs6CWY7bfa1pbw6nx8KJJfBNvB9xsm0USVAmRa1PpoKXowY1pVLZbClWGpYbuiDS1Vy7jSXY/9nqvMMCPoLbqunAZ9rwoT1Mi9128EDkDyo0xPnsjdq+SYFXY0jXilEyfMzR3GnycDnw9E95Cq1/h/L9K7FfKZzbwCBWA+UR0hzixcYW8DAW6zxWkgG4XBzvSWea1ORcZK37w0PIx5Q8DcV45j2vw4C6l+R7no1bLEno1P8mMhJDJ0iGmhIvkwE+TDaCsyg6gATPvQv6di2tL8EjcQs/OsxdS9b8xmH3elwe1UblmXON4ypddHXlOGR5UABQWstRHuiRM8ZVDnvRM6M2hDc/trQPzRXEPpTstl0RjEHIWHXLjActXRbBJMsLiZlNUnZrBnl+dVNJQB2HPezT1HHZjl+PdedcPV9TQZxY2msq/DZ88o85FipC8fyl1U23Q0fFxqrg5t8+zru5IAPm3DjOBtUGj6X/AQ8XqeksA4tciWbwXcUg5pMARUQTnHx0kU3dA89xhSRg0G+qPyqqG7NteX4I2if9nkelFSTJ/dxsUbQZB51D6zTSQLG4bhGH4BdnDZIUr6zivkF2MdDcBpiY7hgsFL/BP31EGnrRwrawhmPL4QzuOSqYmi9GJl+45LnY5SPRzLelFndFlgIoIfsUFvv+QVLgEQWMHmTgDdyPUhcwescY3cHJR6JGNdpsUo7Mti7PUO3I/cOULga48tWsUM35PfCj7VJuZPY5k/DiqBxb2uJvoOr9Kj9VkNlxmAUuYarJJ+sasig4OEg/e21Y3z5z7mvhFAY/dFXbZoXO9W9Ep7AoyRvRHLgX88+XwA==
X-MS-TrafficTypeDiagnostic: BN6PR05MB3314:
X-Microsoft-Exchange-Diagnostics: 1; BN6PR05MB3314; 25:LMT+04H/+NsVMh9f2vDhl5Zk5w86bvMcoIMMH2mIAkGzj/qw6kCeRKSKWvdC+kX5w1MzgFk5qATMkw4eB/dd76n/i7OgmTyzO1FiEy1sR3kd8P2iY8gMZsQ7E/khxz9uFcCq0ZDsvl/4IWKBanAnNp3ab3P6G3eTV2d+9LzV7xygv/veGUw4DkS6MXlta0sS+ZsWtVt95YjX2f6StwN0RkmLY01Qcc31S7WO6y6e4a1n3hyIlBXqsObXZUNm9YBE0DseW4gIutynCEVo0qafwaN6ZU50dslxyRpZuW74hdEImo4gTzPc4ScI8Y/deHcFpxAW+oliQzyLeRm62i7cL78coHsVpbHE41xl8yPxDHOe206ikFdjFBEqD3HLFSY5wNhRwO7w8SOY2rfRlZJRqHuYODYAT4Fd4+2kqRJdhalatA2LqV8MLWA4sWerPJPqQphTsybpF/56muBWhiWHQ/Kf1vXDwWY0VUsbqV4X93R+CtRIqLW71KKUxPMlxumhJoSe7LyRcNCq+pn0DCYOPR9nwLz5oQxWftkSqUw13Nggw5+y8Y/5++xurPqvEGRCJ2csOtdaAOfTFHxN7a7gn/Z3cs9LRPKH3Tq6RtwUegVGoj2yJkOVT08PHvjI6TCTIQQ2WZVm29XRU2CfOeUqCmnQ3QcwC1Ubjv20v4i4oV6imjnX+zf1YfbtlZ7cKQZNhMvutq4KTSAPa6yNphrkgLczjGqqTQr2Ao73GIF3DNrke9tFWucpawKjBL0sJ8Zs9wDqkywX6luVTx/+6fCDYOphube3k0X4IYqMZziNqiJSiuvnNcWiuNQ0Fxe+n7GIPTfe2huTDTPTaceY2nS/KnCiMSlfqivCWRvM/Blql2VmIbWc1CquFc466sPY+m7kln7HISwsyc//JBqBxUBnkmYVIWw+GSzP8x8i8hw1prI=
X-Microsoft-Exchange-Diagnostics: 1; BN6PR05MB3314; 31:PDPGZt91C0I8mH/RpbuqTVxKwPdK3Sx0b1oMCHBC0h8jTHuNMafvSk1xKFelFFenRqbKExT3t8AOhRM/pFqMxkMfyD491mvr5wJ2vF2GTo/Tlw9FM2I7Ns/PqxHTbPm2jgpAFIv8XuEwosTYv7OW4tUCfYDyJM1aWZwNgAPo4+NFOkrZY1J9Djke7wxvLLNQ/oEhJd/BkmOnXD9VdWBxqADS8alg81jwDk4g7VVMhH94ex3gynpdvbNKnt5Mils/Pu40wbU1mTB4Td3Kua1QjgQO2J2U3FgnmeSxMikrfNsESMKM7a2HstWCqSb0DeHQgjwi7OGaZ/k3/fU5rwhN8JhqvT5m+WXylqqwl1iSXRVDxD6iYXrf4TMuMengNRmEZJPJnPRZwDM16+eBu0Qf+2IJWJvWfEsWW6eL5Lwjp+H6b77T3b5FN6SXMmCr2pf4hX8YUoRCBpFpGObo8z5xXu8EaqszPp2k9lCyuUTM9wW+9TI54uCLtYYda0dlF8ycMrKsPW1S6GVLLeHvLRbNXaPpEZVwtTVp6F4GxcEBED5gOjmLNTjvoEwkd4X5/vOZELOvkF4kNRU5Z1SKsJwtR0nHi74jo9cYlyS1bUtY83tePMlq2x4LPRlWPOCWtTNrmGUEuzwLEjg5K2m1gLtUMbSzRdvc6rjQ5lL9iAulm8BlYY6BIgJam06fM8IvbCPereZ0sK7id7eqg09XEGczoA==
X-Microsoft-Exchange-Diagnostics: 1; BN6PR05MB3314; 20:v7AWRR65HBeds2wReGwiFAAwflLiukSlfFeAFZ90T5TWj6aiCp3YtvL7aJy4Lk9Fr8oe9rvkPCy3S7DP8k1TEEjQ6T/6Wt/aEgoNy8Yo4PXseT4RXfMLRdXRvcaVCfymSpGXRXEA4Guo0d5s838GryPqPi+Sa2DNpMTndX4cFDXQt2PU4MAjmK5lHnL1F7wcT+b0ob8Lj7wzn0F4iPmqpnOj4W3xIJEZLMuEhkv+5Qbv4QjOpOVougzaUieU18Uy6pOuRruqOi9qVDbnth9Jv5RCJYgZEfDua6h8DRZH4k6Zpou8dKllI1Ewn8ShqWUtUNJxa+YdXrUxU42hY/ZxA6av6t3841378ISLHVCItcSKgklTJIIV0uMOaL+5kf+3JB09RKFnzUWOd9Bs5SfHmVcXa5KK65iicblzIBN/e5ZnuagceMFnXW0kvWJ/1uxaVz1UL4/m6HzJpKy0VFxzdXfaauL9FJT/mFg9Hu0JQEmOyjyWnpqFIWmZ8kB9PmGR
X-Exchange-Antispam-Report-Test: UriScan:(20558992708506)(788757137089);
X-Microsoft-Antispam-PRVS: <BN6PR05MB3314F4DBF77462DA5F5355FEA4BE0@BN6PR05MB3314.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(13016025)(5005006)(13018025)(93006095)(93001095)(3002001)(100000703101)(100105400095)(10201501046)(6055026)(6041248)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123555025)(20161123560025)(20161123558100)(20161123562025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BN6PR05MB3314; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BN6PR05MB3314; 
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; BN6PR05MB3314; 4:HxjFPIhL6XWOEflDFzqIb/kQDMHfcQps6zSMNgXOw1?= =?us-ascii?Q?vZIl9PjOqRbJlg0YWX2epxV+g28mmVybRPuCl5ljWOhZIeORrqbRswOiwvDY?= =?us-ascii?Q?cjVA1KhQtRIihIJp7DsbHCqAG/wd2+ywJ7xQDP/7//TLpY9ws6xfsZ/nfYo5?= =?us-ascii?Q?9iN7NYgtitOuTqAhx4tYq1bZkb4Mt/u6tnSatB3HLVhrReRxybbXxfJuVwZK?= =?us-ascii?Q?tf3kcGwqlkYaOuI57GrWSxnJmo+C6qEEA4MvO1gStHQ2qzd1yeVNMVf5KPDT?= =?us-ascii?Q?Sbz2eBy5Wp8la1pIe+AaMHxtm7vngq+vWFog9jDXMWN52F/g9UFG3XXcAExJ?= =?us-ascii?Q?BN/9u+ZfOmLrqdhEE/T9ofhcuSpdBMyUSBEFQ4/zoLH3gOIrqBz9+q0O/hIm?= =?us-ascii?Q?ZBPlqs18flE1Pim2SjcZ+QT+c0Bheo3V3p+WXMznaGdBnHc3ZyaSS9S64pE+?= =?us-ascii?Q?zYrgsIn88rOcyZ5U6HM/nbvE4IRcZEBhrm9ahbh+dIVOhRhubKJK+08dRF1Z?= =?us-ascii?Q?fVfPw4hqg5ZiUv+RGrl0jLWrjoL9yUl0/QeXe4rY9Nr1mZyX9vvCYRlLOe4w?= =?us-ascii?Q?lcvwgBE8ACuI/oHyYl31aDdNRLiS0TgJ6Ta2w0h+v590R2p+yYgWXpACD/cU?= =?us-ascii?Q?MZjW4oe1JQ9Sq0qVC/IN3DRUk8rwZHr4o+eW88BcRppFVQAkuwqFQ7BISqY/?= =?us-ascii?Q?n9jwLyzmlAy02J39+nY5NMzrNutiUducikb7NZeq/jFuc+pnwIiVNdXmkMto?= =?us-ascii?Q?mn4RuotU5pyOl1K8WB6+lA41qgrw0Tv95hWrrOMEsGPK2xG9c7n59B61GLhU?= =?us-ascii?Q?VTLLastqJ+odrJBaa3SjMgW6Jo4waX1zk8Q0gwtUlDp4D+swx2CH2Ra+dtxb?= =?us-ascii?Q?z+x0nLpUT0jK/1VIZMtEHqYjNDBuecdmEhZEAbsGcNzvNipk+AdpHzwI9QLI?= =?us-ascii?Q?gsEiS8DhZs6pRixq1daixLDZZcLPaS5keHZaiUfzeXLGYYA8qY4zm4mJE6dw?= =?us-ascii?Q?+5uljpRDmubitcbPFahDnPZf/9DtfXHyt4v1RIAvbwJ13WsX5vO0RyMnRXWG?= =?us-ascii?Q?sLvoWjrns/0Hvxia/S1qDz0auT7N1mJ59BV9VuQdXoCpLIFn2BqAPzpqpSKB?= =?us-ascii?Q?uomGaOpS4Xiq9+Kvn7eEg/csPJTbce5nDnEuUDGF71BwP/nx9dA/RfN6kHgE?= =?us-ascii?Q?+lq3Ixw/f+2AgoMXsGjCfOLZcZiHo4Q+lFO8xaCZqPI7QLTnJZrVRAjVU4pA?= =?us-ascii?Q?PZnxGhjhBCiBXmMNV12kAIfmNl8egluGbnM+bm?=
X-Forefront-PRVS: 03818C953D
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; BN6PR05MB3314; 23:h7OJsoWFn1QmhlhJjaS3LjXYUBFoZEZ75QE8Fs0rL?= =?us-ascii?Q?ZYibKegdkqJ71J50LV+RUgHQeEydvFyyKggykjdwKgFT87mLIsOHzjJsUbgW?= =?us-ascii?Q?GjJL3KWxodEYMVqd2Rc/5FsfjXHvlGtIUxn/ndgnkiCRZANOKrrOLANdI/Md?= =?us-ascii?Q?cykMdChLxPjKnfGzRwHxFCa2rI4mAfkyiwZLNMC6nTEaaOwjdpgR0kzut2EB?= =?us-ascii?Q?KVkVBe2Ds/s/eZeji0oI5NILL3n99o/SLexJK1hp5sjD9ubo9JGTNw7av51P?= =?us-ascii?Q?oHzYu03eD98gqCUH3kMtkqq0m+2nd56+VMyZfVuEwfaHmpExmO/F0dHtmCAP?= =?us-ascii?Q?eRu5YRdd6SqDBLCKKdb4Qntr9QnBpvXr4KklgTwUN6iIn6OvwDkGBNuZdNE2?= =?us-ascii?Q?cD4kPQTjdOd91yeeZbp0WBqINdBs0C0OxTLLMPrNfBtVCcTOlfQFXfVUSq+W?= =?us-ascii?Q?YIdZEfHwMZOWgCNmB5zhzvUEIcJz+A1qZdh5Y3vkaUfchrc3TvSU8XtDcngA?= =?us-ascii?Q?4kBBDYVFnbjbjy6WjzVLmA8jGsS9wJRUlseAS53A1CewCf9FQ5DQCx4uW18U?= =?us-ascii?Q?QMsa1GqcVcayJx3DtvhGEy/Bazk60njq/8aGwzHIFSHvPv4A9j7J2axGk5I4?= =?us-ascii?Q?787hSjFcq8SW5V7xGMqWy7ths34rjZqMxGLUzTDmiLveFGkyseOHVwReXils?= =?us-ascii?Q?CpTaZeCTLylfmJra1VfYXjjFWDKX33wakza83pUwtaZeb77XRYxq+/+Me0Pj?= =?us-ascii?Q?sv0GbmJMV0j+XI8VhFEPvhItriat2b8YjpJVYhrBSKH07W+nezKQUp+irhSx?= =?us-ascii?Q?Dxx7tgA0QGMyRZC2uOHitWwxqqTrH1UTibNkayteQz65fqYvNH3ZA9k1SSNo?= =?us-ascii?Q?+GNNyd3Hdwhi+Dx3WPvZFslcZBowi9snBSoJMgVamrfpR8VHixG3x8wS9KcK?= =?us-ascii?Q?kwUCQXyqsJJOp88ecTFKuJsA69ZbHzQhAFdiMYMztchn+XdADHs1DJno7bJb?= =?us-ascii?Q?tZRsE53vk5Mb1DB10UoegzGBbT60AF5rs03enl8OLjE+FiGYzIDXdeJw0Rqm?= =?us-ascii?Q?kCwdM29J3SKJZx9sFDotgkED1e+hZVOgRENDLp7X4rb2tZD5C/jSAFbRyViV?= =?us-ascii?Q?4rR6uVRBv7NmQvCDBQUrhnmBkHtkJbqhxOYDRgRouXZrE5tXB1SEEMPjiKs0?= =?us-ascii?Q?jLd+itm7LoHl6Uo3Pc6hCAcB/etgz25FzhjrhwmK2VJprh+nxI3uEfcYZZd+?= =?us-ascii?Q?NE2+3YQub1zkVC75au/fFrRUVC8gYPPNDzbemnUYYJjUc0TqJO8Xlfusvxwp?= =?us-ascii?Q?vnmpVtrdvSS0n/Y3cj95j4MqIalzfV7R6q2utdrm2SHVSNEp9MQn/TuxNU/D?= =?us-ascii?Q?1E9HBFBCUiKVeUf/ybdnkWePKZqeR1H9kyISVKyl2v49MvZxd76KtRul2FrP?= =?us-ascii?Q?pgPhyvDuw=3D=3D?=
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; BN6PR05MB3314; 6:zi7gR2DCTWkoxhWxkiq/YCEyjK9cnnW/Ba0a0mvl59?= =?us-ascii?Q?COzmDUqMT0MrX9TzRW+QpwYeeMmvtlcKzIVNe58AnLIh2yQpS505K9/fTFuB?= =?us-ascii?Q?b4UCqF9r1j27QlszrAXThwktN5brma/SQAUQbM2iiHDVFB0mNfub+xvboNXb?= =?us-ascii?Q?PIlZFjGz1HMq8pi3tZ6GEskjYESMfNbBKJK9qkUz6UWJum8xL9UJW+SixkgD?= =?us-ascii?Q?P0MlCTIGNHPFldMXbNoGAlO5+BWIC2mqU7goPICoypGS7I0TqrwOX7DJ9bF6?= =?us-ascii?Q?RQX2TjQKy2MWE9BoXgjWDRYwEDQ/H+qHJhdP4WRTUCxELS0UswtaoGhSxyLu?= =?us-ascii?Q?Ww5U/W1/xMsdkfzxhj11bAxUzVhojeJYhRZz5Ryc8SA+beo7YkqFDwIuCqig?= =?us-ascii?Q?zTNG7pDDov+jIhaA1rW4xc459qyNjF2xi9U5/b15wuyw6Ic3tf5PhGMd6P4H?= =?us-ascii?Q?6xuh+sdkhtdg2IO7MGTDXr4FfRucQptyq2aS2Xzq3cCO6l/8bF8w3fo1YQxo?= =?us-ascii?Q?KUHepIx3bnc5NzJGfSwrVROfvXqYeAsGvJa4KcgIsUc8WrgSVPJBpXrJHWiE?= =?us-ascii?Q?ouvDNVRhAGIZ5g1O+tJ7ajAEcAywV3zOHtqnjZViiJm5MuAgiVbmXIS4Ga/h?= =?us-ascii?Q?uW76OqMlyn6opEkIaqC4z2uKRTeOYCoqgeuFg0Tb2hVpSqZWHBrKnpKQtrVT?= =?us-ascii?Q?S3f6/3fB3pKMrJaN+Hmkn75AdTqWdXqlgtHlJJ3X05kd4tv3xDdHh9lZt6my?= =?us-ascii?Q?QORKjVlrNPCCZt4b5cTHz9FR4NPwcudrKNZCVp5qafOgLHAp4zHoHvDCG6L+?= =?us-ascii?Q?o5iGw9zrjKkuVKMiewzZEOSGrVzi095bua6s5l9A8ZW6Gro1hO4JEf1D3Ali?= =?us-ascii?Q?LzgHBL4nUXmzstMa8PTBasqj9Y+Z1Gtwnc3UjdD+25mK2Efh5brZ7EydY/+3?= =?us-ascii?Q?/Pcd4B+nayJ4aIpDviOkqjxlc6cSbpYYB2lP1Mk/j0Gt5M61gXrmzh5HmMUI?= =?us-ascii?Q?/b1Cvg9BtCGanUkXDwmL37?=
X-Microsoft-Exchange-Diagnostics: 1; BN6PR05MB3314; 5:MHeuwbf2SZBl0Vo+4EU0X85aqLgigPwlSE3TAht63+RZhXQYTZJtnF0XfUP4IkllOLtIUUUU4zT/aOKBs2SvHptZgQ3FiXEbHLEk2nH/XAokREon2RnFBRPm7+M+21n0GxyVFrp8rmTZW3kak9X2dNUac7Bre27E3TxLigbuA7yf65fiklUPWvo0/zQanQDs+v4K31M3Wp3psrnNSgk3jMiuMGWd6RlkR4jrhPIfojSWLSp7sBb99SuweBpgjxgQeZYnc88zOnq7cFF5unWHAcUbJUW9oLccMyhMNaqgNYrt60wWo77jmRqmC8QKUKeuO66uGO9vWjPVZ/QPu0phWfsWiHwh1PkxfkMcuBeW7RC7bgJHo67DJDeGrpj09fmDyeG2flneFRS+msscjXRbDstJGthoXXc5oBA+WROVflNu0flAcTdvkFSWPfzcXrBu7IH3N4LhjITsTvUighdbFvOtoQDp0fvZr6PoFsndz39XUg86ykU4oxGydrE5HDRy; 24:u8Szor4ZV87jSgpeIW/ptX780bJkKpu0Qzo8DnfNlxsC7mkAFXcpenSMcYBlYTgOSkwRbjCsLVKveYDloX8E0tJO5Vcu67wGsrzILFapqA8=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; BN6PR05MB3314; 7:hpu4HzI/+K8TDTQWk16eiC8bJwEojUuUZcixUWii9zZxmtW25Y3sNUZz1djzgMcxUjEd5VRvJHWWofuRu2y+FgKWvhL9Rr31gBTnpYos/f3rRcMGTKVa8O3ZhYe8wQBOkLt+ChAV5kkYoVT3P8Yc+7CfYMZ4VgMfYCbnOQIkN7qxF62LknfMTfuvgw2lUkgLDsWN4JpnGkewQnaWluiNL9sRnCL5regQDn3ot2a3ufkKdlgqW2V+aHUEyTpZPgWYBUefAVoOW7bNgFBAeQcyto3SfEs6VFs0YV/gxhJ4LbnvMag3XqqNxgmET3S8FqhgXUI+lqw3DkjzQHD98YoNU3SdyCP1M2qH2tflTT1Ul8iXvA2FFHVgOjTzlxIsPAIIMH9ayDJ6tvvhwgmTHm61Hj/WqqlwdYUhkAf+Iuj17l7AX69kUXmJM8BfVPKB+stMfcQCQfZkQJaU8IFhmKnFENIdH0vvbD58c3xiSFWAY+9/+GN12zP1wE/TEOx2w4S0pjPqtvl3hJ4dqUWWu+BIq0/CAk6e0Ok1+6NOMhdHAVXEWMbzqKDxj4asdhZZNyi6Rl4DWG5/z0yYTulc850hhfZhRBGisPMXnQzWOlasSbideUNZt0Rix3wDslRQJCjfzHNnZ3vSsQu7LssrahPBY8sd+kFliOFRDITJcURLQ3T3jJdLvUKLQxYg7e3FIEd2K+2G0pfhofthJgJBbFJ1fkRF2gMbX2UdKlSRXZVZE8zhwk5Up7MC3YpWV6QP7cU9DXrkecu52nBX1/E1whLfrR0cmfKyCHqgMlqCBpFQRXM=
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 27 Jul 2017 15:32:17.9651 (UTC)
X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.15];  Helo=[P-EMFE01C-SAC.jnpr.net]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR05MB3314
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/41JKXPSgCXhJO4ulZA9tqWidw8o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 15:32:21 -0000

+1 for finding a way to keep both UIs.  I find these to be complementary 
tools- mailarchive.ietf.org is great for searching content and filtering, 
but my linear/non-Millenial brain finds the Mhonarc UI much easier to read 
and consume.

Do we really need to remove messages from the archive (sounds so 
Orwellian)?  I'd rather have spam in the archive than lose the Mhonarc UI.

-Lenny

| -------- Forwarded Message --------
| Subject: Next steps in IETF list email archiving
| Date: Wed, 19 Jul 2017 09:43:24 +0200
| From: Robert Sparks <rjsparks@nostrum.com>
| To: ietf@ietf.org <ietf@ietf.org>
| 
| Several years ago, we identified a set of issues with the way
| we were archiving email messages and new functionality that a
| searching and browsing solution should contain. The initial
| requirements for improvements were captured in RFC 6778, and a
| subsequent round of requirements were captured in RFC 7842.
| 
| One of the key issues was (and is) related to management of
| the archives.  Currently if a message has to be removed
| (rare, but not as rare as we would like due to spam hitting
| some lists), the secretariat has to touch many places. One
| of those is Mhonarc. Touching one message there involves
| changing many files (any other message that contains a
| navigation link to this one, and the index files that speak
| about the message).
| 
| As we built the new systems, we've targeted having one source
| of truth for the archives. For instance, as we added IMAP
| access to the archives (RFC 7017), we ensured that it was
| served from the same bits used by mailarchive.ietf.org.  It
| has been our expectation from the beginning that
| mailarchive.org would replace the Mhonarc archives (see
| section 2.7 of RFC 6778).
| 
| We believe we are getting close to the point where we can
| make that replacement. The rate of bug reports and feature
| requests for mailarchive.ietf.org is slow. (As we do for
| the datatracker, we plan to continuously improve the
| mailarchive interface. We know already of some things that
| need to be improved when viewing on phone-sized displays.)
| 
| If you use the mhonarc archives heavily, and have not yet
| explored mailarchive.ietf.org, we encourage you to do so now,
| and report any difficulties you find. We recognize that the
| experience is different, but many of the RFC 7842 driven
| improvements focused on minimizing the transition pain.
| 
| We have successfully tested the code that will redirect all
| existing Mhonarc URLs into the mailarchive using the
| testlist.
| 
| We are not going to make this transition immediately, but
| we do plan to make it more in the near future than the far
| future. Please help us identify any additional things we can
| do to minimize the disruption to your current workflow.
| 
| RjS
| 
| 
| 
| 


From nobody Thu Jul 27 10:02:49 2017
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EA5C131D22 for <ietf@ietfa.amsl.com>; Thu, 27 Jul 2017 10:02:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 qzExPF-dzOzb for <ietf@ietfa.amsl.com>; Thu, 27 Jul 2017 10:02:42 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7BB4131F6A for <ietf@ietf.org>; Thu, 27 Jul 2017 10:02:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id EA7CB30056B for <ietf@ietf.org>; Thu, 27 Jul 2017 13:02:38 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Vp1IT-y8Ubo2 for <ietf@ietf.org>; Thu, 27 Jul 2017 13:02:37 -0400 (EDT)
Received: from a860b60074bd.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id 558A5300429; Thu, 27 Jul 2017 13:02:37 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Next steps in IETF list email archiving
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <alpine.DEB.2.02.1707270820520.9841@svl-jtac-lnx02>
Date: Thu, 27 Jul 2017 13:02:37 -0400
Cc: IETF <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A80A02D1-D9BD-453C-A97A-5381B308939B@vigilsec.com>
References: <fe950cd9-bea8-7831-046d-2f48eaaeafb9@nostrum.com> <63dd5451-73ac-9cc9-5d3a-4501aff9a285@nostrum.com> <alpine.DEB.2.02.1707270820520.9841@svl-jtac-lnx02>
To: Leonard Giuliano <lenny@juniper.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/t0ni0lN7hnvevDUlEffPp_N8BZk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 17:02:45 -0000

 In the most recent release of the mail archive search tool, many =
different ways of sorting the threads were added .What about the Mhonarc =
UI is useful to you?  Is that view not available in the recent release?  =
Just saying that your non-Millenial mind finds it easier does not help =
figure out the best next steps.

Russ

=20
> On Jul 27, 2017, at 11:32 AM, Leonard Giuliano <lenny@juniper.net> =
wrote:
>=20
>=20
> +1 for finding a way to keep both UIs.  I find these to be =
complementary=20
> tools- mailarchive.ietf.org is great for searching content and =
filtering,=20
> but my linear/non-Millenial brain finds the Mhonarc UI much easier to =
read=20
> and consume.
>=20
> Do we really need to remove messages from the archive (sounds so=20
> Orwellian)?  I'd rather have spam in the archive than lose the Mhonarc =
UI.
>=20
> -Lenny
>=20
> | -------- Forwarded Message --------
> | Subject: Next steps in IETF list email archiving
> | Date: Wed, 19 Jul 2017 09:43:24 +0200
> | From: Robert Sparks <rjsparks@nostrum.com>
> | To: ietf@ietf.org <ietf@ietf.org>
> |=20
> | Several years ago, we identified a set of issues with the way
> | we were archiving email messages and new functionality that a
> | searching and browsing solution should contain. The initial
> | requirements for improvements were captured in RFC 6778, and a
> | subsequent round of requirements were captured in RFC 7842.
> |=20
> | One of the key issues was (and is) related to management of
> | the archives.  Currently if a message has to be removed
> | (rare, but not as rare as we would like due to spam hitting
> | some lists), the secretariat has to touch many places. One
> | of those is Mhonarc. Touching one message there involves
> | changing many files (any other message that contains a
> | navigation link to this one, and the index files that speak
> | about the message).
> |=20
> | As we built the new systems, we've targeted having one source
> | of truth for the archives. For instance, as we added IMAP
> | access to the archives (RFC 7017), we ensured that it was
> | served from the same bits used by mailarchive.ietf.org.  It
> | has been our expectation from the beginning that
> | mailarchive.org would replace the Mhonarc archives (see
> | section 2.7 of RFC 6778).
> |=20
> | We believe we are getting close to the point where we can
> | make that replacement. The rate of bug reports and feature
> | requests for mailarchive.ietf.org is slow. (As we do for
> | the datatracker, we plan to continuously improve the
> | mailarchive interface. We know already of some things that
> | need to be improved when viewing on phone-sized displays.)
> |=20
> | If you use the mhonarc archives heavily, and have not yet
> | explored mailarchive.ietf.org, we encourage you to do so now,
> | and report any difficulties you find. We recognize that the
> | experience is different, but many of the RFC 7842 driven
> | improvements focused on minimizing the transition pain.
> |=20
> | We have successfully tested the code that will redirect all
> | existing Mhonarc URLs into the mailarchive using the
> | testlist.
> |=20
> | We are not going to make this transition immediately, but
> | we do plan to make it more in the near future than the far
> | future. Please help us identify any additional things we can
> | do to minimize the disruption to your current workflow.
> |=20
> | RjS
> |=20
> |=20
> |=20
> |=20
>=20


From nobody Thu Jul 27 10:14:21 2017
Return-Path: <iab-chair@iab.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61076131D15; Thu, 27 Jul 2017 10:14:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.898
X-Spam-Level: 
X-Spam-Status: No, score=-2.898 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, HTML_MESSAGE=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 8aCZNkHOX47R; Thu, 27 Jul 2017 10:14:17 -0700 (PDT)
Received: from thornhill.mtv.corp.google.com (unknown [IPv6:2620:0:1000:4200:80e9:a65d:dd2c:b60f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id EC8CA131CFD; Thu, 27 Jul 2017 10:14:16 -0700 (PDT)
Subject: Deadline extended: Call for Participation, Workshop on Internet naming systems
From: IAB Chair <iab-chair@iab.org>
To: ietf@ietf.org, ietf-announce@ietf.org, iab@iab.org
References: <d22eeed9-b3ab-71ab-8f8b-fafd2a3ffc52@iab.org>
Message-ID: <5b5d34d5-859c-51eb-632e-e8ebeb95d824@iab.org>
Date: Thu, 27 Jul 2017 10:14:16 -0700
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: <d22eeed9-b3ab-71ab-8f8b-fafd2a3ffc52@iab.org>
Content-Type: multipart/alternative; boundary="------------03055F6ECFA1CFA196E912EB"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gYMvafje02EWr-U_pze5632BtPU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 17:14:19 -0000

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

Given the change in date for this workshop, a number of potential 
participants asked if the deadline could be extended.  In order to 
facilitate the broadest possible participation, the IAB has agreed.  
Position papers will now be accepted until August 11, 2017.  The program 
committee will notify accepted participants as soon as possible after 
that, in order to allow for travel arrangements to be made.

A copy of the solicitation and the announcement of the updated dates is 
appended below for your reference.


regards,


Ted Hardie

for the IAB


> When the IAB issued the initial call for participation for the 
> upcoming ENAME workshop, several folks pointed out conflicts for 
> potential attendees on the proposed dates. Among the conflicts were 
> meetings of the DNS Operations, Analysis, and Research Center (OARC),  
> ISO's technical committee on coded character sets (ISO/IEC JTC1/SC2),  
> and the Information-Centric Networking Research Group (ICNRG).  After 
> considering these conflicts and others for the times near the original 
> dates, the IAB has decided to change the dates to October 10th and 
> 11th.  Microsoft has kindly offered a venue in Vancouver, British 
> Columbia  for these dates.
>
>
> Note that the new dates immediately follow both Canadian Thanksgiving 
> and the U.S. Columbus Day holiday.  While this represents a different 
> conflict problem, the IAB has agreed that the overlap with OARC, 
> ICNRG, SC2, and the related meetings were serious enough to accept the 
> trade-off.  In order to minimize the impact of holiday travel to the 
> extent possible, we intend for the workshop to be a half-day on the 
> 10th and a full day on the 11th.
>
>
> The updated call for participation is below.
>
>
> regards,
>
>
> Ted Hardie
>
> for the IAB
>
>
>
>
> Call for Participation
>
> IAB workshop on Explicit Internet Naming Systems
>
> Internet namespaces relyon Internet connected systems sharing a common 
> set of assumptions on the scope, method of resolution, and uniqueness 
> of the names.    That set of assumption allowed the creation of URIs 
> and other systems which presumed that you could authoritatively 
> identify a service using an Internet name, a service port, and a set 
> of locally-significant path elements.
>
> There are now multiple challenges to maintaining that commonality of 
> understanding.
>
>   * Some naming systems wish to use URIs to identify both a service
>     and the method of resolution used to map the name to a serving
>     node.  Because there is no common facility for varying the
>     resolution method in the URI structure, those naming systems must
>     either mint new URI schemes for each resolution service or infer
>     the resolution method from a reserved name or pattern.  Both
>     methods are currently difficult and costly, and the effort thus
>     scales poorly.
>   * Users’ intentions to refer to specific names are now often
>     expressed in voice input, gestures, and other methods which must
>     be interpreted before being put into practice.  The systems which
>     carry on that interpretation often infer which intent a user is
>     expressing, and thus what name is meant, by contextual elements. 
>     Those systems are linked to existing systems who have no access to
>     that context and which may thus return results or create security
>     expectations for an unintended name.
>
>   * Unicode allows for both combining characters and composed
>     characters when local language communities have different
>     practices. When these do not have a single normalization, context
>     is required to determine which to produce or assume in
>     resolution.  How can this context be maintained in Internet systems?
>
> While any of these challenges could easily be the topic of a 
> stand-alone effort, this workshop seeks to explore whether there is a 
> common set of root problems in the explicitness of the resolution 
> context, heuristic derivation of intent, or language matching.   If 
> so, it seeks to identify promising areas for the development of new, 
> more explicit naming systems for the Internet.
>
> We invite position papers on this topic to be submitted by July 28, 
> 2017 toename@iab.org <mailto:ename@iab.org>.    Decisions on accepted 
> submissions will be made by August 11, 2017.
>
> Proposed dates for the workshop are October 10th and 11th, 2017 and 
> the proposed location is Vancouver, British Columbia.  Further 
> logistics will be provided to selected participants.
>
> Ted Hardie
>
> for the IAB
>
>


--------------03055F6ECFA1CFA196E912EB
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>Given the change in date for this workshop, a number of potential
      participants asked if the deadline could be extended.  In order to
      facilitate the broadest possible participation, the IAB has
      agreed.  Position papers will now be accepted until August 11,
      2017.  The program committee will notify accepted participants as
      soon as possible after that, in order to allow for travel
      arrangements to be made.</p>
    <p>A copy of the solicitation and the announcement of the updated
      dates is appended below for your reference.<br>
    </p>
    <p><br>
    </p>
    <p>regards,</p>
    <p><br>
    </p>
    <p>Ted Hardie</p>
    <p>for the IAB<br>
    </p>
    <div class="moz-cite-prefix"><br>
    </div>
    <blockquote type="cite"
      cite="mid:d22eeed9-b3ab-71ab-8f8b-fafd2a3ffc52@iab.org">
      <meta http-equiv="content-type" content="text/html; charset=utf-8">
      <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">When
          the IAB issued the initial call for participation for the
          upcoming ENAME workshop, several folks pointed out conflicts
          for potential attendees on the proposed dates.  </span><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><span
class="m_3425431854733555235gmail-m_-4759927563509228757gmail-c0"><span
style="font-family:&quot;Arial&quot;,sans-serif;color:black">Among the
              conflicts were meetings of the DNS Operations, Analysis,
              and Research Center (OARC),  ISO's technical committee on
              coded character sets (</span></span><span
            class="m_3425431854733555235gmail-m_-4759927563509228757gmail-c0"><span
style="font-family:&quot;Arial&quot;,sans-serif;color:black">ISO/IEC
              JTC1/SC2),  and the Information-Centric Networking
              Research Group (ICNRG).</span></span>  After considering
          these conflicts and others for the times near the original
          dates, the IAB has decided to change the dates to October 10th
          and 11th.  Microsoft has kindly offered a venue in Vancouver,
          British Columbia  for these dates.</span></p>
      <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><br>
        </span></p>
      <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">Note
          that the new dates immediately follow both Canadian
          Thanksgiving and the U.S. Columbus Day holiday.  While this
          represents a different conflict problem, the IAB has agreed
          that the overlap with OARC, ICNRG, SC2, and the related
          meetings were serious enough to accept the trade-off.  In
          order to minimize the impact of holiday travel to the extent
          possible, we intend for the workshop to be a half-day on the
          10th and a full day on the 11th.  <br>
        </span></p>
      <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><br>
        </span></p>
      <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">The
          updated call for participation is below.</span></p>
      <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><br>
        </span></p>
      <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">regards,</span></p>
      <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><br>
        </span></p>
      <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">Ted
          Hardie</span></p>
      <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">for
          the IAB<br>
        </span></p>
      <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><br>
        </span></p>
      <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><br>
        </span></p>
      <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><br>
        </span></p>
      <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">Call
          for Participation</span></p>
      <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span>IAB
          workshop on Explicit Internet Naming Systems</span></p>
      <p class="m_-7295555480336933649gmail-c1
        m_-7295555480336933649gmail-c2"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;height:11pt;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"></span></p>
      <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span>Internet
          namespaces rely<span> </span></span><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">on
          Internet connected systems sharing a common set of assumptions
          on the scope, method of resolution, and uniqueness of the
          names.    That set of assumption allowed the creation of URIs
          and other systems which presumed that you could
          authoritatively identify a service using an Internet name, a
          service port, and a set of locally-significant path elements.
           </span></p>
      <p class="m_-7295555480336933649gmail-c1
        m_-7295555480336933649gmail-c2"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;height:11pt;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"></span></p>
      <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">There
          are now multiple challenges to maintaining that commonality of
          understanding.  </span></p>
      <p class="m_-7295555480336933649gmail-c1
        m_-7295555480336933649gmail-c2"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;height:11pt;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"></span></p>
      <ul class="m_-7295555480336933649gmail-c3
        m_-7295555480336933649gmail-lst-kix_vlchuldijmo2-0
        m_-7295555480336933649gmail-start"
style="padding:0px;margin:0px;list-style-type:none;color:rgb(0,0,0);font-family:&quot;Times
        New
Roman&quot;;font-size:medium;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial">
        <li class="m_-7295555480336933649gmail-c4"
style="color:rgb(0,0,0);font-size:11pt;font-family:Arial;margin-left:36pt;padding-top:0pt;padding-left:0pt;padding-bottom:10pt;line-height:1.15;text-align:left"><span
            class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">Some
            naming systems wish to use URIs to identify both a service
            and the method of resolution used to map the name to a
            serving node.  Because there is no common facility for
            varying the resolution method in the URI structure, those
            naming systems must either mint new URI schemes for each
            resolution service or infer the resolution method from a
            reserved name or pattern.  Both methods are currently
            difficult and costly, and the effort thus scales poorly.</span></li>
        <li class="m_-7295555480336933649gmail-c4"
style="color:rgb(0,0,0);font-size:11pt;font-family:Arial;margin-left:36pt;padding-top:0pt;padding-left:0pt;padding-bottom:10pt;line-height:1.15;text-align:left"><span
            class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">Users’
            intentions to refer to specific names are now often
            expressed in voice input, gestures, and other methods which
            must be interpreted before being put into practice.  The
            systems which carry on that interpretation often infer which
            intent a user is expressing, and thus what name is meant, by
            contextual elements.  Those systems are linked to existing
            systems who have no access to that context and which may
            thus return results or create security expectations for an
            unintended name.</span></li>
      </ul>
      <ul class="m_-7295555480336933649gmail-c3
        m_-7295555480336933649gmail-lst-kix_ykgz29z81s2h-0
        m_-7295555480336933649gmail-start"
style="padding:0px;margin:0px;list-style-type:none;color:rgb(0,0,0);font-family:&quot;Times
        New
Roman&quot;;font-size:medium;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial">
        <li class="m_-7295555480336933649gmail-c4"
style="color:rgb(0,0,0);font-size:11pt;font-family:Arial;margin-left:36pt;padding-top:0pt;padding-left:0pt;padding-bottom:10pt;line-height:1.15;text-align:left"><span
            class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">Unicode
            allows for both combining characters and composed characters
            when local language communities have different practices. 
            When these do not have a single normalization, context is
            required to determine which to produce or assume in
            resolution.  How can this context be maintained in Internet
            systems?</span></li>
      </ul>
      <p class="m_-7295555480336933649gmail-c1
        m_-7295555480336933649gmail-c2"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;height:11pt;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"></span></p>
      <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">While
          any of these challenges could easily be the topic of a
          stand-alone effort, this workshop seeks to explore whether
          there is a common set of root problems in the explicitness of
          the resolution context, heuristic derivation of intent, or
          language matching.   If so, it seeks to identify promising
          areas for the development of new, more explicit naming systems
          for the Internet.</span></p>
      <p class="m_-7295555480336933649gmail-c1
        m_-7295555480336933649gmail-c2"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;height:11pt;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"></span></p>
      <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span>We
          invite position papers on this topic to be submitted by July
          28, 2017 to<span> </span></span><span
          class="m_-7295555480336933649gmail-c8"
          style="color:rgb(17,85,204);text-decoration:underline"><a
            class="m_-7295555480336933649gmail-c6"
            href="mailto:ename@iab.org"
            style="color:inherit;text-decoration:inherit"
            target="_blank" moz-do-not-send="true">ename@iab.org</a></span><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">.
             Decisions on accepted submissions will be made by August
          11, 2017.</span></p>
      <p class="m_-7295555480336933649gmail-c1
        m_-7295555480336933649gmail-c2"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;height:11pt;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"></span></p>
      <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">Proposed
          dates for the workshop are October 10th and 11th, 2017 and the
          proposed location is Vancouver, British Columbia.  Further
          logistics will be provided to selected participants.</span></p>
      <p class="m_-7295555480336933649gmail-c1
        m_-7295555480336933649gmail-c2"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;height:11pt;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"></span></p>
      <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">Ted
          Hardie</span></p>
      <p class="m_-7295555480336933649gmail-c1"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal">for
          the IAB</span></p>
      <p class="m_-7295555480336933649gmail-c1
        m_-7295555480336933649gmail-c2"
style="margin:0px;color:rgb(0,0,0);font-size:11pt;font-family:Arial;padding-top:0pt;padding-bottom:0pt;line-height:1.15;text-align:left;height:11pt;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><span
          class="m_-7295555480336933649gmail-c0"
style="color:rgb(0,0,0);font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:Arial;font-style:normal"><br>
        </span></p>
    </blockquote>
    <br>
  </body>
</html>

--------------03055F6ECFA1CFA196E912EB--


From nobody Thu Jul 27 15:38:11 2017
Return-Path: <kwatsen@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66DBF12700F; Thu, 27 Jul 2017 15:37:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.022
X-Spam-Level: 
X-Spam-Status: No, score=-2.022 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=juniper.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 8t-MZgcj6sfa; Thu, 27 Jul 2017 15:37:53 -0700 (PDT)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0102.outbound.protection.outlook.com [104.47.36.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 457E012EAF7; Thu, 27 Jul 2017 15:37:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=kpgH84R2iu9yMGPx7AkqMPzFnVubgspvWPRjTGH0yOY=; b=WuCoslmNtIO7iCROF9poW6SiWgW3I8V2DPg4Lthl8JHUff8dTq2OexXy+8LxaIbW3nPXNU/ktgb9530/0LtITaFZ5T7NPJqFrw7HYbUVC0LMgg5BAlHGvi39UK6x84NZuoybh+O40Jy3wXC6KDcgrw3qmrFGE7ZCpkphh05wmhM=
Received: from BN3PR0501MB1442.namprd05.prod.outlook.com (10.160.117.151) by BN3PR0501MB1585.namprd05.prod.outlook.com (10.161.217.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1304.10; Thu, 27 Jul 2017 22:37:51 +0000
Received: from BN3PR0501MB1442.namprd05.prod.outlook.com ([10.160.117.151]) by BN3PR0501MB1442.namprd05.prod.outlook.com ([10.160.117.151]) with mapi id 15.01.1304.016; Thu, 27 Jul 2017 22:37:50 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>, "draft-ietf-netconf-keystore.all@ietf.org" <draft-ietf-netconf-keystore.all@ietf.org>, "netconf@ietf.org" <netconf@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Yangdoctors last call review of draft-ietf-netconf-keystore-02
Thread-Topic: Yangdoctors last call review of draft-ietf-netconf-keystore-02
Thread-Index: AQHS/tjFB6LSB6mMA0ixt1H16U9uU6Jbyb8AgAEruACAAAVBAIALFnwA
Date: Thu, 27 Jul 2017 22:37:50 +0000
Message-ID: <7F1757E2-F21A-44A4-B6F4-57F69CE44642@juniper.net>
References: <150028100874.32703.14161403810529927281@ietfa.amsl.com> <B1AC6895-5681-48F8-B7E7-418118120B4E@juniper.net> <20170720165942.GB21506@elstar.local> <20170720171829.GA21659@elstar.local>
In-Reply-To: <20170720171829.GA21659@elstar.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.20.0.170309
authentication-results: spf=none (sender IP is ) smtp.mailfrom=kwatsen@juniper.net; 
x-originating-ip: [66.129.241.12]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN3PR0501MB1585; 7:MaTp460Ts2E2l2cabpmXR5CID/InXn1U16hH0JpVstvRfdtQhfX7tQ3nQE4JtMEMrRo4lpTV0D2jTD0wJrMrZXirGKRM8z/SDqIMt6JNtiE6z6+ZJ4QFpOpuFajSGg4i8v8U6oVoShd5tkvbANDRY8rOpughSlmdAsZF9nUi4GGSJSEbY9jAp4oFDGlTquO2os6YrjIWTnz/YUrqSiaN2axdK09tqy0h8ur3nfAgkvnvJHafOumvy7NJXwh9pbjCMFwGDAW/XCY8Hq4QAR4sPuz7M7893+3gRFvG40KbeokdQT1pYgWMNsGhCmpXEn1wSqY9od1c12fi6/o1orhGdCvwEUSnWD0afwTO2+cmzQSGklLwq9uj9qbHPxSLa+et93lpgS+Iu5NfM/AURDGPPSKjRMMdGBzqZsEnuRUB6yQ0/RnMbm6NMDHm4vE4XfOhpeNmdqzy0uJMAgTnn4cUaF32pS2crSUYnDVsGP9ioJRNjEJBv8TzWp1hMtKYDVlRZiNATjoJvFo3NO6s5D3J1Y3ELvf/rFM3uKGrpVJm5P1QKoqReN7dTnRL77NG/TeAm+EbIqozaNmDP/Ick7lSsKpqn8qECNGoyvqLcoxUofZlkrViUB9gAxqfjjV9t0ZaFQE3eR1mtZxe/q4rj2q3DP7OFkoN1h8StmFrYHZvZdLyFK1+tVz6Ex0GR94sFEACaPXMup0w3VHf7fIsVBG8qSKyrsaUGCC5k9ZoG/4M6gJdPcHmK2+huFszJWQDXBFYwZ+TgxBsKbZ1PtDCjgZt5DvqiLPF77ZjOjP/O1FbB9I=
x-ms-office365-filtering-correlation-id: 2f7a71f9-cfeb-45ff-f32d-08d4d5401d28
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254116)(48565401081)(300000503095)(300135400095)(2017052603031)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:BN3PR0501MB1585; 
x-ms-traffictypediagnostic: BN3PR0501MB1585:
x-exchange-antispam-report-test: UriScan:(192374486261705);
x-microsoft-antispam-prvs: <BN3PR0501MB1585C0E630683C3A0830D431A5BE0@BN3PR0501MB1585.namprd05.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(5005006)(10201501046)(100000703101)(100105400095)(3002001)(93006095)(93001095)(6055026)(6041248)(20161123562025)(20161123555025)(20161123560025)(20161123564025)(20161123558100)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BN3PR0501MB1585; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BN3PR0501MB1585; 
x-forefront-prvs: 03818C953D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39850400002)(39410400002)(39400400002)(39450400003)(39840400002)(39860400002)(189002)(199003)(51444003)(2201001)(189998001)(2906002)(7736002)(5660300001)(8676002)(36756003)(8936002)(81166006)(81156014)(97736004)(4001350100001)(2900100001)(14454004)(229853002)(6246003)(54356999)(53936002)(76176999)(305945005)(38730400002)(6486002)(99286003)(6512007)(50986999)(77096006)(6506006)(25786009)(86362001)(33656002)(3280700002)(3660700001)(83716003)(478600001)(6436002)(68736007)(102836003)(2501003)(82746002)(6116002)(230783001)(83506001)(93886004)(3846002)(2950100002)(106356001)(101416001)(105586002)(66066001); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR0501MB1585; H:BN3PR0501MB1442.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <D6AD81B479A3DA44B600270863085655@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Jul 2017 22:37:50.8522 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0501MB1585
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Tft4GUuh2qN2J5J2P2bieCcrLLE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 22:37:55 -0000

SGkgSnVlcmdlbiwNCg0KPiBJIGxvb2tlZCBhIGJpdCBtb3JlIGFuZCB5b3UgZGVmaW5lDQo+DQo+
ICBpZGVudGl0eSBrZXktYWxnb3JpdGhtIHsNCj4gICAgZGVzY3JpcHRpb24NCj4gICAgICAiQmFz
ZSBpZGVudGl0eSBmcm9tIHdoaWNoIGFsbCBrZXktYWxnb3JpdGhtcyBhcmUgZGVyaXZlZC4iOw0K
PiAgfQ0KPg0KPiBwbHVzIGEgYnVuY2ggb2YgY29uY3JldGUgYWxnb3JpdGhtcy4gZHJhZnQtaWV0
Zi1ydGd3Zy15YW5nLWtleS1jaGFpbi0yNA0KPiBkZWZpbmVzDQo+DQo+ICAgIGlkZW50aXR5IGNy
eXB0by1hbGdvcml0aG0gew0KPiAgICAgICBkZXNjcmlwdGlvbg0KPiAgICAgICAgICJCYXNlIGlk
ZW50aXR5IG9mIGNyeXB0b2dyYXBoaWMgYWxnb3JpdGhtIG9wdGlvbnMuIjsNCj4gICAgIH0NCj4N
Cj4gYW5kIHRoZW4gYSBidW5jaCBvZiBjb25jcmV0ZSBhbGdvcml0aG1zIChoYXNoZXMgYW5kIHN5
bW1ldHJpYyBvbmVzKS4NCj4gVGhleSBhbHNvIGRvIG5vdCBleHBlY3QgSUFOQSB0byBtYWludGFp
biB0aGluZ3MuIEkgd291bGQgbG92ZSBpZg0KPiBzZWN1cml0eSBhcmVhIHBlb3BsZSB3b3VsZCBo
ZWxwIHVzIHdpdGggZ2V0dGluZyB0aGlzIHJpZ2h0LCB3ZWxsDQo+IHBlcmhhcHMgdGhleSBqdW1w
IGluIGR1cmluZyBzZWNkaXIgcmV2aWV3Lg0KDQoNCkZXSVcsIHRoZSB0d28gc2V0cyBvZiBhbGdv
cml0aG0gaWRlbnRpdGllcyBhcmUgZGlzam9pbnQuICBUaGUgb25lcyBpbg0KdGhlIGtleXN0b3Jl
IGRyYWZ0IGFyZSBhbGwgcHVibGljLWtleSBhbGdvcml0aG1zLiAgQXMgZm9yIHRoZSBrZXktY2hh
aW4NCmRyYWZ0LCBhbGwgYnV0IG9uZSBvZiB0aGUgaWRlbnRpdGllcyBhcmUgaG1hYyBhbGdvcml0
aG1zLCB3aXRoIHRoZSBsYXN0DQpvbmUgYmVpbmcgZm9yIGEga2V5IGRlcml2YXRpb24gZnVuY3Rp
b24uDQoNCkl0IHdvdWxkIGJlIGJlc3QgdG8gYWRkcmVzcyB0aGlzIGluIHRoZSBXRywgZm9yIHZp
c2liaWxpdHkuICBJIHRoaW5rDQp0aGF0IGl0J3MgcG9zc2libGUgdG8gcmVxdWVzdCBhbiBlYXJs
eSBzZWNkaXIgcmV2aWV3LCBvciBtYXliZSB3ZSBjYW4gDQphc2sgYWJvdXQganVzdCB0aGlzIGNv
bmNlcm4uICBUaGlzIGlzIGEgY2hhaXItYWN0aW9uLiANCg0KS2VudA0KDQoNCg0K


From nobody Thu Jul 27 16:00:49 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35013131E39 for <ietf@ietfa.amsl.com>; Thu, 27 Jul 2017 16:00:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.517
X-Spam-Level: 
X-Spam-Status: No, score=-0.517 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DRUGS_ANXIETY=1.483, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 nxGJhxOU97_1 for <ietf@ietfa.amsl.com>; Thu, 27 Jul 2017 16:00:47 -0700 (PDT)
Received: from mail-pf0-x241.google.com (mail-pf0-x241.google.com [IPv6:2607:f8b0:400e:c00::241]) (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 1C04B12F274 for <ietf@ietf.org>; Thu, 27 Jul 2017 16:00:47 -0700 (PDT)
Received: by mail-pf0-x241.google.com with SMTP id q85so19179425pfq.2 for <ietf@ietf.org>; Thu, 27 Jul 2017 16:00:47 -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=8UKwp/SII+LT1ymeOWRgcXX9jCiZkm8nX11Mb6yWaLc=; b=qOKhOOqbwCZKdwlEbh4HnqAu5zIuast0CLIm0ZyXlf+4iiZwrYP7qHjLdAxdJhEpNl TK29PB++avVpzIMd1X2MdpX+4GhuovJpWk1fLRdtmpd4WO4Qhz74lwmP5kfgU1a0ANBH qKVQnaWs9/Gmj4j6w3s45XLJ+2eCSbVZZJ8LCOZ+c02YZP8BaiLyqQ7iw0WM4qjWqmFB GWbE+JKY9mDz7ir9N0G2d7ovg+BA+5DF3jCIwbyVW/SDvENg2Eb3iUllwfQvlKeMZI9r TAfqXjvBniCM6jUNl+ZBrgH9VvDI7m+g0zTFWy0gZtMRb68qQVPIwU0zeYLlowlg8UIA UScQ==
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=8UKwp/SII+LT1ymeOWRgcXX9jCiZkm8nX11Mb6yWaLc=; b=DagZsdhPa5JS5YrnSXHfuymXOyZH4M6F4lffjLotmhYb2hXCGUaPZbA5XLGxlFMv+n MjAQz16W6LjP2vj4BEHRwBXeZw8uxCM/ldpxhXrv5wKXnRUuze+JRoJ0/UKrSfESN8sk aS87yeQyWiRSaCmjj/jR38VjDY42G715HISzWKii7uhLFc+sKJIQj9OkiHGtHRvoEaqp wIqtEbIKxlCyVoavbgpfyyZBEMbbwYQI2rLSCBQCvcxbaGZREVMeVXV4gzKzhwpe12dO UGMhYMjGld3yZwyBPwMAkL/HWjVomNn5rYYTEkLVixOyWNQawoBzEI2VQ/3/jSdNnr1A xfLQ==
X-Gm-Message-State: AIVw111CEGh6W5BVtrwg2RcUVTYY99Qc6DE2da8hbiaipdn6vtu210EL Isicug90ltFb5a7k
X-Received: by 10.99.123.78 with SMTP id k14mr5495162pgn.47.1501196446515; Thu, 27 Jul 2017 16:00:46 -0700 (PDT)
Received: from ?IPv6:2406:e007:4beb:1:28cc:dc4c:9703:6781? ([2406:e007:4beb:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id m190sm12029236pfb.102.2017.07.27.16.00.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 27 Jul 2017 16:00:45 -0700 (PDT)
Subject: Re: Visiting Singapore/Customs Clearance
To: Mary B <mary.h.barnes@gmail.com>, Mike StJohns <mstjohns@comcast.net>
Cc: "Gary E. Miller" <gem@rellim.com>, IETF discussion list <ietf@ietf.org>
References: <73ae5759-32a7-38fb-3232-9630a4dd6faa@gmail.com> <20170726222602.72dc27ab@spidey.rellim.com> <CABmDk8m3V7dPi-qNn3sig89_keOaepo29_GAyEr+__MjUrLLHA@mail.gmail.com> <4C169449-D1E2-4F9C-8163-CF3B5A067772@comcast.net> <CABmDk8kWr_NSh_r2JCeVST929UJVXFwPPkxAf9+k6_PBuQmmsw@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <45b53222-7c78-939d-3819-d567c70ea60e@gmail.com>
Date: Fri, 28 Jul 2017 11:00:50 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CABmDk8kWr_NSh_r2JCeVST929UJVXFwPPkxAf9+k6_PBuQmmsw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PxhvLRSZVbgb4F8-hku45Sk3joc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 23:00:48 -0000

On 28/07/2017 01:49, Mary B wrote:
> Yeah, I just came across that page.   Valium is also on that list - we
> might have a lot of wide awake, anxious people at this meeting ;)     That
> page also mentions that Pseudoephedrine has limitations

Pseudoephedrine is a precursor of methamphetamine and as such is a red
flag in many countries. If I carry a decongestant, it's one based on
phenylephrine. 

   Brian


From nobody Thu Jul 27 17:26:19 2017
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A5F6131EA3 for <ietf@ietfa.amsl.com>; Thu, 27 Jul 2017 17:26:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.88
X-Spam-Level: 
X-Spam-Status: No, score=-5.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 XkHU1BKCYQeJ for <ietf@ietfa.amsl.com>; Thu, 27 Jul 2017 17:26:16 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (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 8BE16126C83 for <ietf@ietf.org>; Thu, 27 Jul 2017 17:26:16 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id F2B88349829; Fri, 28 Jul 2017 00:26:13 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id E2F09160075; Fri, 28 Jul 2017 00:26:13 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id D4F66160074; Fri, 28 Jul 2017 00:26:13 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id vd0FX8CZMNBO; Fri, 28 Jul 2017 00:26:13 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 90B6A160036; Fri, 28 Jul 2017 00:26:13 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id BD5CB802E4D8; Fri, 28 Jul 2017 10:26:11 +1000 (AEST)
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, ietf@ietf.org
From: Mark Andrews <marka@isc.org>
Subject: Re: IETF 100 Registration and Hotel Reservations Open!
In-reply-to: Your message of "Thu, 27 Jul 2017 10:59:42 +1000."
Date: Fri, 28 Jul 2017 10:26:11 +1000
Message-Id: <20170728002611.BD5CB802E4D8@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oJIyZkVOMKWWHKqusB0ZYju1-J4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 00:26:18 -0000

And it is now fixed.

Mark Andrews writes:
> 
> I've opened a ticket for this.
> 
> In message <20170727005036.5D0C78013DB1@rock.dv.isc.org>, Mark Andrews writes
> :
> > 
> > In message <3129.1501089388@obiwan.sandelman.ca>, Michael Richardson writes
> :
> > > IETF Secretariat <ietf-secretariat@ietf.org> wrote:
> > >     > IETF 100 Information: https://ietf.org/meeting/100/index.html
> > >     > Register online at: https://ietf.org/meeting/register.html
> > > 
> > > Any reason the remote participation registration form can not open at the
> > > same time?
> >  
> > It appears to be half there.  Registration type on the main
> > registration page has a link to
> > https://www.ietf.org/registration/ietf100/remotereg.py but when you
> > hit "Submit Registration" it returns to the main registration page
> > for conformation with the "Full Rate Registration" radio box checked.
> > 
> > Mark
> > 
> > > --
> > > Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> > >  -= IPv6 IoT consulting =-
> > -- 
> > Mark Andrews, ISC
> > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
> > 
> -- 
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Thu Jul 27 21:53:26 2017
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7424E128961 for <ietf@ietfa.amsl.com>; Thu, 27 Jul 2017 21:53:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level: 
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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
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 iHZTbEJFJQ8c for <ietf@ietfa.amsl.com>; Thu, 27 Jul 2017 21:53:21 -0700 (PDT)
Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) (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 8CE71131EB8 for <ietf@ietf.org>; Thu, 27 Jul 2017 21:53:21 -0700 (PDT)
Received: from pps.filterd (m0098421.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v6S4n8TZ028349 for <ietf@ietf.org>; Fri, 28 Jul 2017 00:53:19 -0400
Received: from e11.ny.us.ibm.com (e11.ny.us.ibm.com [129.33.205.201]) by mx0a-001b2d01.pphosted.com with ESMTP id 2byrpcv1rr-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 28 Jul 2017 00:53:18 -0400
Received: from localhost by e11.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 28 Jul 2017 00:53:17 -0400
Received: from b01cxnp22036.gho.pok.ibm.com (9.57.198.26) by e11.ny.us.ibm.com (146.89.104.198) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 28 Jul 2017 00:53:15 -0400
Received: from b01ledav006.gho.pok.ibm.com (b01ledav006.gho.pok.ibm.com [9.57.199.111]) by b01cxnp22036.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v6S4rFbn26149030 for <ietf@ietf.org>; Fri, 28 Jul 2017 04:53:15 GMT
Received: from b01ledav006.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 03395AC03F for <ietf@ietf.org>; Fri, 28 Jul 2017 00:53:28 -0400 (EDT)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b01ledav006.gho.pok.ibm.com (Postfix) with ESMTPS id DF4B5AC03A for <ietf@ietf.org>; Fri, 28 Jul 2017 00:53:27 -0400 (EDT)
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.15.2/8.12.5) with ESMTP id v6S4rDRS019632 for <ietf@ietf.org>; Fri, 28 Jul 2017 00:53:13 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v6S4rDEj019614 for ietf@ietf.org; Fri, 28 Jul 2017 00:53:13 -0400
From: narten@us.ibm.com
Date: Fri, 28 Jul 2017 00:53:12 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-GCONF: 00
x-cbid: 17072804-2213-0000-0000-00000200E8E5
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00007439; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000214; SDB=6.00893955; UDB=6.00446969; IPR=6.00674115;  BA=6.00005495; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00016418; XFM=3.00000015; UTC=2017-07-28 04:53:16
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17072804-2214-0000-0000-000057067BF3
Message-Id: <201707280453.v6S4rDEj019614@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-07-28_01:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=13 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1706020000 definitions=main-1707280073
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qiR9v87bPuGb2uT2SEb3g7WK7Kw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 04:53:24 -0000

Total of 112 messages in the last 7 days.
 
script run at: Fri Jul 28 00:53:07 EDT 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  6.25% |    7 |  5.12% |    61458 | john-ietf@jck.com
  5.36% |    6 |  4.78% |    57358 | tjc@ecs.soton.ac.uk
  5.36% |    6 |  4.29% |    51437 | brian.e.carpenter@gmail.com
  5.36% |    6 |  3.34% |    40059 | lyndon@orthanc.ca
  1.79% |    2 |  6.41% |    76925 | naiming@cisco.com
  4.46% |    5 |  3.44% |    41296 | mcr+ietf@sandelman.ca
  3.57% |    4 |  4.06% |    48756 | mellon@fugue.com
  2.68% |    3 |  3.76% |    45088 | mary.h.barnes@gmail.com
  3.57% |    4 |  2.58% |    30975 | marka@isc.org
  3.57% |    4 |  2.49% |    29897 | stewart.bryant@gmail.com
  2.68% |    3 |  2.76% |    33170 | ludwig@clemm.org
  1.79% |    2 |  3.41% |    40984 | denisbider.ietf@gmail.com
  2.68% |    3 |  2.22% |    26654 | shares@ndzh.com
  0.89% |    1 |  3.24% |    38851 | iab-chair@iab.org
  1.79% |    2 |  1.98% |    23704 | akatlas@gmail.com
  1.79% |    2 |  1.92% |    23032 | mstjohns@comcast.net
  1.79% |    2 |  1.85% |    22181 | olejacobsen@me.com
  1.79% |    2 |  1.78% |    21356 | linuxwolf+ietf@outer-planes.net
  1.79% |    2 |  1.72% |    20667 | spencerdawkins.ietf@gmail.com
  1.79% |    2 |  1.66% |    19888 | narellec@gmail.com
  1.79% |    2 |  1.53% |    18387 | ajs@anvilwalrusden.com
  1.79% |    2 |  1.46% |    17559 | housley@vigilsec.com
  1.79% |    2 |  1.43% |    17149 | ietf-secretariat@ietf.org
  1.79% |    2 |  1.40% |    16746 | swmike@swm.pp.se
  0.89% |    1 |  2.02% |    24212 | lenny@juniper.net
  0.89% |    1 |  1.93% |    23117 | rpelletier@isoc.org
  1.79% |    2 |  1.01% |    12139 | rjsparks@nostrum.com
  0.89% |    1 |  1.84% |    22118 | daedulus@btconnect.com
  0.89% |    1 |  1.73% |    20810 | christer.holmberg@ericsson.com
  0.89% |    1 |  1.67% |    20077 | bew@cisco.com
  0.89% |    1 |  1.02% |    12187 | kwatsen@juniper.net
  0.89% |    1 |  1.01% |    12120 | jordi.palet@consulintel.es
  0.89% |    1 |  1.01% |    12102 | narten@us.ibm.com
  0.89% |    1 |  0.93% |    11173 | lee@asgard.org
  0.89% |    1 |  0.92% |    11021 | ggm@algebras.org
  0.89% |    1 |  0.91% |    10877 | lear@cisco.com
  0.89% |    1 |  0.88% |    10576 | alexey.melnikov@isode.com
  0.89% |    1 |  0.86% |    10336 | rsalz@akamai.com
  0.89% |    1 |  0.83% |     9932 | bob.hinden@gmail.com
  0.89% |    1 |  0.82% |     9897 | agmalis@gmail.com
  0.89% |    1 |  0.80% |     9567 | volz@cisco.com
  0.89% |    1 |  0.79% |     9457 | mnot@mnot.net
  0.89% |    1 |  0.77% |     9202 | john@jck.com
  0.89% |    1 |  0.75% |     9015 | jari.arkko@piuha.net
  0.89% |    1 |  0.71% |     8533 | gem@rellim.com
  0.89% |    1 |  0.68% |     8155 | alejandroacostaalamo@gmail.com
  0.89% |    1 |  0.67% |     8074 | borje.ohlman@ericsson.com
  0.89% |    1 |  0.66% |     7959 | mariainesrobles@googlemail.com
  0.89% |    1 |  0.65% |     7856 | lhotka@nic.cz
  0.89% |    1 |  0.65% |     7791 | randy_presuhn@alumni.stanford.edu
  0.89% |    1 |  0.65% |     7779 | mrex@sap.com
  0.89% |    1 |  0.62% |     7413 | aaron.falk@gmail.com
  0.89% |    1 |  0.59% |     7075 | charlie.perkins@huawei.com
  0.89% |    1 |  0.58% |     6988 | amorris@amsl.com
  0.89% |    1 |  0.51% |     6129 | randy@psg.com
  0.89% |    1 |  0.51% |     6098 | johnl@taugh.com
  0.89% |    1 |  0.48% |     5739 | jouni.nospam@gmail.com
  0.89% |    1 |  0.46% |     5567 | presnick@qti.qualcomm.com
  0.89% |    1 |  0.45% |     5454 | ron.even.tlv@gmail.com
--------+------+--------+----------+------------------------
100.00% |  112 |100.00% |  1200122 | Total


From nobody Thu Jul 27 22:21:34 2017
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B2FF126DD9; Thu, 27 Jul 2017 22:21:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 pmh0T8F9_sJH; Thu, 27 Jul 2017 22:21:31 -0700 (PDT)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C21AB128AB0; Thu, 27 Jul 2017 22:21:30 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id 971776EC; Fri, 28 Jul 2017 07:21:29 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.217]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id 0-Ztj5aSeXkv; Fri, 28 Jul 2017 07:21:24 +0200 (CEST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas5.jacobs-university.de (Postfix) with ESMTPS; Fri, 28 Jul 2017 07:21:29 +0200 (CEST)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 424E0200BA; Fri, 28 Jul 2017 07:21:29 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id oiSOXwv6h8n1; Fri, 28 Jul 2017 07:21:28 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id D0D7D200AA; Fri, 28 Jul 2017 07:21:28 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id D2730400067F; Fri, 28 Jul 2017 07:21:27 +0200 (CEST)
Date: Fri, 28 Jul 2017 07:21:27 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Kent Watsen <kwatsen@juniper.net>
Cc: "yang-doctors@ietf.org" <yang-doctors@ietf.org>, "draft-ietf-netconf-keystore.all@ietf.org" <draft-ietf-netconf-keystore.all@ietf.org>,  "netconf@ietf.org" <netconf@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Yangdoctors last call review of draft-ietf-netconf-keystore-02
Message-ID: <20170728052127.GA28770@elstar.local>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Kent Watsen <kwatsen@juniper.net>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>, "draft-ietf-netconf-keystore.all@ietf.org" <draft-ietf-netconf-keystore.all@ietf.org>,  "netconf@ietf.org" <netconf@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
References: <150028100874.32703.14161403810529927281@ietfa.amsl.com> <B1AC6895-5681-48F8-B7E7-418118120B4E@juniper.net> <20170720165942.GB21506@elstar.local> <20170720171829.GA21659@elstar.local> <7F1757E2-F21A-44A4-B6F4-57F69CE44642@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7F1757E2-F21A-44A4-B6F4-57F69CE44642@juniper.net>
User-Agent: Mutt/1.6.0 (2016-04-01)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jFvOW54Eq7jfyv-1PCIKeXiYsBE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 05:21:33 -0000

On Thu, Jul 27, 2017 at 10:37:50PM +0000, Kent Watsen wrote:
> Hi Juergen,
> 
> > I looked a bit more and you define
> >
> >  identity key-algorithm {
> >    description
> >      "Base identity from which all key-algorithms are derived.";
> >  }
> >
> > plus a bunch of concrete algorithms. draft-ietf-rtgwg-yang-key-chain-24
> > defines
> >
> >    identity crypto-algorithm {
> >       description
> >         "Base identity of cryptographic algorithm options.";
> >     }
> >
> > and then a bunch of concrete algorithms (hashes and symmetric ones).
> > They also do not expect IANA to maintain things. I would love if
> > security area people would help us with getting this right, well
> > perhaps they jump in during secdir review.
> 
> 
> FWIW, the two sets of algorithm identities are disjoint.  The ones in
> the keystore draft are all public-key algorithms.  As for the key-chain
> draft, all but one of the identities are hmac algorithms, with the last
> one being for a key derivation function.
> 
> It would be best to address this in the WG, for visibility.  I think
> that it's possible to request an early secdir review, or maybe we can 
> ask about just this concern.  This is a chair-action. 
>

I all for secdir review for this document. That said, perhaps it is OK
to have the identities as they are and to define a proper IANA
registry later. The price might be that some identities are defined
twice but that would likely not be a significant implementation cost.
Its a trade off between (i) moving fast and maybe requiring to adapt
later or (ii) trying to work everything out while doing the first
version and hence being slow.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>


From nobody Thu Jul 27 23:53:07 2017
Return-Path: <denisbider.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E88B61296C9; Thu, 27 Jul 2017 23:53:00 -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 zqFUWeUwk-2e; Thu, 27 Jul 2017 23:52:58 -0700 (PDT)
Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002: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 4651B126DCA; Thu, 27 Jul 2017 23:52:58 -0700 (PDT)
Received: by mail-yw0-x236.google.com with SMTP id l82so60641831ywc.2; Thu, 27 Jul 2017 23:52:58 -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=UNpe3sfb4eHaFiGzO/beeSLE5H0XMVlRgkU4j5UDMDQ=; b=Jpxp19cW3Wa+/92dqagKAzRQO2ybpV7KyQk3DuonqUwPkxObRM7Am5Mo8iFX9WAj+l hQhc5m6lthyl2l8RVuwXvNV/6r5IR+5QcTVWPpHg7brRjNf0FVby6KRzBG4zvpBop0Nz GomVITUTzrgzSX+N4u0KDsruH7IH5M2OV1/qQZUIUAExpWnObuA1t0zj+1PWTlwkH8d/ Zf88Pfg/GD6pinz8M6AH81nutEAe/6QkJ3klcLB0Ot2iLBFJ+GjugZHZ6qr4vBOw2JiT cCYAxNgbh7uFASoWKKMCsi1HtrGwd1NjRv7RFfI43ssrSA9KAQRoStEWhY5sLylcanvt 7Ieg==
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=UNpe3sfb4eHaFiGzO/beeSLE5H0XMVlRgkU4j5UDMDQ=; b=isFQJgyEjs+/8PBrll/z0xgrWkmV0CNCLwX2LBZsIINWdP6FPyzxkQy1PbeN9FUyTL T8KvKlXdQuYN17gj2vIgzhUNrR04GFz32OTSYlR7Tl7jmtEgcyPgi1sxKFmf+4Zr6LgA knQ8OaOpEGmSyOeOuJ01Qpl/Xx2ivDq4lNJZ7BkZt1KCzOdD9tt3gfWOoPqAELLQAR5c 8OlkGKr0uUSx4VgRe4GJTNpsZn4ecQf+yYkJRwbeU5sVNeesFEuUVWK4m4FcUDmDrm7s nOy7pcf18TpRvukKkTq0tVL5s7hPlK9CbEZBc/eYoLYdA2FpaJyxU8DTuB7qr62PEbhv kjnQ==
X-Gm-Message-State: AIVw113sNMel8bI1Z9to6cDIrvC5EQ0moD/z/c4vXm10dML+G4BGFPDJ c2sRa2uLeyesSEmANgPyJgfq1k4JWZXs
X-Received: by 10.129.154.16 with SMTP id r16mr5487871ywg.282.1501224777586; Thu, 27 Jul 2017 23:52:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.42.200 with HTTP; Thu, 27 Jul 2017 23:52:57 -0700 (PDT)
In-Reply-To: <CADPMZDDjQoHc9yoYb7sSTa2r7e71DSMdqQ7OEH7neWU0ygKzNw@mail.gmail.com>
References: <150093015937.32021.12465797358778837950@ietfa.amsl.com> <CADPMZDCE+m+_QA7s6vdFOw-7uF4cfV4g8_U07fb-Ydur30OR5g@mail.gmail.com> <1eef6165-9b5b-c354-dffe-5df1e98098fa@outer-planes.net> <CADPMZDDjQoHc9yoYb7sSTa2r7e71DSMdqQ7OEH7neWU0ygKzNw@mail.gmail.com>
From: denis bider <denisbider.ietf@gmail.com>
Date: Fri, 28 Jul 2017 00:52:57 -0600
Message-ID: <CADPMZDC7=BzfohUCmYbQR8LzqY8GauDeGrtJOo97M00attP8Ag@mail.gmail.com>
Subject: Re: [Curdle] Genart last call review of draft-ietf-curdle-ssh-ext-info-10
To: "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>
Cc: gen-art@ietf.org, curdle <curdle@ietf.org>, ietf@ietf.org,  draft-ietf-curdle-ssh-ext-info.all@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c0b8698989d6605555b21e8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qXlLG1sgTL-Mk41eH6FlzinMuZQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 06:53:01 -0000

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

OK, I have uploaded version -11 with language as follows:

"An extension MAY dictate, where it is specified, that in order to take
effect, both parties must include it in their EXT_INFO; or it MAY be
sufficient that only one party includes it; or other rules MAY be
specified. The relative order in which extensions appear in an EXT_INFO
message MUST be ignored by default; but an extension MAY specify that the
order matters for that extension, in a specific way."

This seems clearer to me than it was in -10. If you still see room for
improvement, let me know!


On Wed, Jul 26, 2017 at 9:09 PM, denis bider <denisbider.ietf@gmail.com>
wrote:

> Hello Matthew,
>
> I'm not sure if I know how to address this better than with the language
> so far proposed.
>
> Perhaps one choice would be to simply remove this paragraph. However, the
> reason it was added was because an earlier reviewer (I'm not sure of the
> details at this time) raised the question about whether extension
> negotiation works like it does for algorithm lists, such as in e.g.
> SSH_MSG_KEXINIT. In that case, multiple algorithms are enumerated by both
> sides, and only one is chosen that (1) is enumerated by both sides, and (2)
> is the first of those to be enumerated by the client. The main purpose of
> this paragraph has been to clarify that extension negotiation does not work
> that way in EXT_INFO.
>
> What language would you propose? Is there some simple language that would
> do? How about this?
>
> "An extension may dictate, where it is specified, that in order to take
> effect, both parties must include it in its EXT_INFO; or it may be
> sufficient that only one party does; or more complex rules may be
> specified."
>
>
> On Wed, Jul 26, 2017 at 1:28 PM, Matthew A. Miller <
> linuxwolf+ietf@outer-planes.net> wrote:
>
>> Thanks very much for the response, Denis.
>>
>> I think I understand the intent here, but I'm not sure this new text is
>> enough to mitigate some future conflict.  I'm also concerned that it
>> completely ignores the one-party extensions (e.g., an extension included
>> in the EXT_INFO by only the client or the server, but not both), and
>> what the impact is holistically.  Looking at the one-party extensions
>> defined herein, I can't see how their order matters; but does that mean
>> the order will never matter?
>>
>> In writing this reply, I wondered if it's better for the order to always
>> be irrelevant; an implementation might be allowed to hint its preferred
>> order in the EXT_INFO, but implementations are still free to do whatever
>> makes sense to them within the bounds of the relevant extension
>> definitions.  If an extension ought to take precedence over another,
>> make it clear in its specification that it SHOULD (or MUST) be dealt
>> with before (or after) others.
>>
>> Does that make sense?
>>
>>
>> - m&m
>>
>> Matthew A. Miller
>>
>> On 17/07/25 16:24, denis bider wrote:
>> > Good catch. I believe this refers to the following paragraph:
>> >
>> > "If an extension requires both the client and the server to include it
>> > in order for the extension to take effect, the relative position of the
>> > extension-name in each EXT_INFO message is irrelevant."
>> >
>> > I have drafted the following new wording:
>> >
>> > "Unless a particular extension's specification indicates differently;
>> > then, if an extension requires both the client and the server to include
>> > it in order for the extension to take effect; implementers MUST use a
>> > default assumption that the relative position of the extension-name in
>> > each EXT_INFO message is irrelevant with respect to whether the
>> > extension takes effect."
>> >
>> > The purpose of this wording is to:
>> >
>> > - Provide a sensible default, which is that in the absence of specific
>> > knowledge, order of extension names does not matter.
>> >
>> > - Allow for deviations in special cases where there is specific
>> knowledge.
>> >
>> > For example, extension "foo-linux" could be specified, but after some
>> > years of use, it's observed that it works well for its main purpose, but
>> > is not ideal for a server on Windows. Therefore, extension "foo-windows"
>> > is specified, which works well when the server is Windows, but not as
>> > well when it's Linux.
>> >
>> > In this case, an implementation that supports "foo-linux" only would be
>> > ignorant of anything else, and would use the default rule (order of
>> > extension names does not matter). However, an implementation that
>> > supports "foo-windows" could implement only that, or both "foo-linux"
>> > and "foo-windows". The specification for "foo-windows" could indicate
>> > that when both are supported, the first one listed by the server (or in
>> > other cases, by the client) is used.
>> >
>> > Allowing for such an extension-defined special case would allow a Linux
>> > server to advertise extensions [... "foo-linux", ..., "foo-windows",
>> > ...], preferring "foo-linux", but supporting the less appropriate
>> > "foo-windows" mechanism as well. Whereas, a Windows server could
>> > advertise [... "foo-windows", ..., "foo-linux", ...], preferring
>> > "foo-windows", but supporting the less appropriate "foo-linux" mechanism
>> > as well.
>> >
>> > Does this work?
>> >
>> > If there are no objections, I'll upload a -11 draft version with this
>> > new wording.
>> >
>> >
>> >
>> > On Mon, Jul 24, 2017 at 3:02 PM, Matthew Miller
>> > <linuxwolf+ietf@outer-planes.net
>> > <mailto:linuxwolf+ietf@outer-planes.net>> wrote:
>> >
>> >     Reviewer: Matthew Miller
>> >     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
>> >     <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>>.
>> >
>> >     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
>> >
>> >     Summary:
>> >
>> >     This document is ready with an issue.
>> >
>> >     I found this document very coherent and easy to follow.
>> >
>> >     Major issues:
>> >
>> >     Minor issues:
>> >
>> >     My only issue borders on nit, but sided with nit as I can see it
>> >     potentially causing confusion for an implementer in the future.
>> >
>> >     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.
>> >
>> >     Nits/editorial comments:
>> >
>> >     * RFC 5226 is referenced by this document, but is obsoleted by RFC
>> 8126.
>> >
>> >
>> >     _______________________________________________
>> >     Curdle mailing list
>> >     Curdle@ietf.org <mailto:Curdle@ietf.org>
>> >     https://www.ietf.org/mailman/listinfo/curdle
>> >     <https://www.ietf.org/mailman/listinfo/curdle>
>> >
>> >
>>
>>
>

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

<div dir=3D"ltr">OK, I have uploaded version -11 with language as follows:<=
div><br></div><div>&quot;An extension MAY dictate, where it is specified, t=
hat in order to take effect, both parties must include it in their EXT_INFO=
; or it MAY be sufficient that only one party includes it; or other rules M=
AY be specified. The relative order in which extensions appear in an EXT_IN=
FO message MUST be ignored by default; but an extension MAY specify that th=
e order matters for that extension, in a specific way.&quot;</div><div><br>=
</div><div>This seems clearer to me than it was in -10. If you still see ro=
om for improvement, let me know!</div><div><br></div></div><div class=3D"gm=
ail_extra"><br><div class=3D"gmail_quote">On Wed, Jul 26, 2017 at 9:09 PM, =
denis bider <span dir=3D"ltr">&lt;<a href=3D"mailto:denisbider.ietf@gmail.c=
om" target=3D"_blank">denisbider.ietf@gmail.com</a>&gt;</span> wrote:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex"><div dir=3D"ltr">Hello Matthew,<div><br></div>=
<div>I&#39;m not sure if I know how to address this better than with the la=
nguage so far proposed.</div><div><br></div><div>Perhaps one choice would b=
e to simply remove this paragraph. However, the reason it was added was bec=
ause an earlier reviewer (I&#39;m not sure of the details at this time) rai=
sed the question about whether extension negotiation works like it does for=
 algorithm lists, such as in e.g. SSH_MSG_KEXINIT. In that case, multiple a=
lgorithms are enumerated by both sides, and only one is chosen that (1) is =
enumerated by both sides, and (2) is the first of those to be enumerated by=
 the client. The main purpose of this paragraph has been to clarify that ex=
tension negotiation does not work that way in EXT_INFO.</div><div><br></div=
><div>What language would you propose? Is there some simple language that w=
ould do? How about this?</div><div><br></div><div>&quot;An extension may di=
ctate, where it is specified, that in order to take effect, both parties mu=
st include it in its EXT_INFO; or it may be sufficient that only one party =
does; or more complex rules may be specified.&quot;</div><div><br></div></d=
iv><div class=3D"HOEnZb"><div class=3D"h5"><div class=3D"gmail_extra"><br><=
div class=3D"gmail_quote">On Wed, Jul 26, 2017 at 1:28 PM, Matthew A. Mille=
r <span dir=3D"ltr">&lt;<a href=3D"mailto:linuxwolf+ietf@outer-planes.net" =
target=3D"_blank">linuxwolf+ietf@outer-planes.<wbr>net</a>&gt;</span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">Thanks very much for the response, Deni=
s.<br>
<br>
I think I understand the intent here, but I&#39;m not sure this new text is=
<br>
enough to mitigate some future conflict.=C2=A0 I&#39;m also concerned that =
it<br>
completely ignores the one-party extensions (e.g., an extension included<br=
>
in the EXT_INFO by only the client or the server, but not both), and<br>
what the impact is holistically.=C2=A0 Looking at the one-party extensions<=
br>
defined herein, I can&#39;t see how their order matters; but does that mean=
<br>
the order will never matter?<br>
<br>
In writing this reply, I wondered if it&#39;s better for the order to alway=
s<br>
be irrelevant; an implementation might be allowed to hint its preferred<br>
order in the EXT_INFO, but implementations are still free to do whatever<br=
>
makes sense to them within the bounds of the relevant extension<br>
definitions.=C2=A0 If an extension ought to take precedence over another,<b=
r>
make it clear in its specification that it SHOULD (or MUST) be dealt<br>
with before (or after) others.<br>
<br>
Does that make sense?<br>
<br>
<br>
- m&amp;m<br>
<br>
Matthew A. Miller<br>
<div><div class=3D"m_6646268239450461900h5"><br>
On 17/07/25 16:24, denis bider wrote:<br>
&gt; Good catch. I believe this refers to the following paragraph:<br>
&gt;<br>
&gt; &quot;If an extension requires both the client and the server to inclu=
de it<br>
&gt; in order for the extension to take effect, the relative position of th=
e<br>
&gt; extension-name in each EXT_INFO message is irrelevant.&quot;<br>
&gt;<br>
&gt; I have drafted the following new wording:<br>
&gt;<br>
&gt; &quot;Unless a particular extension&#39;s specification indicates diff=
erently;<br>
&gt; then, if an extension requires both the client and the server to inclu=
de<br>
&gt; it in order for the extension to take effect; implementers MUST use a<=
br>
&gt; default assumption that the relative position of the extension-name in=
<br>
&gt; each EXT_INFO message is irrelevant with respect to whether the<br>
&gt; extension takes effect.&quot;<br>
&gt;<br>
&gt; The purpose of this wording is to:<br>
&gt;<br>
&gt; - Provide a sensible default, which is that in the absence of specific=
<br>
&gt; knowledge, order of extension names does not matter.<br>
&gt;<br>
&gt; - Allow for deviations in special cases where there is specific knowle=
dge.<br>
&gt;<br>
&gt; For example, extension &quot;foo-linux&quot; could be specified, but a=
fter some<br>
&gt; years of use, it&#39;s observed that it works well for its main purpos=
e, but<br>
&gt; is not ideal for a server on Windows. Therefore, extension &quot;foo-w=
indows&quot;<br>
&gt; is specified, which works well when the server is Windows, but not as<=
br>
&gt; well when it&#39;s Linux.<br>
&gt;<br>
&gt; In this case, an implementation that supports &quot;foo-linux&quot; on=
ly would be<br>
&gt; ignorant of anything else, and would use the default rule (order of<br=
>
&gt; extension names does not matter). However, an implementation that<br>
&gt; supports &quot;foo-windows&quot; could implement only that, or both &q=
uot;foo-linux&quot;<br>
&gt; and &quot;foo-windows&quot;. The specification for &quot;foo-windows&q=
uot; could indicate<br>
&gt; that when both are supported, the first one listed by the server (or i=
n<br>
&gt; other cases, by the client) is used.<br>
&gt;<br>
&gt; Allowing for such an extension-defined special case would allow a Linu=
x<br>
&gt; server to advertise extensions [... &quot;foo-linux&quot;, ..., &quot;=
foo-windows&quot;,<br>
&gt; ...], preferring &quot;foo-linux&quot;, but supporting the less approp=
riate<br>
&gt; &quot;foo-windows&quot; mechanism as well. Whereas, a Windows server c=
ould<br>
&gt; advertise [... &quot;foo-windows&quot;, ..., &quot;foo-linux&quot;, ..=
.], preferring<br>
&gt; &quot;foo-windows&quot;, but supporting the less appropriate &quot;foo=
-linux&quot; mechanism<br>
&gt; as well.<br>
&gt;<br>
&gt; Does this work?<br>
&gt;<br>
&gt; If there are no objections, I&#39;ll upload a -11 draft version with t=
his<br>
&gt; new wording.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; On Mon, Jul 24, 2017 at 3:02 PM, Matthew Miller<br>
&gt; &lt;<a href=3D"mailto:linuxwolf%2Bietf@outer-planes.net" target=3D"_bl=
ank">linuxwolf+ietf@outer-planes.n<wbr>et</a><br>
</div></div><div><div class=3D"m_6646268239450461900h5">&gt; &lt;mailto:<a =
href=3D"mailto:linuxwolf%2Bietf@outer-planes.net" target=3D"_blank">linuxwo=
lf+ietf@outer-p<wbr>lanes.net</a>&gt;&gt; wrote:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Reviewer: Matthew Miller<br>
&gt;=C2=A0 =C2=A0 =C2=A0Review result: Ready with Issues<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0I am the assigned Gen-ART reviewer for this draft. =
The General Area<br>
&gt;=C2=A0 =C2=A0 =C2=A0Review Team (Gen-ART) reviews all IETF documents be=
ing processed<br>
&gt;=C2=A0 =C2=A0 =C2=A0by the IESG for the IETF Chair.=C2=A0 Please treat =
these comments just<br>
&gt;=C2=A0 =C2=A0 =C2=A0like any other last call comments.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0For more information, please see the FAQ at<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/=
GenArtfaq" rel=3D"noreferrer" target=3D"_blank">https://trac.ietf.org/trac/=
g<wbr>en/wiki/GenArtfaq</a><br>
&gt;=C2=A0 =C2=A0 =C2=A0&lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/=
GenArtfaq" rel=3D"noreferrer" target=3D"_blank">https://trac.ietf.org/trac/=
g<wbr>en/wiki/GenArtfaq</a>&gt;&gt;.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Document: draft-ietf-curdle-ssh-ext-info<wbr>-10<br=
>
&gt;=C2=A0 =C2=A0 =C2=A0Reviewer: Matthew Miller<br>
&gt;=C2=A0 =C2=A0 =C2=A0Review Date: 2017-07-24<br>
&gt;=C2=A0 =C2=A0 =C2=A0IETF LC End Date: 2017-07-30<br>
&gt;=C2=A0 =C2=A0 =C2=A0IESG Telechat date: N/A<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Summary:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0This document is ready with an issue.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0I found this document very coherent and easy to fol=
low.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Major issues:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Minor issues:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0My only issue borders on nit, but sided with nit as=
 I can see it<br>
&gt;=C2=A0 =C2=A0 =C2=A0potentially causing confusion for an implementer in=
 the future.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Section 2.5. &quot;Interpretation of Extension Name=
s and Values&quot; explicitly<br>
&gt;=C2=A0 =C2=A0 =C2=A0states in the second paragraph a condition where th=
e relative order of<br>
&gt;=C2=A0 =C2=A0 =C2=A0extension-names in an EXT_INFO message is irrelevan=
t.=C2=A0 However, the rest<br>
&gt;=C2=A0 =C2=A0 =C2=A0of the section seems to imply to me that relative o=
rder is not<br>
&gt;=C2=A0 =C2=A0 =C2=A0important;<br>
&gt;=C2=A0 =C2=A0 =C2=A0so to explicitly call out a scenario seems to imply=
 that relative order<br>
&gt;=C2=A0 =C2=A0 =C2=A0*is* relevant/important, sometimes.=C2=A0 If relati=
ve order is expected to be<br>
&gt;=C2=A0 =C2=A0 =C2=A0important most of the time, I think it helpful to e=
xplicitly state that<br>
&gt;=C2=A0 =C2=A0 =C2=A0and give a rationale for it.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Nits/editorial comments:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0* RFC 5226 is referenced by this document, but is o=
bsoleted by RFC 8126.<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0_____________________________<wbr>_________________=
_<br>
&gt;=C2=A0 =C2=A0 =C2=A0Curdle mailing list<br>
</div></div>&gt;=C2=A0 =C2=A0 =C2=A0<a href=3D"mailto:Curdle@ietf.org" targ=
et=3D"_blank">Curdle@ietf.org</a> &lt;mailto:<a href=3D"mailto:Curdle@ietf.=
org" target=3D"_blank">Curdle@ietf.org</a>&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0<a href=3D"https://www.ietf.org/mailman/listinfo/cu=
rdle" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<wb=
r>listinfo/curdle</a><br>
&gt;=C2=A0 =C2=A0 =C2=A0&lt;<a href=3D"https://www.ietf.org/mailman/listinf=
o/curdle" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/<wbr>ma=
ilman/listinfo/curdle</a>&gt;<br>
&gt;<br>
&gt;<br>
<br>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>

--94eb2c0b8698989d6605555b21e8--


From nobody Fri Jul 28 03:37:37 2017
Return-Path: <dhruv.dhody@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2FB71318A8; Fri, 28 Jul 2017 03:37:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.82
X-Spam-Level: 
X-Spam-Status: No, score=-2.82 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_COMMENT_SAVED_URL=1.391, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, T_HTML_ATTACH=0.01] 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 COJ_-RNkWBkD; Fri, 28 Jul 2017 03:37:14 -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 F2E061322C1; Fri, 28 Jul 2017 03:37:08 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DSF30652; Fri, 28 Jul 2017 10:37:06 +0000 (GMT)
Received: from BLREML701-CAH.china.huawei.com (10.20.4.170) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.301.0; Fri, 28 Jul 2017 11:36:47 +0100
Received: from BLREML501-MBB.china.huawei.com ([10.20.5.200]) by blreml701-cah.china.huawei.com ([::1]) with mapi id 14.03.0301.000; Fri, 28 Jul 2017 16:06:34 +0530
From: Dhruv Dhody <dhruv.dhody@huawei.com>
To: Dale Worley <worley@ariadne.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-pce-pceps.all@ietf.org" <draft-ietf-pce-pceps.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Dhruv Dhody <dhruv.ietf@gmail.com>
Subject: RE: [Pce] Genart last call review of draft-ietf-pce-pceps-14
Thread-Topic: [Pce] Genart last call review of draft-ietf-pce-pceps-14
Thread-Index: AQHS+rw6zqPRSDFqSU+m/UcLVejzmaJXhnYg
Date: Fri, 28 Jul 2017 10:36:34 +0000
Message-ID: <23CE718903A838468A8B325B80962F9B8CB95DF7@blreml501-mbb>
References: <149982889725.9262.6380278547558008402@ietfa.amsl.com>
In-Reply-To: <149982889725.9262.6380278547558008402@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.149.39]
Content-Type: multipart/mixed; boundary="_003_23CE718903A838468A8B325B80962F9B8CB95DF7blreml501mbb_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090203.597B13D3.01DE, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 97a2993c040c166ea2819edd2dfdf4b1
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PRqE2y_ZtrqNUs_UDIE4FmaMm1Q>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 10:37:22 -0000

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

Hi Dale,=20

Thanks for your detailed review and providing suggested text.=20
Sorry for being a little late with this reply.=20
Please see inline...

> -----Original Message-----
> From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Dale Worley
> Sent: 12 July 2017 08:38
> To: gen-art@ietf.org
> Cc: draft-ietf-pce-pceps.all@ietf.org; pce@ietf.org; ietf@ietf.org
> Subject: [Pce] Genart last call review of draft-ietf-pce-pceps-14
>=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 treat these comments just like any other
> last call comments.
>=20
> For more information, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Document:  draft-ietf-pce-pceps-14
> Reviewer:  Dale R. Worley
> Review Date:  2017-07-11
> IETF LC End Date:  2017-07-12
> IESG Telechat date:  2017-08-03
>=20
> Summary:
>=20
>        This draft is basically ready for publication, but has nits
>        that should be fixed before publication.
>=20
> Nits/editorial comments:
>=20
> A few of these may rise to the level of minor technical issues,
> especially:
> section 3.2: whether error TBA2/2 is distinct from error 1/1=20
[[Dhruv Dhody]] The context of these error are different, one is before TLS=
 establishment (startTLS) and another is during PCEP session establishment =
(which is after TLS has been established). IMHO it is better to keep them d=
istinct.=20

section 3.2:
> the receipt of an PCErr during the failure of TLS
>              establishment
[[Dhruv Dhody]] The idea behind Error TBA2/3 and TBA2/4, is to let the peer=
 know if it is unwilling (or willing) to establish PCEP session without TLS=
 from this peer. This is useful information to figure out how the peer shou=
ld react without human intervention. =20
=20
> section 3.3: the distinction between StartTLSWait and OpenWait
[[Dhruv Dhody]] Both timers are wait timers but they wait for different mes=
sages and used in different context. Also the values can be set differently=
 based on the deployment.=20

> section 5:   a full discussion of backward compatibility considerations
[[Dhruv Dhody]] I have added some more details.=20

> section 8.2: MIB extension
[[Dhruv Dhody]] I have added some more details.

More details on above inline.=20

>=20
> 1.  Introduction
>=20
>    This document describes a security container for the transport of
>    PCEP messages, and therefore they do not affect the flexibility and
>    extensibility of PCEP.
>=20
> There is no plural antecedent for "they" to reference.  I think you could
> use "it", but the Editor may have better suggestions.
>=20

[[Dhruv Dhody]] Ack

> 3.2.  Initiating the TLS Procedures
>=20
>    with a PCErr message with Error-Type set to [TBA2 by IANA] (PCEP
>    StartTLS failure)
>=20
> It seems that we shouldn't use this Error-Type to object to the use of a
> message other than Open and StartTLS as an initial message, as that error
> isn't a misuse of StartTLS per se and is only incidentally related to
> StartTLS.  Indeed, isn't there already an Error-Type for this error
> (unexpected initial message), since two RFC 5440 implementations can
> commit/detect it?  Looking at RFC 5440 section 7.15, I see:
>=20
>    Error-Type    Meaning
>       1          PCEP session establishment failure
>                  Error-value=3D1: reception of an invalid Open message or
>                                 a non Open message.
>=20
> It seems to me that this document is adjusting the meaning of error 1/1,
> rather than defining a new error situation.
>=20
[[Dhruv Dhody]] We wanted to differentiate between the message exchanges du=
ring PCEP session establishment (which starts with open) and with StartTLS =
(which starts with StartTLS). Note that in case of TLS, we would move to th=
e PCEP session establishment phase after the TLS is established, and we cou=
ld still receive error 1/1.=20
Regarding TBA2/2, in case of PCEPS, a peer could respond with StartTls, Ope=
n or PCErr (but all in the context of this document), so we needed a new er=
ror. The peer was expecting StartTLS related message but something else hap=
pened and thus an error! IMHO putting this under "PCEP StartTLS failure" er=
ror-type is better!=20

Do you feel strongly about changing this?=20

>    If the PCEP speaker that does not support PCEPS, receives a StartTLS
>    message, it MUST behave according to the existing error mechanism
>    described in section 6.2 of [RFC5440] (in case message is received
>    prior to an Open message) or section 6.9 of [RFC5440] (for the case
>    of reception of unknown message).
>=20
> I think you want s/MUST/will/, since the described behavior isn't
> specified by this document, but rather by RFC 5440.

[[Dhruv Dhody]] Ack, updated.
>=20
> In any case, this paragraph might want to reference the backward-
> compatibility consideration that I would expect to appear in section 5 --
> How does the PCEPS-supporting element deal with the non-PCEPS-supporting
> element after the connection attempt with StartTLS fails?

 [[Dhruv Dhody]] I have added that in section 5.=20
>=20
>    After the exchange of startTLS messages, if a PCEP speaker cannot
>    establish a TLS connection for some reason (e.g. the required
>    mechanisms for certificate revocation checking are not available), it
>    MUST return a PCErr message (in clear) with Error-Type set to [TBA2
>    by IANA] (PCEP StartTLS failure) and Error-value set to:
>=20
> s/startTLS/StartTLS/

[[Dhruv Dhody]] Ack.
>=20
> Is there a well-defined way for a participant in a TLS connection start t=
o
> receive *either* a PCErr message in the clear *or* whatever comes next in
> TLS setup -- and know which case has happened?  Is there a way to use
> popular modular TLS libraries and have the application above the library
> receive such a PCErr message?  I don't understand TLS nearly well enough
> to know the answer to this, but it would probably help implementors if
> answers were given to these questions.

[[Dhruv Dhody]] If the TLS handshake is successful, both local and remote p=
arties are aware of this. Same is the case for TLS failure. So receiving an=
 error message in clear will not be a surprise.=20
Also, I checked some of the other documents that describe the use of TLS, b=
ut did not find any such handling.=20

>=20
>       The peer MAY choose to re-establish the PCEP session
>       without TLS next.
>=20
> I think you mean "The peer that initiated the connection MAY choose to re=
-
> establish ...".  As written, "the peer" seems to refer to the peer that
> generated the PCErr, but if it was the receiving peer that generated the
> PCErr, you probably don't want it to attempt to re-establish the session
> but rather wait for the initiating peer to do so.
>=20

[[Dhruv Dhody]] Ack. Changed peer to receiver.=20

>    Given the asymmetric nature of TLS for connection establishment it is
>    relevant to identify the roles of each of the PCEP peers in it.  The
>    PCC SHALL act as TLS client, and the PCE SHALL act as TLS server,
>    according to [RFC5246].
>=20
> See comments re section 4 about terminology.  I think you need to have
> terms for the element that is initiating the connection (either a PCC or =
a
> PCE) and the element that is receiving the connection (always a PCE).
>=20

[[Dhruv Dhody]] I have updated this.=20

> 3.3.  The StartTLS Message
>=20
>    Once the TCP connection has been successfully established and the
>    StartTLS message sent, the sender MUST start a timer called
>    StartTLSWait timer, after the expiration of which, if no StartTLS
>    message has been received, it MUST send a PCErr message and releases
>    the TCP connection with Error-Type set to [TBA2 by IANA] and Error-
>    value set to 5 (no StartTLS message received before the expiration of
>    the StartTLSWait timer).  A RECOMMENDED value for StartTLSWait timer
>    is 60 seconds.
>=20
> Really, the timer is the time to wait for *any* message to received.
> Open messages will cause start of upward-compatibility mechanisms (if any=
);
> any other message will be immediately rejected as an error.
>=20
> Indeed, isn't there already a timer which a peer uses to wait for the
> other peer to send a message?  Isn't StartTLSWait functionally the same a=
s
> OpenWait (RFC 5440 section 6.2)?
>=20

[[Dhruv Dhody]] I have updated the description, but I would still like to k=
eep a different timer similar to OpenWait and KeepWait (in the spirit of RF=
C 5440).=20

>    ... it MUST send a PCErr message and releases ...
>=20
> This sentence is grammatically interesting.  One part is logically "it
> MUST send a PCErr message".  The second part might be "it MUST release th=
e
> TCP connection", or "it releases the TCP connection".  Strictly speaking,
> the rules of English grammar cause the release/releases distinction to
> disambiguate whether MUST applies to both parts or only to the first part=
.
> But I don't think you want to rely on that, and you want to say "... and
> MUST release the TCP connection ...".

[[Dhruv Dhody]] Updated.

>=20
> 3.4.  TLS Connection Establishment
>=20
>    1.  Immediately negotiate TLS sessions according to [RFC5246].
>=20
> In this case, you'd say "Immediately negotiate a TLS session ...".

[[Dhruv Dhody]] Ack

>=20
> 3.5.  Peer Identity
>=20
>    At least the following parameters of the X.509 certificate SHOULD
>    be exposed:
>=20
>    o  Peer's IP address
>=20
>    o  Peer's fully qualified domain name (FQDN)
>=20
> To the naive (me), these two items seem to refer to the TCP connection
> that was established.  But I suspect that they're intended to refer to th=
e
> IP address and FQDN that might be encoded in the certificate (as in, "The
> following precedence applies: for DNS name validation, subjectAltName:DNS
> has precedence over CN; for IP address validation, subjectAltName:iPAddr
> has precedence over CN.")
>=20
> And it seems that the actual remote IP address of the TCP connection and
> whatever remote FQDN or IP address was used to initiate the connection
> should also be exposed to the administrative system.
>=20
> So I think there's room to expand on and clarify exactly the data items
> that are intended here.

[[Dhruv Dhody]] The statement above the list clearly state that this is the=
 information from X.509 certificate.
The TCP socket IP address is definitely known and exposed as that this way =
to identify a session. I have added this text -=20

"Note that the remote IP address used for the TCP session establishment is =
also exposed."

>=20
> 4.  Discovery Mechanisms
>=20
>    A PCE can advertise its capability to support PCEPS using the IGP
>    advertisement and discovery mechanism.
>=20
> If I understand this correctly, IGP is "Interior Gateway Protocol", and
> it's a category of protocols, not a specific protocol.  And what you're
> saying is that a PCE can advertise using the relevant IGP's mechanism.  I=
n
> that case, I think you'd say "the IGP's advertisement and discovery
> mechanism".  (Unless somehow IS-IS and OSPF are seen as variants of the
> same protocol, which can generically be called IGP.)
>=20

[[Dhruv Dhody]] Updated.

>    A new
>    capability flag bit for the PCE-CAP-FLAGS sub-TLV that can be
>    announced as attribute to distribute PCEP security support
>    information is proposed in [I-D.wu-pce-discovery-pceps-support]
>=20
> s/announced as attribute/announced as an attribute/.
>=20

[[Dhruv Dhody]] Updated.

> But you don't want to say "is proposed in ..." because that suggests that
> the proposal might not be approved, and you've already positively stated
> "A PCE can advertise ...".  So you want to say "A new capability flag ...
> is defined in ..." -- and raise draft-wu-pce-discovery-pceps-support to a
> normative reference.
>=20
> Similar considerations apply to discovery via DNS
> (draft-wu-pce-dns-pce-discovery) -- you want to mention it here and
> consider it a normative reference.
>=20
> -- Unless you choose to make this part of the section clearly hypothetica=
l
> by starting "This document does not specify any method a PCE can advertis=
e
> that it supports (or requires) PCEPS, but two mechanisms have been
> proposed:"

[[Dhruv Dhody]] I would like to avoid normative reference as these are=20
not mandatory and we would not want to block publication of this draft.=20
I have updated the text accordingly and removed the text from this document=
=20
Regarding DNS.=20

>=20
>    When DNS is used by a PCC (or a PCE acting as a client, for the rest
>    of the section, PCC refers to both) willing to use PCEPS to locate an
>    appropriate PCE [I-D.wu-pce-dns-pce-discovery], the PCC as an
>    initiating entity, chooses at least one of the returned FQDNs to
>    resolve, which it does by performing DNS "A" or "AAAA" lookups on the
>    FDQN.
>=20
> s/FDQN/FQDN/
>=20
> This one sentence uses the terms "acting as a client" and "as an
> initiating entity" to mean the same thing.  You should fix on one term.
> And given that the same concept arises in the discussion of TLS initiatio=
n
> (section 3.2), you probably want to define the term for "a PCC (or a PCE
> acting as a client)" near the beginning as document-wide terminology.
> Once you've got names for the concepts of the initiating entity and the
> receiving entity, a number of things in the document can then be stated
> more clearly.
>=20
>    If the PCC receives a response to its SRV query but it is not able to
>    establish a PCEPS connection using the data received in the response,
>    as initiating entity it MAY fall back to lookup a PCE that uses TCP
>    as transport.
>=20
> This is unclear -- if the process of resolving the original FQDN into
> addresses fails to produce an address that can be contacted, how can the
> PCC "fall back to lookup a PCE that uses TCP as transport" -- it has
> already done the looking up, and that failed.
>=20
> I suspect you mean that the PCC is required to first attempt to contact
> each address using TLS, and then only if all of those attempts fail is it
> then permitted to fall back to using TCP.  But you don't actually say tha=
t.
>=20

[[Dhruv Dhody]] I have removed the details from this document.=20

> 5.  Backward Compatibility
>=20
> It would help if this section gave a more comprehensive discussion of how
> PCEPS-supporting PCEs/PCCs and non-PCEPS-supporting PCEs/PCCs can
> interwork, i.e., how to incrementally deploy PCEPS into an AS.  The two
> major points seem to be (1) arranging that any two elements will
> communicate with the highest level of security that they both implement,
> and (2) any system of PCEPS-supporting and non-PCEPS-supporting elements
> can interwork successfully.  There probably are some "interesting"
> management and security issues involved in this.
>=20

[[Dhruv Dhody]] Updated.=20

   If a PCEP implementation that does not support PCEPS receives a
   StartTLS message, it would behave according to the existing error
   mechanism of [RFC5440].  On receiving the error, based on the local
   policy, a peer could try to establishing PCEP session without TLS as
   per the procedures defined in [RFC5440].  For successful TLS
   operations with PCEP, both PCEP peers in the network would need to be
   upgraded to support this document.

   An existing PCEP session cannot be upgraded to PCEPS, the session
   needs to be terminated and reestablished as per the procedure
   described in this document.  During the incremental upgrade, the PCEP
   speaker SHOULD allow session establishment with and without TLS.
   Once both PCEP speakers are upgraded to support PCEPS, the PCEP
   session is re-established with TLS, otherwise PCEP session without
   TLS is setup.  A redundant PCE MAY also be used during the
   incremental deployment to take over the PCE undergoing upgrade.  Once
   the upgrade is completed, support for unsecured version SHOULD be
   removed.

> 6.2.  New Error-Values
>=20
> I've noted above that the function of Error-Type=3DTBA2/Error-Value=3D2 s=
eems
> to duplicate that of Error-Type=3D1/Error-Value=3D1.
>=20

[[Dhruv Dhody]] See reply above.=20

> The meaning of Error-Type=3DTBA2 is named "StartTLS Failure" here, but th=
e
> rest of the text uses "StartTLS failure".  The table given in RFC
> 5440 section 7.15 is not consistent about capitalization in the names of
> Error-Types, but most entries do not capitalize non-initial words.
> That suggests "StartTLS failure" should be used here.

[[Dhruv Dhody]] Ack.

>=20
> 7.  Security Considerations
>=20
> There needs to be some consideration of interoperation of mixed PCEPS-
> capable and non-PCEPS-capable elements (unless such mixtures are NOT
> RECOMMENDED).
>=20

[[Dhruv Dhody]] yes strict TLS is recommended.=20
.

> 8.1.  Control of Function and Policy
>=20
>    A PCEP implementation SHOULD allow configuring the following PCEP
>    security parameters:
>=20
>    o  StartTLSWait timer value
>=20
>    PCEPS implementations MAY provide ...
>=20
> If I read this correctly, there is only one security parameter in this
> list.  But since the text says "the following PCEP security parameters:",
> on my first reading, I assumed that "PCEPS implementation MAY provide ...=
"
> was the beginning of a second item (with the initial "o" omitted).
>=20

[[Dhruv Dhody]] Updated.

>    provide ways for the operator to complete the following tasks:
>=20
> It looks like all of the following tasks are with regard to a selected
> PCEP session, though only the first task is labeled as such, whereas the
> 2nd through 4th are not.  It seems like you want to say "to complete the
> following tasks in regard to any PCEP session:" and change the 1st to
> "Determine if the session is protected via PCEPS."
>=20

[[Dhruv Dhody]] Updated.

> 8.2.  Information and Data Models
>=20
>    The PCEP MIB module SHOULD be extended to include PCEPS capabilities,
>    information, and status.
>=20
> This isn't a "SHOULD" because it isn't a constraint on implementations,
> it's a statement of what would be a desirable action by the IETF. --
> Unless the idea is that the implementor SHOULD add a (necessarily
> proprietary) extension to the MIB.  In any case, RFC 7420 should be
> referenced.)
>=20

[[Dhruv Dhody]] Ack.

> 8.4.  Verify Correct Operations
>=20
> This section title is a verb phrase while the rest of the titles are noun
> phrases.  Perhaps "Verification of Correct Operations".
>=20

[[Dhruv Dhody]] Changed to "Verifying Correct Operation".

> 8.5.  Requirements on Other Protocols
>=20
>    Mechanisms defined in this document do not imply any new requirements
>    on other protocols.
>=20
> There is a correlated discovery mechanism:
> draft-wu-pce-discovery-pceps-support defines a correlated change to OSPF
> and IS-IS.  I suppose that isn't *required* by this document, as draft-wu=
-
> pce-dns-pce-discovery or configuration might be used.  But conceptually,
> the two discovery mechanisms are implied by this document.
>=20

[[Dhruv Dhody]] Ack.

> 10.1.  Normative References
>=20
> It seems to me that draft-wu-pce-discovery-pceps-support and draft-wu-pce=
-
> dns-pce-discovery should be considered normative references.
>=20
>=20

[[Dhruv Dhody]] Updated the text so that they could remain informative.=20

Thanks again for your review.=20
I have attached the working copy and the diff.=20

Regards,
Dhruv

> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce

--_003_23CE718903A838468A8B325B80962F9B8CB95DF7blreml501mbb_
Content-Type: text/plain; name="draft-ietf-pce-pceps-15.txt"
Content-Description: draft-ietf-pce-pceps-15.txt
Content-Disposition: attachment; filename="draft-ietf-pce-pceps-15.txt";
	size=44700; creation-date="Fri, 28 Jul 2017 10:21:02 GMT";
	modification-date="Fri, 28 Jul 2017 10:21:02 GMT"
Content-Transfer-Encoding: base64

CgoKClBDRSBXb3JraW5nIEdyb3VwICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICBELiBMb3BlegpJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIE8uIEdvbnphbGV6IGRlIERpb3MKVXBkYXRlczogNTQ0MCAoaWYgYXBw
cm92ZWQpICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFRlbGVmb25pY2EgSStECkludGVu
ZGVkIHN0YXR1czogU3RhbmRhcmRzIFRyYWNrICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICBRLiBXdQpFeHBpcmVzOiBKYW51YXJ5IDI5LCAyMDE4ICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgRC4gRGhvZHkKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgSHVhd2VpCiAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgSnVseSAyOCwgMjAx
NwoKCiAgICAgICAgICAgICAgICAgICAgICAgU2VjdXJlIFRyYW5zcG9ydCBmb3IgUENFUAogICAg
ICAgICAgICAgICAgICAgICAgICBkcmFmdC1pZXRmLXBjZS1wY2Vwcy0xNQoKQWJzdHJhY3QKCiAg
IFRoZSBQYXRoIENvbXB1dGF0aW9uIEVsZW1lbnQgQ29tbXVuaWNhdGlvbiBQcm90b2NvbCAoUENF
UCkgZGVmaW5lcwogICB0aGUgbWVjaGFuaXNtcyBmb3IgdGhlIGNvbW11bmljYXRpb24gYmV0d2Vl
biBhIFBhdGggQ29tcHV0YXRpb24KICAgQ2xpZW50IChQQ0MpIGFuZCBhIFBhdGggQ29tcHV0YXRp
b24gRWxlbWVudCAoUENFKSwgb3IgYW1vbmcgUENFcy4KICAgVGhpcyBkb2N1bWVudCBkZXNjcmli
ZSB0aGUgdXNhZ2Ugb2YgVHJhbnNwb3J0IExheWVyIFNlY3VyaXR5IChUTFMpIHRvCiAgIGVuaGFu
Y2UgUENFUCBzZWN1cml0eSwgaGVuY2UgdGhlIFBDRVBTIGFjcm9ueW0gcHJvcG9zZWQgZm9yIGl0
LiAgVGhlCiAgIGFkZGl0aW9uYWwgc2VjdXJpdHkgbWVjaGFuaXNtcyBhcmUgcHJvdmlkZWQgYnkg
dGhlIHRyYW5zcG9ydCBwcm90b2NvbAogICBzdXBwb3J0aW5nIFBDRVAsIGFuZCB0aGVyZWZvcmUg
dGhleSBkbyBub3QgYWZmZWN0IHRoZSBmbGV4aWJpbGl0eSBhbmQKICAgZXh0ZW5zaWJpbGl0eSBv
ZiBQQ0VQLgoKICAgVGhpcyBkb2N1bWVudCB1cGRhdGVzIFJGQyA1NDQwIHJlZ2FyZGluZyB0aGUg
UENFUCBpbml0aWFsaXphdGlvbgogICBwaGFzZSBzcGVjaWZpY2F0aW9uLgoKU3RhdHVzIG9mIFRo
aXMgTWVtbwoKICAgVGhpcyBJbnRlcm5ldC1EcmFmdCBpcyBzdWJtaXR0ZWQgaW4gZnVsbCBjb25m
b3JtYW5jZSB3aXRoIHRoZQogICBwcm92aXNpb25zIG9mIEJDUCA3OCBhbmQgQkNQIDc5LgoKICAg
SW50ZXJuZXQtRHJhZnRzIGFyZSB3b3JraW5nIGRvY3VtZW50cyBvZiB0aGUgSW50ZXJuZXQgRW5n
aW5lZXJpbmcKICAgVGFzayBGb3JjZSAoSUVURikuICBOb3RlIHRoYXQgb3RoZXIgZ3JvdXBzIG1h
eSBhbHNvIGRpc3RyaWJ1dGUKICAgd29ya2luZyBkb2N1bWVudHMgYXMgSW50ZXJuZXQtRHJhZnRz
LiAgVGhlIGxpc3Qgb2YgY3VycmVudCBJbnRlcm5ldC0KICAgRHJhZnRzIGlzIGF0IGh0dHA6Ly9k
YXRhdHJhY2tlci5pZXRmLm9yZy9kcmFmdHMvY3VycmVudC8uCgogICBJbnRlcm5ldC1EcmFmdHMg
YXJlIGRyYWZ0IGRvY3VtZW50cyB2YWxpZCBmb3IgYSBtYXhpbXVtIG9mIHNpeCBtb250aHMKICAg
YW5kIG1heSBiZSB1cGRhdGVkLCByZXBsYWNlZCwgb3Igb2Jzb2xldGVkIGJ5IG90aGVyIGRvY3Vt
ZW50cyBhdCBhbnkKICAgdGltZS4gIEl0IGlzIGluYXBwcm9wcmlhdGUgdG8gdXNlIEludGVybmV0
LURyYWZ0cyBhcyByZWZlcmVuY2UKICAgbWF0ZXJpYWwgb3IgdG8gY2l0ZSB0aGVtIG90aGVyIHRo
YW4gYXMgIndvcmsgaW4gcHJvZ3Jlc3MuIgoKICAgVGhpcyBJbnRlcm5ldC1EcmFmdCB3aWxsIGV4
cGlyZSBvbiBKYW51YXJ5IDI5LCAyMDE4LgoKQ29weXJpZ2h0IE5vdGljZQoKICAgQ29weXJpZ2h0
IChjKSAyMDE3IElFVEYgVHJ1c3QgYW5kIHRoZSBwZXJzb25zIGlkZW50aWZpZWQgYXMgdGhlCiAg
IGRvY3VtZW50IGF1dGhvcnMuICBBbGwgcmlnaHRzIHJlc2VydmVkLgoKCgoKTG9wZXosIGV0IGFs
LiAgICAgICAgICAgRXhwaXJlcyBKYW51YXJ5IDI5LCAyMDE4ICAgICAgICAgICAgICAgIFtQYWdl
IDFdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgU2VjdXJlIFRyYW5zcG9ydCBmb3IgUENFUCAg
ICAgICAgICAgICAgSnVseSAyMDE3CgoKICAgVGhpcyBkb2N1bWVudCBpcyBzdWJqZWN0IHRvIEJD
UCA3OCBhbmQgdGhlIElFVEYgVHJ1c3QncyBMZWdhbAogICBQcm92aXNpb25zIFJlbGF0aW5nIHRv
IElFVEYgRG9jdW1lbnRzCiAgIChodHRwOi8vdHJ1c3RlZS5pZXRmLm9yZy9saWNlbnNlLWluZm8p
IGluIGVmZmVjdCBvbiB0aGUgZGF0ZSBvZgogICBwdWJsaWNhdGlvbiBvZiB0aGlzIGRvY3VtZW50
LiAgUGxlYXNlIHJldmlldyB0aGVzZSBkb2N1bWVudHMKICAgY2FyZWZ1bGx5LCBhcyB0aGV5IGRl
c2NyaWJlIHlvdXIgcmlnaHRzIGFuZCByZXN0cmljdGlvbnMgd2l0aCByZXNwZWN0CiAgIHRvIHRo
aXMgZG9jdW1lbnQuICBDb2RlIENvbXBvbmVudHMgZXh0cmFjdGVkIGZyb20gdGhpcyBkb2N1bWVu
dCBtdXN0CiAgIGluY2x1ZGUgU2ltcGxpZmllZCBCU0QgTGljZW5zZSB0ZXh0IGFzIGRlc2NyaWJl
ZCBpbiBTZWN0aW9uIDQuZSBvZgogICB0aGUgVHJ1c3QgTGVnYWwgUHJvdmlzaW9ucyBhbmQgYXJl
IHByb3ZpZGVkIHdpdGhvdXQgd2FycmFudHkgYXMKICAgZGVzY3JpYmVkIGluIHRoZSBTaW1wbGlm
aWVkIEJTRCBMaWNlbnNlLgoKICAgVGhpcyBkb2N1bWVudCBtYXkgY29udGFpbiBtYXRlcmlhbCBm
cm9tIElFVEYgRG9jdW1lbnRzIG9yIElFVEYKICAgQ29udHJpYnV0aW9ucyBwdWJsaXNoZWQgb3Ig
bWFkZSBwdWJsaWNseSBhdmFpbGFibGUgYmVmb3JlIE5vdmVtYmVyCiAgIDEwLCAyMDA4LiAgVGhl
IHBlcnNvbihzKSBjb250cm9sbGluZyB0aGUgY29weXJpZ2h0IGluIHNvbWUgb2YgdGhpcwogICBt
YXRlcmlhbCBtYXkgbm90IGhhdmUgZ3JhbnRlZCB0aGUgSUVURiBUcnVzdCB0aGUgcmlnaHQgdG8g
YWxsb3cKICAgbW9kaWZpY2F0aW9ucyBvZiBzdWNoIG1hdGVyaWFsIG91dHNpZGUgdGhlIElFVEYg
U3RhbmRhcmRzIFByb2Nlc3MuCiAgIFdpdGhvdXQgb2J0YWluaW5nIGFuIGFkZXF1YXRlIGxpY2Vu
c2UgZnJvbSB0aGUgcGVyc29uKHMpIGNvbnRyb2xsaW5nCiAgIHRoZSBjb3B5cmlnaHQgaW4gc3Vj
aCBtYXRlcmlhbHMsIHRoaXMgZG9jdW1lbnQgbWF5IG5vdCBiZSBtb2RpZmllZAogICBvdXRzaWRl
IHRoZSBJRVRGIFN0YW5kYXJkcyBQcm9jZXNzLCBhbmQgZGVyaXZhdGl2ZSB3b3JrcyBvZiBpdCBt
YXkKICAgbm90IGJlIGNyZWF0ZWQgb3V0c2lkZSB0aGUgSUVURiBTdGFuZGFyZHMgUHJvY2Vzcywg
ZXhjZXB0IHRvIGZvcm1hdAogICBpdCBmb3IgcHVibGljYXRpb24gYXMgYW4gUkZDIG9yIHRvIHRy
YW5zbGF0ZSBpdCBpbnRvIGxhbmd1YWdlcyBvdGhlcgogICB0aGFuIEVuZ2xpc2guCgpUYWJsZSBv
ZiBDb250ZW50cwoKICAgMS4gIEludHJvZHVjdGlvbiAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gICAzCiAgIDIuICBSZXF1aXJlbWVudHMgTGFuZ3VhZ2Ug
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgNAogICAzLiAgQXBwbHlp
bmcgUENFUFMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAg
IDQKICAgICAzLjEuICBPdmVydmlldyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gICA0CiAgICAgMy4yLiAgSW5pdGlhdGluZyB0aGUgVExTIFByb2NlZHVy
ZXMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgNAogICAgIDMuMy4gIFRoZSBTdGFydFRM
UyBNZXNzYWdlICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDYKICAgICAz
LjQuICBUTFMgQ29ubmVjdGlvbiBFc3RhYmxpc2htZW50ICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gICA4CiAgICAgMy41LiAgUGVlciBJZGVudGl0eSAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxMAogICAgIDMuNi4gIENvbm5lY3Rpb24gRXN0YWJsaXNo
bWVudCBGYWlsdXJlICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTEKICAgNC4gIERpc2NvdmVy
eSBNZWNoYW5pc21zICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDEy
CiAgICAgNC4xLiAgREFORSBBcHBsaWNhYmlsaXR5ICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuICAxMgogICA1LiAgQmFja3dhcmQgQ29tcGF0aWJpbGl0eSAgLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTIKICAgNi4gIElBTkEgQ29uc2lkZXJhdGlv
bnMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDEzCiAgICAgNi4x
LiAgTmV3IFBDRVAgTWVzc2FnZSAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuICAxMwogICAgIDYuMi4gIE5ldyBFcnJvci1WYWx1ZXMgIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAgMTMKICAgNy4gIFNlY3VyaXR5IENvbnNpZGVyYXRpb25zIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDE0CiAgIDguICBNYW5hZ2VhYmls
aXR5IENvbnNpZGVyYXRpb25zICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxNQog
ICAgIDguMS4gIENvbnRyb2wgb2YgRnVuY3Rpb24gYW5kIFBvbGljeSAgLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAgMTUKICAgICA4LjIuICBJbmZvcm1hdGlvbiBhbmQgRGF0YSBNb2RlbHMgLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDE2CiAgICAgOC4zLiAgTGl2ZW5lc3MgRGV0ZWN0
aW9uIGFuZCBNb25pdG9yaW5nIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxNgogICAgIDguNC4g
IFZlcmlmeWluZyBDb3JyZWN0IE9wZXJhdGlvbnMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAgMTYKICAgICA4LjUuICBSZXF1aXJlbWVudHMgb24gT3RoZXIgUHJvdG9jb2xzIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gIDE2CiAgICAgOC42LiAgSW1wYWN0IG9uIE5ldHdvcmsgT3BlcmF0
aW9uIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxNgogICA5LiAgQWNrbm93bGVkZ2Vt
ZW50cyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTYKCgoK
TG9wZXosIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBKYW51YXJ5IDI5LCAyMDE4ICAgICAgICAg
ICAgICAgIFtQYWdlIDJdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgU2VjdXJlIFRyYW5zcG9y
dCBmb3IgUENFUCAgICAgICAgICAgICAgSnVseSAyMDE3CgoKICAgMTAuIFJlZmVyZW5jZXMgIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDE3CiAgICAg
MTAuMS4gIE5vcm1hdGl2ZSBSZWZlcmVuY2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuICAxNwogICAgIDEwLjIuICBJbmZvcm1hdGl2ZSBSZWZlcmVuY2VzIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTgKICAgQXV0aG9ycycgQWRkcmVzc2VzICAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDIwCgoxLiAgSW50cm9kdWN0
aW9uCgogICBUaGUgUGF0aCBDb21wdXRhdGlvbiBFbGVtZW50IENvbW11bmljYXRpb24gUHJvdG9j
b2wgKFBDRVApIFtSRkM1NDQwXQogICBkZWZpbmVzIHRoZSBtZWNoYW5pc21zIGZvciB0aGUgY29t
bXVuaWNhdGlvbiBiZXR3ZWVuIGEgUGF0aAogICBDb21wdXRhdGlvbiBDbGllbnQgKFBDQykgYW5k
IGEgUGF0aCBDb21wdXRhdGlvbiBFbGVtZW50IChQQ0UpLCBvcgogICBiZXR3ZWVuIHR3byBQQ0Vz
LiAgVGhlc2UgaW50ZXJhY3Rpb25zIGluY2x1ZGUgcmVxdWVzdHMgYW5kIHJlcGxpZXMKICAgdGhh
dCBjYW4gYmUgY3JpdGljYWwgZm9yIGEgc3VzdGFpbmFibGUgbmV0d29yayBvcGVyYXRpb24gYW5k
IGFkZXF1YXRlCiAgIHJlc291cmNlIGFsbG9jYXRpb24sIGFuZCB0aGVyZWZvcmUgYXBwcm9wcmlh
dGUgc2VjdXJpdHkgYmVjb21lcyBhIGtleQogICBlbGVtZW50IGluIHRoZSBQQ0UgaW5mcmFzdHJ1
Y3R1cmUuICBBcyB0aGUgYXBwbGljYXRpb25zIG9mIHRoZSBQQ0UKICAgZnJhbWV3b3JrIGV2b2x2
ZXMsIGFuZCBtb3JlIGNvbXBsZXggc2VydmljZSBwYXR0ZXJucyBlbWVyZ2UsIHRoZQogICBkZWZp
bml0aW9uIG9mIGEgc2VjdXJlIG1vZGUgb2Ygb3BlcmF0aW9uIGJlY29tZXMgbW9yZSByZWxldmFu
dC4KCiAgIFtSRkM1NDQwXSBhbmFseXplcyBpbiBpdHMgc2VjdGlvbiBvbiBzZWN1cml0eSBjb25z
aWRlcmF0aW9ucyB0aGUKICAgcG90ZW50aWFsIHRocmVhdHMgdG8gUENFUCBhbmQgdGhlaXIgY29u
c2VxdWVuY2VzLCBhbmQgZGlzY3Vzc2VzCiAgIHNldmVyYWwgbWVjaGFuaXNtcyBmb3IgcHJvdGVj
dGluZyBQQ0VQIGFnYWluc3Qgc2VjdXJpdHkgYXR0YWNrcywKICAgd2l0aG91dCBtYWtpbmcgYSBz
cGVjaWZpYyByZWNvbW1lbmRhdGlvbiBvbiBhIHBhcnRpY3VsYXIgb25lIG9yCiAgIGRlZmluaW5n
IHRoZWlyIGFwcGxpY2F0aW9uIGluIGRlcHRoLiAgTW9yZW92ZXIsIFtSRkM2OTUyXSByZW1hcmtz
IHRoZQogICBpbXBvcnRhbmNlIG9mIGVuc3VyaW5nIFBDRVAgY29tbXVuaWNhdGlvbiBwcml2YWN5
LCBlc3BlY2lhbGx5IHdoZW4KICAgUENFUCBjb21tdW5pY2F0aW9uIGVuZHBvaW50cyBkbyBub3Qg
cmVzaWRlIGluIHRoZSBzYW1lIEF1dG9ub21vdXMKICAgU3lzdGVtIChBUyksIGFzIHRoZSBpbnRl
cmNlcHRpb24gb2YgUENFUCBtZXNzYWdlcyBjb3VsZCBsZWFrCiAgIHNlbnNpdGl2ZSBpbmZvcm1h
dGlvbiByZWxhdGVkIHRvIGNvbXB1dGVkIHBhdGhzIGFuZCByZXNvdXJjZXMuCgogICBBbW9uZyB0
aGUgcG9zc2libGUgc29sdXRpb25zIG1lbnRpb25lZCBpbiB0aGVzZSBkb2N1bWVudHMsIFRyYW5z
cG9ydAogICBMYXllciBTZWN1cml0eSAoVExTKSBbUkZDNTI0Nl0gcHJvdmlkZXMgc3VwcG9ydCBm
b3IgcGVlcgogICBhdXRoZW50aWNhdGlvbiwgYW5kIG1lc3NhZ2UgZW5jcnlwdGlvbiBhbmQgaW50
ZWdyaXR5LiAgVExTIHN1cHBvcnRzCiAgIHRoZSB1c2FnZSBvZiB3ZWxsLWtub3duIG1lY2hhbmlz
bXMgdG8gc3VwcG9ydCBrZXkgY29uZmlndXJhdGlvbiBhbmQKICAgZXhjaGFuZ2UsIGFuZCBtZWFu
cyB0byBwZXJmb3JtIHNlY3VyaXR5IGNoZWNrcyBvbiB0aGUgcmVzdWx0cyBvZiBQQ0UKICAgZGlz
Y292ZXJ5IHByb2NlZHVyZXMgdmlhIEludGVyaW9yIEdhdGV3YXkgUHJvdG9jb2wgKElHUCkgKFtS
RkM1MDg4XQogICBhbmQgW1JGQzUwODldKS4KCiAgIFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzIGEg
c2VjdXJpdHkgY29udGFpbmVyIGZvciB0aGUgdHJhbnNwb3J0IG9mCiAgIFBDRVAgbWVzc2FnZXMs
IGFuZCB0aGVyZWZvcmUgaXQgZG9lcyBub3QgYWZmZWN0IHRoZSBmbGV4aWJpbGl0eSBhbmQKICAg
ZXh0ZW5zaWJpbGl0eSBvZiBQQ0VQLgoKICAgVGhpcyBkb2N1bWVudCBkZXNjcmliZXMgaG93IHRv
IGFwcGx5IFRMUyBpbiBzZWN1cmluZyBQQ0UKICAgaW50ZXJhY3Rpb25zLCBpbmNsdWRpbmcgaW5p
dGlhdGlvbiBvZiB0aGUgVExTIHByb2NlZHVyZXMsIHRoZSBUTFMKICAgaGFuZHNoYWtlIG1lY2hh
bmlzbXMsIHRoZSBUTFMgbWV0aG9kcyBmb3IgcGVlciBhdXRoZW50aWNhdGlvbiwgdGhlCiAgIGFw
cGxpY2FibGUgVExTIGNpcGhlcnN1aXRlcyBmb3IgZGF0YSBleGNoYW5nZSwgYW5kIHRoZSBoYW5k
bGluZyBvZgogICBlcnJvcnMgaW4gdGhlIHNlY3VyaXR5IGNoZWNrcy4gIEluIHRoZSByZXN0IG9m
IHRoZSBkb2N1bWVudCB3ZSB3aWxsCiAgIHJlZmVyIHRvIHRoaXMgdXNhZ2Ugb2YgVExTIHRvIHBy
b3ZpZGUgYSBzZWN1cmUgdHJhbnNwb3J0IGZvciBQQ0VQIGFzCiAgICJQQ0VQUyIuCgoKCgoKTG9w
ZXosIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBKYW51YXJ5IDI5LCAyMDE4ICAgICAgICAgICAg
ICAgIFtQYWdlIDNdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgU2VjdXJlIFRyYW5zcG9ydCBm
b3IgUENFUCAgICAgICAgICAgICAgSnVseSAyMDE3CgoKICAgV2l0aGluIHRoaXMgZG9jdW1lbnQs
IFBDRVAgY29tbXVuaWNhdGlvbnMgYXJlIGRlc2NyaWJlZCB0aHJvdWdoIFBDQy0KICAgUENFIHJl
bGF0aW9uc2hpcC4gIFRoZSBQQ0UgYXJjaGl0ZWN0dXJlIGFsc28gc3VwcG9ydHMgdGhlIFBDRS1Q
Q0UKICAgY29tbXVuaWNhdGlvbiwgYnkgaGF2aW5nIHRoZSByZXF1ZXN0aW5nIFBDRSBmaWxsIHRo
ZSByb2xlIG9mIGEgUENDLAogICBhcyB1c3VhbC4gIFRodXMsIHRoZSBQQ0MgcmVmZXJzIHRvIGEg
UENDIG9yIGEgUENFIGluaXRpYXRpbmcgdGhlIFBDRVAKICAgc2Vzc2lvbiBhbmQgYWN0aW5nIGFz
IGEgY2xpZW50LgoKMi4gIFJlcXVpcmVtZW50cyBMYW5ndWFnZQoKICAgVGhlIGtleSB3b3JkcyAi
TVVTVCIsICJNVVNUIE5PVCIsICJSRVFVSVJFRCIsICJTSEFMTCIsICJTSEFMTCBOT1QiLAogICAi
U0hPVUxEIiwgIlNIT1VMRCBOT1QiLCAiUkVDT01NRU5ERUQiLCAiTUFZIiwgYW5kICJPUFRJT05B
TCIgaW4gdGhpcwogICBkb2N1bWVudCBhcmUgdG8gYmUgaW50ZXJwcmV0ZWQgYXMgZGVzY3JpYmVk
IGluIFtSRkMyMTE5XS4KCjMuICBBcHBseWluZyBQQ0VQUwoKMy4xLiAgT3ZlcnZpZXcKCiAgIFRo
ZSBzdGVwcyBpbnZvbHZlZCBpbiBlc3RhYmxpc2hpbmcgYSBQQ0VQUyBzZXNzaW9uIGFyZSBhcyBm
b2xsb3dzOgoKICAgMS4gIEVzdGFibGlzaG1lbnQgb2YgYSBUQ1AgY29ubmVjdGlvbi4KCiAgIDIu
ICBJbml0aWF0aW5nIHRoZSBUTFMgcHJvY2VkdXJlcyBieSB0aGUgU3RhcnRUTFMgbWVzc2FnZSBm
cm9tIFBDRSB0bwogICAgICAgUENDIGFuZCBmcm9tIFBDQyB0byBQQ0UuCgogICAzLiAgRXN0YWJs
aXNobWVudCBvZiBUTFMgY29ubmVjdGlvbi4KCiAgIDQuICBTdGFydCBleGNoYW5naW5nIFBDRVAg
bWVzc2FnZXMgYXMgcGVyIFtSRkM1NDQwXS4KCiAgIEltcGxlbWVudGF0aW9ucyBTSE9VTEQgZm9s
bG93IHRoZSBiZXN0IHByYWN0aWNlcyBhbmQgcmVjb21tZW5kYXRpb25zCiAgIGZvciB1c2luZyBU
TFMsIGFzIHBlciBbUkZDNzUyNV0uCgogICBJdCBzaG91bGQgYmUgbm90ZWQgdGhhdCB0aGlzIHBy
b2NlZHVyZSB1cGRhdGVzIHdoYXQgaXMgZGVmaW5lZCBpbgogICBzZWN0aW9uIDQuMi4xIGFuZCBz
ZWN0aW9uIDYuNyBvZiBbUkZDNTQ0MF0gcmVnYXJkaW5nIHRoZQogICBpbml0aWFsaXphdGlvbiBw
aGFzZSBhbmQgdGhlIHByb2Nlc3Npbmcgb2YgbWVzc2FnZXMgcHJpb3IgdG8gdGhlIE9wZW4KICAg
bWVzc2FnZS4gIFRoZSBkZXRhaWxzIG9mIHByb2Nlc3NpbmcgaW5jbHVkaW5nIGJhY2t3YXJkIGNv
bXBhdGliaWxpdHkKICAgYXJlIGRpc2N1c3NlZCBpbiB0aGUgZm9sbG93aW5nIHNlY3Rpb25zLgoK
My4yLiAgSW5pdGlhdGluZyB0aGUgVExTIFByb2NlZHVyZXMKCiAgIFNpbmNlIFBDRVAgY2FuIG9w
ZXJhdGUgZWl0aGVyIHdpdGggb3Igd2l0aG91dCBUTFMsIGl0IGlzIG5lY2Vzc2FyeQogICBmb3Ig
dGhlIFBDRVAgc3BlYWtlciB0byBpbmRpY2F0ZSB3aGV0aGVyIGl0IHdhbnRzIHRvIHNldCB1cCBh
IFRMUwogICBjb25uZWN0aW9uIG9yIG5vdC4gIEZvciB0aGlzIHB1cnBvc2UsIHRoaXMgZG9jdW1l
bnQgc3BlY2lmaWVzIGEgbmV3CiAgIFBDRVAgbWVzc2FnZSBjYWxsZWQgU3RhcnRUTFMuICBUaHVz
IHRoZSBQQ0VQIHNlc3Npb24gaXMgc2VjdXJlZCB2aWEKICAgVExTIGZyb20gdGhlIHN0YXJ0IGJl
Zm9yZSBleGNoYW5nZSBvZiBhbnkgb3RoZXIgUENFUCBtZXNzYWdlICh0aGF0CiAgIGluY2x1ZGVz
IHRoZSBPcGVuIG1lc3NhZ2UpLiAgVGhpcyBkb2N1bWVudCB0aHVzIHVwZGF0ZXMgW1JGQzU0NDBd
LAogICB3aGljaCByZXF1aXJlZCB0aGUgT3BlbiBtZXNzYWdlIHRvIGJlIHRoZSBmaXJzdCBQQ0VQ
IG1lc3NhZ2UuICBJbiB0aGUKICAgY2FzZSBvZiBhIFBDRVAgc2Vzc2lvbiB1c2luZyBUTFMgdGhl
IFN0YXJ0VExTIG1lc3NhZ2Ugd2lsbCBiZSBzZW50CiAgIGZpcnN0LgoKCgoKTG9wZXosIGV0IGFs
LiAgICAgICAgICAgRXhwaXJlcyBKYW51YXJ5IDI5LCAyMDE4ICAgICAgICAgICAgICAgIFtQYWdl
IDRdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgU2VjdXJlIFRyYW5zcG9ydCBmb3IgUENFUCAg
ICAgICAgICAgICAgSnVseSAyMDE3CgoKICAgVGhlIFBDRVAgc3BlYWtlciBNQVkgZGlzY292ZXIg
dGhhdCB0aGUgUENFUCBwZWVyIHN1cHBvcnRzIFBDRVBTIG9yCiAgIGNhbiBiZSBwcmVjb25maWd1
cmVkIHRvIHVzZSBQQ0VQUyBmb3IgYSBnaXZlbiBwZWVyIChzZWUgU2VjdGlvbiA0IGZvcgogICBt
b3JlIGRldGFpbHMpLiAgU2VjdXJpbmcgdmlhIFRMUyBvZiBhbiBleGlzdGluZyBQQ0VQIHNlc3Np
b24gaXMgbm90CiAgIHBlcm1pdHRlZCwgdGhlIHNlc3Npb24gTVVTVCBiZSBjbG9zZWQgYW5kIHJl
LWVzdGFibGlzaGVkIHdpdGggVExTIGFzCiAgIHBlciB0aGUgcHJvY2VkdXJlIGRlc2NyaWJlZCBp
biB0aGlzIGRvY3VtZW50LgoKICAgVGhlIFN0YXJ0VExTIG1lc3NhZ2UgaXMgYSBQQ0VQIG1lc3Nh
Z2Ugc2VudCBieSBhIFBDQyB0byBhIFBDRSBhbmQgYnkKICAgYSBQQ0UgdG8gYSBQQ0MgaW4gb3Jk
ZXIgdG8gaW5pdGlhdGUgdGhlIFRMUyBwcm9jZWR1cmUgZm9yIFBDRVAuICBUaGUKICAgTWVzc2Fn
ZS1UeXBlIGZpZWxkIG9mIHRoZSBQQ0VQIGNvbW1vbiBoZWFkZXIgZm9yIHRoZSBTdGFydFRMUyBt
ZXNzYWdlCiAgIGlzIHNldCB0byBbVEJBMSBieSBJQU5BXS4KCiAgIE9uY2UgdGhlIFRDUCBjb25u
ZWN0aW9uIGhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBlc3RhYmxpc2hlZCwgdGhlIGZpcnN0CiAgIG1l
c3NhZ2Ugc2VudCBieSB0aGUgUENDIHRvIHRoZSBQQ0UgYW5kIGJ5IHRoZSBQQ0UgdG8gdGhlIFBD
QyBNVVNUIGJlCiAgIGEgU3RhcnRUTFMgbWVzc2FnZSBmb3IgdGhlIFBDRVBTLiAgTm90ZSB0aGlz
IGlzIGEgc2lnbmlmaWNhbnQgY2hhbmdlCiAgIGZyb20gW1JGQzU0NDBdIHdoZXJlIHRoZSBmaXJz
dCBQQ0VQIG1lc3NhZ2UgaXMgdGhlIE9wZW4gbWVzc2FnZS4KCiAgIEEgUENFUCBzcGVha2VyIHJl
Y2VpdmluZyBhIFN0YXJ0VExTIG1lc3NhZ2UsIGFmdGVyIGFueSBvdGhlciBQQ0VQCiAgIGV4Y2hh
bmdlIGhhcyB0YWtlbiBwbGFjZSAoYnkgcmVjZWl2aW5nIG9yIHNlbmRpbmcgYW55IG90aGVyIG1l
c3NhZ2VzCiAgIGZyb20gZWl0aGVyIHNpZGUpIE1VU1QgdHJlYXQgaXQgYXMgYW4gdW5leHBlY3Rl
ZCBtZXNzYWdlIGFuZCByZXBseQogICB3aXRoIGEgUENFcnIgbWVzc2FnZSB3aXRoIEVycm9yLVR5
cGUgc2V0IHRvIFtUQkEyIGJ5IElBTkFdIChQQ0VQCiAgIFN0YXJ0VExTIGZhaWx1cmUpIGFuZCBF
cnJvci12YWx1ZSBzZXQgdG8gMSAocmVjZXB0aW9uIG9mIFN0YXJ0VExTCiAgIGFmdGVyIGFueSBQ
Q0VQIGV4Y2hhbmdlKSwgYW5kIE1VU1QgY2xvc2UgdGhlIFRDUCBjb25uZWN0aW9uLiAgQSBQQ0VQ
CiAgIHNwZWFrZXIgcmVjZWl2aW5nIGFueSBvdGhlciBtZXNzYWdlIGFwYXJ0IGZyb20gU3RhcnRU
TFMsIE9wZW4sIG9yCiAgIFBDRXJyIGFzIHRoZSBmaXJzdCBtZXNzYWdlLCBNVVNUIHRyZWF0IGl0
IGFzIGFuIHVuZXhwZWN0ZWQgbWVzc2FnZQogICBhbmQgcmVwbHkgd2l0aCBhIFBDRXJyIG1lc3Nh
Z2Ugd2l0aCBFcnJvci1UeXBlIHNldCB0byBbVEJBMiBieSBJQU5BXQogICAoUENFUCBTdGFydFRM
UyBmYWlsdXJlKSBhbmQgRXJyb3ItdmFsdWUgc2V0IHRvIDIgKHJlY2VwdGlvbiBvZiBhbnkKICAg
b3RoZXIgbWVzc2FnZSBhcGFydCBmcm9tIFN0YXJ0VExTLCBPcGVuLCBvciBQQ0VyciBtZXNzYWdl
KSwgYW5kIE1VU1QKICAgY2xvc2UgdGhlIFRDUCBjb25uZWN0aW9uLgoKICAgSWYgdGhlIFBDRVAg
c3BlYWtlciB0aGF0IGRvZXMgbm90IHN1cHBvcnQgUENFUFMsIHJlY2VpdmVzIGEgU3RhcnRUTFMK
ICAgbWVzc2FnZSwgaXQgd2lsbCBiZWhhdmUgYWNjb3JkaW5nIHRvIHRoZSBleGlzdGluZyBlcnJv
ciBtZWNoYW5pc20KICAgZGVzY3JpYmVkIGluIHNlY3Rpb24gNi4yIG9mIFtSRkM1NDQwXSAoaW4g
Y2FzZSBtZXNzYWdlIGlzIHJlY2VpdmVkCiAgIHByaW9yIHRvIGFuIE9wZW4gbWVzc2FnZSkgb3Ig
c2VjdGlvbiA2Ljkgb2YgW1JGQzU0NDBdIChmb3IgdGhlIGNhc2UKICAgb2YgcmVjZXB0aW9uIG9m
IHVua25vd24gbWVzc2FnZSkuICBTZWUgU2VjdGlvbiA1IGZvciBtb3JlIGRldGFpbHMuCgogICBB
ZnRlciB0aGUgZXhjaGFuZ2Ugb2YgU3RhcnRUTFMgbWVzc2FnZXMsIGlmIGEgUENFUCBzcGVha2Vy
IGNhbm5vdAogICBlc3RhYmxpc2ggYSBUTFMgY29ubmVjdGlvbiBmb3Igc29tZSByZWFzb24gKGUu
Zy4gdGhlIHJlcXVpcmVkCiAgIG1lY2hhbmlzbXMgZm9yIGNlcnRpZmljYXRlIHJldm9jYXRpb24g
Y2hlY2tpbmcgYXJlIG5vdCBhdmFpbGFibGUpLCBpdAogICBNVVNUIHJldHVybiBhIFBDRXJyIG1l
c3NhZ2UgKGluIGNsZWFyKSB3aXRoIEVycm9yLVR5cGUgc2V0IHRvIFtUQkEyCiAgIGJ5IElBTkFd
IChQQ0VQIFN0YXJ0VExTIGZhaWx1cmUpIGFuZCBFcnJvci12YWx1ZSBzZXQgdG86CgogICBvICAz
IChub3Qgd2l0aG91dCBUTFMpIGlmIGl0IGlzIG5vdCB3aWxsaW5nIHRvIGV4Y2hhbmdlIFBDRVAg
bWVzc2FnZXMKICAgICAgd2l0aG91dCB0aGUgc29saWNpdGVkIFRMUyBjb25uZWN0aW9uLCBhbmQg
aXQgTVVTVCBjbG9zZSB0aGUgVENQCiAgICAgIHNlc3Npb24uCgogICBvICA0IChvayB3aXRob3V0
IFRMUykgaWYgaXQgaXMgd2lsbGluZyB0byBleGNoYW5nZSBQQ0VQIG1lc3NhZ2VzCiAgICAgIHdp
dGhvdXQgdGhlIHNvbGljaXRlZCBUTFMgY29ubmVjdGlvbiwgYW5kIGl0IE1VU1QgY2xvc2UgdGhl
IFRDUAoKCgoKTG9wZXosIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBKYW51YXJ5IDI5LCAyMDE4
ICAgICAgICAgICAgICAgIFtQYWdlIDVdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgU2VjdXJl
IFRyYW5zcG9ydCBmb3IgUENFUCAgICAgICAgICAgICAgSnVseSAyMDE3CgoKICAgICAgc2Vzc2lv
bi4gIFRoZSByZWNlaXZlciBNQVkgY2hvb3NlIHRvIHJlLWVzdGFibGlzaCB0aGUgUENFUCBzZXNz
aW9uCiAgICAgIHdpdGhvdXQgVExTIG5leHQuCgogICBJZiB0aGUgUENFUCBzcGVha2VyIHN1cHBv
cnRzIFBDRVBTIGFuZCBjYW4gZXN0YWJsaXNoIGEgVExTIGNvbm5lY3Rpb24KICAgaXQgTVVTVCBz
dGFydCB0aGUgVExTIGNvbm5lY3Rpb24gZXN0YWJsaXNobWVudCBzdGVwcyBkZXNjcmliZWQgaW4K
ICAgU2VjdGlvbiAzLjQgYmVmb3JlIHRoZSBQQ0VQIGluaXRpYWxpemF0aW9uIHByb2NlZHVyZSAo
c2VjdGlvbiA0LjIuMQogICBvZiBbUkZDNTQ0MF0pLgoKICAgQSBQQ0VQIHNwZWFrZXIgdGhhdCBk
b2VzIG5vdCBzdXBwb3J0IFBDRVBTIG9yIGhhcyBsZWFybmVkIHRoZSBwZWVyCiAgIHdpbGxpbmdu
ZXNzIHRvIHJlZXN0YWJsaXNoIHNlc3Npb24gd2l0aG91dCBUTFMsIGNhbiBzZW5kIHRoZSBPcGVu
CiAgIG1lc3NhZ2UgZGlyZWN0bHksIGFzIHBlciBbUkZDNTQ0MF0uCgogICBHaXZlbiB0aGUgYXN5
bW1ldHJpYyBuYXR1cmUgb2YgVExTIGZvciBjb25uZWN0aW9uIGVzdGFibGlzaG1lbnQgaXQgaXMK
ICAgcmVsZXZhbnQgdG8gaWRlbnRpZnkgdGhlIHJvbGVzIG9mIGVhY2ggb2YgdGhlIFBDRVAgcGVl
cnMgaW4gaXQuICBUaGUKICAgUENDIFNIQUxMIGFjdCBhcyBUTFMgY2xpZW50LCBhbmQgdGhlIFBD
RSBTSEFMTCBhY3QgYXMgVExTIHNlcnZlciwKICAgYWNjb3JkaW5nIHRvIFtSRkM1MjQ2XS4KCiAg
IFRoZXNlIHByb2NlZHVyZXMgbWluaW1pemUgdGhlIGltcGFjdCBvZiBQQ0VQUyBzdXBwb3J0IGlu
IFBDRVAKICAgaW1wbGVtZW50YXRpb25zIHdpdGhvdXQgcmVxdWlyaW5nIGFkZGl0aW9uYWwgZGVk
aWNhdGVkIHBvcnRzIGZvcgogICBydW5uaW5nIFBDRVAgd2l0aCBUTFMuCgogICBBcyBwZXIgdGhl
IHJlY29tbWVuZGF0aW9uIGZyb20gW1JGQzc1MjVdIHRvIGF2b2lkIGRvd25ncmFkZSBhdHRhY2tz
LAogICBQQ0VQIHBlZXJzIHRoYXQgc3VwcG9ydCBQQ0VQUywgU0hPVUxEIGRlZmF1bHQgdG8gc3Ry
aWN0IFRMUwogICBjb25maWd1cmF0aW9uIGkuZS4gZG8gbm90IGFsbG93IG5vbi1UTFMgUENFUCBz
ZXNzaW9ucyB0byBiZQogICBlc3RhYmxpc2hlZC4gIFBDRVBTIGltcGxlbWVudGF0aW9ucyBNQVkg
cHJvdmlkZSBhbiBvcHRpb24gdG8gYWxsb3cKICAgdGhlIG9wZXJhdG9yIHRvIG1hbnVhbGx5IG92
ZXJyaWRlIHN0cmljdCBUTFMgY29uZmlndXJhdGlvbiBhbmQgYWxsb3cKICAgdW5zZWN1cmVkIGNv
bm5lY3Rpb25zLiAgRXhlY3V0aW9uIG9mIHRoaXMgb3ZlcnJpZGUgU0hPVUxEIHRyaWdnZXIgYQog
ICB3YXJuaW5nIGFib3V0IHRoZSBzZWN1cml0eSBpbXBsaWNhdGlvbnMgb2YgcGVybWl0dGluZyB1
bnNlY3VyZWQKICAgY29ubmVjdGlvbnMuCgozLjMuICBUaGUgU3RhcnRUTFMgTWVzc2FnZQoKICAg
VGhlIFN0YXJ0VExTIG1lc3NhZ2UgaXMgdXNlZCB0byBpbml0aWF0ZSB0aGUgVExTIHByb2NlZHVy
ZSBmb3IgYQogICBQQ0VQUyBzZXNzaW9uIGJldHdlZW4gdGhlIFBDRVAgcGVlcnMuICBBIFBDRVAg
c3BlYWtlciBzZW5kcyB0aGUKICAgU3RhcnRUTFMgbWVzc2FnZSB0byByZXF1ZXN0IG5lZ290aWF0
aW9uIGFuZCBlc3RhYmxpc2htZW50IG9mIFRMUwogICBjb25uZWN0aW9uIGZvciBQQ0VQLiAgT24g
cmVjZWl2aW5nIGEgU3RhcnRUTFMgbWVzc2FnZSBmcm9tIHRoZSBQQ0VQCiAgIHBlZXIgKGkuZS4g
IHdoZW4gdGhlIFBDRVAgc3BlYWtlciBoYXMgc2VudCBhbmQgcmVjZWl2ZWQgU3RhcnRUTFMKICAg
bWVzc2FnZSkgaXQgaXMgcmVhZHkgdG8gc3RhcnQgVExTIG5lZ290aWF0aW9uIGFuZCBlc3RhYmxp
c2htZW50IGFuZAogICBtb3ZlIHRvIHN0ZXBzIGRlc2NyaWJlZCBpbiBTZWN0aW9uIDMuNC4KCiAg
IFRoZSBjb2xsaXNpb24gcmVzb2x1dGlvbiBwcm9jZWR1cmVzIGRlc2NyaWJlZCBpbiBbUkZDNTQ0
MF0gZm9yIHRoZQogICBleGNoYW5nZSBvZiBPcGVuIG1lc3NhZ2VzIE1VU1QgYmUgYXBwbGllZCBi
eSB0aGUgUENFUCBwZWVycyBkdXJpbmcKICAgdGhlIGV4Y2hhbmdlIG9mIFN0YXJ0VExTIG1lc3Nh
Z2VzLgoKICAgVGhlIGZvcm1hdCBvZiBhIFN0YXJ0VExTIG1lc3NhZ2UgaXMgYXMgZm9sbG93czoK
CgoKCgoKTG9wZXosIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBKYW51YXJ5IDI5LCAyMDE4ICAg
ICAgICAgICAgICAgIFtQYWdlIDZdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgU2VjdXJlIFRy
YW5zcG9ydCBmb3IgUENFUCAgICAgICAgICAgICAgSnVseSAyMDE3CgoKICAgICAgPFN0YXJ0VExT
IE1lc3NhZ2U+Ojo9IDxDb21tb24gSGVhZGVyPgoKCiAgIFRoZSBTdGFydFRMUyBtZXNzYWdlIE1V
U1QgY29udGFpbiBvbmx5IHRoZSBQQ0VQIGNvbW1vbiBoZWFkZXIgd2l0aAogICBNZXNzYWdlLVR5
cGUgZmllbGQgc2V0IHRvIFtUQkExIGJ5IElBTkFdLgoKICAgT25jZSB0aGUgVENQIGNvbm5lY3Rp
b24gaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IGVzdGFibGlzaGVkIGFuZCB0aGUKICAgU3RhcnRUTFMg
bWVzc2FnZSBzZW50LCB0aGUgc2VuZGVyIE1VU1Qgc3RhcnQgYSB0aW1lciBjYWxsZWQKICAgU3Rh
cnRUTFNXYWl0IHRpbWVyLCBhZnRlciB0aGUgZXhwaXJhdGlvbiBvZiB3aGljaCwgaWYgbm8gU3Rh
cnRUTFMKICAgbWVzc2FnZSBoYXMgYmVlbiByZWNlaXZlZCAoYW5kIGluIGNhc2Ugb2YgZmFpbHVy
ZSwgYSBQQ0VyciBvciBPcGVuCiAgIG1lc3NhZ2UgaXMgbm90IHJlY2VpdmVkKSwgaXQgTVVTVCBz
ZW5kIGEgUENFcnIgbWVzc2FnZSB3aXRoIEVycm9yLQogICBUeXBlIHNldCB0byBbVEJBMiBieSBJ
QU5BXSBhbmQgRXJyb3ItdmFsdWUgc2V0IHRvIDUgKG5vIFN0YXJ0VExTIChub3IKICAgUENFcnIv
T3BlbikgbWVzc2FnZSByZWNlaXZlZCBiZWZvcmUgdGhlIGV4cGlyYXRpb24gb2YgdGhlCiAgIFN0
YXJ0VExTV2FpdCB0aW1lcikgYW5kIGl0IE1VU1QgcmVsZWFzZSB0aGUgVENQIGNvbm5lY3Rpb24g
LiBBCiAgIFJFQ09NTUVOREVEIHZhbHVlIGZvciBTdGFydFRMU1dhaXQgdGltZXIgaXMgNjAgc2Vj
b25kcy4KCgogICAgICAgICAgICAgICAgICArLSstKyAgICAgICAgICAgICAgICAgKy0rLSsKICAg
ICAgICAgICAgICAgICAgfFBDQ3wgICAgICAgICAgICAgICAgIHxQQ0V8CiAgICAgICAgICAgICAg
ICAgICstKy0rICAgICAgICAgICAgICAgICArLSstKwogICAgICAgICAgICAgICAgICAgIHwgICAg
ICAgICAgICAgICAgICAgICB8CiAgICAgICAgICAgICAgICAgICAgfCBTdGFydFRMUyAgICAgICAg
ICAgIHwKICAgICAgICAgICAgICAgICAgICB8IG1zZyAgICAgICAgICAgICAgICAgfAogICAgICAg
ICAgICAgICAgICAgIHwtLS0tLS0tICAgICAgICAgICAgICB8CiAgICAgICAgICAgICAgICAgICAg
fCAgICAgICBcICAgU3RhcnRUTFMgIHwKICAgICAgICAgICAgICAgICAgICB8ICAgICAgICBcICBt
c2cgICAgICAgfAogICAgICAgICAgICAgICAgICAgIHwgICAgICAgICBcICAtLS0tLS0tLS18CiAg
ICAgICAgICAgICAgICAgICAgfCAgICAgICAgICBcLyAgICAgICAgIHwKICAgICAgICAgICAgICAg
ICAgICB8ICAgICAgICAgIC9cICAgICAgICAgfAogICAgICAgICAgICAgICAgICAgIHwgICAgICAg
ICAvICAtLS0tLS0tLT58CiAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgLyAgICAgICAgICAg
IHwKICAgICAgICAgICAgICAgICAgICB8PC0tLS0tLSAgICAgICAgICAgICAgfAogICAgICAgICAg
ICAgICAgICAgIHw6Ojo6Ojo6OjpUTFM6Ojo6Ojo6Ojp8CiAgICAgICAgICAgICAgICAgICAgfDo6
Ojo6RXN0YWJsaXNobWVudDo6OnwKICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAg
ICAgICAgfAogICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICB8CiAgICAg
ICAgICAgICAgICAgICAgfDo6Ojo6OjpQQ0VQOjo6Ojo6Ojo6OnwKICAgICAgICAgICAgICAgICAg
ICB8ICAgICAgICAgICAgICAgICAgICAgfAoKICAgICAgICAgICAgICAgIEZpZ3VyZSAxOiBCb3Ro
IFBDRVAgU3BlYWtlciBzdXBwb3J0cyBQQ0VQUwoKCgoKCgoKCgoKCkxvcGV6LCBldCBhbC4gICAg
ICAgICAgIEV4cGlyZXMgSmFudWFyeSAyOSwgMjAxOCAgICAgICAgICAgICAgICBbUGFnZSA3XQoM
CkludGVybmV0LURyYWZ0ICAgICAgICAgIFNlY3VyZSBUcmFuc3BvcnQgZm9yIFBDRVAgICAgICAg
ICAgICAgIEp1bHkgMjAxNwoKCiAgICAgICAgICAgICAgICAgICstKy0rICAgICAgICAgICAgICAg
ICArLSstKwogICAgICAgICAgICAgICAgICB8UENDfCAgICAgICAgICAgICAgICAgfFBDRXwKICAg
ICAgICAgICAgICAgICAgKy0rLSsgICAgICAgICAgICAgICAgICstKy0rCiAgICAgICAgICAgICAg
ICAgICAgfCAgICAgICAgICAgICAgICAgICAgIHwgRG9lcyBub3Qgc2VuZAogICAgICAgICAgICAg
ICAgICAgIHwgICAgICBTdGFydFRMUyAgICAgICB8IFN0YXJ0VExTIGFzCiAgICAgICAgICAgICAg
ICAgICAgfC0tLS0tLS0tLS0tLS0tLS0tLS0tPnwgY2Fubm90IGVzdGFibGlzaAogICAgICAgICAg
ICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICB8IFRMUwogICAgICAgICAgICAgICAgICAg
IHwgICAgICAgICAgICAgICAgICAgICB8CiAgICAgICAgICAgICAgICAgICAgfDwtLS0tLS0tLS0t
LS0tLS0tLS0tLXwgU2VuZCBFcnJvcgogICAgICAgICAgICAgICAgICAgIHwgICAgICBQQ0VyciAg
ICAgICAgICB8IEVycm9yLVZhbHVlIDMvNAogICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAg
ICAgICAgICAgICB8CgoKICAgRmlndXJlIDI6IEJvdGggUENFUCBTcGVha2VyIHN1cHBvcnRzIFBD
RVBTLCBCdXQgY2Fubm90IGVzdGFibGlzaCBUTFMKCgogICAgICAgICAgICAgICAgICArLSstKyAg
ICAgICAgICAgICAgICAgKy0rLSsKICAgICAgICAgICAgICAgICAgfFBDQ3wgICAgICAgICAgICAg
ICAgIHxQQ0V8CiAgICAgICAgICAgICAgICAgICstKy0rICAgICAgICAgICAgICAgICArLSstKwog
ICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICB8ICBEb2VzIG5vdCBzdXBw
b3J0CiAgICAgICAgICAgICAgICAgICAgfCBTdGFydFRMUyAgICAgICAgICAgIHwgIFBDRVBTIGFu
ZCB0aHVzCiAgICAgICAgICAgICAgICAgICAgfCBtc2cgICAgICAgICAgICAgICAgIHwgIHNlbmRz
IE9wZW4KICAgICAgICAgICAgICAgICAgICB8LS0tLS0tLSAgICAgICAgICAgICAgfAogICAgICAg
ICAgICAgICAgICAgIHwgICAgICAgXCAgIE9wZW4gICAgICB8CiAgICAgICAgICAgICAgICAgICAg
fCAgICAgICAgXCAgbXNnICAgICAgIHwKICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAgXCAg
LS0tLS0tLS0tfAogICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgXC8gICAgICAgICB8CiAg
ICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAvXCAgICAgICAgIHwKICAgICAgICAgICAgICAg
ICAgICB8ICAgICAgICAgLyAgLS0tLS0tLS0+fAogICAgICAgICAgICAgICAgICAgIHwgICAgICAg
IC8gICAgICAgICAgICB8CiAgICAgICAgICAgICAgICAgICAgfDwtLS0tLS0gICAgICAgICAgICAg
IHwKICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgfAogICAgICAgICAg
ICAgICAgICAgIHw8LS0tLS0tLS0tLS0tLS0tLS0tLS18IFNlbmQgRXJyb3IKICAgICAgICAgICAg
ICAgICAgICB8ICAgICAgIFBDRXJyICAgICAgICAgfCAobm9uLU9wZW4gbWVzc2FnZQogICAgICAg
ICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICB8ICByZWNlaXZlZCkKCgoKICAgICAg
ICAgICAgIEZpZ3VyZSAzOiBPbmUgUENFUCBTcGVha2VyIGRvZXMgbm90IHN1cHBvcnQgUENFUFMK
CjMuNC4gIFRMUyBDb25uZWN0aW9uIEVzdGFibGlzaG1lbnQKCiAgIE9uY2UgdGhlIGVzdGFibGlz
aG1lbnQgb2YgVExTIGhhcyBiZWVuIGFncmVlZCBieSB0aGUgUENFUCBwZWVycywgdGhlCiAgIGNv
bm5lY3Rpb24gZXN0YWJsaXNobWVudCBTSEFMTCBmb2xsb3cgdGhlIGZvbGxvd2luZyBzdGVwczoK
CiAgIDEuICBJbW1lZGlhdGVseSBuZWdvdGlhdGUgYSBUTFMgc2Vzc2lvbiBhY2NvcmRpbmcgdG8g
W1JGQzUyNDZdLiAgVGhlCiAgICAgICBmb2xsb3dpbmcgcmVzdHJpY3Rpb25zIGFwcGx5OgoKCgoK
TG9wZXosIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBKYW51YXJ5IDI5LCAyMDE4ICAgICAgICAg
ICAgICAgIFtQYWdlIDhdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgU2VjdXJlIFRyYW5zcG9y
dCBmb3IgUENFUCAgICAgICAgICAgICAgSnVseSAyMDE3CgoKICAgICAgICogIFN1cHBvcnQgZm9y
IFRMUyB2MS4yIFtSRkM1MjQ2XSBvciBsYXRlciBpcyBSRVFVSVJFRC4KCiAgICAgICAqICBTdXBw
b3J0IGZvciBjZXJ0aWZpY2F0ZS1iYXNlZCBtdXR1YWwgYXV0aGVudGljYXRpb24gaXMKICAgICAg
ICAgIFJFUVVJUkVELgoKICAgICAgICogIE5lZ290aWF0aW9uIG9mIG11dHVhbCBhdXRoZW50aWNh
dGlvbiBpcyBSRVFVSVJFRC4KCiAgICAgICAqICBOZWdvdGlhdGlvbiBvZiBhIGNpcGhlcnN1aXRl
IHByb3ZpZGluZyBmb3IgaW50ZWdyaXR5CiAgICAgICAgICBwcm90ZWN0aW9uIGlzIFJFUVVJUkVE
LgoKICAgICAgICogIE5lZ290aWF0aW9uIG9mIGEgY2lwaGVyc3VpdGUgcHJvdmlkaW5nIGZvciBj
b25maWRlbnRpYWxpdHkgaXMKICAgICAgICAgIFJFQ09NTUVOREVELgoKICAgICAgICogIFN1cHBv
cnQgZm9yIGFuZCBuZWdvdGlhdGlvbiBvZiBjb21wcmVzc2lvbiBpcyBPUFRJT05BTC4KCiAgICAg
ICAqICBQQ0VQUyBpbXBsZW1lbnRhdGlvbnMgTVVTVCwgYXQgYSBtaW5pbXVtLCBzdXBwb3J0IG5l
Z290aWF0aW9uCiAgICAgICAgICBvZiB0aGUgVExTX1JTQV9XSVRIX0FFU18xMjhfR0NNX1NIQTI1
NiwgYW5kIFNIT1VMRCBzdXBwb3J0CiAgICAgICAgICBUTFNfUlNBX1dJVEhfQUVTXzI1Nl9HQ01f
U0hBMzg0IGFzIHdlbGwgW1JGQzUyODhdLiAgSW4KICAgICAgICAgIGFkZGl0aW9uLCBQQ0VQUyBp
bXBsZW1lbnRhdGlvbnMgTVVTVCBzdXBwb3J0IG5lZ290aWF0aW9uIG9mCiAgICAgICAgICB0aGUg
bWFuZGF0b3J5LXRvLWltcGxlbWVudCBjaXBoZXJzdWl0ZXMgcmVxdWlyZWQgYnkgdGhlCiAgICAg
ICAgICB2ZXJzaW9ucyBvZiBUTFMgdGhhdCB0aGV5IHN1cHBvcnQuCgogICAyLiAgUGVlciBhdXRo
ZW50aWNhdGlvbiBjYW4gYmUgcGVyZm9ybWVkIGluIGFueSBvZiB0aGUgZm9sbG93aW5nIHR3bwog
ICAgICAgUkVRVUlSRUQgb3BlcmF0aW9uIG1vZGVsczoKCiAgICAgICAqICBUTFMgd2l0aCBYLjUw
OSBjZXJ0aWZpY2F0ZXMgdXNpbmcgUHVibGljLUtleSBJbmZyYXN0cnVjdHVyZQogICAgICAgICAg
RXhjaGFuZ2UgKFBLSVgpIHRydXN0IG1vZGVsczoKCiAgICAgICAgICArICBJbXBsZW1lbnRhdGlv
bnMgTVVTVCBhbGxvdyB0aGUgY29uZmlndXJhdGlvbiBvZiBhIGxpc3Qgb2YKICAgICAgICAgICAg
IHRydXN0ZWQgQ2VydGlmaWNhdGlvbiBBdXRob3JpdGllcyAoQ0FzKSBmb3IgaW5jb21pbmcKICAg
ICAgICAgICAgIGNvbm5lY3Rpb25zLgoKICAgICAgICAgICsgIENlcnRpZmljYXRlIHZhbGlkYXRp
b24gTVVTVCBpbmNsdWRlIHRoZSB2ZXJpZmljYXRpb24gcnVsZXMKICAgICAgICAgICAgIGFzIHBl
ciBbUkZDNTI4MF0uCgogICAgICAgICAgKyAgUENFUFMgaW1wbGVtZW50YXRpb25zIFNIT1VMRCBp
bmNvcnBvcmF0ZSByZXZvY2F0aW9uIG1ldGhvZHMKICAgICAgICAgICAgIChDUkwgZG93bmxvYWRp
bmcsIE9DU1AuLi4pIGFjY29yZGluZyB0byB0aGUgdHJ1c3RlZCBDQQogICAgICAgICAgICAgcG9s
aWNpZXMuCgogICAgICAgICAgKyAgSW1wbGVtZW50YXRpb25zIFNIT1VMRCBpbmRpY2F0ZSB0aGVp
ciB0cnVzdGVkIENBcy4gIEZvciBUTFMKICAgICAgICAgICAgIDEuMiwgdGhpcyBpcyBkb25lIHVz
aW5nIFtSRkM1MjQ2XSwgU2VjdGlvbiA3LjQuNCwKICAgICAgICAgICAgICJjZXJ0aWZpY2F0ZV9h
dXRob3JpdGllcyIgKHNlcnZlciBzaWRlKSBhbmQgW1JGQzYwNjZdLAogICAgICAgICAgICAgU2Vj
dGlvbiA2ICJUcnVzdGVkIENBIEluZGljYXRpb24iIChjbGllbnQgc2lkZSkuCgogICAgICAgICAg
KyAgUGVlciB2YWxpZGF0aW9uIGFsd2F5cyBTSE9VTEQgaW5jbHVkZSBhIGNoZWNrIG9uIHdoZXRo
ZXIKICAgICAgICAgICAgIHRoZSBsb2NhbGx5IGNvbmZpZ3VyZWQgZXhwZWN0ZWQgRE5TIG5hbWUg
b3IgSVAgYWRkcmVzcyBvZgogICAgICAgICAgICAgdGhlIHBlZXIgdGhhdCBpcyBjb250YWN0ZWQg
bWF0Y2hlcyBpdHMgcHJlc2VudGVkCiAgICAgICAgICAgICBjZXJ0aWZpY2F0ZS4gIEROUyBuYW1l
cyBhbmQgSVAgYWRkcmVzc2VzIGNhbiBiZSBjb250YWluZWQKCgoKTG9wZXosIGV0IGFsLiAgICAg
ICAgICAgRXhwaXJlcyBKYW51YXJ5IDI5LCAyMDE4ICAgICAgICAgICAgICAgIFtQYWdlIDldCgwK
SW50ZXJuZXQtRHJhZnQgICAgICAgICAgU2VjdXJlIFRyYW5zcG9ydCBmb3IgUENFUCAgICAgICAg
ICAgICAgSnVseSAyMDE3CgoKICAgICAgICAgICAgIGluIHRoZSBDb21tb24gTmFtZSAoQ04pIG9y
IHN1YmplY3RBbHROYW1lIGVudHJpZXMuICBGb3IKICAgICAgICAgICAgIHZlcmlmaWNhdGlvbiwg
b25seSBvbmUgb2YgdGhlc2UgZW50cmllcyBpcyB0byBiZQogICAgICAgICAgICAgY29uc2lkZXJl
ZC4gIFRoZSBmb2xsb3dpbmcgcHJlY2VkZW5jZSBhcHBsaWVzOiBmb3IgRE5TIG5hbWUKICAgICAg
ICAgICAgIHZhbGlkYXRpb24sIHN1YmplY3RBbHROYW1lOkROUyBoYXMgcHJlY2VkZW5jZSBvdmVy
IENOOyBmb3IKICAgICAgICAgICAgIElQIGFkZHJlc3MgdmFsaWRhdGlvbiwgc3ViamVjdEFsdE5h
bWU6aVBBZGRyIGhhcyBwcmVjZWRlbmNlCiAgICAgICAgICAgICBvdmVyIENOLgoKICAgICAgICAg
ICsgIEltcGxlbWVudGF0aW9ucyBNQVkgYWxsb3cgdGhlIGNvbmZpZ3VyYXRpb24gb2YgYSBzZXQg
b2YKICAgICAgICAgICAgIGFkZGl0aW9uYWwgcHJvcGVydGllcyBvZiB0aGUgY2VydGlmaWNhdGUg
dG8gY2hlY2sgZm9yIGEKICAgICAgICAgICAgIHBlZXIncyBhdXRob3JpemF0aW9uIHRvIGNvbW11
bmljYXRlIChlLmcuLCBhIHNldCBvZiBhbGxvd2VkCiAgICAgICAgICAgICB2YWx1ZXMgaW4gc3Vi
amVjdEFsdE5hbWU6VVJJIG9yIGEgc2V0IG9mIGFsbG93ZWQgWDUwOXYzCiAgICAgICAgICAgICBD
ZXJ0aWZpY2F0ZSBQb2xpY2llcykKCiAgICAgICAqICBUTFMgd2l0aCBYLjUwOSBjZXJ0aWZpY2F0
ZXMgdXNpbmcgY2VydGlmaWNhdGUgZmluZ2VycHJpbnRzOgogICAgICAgICAgSW1wbGVtZW50YXRp
b25zIE1VU1QgYWxsb3cgdGhlIGNvbmZpZ3VyYXRpb24gb2YgYSBsaXN0IG9mCiAgICAgICAgICB0
cnVzdGVkIGNlcnRpZmljYXRlcywgaWRlbnRpZmllZCB2aWEgZmluZ2VycHJpbnQgb2YgdGhlCiAg
ICAgICAgICBEaXN0aW5ndWlzaGVkIEVuY29kaW5nIFJ1bGVzIChERVIpIGVuY29kZWQgY2VydGlm
aWNhdGUgb2N0ZXRzLgogICAgICAgICAgSW1wbGVtZW50YXRpb25zIE1VU1Qgc3VwcG9ydCBTSEEt
MjU2IGFzIGRlZmluZWQgYnkgW1NIU10gYXMKICAgICAgICAgIHRoZSBoYXNoIGFsZ29yaXRobSBm
b3IgdGhlIGZpbmdlcnByaW50LgoKICAgMy4gIFN0YXJ0IGV4Y2hhbmdpbmcgUENFUCBtZXNzYWdl
cy4KCiAgIFRvIHN1cHBvcnQgVExTIHJlLW5lZ290aWF0aW9uIGJvdGggcGVlcnMgTVVTVCBzdXBw
b3J0IHRoZSBtZWNoYW5pc20KICAgZGVzY3JpYmVkIGluIFtSRkM1NzQ2XS4gIEFueSBhdHRlbXB0
IHRvIGluaXRpYXRlIGEgVExTIGhhbmRzaGFrZSB0bwogICBlc3RhYmxpc2ggbmV3IGNyeXB0b2dy
YXBoaWMgcGFyYW1ldGVycyBub3QgYWxpZ25lZCB3aXRoIFtSRkM1NzQ2XQogICBTSEFMTCBiZSBj
b25zaWRlcmVkIGEgVExTIG5lZ290aWF0aW9uIGZhaWx1cmUuCgozLjUuICBQZWVyIElkZW50aXR5
CgogICBEZXBlbmRpbmcgb24gdGhlIHBlZXIgYXV0aGVudGljYXRpb24gbWV0aG9kIGluIHVzZSwg
UENFUFMgc3VwcG9ydHMKICAgZGlmZmVyZW50IG9wZXJhdGlvbiBtb2RlcyB0byBlc3RhYmxpc2gg
cGVlcidzIGlkZW50aXR5IGFuZCB3aGV0aGVyIGl0CiAgIGlzIGVudGl0bGVkIHRvIHBlcmZvcm0g
cmVxdWVzdHMgb3IgY2FuIGJlIGNvbnNpZGVyZWQgYXV0aG9yaXRhdGl2ZSBpbgogICBpdHMgcmVw
bGllcy4gIFBDRVBTIGltcGxlbWVudGF0aW9ucyBTSE9VTEQgcHJvdmlkZSBtZWNoYW5pc21zIGZv
cgogICBhc3NvY2lhdGluZyBwZWVyIGlkZW50aXRpZXMgd2l0aCBkaWZmZXJlbnQgbGV2ZWxzIG9m
IGFjY2VzcyBhbmQvb3IKICAgYXV0aG9yaXRhdGl2ZW5lc3MsIGFuZCB0aGV5IE1VU1QgcHJvdmlk
ZSBhIG1lY2hhbmlzbSBmb3IgZXN0YWJsaXNoaW5nCiAgIGEgZGVmYXVsdCBsZXZlbCBmb3IgcHJv
cGVybHkgaWRlbnRpZmllZCBwZWVycy4gIEFueSBjb25uZWN0aW9uCiAgIGVzdGFibGlzaGVkIHdp
dGggYSBwZWVyIHRoYXQgY2Fubm90IGJlIHByb3Blcmx5IGlkZW50aWZpZWQgU0hBTEwgYmUKICAg
dGVybWluYXRlZCBiZWZvcmUgYW55IFBDRVAgZXhjaGFuZ2UgdGFrZXMgcGxhY2UuCgogICBJbiBU
TFMtWC41MDkgbW9kZSB1c2luZyBmaW5nZXJwcmludHMsIGEgcGVlciBpcyB1bmlxdWVseSBpZGVu
dGlmaWVkCiAgIGJ5IHRoZSBmaW5nZXJwcmludCBvZiB0aGUgcHJlc2VudGVkIGNlcnRpZmljYXRl
LgoKICAgVGhlcmUgYXJlIG51bWVyb3VzIHRydXN0IG1vZGVscyBpbiBQS0lYIGVudmlyb25tZW50
cywgYW5kIGl0IGlzCiAgIGJleW9uZCB0aGUgc2NvcGUgb2YgdGhpcyBkb2N1bWVudCB0byBkZWZp
bmUgaG93IGEgcGFydGljdWxhcgogICBkZXBsb3ltZW50IGRldGVybWluZXMgd2hldGhlciBhIHBl
ZXIgaXMgdHJ1c3R3b3J0aHkuICBJbXBsZW1lbnRhdGlvbnMKICAgdGhhdCB3YW50IHRvIHN1cHBv
cnQgYSB3aWRlIHZhcmlldHkgb2YgdHJ1c3QgbW9kZWxzIFNIT1VMRCBleHBvc2UgYXMKICAgbWFu
eSBkZXRhaWxzIG9mIHRoZSBwcmVzZW50ZWQgY2VydGlmaWNhdGUgdG8gdGhlIGFkbWluaXN0cmF0
b3IgYXMKICAgcG9zc2libGUgc28gdGhhdCB0aGUgdHJ1c3QgbW9kZWwgY2FuIGJlIGltcGxlbWVu
dGVkIGJ5IHRoZQoKCgpMb3BleiwgZXQgYWwuICAgICAgICAgICBFeHBpcmVzIEphbnVhcnkgMjks
IDIwMTggICAgICAgICAgICAgICBbUGFnZSAxMF0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICBT
ZWN1cmUgVHJhbnNwb3J0IGZvciBQQ0VQICAgICAgICAgICAgICBKdWx5IDIwMTcKCgogICBhZG1p
bmlzdHJhdG9yLiAgQXQgbGVhc3QgdGhlIGZvbGxvd2luZyBwYXJhbWV0ZXJzIG9mIHRoZSBYLjUw
OQogICBjZXJ0aWZpY2F0ZSBTSE9VTEQgYmUgZXhwb3NlZDoKCiAgIG8gIFBlZXIncyBJUCBhZGRy
ZXNzCgogICBvICBQZWVyJ3MgZnVsbHkgcXVhbGlmaWVkIGRvbWFpbiBuYW1lIChGUUROKQoKICAg
byAgQ2VydGlmaWNhdGUgRmluZ2VycHJpbnQKCiAgIG8gIElzc3VlcgoKICAgbyAgU3ViamVjdAoK
ICAgbyAgQWxsIFg1MDl2MyBFeHRlbmRlZCBLZXkgVXNhZ2UKCiAgIG8gIEFsbCBYNTA5djMgU3Vi
amVjdCBBbHRlcm5hdGl2ZSBOYW1lCgogICBvICBBbGwgWDUwOXYzIENlcnRpZmljYXRlIFBvbGlj
aWVzCgogICBOb3RlIHRoYXQgdGhlIHJlbW90ZSBJUCBhZGRyZXNzIHVzZWQgZm9yIHRoZSBUQ1Ag
c2Vzc2lvbgogICBlc3RhYmxpc2htZW50IGlzIGFsc28gZXhwb3NlZC4KCiAgIFtJLUQuaWV0Zi1w
Y2Utc3RhdGVmdWwtc3luYy1vcHRpbWl6YXRpb25zXSBzcGVjaWZ5IGEgU3BlYWtlciBFbnRpdHkK
ICAgSWRlbnRpZmllciBUTFYgKFNQRUFLRVItRU5USVRZLUlEKSwgYXMgYW4gb3B0aW9uYWwgVExW
IHRoYXQgTUFZIGJlCiAgIGluY2x1ZGVkIGluIHRoZSBPUEVOIE9iamVjdC4gIEl0IGNvbnRhaW5z
IGEgdW5pcXVlIGlkZW50aWZpZXIgZm9yIHRoZQogICBub2RlIHRoYXQgZG9lcyBub3QgY2hhbmdl
IGR1cmluZyB0aGUgbGlmZXRpbWUgb2YgdGhlIFBDRVAgc3BlYWtlci4KICAgQW4gaW1wbGVtZW50
YXRpb24gd291bGQgdGh1cyBleHBvc2UgdGhlIHNwZWFrZXIgZW50aXR5IGlkZW50aWZpZXIgYXMK
ICAgcGFydCBvZiB0aGUgWDUwOXYzIGNlcnRpZmljYXRlLCBzbyB0aGF0IGFuIGltcGxlbWVudGF0
aW9uIGNvdWxkIHVzZQogICB0aGlzIGlkZW50aWZpZXIgZm9yIHRoZSBwZWVyIGlkZW50aWZpY2F0
aW9uIHRydXN0IG1vZGVsLgoKICAgSW4gYWRkaXRpb24sIGEgUENDIE1BWSBhcHBseSB0aGUgcHJv
Y2VkdXJlcyBkZXNjcmliZWQgaW4gW1JGQzY2OThdCiAgIEROUy1CYXNlZCBBdXRoZW50aWNhdGlv
biBvZiBOYW1lZCBFbnRpdGllcyAoREFORSkgdG8gdmVyaWZ5IGl0cyBwZWVyCiAgIGlkZW50aXR5
IHdoZW4gdXNpbmcgRE5TIGRpc2NvdmVyeS4gIFNlZSBzZWN0aW9uIFNlY3Rpb24gNC4xIGZvcgog
ICBmdXJ0aGVyIGRldGFpbHMuCgozLjYuICBDb25uZWN0aW9uIEVzdGFibGlzaG1lbnQgRmFpbHVy
ZQoKICAgSW4gY2FzZSB0aGUgaW5pdGlhbCBUTFMgbmVnb3RpYXRpb24gb3IgdGhlIHBlZXIgaWRl
bnRpdHkgY2hlY2sgZmFpbHMsCiAgIGFjY29yZGluZyB0byB0aGUgcHJvY2VkdXJlcyBsaXN0ZWQg
aW4gdGhpcyBkb2N1bWVudCwgdGhlIHBlZXIgTVVTVAogICBmaXJzdCBzZW5kIGEgUENFcnIgbWVz
c2FnZSBhcyBwZXIgU2VjdGlvbiAzLjIgYW5kIHRoZW4gdGVybWluYXRlIHRoZQogICBzZXNzaW9u
LiAgSXQgU0hPVUxEIGZvbGxvdyB0aGUgcHJvY2VkdXJlIGxpc3RlZCBpbiBbUkZDNTQ0MF0gdG8g
cmV0cnkKICAgc2Vzc2lvbiBzZXR1cCBhbG9uZyB3aXRoIGFuIGV4cG9uZW50aWFsIGJhY2stb2Zm
IHNlc3Npb24KICAgZXN0YWJsaXNobWVudCByZXRyeSBwcm9jZWR1cmUuCgoKCgoKCgoKTG9wZXos
IGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBKYW51YXJ5IDI5LCAyMDE4ICAgICAgICAgICAgICAg
W1BhZ2UgMTFdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgU2VjdXJlIFRyYW5zcG9ydCBmb3Ig
UENFUCAgICAgICAgICAgICAgSnVseSAyMDE3CgoKNC4gIERpc2NvdmVyeSBNZWNoYW5pc21zCgog
ICBUaGlzIGRvY3VtZW50IGRvZXMgbm90IHNwZWNpZnkgYW55IGRpc2NvdmVyeSBtZWNoYW5pc20g
Zm9yIHN1cHBvcnQgb2YKICAgUENFUFMuICBPdGhlciBkb2N1bWVudHMsIFtJLUQud3UtcGNlLWRp
c2NvdmVyeS1wY2Vwcy1zdXBwb3J0XSBhbmQKICAgW0ktRC53dS1wY2UtZG5zLXBjZS1kaXNjb3Zl
cnldIGhhdmUgbWFkZSBwcm9wb3NhbHM6CgogICBvICBBIFBDRSBjYW4gYWR2ZXJ0aXNlIGl0cyBj
YXBhYmlsaXR5IHRvIHN1cHBvcnQgUENFUFMgdXNpbmcgdGhlCiAgICAgIElHUCdzIGFkdmVydGlz
ZW1lbnQgbWVjaGFuaXNtIG9mIHRoZSBQQ0UgZGlzY292ZXJ5IGluZm9ybWF0aW9uLgogICAgICBU
aGUgUENFLUNBUC1GTEFHUyBzdWItVExWIGlzIGFuIG9wdGlvbmFsIHN1Yi1UTFYgdXNlZCB0byBh
ZHZlcnRpc2UKICAgICAgUENFIGNhcGFiaWxpdGllcy4gIEl0IGlzIHByZXNlbnQgd2l0aGluIHRo
ZSBQQ0UgRGlzY292ZXJ5IChQQ0VEKQogICAgICBzdWItVExWIGNhcnJpZWQgYnkgT1NQRiBvciBJ
Uy1JUy4gIFtSRkM1MDg4XSBhbmQgW1JGQzUwODldIHByb3ZpZGUKICAgICAgdGhlIGRlc2NyaXB0
aW9uIGFuZCBwcm9jZXNzaW5nIHJ1bGVzIGZvciB0aGlzIHN1Yi1UTFYgd2hlbiBjYXJyaWVkCiAg
ICAgIHdpdGhpbiBPU1BGIGFuZCBJUy1JUywgcmVzcGVjdGl2ZWx5LiAgUENFIGNhcGFiaWxpdHkg
Yml0cyBhcmUKICAgICAgZGVmaW5lZCBpbiBbUkZDNTA4OF0uICBBIG5ldyBjYXBhYmlsaXR5IGZs
YWcgYml0IGZvciB0aGUgUENFLUNBUC0KICAgICAgRkxBR1Mgc3ViLVRMViB0aGF0IGNhbiBiZSBh
bm5vdW5jZWQgYXMgYW4gYXR0cmlidXRlIHRvIGRpc3RyaWJ1dGUKICAgICAgUENFUCBzZWN1cml0
eSBzdXBwb3J0IGluZm9ybWF0aW9uIGlzIHByb3Bvc2VkIGluCiAgICAgIFtJLUQud3UtcGNlLWRp
c2NvdmVyeS1wY2Vwcy1zdXBwb3J0XS4KCiAgIG8gIEEgUENFIGNhbiBhZHZlcnRpc2UgaXRzIGNh
cGFiaWxpdHkgdG8gc3VwcG9ydCBQQ0VQUyB1c2luZyB0aGUgRE5TCiAgICAgIFtJLUQud3UtcGNl
LWRucy1wY2UtZGlzY292ZXJ5XSBieSBpZGVudGlmeWluZyB0aGUgc3VwcG9ydCBvZiBUTFMuCgo0
LjEuICBEQU5FIEFwcGxpY2FiaWxpdHkKCiAgIERBTkUgW1JGQzY2OThdIGRlZmluZXMgYSBzZWN1
cmUgbWV0aG9kIHRvIGFzc29jaWF0ZSB0aGUgY2VydGlmaWNhdGUKICAgdGhhdCBpcyBvYnRhaW5l
ZCBmcm9tIGEgVExTIHNlcnZlciB3aXRoIGEgZG9tYWluIG5hbWUgdXNpbmcgRE5TLAogICBpLmUu
LCB1c2luZyB0aGUgVExTQSBETlMgcmVzb3VyY2UgcmVjb3JkIChSUikgdG8gYXNzb2NpYXRlIGEg
VExTCiAgIHNlcnZlciBjZXJ0aWZpY2F0ZSBvciBwdWJsaWMga2V5IHdpdGggdGhlIGRvbWFpbiBu
YW1lIHdoZXJlIHRoZQogICByZWNvcmQgaXMgZm91bmQsIHRodXMgZm9ybWluZyBhICJUTFNBIGNl
cnRpZmljYXRlIGFzc29jaWF0aW9uIi4gIFRoZQogICBETlMgaW5mb3JtYXRpb24gbmVlZHMgdG8g
YmUgcHJvdGVjdGVkIGJ5IEROUyBTZWN1cml0eSAoRE5TU0VDKS4gIEEKICAgUENDIHdpbGxpbmcg
dG8gYXBwbHkgREFORSB0byB2ZXJpZnkgc2VydmVyIGlkZW50aXR5IE1VU1QgY29uZm9ybSB0bwog
ICB0aGUgcnVsZXMgZGVmaW5lZCBpbiBzZWN0aW9uIDQgb2YgW1JGQzY2OThdLiAgVGhlIHNlcnZl
cidzIGRvbWFpbgogICBuYW1lIG11c3QgYmUgYXV0aG9yaXplZCBzZXBhcmF0ZWx5LCBhcyBUTFNB
IGRvZXMgbm90IHByb3ZpZGUgYW55CiAgIHVzZWZ1bCBhdXRob3JpemF0aW9uIGd1YXJhbnRlZXMu
Cgo1LiAgQmFja3dhcmQgQ29tcGF0aWJpbGl0eQoKICAgVGhlIHByb2NlZHVyZXMgZGVzY3JpYmVk
IGluIHRoaXMgZG9jdW1lbnQgZGVmaW5lIGEgc2VjdXJpdHkgY29udGFpbmVyCiAgIGZvciB0aGUg
dHJhbnNwb3J0IG9mIFBDRVAgcmVxdWVzdHMgYW5kIHJlcGxpZXMgY2FycmllZCBieSBhIFRMUwog
ICBjb25uZWN0aW9uIGluaXRpYXRlZCBieSBtZWFucyBvZiBhIHNwZWNpZmljIGV4dGVuZGVkIG1l
c3NhZ2UKICAgKFN0YXJ0VExTKSB0aGF0IGRvZXMgbm90IGludGVyZmVyZSB3aXRoIFBDRVAgc3Bl
YWtlciBpbXBsZW1lbnRhdGlvbnMKICAgbm90IHN1cHBvcnRpbmcgaXQuCgogICBJZiBhIFBDRVAg
aW1wbGVtZW50YXRpb24gdGhhdCBkb2VzIG5vdCBzdXBwb3J0IFBDRVBTIHJlY2VpdmVzIGEKICAg
U3RhcnRUTFMgbWVzc2FnZSwgaXQgd291bGQgYmVoYXZlIGFjY29yZGluZyB0byB0aGUgZXhpc3Rp
bmcgZXJyb3IKICAgbWVjaGFuaXNtIG9mIFtSRkM1NDQwXS4gIE9uIHJlY2VpdmluZyB0aGUgZXJy
b3IsIGJhc2VkIG9uIHRoZSBsb2NhbAogICBwb2xpY3ksIGEgcGVlciBjb3VsZCB0cnkgdG8gZXN0
YWJsaXNoaW5nIFBDRVAgc2Vzc2lvbiB3aXRob3V0IFRMUyBhcwogICBwZXIgdGhlIHByb2NlZHVy
ZXMgZGVmaW5lZCBpbiBbUkZDNTQ0MF0uICBGb3Igc3VjY2Vzc2Z1bCBUTFMKCgoKCkxvcGV6LCBl
dCBhbC4gICAgICAgICAgIEV4cGlyZXMgSmFudWFyeSAyOSwgMjAxOCAgICAgICAgICAgICAgIFtQ
YWdlIDEyXQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgIFNlY3VyZSBUcmFuc3BvcnQgZm9yIFBD
RVAgICAgICAgICAgICAgIEp1bHkgMjAxNwoKCiAgIG9wZXJhdGlvbnMgd2l0aCBQQ0VQLCBib3Ro
IFBDRVAgcGVlcnMgaW4gdGhlIG5ldHdvcmsgd291bGQgbmVlZCB0byBiZQogICB1cGdyYWRlZCB0
byBzdXBwb3J0IHRoaXMgZG9jdW1lbnQuCgogICBBbiBleGlzdGluZyBQQ0VQIHNlc3Npb24gY2Fu
bm90IGJlIHVwZ3JhZGVkIHRvIFBDRVBTLCB0aGUgc2Vzc2lvbgogICBuZWVkcyB0byBiZSB0ZXJt
aW5hdGVkIGFuZCByZWVzdGFibGlzaGVkIGFzIHBlciB0aGUgcHJvY2VkdXJlCiAgIGRlc2NyaWJl
ZCBpbiB0aGlzIGRvY3VtZW50LiAgRHVyaW5nIHRoZSBpbmNyZW1lbnRhbCB1cGdyYWRlLCB0aGUg
UENFUAogICBzcGVha2VyIFNIT1VMRCBhbGxvdyBzZXNzaW9uIGVzdGFibGlzaG1lbnQgd2l0aCBh
bmQgd2l0aG91dCBUTFMuCiAgIE9uY2UgYm90aCBQQ0VQIHNwZWFrZXJzIGFyZSB1cGdyYWRlZCB0
byBzdXBwb3J0IFBDRVBTLCB0aGUgUENFUAogICBzZXNzaW9uIGlzIHJlLWVzdGFibGlzaGVkIHdp
dGggVExTLCBvdGhlcndpc2UgUENFUCBzZXNzaW9uIHdpdGhvdXQKICAgVExTIGlzIHNldHVwLiAg
QSByZWR1bmRhbnQgUENFIE1BWSBhbHNvIGJlIHVzZWQgZHVyaW5nIHRoZQogICBpbmNyZW1lbnRh
bCBkZXBsb3ltZW50IHRvIHRha2Ugb3ZlciB0aGUgUENFIHVuZGVyZ29pbmcgdXBncmFkZS4gIE9u
Y2UKICAgdGhlIHVwZ3JhZGUgaXMgY29tcGxldGVkLCBzdXBwb3J0IGZvciB1bnNlY3VyZWQgdmVy
c2lvbiBTSE9VTEQgYmUKICAgcmVtb3ZlZC4KCjYuICBJQU5BIENvbnNpZGVyYXRpb25zCgo2LjEu
ICBOZXcgUENFUCBNZXNzYWdlCgogICBJQU5BIGlzIHJlcXVlc3RlZCB0byBhbGxvY2F0ZSBuZXcg
bWVzc2FnZSB0eXBlcyB3aXRoaW4gdGhlICJQQ0VQCiAgIE1lc3NhZ2VzIiBzdWItcmVnaXN0cnkg
b2YgdGhlIFBDRVAgTnVtYmVycyByZWdpc3RyeSwgYXMgZm9sbG93czoKCiAgICAgIFZhbHVlICBE
ZXNjcmlwdGlvbiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgUmVmZXJlbmNlCiAgICAgICBU
QkExICBUaGUgU3RhcnQgVExTIE1lc3NhZ2UgKFN0YXJ0VExTKSAgICAgICAgVGhpcyBkb2N1bWVu
dAoKNi4yLiAgTmV3IEVycm9yLVZhbHVlcwoKICAgSUFOQSBpcyByZXF1ZXN0ZWQgdG8gYWxsb2Nh
dGUgbmV3IEVycm9yIFR5cGVzIGFuZCBFcnJvciBWYWx1ZXMgd2l0aGluCiAgIHRoZSAiIFBDRVAt
RVJST1IgT2JqZWN0IEVycm9yIFR5cGVzIGFuZCBWYWx1ZXMiIHN1Yi1yZWdpc3RyeSBvZiB0aGUK
ICAgUENFUCBOdW1iZXJzIHJlZ2lzdHJ5LCBhcyBmb2xsb3dzOgoKCgoKCgoKCgoKCgoKCgoKCgoK
CgoKTG9wZXosIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBKYW51YXJ5IDI5LCAyMDE4ICAgICAg
ICAgICAgICAgW1BhZ2UgMTNdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgU2VjdXJlIFRyYW5z
cG9ydCBmb3IgUENFUCAgICAgICAgICAgICAgSnVseSAyMDE3CgoKICAgRXJyb3ItCiAgIFR5cGUg
ICAgTWVhbmluZyAgICAgICAgICAgICAgIEVycm9yLXZhbHVlICAgICAgICAgICAgIFJlZmVyZW5j
ZQoKICAgVEJBMiAgICBQQ0VQIFN0YXJ0VExTICAgICAgICAgMDpVbmFzc2lnbmVkICAgICAgICAg
ICAgVGhpcyBkb2N1bWVudAogICAgICAgICAgIGZhaWx1cmUgICAgICAgICAgICAgICAxOlJlY2Vw
dGlvbiBvZiAgICAgICAgICBUaGlzIGRvY3VtZW50CiAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIFN0YXJ0VExTIGFmdGVyCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIGFu
eSBQQ0VQIGV4Y2hhbmdlCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIDI6UmVjZXB0
aW9uIG9mICAgICAgICAgIFRoaXMgZG9jdW1lbnQKICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgYW55IG90aGVyIG1lc3NhZ2UKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
YXBhcnQgZnJvbSBTdGFydFRMUywKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgT3Bl
biBvciBQQ0VycgogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAzOkZhaWx1cmUsIGNv
bm5lY3Rpb24gICBUaGlzIGRvY3VtZW50CiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IHdpdGhvdXQgVExTIG5vdAogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBwb3NzaWJs
ZQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICA0OkZhaWx1cmUsIGNvbm5lY3Rpb24g
ICBUaGlzIGRvY3VtZW50CiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHdpdGhvdXQg
VExTIHBvc3NpYmxlCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIDU6Tm8gU3RhcnRU
TFMgbWVzc2FnZSAgIFRoaXMgZG9jdW1lbnQKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgKG5vciBQQ0Vyci9PcGVuKQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBiZWZv
cmUgU3RhcnRUTFNXYWl0CiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHRpbWVyIGV4
cGlyeQoKNy4gIFNlY3VyaXR5IENvbnNpZGVyYXRpb25zCgogICBXaGlsZSB0aGUgYXBwbGljYXRp
b24gb2YgVExTIHNhdGlzZmllcyB0aGUgcmVxdWlyZW1lbnQgb24gcHJpdmFjeSBhcwogICB3ZWxs
IGFzIGZpbmUtZ3JhaW5lZCwgcG9saWN5LWJhc2VkIHBlZXIgYXV0aGVudGljYXRpb24sIHRoZXJl
IGFyZQogICBzZWN1cml0eSB0aHJlYXRzIHRoYXQgaXQgY2Fubm90IGFkZHJlc3MuICBJdCBtYXkg
YmUgYWR2aXNhYmxlIHRvCiAgIGFwcGx5IGFkZGl0aW9uYWwgcHJvdGVjdGlvbiBtZWFzdXJlcywg
aW4gcGFydGljdWxhciBpbiB3aGF0IHJlbGF0ZXMKICAgdG8gYXR0YWNrcyBzcGVjaWZpY2FsbHkg
YWRkcmVzc2VkIHRvIGZvcmdpbmcgdGhlIFRDUCBjb25uZWN0aW9uCiAgIHVuZGVycGlubmluZyBU
TFMsIGVzcGVjaWFsbHkgaW4gdGhlIGNhc2Ugb2YgbG9uZy1saXZlZCBjb25uZWN0aW9ucy4KICAg
T25lIG9mIHRoZXNlIG1lYXN1cmVzIGlzIHRoZSBhcHBsaWNhdGlvbiBvZiBUQ1AtQU8gKFRDUAog
ICBBdXRoZW50aWNhdGlvbiBPcHRpb24gW1JGQzU5MjVdKSwgd2hpY2ggaXMgZnVsbHkgY29tcGF0
aWJsZSB3aXRoIGFuZAogICBkZWVtZWQgYXMgY29tcGxlbWVudGFyeSB0byBUTFMuICBUaGUgbWVj
aGFuaXNtcyB0byBjb25maWd1cmUgdGhlCiAgIHJlcXVpcmVtZW50cyB0byB1c2UgVENQLUFPIGFu
ZCBvdGhlciBsb3dlci1sYXllciBwcm90ZWN0aW9uIG1lYXN1cmVzCiAgIHdpdGggYSBwYXJ0aWN1
bGFyIHBlZXIgYXJlIG91dHNpZGUgdGhlIHNjb3BlIG9mIHRoaXMgZG9jdW1lbnQuCgogICBTaW5j
ZSBjb21wdXRhdGlvbmFsIHJlc291cmNlcyByZXF1aXJlZCBieSBUTFMgaGFuZHNoYWtlIGFuZAog
ICBjaXBoZXJzdWl0ZSBhcmUgaGlnaGVyIHRoYW4gdW5lbmNyeXB0ZWQgVENQLCBjbGllbnRzIGNv
bm5lY3RpbmcgdG8gYQogICBQQ0VQUyBzZXJ2ZXIgY2FuIG1vcmUgZWFzaWx5IGNyZWF0ZSBoaWdo
IGxvYWQgY29uZGl0aW9ucyBhbmQgYQogICBtYWxpY2lvdXMgY2xpZW50IG1pZ2h0IGNyZWF0ZSBh
IERlbmlhbC1vZi1TZXJ2aWNlIGF0dGFjayBtb3JlIGVhc2lseS4KCiAgIFNvbWUgVExTIGNpcGhl
cnN1aXRlcyBvbmx5IHByb3ZpZGUgaW50ZWdyaXR5IHZhbGlkYXRpb24gb2YgdGhlaXIKICAgcGF5
bG9hZCwgYW5kIHByb3ZpZGUgbm8gZW5jcnlwdGlvbi4gIFRoaXMgc3BlY2lmaWNhdGlvbiBkb2Vz
IG5vdAogICBmb3JiaWQgdGhlIHVzZSBvZiBzdWNoIGNpcGhlcnN1aXRlcywgYnV0IGFkbWluaXN0
cmF0b3JzIG11c3Qgd2VpZ2h0CiAgIGNhcmVmdWxseSB0aGUgcmlzayBvZiByZWxldmFudCBpbnRl
cm5hbCBkYXRhIGxlYWthZ2UgdGhhdCBjYW4gb2NjdXIKICAgaW4gc3VjaCBhIGNhc2UsIGFzIGV4
cGxpY2l0bHkgc3RhdGVkIGJ5IFtSRkM2OTUyXS4KCiAgIFdoZW4gdXNpbmcgY2VydGlmaWNhdGUg
ZmluZ2VycHJpbnRzIHRvIGlkZW50aWZ5IFBDRVBTIHBlZXJzLCBhbnkgdHdvCiAgIGNlcnRpZmlj
YXRlcyB0aGF0IHByb2R1Y2UgdGhlIHNhbWUgaGFzaCB2YWx1ZSB3aWxsIGJlIGNvbnNpZGVyZWQg
dGhlCgoKCkxvcGV6LCBldCBhbC4gICAgICAgICAgIEV4cGlyZXMgSmFudWFyeSAyOSwgMjAxOCAg
ICAgICAgICAgICAgIFtQYWdlIDE0XQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgIFNlY3VyZSBU
cmFuc3BvcnQgZm9yIFBDRVAgICAgICAgICAgICAgIEp1bHkgMjAxNwoKCiAgIHNhbWUgcGVlci4g
IFRoZXJlZm9yZSwgaXQgaXMgaW1wb3J0YW50IHRvIG1ha2Ugc3VyZSB0aGF0IHRoZSBoYXNoCiAg
IGZ1bmN0aW9uIHVzZWQgaXMgY3J5cHRvZ3JhcGhpY2FsbHkgdW5jb21wcm9taXNlZCBzbyB0aGF0
IGF0dGFja2VycwogICBhcmUgdmVyeSB1bmxpa2VseSB0byBiZSBhYmxlIHRvIHByb2R1Y2UgYSBo
YXNoIGNvbGxpc2lvbiB3aXRoIGEKICAgY2VydGlmaWNhdGUgb2YgdGhlaXIgY2hvaWNlLiAgVGhp
cyBkb2N1bWVudCBtYW5kYXRlcyBzdXBwb3J0IGZvcgogICBTSEEtMjU2IGFzIGRlZmluZWQgYnkg
W1NIU10sIGJ1dCBhIGxhdGVyIHJldmlzaW9uIG1heSBkZW1hbmQgc3VwcG9ydAogICBmb3Igc3Ry
b25nZXIgZnVuY3Rpb25zIGlmIHN1aXRhYmxlIGF0dGFja3Mgb24gaXQgYXJlIGtub3duLgoKICAg
VGhlIGd1aWRhbmNlIGdpdmVuIGluIFtSRkM3NTI1XSBTSE9VTEQgYmUgZm9sbG93ZWQgdG8gYXZv
aWQgYXR0YWNrcwogICBvbiBUTFMuCgo4LiAgTWFuYWdlYWJpbGl0eSBDb25zaWRlcmF0aW9ucwoK
ICAgQWxsIG1hbmFnZWFiaWxpdHkgcmVxdWlyZW1lbnRzIGFuZCBjb25zaWRlcmF0aW9ucyBsaXN0
ZWQgaW4gW1JGQzU0NDBdCiAgIGFwcGx5IHRvIFBDRVAgcHJvdG9jb2wgZXh0ZW5zaW9ucyBkZWZp
bmVkIGluIHRoaXMgZG9jdW1lbnQuICBJbgogICBhZGRpdGlvbiwgcmVxdWlyZW1lbnRzIGFuZCBj
b25zaWRlcmF0aW9ucyBsaXN0ZWQgaW4gdGhpcyBzZWN0aW9uCiAgIGFwcGx5LgoKOC4xLiAgQ29u
dHJvbCBvZiBGdW5jdGlvbiBhbmQgUG9saWN5CgogICBBIFBDRSBvciBQQ0MgaW1wbGVtZW50YXRp
b24gTVVTVCBhbGxvdyBjb25maWd1cmluZyB0aGUgUENFUCBzZWN1cml0eQogICB2aWEgVExTIGNh
cGFiaWxpdGllcyBhcyBkZXNjcmliZWQgaW4gdGhpcyBkb2N1bWVudC4KCiAgIEEgUENFIG9yIFBD
QyBpbXBsZW1lbnRhdGlvbiBzdXBwb3J0aW5nIFBDRVAgc2VjdXJpdHkgdmlhIFRMUyBNVVNUCiAg
IHN1cHBvcnQgZ2VuZXJhbCBUTFMgY29uZmlndXJhdGlvbiBhcyBwZXIgW1JGQzUyNDZdLiAgQXQg
bGVhc3QgdGhlCiAgIGNvbmZpZ3VyYXRpb24gb2Ygb25lIG9mIHRoZSB0cnVzdCBtb2RlbHMgYW5k
IGl0cyBjb3JyZXNwb25kaW5nCiAgIHBhcmFtZXRlcnMsIGFzIGRlc2NyaWJlZCBpbiBTZWN0aW9u
IDMuNCBhbmQgU2VjdGlvbiAzLjUsIE1VU1QgYmUKICAgc3VwcG9ydGVkIGJ5IHRoZSBpbXBsZW1l
bnRhdGlvbi4KCiAgIEEgUENFUCBpbXBsZW1lbnRhdGlvbiBTSE9VTEQgYWxsb3cgY29uZmlndXJp
bmcgdGhlIFN0YXJ0VExTV2FpdCB0aW1lcgogICB2YWx1ZS4KCiAgIFBDRVBTIGltcGxlbWVudGF0
aW9ucyBNQVkgcHJvdmlkZSBhbiBvcHRpb24gdG8gYWxsb3cgdGhlIG9wZXJhdG9yIHRvCiAgIG1h
bnVhbGx5IG92ZXJyaWRlIHN0cmljdCBUTFMgY29uZmlndXJhdGlvbiBhbmQgYWxsb3cgdW5zZWN1
cmUKICAgY29ubmVjdGlvbnMuICBFeGVjdXRpb24gb2YgdGhpcyBvdmVycmlkZSBTSE9VTEQgdHJp
Z2dlciBhIHdhcm5pbmcKICAgYWJvdXQgdGhlIHNlY3VyaXR5IGltcGxpY2F0aW9ucyBvZiBwZXJt
aXR0aW5nIHVuc2VjdXJlIGNvbm5lY3Rpb25zLgoKICAgRnVydGhlciwgdGhlIG9wZXJhdG9yIG5l
ZWRzIHRvIGRldmVsb3Agc3VpdGFibGUgc2VjdXJpdHkgcG9saWNpZXMKICAgYXJvdW5kIFBDRVAg
d2l0aGluIGhpcyBuZXR3b3JrLiAgRnVydGhlciB0aGUgUENFUCBwZWVycyBTSE9VTEQKICAgcHJv
dmlkZSB3YXlzIGZvciB0aGUgb3BlcmF0b3IgdG8gY29tcGxldGUgdGhlIGZvbGxvd2luZyB0YXNr
cyBpbgogICByZWdhcmRzIHRvIGEgUENFUCBzZXNzaW9uOgoKICAgbyAgRGV0ZXJtaW5lIGlmIGEg
c2Vzc2lvbiBpcyBwcm90ZWN0ZWQgdmlhIFBDRVBTLgoKICAgbyAgRGV0ZXJtaW5lIHRoZSB2ZXJz
aW9uIG9mIFRMUywgdGhlIG1lY2hhbmlzbSB1c2VkIGZvcgogICAgICBhdXRoZW50aWNhdGlvbiwg
YW5kIHRoZSBjaXBoZXJzdWl0ZSBpbiB1c2UuCgogICBvICBEZXRlcm1pbmUgaWYgdGhlIGNlcnRp
ZmljYXRlIGNvdWxkIG5vdCBiZSB2ZXJpZmllZCwgYW5kIHRoZSByZWFzb24KICAgICAgZm9yIHRo
aXMgY2lyY3Vtc3RhbmNlLgoKCgpMb3BleiwgZXQgYWwuICAgICAgICAgICBFeHBpcmVzIEphbnVh
cnkgMjksIDIwMTggICAgICAgICAgICAgICBbUGFnZSAxNV0KDApJbnRlcm5ldC1EcmFmdCAgICAg
ICAgICBTZWN1cmUgVHJhbnNwb3J0IGZvciBQQ0VQICAgICAgICAgICAgICBKdWx5IDIwMTcKCgog
ICBvICBJbnNwZWN0IHRoZSBjZXJ0aWZpY2F0ZSBvZmZlcmVkIGJ5IHRoZSBQQ0VQIHBlZXIuCgog
ICBvICBCZSB3YXJuZWQgaWYgU3RhcnRUTFMgcHJvY2VkdXJlIGZhaWxzIGZvciB0aGUgUENFUCBw
ZWVycywgdGhhdCBhcmUKICAgICAga25vd24gdG8gc3VwcG9ydCBQQ0VQUywgdmlhIGNvbmZpZ3Vy
YXRpb25zIG9yIGNhcGFiaWxpdHkKICAgICAgYWR2ZXJ0aXNlbWVudHMuCgo4LjIuICBJbmZvcm1h
dGlvbiBhbmQgRGF0YSBNb2RlbHMKCiAgIFRoZSBQQ0VQIE1JQiBtb2R1bGUgaXMgZGVmaW5lZCBp
biBbUkZDNzQyMF0uICBUaGUgTUlCIG1vZHVsZSBjb3VsZCBiZQogICBleHRlbmRlZCB0byBpbmNs
dWRlIHRoZSBhYmlsaXR5IHRvIHZpZXcgdGhlIFBDRVBTIGNhcGFiaWxpdHksIFRMUwogICByZWxh
dGVkIGluZm9ybWF0aW9uIGFzIHdlbGwgYXMgVExTIHN0YXR1cyBmb3IgZWFjaCBQQ0VQIHBlZXIu
CgogICBBbiBpbXBsZW1lbnRhdGlvbiBTSE9VTEQgYWxzbyBhbGxvdyB0aGUgb3BlcmF0b3IgdG8g
Y29uZmlndXJlIHRoZQogICBQQ0VQUyBjYXBhYmlsaXR5IGFuZCB2YXJpb3VzIFRMUyByZWxhdGVk
IHBhcmFtZXRlcnMgaW4gYWRkaXRpb24gdG8KICAgYWJpbGl0eSB0byB2aWV3IHRoZSBjdXJyZW50
IFRMUyBzdGF0dXMgZm9yIGEgUENFUCBzZXNzaW9uLiAgVG8gc2VydmUKICAgdGhpcyBwdXJwb3Nl
LCB0aGUgUENFUCBZQU5HIG1vZHVsZSBbSS1ELmlldGYtcGNlLXBjZXAteWFuZ10gaXMKICAgZXh0
ZW5kZWQgdG8gaW5jbHVkZSBUTFMgcmVsYXRlZCBjb25maWd1cmF0aW9uIGFuZCBzdGF0ZSBpbmZv
cm1hdGlvbi4KCjguMy4gIExpdmVuZXNzIERldGVjdGlvbiBhbmQgTW9uaXRvcmluZwoKICAgTWVj
aGFuaXNtcyBkZWZpbmVkIGluIHRoaXMgZG9jdW1lbnQgZG8gbm90IGltcGx5IGFueSBuZXcgbGl2
ZW5lc3MKICAgZGV0ZWN0aW9uIGFuZCBtb25pdG9yaW5nIHJlcXVpcmVtZW50cyBpbiBhZGRpdGlv
biB0byB0aG9zZSBhbHJlYWR5CiAgIGxpc3RlZCBpbiBbUkZDNTQ0MF0gYW5kIFtSRkM1MjQ2XS4K
CjguNC4gIFZlcmlmeWluZyBDb3JyZWN0IE9wZXJhdGlvbnMKCiAgIEEgUENFUFMgaW1wbGVtZW50
YXRpb24gU0hPVUxEIGxvZyBlcnJvciBldmVudHMgYW5kIHByb3ZpZGUgUENFUFMKICAgZmFpbHVy
ZSBzdGF0aXN0aWNzIHdpdGggcmVhc29ucy4KCjguNS4gIFJlcXVpcmVtZW50cyBvbiBPdGhlciBQ
cm90b2NvbHMKCiAgIE1lY2hhbmlzbXMgZGVmaW5lZCBpbiB0aGlzIGRvY3VtZW50IGRvIG5vdCBp
bXBseSBhbnkgbmV3IHJlcXVpcmVtZW50cwogICBvbiBvdGhlciBwcm90b2NvbHMuICBOb3RlIHRo
YXQsIFNlY3Rpb24gNCBsaXN0IHBvc3NpYmxlIGRpc2NvdmVyeQogICBtZWNoYW5pc20gZm9yIHN1
cHBvcnQgb2YgUENFUFMuCgo4LjYuICBJbXBhY3Qgb24gTmV0d29yayBPcGVyYXRpb24KCiAgIE1l
Y2hhbmlzbXMgZGVmaW5lZCBpbiB0aGlzIGRvY3VtZW50IGRvIG5vdCBoYXZlIGFueSBzaWduaWZp
Y2FudAogICBpbXBhY3Qgb24gbmV0d29yayBvcGVyYXRpb25zIGluIGFkZGl0aW9uIHRvIHRob3Nl
IGFscmVhZHkgbGlzdGVkIGluCiAgIFtSRkM1NDQwXSwgYW5kIHRoZSBwb2xpY3kgYW5kIG1hbmFn
ZW1lbnQgaW1wbGljYXRpb25zIGRpc2N1c3NlZAogICBhYm92ZS4KCjkuICBBY2tub3dsZWRnZW1l
bnRzCgogICBUaGlzIHNwZWNpZmljYXRpb24gcmVsaWVzIG9uIHRoZSBhbmFseXNpcyBhbmQgcHJv
ZmlsaW5nIG9mIFRMUwogICBpbmNsdWRlZCBpbiBbUkZDNjYxNF0gYW5kIHRoZSBwcm9jZWR1cmVz
IGRlc2NyaWJlZCBmb3IgdGhlIFNUQVJUVExTCiAgIGNvbW1hbmQgaW4gW1JGQzQ1MTNdLgoKCgoK
TG9wZXosIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBKYW51YXJ5IDI5LCAyMDE4ICAgICAgICAg
ICAgICAgW1BhZ2UgMTZdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgU2VjdXJlIFRyYW5zcG9y
dCBmb3IgUENFUCAgICAgICAgICAgICAgSnVseSAyMDE3CgoKICAgV2Ugd291bGQgbGlrZSB0byB0
aGFuayBKb2UgVG91Y2ggZm9yIGhpcyBzdWdnZXN0aW9ucyBhbmQgc3VwcG9ydAogICByZWdhcmRp
bmcgdGhlIFRMUyBzdGFydCBtZWNoYW5pc21zLgoKICAgVGhhbmtzIHRvIERhbmllbCBLaW5nIGZv
ciByZW1pbmRpbmcgdGhlIGF1dGhvcnMgYWJvdXQgbWFuYWdlYWJpbGl0eQogICBjb25zaWRlcmF0
aW9ucy4KCiAgIFRoYW5rcyB0byBDeXJpbCBNYXJnYXJpYSBmb3Igc2hlcGhlcmRpbmcgdGhpcyBk
b2N1bWVudC4KCiAgIFRoYW5rcyB0byBEYXZpZCBNYW5kZWxiZXJnIGZvciBlYXJseSBTRUNESVIg
cmV2aWV3IGNvbW1lbnRzIGFzIHdlbGwKICAgYXMgcmUtcmV2aWV3aW5nIGR1cmluZyBJRVRGIGxh
c3QgY2FsbC4KCiAgIFRoYW5rcyB0byBEYW4gRnJvc3QgZm9yIHRoZSBSVEdESVIgcmV2aWV3IGFu
ZCBjb21tZW50cy4KCiAgIFRoYW5rcyB0byBEYWxlIFdvcmxleSBmb3IgdGhlIEdlbi1BUlQgcmV2
aWV3IGFuZCBjb21tZW50cy4KCiAgIEFsc28gdGhhbmtzIHRvIFRpYW5yYW4gWmhvdSBmb3IgT1BT
RElSIHJldmlldy4KCiAgIFRoYW5rcyB0byBEZWJvcmFoIEJydW5nYXJkIGZvciBiZWluZyB0aGUg
cmVzcG9uc2libGUgQUQgYW5kIGd1aWRpbmcKICAgdGhlIGF1dGhvcnMgYXMgbmVlZGVkLgoKMTAu
ICBSZWZlcmVuY2VzCgoxMC4xLiAgTm9ybWF0aXZlIFJlZmVyZW5jZXMKCiAgIFtSRkMyMTE5XSAg
QnJhZG5lciwgUy4sICJLZXkgd29yZHMgZm9yIHVzZSBpbiBSRkNzIHRvIEluZGljYXRlCiAgICAg
ICAgICAgICAgUmVxdWlyZW1lbnQgTGV2ZWxzIiwgQkNQIDE0LCBSRkMgMjExOSwKICAgICAgICAg
ICAgICBET0kgMTAuMTc0ODcvUkZDMjExOSwgTWFyY2ggMTk5NywKICAgICAgICAgICAgICA8aHR0
cDovL3d3dy5yZmMtZWRpdG9yLm9yZy9pbmZvL3JmYzIxMTk+LgoKICAgW1JGQzUyNDZdICBEaWVy
a3MsIFQuIGFuZCBFLiBSZXNjb3JsYSwgIlRoZSBUcmFuc3BvcnQgTGF5ZXIgU2VjdXJpdHkKICAg
ICAgICAgICAgICAoVExTKSBQcm90b2NvbCBWZXJzaW9uIDEuMiIsIFJGQyA1MjQ2LAogICAgICAg
ICAgICAgIERPSSAxMC4xNzQ4Ny9SRkM1MjQ2LCBBdWd1c3QgMjAwOCwKICAgICAgICAgICAgICA8
aHR0cDovL3d3dy5yZmMtZWRpdG9yLm9yZy9pbmZvL3JmYzUyNDY+LgoKICAgW1JGQzUyODBdICBD
b29wZXIsIEQuLCBTYW50ZXNzb24sIFMuLCBGYXJyZWxsLCBTLiwgQm9leWVuLCBTLiwKICAgICAg
ICAgICAgICBIb3VzbGV5LCBSLiwgYW5kIFcuIFBvbGssICJJbnRlcm5ldCBYLjUwOSBQdWJsaWMg
S2V5CiAgICAgICAgICAgICAgSW5mcmFzdHJ1Y3R1cmUgQ2VydGlmaWNhdGUgYW5kIENlcnRpZmlj
YXRlIFJldm9jYXRpb24gTGlzdAogICAgICAgICAgICAgIChDUkwpIFByb2ZpbGUiLCBSRkMgNTI4
MCwgRE9JIDEwLjE3NDg3L1JGQzUyODAsIE1heSAyMDA4LAogICAgICAgICAgICAgIDxodHRwOi8v
d3d3LnJmYy1lZGl0b3Iub3JnL2luZm8vcmZjNTI4MD4uCgogICBbUkZDNTI4OF0gIFNhbG93ZXks
IEouLCBDaG91ZGh1cnksIEEuLCBhbmQgRC4gTWNHcmV3LCAiQUVTIEdhbG9pcwogICAgICAgICAg
ICAgIENvdW50ZXIgTW9kZSAoR0NNKSBDaXBoZXIgU3VpdGVzIGZvciBUTFMiLCBSRkMgNTI4OCwK
ICAgICAgICAgICAgICBET0kgMTAuMTc0ODcvUkZDNTI4OCwgQXVndXN0IDIwMDgsCiAgICAgICAg
ICAgICAgPGh0dHA6Ly93d3cucmZjLWVkaXRvci5vcmcvaW5mby9yZmM1Mjg4Pi4KCgoKCgoKCkxv
cGV6LCBldCBhbC4gICAgICAgICAgIEV4cGlyZXMgSmFudWFyeSAyOSwgMjAxOCAgICAgICAgICAg
ICAgIFtQYWdlIDE3XQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgIFNlY3VyZSBUcmFuc3BvcnQg
Zm9yIFBDRVAgICAgICAgICAgICAgIEp1bHkgMjAxNwoKCiAgIFtSRkM1NDQwXSAgVmFzc2V1ciwg
SlAuLCBFZC4gYW5kIEpMLiBMZSBSb3V4LCBFZC4sICJQYXRoIENvbXB1dGF0aW9uCiAgICAgICAg
ICAgICAgRWxlbWVudCAoUENFKSBDb21tdW5pY2F0aW9uIFByb3RvY29sIChQQ0VQKSIsIFJGQyA1
NDQwLAogICAgICAgICAgICAgIERPSSAxMC4xNzQ4Ny9SRkM1NDQwLCBNYXJjaCAyMDA5LAogICAg
ICAgICAgICAgIDxodHRwOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2luZm8vcmZjNTQ0MD4uCgogICBb
UkZDNTc0Nl0gIFJlc2NvcmxhLCBFLiwgUmF5LCBNLiwgRGlzcGVuc2EsIFMuLCBhbmQgTi4gT3Nr
b3YsCiAgICAgICAgICAgICAgIlRyYW5zcG9ydCBMYXllciBTZWN1cml0eSAoVExTKSBSZW5lZ290
aWF0aW9uIEluZGljYXRpb24KICAgICAgICAgICAgICBFeHRlbnNpb24iLCBSRkMgNTc0NiwgRE9J
IDEwLjE3NDg3L1JGQzU3NDYsIEZlYnJ1YXJ5IDIwMTAsCiAgICAgICAgICAgICAgPGh0dHA6Ly93
d3cucmZjLWVkaXRvci5vcmcvaW5mby9yZmM1NzQ2Pi4KCiAgIFtSRkM2MDY2XSAgRWFzdGxha2Ug
M3JkLCBELiwgIlRyYW5zcG9ydCBMYXllciBTZWN1cml0eSAoVExTKQogICAgICAgICAgICAgIEV4
dGVuc2lvbnM6IEV4dGVuc2lvbiBEZWZpbml0aW9ucyIsIFJGQyA2MDY2LAogICAgICAgICAgICAg
IERPSSAxMC4xNzQ4Ny9SRkM2MDY2LCBKYW51YXJ5IDIwMTEsCiAgICAgICAgICAgICAgPGh0dHA6
Ly93d3cucmZjLWVkaXRvci5vcmcvaW5mby9yZmM2MDY2Pi4KCiAgIFtSRkM2Njk4XSAgSG9mZm1h
biwgUC4gYW5kIEouIFNjaGx5dGVyLCAiVGhlIEROUy1CYXNlZCBBdXRoZW50aWNhdGlvbgogICAg
ICAgICAgICAgIG9mIE5hbWVkIEVudGl0aWVzIChEQU5FKSBUcmFuc3BvcnQgTGF5ZXIgU2VjdXJp
dHkgKFRMUykKICAgICAgICAgICAgICBQcm90b2NvbDogVExTQSIsIFJGQyA2Njk4LCBET0kgMTAu
MTc0ODcvUkZDNjY5OCwgQXVndXN0CiAgICAgICAgICAgICAgMjAxMiwgPGh0dHA6Ly93d3cucmZj
LWVkaXRvci5vcmcvaW5mby9yZmM2Njk4Pi4KCiAgIFtSRkM3NTI1XSAgU2hlZmZlciwgWS4sIEhv
bHosIFIuLCBhbmQgUC4gU2FpbnQtQW5kcmUsCiAgICAgICAgICAgICAgIlJlY29tbWVuZGF0aW9u
cyBmb3IgU2VjdXJlIFVzZSBvZiBUcmFuc3BvcnQgTGF5ZXIKICAgICAgICAgICAgICBTZWN1cml0
eSAoVExTKSBhbmQgRGF0YWdyYW0gVHJhbnNwb3J0IExheWVyIFNlY3VyaXR5CiAgICAgICAgICAg
ICAgKERUTFMpIiwgQkNQIDE5NSwgUkZDIDc1MjUsIERPSSAxMC4xNzQ4Ny9SRkM3NTI1LCBNYXkK
ICAgICAgICAgICAgICAyMDE1LCA8aHR0cDovL3d3dy5yZmMtZWRpdG9yLm9yZy9pbmZvL3JmYzc1
MjU+LgoKICAgW1NIU10gICAgICBOYXRpb25hbCBJbnN0aXR1dGUgb2YgU3RhbmRhcmRzIGFuZCBU
ZWNobm9sb2d5LCAiU2VjdXJlCiAgICAgICAgICAgICAgSGFzaCBTdGFuZGFyZCAoU0hTKSwgRklQ
UyBQVUIgMTgwLTQiLAogICAgICAgICAgICAgIERPSSAxMC42MDI4L05JU1QuRklQUy4xODAtNCwg
QXVndXN0IDIwMTUsCiAgICAgICAgICAgICAgPGh0dHA6Ly9udmxwdWJzLm5pc3QuZ292L25pc3Rw
dWJzL0ZJUFMvCiAgICAgICAgICAgICAgTklTVC5GSVBTLjE4MC00LnBkZj4uCgoxMC4yLiAgSW5m
b3JtYXRpdmUgUmVmZXJlbmNlcwoKICAgW1JGQzQ1MTNdICBIYXJyaXNvbiwgUi4sIEVkLiwgIkxp
Z2h0d2VpZ2h0IERpcmVjdG9yeSBBY2Nlc3MgUHJvdG9jb2wKICAgICAgICAgICAgICAoTERBUCk6
IEF1dGhlbnRpY2F0aW9uIE1ldGhvZHMgYW5kIFNlY3VyaXR5IE1lY2hhbmlzbXMiLAogICAgICAg
ICAgICAgIFJGQyA0NTEzLCBET0kgMTAuMTc0ODcvUkZDNDUxMywgSnVuZSAyMDA2LAogICAgICAg
ICAgICAgIDxodHRwOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2luZm8vcmZjNDUxMz4uCgogICBbUkZD
NTA4OF0gIExlIFJvdXgsIEpMLiwgRWQuLCBWYXNzZXVyLCBKUC4sIEVkLiwgSWtlamlyaSwgWS4s
IGFuZCBSLgogICAgICAgICAgICAgIFpoYW5nLCAiT1NQRiBQcm90b2NvbCBFeHRlbnNpb25zIGZv
ciBQYXRoIENvbXB1dGF0aW9uCiAgICAgICAgICAgICAgRWxlbWVudCAoUENFKSBEaXNjb3Zlcnki
LCBSRkMgNTA4OCwgRE9JIDEwLjE3NDg3L1JGQzUwODgsCiAgICAgICAgICAgICAgSmFudWFyeSAy
MDA4LCA8aHR0cDovL3d3dy5yZmMtZWRpdG9yLm9yZy9pbmZvL3JmYzUwODg+LgoKICAgW1JGQzUw
ODldICBMZSBSb3V4LCBKTC4sIEVkLiwgVmFzc2V1ciwgSlAuLCBFZC4sIElrZWppcmksIFkuLCBh
bmQgUi4KICAgICAgICAgICAgICBaaGFuZywgIklTLUlTIFByb3RvY29sIEV4dGVuc2lvbnMgZm9y
IFBhdGggQ29tcHV0YXRpb24KICAgICAgICAgICAgICBFbGVtZW50IChQQ0UpIERpc2NvdmVyeSIs
IFJGQyA1MDg5LCBET0kgMTAuMTc0ODcvUkZDNTA4OSwKICAgICAgICAgICAgICBKYW51YXJ5IDIw
MDgsIDxodHRwOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2luZm8vcmZjNTA4OT4uCgoKCkxvcGV6LCBl
dCBhbC4gICAgICAgICAgIEV4cGlyZXMgSmFudWFyeSAyOSwgMjAxOCAgICAgICAgICAgICAgIFtQ
YWdlIDE4XQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgIFNlY3VyZSBUcmFuc3BvcnQgZm9yIFBD
RVAgICAgICAgICAgICAgIEp1bHkgMjAxNwoKCiAgIFtSRkM1OTI1XSAgVG91Y2gsIEouLCBNYW5r
aW4sIEEuLCBhbmQgUi4gQm9uaWNhLCAiVGhlIFRDUAogICAgICAgICAgICAgIEF1dGhlbnRpY2F0
aW9uIE9wdGlvbiIsIFJGQyA1OTI1LCBET0kgMTAuMTc0ODcvUkZDNTkyNSwKICAgICAgICAgICAg
ICBKdW5lIDIwMTAsIDxodHRwOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2luZm8vcmZjNTkyNT4uCgog
ICBbUkZDNjYxNF0gIFdpbnRlciwgUy4sIE1jQ2F1bGV5LCBNLiwgVmVuYWFzLCBTLiwgYW5kIEsu
IFdpZXJlbmdhLAogICAgICAgICAgICAgICJUcmFuc3BvcnQgTGF5ZXIgU2VjdXJpdHkgKFRMUykg
RW5jcnlwdGlvbiBmb3IgUkFESVVTIiwKICAgICAgICAgICAgICBSRkMgNjYxNCwgRE9JIDEwLjE3
NDg3L1JGQzY2MTQsIE1heSAyMDEyLAogICAgICAgICAgICAgIDxodHRwOi8vd3d3LnJmYy1lZGl0
b3Iub3JnL2luZm8vcmZjNjYxND4uCgogICBbUkZDNjk1Ml0gIEpldGhhbmFuZGFuaSwgTS4sIFBh
dGVsLCBLLiwgYW5kIEwuIFpoZW5nLCAiQW5hbHlzaXMgb2YKICAgICAgICAgICAgICBCR1AsIExE
UCwgUENFUCwgYW5kIE1TRFAgSXNzdWVzIEFjY29yZGluZyB0byB0aGUgS2V5aW5nCiAgICAgICAg
ICAgICAgYW5kIEF1dGhlbnRpY2F0aW9uIGZvciBSb3V0aW5nIFByb3RvY29scyAoS0FSUCkgRGVz
aWduCiAgICAgICAgICAgICAgR3VpZGUiLCBSRkMgNjk1MiwgRE9JIDEwLjE3NDg3L1JGQzY5NTIs
IE1heSAyMDEzLAogICAgICAgICAgICAgIDxodHRwOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2luZm8v
cmZjNjk1Mj4uCgogICBbUkZDNzQyMF0gIEtvdXNoaWssIEEuLCBTdGVwaGFuLCBFLiwgWmhhbywg
US4sIEtpbmcsIEQuLCBhbmQgSi4KICAgICAgICAgICAgICBIYXJkd2ljaywgIlBhdGggQ29tcHV0
YXRpb24gRWxlbWVudCBDb21tdW5pY2F0aW9uIFByb3RvY29sCiAgICAgICAgICAgICAgKFBDRVAp
IE1hbmFnZW1lbnQgSW5mb3JtYXRpb24gQmFzZSAoTUlCKSBNb2R1bGUiLAogICAgICAgICAgICAg
IFJGQyA3NDIwLCBET0kgMTAuMTc0ODcvUkZDNzQyMCwgRGVjZW1iZXIgMjAxNCwKICAgICAgICAg
ICAgICA8aHR0cDovL3d3dy5yZmMtZWRpdG9yLm9yZy9pbmZvL3JmYzc0MjA+LgoKICAgW0ktRC5p
ZXRmLXBjZS1zdGF0ZWZ1bC1zeW5jLW9wdGltaXphdGlvbnNdCiAgICAgICAgICAgICAgQ3JhYmJl
LCBFLiwgTWluZWksIEkuLCBNZWR2ZWQsIEouLCBWYXJnYSwgUi4sIFpoYW5nLCBYLiwKICAgICAg
ICAgICAgICBhbmQgRC4gRGhvZHksICJPcHRpbWl6YXRpb25zIG9mIExhYmVsIFN3aXRjaGVkIFBh
dGggU3RhdGUKICAgICAgICAgICAgICBTeW5jaHJvbml6YXRpb24gUHJvY2VkdXJlcyBmb3IgYSBT
dGF0ZWZ1bCBQQ0UiLCBkcmFmdC0KICAgICAgICAgICAgICBpZXRmLXBjZS1zdGF0ZWZ1bC1zeW5j
LW9wdGltaXphdGlvbnMtMTAgKHdvcmsgaW4KICAgICAgICAgICAgICBwcm9ncmVzcyksIE1hcmNo
IDIwMTcuCgogICBbSS1ELmlldGYtcGNlLXBjZXAteWFuZ10KICAgICAgICAgICAgICBEaG9keSwg
RC4sIEhhcmR3aWNrLCBKLiwgQmVlcmFtLCBWLiwgYW5kIGouCiAgICAgICAgICAgICAgamVmZnRh
bnRAZ21haWwuY29tLCAiQSBZQU5HIERhdGEgTW9kZWwgZm9yIFBhdGgKICAgICAgICAgICAgICBD
b21wdXRhdGlvbiBFbGVtZW50IENvbW11bmljYXRpb25zIFByb3RvY29sIChQQ0VQKSIsCiAgICAg
ICAgICAgICAgZHJhZnQtaWV0Zi1wY2UtcGNlcC15YW5nLTA1ICh3b3JrIGluIHByb2dyZXNzKSwg
SnVuZSAyMDE3LgoKICAgW0ktRC53dS1wY2UtZG5zLXBjZS1kaXNjb3ZlcnldCiAgICAgICAgICAg
ICAgV3UsIFEuLCBEaG9keSwgRC4sIEtpbmcsIEQuLCBMb3BleiwgRC4sIGFuZCBKLiBUYW50c3Vy
YSwKICAgICAgICAgICAgICAiUGF0aCBDb21wdXRhdGlvbiBFbGVtZW50IChQQ0UpIERpc2NvdmVy
eSB1c2luZyBEb21haW4KICAgICAgICAgICAgICBOYW1lIFN5c3RlbShETlMpIiwgZHJhZnQtd3Ut
cGNlLWRucy1wY2UtZGlzY292ZXJ5LTEwICh3b3JrCiAgICAgICAgICAgICAgaW4gcHJvZ3Jlc3Mp
LCBNYXJjaCAyMDE3LgoKICAgW0ktRC53dS1wY2UtZGlzY292ZXJ5LXBjZXBzLXN1cHBvcnRdCiAg
ICAgICAgICAgICAgTG9wZXosIEQuLCBXdSwgUS4sIERob2R5LCBELiwgYW5kIEQuIEtpbmcsICJJ
R1AgZXh0ZW5zaW9uCiAgICAgICAgICAgICAgZm9yIFBDRVAgc2VjdXJpdHkgY2FwYWJpbGl0eSBz
dXBwb3J0IGluIHRoZSBQQ0UKICAgICAgICAgICAgICBkaXNjb3ZlcnkiLCBkcmFmdC13dS1wY2Ut
ZGlzY292ZXJ5LXBjZXBzLXN1cHBvcnQtMDcgKHdvcmsKICAgICAgICAgICAgICBpbiBwcm9ncmVz
cyksIE1hcmNoIDIwMTcuCgoKCgoKCkxvcGV6LCBldCBhbC4gICAgICAgICAgIEV4cGlyZXMgSmFu
dWFyeSAyOSwgMjAxOCAgICAgICAgICAgICAgIFtQYWdlIDE5XQoMCkludGVybmV0LURyYWZ0ICAg
ICAgICAgIFNlY3VyZSBUcmFuc3BvcnQgZm9yIFBDRVAgICAgICAgICAgICAgIEp1bHkgMjAxNwoK
CkF1dGhvcnMnIEFkZHJlc3NlcwoKICAgRGllZ28gUi4gTG9wZXoKICAgVGVsZWZvbmljYSBJK0QK
ICAgRG9uIFJhbW9uIGRlIGxhIENydXosIDgyCiAgIE1hZHJpZCAgMjgwMDYKICAgU3BhaW4KCiAg
IFBob25lOiArMzQgOTEzIDEyOSAwNDEKICAgRU1haWw6IGRpZWdvLnIubG9wZXpAdGVsZWZvbmlj
YS5jb20KCgogICBPc2NhciBHb256YWxleiBkZSBEaW9zCiAgIFRlbGVmb25pY2EgSStECiAgIERv
biBSYW1vbiBkZSBsYSBDcnV6LCA4MgogICBNYWRyaWQgIDI4MDA2CiAgIFNwYWluCgogICBQaG9u
ZTogKzM0IDkxMyAxMjkgMDQxCiAgIEVNYWlsOiBvc2Nhci5nb256YWxlemRlZGlvc0B0ZWxlZm9u
aWNhLmNvbQoKCiAgIFFpbiBXdQogICBIdWF3ZWkKICAgMTAxIFNvZnR3YXJlIEF2ZW51ZSwgWXVo
dWEgRGlzdHJpY3QKICAgTmFuamluZywgSmlhbmdzdSAgMjEwMDEyCiAgIENoaW5hCgogICBFTWFp
bDogc3Vuc2Vhd3FAaHVhd2VpLmNvbQoKCiAgIERocnV2IERob2R5CiAgIEh1YXdlaQogICBEaXZ5
YXNocmVlIFRlY2hubyBQYXJrLCBXaGl0ZWZpZWxkCiAgIEJhbmdhbG9yZSwgS0EgIDU2MDA2Ngog
ICBJbmRpYQoKICAgRU1haWw6IGRocnV2LmlldGZAZ21haWwuY29tCgoKCgoKCgoKCgoKCgpMb3Bl
eiwgZXQgYWwuICAgICAgICAgICBFeHBpcmVzIEphbnVhcnkgMjksIDIwMTggICAgICAgICAgICAg
ICBbUGFnZSAyMF0K

--_003_23CE718903A838468A8B325B80962F9B8CB95DF7blreml501mbb_
Content-Type: text/html;
	name="Diff_ draft-ietf-pce-pceps-14.txt - draft-ietf-pce-pceps-15.txt.html"
Content-Description: Diff_ draft-ietf-pce-pceps-14.txt -
 draft-ietf-pce-pceps-15.txt.html
Content-Disposition: attachment; filename="Diff_ draft-ietf-pce-pceps-14.txt
 - draft-ietf-pce-pceps-15.txt.html"; size=133826;
	creation-date="Fri, 28 Jul 2017 10:21:02 GMT";
	modification-date="Fri, 28 Jul 2017 10:21:02 GMT"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIGh0bWwgUFVCTElDICItLy9XM0MvL0RURCBYSFRNTCAxLjAgVHJhbnNpdGlvbmFs
Ly9FTiIgImh0dHA6Ly93d3cudzMub3JnL1RSL3hodG1sMS9EVEQveGh0bWwxLXRyYW5zaXRpb25h
bC5kdGQiPgo8IS0tIHNhdmVkIGZyb20gdXJsPSgwMDMwKWh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcv
cmZjZGlmZiAtLT4KPGh0bWwgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkveGh0bWwiPjxo
ZWFkPjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0idGV4dC9odG1sOyBj
aGFyc2V0PVVURi04Ij4gCiAgIAogIDxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtU3R5bGUtVHlw
ZSIgY29udGVudD0idGV4dC9jc3MiPiAKICA8dGl0bGU+RGlmZjogZHJhZnQtaWV0Zi1wY2UtcGNl
cHMtMTQudHh0IC0gZHJhZnQtaWV0Zi1wY2UtcGNlcHMtMTUudHh0PC90aXRsZT4gCiAgPHN0eWxl
IHR5cGU9InRleHQvY3NzIj4gCiAgICBib2R5ICAgIHsgbWFyZ2luOiAwLjRleDsgbWFyZ2luLXJp
Z2h0OiBhdXRvOyB9IAogICAgdHIgICAgICB7IH0gCiAgICB0ZCAgICAgIHsgd2hpdGUtc3BhY2U6
IHByZTsgZm9udC1mYW1pbHk6IG1vbm9zcGFjZTsgdmVydGljYWwtYWxpZ246IHRvcDsgZm9udC1z
aXplOiAwLjg2ZW07fSAKICAgIHRoICAgICAgeyBmb250LXNpemU6IDAuODZlbTsgfSAKICAgIC5z
bWFsbCAgeyBmb250LXNpemU6IDAuNmVtOyBmb250LXN0eWxlOiBpdGFsaWM7IGZvbnQtZmFtaWx5
OiBWZXJkYW5hLCBIZWx2ZXRpY2EsIHNhbnMtc2VyaWY7IH0gCiAgICAubGVmdCAgIHsgYmFja2dy
b3VuZC1jb2xvcjogI0VFRTsgfSAKICAgIC5yaWdodCAgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjRkZG
OyB9IAogICAgLmRpZmYgICB7IGJhY2tncm91bmQtY29sb3I6ICNDQ0Y7IH0gCiAgICAubGJsb2Nr
IHsgYmFja2dyb3VuZC1jb2xvcjogI0JGQjsgfSAKICAgIC5yYmxvY2sgeyBiYWNrZ3JvdW5kLWNv
bG9yOiAjRkY4OyB9IAogICAgLmluc2VydCB7IGJhY2tncm91bmQtY29sb3I6ICM4RkY7IH0gCiAg
ICAuZGVsZXRlIHsgYmFja2dyb3VuZC1jb2xvcjogI0FDRjsgfSAKICAgIC52b2lkICAgeyBiYWNr
Z3JvdW5kLWNvbG9yOiAjRkZCOyB9IAogICAgLmNvbnQgICB7IGJhY2tncm91bmQtY29sb3I6ICNF
RUU7IH0gCiAgICAubGluZWJyIHsgYmFja2dyb3VuZC1jb2xvcjogI0FBQTsgfSAKICAgIC5saW5l
bm8geyBjb2xvcjogcmVkOyBiYWNrZ3JvdW5kLWNvbG9yOiAjRkZGOyBmb250LXNpemU6IDAuN2Vt
OyB0ZXh0LWFsaWduOiByaWdodDsgcGFkZGluZzogMCAycHg7IH0gCiAgICAuZWxpcHNpc3sgYmFj
a2dyb3VuZC1jb2xvcjogI0FBQTsgfSAKICAgIC5sZWZ0IC5jb250IHsgYmFja2dyb3VuZC1jb2xv
cjogI0RERDsgfSAKICAgIC5yaWdodCAuY29udCB7IGJhY2tncm91bmQtY29sb3I6ICNFRUU7IH0g
CiAgICAubGJsb2NrIC5jb250IHsgYmFja2dyb3VuZC1jb2xvcjogIzlEOTsgfSAKICAgIC5yYmxv
Y2sgLmNvbnQgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjREQ2OyB9IAogICAgLmluc2VydCAuY29udCB7
IGJhY2tncm91bmQtY29sb3I6ICMwREQ7IH0gCiAgICAuZGVsZXRlIC5jb250IHsgYmFja2dyb3Vu
ZC1jb2xvcjogIzhBRDsgfSAKICAgIC5zdGF0cywgLnN0YXRzIHRkLCAuc3RhdHMgdGggeyBiYWNr
Z3JvdW5kLWNvbG9yOiAjRUVFOyBwYWRkaW5nOiAycHggMDsgfSAKICAgIHNwYW4uaGlkZSB7IGRp
c3BsYXk6IG5vbmU7IGNvbG9yOiAjYWFhO30gICAgYTpob3ZlciBzcGFuIHsgZGlzcGxheTogaW5s
aW5lOyB9ICAgIHRyLmNoYW5nZSB7IGJhY2tncm91bmQtY29sb3I6IGdyYXk7IH0gCiAgICB0ci5j
aGFuZ2UgYSB7IHRleHQtZGVjb3JhdGlvbjogbm9uZTsgY29sb3I6IGJsYWNrIH0gCiAgPC9zdHls
ZT4gCiAgICAgPHNjcmlwdD4KdmFyIGNodW5rX2luZGV4ID0gMDsKdmFyIG9sZF9jaHVuayA9IG51
bGw7CgpmdW5jdGlvbiBmb3JtYXRfY2h1bmsoaW5kZXgpIHsKICAgIHZhciBwcmVmaXggPSAiZGlm
ZiI7CiAgICB2YXIgc3RyID0gaW5kZXgudG9TdHJpbmcoKTsKICAgIGZvciAoeD0wOyB4PCg0LXN0
ci5sZW5ndGgpOyArK3gpIHsKICAgICAgICBwcmVmaXgrPScwJzsKICAgIH0KICAgIHJldHVybiBw
cmVmaXggKyBzdHI7Cn0KCmZ1bmN0aW9uIGZpbmRfY2h1bmsobil7CiAgICByZXR1cm4gZG9jdW1l
bnQucXVlcnlTZWxlY3RvcigndHJbaWQkPSInICsgbiArICciXScpOwp9CgpmdW5jdGlvbiBjaGFu
Z2VfY2h1bmsob2Zmc2V0KSB7CiAgICB2YXIgaW5kZXggPSBjaHVua19pbmRleCArIG9mZnNldDsK
ICAgIHZhciBuZXdfc3RyOwogICAgdmFyIG5ld19jaHVuazsKCiAgICBuZXdfc3RyID0gZm9ybWF0
X2NodW5rKGluZGV4KTsKICAgIG5ld19jaHVuayA9IGZpbmRfY2h1bmsobmV3X3N0cik7CiAgICBp
ZiAoIW5ld19jaHVuaykgewogICAgICAgIHJldHVybjsKICAgIH0KICAgIGlmIChvbGRfY2h1bmsp
IHsKICAgICAgICBvbGRfY2h1bmsuc3R5bGUub3V0bGluZSA9ICIiOwogICAgfQogICAgb2xkX2No
dW5rID0gbmV3X2NodW5rOwogICAgb2xkX2NodW5rLnN0eWxlLm91dGxpbmUgPSAiMXB4IHNvbGlk
IHJlZCI7CiAgICB3aW5kb3cubG9jYXRpb24uaGFzaCA9ICIjIiArIG5ld19zdHI7CiAgICB3aW5k
b3cuc2Nyb2xsQnkoMCwtMTAwKTsKICAgIGNodW5rX2luZGV4ID0gaW5kZXg7Cn0KCmRvY3VtZW50
Lm9ua2V5ZG93biA9IGZ1bmN0aW9uKGUpIHsKICAgIHN3aXRjaCAoZS5rZXlDb2RlKSB7CiAgICBj
YXNlIDc4OgogICAgICAgIGNoYW5nZV9jaHVuaygxKTsKICAgICAgICBicmVhazsKICAgIGNhc2Ug
ODA6CiAgICAgICAgY2hhbmdlX2NodW5rKC0xKTsKICAgICAgICBicmVhazsKICAgIH0KfTsKICAg
PC9zY3JpcHQ+IAo8c3R5bGUgdHlwZT0idGV4dC9jc3MiIGlkPSJHSU5HRVJfU09GVFdBUkVfc3R5
bGUiPi5HSU5HRVJfU09GVFdBUkVfbm9NYXJrIHsgYmFja2dyb3VuZCA6IHRyYW5zcGFyZW50OyB9
ICAuR0lOR0VSX1NPRlRXQVJFX3dyYXBwZXJ7IHBvc2l0aW9uOiBhYnNvbHV0ZTsgb3ZlcmZsb3c6
IGhpZGRlbjsgbWFyZ2luOiAwcHg7IHBhZGRpbmc6IDBweDsgYm9yZGVyOiAwcHggc29saWQgdHJh
bnNwYXJlbnQgfSAuR0lOR0VSX1NPRlRXQVJFX2NvbnRvdXIgeyBwb3NpdGlvbiA6IGFic29sdXRl
OyBtYXJnaW46IDBweDsgfSAgLkdJTkdFUl9TT0ZUV0FSRV9yaWNoVGV4dCB7IG1hcmdpbiA6IDBw
eDsgcGFkZGluZy1ib3R0b206IDNweDsgYm9yZGVyLXdpZHRoOiAwcHg7IGJvcmRlci1jb2xvcjog
dHJhbnNwYXJlbnQ7IGRpc3BsYXk6IGJsb2NrOyBjb2xvcjogdHJhbnNwYXJlbnQ7IC13ZWJraXQt
dGV4dC1maWxsLWNvbG9yOiB0cmFuc3BhcmVudDsgb3ZlcmZsb3c6IGhpZGRlbjsgd2hpdGUtc3Bh
Y2U6IHByZS13cmFwO30gIC5HSU5HRVJfU09GVFdBUkVfaW5wdXRXcmFwcGVyIC5HSU5HRVJfU09G
VFdBUkVfcmljaFRleHQge3Bvc2l0aW9uOiBhYnNvbHV0ZTt9ICAuR0lOR0VSX1NPRlRXQVJFX2Nh
bnZhcyB7IGRpc3BsYXk6bm9uZTsgYmFja2dyb3VuZC1yZXBlYXQ6bm8tcmVwZWF0O30gIC5HSU5H
RVJfU09GVFdBUkVfY29udHJvbCAuR0lOR0VSX1NPRlRXQVJFX2NvcnJlY3QsIC5HSU5HRVJfU09G
VFdBUkVfY29udHJvbCAuR0lOR0VSX1NPRlRXQVJFX1NwZWxsaW5nQ29ycmVjdCwgLkdJTkdFUl9T
T0ZUV0FSRV9jb250cm9sIC5HSU5HRVJfU09GVFdBUkVfc3BlbGxpbmcsIC5HSU5HRVJfU09GVFdB
UkVfY29udHJvbCAuR0lOR0VSX1NPRlRXQVJFX21hcmsge2JvcmRlci10b3AtbGVmdC1yYWRpdXM6
MnB4OyBib3JkZXItdG9wLXJpZ2h0LXJhZGl1czoycHg7IGJvcmRlci1ib3R0b20tcmlnaHQtcmFk
aXVzOjJweDsgYm9yZGVyLWJvdHRvbS1sZWZ0LXJhZGl1czoycHg7fSAuR0lOR0VSX1NPRlRXQVJF
X2NvbnRyb2wgLkdJTkdFUl9TT0ZUV0FSRV9jb3JyZWN0LCAuR0lOR0VSX1NPRlRXQVJFX2NvbnRy
b2wgLkdJTkdFUl9TT0ZUV0FSRV9TcGVsbGluZ0NvcnJlY3QsIC5HSU5HRVJfU09GVFdBUkVfY29u
dHJvbCAuR0lOR0VSX1NPRlRXQVJFX3NwZWxsaW5nLCAuR0lOR0VSX1NPRlRXQVJFX2NvbnRyb2wg
LkdJTkdFUl9TT0ZUV0FSRV9tYXJrIHtiYWNrZ3JvdW5kLWltYWdlOnVybChkYXRhOmltYWdlL2dp
ZjtiYXNlNjQsaVZCT1J3MEtHZ29BQUFBTlNVaEVVZ0FBQUFFQUFBQUJDQUlBQUFDUWQxUGVBQUFB
R1hSRldIUlRiMlowZDJGeVpRQkJaRzlpWlNCSmJXRm5aVkpsWVdSNWNjbGxQQUFBQXlCcFZGaDBX
RTFNT21OdmJTNWhaRzlpWlM1NGJYQUFBQUFBQUR3L2VIQmhZMnRsZENCaVpXZHBiajBpNzd1L0lp
QnBaRDBpVnpWTk1FMXdRMlZvYVVoNmNtVlRlazVVWTNwcll6bGtJajgrSUR4NE9uaHRjRzFsZEdF
Z2VHMXNibk02ZUQwaVlXUnZZbVU2Ym5NNmJXVjBZUzhpSUhnNmVHMXdkR3M5SWtGa2IySmxJRmhO
VUNCRGIzSmxJRFV1TUMxak1EWXdJRFl4TGpFek5EYzNOeXdnTWpBeE1DOHdNaTh4TWkweE56b3pN
am93TUNBZ0lDQWdJQ0FnSWo0Z1BISmtaanBTUkVZZ2VHMXNibk02Y21SbVBTSm9kSFJ3T2k4dmQz
ZDNMbmN6TG05eVp5OHhPVGs1THpBeUx6SXlMWEprWmkxemVXNTBZWGd0Ym5NaklqNGdQSEprWmpw
RVpYTmpjbWx3ZEdsdmJpQnlaR1k2WVdKdmRYUTlJaUlnZUcxc2JuTTZlRzF3UFNKb2RIUndPaTh2
Ym5NdVlXUnZZbVV1WTI5dEwzaGhjQzh4TGpBdklpQjRiV3h1Y3pwNGJYQk5UVDBpYUhSMGNEb3ZM
MjV6TG1Ga2IySmxMbU52YlM5NFlYQXZNUzR3TDIxdEx5SWdlRzFzYm5NNmMzUlNaV1k5SW1oMGRI
QTZMeTl1Y3k1aFpHOWlaUzVqYjIwdmVHRndMekV1TUM5elZIbHdaUzlTWlhOdmRYSmpaVkpsWmlN
aUlIaHRjRHBEY21WaGRHOXlWRzl2YkQwaVFXUnZZbVVnVUdodmRHOXphRzl3SUVOVE5TQlhhVzVr
YjNkeklpQjRiWEJOVFRwSmJuTjBZVzVqWlVsRVBTSjRiWEF1YVdsa09qaEZRMFkyT0VOR016RTVP
VEV4UlRJNE5qTXhPVEV4TlRVeU1EaEVNRE13SWlCNGJYQk5UVHBFYjJOMWJXVnVkRWxFUFNKNGJY
QXVaR2xrT2poRlEwWTJPRVF3TXpFNU9URXhSVEk0TmpNeE9URXhOVFV5TURoRU1ETXdJajRnUEho
dGNFMU5Pa1JsY21sMlpXUkdjbTl0SUhOMFVtVm1PbWx1YzNSaGJtTmxTVVE5SW5odGNDNXBhV1E2
T0VWRFJqWTRRMFF6TVRrNU1URkZNamcyTXpFNU1URTFOVEl3T0VRd016QWlJSE4wVW1WbU9tUnZZ
M1Z0Wlc1MFNVUTlJbmh0Y0M1a2FXUTZPRVZEUmpZNFEwVXpNVGs1TVRGRk1qZzJNekU1TVRFMU5U
SXdPRVF3TXpBaUx6NGdQQzl5WkdZNlJHVnpZM0pwY0hScGIyNCtJRHd2Y21SbU9sSkVSajRnUEM5
NE9uaHRjRzFsZEdFK0lEdy9lSEJoWTJ0bGRDQmxibVE5SW5JaVB6NVJSeFJ4QUFBQUQwbEVRVlI0
Mm1LNDgrdzdRSUFCQUFWYkFyb293TjA4QUFBQUFFbEZUa1N1UW1DQykhaW1wb3J0YW50O30gLkdJ
TkdFUl9TT0ZUV0FSRV9jb250cm9sIC5HSU5HRVJfU09GVFdBUkVfY29ycmVjdC5HSU5HRVJfU09G
VFdBUkVfc3lub255bSwgLkdJTkdFUl9TT0ZUV0FSRV9jb250cm9sIC5HSU5HRVJfU09GVFdBUkVf
U3BlbGxpbmdDb3JyZWN0LkdJTkdFUl9TT0ZUV0FSRV9zeW5vbnltLCAuR0lOR0VSX1NPRlRXQVJF
X2NvbnRyb2wgLkdJTkdFUl9TT0ZUV0FSRV9zcGVsbGluZy5HSU5HRVJfU09GVFdBUkVfc3lub255
bSwgLkdJTkdFUl9TT0ZUV0FSRV9jb250cm9sIC5HSU5HRVJfU09GVFdBUkVfbWFyay5HSU5HRVJf
U09GVFdBUkVfc3lub255bSB7YmFja2dyb3VuZC1pbWFnZTp1cmwoZGF0YTppbWFnZS9naWY7YmFz
ZTY0LGlWQk9SdzBLR2dvQUFBQU5TVWhFVWdBQUFBRUFBQUFCQ0FJQUFBQ1FkMVBlQUFBQUNYQklX
WE1BQUFzVEFBQUxFd0VBbXB3WUFBQUtUMmxEUTFCUWFHOTBiM05vYjNBZ1NVTkRJSEJ5YjJacGJH
VUFBSGphblZOblZGUHBGajMzM3ZSQ1M0aUFsRXR2VWhVSUlGSkNpNEFVa1NZcUlRa1FTb2dob2Rr
VlVjRVJSVVVFRzhpZ2lBT09qb0NNRlZFc0RJb0syQWZrSWFLT2c2T0lpc3I3NFh1amE5YTg5K2JO
L3JYWFB1ZXM4NTJ6endmQUNBeVdTRE5STllBTXFVSWVFZUNEeDhURzRlUXVRSUVLSkhBQUVBaXpa
Q0Z6L1NNQkFQaCtQRHdySXNBSHZnQUJlTk1MQ0FEQVRadkFNQnlIL3cvcVFwbGNBWUNFQWNCMGtU
aExDSUFVQUVCNmprS21BRUJHQVlDZG1DWlRBS0FFQUdETFkyTGpBRkF0QUdBbmYrYlRBSUNkK0ps
N0FRQmJsQ0VWQWFDUkFDQVRaWWhFQUdnN0FLelBWb3BGQUZnd0FCUm1TOFE1QU5ndEFEQkpWMlpJ
QUxDM0FNRE9FQXV5QUFnTUFEQlJpSVVwQUFSN0FHRElJeU40QUlTWkFCUkc4bGM4OFN1dUVPY3FB
QUI0bWJJOHVTUTVSWUZiQ0MxeEIxZFhMaDRvemtrWEt4UTJZUUpobWtBdXdubVpHVEtCTkEvZzg4
d0FBS0NSRlJIZ2cvUDllTTRPcnM3T05vNjJEbDh0NnI4Ry95SmlZdVArNWMrcmNFQUFBT0YwZnRI
K0xDK3pHb0E3Qm9CdC9xSWw3Z1JvWGd1Z2RmZUxacklQUUxVQW9PbmFWL053K0g0OFBFV2hrTG5a
MmVYazVOaEt4RUpiWWNwWGZmNW53bC9BVi8xcytYNDgvUGYxNEw3aUpJRXlYWUZIQlBqZ3dzejBU
S1VjejVJSmhHTGM1bzlIL0xjTC8vd2QweUxFU1dLNVdDb1U0MUVTY1k1RW1venpNcVVpaVVLU0tj
VWwwdjlrNHQ4cyt3TSszelVBc0dvK0FYdVJMYWhkWXdQMlN5Y1FXSFRBNHZjQUFQSzdiOEhVS0Fn
RGdHaUQ0YzkzLys4Ly9VZWdKUUNBWmttU2NRQUFYa1FrTGxUS3N6L0hDQUFBUktDQktyQkJHL1RC
R0N6QUJoekJCZHpCQy94Z05vUkNKTVRDUWhCQ0NtU0FISEpnS2F5Q1FpaUd6YkFkS21BdjFFQWRO
TUJSYUlhVGNBNHV3bFc0RGoxd0QvcGhDSjdCS0x5QkNRUkJ5QWdUWVNIYWlBRmlpbGdqamdnWG1Z
WDRJY0ZJQkJLTEpDREppQlJSSWt1Uk5VZ3hVb3BVSUZWSUhmSTljZ0k1aDF4R3VwRTd5QUF5Z3Z5
R3ZFY3hsSUd5VVQzVURMVkR1YWczR29SR29ndlFaSFF4bW84V29KdlFjclFhUFl3Mm9lZlFxMmdQ
Mm84K1E4Y3d3T2dZQnpQRWJEQXV4c05Dc1Rnc0NaTmp5N0VpckF5cnhocXdWcXdEdTRuMVk4K3hk
d1FTZ1VYQUNUWUVkMElnWVI1QlNGaE1XRTdZU0tnZ0hDUTBFZG9KTndrRGhGSENKeUtUcUV1MEpy
b1IrY1FZWWpJeGgxaElMQ1BXRW84VEx4QjdpRVBFTnlRU2lVTXlKN21RQWtteHBGVFNFdEpHMG01
U0kra3NxWnMwU0Jvams4bmFaR3V5QnptVUxDQXJ5SVhrbmVURDVEUGtHK1FoOGxzS25XSkFjYVQ0
VStJb1VzcHFTaG5sRU9VMDVRWmxtREpCVmFPYVV0Mm9vVlFSTlk5YVFxMmh0bEt2VVllb0V6UjFt
am5OZ3haSlM2V3RvcFhUR21nWGFQZHByK2gwdWhIZGxSNU9sOUJYMHN2cFIraVg2QVAwZHd3Tmho
V0R4NGhuS0JtYkdBY1laeGwzR0srWVRLWVowNHNaeDFRd056SHJtT2VaRDVsdlZWZ3F0aXA4RlpI
S0NwVktsU2FWR3lvdlZLbXFwcXJlcWd0VjgxWExWSStwWGxOOXJrWlZNMVBqcVFuVWxxdFZxcDFR
NjFNYlUyZXBPNmlIcW1lb2IxUS9wSDVaL1lrR1djTk13MDlEcEZHZ3NWL2p2TVlnQzJNWnMzZ3NJ
V3NOcTRaMWdUWEVKckhOMlh4MktydVkvUjI3aXoycXFhRTVRek5LTTFlelV2T1VaajhINDVoeCtK
eDBUZ25uS0tlWDgzNkszaFR2S2VJcEc2WTBUTGt4WlZ4cnFwYVhsbGlyU0t0UnEwZnJ2VGF1N2Fl
ZHByMUZ1MW43Z1E1Qngwb25YQ2RIWjQvT0JaM25VOWxUM2FjS3B4Wk5QVHIxcmk2cWE2VWJvYnRF
ZDc5dXArNllucjVlZ0o1TWI2ZmVlYjNuK2h4OUwvMVUvVzM2cC9WSERGZ0dzd3drQnRzTXpoZzh4
VFZ4Ynp3ZEw4ZmI4VkZEWGNOQVE2VmhsV0dYNFlTUnVkRThvOVZHalVZUGpHbkdYT01rNDIzR2Jj
YWpKZ1ltSVNaTFRlcE43cHBTVGJtbUthWTdURHRNeDgzTXphTE4xcGsxbXoweDF6TG5tK2ViMTV2
ZnQyQmFlRm9zdHFpMnVHVkpzdVJhcGxudXRyeHVoVm81V2FWWVZWcGRzMGF0bmEwbDFydXR1NmNS
cDdsT2swNnJudFpudzdEeHRzbTJxYmNac09YWUJ0dXV0bTIyZldGblloZG50OFd1dys2VHZaTjl1
bjJOL1QwSERZZlpEcXNkV2gxK2M3UnlGRHBXT3Q2YXpwenVQMzNGOUpicEwyZFl6eERQMkRQanRo
UExLY1JwblZPYjAwZG5GMmU1YzRQemlJdUpTNExMTHBjK0xwc2J4dDNJdmVSS2RQVnhYZUY2MHZX
ZG03T2J3dTJvMjYvdU51NXA3b2Zjbjh3MG55bWVXVE56ME1QSVErQlI1ZEUvQzUrVk1HdmZySDVQ
UTArQlo3WG5JeTlqTDVGWHJkZXd0NlYzcXZkaDd4Yys5ajV5bitNKzR6dzMzakxlV1YvTU44QzN5
TGZMVDhOdm5sK0YzME4vSS85ay8zci8wUUNuZ0NVQlp3T0pnVUdCV3dMNytIcDhJYitPUHpyYlpm
YXkyZTFCaktDNVFSVkJqNEt0Z3VYQnJTRm95T3lRclNIMzU1ak9rYzVwRG9WUWZ1alcwQWRoNW1H
THczNE1KNFdIaFZlR1A0NXdpRmdhMFRHWE5YZlIzRU56MzBUNlJKWkUzcHRuTVU4NXJ5MUtOU28r
cWk1cVBObzN1alM2UDhZdVpsbk0xVmlkV0Vsc1N4dzVMaXF1Tm01c3Z0Lzg3Zk9INHAzaUMrTjdG
NWd2eUYxd2VhSE93dlNGcHhhcExoSXNPcFpBVEloT09KVHdRUkFxcUJhTUpmSVRkeVdPQ25uQ0hj
Sm5JaS9STnRHSTJFTmNLaDVPOGtncVRYcVM3Skc4Tlhra3hUT2xMT1c1aENlcGtMeE1EVXpkbXpx
ZUZwcDJJRzB5UFRxOU1ZT1NrWkJ4UXFvaFRaTzJaK3BuNW1aMnk2eGxoYkwreFc2THR5OGVsUWZK
YTdPUXJBVlpMUXEyUXFib1ZGb28xeW9Ic21kbFYyYS96WW5LT1phcm5pdk43Y3l6eXR1UU41enZu
Ly90RXNJUzRaSzJwWVpMVnkwZFdPYTlyR281c2p4eGVkc0s0eFVGSzRaV0Jxdzh1SXEyS20zVlQ2
dnRWNWV1ZnIwbWVrMXJnVjdCeW9MQnRRRnI2d3RWQ3VXRmZldmMxKzFkVDFndldkKzFZZnFHblJz
K0ZZbUtyaFRiRjVjVmY5Z28zSGpsRzRkdnlyK1ozSlMwcWF2RXVXVFBadEptNmViZUxaNWJEcGFx
bCthWERtNE4yZHEwRGQ5V3RPMzE5a1hiTDVmTktOdTdnN1pEdWFPL1BMaThaYWZKenMwN1AxU2tW
UFJVK2xRMjd0TGR0V0hYK0c3UjdodDd2UFkwN05YYlc3ejMvVDdKdnR0VkFWVk4xV2JWWmZ0Sis3
UDNQNjZKcXVuNGx2dHRYYTFPYlhIdHh3UFNBLzBISXc2MjE3blUxUjNTUFZSU2o5WXI2MGNPeHgr
Ky9wM3ZkeTBOTmcxVmpaekc0aU53UkhuazZmY0ozL2NlRFRyYWRveDdyT0VIMHg5MkhXY2RMMnBD
bXZLYVJwdFRtdnRiWWx1NlQ4dyswZGJxM25yOFI5c2ZENXcwUEZsNVN2TlV5V25hNllMVGsyZnl6
NHlkbFoxOWZpNzUzR0Rib3JaNzUyUE8zMm9QYisrNkVIVGgwa1gvaStjN3ZEdk9YUEs0ZFBLeTIr
VVRWN2hYbXE4NlgyM3FkT284L3BQVFQ4ZTduTHVhcnJsY2E3bnVlcjIxZTJiMzZSdWVOODdkOUwx
NThSYi8xdFdlT1QzZHZmTjZiL2ZGOS9YZkZ0MStjaWY5enN1NzJYY243cTI4VDd4ZjlFRHRRZGxE
M1lmVlAxdiszTmp2M0g5cXdIZWc4OUhjUi9jR2hZUFAvcEgxanc5REJZK1pqOHVHRFlicm5qZytP
VG5pUDNMOTZmeW5RODlrenlhZUYvNmkvc3V1RnhZdmZ2alY2OWZPMFpqUm9aZnlsNU8vYlh5bC9l
ckE2eG12MjhiQ3hoNit5WGd6TVY3MFZ2dnR3WGZjZHgzdm85OFBUK1I4SUg4by8yajVzZlZUMEtm
N2t4bVRrLzhFQTVqei9HTXpMZHNBQUFBZ1kwaFNUUUFBZWlVQUFJQ0RBQUQ1L3dBQWdPa0FBSFV3
QUFEcVlBQUFPcGdBQUJkdmtsL0ZSZ0FBQUJKSlJFRlVlTnBpK1A5Z0V3QUFBUC8vQXdBRmN3S1Mz
ZDdCbndBQUFBQkpSVTVFcmtKZ2dnPT0pIWltcG9ydGFudDt9IC5HSU5HRVJfU09GVFdBUkVfY29u
dHJvbCAuR0lOR0VSX1NPRlRXQVJFX2NvcnJlY3QuR0lOR0VSX1NPRlRXQVJFX25vU3VnZ2VzdGlv
biwgLkdJTkdFUl9TT0ZUV0FSRV9jb250cm9sIC5HSU5HRVJfU09GVFdBUkVfU3BlbGxpbmdDb3Jy
ZWN0LkdJTkdFUl9TT0ZUV0FSRV9ub1N1Z2dlc3Rpb24sIC5HSU5HRVJfU09GVFdBUkVfY29udHJv
bCAuR0lOR0VSX1NPRlRXQVJFX3NwZWxsaW5nLkdJTkdFUl9TT0ZUV0FSRV9ub1N1Z2dlc3Rpb24s
IC5HSU5HRVJfU09GVFdBUkVfY29udHJvbCAuR0lOR0VSX1NPRlRXQVJFX21hcmsuR0lOR0VSX1NP
RlRXQVJFX25vU3VnZ2VzdGlvbiB7YmFja2dyb3VuZC1pbWFnZTp1cmwoZGF0YTppbWFnZS9naWY7
YmFzZTY0LGlWQk9SdzBLR2dvQUFBQU5TVWhFVWdBQUFBRUFBQUFCQ0FJQUFBQ1FkMVBlQUFBQUdY
UkZXSFJUYjJaMGQyRnlaUUJCWkc5aVpTQkpiV0ZuWlZKbFlXUjVjY2xsUEFBQUF5QnBWRmgwV0Ux
TU9tTnZiUzVoWkc5aVpTNTRiWEFBQUFBQUFEdy9lSEJoWTJ0bGRDQmlaV2RwYmowaTc3dS9JaUJw
WkQwaVZ6Vk5NRTF3UTJWb2FVaDZjbVZUZWs1VVkzcHJZemxrSWo4K0lEeDRPbmh0Y0cxbGRHRWdl
RzFzYm5NNmVEMGlZV1J2WW1VNmJuTTZiV1YwWVM4aUlIZzZlRzF3ZEdzOUlrRmtiMkpsSUZoTlVD
QkRiM0psSURVdU1DMWpNRFl3SURZeExqRXpORGMzTnl3Z01qQXhNQzh3TWk4eE1pMHhOem96TWpv
d01DQWdJQ0FnSUNBZ0lqNGdQSEprWmpwU1JFWWdlRzFzYm5NNmNtUm1QU0pvZEhSd09pOHZkM2Qz
TG5jekxtOXlaeTh4T1RrNUx6QXlMekl5TFhKa1ppMXplVzUwWVhndGJuTWpJajRnUEhKa1pqcEVa
WE5qY21sd2RHbHZiaUJ5WkdZNllXSnZkWFE5SWlJZ2VHMXNibk02ZUcxd1BTSm9kSFJ3T2k4dmJu
TXVZV1J2WW1VdVkyOXRMM2hoY0M4eExqQXZJaUI0Yld4dWN6cDRiWEJOVFQwaWFIUjBjRG92TDI1
ekxtRmtiMkpsTG1OdmJTOTRZWEF2TVM0d0wyMXRMeUlnZUcxc2JuTTZjM1JTWldZOUltaDBkSEE2
THk5dWN5NWhaRzlpWlM1amIyMHZlR0Z3THpFdU1DOXpWSGx3WlM5U1pYTnZkWEpqWlZKbFppTWlJ
SGh0Y0RwRGNtVmhkRzl5Vkc5dmJEMGlRV1J2WW1VZ1VHaHZkRzl6YUc5d0lFTlROU0JYYVc1a2Iz
ZHpJaUI0YlhCTlRUcEpibk4wWVc1alpVbEVQU0o0YlhBdWFXbGtPamhGUTBZMk9FTkdNekU1T1RF
eFJUSTROak14T1RFeE5UVXlNRGhFTURNd0lpQjRiWEJOVFRwRWIyTjFiV1Z1ZEVsRVBTSjRiWEF1
Wkdsa09qaEZRMFkyT0VRd016RTVPVEV4UlRJNE5qTXhPVEV4TlRVeU1EaEVNRE13SWo0Z1BIaHRj
RTFOT2tSbGNtbDJaV1JHY205dElITjBVbVZtT21sdWMzUmhibU5sU1VROUluaHRjQzVwYVdRNk9F
VkRSalk0UTBRek1UazVNVEZGTWpnMk16RTVNVEUxTlRJd09FUXdNekFpSUhOMFVtVm1PbVJ2WTNW
dFpXNTBTVVE5SW5odGNDNWthV1E2T0VWRFJqWTRRMFV6TVRrNU1URkZNamcyTXpFNU1URTFOVEl3
T0VRd016QWlMejRnUEM5eVpHWTZSR1Z6WTNKcGNIUnBiMjQrSUR3dmNtUm1PbEpFUmo0Z1BDOTRP
bmh0Y0cxbGRHRStJRHcvZUhCaFkydGxkQ0JsYm1ROUluSWlQejVSUnhSeEFBQUFEMGxFUVZSNDJt
SzQ4K3c3UUlBQkFBVmJBcm9vd04wOEFBQUFBRWxGVGtTdVFtQ0MpIWltcG9ydGFudDt9IC5HSU5H
RVJfU09GVFdBUkVfcmljaFRleHQgLkdJTkdFUl9TT0ZUV0FSRV9jb3JyZWN0LCAuR0lOR0VSX1NP
RlRXQVJFX3JpY2hUZXh0IC5HSU5HRVJfU09GVFdBUkVfU3BlbGxpbmdDb3JyZWN0LCAuR0lOR0VS
X1NPRlRXQVJFX3JpY2hUZXh0IC5HSU5HRVJfU09GVFdBUkVfc3BlbGxpbmcsIC5HSU5HRVJfU09G
VFdBUkVfcmljaFRleHQgLkdJTkdFUl9TT0ZUV0FSRV9tYXJrIHtwb3NpdGlvbjpyZWxhdGl2ZTsg
YmFja2dyb3VuZC1pbWFnZTpub25lIWltcG9ydGFudDt9IC5HSU5HRVJfU09GVFdBUkVfcmljaFRl
eHQgLkdJTkdFUl9TT0ZUV0FSRV9tYXJrSGlnaGxpZ2h0TGVmdCB7IHBvc2l0aW9uIDogYWJzb2x1
dGU7IGxlZnQ6LTJweDsgdG9wOjBweDsgYm90dG9tOjBweDsgd2lkdGg6MnB4O30gLkdJTkdFUl9T
T0ZUV0FSRV9yaWNoVGV4dCAuR0lOR0VSX1NPRlRXQVJFX21hcmtIaWdobGlnaHRSaWdodCB7IHBv
c2l0aW9uIDogYWJzb2x1dGU7IHJpZ2h0Oi0ycHg7IHRvcDowcHg7IGJvdHRvbTowcHg7IHdpZHRo
OjJweDt9IC5HSU5HRVJfU09GVFdBUkVfcmljaFRleHQgLkdJTkdFUl9TT0ZUV0FSRV9tYXJrSGln
aGxpZ2h0VG9wIHsgcG9zaXRpb24gOiBhYnNvbHV0ZTsgbGVmdDowcHg7IHJpZ2h0OjBweDsgdG9w
Oi0ycHg7IGhlaWdodDozcHg7fSAuR0lOR0VSX1NPRlRXQVJFX3JpY2hUZXh0IC5HSU5HRVJfU09G
VFdBUkVfbWFya0hpZ2hsaWdodEJvdHRvbSB7IHBvc2l0aW9uIDogYWJzb2x1dGU7IGxlZnQ6MHB4
OyByaWdodDowcHg7IGJvdHRvbTotMnB4OyBoZWlnaHQ6M3B4O308L3N0eWxlPjwvaGVhZD4gCjxi
b2R5IGdpbmdlcl9zb2Z0d2FyZV9zdHlsZXNoZWV0PSJ0cnVlIiBnaW5nZXJfc29mdHdhcmVfZG9j
PSJ0cnVlIj4gCiAgPHRhYmxlIGJvcmRlcj0iMCIgY2VsbHBhZGRpbmc9IjAiIGNlbGxzcGFjaW5n
PSIwIj4gCiAgPHRib2R5Pjx0ciBpZD0icGFydC0xIiBiZ2NvbG9yPSJvcmFuZ2UiPjx0aD48L3Ro
Pjx0aD48YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1p
ZXRmLXBjZS1wY2Vwcy0xNC50eHQiIHN0eWxlPSJjb2xvcjojMDA4OyB0ZXh0LWRlY29yYXRpb246
bm9uZTsiPiZsdDs8L2E+Jm5ic3A7PGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1s
L2RyYWZ0LWlldGYtcGNlLXBjZXBzLTE0LnR4dCIgc3R5bGU9ImNvbG9yOiMwMDgiPmRyYWZ0LWll
dGYtcGNlLXBjZXBzLTE0LnR4dDwvYT4mbmJzcDs8L3RoPjx0aD4gPC90aD48dGg+Jm5ic3A7PGEg
aHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtcGNlLXBjZXBzLTE1
LnR4dCIgc3R5bGU9ImNvbG9yOiMwMDgiPmRyYWZ0LWlldGYtcGNlLXBjZXBzLTE1LnR4dDwvYT4m
bmJzcDs8YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL3JmY2RpZmY/dXJsMT1kcmFmdC1p
ZXRmLXBjZS1wY2Vwcy0xNS50eHQiIHN0eWxlPSJjb2xvcjojMDA4OyB0ZXh0LWRlY29yYXRpb246
bm9uZTsiPiZndDs8L2E+PC90aD48dGg+PC90aD48L3RyPiAKICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij5QQ0UgV29ya2luZyBHcm91cCAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgRC4gTG9wZXo8L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij5QQ0UgV29ya2luZyBHcm91cCAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgRC4gTG9wZXo8L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQg
Y2xhc3M9ImxlZnQiPkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgTy4gR29uemFsZXogZGUgRGlvczwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
Ty4gR29uemFsZXogZGUgRGlvczwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+VXBkYXRlczog
NTQ0MCAoaWYgYXBwcm92ZWQpICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFRlbGVmb25p
Y2EgSStEPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+VXBkYXRlczogNTQ0MCAoaWYg
YXBwcm92ZWQpICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFRlbGVmb25pY2EgSStEPC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij5JbnRlbmRlZCBzdGF0dXM6IFN0YW5kYXJkcyBUcmFj
ayAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgUS4gV3U8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij5JbnRlbmRlZCBzdGF0dXM6IFN0YW5kYXJkcyBUcmFjayAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgUS4gV3U8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMDEiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+RXhwaXJlczogPHNw
YW4gY2xhc3M9ImRlbGV0ZSI+Tm92ZW1iZXIgMjMsIDIwMTc8L3NwYW4+ICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICBELiBEaG9keTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmJsb2NrIj5FeHBpcmVzOiA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5KYW51YXJ5IDI5LCAyMDE4IDwv
c3Bhbj4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIEQuIERob2R5PC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBIdWF3ZWk8L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICBIdWF3ZWk8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMDIiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICA8c3BhbiBjbGFzcz0i
ZGVsZXRlIj4gTWF5IDIyPC9zcGFuPiwgMjAxNzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJs
b2NrIj4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIDxzcGFuIGNsYXNzPSJpbnNlcnQiPkp1bHkgMjg8L3NwYW4+LCAyMDE3PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICAgICAgICAgU2VjdXJlIFRy
YW5zcG9ydCBmb3IgUENFUDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAg
ICAgICAgICAgICAgICAgU2VjdXJlIFRyYW5zcG9ydCBmb3IgUENFUDwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJkaWZmMDAwMyI+PHRkPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAg
ICAgICAgICAgICAgICAgICAgICBkcmFmdC1pZXRmLXBjZS1wY2Vwcy0xPHNwYW4gY2xhc3M9ImRl
bGV0ZSI+NDwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgICAgICAg
ICAgICAgICAgICAgICAgZHJhZnQtaWV0Zi1wY2UtcGNlcHMtMTxzcGFuIGNsYXNzPSJpbnNlcnQi
PjU8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPkFic3RyYWN0PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+QWJzdHJhY3Q8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+ICAgVGhlIFBhdGggQ29tcHV0YXRpb24gRWxlbWVudCBDb21tdW5pY2F0aW9u
IFByb3RvY29sIChQQ0VQKSBkZWZpbmVzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
ICAgVGhlIFBhdGggQ29tcHV0YXRpb24gRWxlbWVudCBDb21tdW5pY2F0aW9uIFByb3RvY29sIChQ
Q0VQKSBkZWZpbmVzPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICB0aGUgbWVjaGFuaXNt
cyBmb3IgdGhlIGNvbW11bmljYXRpb24gYmV0d2VlbiBhIFBhdGggQ29tcHV0YXRpb248L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICB0aGUgbWVjaGFuaXNtcyBmb3IgdGhlIGNvbW11
bmljYXRpb24gYmV0d2VlbiBhIFBhdGggQ29tcHV0YXRpb248L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgIENsaWVudCAoUENDKSBhbmQgYSBQYXRoIENvbXB1dGF0aW9uIEVsZW1lbnQgKFBD
RSksIG9yIGFtb25nIFBDRXMuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgQ2xp
ZW50IChQQ0MpIGFuZCBhIFBhdGggQ29tcHV0YXRpb24gRWxlbWVudCAoUENFKSwgb3IgYW1vbmcg
UENFcy48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRoaXMgZG9jdW1lbnQgZGVzY3Jp
YmUgdGhlIHVzYWdlIG9mIFRyYW5zcG9ydCBMYXllciBTZWN1cml0eSAoVExTKSB0bzwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFRoaXMgZG9jdW1lbnQgZGVzY3JpYmUgdGhlIHVz
YWdlIG9mIFRyYW5zcG9ydCBMYXllciBTZWN1cml0eSAoVExTKSB0bzwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+ICAgZW5oYW5jZSBQQ0VQIHNlY3VyaXR5LCBoZW5jZSB0aGUgUENFUFMgYWNy
b255bSBwcm9wb3NlZCBmb3IgaXQuICBUaGU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICBlbmhhbmNlIFBDRVAgc2VjdXJpdHksIGhlbmNlIHRoZSBQQ0VQUyBhY3JvbnltIHByb3Bv
c2VkIGZvciBpdC4gIFRoZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgYWRkaXRpb25h
bCBzZWN1cml0eSBtZWNoYW5pc21zIGFyZSBwcm92aWRlZCBieSB0aGUgdHJhbnNwb3J0IHByb3Rv
Y29sPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgYWRkaXRpb25hbCBzZWN1cml0
eSBtZWNoYW5pc21zIGFyZSBwcm92aWRlZCBieSB0aGUgdHJhbnNwb3J0IHByb3RvY29sPC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBzdXBwb3J0aW5nIFBDRVAsIGFuZCB0aGVyZWZvcmUg
dGhleSBkbyBub3QgYWZmZWN0IHRoZSBmbGV4aWJpbGl0eSBhbmQ8L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4gICBzdXBwb3J0aW5nIFBDRVAsIGFuZCB0aGVyZWZvcmUgdGhleSBkbyBu
b3QgYWZmZWN0IHRoZSBmbGV4aWJpbGl0eSBhbmQ8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJwYXJ0LTIiIGNsYXNzPSJjaGFuZ2UiPjx0ZD48L3Rk
Pjx0aD48c21hbGw+c2tpcHBpbmcgdG8gY2hhbmdlIGF0PC9zbWFsbD48YSBocmVmPSJodHRwczov
L3Rvb2xzLmlldGYub3JnL3JmY2RpZmYjcGFydC0yIj48ZW0+IHBhZ2UgMSwgbGluZSA0MzxzcGFu
IGNsYXNzPSJoaWRlIj4gwrY8L3NwYW4+PC9lbT48L2E+PC90aD48dGg+IDwvdGg+PHRoPjxzbWFs
bD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0
Zi5vcmcvcmZjZGlmZiNwYXJ0LTIiPjxlbT4gcGFnZSAxLCBsaW5lIDQzPHNwYW4gY2xhc3M9Imhp
ZGUiPiDCtjwvc3Bhbj48L2VtPjwvYT48L3RoPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIEludGVybmV0LURyYWZ0cyBh
cmUgd29ya2luZyBkb2N1bWVudHMgb2YgdGhlIEludGVybmV0IEVuZ2luZWVyaW5nPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgSW50ZXJuZXQtRHJhZnRzIGFyZSB3b3JraW5nIGRv
Y3VtZW50cyBvZiB0aGUgSW50ZXJuZXQgRW5naW5lZXJpbmc8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgIFRhc2sgRm9yY2UgKElFVEYpLiAgTm90ZSB0aGF0IG90aGVyIGdyb3VwcyBtYXkg
YWxzbyBkaXN0cmlidXRlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgVGFzayBG
b3JjZSAoSUVURikuICBOb3RlIHRoYXQgb3RoZXIgZ3JvdXBzIG1heSBhbHNvIGRpc3RyaWJ1dGU8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHdvcmtpbmcgZG9jdW1lbnRzIGFzIEludGVy
bmV0LURyYWZ0cy4gIFRoZSBsaXN0IG9mIGN1cnJlbnQgSW50ZXJuZXQtPC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+ICAgd29ya2luZyBkb2N1bWVudHMgYXMgSW50ZXJuZXQtRHJhZnRz
LiAgVGhlIGxpc3Qgb2YgY3VycmVudCBJbnRlcm5ldC08L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgIERyYWZ0cyBpcyBhdCBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZHJhZnRzL2N1
cnJlbnQvLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIERyYWZ0cyBpcyBhdCBo
dHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZHJhZnRzL2N1cnJlbnQvLjwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBJbnRlcm5ldC1EcmFmdHMgYXJlIGRyYWZ0IGRvY3VtZW50
cyB2YWxpZCBmb3IgYSBtYXhpbXVtIG9mIHNpeCBtb250aHM8L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICBJbnRlcm5ldC1EcmFmdHMgYXJlIGRyYWZ0IGRvY3VtZW50cyB2YWxpZCBm
b3IgYSBtYXhpbXVtIG9mIHNpeCBtb250aHM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
IGFuZCBtYXkgYmUgdXBkYXRlZCwgcmVwbGFjZWQsIG9yIG9ic29sZXRlZCBieSBvdGhlciBkb2N1
bWVudHMgYXQgYW55PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgYW5kIG1heSBi
ZSB1cGRhdGVkLCByZXBsYWNlZCwgb3Igb2Jzb2xldGVkIGJ5IG90aGVyIGRvY3VtZW50cyBhdCBh
bnk8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHRpbWUuICBJdCBpcyBpbmFwcHJvcHJp
YXRlIHRvIHVzZSBJbnRlcm5ldC1EcmFmdHMgYXMgcmVmZXJlbmNlPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgdGltZS4gIEl0IGlzIGluYXBwcm9wcmlhdGUgdG8gdXNlIEludGVy
bmV0LURyYWZ0cyBhcyByZWZlcmVuY2U8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIG1h
dGVyaWFsIG9yIHRvIGNpdGUgdGhlbSBvdGhlciB0aGFuIGFzICJ3b3JrIGluIHByb2dyZXNzLiI8
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBtYXRlcmlhbCBvciB0byBjaXRlIHRo
ZW0gb3RoZXIgdGhhbiBhcyAid29yayBpbiBwcm9ncmVzcy4iPC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMDQiPjx0ZD48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAg
VGhpcyBJbnRlcm5ldC1EcmFmdCB3aWxsIGV4cGlyZSBvbiA8c3BhbiBjbGFzcz0iZGVsZXRlIj5O
b3ZlbWJlciAyMywgMjAxNzwvc3Bhbj4uPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2si
PiAgIFRoaXMgSW50ZXJuZXQtRHJhZnQgd2lsbCBleHBpcmUgb24gPHNwYW4gY2xhc3M9Imluc2Vy
dCI+SmFudWFyeSAyOSwgMjAxODwvc3Bhbj4uPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPkNvcHlyaWdodCBOb3RpY2U8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij5Db3B5
cmlnaHQgTm90aWNlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIENvcHlyaWdo
dCAoYykgMjAxNyBJRVRGIFRydXN0IGFuZCB0aGUgcGVyc29ucyBpZGVudGlmaWVkIGFzIHRoZTwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIENvcHlyaWdodCAoYykgMjAxNyBJRVRG
IFRydXN0IGFuZCB0aGUgcGVyc29ucyBpZGVudGlmaWVkIGFzIHRoZTwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+ICAgZG9jdW1lbnQgYXV0aG9ycy4gIEFsbCByaWdodHMgcmVzZXJ2ZWQuPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgZG9jdW1lbnQgYXV0aG9ycy4gIEFsbCBy
aWdodHMgcmVzZXJ2ZWQuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRoaXMg
ZG9jdW1lbnQgaXMgc3ViamVjdCB0byBCQ1AgNzggYW5kIHRoZSBJRVRGIFRydXN0J3MgTGVnYWw8
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBUaGlzIGRvY3VtZW50IGlzIHN1Ympl
Y3QgdG8gQkNQIDc4IGFuZCB0aGUgSUVURiBUcnVzdCdzIExlZ2FsPC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij4gICBQcm92aXNpb25zIFJlbGF0aW5nIHRvIElFVEYgRG9jdW1lbnRzPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgUHJvdmlzaW9ucyBSZWxhdGluZyB0byBJRVRG
IERvY3VtZW50czwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgKGh0dHA6Ly90cnVzdGVl
LmlldGYub3JnL2xpY2Vuc2UtaW5mbykgaW4gZWZmZWN0IG9uIHRoZSBkYXRlIG9mPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgKGh0dHA6Ly90cnVzdGVlLmlldGYub3JnL2xpY2Vu
c2UtaW5mbykgaW4gZWZmZWN0IG9uIHRoZSBkYXRlIG9mPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij4gICBwdWJsaWNhdGlvbiBvZiB0aGlzIGRvY3VtZW50LiAgUGxlYXNlIHJldmlldyB0aGVz
ZSBkb2N1bWVudHM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBwdWJsaWNhdGlv
biBvZiB0aGlzIGRvY3VtZW50LiAgUGxlYXNlIHJldmlldyB0aGVzZSBkb2N1bWVudHM8L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJwYXJ0LTMiIGNs
YXNzPSJjaGFuZ2UiPjx0ZD48L3RkPjx0aD48c21hbGw+c2tpcHBpbmcgdG8gY2hhbmdlIGF0PC9z
bWFsbD48YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL3JmY2RpZmYjcGFydC0zIj48ZW0+
IHBhZ2UgMiwgbGluZSAzODxzcGFuIGNsYXNzPSJoaWRlIj4gwrY8L3NwYW4+PC9lbT48L2E+PC90
aD48dGg+IDwvdGg+PHRoPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxhIGhy
ZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvcmZjZGlmZiNwYXJ0LTMiPjxlbT4gcGFnZSAyLCBs
aW5lIDM4PHNwYW4gY2xhc3M9ImhpZGUiPiDCtjwvc3Bhbj48L2VtPjwvYT48L3RoPjx0ZD48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+ICAgMS4gIEludHJvZHVjdGlvbiAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gICAzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAg
MS4gIEludHJvZHVjdGlvbiAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gICAzPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAyLiAgUmVxdWlyZW1l
bnRzIExhbmd1YWdlIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDQ8
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAyLiAgUmVxdWlyZW1lbnRzIExhbmd1
YWdlIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDQ8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgIDMuICBBcHBseWluZyBQQ0VQUyAgLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgNDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgIDMuICBBcHBseWluZyBQQ0VQUyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgNDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
ICAzLjEuICBPdmVydmlldyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gICA0PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAzLjEuICBP
dmVydmlldyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
ICA0PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgIDMuMi4gIEluaXRpYXRpbmcgdGhl
IFRMUyBQcm9jZWR1cmVzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDQ8L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgIDMuMi4gIEluaXRpYXRpbmcgdGhlIFRMUyBQcm9j
ZWR1cmVzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDQ8L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPiAgICAgMy4zLiAgVGhlIFN0YXJ0VExTIE1lc3NhZ2UgIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgNjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgICAgMy4zLiAgVGhlIFN0YXJ0VExTIE1lc3NhZ2UgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuICAgNjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAzLjQuICBU
TFMgQ29ubmVjdGlvbiBFc3RhYmxpc2htZW50ICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
ICA4PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAzLjQuICBUTFMgQ29ubmVj
dGlvbiBFc3RhYmxpc2htZW50ICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gICA4PC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgIDMuNS4gIFBlZXIgSWRlbnRpdHkgLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTA8L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4gICAgIDMuNS4gIFBlZXIgSWRlbnRpdHkgLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTA8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PiAgICAgMy42LiAgQ29ubmVjdGlvbiBFc3RhYmxpc2htZW50IEZhaWx1cmUgIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuICAxMTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgMy42
LiAgQ29ubmVjdGlvbiBFc3RhYmxpc2htZW50IEZhaWx1cmUgIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuICAxMTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJk
aWZmMDAwNSI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGJsb2NrIj4gICA0LiAgRGlzY292ZXJ5IE1lY2hhbmlzbXMgIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTxzcGFuIGNsYXNzPSJkZWxldGUiPjE8
L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIDQuICBEaXNjb3Zlcnkg
TWVjaGFuaXNtcyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxPHNw
YW4gY2xhc3M9Imluc2VydCI+Mjwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
ICAgNC4xLiAgREFORSBBcHBsaWNhYmlsaXR5ICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuICAxMjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgNC4xLiAg
REFORSBBcHBsaWNhYmlsaXR5ICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
ICAxMjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgNS4gIEJhY2t3YXJkIENvbXBhdGli
aWxpdHkgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDEyPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgNS4gIEJhY2t3YXJkIENvbXBhdGliaWxpdHkgIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDEyPC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9ImRpZmYwMDA2Ij48dGQ+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIDYu
ICBJQU5BIENvbnNpZGVyYXRpb25zIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuICA8c3BhbiBjbGFzcz0iZGVsZXRlIj4xMjwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJibG9jayI+ICAgNi4gIElBTkEgQ29uc2lkZXJhdGlvbnMgLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDxzcGFuIGNsYXNzPSJpbnNlcnQiPjEzPC9zcGFu
PjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAgIDYuMS4gIE5ldyBQQ0VQIE1lc3Nh
Z2UgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgPHNwYW4gY2xhc3M9
ImRlbGV0ZSI+MTI8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgICAg
Ni4xLiAgTmV3IFBDRVAgTWVzc2FnZSAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuICA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij4xMzwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPiAgICAgNi4yLiAgTmV3IEVycm9yLVZhbHVlcyAgLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxMzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgICAgNi4yLiAgTmV3IEVycm9yLVZhbHVlcyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuICAxMzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyIGlkPSJkaWZmMDAwNyI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICA3LiAgU2VjdXJpdHkgQ29uc2lkZXJhdGlv
bnMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgPHNwYW4gY2xhc3M9ImRl
bGV0ZSI+MTM8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIDcuICBT
ZWN1cml0eSBDb25zaWRlcmF0aW9ucyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuICA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij4xNDwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxibG9jayI+ICAgOC4gIE1hbmFnZWFiaWxpdHkgQ29uc2lkZXJhdGlvbnMgIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gIDxzcGFuIGNsYXNzPSJkZWxldGUiPjE0PC9zcGFuPjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICA4LiAgTWFuYWdlYWJpbGl0eSBDb25zaWRl
cmF0aW9ucyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgPHNwYW4gY2xhc3M9Imlu
c2VydCI+MTU8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgICAgOC4xLiAg
Q29udHJvbCBvZiBGdW5jdGlvbiBhbmQgUG9saWN5ICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
ICA8c3BhbiBjbGFzcz0iZGVsZXRlIj4xNDwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJibG9jayI+ICAgICA4LjEuICBDb250cm9sIG9mIEZ1bmN0aW9uIGFuZCBQb2xpY3kgIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gIDxzcGFuIGNsYXNzPSJpbnNlcnQiPjE1PC9zcGFuPjwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAgIDguMi4gIEluZm9ybWF0aW9uIGFuZCBEYXRh
IE1vZGVscyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgPHNwYW4gY2xhc3M9ImRlbGV0
ZSI+MTU8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgICAgOC4yLiAg
SW5mb3JtYXRpb24gYW5kIERhdGEgTW9kZWxzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
ICA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij4xNjwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxi
bG9jayI+ICAgICA4LjMuICBMaXZlbmVzcyBEZXRlY3Rpb24gYW5kIE1vbml0b3JpbmcgLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gIDxzcGFuIGNsYXNzPSJkZWxldGUiPjE1PC9zcGFuPjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAgIDguMy4gIExpdmVuZXNzIERldGVjdGlvbiBh
bmQgTW9uaXRvcmluZyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgPHNwYW4gY2xhc3M9Imluc2Vy
dCI+MTY8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgICAgOC40LiAgPHNw
YW4gY2xhc3M9ImRlbGV0ZSI+VmVyaWZ5PC9zcGFuPiBDb3JyZWN0IE9wZXJhdGlvbnMgLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIDxzcGFuIGNsYXNzPSJkZWxldGUiPi4gLiAgMTU8L3NwYW4+
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgICAgOC40LiAgPHNwYW4gY2xhc3M9
Imluc2VydCI+VmVyaWZ5aW5nPC9zcGFuPiBDb3JyZWN0IE9wZXJhdGlvbnMgIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAgPHNwYW4gY2xhc3M9Imluc2VydCI+MTY8L3NwYW4+PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgICAgOC41LiAgUmVxdWlyZW1lbnRzIG9uIE90aGVyIFBy
b3RvY29scyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA8c3BhbiBjbGFzcz0iZGVsZXRlIj4x
NTwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgICA4LjUuICBSZXF1
aXJlbWVudHMgb24gT3RoZXIgUHJvdG9jb2xzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDxz
cGFuIGNsYXNzPSJpbnNlcnQiPjE2PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgICA4LjYuICBJbXBhY3Qgb24gTmV0d29yayBPcGVyYXRpb24gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gIDE2PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICA4LjYu
ICBJbXBhY3Qgb24gTmV0d29yayBPcGVyYXRpb24gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gIDE2PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICA5LiAgQWNrbm93bGVkZ2VtZW50
cyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTY8L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICA5LiAgQWNrbm93bGVkZ2VtZW50cyAgLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTY8L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMDgiPjx0ZD48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAg
MTAuIFJlZmVyZW5jZXMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gIDxzcGFuIGNsYXNzPSJkZWxldGUiPjE2PC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmJsb2NrIj4gICAxMC4gUmVmZXJlbmNlcyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgPHNwYW4gY2xhc3M9Imluc2VydCI+MTc8L3Nw
YW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgICAgMTAuMS4gIE5vcm1hdGl2ZSBS
ZWZlcmVuY2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA8c3BhbiBjbGFz
cz0iZGVsZXRlIj4xNjwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAg
ICAxMC4xLiAgTm9ybWF0aXZlIFJlZmVyZW5jZXMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gIDxzcGFuIGNsYXNzPSJpbnNlcnQiPjE3PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGJsb2NrIj4gICAgIDEwLjIuICBJbmZvcm1hdGl2ZSBSZWZlcmVuY2VzIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+MTc8L3NwYW4+
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgICAgMTAuMi4gIEluZm9ybWF0aXZl
IFJlZmVyZW5jZXMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA8c3BhbiBjbGFz
cz0iaW5zZXJ0Ij4xODwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgQXV0
aG9ycycgQWRkcmVzc2VzICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gIDxzcGFuIGNsYXNzPSJkZWxldGUiPjE4PC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmJsb2NrIj4gICBBdXRob3JzJyBBZGRyZXNzZXMgIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgPHNwYW4gY2xhc3M9Imluc2VydCI+MjA8L3NwYW4+
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjEuICBJbnRyb2R1Y3Rpb248L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4xLiAgSW50cm9kdWN0aW9uPC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRoZSBQYXRoIENvbXB1dGF0aW9uIEVsZW1lbnQgQ29tbXVu
aWNhdGlvbiBQcm90b2NvbCAoUENFUCkgW1JGQzU0NDBdPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgVGhlIFBhdGggQ29tcHV0YXRpb24gRWxlbWVudCBDb21tdW5pY2F0aW9uIFBy
b3RvY29sIChQQ0VQKSBbUkZDNTQ0MF08L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGRl
ZmluZXMgdGhlIG1lY2hhbmlzbXMgZm9yIHRoZSBjb21tdW5pY2F0aW9uIGJldHdlZW4gYSBQYXRo
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgZGVmaW5lcyB0aGUgbWVjaGFuaXNt
cyBmb3IgdGhlIGNvbW11bmljYXRpb24gYmV0d2VlbiBhIFBhdGg8L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPiAgIENvbXB1dGF0aW9uIENsaWVudCAoUENDKSBhbmQgYSBQYXRoIENvbXB1dGF0
aW9uIEVsZW1lbnQgKFBDRSksIG9yPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAg
Q29tcHV0YXRpb24gQ2xpZW50IChQQ0MpIGFuZCBhIFBhdGggQ29tcHV0YXRpb24gRWxlbWVudCAo
UENFKSwgb3I8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGJldHdlZW4gdHdvIFBDRXMu
ICBUaGVzZSBpbnRlcmFjdGlvbnMgaW5jbHVkZSByZXF1ZXN0cyBhbmQgcmVwbGllczwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGJldHdlZW4gdHdvIFBDRXMuICBUaGVzZSBpbnRl
cmFjdGlvbnMgaW5jbHVkZSByZXF1ZXN0cyBhbmQgcmVwbGllczwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGVmdCI+ICAgdGhhdCBjYW4gYmUgY3JpdGljYWwgZm9yIGEgc3VzdGFpbmFibGUgbmV0d29y
ayBvcGVyYXRpb24gYW5kIGFkZXF1YXRlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
ICAgdGhhdCBjYW4gYmUgY3JpdGljYWwgZm9yIGEgc3VzdGFpbmFibGUgbmV0d29yayBvcGVyYXRp
b24gYW5kIGFkZXF1YXRlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICByZXNvdXJjZSBh
bGxvY2F0aW9uLCBhbmQgdGhlcmVmb3JlIGFwcHJvcHJpYXRlIHNlY3VyaXR5IGJlY29tZXMgYSBr
ZXk8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICByZXNvdXJjZSBhbGxvY2F0aW9u
LCBhbmQgdGhlcmVmb3JlIGFwcHJvcHJpYXRlIHNlY3VyaXR5IGJlY29tZXMgYSBrZXk8L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGVsZW1lbnQgaW4gdGhlIFBDRSBpbmZyYXN0cnVjdHVy
ZS4gIEFzIHRoZSBhcHBsaWNhdGlvbnMgb2YgdGhlIFBDRTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgIGVsZW1lbnQgaW4gdGhlIFBDRSBpbmZyYXN0cnVjdHVyZS4gIEFzIHRoZSBh
cHBsaWNhdGlvbnMgb2YgdGhlIFBDRTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHIgaWQ9InBhcnQtNCIgY2xhc3M9ImNoYW5nZSI+PHRkPjwvdGQ+PHRoPjxz
bWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxhIGhyZWY9Imh0dHBzOi8vdG9vbHMu
aWV0Zi5vcmcvcmZjZGlmZiNwYXJ0LTQiPjxlbT4gcGFnZSAzLCBsaW5lIDQwPHNwYW4gY2xhc3M9
ImhpZGUiPiDCtjwvc3Bhbj48L2VtPjwvYT48L3RoPjx0aD4gPC90aD48dGg+PHNtYWxsPnNraXBw
aW5nIHRvIGNoYW5nZSBhdDwvc21hbGw+PGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9y
ZmNkaWZmI3BhcnQtNCI+PGVtPiBwYWdlIDMsIGxpbmUgNDA8c3BhbiBjbGFzcz0iaGlkZSI+IMK2
PC9zcGFuPjwvZW0+PC9hPjwvdGg+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBBbW9uZyB0aGUgcG9zc2libGUg
c29sdXRpb25zIG1lbnRpb25lZCBpbiB0aGVzZSBkb2N1bWVudHMsIFRyYW5zcG9ydDwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIEFtb25nIHRoZSBwb3NzaWJsZSBzb2x1dGlvbnMg
bWVudGlvbmVkIGluIHRoZXNlIGRvY3VtZW50cywgVHJhbnNwb3J0PC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij4gICBMYXllciBTZWN1cml0eSAoVExTKSBbUkZDNTI0Nl0gcHJvdmlkZXMgc3Vw
cG9ydCBmb3IgcGVlcjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIExheWVyIFNl
Y3VyaXR5IChUTFMpIFtSRkM1MjQ2XSBwcm92aWRlcyBzdXBwb3J0IGZvciBwZWVyPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBhdXRoZW50aWNhdGlvbiwgYW5kIG1lc3NhZ2UgZW5jcnlw
dGlvbiBhbmQgaW50ZWdyaXR5LiAgVExTIHN1cHBvcnRzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgYXV0aGVudGljYXRpb24sIGFuZCBtZXNzYWdlIGVuY3J5cHRpb24gYW5kIGlu
dGVncml0eS4gIFRMUyBzdXBwb3J0czwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgdGhl
IHVzYWdlIG9mIHdlbGwta25vd24gbWVjaGFuaXNtcyB0byBzdXBwb3J0IGtleSBjb25maWd1cmF0
aW9uIGFuZDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHRoZSB1c2FnZSBvZiB3
ZWxsLWtub3duIG1lY2hhbmlzbXMgdG8gc3VwcG9ydCBrZXkgY29uZmlndXJhdGlvbiBhbmQ8L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGV4Y2hhbmdlLCBhbmQgbWVhbnMgdG8gcGVyZm9y
bSBzZWN1cml0eSBjaGVja3Mgb24gdGhlIHJlc3VsdHMgb2YgUENFPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgZXhjaGFuZ2UsIGFuZCBtZWFucyB0byBwZXJmb3JtIHNlY3VyaXR5
IGNoZWNrcyBvbiB0aGUgcmVzdWx0cyBvZiBQQ0U8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PiAgIGRpc2NvdmVyeSBwcm9jZWR1cmVzIHZpYSBJbnRlcmlvciBHYXRld2F5IFByb3RvY29sIChJ
R1ApIChbUkZDNTA4OF08L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBkaXNjb3Zl
cnkgcHJvY2VkdXJlcyB2aWEgSW50ZXJpb3IgR2F0ZXdheSBQcm90b2NvbCAoSUdQKSAoW1JGQzUw
ODhdPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBhbmQgW1JGQzUwODldKS48L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBhbmQgW1JGQzUwODldKS48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgVGhpcyBkb2N1bWVudCBkZXNjcmliZXMgYSBzZWN1cml0
eSBjb250YWluZXIgZm9yIHRoZSB0cmFuc3BvcnQgb2Y8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICBUaGlzIGRvY3VtZW50IGRlc2NyaWJlcyBhIHNlY3VyaXR5IGNvbnRhaW5lciBm
b3IgdGhlIHRyYW5zcG9ydCBvZjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyIGlkPSJkaWZmMDAwOSI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBQQ0VQIG1lc3NhZ2VzLCBhbmQgdGhl
cmVmb3JlIDxzcGFuIGNsYXNzPSJkZWxldGUiPnRoZXkgZG88L3NwYW4+IG5vdCBhZmZlY3QgdGhl
IGZsZXhpYmlsaXR5IGFuZDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICBQQ0VQ
IG1lc3NhZ2VzLCBhbmQgdGhlcmVmb3JlIDxzcGFuIGNsYXNzPSJpbnNlcnQiPml0IGRvZXM8L3Nw
YW4+IG5vdCBhZmZlY3QgdGhlIGZsZXhpYmlsaXR5IGFuZDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+ICAgZXh0ZW5zaWJpbGl0eSBvZiBQQ0VQLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPiAgIGV4dGVuc2liaWxpdHkgb2YgUENFUC48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGVmdCI+ICAgVGhpcyBkb2N1bWVudCBkZXNjcmliZXMgaG93IHRvIGFwcGx5IFRMUyBpbiBz
ZWN1cmluZyBQQ0U8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBUaGlzIGRvY3Vt
ZW50IGRlc2NyaWJlcyBob3cgdG8gYXBwbHkgVExTIGluIHNlY3VyaW5nIFBDRTwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+ICAgaW50ZXJhY3Rpb25zLCBpbmNsdWRpbmcgaW5pdGlhdGlvbiBv
ZiB0aGUgVExTIHByb2NlZHVyZXMsIHRoZSBUTFM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICBpbnRlcmFjdGlvbnMsIGluY2x1ZGluZyBpbml0aWF0aW9uIG9mIHRoZSBUTFMgcHJv
Y2VkdXJlcywgdGhlIFRMUzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgaGFuZHNoYWtl
IG1lY2hhbmlzbXMsIHRoZSBUTFMgbWV0aG9kcyBmb3IgcGVlciBhdXRoZW50aWNhdGlvbiwgdGhl
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgaGFuZHNoYWtlIG1lY2hhbmlzbXMs
IHRoZSBUTFMgbWV0aG9kcyBmb3IgcGVlciBhdXRoZW50aWNhdGlvbiwgdGhlPC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij4gICBhcHBsaWNhYmxlIFRMUyBjaXBoZXJzdWl0ZXMgZm9yIGRhdGEg
ZXhjaGFuZ2UsIGFuZCB0aGUgaGFuZGxpbmcgb2Y8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICBhcHBsaWNhYmxlIFRMUyBjaXBoZXJzdWl0ZXMgZm9yIGRhdGEgZXhjaGFuZ2UsIGFu
ZCB0aGUgaGFuZGxpbmcgb2Y8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGVycm9ycyBp
biB0aGUgc2VjdXJpdHkgY2hlY2tzLiAgSW4gdGhlIHJlc3Qgb2YgdGhlIGRvY3VtZW50IHdlIHdp
bGw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBlcnJvcnMgaW4gdGhlIHNlY3Vy
aXR5IGNoZWNrcy4gIEluIHRoZSByZXN0IG9mIHRoZSBkb2N1bWVudCB3ZSB3aWxsPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICByZWZlciB0byB0aGlzIHVzYWdlIG9mIFRMUyB0byBwcm92
aWRlIGEgc2VjdXJlIHRyYW5zcG9ydCBmb3IgUENFUCBhczwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgIHJlZmVyIHRvIHRoaXMgdXNhZ2Ugb2YgVExTIHRvIHByb3ZpZGUgYSBzZWN1
cmUgdHJhbnNwb3J0IGZvciBQQ0VQIGFzPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAi
UENFUFMiLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICJQQ0VQUyIuPC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMTAi
Pjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIDxzcGFuIGNs
YXNzPSJpbnNlcnQiPldpdGhpbiB0aGlzIGRvY3VtZW50LCBQQ0VQIGNvbW11bmljYXRpb25zIGFy
ZSBkZXNjcmliZWQgdGhyb3VnaCBQQ0MtPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJs
b2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2Vy
dCI+ICAgUENFIHJlbGF0aW9uc2hpcC4gIFRoZSBQQ0UgYXJjaGl0ZWN0dXJlIGFsc28gc3VwcG9y
dHMgdGhlIFBDRS1QQ0U8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICBjb21t
dW5pY2F0aW9uLCBieSBoYXZpbmcgdGhlIHJlcXVlc3RpbmcgUENFIGZpbGwgdGhlIHJvbGUgb2Yg
YSBQQ0MsPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgYXMgdXN1YWwuICBU
aHVzLCB0aGUgUENDIHJlZmVycyB0byBhIFBDQyBvciBhIFBDRSBpbml0aWF0aW5nIHRoZSBQQ0VQ
PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgc2Vzc2lvbiBhbmQgYWN0aW5n
IGFzIGEgY2xpZW50Ljwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICA8L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPjIuICBSZXF1aXJlbWVudHMgTGFuZ3VhZ2U8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4yLiAgUmVxdWlyZW1lbnRzIExhbmd1YWdlPC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRoZSBrZXkgd29yZHMgIk1VU1QiLCAiTVVTVCBOT1QiLCAi
UkVRVUlSRUQiLCAiU0hBTEwiLCAiU0hBTEwgTk9UIiw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICBUaGUga2V5IHdvcmRzICJNVVNUIiwgIk1VU1QgTk9UIiwgIlJFUVVJUkVEIiwg
IlNIQUxMIiwgIlNIQUxMIE5PVCIsPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAiU0hP
VUxEIiwgIlNIT1VMRCBOT1QiLCAiUkVDT01NRU5ERUQiLCAiTUFZIiwgYW5kICJPUFRJT05BTCIg
aW4gdGhpczwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICJTSE9VTEQiLCAiU0hP
VUxEIE5PVCIsICJSRUNPTU1FTkRFRCIsICJNQVkiLCBhbmQgIk9QVElPTkFMIiBpbiB0aGlzPC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBkb2N1bWVudCBhcmUgdG8gYmUgaW50ZXJwcmV0
ZWQgYXMgZGVzY3JpYmVkIGluIFtSRkMyMTE5XS48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICBkb2N1bWVudCBhcmUgdG8gYmUgaW50ZXJwcmV0ZWQgYXMgZGVzY3JpYmVkIGluIFtS
RkMyMTE5XS48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+My4gIEFwcGx5aW5nIFBD
RVBTPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+My4gIEFwcGx5aW5nIFBDRVBTPC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjMuMS4gIE92ZXJ2aWV3PC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+My4xLiAgT3ZlcnZpZXc8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9InBhcnQtNSIgY2xhc3M9ImNoYW5n
ZSI+PHRkPjwvdGQ+PHRoPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxhIGhy
ZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvcmZjZGlmZiNwYXJ0LTUiPjxlbT4gcGFnZSA1LCBs
aW5lIDI5PHNwYW4gY2xhc3M9ImhpZGUiPiDCtjwvc3Bhbj48L2VtPjwvYT48L3RoPjx0aD4gPC90
aD48dGg+PHNtYWxsPnNraXBwaW5nIHRvIGNoYW5nZSBhdDwvc21hbGw+PGEgaHJlZj0iaHR0cHM6
Ly90b29scy5pZXRmLm9yZy9yZmNkaWZmI3BhcnQtNSI+PGVtPiBwYWdlIDUsIGxpbmUgMzU8c3Bh
biBjbGFzcz0iaGlkZSI+IMK2PC9zcGFuPjwvZW0+PC9hPjwvdGg+PHRkPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgU3RhcnRU
TFMgZmFpbHVyZSkgYW5kIEVycm9yLXZhbHVlIHNldCB0byAxIChyZWNlcHRpb24gb2YgU3RhcnRU
TFM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBTdGFydFRMUyBmYWlsdXJlKSBh
bmQgRXJyb3ItdmFsdWUgc2V0IHRvIDEgKHJlY2VwdGlvbiBvZiBTdGFydFRMUzwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+ICAgYWZ0ZXIgYW55IFBDRVAgZXhjaGFuZ2UpLCBhbmQgTVVTVCBj
bG9zZSB0aGUgVENQIGNvbm5lY3Rpb24uICBBIFBDRVA8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICBhZnRlciBhbnkgUENFUCBleGNoYW5nZSksIGFuZCBNVVNUIGNsb3NlIHRoZSBU
Q1AgY29ubmVjdGlvbi4gIEEgUENFUDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgc3Bl
YWtlciByZWNlaXZpbmcgYW55IG90aGVyIG1lc3NhZ2UgYXBhcnQgZnJvbSBTdGFydFRMUywgT3Bl
biwgb3I8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBzcGVha2VyIHJlY2Vpdmlu
ZyBhbnkgb3RoZXIgbWVzc2FnZSBhcGFydCBmcm9tIFN0YXJ0VExTLCBPcGVuLCBvcjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgUENFcnIgYXMgdGhlIGZpcnN0IG1lc3NhZ2UsIE1VU1Qg
dHJlYXQgaXQgYXMgYW4gdW5leHBlY3RlZCBtZXNzYWdlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgUENFcnIgYXMgdGhlIGZpcnN0IG1lc3NhZ2UsIE1VU1QgdHJlYXQgaXQgYXMg
YW4gdW5leHBlY3RlZCBtZXNzYWdlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBhbmQg
cmVwbHkgd2l0aCBhIFBDRXJyIG1lc3NhZ2Ugd2l0aCBFcnJvci1UeXBlIHNldCB0byBbVEJBMiBi
eSBJQU5BXTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGFuZCByZXBseSB3aXRo
IGEgUENFcnIgbWVzc2FnZSB3aXRoIEVycm9yLVR5cGUgc2V0IHRvIFtUQkEyIGJ5IElBTkFdPC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAoUENFUCBTdGFydFRMUyBmYWlsdXJlKSBhbmQg
RXJyb3ItdmFsdWUgc2V0IHRvIDIgKHJlY2VwdGlvbiBvZiBhbnk8L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4gICAoUENFUCBTdGFydFRMUyBmYWlsdXJlKSBhbmQgRXJyb3ItdmFsdWUg
c2V0IHRvIDIgKHJlY2VwdGlvbiBvZiBhbnk8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
IG90aGVyIG1lc3NhZ2UgYXBhcnQgZnJvbSBTdGFydFRMUywgT3Blbiwgb3IgUENFcnIgbWVzc2Fn
ZSksIGFuZCBNVVNUPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgb3RoZXIgbWVz
c2FnZSBhcGFydCBmcm9tIFN0YXJ0VExTLCBPcGVuLCBvciBQQ0VyciBtZXNzYWdlKSwgYW5kIE1V
U1Q8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGNsb3NlIHRoZSBUQ1AgY29ubmVjdGlv
bi48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBjbG9zZSB0aGUgVENQIGNvbm5l
Y3Rpb24uPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIElmIHRoZSBQQ0VQIHNw
ZWFrZXIgdGhhdCBkb2VzIG5vdCBzdXBwb3J0IFBDRVBTLCByZWNlaXZlcyBhIFN0YXJ0VExTPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgSWYgdGhlIFBDRVAgc3BlYWtlciB0aGF0
IGRvZXMgbm90IHN1cHBvcnQgUENFUFMsIHJlY2VpdmVzIGEgU3RhcnRUTFM8L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMTEiPjx0ZD48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+
ICAgbWVzc2FnZSwgaXQgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+TVVTVDwvc3Bhbj4gYmVoYXZlIGFj
Y29yZGluZyB0byB0aGUgZXhpc3RpbmcgZXJyb3IgbWVjaGFuaXNtPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyYmxvY2siPiAgIG1lc3NhZ2UsIGl0IDxzcGFuIGNsYXNzPSJpbnNlcnQiPndpbGw8
L3NwYW4+IGJlaGF2ZSBhY2NvcmRpbmcgdG8gdGhlIGV4aXN0aW5nIGVycm9yIG1lY2hhbmlzbTwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgZGVzY3JpYmVkIGluIHNlY3Rpb24gNi4yIG9m
IFtSRkM1NDQwXSAoaW4gY2FzZSBtZXNzYWdlIGlzIHJlY2VpdmVkPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgZGVzY3JpYmVkIGluIHNlY3Rpb24gNi4yIG9mIFtSRkM1NDQwXSAo
aW4gY2FzZSBtZXNzYWdlIGlzIHJlY2VpdmVkPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICBwcmlvciB0byBhbiBPcGVuIG1lc3NhZ2UpIG9yIHNlY3Rpb24gNi45IG9mIFtSRkM1NDQwXSAo
Zm9yIHRoZSBjYXNlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgcHJpb3IgdG8g
YW4gT3BlbiBtZXNzYWdlKSBvciBzZWN0aW9uIDYuOSBvZiBbUkZDNTQ0MF0gKGZvciB0aGUgY2Fz
ZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJkaWZmMDAx
MiI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGJsb2NrIj4gICBvZiByZWNlcHRpb24gb2YgdW5rbm93biBtZXNzYWdlKS48L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgb2YgcmVjZXB0aW9uIG9mIHVua25vd24gbWVz
c2FnZSkuPHNwYW4gY2xhc3M9Imluc2VydCI+ICBTZWUgU2VjdGlvbiA1IGZvciBtb3JlIGRldGFp
bHMuPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHIgaWQ9ImRpZmYwMDEzIj48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIEFmdGVyIHRoZSBleGNoYW5nZSBvZiA8c3Bh
biBjbGFzcz0iZGVsZXRlIj5zPC9zcGFuPnRhcnRUTFMgbWVzc2FnZXMsIGlmIGEgUENFUCBzcGVh
a2VyIGNhbm5vdDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICBBZnRlciB0aGUg
ZXhjaGFuZ2Ugb2YgPHNwYW4gY2xhc3M9Imluc2VydCI+Uzwvc3Bhbj50YXJ0VExTIG1lc3NhZ2Vz
LCBpZiBhIFBDRVAgc3BlYWtlciBjYW5ub3Q8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
IGVzdGFibGlzaCBhIFRMUyBjb25uZWN0aW9uIGZvciBzb21lIHJlYXNvbiAoZS5nLiB0aGUgcmVx
dWlyZWQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBlc3RhYmxpc2ggYSBUTFMg
Y29ubmVjdGlvbiBmb3Igc29tZSByZWFzb24gKGUuZy4gdGhlIHJlcXVpcmVkPC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij4gICBtZWNoYW5pc21zIGZvciBjZXJ0aWZpY2F0ZSByZXZvY2F0aW9u
IGNoZWNraW5nIGFyZSBub3QgYXZhaWxhYmxlKSwgaXQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICBtZWNoYW5pc21zIGZvciBjZXJ0aWZpY2F0ZSByZXZvY2F0aW9uIGNoZWNraW5n
IGFyZSBub3QgYXZhaWxhYmxlKSwgaXQ8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIE1V
U1QgcmV0dXJuIGEgUENFcnIgbWVzc2FnZSAoaW4gY2xlYXIpIHdpdGggRXJyb3ItVHlwZSBzZXQg
dG8gW1RCQTI8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBNVVNUIHJldHVybiBh
IFBDRXJyIG1lc3NhZ2UgKGluIGNsZWFyKSB3aXRoIEVycm9yLVR5cGUgc2V0IHRvIFtUQkEyPC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBieSBJQU5BXSAoUENFUCBTdGFydFRMUyBmYWls
dXJlKSBhbmQgRXJyb3ItdmFsdWUgc2V0IHRvOjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgIGJ5IElBTkFdIChQQ0VQIFN0YXJ0VExTIGZhaWx1cmUpIGFuZCBFcnJvci12YWx1ZSBz
ZXQgdG86PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIG8gIDMgKG5vdCB3aXRo
b3V0IFRMUykgaWYgaXQgaXMgbm90IHdpbGxpbmcgdG8gZXhjaGFuZ2UgUENFUCBtZXNzYWdlczwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIG8gIDMgKG5vdCB3aXRob3V0IFRMUykg
aWYgaXQgaXMgbm90IHdpbGxpbmcgdG8gZXhjaGFuZ2UgUENFUCBtZXNzYWdlczwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgd2l0aG91dCB0aGUgc29saWNpdGVkIFRMUyBjb25uZWN0
aW9uLCBhbmQgaXQgTVVTVCBjbG9zZSB0aGUgVENQPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+ICAgICAgd2l0aG91dCB0aGUgc29saWNpdGVkIFRMUyBjb25uZWN0aW9uLCBhbmQgaXQg
TVVTVCBjbG9zZSB0aGUgVENQPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBzZXNz
aW9uLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIHNlc3Npb24uPC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIG8gIDQgKG9rIHdpdGhvdXQgVExTKSBpZiBp
dCBpcyB3aWxsaW5nIHRvIGV4Y2hhbmdlIFBDRVAgbWVzc2FnZXM8L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4gICBvICA0IChvayB3aXRob3V0IFRMUykgaWYgaXQgaXMgd2lsbGluZyB0
byBleGNoYW5nZSBQQ0VQIG1lc3NhZ2VzPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAg
ICB3aXRob3V0IHRoZSBzb2xpY2l0ZWQgVExTIGNvbm5lY3Rpb24sIGFuZCBpdCBNVVNUIGNsb3Nl
IHRoZSBUQ1A8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICB3aXRob3V0IHRo
ZSBzb2xpY2l0ZWQgVExTIGNvbm5lY3Rpb24sIGFuZCBpdCBNVVNUIGNsb3NlIHRoZSBUQ1A8L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMTQiPjx0
ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxibG9jayI+ICAgICAgc2Vzc2lvbi4gIFRoZSA8c3BhbiBjbGFzcz0iZGVsZXRlIj5wZTwvc3Bh
bj5lciBNQVkgY2hvb3NlIHRvIHJlLWVzdGFibGlzaCB0aGUgUENFUCBzZXNzaW9uPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgICAgIHNlc3Npb24uICBUaGUgPHNwYW4gY2xhc3M9
Imluc2VydCI+cmVjZWl2PC9zcGFuPmVyIE1BWSBjaG9vc2UgdG8gcmUtZXN0YWJsaXNoIHRoZSBQ
Q0VQIHNlc3Npb248L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIHdpdGhvdXQgVExT
IG5leHQuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgd2l0aG91dCBUTFMg
bmV4dC48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgSWYgdGhlIFBDRVAgc3Bl
YWtlciBzdXBwb3J0cyBQQ0VQUyBhbmQgY2FuIGVzdGFibGlzaCBhIFRMUyBjb25uZWN0aW9uPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgSWYgdGhlIFBDRVAgc3BlYWtlciBzdXBw
b3J0cyBQQ0VQUyBhbmQgY2FuIGVzdGFibGlzaCBhIFRMUyBjb25uZWN0aW9uPC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij4gICBpdCBNVVNUIHN0YXJ0IHRoZSBUTFMgY29ubmVjdGlvbiBlc3Rh
Ymxpc2htZW50IHN0ZXBzIGRlc2NyaWJlZCBpbjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgIGl0IE1VU1Qgc3RhcnQgdGhlIFRMUyBjb25uZWN0aW9uIGVzdGFibGlzaG1lbnQgc3Rl
cHMgZGVzY3JpYmVkIGluPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBTZWN0aW9uIDMu
NCBiZWZvcmUgdGhlIFBDRVAgaW5pdGlhbGl6YXRpb24gcHJvY2VkdXJlIChzZWN0aW9uIDQuMi4x
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgU2VjdGlvbiAzLjQgYmVmb3JlIHRo
ZSBQQ0VQIGluaXRpYWxpemF0aW9uIHByb2NlZHVyZSAoc2VjdGlvbiA0LjIuMTwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+ICAgb2YgW1JGQzU0NDBdKS48L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICBvZiBbUkZDNTQ0MF0pLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij4gICBBIFBDRVAgc3BlYWtlciB0aGF0IGRvZXMgbm90IHN1cHBvcnQgUENFUFMgb3IgaGFz
IGxlYXJuZWQgdGhlIHBlZXI8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBBIFBD
RVAgc3BlYWtlciB0aGF0IGRvZXMgbm90IHN1cHBvcnQgUENFUFMgb3IgaGFzIGxlYXJuZWQgdGhl
IHBlZXI8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHdpbGxpbmduZXNzIHRvIHJlZXN0
YWJsaXNoIHNlc3Npb24gd2l0aG91dCBUTFMsIGNhbiBzZW5kIHRoZSBPcGVuPC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgd2lsbGluZ25lc3MgdG8gcmVlc3RhYmxpc2ggc2Vzc2lv
biB3aXRob3V0IFRMUywgY2FuIHNlbmQgdGhlIE9wZW48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgIG1lc3NhZ2UgZGlyZWN0bHksIGFzIHBlciBbUkZDNTQ0MF0uPC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+ICAgbWVzc2FnZSBkaXJlY3RseSwgYXMgcGVyIFtSRkM1NDQwXS48
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJwYXJ0
LTYiIGNsYXNzPSJjaGFuZ2UiPjx0ZD48L3RkPjx0aD48c21hbGw+c2tpcHBpbmcgdG8gY2hhbmdl
IGF0PC9zbWFsbD48YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL3JmY2RpZmYjcGFydC02
Ij48ZW0+IHBhZ2UgNywgbGluZSA0PHNwYW4gY2xhc3M9ImhpZGUiPiDCtjwvc3Bhbj48L2VtPjwv
YT48L3RoPjx0aD4gPC90aD48dGg+PHNtYWxsPnNraXBwaW5nIHRvIGNoYW5nZSBhdDwvc21hbGw+
PGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9yZmNkaWZmI3BhcnQtNiI+PGVtPiBwYWdl
IDcsIGxpbmUgMTM8c3BhbiBjbGFzcz0iaGlkZSI+IMK2PC9zcGFuPjwvZW0+PC9hPjwvdGg+PHRk
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+ICAgVGhlIGZvcm1hdCBvZiBhIFN0YXJ0VExTIG1lc3NhZ2UgaXMgYXMgZm9sbG93czo8
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBUaGUgZm9ybWF0IG9mIGEgU3RhcnRU
TFMgbWVzc2FnZSBpcyBhcyBmb2xsb3dzOjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij4gICAgICAmbHQ7U3RhcnRUTFMgTWVzc2FnZSZndDs6Oj0gJmx0O0NvbW1vbiBIZWFkZXImZ3Q7
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgJmx0O1N0YXJ0VExTIE1lc3Nh
Z2UmZ3Q7Ojo9ICZsdDtDb21tb24gSGVhZGVyJmd0OzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICBUaGUgU3RhcnRUTFMgbWVzc2FnZSBNVVNUIGNvbnRhaW4gb25seSB0aGUgUENF
UCBjb21tb24gaGVhZGVyIHdpdGg8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBU
aGUgU3RhcnRUTFMgbWVzc2FnZSBNVVNUIGNvbnRhaW4gb25seSB0aGUgUENFUCBjb21tb24gaGVh
ZGVyIHdpdGg8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIE1lc3NhZ2UtVHlwZSBmaWVs
ZCBzZXQgdG8gW1RCQTEgYnkgSUFOQV0uPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
ICAgTWVzc2FnZS1UeXBlIGZpZWxkIHNldCB0byBbVEJBMSBieSBJQU5BXS48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgT25jZSB0aGUgVENQIGNvbm5lY3Rpb24gaGFzIGJlZW4g
c3VjY2Vzc2Z1bGx5IGVzdGFibGlzaGVkIGFuZCB0aGU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICBPbmNlIHRoZSBUQ1AgY29ubmVjdGlvbiBoYXMgYmVlbiBzdWNjZXNzZnVsbHkg
ZXN0YWJsaXNoZWQgYW5kIHRoZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgU3RhcnRU
TFMgbWVzc2FnZSBzZW50LCB0aGUgc2VuZGVyIE1VU1Qgc3RhcnQgYSB0aW1lciBjYWxsZWQ8L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBTdGFydFRMUyBtZXNzYWdlIHNlbnQsIHRo
ZSBzZW5kZXIgTVVTVCBzdGFydCBhIHRpbWVyIGNhbGxlZDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+ICAgU3RhcnRUTFNXYWl0IHRpbWVyLCBhZnRlciB0aGUgZXhwaXJhdGlvbiBvZiB3aGlj
aCwgaWYgbm8gU3RhcnRUTFM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBTdGFy
dFRMU1dhaXQgdGltZXIsIGFmdGVyIHRoZSBleHBpcmF0aW9uIG9mIHdoaWNoLCBpZiBubyBTdGFy
dFRMUzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJkaWZm
MDAxNSI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGJsb2NrIj4gICBtZXNzYWdlIGhhcyBiZWVuIDxzcGFuIGNsYXNzPSJkZWxldGUi
PnJlY2VpdmVkLDwvc3Bhbj4gaXQgTVVTVCBzZW5kIGEgUENFcnIgbWVzc2FnZSA8c3BhbiBjbGFz
cz0iZGVsZXRlIj5hbmQgcmVsZWFzZXM8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
YmxvY2siPiAgIG1lc3NhZ2UgaGFzIGJlZW4gPHNwYW4gY2xhc3M9Imluc2VydCI+cmVjZWl2ZWQg
KGFuZCBpbiBjYXNlIG9mIGZhaWx1cmUsIGEgUENFcnIgb3IgT3Blbjwvc3Bhbj48L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxibG9jayI+PHNwYW4gY2xhc3M9ImRlbGV0ZSI+ICAgdGhlIFRDUCBjb25u
ZWN0aW9uPC9zcGFuPiB3aXRoIDxzcGFuIGNsYXNzPSJkZWxldGUiPkVycm9yLVR5cGU8L3NwYW4+
IHNldCB0byBbVEJBMiBieSBJQU5BXSBhbmQgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+RXJyb3ItPC9z
cGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0
Ij4gICBtZXNzYWdlIGlzIG5vdCByZWNlaXZlZCksPC9zcGFuPiBpdCBNVVNUIHNlbmQgYSBQQ0Vy
ciBtZXNzYWdlIHdpdGggPHNwYW4gY2xhc3M9Imluc2VydCI+RXJyb3ItPC9zcGFuPjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48c3BhbiBjbGFzcz0iZGVsZXRlIj4gICB2YWx1ZTwvc3Bh
bj4gc2V0IHRvIDUgKG5vIFN0YXJ0VExTIG1lc3NhZ2UgcmVjZWl2ZWQgYmVmb3JlIHRoZSBleHBp
cmF0aW9uIG9mPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJp
bnNlcnQiPiAgIFR5cGU8L3NwYW4+IHNldCB0byBbVEJBMiBieSBJQU5BXSBhbmQgPHNwYW4gY2xh
c3M9Imluc2VydCI+RXJyb3ItdmFsdWU8L3NwYW4+IHNldCB0byA1IChubyBTdGFydFRMUyA8c3Bh
biBjbGFzcz0iaW5zZXJ0Ij4obm9yPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2Nr
Ij4gICB0aGUgU3RhcnRUTFNXYWl0IDxzcGFuIGNsYXNzPSJkZWxldGUiPnRpbWVyKS48L3NwYW4+
ICBBIFJFQ09NTUVOREVEIHZhbHVlIGZvciBTdGFydFRMU1dhaXQgdGltZXI8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgUENFcnIvT3Blbik8
L3NwYW4+IG1lc3NhZ2UgcmVjZWl2ZWQgYmVmb3JlIHRoZSBleHBpcmF0aW9uIG9mIHRoZTwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBpcyA2MCBzZWNvbmRzLjwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmJsb2NrIj4gICBTdGFydFRMU1dhaXQgPHNwYW4gY2xhc3M9Imluc2VydCI+
dGltZXIpIGFuZCBpdCBNVVNUIHJlbGVhc2UgdGhlIFRDUCBjb25uZWN0aW9uIC48L3NwYW4+IEE8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
YmxvY2siPiAgIFJFQ09NTUVOREVEIHZhbHVlIGZvciBTdGFydFRMU1dhaXQgdGltZXIgaXMgNjAg
c2Vjb25kcy48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAg
ICAgKy0rLSsgICAgICAgICAgICAgICAgICstKy0rPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+ICAgICAgICAgICAgICAgICAgKy0rLSsgICAgICAgICAgICAgICAgICstKy0rPC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgICB8UENDfCAgICAgICAgICAg
ICAgICAgfFBDRXw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAg
ICAgICB8UENDfCAgICAgICAgICAgICAgICAgfFBDRXw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgICAgICAgICAgICAgICAgICstKy0rICAgICAgICAgICAgICAgICArLSstKzwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgICAgICstKy0rICAgICAgICAg
ICAgICAgICArLSstKzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAg
ICAgICB8ICAgICAgICAgICAgICAgICAgICAgfDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICAgICAgIHw8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICAgICAgfCBTdGFydFRMUyAgICAgICAg
ICAgIHw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgICAgICAg
IHwgU3RhcnRUTFMgICAgICAgICAgICB8PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAg
ICAgICAgICAgICAgICAgIHwgbXNnICAgICAgICAgICAgICAgICB8PC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICAgICAgICB8IG1zZyAgICAgICAgICAgICAgICAg
fDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAgICAgICB8LS0tLS0t
LSAgICAgICAgICAgICAgfDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAg
ICAgICAgICAgICAgfC0tLS0tLS0gICAgICAgICAgICAgIHw8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgICAgICAgICAgICAgICAgICAgfCAgICAgICBcICAgU3RhcnRUTFMgIHw8L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgICAgICAgIHwgICAgICAgXCAg
IFN0YXJ0VExTICB8PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAg
ICAgIHwgICAgICAgIFwgIG1zZyAgICAgICB8PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+ICAgICAgICAgICAgICAgICAgICB8ICAgICAgICBcICBtc2cgICAgICAgfDwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9InBhcnQtNyIgY2xhc3M9
ImNoYW5nZSI+PHRkPjwvdGQ+PHRoPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxs
PjxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvcmZjZGlmZiNwYXJ0LTciPjxlbT4gcGFn
ZSA4LCBsaW5lIDMxPHNwYW4gY2xhc3M9ImhpZGUiPiDCtjwvc3Bhbj48L2VtPjwvYT48L3RoPjx0
aD4gPC90aD48dGg+PHNtYWxsPnNraXBwaW5nIHRvIGNoYW5nZSBhdDwvc21hbGw+PGEgaHJlZj0i
aHR0cHM6Ly90b29scy5pZXRmLm9yZy9yZmNkaWZmI3BhcnQtNyI+PGVtPiBwYWdlIDgsIGxpbmUg
NDU8c3BhbiBjbGFzcz0iaGlkZSI+IMK2PC9zcGFuPjwvZW0+PC9hPjwvdGg+PHRkPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
ICAgICAgICAgICAgICAgICB8ICAgICAgIFBDRXJyICAgICAgICAgfCAobm9uLU9wZW4gbWVzc2Fn
ZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgICAgICAgfCAg
ICAgICBQQ0VyciAgICAgICAgIHwgKG5vbi1PcGVuIG1lc3NhZ2U8L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPiAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICAgICAgIHwgIHJl
Y2VpdmVkKTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgICAg
ICAgfCAgICAgICAgICAgICAgICAgICAgIHwgIHJlY2VpdmVkKTwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgRmlndXJlIDM6IE9uZSBQQ0VQIFNwZWFrZXIgZG9l
cyBub3Qgc3VwcG9ydCBQQ0VQUzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAg
ICAgICAgICBGaWd1cmUgMzogT25lIFBDRVAgU3BlYWtlciBkb2VzIG5vdCBzdXBwb3J0IFBDRVBT
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjMuNC4gIFRMUyBDb25uZWN0aW9uIEVz
dGFibGlzaG1lbnQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4zLjQuICBUTFMgQ29u
bmVjdGlvbiBFc3RhYmxpc2htZW50PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
IE9uY2UgdGhlIGVzdGFibGlzaG1lbnQgb2YgVExTIGhhcyBiZWVuIGFncmVlZCBieSB0aGUgUENF
UCBwZWVycywgdGhlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgT25jZSB0aGUg
ZXN0YWJsaXNobWVudCBvZiBUTFMgaGFzIGJlZW4gYWdyZWVkIGJ5IHRoZSBQQ0VQIHBlZXJzLCB0
aGU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGNvbm5lY3Rpb24gZXN0YWJsaXNobWVu
dCBTSEFMTCBmb2xsb3cgdGhlIGZvbGxvd2luZyBzdGVwczo8L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICBjb25uZWN0aW9uIGVzdGFibGlzaG1lbnQgU0hBTEwgZm9sbG93IHRoZSBm
b2xsb3dpbmcgc3RlcHM6PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0ciBpZD0iZGlmZjAwMTYiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgMS4gIEltbWVkaWF0ZWx5IG5lZ290
aWF0ZSA8c3BhbiBjbGFzcz0iZGVsZXRlIj5UTFMgc2Vzc2lvbnM8L3NwYW4+IGFjY29yZGluZyB0
byBbUkZDNTI0Nl0uICBUaGU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgMS4g
IEltbWVkaWF0ZWx5IG5lZ290aWF0ZSA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5hIFRMUyBzZXNzaW9u
PC9zcGFuPiBhY2NvcmRpbmcgdG8gW1JGQzUyNDZdLiAgVGhlPC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICAgICAgZm9sbG93aW5nIHJlc3RyaWN0aW9ucyBhcHBseTo8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgZm9sbG93aW5nIHJlc3RyaWN0aW9ucyBhcHBseTo8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICogIFN1cHBvcnQgZm9yIFRM
UyB2MS4yIFtSRkM1MjQ2XSBvciBsYXRlciBpcyBSRVFVSVJFRC48L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4gICAgICAgKiAgU3VwcG9ydCBmb3IgVExTIHYxLjIgW1JGQzUyNDZdIG9y
IGxhdGVyIGlzIFJFUVVJUkVELjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAg
ICAgKiAgU3VwcG9ydCBmb3IgY2VydGlmaWNhdGUtYmFzZWQgbXV0dWFsIGF1dGhlbnRpY2F0aW9u
IGlzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICogIFN1cHBvcnQgZm9y
IGNlcnRpZmljYXRlLWJhc2VkIG11dHVhbCBhdXRoZW50aWNhdGlvbiBpczwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgIFJFUVVJUkVELjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgICAgICAgICBSRVFVSVJFRC48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+ICAgICAgICogIE5lZ290aWF0aW9uIG9mIG11dHVhbCBhdXRoZW50aWNhdGlvbiBpcyBS
RVFVSVJFRC48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgKiAgTmVnb3Rp
YXRpb24gb2YgbXV0dWFsIGF1dGhlbnRpY2F0aW9uIGlzIFJFUVVJUkVELjwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgKiAgTmVnb3RpYXRpb24gb2YgYSBjaXBoZXJzdWl0
ZSBwcm92aWRpbmcgZm9yIGludGVncml0eTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgICAgICAqICBOZWdvdGlhdGlvbiBvZiBhIGNpcGhlcnN1aXRlIHByb3ZpZGluZyBmb3IgaW50
ZWdyaXR5PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBp
ZD0icGFydC04IiBjbGFzcz0iY2hhbmdlIj48dGQ+PC90ZD48dGg+PHNtYWxsPnNraXBwaW5nIHRv
IGNoYW5nZSBhdDwvc21hbGw+PGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9yZmNkaWZm
I3BhcnQtOCI+PGVtPiBwYWdlIDExLCBsaW5lIDQ8c3BhbiBjbGFzcz0iaGlkZSI+IMK2PC9zcGFu
PjwvZW0+PC9hPjwvdGg+PHRoPiA8L3RoPjx0aD48c21hbGw+c2tpcHBpbmcgdG8gY2hhbmdlIGF0
PC9zbWFsbD48YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL3JmY2RpZmYjcGFydC04Ij48
ZW0+IHBhZ2UgMTEsIGxpbmUgMTg8c3BhbiBjbGFzcz0iaGlkZSI+IMK2PC9zcGFuPjwvZW0+PC9h
PjwvdGg+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBvICBQZWVyJ3MgZnVsbHkgcXVhbGlmaWVkIGRvbWFpbiBu
YW1lIChGUUROKTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIG8gIFBlZXIncyBm
dWxseSBxdWFsaWZpZWQgZG9tYWluIG5hbWUgKEZRRE4pPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPiAgIG8gIENlcnRpZmljYXRlIEZpbmdlcnByaW50PC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgbyAgQ2VydGlmaWNhdGUgRmluZ2VycHJpbnQ8L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgbyAgSXNzdWVyPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgbyAgSXNzdWVyPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
IG8gIFN1YmplY3Q8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBvICBTdWJqZWN0
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIG8gIEFsbCBYNTA5djMgRXh0ZW5k
ZWQgS2V5IFVzYWdlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgbyAgQWxsIFg1
MDl2MyBFeHRlbmRlZCBLZXkgVXNhZ2U8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0ciBpZD0iZGlmZjAwMTciPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICA8L3NwYW4+
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBvICBBbGwgWDUwOXYzIFN1YmplY3QgQWx0
ZXJuYXRpdmUgTmFtZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIG8gIEFsbCBY
NTA5djMgU3ViamVjdCBBbHRlcm5hdGl2ZSBOYW1lPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgIG8gIEFsbCBYNTA5djMgQ2VydGlmaWNhdGUgUG9saWNpZXM8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBvICBBbGwgWDUwOXYzIENlcnRpZmljYXRlIFBvbGljaWVz
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlm
ZjAwMTgiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIDxz
cGFuIGNsYXNzPSJpbnNlcnQiPk5vdGUgdGhhdCB0aGUgcmVtb3RlIElQIGFkZHJlc3MgdXNlZCBm
b3IgdGhlIFRDUCBzZXNzaW9uPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAg
ZXN0YWJsaXNobWVudCBpcyBhbHNvIGV4cG9zZWQuPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgIDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgW0ktRC5pZXRmLXBjZS1zdGF0ZWZ1
bC1zeW5jLW9wdGltaXphdGlvbnNdIHNwZWNpZnkgYSBTcGVha2VyIEVudGl0eTwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFtJLUQuaWV0Zi1wY2Utc3RhdGVmdWwtc3luYy1vcHRp
bWl6YXRpb25zXSBzcGVjaWZ5IGEgU3BlYWtlciBFbnRpdHk8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgIElkZW50aWZpZXIgVExWIChTUEVBS0VSLUVOVElUWS1JRCksIGFzIGFuIG9wdGlv
bmFsIFRMViB0aGF0IE1BWSBiZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIElk
ZW50aWZpZXIgVExWIChTUEVBS0VSLUVOVElUWS1JRCksIGFzIGFuIG9wdGlvbmFsIFRMViB0aGF0
IE1BWSBiZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgaW5jbHVkZWQgaW4gdGhlIE9Q
RU4gT2JqZWN0LiAgSXQgY29udGFpbnMgYSB1bmlxdWUgaWRlbnRpZmllciBmb3IgdGhlPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgaW5jbHVkZWQgaW4gdGhlIE9QRU4gT2JqZWN0
LiAgSXQgY29udGFpbnMgYSB1bmlxdWUgaWRlbnRpZmllciBmb3IgdGhlPC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij4gICBub2RlIHRoYXQgZG9lcyBub3QgY2hhbmdlIGR1cmluZyB0aGUgbGlm
ZXRpbWUgb2YgdGhlIFBDRVAgc3BlYWtlci48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICBub2RlIHRoYXQgZG9lcyBub3QgY2hhbmdlIGR1cmluZyB0aGUgbGlmZXRpbWUgb2YgdGhl
IFBDRVAgc3BlYWtlci48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIEFuIGltcGxlbWVu
dGF0aW9uIHdvdWxkIHRodXMgZXhwb3NlIHRoZSBzcGVha2VyIGVudGl0eSBpZGVudGlmaWVyIGFz
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgQW4gaW1wbGVtZW50YXRpb24gd291
bGQgdGh1cyBleHBvc2UgdGhlIHNwZWFrZXIgZW50aXR5IGlkZW50aWZpZXIgYXM8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHBhcnQgb2YgdGhlIFg1MDl2MyBjZXJ0aWZpY2F0ZSwgc28g
dGhhdCBhbiBpbXBsZW1lbnRhdGlvbiBjb3VsZCB1c2U8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICBwYXJ0IG9mIHRoZSBYNTA5djMgY2VydGlmaWNhdGUsIHNvIHRoYXQgYW4gaW1w
bGVtZW50YXRpb24gY291bGQgdXNlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICB0aGlz
IGlkZW50aWZpZXIgZm9yIHRoZSBwZWVyIGlkZW50aWZpY2F0aW9uIHRydXN0IG1vZGVsLjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHRoaXMgaWRlbnRpZmllciBmb3IgdGhlIHBl
ZXIgaWRlbnRpZmljYXRpb24gdHJ1c3QgbW9kZWwuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgIEluIGFkZGl0aW9uLCBhIFBDQyBNQVkgYXBwbHkgdGhlIHByb2NlZHVyZXMgZGVz
Y3JpYmVkIGluIFtSRkM2Njk4XTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIElu
IGFkZGl0aW9uLCBhIFBDQyBNQVkgYXBwbHkgdGhlIHByb2NlZHVyZXMgZGVzY3JpYmVkIGluIFtS
RkM2Njk4XTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgRE5TLUJhc2VkIEF1dGhlbnRp
Y2F0aW9uIG9mIE5hbWVkIEVudGl0aWVzIChEQU5FKSB0byB2ZXJpZnkgaXRzIHBlZXI8L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBETlMtQmFzZWQgQXV0aGVudGljYXRpb24gb2Yg
TmFtZWQgRW50aXRpZXMgKERBTkUpIHRvIHZlcmlmeSBpdHMgcGVlcjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9InBhcnQtOSIgY2xhc3M9ImNoYW5n
ZSI+PHRkPjwvdGQ+PHRoPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxhIGhy
ZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvcmZjZGlmZiNwYXJ0LTkiPjxlbT4gcGFnZSAxMSwg
bGluZSAzMjxzcGFuIGNsYXNzPSJoaWRlIj4gwrY8L3NwYW4+PC9lbT48L2E+PC90aD48dGg+IDwv
dGg+PHRoPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxhIGhyZWY9Imh0dHBz
Oi8vdG9vbHMuaWV0Zi5vcmcvcmZjZGlmZiNwYXJ0LTkiPjxlbT4gcGFnZSAxMiwgbGluZSA3PHNw
YW4gY2xhc3M9ImhpZGUiPiDCtjwvc3Bhbj48L2VtPjwvYT48L3RoPjx0ZD48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
SW4gY2FzZSB0aGUgaW5pdGlhbCBUTFMgbmVnb3RpYXRpb24gb3IgdGhlIHBlZXIgaWRlbnRpdHkg
Y2hlY2sgZmFpbHMsPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgSW4gY2FzZSB0
aGUgaW5pdGlhbCBUTFMgbmVnb3RpYXRpb24gb3IgdGhlIHBlZXIgaWRlbnRpdHkgY2hlY2sgZmFp
bHMsPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBhY2NvcmRpbmcgdG8gdGhlIHByb2Nl
ZHVyZXMgbGlzdGVkIGluIHRoaXMgZG9jdW1lbnQsIHRoZSBwZWVyIE1VU1Q8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBhY2NvcmRpbmcgdG8gdGhlIHByb2NlZHVyZXMgbGlzdGVk
IGluIHRoaXMgZG9jdW1lbnQsIHRoZSBwZWVyIE1VU1Q8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgIGZpcnN0IHNlbmQgYSBQQ0VyciBtZXNzYWdlIGFzIHBlciBTZWN0aW9uIDMuMiBhbmQg
dGhlbiB0ZXJtaW5hdGUgdGhlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgZmly
c3Qgc2VuZCBhIFBDRXJyIG1lc3NhZ2UgYXMgcGVyIFNlY3Rpb24gMy4yIGFuZCB0aGVuIHRlcm1p
bmF0ZSB0aGU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHNlc3Npb24uICBJdCBTSE9V
TEQgZm9sbG93IHRoZSBwcm9jZWR1cmUgbGlzdGVkIGluIFtSRkM1NDQwXSB0byByZXRyeTwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHNlc3Npb24uICBJdCBTSE9VTEQgZm9sbG93
IHRoZSBwcm9jZWR1cmUgbGlzdGVkIGluIFtSRkM1NDQwXSB0byByZXRyeTwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgc2Vzc2lvbiBzZXR1cCBhbG9uZyB3aXRoIGFuIGV4cG9uZW50aWFs
IGJhY2stb2ZmIHNlc3Npb248L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBzZXNz
aW9uIHNldHVwIGFsb25nIHdpdGggYW4gZXhwb25lbnRpYWwgYmFjay1vZmYgc2Vzc2lvbjwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgZXN0YWJsaXNobWVudCByZXRyeSBwcm9jZWR1cmUu
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgZXN0YWJsaXNobWVudCByZXRyeSBw
cm9jZWR1cmUuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjQuICBEaXNjb3Zlcnkg
TWVjaGFuaXNtczwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjQuICBEaXNjb3Zlcnkg
TWVjaGFuaXNtczwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHIgaWQ9ImRpZmYwMDE5Ij48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIDxzcGFuIGNsYXNzPSJkZWxldGUiPkEgUENF
IGNhbiBhZHZlcnRpc2UgaXRzIGNhcGFiaWxpdHkgdG8gc3VwcG9ydCBQQ0VQUyB1c2luZyB0aGUg
SUdQPC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICA8c3BhbiBjbGFz
cz0iaW5zZXJ0Ij5UaGlzIGRvY3VtZW50IGRvZXMgbm90IHNwZWNpZnkgYW55PC9zcGFuPiBkaXNj
b3ZlcnkgPHNwYW4gY2xhc3M9Imluc2VydCI+bWVjaGFuaXNtPC9zcGFuPiBmb3Igc3VwcG9ydCBv
ZjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48c3BhbiBjbGFzcz0iZGVsZXRlIj4gICBh
ZHZlcnRpc2VtZW50IGFuZDwvc3Bhbj4gZGlzY292ZXJ5IDxzcGFuIGNsYXNzPSJkZWxldGUiPm1l
Y2hhbmlzbS4gIFRoZSBQQ0UtQ0FQLUZMQUdTIHN1Yi1UTFYgaXM8L3NwYW4+PC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIDxzcGFuIGNsYXNzPSJpbnNlcnQiPlBDRVBTLiAgT3Ro
ZXIgZG9jdW1lbnRzLCBbSS1ELnd1LXBjZS1kaXNjb3ZlcnktcGNlcHMtc3VwcG9ydF0gYW5kPC9z
cGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48c3BhbiBjbGFzcz0iZGVsZXRlIj4g
ICBhbiBvcHRpb25hbCBzdWItVExWIHVzZWQgdG8gYWR2ZXJ0aXNlIFBDRSBjYXBhYmlsaXRpZXMu
ICBJdCBNQVkgYmU8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFu
IGNsYXNzPSJpbnNlcnQiPiAgIFtJLUQud3UtcGNlLWRucy1wY2UtZGlzY292ZXJ5XSBoYXZlIG1h
ZGUgcHJvcG9zYWxzOjwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PHNwYW4g
Y2xhc3M9ImRlbGV0ZSI+ICAgcHJlc2VudCB3aXRoaW4gdGhlIFBDRSBEaXNjb3ZlcnkgKFBDRUQp
IHN1Yi1UTFYgY2FycmllZCBieSBPU1BGIG9yPC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmJsb2NrIj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PHNwYW4gY2xhc3M9ImRl
bGV0ZSI+ICAgSVMtSVMuICBbUkZDNTA4OF0gYW5kIFtSRkM1MDg5XSBwcm92aWRlIHRoZSBkZXNj
cmlwdGlvbiBhbmQ8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48c3BhbiBjbGFzcz0iZGVsZXRlIj4gICBwcm9jZXNz
aW5nIHJ1bGVzIGZvciB0aGlzIHN1Yi1UTFYgd2hlbiBjYXJyaWVkIHdpdGhpbiBPU1BGIGFuZCBJ
Uy1JUyw8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGJsb2NrIj48c3BhbiBjbGFzcz0iZGVsZXRlIj4gICByZXNwZWN0aXZlbHku
ICBQQ0UgY2FwYWJpbGl0eSBiaXRzIGFyZSBkZWZpbmVkIGluIFtSRkM1MDg4XS4gIEEgbmV3PC9z
cGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxibG9jayI+PHNwYW4gY2xhc3M9ImRlbGV0ZSI+ICAgY2FwYWJpbGl0eSBmbGFnIGJpdDwv
c3Bhbj4gZm9yIDxzcGFuIGNsYXNzPSJkZWxldGUiPnRoZSBQQ0UtQ0FQLUZMQUdTIHN1Yi1UTFYg
dGhhdCBjYW4gYmU8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48c3BhbiBjbGFzcz0iZGVsZXRlIj4gICBhbm5vdW5j
ZWQgYXMgYXR0cmlidXRlIHRvIGRpc3RyaWJ1dGUgUENFUCBzZWN1cml0eTwvc3Bhbj4gc3VwcG9y
dDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxibG9jayI+ICAgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+aW5mb3JtYXRpb24gaXMgcHJvcG9zZWQg
aW4gW0ktRC53dS1wY2UtZGlzY292ZXJ5LXBjZXBzLXN1cHBvcnRdPC9zcGFuPjwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PHNw
YW4gY2xhc3M9ImRlbGV0ZSI+PC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2Nr
Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PHNwYW4gY2xhc3M9ImRlbGV0ZSI+ICAg
V2hlbiBETlMgaXMgdXNlZCBieSBhIFBDQyAob3IgYSBQQ0UgYWN0aW5nIGFzIGEgY2xpZW50LCBm
b3IgdGhlIHJlc3Q8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBvZiA8c3BhbiBjbGFzcz0iZGVsZXRlIj50aGUg
c2VjdGlvbiwgUENDIHJlZmVycyB0byBib3RoKSB3aWxsaW5nIHRvIHVzZSBQQ0VQUyB0byBsb2Nh
dGUgYW48L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGJsb2NrIj48c3BhbiBjbGFzcz0iZGVsZXRlIj4gICBhcHByb3ByaWF0ZSBQ
Q0UgW0ktRC53dS1wY2UtZG5zLXBjZS1kaXNjb3ZlcnldLCB0aGUgUENDIGFzIGFuPC9zcGFuPjwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxi
bG9jayI+PHNwYW4gY2xhc3M9ImRlbGV0ZSI+ICAgaW5pdGlhdGluZyBlbnRpdHksIGNob29zZXMg
YXQgbGVhc3Qgb25lIG9mIHRoZSByZXR1cm5lZCBGUUROcyB0bzwvc3Bhbj48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJibG9jayI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFu
IGNsYXNzPSJkZWxldGUiPiAgIHJlc29sdmUsIHdoaWNoIGl0IGRvZXMgYnkgcGVyZm9ybWluZyBE
TlMgIkEiIG9yICJBQUFBIiBsb29rdXBzIG9uIHRoZTwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJibG9jayI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNsYXNz
PSJkZWxldGUiPiAgIEZEUU4uICBUaGlzIHdpbGwgZXZlbnR1YWxseSByZXN1bHQgaW4gYW4gSVB2
NCBvciBJUHY2IGFkZHJlc3MuICBUaGU8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
YmxvY2siPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48c3BhbiBjbGFzcz0iZGVsZXRl
Ij4gICBQQ0MgU0hBTEwgdXNlIHRoZSBJUCBhZGRyZXNzKGVzKSBmcm9tIHRoZSBzdWNjZXNzZnVs
bHkgcmVzb2x2ZWQgRkRRTjwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNsYXNzPSJkZWxldGUiPiAgICh3
aXRoIHRoZSBjb3JyZXNwb25kaW5nIHBvcnQgbnVtYmVyIHJldHVybmVkIGJ5IHRoZSBETlMgU2Vy
dmljZTwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNsYXNzPSJkZWxldGUiPiAgIFJlY29yZCAoU1JWKSBs
b29rdXApIGFzIHRoZSBjb25uZWN0aW9uIGFkZHJlc3MoZXMpIGZvciB0aGUgcmVjZWl2aW5nPC9z
cGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxibG9jayI+PHNwYW4gY2xhc3M9ImRlbGV0ZSI+ICAgZW50aXR5Ljwvc3Bhbj48L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMjAiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgPHNwYW4gY2xh
c3M9ImRlbGV0ZSI+SWYgdGhlIFBDQyBmYWlsczwvc3Bhbj4gdG8gPHNwYW4gY2xhc3M9ImRlbGV0
ZSI+Y29ubmVjdDwvc3Bhbj4gdXNpbmcgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+YW4gSVAgYWRkcmVz
cyBidXQgdGhlICJBIiBvciAiQUFBQSI8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
YmxvY2siPiAgIDxzcGFuIGNsYXNzPSJpbnNlcnQiPm8gIEEgUENFIGNhbiBhZHZlcnRpc2UgaXRz
IGNhcGFiaWxpdHk8L3NwYW4+IHRvIDxzcGFuIGNsYXNzPSJpbnNlcnQiPnN1cHBvcnQgUENFUFM8
L3NwYW4+IHVzaW5nIHRoZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48c3BhbiBjbGFz
cz0iZGVsZXRlIj4gICBsb29rdXBzIHJldHVybmVkIG1vcmUgdGhhbiBvbmUgSVAgYWRkcmVzcywg
dGhlbiB0aGUgUENDIFNIT1VMRCB1c2U8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
YmxvY2siPiAgICAgIDxzcGFuIGNsYXNzPSJpbnNlcnQiPklHUCdzIGFkdmVydGlzZW1lbnQgbWVj
aGFuaXNtIG9mPC9zcGFuPiB0aGUgPHNwYW4gY2xhc3M9Imluc2VydCI+UENFIGRpc2NvdmVyeSBp
bmZvcm1hdGlvbi48L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNs
YXNzPSJkZWxldGUiPiAgIHRoZSBuZXh0IHJlc29sdmVkIElQIGFkZHJlc3MgZm9yIHRoYXQgRkRR
TiBhczwvc3Bhbj4gdGhlIDxzcGFuIGNsYXNzPSJkZWxldGUiPmNvbm5lY3Rpb24gYWRkcmVzcy48
L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNl
cnQiPiAgICAgIFRoZSBQQ0UtQ0FQLUZMQUdTIHN1Yi1UTFYgaXMgYW4gb3B0aW9uYWwgc3ViLVRM
ViB1c2VkPC9zcGFuPiB0byA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5hZHZlcnRpc2U8L3NwYW4+PC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNsYXNzPSJkZWxldGUiPiAgIElmPC9z
cGFuPiB0aGUgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+UENDIGZhaWxzPC9zcGFuPiB0byA8c3BhbiBj
bGFzcz0iZGVsZXRlIj5jb25uZWN0IHVzaW5nIGFsbCByZXNvbHZlZCBJUCBhZGRyZXNzZXMgZm9y
IGE8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJp
bnNlcnQiPiAgICAgIFBDRSBjYXBhYmlsaXRpZXMuICBJdCBpcyBwcmVzZW50IHdpdGhpbiB0aGUg
UENFIERpc2NvdmVyeSAoUENFRCk8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2si
PjxzcGFuIGNsYXNzPSJkZWxldGUiPiAgIGdpdmVuIEZEUU4sIHRoZW4gaXQgU0hPVUxEIHJlcGVh
dDwvc3Bhbj4gdGhlIDxzcGFuIGNsYXNzPSJkZWxldGUiPnByb2Nlc3Mgb2YgcmVzb2x1dGlvbjwv
c3Bhbj4gYW5kPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJp
bnNlcnQiPiAgICAgIHN1Yi1UTFYgY2FycmllZCBieSBPU1BGIG9yIElTLUlTLiAgW1JGQzUwODhd
IGFuZCBbUkZDNTA4OV0gcHJvdmlkZTwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9j
ayI+ICAgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+Y29ubmVjdGlvbjwvc3Bhbj4gZm9yIDxzcGFuIGNs
YXNzPSJkZWxldGUiPnRoZSBuZXh0IEZRRE4gcmV0dXJuZWQgYnkgdGhlIFNSViBsb29rdXAgYmFz
ZWQgb24gdGhlPC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAgICB0
aGUgPHNwYW4gY2xhc3M9Imluc2VydCI+ZGVzY3JpcHRpb248L3NwYW4+IGFuZCA8c3BhbiBjbGFz
cz0iaW5zZXJ0Ij5wcm9jZXNzaW5nIHJ1bGVzPC9zcGFuPiBmb3IgPHNwYW4gY2xhc3M9Imluc2Vy
dCI+dGhpcyBzdWItVExWIHdoZW4gY2FycmllZDwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxibG9jayI+PHNwYW4gY2xhc3M9ImRlbGV0ZSI+ICAgcHJpb3JpdHk8L3NwYW4+IGFuZCA8c3Bh
biBjbGFzcz0iZGVsZXRlIj53ZWlnaHQuPC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICAgICB3aXRoaW4gT1NQRjwvc3Bhbj4gYW5k
IDxzcGFuIGNsYXNzPSJpbnNlcnQiPklTLUlTLCByZXNwZWN0aXZlbHkuICBQQ0UgY2FwYWJpbGl0
eSBiaXRzIGFyZTwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgICAgIGRlZmlu
ZWQgaW4gW1JGQzUwODhdLiAgQSBuZXcgY2FwYWJpbGl0eSBmbGFnIGJpdCBmb3IgdGhlIFBDRS1D
QVAtPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgICAgRkxBR1Mgc3ViLVRM
ViB0aGF0IGNhbiBiZSBhbm5vdW5jZWQgYXMgYW4gYXR0cmlidXRlIHRvIGRpc3RyaWJ1dGU8L3Nw
YW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICAgICBQQ0VQIHNlY3VyaXR5IHN1cHBv
cnQgaW5mb3JtYXRpb24gaXMgcHJvcG9zZWQgaW48L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0i
aW5zZXJ0Ij4gICAgICBbSS1ELnd1LXBjZS1kaXNjb3ZlcnktcGNlcHMtc3VwcG9ydF0uPC9zcGFu
PjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9ImRp
ZmYwMDIxIj48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsYmxvY2siPiAgIDxzcGFuIGNsYXNzPSJkZWxldGUiPklmIHRoZSBQQ0MgcmVj
ZWl2ZXMgYSByZXNwb25zZSB0bzwvc3Bhbj4gaXRzIDxzcGFuIGNsYXNzPSJkZWxldGUiPlNSViBx
dWVyeSBidXQgaXQgaXMgbm90IGFibGU8L3NwYW4+IHRvPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyYmxvY2siPiAgIDxzcGFuIGNsYXNzPSJpbnNlcnQiPm8gIEEgUENFIGNhbiBhZHZlcnRpc2U8
L3NwYW4+IGl0cyA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5jYXBhYmlsaXR5PC9zcGFuPiB0byA8c3Bh
biBjbGFzcz0iaW5zZXJ0Ij5zdXBwb3J0PC9zcGFuPiBQQ0VQUyB1c2luZyB0aGUgPHNwYW4gY2xh
c3M9Imluc2VydCI+RE5TPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICA8
c3BhbiBjbGFzcz0iZGVsZXRlIj5lc3RhYmxpc2ggYTwvc3Bhbj4gUENFUFMgPHNwYW4gY2xhc3M9
ImRlbGV0ZSI+Y29ubmVjdGlvbjwvc3Bhbj4gdXNpbmcgdGhlIDxzcGFuIGNsYXNzPSJkZWxldGUi
PmRhdGEgcmVjZWl2ZWQgaW48L3NwYW4+IHRoZSA8c3BhbiBjbGFzcz0iZGVsZXRlIj5yZXNwb25z
ZSw8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJp
bnNlcnQiPiAgICAgIFtJLUQud3UtcGNlLWRucy1wY2UtZGlzY292ZXJ5XSBieSBpZGVudGlmeWlu
Zzwvc3Bhbj4gdGhlIDxzcGFuIGNsYXNzPSJpbnNlcnQiPnN1cHBvcnQgb2YgVExTLjwvc3Bhbj48
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PHNwYW4gY2xhc3M9ImRlbGV0ZSI+ICAgYXMg
aW5pdGlhdGluZyBlbnRpdHkgaXQgTUFZIGZhbGwgYmFjayB0byBsb29rdXAgYSBQQ0UgdGhhdCB1
c2VzIFRDUDwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNsYXNzPSJkZWxldGUiPiAgIGFzIHRyYW5zcG9y
dC48L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij40LjEuICBEQU5FIEFwcGxpY2FiaWxpdHk8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij40LjEuICBEQU5FIEFwcGxpY2FiaWxpdHk8L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgREFORSBbUkZDNjY5OF0gZGVmaW5lcyBhIHNlY3VyZSBt
ZXRob2QgdG8gYXNzb2NpYXRlIHRoZSBjZXJ0aWZpY2F0ZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgIERBTkUgW1JGQzY2OThdIGRlZmluZXMgYSBzZWN1cmUgbWV0aG9kIHRvIGFz
c29jaWF0ZSB0aGUgY2VydGlmaWNhdGU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHRo
YXQgaXMgb2J0YWluZWQgZnJvbSBhIFRMUyBzZXJ2ZXIgd2l0aCBhIGRvbWFpbiBuYW1lIHVzaW5n
IEROUyw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICB0aGF0IGlzIG9idGFpbmVk
IGZyb20gYSBUTFMgc2VydmVyIHdpdGggYSBkb21haW4gbmFtZSB1c2luZyBETlMsPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBpLmUuLCB1c2luZyB0aGUgVExTQSBETlMgcmVzb3VyY2Ug
cmVjb3JkIChSUikgdG8gYXNzb2NpYXRlIGEgVExTPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+ICAgaS5lLiwgdXNpbmcgdGhlIFRMU0EgRE5TIHJlc291cmNlIHJlY29yZCAoUlIpIHRv
IGFzc29jaWF0ZSBhIFRMUzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgc2VydmVyIGNl
cnRpZmljYXRlIG9yIHB1YmxpYyBrZXkgd2l0aCB0aGUgZG9tYWluIG5hbWUgd2hlcmUgdGhlPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgc2VydmVyIGNlcnRpZmljYXRlIG9yIHB1
YmxpYyBrZXkgd2l0aCB0aGUgZG9tYWluIG5hbWUgd2hlcmUgdGhlPC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij4gICByZWNvcmQgaXMgZm91bmQsIHRodXMgZm9ybWluZyBhICJUTFNBIGNlcnRp
ZmljYXRlIGFzc29jaWF0aW9uIi4gIFRoZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgIHJlY29yZCBpcyBmb3VuZCwgdGh1cyBmb3JtaW5nIGEgIlRMU0EgY2VydGlmaWNhdGUgYXNz
b2NpYXRpb24iLiAgVGhlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBETlMgaW5mb3Jt
YXRpb24gbmVlZHMgdG8gYmUgcHJvdGVjdGVkIGJ5IEROUyBTZWN1cml0eSAoRE5TU0VDKS4gIEE8
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBETlMgaW5mb3JtYXRpb24gbmVlZHMg
dG8gYmUgcHJvdGVjdGVkIGJ5IEROUyBTZWN1cml0eSAoRE5TU0VDKS4gIEE8L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPiAgIFBDQyB3aWxsaW5nIHRvIGFwcGx5IERBTkUgdG8gdmVyaWZ5IHNl
cnZlciBpZGVudGl0eSBNVVNUIGNvbmZvcm0gdG88L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICBQQ0Mgd2lsbGluZyB0byBhcHBseSBEQU5FIHRvIHZlcmlmeSBzZXJ2ZXIgaWRlbnRp
dHkgTVVTVCBjb25mb3JtIHRvPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0ciBpZD0icGFydC0xMCIgY2xhc3M9ImNoYW5nZSI+PHRkPjwvdGQ+PHRoPjxzbWFs
bD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0
Zi5vcmcvcmZjZGlmZiNwYXJ0LTEwIj48ZW0+IHBhZ2UgMTIsIGxpbmUgNDM8c3BhbiBjbGFzcz0i
aGlkZSI+IMK2PC9zcGFuPjwvZW0+PC9hPjwvdGg+PHRoPiA8L3RoPjx0aD48c21hbGw+c2tpcHBp
bmcgdG8gY2hhbmdlIGF0PC9zbWFsbD48YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL3Jm
Y2RpZmYjcGFydC0xMCI+PGVtPiBwYWdlIDEyLCBsaW5lIDQ5PHNwYW4gY2xhc3M9ImhpZGUiPiDC
tjwvc3Bhbj48L2VtPjwvYT48L3RoPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjUuICBCYWNrd2FyZCBDb21wYXRpYmlsaXR5
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+NS4gIEJhY2t3YXJkIENvbXBhdGliaWxp
dHk8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgVGhlIHByb2NlZHVyZXMgZGVz
Y3JpYmVkIGluIHRoaXMgZG9jdW1lbnQgZGVmaW5lIGEgc2VjdXJpdHkgY29udGFpbmVyPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgVGhlIHByb2NlZHVyZXMgZGVzY3JpYmVkIGlu
IHRoaXMgZG9jdW1lbnQgZGVmaW5lIGEgc2VjdXJpdHkgY29udGFpbmVyPC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij4gICBmb3IgdGhlIHRyYW5zcG9ydCBvZiBQQ0VQIHJlcXVlc3RzIGFuZCBy
ZXBsaWVzIGNhcnJpZWQgYnkgYSBUTFM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4g
ICBmb3IgdGhlIHRyYW5zcG9ydCBvZiBQQ0VQIHJlcXVlc3RzIGFuZCByZXBsaWVzIGNhcnJpZWQg
YnkgYSBUTFM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGNvbm5lY3Rpb24gaW5pdGlh
dGVkIGJ5IG1lYW5zIG9mIGEgc3BlY2lmaWMgZXh0ZW5kZWQgbWVzc2FnZTwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPiAgIGNvbm5lY3Rpb24gaW5pdGlhdGVkIGJ5IG1lYW5zIG9mIGEg
c3BlY2lmaWMgZXh0ZW5kZWQgbWVzc2FnZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
KFN0YXJ0VExTKSB0aGF0IGRvZXMgbm90IGludGVyZmVyZSB3aXRoIFBDRVAgc3BlYWtlciBpbXBs
ZW1lbnRhdGlvbnM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAoU3RhcnRUTFMp
IHRoYXQgZG9lcyBub3QgaW50ZXJmZXJlIHdpdGggUENFUCBzcGVha2VyIGltcGxlbWVudGF0aW9u
czwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgbm90IHN1cHBvcnRpbmcgaXQuPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgbm90IHN1cHBvcnRpbmcgaXQuPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIElmIGEgUENFUCBpbXBsZW1lbnRhdGlvbiB0aGF0
IGRvZXMgbm90IHN1cHBvcnQgUENFUFMgcmVjZWl2ZXMgYTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgIElmIGEgUENFUCBpbXBsZW1lbnRhdGlvbiB0aGF0IGRvZXMgbm90IHN1cHBv
cnQgUENFUFMgcmVjZWl2ZXMgYTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgU3RhcnRU
TFMgbWVzc2FnZSwgaXQgd291bGQgYmVoYXZlIGFjY29yZGluZyB0byB0aGUgZXhpc3RpbmcgZXJy
b3I8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBTdGFydFRMUyBtZXNzYWdlLCBp
dCB3b3VsZCBiZWhhdmUgYWNjb3JkaW5nIHRvIHRoZSBleGlzdGluZyBlcnJvcjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJkaWZmMDAyMiI+PHRkPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2Nr
Ij4gICBtZWNoYW5pc20gb2YgW1JGQzU0NDBdLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJs
b2NrIj4gICBtZWNoYW5pc20gb2YgW1JGQzU0NDBdLiAgPHNwYW4gY2xhc3M9Imluc2VydCI+T24g
cmVjZWl2aW5nIHRoZSBlcnJvciwgYmFzZWQgb24gdGhlIGxvY2FsPC9zcGFuPjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNw
YW4gY2xhc3M9Imluc2VydCI+ICAgcG9saWN5LCBhIHBlZXIgY291bGQgdHJ5IHRvIGVzdGFibGlz
aGluZyBQQ0VQIHNlc3Npb24gd2l0aG91dCBUTFMgYXM8L3NwYW4+PC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFz
cz0iaW5zZXJ0Ij4gICBwZXIgdGhlIHByb2NlZHVyZXMgZGVmaW5lZCBpbiBbUkZDNTQ0MF0uICBG
b3Igc3VjY2Vzc2Z1bCBUTFM8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICBv
cGVyYXRpb25zIHdpdGggUENFUCwgYm90aCBQQ0VQIHBlZXJzIGluIHRoZSBuZXR3b3JrIHdvdWxk
IG5lZWQgdG8gYmU8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICB1cGdyYWRl
ZCB0byBzdXBwb3J0IHRoaXMgZG9jdW1lbnQuPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imlu
c2VydCI+PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgQW4gZXhpc3Rpbmcg
UENFUCBzZXNzaW9uIGNhbm5vdCBiZSB1cGdyYWRlZCB0byBQQ0VQUywgdGhlIHNlc3Npb248L3Nw
YW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICBuZWVkcyB0byBiZSB0ZXJtaW5hdGVk
IGFuZCByZWVzdGFibGlzaGVkIGFzIHBlciB0aGUgcHJvY2VkdXJlPC9zcGFuPjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNw
YW4gY2xhc3M9Imluc2VydCI+ICAgZGVzY3JpYmVkIGluIHRoaXMgZG9jdW1lbnQuICBEdXJpbmcg
dGhlIGluY3JlbWVudGFsIHVwZ3JhZGUsIHRoZSBQQ0VQPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xh
c3M9Imluc2VydCI+ICAgc3BlYWtlciBTSE9VTEQgYWxsb3cgc2Vzc2lvbiBlc3RhYmxpc2htZW50
IHdpdGggYW5kIHdpdGhvdXQgVExTLjwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9j
ayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQi
PiAgIE9uY2UgYm90aCBQQ0VQIHNwZWFrZXJzIGFyZSB1cGdyYWRlZCB0byBzdXBwb3J0IFBDRVBT
LCB0aGUgUENFUDwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgIHNlc3Npb24g
aXMgcmUtZXN0YWJsaXNoZWQgd2l0aCBUTFMsIG90aGVyd2lzZSBQQ0VQIHNlc3Npb24gd2l0aG91
dDwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgIFRMUyBpcyBzZXR1cC4gIEEg
cmVkdW5kYW50IFBDRSBNQVkgYWxzbyBiZSB1c2VkIGR1cmluZyB0aGU8L3NwYW4+PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48
c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICBpbmNyZW1lbnRhbCBkZXBsb3ltZW50IHRvIHRha2Ugb3Zl
ciB0aGUgUENFIHVuZGVyZ29pbmcgdXBncmFkZS4gIE9uY2U8L3NwYW4+PC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBj
bGFzcz0iaW5zZXJ0Ij4gICB0aGUgdXBncmFkZSBpcyBjb21wbGV0ZWQsIHN1cHBvcnQgZm9yIHVu
c2VjdXJlZCB2ZXJzaW9uIFNIT1VMRCBiZTwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxi
bG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNl
cnQiPiAgIHJlbW92ZWQuPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij42
LiAgSUFOQSBDb25zaWRlcmF0aW9uczwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjYu
ICBJQU5BIENvbnNpZGVyYXRpb25zPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjYu
MS4gIE5ldyBQQ0VQIE1lc3NhZ2U8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij42LjEu
ICBOZXcgUENFUCBNZXNzYWdlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIElB
TkEgaXMgcmVxdWVzdGVkIHRvIGFsbG9jYXRlIG5ldyBtZXNzYWdlIHR5cGVzIHdpdGhpbiB0aGUg
IlBDRVA8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBJQU5BIGlzIHJlcXVlc3Rl
ZCB0byBhbGxvY2F0ZSBuZXcgbWVzc2FnZSB0eXBlcyB3aXRoaW4gdGhlICJQQ0VQPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBNZXNzYWdlcyIgc3ViLXJlZ2lzdHJ5IG9mIHRoZSBQQ0VQ
IE51bWJlcnMgcmVnaXN0cnksIGFzIGZvbGxvd3M6PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+ICAgTWVzc2FnZXMiIHN1Yi1yZWdpc3RyeSBvZiB0aGUgUENFUCBOdW1iZXJzIHJlZ2lz
dHJ5LCBhcyBmb2xsb3dzOjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBW
YWx1ZSAgRGVzY3JpcHRpb24gICAgICAgICAgICAgICAgICAgICAgICAgICAgIFJlZmVyZW5jZTwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIFZhbHVlICBEZXNjcmlwdGlvbiAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgUmVmZXJlbmNlPC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICAgICAgVEJBMSAgVGhlIFN0YXJ0IFRMUyBNZXNzYWdlIChTdGFydFRMUykgICAg
ICAgIFRoaXMgZG9jdW1lbnQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAg
VEJBMSAgVGhlIFN0YXJ0IFRMUyBNZXNzYWdlIChTdGFydFRMUykgICAgICAgIFRoaXMgZG9jdW1l
bnQ8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+Ni4yLiAgTmV3IEVycm9yLVZhbHVl
czwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjYuMi4gIE5ldyBFcnJvci1WYWx1ZXM8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgSUFOQSBpcyByZXF1ZXN0ZWQgdG8g
YWxsb2NhdGUgbmV3IEVycm9yIFR5cGVzIGFuZCBFcnJvciBWYWx1ZXMgd2l0aGluPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgSUFOQSBpcyByZXF1ZXN0ZWQgdG8gYWxsb2NhdGUg
bmV3IEVycm9yIFR5cGVzIGFuZCBFcnJvciBWYWx1ZXMgd2l0aGluPC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij4gICB0aGUgIiBQQ0VQLUVSUk9SIE9iamVjdCBFcnJvciBUeXBlcyBhbmQgVmFs
dWVzIiBzdWItcmVnaXN0cnkgb2YgdGhlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
ICAgdGhlICIgUENFUC1FUlJPUiBPYmplY3QgRXJyb3IgVHlwZXMgYW5kIFZhbHVlcyIgc3ViLXJl
Z2lzdHJ5IG9mIHRoZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgUENFUCBOdW1iZXJz
IHJlZ2lzdHJ5LCBhcyBmb2xsb3dzOjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAg
IFBDRVAgTnVtYmVycyByZWdpc3RyeSwgYXMgZm9sbG93czo8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+ICAgRXJyb3ItPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAg
RXJyb3ItPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBUeXBlICAgIE1lYW5pbmcgICAg
ICAgICAgICAgICBFcnJvci12YWx1ZSAgICAgICAgICAgICBSZWZlcmVuY2U8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBUeXBlICAgIE1lYW5pbmcgICAgICAgICAgICAgICBFcnJv
ci12YWx1ZSAgICAgICAgICAgICBSZWZlcmVuY2U8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJkaWZmMDAyMyI+PHRkPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBUQkEyICAg
IFN0YXJ0VExTIDxzcGFuIGNsYXNzPSJkZWxldGUiPkZhaWx1cmU8L3NwYW4+ICAgICAgMDpVbmFz
c2lnbmVkICAgICAgICAgICAgVGhpcyBkb2N1bWVudDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmJsb2NrIj4gICBUQkEyICAgIDxzcGFuIGNsYXNzPSJpbnNlcnQiPlBDRVA8L3NwYW4+IFN0YXJ0
VExTICAgICAgICAgMDpVbmFzc2lnbmVkICAgICAgICAgICAgVGhpcyBkb2N1bWVudDwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAx
OlJlY2VwdGlvbiBvZiAgICAgICAgICBUaGlzIGRvY3VtZW50PC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyYmxvY2siPiAgICAgICAgICAgPHNwYW4gY2xhc3M9Imluc2VydCI+ZmFpbHVyZTwvc3Bh
bj4gICAgICAgICAgICAgICAxOlJlY2VwdGlvbiBvZiAgICAgICAgICBUaGlzIGRvY3VtZW50PC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICBTdGFydFRMUyBhZnRlcjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIFN0YXJ0VExTIGFmdGVyPC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBhbnkgUENFUCBleGNo
YW5nZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIGFueSBQQ0VQIGV4Y2hhbmdlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAyOlJlY2VwdGlvbiBvZiAgICAgICAg
ICBUaGlzIGRvY3VtZW50PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgMjpSZWNlcHRpb24gb2YgICAgICAgICAgVGhpcyBkb2N1
bWVudDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgYW55IG90aGVyIG1lc3NhZ2U8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBhbnkgb3RoZXIgbWVzc2FnZTwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
YXBhcnQgZnJvbSBTdGFydFRMUyw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICBhcGFydCBmcm9tIFN0YXJ0VExTLDwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgT3Bl
biBvciBQQ0VycjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIE9wZW4gb3IgUENFcnI8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIDM6RmFpbHVyZSwgY29ubmVjdGlv
biAgIFRoaXMgZG9jdW1lbnQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAzOkZhaWx1cmUsIGNvbm5lY3Rpb24gICBUaGlzIGRv
Y3VtZW50PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICB3aXRob3V0IFRMUyBub3Q8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB3aXRob3V0IFRMUyBub3Q8L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHBv
c3NpYmxlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgcG9zc2libGU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgIDQ6RmFpbHVyZSwgY29ubmVjdGlvbiAgIFRoaXMg
ZG9jdW1lbnQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICA0OkZhaWx1cmUsIGNvbm5lY3Rpb24gICBUaGlzIGRvY3VtZW50PC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICB3aXRob3V0IFRMUyBwb3NzaWJsZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHdpdGhvdXQgVExTIHBvc3NpYmxlPC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICA1
Ok5vIFN0YXJ0VExTIG1lc3NhZ2UgICBUaGlzIGRvY3VtZW50PC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgNTpObyBTdGFydFRM
UyBtZXNzYWdlICAgVGhpcyBkb2N1bWVudDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyIGlkPSJkaWZmMDAyNCI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgKG5vciBQQ0Vyci9PcGVuKTwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIGJlZm9yZSBTdGFydFRMU1dh
aXQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICBiZWZvcmUgU3RhcnRUTFNXYWl0PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB0aW1lciBleHBpcnk8L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB0
aW1lciBleHBpcnk8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+Ny4gIFNlY3VyaXR5
IENvbnNpZGVyYXRpb25zPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+Ny4gIFNlY3Vy
aXR5IENvbnNpZGVyYXRpb25zPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFdo
aWxlIHRoZSBhcHBsaWNhdGlvbiBvZiBUTFMgc2F0aXNmaWVzIHRoZSByZXF1aXJlbWVudCBvbiBw
cml2YWN5IGFzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgV2hpbGUgdGhlIGFw
cGxpY2F0aW9uIG9mIFRMUyBzYXRpc2ZpZXMgdGhlIHJlcXVpcmVtZW50IG9uIHByaXZhY3kgYXM8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHdlbGwgYXMgZmluZS1ncmFpbmVkLCBwb2xp
Y3ktYmFzZWQgcGVlciBhdXRoZW50aWNhdGlvbiwgdGhlcmUgYXJlPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgd2VsbCBhcyBmaW5lLWdyYWluZWQsIHBvbGljeS1iYXNlZCBwZWVy
IGF1dGhlbnRpY2F0aW9uLCB0aGVyZSBhcmU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
IHNlY3VyaXR5IHRocmVhdHMgdGhhdCBpdCBjYW5ub3QgYWRkcmVzcy4gIEl0IG1heSBiZSBhZHZp
c2FibGUgdG88L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBzZWN1cml0eSB0aHJl
YXRzIHRoYXQgaXQgY2Fubm90IGFkZHJlc3MuICBJdCBtYXkgYmUgYWR2aXNhYmxlIHRvPC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBhcHBseSBhZGRpdGlvbmFsIHByb3RlY3Rpb24gbWVh
c3VyZXMsIGluIHBhcnRpY3VsYXIgaW4gd2hhdCByZWxhdGVzPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgYXBwbHkgYWRkaXRpb25hbCBwcm90ZWN0aW9uIG1lYXN1cmVzLCBpbiBw
YXJ0aWN1bGFyIGluIHdoYXQgcmVsYXRlczwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
dG8gYXR0YWNrcyBzcGVjaWZpY2FsbHkgYWRkcmVzc2VkIHRvIGZvcmdpbmcgdGhlIFRDUCBjb25u
ZWN0aW9uPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgdG8gYXR0YWNrcyBzcGVj
aWZpY2FsbHkgYWRkcmVzc2VkIHRvIGZvcmdpbmcgdGhlIFRDUCBjb25uZWN0aW9uPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0icGFydC0xMSIgY2xh
c3M9ImNoYW5nZSI+PHRkPjwvdGQ+PHRoPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3Nt
YWxsPjxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvcmZjZGlmZiNwYXJ0LTExIj48ZW0+
IHBhZ2UgMTQsIGxpbmUgNDE8c3BhbiBjbGFzcz0iaGlkZSI+IMK2PC9zcGFuPjwvZW0+PC9hPjwv
dGg+PHRoPiA8L3RoPjx0aD48c21hbGw+c2tpcHBpbmcgdG8gY2hhbmdlIGF0PC9zbWFsbD48YSBo
cmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL3JmY2RpZmYjcGFydC0xMSI+PGVtPiBwYWdlIDE1
LCBsaW5lIDMyPHNwYW4gY2xhc3M9ImhpZGUiPiDCtjwvc3Bhbj48L2VtPjwvYT48L3RoPjx0ZD48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGVmdCI+ICAgQSBQQ0Ugb3IgUENDIGltcGxlbWVudGF0aW9uIE1VU1QgYWxsb3cgY29uZmln
dXJpbmcgdGhlIFBDRVAgc2VjdXJpdHk8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4g
ICBBIFBDRSBvciBQQ0MgaW1wbGVtZW50YXRpb24gTVVTVCBhbGxvdyBjb25maWd1cmluZyB0aGUg
UENFUCBzZWN1cml0eTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgdmlhIFRMUyBjYXBh
YmlsaXRpZXMgYXMgZGVzY3JpYmVkIGluIHRoaXMgZG9jdW1lbnQuPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgdmlhIFRMUyBjYXBhYmlsaXRpZXMgYXMgZGVzY3JpYmVkIGluIHRo
aXMgZG9jdW1lbnQuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIEEgUENFIG9y
IFBDQyBpbXBsZW1lbnRhdGlvbiBzdXBwb3J0aW5nIFBDRVAgc2VjdXJpdHkgdmlhIFRMUyBNVVNU
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgQSBQQ0Ugb3IgUENDIGltcGxlbWVu
dGF0aW9uIHN1cHBvcnRpbmcgUENFUCBzZWN1cml0eSB2aWEgVExTIE1VU1Q8L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPiAgIHN1cHBvcnQgZ2VuZXJhbCBUTFMgY29uZmlndXJhdGlvbiBhcyBw
ZXIgW1JGQzUyNDZdLiAgQXQgbGVhc3QgdGhlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+ICAgc3VwcG9ydCBnZW5lcmFsIFRMUyBjb25maWd1cmF0aW9uIGFzIHBlciBbUkZDNTI0Nl0u
ICBBdCBsZWFzdCB0aGU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGNvbmZpZ3VyYXRp
b24gb2Ygb25lIG9mIHRoZSB0cnVzdCBtb2RlbHMgYW5kIGl0cyBjb3JyZXNwb25kaW5nPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgY29uZmlndXJhdGlvbiBvZiBvbmUgb2YgdGhl
IHRydXN0IG1vZGVscyBhbmQgaXRzIGNvcnJlc3BvbmRpbmc8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgIHBhcmFtZXRlcnMsIGFzIGRlc2NyaWJlZCBpbiBTZWN0aW9uIDMuNCBhbmQgU2Vj
dGlvbiAzLjUsIE1VU1QgYmU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBwYXJh
bWV0ZXJzLCBhcyBkZXNjcmliZWQgaW4gU2VjdGlvbiAzLjQgYW5kIFNlY3Rpb24gMy41LCBNVVNU
IGJlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBzdXBwb3J0ZWQgYnkgdGhlIGltcGxl
bWVudGF0aW9uLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHN1cHBvcnRlZCBi
eSB0aGUgaW1wbGVtZW50YXRpb24uPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMjUiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgQSBQQ0VQIGltcGxlbWVu
dGF0aW9uIFNIT1VMRCBhbGxvdyBjb25maWd1cmluZyB0aGUgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+
Zm9sbG93aW5nIFBDRVA8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAg
IEEgUENFUCBpbXBsZW1lbnRhdGlvbiBTSE9VTEQgYWxsb3cgY29uZmlndXJpbmcgdGhlIFN0YXJ0
VExTV2FpdCB0aW1lcjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48c3BhbiBjbGFzcz0i
ZGVsZXRlIj4gICBzZWN1cml0eSBwYXJhbWV0ZXJzOjwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJibG9jayI+ICAgPHNwYW4gY2xhc3M9Imluc2VydCI+dmFsdWUuPC9zcGFuPjwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48c3BhbiBjbGFzcz0iZGVsZXRlIj48L3NwYW4+PC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJs
b2NrIj48c3BhbiBjbGFzcz0iZGVsZXRlIj4gICBvPC9zcGFuPiAgU3RhcnRUTFNXYWl0IHRpbWVy
IDxzcGFuIGNsYXNzPSJkZWxldGUiPnZhbHVlPC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmJsb2NrIj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgUENFUFMgaW1w
bGVtZW50YXRpb25zIE1BWSBwcm92aWRlIGFuIG9wdGlvbiB0byBhbGxvdyB0aGUgb3BlcmF0b3Ig
dG88L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBQQ0VQUyBpbXBsZW1lbnRhdGlv
bnMgTUFZIHByb3ZpZGUgYW4gb3B0aW9uIHRvIGFsbG93IHRoZSBvcGVyYXRvciB0bzwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgbWFudWFsbHkgb3ZlcnJpZGUgc3RyaWN0IFRMUyBjb25m
aWd1cmF0aW9uIGFuZCBhbGxvdyB1bnNlY3VyZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgIG1hbnVhbGx5IG92ZXJyaWRlIHN0cmljdCBUTFMgY29uZmlndXJhdGlvbiBhbmQgYWxs
b3cgdW5zZWN1cmU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGNvbm5lY3Rpb25zLiAg
RXhlY3V0aW9uIG9mIHRoaXMgb3ZlcnJpZGUgU0hPVUxEIHRyaWdnZXIgYSB3YXJuaW5nPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgY29ubmVjdGlvbnMuICBFeGVjdXRpb24gb2Yg
dGhpcyBvdmVycmlkZSBTSE9VTEQgdHJpZ2dlciBhIHdhcm5pbmc8L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPiAgIGFib3V0IHRoZSBzZWN1cml0eSBpbXBsaWNhdGlvbnMgb2YgcGVybWl0dGlu
ZyB1bnNlY3VyZSBjb25uZWN0aW9ucy48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4g
ICBhYm91dCB0aGUgc2VjdXJpdHkgaW1wbGljYXRpb25zIG9mIHBlcm1pdHRpbmcgdW5zZWN1cmUg
Y29ubmVjdGlvbnMuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIEZ1cnRoZXIs
IHRoZSBvcGVyYXRvciBuZWVkcyB0byBkZXZlbG9wIHN1aXRhYmxlIHNlY3VyaXR5IHBvbGljaWVz
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgRnVydGhlciwgdGhlIG9wZXJhdG9y
IG5lZWRzIHRvIGRldmVsb3Agc3VpdGFibGUgc2VjdXJpdHkgcG9saWNpZXM8L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPiAgIGFyb3VuZCBQQ0VQIHdpdGhpbiBoaXMgbmV0d29yay4gIEZ1cnRo
ZXIgdGhlIFBDRVAgcGVlcnMgU0hPVUxEPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
ICAgYXJvdW5kIFBDRVAgd2l0aGluIGhpcyBuZXR3b3JrLiAgRnVydGhlciB0aGUgUENFUCBwZWVy
cyBTSE9VTEQ8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0i
ZGlmZjAwMjYiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgcHJvdmlkZSB3YXlzIGZvciB0aGUgb3BlcmF0b3IgdG8g
Y29tcGxldGUgdGhlIGZvbGxvd2luZyA8c3BhbiBjbGFzcz0iZGVsZXRlIj50YXNrczo8L3NwYW4+
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIHByb3ZpZGUgd2F5cyBmb3IgdGhl
IG9wZXJhdG9yIHRvIGNvbXBsZXRlIHRoZSBmb2xsb3dpbmcgPHNwYW4gY2xhc3M9Imluc2VydCI+
dGFza3MgaW48L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICByZWdhcmRzIHRv
IGEgUENFUCBzZXNzaW9uOjwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyIGlkPSJkaWZmMDAyNyI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBvICBEZXRlcm1pbmUg
aWYgYSA8c3BhbiBjbGFzcz0iZGVsZXRlIj5QQ0VQIDwvc3Bhbj5zZXNzaW9uIGlzIHByb3RlY3Rl
ZCB2aWEgUENFUFMuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIG8gIERldGVy
bWluZSBpZiBhIHNlc3Npb24gaXMgcHJvdGVjdGVkIHZpYSBQQ0VQUy48L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQg
Y2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+ICAgbyAgRGV0ZXJtaW5lIHRoZSB2ZXJzaW9uIG9mIFRMUywgdGhl
IG1lY2hhbmlzbSB1c2VkIGZvcjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIG8g
IERldGVybWluZSB0aGUgdmVyc2lvbiBvZiBUTFMsIHRoZSBtZWNoYW5pc20gdXNlZCBmb3I8L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIGF1dGhlbnRpY2F0aW9uLCBhbmQgdGhlIGNp
cGhlcnN1aXRlIGluIHVzZS48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICBh
dXRoZW50aWNhdGlvbiwgYW5kIHRoZSBjaXBoZXJzdWl0ZSBpbiB1c2UuPC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgIG8gIERldGVybWluZSBpZiB0aGUgY2VydGlmaWNhdGUgY291
bGQgbm90IGJlIHZlcmlmaWVkLCBhbmQgdGhlIHJlYXNvbjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgIG8gIERldGVybWluZSBpZiB0aGUgY2VydGlmaWNhdGUgY291bGQgbm90IGJl
IHZlcmlmaWVkLCBhbmQgdGhlIHJlYXNvbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
ICAgZm9yIHRoaXMgY2lyY3Vtc3RhbmNlLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgICAgIGZvciB0aGlzIGNpcmN1bXN0YW5jZS48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+ICAgbyAgSW5zcGVjdCB0aGUgY2VydGlmaWNhdGUgb2ZmZXJlZCBieSB0aGUgUENFUCBw
ZWVyLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIG8gIEluc3BlY3QgdGhlIGNl
cnRpZmljYXRlIG9mZmVyZWQgYnkgdGhlIFBDRVAgcGVlci48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+ICAgbyAgQmUgd2FybmVkIGlmIFN0YXJ0VExTIHByb2NlZHVyZSBmYWlscyBm
b3IgdGhlIFBDRVAgcGVlcnMsIHRoYXQgYXJlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+ICAgbyAgQmUgd2FybmVkIGlmIFN0YXJ0VExTIHByb2NlZHVyZSBmYWlscyBmb3IgdGhlIFBD
RVAgcGVlcnMsIHRoYXQgYXJlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBrbm93
biB0byBzdXBwb3J0IFBDRVBTLCB2aWEgY29uZmlndXJhdGlvbnMgb3IgY2FwYWJpbGl0eTwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIGtub3duIHRvIHN1cHBvcnQgUENFUFMs
IHZpYSBjb25maWd1cmF0aW9ucyBvciBjYXBhYmlsaXR5PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij4gICAgICBhZHZlcnRpc2VtZW50cy48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICAgICBhZHZlcnRpc2VtZW50cy48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
OC4yLiAgSW5mb3JtYXRpb24gYW5kIERhdGEgTW9kZWxzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+OC4yLiAgSW5mb3JtYXRpb24gYW5kIERhdGEgTW9kZWxzPC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMjgiPjx0ZD48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9j
ayI+ICAgVGhlIFBDRVAgTUlCIG1vZHVsZSA8c3BhbiBjbGFzcz0iZGVsZXRlIj5TSE9VTEQ8L3Nw
YW4+IGJlIGV4dGVuZGVkIHRvIGluY2x1ZGUgUENFUFMgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+Y2Fw
YWJpbGl0aWVzLDwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgVGhl
IFBDRVAgTUlCIG1vZHVsZSA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5pcyBkZWZpbmVkIGluIFtSRkM3
NDIwXS4gIFRoZSBNSUIgbW9kdWxlIGNvdWxkPC9zcGFuPiBiZTwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGJsb2NrIj48c3BhbiBjbGFzcz0iZGVsZXRlIj4gICBpbmZvcm1hdGlvbiwgYW5kIHN0YXR1
cy48L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIGV4dGVuZGVkIHRv
IGluY2x1ZGUgPHNwYW4gY2xhc3M9Imluc2VydCI+dGhlIGFiaWxpdHkgdG8gdmlldyB0aGU8L3Nw
YW4+IFBDRVBTIDxzcGFuIGNsYXNzPSJpbnNlcnQiPmNhcGFiaWxpdHksIFRMUzwvc3Bhbj48L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxv
Y2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgIHJlbGF0ZWQgaW5mb3JtYXRpb24gYXMgd2VsbCBh
cyBUTFMgc3RhdHVzIGZvciBlYWNoIFBDRVAgcGVlci48L3NwYW4+PC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMjkiPjx0ZD48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+
ICAgQW4gaW1wbGVtZW50YXRpb24gU0hPVUxEIGFsbG93IHRoZSBvcGVyYXRvciB0byBjb25maWd1
cmUgdGhlIFBDRVBTPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIEFuIGltcGxl
bWVudGF0aW9uIFNIT1VMRCA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5hbHNvPC9zcGFuPiBhbGxvdyB0
aGUgb3BlcmF0b3IgdG8gY29uZmlndXJlIHRoZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2Nr
Ij4gICBjYXBhYmlsaXR5IGFuZCB2YXJpb3VzIFRMUyByZWxhdGVkIDxzcGFuIGNsYXNzPSJkZWxl
dGUiPnBhcmFtZXRlcnMsIGFzIHdlbGwgYXMgYWxsb3c8L3NwYW4+IHRvPC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyYmxvY2siPiAgIFBDRVBTIGNhcGFiaWxpdHkgYW5kIHZhcmlvdXMgVExTIHJl
bGF0ZWQgPHNwYW4gY2xhc3M9Imluc2VydCI+cGFyYW1ldGVycyBpbiBhZGRpdGlvbiB0bzwvc3Bh
bj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgdmlldyB0aGUgY3VycmVudCBUTFMg
c3RhdHVzIGZvciBhIFBDRVAgc2Vzc2lvbi4gIFRvIHNlcnZlIHRoaXM8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgYWJpbGl0eTwvc3Bhbj4g
dG8gdmlldyB0aGUgY3VycmVudCBUTFMgc3RhdHVzIGZvciBhIFBDRVAgc2Vzc2lvbi4gIFRvIHNl
cnZlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIHB1cnBvc2UsIHRoZSBQQ0VQIFlB
TkcgbW9kdWxlIFtJLUQuaWV0Zi1wY2UtcGNlcC15YW5nXSA8c3BhbiBjbGFzcz0iZGVsZXRlIj5j
YW4gYmU8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIHRoaXMgcHVy
cG9zZSwgdGhlIFBDRVAgWUFORyBtb2R1bGUgW0ktRC5pZXRmLXBjZS1wY2VwLXlhbmddIDxzcGFu
IGNsYXNzPSJpbnNlcnQiPmlzPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4g
ICBleHRlbmRlZCB0byBpbmNsdWRlIFRMUyByZWxhdGVkIGNvbmZpZ3VyYXRpb24gYW5kIDxzcGFu
IGNsYXNzPSJkZWxldGUiPnN0YXRlLjwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJi
bG9jayI+ICAgZXh0ZW5kZWQgdG8gaW5jbHVkZSBUTFMgcmVsYXRlZCBjb25maWd1cmF0aW9uIGFu
ZCA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5zdGF0ZSBpbmZvcm1hdGlvbi48L3NwYW4+PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjguMy4gIExpdmVuZXNzIERldGVjdGlvbiBhbmQgTW9u
aXRvcmluZzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjguMy4gIExpdmVuZXNzIERl
dGVjdGlvbiBhbmQgTW9uaXRvcmluZzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICBNZWNoYW5pc21zIGRlZmluZWQgaW4gdGhpcyBkb2N1bWVudCBkbyBub3QgaW1wbHkgYW55IG5l
dyBsaXZlbmVzczwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIE1lY2hhbmlzbXMg
ZGVmaW5lZCBpbiB0aGlzIGRvY3VtZW50IGRvIG5vdCBpbXBseSBhbnkgbmV3IGxpdmVuZXNzPC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBkZXRlY3Rpb24gYW5kIG1vbml0b3JpbmcgcmVx
dWlyZW1lbnRzIGluIGFkZGl0aW9uIHRvIHRob3NlIGFscmVhZHk8L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4gICBkZXRlY3Rpb24gYW5kIG1vbml0b3JpbmcgcmVxdWlyZW1lbnRzIGlu
IGFkZGl0aW9uIHRvIHRob3NlIGFscmVhZHk8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
IGxpc3RlZCBpbiBbUkZDNTQ0MF0gYW5kIFtSRkM1MjQ2XS48L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICBsaXN0ZWQgaW4gW1JGQzU0NDBdIGFuZCBbUkZDNTI0Nl0uPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMzAiPjx0
ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxibG9jayI+OC40LiAgVmVyaWZ5IENvcnJlY3QgT3BlcmF0aW9uczwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmJsb2NrIj44LjQuICBWZXJpZnk8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5pbmc8L3Nw
YW4+IENvcnJlY3QgT3BlcmF0aW9uczwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICBBIFBDRVBTIGltcGxlbWVudGF0aW9uIFNIT1VMRCBsb2cgZXJyb3IgZXZlbnRzIGFuZCBwcm92
aWRlIFBDRVBTPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgQSBQQ0VQUyBpbXBs
ZW1lbnRhdGlvbiBTSE9VTEQgbG9nIGVycm9yIGV2ZW50cyBhbmQgcHJvdmlkZSBQQ0VQUzwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgZmFpbHVyZSBzdGF0aXN0aWNzIHdpdGggcmVhc29u
cy48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBmYWlsdXJlIHN0YXRpc3RpY3Mg
d2l0aCByZWFzb25zLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij44LjUuICBSZXF1
aXJlbWVudHMgb24gT3RoZXIgUHJvdG9jb2xzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+OC41LiAgUmVxdWlyZW1lbnRzIG9uIE90aGVyIFByb3RvY29sczwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij4gICBNZWNoYW5pc21zIGRlZmluZWQgaW4gdGhpcyBkb2N1bWVudCBk
byBub3QgaW1wbHkgYW55IG5ldyByZXF1aXJlbWVudHM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICBNZWNoYW5pc21zIGRlZmluZWQgaW4gdGhpcyBkb2N1bWVudCBkbyBub3QgaW1w
bHkgYW55IG5ldyByZXF1aXJlbWVudHM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0ciBpZD0iZGlmZjAwMzEiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgb24gb3RoZXIgcHJvdG9jb2xz
LjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICBvbiBvdGhlciBwcm90b2NvbHMu
ICA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5Ob3RlIHRoYXQsIFNlY3Rpb24gNCBsaXN0IHBvc3NpYmxl
IGRpc2NvdmVyeTwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgIG1lY2hhbmlz
bSBmb3Igc3VwcG9ydCBvZiBQQ0VQUy48L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPjguNi4gIEltcGFjdCBvbiBOZXR3b3JrIE9wZXJhdGlvbjwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmlnaHQiPjguNi4gIEltcGFjdCBvbiBOZXR3b3JrIE9wZXJhdGlvbjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBNZWNoYW5pc21zIGRlZmluZWQgaW4gdGhpcyBk
b2N1bWVudCBkbyBub3QgaGF2ZSBhbnkgc2lnbmlmaWNhbnQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICBNZWNoYW5pc21zIGRlZmluZWQgaW4gdGhpcyBkb2N1bWVudCBkbyBub3Qg
aGF2ZSBhbnkgc2lnbmlmaWNhbnQ8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGltcGFj
dCBvbiBuZXR3b3JrIG9wZXJhdGlvbnMgaW4gYWRkaXRpb24gdG8gdGhvc2UgYWxyZWFkeSBsaXN0
ZWQgaW48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBpbXBhY3Qgb24gbmV0d29y
ayBvcGVyYXRpb25zIGluIGFkZGl0aW9uIHRvIHRob3NlIGFscmVhZHkgbGlzdGVkIGluPC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBbUkZDNTQ0MF0sIGFuZCB0aGUgcG9saWN5IGFuZCBt
YW5hZ2VtZW50IGltcGxpY2F0aW9ucyBkaXNjdXNzZWQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICBbUkZDNTQ0MF0sIGFuZCB0aGUgcG9saWN5IGFuZCBtYW5hZ2VtZW50IGltcGxp
Y2F0aW9ucyBkaXNjdXNzZWQ8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGFib3ZlLjwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGFib3ZlLjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij45LiAgQWNrbm93bGVkZ2VtZW50czwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPjkuICBBY2tub3dsZWRnZW1lbnRzPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPiAgIFRoaXMgc3BlY2lmaWNhdGlvbiByZWxpZXMgb24gdGhlIGFuYWx5c2lzIGFu
ZCBwcm9maWxpbmcgb2YgVExTPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgVGhp
cyBzcGVjaWZpY2F0aW9uIHJlbGllcyBvbiB0aGUgYW5hbHlzaXMgYW5kIHByb2ZpbGluZyBvZiBU
TFM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGluY2x1ZGVkIGluIFtSRkM2NjE0XSBh
bmQgdGhlIHByb2NlZHVyZXMgZGVzY3JpYmVkIGZvciB0aGUgU1RBUlRUTFM8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBpbmNsdWRlZCBpbiBbUkZDNjYxNF0gYW5kIHRoZSBwcm9j
ZWR1cmVzIGRlc2NyaWJlZCBmb3IgdGhlIFNUQVJUVExTPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij4gICBjb21tYW5kIGluIFtSRkM0NTEzXS48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICBjb21tYW5kIGluIFtSRkM0NTEzXS48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+ICAgV2Ugd291bGQgbGlrZSB0byB0aGFuayBKb2UgVG91Y2ggZm9yIGhpcyBzdWdnZXN0
aW9ucyBhbmQgc3VwcG9ydDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFdlIHdv
dWxkIGxpa2UgdG8gdGhhbmsgSm9lIFRvdWNoIGZvciBoaXMgc3VnZ2VzdGlvbnMgYW5kIHN1cHBv
cnQ8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHJlZ2FyZGluZyB0aGUgVExTIHN0YXJ0
IG1lY2hhbmlzbXMuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgcmVnYXJkaW5n
IHRoZSBUTFMgc3RhcnQgbWVjaGFuaXNtcy48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyIGlkPSJkaWZmMDAzMiI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBUaGFua3MgdG8g
RGFuIEtpbmcgZm9yIHJlbWluZGluZyB0aGUgYXV0aG9ycyBhYm91dCBtYW5hZ2VhYmlsaXR5PC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIFRoYW5rcyB0byBEYW48c3BhbiBjbGFz
cz0iaW5zZXJ0Ij5pZWw8L3NwYW4+IEtpbmcgZm9yIHJlbWluZGluZyB0aGUgYXV0aG9ycyBhYm91
dCBtYW5hZ2VhYmlsaXR5PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBjb25zaWRlcmF0
aW9ucy48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBjb25zaWRlcmF0aW9ucy48
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgVGhhbmtzIHRvIEN5cmlsIE1hcmdh
cmlhIGZvciBzaGVwaGVyZGluZyB0aGlzIGRvY3VtZW50LjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgIFRoYW5rcyB0byBDeXJpbCBNYXJnYXJpYSBmb3Igc2hlcGhlcmRpbmcgdGhp
cyBkb2N1bWVudC48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyIGlkPSJkaWZmMDAzMyI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBUaGFua3MgdG8gRGFuIEZyb3N0IGZvciB0
aGUgUlRHRElSIHJldmlldy48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgVGhh
bmtzIHRvIDxzcGFuIGNsYXNzPSJpbnNlcnQiPkRhdmlkIE1hbmRlbGJlcmcgZm9yIGVhcmx5IFNF
Q0RJUiByZXZpZXcgY29tbWVudHMgYXMgd2VsbDwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJp
bnNlcnQiPiAgIGFzIHJlLXJldmlld2luZyBkdXJpbmcgSUVURiBsYXN0IGNhbGwuPC9zcGFuPjwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJi
bG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imlu
c2VydCI+ICAgVGhhbmtzIHRvPC9zcGFuPiBEYW4gRnJvc3QgZm9yIHRoZSBSVEdESVIgPHNwYW4g
Y2xhc3M9Imluc2VydCI+cmV2aWV3IGFuZCBjb21tZW50cy48L3NwYW4+PC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBj
bGFzcz0iaW5zZXJ0Ij48L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICBUaGFu
a3MgdG8gRGFsZSBXb3JsZXkgZm9yIHRoZSBHZW4tQVJUIHJldmlldyBhbmQgY29tbWVudHMuPC9z
cGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xh
c3M9Imluc2VydCI+ICAgQWxzbyB0aGFua3MgdG8gVGlhbnJhbiBaaG91IGZvciBPUFNESVI8L3Nw
YW4+IHJldmlldy48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyYmxvY2siPiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICA8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIDxzcGFuIGNsYXNz
PSJpbnNlcnQiPlRoYW5rcyB0byBEZWJvcmFoIEJydW5nYXJkIGZvciBiZWluZyB0aGUgcmVzcG9u
c2libGUgQUQgYW5kIGd1aWRpbmc8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2si
PjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4g
ICB0aGUgYXV0aG9ycyBhcyBuZWVkZWQuPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4xMC4gIFJlZmVyZW5jZXM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4x
MC4gIFJlZmVyZW5jZXM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+MTAuMS4gIE5v
cm1hdGl2ZSBSZWZlcmVuY2VzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+MTAuMS4g
IE5vcm1hdGl2ZSBSZWZlcmVuY2VzPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
IFtSRkMyMTE5XSAgQnJhZG5lciwgUy4sICJLZXkgd29yZHMgZm9yIHVzZSBpbiBSRkNzIHRvIElu
ZGljYXRlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgW1JGQzIxMTldICBCcmFk
bmVyLCBTLiwgIktleSB3b3JkcyBmb3IgdXNlIGluIFJGQ3MgdG8gSW5kaWNhdGU8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgUmVxdWlyZW1lbnQgTGV2ZWxzIiwgQkNQ
IDE0LCBSRkMgMjExOSw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAg
ICAgIFJlcXVpcmVtZW50IExldmVscyIsIEJDUCAxNCwgUkZDIDIxMTksPC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgIERPSSAxMC4xNzQ4Ny9SRkMyMTE5LCBNYXJjaCAx
OTk3LDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgRE9JIDEw
LjE3NDg3L1JGQzIxMTksIE1hcmNoIDE5OTcsPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICAgICAgICAgICAgICZsdDtodHRwOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2luZm8vcmZjMjExOSZn
dDsuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICAmbHQ7aHR0
cDovL3d3dy5yZmMtZWRpdG9yLm9yZy9pbmZvL3JmYzIxMTkmZ3Q7LjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0icGFydC0xMiIgY2xhc3M9
ImNoYW5nZSI+PHRkPjwvdGQ+PHRoPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxs
PjxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvcmZjZGlmZiNwYXJ0LTEyIj48ZW0+IHBh
Z2UgMTgsIGxpbmUgMjA8c3BhbiBjbGFzcz0iaGlkZSI+IMK2PC9zcGFuPjwvZW0+PC9hPjwvdGg+
PHRoPiA8L3RoPjx0aD48c21hbGw+c2tpcHBpbmcgdG8gY2hhbmdlIGF0PC9zbWFsbD48YSBocmVm
PSJodHRwczovL3Rvb2xzLmlldGYub3JnL3JmY2RpZmYjcGFydC0xMiI+PGVtPiBwYWdlIDE5LCBs
aW5lIDIwPHNwYW4gY2xhc3M9ImhpZGUiPiDCtjwvc3Bhbj48L2VtPjwvYT48L3RoPjx0ZD48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PiAgICAgICAgICAgICAgIlRyYW5zcG9ydCBMYXllciBTZWN1cml0eSAoVExTKSBFbmNyeXB0aW9u
IGZvciBSQURJVVMiLDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAg
ICAgIlRyYW5zcG9ydCBMYXllciBTZWN1cml0eSAoVExTKSBFbmNyeXB0aW9uIGZvciBSQURJVVMi
LDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICBSRkMgNjYxNCwgRE9J
IDEwLjE3NDg3L1JGQzY2MTQsIE1heSAyMDEyLDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgICAgICAgICAgICAgUkZDIDY2MTQsIERPSSAxMC4xNzQ4Ny9SRkM2NjE0LCBNYXkgMjAx
Miw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgJmx0O2h0dHA6Ly93
d3cucmZjLWVkaXRvci5vcmcvaW5mby9yZmM2NjE0Jmd0Oy48L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICAgICAgICAgICAgICZsdDtodHRwOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2lu
Zm8vcmZjNjYxNCZndDsuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFtSRkM2
OTUyXSAgSmV0aGFuYW5kYW5pLCBNLiwgUGF0ZWwsIEsuLCBhbmQgTC4gWmhlbmcsICJBbmFseXNp
cyBvZjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFtSRkM2OTUyXSAgSmV0aGFu
YW5kYW5pLCBNLiwgUGF0ZWwsIEsuLCBhbmQgTC4gWmhlbmcsICJBbmFseXNpcyBvZjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICBCR1AsIExEUCwgUENFUCwgYW5kIE1T
RFAgSXNzdWVzIEFjY29yZGluZyB0byB0aGUgS2V5aW5nPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgICAgICAgICAgICBCR1AsIExEUCwgUENFUCwgYW5kIE1TRFAgSXNzdWVzIEFj
Y29yZGluZyB0byB0aGUgS2V5aW5nPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAg
ICAgICAgIGFuZCBBdXRoZW50aWNhdGlvbiBmb3IgUm91dGluZyBQcm90b2NvbHMgKEtBUlApIERl
c2lnbjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgYW5kIEF1
dGhlbnRpY2F0aW9uIGZvciBSb3V0aW5nIFByb3RvY29scyAoS0FSUCkgRGVzaWduPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgIEd1aWRlIiwgUkZDIDY5NTIsIERPSSAx
MC4xNzQ4Ny9SRkM2OTUyLCBNYXkgMjAxMyw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICAgICAgICAgICAgIEd1aWRlIiwgUkZDIDY5NTIsIERPSSAxMC4xNzQ4Ny9SRkM2OTUyLCBN
YXkgMjAxMyw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgJmx0O2h0
dHA6Ly93d3cucmZjLWVkaXRvci5vcmcvaW5mby9yZmM2OTUyJmd0Oy48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgICZsdDtodHRwOi8vd3d3LnJmYy1lZGl0b3Iu
b3JnL2luZm8vcmZjNjk1MiZndDsuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMzQiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyYmxvY2siPiAgIDxzcGFuIGNsYXNzPSJpbnNlcnQiPltSRkM3NDIwXSAgS291c2hp
aywgQS4sIFN0ZXBoYW4sIEUuLCBaaGFvLCBRLiwgS2luZywgRC4sIGFuZCBKLjwvc3Bhbj48L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxv
Y2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgICAgICAgICAgICAgSGFyZHdpY2ssICJQYXRoIENv
bXB1dGF0aW9uIEVsZW1lbnQgQ29tbXVuaWNhdGlvbiBQcm90b2NvbDwvc3Bhbj48L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxz
cGFuIGNsYXNzPSJpbnNlcnQiPiAgICAgICAgICAgICAgKFBDRVApIE1hbmFnZW1lbnQgSW5mb3Jt
YXRpb24gQmFzZSAoTUlCKSBNb2R1bGUiLDwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxi
bG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNl
cnQiPiAgICAgICAgICAgICAgUkZDIDc0MjAsIERPSSAxMC4xNzQ4Ny9SRkM3NDIwLCBEZWNlbWJl
ciAyMDE0LDwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgICAgICAgICAgICAg
Jmx0O2h0dHA6Ly93d3cucmZjLWVkaXRvci5vcmcvaW5mby9yZmM3NDIwJmd0Oy48L3NwYW4+PC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJs
b2NrIj4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBbSS1E
LmlldGYtcGNlLXN0YXRlZnVsLXN5bmMtb3B0aW1pemF0aW9uc108L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4gICBbSS1ELmlldGYtcGNlLXN0YXRlZnVsLXN5bmMtb3B0aW1pemF0aW9u
c108L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgQ3JhYmJlLCBFLiwg
TWluZWksIEkuLCBNZWR2ZWQsIEouLCBWYXJnYSwgUi4sIFpoYW5nLCBYLiw8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgIENyYWJiZSwgRS4sIE1pbmVpLCBJLiwg
TWVkdmVkLCBKLiwgVmFyZ2EsIFIuLCBaaGFuZywgWC4sPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij4gICAgICAgICAgICAgIGFuZCBELiBEaG9keSwgIk9wdGltaXphdGlvbnMgb2YgTGFiZWwg
U3dpdGNoZWQgUGF0aCBTdGF0ZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAg
ICAgICAgICAgYW5kIEQuIERob2R5LCAiT3B0aW1pemF0aW9ucyBvZiBMYWJlbCBTd2l0Y2hlZCBQ
YXRoIFN0YXRlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgIFN5bmNo
cm9uaXphdGlvbiBQcm9jZWR1cmVzIGZvciBhIFN0YXRlZnVsIFBDRSIsIGRyYWZ0LTwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgU3luY2hyb25pemF0aW9uIFBy
b2NlZHVyZXMgZm9yIGEgU3RhdGVmdWwgUENFIiwgZHJhZnQtPC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICAgICAgICAgICAgIGlldGYtcGNlLXN0YXRlZnVsLXN5bmMtb3B0aW1pemF0aW9u
cy0xMCAod29yayBpbjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAg
ICAgaWV0Zi1wY2Utc3RhdGVmdWwtc3luYy1vcHRpbWl6YXRpb25zLTEwICh3b3JrIGluPC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgIHByb2dyZXNzKSwgTWFyY2ggMjAx
Ny48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgIHByb2dyZXNz
KSwgTWFyY2ggMjAxNy48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgW0ktRC5p
ZXRmLXBjZS1wY2VwLXlhbmddPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgW0kt
RC5pZXRmLXBjZS1wY2VwLXlhbmddPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAg
ICAgICAgIERob2R5LCBELiwgSGFyZHdpY2ssIEouLCBCZWVyYW0sIFYuLCBhbmQgai48L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgIERob2R5LCBELiwgSGFyZHdp
Y2ssIEouLCBCZWVyYW0sIFYuLCBhbmQgai48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
ICAgICAgICAgICAgamVmZnRhbnRAZ21haWwuY29tLCAiQSBZQU5HIERhdGEgTW9kZWwgZm9yIFBh
dGg8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgIGplZmZ0YW50
QGdtYWlsLmNvbSwgIkEgWUFORyBEYXRhIE1vZGVsIGZvciBQYXRoPC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij4gICAgICAgICAgICAgIENvbXB1dGF0aW9uIEVsZW1lbnQgQ29tbXVuaWNhdGlv
bnMgUHJvdG9jb2wgKFBDRVApIiw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAg
ICAgICAgICAgIENvbXB1dGF0aW9uIEVsZW1lbnQgQ29tbXVuaWNhdGlvbnMgUHJvdG9jb2wgKFBD
RVApIiw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlm
ZjAwMzUiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxibG9jayI+ICAgICAgICAgICAgICA8c3BhbiBjbGFzcz0iZGVsZXRlIj5kcmFm
dC1pZXRmLXBjZS1wY2VwLXlhbmctMDI8L3NwYW4+ICh3b3JrIGluIHByb2dyZXNzKSwgPHNwYW4g
Y2xhc3M9ImRlbGV0ZSI+TWFyY2g8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxv
Y2siPiAgICAgICAgICAgICAgPHNwYW4gY2xhc3M9Imluc2VydCI+ZHJhZnQtaWV0Zi1wY2UtcGNl
cC15YW5nLTA1PC9zcGFuPiAod29yayBpbiBwcm9ncmVzcyksIDxzcGFuIGNsYXNzPSJpbnNlcnQi
Pkp1bmU8L3NwYW4+IDIwMTcuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgICAgICAg
ICAgICAgMjAxNy48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFtJLUQud3UtcGNlLWRucy1wY2UtZGlzY292ZXJ5XTwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFtJLUQud3UtcGNlLWRucy1wY2UtZGlz
Y292ZXJ5XTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICBXdSwgUS4s
IERob2R5LCBELiwgS2luZywgRC4sIExvcGV6LCBELiwgYW5kIEouIFRhbnRzdXJhLDwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgV3UsIFEuLCBEaG9keSwgRC4s
IEtpbmcsIEQuLCBMb3BleiwgRC4sIGFuZCBKLiBUYW50c3VyYSw8L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPiAgICAgICAgICAgICAgIlBhdGggQ29tcHV0YXRpb24gRWxlbWVudCAoUENFKSBE
aXNjb3ZlcnkgdXNpbmcgRG9tYWluPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAg
ICAgICAgICAgICAiUGF0aCBDb21wdXRhdGlvbiBFbGVtZW50IChQQ0UpIERpc2NvdmVyeSB1c2lu
ZyBEb21haW48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgTmFtZSBT
eXN0ZW0oRE5TKSIsIGRyYWZ0LXd1LXBjZS1kbnMtcGNlLWRpc2NvdmVyeS0xMCAod29yazwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgTmFtZSBTeXN0ZW0oRE5T
KSIsIGRyYWZ0LXd1LXBjZS1kbnMtcGNlLWRpc2NvdmVyeS0xMCAod29yazwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICBpbiBwcm9ncmVzcyksIE1hcmNoIDIwMTcuPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICBpbiBwcm9ncmVzcyks
IE1hcmNoIDIwMTcuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFtJLUQud3Ut
cGNlLWRpc2NvdmVyeS1wY2Vwcy1zdXBwb3J0XTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgIFtJLUQud3UtcGNlLWRpc2NvdmVyeS1wY2Vwcy1zdXBwb3J0XTwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICBMb3BleiwgRC4sIFd1LCBRLiwgRGhvZHksIEQu
LCBhbmQgRC4gS2luZywgIklHUCBleHRlbnNpb248L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICAgICAgICAgICAgIExvcGV6LCBELiwgV3UsIFEuLCBEaG9keSwgRC4sIGFuZCBELiBL
aW5nLCAiSUdQIGV4dGVuc2lvbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAg
ICAgICBmb3IgUENFUCBzZWN1cml0eSBjYXBhYmlsaXR5IHN1cHBvcnQgaW4gdGhlIFBDRTwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgZm9yIFBDRVAgc2VjdXJp
dHkgY2FwYWJpbGl0eSBzdXBwb3J0IGluIHRoZSBQQ0U8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CgogICAgIDx0cj48dGQ+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkPjwvdGQ+PC90cj4KICAgICA8dHIgaWQ9ImVu
ZCIgYmdjb2xvcj0iZ3JheSI+PHRoIGNvbHNwYW49IjUiIGFsaWduPSJjZW50ZXIiPiZuYnNwO0Vu
ZCBvZiBjaGFuZ2VzLiAzNSBjaGFuZ2UgYmxvY2tzLiZuYnNwOzwvdGg+PC90cj4KICAgICA8dHIg
Y2xhc3M9InN0YXRzIj48dGQ+PC90ZD48dGg+PGk+ODMgbGluZXMgY2hhbmdlZCBvciBkZWxldGVk
PC9pPjwvdGg+PHRoPjxpPiA8L2k+PC90aD48dGg+PGk+MTEwIGxpbmVzIGNoYW5nZWQgb3IgYWRk
ZWQ8L2k+PC90aD48dGQ+PC90ZD48L3RyPgogICAgIDx0cj48dGQgY29sc3Bhbj0iNSIgYWxpZ249
ImNlbnRlciIgY2xhc3M9InNtYWxsIj48YnI+VGhpcyBodG1sIGRpZmYgd2FzIHByb2R1Y2VkIGJ5
IHJmY2RpZmYgMS40NS4gVGhlIGxhdGVzdCB2ZXJzaW9uIGlzIGF2YWlsYWJsZSBmcm9tIDxhIGhy
ZWY9Imh0dHA6Ly93d3cudG9vbHMuaWV0Zi5vcmcvdG9vbHMvcmZjZGlmZi8iPmh0dHA6Ly90b29s
cy5pZXRmLm9yZy90b29scy9yZmNkaWZmLzwvYT4gPC90ZD48L3RyPgogICA8L3Rib2R5PjwvdGFi
bGU+CiAgIAogICAKPGlmcmFtZSB3aWR0aD0iMCIgaGVpZ2h0PSIwIiBmcmFtZWJvcmRlcj0iMCIg
c3JjPSIuL0RpZmZfIGRyYWZ0LWlldGYtcGNlLXBjZXBzLTE0LnR4dCAtIGRyYWZ0LWlldGYtcGNl
LXBjZXBzLTE1LnR4dF9maWxlcy9zYXZlZF9yZXNvdXJjZS5odG1sIiBpZD0iR0lOR0VSX1NPRlRX
QVJFX2J1YmJsZXNJRnJhbWUiIHNjcm9sbGluZz0ibm8iIHN0eWxlPSJib3JkZXI6IDBweCBzb2xp
ZDsgZGlzcGxheTogbm9uZTsgcG9zaXRpb246IGFic29sdXRlOyB6LWluZGV4OiAyMTQ3NDgzNjQ3
OyBoZWlnaHQ6IDBweDsgd2lkdGg6IDBweDsgYmFja2dyb3VuZC1jb2xvcjogdHJhbnNwYXJlbnQ7
Ij48L2lmcmFtZT48ZGl2IGlkPSJHaW5nZXJXaWRnZXRJbmZvIiBzdHlsZT0iZGlzcGxheTpub25l
OyI+eyJ2ZXJzaW9uIjoiMC4xLjAuNjE4IiwiaXNFeHRlbnNpb24iOnRydWUsImV4dGVuc2lvbk5h
bWUiOiJDaHJvbWUifTwvZGl2PjwvYm9keT48c2NyaXB0PihmdW5jdGlvbigpeyhmdW5jdGlvbiAo
KXsKICAgICAgICAgICAgLy9Ub2RvOmlzIGluamVjdGlvbiBuZWVkZWQgaGVyZT8KICAgICAgICAg
ICAgdmFyIGV2ZW50UmVnaXN0ZXIgPSB7fTsKCiAgICAgICAgICAgIHZhciBmaW5kUmVhY3RQcm9w
ID0gZnVuY3Rpb24oZWxlbSl7CiAgICAgICAgICAgICAgICBmb3IodmFyIGtleSBpbiBlbGVtKXsK
ICAgICAgICAgICAgICAgICAgICBpZihrZXkuaW5kZXhPZigiX19yZWFjdEludGVybmFsSW5zdGFu
Y2UiKT09PTApewogICAgICAgICAgICAgICAgICAgICAgICAvL3ZhciBwID0gbnVsbDsKICAgICAg
ICAgICAgICAgICAgICAgICAgLy9pZihlbGVtW2tleV0ubWVtb2l6ZWRQcm9wcyl7CiAgICAgICAg
ICAgICAgICAgICAgICAgIC8vICAgIHAgPSBlbGVtW2tleV0ubWVtb2l6ZWRQcm9wczsKICAgICAg
ICAgICAgICAgICAgICAgICAgLy99IGVsc2UgaWYoZWxlbVtrZXldLl9jdXJyZW50RWxlbWVudCl7
CiAgICAgICAgICAgICAgICAgICAgICAgIC8vICAgIHAgPSBlbGVtW2tleV0uX2N1cnJlbnRFbGVt
ZW50LnByb3BzCiAgICAgICAgICAgICAgICAgICAgICAgIC8vfQoKICAgICAgICAgICAgICAgICAg
ICAgICAgLy9UT0RPOiByZXBvcnQgaWYgcHJvcHMgaXMgbm90IGZvdW5kIHdpdGggRmFjZWJvb2sg
dmVyc2lvbgogICAgICAgICAgICAgICAgICAgICAgICByZXR1cm4gKGVsZW1ba2V5XS5tZW1vaXpl
ZFByb3BzIHx8IGVsZW1ba2V5XS5fY3VycmVudEVsZW1lbnQucHJvcHMpOwogICAgICAgICAgICAg
ICAgICAgIH0KICAgICAgICAgICAgICAgIH0KICAgICAgICAgICAgICAgIHJldHVybiBudWxsOwog
ICAgICAgICAgICB9OwoKICAgICAgICAgICAgZG9jdW1lbnQuYWRkRXZlbnRMaXN0ZW5lcigiZ2lu
Z2VyTW9kdWxlLWV2ZW50RW1pdHRlci1yZWFjdC1maXJlIixmdW5jdGlvbihlKXsKICAgICAgICAg
ICAgICAgIC8vY29uc29sZS5sb2coImZpcmluZyIsIGUpOwogICAgICAgICAgICAgICAgdmFyIHJl
YWN0UHJvcHMgPSBmaW5kUmVhY3RQcm9wKGRvY3VtZW50LmFjdGl2ZUVsZW1lbnQpOwogICAgICAg
ICAgICAgICAgdmFyIGV2ZW50TmFtZSA9IGUuZGV0YWlsLmV2ZW50OwogICAgICAgICAgICAgICAg
dmFyIGV2ZW50UGFyYW1zID0gZS5kZXRhaWwucGFyYW1zIHx8IHt9OwogICAgICAgICAgICAgICAg
ZXZlbnRQYXJhbXMucHJldmVudERlZmF1bHQgPSBmdW5jdGlvbigpe307CiAgICAgICAgICAgICAg
ICBpZihyZWFjdFByb3BzICYmIGV2ZW50TmFtZSkgewogICAgICAgICAgICAgICAgICAgIHJlYWN0
UHJvcHNbZXZlbnROYW1lXShldmVudFBhcmFtcyk7CiAgICAgICAgICAgICAgICB9CiAgICAgICAg
ICAgIH0pOwogICAgICAgICAgICBkb2N1bWVudC5hZGRFdmVudExpc3RlbmVyKCJnaW5nZXJNb2R1
bGUtZXZlbnRFbWl0dGVyLW9uc2VsZWN0IixmdW5jdGlvbihlKXsKICAgICAgICAgICAgICAgIHZh
ciByZWFjdFByb3BzID0gZmluZFJlYWN0UHJvcChkb2N1bWVudC5hY3RpdmVFbGVtZW50KTsKICAg
ICAgICAgICAgICAgIC8vdHJpZ2dlcigic2VsZWN0Iik7CiAgICAgICAgICAgICAgICBpZihyZWFj
dFByb3BzKSB7CiAgICAgICAgICAgICAgICAgICAgcmVhY3RQcm9wcy5vblNlbGVjdCgpOwogICAg
ICAgICAgICAgICAgfQogICAgICAgICAgICB9KTsKICAgICAgICAgICAgZG9jdW1lbnQuYWRkRXZl
bnRMaXN0ZW5lcigiZ2luZ2VyTW9kdWxlLWV2ZW50RW1pdHRlci1vbnBhc3RlIixmdW5jdGlvbihl
KXsKICAgICAgICAgICAgICAgIHZhciByZWFjdFByb3BzID0gZmluZFJlYWN0UHJvcChkb2N1bWVu
dC5hY3RpdmVFbGVtZW50KTsKICAgICAgICAgICAgICAgIHZhciBwYXN0ZU9iaiA9IHsKICAgICAg
ICAgICAgICAgICAgICBkZWZhdWx0UHJldmVudGVkOiBmYWxzZSwKICAgICAgICAgICAgICAgICAg
ICB0YXJnZXQ6IGRvY3VtZW50LmFjdGl2ZUVsZW1lbnQsCiAgICAgICAgICAgICAgICAgICAgcHJl
dmVudERlZmF1bHQ6IGZ1bmN0aW9uKCkge30sCiAgICAgICAgICAgICAgICAgICAgY2xpcGJvYXJk
RGF0YSA6IHsKICAgICAgICAgICAgICAgICAgICAgICAgZ2V0RGF0YTogZnVuY3Rpb24gKCkgewog
ICAgICAgICAgICAgICAgICAgICAgICAgICAgcmV0dXJuIGUuZGV0YWlsIHx8ICIiOwogICAgICAg
ICAgICAgICAgICAgICAgICB9LAogICAgICAgICAgICAgICAgICAgICAgICBpdGVtczogWyJ0ZXh0
L3BsYWluIl0KICAgICAgICAgICAgICAgICAgICB9CiAgICAgICAgICAgICAgICB9OwogICAgICAg
ICAgICAgICAgLy90cmlnZ2VyKCJwYXN0ZSIscGFzdGVPYmopOwogICAgICAgICAgICAgICAgaWYo
cmVhY3RQcm9wcykgewogICAgICAgICAgICAgICAgICAgIHJlYWN0UHJvcHMub25QYXN0ZShwYXN0
ZU9iaik7CiAgICAgICAgICAgICAgICB9CiAgICAgICAgICAgIH0pOwoKICAgICAgICAgICAgdmFy
IHRyaWdnZXIgPSBmdW5jdGlvbihldmVudE5hbWUsZGF0YSl7CiAgICAgICAgICAgICAgICBpZigh
ZXZlbnRSZWdpc3RlcltldmVudE5hbWVdKSByZXR1cm47CiAgICAgICAgICAgICAgICBmb3IodmFy
IGkgPSAwOyBpPGV2ZW50UmVnaXN0ZXJbZXZlbnROYW1lXS5sZW5ndGg7IGkrKyl7CiAgICAgICAg
ICAgICAgICAgICAgdmFyIGxpc3RlbmVyID0gZXZlbnRSZWdpc3RlcltldmVudE5hbWVdW2ldOwog
ICAgICAgICAgICAgICAgICAgIGxpc3RlbmVyKG5ldyBDdXN0b21FdmVudChldmVudE5hbWUpLGRh
dGEpOwogICAgICAgICAgICAgICAgfQogICAgICAgICAgICB9OwoKICAgICAgICAgICAgdmFyIG5h
dGl2ZUV2ZW50TGlzdGVuZXIgPSBkb2N1bWVudC5hZGRFdmVudExpc3RlbmVyLmJpbmQoZG9jdW1l
bnQpOwogICAgICAgICAgICBkb2N1bWVudC5hZGRFdmVudExpc3RlbmVyID0gZnVuY3Rpb24oZXZl
bnROYW1lLCBjYWxsYmFjaywgb3B0aW9ucykgewogICAgICAgICAgICAgICAgY29uc29sZS5sb2co
InJlZ2lzdGVyaW5nIGV2ZW50IixldmVudE5hbWUpOwogICAgICAgICAgICAgICAgdmFyIGV2ZW50
UmVnaXN0ZXJJdGVtID0gZXZlbnRSZWdpc3RlcltldmVudE5hbWVdIHx8IFtdOwogICAgICAgICAg
ICAgICAgZXZlbnRSZWdpc3Rlckl0ZW0ucHVzaChjYWxsYmFjayk7CiAgICAgICAgICAgICAgICBl
dmVudFJlZ2lzdGVyW2V2ZW50TmFtZV0gPSBldmVudFJlZ2lzdGVySXRlbTsKICAgICAgICAgICAg
ICAgIG5hdGl2ZUV2ZW50TGlzdGVuZXIoZXZlbnROYW1lLCBjYWxsYmFjaywgb3B0aW9ucyk7CiAg
ICAgICAgICAgIH07CgogICAgICAgIH0pKCkgfSkoKTwvc2NyaXB0PjwvaHRtbD4=

--_003_23CE718903A838468A8B325B80962F9B8CB95DF7blreml501mbb_--



From nobody Fri Jul 28 05:12:07 2017
Return-Path: <lhotka@nic.cz>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BB39131C2B; Fri, 28 Jul 2017 05:12:00 -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] 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 K5bS5eO8mFtD; Fri, 28 Jul 2017 05:11:57 -0700 (PDT)
Received: from trail.lhotka.name (trail.lhotka.name [77.48.224.143]) by ietfa.amsl.com (Postfix) with ESMTP id 88F3712783A; Fri, 28 Jul 2017 05:11:56 -0700 (PDT)
Received: by trail.lhotka.name (Postfix, from userid 109) id 8130D1820E71; Fri, 28 Jul 2017 14:13:38 +0200 (CEST)
Received: from localhost (unknown [195.113.220.110]) by trail.lhotka.name (Postfix) with ESMTPSA id 62A521820E6F; Fri, 28 Jul 2017 14:13:36 +0200 (CEST)
From: Ladislav Lhotka <lhotka@nic.cz>
To: Alexander Clemm <ludwig@clemm.org>, 'Susan Hares' <shares@ndzh.com>, yang-doctors@ietf.org
Cc: i2rs@ietf.org, ietf@ietf.org, draft-ietf-i2rs-yang-l3-topology.all@ietf.org
Subject: RE: [i2rs] Yangdoctors early review of draft-ietf-i2rs-yang-l3-topology-10
In-Reply-To: <00d801d30620$9bdabc40$d39034c0$@clemm.org>
References: <150105874813.26401.2245891817517041568@ietfa.amsl.com> <00a001d3060c$46a59fb0$d3f0df10$@ndzh.com> <00d801d30620$9bdabc40$d39034c0$@clemm.org>
Date: Fri, 28 Jul 2017 14:11:51 +0200
Message-ID: <m2inic3gmw.fsf@birdie.labs.nic.cz>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-FTkHTL-0Xmkvy5UYMkoba6NZFE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 12:12:01 -0000

Hi Alex,

Alexander Clemm <ludwig@clemm.org> writes:

> Hello Lada,
>
> Thank you very much for your detailed review.   Will plan to update the
> draft over the coming two weeks or so (as I may be taking a few days off).
> Most of the comments should be reasonably straightforward to accommodate.
> However, I do have comments regarding #1 and #4.  
>
> On #1 (presence containers vs identities).  Unless you feel very strongly
> about this, we would prefer to keep this as is, not revert to identities.
> This node is subject to quite a few "when" condition checks (when it comes
> to topology-specific augmentations) which are very simple this way.

It means that the type info can change at run time, right? Then it
probably needs some more explanation and examples because at this level
the use cases are not very clear.

> Changing this makes the conditions more complex and has ripple effects
> through dependant modules.  Note that a topology can have multiple types; a
> single leaf with identity would not be sufficient, it would need to be a
> leaf-list.  On #4, (URIs) we had multiple discussions in the past but have
> always come back to that; I would prefer to not change this at this point.
> Please note that the model is implemented and deployed today, e.g. in Open
> Daylight.

Does OpenDaylight UI expose human users to these URIs?

Lada

>  
> Thanks
> --- Alex
>
> -----Original Message-----
> From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Susan Hares
> Sent: Wednesday, July 26, 2017 5:40 AM
> To: 'Ladislav Lhotka' <lhotka@nic.cz>; yang-doctors@ietf.org
> Cc: i2rs@ietf.org; ietf@ietf.org;
> draft-ietf-i2rs-yang-l3-topology.all@ietf.org
> Subject: Re: [i2rs] Yangdoctors early review of
> draft-ietf-i2rs-yang-l3-topology-10
>
> Lada:
>
> Thank you for reviewing the draft with such a careful eye to now and the
> future.  Please look for a response from Alex within a few days, .
>
> Sue 
>
> -----Original Message-----
> From: Ladislav Lhotka [mailto:lhotka@nic.cz] 
> Sent: Wednesday, July 26, 2017 4:46 AM
> To: yang-doctors@ietf.org
> Cc: i2rs@ietf.org; ietf@ietf.org;
> draft-ietf-i2rs-yang-l3-topology.all@ietf.org
> Subject: Yangdoctors early review of draft-ietf-i2rs-yang-l3-topology-10
>
> Reviewer: Ladislav Lhotka
> Review result: Ready with Issues
>
> This YANG module and I-D belong to an extensible suite of data models
> addressing multi-layered network topology. It is an interesting, even if
> somewhat atypical, application of YANG.
>
> The entire network topology suite seems well thought out, and it is apparent
> that the document has already undergone several rounds of discussions and
> iterations. It is also positive that the document deals with possible
> overlaps with other YANG modules such as ietf-interfaces or ietf-hardware.
> Of course, an ultimate acid test of the network topology suite will come
> with applications to real-life network.
>
> My review below raises several issues that need to be addressed (especially
> #1). Some of them are related to design decisions described in
> draft-ietf-i2rs-yang-network-topo. Apart from that, I believe the document
> is ready to be published.
>
> *** Comments to draft-ietf-i2rs-yang-network-topo-14:
>
> 1. With YANG 1.1, the network type information looks like a perfect
>    candidate for identities (with multiple inheritance). Instead, it
>    is modelled with presence containers, which is cumbersome and
>    redundant. I don't see any reasons for doing so, if there are any,
>    then they should be explained in sec. 4.4.8.
>
> 2. The document defines "supporting network" and then says "A
>    supporting network is in effect an underlay network." In the
>    subsequent text "underlay network" is used almost exclusively. So
>    perhaps the term "supporting network" should be dropped altogether?
>
> 3. The text should be better aligned with the terminology of
>    draft-ietf-netmod-revised-datastores. In particular,
>    "system-controlled" should be used instead of "server-provided".
>
> 4. Is it necessary to use URIs for identifying all objects in the
>    data model. URIs are difficult to use, so applications are likely
>    to introduce some abbreviations and keep an internal mapping, which
>    could cause problems, e.g. when matching objects in notifications
>    with a GUI representation. In my view, it should be sufficient to
>    use URIs for network-id and plain strings for other IDs, because
>    all other objects are encapsulated inside a network, so their name
>    conflicts shouldn't matter.
>
> *** Comments to draft-ietf-i2rs-yang-l3-topology-10
>
> 5. The type of "router-id" should be "yang:dotted-quad" and not
>    "inet:ip-address" because the latter means both IPv4 and IPv6
>    address, possibly also with a zone index.
>
> 6. Both prefix and link attributes include the "metric" parameter. It
>    should be explained what they mean. In the context of ietf-routing
>    the option of including "metric" as a general route parameter was
>    discussed and finally rejected because different routing protocol use
>    metrics with different semantics and properties. I wonder if it is
>    the same case here. 
>
> *** Formal issues and typos
>
> 7. Both documents should refer to draft-ietf-netmod-yang-tree-diagrams
>    rather than describe the notation of tree diagrams in the text.
>
> 8. Sec. 7 in draft-ietf-i2rs-yang-l3-topology-10: s/moodel/model/
>
>
>
> _______________________________________________
> i2rs mailing list
> i2rs@ietf.org
> https://www.ietf.org/mailman/listinfo/i2rs
>

-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67


From nobody Fri Jul 28 07:27:52 2017
Return-Path: <tjw.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BA21129A92 for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 07:27:51 -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, FREEMAIL_FROM=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 wQ1Oa5xge2sn for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 07:27:49 -0700 (PDT)
Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d:c09::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 57EF3131C8C for <ietf@ietf.org>; Fri, 28 Jul 2017 07:27:49 -0700 (PDT)
Received: by mail-qk0-x231.google.com with SMTP id u139so58023568qka.1 for <ietf@ietf.org>; Fri, 28 Jul 2017 07:27:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=hhywq2xvU/Oyt2bPhzWQwrIl6WKepWJlwwonFwnsZdU=; b=E8CCHtIfxQ0uOhHc6nTh/Gk+BUF4yJcnjKYTrenCOdGRQRcaj8ksnihEAVYiyV2rfM uZ/nvQuyiFYi2Sc3vkaZDyFzJ//YO7nY2r8XV9It1/ppcTTKxRwgNxQiQygGAEZTDH7C aUL5WNGZY0GSlQ+LzW92XpZ65Q/16T1Gf9z9O0Re49R72R3AFmkZranxvRltMbPyoHnO mRDXfiyuYu2vtu+qyDcVkQbOI/cXZhNaX2bkaYmOvmRKEGEhF59jMRaD/dwv0YqefSpx OrZUKvTy1OKdpwtp8W42GAc+qadFWs2pOussmfJ9BWlZssYA/nIXa+zmpfUIY0h0d8KW z9Sw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=hhywq2xvU/Oyt2bPhzWQwrIl6WKepWJlwwonFwnsZdU=; b=a3EXIYEewhKCnH/yGpoU/mwQJrlCbPp6NBhXO0r3h++a2+fv5SXb7pEl5oZoUGtrq0 Ma/MgZCYsBokRd6f06e58U55tcTQTH9z5Vq3TdmkRkJhuswVoBs4Nta4J4FchyPWI2CG ZLcZdi1wFpazYuxLK7Gs+49uLhbY1av9AYgBZ7w3c6X9vH3kkzgXw90EEJ51tl4cQIIB JKuCh0KdOQWHyq3m48ysFjzF4mu+oZlKDIJw/o96UrKU1V3RBtAjGjv5PXei1N4I+QxG uz2OjwS2UV3PVk+TfqS2lWQZUhb9CiMW9TVTPFJ6RlOmP6QUGMU7HjHYdrJhzR7WmKmz bKxw==
X-Gm-Message-State: AIVw1136DoF7lDkFNuLDft8bH/Q1MkBVUqTgdSuK02x7JlyRrvLZd6Sl HnrjW/oIohJmkyub
X-Received: by 10.55.49.18 with SMTP id x18mr9822013qkx.61.1501252068227; Fri, 28 Jul 2017 07:27:48 -0700 (PDT)
Received: from twicinski-ltm1.internal.salesforce.com ([204.14.236.152]) by smtp.googlemail.com with ESMTPSA id 59sm15532230qtc.35.2017.07.28.07.27.46 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 Jul 2017 07:27:47 -0700 (PDT)
Subject: Re: Announcement on IETF 100 Hotel Reservations
To: ietf@ietf.org
References: <150108971740.23120.257371533321943899.idtracker@ietfa.amsl.com> <EF2F4195-A97F-46CB-B2D2-DB7A5E11874F@gmail.com> <100a6ef1-1b1a-9123-398f-1883a167c5e1@comcast.net> <alpine.OSX.2.01.1707261133380.78919@rabdullah.local>
From: Tim Wicinski <tjw.ietf@gmail.com>
Message-ID: <0d19da56-b55d-79b9-c9d1-464e5f561742@gmail.com>
Date: Fri, 28 Jul 2017 10:27:45 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <alpine.OSX.2.01.1707261133380.78919@rabdullah.local>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oPiztVA_gpQIrRkoWEfiQbjqpYM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 14:27:51 -0000

As someone who travels regularly to Singapore for my employer, I agree 
with everything Ole says.  And the public transit system is staffed by 
super helpful folks who can assist in navigating the fare system. (just 
don't hold hands on the metro - I saw young couples scolded for such 
handholding).

I've never been hassled for any of the things I've brought in - 
medicine, electronics, and even gum.

On 7/26/17 2:47 PM, Ole Jacobsen wrote:
> 
> As a relatively frequent visitor to Singapore, let me just add:
> 
> * There are LOTS of hotels in town, you can most likely find one in
>    your favorite price range and hotel group. Hilton, Hyatt, Marriott,
>    Intercontinental, etc, all can be found in Singapore.
> 
> * Singapore has a very comprehensive public transport system:
> 
> https://www.lta.gov.sg/content/ltaweb/en/public-transport/mrt-and-lrt-trains/train-system-map.html
> 
> * If you arrive very late and you are tired, I'd recommend taking a
>    taxi to your hotel. The rates are not very high compared to many
>    places in the world, even at the "night tariff."
> 
> * The ride from Changi to the center of Singapore takes about 20
>    minutes.
> 
> * It is always hot and humid in Singapore, see:
> 
> http://www.holiday-weather.com/singapore/averages/
> 
> 
> Ole
> 
> 
> Ole J. Jacobsen
> Editor and Publisher
> The Internet Protocol Journal
> Office:  +1 415-550-9433
> Cell:    +1 415-370-4628
> Docomo:  090 3337-9311
> Web: protocoljournal.org
> E-mail: olejacobsen@me.com
> 
> 
> 
> 


From nobody Fri Jul 28 07:43:55 2017
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33815131C39 for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 07:43:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-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=yitter.info header.b=LxJ7WpPq; dkim=pass (1024-bit key) header.d=yitter.info header.b=a9NZH2bf
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 moY-S5C8u-HL for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 07:43:51 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 999E4129ACD for <ietf@ietf.org>; Fri, 28 Jul 2017 07:43:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id C7F0ABE6F3 for <ietf@ietf.org>; Fri, 28 Jul 2017 14:43:20 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1501253000; bh=taweuMM5ZOa6YxextTw62dOMivfzYuM4ZFTD1IKtRus=; h=Date:From:To:Subject:References:In-Reply-To:From; b=LxJ7WpPqpZwaDBVERBd1GJI1S8ARYDqizX8DE+Ng02pVje3dD5NivC6NS4tsRn9O3 bTWPT7giksDvhjVywaAS2VVEyRluKdva6tdckQLr7kQafYUqgR3n2or5xjPs1pzaUs 5+kYu7/iSUfxyQ9CJSo3WvuJo2Hrenqo4Sl9V0Yw=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xumOFe-zfLGx for <ietf@ietf.org>; Fri, 28 Jul 2017 14:43:19 +0000 (UTC)
Date: Fri, 28 Jul 2017 10:43:17 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1501252999; bh=taweuMM5ZOa6YxextTw62dOMivfzYuM4ZFTD1IKtRus=; h=Date:From:To:Subject:References:In-Reply-To:From; b=a9NZH2bf2Yqp/xc1zGrZJrtteJxj9U8jcppHEzsUqrCspcIPyQE/gfz6EIEuisQu8 +otJ95qZo/q2+R16l2E2dDN10kjrPpj5bIzYIXEzLrFclaRfI8nirWJtwG68R32XYh R1fiugJeq6Vbvwab6eF8HmrkpmdskyLLkLmGo0m8=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Announcement on IETF 100 Hotel Reservations
Message-ID: <20170728144317.k3do5nul22nlc6pf@mx4.yitter.info>
References: <150108971740.23120.257371533321943899.idtracker@ietfa.amsl.com> <EF2F4195-A97F-46CB-B2D2-DB7A5E11874F@gmail.com> <100a6ef1-1b1a-9123-398f-1883a167c5e1@comcast.net> <alpine.OSX.2.01.1707261133380.78919@rabdullah.local> <0d19da56-b55d-79b9-c9d1-464e5f561742@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0d19da56-b55d-79b9-c9d1-464e5f561742@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bAxFWtZwolWSvm3Upcv-WcQeJ1c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 14:43:53 -0000

Hi,

On Fri, Jul 28, 2017 at 10:27:45AM -0400, Tim Wicinski wrote:
 
> I've never been hassled for any of the things I've brought in - medicine,
> electronics, and even gum.

I haven't visited as often as either of you, I think, but I also found
the entry to be mostly painless.  At the same time, however, I think
we need to be quite careful in what we are saying.  We are encroaching
again on the same controversy that caused difficulty when the site was
announced.

There are two ways to evaluate risk in respect of a jurisdiction's
rules.  One is to take the literal text of the rules and assume that
those rules are in effect.  The other is to attend to what mostly
happens in the jurisdiction under normal circumstances, and treat that
as the actual, practical risk in the jurisdiction.

The second approach has the natural appeal that it is pragmatic, and I
am prepared to believe that most of the people involved in this sort
of travel make that kind of judgement all the time.

But the problem with it for an organization like ours that is
travelling _en masse_ to a location is that the rules remain in place.
They are therefore available to be imposed on any individual if
circumstances emerge such that authorities would like to do that.
That Singaporeans are themselves apparently mostly disinclined to
enforce many of the official rules capriciously is certainly good news
(I can think of one country we travelled to in the recent past where
that appears not to be the case).

Circumstances change in countries, sometimes in surprising ways.
Therefore, IETF participants who are going to attend IETF 100 should
be aware that the rules are strict and published.  Each traveller
should weigh the reports of non-enforcement against the risk that the
rule could be enforced in one's own case.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Fri Jul 28 07:44:46 2017
Return-Path: <aallen@blackberry.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FC51132005 for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 07:44:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, 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 sK9nCKHgslrI for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 07:44:43 -0700 (PDT)
Received: from smtp-p01.blackberry.com (smtp-p01.blackberry.com [208.65.78.88]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DEB0129ACD for <ietf@ietf.org>; Fri, 28 Jul 2017 07:44:43 -0700 (PDT)
Received: from xct105cnc.rim.net ([10.65.161.205]) by mhs211cnc.rim.net with ESMTP/TLS/DHE-RSA-AES256-SHA; 28 Jul 2017 10:44:42 -0400
Received: from XCT115CNC.rim.net (10.65.161.215) by XCT105CNC.rim.net (10.65.161.205) with Microsoft SMTP Server (TLS) id 14.3.319.2; Fri, 28 Jul 2017 10:44:42 -0400
Received: from XMB122CNC.rim.net ([fe80::28c6:fa1c:91c6:2e23]) by XCT115CNC.rim.net ([::1]) with mapi id 14.03.0319.002; Fri, 28 Jul 2017 10:44:41 -0400
From: Andrew Allen <aallen@blackberry.com>
To: Tim Wicinski <tjw.ietf@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Announcement on IETF 100 Hotel Reservations
Thread-Topic: Announcement on IETF 100 Hotel Reservations
Thread-Index: AQHTBjO3c69kR3yqt0eCJgC9FXzEzKJmpRsAgAAMpACAAAQ3gIAC3AyA//+/vCA=
Date: Fri, 28 Jul 2017 14:44:40 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD233A998284@XMB122CNC.rim.net>
References: <150108971740.23120.257371533321943899.idtracker@ietfa.amsl.com> <EF2F4195-A97F-46CB-B2D2-DB7A5E11874F@gmail.com> <100a6ef1-1b1a-9123-398f-1883a167c5e1@comcast.net> <alpine.OSX.2.01.1707261133380.78919@rabdullah.local> <0d19da56-b55d-79b9-c9d1-464e5f561742@gmail.com>
In-Reply-To: <0d19da56-b55d-79b9-c9d1-464e5f561742@gmail.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.65.160.252]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XquyUDuGYJdSBLvPmD0HIOT6lyc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 14:44:45 -0000

SXQncyB2ZXJ5IGNsb3NlIHRvIHRoZSBlcXVhdG9yIC0gYWJvdXQgMS4zIGRlZ3JlZXMgTiBsYXRp
dHVkZSANCg0KT24gNy8yNi8xNyAyOjQ3IFBNLCBPbGUgSmFjb2JzZW4gd3JvdGU6DQo+IA0KPiAN
Cj4gKiBJdCBpcyBhbHdheXMgaG90IGFuZCBodW1pZCBpbiBTaW5nYXBvcmUsIHNlZToNCj4gDQo+
IGh0dHA6Ly93d3cuaG9saWRheS13ZWF0aGVyLmNvbS9zaW5nYXBvcmUvYXZlcmFnZXMvDQo+IA0K
DQo=


From nobody Fri Jul 28 09:05:25 2017
Return-Path: <linuxwolf+ietf@outer-planes.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 288A6131CE7 for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 09:05:13 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outer-planes-net.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 mEAzlWaCn7bv for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 09:05:11 -0700 (PDT)
Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002: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 BDD0E131FF1 for <ietf@ietf.org>; Fri, 28 Jul 2017 09:05:08 -0700 (PDT)
Received: by mail-yw0-x231.google.com with SMTP id l82so68009406ywc.2 for <ietf@ietf.org>; Fri, 28 Jul 2017 09:05:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outer-planes-net.20150623.gappssmtp.com; s=20150623; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to; bh=/XT1NiuGZE2tfih6Fzg8BsQWYlWwA+rjHRnSy5L+KmY=; b=t3goYSFtkeGOfTnKr+lXWVjZM00ph+Pbr8eR96u4Xf7M+HpNC0clGnZzCuVah/2tPO bjkcWsGnlDczun4J4OoRTZx2dslWltJVa6zcHIauuv6sUIBPCHp30G8GkPkPl7vP56Bm uVOOBnsDv7qTeX9u7xXWf4kTh4apu0nPeM80rrsZHnNtqEydtdYHc1FSuJ8niEZeEacO A/6wlrysr0zDMpmUngweBmqlwTg8zKak56LAsW6GRbbIexihg5CGKEvhLKcqihZm5JbM 0Joy8CCBsNlFPttmVuIwKCcA0A26Wm+UnONOZeQNzSczQFEyucbHdo00p05pbAgT9cbQ xH7w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to; bh=/XT1NiuGZE2tfih6Fzg8BsQWYlWwA+rjHRnSy5L+KmY=; b=bcBhayoUKhwu7E8JJOcv46LSl+kfU+hockSTPyuwWN8cTRfH1WD+W0Y960pzdY3gm9 f51I2dd/VOKLdtxhQOkbvFmnnwN3nqatPGoMQ1tTADc7fJctKuKd1w+JoHzihi91LHl4 bI1aA3tmeT6PihvREpH84VBWL0meyoTXXPmBgv2vtGVj9oYeMGsUtuV8Ms1IGUSrAjOc 6Tk/p6gTzFBtk0/LNAV8NbNC6O6xkLCA4FDiIxEB48Yw3wkyxLgz+Fp0gNDL1FyJfg46 /9pppp0ewtSdz51gjq46w8EJLE5SVGKgTJezhN72toDzGG6HziyXorchVePENdxwLdQA n87g==
X-Gm-Message-State: AIVw110HKM5ELjJmN2iGay6zdnaHaq6LpgUP87nILnp35QDgvaML8dcH +acqEuwmbqeRq47u
X-Received: by 10.129.108.17 with SMTP id h17mr7040897ywc.447.1501257907696; Fri, 28 Jul 2017 09:05:07 -0700 (PDT)
Received: from [10.6.23.170] ([128.177.113.102]) by smtp.gmail.com with ESMTPSA id u196sm3337355ywf.64.2017.07.28.09.05.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 Jul 2017 09:05:07 -0700 (PDT)
Sender: Matthew Miller <linuxwolf@outer-planes.net>
Subject: Re: [Curdle] Genart last call review of draft-ietf-curdle-ssh-ext-info-10
To: denis bider <denisbider.ietf@gmail.com>
Cc: gen-art@ietf.org, curdle <curdle@ietf.org>, ietf@ietf.org, draft-ietf-curdle-ssh-ext-info.all@ietf.org
References: <150093015937.32021.12465797358778837950@ietfa.amsl.com> <CADPMZDCE+m+_QA7s6vdFOw-7uF4cfV4g8_U07fb-Ydur30OR5g@mail.gmail.com> <1eef6165-9b5b-c354-dffe-5df1e98098fa@outer-planes.net> <CADPMZDDjQoHc9yoYb7sSTa2r7e71DSMdqQ7OEH7neWU0ygKzNw@mail.gmail.com> <CADPMZDC7=BzfohUCmYbQR8LzqY8GauDeGrtJOo97M00attP8Ag@mail.gmail.com>
From: "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>
Message-ID: <0406a3c8-0400-b0b5-2b09-93bb5078cb0a@outer-planes.net>
Date: Fri, 28 Jul 2017 10:05:04 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:55.0) Gecko/20100101 Thunderbird/55.0
MIME-Version: 1.0
In-Reply-To: <CADPMZDC7=BzfohUCmYbQR8LzqY8GauDeGrtJOo97M00attP8Ag@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="aJCcI3oc7MIhLwqvcFkJjimEiMODAcsw1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/78SQegC5ZTmhFxi0ezUKeOOKP54>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 16:05:13 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--aJCcI3oc7MIhLwqvcFkJjimEiMODAcsw1
Content-Type: multipart/mixed; boundary="P46VhQpSaqIMfmUxSVWPmgGMJph8nW77i";
 protected-headers="v1"
From: "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>
To: denis bider <denisbider.ietf@gmail.com>
Cc: gen-art@ietf.org, curdle <curdle@ietf.org>, ietf@ietf.org,
 draft-ietf-curdle-ssh-ext-info.all@ietf.org
Message-ID: <0406a3c8-0400-b0b5-2b09-93bb5078cb0a@outer-planes.net>
Subject: Re: [Curdle] Genart last call review of
 draft-ietf-curdle-ssh-ext-info-10
References: <150093015937.32021.12465797358778837950@ietfa.amsl.com>
 <CADPMZDCE+m+_QA7s6vdFOw-7uF4cfV4g8_U07fb-Ydur30OR5g@mail.gmail.com>
 <1eef6165-9b5b-c354-dffe-5df1e98098fa@outer-planes.net>
 <CADPMZDDjQoHc9yoYb7sSTa2r7e71DSMdqQ7OEH7neWU0ygKzNw@mail.gmail.com>
 <CADPMZDC7=BzfohUCmYbQR8LzqY8GauDeGrtJOo97M00attP8Ag@mail.gmail.com>
In-Reply-To: <CADPMZDC7=BzfohUCmYbQR8LzqY8GauDeGrtJOo97M00attP8Ag@mail.gmail.com>

--P46VhQpSaqIMfmUxSVWPmgGMJph8nW77i
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Hello Denis,

I had other things I needed to attend to, and could not respond until
now.  I think this new text is much improved, thank you.

I find the guidance for an extension's specification to be more vague
than I like, but I'm maybe that's effectively addressed with the IANA
extension table's registration requirements.


Thanks again,

- m&m

Matthew A. Miller

On 17/07/28 00:52, denis bider wrote:
> OK, I have uploaded version -11 with language as follows:
>=20
> "An extension MAY dictate, where it is specified, that in order to take=

> effect, both parties must include it in their EXT_INFO; or it MAY be
> sufficient that only one party includes it; or other rules MAY be
> specified. The relative order in which extensions appear in an EXT_INFO=

> message MUST be ignored by default; but an extension MAY specify that
> the order matters for that extension, in a specific way."
>=20
> This seems clearer to me than it was in -10. If you still see room for
> improvement, let me know!
>=20
>=20
> On Wed, Jul 26, 2017 at 9:09 PM, denis bider <denisbider.ietf@gmail.com=

> <mailto:denisbider.ietf@gmail.com>> wrote:
>=20
>     Hello Matthew,
>=20
>     I'm not sure if I know how to address this better than with the
>     language so far proposed.
>=20
>     Perhaps one choice would be to simply remove this paragraph.
>     However, the reason it was added was because an earlier reviewer
>     (I'm not sure of the details at this time) raised the question abou=
t
>     whether extension negotiation works like it does for algorithm
>     lists, such as in e.g. SSH_MSG_KEXINIT. In that case, multiple
>     algorithms are enumerated by both sides, and only one is chosen tha=
t
>     (1) is enumerated by both sides, and (2) is the first of those to b=
e
>     enumerated by the client. The main purpose of this paragraph has
>     been to clarify that extension negotiation does not work that way i=
n
>     EXT_INFO.
>=20
>     What language would you propose? Is there some simple language that=

>     would do? How about this?
>=20
>     "An extension may dictate, where it is specified, that in order to
>     take effect, both parties must include it in its EXT_INFO; or it ma=
y
>     be sufficient that only one party does; or more complex rules may b=
e
>     specified."
>=20
>=20
>     On Wed, Jul 26, 2017 at 1:28 PM, Matthew A. Miller
>     <linuxwolf+ietf@outer-planes.net
>     <mailto:linuxwolf+ietf@outer-planes.net>> wrote:
>=20
>         Thanks very much for the response, Denis.
>=20
>         I think I understand the intent here, but I'm not sure this new=

>         text is
>         enough to mitigate some future conflict.=C2=A0 I'm also concern=
ed that it
>         completely ignores the one-party extensions (e.g., an extension=

>         included
>         in the EXT_INFO by only the client or the server, but not both)=
, and
>         what the impact is holistically.=C2=A0 Looking at the one-party=

>         extensions
>         defined herein, I can't see how their order matters; but does
>         that mean
>         the order will never matter?
>=20
>         In writing this reply, I wondered if it's better for the order
>         to always
>         be irrelevant; an implementation might be allowed to hint its
>         preferred
>         order in the EXT_INFO, but implementations are still free to do=

>         whatever
>         makes sense to them within the bounds of the relevant extension=

>         definitions.=C2=A0 If an extension ought to take precedence ove=
r another,
>         make it clear in its specification that it SHOULD (or MUST) be =
dealt
>         with before (or after) others.
>=20
>         Does that make sense?
>=20
>=20
>         - m&m
>=20
>         Matthew A. Miller
>=20
>         On 17/07/25 16:24, denis bider wrote:
>         > Good catch. I believe this refers to the following paragraph:=

>         >
>         > "If an extension requires both the client and the server to
>         include it
>         > in order for the extension to take effect, the relative
>         position of the
>         > extension-name in each EXT_INFO message is irrelevant."
>         >
>         > I have drafted the following new wording:
>         >
>         > "Unless a particular extension's specification indicates
>         differently;
>         > then, if an extension requires both the client and the server=

>         to include
>         > it in order for the extension to take effect; implementers
>         MUST use a
>         > default assumption that the relative position of the
>         extension-name in
>         > each EXT_INFO message is irrelevant with respect to whether t=
he
>         > extension takes effect."
>         >
>         > The purpose of this wording is to:
>         >
>         > - Provide a sensible default, which is that in the absence of=

>         specific
>         > knowledge, order of extension names does not matter.
>         >
>         > - Allow for deviations in special cases where there is
>         specific knowledge.
>         >
>         > For example, extension "foo-linux" could be specified, but
>         after some
>         > years of use, it's observed that it works well for its main
>         purpose, but
>         > is not ideal for a server on Windows. Therefore, extension
>         "foo-windows"
>         > is specified, which works well when the server is Windows, bu=
t
>         not as
>         > well when it's Linux.
>         >
>         > In this case, an implementation that supports "foo-linux" onl=
y
>         would be
>         > ignorant of anything else, and would use the default rule
>         (order of
>         > extension names does not matter). However, an implementation =
that
>         > supports "foo-windows" could implement only that, or both
>         "foo-linux"
>         > and "foo-windows". The specification for "foo-windows" could
>         indicate
>         > that when both are supported, the first one listed by the
>         server (or in
>         > other cases, by the client) is used.
>         >
>         > Allowing for such an extension-defined special case would
>         allow a Linux
>         > server to advertise extensions [... "foo-linux", ...,
>         "foo-windows",
>         > ...], preferring "foo-linux", but supporting the less appropr=
iate
>         > "foo-windows" mechanism as well. Whereas, a Windows server co=
uld
>         > advertise [... "foo-windows", ..., "foo-linux", ...], preferr=
ing
>         > "foo-windows", but supporting the less appropriate "foo-linux=
"
>         mechanism
>         > as well.
>         >
>         > Does this work?
>         >
>         > If there are no objections, I'll upload a -11 draft version
>         with this
>         > new wording.
>         >
>         >
>         >
>         > On Mon, Jul 24, 2017 at 3:02 PM, Matthew Miller
>         > <linuxwolf+ietf@outer-planes.net
>         <mailto:linuxwolf%2Bietf@outer-planes.net>
>         > <mailto:linuxwolf+ietf@outer-planes.net
>         <mailto:linuxwolf%2Bietf@outer-planes.net>>> wrote:
>         >
>         >=C2=A0 =C2=A0 =C2=A0Reviewer: Matthew Miller
>         >=C2=A0 =C2=A0 =C2=A0Review result: Ready with Issues
>         >
>         >=C2=A0 =C2=A0 =C2=A0I am the assigned Gen-ART reviewer for thi=
s draft. The
>         General Area
>         >=C2=A0 =C2=A0 =C2=A0Review Team (Gen-ART) reviews all IETF doc=
uments being
>         processed
>         >=C2=A0 =C2=A0 =C2=A0by the IESG for the IETF Chair.=C2=A0 Plea=
se treat these
>         comments just
>         >=C2=A0 =C2=A0 =C2=A0like any other last call comments.
>         >
>         >=C2=A0 =C2=A0 =C2=A0For more information, please see the FAQ a=
t
>         >
>         >=C2=A0 =C2=A0 =C2=A0<https://trac.ietf.org/trac/gen/wiki/GenAr=
tfaq
>         <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>
>         >=C2=A0 =C2=A0 =C2=A0<https://trac.ietf.org/trac/gen/wiki/GenAr=
tfaq
>         <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>>>.
>         >
>         >=C2=A0 =C2=A0 =C2=A0Document: draft-ietf-curdle-ssh-ext-info-1=
0
>         >=C2=A0 =C2=A0 =C2=A0Reviewer: Matthew Miller
>         >=C2=A0 =C2=A0 =C2=A0Review Date: 2017-07-24
>         >=C2=A0 =C2=A0 =C2=A0IETF LC End Date: 2017-07-30
>         >=C2=A0 =C2=A0 =C2=A0IESG Telechat date: N/A
>         >
>         >=C2=A0 =C2=A0 =C2=A0Summary:
>         >
>         >=C2=A0 =C2=A0 =C2=A0This document is ready with an issue.
>         >
>         >=C2=A0 =C2=A0 =C2=A0I found this document very coherent and ea=
sy to follow.
>         >
>         >=C2=A0 =C2=A0 =C2=A0Major issues:
>         >
>         >=C2=A0 =C2=A0 =C2=A0Minor issues:
>         >
>         >=C2=A0 =C2=A0 =C2=A0My only issue borders on nit, but sided wi=
th nit as I can
>         see it
>         >=C2=A0 =C2=A0 =C2=A0potentially causing confusion for an imple=
menter in the
>         future.
>         >
>         >=C2=A0 =C2=A0 =C2=A0Section 2.5. "Interpretation of Extension =
Names and
>         Values" explicitly
>         >=C2=A0 =C2=A0 =C2=A0states in the second paragraph a condition=
 where the
>         relative order of
>         >=C2=A0 =C2=A0 =C2=A0extension-names in an EXT_INFO message is =
irrelevant.=C2=A0
>         However, the rest
>         >=C2=A0 =C2=A0 =C2=A0of the section seems to imply to me that r=
elative order is not
>         >=C2=A0 =C2=A0 =C2=A0important;
>         >=C2=A0 =C2=A0 =C2=A0so to explicitly call out a scenario seems=
 to imply that
>         relative order
>         >=C2=A0 =C2=A0 =C2=A0*is* relevant/important, sometimes.=C2=A0 =
If relative order is
>         expected to be
>         >=C2=A0 =C2=A0 =C2=A0important most of the time, I think it hel=
pful to
>         explicitly state that
>         >=C2=A0 =C2=A0 =C2=A0and give a rationale for it.
>         >
>         >=C2=A0 =C2=A0 =C2=A0Nits/editorial comments:
>         >
>         >=C2=A0 =C2=A0 =C2=A0* RFC 5226 is referenced by this document,=
 but is
>         obsoleted by RFC 8126.
>         >
>         >
>         >=C2=A0 =C2=A0 =C2=A0__________________________________________=
_____
>         >=C2=A0 =C2=A0 =C2=A0Curdle mailing list
>         >=C2=A0 =C2=A0 =C2=A0Curdle@ietf.org <mailto:Curdle@ietf.org>
>         <mailto:Curdle@ietf.org <mailto:Curdle@ietf.org>>
>         >=C2=A0 =C2=A0 =C2=A0https://www.ietf.org/mailman/listinfo/curd=
le
>         <https://www.ietf.org/mailman/listinfo/curdle>
>         >=C2=A0 =C2=A0 =C2=A0<https://www.ietf.org/mailman/listinfo/cur=
dle
>         <https://www.ietf.org/mailman/listinfo/curdle>>
>         >
>         >
>=20
>=20
>=20


--P46VhQpSaqIMfmUxSVWPmgGMJph8nW77i--

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

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJZe2CxAAoJEOz0ck4QngW7efcH/iSZgOSSttcv2DsWZA2dXoU9
n1uhdbWGogTaIu5CMMscw1fvHLuCJid5WrZExJSddQJGI1tgYE9ieOWMzVfavLGp
v809lNyCTZKQklLcJDWQLM4VTLi18g8D2RDzb8QXd4/ViAml0HGMzaCaLoMpr1Vr
lP5RtFezOKR/M4zR86TwQkGOa921dH0pInQfp5evRbN/FOoYwWA2UZDKnJk+sYaa
uPcXLwg+9c60vmd8nTI5lM/w0WtjgSGiyfdx4h1sQN43zO/SCEOycYGb3PfX7rSP
tms+eRO6eMRwqieKs8y49jVfcQKWih1KcJVKSG9RQSObuYUyvMPtFMdykH5c00Q=
=Yk5d
-----END PGP SIGNATURE-----

--aJCcI3oc7MIhLwqvcFkJjimEiMODAcsw1--


From nobody Fri Jul 28 10:33:27 2017
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C9B912EC3F for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 10:33:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, 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 gxgrQIJPACfu for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 10:33:24 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37C0612778D for <ietf@ietf.org>; Fri, 28 Jul 2017 10:33:24 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 408722009E for <ietf@ietf.org>; Fri, 28 Jul 2017 13:34:58 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 293CD8076D for <ietf@ietf.org>; Fri, 28 Jul 2017 13:33:23 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: The index page [Revamp of the www.ietf.org website]
In-Reply-To: <EMEW3|b536356ced6bc10f3c2876d5af92c499y6Q0Wx03tjc|ecs.soton.ac.uk|B0F00265-66C0-4F84-A647-D111348BC010@ecs.soton.ac.uk>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6394482@GLKXM0002V.GREENLNK.net> <39D1C0A9-DB43-42DD-BD3F-7D636856ECEF@gmail.com> <20170721083215.a2qdgfrpg2jf6irq@mx4.yitter.info> <B5AD9DB5-A261-4924-98F4-0D5945E68366@isoc.org> <D3576F2D-4D8F-4FAA-9E6E-80D2E08FE5A8@piuha.net> <28C0B89A-73A1-4CC3-8903-822D07F2383F@ecs.soton.ac.uk> <EMEW3|93a21cfe95bdba7176c7d3d313daf9d5y6PAMX03tjc|ecs.soton.ac.uk|28C0B89A-73A1-4CC3-8903-822D07F2383F@ecs.soton.ac.uk> <04052cf6-11de-193d-7bc5-c3926182ca0a@gmail.com> <B0F00265-66C0-4F84-A647-D111348BC010@ecs.soton.ac.uk> <EMEW3|b536356ced6bc10f3c2876d5af92c499y6Q0Wx03tjc|ecs.soton.ac.uk|B0F00265-66C0-4F84-A647-D111348BC010@ecs.soton.ac.uk>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Fri, 28 Jul 2017 13:33:23 -0400
Message-ID: <11267.1501263203@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2h7TS1kpWB9TGgpsenmi5WUg3lQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 17:33:26 -0000

--=-=-=
Content-Type: text/plain


Tim Chown <tjc@ecs.soton.ac.uk> wrote:
    >> And for me the exemplar is still https://www.ietf.org/content.html,
    >> updated with links to the new site.

    > Yes, that page is a great example.

That page works for me too.
I tried beta.ietf.org/content.html, and it didn't work.
So I think, if it worked, it would be perfect.


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAll7dWIACgkQgItw+93Q
3WWtuAf+OUU77XWGwL8RYDO5uLf9h8YSvuZ/RdFZCIiGnhYtpESeF3Fngzd5LNUH
PJYje7Bpe7eveiUvUDRlRlASj/dwuZQnCKhDV6oX/47fKKV5pdvHzSz5ymyKxTZM
xJy1n2neqYboCHUa6dDBNNH59iMfi3c9UleLAtiEWy8jrjSvDCgsZXCA0KC3eJv8
agY5nVcsh987NQ8Or4vXROosq3S3Wd9FitntkqLpwyiy5TbtphN78YYYjifamcq/
IYYJvB2TvpDrZpGSRNSkjs0UbSP7F2EzcwvBHuqGiUvrggAfpJxZTngsd+Evf86D
x0uA109jBT+RPF+9F+02ffOrcYM2bA==
=s+QF
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Jul 28 10:47:12 2017
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04BBF131D0C for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 10:47:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, 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 FXfLsxFvLPUh for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 10:47:09 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E08D131CF0 for <ietf@ietf.org>; Fri, 28 Jul 2017 10:47:09 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id D83C92009E; Fri, 28 Jul 2017 13:48:43 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id BEA788076D; Fri, 28 Jul 2017 13:47:08 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: George Michaelson <ggm@algebras.org>
cc: IETF <ietf@ietf.org>
Subject: Re: Revamp of the www.ietf.org website
In-Reply-To: <CAKr6gn2Bkbe9tY2J7d+=+HxWKQZ4FPFanUsh7EphkqhTq7D4kQ@mail.gmail.com>
References: <alpine.DEB.2.02.1707261649140.29742@uplift.swm.pp.se> <20170726212551.85E0F1A6CB@ld9781.wdf.sap.corp> <CAKr6gn2Bkbe9tY2J7d+=+HxWKQZ4FPFanUsh7EphkqhTq7D4kQ@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Fri, 28 Jul 2017 13:47:08 -0400
Message-ID: <14310.1501264028@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9mYkgHNiPz0L_ho6kij5vnRX8QY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 17:47:11 -0000

--=-=-=
Content-Type: text/plain


George Michaelson <ggm@algebras.org> wrote:
    > * It trivially can be translated

    > It has one major drawback: a lot of people think its ugly.

I don't think it has to be that way.

    > The newer kind, the responsive reactive javascript kind, is far

You use a bunch of words with are not always forced together.
I understand responsive web sites to mean that they look good on different
size screens.  This means doing layout with CSS and div rather than tables.
(HTML4 vs HTML5).
www.ietf.org currently uses a mix of methods.

beta.ietf.org seems to rely on JS for menus and the like (I could be wrong),
while in fact there are pure CSS methods to do this.

The industry has moved beyond JS for many of these things and back to CSS for
reasons of mobile devices, loading time and the like.

I think we could move forward, and I don't mind the new site as I hardly ever
use the old site. But we do need to make sure that we are using the
technology in appropriate moderation.

    > isn't that actually close to what we want? Aren't we actually closer
    > to github, a wiki, and a calendar, than anything else?

For datatracker, I think we are.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAll7eJwACgkQgItw+93Q
3WVTEAgAhqnUhjp54yckCYrlkZynefvbUf5aalxlrouGyBuW+9k+IYnQH4zcRkVf
yKKhWNfHywits60hiW8WnEwlGCcDo7uo2ObqfITmKHuegYkMjRo/aSq0x0rfKB7u
HwlV2kMX7MNWbB5O1sStutVVLNfuhMv3Gx2FtCdziVf9a/CNeCE0lJ0gxK8Qiazu
HStNlkoh1+VFJWMBLQRHYGhIgA3L78/F864lj/LlQcfIbMHW73jxtqMVtroYcq/x
6riPPMQqaHSc92FTANPgIAC07aJW+y5TPVzVoFbt9zpcyIJQhIRy66oz9dh8E+jd
yoFF+Qba+saIR1lZl/jBv5JuzeO6sg==
=mkBQ
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Jul 28 11:02:46 2017
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD288131CC2 for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 11:02:44 -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 87HFcaMA9Xy2 for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 11:02:43 -0700 (PDT)
Received: from mail-yw0-x22b.google.com (mail-yw0-x22b.google.com [IPv6:2607:f8b0:4002:c05::22b]) (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 50011131C3A for <ietf@ietf.org>; Fri, 28 Jul 2017 11:02:43 -0700 (PDT)
Received: by mail-yw0-x22b.google.com with SMTP id i6so94188857ywb.1 for <ietf@ietf.org>; Fri, 28 Jul 2017 11:02:43 -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=koqEG+ZJZ85QgS1pXBjkC4iIgcIPTqSlGIJ/Uz0CqFs=; b=JJLDIT9NpzSeFhUXIB5jgUpYT1jSYG1jRdvaLaj4POXVnHPU8X5C/9S14C9CLjLu7s Dj5LfLPHK2gz6vjvsOqYPehviV35swTh5CuDl+T/LDoN9n70v35DcAl2h8B3ad68q4Ki ZTpbLAd9NQUEdQjkUA5vkLFVb+jABjETZlShop3A6UQ/IcE048maHYKlkkdwBuM9XMFJ za+kmPAIJM1cWCvodyNwPzZ8Cabl6Xo0wUjuvveTiGCLoZt/W957XlpkVAwxSUhX2/t/ yfch4jtVD+FCHh+aH1TnNqEh6r3cp4VMdVQBRvo6ijVAA2xriHJoVCSgHSeOg6iZ16yc r8Ag==
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=koqEG+ZJZ85QgS1pXBjkC4iIgcIPTqSlGIJ/Uz0CqFs=; b=b1rUppbdaNgHqKPn3igG9tAPukfyWKE+5/EvvhqBJ/S4w7FyjPRSQS7+vf+hQuefdV XUuoSPlk90yTvl/WRCEo9Oegzz/Hp93/LJOK4OefbRtu9hy5S9V3gObbp/ehJo3qlArR zezv1vQPYDW+CIvd0nlVomliJwXnCNbxoarQBFMZd3K4QRbXdW0h+vtnryIu010qPoZk HP1fnCG6FcsKs/PMm4kvDFPEPQ3RhfXCfbqGQ9+oHkxlKPvIVahskbV91LfZ01+jmyFF LcuJrAxA1JrbJO0TxEiREW+0SwRW2Nk0f6y7AGEbu1gcZ0wPIiE28Toh4dxkzR7mVKqj d4Rg==
X-Gm-Message-State: AIVw11332gzryd0N6b9Rl2N8/a3pUkgQGwvpBHTExSd9eXewTDhI8d33 tVLcqlBZRVOLTRGxrHvVKXS7NSAvWw==
X-Received: by 10.37.38.146 with SMTP id m140mr7374824ybm.66.1501264962287; Fri, 28 Jul 2017 11:02:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.202.69 with HTTP; Fri, 28 Jul 2017 11:02:41 -0700 (PDT)
In-Reply-To: <m2o9s6lfy7.wl-randy@psg.com>
References: <150108971740.23120.257371533321943899.idtracker@ietfa.amsl.com> <EF2F4195-A97F-46CB-B2D2-DB7A5E11874F@gmail.com> <m2o9s6lfy7.wl-randy@psg.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Fri, 28 Jul 2017 13:02:41 -0500
Message-ID: <CAKKJt-eD2YVyZVQzxYaDO9RJv5_r6EBT8ipCV9juyj0RuyeoiQ@mail.gmail.com>
Subject: Re: Announcement on IETF 100 Hotel Reservations
To: Randy Bush <randy@psg.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c18f336ca839b0555647cc4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YhWusTOpL4XOmoxRWOJlCUSMkAw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 18:02:44 -0000

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

Thanks to all who are posting in this thread.

I haven't been to Singapore previously, so have questions, and I'm seeing a
lot of answers I expected to have to dig for (hoping they would be in the
wiki, but bracing myself for Le Google).

Spencer

On Wed, Jul 26, 2017 at 10:24 PM, Randy Bush <randy@psg.com> wrote:

> > I note that there are transit hotels in the airport, this might make
> > sense to get some sleep after I arrive.
>
> i have used the changi transit hotels a fair bit.  they're functional.
> be sure to visit the butterfly garden!
>
> randy
>
>

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

<div dir=3D"ltr">Thanks to all who are posting in this thread.=C2=A0<div><b=
r></div><div>I haven&#39;t been to Singapore previously, so have questions,=
 and I&#39;m seeing a lot of answers I expected to have to dig for (hoping =
they would be in the wiki, but bracing myself for Le Google).<div><br></div=
><div>Spencer</div></div></div><div class=3D"gmail_extra"><br><div class=3D=
"gmail_quote">On Wed, Jul 26, 2017 at 10:24 PM, Randy Bush <span dir=3D"ltr=
">&lt;<a href=3D"mailto:randy@psg.com" target=3D"_blank">randy@psg.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"><span class=3D"">&gt; I=
 note that there are transit hotels in the airport, this might make<br>
&gt; sense to get some sleep after I arrive.<br>
<br>
</span>i have used the changi transit hotels a fair bit.=C2=A0 they&#39;re =
functional.<br>
be sure to visit the butterfly garden!<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
randy<br>
<br>
</font></span></blockquote></div><br></div>

--94eb2c18f336ca839b0555647cc4--


From nobody Fri Jul 28 11:31:18 2017
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21448129B43 for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 11:31:17 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.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 seq5lJHyYD_r for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 11:31:15 -0700 (PDT)
Received: from mail-ua0-x236.google.com (mail-ua0-x236.google.com [IPv6:2607:f8b0:400c:c08::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 DB087131FFC for <ietf@ietf.org>; Fri, 28 Jul 2017 11:31:14 -0700 (PDT)
Received: by mail-ua0-x236.google.com with SMTP id 80so169355683uas.0 for <ietf@ietf.org>; Fri, 28 Jul 2017 11:31:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NNiv61nIBr+8z5V4ycXHjoWGkwgkRm+bs6in6W5VpV8=; b=eCpKmm98l17yrQfVTqQ+l9TqspGTaYt2D2noTXe96FjfKVDW2gFzEkXyt7SxVDtWQJ wXNa7+XlLHZfKA++z8i4mZ97M6c+KVexHb3yNSqY9u2TtTYHbqhSocGfYFy1WYmjaQ1c p5UlnzyM7aicvIhN0GsBNfycfltOQPjDDFcCjElzCESGNatWs4lHv3/XSuXNlWY71WAt rMQYrKRstSesF+9HbXQAoN877S07pMpsl3dHA4qSLgVFT5T7BzYZqNkr1Mxd874pnr+o I1v6DHhFMxlyoRSw9GqIOrOpvn1EOVFZl9b+AYHqa6oPRAYKBLt/yiCb/bXcSJUPaNzc iCrA==
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=NNiv61nIBr+8z5V4ycXHjoWGkwgkRm+bs6in6W5VpV8=; b=TCwWH7hDwluTOk8zWmrQLwjN8GF5YD2ozWBTSZOb6XADC+GIg6s+QsCIwxtdSOyxdN WkpbMKpk4qwTWm16Z1Xt+8HHzg9p2ZKvuUmKoFTenJPkd2fA8qeGNJvg4/vzuUHg2WWV 4Zud0KYgDjjWTA0OxYW4dKsHtv9U07be+FnLZ74XjVgHR/ZvFHRNcpsctHkggzfpQVGp qqzWHrMXYERdW2FTFJ1S13gA67J0q5jLEX57vdI7d8rn123BVGa6ykpbJUZ3d7YBLM8f tLTwI/xWIpFdsB3fdt2RmGIfZwKc7Pon37iJJSMdN9Ori6kS6c2XzKJGLLbyxoEVQxaD RUMg==
X-Gm-Message-State: AIVw110fJDyN6dWVmEO/0nDZd+X9FfknLzkuVFCMW1n+YZsy8OLNHhVJ Q4mXdJ41sYatpl+J5zEx2oV26m6D7wbfQX1KQQ==
X-Received: by 10.31.115.2 with SMTP id o2mr4477921vkc.8.1501266673880; Fri, 28 Jul 2017 11:31:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.9.231 with HTTP; Fri, 28 Jul 2017 11:30:33 -0700 (PDT)
In-Reply-To: <CAKKJt-eD2YVyZVQzxYaDO9RJv5_r6EBT8ipCV9juyj0RuyeoiQ@mail.gmail.com>
References: <150108971740.23120.257371533321943899.idtracker@ietfa.amsl.com> <EF2F4195-A97F-46CB-B2D2-DB7A5E11874F@gmail.com> <m2o9s6lfy7.wl-randy@psg.com> <CAKKJt-eD2YVyZVQzxYaDO9RJv5_r6EBT8ipCV9juyj0RuyeoiQ@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
Date: Fri, 28 Jul 2017 14:30:33 -0400
Message-ID: <CAHw9_iJz2Q1hWY+E_e=Mr1kaS3w3YeDXAC1QRWN52j86A6nx7Q@mail.gmail.com>
Subject: Re: Announcement on IETF 100 Hotel Reservations
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: Randy Bush <randy@psg.com>, Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/U3LmZIFJZo3L_gVeOEpAWT1Wbfw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 18:31:17 -0000

On Fri, Jul 28, 2017 at 2:02 PM, Spencer Dawkins at IETF
<spencerdawkins.ietf@gmail.com> wrote:
> Thanks to all who are posting in this thread.
>
> I haven't been to Singapore previously, so have questions, and I'm seeing a
> lot of answers I expected to have to dig for (hoping they would be in the
> wiki, but bracing myself for Le Google).

My few tips:
1: Bring a number of cooling / wicking t-shirts -- I like the " 32
Degrees Cool" ones - Costco generally has a 2 pack for $9.99 (this is
only helpful if you live in the USA and have a costco membership :-P
). I'd go for a walk outside, and then rinse it in the shower. They
dry quickly and a then fine for going out later in the day.

2: Bring a sun hat

3: Drink lots of water!

4: When I first travelled to Singapore (and was jetlagged!) I was
surprised how many people made very straight queues to cross the road
-- and then I figured out that they were actually just standing in the
shade of the lamppost :-)

5: In spite of the heat / humidity (and my built in insulation!),
Singapore is one of my favorite places -- from the hotel it is an easy
walk to a number of different areas, including Little India, Chinatown
and Arab Street.
There is a large variety of architectures, many sights, lots of
interesting food, etc. Prices are reasonable, I've never felt unsafe,
everyone is pleasant, etc. As with anywhere, try to be respectful of
cultural norms and you'll have a great time.
Oh, the hotel complex is over a mall
(http://www.rafflescity.com.sg/store-guide/) with some great food
court offerings, including a Din Tai Fung
(http://www.dintaifung.com.sg/) -- when I was there for an ICANN
meeting I ate there ~12 times in 9 days :-)

W

>
> Spencer
>
> On Wed, Jul 26, 2017 at 10:24 PM, Randy Bush <randy@psg.com> wrote:
>>
>> > I note that there are transit hotels in the airport, this might make
>> > sense to get some sleep after I arrive.
>>
>> i have used the changi transit hotels a fair bit.  they're functional.
>> be sure to visit the butterfly garden!
>>
>> randy
>>
>



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf


From nobody Fri Jul 28 12:04:39 2017
Return-Path: <fenner@fenron.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD4AA131DA9 for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 12:04:37 -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=fenron.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 MGYNo5MX2I62 for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 12:04:34 -0700 (PDT)
Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (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 5E9EB131DA8 for <ietf@ietf.org>; Fri, 28 Jul 2017 12:04:34 -0700 (PDT)
Received: by mail-oi0-x22c.google.com with SMTP id g131so140721208oic.3 for <ietf@ietf.org>; Fri, 28 Jul 2017 12:04:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fenron.com; s=google;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=yP/WUEJAzgM4SicRfmvHa4E7Kx1vGOoh3coiEP5Ica8=; b=C2NlyJYRDTPExXwrTPnhRB889eWEUOWFpnJP/kvADG0cIY1IjNPcLdf9Qgj0XvMrzo ntsHXJQZxnAyJnihEBuwisiGY6JaVqLpt94FJMMtJspOzKQe5LK+BbfJun5hlHnFlUZ4 /CX7Wq4G7Fs47R5ZBN7FE4zVe3ATqlGSPhgJk=
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=yP/WUEJAzgM4SicRfmvHa4E7Kx1vGOoh3coiEP5Ica8=; b=tePkGlmVAqGdBHnpoR1pSVJPz3TlVG7/djpYbwI3V0rYpZXCAD0vUxGMfOLTdCeVJL NhXOGYNU5fm+IkaNv+H0LjcrPth6yTtU24xfRkKgBeJINIDutpOibrSrTsoCbKMGmKSA OKiNwAL/0nIvqR8FFGaDehJE03o2cYq2aQpNd6K5MtmyOtipkMGWJ0DQ9KvbOZGzENBO /ArRjArwB9JLU9UuhqD6H7BeVW9EDLmNM2bsUBQLZd6zvHrB7dzMl1hBioChQXJtplsj wLYJTzbv34MpzWhzjsOJyF2y5zI5zoJY8QYFgUbDzsM7NTF9KfxvOzAS4nyX3NYdkG4d p/vA==
X-Gm-Message-State: AIVw110TMVrkpjzsRmBJ+g4bvss0XnIEt4oBylenVi8g4zVspLZqzVYk b1oElCHY0Wf5mkBvhK9iUdaUCSqg45mRCeM=
X-Received: by 10.202.220.195 with SMTP id t186mr7268971oig.111.1501268673453;  Fri, 28 Jul 2017 12:04:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.148.9 with HTTP; Fri, 28 Jul 2017 12:04:32 -0700 (PDT)
In-Reply-To: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com>
From: Bill Fenner <fenner@fenron.com>
Date: Fri, 28 Jul 2017 15:04:32 -0400
Message-ID: <CAATsVbacCxdj1ijt6oqu+hcPYpcYnziWUAtVrG2KiPMfFk90hQ@mail.gmail.com>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: "ietf@ietf.org" <ietf@ietf.org>
Cc: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,  "Brzozowski, John" <John_Brzozowski@comcast.com>, Suresh Krishnan <suresh.krishnan@gmail.com>
Content-Type: multipart/alternative; boundary="001a113d3e20fe77090555655979"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fhwCm8tax0OswsRrVoIbrVyVd00>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 19:04:38 -0000

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

I understand there was a great deal of private discussion on this topic,
but none of it made it to the public lists.  Can someone who was involved
with the private discussion summarize it for this list?

Thanks,
  Bill


On Mon, Jul 17, 2017 at 3:33 AM, Brzozowski, John <
John_Brzozowski@comcast.com> wrote:

> Apologies, I understand this mail did not make it to the various lists.
>
> John
> +1-484-962-0060
>
> -----Original Message-----
> From: John Brzozowski <John_Brzozowski@Cable.Comcast.com>
> Date: Sunday, July 16, 2017 at 20:28
> To: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <
> draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>
> Cc: Randy Bush <randy@psg.com>, Alissa Cooper <alissa@cooperw.in>, Jim
> Martin <jim@daedelus.com>, Jari Arkko <jari.arkko@piuha.net>, Suresh
> Krishnan <suresh.krishnan@gmail.com>, Russ Housley <housley@vigilsec.com>
> Subject: Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
>
>     Folks,
>
>     Apologies in advance for the gratuitous cross posting (v6ops, ietf,
> ipv6, sunset4, softwires).  I hope, to you all, this is worth the added
> email.
>
>     The draft below was written to provide the necessary documentation to
> enable the IETF (the NOC, participants, etc.) to migrate to an IPv6 only
> primary network connection (Wi-Fi and wired) that utilizes NAT64+DNS64 to
> access IPv4 only content.  The request for IETF 99 has been to have the
> primary =E2=80=9Cietf=E2=80=9D SSID adhere to what is documented in the I=
-D below.  I trust
> the motivation is understood.  This means that the main =E2=80=9Cietf=E2=
=80=9D SSID would
> be switched to be IPv6 only with NAT64+DNS64 (at layer 3) per the I-D
> below.  Given the that IETF99 is upon us, this may or may not be entirely
> possible.
>
>     At this stage, the infrastructure preparations for IETF 99 should be
> in place to ensure that the IETF has the necessary hardware for redundanc=
y
> and performance.
>
>     So, we are all seeking your input.  Given the above, what would all
> you suggest is tolerable for IETF99 as it pertains to the I-D below?
>
>     =E2=80=A2 IPv6 only per the I-D for the balance of IETF week?
>     =E2=80=A2 IPv6 only per the I-D for one or more days this week?
>     =E2=80=A2 IPv6 only per the I-D for the plenary?
>     =E2=80=A2 IPv6 only per the I-D for the next IETF meeting?
>
>     Please send us your feedback.
>
>     Regards,
>
>     John
>     +1-484-962-0060
>
>     -----Original Message-----
>     From: "internet-drafts@ietf.org" <internet-drafts@ietf.org>
>     Date: Saturday, July 1, 2017 at 03:04
>     To: Marcus Keane <marcus.keane@microsoft.com>, Jen Linkova <
> furry@google.com>, Lorenzo Colitti <lorenzo@google.com>, John Brzozowski =
<
> John_Brzozowski@Cable.Comcast.com>, Erik Kline <ek@google.com>, John
> Brzozowski <John_Brzozowski@Cable.Comcast.com>, David Schinazi <
> dschinazi@apple.com>, Stuart Cheshire <cheshire@apple.com>, Jen Linkova <
> furry@google.com>, Paul Saab <ps@fb.com>, David Schinazi <
> dschinazi@apple.com>
>     Subject: New Version Notification for draft-jjmb-v6ops-ietf-ipv6-
> only-incremental-00.txt
>
>
>         A new version of I-D, draft-jjmb-v6ops-ietf-ipv6-
> only-incremental-00.txt
>         has been successfully submitted by John Jason Brzozowski and
> posted to the
>         IETF repository.
>
>         Name:           draft-jjmb-v6ops-ietf-ipv6-only-incremental
>         Revision:       00
>         Title:          Incremental Deployment of IPv6-only Wi-Fi for IET=
F
> Meetings
>         Document date:  2017-06-30
>         Group:          Individual Submission
>         Pages:          15
>         URL:            https://www.ietf.org/internet-
> drafts/draft-jjmb-v6ops-ietf-ipv6-only-incremental-00.txt
>         Status:         https://datatracker.ietf.org/
> doc/draft-jjmb-v6ops-ietf-ipv6-only-incremental/
>         Htmlized:       https://tools.ietf.org/html/
> draft-jjmb-v6ops-ietf-ipv6-only-incremental-00
>         Htmlized:       https://datatracker.ietf.org/
> doc/html/draft-jjmb-v6ops-ietf-ipv6-only-incremental-00
>
>
>         Abstract:
>            The purpose of this document is to provide a blueprint and
> guidance
>            for deploying IPv6-only Wi-Fi at IETF meetings.  This document
>            outlines infrastructure and operational guidance that operator=
s
>            should consider when deploying IPv6-only networks using NAT64
> and
>            DNS64 to support communication to legacy IPv4-only services.
>
>
>
>
>         Please note that it may take a couple of minutes from the time of
> submission
>         until the htmlized version and diff are available at
> tools.ietf.org.
>
>         The IETF Secretariat
>
>
>
>
>
>
>

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

<div dir=3D"ltr">I understand there was a great deal of private discussion =
on this topic, but none of it made it to the public lists.=C2=A0 Can someon=
e who was involved with the private discussion summarize it for this list?<=
div><br></div><div>Thanks,</div><div>=C2=A0 Bill</div><div><br></div></div>=
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Jul 17, 2=
017 at 3:33 AM, Brzozowski, John <span dir=3D"ltr">&lt;<a href=3D"mailto:Jo=
hn_Brzozowski@comcast.com" target=3D"_blank">John_Brzozowski@comcast.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">Apologies, I understa=
nd this mail did not make it to the various lists.<br>
<br>
John<br>
<a href=3D"tel:%2B1-484-962-0060" value=3D"+14849620060">+1-484-962-0060</a=
><br>
<br>
-----Original Message-----<br>
From: John Brzozowski &lt;<a href=3D"mailto:John_Brzozowski@Cable.Comcast.c=
om">John_Brzozowski@Cable.<wbr>Comcast.com</a>&gt;<br>
Date: Sunday, July 16, 2017 at 20:28<br>
To: &quot;<a href=3D"mailto:draft-jjmb-v6ops-ietf-ipv6-only-incremental@iet=
f.org">draft-jjmb-v6ops-ietf-ipv6-<wbr>only-incremental@ietf.org</a>&quot; =
&lt;<a href=3D"mailto:draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org"=
>draft-jjmb-v6ops-ietf-ipv6-<wbr>only-incremental@ietf.org</a>&gt;<br>
Cc: Randy Bush &lt;<a href=3D"mailto:randy@psg.com">randy@psg.com</a>&gt;, =
Alissa Cooper &lt;<a href=3D"mailto:alissa@cooperw.in">alissa@cooperw.in</a=
>&gt;, Jim Martin &lt;<a href=3D"mailto:jim@daedelus.com">jim@daedelus.com<=
/a>&gt;, Jari Arkko &lt;<a href=3D"mailto:jari.arkko@piuha.net">jari.arkko@=
piuha.net</a>&gt;, Suresh Krishnan &lt;<a href=3D"mailto:suresh.krishnan@gm=
ail.com">suresh.krishnan@gmail.com</a>&gt;, Russ Housley &lt;<a href=3D"mai=
lto:housley@vigilsec.com">housley@vigilsec.com</a>&gt;<br>
Subject: Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings<br>
<br>
=C2=A0 =C2=A0 Folks,<br>
<br>
=C2=A0 =C2=A0 Apologies in advance for the gratuitous cross posting (v6ops,=
 ietf, ipv6, sunset4, softwires).=C2=A0 I hope, to you all, this is worth t=
he added email.<br>
<br>
=C2=A0 =C2=A0 The draft below was written to provide the necessary document=
ation to enable the IETF (the NOC, participants, etc.) to migrate to an IPv=
6 only primary network connection (Wi-Fi and wired) that utilizes NAT64+DNS=
64 to access IPv4 only content.=C2=A0 The request for IETF 99 has been to h=
ave the primary =E2=80=9Cietf=E2=80=9D SSID adhere to what is documented in=
 the I-D below.=C2=A0 I trust the motivation is understood.=C2=A0 This mean=
s that the main =E2=80=9Cietf=E2=80=9D SSID would be switched to be IPv6 on=
ly with NAT64+DNS64 (at layer 3) per the I-D below.=C2=A0 Given the that IE=
TF99 is upon us, this may or may not be entirely possible.<br>
<br>
=C2=A0 =C2=A0 At this stage, the infrastructure preparations for IETF 99 sh=
ould be in place to ensure that the IETF has the necessary hardware for red=
undancy and performance.<br>
<br>
=C2=A0 =C2=A0 So, we are all seeking your input.=C2=A0 Given the above, wha=
t would all you suggest is tolerable for IETF99 as it pertains to the I-D b=
elow?<br>
<br>
=C2=A0 =C2=A0 =E2=80=A2 IPv6 only per the I-D for the balance of IETF week?=
<br>
=C2=A0 =C2=A0 =E2=80=A2 IPv6 only per the I-D for one or more days this wee=
k?<br>
=C2=A0 =C2=A0 =E2=80=A2 IPv6 only per the I-D for the plenary?<br>
=C2=A0 =C2=A0 =E2=80=A2 IPv6 only per the I-D for the next IETF meeting?<br=
>
<br>
=C2=A0 =C2=A0 Please send us your feedback.<br>
<br>
=C2=A0 =C2=A0 Regards,<br>
<br>
=C2=A0 =C2=A0 John<br>
=C2=A0 =C2=A0 +1-484-962-0060<br>
<br>
=C2=A0 =C2=A0 -----Original Message-----<br>
=C2=A0 =C2=A0 From: &quot;<a href=3D"mailto:internet-drafts@ietf.org">inter=
net-drafts@ietf.org</a>&quot; &lt;<a href=3D"mailto:internet-drafts@ietf.or=
g">internet-drafts@ietf.org</a>&gt;<br>
=C2=A0 =C2=A0 Date: Saturday, July 1, 2017 at 03:04<br>
=C2=A0 =C2=A0 To: Marcus Keane &lt;<a href=3D"mailto:marcus.keane@microsoft=
.com">marcus.keane@microsoft.com</a>&gt;, Jen Linkova &lt;<a href=3D"mailto=
:furry@google.com">furry@google.com</a>&gt;, Lorenzo Colitti &lt;<a href=3D=
"mailto:lorenzo@google.com">lorenzo@google.com</a>&gt;, John Brzozowski &lt=
;<a href=3D"mailto:John_Brzozowski@Cable.Comcast.com">John_Brzozowski@Cable=
.<wbr>Comcast.com</a>&gt;, Erik Kline &lt;<a href=3D"mailto:ek@google.com">=
ek@google.com</a>&gt;, John Brzozowski &lt;<a href=3D"mailto:John_Brzozowsk=
i@Cable.Comcast.com">John_Brzozowski@Cable.<wbr>Comcast.com</a>&gt;, David =
Schinazi &lt;<a href=3D"mailto:dschinazi@apple.com">dschinazi@apple.com</a>=
&gt;, Stuart Cheshire &lt;<a href=3D"mailto:cheshire@apple.com">cheshire@ap=
ple.com</a>&gt;, Jen Linkova &lt;<a href=3D"mailto:furry@google.com">furry@=
google.com</a>&gt;, Paul Saab &lt;<a href=3D"mailto:ps@fb.com">ps@fb.com</a=
>&gt;, David Schinazi &lt;<a href=3D"mailto:dschinazi@apple.com">dschinazi@=
apple.com</a>&gt;<br>
=C2=A0 =C2=A0 Subject: New Version Notification for draft-jjmb-v6ops-ietf-i=
pv6-<wbr>only-incremental-00.txt<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 A new version of I-D, draft-jjmb-v6ops-ietf-ipv=
6-<wbr>only-incremental-00.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 has been successfully submitted by John Jason B=
rzozowski and posted to the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 IETF repository.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0d=
raft-jjmb-v6ops-ietf-ipv6-<wbr>only-incremental<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A000<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Increm=
ental Deployment of IPv6-only Wi-Fi for IETF Meetings<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Document date:=C2=A0 2017-06-30<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Indivi=
dual Submission<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 15<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <=
a href=3D"https://www.ietf.org/internet-drafts/draft-jjmb-v6ops-ietf-ipv6-o=
nly-incremental-00.txt" rel=3D"noreferrer" target=3D"_blank">https://www.ie=
tf.org/internet-<wbr>drafts/draft-jjmb-v6ops-ietf-<wbr>ipv6-only-incrementa=
l-00.txt</a><br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a hre=
f=3D"https://datatracker.ietf.org/doc/draft-jjmb-v6ops-ietf-ipv6-only-incre=
mental/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/=
<wbr>doc/draft-jjmb-v6ops-ietf-<wbr>ipv6-only-incremental/</a><br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"=
https://tools.ietf.org/html/draft-jjmb-v6ops-ietf-ipv6-only-incremental-00"=
 rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<wbr>draf=
t-jjmb-v6ops-ietf-ipv6-<wbr>only-incremental-00</a><br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"=
https://datatracker.ietf.org/doc/html/draft-jjmb-v6ops-ietf-ipv6-only-incre=
mental-00" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.or=
g/<wbr>doc/html/draft-jjmb-v6ops-<wbr>ietf-ipv6-only-incremental-00</a><br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Abstract:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0The purpose of this document is to=
 provide a blueprint and guidance<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0for deploying IPv6-only Wi-Fi at I=
ETF meetings.=C2=A0 This document<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0outlines infrastructure and operat=
ional guidance that operators<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0should consider when deploying IPv=
6-only networks using NAT64 and<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0DNS64 to support communication to =
legacy IPv4-only services.<br>
<br>
<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Please note that it may take a couple of minute=
s from the time of submission<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 until the htmlized version and diff are availab=
le at <a href=3D"http://tools.ietf.org" rel=3D"noreferrer" target=3D"_blank=
">tools.ietf.org</a>.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 The IETF Secretariat<br>
<br>
<br>
<br>
<br>
<br>
<br>
</blockquote></div><br></div>

--001a113d3e20fe77090555655979--


From nobody Fri Jul 28 13:39:07 2017
Return-Path: <ekr@rtfm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5780C129B62 for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 13:39:05 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, 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=rtfm-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 7GfqMOgO-iOX for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 13:39:02 -0700 (PDT)
Received: from mail-yw0-x234.google.com (mail-yw0-x234.google.com [IPv6:2607:f8b0:4002:c05::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 21CC612EA7C for <ietf@ietf.org>; Fri, 28 Jul 2017 13:39:02 -0700 (PDT)
Received: by mail-yw0-x234.google.com with SMTP id i6so96237118ywb.1 for <ietf@ietf.org>; Fri, 28 Jul 2017 13:39:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=BEkbYOa7/JGMyeEOGIZ4lUGQgwhJV94C/8bytyGsCB0=; b=Avy/yRaJJIGNqTHRc3RVNQOdqaXfF1xa6bQkz3mehUBLMlRqQ4wnrpFUkcRXJn7c1j IC4Fj+rIwf2pDAlYCOrGkXoPjhUtKCC2PLyPh6uGEwAw8uZCwUadnTB5Wo0gaJPDB76N T7+RZ/SajHEccQjB9rdp9UL3zP4iBvYYZNeLSbwONOGBlKAxG36emmNGEzKm0820bxu9 EGt383l1RMUHDwz2Qp1IUDKGPMDvAqta7ERqW4ITS+CqgqqhIYgVX1YP0FvLdjldl53E bQYc2laafHdIw1cwFYrvHn7YDvOE99inQlyDFxpT0tKKnYLhT+h4wl1QQOh32U3YmnDX S35A==
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=BEkbYOa7/JGMyeEOGIZ4lUGQgwhJV94C/8bytyGsCB0=; b=Hj1wInT+t6EtVok0SfAhYHgBRCvRwpWcecDy5PNjHA6S2fOSeedAoHm6vTknjXeLyv A3LerOjF1S4eFvs9NXfEO1BnMPAKz8O531T1Qm5LHG0/WlPzurVO8c+J+EsoqqyO/YOw QEHInkhKIkEg232KabLr/iCZTV23nee5Zog2lmV1p+SXZFXfPlqShmOslcIQgb7ZMHiD gmUqNhmYPRsQK97dihLLVOu91xXQyAngnwwDW6b0xErVXSiHHIYHBaeOFGe3myLnIFtX b+YOHW55DTbIp2eynrziUtQ1RsD6Fc0vc68Hf5dDDI9+TBZhZiYwskrAEdw8gQkhsYAI 7KGg==
X-Gm-Message-State: AIVw1124HTAChmIsOBIeUA7Spdb4bbGScP3sVwWFJQzI/tmqrV8R8cmm fFO+rs63FIJHr+m6R9PG5EnZ1sr/FcUn
X-Received: by 10.37.160.41 with SMTP id x38mr7396132ybh.339.1501274341384; Fri, 28 Jul 2017 13:39:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.36.12 with HTTP; Fri, 28 Jul 2017 13:38:20 -0700 (PDT)
In-Reply-To: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 28 Jul 2017 13:38:20 -0700
Message-ID: <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: "Brzozowski, John" <John_Brzozowski@comcast.com>
Cc: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>, Suresh Krishnan <suresh.krishnan@gmail.com>
Content-Type: multipart/alternative; boundary="94eb2c1a0650d4669a055566ab39"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iF3tbo8Tnz0dSYTbvjw0rk3bGD0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 20:39:05 -0000

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

I'm not very enthusiastic about this. People come to the IETF to do work
and having
to deal with potential bustage from this experiment gets in the way of that=
.

-Ekr


On Mon, Jul 17, 2017 at 12:33 AM, Brzozowski, John <
John_Brzozowski@comcast.com> wrote:

> Apologies, I understand this mail did not make it to the various lists.
>
> John
> +1-484-962-0060
>
> -----Original Message-----
> From: John Brzozowski <John_Brzozowski@Cable.Comcast.com>
> Date: Sunday, July 16, 2017 at 20:28
> To: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <
> draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>
> Cc: Randy Bush <randy@psg.com>, Alissa Cooper <alissa@cooperw.in>, Jim
> Martin <jim@daedelus.com>, Jari Arkko <jari.arkko@piuha.net>, Suresh
> Krishnan <suresh.krishnan@gmail.com>, Russ Housley <housley@vigilsec.com>
> Subject: Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
>
>     Folks,
>
>     Apologies in advance for the gratuitous cross posting (v6ops, ietf,
> ipv6, sunset4, softwires).  I hope, to you all, this is worth the added
> email.
>
>     The draft below was written to provide the necessary documentation to
> enable the IETF (the NOC, participants, etc.) to migrate to an IPv6 only
> primary network connection (Wi-Fi and wired) that utilizes NAT64+DNS64 to
> access IPv4 only content.  The request for IETF 99 has been to have the
> primary =E2=80=9Cietf=E2=80=9D SSID adhere to what is documented in the I=
-D below.  I trust
> the motivation is understood.  This means that the main =E2=80=9Cietf=E2=
=80=9D SSID would
> be switched to be IPv6 only with NAT64+DNS64 (at layer 3) per the I-D
> below.  Given the that IETF99 is upon us, this may or may not be entirely
> possible.
>
>     At this stage, the infrastructure preparations for IETF 99 should be
> in place to ensure that the IETF has the necessary hardware for redundanc=
y
> and performance.
>
>     So, we are all seeking your input.  Given the above, what would all
> you suggest is tolerable for IETF99 as it pertains to the I-D below?
>
>     =E2=80=A2 IPv6 only per the I-D for the balance of IETF week?
>     =E2=80=A2 IPv6 only per the I-D for one or more days this week?
>     =E2=80=A2 IPv6 only per the I-D for the plenary?
>     =E2=80=A2 IPv6 only per the I-D for the next IETF meeting?
>
>     Please send us your feedback.
>
>     Regards,
>
>     John
>     +1-484-962-0060
>
>     -----Original Message-----
>     From: "internet-drafts@ietf.org" <internet-drafts@ietf.org>
>     Date: Saturday, July 1, 2017 at 03:04
>     To: Marcus Keane <marcus.keane@microsoft.com>, Jen Linkova <
> furry@google.com>, Lorenzo Colitti <lorenzo@google.com>, John Brzozowski =
<
> John_Brzozowski@Cable.Comcast.com>, Erik Kline <ek@google.com>, John
> Brzozowski <John_Brzozowski@Cable.Comcast.com>, David Schinazi <
> dschinazi@apple.com>, Stuart Cheshire <cheshire@apple.com>, Jen Linkova <
> furry@google.com>, Paul Saab <ps@fb.com>, David Schinazi <
> dschinazi@apple.com>
>     Subject: New Version Notification for draft-jjmb-v6ops-ietf-ipv6-
> only-incremental-00.txt
>
>
>         A new version of I-D, draft-jjmb-v6ops-ietf-ipv6-
> only-incremental-00.txt
>         has been successfully submitted by John Jason Brzozowski and
> posted to the
>         IETF repository.
>
>         Name:           draft-jjmb-v6ops-ietf-ipv6-only-incremental
>         Revision:       00
>         Title:          Incremental Deployment of IPv6-only Wi-Fi for IET=
F
> Meetings
>         Document date:  2017-06-30
>         Group:          Individual Submission
>         Pages:          15
>         URL:            https://www.ietf.org/internet-
> drafts/draft-jjmb-v6ops-ietf-ipv6-only-incremental-00.txt
>         Status:         https://datatracker.ietf.org/
> doc/draft-jjmb-v6ops-ietf-ipv6-only-incremental/
>         Htmlized:       https://tools.ietf.org/html/
> draft-jjmb-v6ops-ietf-ipv6-only-incremental-00
>         Htmlized:       https://datatracker.ietf.org/
> doc/html/draft-jjmb-v6ops-ietf-ipv6-only-incremental-00
>
>
>         Abstract:
>            The purpose of this document is to provide a blueprint and
> guidance
>            for deploying IPv6-only Wi-Fi at IETF meetings.  This document
>            outlines infrastructure and operational guidance that operator=
s
>            should consider when deploying IPv6-only networks using NAT64
> and
>            DNS64 to support communication to legacy IPv4-only services.
>
>
>
>
>         Please note that it may take a couple of minutes from the time of
> submission
>         until the htmlized version and diff are available at
> tools.ietf.org.
>
>         The IETF Secretariat
>
>
>
>
>
>
>

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

<div dir=3D"ltr">I&#39;m not very enthusiastic about this. People come to t=
he IETF to do work and having<div>to deal with potential bustage from this =
experiment gets in the way of that.</div><div><br></div><div>-Ekr</div><div=
><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Mon, Jul 17, 2017 at 12:33 AM, Brzozowski, John <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:John_Brzozowski@comcast.com" target=3D"_blank">John_Brzozow=
ski@comcast.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">Apo=
logies, I understand this mail did not make it to the various lists.<br>
<br>
John<br>
<a href=3D"tel:%2B1-484-962-0060" value=3D"+14849620060">+1-484-962-0060</a=
><br>
<br>
-----Original Message-----<br>
From: John Brzozowski &lt;<a href=3D"mailto:John_Brzozowski@Cable.Comcast.c=
om">John_Brzozowski@Cable.<wbr>Comcast.com</a>&gt;<br>
Date: Sunday, July 16, 2017 at 20:28<br>
To: &quot;<a href=3D"mailto:draft-jjmb-v6ops-ietf-ipv6-only-incremental@iet=
f.org">draft-jjmb-v6ops-ietf-ipv6-<wbr>only-incremental@ietf.org</a>&quot; =
&lt;<a href=3D"mailto:draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org"=
>draft-jjmb-v6ops-ietf-ipv6-<wbr>only-incremental@ietf.org</a>&gt;<br>
Cc: Randy Bush &lt;<a href=3D"mailto:randy@psg.com">randy@psg.com</a>&gt;, =
Alissa Cooper &lt;<a href=3D"mailto:alissa@cooperw.in">alissa@cooperw.in</a=
>&gt;, Jim Martin &lt;<a href=3D"mailto:jim@daedelus.com">jim@daedelus.com<=
/a>&gt;, Jari Arkko &lt;<a href=3D"mailto:jari.arkko@piuha.net">jari.arkko@=
piuha.net</a>&gt;, Suresh Krishnan &lt;<a href=3D"mailto:suresh.krishnan@gm=
ail.com">suresh.krishnan@gmail.com</a>&gt;, Russ Housley &lt;<a href=3D"mai=
lto:housley@vigilsec.com">housley@vigilsec.com</a>&gt;<br>
Subject: Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings<br>
<br>
=C2=A0 =C2=A0 Folks,<br>
<br>
=C2=A0 =C2=A0 Apologies in advance for the gratuitous cross posting (v6ops,=
 ietf, ipv6, sunset4, softwires).=C2=A0 I hope, to you all, this is worth t=
he added email.<br>
<br>
=C2=A0 =C2=A0 The draft below was written to provide the necessary document=
ation to enable the IETF (the NOC, participants, etc.) to migrate to an IPv=
6 only primary network connection (Wi-Fi and wired) that utilizes NAT64+DNS=
64 to access IPv4 only content.=C2=A0 The request for IETF 99 has been to h=
ave the primary =E2=80=9Cietf=E2=80=9D SSID adhere to what is documented in=
 the I-D below.=C2=A0 I trust the motivation is understood.=C2=A0 This mean=
s that the main =E2=80=9Cietf=E2=80=9D SSID would be switched to be IPv6 on=
ly with NAT64+DNS64 (at layer 3) per the I-D below.=C2=A0 Given the that IE=
TF99 is upon us, this may or may not be entirely possible.<br>
<br>
=C2=A0 =C2=A0 At this stage, the infrastructure preparations for IETF 99 sh=
ould be in place to ensure that the IETF has the necessary hardware for red=
undancy and performance.<br>
<br>
=C2=A0 =C2=A0 So, we are all seeking your input.=C2=A0 Given the above, wha=
t would all you suggest is tolerable for IETF99 as it pertains to the I-D b=
elow?<br>
<br>
=C2=A0 =C2=A0 =E2=80=A2 IPv6 only per the I-D for the balance of IETF week?=
<br>
=C2=A0 =C2=A0 =E2=80=A2 IPv6 only per the I-D for one or more days this wee=
k?<br>
=C2=A0 =C2=A0 =E2=80=A2 IPv6 only per the I-D for the plenary?<br>
=C2=A0 =C2=A0 =E2=80=A2 IPv6 only per the I-D for the next IETF meeting?<br=
>
<br>
=C2=A0 =C2=A0 Please send us your feedback.<br>
<br>
=C2=A0 =C2=A0 Regards,<br>
<br>
=C2=A0 =C2=A0 John<br>
=C2=A0 =C2=A0 +1-484-962-0060<br>
<br>
=C2=A0 =C2=A0 -----Original Message-----<br>
=C2=A0 =C2=A0 From: &quot;<a href=3D"mailto:internet-drafts@ietf.org">inter=
net-drafts@ietf.org</a>&quot; &lt;<a href=3D"mailto:internet-drafts@ietf.or=
g">internet-drafts@ietf.org</a>&gt;<br>
=C2=A0 =C2=A0 Date: Saturday, July 1, 2017 at 03:04<br>
=C2=A0 =C2=A0 To: Marcus Keane &lt;<a href=3D"mailto:marcus.keane@microsoft=
.com">marcus.keane@microsoft.com</a>&gt;, Jen Linkova &lt;<a href=3D"mailto=
:furry@google.com">furry@google.com</a>&gt;, Lorenzo Colitti &lt;<a href=3D=
"mailto:lorenzo@google.com">lorenzo@google.com</a>&gt;, John Brzozowski &lt=
;<a href=3D"mailto:John_Brzozowski@Cable.Comcast.com">John_Brzozowski@Cable=
.<wbr>Comcast.com</a>&gt;, Erik Kline &lt;<a href=3D"mailto:ek@google.com">=
ek@google.com</a>&gt;, John Brzozowski &lt;<a href=3D"mailto:John_Brzozowsk=
i@Cable.Comcast.com">John_Brzozowski@Cable.<wbr>Comcast.com</a>&gt;, David =
Schinazi &lt;<a href=3D"mailto:dschinazi@apple.com">dschinazi@apple.com</a>=
&gt;, Stuart Cheshire &lt;<a href=3D"mailto:cheshire@apple.com">cheshire@ap=
ple.com</a>&gt;, Jen Linkova &lt;<a href=3D"mailto:furry@google.com">furry@=
google.com</a>&gt;, Paul Saab &lt;<a href=3D"mailto:ps@fb.com">ps@fb.com</a=
>&gt;, David Schinazi &lt;<a href=3D"mailto:dschinazi@apple.com">dschinazi@=
apple.com</a>&gt;<br>
=C2=A0 =C2=A0 Subject: New Version Notification for draft-jjmb-v6ops-ietf-i=
pv6-<wbr>only-incremental-00.txt<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 A new version of I-D, draft-jjmb-v6ops-ietf-ipv=
6-<wbr>only-incremental-00.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 has been successfully submitted by John Jason B=
rzozowski and posted to the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 IETF repository.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0d=
raft-jjmb-v6ops-ietf-ipv6-<wbr>only-incremental<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A000<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Increm=
ental Deployment of IPv6-only Wi-Fi for IETF Meetings<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Document date:=C2=A0 2017-06-30<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Indivi=
dual Submission<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 15<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <=
a href=3D"https://www.ietf.org/internet-drafts/draft-jjmb-v6ops-ietf-ipv6-o=
nly-incremental-00.txt" rel=3D"noreferrer" target=3D"_blank">https://www.ie=
tf.org/internet-<wbr>drafts/draft-jjmb-v6ops-ietf-<wbr>ipv6-only-incrementa=
l-00.txt</a><br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a hre=
f=3D"https://datatracker.ietf.org/doc/draft-jjmb-v6ops-ietf-ipv6-only-incre=
mental/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/=
<wbr>doc/draft-jjmb-v6ops-ietf-<wbr>ipv6-only-incremental/</a><br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"=
https://tools.ietf.org/html/draft-jjmb-v6ops-ietf-ipv6-only-incremental-00"=
 rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<wbr>draf=
t-jjmb-v6ops-ietf-ipv6-<wbr>only-incremental-00</a><br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"=
https://datatracker.ietf.org/doc/html/draft-jjmb-v6ops-ietf-ipv6-only-incre=
mental-00" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.or=
g/<wbr>doc/html/draft-jjmb-v6ops-<wbr>ietf-ipv6-only-incremental-00</a><br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Abstract:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0The purpose of this document is to=
 provide a blueprint and guidance<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0for deploying IPv6-only Wi-Fi at I=
ETF meetings.=C2=A0 This document<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0outlines infrastructure and operat=
ional guidance that operators<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0should consider when deploying IPv=
6-only networks using NAT64 and<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0DNS64 to support communication to =
legacy IPv4-only services.<br>
<br>
<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Please note that it may take a couple of minute=
s from the time of submission<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 until the htmlized version and diff are availab=
le at <a href=3D"http://tools.ietf.org" rel=3D"noreferrer" target=3D"_blank=
">tools.ietf.org</a>.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 The IETF Secretariat<br>
<br>
<br>
<br>
<br>
<br>
<br>
</blockquote></div><br></div>

--94eb2c1a0650d4669a055566ab39--


From nobody Fri Jul 28 14:17:13 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57FAD132189 for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 14:17:12 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-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 VTZyUZZ9y-M7 for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 14:17:09 -0700 (PDT)
Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::22b]) (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 6D6DF132185 for <ietf@ietf.org>; Fri, 28 Jul 2017 14:17:09 -0700 (PDT)
Received: by mail-qt0-x22b.google.com with SMTP id a18so67299679qta.0 for <ietf@ietf.org>; Fri, 28 Jul 2017 14:17:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=cik2KZlFKOzY1SGIfbBUvf5IOvDTImXyb5EIuvH6hY4=; b=mH5Thg5VpYcBkJlR1Auus63Kn3kKMrf6EjDJgLbfkUTZ9BWNk4O20WiIhG/ECr+1z4 SWl9Y40Ui8OCjNO7K7fECg4F1UCJjvQI0h8ItC1ow1cstJz4esSd13CbQZ3xgqrKQnHg oujyQ/qvI/kYRCR+ZIbsenIwgYRrspEW1N+V9y9NCS3MG8hkkADqiLd45BMhKC5WHwL8 7cFeLxQcY9e2DKUr/i2ja1xj4qHaNdK7HwQAZQtexHeHlZ/NSoEjIzDPDJgm2U2w/e1z FT5dP0XTvex08nuklpOJ+EgFVLD/Cj+lG8+ckz0IuCaxdjfa3bTZP4h+YQcRkkY2B8sv 0q5Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=cik2KZlFKOzY1SGIfbBUvf5IOvDTImXyb5EIuvH6hY4=; b=Vmi5rwS4hqapDgUd0bIFQBfcmMHM+d61oPioOqILH2vXIQ5p7AO6GG5lMV+PZoAxu/ iDJVLnZtUc9FFeQpjerjzaA8OLn2Akx1KSbU7xqd34ZOh4alNt6jUgA2wCFnwG5SB6wA hEmbaFV3jf0wDkDtRy+NMqktCN80daaU+cZ3JoU81WFK+D+6v8xi7fuiQyM5o2GcY2cY Jpa2DD5l+uPVvh8qMbFonKRVhOK4L8dQKFiOqchMDX2PIQ6tZaf7elUSvy80ruiPDfEb DjGNBxe0u7S6sU9e2sf89rYwm/nVlXWkU6s7JfG+RY8PfngLXHWUZQaFKTInzEV9Pe4n 3WMw==
X-Gm-Message-State: AIVw112PnU3qBrxfiSAHSq03VvxSdOQhmM6RRrcyauPkqxUPfHzGIsP/ QGbTHuYLt2YL4dhl
X-Received: by 10.200.47.247 with SMTP id m52mr13023840qta.187.1501276628547;  Fri, 28 Jul 2017 14:17:08 -0700 (PDT)
Received: from macbook-pro-6.w50.lede.home (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id z47sm16584273qth.86.2017.07.28.14.17.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 Jul 2017 14:17:07 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_2AD6610B-C2FA-42DF-972F-248112B73423"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Fri, 28 Jul 2017 17:17:06 -0400
In-Reply-To: <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com>
Cc: "Brzozowski, John" <John_Brzozowski@comcast.com>, "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,  Suresh Krishnan <suresh.krishnan@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
To: Eric Rescorla <ekr@rtfm.com>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/J-tTP34ERV5chfZIdeu0VYIXs7E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 21:17:12 -0000

--Apple-Mail=_2AD6610B-C2FA-42DF-972F-248112B73423
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jul 28, 2017, at 4:38 PM, Eric Rescorla <ekr@rtfm.com> wrote:
> I'm not very enthusiastic about this. People come to the IETF to do =
work and having
> to deal with potential bustage from this experiment gets in the way of =
that.

If you encounter bustage, you can switch to the legacy network.   You =
aren't the first person to raise this point, but I find it a bit =
perplexing.



--Apple-Mail=_2AD6610B-C2FA-42DF-972F-248112B73423
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jul 28, 2017, at 4:38 PM, Eric Rescorla &lt;<a =
href=3D"mailto:ekr@rtfm.com" class=3D"">ekr@rtfm.com</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">I'm not very enthusiastic about =
this. People come to the IETF to do work and having</span><div =
style=3D"font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D"">to =
deal with potential bustage from this experiment gets in the way of =
that.</div></div></blockquote><br class=3D""></div><div>If you encounter =
bustage, you can switch to the legacy network. &nbsp; You aren't the =
first person to raise this point, but I find it a bit =
perplexing.</div><div><br class=3D""></div><br class=3D""></body></html>=

--Apple-Mail=_2AD6610B-C2FA-42DF-972F-248112B73423--


From nobody Fri Jul 28 14:40:46 2017
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24DF01321AA; Fri, 28 Jul 2017 14:40:45 -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 cF3QWja0yIAq; Fri, 28 Jul 2017 14:40:43 -0700 (PDT)
Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::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 9B0B51321A8; Fri, 28 Jul 2017 14:40:43 -0700 (PDT)
Received: by mail-oi0-x235.google.com with SMTP id e124so183605566oig.2; Fri, 28 Jul 2017 14:40:43 -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=+AwBs4Y7+IwurytxrOeLYMD//9hWfyuYE/9JFGyAMGc=; b=JcxEKUJRDo9CInwp0Rlvbcb911ZjRL46IqhntAzNPgsAlnyOgC+4AVphkyO2fteYLD 7LCPWW2Jg3OijqZm/1LhVKDcE1xcMALBnVZDLhfO7LCJgXFnFvnAYgS07mu1zGeUlumA fy1MwnlJss2QH7V3hUYuLuRcLFaZuKs1LODkHDixOxWfvgOkLgVSJetitdpHrHwoU+xP 02JLahC1fXER9GPNIhnj+Bzag9ilzaDRI3nqx2lWDNKWxKqRzWFqxHMdMiXoaOi/zTJx XNrsyVYWLEPerxhu5NQ9PaKsbNdZ5EQ6bEuuu+GkSDwf4VZEf1WK4tpRDNNvvcX2eEoD I6IA==
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=+AwBs4Y7+IwurytxrOeLYMD//9hWfyuYE/9JFGyAMGc=; b=aX8pKBG9HxJIl/j8Cyp/VrlHUtql5CmAoeOWg93OfxhR6sCK8rvc6M/2gE6IRCqRDq MyuvbVmwx2huwrj/oLkwmtULRLNLIrx65a43wMin0iq8GpP3RkIOCbSAsXS4QpF2jiiX bcpE3vA+fubOmFFsBiunmTkKz/T0t03+u+LwgOIB1UHVAF/syJKyuigMiDWAxU4SHOQb 4VKS8bYdZzbuoZGxibgiO7hRLfTh46Ro98Jp/KYq/XUUksAMR7cUSONx+6EGO51RH72J NV9E4caZAXnFx79qPyG1IY47TIlsd8SK8UfmMe8yMHoO58sX1a17ELph/PVtePUlc9ic yKZQ==
X-Gm-Message-State: AIVw11162daeWKWKiiCxck5I5dq6p9r4sJ8POir5IxaMkVebV6QYqC13 Jxk5VytCaErPOpCKpqArMpwDUoFPVQ==
X-Received: by 10.202.173.209 with SMTP id w200mr7504553oie.170.1501278043000;  Fri, 28 Jul 2017 14:40:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.232.34 with HTTP; Fri, 28 Jul 2017 14:40:22 -0700 (PDT)
In-Reply-To: <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Fri, 28 Jul 2017 17:40:22 -0400
Message-ID: <CAA=duU1y8y97f6fBau-g2Oc8uuzmoQMbb96di3HEqjv+Vo6_AA@mail.gmail.com>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: Ted Lemon <mellon@fugue.com>
Cc: Eric Rescorla <ekr@rtfm.com>,  "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,  Suresh Krishnan <suresh.krishnan@gmail.com>,  "Brzozowski, John" <John_Brzozowski@comcast.com>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a113cf6827658030555678867"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KBT-iXKWB68SewqJOwG-SWvE1_k>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 21:40:45 -0000

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

Ted,

As one example, I have a VPN application over which I have no control that
I must use to reach corporate resources, including email. I haven=E2=80=99t=
 yet had
a chance to try it with V6 and nat64, maybe it=E2=80=99ll work and maybe it=
 won=E2=80=99t.
If it doesn=E2=80=99t, I=E2=80=99ll need to use the legacy network, which i=
s currently
unencrypted. We would need to include a new SSID for an encrypted v4/v6
network (what we currently deliver on the =E2=80=9Cietf=E2=80=9D SSID). If =
that new SSID is
provided, then I=E2=80=99ll be OK with the migration.

Thanks,
Andy

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

<div dir=3D"ltr">Ted,<div><br></div><div>As one example, I have a VPN appli=
cation over which I have no control that I must use to reach corporate reso=
urces, including email. I haven=E2=80=99t yet had a chance to try it with V=
6 and nat64, maybe it=E2=80=99ll work and maybe it won=E2=80=99t. If it doe=
sn=E2=80=99t, I=E2=80=99ll need to use the legacy network, which is current=
ly unencrypted. We would need to include a new SSID for an encrypted v4/v6 =
network (what we currently deliver on the =E2=80=9Cietf=E2=80=9D SSID). If =
that new SSID is provided, then I=E2=80=99ll be OK with the migration.</div=
><div><br></div><div>Thanks,</div><div>Andy</div><div><br></div></div>

--001a113cf6827658030555678867--


From nobody Fri Jul 28 14:44:46 2017
Return-Path: <adam@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4DCB1321AA for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 14:44:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.881
X-Spam-Level: 
X-Spam-Status: No, score=-1.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 mmnm3WgK1dUe for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 14:44:43 -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 ED986131DA7 for <ietf@ietf.org>; Fri, 28 Jul 2017 14:44:42 -0700 (PDT)
Received: from Orochi.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v6SLiUAm052098 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 28 Jul 2017 16:44:34 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Orochi.local
Subject: Re: Visiting Singapore/Customs Clearance
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Mary B <mary.h.barnes@gmail.com>, Mike StJohns <mstjohns@comcast.net>
Cc: "Gary E. Miller" <gem@rellim.com>, IETF discussion list <ietf@ietf.org>
References: <73ae5759-32a7-38fb-3232-9630a4dd6faa@gmail.com> <20170726222602.72dc27ab@spidey.rellim.com> <CABmDk8m3V7dPi-qNn3sig89_keOaepo29_GAyEr+__MjUrLLHA@mail.gmail.com> <4C169449-D1E2-4F9C-8163-CF3B5A067772@comcast.net> <CABmDk8kWr_NSh_r2JCeVST929UJVXFwPPkxAf9+k6_PBuQmmsw@mail.gmail.com> <45b53222-7c78-939d-3819-d567c70ea60e@gmail.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <23ef12f9-bb92-fbad-b1c3-ba3312cf1711@nostrum.com>
Date: Fri, 28 Jul 2017 16:44:24 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <45b53222-7c78-939d-3819-d567c70ea60e@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ch2lJztPikLAxkAaUifYGuct57c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 21:44:45 -0000

On 7/27/17 18:00, Brian E Carpenter wrote:
> If I carry a decongestant, it's one based on phenylephrine.


Empirically, what you're carrying around isn't a decongestant, then.

https://www.ncbi.nlm.nih.gov/pubmed/19230461

Save your money and take sugar pills.

/a


From nobody Fri Jul 28 14:51:00 2017
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBA4C131CCA; Fri, 28 Jul 2017 14:50:57 -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] 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 74dp2PJH7WP8; Fri, 28 Jul 2017 14:50:56 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 A012012942F; Fri, 28 Jul 2017 14:50:54 -0700 (PDT)
Received: from [169.254.181.124] (142-254-101-176.dsl.dynamic.fusionbroadband.com [142.254.101.176]) (authenticated bits=0) by mail.proper.com (8.15.2/8.14.9) with ESMTPSA id v6SLo2rG090365 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 28 Jul 2017 14:50:03 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 142-254-101-176.dsl.dynamic.fusionbroadband.com [142.254.101.176] claimed to be [169.254.181.124]
From: "Paul Hoffman" <paul.hoffman@vpnc.org>
To: "ietf@ietf.org" <ietf@ietf.org>
Cc: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Fri, 28 Jul 2017 14:50:52 -0700
Message-ID: <B8D4A14E-7A79-4D72-9278-A3F89A343596@vpnc.org>
In-Reply-To: <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.6r5347)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8y0j-ei6L4xL2zFHQPHSQVW5rZ4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 21:50:58 -0000

On 28 Jul 2017, at 14:17, Ted Lemon wrote:

> If you encounter bustage, you can switch to the legacy network.

The legacy network will have a different SSID. All laptops remember 
which SSIDs you have connected to successfully in the past. Thus, it is 
likely that if you encounter problems and have to switch to the 
example-ssid-legacy SSID, and you close your laptop to move to a new 
room and open it again, you'll be put back onto the ietf SSID.

The only way around this repeated problem is to *remove* the ietf SSID 
from the list of your trusted SSIDs. This is not only an additional 
step, but it is one that has effects on future IETF meetings.

Further, section 4.1 of the draft has no instructions for end users of 
various versions of various operating systems. The draft assumes that 
everyone attending an IETF meeting understands SLAAC and RA options and 
how they are set on their laptops: that assumption is demonstrably 
false, quite possibly for the majority of IETF attendees.

If we want to have a real dogfood test, the first step is documentation, 
not forced breakage for a significant portion of the attendees.

--Paul Hoffman


From nobody Fri Jul 28 15:15:09 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21F4B1321C4 for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 15:14:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 7lpew5TCL6vf for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 15:14:55 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 C724C126D46 for <ietf@ietf.org>; Fri, 28 Jul 2017 15:14:55 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dbDX2-0005WK-Hx; Fri, 28 Jul 2017 22:14:54 +0000
Date: Sat, 29 Jul 2017 07:14:51 +0900
Message-ID: <m2379gjjj8.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: Announcement on IETF 100 Hotel Reservations
In-Reply-To: <CAKKJt-eD2YVyZVQzxYaDO9RJv5_r6EBT8ipCV9juyj0RuyeoiQ@mail.gmail.com>
References: <150108971740.23120.257371533321943899.idtracker@ietfa.amsl.com> <EF2F4195-A97F-46CB-B2D2-DB7A5E11874F@gmail.com> <m2o9s6lfy7.wl-randy@psg.com> <CAKKJt-eD2YVyZVQzxYaDO9RJv5_r6EBT8ipCV9juyj0RuyeoiQ@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EDQR1jPdpVDyoI10VSV1qJWBVak>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 22:14:57 -0000

hint: there are only two words you need to know, "hawkers' markets."

we should all register so we can move off the ietf list and to the
attendees' list.

randy


From nobody Fri Jul 28 15:20:09 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EACE1321C7 for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 15:20:07 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-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 ssy_kBO8yidR for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 15:20:04 -0700 (PDT)
Received: from mail-qt0-x22e.google.com (mail-qt0-x22e.google.com [IPv6:2607:f8b0:400d:c0d::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 6F40E131CEB for <ietf@ietf.org>; Fri, 28 Jul 2017 15:20:04 -0700 (PDT)
Received: by mail-qt0-x22e.google.com with SMTP id v29so65740829qtv.3 for <ietf@ietf.org>; Fri, 28 Jul 2017 15:20:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=9BTDc0E8rD4cDyK1Pt4erKFvXVFnoqFxUpoP6zEmJjI=; b=CbT5eSGqlLqQoru72fE44lRDHLog0ASf4gH7GHtKUWAwEn9w+u0f/F6xqZPsJk3RpB 7XqAQfhaPJ19PhO2zj7kU7zeoblq40yhGSUq362QWpd9nJxzj+w3nGGhsUElGmTotMAJ Ty4ukyULRns2dzgIUIYF2I5dxeRn3ZKsKpAjzeFNF3cYFNKy3KvQEvzOqxjle3Ar0TAh tZtcSucFStzrWPb9/tAIxZqsE6a9CYRx/JWFxEXS6zR3UXPfbcIKthAo/rdXfjmnrh// PYSl1FrxuD1kOsyKnqHWdHKHp05mVLVCLCUf+HnF0Vptny7XdRkXGO/eGdf7HEFiMKhr ZJQA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=9BTDc0E8rD4cDyK1Pt4erKFvXVFnoqFxUpoP6zEmJjI=; b=JaMAmu/Soc2ACuHv2hmmvGC6aAC8BRkgYAw6NkWeAgZC0AityMu4/JZCoAGgKCrRKm W3gZirX9eVbQcD2+uzZnWGxi486TWovx9VgmjlXSnA4ps1Qa0GfqsY2VxU3S6gf5i3Fo h940wKRAXIhdllAZCdI7Kl+UPlH91G0BHwkjfsavJZljYBGSgjSuiAZ9ktdh2ilTirj6 VW6aMT2L3yEwgdVr/KK45gNbWqVh3rttg8lxCwUKOTWfFa9s/OlY09Ph0ObMaWrgCy8S dzJyCzdMe6aD4ijtjgvl9oFUn3nHo5pd4wRwngkUoQEUipEV0L8XT8VAOXFNoxBC0b9q AH9w==
X-Gm-Message-State: AIVw1128UlpA4dyDtzzmqh1PCv7lDBG10gQEo19BQGK59BxSVUKvXSrl fY0xHz5ALxvUD6Wt
X-Received: by 10.200.48.49 with SMTP id f46mr13672516qte.88.1501280403625; Fri, 28 Jul 2017 15:20:03 -0700 (PDT)
Received: from macbook-pro-6.w50.lede.home (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id e66sm15982154qkb.69.2017.07.28.15.20.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 Jul 2017 15:20:02 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <C411E9E5-9ECC-4B61-BD8A-BD7EC6322E5C@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_6EFF898A-CF10-422A-A30E-A2383236BBDD"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Fri, 28 Jul 2017 18:20:02 -0400
In-Reply-To: <CAA=duU1y8y97f6fBau-g2Oc8uuzmoQMbb96di3HEqjv+Vo6_AA@mail.gmail.com>
Cc: Eric Rescorla <ekr@rtfm.com>, "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,  Suresh Krishnan <suresh.krishnan@gmail.com>, "Brzozowski, John" <John_Brzozowski@comcast.com>, "ietf@ietf.org" <ietf@ietf.org>
To: "Andrew G. Malis" <agmalis@gmail.com>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CAA=duU1y8y97f6fBau-g2Oc8uuzmoQMbb96di3HEqjv+Vo6_AA@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pReIVdVL05H7TYWp3zRmp39-34g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 22:20:08 -0000

--Apple-Mail=_6EFF898A-CF10-422A-A30E-A2383236BBDD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Jul 28, 2017, at 5:40 PM, Andrew G. Malis <agmalis@gmail.com> wrote:
> We would need to include a new SSID for an encrypted v4/v6 network =
(what we currently deliver on the =E2=80=9Cietf=E2=80=9D SSID). If that =
new SSID is provided, then I=E2=80=99ll be OK with the migration.

ietf-nat64 would be going away, so I don't think that would be a =
problem.



--Apple-Mail=_6EFF898A-CF10-422A-A30E-A2383236BBDD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jul 28, 2017, at 5:40 PM, Andrew G. Malis &lt;<a =
href=3D"mailto:agmalis@gmail.com" class=3D"">agmalis@gmail.com</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><div =
style=3D"font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D"">We =
would need to include a new SSID for an encrypted v4/v6 network (what we =
currently deliver on the =E2=80=9Cietf=E2=80=9D SSID). If that new SSID =
is provided, then I=E2=80=99ll be OK with the =
migration.</div></div></blockquote><br class=3D""></div><div>ietf-nat64 =
would be going away, so I don't think that would be a =
problem.</div><div><br class=3D""></div><br class=3D""></body></html>=

--Apple-Mail=_6EFF898A-CF10-422A-A30E-A2383236BBDD--


From nobody Fri Jul 28 15:21:52 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DE271321CD for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 15:21:50 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 DqR6C1WPy4XU for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 15:21:47 -0700 (PDT)
Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (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 AFE1C131CEB for <ietf@ietf.org>; Fri, 28 Jul 2017 15:21:47 -0700 (PDT)
Received: by mail-qt0-x22c.google.com with SMTP id 16so46442523qtz.4 for <ietf@ietf.org>; Fri, 28 Jul 2017 15:21:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=ArsSmWv/ahxPOUezMVZeCAGQhriRvLHBy2WI27LcREM=; b=p9xA0QpHss9F78gP/+yW38bTqEyA5jfS4I3hy6W3DnQk4eCDjYY6bnAbxpE8yPO7uN liF3p7UpEqVK3juPstzsHVEXGUxondDR0NEq7iosLKGKDdHERKFkJ5WmIXL/rHGSfNM4 QiyBjWnFY21hapqoAcjsGNT1KATtWMSXW58yXFl2PPQwytLQJnepUEydLxCDLkTjLrse I/7SDVxAupEWIcIjIhHJ98GtNliSEKhYOEM7RCvQen7l6e7XtmrB51nfnCKda5OPKGYH VwMuiAIhK6N0+V80n7kO3RYPsU7JrnpEvBN3tJmV4LJRQy+K9UXp5Wz7OxeEBw3reuK1 4qCg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=ArsSmWv/ahxPOUezMVZeCAGQhriRvLHBy2WI27LcREM=; b=iy5ZyXGCzwDqdwR8OgOZNPD5dkcSIuEpgTH++Aua7vuwQSWTklcyj4il2qknn0txr7 63L3rlMsNd882fA3i0gqVgwQCQgThDD40SbbnYGtEUvvodMKIqAeql2eJPIagxHazdRD CbUyKT77OhJFigEAD3kKeP0cYOrB1QH40COhT1iG5/5jfTUMUBgCfLcecKKqvTpMPrP8 HX7aX62QJvkeLsPVlrF4baVrqWKtjAaO+SW/gyYrRoSsH6xp1peE3glF7hM5eoVzxrpe VT8AFnbr+ahmW+V2lKTuRUSHonv8DCdo9Xy4onBdd5r8eWKySG30u5CV6/a13DcDslLx Hrnw==
X-Gm-Message-State: AIVw110tCpCbiOsNqd6TE9hsNEQDuAvRpIe5VGf+6yGk+NJQo2pf121Q hZc08qD39CcASCg0
X-Received: by 10.200.53.65 with SMTP id z1mr12093040qtb.337.1501280506864; Fri, 28 Jul 2017 15:21:46 -0700 (PDT)
Received: from macbook-pro-6.w50.lede.home (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id c19sm6255585qkg.6.2017.07.28.15.21.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 Jul 2017 15:21:46 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <01D1995D-650F-4B8C-96C3-8694C5E5859A@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3EC13C83-856B-4E3B-9E12-926CDFC6D5B7"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Fri, 28 Jul 2017 18:21:45 -0400
In-Reply-To: <B8D4A14E-7A79-4D72-9278-A3F89A343596@vpnc.org>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <B8D4A14E-7A79-4D72-9278-A3F89A343596@vpnc.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/luTMQwNLCoGhSQwJSfhUqC9TrPk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 22:21:50 -0000

--Apple-Mail=_3EC13C83-856B-4E3B-9E12-926CDFC6D5B7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jul 28, 2017, at 5:50 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
> The legacy network will have a different SSID. All laptops remember =
which SSIDs you have connected to successfully in the past. Thus, it is =
likely that if you encounter problems and have to switch to the =
example-ssid-legacy SSID, and you close your laptop to move to a new =
room and open it again, you'll be put back onto the ietf SSID.

This is a good point.   Arguably, we should use a different SSID every =
IETF.   E.g., ietf-100 instead of ietf.   We're already proposing to do =
that for ietf-legacy so that people don't automatically associate with =
that ssid.

So if ietf goes away in favor of ietf-100, and ietf-hotel becomes =
ietf-100-hotel (or something like that), then would that address your =
objection?


--Apple-Mail=_3EC13C83-856B-4E3B-9E12-926CDFC6D5B7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jul 28, 2017, at 5:50 PM, Paul Hoffman &lt;<a =
href=3D"mailto:paul.hoffman@vpnc.org" =
class=3D"">paul.hoffman@vpnc.org</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">The legacy network will have a different =
SSID. All laptops remember which SSIDs you have connected to =
successfully in the past. Thus, it is likely that if you encounter =
problems and have to switch to the example-ssid-legacy SSID, and you =
close your laptop to move to a new room and open it again, you'll be put =
back onto the ietf SSID.</span></div></blockquote></div><br =
class=3D""><div class=3D"">This is a good point. &nbsp; Arguably, we =
should use a different SSID every IETF. &nbsp; E.g., ietf-100 instead of =
ietf. &nbsp; We're already proposing to do that for ietf-legacy so that =
people don't automatically associate with that ssid.</div><div =
class=3D""><br class=3D""></div><div class=3D"">So if ietf goes away in =
favor of ietf-100, and ietf-hotel becomes ietf-100-hotel (or something =
like that), then would that address your objection?</div><div =
class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_3EC13C83-856B-4E3B-9E12-926CDFC6D5B7--


From nobody Fri Jul 28 15:33:48 2017
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EDA5131CCE; Fri, 28 Jul 2017 15:33:47 -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] 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 yAPEshoTjkW1; Fri, 28 Jul 2017 15:33:45 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 A912B131761; Fri, 28 Jul 2017 15:33:45 -0700 (PDT)
Received: from [169.254.181.124] (142-254-101-176.dsl.dynamic.fusionbroadband.com [142.254.101.176]) (authenticated bits=0) by mail.proper.com (8.15.2/8.14.9) with ESMTPSA id v6SMWn8I092785 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 28 Jul 2017 15:32:50 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 142-254-101-176.dsl.dynamic.fusionbroadband.com [142.254.101.176] claimed to be [169.254.181.124]
From: "Paul Hoffman" <paul.hoffman@vpnc.org>
To: "Ted Lemon" <mellon@fugue.com>
Cc: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Fri, 28 Jul 2017 15:33:38 -0700
Message-ID: <AD12C52C-90E4-48D3-98EA-35F78DCBCBED@vpnc.org>
In-Reply-To: <01D1995D-650F-4B8C-96C3-8694C5E5859A@fugue.com>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <B8D4A14E-7A79-4D72-9278-A3F89A343596@vpnc.org> <01D1995D-650F-4B8C-96C3-8694C5E5859A@fugue.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.6r5347)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/m6C-Gc4Y5Fh8rdzwjVMJgKp1-Yo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 22:33:47 -0000

On 28 Jul 2017, at 15:21, Ted Lemon wrote:

> So if ietf goes away in favor of ietf-100, and ietf-hotel becomes 
> ietf-100-hotel (or something like that), then would that address your 
> objection?

That would fix the first problem, but your response skipped over the 
harder part:

Further, section 4.1 of the draft has no instructions for end users of 
various versions of various operating systems. The draft assumes that 
everyone attending an IETF meeting understands SLAAC and RA options and 
how they are set on their laptops: that assumption is demonstrably 
false, quite possibly for the majority of IETF attendees.

If we want to have a real dogfood test, the first step is documentation, 
not forced breakage for a significant portion of the attendees.

--Paul Hoffman


From nobody Fri Jul 28 15:41:02 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1A291321C1 for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 15:40:59 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-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 aszbgfbw7ISJ for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 15:40:58 -0700 (PDT)
Received: from mail-qt0-x233.google.com (mail-qt0-x233.google.com [IPv6:2607:f8b0:400d:c0d::233]) (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 CFF6C127ABE for <ietf@ietf.org>; Fri, 28 Jul 2017 15:40:57 -0700 (PDT)
Received: by mail-qt0-x233.google.com with SMTP id 16so46594323qtz.4 for <ietf@ietf.org>; Fri, 28 Jul 2017 15:40:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=5IYpcgQAUZW10KLhXjdxOSnsduaMYrjp9V59NkLwbPA=; b=eXLJZl0HrHuMu7sQU/K4VD8apVIsm6lJoMFcSykBLyxUXkH7ujPHoKRaK+un4x8iBI SWditc3NCVMqfzH92YChtMy94WNqtYfLcOd3STlNt4XiBJVl+1GyjUIpBcEzqcRc4/ha 6cnlZXKad1/hwOHYUHBonT+akDkFABrrSUpKQEjd3ahVQ1zq0dMRgSbFzg1747C6a7hL 6m8AF+r7gewmFcg6JeyvAoHNizkfg7KzlC3abP/SEotPibzwnqCNCVZwcsa1dZJXvVZi j7o51Q/8GYxd2lkWCzrMErROfbTVPXvaOHg0Z4Wvx4sTrLjFbjLSwuzO+o3gG6JBh2Iu Ukhw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=5IYpcgQAUZW10KLhXjdxOSnsduaMYrjp9V59NkLwbPA=; b=aKQgbZ6DdcFsCC9GITo1ucPUFOW46nKsgavUKGLiOoLcu8uOwQKUP94UebWUQe8b4F AH34kiYqP+z4qWEXKsmHoHvJztPzNdenzK1VkEtTWeHn54hssmkEjKq/SDUaUXgqKw44 6MBKpi0YD4WtRysSUL8f+lG4vDf5K9B+UKkb0C6QnkG+5KSvOI/Yoip7jgNtTcn3eOX5 QHJ+PIJlDW0fZNg+bo4ktxQvzsdsdqUOragqPtQ/W6BCMJ6IL9bU/oDv5J3fB9AaqekJ cxZ+3FQXlZKXD4tZQb0ZXDXoMoCD0A76yBIVPr1N+ZQWu4I6wwdkdjGBBvIgBw7PR89/ iIUw==
X-Gm-Message-State: AIVw111OEHk0o+WoqVQQ7C7qK2+3DiMdhsQnwk3UPsRcwUkDqOn99DNW OkjL3T8cbYd8a0a5fKJmNg==
X-Received: by 10.200.45.240 with SMTP id q45mr13470590qta.332.1501281656983;  Fri, 28 Jul 2017 15:40:56 -0700 (PDT)
Received: from macbook-pro-6.w50.lede.home (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id i8sm15824680qtb.40.2017.07.28.15.40.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 Jul 2017 15:40:56 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <A8DE10F1-B72F-4543-B0EB-34A9F87E8AAD@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5FFE3143-E374-4F6F-B81E-40D3E0AF6FC2"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Fri, 28 Jul 2017 18:40:55 -0400
In-Reply-To: <AD12C52C-90E4-48D3-98EA-35F78DCBCBED@vpnc.org>
Cc: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <B8D4A14E-7A79-4D72-9278-A3F89A343596@vpnc.org> <01D1995D-650F-4B8C-96C3-8694C5E5859A@fugue.com> <AD12C52C-90E4-48D3-98EA-35F78DCBCBED@vpnc.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/o-3gnhxwt5dA1IkbH5i5z_-Mz74>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 22:41:00 -0000

--Apple-Mail=_5FFE3143-E374-4F6F-B81E-40D3E0AF6FC2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jul 28, 2017, at 6:33 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
> If we want to have a real dogfood test, the first step is =
documentation, not forced breakage for a significant portion of the =
attendees.

I don't actually know of any devices that would require manual =
configuration.   Maybe Linux with NetworkMangler?   If it were indeed =
the belief of the authors of the draft that any such configuration were =
required, I'm sure they would have mentioned it.   For any user for whom =
such configuration is required, I would argue that that user is =
experiencing brokenness, and should switch to the legacy network and =
report the problem, rather than attempting manual intervention.

The status quo as far as I am aware is that all modern operating systems =
support v6-only out of the box.   That's why this experiment makes sense =
now.   Even two years ago, that would not have been the case.   =
Hopefully nobody comes to IETF running unpatched, ancient software...


--Apple-Mail=_5FFE3143-E374-4F6F-B81E-40D3E0AF6FC2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jul 28, 2017, at 6:33 PM, Paul Hoffman &lt;<a =
href=3D"mailto:paul.hoffman@vpnc.org" =
class=3D"">paul.hoffman@vpnc.org</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">If we want to have a real dogfood test, =
the first step is documentation, not forced breakage for a significant =
portion of the attendees.</span></div></blockquote></div><br =
class=3D""><div class=3D"">I don't actually know of any devices that =
would require manual configuration. &nbsp; Maybe Linux with =
NetworkMangler? &nbsp; If it were indeed the belief of the authors of =
the draft that any such configuration were required, I'm sure they would =
have mentioned it. &nbsp; For any user for whom such configuration <i =
class=3D"">is</i>&nbsp;required, I would argue that that user is =
experiencing brokenness, and should switch to the legacy network and =
report the problem, rather than attempting manual =
intervention.</div><div class=3D""><br class=3D""></div><div =
class=3D"">The status quo as far as I am aware is that all modern =
operating systems support v6-only out of the box. &nbsp; That's why this =
experiment makes sense now. &nbsp; Even two years ago, that would not =
have been the case. &nbsp; Hopefully nobody comes to IETF running =
unpatched, ancient software...</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_5FFE3143-E374-4F6F-B81E-40D3E0AF6FC2--


From nobody Fri Jul 28 15:42:33 2017
Return-Path: <dorian@blackrose.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92847131C2E; Fri, 28 Jul 2017 15:42:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 tVDC00BHEXD8; Fri, 28 Jul 2017 15:42:28 -0700 (PDT)
Received: from thorn.blackrose.org (thorn.blackrose.org [192.131.22.7]) by ietfa.amsl.com (Postfix) with ESMTP id 6BBC6127601; Fri, 28 Jul 2017 15:42:28 -0700 (PDT)
Received: from [10.0.1.28] (c-68-49-163-78.hsd1.mi.comcast.net [68.49.163.78]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by thorn.blackrose.org (Postfix) with ESMTP id 971061AA801D; Fri, 28 Jul 2017 18:42:27 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
From: Dorian Kim <dorian@blackrose.org>
In-Reply-To: <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com>
Date: Fri, 28 Jul 2017 18:42:26 -0400
Cc: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,  Suresh Krishnan <suresh.krishnan@gmail.com>, "Brzozowski, John" <John_Brzozowski@comcast.com>, "ietf@ietf.org" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E1412C0A-28AA-4143-9944-A175F3EB2161@blackrose.org>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SzPql1pmmzovrU1vbvlFolVo3xw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 22:42:30 -0000

Doesn=E2=80=99t this all assume being able to get functional IPv6 =
connectivity to IETF meeting sites?

-dorian


From nobody Fri Jul 28 16:00:11 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C45D9131D34 for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 16:00:09 -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, 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=fugue-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 xfJe8xK1awse for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 16:00:08 -0700 (PDT)
Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::22c]) (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 39298131461 for <ietf@ietf.org>; Fri, 28 Jul 2017 16:00:08 -0700 (PDT)
Received: by mail-qk0-x22c.google.com with SMTP id x191so59786216qka.5 for <ietf@ietf.org>; Fri, 28 Jul 2017 16:00:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=qnL+ahj+ywal5Xey0i7oDFxx7uJiNgsWcpl9an3miu0=; b=edtxjKBlEKLcXkh6L+LWlowvTRgCKeVigVgWCdfUeT8K2Ik+qt4iXsoqxcK2qxCI71 l3MU0Ju5O5Y4HWqhAby6/t5qz0QoJw6OzUG3plKJ/XAzBuYWzM6H2lNiKhey04Eor+EK x4pCbRu2Jpt03wH2NjqVSU4wY1PHf8qx4apg/CGLH+0dZbZreiPNwSOnfXfB9KQykumm ygwLLUajm1TIlFw3Qg4aA6PJI2SzHRAj212YoBVFqVQvvDDqEEh0Ll0qP8EEOWL6YkE2 aGbt0rlLfhYxXIsUCrLsf2WA+DeXUyUnpzq4AVb+lvD5AsttHhG5SxYE4ckg5WpT6ps8 nfpg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=qnL+ahj+ywal5Xey0i7oDFxx7uJiNgsWcpl9an3miu0=; b=ElcKDbHcNi2hEz12eA/VVP5phLn3Y3pTpAqxsE4IPFeQEGtJYWUbWNWSaIx+7Mwrn8 1KR8MCweDc8kgpa1Uru8FAIQ8aFcVftERYU7xxRwaJILlDZlXwqOeQho+s6lPKRyEHru w15hOA5JRwsfhCZbpnfMEzwpzpWmtWwsFfg/QZTmkLRpLamLn0dKXZp9XRrEhE5QpzmN l4cdnVdFU/742Vpgi9DuOv+V+jXV7FFW307dXJgF57V5aqkPNy+sx8RQUV5QY7innaIK a3P9DCfJ81gq1EOcqMN/8FwMQPhu1TfWJc8G8mjL5p48L0e4RUigatGjvU3zkAWfhwXg YUGw==
X-Gm-Message-State: AIVw111jZ8SBBATbEHuyIQd1q8QxRaetAktcm+W9zTrabSr3/OpYQEnt 7Q27kr5aMCcj8V6sTMJYJw==
X-Received: by 10.55.168.140 with SMTP id r134mr13001338qke.204.1501282807199;  Fri, 28 Jul 2017 16:00:07 -0700 (PDT)
Received: from macbook-pro-6.w50.lede.home (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id f20sm9086030qta.58.2017.07.28.16.00.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 Jul 2017 16:00:06 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <AE97CB86-B138-4720-93D4-634FA40CC91E@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8152E439-2CE0-4814-B35D-4BDB5E3181CB"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Fri, 28 Jul 2017 19:00:04 -0400
In-Reply-To: <E1412C0A-28AA-4143-9944-A175F3EB2161@blackrose.org>
Cc: "ietf@ietf.org" <ietf@ietf.org>
To: Dorian Kim <dorian@blackrose.org>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <E1412C0A-28AA-4143-9944-A175F3EB2161@blackrose.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/atkrMSqdVVi-PZMaEc-1LNEZA0E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 23:00:10 -0000

--Apple-Mail=_8152E439-2CE0-4814-B35D-4BDB5E3181CB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Jul 28, 2017, at 6:42 PM, Dorian Kim <dorian@blackrose.org> wrote:
> Doesn=E2=80=99t this all assume being able to get functional IPv6 =
connectivity to IETF meeting sites?

We've been doing that for a long time now.   Don't see any reason why it =
would be a problem in .sg.


--Apple-Mail=_8152E439-2CE0-4814-B35D-4BDB5E3181CB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jul 28, 2017, at 6:42 PM, Dorian Kim &lt;<a =
href=3D"mailto:dorian@blackrose.org" =
class=3D"">dorian@blackrose.org</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">Doesn=E2=80=99t this all assume being =
able to get functional IPv6 connectivity to IETF meeting =
sites?</span><br style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""></div></blockquote></div><br =
class=3D""><div class=3D"">We've been doing that for a long time now. =
&nbsp; Don't see any reason why it would be a problem in .sg.</div><div =
class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_8152E439-2CE0-4814-B35D-4BDB5E3181CB--


From nobody Fri Jul 28 16:25:54 2017
Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6718B13203D; Fri, 28 Jul 2017 16:25:52 -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, MIME_QP_LONG_LINE=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 EJICWVywxzsK; Fri, 28 Jul 2017 16:25:50 -0700 (PDT)
Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (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 DA1BB131E6C; Fri, 28 Jul 2017 16:25:49 -0700 (PDT)
Received: by mail-io0-x233.google.com with SMTP id m88so86176421iod.2; Fri, 28 Jul 2017 16:25:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version; bh=5YT86f5vcCa8LYickVfTzfyrmvAJ5uOsWstLYVhbvzI=; b=LWfcHqNXIZlmjnlI1aY+FDX4vVgX2F7dxYB7KuLGHcOroOYgB4l8tHU5Z5X2gJrjwI 4Kbez4Dkk3iVfy45RmOA11P7ozni/9BGAyOSYhDySLCj9+NBALEW/UeY2R7GeDT4FO+0 Xhhiaeo1yK0BFz5aLyBeAPVqNjfh0xohA4e+uPbOtnS0TxoqciDm1qwSoCC3jQK66Pvo IiyXPNWRGqODyPV5BcgbS6fXMOSJM1gLyewnnRrf0G6OuBS8XWs1C9A61biJbAGY8vxa WjKCRxSWwsh7wf3UAL9gLez9M1g/SsZEKJv661LY05ZdARu6DPjwXkfGq3b9kSRIO1Jo yMzQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version; bh=5YT86f5vcCa8LYickVfTzfyrmvAJ5uOsWstLYVhbvzI=; b=HXsheg8P8Xdr+WBvEayQDUUtD6+OULUdhn/PijwVuhW2VEYzR4uaTtOpEZ12t96WYm SbB7PUgh3eYWwusl+dEV8GgHct00lryLWx4/7sedpe44oxXH6pgLUCEUNZEYV9pG1oUr iHzqomuWRIVmGO+2glmzwB7nVpHy+ToZtBjsEgJVbPS5sB8erj6lomJLEn40n9VZkjsk g9mJKAO1yWZa1ls5OphxAWTgpeNF0p2C/wYHLxJxGe0PWMbL86y1nWZllp/kXNcnvPvB lxQBezOayr0xuliH1bQYYEwkDgh5B6I1AbLX7hYiNbskwVwcwxzQDRvfGfg9kdbBzmJ4 dcnw==
X-Gm-Message-State: AIVw110B1b1rwf+kjIzyZodAoFqqd9nVdGQ7AtjeAtKz7PShS5BISToU a4CfxS0rjO6kBj5+
X-Received: by 10.107.190.194 with SMTP id o185mr10860595iof.287.1501284349216;  Fri, 28 Jul 2017 16:25:49 -0700 (PDT)
Received: from [192.168.0.108] (47-36-65-40.dhcp.reno.nv.charter.com. [47.36.65.40]) by smtp.gmail.com with ESMTPSA id 202sm2731503itx.24.2017.07.28.16.25.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 Jul 2017 16:25:48 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/f.24.1.170721
Date: Fri, 28 Jul 2017 16:25:46 -0700
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: "Andrew G. Malis" <agmalis@gmail.com>, Ted Lemon <mellon@fugue.com>
CC: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>, "Brzozowski, John" <John_Brzozowski@comcast.com>, Suresh Krishnan <suresh.krishnan@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <3A2839E4-EAB9-41A1-83DA-B91F98606549@gmail.com>
Thread-Topic: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CAA=duU1y8y97f6fBau-g2Oc8uuzmoQMbb96di3HEqjv+Vo6_AA@mail.gmail.com>
In-Reply-To: <CAA=duU1y8y97f6fBau-g2Oc8uuzmoQMbb96di3HEqjv+Vo6_AA@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3584103948_1202729791"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DG21L0NujA8vhDC1kBYNONnok5w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 23:25:52 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3584103948_1202729791
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

I assume =E2=80=93 many of us are in the similar situation, especially those who =
use VPN access to their enterprises.

I=E2=80=99m all for v6 everywhere, however, in order to support those, who can=E2=80=99=
t be on v6, separate SSID should be provided, perhaps would be good to remin=
d all IETF attendees =E2=80=93 test your stuff on v6 only network, otherwise you m=
ight be out of luck in the future. Singapore however wouldn=E2=80=99t be the right=
 point in time to switch v4 off completely.

=20

My 0.2

=20

Cheers,

Jeff

=20

From: ietf <ietf-bounces@ietf.org> on behalf of "Andrew G. Malis" <agmalis@=
gmail.com>
Date: Friday, July 28, 2017 at 14:41
To: Ted Lemon <mellon@fugue.com>
Cc: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6op=
s-ietf-ipv6-only-incremental@ietf.org>, "Brzozowski, John" <John_Brzozowski@=
comcast.com>, Suresh Krishnan <suresh.krishnan@gmail.com>, "ietf@ietf.org" <=
ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF=
 Meetings

=20

Ted,

=20

As one example, I have a VPN application over which I have no control that =
I must use to reach corporate resources, including email. I haven=E2=80=99t yet ha=
d a chance to try it with V6 and nat64, maybe it=E2=80=99ll work and maybe it won=E2=
=80=99t. If it doesn=E2=80=99t, I=E2=80=99ll need to use the legacy network, which is curren=
tly unencrypted. We would need to include a new SSID for an encrypted v4/v6 =
network (what we currently deliver on the =E2=80=9Cietf=E2=80=9D SSID). If that new SSID=
 is provided, then I=E2=80=99ll be OK with the migration.

=20

Thanks,

Andy

=20


--B_3584103948_1202729791
Content-type: text/html;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:schema=
s-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/office/20=
04/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DTitle c=
ontent=3D""><meta name=3DKeywords content=3D""><meta http-equiv=3DContent-Type conte=
nt=3D"text/html; charset=3Dutf-8"><meta name=3DGenerator content=3D"Microsoft Word 1=
5 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Arial;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@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-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;
	font-weight:normal;
	font-style:normal;}
span.msoIns
	{mso-style-type:export-only;
	mso-style-name:"";
	text-decoration:underline;
	color:teal;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style></head><body bgcolor=3Dwhite lang=3DEN-US link=3D"#0563C1" vlink=3D"#954=
F72"><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'font-size:12.0p=
t'>I assume =E2=80=93 many of us are in the similar situation, especially those wh=
o use VPN access to their enterprises.<o:p></o:p></span></p><p class=3DMsoNorm=
al><span style=3D'font-size:12.0pt'>I=E2=80=99m all for v6 everywhere, however, in o=
rder to support those, who can=E2=80=99t be on v6, separate SSID should be provide=
d, perhaps would be good to remind all IETF attendees =E2=80=93 test your stuff on=
 v6 only network, otherwise you might be out of luck in the future. Singapor=
e however wouldn=E2=80=99t be the right point in time to switch v4 off completely.=
<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt'><o:p=
>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt'>My=
 0.2<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt'>=
<o:p>&nbsp;</o:p></span></p><div><p class=3DMsoNormal><span style=3D'font-size:1=
0.5pt;color:black'>Cheers,<o:p></o:p></span></p></div><p class=3DMsoNormal><sp=
an style=3D'font-size:10.5pt;color:black'>Jeff</span><span style=3D'font-size:12=
.0pt'><o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt=
'><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;border-top:solid #B5C4=
DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal style=3D'margin-left:.5=
in'><b><span style=3D'font-size:12.0pt;color:black'>From: </span></b><span sty=
le=3D'font-size:12.0pt;color:black'>ietf &lt;ietf-bounces@ietf.org&gt; on beha=
lf of &quot;Andrew G. Malis&quot; &lt;agmalis@gmail.com&gt;<br><b>Date: </b>=
Friday, July 28, 2017 at 14:41<br><b>To: </b>Ted Lemon &lt;mellon@fugue.com&=
gt;<br><b>Cc: </b>&quot;draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org=
&quot; &lt;draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org&gt;, &quot;B=
rzozowski, John&quot; &lt;John_Brzozowski@comcast.com&gt;, Suresh Krishnan &=
lt;suresh.krishnan@gmail.com&gt;, &quot;ietf@ietf.org&quot; &lt;ietf@ietf.or=
g&gt;<br><b>Subject: </b>Re: RESENDING - Incremental Deployment of IPv6-only=
 Wi-Fi for IETF Meetings<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'margin-left:.5in'><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal =
style=3D'margin-left:.5in'>Ted,<o:p></o:p></p><div><p class=3DMsoNormal style=3D'm=
argin-left:.5in'><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal style=3D'm=
argin-left:.5in'>As one example, I have a VPN application over which I have =
no control that I must use to reach corporate resources, including email. I =
haven=E2=80=99t yet had a chance to try it with V6 and nat64, maybe it=E2=80=99ll work a=
nd maybe it won=E2=80=99t. If it doesn=E2=80=99t, I=E2=80=99ll need to use the legacy network,=
 which is currently unencrypted. We would need to include a new SSID for an =
encrypted v4/v6 network (what we currently deliver on the =E2=80=9Cietf=E2=80=9D SSID). =
If that new SSID is provided, then I=E2=80=99ll be OK with the migration.<o:p></o:=
p></p></div><div><p class=3DMsoNormal style=3D'margin-left:.5in'><o:p>&nbsp;</o:=
p></p></div><div><p class=3DMsoNormal style=3D'margin-left:.5in'>Thanks,<o:p></o=
:p></p></div><div><p class=3DMsoNormal style=3D'margin-left:.5in'>Andy<o:p></o:p=
></p></div><div><p class=3DMsoNormal style=3D'margin-left:.5in'><o:p>&nbsp;</o:p=
></p></div></div></div></body></html>

--B_3584103948_1202729791--



From nobody Fri Jul 28 16:54:01 2017
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C39E1321B0; Fri, 28 Jul 2017 16:53:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level: 
X-Spam-Status: No, score=-4.302 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_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 WVLs73B-kzTG; Fri, 28 Jul 2017 16:53:56 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F173B1321D8; Fri, 28 Jul 2017 16:53:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 47FC4BE2D; Sat, 29 Jul 2017 00:53:52 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2sk00pmspGIF; Sat, 29 Jul 2017 00:53:48 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 3B751BDF9; Sat, 29 Jul 2017 00:53:48 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1501286028; bh=3TlGrMuJugn31QT0CsuaPiLppFEgF6JiZIhsvs7SLCY=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=zAHI1PVJadOrToS5P+8h8jBsnJ6t+DJ9lVc9U52fDjhwKGhZrpx8FntGv63T2wNpv HNp36pCBCkWee8XS5loWjW8heHLcTnBSZsB6pkbWhv91KjZeZGTPqkM1l08FHBNzkp FI5WOiEu+NhU1FAgmxiycoRPvcEmtmws7ANxpMMI=
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: Eric Rescorla <ekr@rtfm.com>, "Brzozowski, John" <John_Brzozowski@comcast.com>
Cc: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>, Suresh Krishnan <suresh.krishnan@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <e9095813-b5b5-29ba-34ab-f11c423aea26@cs.tcd.ie>
Date: Sat, 29 Jul 2017 00:53:47 +0100
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: <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="qGAEigxUpaDBBmexsXFuqXVt8Dihp8NoV"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IPC52pciCpoNfp307Eu0NkyDodw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 23:53:59 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--qGAEigxUpaDBBmexsXFuqXVt8Dihp8NoV
Content-Type: multipart/mixed; boundary="fjR2R7LU2TV3F7emGaNGtHDm6Rv6Ol7LT";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Eric Rescorla <ekr@rtfm.com>,
 "Brzozowski, John" <John_Brzozowski@comcast.com>
Cc: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org"
 <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,
 Suresh Krishnan <suresh.krishnan@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <e9095813-b5b5-29ba-34ab-f11c423aea26@cs.tcd.ie>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF
 Meetings
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com>
 <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com>
In-Reply-To: <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com>

--fjR2R7LU2TV3F7emGaNGtHDm6Rv6Ol7LT
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: quoted-printable



On 28/07/17 21:38, Eric Rescorla wrote:
> I'm not very enthusiastic about this. People come to the IETF to do wor=
k
> and having
> to deal with potential bustage from this experiment gets in the way of =
that.
>=20

+1

IIUC correctly this'd also break DNSSEC for some names and has to.
If so, I'd be against it.

S.

> -Ekr
>=20
>=20
> On Mon, Jul 17, 2017 at 12:33 AM, Brzozowski, John <
> John_Brzozowski@comcast.com> wrote:
>=20
>> Apologies, I understand this mail did not make it to the various lists=
=2E
>>
>> John
>> +1-484-962-0060
>>
>> -----Original Message-----
>> From: John Brzozowski <John_Brzozowski@Cable.Comcast.com>
>> Date: Sunday, July 16, 2017 at 20:28
>> To: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <
>> draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>
>> Cc: Randy Bush <randy@psg.com>, Alissa Cooper <alissa@cooperw.in>, Jim=

>> Martin <jim@daedelus.com>, Jari Arkko <jari.arkko@piuha.net>, Suresh
>> Krishnan <suresh.krishnan@gmail.com>, Russ Housley <housley@vigilsec.c=
om>
>> Subject: Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
>>
>>     Folks,
>>
>>     Apologies in advance for the gratuitous cross posting (v6ops, ietf=
,
>> ipv6, sunset4, softwires).  I hope, to you all, this is worth the adde=
d
>> email.
>>
>>     The draft below was written to provide the necessary documentation=
 to
>> enable the IETF (the NOC, participants, etc.) to migrate to an IPv6 on=
ly
>> primary network connection (Wi-Fi and wired) that utilizes NAT64+DNS64=
 to
>> access IPv4 only content.  The request for IETF 99 has been to have th=
e
>> primary =C3=A2=E2=82=AC=C5=93ietf=C3=A2=E2=82=AC=C2=9D SSID adhere to =
what is documented in the I-D below.  I trust
>> the motivation is understood.  This means that the main =C3=A2=E2=82=AC=
=C5=93ietf=C3=A2=E2=82=AC=C2=9D SSID would
>> be switched to be IPv6 only with NAT64+DNS64 (at layer 3) per the I-D
>> below.  Given the that IETF99 is upon us, this may or may not be entir=
ely
>> possible.
>>
>>     At this stage, the infrastructure preparations for IETF 99 should =
be
>> in place to ensure that the IETF has the necessary hardware for redund=
ancy
>> and performance.
>>
>>     So, we are all seeking your input.  Given the above, what would al=
l
>> you suggest is tolerable for IETF99 as it pertains to the I-D below?
>>
>>     =C3=A2=E2=82=AC=C2=A2 IPv6 only per the I-D for the balance of IET=
F week?
>>     =C3=A2=E2=82=AC=C2=A2 IPv6 only per the I-D for one or more days t=
his week?
>>     =C3=A2=E2=82=AC=C2=A2 IPv6 only per the I-D for the plenary?
>>     =C3=A2=E2=82=AC=C2=A2 IPv6 only per the I-D for the next IETF meet=
ing?
>>
>>     Please send us your feedback.
>>
>>     Regards,
>>
>>     John
>>     +1-484-962-0060
>>
>>     -----Original Message-----
>>     From: "internet-drafts@ietf.org" <internet-drafts@ietf.org>
>>     Date: Saturday, July 1, 2017 at 03:04
>>     To: Marcus Keane <marcus.keane@microsoft.com>, Jen Linkova <
>> furry@google.com>, Lorenzo Colitti <lorenzo@google.com>, John Brzozows=
ki <
>> John_Brzozowski@Cable.Comcast.com>, Erik Kline <ek@google.com>, John
>> Brzozowski <John_Brzozowski@Cable.Comcast.com>, David Schinazi <
>> dschinazi@apple.com>, Stuart Cheshire <cheshire@apple.com>, Jen Linkov=
a <
>> furry@google.com>, Paul Saab <ps@fb.com>, David Schinazi <
>> dschinazi@apple.com>
>>     Subject: New Version Notification for draft-jjmb-v6ops-ietf-ipv6-
>> only-incremental-00.txt
>>
>>
>>         A new version of I-D, draft-jjmb-v6ops-ietf-ipv6-
>> only-incremental-00.txt
>>         has been successfully submitted by John Jason Brzozowski and
>> posted to the
>>         IETF repository.
>>
>>         Name:           draft-jjmb-v6ops-ietf-ipv6-only-incremental
>>         Revision:       00
>>         Title:          Incremental Deployment of IPv6-only Wi-Fi for =
IETF
>> Meetings
>>         Document date:  2017-06-30
>>         Group:          Individual Submission
>>         Pages:          15
>>         URL:            https://www.ietf.org/internet-
>> drafts/draft-jjmb-v6ops-ietf-ipv6-only-incremental-00.txt
>>         Status:         https://datatracker.ietf.org/
>> doc/draft-jjmb-v6ops-ietf-ipv6-only-incremental/
>>         Htmlized:       https://tools.ietf.org/html/
>> draft-jjmb-v6ops-ietf-ipv6-only-incremental-00
>>         Htmlized:       https://datatracker.ietf.org/
>> doc/html/draft-jjmb-v6ops-ietf-ipv6-only-incremental-00
>>
>>
>>         Abstract:
>>            The purpose of this document is to provide a blueprint and
>> guidance
>>            for deploying IPv6-only Wi-Fi at IETF meetings.  This docum=
ent
>>            outlines infrastructure and operational guidance that opera=
tors
>>            should consider when deploying IPv6-only networks using NAT=
64
>> and
>>            DNS64 to support communication to legacy IPv4-only services=
=2E
>>
>>
>>
>>
>>         Please note that it may take a couple of minutes from the time=
 of
>> submission
>>         until the htmlized version and diff are available at
>> tools.ietf.org.
>>
>>         The IETF Secretariat
>>
>>
>>
>>
>>
>>
>>
>=20


--fjR2R7LU2TV3F7emGaNGtHDm6Rv6Ol7LT--

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

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJZe86LAAoJEC88hzaAX42irDMH/1gREg90iw+7RiF2hwV1Rnlx
nAnDrHNIfjntvpIMud4OHqG0ZREGbw0gKyWXgsfG7hLll5DntpaNmXE/rNcd+vUX
GkBev+XebVytuuZYspg2evhGTVCChWnov37RFgvTFRWtGRHPacRG5d/XGm5vLtve
dZcDU1FtGrfOjFl5DFkPr7ewEu/3cL6ynEQ31LG0lsQ1WYcmRR+UFVqox/DNF+6c
qYUGdDuLmqZyAuwhsD7xgWklSWYpA4voNHRL/5GhN1u7L/R6whegd9whjW2ihACV
XQAcm8BowlaevEV7iDSJ/PEDjot9zRNVrCRO6/p78niQn4EfiE6bMDCtcXG3eOU=
=fGND
-----END PGP SIGNATURE-----

--qGAEigxUpaDBBmexsXFuqXVt8Dihp8NoV--


From nobody Fri Jul 28 17:08:13 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86A47131DFE for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 17:08:11 -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, 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 (2048-bit key) header.d=fugue-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 c-nXPPWO7UNt for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 17:08:09 -0700 (PDT)
Received: from mail-qk0-x22d.google.com (mail-qk0-x22d.google.com [IPv6:2607:f8b0:400d:c09::22d]) (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 DF46D129AA0 for <ietf@ietf.org>; Fri, 28 Jul 2017 17:08:08 -0700 (PDT)
Received: by mail-qk0-x22d.google.com with SMTP id d136so130904346qkg.3 for <ietf@ietf.org>; Fri, 28 Jul 2017 17:08:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=MaJN2j+hjVJT38st2PfZ8RniJBGLKQFI4KYVDAim9FM=; b=hVbaaz6fxDPyZJNXXOmz7kLOHJAqTWsqyBTNAAolQFq+TnWJvPyXNCCwVw6LWR/KWS 0JMMvWC7PiHRiYKkjIwuZM97p/ppiTJuQQCK790tM1CVmbR+CmMmuuXkD2i22sC5cwdw GxlEuKVknN0TGUD/XWOdVg7FeTw/YD+sdE28UJK66oCoUmLV/+JhjhI5q0z5XPnFA1U3 ApiDfWEIccHnXLhYyZR7i2stPRTy3vOqXnQH2jca22ibv4Zn8+6g0CUoMJUA5MxgJyXR gqtiW0zEn9DiZ02EmYfwytR2XWCPepi8Rin33EB+dpEMWI2Wr30sYm6zlmgjewds+0Ip 3xuw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=MaJN2j+hjVJT38st2PfZ8RniJBGLKQFI4KYVDAim9FM=; b=SkTTv3SkSOeImwSqoqYiYOK2GEJs18vnTDhfZwEn1seJzgYMDZk0aV8cZMrYOnIGNZ e2R0MyCSnc3MyLZ7qIpCN2QGH9Ab2hjOdQjdFurgerJATKge60xi60tEDsJtA/t6KM2L XpWIUFkwzTZ9HM8zeOlOdcdctNbWdvhhCx0MQP1GLtKSznLgEAttVWjwN9U3yuxBWf9e w48yrNMnT84cyXNeDpAMVhGEEJmGPPLXTO7dtbrL4eOQEwjE5L39HCsg6+xP+nRwHeaO sm2lrRaSuq6BWb8G9rMKJIIrUyMwAvOMvpAL/HtoqS8zv961gWGur/Rp6m9FfAO5GDDO /VSg==
X-Gm-Message-State: AIVw1134ihDz65IXbX3dAc4nyh1+cvfSAh/d95EaX3IosP09CWzOz6Co q4qVeSH6Yz5b7vRi
X-Received: by 10.55.137.132 with SMTP id l126mr8276404qkd.322.1501286888026;  Fri, 28 Jul 2017 17:08:08 -0700 (PDT)
Received: from macbook-pro-6.w50.lede.home (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id 74sm5415786qkv.31.2017.07.28.17.08.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 Jul 2017 17:08:07 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <39FD84EA-4614-4331-B562-C9B2219FE949@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D861FECD-21C0-4FD2-BC89-776C0FAB0639"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Fri, 28 Jul 2017 20:08:05 -0400
In-Reply-To: <e9095813-b5b5-29ba-34ab-f11c423aea26@cs.tcd.ie>
Cc: Eric Rescorla <ekr@rtfm.com>, "Brzozowski, John" <John_Brzozowski@comcast.com>, "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,  Suresh Krishnan <suresh.krishnan@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <e9095813-b5b5-29ba-34ab-f11c423aea26@cs.tcd.ie>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bcWdNpniDdnnhA4APvkkxUT-JHc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 00:08:12 -0000

--Apple-Mail=_D861FECD-21C0-4FD2-BC89-776C0FAB0639
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jul 28, 2017, at 7:53 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie> =
wrote:
> IIUC correctly this'd also break DNSSEC for some names and has to.
> If so, I'd be against it.

Yes, if your host doesn't do DNS64 and does do validation, you will get =
validation failures for signed A records.   I would argue that this is a =
broken configuration, but perhaps you would argue otherwise. :)

People who are forward-thinking (but not enough) in their use of DNSSEC =
and backward-thinking in their use of IPv6 will have problems.   It =
would be interesting to see if this produces operational problems in =
practice; if it does, I would expect people who ran into such problems =
to switch to the legacy network, and we would see that in the SSID =
usage.

Would you run into a problem in this case, if I may be so bold as to =
ask?


--Apple-Mail=_D861FECD-21C0-4FD2-BC89-776C0FAB0639
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jul 28, 2017, at 7:53 PM, Stephen Farrell &lt;<a =
href=3D"mailto:stephen.farrell@cs.tcd.ie" =
class=3D"">stephen.farrell@cs.tcd.ie</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">IIUC correctly this'd also break DNSSEC =
for some names and has to.</span><br style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">If so, I'd be =
against it.</span></div></blockquote></div><br class=3D""><div =
class=3D"">Yes, if your host doesn't do DNS64 and does do validation, =
you will get validation failures for signed A records. &nbsp; I would =
argue that this is a broken configuration, but perhaps you would argue =
otherwise. :)</div><div class=3D""><br class=3D""></div><div =
class=3D"">People who are forward-thinking (but not enough) in their use =
of DNSSEC and backward-thinking in their use of IPv6 will have problems. =
&nbsp; It would be interesting to see if this produces operational =
problems in practice; if it does, I would expect people who ran into =
such problems to switch to the legacy network, and we would see that in =
the SSID usage.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Would you run into a problem in this case, if I may be so =
bold as to ask?</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_D861FECD-21C0-4FD2-BC89-776C0FAB0639--


From nobody Fri Jul 28 17:16:41 2017
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74E9F1321E9; Fri, 28 Jul 2017 17:16:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level: 
X-Spam-Status: No, score=-4.302 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_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 1d56tudYTRX8; Fri, 28 Jul 2017 17:16:38 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34840131C24; Fri, 28 Jul 2017 17:16:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id A8D40BE2D; Sat, 29 Jul 2017 01:16:36 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1WJgYjnDe1_h; Sat, 29 Jul 2017 01:16:35 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 524EABDF9; Sat, 29 Jul 2017 01:16:35 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1501287395; bh=iMEbhK2yTOny4idk0nA+uUa/fOB7IFNI/b2OKXZ2vT4=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=cOrhNz4ahLICoq+Q3dX6Krs29af0bG0xb9PKCQqsGf5bGsDsaf7lwWgtLu7e0lxRT 4vfyaxyKCX+/qkQRXXRxwMN8mV1qx7T7gdtk8dvekndMSizvjONm4N9ai4KC93HgOj Vbras666I6r2B96hJT2FuM57VhqJUTws5jaN2RxU=
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: Ted Lemon <mellon@fugue.com>
Cc: Eric Rescorla <ekr@rtfm.com>, "Brzozowski, John" <John_Brzozowski@comcast.com>, "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>, Suresh Krishnan <suresh.krishnan@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <e9095813-b5b5-29ba-34ab-f11c423aea26@cs.tcd.ie> <39FD84EA-4614-4331-B562-C9B2219FE949@fugue.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <71ace01c-66a1-9e85-145b-8bb11f4d9edc@cs.tcd.ie>
Date: Sat, 29 Jul 2017 01:16:34 +0100
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: <39FD84EA-4614-4331-B562-C9B2219FE949@fugue.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="dlSVmNNRQXVWqc4EJLqNG34gB7RAwAvov"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KzugcCZwY1pdy0xyveQAQjkrnv8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 00:16:40 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--dlSVmNNRQXVWqc4EJLqNG34gB7RAwAvov
Content-Type: multipart/mixed; boundary="fIKA1bO2XWK2CSadmIqG9IpgLVNQ0iO0B";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Ted Lemon <mellon@fugue.com>
Cc: Eric Rescorla <ekr@rtfm.com>,
 "Brzozowski, John" <John_Brzozowski@comcast.com>,
 "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org"
 <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,
 Suresh Krishnan <suresh.krishnan@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <71ace01c-66a1-9e85-145b-8bb11f4d9edc@cs.tcd.ie>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF
 Meetings
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com>
 <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com>
 <e9095813-b5b5-29ba-34ab-f11c423aea26@cs.tcd.ie>
 <39FD84EA-4614-4331-B562-C9B2219FE949@fugue.com>
In-Reply-To: <39FD84EA-4614-4331-B562-C9B2219FE949@fugue.com>

--fIKA1bO2XWK2CSadmIqG9IpgLVNQ0iO0B
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: quoted-printable



On 29/07/17 01:08, Ted Lemon wrote:
> Would you run into a problem in this case, if I may be so bold as to as=
k?

Think so. I do have some DNSSEC-signed v4-only hosts with which I
like to chat and do validate. I can't claim the world will end if
I need to muck about to do that, but it a breakage that does not
represent backwards thinking.

S.


--fIKA1bO2XWK2CSadmIqG9IpgLVNQ0iO0B--

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

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJZe9PiAAoJEC88hzaAX42ixUYH/0SSB++WPn0NjhymbiTXPrB9
33t5/w5qEXZxWQGbkzHqK+H2k3QVh6J8r0Ekd+uRCuimbSAr7SZ7Gq8GBGZRcAud
esw8VUhDOPDj7IR9dv6VEpjbCbhruanxXEn1vc417Dn3om7Hhsc3gveKus9IpBnb
AmaPs4R2DE+jsDXNiPsr4Tce/6iH6R6dm0g116EqSJQgj8tGv/YMUMngyxfTVZt0
kEkZm9tpKVm/urB9PKHxPTNSVdPDh/LEbdCJikxk3dbBiTSEi5FejhMbkssfAB8r
9MvR3SN+2C7JKa9z+HegfcHWtp2D6/A/oldVW3sHR2XvjhLdulE45eM9kckxp+g=
=yCsf
-----END PGP SIGNATURE-----

--dlSVmNNRQXVWqc4EJLqNG34gB7RAwAvov--


From nobody Fri Jul 28 17:35:36 2017
Return-Path: <heas@shrubbery.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB2A7131723; Fri, 28 Jul 2017 17:35:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level: 
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 xfgMxqgU1fmT; Fri, 28 Jul 2017 17:35:32 -0700 (PDT)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D86A126C83; Fri, 28 Jul 2017 17:35:32 -0700 (PDT)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id 09DE97894A; Sat, 29 Jul 2017 00:35:32 +0000 (UTC)
Date: Sat, 29 Jul 2017 00:35:32 +0000
From: heasley <heas@shrubbery.net>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: Ted Lemon <mellon@fugue.com>, "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,  "Brzozowski, John" <John_Brzozowski@comcast.com>, Suresh Krishnan <suresh.krishnan@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Message-ID: <20170729003531.GP79820@shrubbery.net>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <e9095813-b5b5-29ba-34ab-f11c423aea26@cs.tcd.ie> <39FD84EA-4614-4331-B562-C9B2219FE949@fugue.com> <71ace01c-66a1-9e85-145b-8bb11f4d9edc@cs.tcd.ie>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <71ace01c-66a1-9e85-145b-8bb11f4d9edc@cs.tcd.ie>
X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc
X-note: live free, or die!
X-homer: i just want to have a beer while i am caring.
X-Claimation: an engineer needs a manager like a fish needs a bicycle
X-reality: only YOU can put an end to the embarrassment that is Tom Cruise
User-Agent: Mutt/1.8.3 (2017-05-23)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/e62ySzAcEEMoNuGSTa_zH_AL5TU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 00:35:34 -0000

Sat, Jul 29, 2017 at 01:16:34AM +0100, Stephen Farrell:
> On 29/07/17 01:08, Ted Lemon wrote:
> > Would you run into a problem in this case, if I may be so bold as to as=
k?
>=20
> Think so. I do have some DNSSEC-signed v4-only hosts with which I
> like to chat and do validate. I can't claim the world will end if
> I need to muck about to do that, but it a breakage that does not
> represent backwards thinking.
>=20
> S.

so, seems you should try it and fix/ticket/etc if it does not work, no?
its been discussed, i forget if on this or the 99-attendees list, that
its not sufficient to nurture v6 and its transition technologies by
simply switching to a v4 ssid nor to avoid using v6.


From nobody Fri Jul 28 18:02:41 2017
Return-Path: <suzworldwide@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD735131E8D for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 18:02:39 -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 dsAhGRaXLlP7 for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 18:02:38 -0700 (PDT)
Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::22d]) (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 3A1B7131E96 for <ietf@ietf.org>; Fri, 28 Jul 2017 18:02:37 -0700 (PDT)
Received: by mail-qt0-x22d.google.com with SMTP id 16so47499534qtz.4 for <ietf@ietf.org>; Fri, 28 Jul 2017 18:02:37 -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=m0PUgmGKFcSgERCoFfVhQcXa+8PdJuxSUyOm6+MokMc=; b=lDKcxf+myH6EHLa6yOnLRZUuqWPp1QjXX1ebhcNDU6iDr52JLAiQwKP3fCndX52ZQ7 3oE4hp7oMlnKTmxXT1uGQO8KGu3UAT73tJzxm0QqdQ9wJGk926yPF0l9hn052tcABsLT 3sppw+Ikp4fAsMDFN21rt/3BN4khe4dViPBDsyMJqohbXphqJjqZo19doL1qajyiKGNQ r8kTeeJr6hUct/A2dPA+wCLX1EGDgKGt3tmnWbuw6fLhT81ZClHGqLTxHRnzTNVBrNUC G99BfR0MffzhDceZFhGIrjvIW0ZSsqnLE9qzbf8akf09VRGXkMv026wD8d+Zhkl+GoB6 mzaQ==
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=m0PUgmGKFcSgERCoFfVhQcXa+8PdJuxSUyOm6+MokMc=; b=h+FjYRTHjFBwdtfX/qcp5TsnsQmgBG4oATKW+n/A8huUvlhIe5wiV8Vrz1JnEzTJvJ Q/D/RtM2oemySu+mpr68gvVMhbAmH14dw/bhDafFKARHuVoIR3ISZlaFnSpQcC43Z/0K U5jo0vL09uZ+UidSZO9b9AbD2iiPzT0Bcf7UCepjKuClrIu/qXJMIlb2GxTIMmw2pGuN yna53FeOIJMM6LcnX9l5nYhp3+pJYFkrKYTXl0rRSUsZA6hwb0WqxuxoUkcZAkXgfu32 xKcdIhii32hX8uvxvhw/3B2IH/HJfYvwW0ZqfGrwfgkVmfdfD+1W1bq1UWV/EY7LlspK gKnw==
X-Gm-Message-State: AIVw110jBwTy2mejo2dIFiGuFrnarizF4dJkOF9jIaecfPWHVYV2sWUl YSJe2YC36b8egnl6Vc4=
X-Received: by 10.200.47.152 with SMTP id l24mr13656734qta.222.1501290157062;  Fri, 28 Jul 2017 18:02:37 -0700 (PDT)
Received: from ?IPv6:2601:181:c381:c20:98f3:7a01:2e8c:2a2? ([2601:181:c381:c20:98f3:7a01:2e8c:2a2]) by smtp.gmail.com with ESMTPSA id b185sm4298528qkf.86.2017.07.28.18.02.35 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 28 Jul 2017 18:02:35 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: Announcement on IETF 100 Hotel Reservations
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <20170728144317.k3do5nul22nlc6pf@mx4.yitter.info>
Date: Fri, 28 Jul 2017 21:02:34 -0400
Cc: ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <D0162F7F-C36F-4241-8CD0-AD6FD1422847@gmail.com>
References: <150108971740.23120.257371533321943899.idtracker@ietfa.amsl.com> <EF2F4195-A97F-46CB-B2D2-DB7A5E11874F@gmail.com> <100a6ef1-1b1a-9123-398f-1883a167c5e1@comcast.net> <alpine.OSX.2.01.1707261133380.78919@rabdullah.local> <0d19da56-b55d-79b9-c9d1-464e5f561742@gmail.com> <20170728144317.k3do5nul22nlc6pf@mx4.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZQl7AJwYKCxgCmGyQ_nWV-DCtQw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 01:02:40 -0000

> On Jul 28, 2017, at 10:43 AM, Andrew Sullivan <ajs@anvilwalrusden.com> =
wrote:
>  At the same time, however, I think
> we need to be quite careful in what we are saying.  We are encroaching
> again on the same controversy that caused difficulty when the site was
> announced.
>=20
> =E2=80=A6..
>=20
> Circumstances change in countries, sometimes in surprising ways.
> Therefore, IETF participants who are going to attend IETF 100 should
> be aware that the rules are strict and published.  Each traveller
> should weigh the reports of non-enforcement against the risk that the
> rule could be enforced in one's own case.

+1.  I=E2=80=99ve been to Singapore multiple times, I=E2=80=99ve never =
had a problem, and I=E2=80=99ve always planned according to the =
published guidelines.


Suzanne


From nobody Fri Jul 28 18:04:52 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06D05131E96 for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 18:04:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 6VLRWeuw7yaG for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 18:04:49 -0700 (PDT)
Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::22d]) (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 E83AF131E8D for <ietf@ietf.org>; Fri, 28 Jul 2017 18:04:48 -0700 (PDT)
Received: by mail-qt0-x22d.google.com with SMTP id s6so97116166qtc.1 for <ietf@ietf.org>; Fri, 28 Jul 2017 18:04:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=a58kfRfAWVfQmMF5kC7/fKs8jAixipk+dCFrtWZPHng=; b=dTekeoe/kUT4A50jJhb1ADGJmXi8jqSAThL/s0hl2BEBhnw0mQXQqt7Ei5W2Z5sKS3 NdnnGU+rqb7kDQCj53Ra1CmgN0jpwooclWQYyz/IhInr+FjdtfYWh+uhBnBuKBJDveHq BRJ1oFFjqgSOMGDNUNYGQFZcdxtUbyQp73X+0AaJv4jTsuRsq6mVSKf95E6wi8fnwsxe IpeaXwfx+otlFLf7a1d61vSNIdn17aIDaIGrfRkDl45iKAZeJgMlJg9TjxEKvuqNNS1S 4QwAHmBo0VzJwVsCZG+t4jvnY5zcTSk2SjehMR1FxGT2yq/txY7d78c9U7oQWktJs29h 0M8w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=a58kfRfAWVfQmMF5kC7/fKs8jAixipk+dCFrtWZPHng=; b=tiJy4z1IuBLGEWpzbCFFtvdHqmd7EvlChWGCnP8hz9z1noweh2e8Vrltm9E/9mngsj uc6mNN35gpIGlQZzCoUPhBUS7E8oGPKpN+F//bRGvzv0IwY6K8QeM7W7sY4Ubm9JzCJJ 9Ixh5WUiAcW9YdQSlfL6iCQpqRAMlylOUm07R1fHG5/CRhQcX5G/oYPinQ/cyn3ljJCO Wenu6hHfcioya5Wn6ggqfsbE991ZrTFRdURO9roBZk+/mvtlfGqsDcrsPIOL5jgfHuhf B0yL1335TdH2wwIb3MKwxz7fpQm6mF7LIDzS/Oq4z+65FAfgR6V8zkvxtGk8HR0WXJbR nt3w==
X-Gm-Message-State: AIVw1110PIZwfmK5pUBOB6nNGfTBaan7SyIXxz0S40ePlnwTY+wRWgTc H98URoYfXIAzXXFH3lSSvw==
X-Received: by 10.200.37.98 with SMTP id 31mr13905003qtn.92.1501290288083; Fri, 28 Jul 2017 18:04:48 -0700 (PDT)
Received: from macbook-pro-6.w50.lede.home (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id 94sm11763429qte.55.2017.07.28.18.04.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 Jul 2017 18:04:47 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <A4C152FA-9A6E-4AFC-AFFC-FBD882B955C1@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3AA3EDCD-C2F1-4C9C-9F2C-BF3E3433AFF0"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Fri, 28 Jul 2017 21:04:45 -0400
In-Reply-To: <71ace01c-66a1-9e85-145b-8bb11f4d9edc@cs.tcd.ie>
Cc: "ietf@ietf.org" <ietf@ietf.org>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <e9095813-b5b5-29ba-34ab-f11c423aea26@cs.tcd.ie> <39FD84EA-4614-4331-B562-C9B2219FE949@fugue.com> <71ace01c-66a1-9e85-145b-8bb11f4d9edc@cs.tcd.ie>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-0tDQq-ulYKBaiTDr8V4njq6BtU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 01:04:51 -0000

--Apple-Mail=_3AA3EDCD-C2F1-4C9C-9F2C-BF3E3433AFF0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jul 28, 2017, at 8:16 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie> =
wrote:
> Think so. I do have some DNSSEC-signed v4-only hosts with which I
> like to chat and do validate. I can't claim the world will end if
> I need to muck about to do that, but it a breakage that does not
> represent backwards thinking.

The point is that if you are validating on your host, which I think is a =
great plan, you should also be doing DNS64 on your host; otherwise you =
will not be able to operate on a NAT64 network.   I guess the other =
option is to never do NAT64, but that's a bit extreme at the present =
time.   And, if you find that the current solution for doing DNS64 on =
your host isn't adequately secure, I would personally like you to =
complain about _that_, because that would likely provoke useful work.   =
:)


--Apple-Mail=_3AA3EDCD-C2F1-4C9C-9F2C-BF3E3433AFF0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jul 28, 2017, at 8:16 PM, Stephen Farrell &lt;<a =
href=3D"mailto:stephen.farrell@cs.tcd.ie" =
class=3D"">stephen.farrell@cs.tcd.ie</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">Think so. I do have some DNSSEC-signed =
v4-only hosts with which I</span><br style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">like to chat and do =
validate. I can't claim the world will end if</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">I need to muck about to do that, but it a =
breakage that does not</span><br style=3D"font-family: Menlo-Regular; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">represent backwards =
thinking.</span></div></blockquote></div><br class=3D""><div =
class=3D"">The point is that if you are validating on your host, which I =
think is a great plan, you should also be doing DNS64 on your host; =
otherwise you will not be able to operate on a NAT64 network. &nbsp; I =
guess the other option is to never do NAT64, but that's a bit extreme at =
the present time. &nbsp; And, if you find that the current solution for =
doing DNS64 on your host isn't adequately secure, I would personally =
like you to complain about _that_, because that would likely provoke =
useful work. &nbsp; :)</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_3AA3EDCD-C2F1-4C9C-9F2C-BF3E3433AFF0--


From nobody Fri Jul 28 18:46:32 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CA05131EC6 for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 18:46:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 LVes5J1zxKrg for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 18:46:29 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 EC5EF131EC3 for <ietf@ietf.org>; Fri, 28 Jul 2017 18:46:28 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dbGpl-0006Un-Jv; Sat, 29 Jul 2017 01:46:26 +0000
Date: Sat, 29 Jul 2017 10:46:23 +0900
Message-ID: <m2pockhv68.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: heasley <heas@shrubbery.net>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
In-Reply-To: <20170729003531.GP79820@shrubbery.net>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <e9095813-b5b5-29ba-34ab-f11c423aea26@cs.tcd.ie> <39FD84EA-4614-4331-B562-C9B2219FE949@fugue.com> <71ace01c-66a1-9e85-145b-8bb11f4d9edc@cs.tcd.ie> <20170729003531.GP79820@shrubbery.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wy4EV5w33jxGuaUJcgb01_f7Scs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 01:46:30 -0000

[ i do not speak for the noc ]

yes, this was discussed after seoul.  folk seemed to have this funny
idea that the meeting network is to facilitate getting work done.  i
hope you felt the chicago and praha networks were successful.

> so, seems you should try it and fix/ticket/etc if it does not work,
> no?  its been discussed, i forget if on this or the 99-attendees list,
> that its not sufficient to nurture v6 and its transition technologies
> by simply switching to a v4 ssid nor to avoid using v6.

in praha, as we had a second A10, we could finally consider nat64 to be
a production service.  we thank those who used, reported successes, and
ticketed problems.

the noc is very open to ideas on an easier/better way of reporting,
discussing, and tracking issues with the nat64 network in s'pore.  we
would like to make it as easy as possible for john and the nat64 folk to
track and deal with the equipment, software, and application vendors.

getting problems with nat64 identified, diagnosed, and fixed (or worked
around, sigh) is in the ietf's and the public's interest.

randy


From nobody Fri Jul 28 21:22:30 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 954F6131D26 for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 21:22:28 -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 PlgjHlmzAoQJ for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2017 21:22:27 -0700 (PDT)
Received: from mail-pg0-x232.google.com (mail-pg0-x232.google.com [IPv6:2607:f8b0:400e:c05::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 B70D31270AC for <ietf@ietf.org>; Fri, 28 Jul 2017 21:22:25 -0700 (PDT)
Received: by mail-pg0-x232.google.com with SMTP id c14so25570891pgn.0 for <ietf@ietf.org>; Fri, 28 Jul 2017 21:22:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=7fDyxmU7QPmKM//mpuKnRuvWTws1pAkZKlNviuaTgZc=; b=AdoXxyrSZunaZuG2qrTRCu3WUCv/Uu9Rln99VzihDHd+QIxSO5uR19X2G1DAZcxf8A rWoHQrDE2SAUzdeUPXKX4RnKIxD+poC0bSImqpF5bn1L9SMWDNJKGx4FLB9VyHz+QYCQ 2NefFAUVnCBSO6mJPlRmzhgDHlUKFaBEJ5KfPm8kgMVJrEV0CxgqdOlRwU7QkJipvE5v 8ImxzRtvs9g4i+8eKbJZ8cYToNA309VXTXeYlwkyATBzMsyTVfUgQUpQaPirLrp0Gh1k kISuTjFk5di7wHS+6Rwx3u2VHPHStmaMrglytrX0tXB74MfJeuUFTzMfG0CK+Ia3xHPI 5SMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=7fDyxmU7QPmKM//mpuKnRuvWTws1pAkZKlNviuaTgZc=; b=Q9bvvWxjcjjzE2eJ0pMdQU+OdJwzvA6807ctCKmhvTl6RVf4tMMiHuqih2lh3Fzwiq X3U4/kshodfauKwc6V0zXlAkTMVKU/4LR+H/FPqnOYlgdcFxzWBRLrKdgLGKzlqbT6rV tKaqTAnU2wapZswFWPwaleheCyXUfVY9dFctVHdz+dmQhkan23kHYjDGanoy4onSszvb b+cdNGGM8JC7PzBx4LdFtKfAZcKi/9PPYs5ofVuCDLp+4vIDgGywu3ilqXFKqmVKApmT 9uqWcx5xECrvSiFy56DV6TBGwIL00dmFJ62pPuzR8ZMovvvgHk9w9qjmDbzJxk6uohRc 8jow==
X-Gm-Message-State: AIVw1102yty/lyytK9nWFip9Lqy/ToRZ2jffZ13w6paVIZ1tqKR3E78a Y4J+82eEopooVRlf
X-Received: by 10.98.200.24 with SMTP id z24mr9110054pff.205.1501302145040; Fri, 28 Jul 2017 21:22:25 -0700 (PDT)
Received: from ?IPv6:2406:e007:4beb:1:28cc:dc4c:9703:6781? ([2406:e007:4beb:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id k4sm13782890pfk.26.2017.07.28.21.22.23 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 Jul 2017 21:22:24 -0700 (PDT)
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: ietf@ietf.org
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <e9095813-b5b5-29ba-34ab-f11c423aea26@cs.tcd.ie> <39FD84EA-4614-4331-B562-C9B2219FE949@fugue.com> <71ace01c-66a1-9e85-145b-8bb11f4d9edc@cs.tcd.ie> <20170729003531.GP79820@shrubbery.net> <m2pockhv68.wl-randy@psg.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <c2b9d518-c93b-57f0-493c-784ed1ceb649@gmail.com>
Date: Sat, 29 Jul 2017 16:22:33 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <m2pockhv68.wl-randy@psg.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rh6VH_adcuobZh-wazcQeEgGpTw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 04:22:29 -0000

On 29/07/2017 13:46, Randy Bush wrote:
...
> getting problems with nat64 identified, diagnosed, and fixed (or worked
> around, sigh) is in the ietf's and the public's interest.

Sure. But dual stack operation is *not* the poor cousin. IMNSHO,
ipv6-only-with-NAT64-with-DNS64 is the poor cousin.

As a compromise, could we have:
1) *No* SSID called "ietf".
2) A secured SSID called "ietf-dual" for the dual stack service.
3) A secured SSID called "ietf-ipv6" for the ipv6+NAT64 service.
4) An insecure "ietf-legacy" that is a dual stack service.
5) The best you can manage for "ietf-hotel", preferably dual stack.

    Brian


From nobody Fri Jul 28 22:02:57 2017
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 082E1131CA3; Fri, 28 Jul 2017 22:02:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, 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 cU4jM7NkGM-m; Fri, 28 Jul 2017 22:02:54 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.185]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1471B12711E; Fri, 28 Jul 2017 22:02:53 -0700 (PDT)
Received: from [192.168.1.96] (cpt84-h01-176-151-112-176.dsl.sta.abo.bbox.fr [176.151.112.176]) by mail.frobbit.se (Postfix) with ESMTPSA id 3E14A21F41; Sat, 29 Jul 2017 07:02:50 +0200 (CEST)
From: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" <paf@frobbit.se>
To: "Ted Lemon" <mellon@fugue.com>
Cc: "Paul Hoffman" <paul.hoffman@vpnc.org>, "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Sat, 29 Jul 2017 07:02:48 +0200
Message-ID: <8AE4855B-EC41-4FB5-83FB-2FD65C078FDC@frobbit.se>
In-Reply-To: <01D1995D-650F-4B8C-96C3-8694C5E5859A@fugue.com>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <B8D4A14E-7A79-4D72-9278-A3F89A343596@vpnc.org> <01D1995D-650F-4B8C-96C3-8694C5E5859A@fugue.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_E6522EBD-050F-4B28-AA3C-1572DE4CB63E_="; micalg=pgp-sha1; protocol="application/pgp-signature"
X-Mailer: MailMate (2.0BETAr6089)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3Ul8f27qo--FCjdyd50Pdv4HjM0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 05:02:56 -0000

This is an OpenPGP/MIME signed message (RFC 3156 and 4880).

--=_MailMate_E6522EBD-050F-4B28-AA3C-1572DE4CB63E_=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 29 Jul 2017, at 0:21, Ted Lemon wrote:

> Arguably, we should use a different SSID every IETF. =C2=A0 E.g., ietf-=
100 instead of ietf.

I am not recommending this.

ICANN is changing SSID every meeting, and it is a pain to get the meeting=
 going.

If there is consensus to make the default SSID (let me call that "IETF") =
IPv6 only, then make "IETF" IPv6 only and add a new SSID that is called s=
omething else "WARNING-IPv4-ONLY-YES-I-KNOW-WHAT-I-AM-DOING" or something=
 else that people manually can add and connect to if they have to.

   Patrik

--=_MailMate_E6522EBD-050F-4B28-AA3C-1572DE4CB63E_=
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename=signature.asc
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAll8FvkACgkQrMabGguI182V5ACfZD/+hJDVliUaH82YEHILtzkL
1SwAnioptnzTbPphySu27gClLKXQOwQC
=nGVI
-----END PGP SIGNATURE-----

--=_MailMate_E6522EBD-050F-4B28-AA3C-1572DE4CB63E_=--


From nobody Sat Jul 29 00:42:38 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BD941323C3 for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 00:42:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 8iagd-SbZxZI for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 00:42:35 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 D8C8F132250 for <ietf@ietf.org>; Sat, 29 Jul 2017 00:42:34 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dbMOL-0008KZ-Gb; Sat, 29 Jul 2017 07:42:29 +0000
Date: Sat, 29 Jul 2017 16:42:28 +0900
Message-ID: <m28tj7it97.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
In-Reply-To: <71ace01c-66a1-9e85-145b-8bb11f4d9edc@cs.tcd.ie>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <e9095813-b5b5-29ba-34ab-f11c423aea26@cs.tcd.ie> <39FD84EA-4614-4331-B562-C9B2219FE949@fugue.com> <71ace01c-66a1-9e85-145b-8bb11f4d9edc@cs.tcd.ie>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FXwa5u9XkIMix17Jd_WXlua7gd4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 07:42:36 -0000

so folk have some data to consider, as of tuesday about 08:00 gmt we had
seen the following unique associations (ietf-hotel excluded, as is not a
measure of choice)

1380 ietf
 967 ietf-legacy99
 611 eduroam
 226 ietf-2.4ONLY
 166 ietf-nat64
  62 ietf-v6ONLY

of course, a device could have been a serial associator, using more than
one network over the measured time period.

some suggested that the high count for legacy99 is partially due to some
devices automatically associating with unprotected networks.

i am not aware of a record of any later snapshot if one was recorded.
and we can not do further analyses now because we wipe all logs at the
end of the meeting just before backing them up (think PII).

randy



From nobody Sat Jul 29 05:54:22 2017
Return-Path: <ekr@rtfm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7565C131FC7 for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 05:54:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.698
X-Spam-Level: 
X-Spam-Status: No, score=-0.698 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-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 npj2AeTbqVhh for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 05:54:20 -0700 (PDT)
Received: from mail-yw0-x232.google.com (mail-yw0-x232.google.com [IPv6:2607:f8b0:4002:c05::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 15E1F131E9F for <ietf@ietf.org>; Sat, 29 Jul 2017 05:54:20 -0700 (PDT)
Received: by mail-yw0-x232.google.com with SMTP id l82so78050276ywc.2 for <ietf@ietf.org>; Sat, 29 Jul 2017 05:54:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=DN/qOOkEBwxX/oiCCbRacTrQ4Dufiouu2CCFvmvaSzY=; b=JhgTXgZ7xxDi3HG90krFrrZwiX93sRyFDWIFTVC9gHBW4VJGPyamPH2pwCAF5KH/Ey i/cspeGV0uPZn3JHMahyH3rku731RSSES7uTNXdT6N00KTB4OnhsMQIdg80/C8uopxvA 6d1/IqmePOZu/gcp8i3Xrukq+LbgAeRNsbLfOHzg07bwNh9nNjH6qZS3WzPfZcnZF4qD 0S22qm70QttRrZwln0RMrJg0GnGg8xZB3L59GHTK3l4QENQ0rfl7r9gPWchkoGmgC4nN or1dMDyKx5fI4fa454J8DJyGC5+RhLZpOAtt3o/IaTtLDGYUoKIj54YRXrfv3XMcBCQ3 SGug==
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=DN/qOOkEBwxX/oiCCbRacTrQ4Dufiouu2CCFvmvaSzY=; b=PZOerVTBPhm1VtZMUvjQ7XA3hw5G9uoMwhmmsZ7cQFExxWaDiH+OhHGRHj8fMNgnbJ +1oMM4ObOu1VKi16LRwrZkbzIxJcSttz/+wJ7PtP4PuU7L5igFctGQTLiHcx9XdxfY6y WxY0OYJEVi1vWE4mbBohlQe+gV0y5rE9IXtv0kxf6EgtOi0sq6Z6zh8hCeo0UrSjGizg ajgHbDhlMy0XPqe+IvSU5Ux25mwGWC7OEy2RN71nWAjTc6KW8a8UFqwdAQVrYjdLMfRT /6BBn10vNGhOszQ0n9Sb5GtS25IkPZIrDYS5qSrXSx2FAVkbDt5PG3nPqi4GatWg6q2b NQ9A==
X-Gm-Message-State: AIVw110uU0OPvyWmK+KZ8KDHAXw+yMksnI91PTRbKYp+Xsmx5gNYvyOp GbLlsNG6DrBxBan7qGp9oun6HjOXP4G/
X-Received: by 10.37.212.22 with SMTP id m22mr2219902ybf.256.1501332859333; Sat, 29 Jul 2017 05:54:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.36.12 with HTTP; Sat, 29 Jul 2017 05:53:38 -0700 (PDT)
In-Reply-To: <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 29 Jul 2017 05:53:38 -0700
Message-ID: <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: Ted Lemon <mellon@fugue.com>
Cc: "Brzozowski, John" <John_Brzozowski@comcast.com>,  "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,  Suresh Krishnan <suresh.krishnan@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c07be5ec545af0555744b18"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1zylj40vA8n5ghW97T60DnMz75s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 12:54:21 -0000

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

On Fri, Jul 28, 2017 at 2:17 PM, Ted Lemon <mellon@fugue.com> wrote:

> On Jul 28, 2017, at 4:38 PM, Eric Rescorla <ekr@rtfm.com> wrote:
>
> I'm not very enthusiastic about this. People come to the IETF to do work
> and having
> to deal with potential bustage from this experiment gets in the way of
> that.
>
>
> If you encounter bustage, you can switch to the legacy network.
>

Of course this is true, but it's equally true that the people who want to
use v6 only can use a separate network. It's not clear why those of us who
just want to get work done need to be inconvenienced in service of a
political point.

-Ekr

You aren't the first person to raise this point, but I find it a bit
> perplexing.
>
>
>

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Fri, Jul 28, 2017 at 2:17 PM, Ted Lemon <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:mellon@fugue.com" target=3D"_blank">mellon@fugue.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"><div style=3D"word-wrap:break=
-word"><span>On Jul 28, 2017, at 4:38 PM, Eric Rescorla &lt;<a href=3D"mail=
to:ekr@rtfm.com" target=3D"_blank">ekr@rtfm.com</a>&gt; wrote:<div><blockqu=
ote type=3D"cite"><div><span style=3D"font-family:Helvetica;font-size:18px;=
font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacin=
g:normal;text-align:start;text-indent:0px;text-transform:none;white-space:n=
ormal;word-spacing:0px;float:none;display:inline!important">I&#39;m not ver=
y enthusiastic about this. People come to the IETF to do work and having</s=
pan><div style=3D"font-family:Helvetica;font-size:18px;font-style:normal;fo=
nt-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:=
start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0=
px">to deal with potential bustage from this experiment gets in the way of =
that.</div></div></blockquote><br></div></span><div>If you encounter bustag=
e, you can switch to the legacy network. =C2=A0</div></div></blockquote><di=
v><br></div><div>Of course this is true, but it&#39;s equally true that the=
 people who want to use v6 only can use a separate network. It&#39;s not cl=
ear why those of us who just want to get work done need to be inconvenience=
d in service of a political point.</div><div><br></div><div>-Ekr</div><div>=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word=
"><div> You aren&#39;t the first person to raise this point, but I find it =
a bit perplexing.</div><div><br></div><br></div></blockquote></div><br></di=
v></div>

--94eb2c07be5ec545af0555744b18--


From nobody Sat Jul 29 07:02:00 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0BB8131C7C for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 07:01:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 rt0jv9u2Pjuy for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 07:01:57 -0700 (PDT)
Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::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 7CFD6131822 for <ietf@ietf.org>; Sat, 29 Jul 2017 07:01:57 -0700 (PDT)
Received: by mail-qt0-x236.google.com with SMTP id a18so73080495qta.0 for <ietf@ietf.org>; Sat, 29 Jul 2017 07:01:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=hF0zidOaYw2TMKoYUhTZSmP1ZANKXBkc6oN3Vz1WS7A=; b=OOK1QlTFo1C5tU3ssfVnLGuAWKJwovbbD+OGSEfOudd02laXJB+XKoRVVEXuoYWlKn X4cdAK/P14yPhfFjDR7YIEpRiZDwkp3jwmV0yxelLFF8QEANemYJVdDAjAR1L0W5q7T4 h26zWiorL16++1c9FdDHfgbgEiiWwrP5IgNEsSuoYc9xZFM5oaUtsj9wWE+Z09/UihhX 81qOa46PdwQHaHfPMe1DEPf+aq+Z1rIR6K/wy18nG6xOUhuIEUErohugwAqLXDWq7ALf 4BDgRB7HQ9ckHAeenejYWIGr/gjbK2auSai9S0M1JKErZVGE9vxjbrq3mZ+SqKkjlZmz 5WIQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=hF0zidOaYw2TMKoYUhTZSmP1ZANKXBkc6oN3Vz1WS7A=; b=UBZ+mRfizXFRAdw38dXhwhY5Ut04LfQAYfHeTrTN3TRfBxM1xcFHI2ZaWG8XcakTXW 6Y+/dL7gS8DH1gTnnAsczb4si0jVToffCRuUFAuyVY3dhcEsP+mLpF6DL8JsjnQLOESL rwWIqZuvveEdKq0csm1zPjMeA5ADLpo6kT1idKdjE+4qYmkKhtPN0ihTod2Xu8iVbT6c GeSN6aWcUq/hDjck0OU+aXHlX+3pUg+nHfl2fE+rzk+3eC8/STEauOslwItIqjwGbqJc GrPutDAt/kQGuQoX5au+IEwXErykKz7xivlpHabOMfeZpZyirhwHg5eRObTlBOZZPCPD 9JxQ==
X-Gm-Message-State: AIVw1128P52F4xPtgNp0afgdm9d8wYeZ9X44ArAblXwiir0mcGrk9aJa pjb88ZW8cwKj4S+wcc8XbA==
X-Received: by 10.200.38.243 with SMTP id 48mr14190270qtp.130.1501336916555; Sat, 29 Jul 2017 07:01:56 -0700 (PDT)
Received: from macbook-pro-6.w50.lede.home (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id s51sm4406193qtc.9.2017.07.29.07.01.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 29 Jul 2017 07:01:55 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_1257B623-8384-48F0-B066-A31713326E86"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Sat, 29 Jul 2017 10:01:54 -0400
In-Reply-To: <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com>
Cc: "Brzozowski, John" <John_Brzozowski@comcast.com>, "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,  Suresh Krishnan <suresh.krishnan@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
To: Eric Rescorla <ekr@rtfm.com>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nweC78e_tNvvL_W0DLM9Cdol1xs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 14:01:59 -0000

--Apple-Mail=_1257B623-8384-48F0-B066-A31713326E86
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jul 29, 2017, at 8:53 AM, Eric Rescorla <ekr@rtfm.com> wrote:
> Of course this is true, but it's equally true that the people who want =
to use v6 only can use a separate network. It's not clear why those of =
us who just want to get work done need to be inconvenienced in service =
of a political point.

It's not a political point, Eric.

The point is that we claim that we have produced something that will =
Just Work for the average user.   If you really think you can't "get =
work done" on an IPv6-only network with working and functional =
transition tech, we have a problem.

So one of two things is true: you are right that such a network would =
not allow IETF attendees to "get work done," or you are wrong.   It =
would be good to know which of these is actually true.   This is the =
point of making it the default: so that you have to opt out rather than =
opting in.   That way we can see how many people opt out, and maybe get =
some feedback as to why.

Honestly, it's really frustrating to me how prevalent this idea is that =
getting things to work is someone else's problem.   You're the last =
person I would have expected to make this case.   Do you think that we =
should still be running TLS 1.1, and that trying to use TLS 1.3 when it =
becomes available would be a "political" choice?   That's essentially =
what you are arguing here, just in a different part of the stack.


--Apple-Mail=_1257B623-8384-48F0-B066-A31713326E86
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jul 29, 2017, at 8:53 AM, Eric Rescorla &lt;<a =
href=3D"mailto:ekr@rtfm.com" class=3D"">ekr@rtfm.com</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">Of course this is true, but it's =
equally true that the people who want to use v6 only can use a separate =
network. It's not clear why those of us who just want to get work done =
need to be inconvenienced in service of a political =
point.</span></div></blockquote></div><br class=3D""><div class=3D"">It's =
not a political point, Eric.</div><div class=3D""><br =
class=3D""></div><div class=3D"">The point is that we claim that we have =
produced something that will Just Work for the average user. &nbsp; If =
you really think you can't "get work done" on an IPv6-only network with =
working and functional transition tech, <i class=3D"">we have a =
problem.</i></div><div class=3D""><br class=3D""></div><div class=3D"">So =
one of two things is true: you are right that such a network would not =
allow IETF attendees to "get work done," or you are wrong. &nbsp; It =
would be good to know which of these is actually true. &nbsp; This is =
the point of making it the default: so that you have to opt out rather =
than opting in. &nbsp; That way we can see how many people opt out, and =
maybe get some feedback as to why.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Honestly, it's really frustrating to me =
how prevalent this idea is that getting things to work is someone else's =
problem. &nbsp; You're the last person I would have expected to make =
this case. &nbsp; Do you think that we should still be running TLS 1.1, =
and that trying to use TLS 1.3 when it becomes available would be a =
"political" choice? &nbsp; That's essentially what you are arguing here, =
just in a different part of the stack.</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_1257B623-8384-48F0-B066-A31713326E86--


From nobody Sat Jul 29 07:48:02 2017
Return-Path: <leifj@mnt.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 486B5131822 for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 07:48:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.697
X-Spam-Level: 
X-Spam-Status: No, score=-0.697 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnt-se.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 ToxFYSaz2FUR for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 07:47:59 -0700 (PDT)
Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::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 2D7B9127B73 for <ietf@ietf.org>; Sat, 29 Jul 2017 07:47:59 -0700 (PDT)
Received: by mail-lf0-x234.google.com with SMTP id y15so100164994lfd.5 for <ietf@ietf.org>; Sat, 29 Jul 2017 07:47:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnt-se.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=OKsP8S4PBG6QQ1jk2c2Em4rfdUJAXR3KTHhSihNh8z4=; b=U1vyrYOw8t7EqAPDlvz9331he67tuuVV2gQPFREwGYYynt+dZYpCvyI6mXcaR/27J2 yLYljN0U62oGuhudQKtA+W4JtwEzM+KaKzN/IlvNxJovadzh/ODE0oDIQ4V1UknL4VIZ UdUZp87q8FiUC5RFqnzDAVWgn//IYrxFom98uOAI8nVWSMMH2XYJ/LJcjJLWrFZ1o7wT QJNlF6vZp1dXob3XEWiGt19Qk4K0ZbB8JJPD85d77UPCDlJ6h3abf7OF8IB0F9xfY/OJ Lwd8QtVQyEe10Qw+PAUfWWyiHL130cPSEhrF8huw7cC9peN0GKNd5rB4BDBHuIDZSZtx DEHQ==
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=OKsP8S4PBG6QQ1jk2c2Em4rfdUJAXR3KTHhSihNh8z4=; b=f2jVzJjCUSZU1fLCJMGXBXHeWi7vUZsLR5th3+FvvpbY4nkdFgFmY1NkwVV9ZeaWp0 bDv1o892ZM3m1wSniiYbO09B3tiGHu45gqpHQaiysISyMoHyTW+UUAYx56JdRdA7nsAW SJ3qCuArVMP1LhMcivSszfTq2wuIzl7e6RQ6Tfsa8whUkTXs0RaGbbxBBYZoksS7d4JP 4iTD7L62MV6GLjbwBmt5vKPABL5cNeAnq3s/q0XgBvCocxouRlX9oRVS9ZLse4HeK86W +Ba8xoykQe2eX3GU7IDcn7JLvw+vOTatkBQolxDF4UUpNk1NHoE9VXrleuHoa4BQcWRN DuLg==
X-Gm-Message-State: AIVw113Y7fzOr1XCDPlV0TQmifT+jyS1FaRgTXGdZSiyOv6g7hcpc/LJ dx1K93XHDCu3QwFd
X-Received: by 10.25.209.20 with SMTP id i20mr3177223lfg.41.1501339677430; Sat, 29 Jul 2017 07:47:57 -0700 (PDT)
Received: from [95.209.44.231] (95.209.44.231.bredband.tre.se. [95.209.44.231]) by smtp.gmail.com with ESMTPSA id v17sm2240534lja.58.2017.07.29.07.47.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 29 Jul 2017 07:47:56 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-307A9079-C5F5-48F0-AE52-AED405F9BDBF
Mime-Version: 1.0 (1.0)
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
From: Leif Johansson <leifj@mnt.se>
X-Mailer: iPhone Mail (14F89)
In-Reply-To: <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com>
Date: Sat, 29 Jul 2017 16:47:55 +0200
Cc: Eric Rescorla <ekr@rtfm.com>, "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,  Suresh Krishnan <suresh.krishnan@gmail.com>, "Brzozowski, John" <John_Brzozowski@comcast.com>, "ietf@ietf.org" <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <3B0BF96C-A504-452F-8C2E-727920AC26D1@mnt.se>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com>
To: Ted Lemon <mellon@fugue.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fnbi23xri0VUrqRGJIbj69-KLVI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 14:48:01 -0000

--Apple-Mail-307A9079-C5F5-48F0-AE52-AED405F9BDBF
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable



Skickat fr=C3=A5n min iPhone

> 29 juli 2017 kl. 16:01 skrev Ted Lemon <mellon@fugue.com>:
>=20
>> On Jul 29, 2017, at 8:53 AM, Eric Rescorla <ekr@rtfm.com> wrote:
>> Of course this is true, but it's equally true that the people who want to=
 use v6 only can use a separate network. It's not clear why those of us who j=
ust want to get work done need to be inconvenienced in service of a politica=
l point.
>=20
> It's not a political point, Eric.
>=20
> The point is that we claim that we have produced something that will Just W=
ork for the average user.   If you really think you can't "get work done" on=
 an IPv6-only network with working and functional transition tech, we have a=
 problem.
>=20
> So one of two things is true: you are right that such a network would not a=
llow IETF attendees to "get work done," or you are wrong.   It would be good=
 to know which of these is actually true.   This is the point of making it t=
he default: so that you have to opt out rather than opting in.   That way we=
 can see how many people opt out, and maybe get some feedback as to why.
>=20
> Honestly, it's really frustrating to me how prevalent this idea is that ge=
tting things to work is someone else's problem.   You're the last person I w=
ould have expected to make this case.   Do you think that we should still be=
 running TLS 1.1, and that trying to use TLS 1.3 when it becomes available w=
ould be a "political" choice?   That's essentially what you are arguing here=
, just in a different part of the stack.
>=20

Or maybe that part of the stack spent less time making sure stuff worked bef=
ore declaring mission accomplished.=

--Apple-Mail-307A9079-C5F5-48F0-AE52-AED405F9BDBF
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=3D=
utf-8"></head><body dir=3D"auto"><div><br><br>Skickat fr=C3=A5n min iPhone</=
div><div><br>29 juli 2017 kl. 16:01 skrev Ted Lemon &lt;<a href=3D"mailto:me=
llon@fugue.com">mellon@fugue.com</a>&gt;:<br><br></div><blockquote type=3D"c=
ite"><div><meta http-equiv=3D"Content-Type" content=3D"text/html charset=3Du=
s-ascii">On Jul 29, 2017, at 8:53 AM, Eric Rescorla &lt;<a href=3D"mailto:ek=
r@rtfm.com" class=3D"">ekr@rtfm.com</a>&gt; wrote:<div><blockquote type=3D"c=
ite" class=3D""><div class=3D""><span style=3D"font-family: Helvetica; font-=
size: 18px; font-style: normal; font-variant-caps: normal; font-weight: norm=
al; letter-spacing: normal; text-align: start; text-indent: 0px; text-transf=
orm: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width=
: 0px; float: none; display: inline !important;" class=3D"">Of course this i=
s true, but it's equally true that the people who want to use v6 only can us=
e a separate network. It's not clear why those of us who just want to get wo=
rk done need to be inconvenienced in service of a political point.</span></d=
iv></blockquote></div><br class=3D""><div class=3D"">It's not a political po=
int, Eric.</div><div class=3D""><br class=3D""></div><div class=3D"">The poi=
nt is that we claim that we have produced something that will Just Work for t=
he average user. &nbsp; If you really think you can't "get work done" on an I=
Pv6-only network with working and functional transition tech, <i class=3D"">=
we have a problem.</i></div><div class=3D""><br class=3D""></div><div class=3D=
"">So one of two things is true: you are right that such a network would not=
 allow IETF attendees to "get work done," or you are wrong. &nbsp; It would b=
e good to know which of these is actually true. &nbsp; This is the point of m=
aking it the default: so that you have to opt out rather than opting in. &nb=
sp; That way we can see how many people opt out, and maybe get some feedback=
 as to why.</div><div class=3D""><br class=3D""></div><div class=3D"">Honest=
ly, it's really frustrating to me how prevalent this idea is that getting th=
ings to work is someone else's problem. &nbsp; You're the last person I woul=
d have expected to make this case. &nbsp; Do you think that we should still b=
e running TLS 1.1, and that trying to use TLS 1.3 when it becomes available w=
ould be a "political" choice? &nbsp; That's essentially what you are arguing=
 here, just in a different part of the stack.</div><div class=3D""><br class=
=3D""></div></div></blockquote><br><div>Or maybe that part of the stack spen=
t less time making sure stuff worked before declaring mission accomplished.<=
/div></body></html>=

--Apple-Mail-307A9079-C5F5-48F0-AE52-AED405F9BDBF--


From nobody Sat Jul 29 08:08:19 2017
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DC27129B5B; Sat, 29 Jul 2017 08:08:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[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 XAwEQ5O2EUiM; Sat, 29 Jul 2017 08:08:16 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 55D7C126C22; Sat, 29 Jul 2017 08:08:16 -0700 (PDT)
Received: from [10.32.60.42] (142-254-101-176.dsl.dynamic.fusionbroadband.com [142.254.101.176]) (authenticated bits=0) by mail.proper.com (8.15.2/8.14.9) with ESMTPSA id v6TF7In3062625 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 29 Jul 2017 08:07:21 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 142-254-101-176.dsl.dynamic.fusionbroadband.com [142.254.101.176] claimed to be [10.32.60.42]
From: "Paul Hoffman" <paul.hoffman@vpnc.org>
To: "Ted Lemon" <mellon@fugue.com>
Cc: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Sat, 29 Jul 2017 08:08:10 -0700
Message-ID: <0CC96AE9-832A-47DB-96A9-5E5DF67B0BA3@vpnc.org>
In-Reply-To: <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.6r5347)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2jXc2fK7LI2sJIEuRldg-GQVNO4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 15:08:17 -0000

On 29 Jul 2017, at 7:01, Ted Lemon wrote:

> On Jul 29, 2017, at 8:53 AM, Eric Rescorla <ekr@rtfm.com> wrote:
>> Of course this is true, but it's equally true that the people who 
>> want to use v6 only can use a separate network. It's not clear why 
>> those of us who just want to get work done need to be inconvenienced 
>> in service of a political point.
>
> It's not a political point, Eric.
>
> The point is that we claim that we have produced something that will 
> Just Work for the average user.

Who is this "we" you are speaking of? I know few people in the IETF who 
make that claim that about v6-only networks, and even fewer who do it 
with a straight face.

> If you really think you can't "get work done" on an IPv6-only network 
> with working and functional transition tech, we have a problem.

Again, that "we". The people who claim that v6-only networks are ready 
by default have a problem, not the IETF as a whole.

--Paul Hoffman


From nobody Sat Jul 29 08:09:06 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66B78131C78 for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 08:09:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 4dcAFL4NG1XN for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 08:09:02 -0700 (PDT)
Received: from mail-pf0-x230.google.com (mail-pf0-x230.google.com [IPv6:2607:f8b0:400e:c00::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 C7BAF126C22 for <ietf@ietf.org>; Sat, 29 Jul 2017 08:09:02 -0700 (PDT)
Received: by mail-pf0-x230.google.com with SMTP id d67so37978387pfc.0 for <ietf@ietf.org>; Sat, 29 Jul 2017 08:09:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=gDYL1oplgo5apmBXsQpNgeKaHa+xDWvHuP41+KBdG2M=; b=FZGNoutMHoV4EzJA61yEb0DiCmOnfLvCduIk42BPuV/lIFSsQC4oLQXVIXegydZxoG Vh6cDsJY9jbQJUgY6dQ3JFq22bOmpkE78eqva2obLznTj6ktPTtlfrOLibXtKdpXfMxK /iMxJ4uucHLa6YjY1il3/gFCwhgoy+DZnvMF8Z+xJYIPnQ2aAuucCBpi1cF1ro848eR5 gzSjMfEqhVnJ03Sgw6KWn+XqqjksdzhFv6LyJ7khkgdSNBqYWDAxOb0+BcmSTeneZMXU 8WhKKrazDYPFYlP7t5CZdMRC4F/NfgzlOK5RTP/I/Br2AB/AWQduxGktf3tTnXs23stA hodw==
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=gDYL1oplgo5apmBXsQpNgeKaHa+xDWvHuP41+KBdG2M=; b=hEBfleh4cZQg0ZhB1hatm/kOfNPmmv2CO82IG17Gpxqc38PhJGUeAMnj4ZXzZbACXz /Vw5go77+TOUDdQWbZPpjnoRkM14LAdJS8MLp4UXTuIac1JS0RJaiMyiSSRBnqaZXGOa +8w2nADzNgHrReVcD6EDYwiNHjsB2Yy1jJELobYhI7RT/6rydefYt442gY+aARmd17B8 8IabiMmKCuPQX9GevcndC8QHYqDTGK5pkon5nlKYAYFPgPGI8txGX1oopyqqdj2vmu87 vc0gDpNxJUU2nZaYYFmnIQDZgzdSLrZgD6eLrld1Hoa9NS/oMIXbtmCTxHggyBExEdPV N44Q==
X-Gm-Message-State: AIVw113ieVy2jgt3kviLX80gTaYxSvGZRtjMOvXnzKp3jyv+NYZY6EWF hcK+2nv6sLGhq52Xhj7dtXgdnpM5w62K
X-Received: by 10.99.56.68 with SMTP id h4mr10416120pgn.52.1501340942239; Sat, 29 Jul 2017 08:09:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.180.131 with HTTP; Sat, 29 Jul 2017 08:08:21 -0700 (PDT)
In-Reply-To: <3B0BF96C-A504-452F-8C2E-727920AC26D1@mnt.se>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <3B0BF96C-A504-452F-8C2E-727920AC26D1@mnt.se>
From: Ted Lemon <mellon@fugue.com>
Date: Sat, 29 Jul 2017 11:08:21 -0400
Message-ID: <CAPt1N1mBx8fR6cTKyRi2d7domqi9-5rV0Ttt-w-fN1B=vDZKdw@mail.gmail.com>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: Leif Johansson <leifj@mnt.se>
Cc: Eric Rescorla <ekr@rtfm.com>,  "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,  Suresh Krishnan <suresh.krishnan@gmail.com>,  "Brzozowski, John" <John_Brzozowski@comcast.com>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="f403045d33f28c9ccd0555762d1e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rsTC3k2iM4EGTrBcYe8WSeXWhjs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 15:09:04 -0000

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

Now *that *is political.

Sorry, Leif.   The deal is that the way you figure out whether something is
working is to try it.   If nobody is willing to try it, there's no way to
be sure that it's working.   The stack itself works fine, and we think the
ops part works too, but in order to *know* that it works, we have to try it=
.

Why is this such an upsetting idea?   Why is it necessary to make someone a
villain here?


On Sat, Jul 29, 2017 at 10:47 AM, Leif Johansson <leifj@mnt.se> wrote:

>
>
> Skickat fr=C3=A5n min iPhone
>
> 29 juli 2017 kl. 16:01 skrev Ted Lemon <mellon@fugue.com>:
>
> On Jul 29, 2017, at 8:53 AM, Eric Rescorla <ekr@rtfm.com> wrote:
>
> Of course this is true, but it's equally true that the people who want to
> use v6 only can use a separate network. It's not clear why those of us wh=
o
> just want to get work done need to be inconvenienced in service of a
> political point.
>
>
> It's not a political point, Eric.
>
> The point is that we claim that we have produced something that will Just
> Work for the average user.   If you really think you can't "get work done=
"
> on an IPv6-only network with working and functional transition tech, *we
> have a problem.*
>
> So one of two things is true: you are right that such a network would not
> allow IETF attendees to "get work done," or you are wrong.   It would be
> good to know which of these is actually true.   This is the point of maki=
ng
> it the default: so that you have to opt out rather than opting in.   That
> way we can see how many people opt out, and maybe get some feedback as to
> why.
>
> Honestly, it's really frustrating to me how prevalent this idea is that
> getting things to work is someone else's problem.   You're the last perso=
n
> I would have expected to make this case.   Do you think that we should
> still be running TLS 1.1, and that trying to use TLS 1.3 when it becomes
> available would be a "political" choice?   That's essentially what you ar=
e
> arguing here, just in a different part of the stack.
>
>
> Or maybe that part of the stack spent less time making sure stuff worked
> before declaring mission accomplished.
>

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

<div dir=3D"ltr">Now <i>that </i>is political.<div><br></div><div>Sorry, Le=
if. =C2=A0 The deal is that the way you figure out whether something is wor=
king is to try it. =C2=A0 If nobody is willing to try it, there&#39;s no wa=
y to be sure that it&#39;s working. =C2=A0 The stack itself works fine, and=
 we think the ops part works too, but in order to <i>know</i>=C2=A0that it =
works, we have to try it.</div><div><br></div><div>Why is this such an upse=
tting idea? =C2=A0 Why is it necessary to make someone a villain here?</div=
><div><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_qu=
ote">On Sat, Jul 29, 2017 at 10:47 AM, Leif Johansson <span dir=3D"ltr">&lt=
;<a href=3D"mailto:leifj@mnt.se" target=3D"_blank">leifj@mnt.se</a>&gt;</sp=
an> 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"auto"><div><br><br=
>Skickat fr=C3=A5n min iPhone</div><div><div class=3D"h5"><div><br>29 juli =
2017 kl. 16:01 skrev Ted Lemon &lt;<a href=3D"mailto:mellon@fugue.com" targ=
et=3D"_blank">mellon@fugue.com</a>&gt;:<br><br></div><blockquote type=3D"ci=
te"><div>On Jul 29, 2017, at 8:53 AM, Eric Rescorla &lt;<a href=3D"mailto:e=
kr@rtfm.com" target=3D"_blank">ekr@rtfm.com</a>&gt; wrote:<div><blockquote =
type=3D"cite"><div><span style=3D"font-family:Helvetica;font-size:18px;font=
-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:no=
rmal;text-align:start;text-indent:0px;text-transform:none;white-space:norma=
l;word-spacing:0px;float:none;display:inline!important">Of course this is t=
rue, but it&#39;s equally true that the people who want to use v6 only can =
use a separate network. It&#39;s not clear why those of us who just want to=
 get work done need to be inconvenienced in service of a political point.</=
span></div></blockquote></div><br><div>It&#39;s not a political point, Eric=
.</div><div><br></div><div>The point is that we claim that we have produced=
 something that will Just Work for the average user. =C2=A0 If you really t=
hink you can&#39;t &quot;get work done&quot; on an IPv6-only network with w=
orking and functional transition tech, <i>we have a problem.</i></div><div>=
<br></div><div>So one of two things is true: you are right that such a netw=
ork would not allow IETF attendees to &quot;get work done,&quot; or you are=
 wrong. =C2=A0 It would be good to know which of these is actually true. =
=C2=A0 This is the point of making it the default: so that you have to opt =
out rather than opting in. =C2=A0 That way we can see how many people opt o=
ut, and maybe get some feedback as to why.</div><div><br></div><div>Honestl=
y, it&#39;s really frustrating to me how prevalent this idea is that gettin=
g things to work is someone else&#39;s problem. =C2=A0 You&#39;re the last =
person I would have expected to make this case. =C2=A0 Do you think that we=
 should still be running TLS 1.1, and that trying to use TLS 1.3 when it be=
comes available would be a &quot;political&quot; choice? =C2=A0 That&#39;s =
essentially what you are arguing here, just in a different part of the stac=
k.</div><div><br></div></div></blockquote><br></div></div><div>Or maybe tha=
t part of the stack spent less time making sure stuff worked before declari=
ng mission accomplished.</div></div></blockquote></div><br></div>

--f403045d33f28c9ccd0555762d1e--


From nobody Sat Jul 29 08:20:06 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 057F5131CC5 for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 08:20:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 5vXh1oDH9rQy for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 08:20:03 -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 8D1C3131CB6 for <ietf@ietf.org>; Sat, 29 Jul 2017 08:20:03 -0700 (PDT)
Received: by mail-pg0-x230.google.com with SMTP id 125so122083684pgi.3 for <ietf@ietf.org>; Sat, 29 Jul 2017 08:20:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=A2czxCLkLFSpyucSRSObOhpWWaJAwOK5EX0VoY/VsqQ=; b=cYonlaRnMPlvPCzEdytpIeHkusuUjmDgudzaPOAdq0o8OfucLDsDoYRZTqzSqF5UX+ fEJ+3rcuSDc8DRp0D2jZUzgqqWGosGvnyDMAslgqVApjkFSvkxxsbdrBKEkiLSoKET50 8vTiY/xEbQPuy7zBpERr8KiMBCUToDINuM3Nr5qLT3rCfnsq8W8PIx3CoUo63TM5nXAb sfJUHqWh8G+X2/EX6n0rpyMBTN2WQKJmF2cORwfDm/lWssZctZdN3NJK0yxc3ZT8Mxu6 70ku86BNE+Iqatr/xybvGuX1iDSLT1l2J/H5LkmSDkjLgbUOyMHiOFHn7Ck5NmuR5rHy HW2A==
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=A2czxCLkLFSpyucSRSObOhpWWaJAwOK5EX0VoY/VsqQ=; b=qncC/nacYVOZ59Wvn9eLfWsGZIEqDzbcyT+35wSsxaFDWTBV1SwCv3u0y/DTxvpg9E nmz8aCF8Yqv7MwEEnIt3Kr0JNJFcTfOGqwvXIXPYBmrMI248oiHXQh71GBF8cned34kJ ApWSB1XW5hgRDG3t9eCNtqiPe3M7TEcQxQ+5CpE6fhdtPle0ypqPaTnkFzUSykTzz2gp ivrley19sLLlgpzautKrgXKsj87WcvwgVa538DmTxwBwP/phWBZgitqryFePK4e9YvA1 v8LEmx1UsiKoix41DjkZKPwWHkrIIeMMABw/uwccQgdcgs6t3FfxwRyewaSmVqYegsZS zpUg==
X-Gm-Message-State: AIVw113bOwu8UfmiuLkQI6ZF9WR+YoF35l78cyPG8MB3wW+ZF/VVQA0C xlB5ERdZ7BzlfmYVNE47WbsdvsG2jOXw
X-Received: by 10.84.215.210 with SMTP id g18mr11491061plj.210.1501341603096;  Sat, 29 Jul 2017 08:20:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.180.131 with HTTP; Sat, 29 Jul 2017 08:19:22 -0700 (PDT)
In-Reply-To: <0CC96AE9-832A-47DB-96A9-5E5DF67B0BA3@vpnc.org>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <0CC96AE9-832A-47DB-96A9-5E5DF67B0BA3@vpnc.org>
From: Ted Lemon <mellon@fugue.com>
Date: Sat, 29 Jul 2017 11:19:22 -0400
Message-ID: <CAPt1N1=8tUWLg03zj_uktUiDyb5f7f9BFmjknDn0H3HTqxEHpw@mail.gmail.com>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: Paul Hoffman <paul.hoffman@vpnc.org>
Cc: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c19f142f07115055576544d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DcLJsNr_6D95ec49PhQQ179wSPw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 15:20:05 -0000

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

The reason you know of few people in the IETF who would make that claim is
that (1) the IETF is actually pretty backwards about trying new things, for
reasons about which I could speculate, but I'm sure that would be a bad
idea.   And (2) IETFers actually use a lot of stuff that regular users
never use, so we are more likely to run into breakage, e.g. Stephen's edge
case.   We are good people to use for testing edge cases.   And I think
most of us are fine with testing edge cases.   So I think that "we" is
actually a lot of IETF participants; however, those IETF participants tend
to avoid the IETF mailing list because discussions like this always devolve
into politics.

The IETF is in the business of designing new networking protocols.   If we
are so allergic to dogfood that we can't even tolerate it for a week at a
time three times a year, when there is an easy way to opt out, I think we
ought to just stop spending millions of tons of carbon every year flying to
these stupid meetings and go grow turnips or something.


On Sat, Jul 29, 2017 at 11:08 AM, Paul Hoffman <paul.hoffman@vpnc.org>
wrote:

> On 29 Jul 2017, at 7:01, Ted Lemon wrote:
>
> On Jul 29, 2017, at 8:53 AM, Eric Rescorla <ekr@rtfm.com> wrote:
>>
>>> Of course this is true, but it's equally true that the people who want
>>> to use v6 only can use a separate network. It's not clear why those of us
>>> who just want to get work done need to be inconvenienced in service of a
>>> political point.
>>>
>>
>> It's not a political point, Eric.
>>
>> The point is that we claim that we have produced something that will Just
>> Work for the average user.
>>
>
> Who is this "we" you are speaking of? I know few people in the IETF who
> make that claim that about v6-only networks, and even fewer who do it with
> a straight face.
>
> If you really think you can't "get work done" on an IPv6-only network with
>> working and functional transition tech, we have a problem.
>>
>
> Again, that "we". The people who claim that v6-only networks are ready by
> default have a problem, not the IETF as a whole.
>
> --Paul Hoffman
>

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

<div dir=3D"ltr">The reason you know of few people in the IETF who would ma=
ke that claim is that (1) the IETF is actually pretty backwards about tryin=
g new things, for reasons about which I could speculate, but I&#39;m sure t=
hat would be a bad idea. =C2=A0 And (2) IETFers actually use a lot of stuff=
 that regular users never use, so we are more likely to run into breakage, =
e.g. Stephen&#39;s edge case. =C2=A0 We are good people to use for testing =
edge cases. =C2=A0 And I think most of us are fine with testing edge cases.=
 =C2=A0 So I think that &quot;we&quot; is actually a lot of IETF participan=
ts; however, those IETF participants tend to avoid the IETF mailing list be=
cause discussions like this always devolve into politics.<div><br></div><di=
v>The IETF is in the business of designing new networking protocols. =C2=A0=
 If we are so allergic to dogfood that we can&#39;t even tolerate it for a =
week at a time three times a year, when there is an easy way to opt out, I =
think we ought to just stop spending millions of tons of carbon every year =
flying to these stupid meetings and go grow turnips or something.</div><div=
><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Sat, Jul 29, 2017 at 11:08 AM, Paul Hoffman <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:paul.hoffman@vpnc.org" target=3D"_blank">paul.hoffman@vpnc.org<=
/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"><span class=3D"">On=
 29 Jul 2017, at 7:01, Ted Lemon wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On Jul 29, 2017, at 8:53 AM, Eric Rescorla &lt;<a href=3D"mailto:ekr@rtfm.c=
om" target=3D"_blank">ekr@rtfm.com</a>&gt; wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Of course this is true, but it&#39;s equally true that the people who want =
to use v6 only can use a separate network. It&#39;s not clear why those of =
us who just want to get work done need to be inconvenienced in service of a=
 political point.<br>
</blockquote>
<br>
It&#39;s not a political point, Eric.<br>
<br>
The point is that we claim that we have produced something that will Just W=
ork for the average user.<br>
</blockquote>
<br></span>
Who is this &quot;we&quot; you are speaking of? I know few people in the IE=
TF who make that claim that about v6-only networks, and even fewer who do i=
t with a straight face.<span class=3D""><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
If you really think you can&#39;t &quot;get work done&quot; on an IPv6-only=
 network with working and functional transition tech, we have a problem.<br=
>
</blockquote>
<br></span>
Again, that &quot;we&quot;. The people who claim that v6-only networks are =
ready by default have a problem, not the IETF as a whole.<span class=3D"HOE=
nZb"><font color=3D"#888888"><br>
<br>
--Paul Hoffman<br>
</font></span></blockquote></div><br></div>

--94eb2c19f142f07115055576544d--


From nobody Sat Jul 29 08:44:47 2017
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 176E5131C3C; Sat, 29 Jul 2017 08:44:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] 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 PR-buDJB9em9; Sat, 29 Jul 2017 08:44:45 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 467E2127444; Sat, 29 Jul 2017 08:44:45 -0700 (PDT)
Received: from [10.32.60.42] (142-254-101-176.dsl.dynamic.fusionbroadband.com [142.254.101.176]) (authenticated bits=0) by mail.proper.com (8.15.2/8.14.9) with ESMTPSA id v6TFhqIN063642 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 29 Jul 2017 08:43:53 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 142-254-101-176.dsl.dynamic.fusionbroadband.com [142.254.101.176] claimed to be [10.32.60.42]
From: "Paul Hoffman" <paul.hoffman@vpnc.org>
To: "Ted Lemon" <mellon@fugue.com>
Cc: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Sat, 29 Jul 2017 08:44:45 -0700
Message-ID: <DF4FC2CA-DC21-468A-A9C3-D1048985E9EF@vpnc.org>
In-Reply-To: <CAPt1N1=8tUWLg03zj_uktUiDyb5f7f9BFmjknDn0H3HTqxEHpw@mail.gmail.com>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <0CC96AE9-832A-47DB-96A9-5E5DF67B0BA3@vpnc.org> <CAPt1N1=8tUWLg03zj_uktUiDyb5f7f9BFmjknDn0H3HTqxEHpw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.6r5347)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OHU9xmObgy_uv41oxXu3iRcLZcQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 15:44:46 -0000

On 29 Jul 2017, at 8:19, Ted Lemon wrote:

> The reason you know of few people in the IETF who would make that 
> claim is
> that (1) the IETF is actually pretty backwards about trying new 
> things, for
> reasons about which I could speculate, but I'm sure that would be a 
> bad
> idea.   And (2) IETFers actually use a lot of stuff that regular users
> never use, so we are more likely to run into breakage, e.g. Stephen's 
> edge
> case.   We are good people to use for testing edge cases.   And I 
> think
> most of us are fine with testing edge cases.

Exactly right. That's why many of us know first-hand that v6 has more 
hard-to-describe choices for end users than v4 does.

> So I think that "we" is
> actually a lot of IETF participants; however, those IETF participants 
> tend
> to avoid the IETF mailing list because discussions like this always 
> devolve
> into politics.

I was not thinking of just people on this mailing list: like you, I talk 
to many people at IETF meetings. I find few people who are not strong v6 
advocates saying that they think a v6-only is will Just Work for the 
average user.

> The IETF is in the business of designing new networking protocols.   
> If we
> are so allergic to dogfood that we can't even tolerate it for a week 
> at a
> time three times a year, when there is an easy way to opt out, I think 
> we
> ought to just stop spending millions of tons of carbon every year 
> flying to
> these stupid meetings and go grow turnips or something.

You can choose to do that if you want, of course: it's an individual 
choice. My preference is to keep developing networking protocols and 
seeing how they help Internet users over time.

--Paul Hoffman


From nobody Sat Jul 29 08:51:14 2017
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A25BC131C3C; Sat, 29 Jul 2017 08:51:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.402
X-Spam-Level: 
X-Spam-Status: No, score=-2.402 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 etmanv8H9Zsv; Sat, 29 Jul 2017 08:51:11 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95DC312EC13; Sat, 29 Jul 2017 08:51:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id B7D2ABE56; Sat, 29 Jul 2017 16:51:08 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3DRXfRKpnHtM; Sat, 29 Jul 2017 16:51:07 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 49C83BE4C; Sat, 29 Jul 2017 16:51:07 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1501343467; bh=RZvS4WoobiQ5c8//3N01uRYJ26t/sLUdeGLZOl7HQw8=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=H6TjEblLjWBT777oROl1g7Le8CJR2OeVHSCpNqnztBDquTib690aeTWmWql4Y8AyW TkTukKqXIAvdOBsBtemraK9vJ4zGrvD0z772vgTQ3guQ9/bRFmRaiKu/TzQNkAH3QO B8LOo9+F1n+w5z2Ron5b15k0cjr33BPoYtWR2HcY=
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: Ted Lemon <mellon@fugue.com>, Paul Hoffman <paul.hoffman@vpnc.org>
Cc: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <0CC96AE9-832A-47DB-96A9-5E5DF67B0BA3@vpnc.org> <CAPt1N1=8tUWLg03zj_uktUiDyb5f7f9BFmjknDn0H3HTqxEHpw@mail.gmail.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <5cf24919-225e-d1f7-fd02-f9d7ba12a472@cs.tcd.ie>
Date: Sat, 29 Jul 2017 16:51:06 +0100
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: <CAPt1N1=8tUWLg03zj_uktUiDyb5f7f9BFmjknDn0H3HTqxEHpw@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="f3qiEbW0W97jqfFuSMkHG2rPBH3BIVroT"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XaIt-EkPErMY76-eWyN32Lk9uOA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 15:51:14 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--f3qiEbW0W97jqfFuSMkHG2rPBH3BIVroT
Content-Type: multipart/mixed; boundary="fPkVWaAOwuM642vNJs544NUI39OAEN33U";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Ted Lemon <mellon@fugue.com>, Paul Hoffman <paul.hoffman@vpnc.org>
Cc: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org"
 <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,
 "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <5cf24919-225e-d1f7-fd02-f9d7ba12a472@cs.tcd.ie>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF
 Meetings
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com>
 <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com>
 <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com>
 <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com>
 <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com>
 <0CC96AE9-832A-47DB-96A9-5E5DF67B0BA3@vpnc.org>
 <CAPt1N1=8tUWLg03zj_uktUiDyb5f7f9BFmjknDn0H3HTqxEHpw@mail.gmail.com>
In-Reply-To: <CAPt1N1=8tUWLg03zj_uktUiDyb5f7f9BFmjknDn0H3HTqxEHpw@mail.gmail.com>

--fPkVWaAOwuM642vNJs544NUI39OAEN33U
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: quoted-printable



On 29/07/17 16:19, Ted Lemon wrote:
> The IETF is in the business of designing new networking protocols.   If=
 we
> are so allergic to dogfood that we can't even tolerate it for a week at=
 a
> time three times a year, when there is an easy way to opt out, I think =
we
> ought to just stop spending millions of tons of carbon every year flyin=
g to
> these stupid meetings and go grow turnips or something.

- I quite like the occasional turnip, but hate the idea of
having to grow the feckers:-)

- I'm also fine with dogfood, e.g the DPRIVE test last time
worked just fine for me - even though I had to switch DNS stuff
about when switching from ietf-hotel to gsm, I was ok with that
as it was an opt-in and I'd opted-in.

- I don't like the sound of the query logging in section 3.1
of the draft, but am confident that the NOC folks wouldn't do
something bad there. It'd still be good to see that properly
described before any switch over, esp if as a default, as I
guess the draft is really aimed at a bigger audience who may
not be as clueful about privacy as our NOC team.

- I have no clue if Ubuntu supports this now - section 4.2
of the draft doesn't fill me with confidence, and I'm puzzled
as to how the draft figures ssh will continue to work "without
incident" given known_hosts has v4 addresses. And opting-in
here will change the state of known_hosts I guess in a way
that might in principle lead to attacks (that said I've not
checked what ssh clients know about dns64/nat64).

The above "corner cases", (not that I agree they are:-), the
DNSSEC stuff already mentioned together and Randy's figures
imply to me that this isn't yet ready to be a default, and
ought remain an opt-in.

I might try it out next time though.

One other note: if there were a perceived benefit for the folks
opting-in that'd help your cause I think. "You can help us all
make this better" is not a sufficiently direct benefit to attract
that many dogfood eaters IMO.

Cheers,
S.




--fPkVWaAOwuM642vNJs544NUI39OAEN33U--

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

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJZfK7qAAoJEC88hzaAX42iK5sIAKZUXB8fm0sQB6Y5AlLHbMvj
o8+D8PgxD2jW34gHacQihc7HG07SetQ/NeoH6hUOICgZhd56nNt/wjaNHeq7t/mr
JxK+34Lur37Q/hUnjJ5JBTS30cLMQzEDKwLsdciouiBMq0mdUzFlJ5Nr1YFQ7x5c
ybv9aybsA0ycWnHfMO239/wWxdXeMIuofvE9Ai1/jlljdtixgvuG0dPkN8wrlll3
tscO45JN59eEZ5lHa/hHrL0v5ZXPRI6toPX1oo6Hg8Q15a7lqTx8IGofCmfvJ0oJ
KVzy/uErx7HIDkeCJIAJFVTdsdn5P9C8YNLOWPZnHY/ZUH2jT4X1GuAyb9vMYc0=
=vDp4
-----END PGP SIGNATURE-----

--f3qiEbW0W97jqfFuSMkHG2rPBH3BIVroT--


From nobody Sat Jul 29 09:22:52 2017
Return-Path: <leifj@mnt.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92F0C131B79 for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 09:22:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.697
X-Spam-Level: 
X-Spam-Status: No, score=-0.697 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnt-se.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 B1zjkSNS6PkG for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 09:22:49 -0700 (PDT)
Received: from mail-lf0-x231.google.com (mail-lf0-x231.google.com [IPv6:2a00:1450:4010:c07::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 04018131945 for <ietf@ietf.org>; Sat, 29 Jul 2017 09:22:49 -0700 (PDT)
Received: by mail-lf0-x231.google.com with SMTP id g25so96998611lfh.1 for <ietf@ietf.org>; Sat, 29 Jul 2017 09:22:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnt-se.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ALm/LTu7lSZcBrtnvFTxUoX/GsQtXC9qDMM6Wvjc8d4=; b=RVa+BJY0plwNzfI3NGvAeAu3lIHNrpO8NPLXMUmtKFsikD3xTaMZS7gNViIoHU9SBy w1F+9DRBSc6NM57M0aFxN4XTxnRDm41BkQ7/pUE+J8euXAbg3qrLun+Ytcbjc2F+XSdJ i2pX284kqXqVP3YP6IpVP2XObF578AGaMUDXTt03v74HIL/XV3lnrV7neJxi/bSZeGef FmoV6FComBzjp1rYMoMNENJW2AXR2ZLaHnlYSNQwtnkdRKdpYAxM3IqCf2GSvOKnDZ9S Mn1U7Pcid6qjRt7IQTKqFDuNVkNFz+e4SP55Gsc3dDdvT2c8l8v0gwhmZK5wTUTX6mNM 2iHQ==
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=ALm/LTu7lSZcBrtnvFTxUoX/GsQtXC9qDMM6Wvjc8d4=; b=tpiqQXzcwIPxGEqTPxK8iFJUbVpTv974G0uhSdN8t4BqoFhqvgoRbEhYbpZ5Lu1PHc p6Hctj0E58oeiYKKfGqllmLJC9gbtBgpp3ISTtjOzmbxCqlf3Km+7glCcrvn63lXRncv I+lpp0KfJ6dw6vm3tK/2t3VgRXxyIzSnhANL4HmiINSZhmC703Kqa86CDu/t0ty+Xhez 7d/v+fmrunSPlRpr9KcKlMXPMhw9+ASW2vFhZ0BssYXsy8TWyFeg3mvEZ/hq8dhe/UmI 41vgCsELteT4WD1Hw0DXhcyX8XrrFF5Ays4+3zSYaSMmPAItHfsRbp2ZvbwYqA8Lza9X iJCQ==
X-Gm-Message-State: AIVw111uW84nv0Nm1GoMdPx3FIXzKoVIBYZtph33A2oKXjpJUD7IhLt5 CvkDwcHQikHKZ8Ly
X-Received: by 10.25.168.3 with SMTP id r3mr3196286lfe.111.1501345367156; Sat, 29 Jul 2017 09:22:47 -0700 (PDT)
Received: from [2.67.72.161] (2.67.72.161.mobile.tre.se. [2.67.72.161]) by smtp.gmail.com with ESMTPSA id f80sm5126700lji.23.2017.07.29.09.22.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 29 Jul 2017 09:22:46 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-2F241FBB-B455-4E71-9F63-7E77E016CA91
Mime-Version: 1.0 (1.0)
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
From: Leif Johansson <leifj@mnt.se>
X-Mailer: iPhone Mail (14F89)
In-Reply-To: <CAPt1N1mBx8fR6cTKyRi2d7domqi9-5rV0Ttt-w-fN1B=vDZKdw@mail.gmail.com>
Date: Sat, 29 Jul 2017 18:22:45 +0200
Cc: Eric Rescorla <ekr@rtfm.com>, "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,  Suresh Krishnan <suresh.krishnan@gmail.com>, "Brzozowski, John" <John_Brzozowski@comcast.com>, "ietf@ietf.org" <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <236273C2-87B0-4F5E-8F0E-5D5190364DED@mnt.se>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <3B0BF96C-A504-452F-8C2E-727920AC26D1@mnt.se> <CAPt1N1mBx8fR6cTKyRi2d7domqi9-5rV0Ttt-w-fN1B=vDZKdw@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/B1FSJ1_Dy31vfOGgRFyMAabODGo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 16:22:52 -0000

--Apple-Mail-2F241FBB-B455-4E71-9F63-7E77E016CA91
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable



Skickat fr=C3=A5n min iPhone

> 29 juli 2017 kl. 17:08 skrev Ted Lemon <mellon@fugue.com>:
>=20
> Now that is political.
>=20
> Sorry, Leif.   The deal is that the way you figure out whether something i=
s working is to try it.   If nobody is willing to try it, there's no way to b=
e sure that it's working.   The stack itself works fine, and we think the op=
s part works too, but in order to know that it works, we have to try it.
>=20


I was merely reacting to what I felt was a lopsided analogy between v6 (whic=
h has had ample time to get tested outside the IETF) and TLS 1.3. The latter=
 is including *lots* of work on implementation and real-world testing in the=
 WG workstream.

> Why is this such an upsetting idea?   Why is it necessary to make someone a=
 villain here?

It isn't. I see no villains.

>=20
>=20
>> On Sat, Jul 29, 2017 at 10:47 AM, Leif Johansson <leifj@mnt.se> wrote:
>>=20
>>=20
>> Skickat fr=C3=A5n min iPhone
>>=20
>>> 29 juli 2017 kl. 16:01 skrev Ted Lemon <mellon@fugue.com>:
>>>=20
>>>> On Jul 29, 2017, at 8:53 AM, Eric Rescorla <ekr@rtfm.com> wrote:
>>>> Of course this is true, but it's equally true that the people who want t=
o use v6 only can use a separate network. It's not clear why those of us who=
 just want to get work done need to be inconvenienced in service of a politi=
cal point.
>>>=20
>>> It's not a political point, Eric.
>>>=20
>>> The point is that we claim that we have produced something that will Jus=
t Work for the average user.   If you really think you can't "get work done"=
 on an IPv6-only network with working and functional transition tech, we hav=
e a problem.
>>>=20
>>> So one of two things is true: you are right that such a network would no=
t allow IETF attendees to "get work done," or you are wrong.   It would be g=
ood to know which of these is actually true.   This is the point of making i=
t the default: so that you have to opt out rather than opting in.   That way=
 we can see how many people opt out, and maybe get some feedback as to why.
>>>=20
>>> Honestly, it's really frustrating to me how prevalent this idea is that g=
etting things to work is someone else's problem.   You're the last person I w=
ould have expected to make this case.   Do you think that we should still be=
 running TLS 1.1, and that trying to use TLS 1.3 when it becomes available w=
ould be a "political" choice?   That's essentially what you are arguing here=
, just in a different part of the stack.
>>>=20
>>=20
>> Or maybe that part of the stack spent less time making sure stuff worked b=
efore declaring mission accomplished.
>=20

--Apple-Mail-2F241FBB-B455-4E71-9F63-7E77E016CA91
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=3D=
utf-8"></head><body dir=3D"auto"><div><br><br>Skickat fr=C3=A5n min iPhone</=
div><div><br>29 juli 2017 kl. 17:08 skrev Ted Lemon &lt;<a href=3D"mailto:me=
llon@fugue.com">mellon@fugue.com</a>&gt;:<br><br></div><blockquote type=3D"c=
ite"><div><div dir=3D"ltr">Now <i>that </i>is political.<div><br></div><div>=
Sorry, Leif. &nbsp; The deal is that the way you figure out whether somethin=
g is working is to try it. &nbsp; If nobody is willing to try it, there's no=
 way to be sure that it's working. &nbsp; The stack itself works fine, and w=
e think the ops part works too, but in order to <i>know</i>&nbsp;that it wor=
ks, we have to try it.</div><div><br></div></div></div></blockquote><div><br=
></div><div><br></div><div>I was merely reacting to what I felt was a lopsid=
ed analogy between v6 (which has had ample time to get tested outside the IE=
TF) and TLS 1.3. The latter is including *lots* of work on implementation an=
d real-world testing in the WG workstream.</div><br><blockquote type=3D"cite=
"><div><div dir=3D"ltr"><div>Why is this such an upsetting idea? &nbsp; Why i=
s it necessary to make someone a villain here?</div></div></div></blockquote=
><div><br></div><div>It isn't. I see no villains.</div><br><blockquote type=3D=
"cite"><div><div dir=3D"ltr"><div><br></div></div><div class=3D"gmail_extra"=
><br><div class=3D"gmail_quote">On Sat, Jul 29, 2017 at 10:47 AM, Leif Johan=
sson <span dir=3D"ltr">&lt;<a href=3D"mailto:leifj@mnt.se" target=3D"_blank"=
>leifj@mnt.se</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div di=
r=3D"auto"><div><br><br>Skickat fr=C3=A5n min iPhone</div><div><div class=3D=
"h5"><div><br>29 juli 2017 kl. 16:01 skrev Ted Lemon &lt;<a href=3D"mailto:m=
ellon@fugue.com" target=3D"_blank">mellon@fugue.com</a>&gt;:<br><br></div><b=
lockquote type=3D"cite"><div>On Jul 29, 2017, at 8:53 AM, Eric Rescorla &lt;=
<a href=3D"mailto:ekr@rtfm.com" target=3D"_blank">ekr@rtfm.com</a>&gt; wrote=
:<div><blockquote type=3D"cite"><div><span style=3D"font-family:Helvetica;fo=
nt-size:18px;font-style:normal;font-variant-caps:normal;font-weight:normal;l=
etter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;wh=
ite-space:normal;word-spacing:0px;float:none;display:inline!important">Of co=
urse this is true, but it's equally true that the people who want to use v6 o=
nly can use a separate network. It's not clear why those of us who just want=
 to get work done need to be inconvenienced in service of a political point.=
</span></div></blockquote></div><br><div>It's not a political point, Eric.</=
div><div><br></div><div>The point is that we claim that we have produced som=
ething that will Just Work for the average user. &nbsp; If you really think y=
ou can't "get work done" on an IPv6-only network with working and functional=
 transition tech, <i>we have a problem.</i></div><div><br></div><div>So one o=
f two things is true: you are right that such a network would not allow IETF=
 attendees to "get work done," or you are wrong. &nbsp; It would be good to k=
now which of these is actually true. &nbsp; This is the point of making it t=
he default: so that you have to opt out rather than opting in. &nbsp; That w=
ay we can see how many people opt out, and maybe get some feedback as to why=
.</div><div><br></div><div>Honestly, it's really frustrating to me how preva=
lent this idea is that getting things to work is someone else's problem. &nb=
sp; You're the last person I would have expected to make this case. &nbsp; D=
o you think that we should still be running TLS 1.1, and that trying to use T=
LS 1.3 when it becomes available would be a "political" choice? &nbsp; That'=
s essentially what you are arguing here, just in a different part of the sta=
ck.</div><div><br></div></div></blockquote><br></div></div><div>Or maybe tha=
t part of the stack spent less time making sure stuff worked before declarin=
g mission accomplished.</div></div></blockquote></div><br></div>
</div></blockquote></body></html>=

--Apple-Mail-2F241FBB-B455-4E71-9F63-7E77E016CA91--


From nobody Sat Jul 29 09:31:06 2017
Return-Path: <rlb@ipv.sx>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FFBB131CB6 for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 09:31:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.698
X-Spam-Level: 
X-Spam-Status: No, score=-0.698 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.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 8o-CBL4yl15p for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 09:31:03 -0700 (PDT)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (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 4CB9312ECEF for <ietf@ietf.org>; Sat, 29 Jul 2017 09:31:03 -0700 (PDT)
Received: by mail-wm0-x22c.google.com with SMTP id m85so43697623wma.0 for <ietf@ietf.org>; Sat, 29 Jul 2017 09:31:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=3yo9zCsLBhue8zzuDSMq9Xnwxyngp/yQF6rKmTlKFJg=; b=zujNQJXpQHPmD4U/fPp6/WpMOa0ts8mRWLNGDTzWF/cVSsE5Hql5bT4YMpR5p3+piY 7AtCDKOeBxXq51j0MhAEvNcEEY00d2KBc7thPXTzVRftwuGdCIN3pjYvAd/oYsLoM5sA 2Kw9sw9qbOUG/urZqi7JVtL8GP4w6VC3hZ7gBXkAtXAGOwLyHzgn+ZgAvLJRrOPOPRoJ /hChxdfPW3eQGAhJA6O2o4aV7A9mLiNEVYtKBtP1DEoT//1j30nZPHHQDAhqVGQkxQ1T 7TGpKIQQAuAeYffHvqu3/FwuBnfCSOUtS+HPkWwZ+7UAyBK5Zy6io6uFamIyy0Wd/26F zrXQ==
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=3yo9zCsLBhue8zzuDSMq9Xnwxyngp/yQF6rKmTlKFJg=; b=mCOKtnEKuLSJk3p8XpfT1VjFA4AN+tWPKf4RnY77Sx2X5CWJpoG8XeGcJ6ULsE2h1a aHL6gTZgYWG3z5nB/AYdm43QuDLzhMSJ6mEIy3D3HeeTHwVMCE46Bg/Y98grSTxInVLI 56zv37i7ywC+2W904ekliOm+yTlVS8bQF7TZm2Nu98XmPjxscYQvRqWDoobU/jwXUxWy hB6PPWlnq9UyvUhjVPtKSMn4h9OlwkMvXSkj+CbaP4kGiLCIQX15QsyrDOlR3bOm2U2o MbE9HagwiUL1FWY4cN3TP1o9Le5c8rJfvpPavbYXkm2nlr8NIkUK5zHCcK7TdmWBcxc/ 84AA==
X-Gm-Message-State: AIVw1112zxuHd9tdkrpvd8QGZ/q0L467xBbI0uq1W9McO2271ky11UbE x3r3+s4dS+v5O4/kZb5Sr5EHlfSd0SuM
X-Received: by 10.28.66.193 with SMTP id k62mr3019371wmi.4.1501345861594; Sat, 29 Jul 2017 09:31:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.225.5 with HTTP; Sat, 29 Jul 2017 09:31:00 -0700 (PDT)
In-Reply-To: <5cf24919-225e-d1f7-fd02-f9d7ba12a472@cs.tcd.ie>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <0CC96AE9-832A-47DB-96A9-5E5DF67B0BA3@vpnc.org> <CAPt1N1=8tUWLg03zj_uktUiDyb5f7f9BFmjknDn0H3HTqxEHpw@mail.gmail.com> <5cf24919-225e-d1f7-fd02-f9d7ba12a472@cs.tcd.ie>
From: Richard Barnes <rlb@ipv.sx>
Date: Sat, 29 Jul 2017 12:31:00 -0400
Message-ID: <CAL02cgTkR56TWfThZ+iSLYkuFXm0Rf561ukKfefKne9ycJB6=w@mail.gmail.com>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: Ted Lemon <mellon@fugue.com>, Paul Hoffman <paul.hoffman@vpnc.org>,  "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c0707cac40dc60555775251"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/albZSmxfVRohXaiIAv5tUikk9ms>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 16:31:05 -0000

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

This is not the Internet Debugging Task Force.  People come to IETF
meetings to get work done, not to debug operational issues.

Of course people should be doing research on operational impacts of the
protocols being developed, bringing the results of that research to the
relevant WGs, and adapting protocols to deal with them.  The TLS 1.3 work
has gone through this cycle several times.

However, just like the TLS 1.3 experimentation was not done on production
servers that were meant for doing actual work, neither is the IETF network
the right place to be discovering protocol issues.  If people want to opt
in, fine, but let's not make it the default.




On Sat, Jul 29, 2017 at 11:51 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie
> wrote:

>
>
> On 29/07/17 16:19, Ted Lemon wrote:
> > The IETF is in the business of designing new networking protocols.   If
> we
> > are so allergic to dogfood that we can't even tolerate it for a week at a
> > time three times a year, when there is an easy way to opt out, I think we
> > ought to just stop spending millions of tons of carbon every year flying
> to
> > these stupid meetings and go grow turnips or something.
>
> - I quite like the occasional turnip, but hate the idea of
> having to grow the feckers:-)
>
> - I'm also fine with dogfood, e.g the DPRIVE test last time
> worked just fine for me - even though I had to switch DNS stuff
> about when switching from ietf-hotel to gsm, I was ok with that
> as it was an opt-in and I'd opted-in.
>
> - I don't like the sound of the query logging in section 3.1
> of the draft, but am confident that the NOC folks wouldn't do
> something bad there. It'd still be good to see that properly
> described before any switch over, esp if as a default, as I
> guess the draft is really aimed at a bigger audience who may
> not be as clueful about privacy as our NOC team.
>
> - I have no clue if Ubuntu supports this now - section 4.2
> of the draft doesn't fill me with confidence, and I'm puzzled
> as to how the draft figures ssh will continue to work "without
> incident" given known_hosts has v4 addresses. And opting-in
> here will change the state of known_hosts I guess in a way
> that might in principle lead to attacks (that said I've not
> checked what ssh clients know about dns64/nat64).
>
> The above "corner cases", (not that I agree they are:-), the
> DNSSEC stuff already mentioned together and Randy's figures
> imply to me that this isn't yet ready to be a default, and
> ought remain an opt-in.
>
> I might try it out next time though.
>
> One other note: if there were a perceived benefit for the folks
> opting-in that'd help your cause I think. "You can help us all
> make this better" is not a sufficiently direct benefit to attract
> that many dogfood eaters IMO.
>
> Cheers,
> S.
>
>
>
>

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

<div dir=3D"ltr"><div>This is not the Internet Debugging Task Force.=C2=A0 =
People come to IETF meetings to get work done, not to debug operational iss=
ues.=C2=A0 <br></div><div><br></div><div>Of course people should be doing r=
esearch on operational impacts of the protocols being developed, bringing t=
he results of that research to the relevant WGs, and adapting protocols to =
deal with them.=C2=A0 The TLS 1.3 work has gone through this cycle several =
times.</div><div><br></div><div>However, just like the TLS 1.3 experimentat=
ion was not done on production servers that were meant for doing actual wor=
k, neither is the IETF network the right place to be discovering protocol i=
ssues.=C2=A0 If people want to opt in, fine, but let&#39;s not make it the =
default.<br></div><div><div><div><br></div><div><br></div><div><br></div><d=
iv><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Sat, Jul 29=
, 2017 at 11:51 AM, Stephen Farrell <span dir=3D"ltr">&lt;<a href=3D"mailto=
:stephen.farrell@cs.tcd.ie" target=3D"_blank">stephen.farrell@cs.tcd.ie</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"><span class=3D""><br>
<br>
On 29/07/17 16:19, Ted Lemon wrote:<br>
&gt; The IETF is in the business of designing new networking protocols.=C2=
=A0 =C2=A0If we<br>
&gt; are so allergic to dogfood that we can&#39;t even tolerate it for a we=
ek at a<br>
&gt; time three times a year, when there is an easy way to opt out, I think=
 we<br>
&gt; ought to just stop spending millions of tons of carbon every year flyi=
ng to<br>
&gt; these stupid meetings and go grow turnips or something.<br>
<br>
</span>- I quite like the occasional turnip, but hate the idea of<br>
having to grow the feckers:-)<br>
<br>
- I&#39;m also fine with dogfood, e.g the DPRIVE test last time<br>
worked just fine for me - even though I had to switch DNS stuff<br>
about when switching from ietf-hotel to gsm, I was ok with that<br>
as it was an opt-in and I&#39;d opted-in.<br>
<br>
- I don&#39;t like the sound of the query logging in section 3.1<br>
of the draft, but am confident that the NOC folks wouldn&#39;t do<br>
something bad there. It&#39;d still be good to see that properly<br>
described before any switch over, esp if as a default, as I<br>
guess the draft is really aimed at a bigger audience who may<br>
not be as clueful about privacy as our NOC team.<br>
<br>
- I have no clue if Ubuntu supports this now - section 4.2<br>
of the draft doesn&#39;t fill me with confidence, and I&#39;m puzzled<br>
as to how the draft figures ssh will continue to work &quot;without<br>
incident&quot; given known_hosts has v4 addresses. And opting-in<br>
here will change the state of known_hosts I guess in a way<br>
that might in principle lead to attacks (that said I&#39;ve not<br>
checked what ssh clients know about dns64/nat64).<br>
<br>
The above &quot;corner cases&quot;, (not that I agree they are:-), the<br>
DNSSEC stuff already mentioned together and Randy&#39;s figures<br>
imply to me that this isn&#39;t yet ready to be a default, and<br>
ought remain an opt-in.<br>
<br>
I might try it out next time though.<br>
<br>
One other note: if there were a perceived benefit for the folks<br>
opting-in that&#39;d help your cause I think. &quot;You can help us all<br>
make this better&quot; is not a sufficiently direct benefit to attract<br>
that many dogfood eaters IMO.<br>
<br>
Cheers,<br>
S.<br>
<br>
<br>
<br>
</blockquote></div><br></div></div></div></div></div>

--94eb2c0707cac40dc60555775251--


From nobody Sat Jul 29 09:53:20 2017
Return-Path: <prvs=13836d3557=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2C911317B1 for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 09:53:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.099
X-Spam-Level: 
X-Spam-Status: No, score=-0.099 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
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 yY6I9b94bwOi for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 09:53:16 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A9531276AF for <ietf@ietf.org>; Sat, 29 Jul 2017 09:53:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1501347194; x=1501951994; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=sfKJu0nACHP7lfy7WrUC8fIc3 wpIJkjIAa3cTLvUdZ0=; b=iFAMo8tdwMXG9CTMYsYwQqA9MAWwbUNeOyNb7Zl/D DYEl7hrKtmn9kk+M1PfiEKMB8mhmS2GXgvkotDgAIWf3h7+qAeuGtgItvy/A3jYD XBuCMkCHNcrtDLMTdVkxaI40WvSggAsIHwgC5MO6Z4U9oolxQpET4uJGLZ3j06cn kA=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=Talhpm327pH2d3+E5xXGthnyMIk0TM0dcuhQpi+qxAaZmJRkpRIBsgs/REmw GgE3pMsP1DUu7V7ZyQ+umuLcQP++I/sdhSgFvCZLolqw70gvMcLfNrjKg iMGXDvUVVfnfxODPNksmoR/ROqfFSsUf5g6o34yRmN8Os8wwjk3i1s=;
X-MDAV-Processed: mail.consulintel.es, Sat, 29 Jul 2017 18:53:14 +0200
X-Spam-Processed: mail.consulintel.es, Sat, 29 Jul 2017 18:53:10 +0200
Received: from [10.10.10.133] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005489867.msg for <ietf@ietf.org>; Sat, 29 Jul 2017 18:53:09 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170729:md50005489867::vFIPnIMMOQM8UMy8:000010lM
X-Return-Path: prvs=13836d3557=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.24.1.170721
Date: Sat, 29 Jul 2017 18:53:08 +0200
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <F9259043-6373-4AD0-ADE2-AFE6709E449B@consulintel.es>
Thread-Topic: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <0CC96AE9-832A-47DB-96A9-5E5DF67B0BA3@vpnc.org> <CAPt1N1=8tUWLg03zj_uktUiDyb5f7f9BFmjknDn0H3HTqxEHpw@mail.gmail.com> <5cf24919-225e-d1f7-fd02-f9d7ba12a472@cs.tcd.ie> <CAL02cgTkR56TWfThZ+iSLYkuFXm0Rf561ukKfefKne9ycJB6=w@mail.gmail.com>
In-Reply-To: <CAL02cgTkR56TWfThZ+iSLYkuFXm0Rf561ukKfefKne9ycJB6=w@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mJfFzGFM8XfV6_Dq6ajTZIy7a_k>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 16:53:19 -0000

+1

Exactly: despite how much I=E2=80=99m pro-IPv6 and not suspicious of being =
against it, and I agree we should try our own dogfood, I fully agree we MUS=
T not force all the IETF participants to try it, as we aren=E2=80=99t the D=
ebugging Task Force, unless we change our principles and clearly state that=
 the IETF network must be considered experimental and in equal conditions f=
or ANYONE willing to experiment on it, despite breaking anything for the re=
st.

Furthermore:
1) Even if we discover 100 of apps that get broken because the =E2=80=9CIPv=
6-only=E2=80=9D network, are we the Internet police or do we have a way to =
tell those apps developers to do it right?
2) If that=E2=80=99s the case, WHO is going to take the work for notifying =
the vendors/developers of those apps and making sure that they actually sol=
ve the problems?
3) We have a major problem here. We don=E2=80=99t have a real definition of=
 what it means IPv6-only. If we believe that the world will run IPv6-only i=
n the near 3-5 years, we are probably wrong, because we don=E2=80=99t have =
the power to make it happen. I agree we are turning into an IPv6-only acces=
s networks world, but we will keep LANs with dual-stack (with private IPv4 =
addresses and some transition mechanism in the access router) until 80% of =
the app developers are done and we can then start considering getting rid-o=
ff IPv4 at 100%.

If anyone is interesting in contributing to clarifying the concept of IPv6-=
only, please, comment in v6ops (pvt is ok too) about:

https://datatracker.ietf.org/doc/draft-palet-ietf-v6ops-ipv6-only/

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Richard Barnes <rlb@ipv.sx>
Responder a: <rlb@ipv.sx>
Fecha: s=C3=A1bado, 29 de julio de 2017, 18:31
Para: Stephen Farrell <stephen.farrell@cs.tcd.ie>
CC: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6op=
s-ietf-ipv6-only-incremental@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org=
>, "ietf@ietf.org" <ietf@ietf.org>
Asunto: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF =
Meetings

    This is not the Internet Debugging Task Force.  People come to IETF mee=
tings to get work done, not to debug operational issues. =20
   =20
   =20
    Of course people should be doing research on operational impacts of the=
 protocols being developed, bringing the results of that research to the re=
levant WGs, and adapting protocols to deal with them.  The TLS 1.3 work has=
 gone through this cycle several times.
   =20
    However, just like the TLS 1.3 experimentation was not done on producti=
on servers that were meant for doing actual work, neither is the IETF netwo=
rk the right place to be discovering protocol issues.  If people want to op=
t in, fine, but let's not make it the default.
   =20
   =20
   =20
   =20
   =20
    On Sat, Jul 29, 2017 at 11:51 AM, Stephen Farrell <stephen.farrell@cs.t=
cd.ie> wrote:
   =20
   =20
   =20
    On 29/07/17 16:19, Ted Lemon wrote:
    > The IETF is in the business of designing new networking protocols.   =
If we
    > are so allergic to dogfood that we can't even tolerate it for a week =
at a
    > time three times a year, when there is an easy way to opt out, I thin=
k we
    > ought to just stop spending millions of tons of carbon every year fly=
ing to
    > these stupid meetings and go grow turnips or something.
   =20
    - I quite like the occasional turnip, but hate the idea of
    having to grow the feckers:-)
   =20
    - I'm also fine with dogfood, e.g the DPRIVE test last time
    worked just fine for me - even though I had to switch DNS stuff
    about when switching from ietf-hotel to gsm, I was ok with that
    as it was an opt-in and I'd opted-in.
   =20
    - I don't like the sound of the query logging in section 3.1
    of the draft, but am confident that the NOC folks wouldn't do
    something bad there. It'd still be good to see that properly
    described before any switch over, esp if as a default, as I
    guess the draft is really aimed at a bigger audience who may
    not be as clueful about privacy as our NOC team.
   =20
    - I have no clue if Ubuntu supports this now - section 4.2
    of the draft doesn't fill me with confidence, and I'm puzzled
    as to how the draft figures ssh will continue to work "without
    incident" given known_hosts has v4 addresses. And opting-in
    here will change the state of known_hosts I guess in a way
    that might in principle lead to attacks (that said I've not
    checked what ssh clients know about dns64/nat64).
   =20
    The above "corner cases", (not that I agree they are:-), the
    DNSSEC stuff already mentioned together and Randy's figures
    imply to me that this isn't yet ready to be a default, and
    ought remain an opt-in.
   =20
    I might try it out next time though.
   =20
    One other note: if there were a perceived benefit for the folks
    opting-in that'd help your cause I think. "You can help us all
    make this better" is not a sufficiently direct benefit to attract
    that many dogfood eaters IMO.
   =20
    Cheers,
    S.
   =20
   =20
   =20
   =20
   =20
   =20
   =20
   =20
   =20
   =20
   =20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Sat Jul 29 09:54:29 2017
Return-Path: <huitema@huitema.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC5B5131C4F for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 09:54:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.701
X-Spam-Level: 
X-Spam-Status: No, score=-0.701 tagged_above=-999 required=5 tests=[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 A6atzTVdzVfS for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 09:54:26 -0700 (PDT)
Received: from mx45.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 59DE81276AF for <ietf@ietf.org>; Sat, 29 Jul 2017 09:54:26 -0700 (PDT)
Received: from xsmtp31.mail2web.com ([168.144.250.234] helo=xsmtp11.mail2web.com) by mx45.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1dbV0R-0004S3-Nj for ietf@ietf.org; Sat, 29 Jul 2017 18:54:24 +0200
Received: from [10.5.2.17] (helo=xmail07.myhosting.com) by xsmtp11.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1dbUzt-0007ow-KQ for ietf@ietf.org; Sat, 29 Jul 2017 12:54:20 -0400
Received: (qmail 24116 invoked from network); 29 Jul 2017 16:53:46 -0000
Received: from unknown (HELO [192.168.1.103]) (Authenticated-user:_huitema@huitema.net@[172.56.42.66]) (envelope-sender <huitema@huitema.net>) by xmail07.myhosting.com (qmail-ldap-1.03) with ESMTPA for <ietf@ietf.org>; 29 Jul 2017 16:53:46 -0000
To: ietf@ietf.org
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <e9095813-b5b5-29ba-34ab-f11c423aea26@cs.tcd.ie> <39FD84EA-4614-4331-B562-C9B2219FE949@fugue.com> <71ace01c-66a1-9e85-145b-8bb11f4d9edc@cs.tcd.ie> <m28tj7it97.wl-randy@psg.com>
From: Christian Huitema <huitema@huitema.net>
Message-ID: <305594a4-c49c-cdcc-8c6a-4c5464431f49@huitema.net>
Date: Sat, 29 Jul 2017 09:53:43 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <m28tj7it97.wl-randy@psg.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
X-Originating-IP: 168.144.250.234
X-SpamExperts-Domain: xsmtpout.mail2web.com
X-SpamExperts-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-SpamExperts-Outgoing-Class: unsure
X-SpamExperts-Outgoing-Evidence: Combined (0.12)
X-Recommended-Action: accept
X-Filter-ID: PqwsvolAWURa0gwxuN3S5YEa3T7JuZT23fGO2rGt3ZgTCGhDnudOJ80D1c8rffxrus7BTv7Ss8cH d2IQQuvdbtM+m4WpRRDP6YzwkAPgQJY8hyefn/FOeAH6Zsqubs62ND46yZLY9QyX+cRXmooQ3hum JwiT+2brWmQlzkLIcXivpIH4ag6BM/+u9ym+BA23xr0hcu3XjpbM756iu2Yy9oCguACQY+STnTP7 IZRHeVmKFLtfeRNs5dZXGcJ+TzagYOEkjsX7F8KmpUaZQHV+SWsC1ltxhvDAAiytf1zpGXO2G5Pj 7iQJEmtNUzH3idZ6uMF2OhyCCCV83x+RZrKIj0QqMGQOSwmEPwP4wBzM77N8GvkYGGDFjg9NrmGY yNnXsSjdYwfRhjHqxQXDsBKLpKOHi0RYvlOYvJoUtCbvS/b6lO4FGen962xgCFRckncKfg1XSK9P 1z/R6plfrFWGydoP7Njwkj9bgQNuxcScIbHeNHk15VolAGHS5rCXQKDym+Gab6cuAPzLi/SdAxlO dgkraHgbbAuZgv0Q6mJ3vUcipz1IT62ZEk6+MmovaufbiR3bHfnMCIEU+nrglojKwMr3vOY18GvB wSXAfWcj2354nZsRKkBYcatjRBY+lWZsNdSMuNhZC3X/nGdDKYyg+1Fotn1TGspRGWfHjmaruO0b XpkevaElTi+sCWwmqxHi+BUHXGjp0J8FpT+J6AFTxtOtsgdMIfWz4G5QKOuFdWw078I0y+3uS4dN KiUgYTBUbhKI389aFgJzvFSwJezeLoAbiteDwjw8P7mx/NBHSRWxZaHLvUGmD7PXY2RS8idsz7fr MHsNPRylYAkPvY1HttQOF909qtkcRbvucYBIc/TSiGRBfhCjzofKjrwJNQRY0i13zjCiwPgdt77s k1WBMw==
X-Report-Abuse-To: spam@quarantine5.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FprItk7jq-dgakBUABekXxP-PfU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 16:54:28 -0000

On 7/29/2017 12:42 AM, Randy Bush wrote:
> so folk have some data to consider, as of tuesday about 08:00 gmt we ha=
d
> seen the following unique associations (ietf-hotel excluded, as is not =
a
> measure of choice)
>
> 1380 ietf
>  967 ietf-legacy99
>  611 eduroam
>  226 ietf-2.4ONLY
>  166 ietf-nat64
>   62 ietf-v6ONLY
>
> of course, a device could have been a serial associator, using more tha=
n
> one network over the measured time period.
I may be a serial associator, since I connected my laptop to ietf,
ietf-nat64, and ietf-v6ONLY. The connection to "ietf" was automatic,
something the laptop remembered from time past. I purposely tried
ietf-v6only, because I like try stuff. Did not work well. One of the
servers I rely on is IPv4 only, and that was just not accessible. I fell
back to ietf-nat64, and it was OK.

So if the purpose of "eating our own dogfood" is to find out bugs and
breakage, here is a clear finding: IPv6 only networks do not provide
access to IPv4 only services today. NAT64 networks seem to work, but we
suspect that there are some drawbacks, such as messing up with DNSSEC,
and maybe also interfering with some P2P services.

So here I go with my $0.02 suggestion: moving the default to IPv6-only
won't work, but moving to NAT64 would mostly work. It would also
probably teach us what exactly is wrong with that technology.

--=20
Christian Huitema



From nobody Sat Jul 29 09:55:03 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15D0E1276AF for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 09:55:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 EQ1kccgupb0b for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 09:54:59 -0700 (PDT)
Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::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 A2C7B131CB7 for <ietf@ietf.org>; Sat, 29 Jul 2017 09:54:59 -0700 (PDT)
Received: by mail-qt0-x235.google.com with SMTP id s6so102199288qtc.1 for <ietf@ietf.org>; Sat, 29 Jul 2017 09:54:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=D1EV+IPj5WX/ALd0Q0uaCLSokDgGIiudniCWIArBqsE=; b=HH01SiSLzs6K7/SEKyCt8PS8WGTal6yXbJkNYMQQHrSdwVB0nwlE92eCwTzGYmIGJk cJQ0TLU27gfdyZ6VnQKQ1f7WZq8jvxvf6JyNtwp4NT48dk7ez62E/kwRYGCGpzqHJfyi uWoyMccn3InmYWj6KAi2n2vZ2GHEXQcfuYX9E1Y9ZFBAXrXXg1PGxXngW/szCbRaCapx bgEzESSn+1EdUu1p1PcjrIjb9G9Avj24tMvXD/eEZl7wCdu490TIL3c+uM7ssIqa6VMb 631Qr5seRneJiX04jaofvRIOQLg+T3wKLUmytxe9ih+T4HnbXas3rqx2PPj8xGyOFPYj ytEg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=D1EV+IPj5WX/ALd0Q0uaCLSokDgGIiudniCWIArBqsE=; b=CjjjtJrk3uwjF5guNrbI3EaDQZtrf1ETpRGI9ZfzdrV+qdFXMYHLVh8TZiQJmRA7LH /YJVB+gfBaXHJ+F6p/P86L+GkCFpvmsE2QayFuFnGhsv8y+NZg/tiK3rd65hvjOPLjmL fvbqK7wJ8N+r1PL5QMqzjDp2XPVubuZaUKdvLsn0EKfvI60C+DizywWnpOCDvKvLyS2u OxS/TtXOWUxYslUXLZeh1LuCEKkXyTrOGfqKusNwxXulIKnfz14kW66fDXERlGXm6xwQ DbN/1GtqdQDLh2L6v85NJcfv5h5wnTF5CTkzswqQuFQ9FZ3JL3z7Ec+iovL/mxwlNNXL +BXA==
X-Gm-Message-State: AIVw111XocTYlcweoFezMvUxXcO+r69A/PsTQqIKsayPmDPsawvRmLXb WttvtQZy7Rztzo4n9qqqww==
X-Received: by 10.200.36.74 with SMTP id d10mr16249596qtd.298.1501347298470; Sat, 29 Jul 2017 09:54:58 -0700 (PDT)
Received: from macbook-pro-6.w50.lede.home (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id d184sm16928059qkc.68.2017.07.29.09.54.56 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 29 Jul 2017 09:54:56 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E67FC9E4-79A2-488E-B618-885940693917"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Sat, 29 Jul 2017 12:54:55 -0400
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <0CC96AE9-832A-47DB-96A9-5E5DF67B0BA3@vpnc.org> <CAPt1N1=8tUWLg03zj_uktUiDyb5f7f9BFmjknDn0H3HTqxEHpw@mail.gmail.com> <DF4FC2CA-DC21-468A-A9C3-D1048985E9EF@vpnc.org>
To: "ietf@ietf.org" <ietf@ietf.org>
In-Reply-To: <DF4FC2CA-DC21-468A-A9C3-D1048985E9EF@vpnc.org>
Message-Id: <6366C6A1-8DAA-4B3A-A2E4-CBD22A4B3F38@fugue.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9fZoj9nvZjziqDVYKVdayFwyemU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 16:55:02 -0000

--Apple-Mail=_E67FC9E4-79A2-488E-B618-885940693917
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jul 29, 2017, at 11:44 AM, Paul Hoffman <paul.hoffman@vpnc.org> =
wrote:
> Exactly right. That's why many of us know first-hand that v6 has more =
hard-to-describe choices for end users than v4 does.

For the end user, there are no choices.   You plug your device into the =
network, and it works, or it doesn't.   What choices are you imagining?

> I was not thinking of just people on this mailing list: like you, I =
talk to many people at IETF meetings. I find few people who are not =
strong v6 advocates saying that they think a v6-only is will Just Work =
for the average user.

Forgive me, but it's always easy to put words in the mouths of people =
who aren't saying anything.   What you are saying here is that everyone =
who is silent on this topic agrees that IPv6 isn't going to Just Work =
for the end-user.   Do you see the flaw in your reasoning?

On Jul 29, 2017, at 11:51 AM, Stephen Farrell =
<stephen.farrell@cs.tcd.ie> wrote:
> - I have no clue if Ubuntu supports this now - section 4.2
> of the draft doesn't fill me with confidence, and I'm puzzled
> as to how the draft figures ssh will continue to work "without
> incident" given known_hosts has v4 addresses. And opting-in
> here will change the state of known_hosts I guess in a way
> that might in principle lead to attacks (that said I've not
> checked what ssh clients know about dns64/nat64).

Right, so known_hosts is broken, because it remembers IP addresses.   =
This is something that ought to get fixed, not persisted.   Imagine how =
this feature interacts with the private service discovery feature that =
is being worked on in dnssd, when the host being connected to does IP =
address privacy.

I want _you_ in particular to use IPv6+nat64 because it will show you =
where some of the implementations of software that you currently use are =
broken, and then (I hope) you will get on board with trying to get them =
fixed.   That's the value proposition.   OpenVPN has known about their =
IPv6 brokenness for about four years, and they still haven't done =
anything about it.

> One other note: if there were a perceived benefit for the folks
> opting-in that'd help your cause I think. "You can help us all
> make this better" is not a sufficiently direct benefit to attract
> that many dogfood eaters IMO.

Right, that's why the "opt out" rather than "opt in" proposal.   We've =
had "opt in" since two Berlins ago, and we just don't get a lot of =
people trying the "opt in" network.   The value proposition is pretty =
obvious to me: we get to see how many people opt out.

On Sat, Jul 29, 2017 at 10:47 AM, Leif Johansson <leifj@mnt.se =
<mailto:leifj@mnt.se>> wrote:
> It isn't. I see no villains.

When you say that something that someone is trying to do that you =
disagree with is political, you are implicitly saying that there is a =
villain, and it is that bad person who is trying to do something for =
"political reasons".   Please don't do that.

IPv6 has had a lot more testing than TLS 1.3.

> On Jul 29, 2017, at 12:31 PM, Richard Barnes <rlb@ipv.sx> wrote:

>> However, just like the TLS 1.3 experimentation was not done on =
production servers that were meant for doing actual work, neither is the =
IETF network the right place to be discovering protocol issues.  If =
people want to opt in, fine, but let's not make it the default.

The conclusion that I would draw from this argument is that you believe =
that nobody should ever use TLS 1.3, because it is new, and it will =
always be the case that at some point in the process end-users will be =
exposed to it for the first time, and possibly run into issues.   That =
sort of thing should never happen in production, hence TLS 1.3 should =
never be deployed.

That really is what you are saying.   The IETF has been running =
IPv6-only with NAT64 as a transition tech for about four years, and I'm =
guessing you've never opted in.   So your argument is basically "it's =
not my problem, and it will never be okay for us to run this in =
production, let's just keep using IPv4."=

--Apple-Mail=_E67FC9E4-79A2-488E-B618-885940693917
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jul 29, 2017, at 11:44 AM, Paul Hoffman &lt;<a =
href=3D"mailto:paul.hoffman@vpnc.org" =
class=3D"">paul.hoffman@vpnc.org</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D"">Exactly right. =
That's why many of us know first-hand that v6 has more hard-to-describe =
choices for end users than v4 does.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>For the =
end user, there are no choices. &nbsp; You plug your device into the =
network, and it works, or it doesn't. &nbsp; What choices are you =
imagining?</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D"">I was not thinking of just =
people on this mailing list: like you, I talk to many people at IETF =
meetings. I find few people who are not strong v6 advocates saying that =
they think a v6-only is will Just Work for the average =
user.</div></div></blockquote></div><br class=3D""><div class=3D"">Forgive=
 me, but it's always easy to put words in the mouths of people who =
aren't saying anything. &nbsp; What you are saying here is that everyone =
who is silent on this topic agrees that IPv6 isn't going to Just Work =
for the end-user. &nbsp; Do you see the flaw in your =
reasoning?</div><div class=3D""><br class=3D""></div><div class=3D"">On =
Jul 29, 2017, at 11:51 AM, Stephen Farrell &lt;<a =
href=3D"mailto:stephen.farrell@cs.tcd.ie" =
class=3D"">stephen.farrell@cs.tcd.ie</a>&gt; wrote:<br =
class=3D""><div><blockquote type=3D"cite" class=3D"">- I have no clue if =
Ubuntu supports this now - section 4.2<br class=3D""><div class=3D"">of =
the draft doesn't fill me with confidence, and I'm puzzled<br =
class=3D"">as to how the draft figures ssh will continue to work =
"without<br class=3D"">incident" given known_hosts has v4 addresses. And =
opting-in<br class=3D"">here will change the state of known_hosts I =
guess in a way<br class=3D"">that might in principle lead to attacks =
(that said I've not<br class=3D"">checked what ssh clients know about =
dns64/nat64).</div></blockquote><div><br class=3D""></div>Right, so =
known_hosts is broken, because it remembers IP addresses. &nbsp; This is =
something that ought to get fixed, not persisted. &nbsp; Imagine how =
this feature interacts with the private service discovery feature that =
is being worked on in dnssd, when the host being connected to does IP =
address privacy.</div><div><br class=3D""></div><div>I want _you_ in =
particular to use IPv6+nat64 because it will show you where some of the =
implementations of software that you currently use are broken, and then =
(I hope) you will get on board with trying to get them fixed. &nbsp; =
That's the value proposition. &nbsp; OpenVPN has known about their IPv6 =
brokenness for about four years, and they still haven't done anything =
about it.<br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D"">One other note: if there were a perceived benefit for the =
folks<br class=3D"">opting-in that'd help your cause I think. "You can =
help us all<br class=3D"">make this better" is not a sufficiently direct =
benefit to attract<br class=3D"">that many dogfood eaters IMO.<br =
class=3D""></blockquote></div><br class=3D""><div class=3D"">Right, =
that's why the "opt out" rather than "opt in" proposal. &nbsp; We've had =
"opt in" since two Berlins ago, and we just don't get a lot of people =
trying the "opt in" network. &nbsp; The value proposition is pretty =
obvious to me: we get to see how many people opt out.</div></div><div =
class=3D""><div class=3D"gmail_extra"><div class=3D"gmail_quote"><br =
class=3D""></div><div class=3D"gmail_quote">On Sat, Jul 29, 2017 at =
10:47 AM, Leif Johansson&nbsp;<span dir=3D"ltr" class=3D"">&lt;<a =
href=3D"mailto:leifj@mnt.se" target=3D"_blank" =
class=3D"">leifj@mnt.se</a>&gt;</span>&nbsp;wrote:</div></div></div><div =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">It =
isn't. I see no villains.</div></blockquote><br class=3D""></div><div =
class=3D"">When you say that something that someone is trying to do that =
you disagree with is political, you are implicitly saying that there is =
a villain, and it is that bad person who is trying to do something for =
"political reasons". &nbsp; Please don't do that.</div><div class=3D""><br=
 class=3D""></div><div class=3D"">IPv6 has had a lot more testing than =
TLS 1.3.</div><div class=3D""><br class=3D""></div><div =
class=3D""><blockquote type=3D"cite" class=3D"">On Jul 29, 2017, at =
12:31 PM, Richard Barnes &lt;<a href=3D"mailto:rlb@ipv.sx" =
class=3D"">rlb@ipv.sx</a>&gt; wrote:<br class=3D""></blockquote><br =
class=3D""><blockquote type=3D"cite" class=3D""><div><blockquote =
type=3D"cite" class=3D"">However, just like the TLS 1.3 experimentation =
was not done on production servers that were meant for doing actual =
work, neither is the IETF network the right place to be discovering =
protocol issues.&nbsp; If people want to opt in, fine, but let's not =
make it the default.</blockquote></div></blockquote><br =
class=3D""></div><div class=3D"">The conclusion that I would draw from =
this argument is that you believe that nobody should <i =
class=3D"">ever</i>&nbsp;use TLS 1.3, because it is new, and it will =
always be the case that at some point in the process end-users will be =
exposed to it for the first time, and possibly run into issues. &nbsp; =
That sort of thing should never happen in production, hence TLS 1.3 =
should never be deployed.</div><div class=3D""><br class=3D""></div><div =
class=3D"">That really is what you are saying. &nbsp; The IETF has been =
running IPv6-only with NAT64 as a transition tech for about four years, =
and I'm guessing you've never opted in. &nbsp; So your argument is =
basically "it's not my problem, and it will never be okay for us to run =
this in production, let's just keep using IPv4."</div></body></html>=

--Apple-Mail=_E67FC9E4-79A2-488E-B618-885940693917--


From nobody Sat Jul 29 10:55:28 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AD7F131CD5 for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 10:55:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.002
X-Spam-Level: 
X-Spam-Status: No, score=-5.002 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 M97tp-2fuul4 for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 10:55:26 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 48E4F131C88 for <ietf@ietf.org>; Sat, 29 Jul 2017 10:55:26 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dbVxU-0001gu-6a; Sat, 29 Jul 2017 17:55:24 +0000
Date: Sun, 30 Jul 2017 02:55:22 +0900
Message-ID: <m2y3r7gmb9.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ted Lemon <mellon@fugue.com>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
In-Reply-To: <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Qs_oLJcQDvbyi2pHYhSOw5SaWRw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 17:55:27 -0000

> The point is that we claim that we have produced something that will
> Just Work for the average user.  If you really think you can't "get
> work done" on an IPv6-only network with working and functional
> transition tech, we have a problem.

bingo!  you are right.  we have a problem.  nat64/dns64 breaks things
people use.  this is known, documented, and extremely annoying this many
years out [0].

the question is how to progress fixing nat64/dns64, given that a lot of
folk come to ietf meetings to simply get work done and not debug a semi-
working transport.  how about a bug bounty?  and maybe a fix bounty a
few times larger!

randy

--

0 - for just how many years, see my plenary rant against 4966 a few
    chicagos back.  it is my $dayjob's customers, the enterprises, who
    are the main target of nat64/dns64, and i am not happy that they can
    not deploy it safely.


From nobody Sat Jul 29 11:18:21 2017
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B819131C32 for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 11:18:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.402
X-Spam-Level: 
X-Spam-Status: No, score=-2.402 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
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 J6IxIyf14uP7 for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 11:18:17 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBF5B131D3D for <ietf@ietf.org>; Sat, 29 Jul 2017 11:18:16 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6TIHmhh031936; Sat, 29 Jul 2017 19:17:49 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v6TIHmhh031936
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1501352270; bh=fJ1Z4eQB9BhyEuxZYCz07f+ceXc=; h=From:Mime-Version:Subject:Date:References:To:In-Reply-To; b=pn4EHgAxWHjguPWbSz/IzfWmmc5pyLRq5199tjQY1jsjxQ+ScnA4AfuXvFuyg0CXY ooQ2ByzWNDEpbe696JFEEGtqak1vf/oSeNVGsr69EXP2Qk6Zxl+AoMuhfdEUsWxa0e GVRkbX1dT5/crInZN+fu2Hrfmyl2gvHgpZrcWWAk=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id y6SJHm2070906038je ret-id none; Sat, 29 Jul 2017 19:17:50 +0100
Received: from 20010a88d51011.ipv6.customer.clara.net (20010a88d51011.ipv6.customer.clara.net [IPv6:2001:a88:d510:1101:f008:5644:2557:1009] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6TIHfYG020368 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 29 Jul 2017 19:17:41 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Sat, 29 Jul 2017 19:17:39 +0100
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <e9095813-b5b5-29ba-34ab-f11c423aea26@cs.tcd.ie> <39FD84EA-4614-4331-B562-C9B2219FE949@fugue.com> <71ace01c-66a1-9e85-145b-8bb11f4d9edc@cs.tcd.ie> <m28tj7it97.wl-randy@psg.com> <305594a4-c49c-cdcc-8c6a-4c5464431f49@huitema.net> <9F93A245-38F0-4A66-9418-4478F292677F@ecs.soton.ac.uk>
To: Christian Huitema <huitema@huitema.net>, IETF Discussion <ietf@ietf.org>
In-Reply-To: <305594a4-c49c-cdcc-8c6a-4c5464431f49@huitema.net>
Message-ID: <EMEW3|79c4c6564a9184e6fcca8fbd0d116402y6SJHm03tjc|ecs.soton.ac.uk|9F93A245-38F0-4A66-9418-4478F292677F@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.3273)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=y6SJHl207090603800; tid=y6SJHm2070906038je; client=relay,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v6TIHmhh031936
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/F75EAppaz3xboLm_QS8ZerwRdeQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 18:18:19 -0000

Hi,

There are many issues intertwined here. I think there are three of =
particular interest:

1. Which technology the =E2=80=98ietf=E2=80=99 SSID offers, as the =
=E2=80=98default=E2=80=99.

There=E2=80=99s some emotive language being used here, but ultimately =
the decision will not prevent anyone getting work done, so long as one =
production quality SSID can be selected.

What the decision does affect is the volume of data we obtain on the =
operation of NAT64/DNS64/464XLAT at the meeting. At IETF99, Randy=E2=80=99=
s data reported 1,380 ietf SSID users, and 166 ietf-nat64 SSID users, as =
of Tuesday morning.  And around 1,900 users with a device on a different =
SSID to those two. So as it stands, around 5% of device associations are =
to the NAT64 network. =20

Would we like to raise the number of devices using the NAT64 network? If =
so, how, if not running the ietf SSD with it?

2. Whether we fully understand how devices of various common OSes select =
an SSID on startup, without manual intervention.

The line in Randy=E2=80=99s data that puzzled me was the 967 devices =
associating to the ietf-legacy99 SSID. I believe the SSID had the =
meeting number appended to avoid devices just re-associating to an =
=E2=80=98ietf-legacy=E2=80=99 SSID every meeting. By adding the number, =
one might hope users would have to manually select the SSID. But perhaps =
at least one major OS prefers this SSID because of its open property?

Understanding an OS=E2=80=99s SSID selection behaviour is important if =
we=E2=80=99re concerned about people having to manually set the =
production quality SSID, and to know that they won=E2=80=99t drift back =
to an undesired SSID while working or on a network (re)attachment.

3. How we capture and report the experiences of users / devices running =
NAT64/DNS64/464XLAT.

Christian said:
> So if the purpose of "eating our own dogfood" is to find out bugs and
> breakage, here is a clear finding: IPv6 only networks do not provide
> access to IPv4 only services today. NAT64 networks seem to work, but =
we
> suspect that there are some drawbacks, such as messing up with DNSSEC,
> and maybe also interfering with some P2P services.

A fair 10,000=E2=80=99 summary, probably. But what empirical evidence do =
we have? What data are we able to gather at an IETF meeting on the =
success or failures of NAT/64/DNS64 (and 464XLAT where also used), =
whether we have 166 devices on the NAT64 SSID, or 1,166 devices? And how =
can this data be publicly reported for everyone to learn and benefit =
from?=20

Tim=


From nobody Sat Jul 29 11:18:46 2017
Return-Path: <ekr@rtfm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7C18131DFC for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 11:18:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.698
X-Spam-Level: 
X-Spam-Status: No, score=-0.698 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-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 kFHqICqU2SVd for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 11:18:40 -0700 (PDT)
Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002: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 22D6B131DA2 for <ietf@ietf.org>; Sat, 29 Jul 2017 11:18:39 -0700 (PDT)
Received: by mail-yw0-x236.google.com with SMTP id p68so1642719ywg.0 for <ietf@ietf.org>; Sat, 29 Jul 2017 11:18:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ICVTgJlpWDP2sgUOtYg8dXwACoJI0cFUEFpsTwWT9Jk=; b=EB7mtkOYEZKYlljEYP2LlrIBMuGYFOkuKxdOyKGV7O4Ka5ybxd298S/1GuVMG0Wj3w 60PqlyW+Um3A4nORg2hzron/RrnYTa4wklZrcCUayJ1iFDpuZJBinrYyvMd4J1zzlEI2 WnpH3rO0/Zagk2CsqXr8C/NuCtb1oSMy1TO80nkRK4D5Ic49q8oWgx2BeodMbaeyRvSY LACdyK45V75U8+hR8+3U0p+HPvAzOnrAis+BQv3wibmpugA/EhKRtuCO5F41OO/zv5IN D84vdiih55MtFsbjKmibrnpY5CoAnFlBPjMS4TxESaUqlXc9f1F1mUbGKXalpf20fsZ9 SHhA==
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=ICVTgJlpWDP2sgUOtYg8dXwACoJI0cFUEFpsTwWT9Jk=; b=VxJKaU73T9GtbV/Ko7lH0tApqan2tQTAeeVpJIPg9N2E2cA/8A+vyeYKW+5v2bB0M5 RoO78Js//WOvX3kXuXEXwqbUrVDJxP4NB+jVU7fBnrszhNbHjAhwyL8EvZlJdpR4I361 qU+N1zIc/NhwxOfGkuIsNdbHN9Yi/L6FxcQOdNwOuDbeaauynM2ITprMzfpJ8gM1F4XE wIU3l+jwHoWT3IUHruUT2pNQ8gNFFHfOpKeqF0jAyPEYIqTUZ1ngZoQ4iNeyXT40cziH kTD9z3m9mxSssBRUSbI/IXQhg49SLV/8UiCN0Z+gLynbtYg7ZfgWYqwOqyMAhbq5QMLV tEUw==
X-Gm-Message-State: AIVw113fbzbHe20zHdPJDE/oTv8M3plBhsPgu2l75h4wsLT0qF0VDkHn q9VpYtatKLK0PFWBCar8WzQS25jesmj/
X-Received: by 10.129.172.21 with SMTP id k21mr1686954ywh.321.1501352318405; Sat, 29 Jul 2017 11:18:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.36.12 with HTTP; Sat, 29 Jul 2017 11:17:57 -0700 (PDT)
In-Reply-To: <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 29 Jul 2017 11:17:57 -0700
Message-ID: <CABcZeBOMnMPsQwCr9UjND3iP3WiY3GxTZ2WbeP1cMeZqmhNgRA@mail.gmail.com>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: Ted Lemon <mellon@fugue.com>
Cc: "Brzozowski, John" <John_Brzozowski@comcast.com>,  "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,  Suresh Krishnan <suresh.krishnan@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="f4030436885e9f32dd055578d3e3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8tXZ6HyGC9VHsJMj73S3kbE0HcU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 18:18:42 -0000

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

On Sat, Jul 29, 2017 at 7:01 AM, Ted Lemon <mellon@fugue.com> wrote:

> On Jul 29, 2017, at 8:53 AM, Eric Rescorla <ekr@rtfm.com> wrote:
>
> Of course this is true, but it's equally true that the people who want to
> use v6 only can use a separate network. It's not clear why those of us who
> just want to get work done need to be inconvenienced in service of a
> political point.
>
>
> It's not a political point, Eric.
>

We'll have to agree to differ, I suppose.


>
> The point is that we claim that we have produced something that will Just
> Work for the average user.   If you really think you can't "get work done"
> on an IPv6-only network with working and functional transition tech, *we
> have a problem.*
>
> So one of two things is true: you are right that such a network would not
> allow IETF attendees to "get work done," or you are wrong.   It would be
> good to know which of these is actually true.   This is the point of making
> it the default: so that you have to opt out rather than opting in.   That
> way we can see how many people opt out, and maybe get some feedback as to
> why.
>

In other words, you want to opt everyone into doing your testing for you.
Again, that's not the purpose of the IETF network.



> Honestly, it's really frustrating to me how prevalent this idea is that
> getting things to work is someone else's problem.   You're the last person
> I would have expected to make this case.   Do you think that we should
> still be running TLS 1.1, and that trying to use TLS 1.3 when it becomes
> available would be a "political" choice?   That's essentially what you are
> arguing here, just in a different part of the stack.
>

No, it's not. The right analogy would be filtering out TLS 1.3 at our
network edge, which you absolutely do not see me suggesting.

-Ekr

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Sat, Jul 29, 2017 at 7:01 AM, Ted Lemon <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:mellon@fugue.com" target=3D"_blank">mellon@fugue.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"><div style=3D"word-wrap:break=
-word"><span class=3D"">On Jul 29, 2017, at 8:53 AM, Eric Rescorla &lt;<a h=
ref=3D"mailto:ekr@rtfm.com" target=3D"_blank">ekr@rtfm.com</a>&gt; wrote:<d=
iv><blockquote type=3D"cite"><div><span style=3D"font-family:Helvetica;font=
-size:18px;font-style:normal;font-variant-caps:normal;font-weight:normal;le=
tter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;wh=
ite-space:normal;word-spacing:0px;float:none;display:inline!important">Of c=
ourse this is true, but it&#39;s equally true that the people who want to u=
se v6 only can use a separate network. It&#39;s not clear why those of us w=
ho just want to get work done need to be inconvenienced in service of a pol=
itical point.</span></div></blockquote></div><br></span><div>It&#39;s not a=
 political point, Eric.</div></div></blockquote><div><br></div><div>We&#39;=
ll have to agree to differ, I suppose.</div><div>=C2=A0</div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex"><div style=3D"word-wrap:break-word"><div><br></div><div>Th=
e point is that we claim that we have produced something that will Just Wor=
k for the average user. =C2=A0 If you really think you can&#39;t &quot;get =
work done&quot; on an IPv6-only network with working and functional transit=
ion tech, <i>we have a problem.</i></div><div><br></div><div>So one of two =
things is true: you are right that such a network would not allow IETF atte=
ndees to &quot;get work done,&quot; or you are wrong. =C2=A0 It would be go=
od to know which of these is actually true. =C2=A0 This is the point of mak=
ing it the default: so that you have to opt out rather than opting in. =C2=
=A0 That way we can see how many people opt out, and maybe get some feedbac=
k as to why.</div></div></blockquote><div><br></div><div>In other words, yo=
u want to opt everyone into doing your testing for you. Again, that&#39;s n=
ot the purpose of the IETF network.</div><div><br></div><div>=C2=A0<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><div><=
/div><div>Honestly, it&#39;s really frustrating to me how prevalent this id=
ea is that getting things to work is someone else&#39;s problem. =C2=A0 You=
&#39;re the last person I would have expected to make this case. =C2=A0 Do =
you think that we should still be running TLS 1.1, and that trying to use T=
LS 1.3 when it becomes available would be a &quot;political&quot; choice? =
=C2=A0 That&#39;s essentially what you are arguing here, just in a differen=
t part of the stack.</div></div></blockquote><div><br></div><div>No, it&#39=
;s not. The right analogy would be filtering out TLS 1.3 at our network edg=
e, which you absolutely do not see me suggesting.</div><div><br></div><div>=
-Ekr</div><div><br></div><div>=C2=A0</div></div><br></div></div>

--f4030436885e9f32dd055578d3e3--


From nobody Sat Jul 29 16:17:42 2017
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13F16131687 for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 16:17:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.402
X-Spam-Level: 
X-Spam-Status: No, score=-2.402 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 GjmSbs5jKPfP for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 16:17:39 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB42E131467 for <ietf@ietf.org>; Sat, 29 Jul 2017 16:17:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 2BA35BE2D; Sun, 30 Jul 2017 00:17:35 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cxsou6qamW1w; Sun, 30 Jul 2017 00:17:33 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id BF8BCBE24; Sun, 30 Jul 2017 00:17:33 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1501370253; bh=oWnuxuc/F5qazxpr+ZYU+ywNREjHLT3VCoivYV2UGYE=; h=Subject:To:References:From:Date:In-Reply-To:From; b=PQO/UYwrLXAuZ50Xx19m7+suOGSNfT2JbVGLIMudCOw9slMs9kqXLCbrfjp8o21IU 7eOrQ1GCNrKQ4/J6WdHHZN/4iBaiPdLrhUGDQGSjc6W0VRrcMKSD5HVrnhxYufP/ZH JtUr+G1xuzK0VzlXacJgqGTJ/2ppqoxzokALjMcc=
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: Ted Lemon <mellon@fugue.com>, "ietf@ietf.org" <ietf@ietf.org>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <0CC96AE9-832A-47DB-96A9-5E5DF67B0BA3@vpnc.org> <CAPt1N1=8tUWLg03zj_uktUiDyb5f7f9BFmjknDn0H3HTqxEHpw@mail.gmail.com> <DF4FC2CA-DC21-468A-A9C3-D1048985E9EF@vpnc.org> <6366C6A1-8DAA-4B3A-A2E4-CBD22A4B3F38@fugue.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <f595d170-b540-a60a-bd93-6ff5abf1f246@cs.tcd.ie>
Date: Sun, 30 Jul 2017 00:17:32 +0100
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: <6366C6A1-8DAA-4B3A-A2E4-CBD22A4B3F38@fugue.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="lR31PMv76C9icXj03O7npoTAXiDuwq6tg"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VjieBICaLiC7kw4FIRedgm3nZHQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 23:17:41 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--lR31PMv76C9icXj03O7npoTAXiDuwq6tg
Content-Type: multipart/mixed; boundary="nbDcOOlxnDvLhOpI5nU1K2QTKFVcAer9B";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Ted Lemon <mellon@fugue.com>, "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <f595d170-b540-a60a-bd93-6ff5abf1f246@cs.tcd.ie>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF
 Meetings
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com>
 <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com>
 <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com>
 <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com>
 <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com>
 <0CC96AE9-832A-47DB-96A9-5E5DF67B0BA3@vpnc.org>
 <CAPt1N1=8tUWLg03zj_uktUiDyb5f7f9BFmjknDn0H3HTqxEHpw@mail.gmail.com>
 <DF4FC2CA-DC21-468A-A9C3-D1048985E9EF@vpnc.org>
 <6366C6A1-8DAA-4B3A-A2E4-CBD22A4B3F38@fugue.com>
In-Reply-To: <6366C6A1-8DAA-4B3A-A2E4-CBD22A4B3F38@fugue.com>

--nbDcOOlxnDvLhOpI5nU1K2QTKFVcAer9B
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: quoted-printable


Hi Ted,

On 29/07/17 17:54, Ted Lemon wrote:
> Right, so known_hosts is broken, because it remembers IP addresses.

I don't think that's likely to be a statement on which everyone agrees.

> This is something that ought to get fixed, not persisted.   Imagine
> how this feature interacts with the private service discovery feature
> that is being worked on in dnssd, when the host being connected to
> does IP address privacy.
>=20
> I want _you_ in particular to use IPv6+nat64 because it will show you
> where some of the implementations of software that you currently use
> are broken, and then (I hope) you will get on board with trying to
> get them fixed.   That's the value proposition.=20

See below, but I think value proposition is the wrong term above.

>  OpenVPN has known
> about their IPv6 brokenness for about four years, and they still
> haven't done anything about it.

I've used openvpn quite successfully in order to get IPv6 so I'm
not sure what brokenness you mean. (No, not for lots of traffic,
but it worked.)

>=20
>> One other note: if there were a perceived benefit for the folks=20
>> opting-in that'd help your cause I think. "You can help us all make
>> this better" is not a sufficiently direct benefit to attract that
>> many dogfood eaters IMO.

> Right, that's why the "opt out" rather than "opt in" proposal.
> We've had "opt in" since two Berlins ago, and we just don't get a lot
> of people trying the "opt in" network.   The value proposition is
> pretty obvious to me: we get to see how many people opt out.

I don't think you got what I meant. Being able to opt-in to fixing
other people's bugs is not a value proposition that'll resonate. And
being opted-in and having to opt-out will only generate rancour.

Last time, with DPRIVE I got my DNS queries encrypted for at least
one hop, so that's a win, albeit a very very minor win, even for people
who know about it and care.

Fixing other people's bugs is frankly not in itself motivating.
Even moreso if we don't agree on which behaviours are bugs or
features;-)

So my question to you was really "what gets better for me if I use
that SSID?" If the answer is "things get worse" then yes you will
continue to have issues attracting people to try it, and so long as
that remains the answer it'll never be ready to be the default.

So I think this is very far from sufficient to justify an opt-out.

Cheers,
S.



--nbDcOOlxnDvLhOpI5nU1K2QTKFVcAer9B--

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

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJZfReNAAoJEC88hzaAX42iKNMIAI+ie17QtH7ZX7sp1k0MldH9
9WUyu7+9565gPqwRJjpnc88d36w58eGmw+oYiiq1KwBL7CYlZcO8aZckudoqSZ51
OD+lOoLBebTXuamJtiAnGeczwR2dUZW/j/YiW4AHGAROPvVw6dYuqoVsSyYFQOOk
yFX1dKRqhX2wwInStScCdX+SxJcIRBPjx0xbp1rXSxxuu8nS50l811U6lesvPCe3
0yCXsqp+CnpexJuQdm6xYWmCZJeB4XogPQBRUWfdLFCI8dhm/aHrrfabux65T3KG
/h1DHBbNVe57ymHIPbkjSxg2YdZQHoS6sXYnfqAFb74Qkn+ELxONBEvi4DmIcT4=
=boGH
-----END PGP SIGNATURE-----

--lR31PMv76C9icXj03O7npoTAXiDuwq6tg--


From nobody Sat Jul 29 17:15:42 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8761131C33 for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 17:15:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.002
X-Spam-Level: 
X-Spam-Status: No, score=-5.002 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 OtJLaUFEHK1m for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 17:15:39 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 DC8461317AD for <ietf@ietf.org>; Sat, 29 Jul 2017 17:15:39 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dbbtP-0004RB-3Z; Sun, 30 Jul 2017 00:15:35 +0000
Date: Sun, 30 Jul 2017 09:15:32 +0900
Message-ID: <m2vamahja3.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
In-Reply-To: <f595d170-b540-a60a-bd93-6ff5abf1f246@cs.tcd.ie>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <0CC96AE9-832A-47DB-96A9-5E5DF67B0BA3@vpnc.org> <CAPt1N1=8tUWLg03zj_uktUiDyb5f7f9BFmjknDn0H3HTqxEHpw@mail.gmail.com> <DF4FC2CA-DC21-468A-A9C3-D1048985E9EF@vpnc.org> <6366C6A1-8DAA-4B3A-A2E4-CBD22A4B3F38@fugue.com> <f595d170-b540-a60a-bd93-6ff5abf1f246@cs.tcd.ie>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ExtQNRdB-80I_J2V4cW2ZQN_nOA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 00:15:41 -0000

> So my question to you was really "what gets better for me if I use
> that SSID?" If the answer is "things get worse" then yes you will
> continue to have issues attracting people to try it, and so long as
> that remains the answer it'll never be ready to be the default.

why not start with what we have traditionally done with new protocols
and implementations, the nat64 aficionados conduct interop testing with
an i-d reporting the result?  for example, in the s'pore hackathon, have
a group with an assortment of devices and a wide assortment of
applications actually testing nat64.  maybe kickstart with the nat64
tickets from {seoul,chicago,praha} if no other ideas come to mind.

randy


From nobody Sat Jul 29 18:16:39 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F67A131CD1 for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 18:16:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.7
X-Spam-Level: 
X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 niTLDe-5gXFw for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 18:16:35 -0700 (PDT)
Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::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 695CF126C83 for <ietf@ietf.org>; Sat, 29 Jul 2017 18:16:35 -0700 (PDT)
Received: by mail-qk0-x236.google.com with SMTP id a77so37217859qkb.0 for <ietf@ietf.org>; Sat, 29 Jul 2017 18:16:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=TAYeKmo4Hn5c+pT6n2egnufFOKLRWhOY+coN0jxYpn4=; b=t7Xupo829nYtNZErLKdSdggfMpsycAtOp6PatYyeoTAtlPbI5P9O/eckxUKYxpKuow fJ0/E5+QthAJrtvSPwAcsiClr8Mrhkp/VuGcbgMTtbqkPsfdr/yFgTGLLaUuhLlqs4mm qmvqUVVOL0iwivJG0lxI0AQEsQnGVxu2Mnj2cYqgEiVbzM69MaSrqzUAgWpVaZ4aUg/D u6w2tHct2qhfPIiI4CmWbPFfNp6IGNRP4j+2hGZrO0KxC8tYQja6V81spwvRFK1WF8rw 3/e9plmaki0pxlllQCFhQ4aKJv4LhpyqDZif96Rf4SbWE0n582k4A4ciZ7tiJLeHu/cU 1J+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=TAYeKmo4Hn5c+pT6n2egnufFOKLRWhOY+coN0jxYpn4=; b=XQRszn5wF3sw8p8GMyxMNsdCUuNJhG0JYBxnPHeorqR0dN3q3oQBYzXurCFIbZotwW 5Mx+te5MkEE8I/XtqmC322pbc3O5pABWJyrIBnBy11iKZ3j045mitmAuQRQ88d1nJk6E HvyiPmxPv1FxWaP29M6W67IwwuiPBKu8eD2xGWWBNwFdSs0UmMCNxkBHCwZ+J1UyQZpt z/9F9AnMlYVjiB7ySxExeNwua8hbWH+gwDEUJbbu6P1/8j47toAIc7oyrENqHo3Aek1h K7VhaOqGJCBPOQ6gnT01EhGO2r0h6C1qBJ27FPNzmMURIn7a1YTgLZw6CBVpbImRZyKN bMzw==
X-Gm-Message-State: AIVw110WZRnKW2YUfjG0rHPrjWm6IZWLyi2aIfw51VNp2wvC/jjeJPZ5 7PIKHJJw6ONwpwqkUNA73g==
X-Received: by 10.55.165.204 with SMTP id o195mr15214742qke.11.1501377394326;  Sat, 29 Jul 2017 18:16:34 -0700 (PDT)
Received: from [10.0.30.153] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id b15sm5312624qta.31.2017.07.29.18.16.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 29 Jul 2017 18:16:33 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <C5B6A27B-8AE1-4706-B2CB-A8AF20245EAF@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_17DEAA7E-F1B6-4277-A81C-541C8924169C"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Sat, 29 Jul 2017 21:16:31 -0400
In-Reply-To: <f595d170-b540-a60a-bd93-6ff5abf1f246@cs.tcd.ie>
Cc: "ietf@ietf.org" <ietf@ietf.org>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <0CC96AE9-832A-47DB-96A9-5E5DF67B0BA3@vpnc.org> <CAPt1N1=8tUWLg03zj_uktUiDyb5f7f9BFmjknDn0H3HTqxEHpw@mail.gmail.com> <DF4FC2CA-DC21-468A-A9C3-D1048985E9EF@vpnc.org> <6366C6A1-8DAA-4B3A-A2E4-CBD22A4B3F38@fugue.com> <f595d170-b540-a60a-bd93-6ff5abf1f246@cs.tcd.ie>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/63ghwTYdya-9XoknfotgVlon0kY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 01:16:38 -0000

--Apple-Mail=_17DEAA7E-F1B6-4277-A81C-541C8924169C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jul 29, 2017, at 7:17 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie> =
wrote:
> So my question to you was really "what gets better for me if I use
> that SSID?" If the answer is "things get worse" then yes you will
> continue to have issues attracting people to try it, and so long as
> that remains the answer it'll never be ready to be the default.

The IETF network is always going to have enough IPv4 addresses for every =
user.   Hence, it is _never_ going to be better for IETF users to use an =
IPv6-only network, because the main feature of IPv6 is end-to-end, and =
if you are still v4-privileged, you have end-to-end with v4, unlike the =
rest of the world.   So if that's the value proposition required to make =
v6-only the default, v6-only is not going to be the default until it =
becomes difficult to get clean v4 peering at IETF meetings.   That is, =
not anytime soon.

It looks like OpenVPN finally supported dual-stack servers with =
stack-agnostic clients roaming to v6-only networks as of 2.4/3.0.

OpenSSH shouldn't store IP addresses in known_hosts files because in the =
real world, 192.168.1.1 refers to a different host depending on what =
network I'm connected to.   So I wind up having to go in and delete =
these addresses from my known_hosts file on a regular basis.   It makes =
some sense to say that server.example.org <http://server.example.org/> =
should have a stable ssh key; it makes very little sense to say that =
some random IP address should have a stable key.

Best case, if the thing you're connecting to uses privacy addresses, =
you're going to have a key file with a _ton_ of stale keys; worse case, =
you're going to be in the habit of editing your known_hosts file to =
delete bogus keys when IP addresses get reused by different hosts.   I =
am probably more likely to encounter this than you because I build and =
test router firmware on a regular basis, but the principle is true in =
general.   If you think DNSSEC is a good idea, why aren't you getting =
your host key from DNSSEC?


--Apple-Mail=_17DEAA7E-F1B6-4277-A81C-541C8924169C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jul 29, 2017, at 7:17 PM, Stephen Farrell &lt;<a =
href=3D"mailto:stephen.farrell@cs.tcd.ie" =
class=3D"">stephen.farrell@cs.tcd.ie</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">So my question to you was really "what =
gets better for me if I use</span><br style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">that SSID?" If the =
answer is "things get worse" then yes you will</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">continue to have issues attracting people to try =
it, and so long as</span><br style=3D"font-family: Menlo-Regular; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">that remains the =
answer it'll never be ready to be the =
default.</span></div></blockquote></div><br class=3D""><div class=3D"">The=
 IETF network is always going to have enough IPv4 addresses for every =
user. &nbsp; Hence, it is _never_ going to be better for IETF users to =
use an IPv6-only network, because the main feature of IPv6 is =
end-to-end, and if you are still v4-privileged, you have end-to-end with =
v4, unlike the rest of the world. &nbsp; So if that's the value =
proposition required to make v6-only the default, v6-only is not going =
to be the default until it becomes difficult to get clean v4 peering at =
IETF meetings. &nbsp; That is, not anytime soon.</div><div class=3D""><br =
class=3D""></div><div class=3D"">It looks like OpenVPN finally supported =
dual-stack servers with stack-agnostic clients roaming to v6-only =
networks as of 2.4/3.0.</div><div class=3D""><br class=3D""></div><div =
class=3D"">OpenSSH shouldn't store IP addresses in known_hosts files =
because in the real world, 192.168.1.1 refers to a different host =
depending on what network I'm connected to. &nbsp; So I wind up having =
to go in and delete these addresses from my known_hosts file on a =
regular basis. &nbsp; It makes some sense to say that <a =
href=3D"http://server.example.org" =
class=3D"">server.example.org</a>&nbsp;should have a stable ssh key; it =
makes very little sense to say that some random IP address should have a =
stable key.</div><div class=3D""><br class=3D""></div><div class=3D"">Best=
 case, if the thing you're connecting to uses privacy addresses, you're =
going to have a key file with a _ton_ of stale keys; worse case, you're =
going to be in the habit of editing your known_hosts file to delete =
bogus keys when IP addresses get reused by different hosts. &nbsp; I am =
probably more likely to encounter this than you because I build and test =
router firmware on a regular basis, but the principle is true in =
general. &nbsp; If you think DNSSEC is a good idea, why aren't you =
getting your host key from DNSSEC?</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_17DEAA7E-F1B6-4277-A81C-541C8924169C--


From nobody Sat Jul 29 18:18:51 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 484B9131C9E for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 18:18:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.7
X-Spam-Level: 
X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 SoE2RTIGbbFw for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 18:18:49 -0700 (PDT)
Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::22c]) (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 D6036126C83 for <ietf@ietf.org>; Sat, 29 Jul 2017 18:18:48 -0700 (PDT)
Received: by mail-qk0-x22c.google.com with SMTP id z18so53363864qka.4 for <ietf@ietf.org>; Sat, 29 Jul 2017 18:18:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Z8to/g82IuwLjBfE/4rah84awNk8LXEie4EbgldeGAc=; b=eku2H26XdeSmlQyqbTNen1afmrUI4NciMHLoph54U/vKWDPVpjYhSdXhsbc3xawvqA 9N23n4AHyZlE2ZIhrvVJwp6Wo5yftVEP5m6VI7QjUvLmTo5xBdVyoZLjp54VA65TuxxM 4I0qxiYG5BlTfE335Akcq0hHsyTt/UvQPzDv/fILjGrDfLixwFMKWHtDYq3O9OSCtAPP juyCt57yqCNxrOc+WKna4VG9b+xonfYiuGvLt53PTyxPJgSXjr1fflG3XN7HEuqNuOiZ xCtodCefpnSD9LLxR3gdOtUtz2eBzFxTnhp5AQ1AujDAoLerIOG9b9XeUUKIis7ulzG4 Ei7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=Z8to/g82IuwLjBfE/4rah84awNk8LXEie4EbgldeGAc=; b=So4E1jgeFUXJ8d1sg5x2YeTMwJZJPvErRT7Y36fjjbjOka9p75YOAqycnVoMgUqLiX phsvJMBm0YFwbP/Hbn16ClNqvTiFD+SlIV33GmoIRJxuGVgE/ZsSN0Cy5N+a29epTUu3 2w8ZY8G/puslUkMOg3DkEVObUAm5ceXJWAZTGamCdTD/apBps+Xwlwi/xej7VIOKJGLo q0eEB0RgR4kRv/WOQDbnFy8XoULf0a1O+6077rd/F9hgQ5h17Y8a2a0IL+HCGjkWHXau JAwOfuZZC/5zSDMtdINwQ0NHQf0+i8TOMqOFpg9C12iEzmVgMhKLUD/LjVn/sc9SfR47 997A==
X-Gm-Message-State: AIVw112FnLc9NsXFUPbfMygTZ2W5Ja+vu1J6CN8wpkwZJ3+TktdgUsTB 7ljKdVRQqyDJheiaPQDUww==
X-Received: by 10.55.174.129 with SMTP id x123mr15335752qke.212.1501377527874;  Sat, 29 Jul 2017 18:18:47 -0700 (PDT)
Received: from [10.0.30.153] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id b71sm18093051qkj.8.2017.07.29.18.18.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 29 Jul 2017 18:18:47 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <AB8FE929-A69C-43DD-911D-0831BAAECAE3@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D9ABF843-3A2B-4998-9ACD-E92491C164F3"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Sat, 29 Jul 2017 21:18:45 -0400
In-Reply-To: <m2vamahja3.wl-randy@psg.com>
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, IETF Rinse Repeat <ietf@ietf.org>
To: Randy Bush <randy@psg.com>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <0CC96AE9-832A-47DB-96A9-5E5DF67B0BA3@vpnc.org> <CAPt1N1=8tUWLg03zj_uktUiDyb5f7f9BFmjknDn0H3HTqxEHpw@mail.gmail.com> <DF4FC2CA-DC21-468A-A9C3-D1048985E9EF@vpnc.org> <6366C6A1-8DAA-4B3A-A2E4-CBD22A4B3F38@fugue.com> <f595d170-b540-a60a-bd93-6ff5abf1f246@cs.tcd.ie> <m2vamahja3.wl-randy@psg.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UwIm7prCKcXRU-ka-ZJZJBCWV2I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 01:18:50 -0000

--Apple-Mail=_D9ABF843-3A2B-4998-9ACD-E92491C164F3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jul 29, 2017, at 8:15 PM, Randy Bush <randy@psg.com> wrote:
> maybe kickstart with the nat64
> tickets from {seoul,chicago,praha} if no other ideas come to mind.

I submitted a lot of tickets on nat64 in prague, but as far as I was =
able to tell they were all layer 1 propagation issues, not layer 3 =
issues.

If in fact there is a database of trouble report tickets that you think =
contains useful data, it would probably be a good idea to do something =
with that.  If we aren't doing that now, then as you say, there is not =
much point in making a V6-only+NAT64 network the default.


--Apple-Mail=_D9ABF843-3A2B-4998-9ACD-E92491C164F3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jul 29, 2017, at 8:15 PM, Randy Bush &lt;<a =
href=3D"mailto:randy@psg.com" class=3D"">randy@psg.com</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">maybe kickstart =
with the nat64</span><br style=3D"font-family: Menlo-Regular; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">tickets from {seoul,chicago,praha} if no =
other ideas come to mind.</span></div></blockquote></div><br =
class=3D""><div class=3D"">I submitted a lot of tickets on nat64 in =
prague, but as far as I was able to tell they were all layer 1 =
propagation issues, not layer 3 issues.</div><div class=3D""><br =
class=3D""></div><div class=3D"">If in fact there is a database of =
trouble report tickets that you think contains useful data, it would =
probably be a good idea to do something with that. &nbsp;If we aren't =
doing that now, then as you say, there is not much point in making a =
V6-only+NAT64 network the default.</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_D9ABF843-3A2B-4998-9ACD-E92491C164F3--


From nobody Sat Jul 29 18:33:54 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF31412EC3F for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 18:33:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.002
X-Spam-Level: 
X-Spam-Status: No, score=-5.002 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 EksYjq6s5-BR for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 18:33:51 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 68DE5126DD9 for <ietf@ietf.org>; Sat, 29 Jul 2017 18:33:51 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dbd77-000593-3O; Sun, 30 Jul 2017 01:33:49 +0000
Date: Sun, 30 Jul 2017 10:33:47 +0900
Message-ID: <m2h8xuzp1g.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ted Lemon <mellon@fugue.com>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
In-Reply-To: <AB8FE929-A69C-43DD-911D-0831BAAECAE3@fugue.com>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <0CC96AE9-832A-47DB-96A9-5E5DF67B0BA3@vpnc.org> <CAPt1N1=8tUWLg03zj_uktUiDyb5f7f9BFmjknDn0H3HTqxEHpw@mail.gmail.com> <DF4FC2CA-DC21-468A-A9C3-D1048985E9EF@vpnc.org> <6366C6A1-8DAA-4B3A-A2E4-CBD22A4B3F38@fugue.com> <f595d170-b540-a60a-bd93-6ff5abf1f246@cs.tcd.ie> <m2vamahja3.wl-randy@psg.com> <AB8FE929-A69C-43DD-911D-0831BAAECAE3@fugue.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7pfRHRgl-jk8mBVW7A5spClRB14>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 01:33:53 -0000

> I submitted a lot of tickets on nat64 in prague, but as far as I was
> able to tell they were all layer 1 propagation issues, not layer 3
> issues.

as ietf-nat64 is just yet another ssid on the same meeting area access
points as the other ssids (bar ietf-hotel), i doubt this is at all
unique to nat64 layer-1/2 propagation.

the only ietf99 ticket i can find from mellon@fugue.com is
https://tickets.meeting.ietf.org/ticket/1138, which sounds to be what
you describe above.  asai san looked at it, responded, asked you to
retest, you did not respond, so the ticket was closed.

> If in fact there is a database of trouble report tickets that you
> think contains useful data, it would probably be a good idea to do
> something with that.

lucy, ietf noc ticket goddess, tried to copy all 99 nat64 tickets into a
bunch, see
https://tickets.meeting.ietf.org/query?status=accepted&status=assigned&status=closed&status=new&status=reopened&component=nat64&milestone=ietf-99&group=milestone&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&order=priority&report=10

collecting from < 99 could probably be done.  but no sense spending noc
volunteers' time on it until you're actually organized to actually do
something useful with the info.

randy


From nobody Sat Jul 29 18:34:57 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F133C131E0D for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 18:34:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 qrTDNmYhEi5r for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 18:34:54 -0700 (PDT)
Received: from mail-pf0-x234.google.com (mail-pf0-x234.google.com [IPv6:2607:f8b0:400e:c00::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 51DD7131E01 for <ietf@ietf.org>; Sat, 29 Jul 2017 18:34:54 -0700 (PDT)
Received: by mail-pf0-x234.google.com with SMTP id d67so40534645pfc.0 for <ietf@ietf.org>; Sat, 29 Jul 2017 18:34:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=yiUfibAAEBuT11qv0Em6XH9BkJSCP/8KnFZuScrWvys=; b=ErHDLFveCr24akEZhf+dwLDr1s2A50QauSNdzfYGp8h9Tozc4GyestK93A3lttLA50 5s2rj5SDJwDui6G/vrSYlsrqfpQc4TiW7QloeuNmikG4MMfQ2WyTzehMVQ1CyMZzk4Tk T4l28wrgZhsR3WypvUO0yF+yk9VReE3DWZ/t4EPcHM1kLDdy6X2CFOUU0T+BpTCB5flH faL/AwMKlTmcQzlVMUqMnggSoqwTaAc1+uRphm91nAPlGHdjiXlCoZeGq5qjxZNMVUcw QtvKbkq9rk/xkXPtAcTFuYmOkAD/u2WArjGONoiFnyMt4HNRVBWV0bfYb9lgPJ5akir3 G0Vw==
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=yiUfibAAEBuT11qv0Em6XH9BkJSCP/8KnFZuScrWvys=; b=dbPPbMN+ZhFusykjb/8jFfcXU/zWzPxvWyeZP+7IPwdp02QlWSuDLLbeiC+Pne2HWd 6qMb3v39E3gAyXj4LvaM1dSgo8mTjlhxvqUVyqmX6tHuV72eJEpA0uSFJTrm03W48dE1 boiHIAg3bL/u6sAIysnrWTcvKifvm1K4xmUgBgPMwm8Qlt7UoZxkN7PxsqEd2PxGCvFV TYxpIZQnQvQL+q2iEk25D/r/FONycyyBgtMpahVE17KcBtBsRJ/JerWmrVtpNumUlx4P lmE57VdsTF2jCMwk/epy9RxXeOYXzMCxcvav0r9oPd8V0vMTdIQx4EzFA6AP4SOyfBNu B0wg==
X-Gm-Message-State: AIVw113yg4ZwG6RCSiWmNyv4hvPsiwgzCykL3sLAMeliz1wjwE1Oo8uX f83jwng1+Pr7LSHbOE28XzkrfrffRumD
X-Received: by 10.99.97.204 with SMTP id v195mr11299481pgb.422.1501378493864;  Sat, 29 Jul 2017 18:34:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.180.131 with HTTP; Sat, 29 Jul 2017 18:34:53 -0700 (PDT)
Received: by 10.100.180.131 with HTTP; Sat, 29 Jul 2017 18:34:53 -0700 (PDT)
In-Reply-To: <m2h8xuzp1g.wl-randy@psg.com>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <0CC96AE9-832A-47DB-96A9-5E5DF67B0BA3@vpnc.org> <CAPt1N1=8tUWLg03zj_uktUiDyb5f7f9BFmjknDn0H3HTqxEHpw@mail.gmail.com> <DF4FC2CA-DC21-468A-A9C3-D1048985E9EF@vpnc.org> <6366C6A1-8DAA-4B3A-A2E4-CBD22A4B3F38@fugue.com> <f595d170-b540-a60a-bd93-6ff5abf1f246@cs.tcd.ie> <m2vamahja3.wl-randy@psg.com> <AB8FE929-A69C-43DD-911D-0831BAAECAE3@fugue.com> <m2h8xuzp1g.wl-randy@psg.com>
From: Ted Lemon <mellon@fugue.com>
Date: Sat, 29 Jul 2017 21:34:53 -0400
Message-ID: <CAPt1N1k9arzDrAHP0qO7jEr+kXvtSWNy4qFyZg45kkdFnOCsJg@mail.gmail.com>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: Randy Bush <randy@psg.com>
Cc: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c08b438ccf31905557eebe1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yTn6PS28uAe3ecHcOvpvDS7cnRI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 01:34:56 -0000

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

Ok, I'll check it out.   Thanks for the pointer.

On Jul 29, 2017 9:33 PM, "Randy Bush" <randy@psg.com> wrote:

> > I submitted a lot of tickets on nat64 in prague, but as far as I was
> > able to tell they were all layer 1 propagation issues, not layer 3
> > issues.
>
> as ietf-nat64 is just yet another ssid on the same meeting area access
> points as the other ssids (bar ietf-hotel), i doubt this is at all
> unique to nat64 layer-1/2 propagation.
>
> the only ietf99 ticket i can find from mellon@fugue.com is
> https://tickets.meeting.ietf.org/ticket/1138, which sounds to be what
> you describe above.  asai san looked at it, responded, asked you to
> retest, you did not respond, so the ticket was closed.
>
> > If in fact there is a database of trouble report tickets that you
> > think contains useful data, it would probably be a good idea to do
> > something with that.
>
> lucy, ietf noc ticket goddess, tried to copy all 99 nat64 tickets into a
> bunch, see
> https://tickets.meeting.ietf.org/query?status=accepted&
> status=assigned&status=closed&status=new&status=reopened&
> component=nat64&milestone=ietf-99&group=milestone&col=
> id&col=summary&col=status&col=type&col=priority&col=
> milestone&col=component&order=priority&report=10
>
> collecting from < 99 could probably be done.  but no sense spending noc
> volunteers' time on it until you're actually organized to actually do
> something useful with the info.
>
> randy
>

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

<div dir=3D"auto">Ok, I&#39;ll check it out. =C2=A0 Thanks for the pointer.=
=C2=A0</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Ju=
l 29, 2017 9:33 PM, &quot;Randy Bush&quot; &lt;<a href=3D"mailto:randy@psg.=
com">randy@psg.com</a>&gt; wrote:<br type=3D"attribution"><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">&gt; I submitted a lot of tickets on nat64 in prague, but as =
far as I was<br>
&gt; able to tell they were all layer 1 propagation issues, not layer 3<br>
&gt; issues.<br>
<br>
as ietf-nat64 is just yet another ssid on the same meeting area access<br>
points as the other ssids (bar ietf-hotel), i doubt this is at all<br>
unique to nat64 layer-1/2 propagation.<br>
<br>
the only ietf99 ticket i can find from <a href=3D"mailto:mellon@fugue.com">=
mellon@fugue.com</a> is<br>
<a href=3D"https://tickets.meeting.ietf.org/ticket/1138" rel=3D"noreferrer"=
 target=3D"_blank">https://tickets.meeting.ietf.<wbr>org/ticket/1138</a>, w=
hich sounds to be what<br>
you describe above.=C2=A0 asai san looked at it, responded, asked you to<br=
>
retest, you did not respond, so the ticket was closed.<br>
<br>
&gt; If in fact there is a database of trouble report tickets that you<br>
&gt; think contains useful data, it would probably be a good idea to do<br>
&gt; something with that.<br>
<br>
lucy, ietf noc ticket goddess, tried to copy all 99 nat64 tickets into a<br=
>
bunch, see<br>
<a href=3D"https://tickets.meeting.ietf.org/query?status=3Daccepted&amp;sta=
tus=3Dassigned&amp;status=3Dclosed&amp;status=3Dnew&amp;status=3Dreopened&a=
mp;component=3Dnat64&amp;milestone=3Dietf-99&amp;group=3Dmilestone&amp;col=
=3Did&amp;col=3Dsummary&amp;col=3Dstatus&amp;col=3Dtype&amp;col=3Dpriority&=
amp;col=3Dmilestone&amp;col=3Dcomponent&amp;order=3Dpriority&amp;report=3D1=
0" rel=3D"noreferrer" target=3D"_blank">https://tickets.meeting.ietf.<wbr>o=
rg/query?status=3Daccepted&amp;<wbr>status=3Dassigned&amp;status=3Dclosed&a=
mp;<wbr>status=3Dnew&amp;status=3Dreopened&amp;<wbr>component=3Dnat64&amp;m=
ilestone=3D<wbr>ietf-99&amp;group=3Dmilestone&amp;col=3D<wbr>id&amp;col=3Ds=
ummary&amp;col=3Dstatus&amp;col=3D<wbr>type&amp;col=3Dpriority&amp;col=3D<w=
br>milestone&amp;col=3Dcomponent&amp;order=3D<wbr>priority&amp;report=3D10<=
/a><br>
<br>
collecting from &lt; 99 could probably be done.=C2=A0 but no sense spending=
 noc<br>
volunteers&#39; time on it until you&#39;re actually organized to actually =
do<br>
something useful with the info.<br>
<br>
randy<br>
</blockquote></div></div>

--94eb2c08b438ccf31905557eebe1--


From nobody Sat Jul 29 19:45:38 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33DFB131E8E for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 19:45:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.002
X-Spam-Level: 
X-Spam-Status: No, score=-5.002 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 b5HR9-5zDA8G for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 19:45:34 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 BC582131E8C for <ietf@ietf.org>; Sat, 29 Jul 2017 19:45:34 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dbeEV-0005iF-0x; Sun, 30 Jul 2017 02:45:32 +0000
Date: Sun, 30 Jul 2017 11:45:29 +0900
Message-ID: <m27eyqzlpy.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ted Lemon <mellon@fugue.com>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
In-Reply-To: <C5B6A27B-8AE1-4706-B2CB-A8AF20245EAF@fugue.com>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <0CC96AE9-832A-47DB-96A9-5E5DF67B0BA3@vpnc.org> <CAPt1N1=8tUWLg03zj_uktUiDyb5f7f9BFmjknDn0H3HTqxEHpw@mail.gmail.com> <DF4FC2CA-DC21-468A-A9C3-D1048985E9EF@vpnc.org> <6366C6A1-8DAA-4B3A-A2E4-CBD22A4B3F38@fugue.com> <f595d170-b540-a60a-bd93-6ff5abf1f246@cs.tcd.ie> <C5B6A27B-8AE1-4706-B2CB-A8AF20245EAF@fugue.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TjhAlJMegH1FooXKNSgcKsYUxR0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 02:45:36 -0000

[ btw, the $subject is broken.  the ipv6only ssid is global ipv6 not
  nat64, which has its own ssid ]
 
> The IETF network is always going to have enough IPv4 addresses for
> every user.  Hence, it is _never_ going to be better for IETF users to
> use an IPv6-only network

as/if the global net becomes mostly v6, this will change.  or so we
hope.

> because the main feature of IPv6 is end-to-end

i suspect most folk believe the main feature is gaurab's dictum, "96
more bits, no magic."

and i suspect that ipv6 will be about as e2e as ipv4; maybe less so if
things such as nat64 are the transition rather than dual stack.  (yes,
dual stack is not realistic given 2^32 is a bit less than 2^128 or even
2^64 or whatever.  get in your time machine and tell that to the ipv6
architects back in 1990.)

> if you are still v4-privileged, you have end-to-end with v4, unlike
> the rest of the world.

perhaps have a look & listen to philipp's talk at irtfopen99
https://youtu.be/JRneMj7LX8U?list=PLC86T-6ZTP5jdbiwi5ggLNnwLn1-r0M4h&t=637
it's a cgn tragedy out there, especially in mobile which rules most of
the world.

it would be interesting to know/measure what proportion of connections
are actually e2e on v4 and v6.  and i am not interested in measures on
facebook, google, root servers, etc.  i am a backbone kinda guy.  the
ipv6 statistic that finally impressed me was when the seattle internet
exchange (about the 20th largest ix) crossed 10% ipv6 last month.

but what we can affect is what we do in the ietf.  and there are a whole
lot of our siblings deliberately breaking e2e.

randy


From nobody Sat Jul 29 22:36:30 2017
Return-Path: <swmike@swm.pp.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4238D126C23 for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 22:36:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level: 
X-Spam-Status: No, score=-4.302 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_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 YejHr7pTpF2Y for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 22:36:27 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (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 D5F381267BB for <ietf@ietf.org>; Sat, 29 Jul 2017 22:36:26 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 68F8EA3; Sun, 30 Jul 2017 07:36:23 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1501392983; bh=ykG8LVLmQGLCav9nbwGOlE16EqBAM14solGA4eeCdZ0=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=1fJuAl28+4fv4UY8Ulf1tEJhfx0Ay7wdDteIQ+hHfbJRQXC978i2+/JSR7q3VeeU+ /rJDqKzA1baXdpAuVS/MklF2AZRgtX86yT2wcvmznYpnc5Y3855IwjoZfpnOtg1NuW 4C4Zcf3pfqjTwX07yqmxmYTFcBZbxa3xTVpzEWtU=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 4EF2AA1; Sun, 30 Jul 2017 07:36:23 +0200 (CEST)
Date: Sun, 30 Jul 2017 07:36:23 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Randy Bush <randy@psg.com>
cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
In-Reply-To: <m2y3r7gmb9.wl-randy@psg.com>
Message-ID: <alpine.DEB.2.02.1707300726150.29742@uplift.swm.pp.se>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <m2y3r7gmb9.wl-randy@psg.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zqqadNu_BBaA_ht9-ibH-siFgc8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 05:36:29 -0000

On Sun, 30 Jul 2017, Randy Bush wrote:

>> The point is that we claim that we have produced something that will
>> Just Work for the average user.  If you really think you can't "get
>> work done" on an IPv6-only network with working and functional
>> transition tech, we have a problem.
>
> bingo!  you are right.  we have a problem.  nat64/dns64 breaks things
> people use.  this is known, documented, and extremely annoying this many
> years out [0].
>
> the question is how to progress fixing nat64/dns64, given that a lot of
> folk come to ietf meetings to simply get work done and not debug a semi-
> working transport.  how about a bug bounty?  and maybe a fix bounty a
> few times larger!

There is nothing inherently broken with NAT64+DNS64+CLAT (or something 
like iOS has with bump-in-the-API).

Android has CLAT. iOS has its bump-in-the-API.

Win10 doesn't have any of this (the adviced CLAT is on WWAN only and 
mobile only). MacOS has bump-in-the-API for devices that use those APIs, 
which a lot doesn't. Anything uses the socket API doesn't get this. Linux 
doesn't have this out of the box afaik.

So there is nothing to be fixed for NAT64+DNS64, what needs to be fixed is 
that these operating systems need to support v4 literals through NAT64 by 
some kind of mechanism. Android does. iOS does. Nothing else does.

This is already well known. This "experiment" being proposed is in my mind 
useless because the outcome is already known. I connected a Win10 box to 
my NAT64+DNS64 experimental network two days ago to re-verify, and there 
were plenty of things that didn't work. Windows update doesn't think it's 
connected to the Internet. Steam won't even start.

Or is the objective of the experiment to have people from the operating 
system vendors discover that their operating systems has problems and that 
this discovery would make them fix these problems?

I emailed people at Microsoft about my 464XLAT findings. That resulted in 
me being told that the blog post would be updated and that a discussion 
would be had regarding that 464XLAT functionality perhaps coming to more 
generic use cases. I have already told people from Apples networking stack 
development team about my problems with NAT64+DNS64 and my VMs and also 
things using the socket API.

It seems a lot easier to just reach out to the OS vendors and tell them, 
than to try to use the painful detour of showing already known breakage on 
the IETF wifi for everybody to discover, most of who can do nothing about 
it.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Sun Jul 30 00:45:46 2017
Return-Path: <prvs=13848a67b3=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9436129AF6 for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 00:45:44 -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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
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 JFeXctnsxPEW for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 00:45:42 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 893FE129AD3 for <ietf@ietf.org>; Sun, 30 Jul 2017 00:45:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1501400740; x=1502005540; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=kjmo8qNt98Uu/RX1WENFsY6k3 jDddfj5LW76F8Bdj6o=; b=D+GffhugQ7RAQy1deQOY2cskRsshL9QOTdm6p8mL5 Alax8bkyj+xSAggr3t81+q54okgdY1M4kxUDyZCbVeY0qV9GaVdasHAH+ApGPmLL ilYeuN5elpBn9CoQC4D3c9M0ojAW8Dl2lCtSOuC+8OuE4nKT/w2qvrg4/whdHIdZ 80=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=LyRK7SdCTxy7t9aNQcMvS9NiP7iytQexHXV5K2j+e8nqxGmYOZywr/sHzR6f EuQnlcoO4rEbs5+770Qt0Z+ffxj/Dfxre34ZkiPfmEGZKhy9Vshv6k31Y etJpsDnY+UiElfsFgneZc+KvqdyGbaQuVk15zuYL/BELnnurnIXo1w=;
X-MDAV-Processed: mail.consulintel.es, Sun, 30 Jul 2017 09:45:40 +0200
X-Spam-Processed: mail.consulintel.es, Sun, 30 Jul 2017 09:45:39 +0200
Received: from [10.10.10.133] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005490233.msg for <ietf@ietf.org>; Sun, 30 Jul 2017 09:45:38 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170730:md50005490233::KP5D3SUBkkg1VB9P:000031ls
X-Return-Path: prvs=13848a67b3=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.24.1.170721
Date: Sun, 30 Jul 2017 09:45:38 +0200
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IETF Rinse Repeat <ietf@ietf.org>
Message-ID: <5FB50770-D61B-4398-AFE4-C64D0041FB46@consulintel.es>
Thread-Topic: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <m2y3r7gmb9.wl-randy@psg.com> <alpine.DEB.2.02.1707300726150.29742@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1707300726150.29742@uplift.swm.pp.se>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LAoAgVYRDStnCA5W2LbUIsnykTc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 07:45:45 -0000

So, looks like I=E2=80=99m not alone believing that instead of just NAT64+D=
NS64 what we actually need is what will solve the problem in the *real worl=
d*, which is CLAT in the LAN networks:

1) Having the IETF SSID with CLAT (as I=E2=80=99m suggesting that the =E2=
=80=9CIPv6-only=E2=80=9D CPEs =E2=80=93 in the sense of IPv6-only-WAN, must=
 support CLAT)
2) Having the hosts supporting CLAT as well, because bump-in-the-API doesn=
=E2=80=99t work for many apps that uses literals and don=E2=80=99t use the =
APIs. This is needed for tablets, laptops and cellular, because they can be=
 used in a network behind a device offering tethering, otherwise 1 above wi=
ll be enough.

And yes, in an ideal world, app developers/vendors will make sure to avoid =
using literals, and we don=E2=80=99t need to be the police+baby sitters, no=
t counting the problem of old devices/apps that are no longer in the market=
 and nobody will be able to take care of those. So again, best solution is =
1+2.

Human nature has proven that we only reported 5-6 tickets, because human na=
ture, when time is previous, during the meeting, will make that folks (incl=
uding myself as my email wat not working on the NAT64 network), which detec=
t a single =E2=80=9Ccritical=E2=80=9D failure (for them), move back to the =
dual-stack SSID (and only maybe report it).

I suggested having a small development to detect those apps automatically i=
f we have a CLAT in the default SSID with the NAT64-DNS64. Yes, we will hav=
e no public IPv4 addresses, but at least we don=E2=80=99t break apps, so th=
e people don=E2=80=99t need to move to the regular dual stack network (unle=
ss they need a public IP, which I=E2=80=99m not sure if it is common becaus=
e in real-world you typically don=E2=80=99t have it). The next hackathon ma=
y be an opportunity to do that if we don=E2=80=99t find somebody before in =
the open source community to work on that. We may start with a simple VM wi=
th Jool, which is a powerful open source implementation for NAT64, SIIT, CL=
AT, etc. and have something that =E2=80=9Cincrease=E2=80=9D the log level t=
o what we need. Even if it is not perfect, even if we only detect 20-30% of=
 the broken apps (which will be all those using the CLAT, and I think will =
be more than this %, just being pessimistic), it will be much more than wha=
t we detect AND report =E2=80=9Cmanually=E2=80=9D.

We still have the issue of who takes the responsibility to inform the broke=
n apps developers/vendors and track them to make sure it gets corrected =E2=
=80=A6

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Mikael Abrahamsson <swmike@sw=
m.pp.se>
Organizaci=C3=B3n: People's Front Against WWW
Responder a: <swmike@swm.pp.se>
Fecha: domingo, 30 de julio de 2017, 7:36
Para: Randy Bush <randy@psg.com>
CC: IETF Rinse Repeat <ietf@ietf.org>
Asunto: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF =
Meetings

    On Sun, 30 Jul 2017, Randy Bush wrote:
   =20
    >> The point is that we claim that we have produced something that will
    >> Just Work for the average user.  If you really think you can't "get
    >> work done" on an IPv6-only network with working and functional
    >> transition tech, we have a problem.
    >
    > bingo!  you are right.  we have a problem.  nat64/dns64 breaks things
    > people use.  this is known, documented, and extremely annoying this m=
any
    > years out [0].
    >
    > the question is how to progress fixing nat64/dns64, given that a lot =
of
    > folk come to ietf meetings to simply get work done and not debug a se=
mi-
    > working transport.  how about a bug bounty?  and maybe a fix bounty a
    > few times larger!
   =20
    There is nothing inherently broken with NAT64+DNS64+CLAT (or something=
=20
    like iOS has with bump-in-the-API).
   =20
    Android has CLAT. iOS has its bump-in-the-API.
   =20
    Win10 doesn't have any of this (the adviced CLAT is on WWAN only and=20
    mobile only). MacOS has bump-in-the-API for devices that use those APIs=
,=20
    which a lot doesn't. Anything uses the socket API doesn't get this. Lin=
ux=20
    doesn't have this out of the box afaik.
   =20
    So there is nothing to be fixed for NAT64+DNS64, what needs to be fixed=
 is=20
    that these operating systems need to support v4 literals through NAT64 =
by=20
    some kind of mechanism. Android does. iOS does. Nothing else does.
   =20
    This is already well known. This "experiment" being proposed is in my m=
ind=20
    useless because the outcome is already known. I connected a Win10 box t=
o=20
    my NAT64+DNS64 experimental network two days ago to re-verify, and ther=
e=20
    were plenty of things that didn't work. Windows update doesn't think it=
's=20
    connected to the Internet. Steam won't even start.
   =20
    Or is the objective of the experiment to have people from the operating=
=20
    system vendors discover that their operating systems has problems and t=
hat=20
    this discovery would make them fix these problems?
   =20
    I emailed people at Microsoft about my 464XLAT findings. That resulted =
in=20
    me being told that the blog post would be updated and that a discussion=
=20
    would be had regarding that 464XLAT functionality perhaps coming to mor=
e=20
    generic use cases. I have already told people from Apples networking st=
ack=20
    development team about my problems with NAT64+DNS64 and my VMs and also=
=20
    things using the socket API.
   =20
    It seems a lot easier to just reach out to the OS vendors and tell them=
,=20
    than to try to use the painful detour of showing already known breakage=
 on=20
    the IETF wifi for everybody to discover, most of who can do nothing abo=
ut=20
    it.
   =20
    --=20
    Mikael Abrahamsson    email: swmike@swm.pp.se
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Sun Jul 30 03:07:20 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82B01126BF3 for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 03:07:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 OEz7IHjAW6aD for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 03:07:18 -0700 (PDT)
Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (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 00D56120227 for <ietf@ietf.org>; Sun, 30 Jul 2017 03:07:17 -0700 (PDT)
Received: by mail-qt0-x22c.google.com with SMTP id t37so100638044qtg.5 for <ietf@ietf.org>; Sun, 30 Jul 2017 03:07:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=oe4kLEEBy5yXDA7lIR25GrIh0hNW3mvET39aYz8ygP4=; b=rupoooTWNA1GaqpaJhbbUs2CS6rBiwNo9E2NXepTbercc87bjZIc/5ag9ALk38y5m6 mbtWErxqnTcMiVTOeoLxAbGYUYCHBf2n5bIMtst2MgSEk9xMk5eMFkxMtIk4gy69enHz OEeuOBv8fSD7Xi48HFslPkz9QrU3RUVuCe9PRXJCYJwevD0bcXSgQamW7qTNf0NtxOuU OKVhUVMyvl8cHmZu7RoKV2OfxDSVqePy/O27/IZFhW86+xDBH4Ebs7iRTCuz72CCSiIv /hFrZY1Iw9HgOPtlv9zlLOWNdJ/uxl01nWFhh9D2LEnjlu0mDr0HQVTKqrAGqEnrMpK2 Aayw==
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=oe4kLEEBy5yXDA7lIR25GrIh0hNW3mvET39aYz8ygP4=; b=cDZPATu3hWFSUNJ8MTyXCoA9HvkzzIvYhOmmYynxnKWjrkrv2kF7jMcT4L1ZQ64PVk bBA3h9nqdK0vEwoArfYVfz/El+Eg6wwBYcMpKkWgx16G6tfimYPzAVl2wriXrT5nViXi luRaibLHGKX5URoq0xTyOVc1S7GJPAorUg6ZogveZhmXFoOz/6eDOfTPrhPsSnq+puEw qmmNqVKQyEV4uAWajOqbjy06oSFCUlIL//ZU6QORC2s2nbsGj8dyPrnSaisRz7cRbLKS qHdCVgoP7Bel4Chhuzsm1Rw5tbysyLbEF+24HGwCZaEgTUpiILT6YG94STek5WmrqHlp x7Vw==
X-Gm-Message-State: AIVw110MYktF/nLw+5EKiCy1imSL/3xyJtm3g08CFi71s8tOb+i3qbkk +OnuHKwAGUBdZ0yx0Ke3XA==
X-Received: by 10.200.52.235 with SMTP id x40mr16735797qtb.70.1501409236692; Sun, 30 Jul 2017 03:07:16 -0700 (PDT)
Received: from [10.1.23.114] (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id k97sm19831504qkh.29.2017.07.30.03.07.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 30 Jul 2017 03:07:15 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
From: Ted Lemon <mellon@fugue.com>
X-Mailer: iPad Mail (15A5327g)
In-Reply-To: <m2h8xuzp1g.wl-randy@psg.com>
Date: Sun, 30 Jul 2017 06:07:14 -0400
Cc: IETF Rinse Repeat <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C52C3BB8-C84D-46A5-9904-7E44750F8744@fugue.com>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <0CC96AE9-832A-47DB-96A9-5E5DF67B0BA3@vpnc.org> <CAPt1N1=8tUWLg03zj_uktUiDyb5f7f9BFmjknDn0H3HTqxEHpw@mail.gmail.com> <DF4FC2CA-DC21-468A-A9C3-D1048985E9EF@vpnc.org> <6366C6A1-8DAA-4B3A-A2E4-CBD22A4B3F38@fugue.com> <f595d170-b540-a60a-bd93-6ff5abf1f246@cs.tcd.ie> <m2vamahja3.wl-randy@psg.com> <AB8FE929-A69C-43DD-911D-0831BAAECAE3@fugue.com> <m2h8xuzp1g.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qKvdyDUpbC-J8sifwAsvaphgsFM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 10:07:19 -0000

On Jul 29, 2017, at 9:33 PM, Randy Bush <randy@psg.com> wrote:
> lucy, ietf noc ticket goddess, tried to copy all 99 nat64 tickets into a
> bunch, see

I read this as 99 tickets, but it=E2=80=99s only six. So not really a very s=
ubstantial data set. :(=


From nobody Sun Jul 30 03:21:21 2017
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB8A8131F08 for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 03:21:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
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 UKH7Cm54HOTD for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 03:21:18 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99315126BF3 for <ietf@ietf.org>; Sun, 30 Jul 2017 03:21:18 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6UAKtC7001143; Sun, 30 Jul 2017 11:20:55 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v6UAKtC7001143
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1501410061; bh=ZsJKhHxmE4feWn0AUCMsdW5f0/g=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=xDWnb1IvAuxU7l41MBhGcZkB7q/ScOHsGCr8w1oQYTqtePXhV33A3bsK+X2XOi8dA cHNe9Dh2Uguh8mW6l1mz1auEcA0+bOZGgStBnspP4VDAFc2IOTWQ6EBIeNVmcifVZM 54hI4zVteWJwO3y0X3T3XXZ1JnNz5WsvOSsEgtik=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id y6YBKo1235802948QK ret-id none; Sun, 30 Jul 2017 11:21:00 +0100
Received: from 20010a88d51011.ipv6.customer.clara.net (20010a88d51011.ipv6.customer.clara.net [IPv6:2001:a88:d510:1101:3d25:de87:64aa:5fc9] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6UAKjSo006218 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 30 Jul 2017 11:20:45 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <C52C3BB8-C84D-46A5-9904-7E44750F8744@fugue.com>
Date: Sun, 30 Jul 2017 11:20:44 +0100
Cc: IETF Rinse Repeat <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|a840160da2fae312689377f3dbb5c924y6YBKo03tjc|ecs.soton.ac.uk|4BCED8BC-00CD-432B-9E61-1FCD438DA8EC@ecs.soton.ac.uk>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <0CC96AE9-832A-47DB-96A9-5E5DF67B0BA3@vpnc.org> <CAPt1N1=8tUWLg03zj_uktUiDyb5f7f9BFmjknDn0H3HTqxEHpw@mail.gmail.com> <DF4FC2CA-DC21-468A-A9C3-D1048985E9EF@vpnc.org> <6366C6A1-8DAA-4B3A-A2E4-CBD22A4B3F38@fugue.com> <f595d170-b540-a60a-bd93-6ff5abf1f246@cs.tcd.ie> <m2vamahja3.wl-randy@psg.com> <AB8FE929-A69C-43DD-911D-0831BAAECAE3@fugue.com> <m2h8xuzp1g.wl-randy@psg.com> <C52C3BB8-C84D-46A5-9904-7E44750F8744@fugue.com> <4BCED8BC-00CD-432B-9E61-1FCD438DA8EC@ecs.soton.ac.uk>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3273)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=y6YBKo123580294800; tid=y6YBKo1235802948QK; client=relay,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v6UAKtC7001143
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/itdMM-yk3GGmTwNxXhl-sPIBwvw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 10:21:21 -0000

> On 30 Jul 2017, at 11:07, Ted Lemon <mellon@fugue.com> wrote:
>=20
> On Jul 29, 2017, at 9:33 PM, Randy Bush <randy@psg.com> wrote:
>> lucy, ietf noc ticket goddess, tried to copy all 99 nat64 tickets =
into a
>> bunch, see
>=20
> I read this as 99 tickets, but it=E2=80=99s only six. So not really a =
very substantial data set. :(

6 tickets from how many users?

It=E2=80=99s great that Randy has pulled together the nat64-realted =
tickets.

Could we also run a short survey on the attendees list after the event, =
using the IETF survey monkey or whatever the meeting survey uses, on =
nat64 experiences for this who used it?

We could then for example use the NOC and survey data to keep a running =
I-D of issues that=E2=80=99s updated after each meeting?

Tim=


From nobody Sun Jul 30 03:26:03 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB6F0131F08 for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 03:26:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 fSKQK51veLyu for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 03:26:00 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 AF645126BF3 for <ietf@ietf.org>; Sun, 30 Jul 2017 03:26:00 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dblQ6-0001Bb-T8; Sun, 30 Jul 2017 10:25:59 +0000
Date: Sun, 30 Jul 2017 19:25:57 +0900
Message-ID: <m2tw1uxlu2.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ted Lemon <mellon@fugue.com>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
In-Reply-To: <C52C3BB8-C84D-46A5-9904-7E44750F8744@fugue.com>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <0CC96AE9-832A-47DB-96A9-5E5DF67B0BA3@vpnc.org> <CAPt1N1=8tUWLg03zj_uktUiDyb5f7f9BFmjknDn0H3HTqxEHpw@mail.gmail.com> <DF4FC2CA-DC21-468A-A9C3-D1048985E9EF@vpnc.org> <6366C6A1-8DAA-4B3A-A2E4-CBD22A4B3F38@fugue.com> <f595d170-b540-a60a-bd93-6ff5abf1f246@cs.tcd.ie> <m2vamahja3.wl-randy@psg.com> <AB8FE929-A69C-43DD-911D-0831BAAECAE3@fugue.com> <m2h8xuzp1g.wl-randy@psg.com> <C52C3BB8-C84D-46A5-9904-7E44750F8744@fugue.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=ISO-8859-7
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/S4ZrZI9hEjWVRtGTAk7gHrhv9xI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 10:26:02 -0000

>> lucy, ietf noc ticket goddess, tried to copy all 99 nat64 tickets
>> into a bunch, see
> I read this as 99 tickets, but it=A2s only six. So not really a very
> substantial data set. :(

i view this as a good thing.  that is, an interop session or two, even
if they multiply it, might produce a list which could be cleared in some
months if y'all could motivate the vendors and app devs.

randy


From nobody Sun Jul 30 03:35:11 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 049F1132002 for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 03:35:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 FNM5NWfFV-_y for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 03:35:08 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 40A13131CF6 for <ietf@ietf.org>; Sun, 30 Jul 2017 03:35:08 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dblYw-0002II-0d; Sun, 30 Jul 2017 10:35:06 +0000
Date: Sun, 30 Jul 2017 19:35:04 +0900
Message-ID: <m2shhexlev.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Cc: Ted Lemon <mellon@fugue.com>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
In-Reply-To: <EMEW3|a840160da2fae312689377f3dbb5c924y6YBKo03tjc|ecs.soton.ac.uk|4BCED8BC-00CD-432B-9E61-1FCD438DA8EC@ecs.soton.ac.uk>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <0CC96AE9-832A-47DB-96A9-5E5DF67B0BA3@vpnc.org> <CAPt1N1=8tUWLg03zj_uktUiDyb5f7f9BFmjknDn0H3HTqxEHpw@mail.gmail.com> <DF4FC2CA-DC21-468A-A9C3-D1048985E9EF@vpnc.org> <6366C6A1-8DAA-4B3A-A2E4-CBD22A4B3F38@fugue.com> <f595d170-b540-a60a-bd93-6ff5abf1f246@cs.tcd.ie> <m2vamahja3.wl-randy@psg.com> <AB8FE929-A69C-43DD-911D-0831BAAECAE3@fugue.com> <m2h8xuzp1g.wl-randy@psg.com> <C52C3BB8-C84D-46A5-9904-7E44750F8744@fugue.com> <4BCED8BC-00CD-432B-9E61-1FCD438DA8EC@ecs.soton.ac.uk> <EMEW3|a840160da2fae312689377f3dbb5c924y6YBKo03tjc|ecs.soton.ac.uk|4BCED8BC-00CD-432B-9E61-1FCD438DA8EC@ecs.soton.ac.uk>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=ISO-8859-7
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gZDCxh78xvXicpk7_cNqsa7XtTw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 10:35:09 -0000

>>> lucy, ietf noc ticket goddess, tried to copy all 99 nat64 tickets into a
>>> bunch, see
>=20
> It=A2s great that Randy has pulled together the nat64-realted tickets.

lucy.  i said lucy.

randy


From nobody Sun Jul 30 04:01:44 2017
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACB48132007 for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 04:01:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
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 JjvBFTCLtCcs for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 04:01:40 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 005F91201F2 for <ietf@ietf.org>; Sun, 30 Jul 2017 04:01:39 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6UB1KBg009589; Sun, 30 Jul 2017 12:01:20 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v6UB1KBg009589
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1501412480; bh=zRvZ/Eyup5iW765yr5lZCiP8b/c=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=tdPw3EDRmp+rAqZ1rbJX6yNWG5StTFk4b5RnGb7nqTnGVbvyQ69izGpKCmjXVc7Q6 BTMQDYUbQjwvRiF8ZFdtLnge0EWw4LGr4DpOJFkntchhzWs3YJO5ymXLoL1sPPAGl9 kvHWz1lNWaz/OO5rro/2u5NaFnnq3NUoVqHHpr+o=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id y6YC1K1235803253nN ret-id none; Sun, 30 Jul 2017 12:01:20 +0100
Received: from 20010a88d51011.ipv6.customer.clara.net (20010a88d51011.ipv6.customer.clara.net [IPv6:2001:a88:d510:1101:3d25:de87:64aa:5fc9] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6UB1FhK020488 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 30 Jul 2017 12:01:15 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <m2shhexlev.wl-randy@psg.com>
Date: Sun, 30 Jul 2017 12:01:13 +0100
Cc: IETF Rinse Repeat <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|84e6773c7915ad7ee020b6137ea30ca2y6YC1K03tjc|ecs.soton.ac.uk|CE05C417-4A5E-4A57-ACF8-CE0948976444@ecs.soton.ac.uk>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <0CC96AE9-832A-47DB-96A9-5E5DF67B0BA3@vpnc.org> <CAPt1N1=8tUWLg03zj_uktUiDyb5f7f9BFmjknDn0H3HTqxEHpw@mail.gmail.com> <DF4FC2CA-DC21-468A-A9C3-D1048985E9EF@vpnc.org> <6366C6A1-8DAA-4B3A-A2E4-CBD22A4B3F38@fugue.com> <f595d170-b540-a60a-bd93-6ff5abf1f246@cs.tcd.ie> <m2vamahja3.wl-randy@psg.com> <AB8FE929-A69C-43DD-911D-0831BAAECAE3@fugue.com> <m2h8xuzp1g.wl-randy@psg.com> <C52C3BB8-C84D-46A5-9904-7E44750F8744@fugue.com> <4BCED8BC-00CD-432B-9E61-1FCD438DA8EC@ecs.soton.ac.uk> <EMEW3|a840160da2fae312689377f3dbb5c924y6YBKo03tjc|ecs.soton.ac.uk|4BCED8BC-00CD-432B-9E61-1FCD438DA8EC@ecs.soton.ac.uk> <m2shhexlev.wl-randy@psg.com> <CE05C417-4A5E-4A57-ACF8-CE0948976444@ecs.soton.ac.uk>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3273)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=y6YC1K123580325300; tid=y6YC1K1235803253nN; client=relay,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v6UB1KBg009589
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MeBNQNjcsKWH9JNpL7YqjNi_B5s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 11:01:42 -0000

> On 30 Jul 2017, at 11:35, Randy Bush <randy@psg.com> wrote:
>=20
>>>> lucy, ietf noc ticket goddess, tried to copy all 99 nat64 tickets =
into a
>>>> bunch, see
>>=20
>> It=E2=80=99s great that Randy has pulled together the nat64-realted =
tickets.
>=20
> lucy.  i said lucy.

Apologies!  Thanks Lucy.

Tim=


From nobody Sun Jul 30 04:02:05 2017
Return-Path: <John_Leddy@comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9185C13200D for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 04:02:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.402
X-Spam-Level: 
X-Spam-Status: No, score=-1.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 TSdIQImgqbMF for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 04:02:00 -0700 (PDT)
Received: from vaadcmhout01.cable.comcast.com (vaadcmhout01.cable.comcast.com [96.114.28.75]) (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 54FBA13200C for <ietf@ietf.org>; Sun, 30 Jul 2017 04:02:00 -0700 (PDT)
X-AuditID: 60721c4b-733ff70000000a8e-a7-597dbca5b45b
Received: from VAADCEX46.cable.comcast.com (vaadcmhoutvip.cable.comcast.com [96.115.73.56]) (using TLS with cipher AES256-SHA256 (256/256 bits)) (Client did not present a certificate) by vaadcmhout01.cable.comcast.com (SMTP Gateway) with SMTP id 1C.10.02702.5ACBD795; Sun, 30 Jul 2017 07:01:58 -0400 (EDT)
Received: from VAADCEX41.cable.comcast.com (147.191.103.218) by VAADCEX46.cable.comcast.com (147.191.103.223) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Sun, 30 Jul 2017 07:01:56 -0400
Received: from VAADCEX41.cable.comcast.com ([fe80::3aea:a7ff:fe12:e268]) by VAADCEX41.cable.comcast.com ([fe80::3aea:a7ff:fe12:e268%19]) with mapi id 15.00.1293.002; Sun, 30 Jul 2017 07:01:56 -0400
From: "Leddy, John" <John_Leddy@comcast.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>, Ted Lemon <mellon@fugue.com>
CC: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Thread-Topic: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Thread-Index: AQHTCRudSZ8j96rs+UKsu6v9cOmSwaJsa9gA///IdoA=
Date: Sun, 30 Jul 2017 11:01:55 +0000
Message-ID: <D66289FA-E4A7-49D8-B6BA-D48C8A56B3AC@cable.comcast.com>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <0CC96AE9-832A-47DB-96A9-5E5DF67B0BA3@vpnc.org> <CAPt1N1=8tUWLg03zj_uktUiDyb5f7f9BFmjknDn0H3HTqxEHpw@mail.gmail.com> <DF4FC2CA-DC21-468A-A9C3-D1048985E9EF@vpnc.org> <6366C6A1-8DAA-4B3A-A2E4-CBD22A4B3F38@fugue.com> <f595d170-b540-a60a-bd93-6ff5abf1f246@cs.tcd.ie> <m2vamahja3.wl-randy@psg.com> <AB8FE929-A69C-43DD-911D-0831BAAECAE3@fugue.com> <m2h8xuzp1g.wl-randy@psg.com> <C52C3BB8-C84D-46A5-9904-7E44750F8744@fugue.com> <4BCED8BC-00CD-432B-9E61-1FCD438DA8EC@ecs.soton.ac.uk> <EMEW3|a840160da2fae312689377f3dbb5c924y6YBKo03tjc|ecs.soton.ac.uk|4BCED8BC-00CD-432B-9E61-1FCD438DA8EC@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|a840160da2fae312689377f3dbb5c924y6YBKo03tjc|ecs.soton.ac.uk|4BCED8BC-00CD-432B-9E61-1FCD438DA8EC@ecs.soton.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.24.1.170721
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [96.115.73.252]
Content-Type: text/plain; charset="utf-8"
Content-ID: <17B6171539317547BAE7F94CBCD64AC8@comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA11Uf2wTVRzPu7tut9I33q5r+9ZtZLsARoP7ocQsaAgmGOevhMQgOTCst/Zo 67p2uWu7DUWnZCSrCovpzCggCp0imZvCCNuYztTJ3JIpE9RoYpTYaFgM8kNcFhh6767drv51 3/f5vPf9fL6fe3kszb1hdrL+YFiSg2KAzzMzLuWJuvs/GNsj1MzOM3W/f3KUqfuzf4KqS439 kbeJrl8ceKz+tQvv59cnkwvUFnq7+RGPFPBHJbl6o8vsi3f9TLfccbQd+Xe/qQP0O2KggMVo PT4xN50XA2aWQ2cpPPF1F60vUgB3//Up0BdTAB/89TpFjuShdbj37e9NpC5Gj+KevgM0qWm0 Bs+d2MfEAMta0XP4ck81KYvRNnxztEzfvQGPXJjRujDq7vNDnzGkhmgz/rtjXKs5dDwfXxrT PBSgToD3XvpFIwCy4/npfkqXcuCf0kcpfQKEk2Pf0Hptw1d+u6tZs6EqnJh8J4OvwzM/pIFe 1+AzfbowRpX47qFBzTKN7sWDo9V6+w244/AM0OtKHH/9cr7uswhPHUxnjjrwFxPDpm5QmjA4 Six3Shg6JQydEoZO7wLTSbAqKooed7MvFAnX1Fa5xcaAVOUONbtFJUy+pwD58XLZU8NgYOHx FEAs4C0Q9O0ROJMYVdqbU6CJpXgbHFihQoWNIU+7T1R8DXIkICl8MaTPvCRwcAlujASaeCc8 NaJuti6hQalVCUhh9abxq6Dv290C51jilIjS4nf7QxGlISIH1GvB0mrbwKDaAHrE9t2SHNLF UqCUZXgHfNYVFTjkFcNSkyS1SHKWbWVZHsPxUfVgkSx5pbZd/kA4S6vnYutVBhkZzWw5lI69 KHB2I2HwWwl3EdpppP9vmWILUsDLWlTfR4g8VFrEZsXvzUhbYTcJyZJFNdkSOEIy4rKgQbIc ei+qEdmzVK7cNOgE7NDtr+YpjgmGgpLTAXcQUUS2+yLBpZGddlhR1CZwKw0EkXaWwUKC2wz4 srqzAl5DKltiYHMNZF+KOeBW74oV7jynqlvUd2R5Yg4uEksrMqA2MIZTZOCiDGaYtwzuJFfC lmFy1ebUYCk12JKIFmxYDBuDjRLUkkUzwYYiWrAZMCfYVkLZs1SukrMDHDh/8pWny5+8su+W 9epbtWznzOnx51NM75els7Sj1FUs713b9UKYGjr9D3NPbTq+9dbmlxNvUjXbYg8LH91+8Gp3 xfWJSa/nxsZzD80XOiRq/wM3VsYnV7uSw4fjx5O2s70Ls7EfL37ccKev571yn9Q2aP98045n tqRXe1NrB1798DthkWcUn1h7Hy0r4n8atxlvnwUAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sdMqyqPyS27sxX9VuTDqiaOMYOA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 11:02:02 -0000

DQpUaGlzIGlzIGEgdmVyeSBkaXNoZWFydGVuaW5nIGRpc2N1c3Npb24gZnJvbSBhbiBJbnRlcm5l
dCBTZXJ2aWNlIFByb3ZpZGVyIGFuZCBFbnRlcnByaXNlIHBlcnNwZWN0aXZlLg0KDQpUaGUgSUVU
RiBiZWxpZXZlcyB0aGF0IHRoZSBtaWdyYXRpb24gdG8gSVBWNiBpcyBjcml0aWNhbCB0byB0aGUg
ZnV0dXJlIG9mIHRoZSBJbnRlcm5ldC4gIChZZXM/KQ0KVGhlIElFVEYgZHJpdmVzIHRoZSBzdGFu
ZGFyZHMgYW5kIHRoZSByZXN1bHRpbmcgcHJvZHVjdHMgdGhhdCBhcmUgYXZhaWxhYmxlIGZvciBk
ZXBsb3ltZW50IHRvIHNvbHZlIEludGVybmV0IHByb2JsZW1zIGluIHRoZSBtaWdyYXRpb24gdG8g
SVBWNi4NClRoZSBJRVRGIGlzIGNvbmNlcm5lZCB0aGF0IHV0aWxpemluZyB0aGVzZSB0ZWNobm9s
b2dpZXMgKGV2ZW4gd2l0aCBhbiBvcHQgb3V0IFY0IG5ldHdvcmspIG1heSBpbXBlZGUgaXRzIHdv
cmsgYXQgYSBjb25mZXJlbmNlLg0KVGhlIElFVEYgaXMgYXBwcmVoZW5zaXZlIHRoYXQgYXR0ZW5k
ZWVzIG1heSBub3QgaGF2ZSB0aGUgc2tpbGwvd2lsbCB0byB0cm91Ymxlc2hvb3QsIHdvcmsgYXJv
dW5kIG9yIGZpeCBhbnkgcmVzdWx0aW5nIGlzc3VlcyB0aGF0IGNvdWxkIHJlc3VsdC4NClRoZSBJ
RVRGIGNvbmNsdWRlcyB0aGF0IHRoZXNlIHRlY2hub2xvZ2llcyBhcmUgbm90IHJlYWR5IGZvciBp
dHMgb3duIHByb2R1Y3Rpb24gdXNlICjigJx3ZSBoYXZlIGFsbCB0aGUgSVBWNCBzcGFjZSB3ZSBu
ZWVk4oCdKSBhbmQgbmVlZCB0byBiZSBkZXBsb3llZCBieSBvdGhlcnMgKHdobyBkbyBub3QgaGF2
ZSBlbm91Z2ggSVBWNCBzcGFjZSkgdG8gYWRkcmVzcyBnYXBzIGluIHRoZSBzdGFuZGFyZHMgYW5k
IHJlc3VsdGluZyBpbXBsZW1lbnRhdGlvbnMuDQpUaGUgSUVURiBiZWxpZXZlcyB0aGUgY29uZmVy
ZW5jZXMgYXJlIHRvIGRvIHRoZSBORVcgd29yayBvZiB0aGUgSUVURiwgbm90IHRvIGJlIGltcGFj
dGVkIGJ5IHRoZSBxdWFsaXR5IG9mIHdvcmsgaXQgaGFzIGFscmVhZHkgZG9uZS4NCg0KSSB0aGlu
ayB5b3Ugd2lsbCBmaW5kIHRoYXQgbmVpdGhlciBTZXJ2aWNlIFByb3ZpZGVycyBub3IgRW50ZXJw
cmlzZXMgYmVsaWV2ZSB0aGF0IHRoZWlyIGJ1c2luZXNzIGlzIGRlcGxveWluZyBJUFY2IHRlY2hu
b2xvZ2llcy4NCldoYXQgc2hvdWxkIHRoZXNlIG9yZ2FuaXphdGlvbnMgdGFrZSBhd2F5IGZyb20g
dGhpcyBkaXNjdXNzaW9uPw0KDQpJcyB0aGUgbWVzc2FnZSByZWFsbHk7IERlcGxveSBJUFY2IGFu
ZCByaXNrIHlvdXIgYnVzaW5lc3M/DQoNCkpvaG4NCg0KT24gNy8zMC8xNywgNjoyMSBBTSwgImll
dGYgb24gYmVoYWxmIG9mIFRpbSBDaG93biIgPGlldGYtYm91bmNlc0BpZXRmLm9yZyBvbiBiZWhh
bGYgb2YgdGpjQGVjcy5zb3Rvbi5hYy51az4gd3JvdGU6DQoNCiAgICA+IE9uIDMwIEp1bCAyMDE3
LCBhdCAxMTowNywgVGVkIExlbW9uIDxtZWxsb25AZnVndWUuY29tPiB3cm90ZToNCiAgICA+IA0K
ICAgID4gT24gSnVsIDI5LCAyMDE3LCBhdCA5OjMzIFBNLCBSYW5keSBCdXNoIDxyYW5keUBwc2cu
Y29tPiB3cm90ZToNCiAgICA+PiBsdWN5LCBpZXRmIG5vYyB0aWNrZXQgZ29kZGVzcywgdHJpZWQg
dG8gY29weSBhbGwgOTkgbmF0NjQgdGlja2V0cyBpbnRvIGENCiAgICA+PiBidW5jaCwgc2VlDQog
ICAgPiANCiAgICA+IEkgcmVhZCB0aGlzIGFzIDk5IHRpY2tldHMsIGJ1dCBpdOKAmXMgb25seSBz
aXguIFNvIG5vdCByZWFsbHkgYSB2ZXJ5IHN1YnN0YW50aWFsIGRhdGEgc2V0LiA6KA0KICAgIA0K
ICAgIDYgdGlja2V0cyBmcm9tIGhvdyBtYW55IHVzZXJzPw0KICAgIA0KICAgIEl04oCZcyBncmVh
dCB0aGF0IFJhbmR5IGhhcyBwdWxsZWQgdG9nZXRoZXIgdGhlIG5hdDY0LXJlYWx0ZWQgdGlja2V0
cy4NCiAgICANCiAgICBDb3VsZCB3ZSBhbHNvIHJ1biBhIHNob3J0IHN1cnZleSBvbiB0aGUgYXR0
ZW5kZWVzIGxpc3QgYWZ0ZXIgdGhlIGV2ZW50LCB1c2luZyB0aGUgSUVURiBzdXJ2ZXkgbW9ua2V5
IG9yIHdoYXRldmVyIHRoZSBtZWV0aW5nIHN1cnZleSB1c2VzLCBvbiBuYXQ2NCBleHBlcmllbmNl
cyBmb3IgdGhpcyB3aG8gdXNlZCBpdD8NCiAgICANCiAgICBXZSBjb3VsZCB0aGVuIGZvciBleGFt
cGxlIHVzZSB0aGUgTk9DIGFuZCBzdXJ2ZXkgZGF0YSB0byBrZWVwIGEgcnVubmluZyBJLUQgb2Yg
aXNzdWVzIHRoYXTigJlzIHVwZGF0ZWQgYWZ0ZXIgZWFjaCBtZWV0aW5nPw0KICAgIA0KICAgIFRp
bQ0KICAgIA0KICAgIA0KDQo=


From nobody Sun Jul 30 04:53:53 2017
Return-Path: <lee@asgard.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73FDB12EA95 for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 04:53:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, 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 9legWHYmLu7r for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 04:53:50 -0700 (PDT)
Received: from atl4mhob21.registeredsite.com (atl4mhob21.registeredsite.com [209.17.115.115]) (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 BF0441243F3 for <ietf@ietf.org>; Sun, 30 Jul 2017 04:53:50 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.203]) by atl4mhob21.registeredsite.com (8.14.4/8.14.4) with ESMTP id v6UBrmoQ038002 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf@ietf.org>; Sun, 30 Jul 2017 07:53:48 -0400
Received: (qmail 24923 invoked by uid 0); 30 Jul 2017 11:53:48 -0000
X-TCPREMOTEIP: 68.33.78.6
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?10.232.226.170?) (lee@asgard.org@68.33.78.6) by 0 with ESMTPA; 30 Jul 2017 11:53:47 -0000
User-Agent: Microsoft-MacOutlook/14.7.2.170228
Date: Sun, 30 Jul 2017 07:53:43 -0400
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
From: Lee Howard <lee@asgard.org>
To: Randy Bush <randy@psg.com>, Ted Lemon <mellon@fugue.com>
CC: IETF Rinse Repeat <ietf@ietf.org>
Message-ID: <D5A33E31.7EE03%lee@asgard.org>
Thread-Topic: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <m2y3r7gmb9.wl-randy@psg.com>
In-Reply-To: <m2y3r7gmb9.wl-randy@psg.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0lk8ZXNhPeX4s3Ws7n6ea9JUXRM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 11:53:52 -0000

On 7/29/17, 1:55 PM, "ietf on behalf of Randy Bush" <ietf-bounces@ietf.org
on behalf of randy@psg.com> wrote:

>> The point is that we claim that we have produced something that will
>> Just Work for the average user.  If you really think you can't "get
>> work done" on an IPv6-only network with working and functional
>> transition tech, we have a problem.
>
>bingo!  you are right.  we have a problem.  nat64/dns64 breaks things
>people use.  this is known, documented, and extremely annoying this many
>years out [0].
>
>the question is how to progress fixing nat64/dns64, given that a lot of
>folk come to ietf meetings to simply get work done and not debug a semi-
>working transport.  how about a bug bounty?  and maybe a fix bounty a
>few times larger!

There are mulitple implementations of DNS64/NAT64. I think the one used by
the IETF NOC is from a router vendor, though I know of three router
vendors, at least one load balancer, and several open source
implementations (only one of which is intended for production use). I
haven=E2=80=99t tested them all, but I have no reason to think they are
particularly buggy.

Rather, I think the bugs are in applications.

How would default-NAT64 get application developers to fix their
applications?=20

In another message, Randy also said:
> why not start with what we have traditionally done with new protocols
> and implementations, the nat64 aficionados conduct interop testing with
> an i-d reporting the result?  for example, in the s'pore hackathon, have
> a group with an assortment of devices and a wide assortment of
> applications actually testing nat64.  maybe kickstart with the nat64
> tickets from {seoul,chicago,praha} if no other ideas come to mind.


I=E2=80=99m working on a research project along these lines, results of which I=E2=80=
=99ll
provide the IETF, and would be happy to help coordinate a NAT64 interop
testing project as part of IETF100-Singapore Hackathon.

Lee



>
>randy
>
>--
>
>0 - for just how many years, see my plenary rant against 4966 a few
>    chicagos back.  it is my $dayjob's customers, the enterprises, who
>    are the main target of nat64/dns64, and i am not happy that they can
>    not deploy it safely.
>
>



From nobody Sun Jul 30 05:55:12 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10DE612009C for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 05:55:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 jnJxzxG2LjpI for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 05:55:08 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 3DFF9126DEE for <ietf@ietf.org>; Sun, 30 Jul 2017 05:55:08 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dbnkO-0005mi-Kg; Sun, 30 Jul 2017 12:55:04 +0000
Date: Sun, 30 Jul 2017 21:55:02 +0900
Message-ID: <m2r2wyxexl.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Lee Howard <lee@asgard.org>
Cc: Ted Lemon <mellon@fugue.com>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
In-Reply-To: <D5A33E31.7EE03%lee@asgard.org>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <m2y3r7gmb9.wl-randy@psg.com> <D5A33E31.7EE03%lee@asgard.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=ISO-8859-7
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WYNsZmVfrc4AhZ6yu-60sppK-pc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 12:55:10 -0000

> There are mulitple implementations of DNS64/NAT64. I think the one
> used by the IETF NOC is from a router vendor

a pair of donated A10s.  the noccers dealing with that stuff did not
want to call ietf-nat64 a suported production service until they got the
second one and could run it in redundant configuration.

> Rather, I think the bugs are in applications.

my guess is applications and the basic nature of nat64/dns64.  but it's
just a guess.

> I=A2m working on a research project along these lines, results of which
> I=A2ll provide the IETF, and would be happy to help coordinate a NAT64
> interop testing project as part of IETF100-Singapore Hackathon.

yay!  thank you.

randy


From nobody Sun Jul 30 06:25:24 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16D36127201 for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 06:25:22 -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, 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=fugue-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 e7XijrtWA1bm for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 06:25:19 -0700 (PDT)
Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::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 9FF2E124207 for <ietf@ietf.org>; Sun, 30 Jul 2017 06:25:19 -0700 (PDT)
Received: by mail-qk0-x22f.google.com with SMTP id a77so39835789qkb.0 for <ietf@ietf.org>; Sun, 30 Jul 2017 06:25:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=YJYqq1keAyved3bp23KSowujox0f+Lu24eCg75h/U30=; b=xJDDcXFBnGCoxNZgMYLtVNG7TpX89UkvLMJcuENAYHaO3rhXvX7UZdIH3c0XUFgjMP jEPVuRNav+dK2kJUjpFmtDRgXPYwgDa8TXPrQ0rR4mZ3kyyyG/bK1/qY21u16VOveSQ7 bRKrGjz2JCtjiCsuuWkZJGQelW9RM6hT/RrN7hEdEmfUVq8kMA+JUN4EeenpKIaTgMvt KTkVHAXhhAlEkDhTBm1btaQ0U79uv+PLK8A97sIKdD8nq9RHBvl2AjazhRv9S6BOyXOl /fzYXcBQs68xClSJGV/ShRRCuXaGJZPuNGmDLDkfYufbZJVyVAOkUjqICf3oBlRMsbzK cZOg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=YJYqq1keAyved3bp23KSowujox0f+Lu24eCg75h/U30=; b=CqZW87ij5qr5zANFvRvuIu3HiKS95mpX6j6ad36B3/KnlXpUCacxgmw5VMBTR5DnAw pdLW7BZPCToi9uHFP8xeqQdldSStn9XNIDBgimcsxq7R7q67tXNB9NT3UaEb5exlYcMR 6RqmCsOdUEHeFtsHS7R2Y8SXrAq3WtJxrLZ0CRZxeVxgq5cFM5vSTquwVRGAgHunt0cI BJAA6YGH4PX7chBURBzzKNG6y4eAkTCQHPNNSIB0Oy81XFBgd0Voh41/4EHi7dhY+CgT OdKiSCVIW/5+lPdRxV5n7VBM558Gaq11zmawSR6SNAEwtN7YXGGOWEIcepogSruGO3Wj urLg==
X-Gm-Message-State: AIVw113N7YGU+u/OJ3COZnIsITXV978Mz0TZr5bGLrvkO5GmvA1ZPmjT PniI2ITWGULZ41pw+D0UEA==
X-Received: by 10.55.107.130 with SMTP id g124mr17182988qkc.210.1501421118484;  Sun, 30 Jul 2017 06:25:18 -0700 (PDT)
Received: from [10.0.30.153] (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id t74sm16724475qke.85.2017.07.30.06.25.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 30 Jul 2017 06:25:17 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <0830C839-BC59-43C8-8B75-693A94FF8D1E@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_FBC71D0B-3DB1-4A77-937A-7372871E6FE4"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Sun, 30 Jul 2017 09:25:15 -0400
In-Reply-To: <m2r2wyxexl.wl-randy@psg.com>
Cc: Lee Howard <lee@asgard.org>, IETF Rinse Repeat <ietf@ietf.org>
To: Randy Bush <randy@psg.com>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <m2y3r7gmb9.wl-randy@psg.com> <D5A33E31.7EE03%lee@asgard.org> <m2r2wyxexl.wl-randy@psg.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jXK2zIkFzBo0Sh2tDzOcVao6S04>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 13:25:22 -0000

--Apple-Mail=_FBC71D0B-3DB1-4A77-937A-7372871E6FE4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jul 30, 2017, at 8:55 AM, Randy Bush <randy@psg.com> wrote:
> my guess is applications and the basic nature of nat64/dns64.  but =
it's
> just a guess.

To applications, a NAT64 IPv4 host just looks like an IPv6 host.   The =
issues that come up tend to be either embedded IPv4 literals, or else =
cases where the app explicitly chooses which version of transport to use =
(e.g., OpenVPN used to do this).   Also, if you open a tunnel and start =
resolving domain names through that, you will start getting IPv4 =
addresses, and all your IPv4 connections will transit the tunnel, which =
may not be what you want. I think there are also issues that come up =
with L2TP, but I don't know the details.

The thing is, these issues are not random issues.   They show up or they =
don't.   They don't show up as flakiness: they show up as "it doesn't =
work at all."   So knowing how many out of an un-selected population =
actually run into these issues is pretty interesting.

That's why I want to make NAT64 the default.  But I suppose I am trying =
to write a check the NOC would have to cash.


--Apple-Mail=_FBC71D0B-3DB1-4A77-937A-7372871E6FE4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jul 30, 2017, at 8:55 AM, Randy Bush &lt;<a =
href=3D"mailto:randy@psg.com" class=3D"">randy@psg.com</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">my guess is =
applications and the basic nature of nat64/dns64. &nbsp;but =
it's</span><br style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">just a guess.</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""></div></blockquote></div><br class=3D""><div class=3D"">To =
applications, a NAT64 IPv4 host just looks like an IPv6 host. &nbsp; The =
issues that come up tend to be either embedded IPv4 literals, or else =
cases where the app explicitly chooses which version of transport to use =
(e.g., OpenVPN used to do this). &nbsp; Also, if you open a tunnel and =
start resolving domain names through that, you will start getting IPv4 =
addresses, and all your IPv4 connections will transit the tunnel, which =
may not be what you want. I think there are also issues that come up =
with L2TP, but I don't know the details.</div><div class=3D""><br =
class=3D""></div><div class=3D"">The thing is, these issues are not =
random issues. &nbsp; They show up or they don't. &nbsp; They don't show =
up as flakiness: they show up as "it doesn't work at all." &nbsp; So =
knowing how many out of an un-selected population actually <i =
class=3D"">run into</i>&nbsp;these issues is pretty =
interesting.</div><div class=3D""><br class=3D""></div><div =
class=3D"">That's why I want to make NAT64 the default. &nbsp;But I =
suppose I am trying to write a check the NOC would have to =
cash.</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_FBC71D0B-3DB1-4A77-937A-7372871E6FE4--


From nobody Sun Jul 30 06:27:23 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 095F6127201 for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 06:27:22 -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, 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=fugue-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 drpTAqn17khq for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 06:27:20 -0700 (PDT)
Received: from mail-qk0-x22d.google.com (mail-qk0-x22d.google.com [IPv6:2607:f8b0:400d:c09::22d]) (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 B8420124207 for <ietf@ietf.org>; Sun, 30 Jul 2017 06:27:20 -0700 (PDT)
Received: by mail-qk0-x22d.google.com with SMTP id a77so39844965qkb.0 for <ietf@ietf.org>; Sun, 30 Jul 2017 06:27:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=TZ/yCFcErv8EZwuu/GQE+wV5Uy6Clx1KORtAhMIEepk=; b=MBeB2sko5s04rVuQSUzs6WkfLHQPa7IW83XThYDp3urenPoWdjtJWVxLlo7zd3JUR1 v8vgz54PGn2hbSO24Kvoa8Xybs+s4E/S2GJGGN+jdEADuABynx0SAlNjdxumijetVu/5 du48ZnF95csqwtlvjjZAVbJUhiIH3ueLpsjhtSOPefj3/nW5KjocdC54PTXR5Ol2M4ta SfLen1ZRE1EXOPNEMGDjSuSxoiGojCE/nVoB6ltuwAVMmmjXEZdKNgt1oacVzmStrrTO cxfWzc4wvfown2BSLaIG7S8TfM8F3Ltq8UcZ7DCUyqgguT8PTg2thdPsT5zJ3EVqWfY1 VU3Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=TZ/yCFcErv8EZwuu/GQE+wV5Uy6Clx1KORtAhMIEepk=; b=BocWqbIqG86ZSBhe8t9ZnS1UHy65RGPFgleI93Fq23QFQjGQWFtImC/QxXBaKYmChI IEUeYvvCQh7Y1s7jK9+2e48EZNbgV68vgm3LYOSTjK7yWeoD8Pa3Rn5n3RB/p/JVpKwa ZxzPxkvShqqaTtx0NNIXYdURkfvh0eN74AIvz+u5rNDPQakH7kcdUMVmw4/6Imc5Xg0b ggDTLyfeQ4VUs+wF6VbF7iHTqqL5ojE7Yk6hTSFuu19+4erWY97VLYtL4RsQJUsHd0EX q989f5ZxtHbOkhxC63fWOaR5QJ4Rpn4rE9lctht0Dqp9AcPn3rLv2+UTOY3jCnv9rKej L0gg==
X-Gm-Message-State: AIVw110HUfmbUYgWYBo1xEw9Mjb0YHrGRVnm7YvlbO6r2gSl+F4ZKK3r jVHFwVDVGETk9SMz
X-Received: by 10.55.78.85 with SMTP id c82mr16114184qkb.154.1501421239897; Sun, 30 Jul 2017 06:27:19 -0700 (PDT)
Received: from [10.0.30.153] (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id 58sm19496913qtu.88.2017.07.30.06.27.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 30 Jul 2017 06:27:19 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <6EDD128A-C804-415B-9AFE-4A790A41CEFA@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_CA72242D-9BFF-4736-8F42-5D502B0316EB"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Sun, 30 Jul 2017 09:27:17 -0400
In-Reply-To: <D5A33E31.7EE03%lee@asgard.org>
Cc: Randy Bush <randy@psg.com>, IETF Rinse Repeat <ietf@ietf.org>
To: Lee Howard <lee@asgard.org>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <m2y3r7gmb9.wl-randy@psg.com> <D5A33E31.7EE03%lee@asgard.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UHaWeA5t4Ege7Rl0GI24AslerqQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 13:27:22 -0000

--Apple-Mail=_CA72242D-9BFF-4736-8F42-5D502B0316EB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jul 30, 2017, at 7:53 AM, Lee Howard <lee@asgard.org> wrote:
> How would default-NAT64 get application developers to fix their
> applications?=20

One of the biggest offenders historically was a Cisco VPN, so presumably =
having Cisco people experience that being borken would help.   Similarly =
with Microsoft people and the Windows Update issue that was mentioned =
earlier.   Desire to avoid public embarrassment is a useful motivating =
factor.


--Apple-Mail=_CA72242D-9BFF-4736-8F42-5D502B0316EB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jul 30, 2017, at 7:53 AM, Lee Howard &lt;<a =
href=3D"mailto:lee@asgard.org" class=3D"">lee@asgard.org</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">How would =
default-NAT64 get application developers to fix their</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">applications?<span =
class=3D"Apple-converted-space">&nbsp;</span></span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""></div></blockquote></div><br class=3D""><div class=3D"">One =
of the biggest offenders historically was a Cisco VPN, so presumably =
having Cisco people experience that being borken would help. &nbsp; =
Similarly with Microsoft people and the Windows Update issue that was =
mentioned earlier. &nbsp; Desire to avoid public embarrassment is a =
useful motivating factor.</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_CA72242D-9BFF-4736-8F42-5D502B0316EB--


From nobody Sun Jul 30 06:57:15 2017
Return-Path: <prvs=13848a67b3=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E06012EAE8 for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 06:57:12 -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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
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 ZstOUq9vIg0Q for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 06:57:10 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94885129B03 for <ietf@ietf.org>; Sun, 30 Jul 2017 06:57:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1501423028; x=1502027828; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=nt6V0FYjQ635M2uRgwsJdDroW 5KHELyTD5fD1nhAMNQ=; b=LqMSd1GArtNFfZJNvSIvQDiFAptSzv7iskUyYz2y0 LRIgvCWj6HDxfXN4auaTQ32B0RXYJZPYdF9fgMP4G+z47wH1MYFJGS9uZuToWIw0 IA5M8DKORj99mUMNwSzlLK8dRqN7nUIvjEqxzPLnnmMwS6D+3nGfPbx8y0QI/AqQ uQ=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=BjvTxUal2tazhb8SfpvKQibSOZ0L8MnHGWuzsdJ3vluFnDLjknm0oyqXJhTO Rnn/zqF/zey2b0xRGI5FFNJOMchBclWvIkYzfsQsEcguAA3MR7Vkd9h5x JgIaLIsQfnQtHEy8vkPwiKLBMDVHLyMeHu2aS2TpIsizeuxqTv6X2M=;
X-MDAV-Processed: mail.consulintel.es, Sun, 30 Jul 2017 15:57:08 +0200
X-Spam-Processed: mail.consulintel.es, Sun, 30 Jul 2017 15:57:04 +0200
Received: from [10.10.10.133] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005490366.msg for <ietf@ietf.org>; Sun, 30 Jul 2017 15:57:04 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170730:md50005490366::yT9VZQao87XeY5w+:00002Qgu
X-Return-Path: prvs=13848a67b3=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.24.1.170721
Date: Sun, 30 Jul 2017 15:57:03 +0200
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IETF Rinse Repeat <ietf@ietf.org>
Message-ID: <7BF06063-9AED-4CB6-8C86-38965BEDDB8F@consulintel.es>
Thread-Topic: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <m2y3r7gmb9.wl-randy@psg.com> <D5A33E31.7EE03%lee@asgard.org> <6EDD128A-C804-415B-9AFE-4A790A41CEFA@fugue.com>
In-Reply-To: <6EDD128A-C804-415B-9AFE-4A790A41CEFA@fugue.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YNvGDzuGaHpnIqSiwsuMisjpfU4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 13:57:12 -0000

Not really so easy like that =E2=80=A6

The reason I can=E2=80=99t use the NAT64 (unless I run my own CLAT VM, whic=
h requires the NOC to assign a /64 to my own laptop, as I did in the IETF98=
, or there is a CLAT in that network), is that Office is not working if the=
 destinations are IPv4-only.

For example, I=E2=80=99ve email accounts that are IPv4-only. They don=E2=80=
=99t work. I=E2=80=99ve also one gmail email account, which is only a backu=
p, I never use it. The gmail servers are dual-stack, so they work fine with=
 Office for Mac.

I=E2=80=99m guessing that the Microsoft guys at the IETF use Microsoft OS (=
which already includes CLAT), so unless the failure is the same and fails a=
s well in Microsoft OS with Office for windows, the Microsoft employees are=
n=E2=80=99t going to =E2=80=9Csuffer=E2=80=9D the same pain as Mac OS users=
 running Office for Mac.

So in my opinion, in a considerable %, this effort is useless.

The folks that are involved in deploying IPv6 in many networks worldwide (a=
s it is my own case), we know without the need to try in the IETF network, =
that we can=E2=80=99t deploy IPv6-only in the LANs. We know that many apps/=
devices will not work if we do that. We know what is the real world, and we=
 know that is a matter of time (probably more than 5 years) for ISPs to del=
iver IPv6-only WAN with IPv6-only LANs.

You can=E2=80=99t force customer to throw away their IP cameras, NAS, or al=
l kind of old systems or business apps with IPv4-only support. Even if we t=
ell the vendors, they will do it when they want, and all the products from =
vendors that don=E2=80=99t exists anymore will never be updated.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Ted Lemon <mellon@fugue.com>
Responder a: <mellon@fugue.com>
Fecha: domingo, 30 de julio de 2017, 15:27
Para: Lee Howard <lee@asgard.org>
CC: IETF Rinse Repeat <ietf@ietf.org>
Asunto: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF =
Meetings

    On Jul 30, 2017, at 7:53 AM, Lee Howard <lee@asgard.org> wrote:
    How would default-NAT64 get application developers to fix their
    applications?=20
   =20
   =20
   =20
   =20
   =20
    One of the biggest offenders historically was a Cisco VPN, so presumabl=
y having Cisco people experience that being borken would help.   Similarly =
with Microsoft people and the Windows Update issue that was mentioned earli=
er.   Desire to avoid public embarrassment is a useful motivating factor.
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Sun Jul 30 07:44:40 2017
Return-Path: <fenner@fenron.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E3D7131C9F for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 07:44:38 -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, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=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 (1024-bit key) header.d=fenron.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 SOQ-rP2VTGlu for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 07:44:37 -0700 (PDT)
Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::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 C8765131C2C for <ietf@ietf.org>; Sun, 30 Jul 2017 07:44:36 -0700 (PDT)
Received: by mail-qk0-x22f.google.com with SMTP id x191so70802345qka.5 for <ietf@ietf.org>; Sun, 30 Jul 2017 07:44:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fenron.com; s=google;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=VbTlO+dE6y2RQOoND9eQ3LEX+bcoNOOA9G5qszuf11A=; b=Su6wyi+jAuqnRiFmxlZzrNvP93sXZMTGlhOSQnQPoBaf+XdshPiK1E3D1XHKr/ZI7B LD3HtpFxK4gZjMwEkf0PnjoPBEAvkDi7ts9nybRdA8nPuo3PfNGywBxHM+XxyH2niC3p d2KWhTJsaW1zeLLDYAC/9BUv0iRyzKKbgm004=
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=VbTlO+dE6y2RQOoND9eQ3LEX+bcoNOOA9G5qszuf11A=; b=Kk9WyPLhUsMbgDUAYBtyqi8K36A4Qkp38fOhWbVdJRhR0/HtKb6jBGyqqKDlj0uWDy pq+2N2a5aWy4tDn8K6ZTaMPF6A8l5nBP0Xl29oqOtfFzp1nhhKUoMYCtLr0VMzy0kA+R ML+qFolP7uamceFXoGvqeQPuvW9LXmg9lChO5h2VUUq/ojVhMA3GWW+UZOwZMW4Hhv/r u/fUfwdGW8D4Qt2bZ9vaopPOKRlLxz3gwqRidLW+RIzjee0CkOH+xN9hj7DgINlJyxQ5 SZ+UzYaHLmjlabnTSVO8oYihC5cSmHKbhd4hfs8zR0K4ip2UBuRDBOe1JIyqnAb7XRUh MM8A==
X-Gm-Message-State: AIVw112kEvEhZScU7YboKeh91YbJXJqMAKuWU7Dnyt86EFSEGOSFFm8m dvr1EwKdkBQpet5l
X-Received: by 10.233.232.130 with SMTP id a124mr16467199qkg.179.1501425875913;  Sun, 30 Jul 2017 07:44:35 -0700 (PDT)
Received: from ?IPv6:2600:380:402c:dfa2:f532:96a2:6121:c37d? ([2600:380:402c:dfa2:f532:96a2:6121:c37d]) by smtp.gmail.com with ESMTPSA id d125sm18596677qkg.43.2017.07.30.07.44.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 30 Jul 2017 07:44:34 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-FA4DFBFF-CE74-4679-8C0F-25F78588F44C
Mime-Version: 1.0 (1.0)
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
From: Bill Fenner <fenner@fenron.com>
X-Mailer: iPhone Mail (14G60)
In-Reply-To: <6EDD128A-C804-415B-9AFE-4A790A41CEFA@fugue.com>
Date: Sun, 30 Jul 2017 10:44:33 -0400
Cc: Lee Howard <lee@asgard.org>, IETF Rinse Repeat <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <CFA58DB0-3D1D-46B7-91FA-16CAEA8F7B38@fenron.com>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <m2y3r7gmb9.wl-randy@psg.com> <D5A33E31.7EE03%lee@asgard.org> <6EDD128A-C804-415B-9AFE-4A790A41CEFA@fugue.com>
To: Ted Lemon <mellon@fugue.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2ppRiuh63366r0HnNgv2DgFx9oA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 14:44:38 -0000

--Apple-Mail-FA4DFBFF-CE74-4679-8C0F-25F78588F44C
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable




  Bill

> On Jul 30, 2017, at 9:27 AM, Ted Lemon <mellon@fugue.com> wrote:
>=20
>> On Jul 30, 2017, at 7:53 AM, Lee Howard <lee@asgard.org> wrote:
>> How would default-NAT64 get application developers to fix their
>> applications?=20
>=20
> One of the biggest offenders historically was a Cisco VPN, so presumably h=
aving Cisco people experience that being borken would help.   Similarly with=
 Microsoft people and the Windows Update issue that was mentioned earlier.  =
 Desire to avoid public embarrassment is a useful motivating factor.
>=20

On the other hand, the corporate VPN I use publishes a support matrix on the=
ir public web site, and specifically says that IPv6 is not supported. I don'=
t think they're embarrassed about it.

Most people using VPNs will be in a weird state with NAT64 anyway, assuming t=
hat they use the VPN's DNS server (e.g., to access internal resources by nam=
e).  A split-tunnel VPN user will lose access to v4-only sites, since it wil=
l lose dns64 translation (and will simultaneously lose the ability to detect=
 the nat64 via the rfc7050 lookup mechanism).  Does this mean "don't bother w=
ith split tunnel VPNs in a nat64 network"?

  Bill


--Apple-Mail-FA4DFBFF-CE74-4679-8C0F-25F78588F44C
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=3D=
utf-8"></head><body dir=3D"auto"><div><br></div><div><div><br><br><div>&nbsp=
; Bill<br></div><div><br></div></div>On Jul 30, 2017, at 9:27 AM, Ted Lemon &=
lt;<a href=3D"mailto:mellon@fugue.com">mellon@fugue.com</a>&gt; wrote:<br><b=
r></div><blockquote type=3D"cite"><div><meta http-equiv=3D"Content-Type" con=
tent=3D"text/html charset=3Dus-ascii">On Jul 30, 2017, at 7:53 AM, Lee Howar=
d &lt;<a href=3D"mailto:lee@asgard.org" class=3D"">lee@asgard.org</a>&gt; wr=
ote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span style=3D=
"font-family: Menlo-Regular; font-size: 18px; font-style: normal; font-varia=
nt-caps: normal; font-weight: normal; letter-spacing: normal; text-align: st=
art; text-indent: 0px; text-transform: none; white-space: normal; word-spaci=
ng: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !impor=
tant;" class=3D"">How would default-NAT64 get application developers to fix t=
heir</span><br style=3D"font-family: Menlo-Regular; font-size: 18px; font-st=
yle: normal; font-variant-caps: normal; font-weight: normal; letter-spacing:=
 normal; text-align: start; text-indent: 0px; text-transform: none; white-sp=
ace: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D"">=
<span style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: norm=
al; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; t=
ext-align: start; text-indent: 0px; text-transform: none; white-space: norma=
l; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: i=
nline !important;" class=3D"">applications?<span class=3D"Apple-converted-sp=
ace">&nbsp;</span></span><br style=3D"font-family: Menlo-Regular; font-size:=
 18px; font-style: normal; font-variant-caps: normal; font-weight: normal; l=
etter-spacing: normal; text-align: start; text-indent: 0px; text-transform: n=
one; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;=
" class=3D""></div></blockquote></div><br class=3D""><div class=3D"">One of t=
he biggest offenders historically was a Cisco VPN, so presumably having Cisc=
o people experience that being borken would help. &nbsp; Similarly with Micr=
osoft people and the Windows Update issue that was mentioned earlier. &nbsp;=
 Desire to avoid public embarrassment is a useful motivating factor.</div><d=
iv class=3D""><br class=3D""></div></div></blockquote><br><div>On the other h=
and, the corporate VPN I use publishes a support matrix on their public web s=
ite, and specifically says that IPv6 is not supported. I don't think they're=
 embarrassed about it.</div><div><br></div><div>Most people using VPNs will b=
e in a weird state with NAT64 anyway, assuming that they use the VPN's DNS s=
erver (e.g., to access internal resources by name). &nbsp;A split-tunnel VPN=
 user will lose access to v4-only sites, since it will lose dns64 translatio=
n (and will simultaneously lose the ability to detect the nat64 via the rfc7=
050 lookup mechanism). &nbsp;Does this mean "don't bother with split tunnel V=
PNs in a nat64 network"?</div><div><br></div><div>&nbsp; Bill</div><div><br>=
</div></body></html>=

--Apple-Mail-FA4DFBFF-CE74-4679-8C0F-25F78588F44C--


From nobody Sun Jul 30 08:58:33 2017
Return-Path: <huitema@huitema.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF1E7129417 for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 08:58:31 -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 i21WWlz8YdPy for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 08:58:30 -0700 (PDT)
Received: from mx44.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 6C349126E3A for <ietf@ietf.org>; Sun, 30 Jul 2017 08:58:30 -0700 (PDT)
Received: from xsmtp05.mail2web.com ([168.144.250.245]) by mx44.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1dbqbs-0004Lz-3Y for ietf@ietf.org; Sun, 30 Jul 2017 17:58:28 +0200
Received: from [10.5.2.35] (helo=xmail10.myhosting.com) by xsmtp05.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1dbqbo-0003Zf-Ge for ietf@ietf.org; Sun, 30 Jul 2017 11:58:25 -0400
Received: (qmail 14427 invoked from network); 30 Jul 2017 15:58:20 -0000
Received: from unknown (HELO [192.168.1.103]) (Authenticated-user:_huitema@huitema.net@[172.56.42.66]) (envelope-sender <huitema@huitema.net>) by xmail10.myhosting.com (qmail-ldap-1.03) with ESMTPA for <ietf@ietf.org>; 30 Jul 2017 15:58:20 -0000
To: ietf@ietf.org
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <m2y3r7gmb9.wl-randy@psg.com> <alpine.DEB.2.02.1707300726150.29742@uplift.swm.pp.se>
From: Christian Huitema <huitema@huitema.net>
Message-ID: <843ddff4-c238-ab54-959a-8ebc9b67ab11@huitema.net>
Date: Sun, 30 Jul 2017 08:58:18 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.02.1707300726150.29742@uplift.swm.pp.se>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
X-Originating-IP: 168.144.250.245
X-SpamExperts-Domain: xsmtpout.mail2web.com
X-SpamExperts-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-SpamExperts-Outgoing-Class: unsure
X-SpamExperts-Outgoing-Evidence: Combined (0.12)
X-Recommended-Action: accept
X-Filter-ID: PqwsvolAWURa0gwxuN3S5YEa3T7JuZT23fGO2rGt3ZgTCGhDnudOJ80D1c8rffxrus7BTv7Ss8cH d2IQQuvdbtM+m4WpRRDP6YzwkAPgQJYWea6pBBugJdVQWCV6zgcsND46yZLY9QyX+cRXmooQ3hum JwiT+2brWmQlzkLIcXivpIH4ag6BM/+u9ym+BA23rGaoc0P5Ic3rzcEagpx//xsZfEPNpdUmElps /3T6JOJJiA+y/3/5HxRo/OD1u4upYOEkjsX7F8KmpUaZQHV+SU9tg6wnJ2lrZSUCZrKFYsG2G5Pj 7iQJEmtNUzH3idZ6uMF2OhyCCCV83x+RZrKIj0QqMGQOSwmEPwP4wBzM77N8GvkYGGDFjg9NrmGY yNnXsSjdYwfRhjHqxQXDsBKLpKrrXdhf8mmRqp8CWMEqUPf6lO4FGen962xgCFRckncKfg1XSK9P 1z/R6plfrFWGyTMwTxcLMYH21xjMOqgtaszeNHk15VolAGHS5rCXQKDym+Gab6cuAPzLi/SdAxlO dgkraHgbbAuZgv0Q6mJ3vUcipz1IT62ZEk6+MmovaufbiR3bHfnMCIEU+nrglojKwMr3vOY18GvB wSXAfWcj2357kOoTgosukdyElz7rBwHENdSMuNhZC3X/nGdDKYyg+1Fotn1TGspRGWfHjmaruO0b XpkevaElTi+sCWwmqxHi+BUHXGjp0J8FpT+J6AFTxpi7UzHpJO9QrRDBoaz9Nyw078I0y+3uS4dN KiUgYTBUQK5usRReSSgnweD6c5lv0IAbiteDwjw8P7mx/NBHSRWxZaHLvUGmD7PXY2RS8idsz7fr MHsNPRylYAkPvY1HttQOF909qtkcRbvucYBIc/TSiGRBfhCjzofKjrwJNQRY0i13zjCiwPgdt77s k1WBMw==
X-Report-Abuse-To: spam@quarantine5.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/u360KhCfiYttCLVYd7URs-M8Ge0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 15:58:32 -0000

On 7/29/2017 10:36 PM, Mikael Abrahamsson wrote:
> There is nothing inherently broken with NAT64+DNS64+CLAT (or something
> like iOS has with bump-in-the-API). 

DNS64 assumes that the host uses the network provided DNS server, and
that it is OK to forge DNS replies. The first assumption is falsified
when the host uses another DNS server, such as provided by a VPN or by
DPRIVE. The second assumption is falsified when the host requires
DNSSEC. There are of course workarounds, which relies on some smart in
the host. And te whole point is to ensure that such workarounds are
deployed.

-- 
Christian Huitema


From nobody Sun Jul 30 09:09:32 2017
Return-Path: <heas@shrubbery.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E735131C3C; Sun, 30 Jul 2017 09:09:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level: 
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 yqOobpGamc2w; Sun, 30 Jul 2017 09:09:30 -0700 (PDT)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7471C12940A; Sun, 30 Jul 2017 09:09:30 -0700 (PDT)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id 2BC1278480; Sun, 30 Jul 2017 16:09:30 +0000 (UTC)
Date: Sun, 30 Jul 2017 16:09:30 +0000
From: heasley <heas@shrubbery.net>
To: Eric Rescorla <ekr@rtfm.com>
Cc: Ted Lemon <mellon@fugue.com>, "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,  Suresh Krishnan <suresh.krishnan@gmail.com>, "Brzozowski, John" <John_Brzozowski@comcast.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Message-ID: <20170730160930.GB44883@shrubbery.net>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <CABcZeBOMnMPsQwCr9UjND3iP3WiY3GxTZ2WbeP1cMeZqmhNgRA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CABcZeBOMnMPsQwCr9UjND3iP3WiY3GxTZ2WbeP1cMeZqmhNgRA@mail.gmail.com>
X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc
X-note: live free, or die!
X-homer: i just want to have a beer while i am caring.
X-Claimation: an engineer needs a manager like a fish needs a bicycle
X-reality: only YOU can put an end to the embarrassment that is Tom Cruise
User-Agent: Mutt/1.8.3 (2017-05-23)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JTJ7HFNPifZFWrLB0G0QhrmDy98>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 16:09:31 -0000

Sat, Jul 29, 2017 at 11:17:57AM -0700, Eric Rescorla:
> In other words, you want to opt everyone into doing your testing for you.

Wow, that is a toxic comment.  Vendors do not run EFT programs for fun.


From nobody Sun Jul 30 13:09:49 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BEB3131CAA for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 13:09:48 -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 8_l89PsGSo99 for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 13:09:47 -0700 (PDT)
Received: from mail-pg0-x243.google.com (mail-pg0-x243.google.com [IPv6:2607:f8b0:400e:c05::243]) (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 18011129B30 for <ietf@ietf.org>; Sun, 30 Jul 2017 13:09:47 -0700 (PDT)
Received: by mail-pg0-x243.google.com with SMTP id 125so15149917pgi.5 for <ietf@ietf.org>; Sun, 30 Jul 2017 13:09:47 -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=VD8jH/TH3tv4P48RHc62rJAz90LSKJgKhiaKu/MqBkI=; b=GYoufRD/H799w2Q8Jj4dQx+lxaB44Nassfyv3qa/DBWNonb9I06iPU0lXRTSLQB5z1 krFRpyd01oy+npjy+IHZtqQI+Ol3vIIo/CXalhHbgL+QsCiEkcUgmfbJbfE09cmE8wcy J7QDYEDd5CniTvvwPl4AJAFKBez3WCuz9p/Er0r2U5LNYPSWdA0Xj7ZIomSLgRUwOstd 2NRzxsTZWvT8NCQ51UhKB3omnjGpmOd+1Yp3KxnReAu9+EZRtDJFEvyIhXyMqpI14Ym6 apecuz2XcvScJ9qX2bdYsDKKBrpCtlEHZcn8RF0P3Qx1qch/LW9kpeKYqYPJmb03FGMZ LywA==
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=VD8jH/TH3tv4P48RHc62rJAz90LSKJgKhiaKu/MqBkI=; b=nRCzFA3lcumCZ3ltQXOwajnvvv68k+uCvdJpaxdr6nkJRaDO/jNBHeoKeZyo/k8HW/ +2T/DLQDhy3yRcxerWyTIpn66knbsxb8Zkm1b1PPTvwEJ4DZNr9HC7QXKGSKcMGuUbBs f5gkv+Cyh+EmawYpC75dTPWJ2mM147EKkS8ei41RkQLlSeZPeeuW6zx556bxp7b3mm2L FrWdsx26s5tV2oYgv7fzoLAxEJSD+syhOZqmeL1W6QmPQqGY42vqmCxBZbKWYumlrQ5h Vtyz6y/0uk3eXsNMEOqBgTZj4qYzk0lU0TSSTJUTdvY8kEyHAPUlpaC7IEoi+IAYQ6YC OANg==
X-Gm-Message-State: AIVw112PpWrJ2YWKkPtszKZxNBQxLSVN9J8d81BdWqVDMxfNrYldTh43 6quJ/Zmbo+UFDryRvAg=
X-Received: by 10.99.45.194 with SMTP id t185mr13083737pgt.388.1501445386327;  Sun, 30 Jul 2017 13:09:46 -0700 (PDT)
Received: from ?IPv6:2406:e007:521f:1:28cc:dc4c:9703:6781? ([2406:e007:521f:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id 84sm9727306pgd.48.2017.07.30.13.09.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 30 Jul 2017 13:09:45 -0700 (PDT)
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: Bill Fenner <fenner@fenron.com>, Ted Lemon <mellon@fugue.com>
Cc: IETF Rinse Repeat <ietf@ietf.org>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com> <m2y3r7gmb9.wl-randy@psg.com> <D5A33E31.7EE03%lee@asgard.org> <6EDD128A-C804-415B-9AFE-4A790A41CEFA@fugue.com> <CFA58DB0-3D1D-46B7-91FA-16CAEA8F7B38@fenron.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <eea3c14d-0ab7-63e7-a933-48e9937f1bb5@gmail.com>
Date: Mon, 31 Jul 2017 08:09:40 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CFA58DB0-3D1D-46B7-91FA-16CAEA8F7B38@fenron.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8dflJmvTslvu2tYtUG2LA7OA1ns>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 20:09:48 -0000

On 31/07/2017 02:44, Bill Fenner wrote:
>> On Jul 30, 2017, at 9:27 AM, Ted Lemon <mellon@fugue.com> wrote:
>>
>>> On Jul 30, 2017, at 7:53 AM, Lee Howard <lee@asgard.org> wrote:
>>> How would default-NAT64 get application developers to fix their
>>> applications? 
>>
>> One of the biggest offenders historically was a Cisco VPN, so presumably having Cisco people experience that being borken would help.   Similarly with Microsoft people and the Windows Update issue that was mentioned earlier.   Desire to avoid public embarrassment is a useful motivating factor.
>>
> 
> On the other hand, the corporate VPN I use publishes a support matrix on their public web site, and specifically says that IPv6 is not supported. I don't think they're embarrassed about it.
> 
> Most people using VPNs will be in a weird state with NAT64 anyway, assuming that they use the VPN's DNS server (e.g., to access internal resources by name).  A split-tunnel VPN user will lose access to v4-only sites, since it will lose dns64 translation (and will simultaneously lose the ability to detect the nat64 via the rfc7050 lookup mechanism).  Does this mean "don't bother with split tunnel VPNs in a nat64 network"?

So here's the thing. All NAT breaks stuff, therefore NAT64 breaks stuff.
In fact, it breaks stuff in more complex ways than NAT44 or even NAT444.

I see no good ending to the attempt to make NAT64 work in all circumstances.

     Brian


From nobody Sun Jul 30 14:26:26 2017
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EA60129ADD for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 14:26:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.358
X-Spam-Level: 
X-Spam-Status: No, score=-5.358 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_06_12=1.543, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 WC3hsIYhc7Jj for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 14:26:24 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 EA898126CD8 for <ietf@ietf.org>; Sun, 30 Jul 2017 14:26:23 -0700 (PDT)
Received: from mb.local ([IPv6:2607:fb90:a22a:95e4:456b:2334:16ec:1c6d]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id v6ULPuWW094140 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Sun, 30 Jul 2017 21:26:03 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host [IPv6:2607:fb90:a22a:95e4:456b:2334:16ec:1c6d] claimed to be mb.local
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: Tim Chown <tjc@ecs.soton.ac.uk>, Christian Huitema <huitema@huitema.net>,  IETF Discussion <ietf@ietf.org>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <e9095813-b5b5-29ba-34ab-f11c423aea26@cs.tcd.ie> <39FD84EA-4614-4331-B562-C9B2219FE949@fugue.com> <71ace01c-66a1-9e85-145b-8bb11f4d9edc@cs.tcd.ie> <m28tj7it97.wl-randy@psg.com> <305594a4-c49c-cdcc-8c6a-4c5464431f49@huitema.net> <9F93A245-38F0-4A66-9418-4478F292677F@ecs.soton.ac.uk> <EMEW3|79c4c6564a9184e6fcca8fbd0d116402y6SJHm03tjc|ecs.soton.ac.uk|9F93A245-38F0-4A66-9418-4478F292677F@ecs.soton.ac.uk>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <ee72ebf2-5e6c-44b0-00f3-2736b0dba9ef@bogus.com>
Date: Sun, 30 Jul 2017 14:49:37 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:55.0) Gecko/20100101 Thunderbird/55.0
MIME-Version: 1.0
In-Reply-To: <EMEW3|79c4c6564a9184e6fcca8fbd0d116402y6SJHm03tjc|ecs.soton.ac.uk|9F93A245-38F0-4A66-9418-4478F292677F@ecs.soton.ac.uk>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jURaUAvEiXva29BoD85OtghmscbCl85Ac"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gmO0-r-S7Mz-4rs0T2e6aQXHI44>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 21:26:25 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--jURaUAvEiXva29BoD85OtghmscbCl85Ac
Content-Type: multipart/mixed; boundary="3dWncWu0sCCg1g9ASPTi76bGULlU8bN5S";
 protected-headers="v1"
From: joel jaeggli <joelja@bogus.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>, Christian Huitema <huitema@huitema.net>,
 IETF Discussion <ietf@ietf.org>
Message-ID: <ee72ebf2-5e6c-44b0-00f3-2736b0dba9ef@bogus.com>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF
 Meetings
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com>
 <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com>
 <e9095813-b5b5-29ba-34ab-f11c423aea26@cs.tcd.ie>
 <39FD84EA-4614-4331-B562-C9B2219FE949@fugue.com>
 <71ace01c-66a1-9e85-145b-8bb11f4d9edc@cs.tcd.ie>
 <m28tj7it97.wl-randy@psg.com>
 <305594a4-c49c-cdcc-8c6a-4c5464431f49@huitema.net>
 <9F93A245-38F0-4A66-9418-4478F292677F@ecs.soton.ac.uk>
 <EMEW3|79c4c6564a9184e6fcca8fbd0d116402y6SJHm03tjc|ecs.soton.ac.uk|9F93A245-38F0-4A66-9418-4478F292677F@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|79c4c6564a9184e6fcca8fbd0d116402y6SJHm03tjc|ecs.soton.ac.uk|9F93A245-38F0-4A66-9418-4478F292677F@ecs.soton.ac.uk>

--3dWncWu0sCCg1g9ASPTi76bGULlU8bN5S
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 7/29/17 20:17, Tim Chown wrote:

> 2. Whether we fully understand how devices of various common OSes
> select an SSID on startup, without manual intervention.
>=20
> The line in Randy=E2=80=99s data that puzzled me was the 967 devices
> associating to the ietf-legacy99 SSID. I believe the SSID had the
> meeting number appended to avoid devices just re-associating to an
> =E2=80=98ietf-legacy=E2=80=99 SSID every meeting. By adding the number,=
 one might
> hope users would have to manually select the SSID. But perhaps at
> least one major OS prefers this SSID because of its open property?

There's nothing paticularly odd about this.several of these operating
systems will both notify you opportunistically of available open
networks by default and make then visually distinctive. you then
condition a user population to select then becuase they are open, and
therefore don't require a cert, shared secret, username, password. and
you get a scenario where it's going to get selected between meetings.
unsurping since it's the low friction option.

We tested the steps associated with with associating with an open wifi
network on all the platforms we had available, and despite the
notification that security might be good idea, it is always the lowest
friction option.


--3dWncWu0sCCg1g9ASPTi76bGULlU8bN5S--

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

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAll91eIACgkQ8AA1q7Z/VrJU3QCfSwkRxdI6oJ4MonI4GSevnFAk
vcoAnRS6SI7MoiUb+FTcPph+hc7Hpkon
=dWQM
-----END PGP SIGNATURE-----

--jURaUAvEiXva29BoD85OtghmscbCl85Ac--


From nobody Sun Jul 30 15:58:39 2017
Return-Path: <jared@puck.nether.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D470129A9F for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 15:58:38 -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, DRUGS_ANXIETY=1.483, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 PafajZEvIfdH for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 15:58:37 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 78675126557 for <ietf@ietf.org>; Sun, 30 Jul 2017 15:58:37 -0700 (PDT)
Received: from [IPv6:2600:380:bd34:4f08:5965:f9f4:850:16bd] (unknown [IPv6:2600:380:bd34:4f08:5965:f9f4:850:16bd]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 3A397540B6D; Sun, 30 Jul 2017 18:58:35 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: Visiting Singapore/Customs Clearance
From: Jared Mauch <jared@puck.nether.net>
X-Mailer: iPhone Mail (14G60)
In-Reply-To: <45b53222-7c78-939d-3819-d567c70ea60e@gmail.com>
Date: Sun, 30 Jul 2017 18:58:30 -0400
Cc: Mary B <mary.h.barnes@gmail.com>, Mike StJohns <mstjohns@comcast.net>, "Gary E. Miller" <gem@rellim.com>, IETF discussion list <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3D61737C-93B4-468F-9077-721274627F00@puck.nether.net>
References: <73ae5759-32a7-38fb-3232-9630a4dd6faa@gmail.com> <20170726222602.72dc27ab@spidey.rellim.com> <CABmDk8m3V7dPi-qNn3sig89_keOaepo29_GAyEr+__MjUrLLHA@mail.gmail.com> <4C169449-D1E2-4F9C-8163-CF3B5A067772@comcast.net> <CABmDk8kWr_NSh_r2JCeVST929UJVXFwPPkxAf9+k6_PBuQmmsw@mail.gmail.com> <45b53222-7c78-939d-3819-d567c70ea60e@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/j7w4-2tXH8ueK5SB3zaJimaDFEI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 22:58:38 -0000

Just go to your doctor and ask for a prescription for Sufafed. I did this be=
fore. It's generally illegal in most countries as it's not OTC. My doctor ha=
ppily wrote me a prescription for it with some generic instructions like tak=
e as needed.=20

Jared Mauch

> On Jul 27, 2017, at 7:00 PM, Brian E Carpenter <brian.e.carpenter@gmail.co=
m> wrote:
>=20
>> On 28/07/2017 01:49, Mary B wrote:
>> Yeah, I just came across that page.   Valium is also on that list - we
>> might have a lot of wide awake, anxious people at this meeting ;)     Tha=
t
>> page also mentions that Pseudoephedrine has limitations
>=20
> Pseudoephedrine is a precursor of methamphetamine and as such is a red
> flag in many countries. If I carry a decongestant, it's one based on
> phenylephrine.=20
>=20
>   Brian


From nobody Sun Jul 30 16:06:57 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD4B8131714 for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 16:06:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 LwNPHeQhjmQ5 for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 16:06:54 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B145131828 for <ietf@ietf.org>; Sun, 30 Jul 2017 16:06:53 -0700 (PDT)
Received: (qmail 44632 invoked from network); 30 Jul 2017 23:06:52 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 30 Jul 2017 23:06:52 -0000
Date: 30 Jul 2017 23:06:30 -0000
Message-ID: <20170730230630.985.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
In-Reply-To: <39FD84EA-4614-4331-B562-C9B2219FE949@fugue.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lcuowIkxsRA15y1MyiEtU2YDSnA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 23:06:56 -0000

In article <39FD84EA-4614-4331-B562-C9B2219FE949@fugue.com> you write:
>People who are forward-thinking (but not enough) in their use of DNSSEC and backward-thinking in their use of IPv6 will have problems.

Quite possibly, but so what.

If the IETF plans to treat what have historically been production
networks as experimental networks, please let us know so we can make
other plans, e.g., mifi from a local wireless carrier.

Even better, don't do that.

R's,
John


From nobody Sun Jul 30 16:11:28 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3275131935 for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 16:11:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 r6T5f9S9vKFD for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 16:11:25 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0BB1129B10 for <ietf@ietf.org>; Sun, 30 Jul 2017 16:11:25 -0700 (PDT)
Received: (qmail 44981 invoked from network); 30 Jul 2017 23:11:24 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 30 Jul 2017 23:11:24 -0000
Date: 30 Jul 2017 23:11:02 -0000
Message-ID: <20170730231102.1014.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
In-Reply-To: <m2y3r7gmb9.wl-randy@psg.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/L1HcXeeCXlD06sG_pdRxWkUkPV0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 23:11:27 -0000

In article <m2y3r7gmb9.wl-randy@psg.com> you write:
>the question is how to progress fixing nat64/dns64, given that a lot of
>folk come to ietf meetings to simply get work done and not debug a semi-
>working transport.  how about a bug bounty?  and maybe a fix bounty a
>few times larger!

A bug bounty on ietf-v6only, perhaps spiffy tee-shirts, would be a dandy idea.

Forcing the whole conference to participate would not.

R's,
John


From nobody Sun Jul 30 17:56:47 2017
Return-Path: <worley@alum.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BCD2127601 for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 17:56:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level: 
X-Spam-Status: No, score=-1.933 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, 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 DfuQ7Ag2-YUx for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 17:56:31 -0700 (PDT)
Received: from resqmta-ch2-12v.sys.comcast.net (resqmta-ch2-12v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:44]) (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 8D7C3131600 for <ietf@ietf.org>; Sun, 30 Jul 2017 17:56:30 -0700 (PDT)
Received: from resomta-ch2-08v.sys.comcast.net ([69.252.207.104]) by resqmta-ch2-12v.sys.comcast.net with ESMTP id bz0XdraUJVbF0bz0XdIeft; Mon, 31 Jul 2017 00:56:29 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-08v.sys.comcast.net with SMTP id bz0VdKDBNFVt8bz0Wdqt0p; Mon, 31 Jul 2017 00:56:29 +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 v6V0uRSa003558; Sun, 30 Jul 2017 20:56:27 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v6V0uQNr003555; Sun, 30 Jul 2017 20:56:26 -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: Dhruv Dhody <dhruv.dhody@huawei.com>
Cc: gen-art@ietf.org, draft-ietf-pce-pceps.all@ietf.org, pce@ietf.org, ietf@ietf.org, dhruv.ietf@gmail.com
Subject: Re: [Pce] Genart last call review of draft-ietf-pce-pceps-14
In-Reply-To: <23CE718903A838468A8B325B80962F9B8CB95DF7@blreml501-mbb> (dhruv.dhody@huawei.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Sun, 30 Jul 2017 20:56:26 -0400
Message-ID: <87379de85h.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfNGHrMV/tGkmygmWI5IRePHJtXqX3uLOLhLbpZdSkmRczGUQym/ZvG+Nqms6C2BERBO0JLgOlrBd9gVfa2jUiHC5kLFNUgibcHVdaRBYGXj1XEw44B1i yuEvM+TMVffGHuM+itU8q/WWqOnOR+SAxY4OaEqvQdCaRw8w/SvMyChH3W8AvzCpWrVyCbBiqoSJ+zSb3EOZ6rR6ZUP7AtjhvlnKpo3Fzu97+qcnqIDu8ysk 2RrNkZYReRGtFWJJHmmDH0Bni+ObyocW/VvmASMewlBHWAruWvoxeZtcSU+A/URo2zVAFYY356UFCSma351hAw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/enBFgKFKK8v9FwgDrml8AhAaeTc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 00:56:33 -0000

Dhruv Dhody <dhruv.dhody@huawei.com> writes:

The bulk of these items I either agree with completely or am willing to
defer to your judgment.  The items that seem to merit further
discussion are below.  Most of these items are consolidations of several
remarks I made that seem to be the same fundamental question.

>> section 3.2: whether error TBA2/2 is distinct from error 1/1 

> [[Dhruv Dhody]] The context of these error are different, one is
> before TLS establishment (startTLS) and another is during PCEP session
> establishment (which is after TLS has been established). IMHO it is
> better to keep them distinct. 

It's more complicated than that:  If a PCE does not like the first
message it receives, if it implements PCEPS, it replies TBA2/2.  But if
it does not implement PCEPS, it replies 1/1.  Similarly, a PCC may
reject an initial message with either of these error codes, depending on
the situation.  If the other endpoint does not implement PCEPS, it might
be surprised by receiving TBA2/2, which it has no way of understanding
in detail (although it will probably simply disconnect, which is what it
would do in reaction to a 1/1).

A non-implementing endpoint rejects an initial message only with 1/1.

OTOH, once TLS has been established, then both endpoints can only object
to the first encrypted message with 1/1.

There's nothing intrinsically incorrect about this, but it is rather
complicated, particularly in the upward-compatibility case where the PCC
is willing to accept either PCEPS-implementing or non-PCEPS-implementing
connections.

>> section 3.3: the distinction between StartTLSWait and OpenWait

> [[Dhruv Dhody]] Both timers are wait timers but they wait for
> different messages and used in different context. Also the values can
> be set differently based on the deployment. 

There's a complication if a PCE allows both PCEPS and PCEP connections.
In that case, it does not send its initial message until it receives a
message from the PCC.  If the message is StartTLS, the PCC wants to
connect using PCEPS and the PCE sends StartTLS; if the message is Open,
the PCC wants to connect using PCEP and the PCE sends Open.

The question is, what timeout does the PCE use while waiting for the
initial message?  If the connection *will be* PCEPS, it should use
StartTLSWait (per draft-ietf-pce-pceps), if the connection *will be*
PCEP, it should use OpenWait (per RFC 5440).  But it does not have the
information to choose the timer.  The difficulty is that initially, the
PCE is simulating both a PCEP and a PCEPS device, and using the message
it receives from the PCC to disambiguate its situation.  But the timeout
values prescribed for the two situations are different.

My feeling is that the two situations -- waiting for Open and waiting
for StartTLS -- are not sufficiently distinguishable to allow
prescribing two different timers.  Of course, this could be cured by
proper configuration -- giving the same value to StartTLSWait and
OpenWait.

OTOH, once TLS has been established and the Open messages are awaited,
both endpoints use OpenWait.  However, this situation is not really the
same as when the TCP connection has been just been established.  And
yet, a PCE may be obligated to use the same timer for both situations.

>> 3.2.  Initiating the TLS Procedures
...
> Do you feel strongly about changing this? 

Of course, I'm only a reviewer, you needn't defer to my opinion about
anything.

>> Is there a well-defined way for a participant in a TLS connection start to
>> receive *either* a PCErr message in the clear *or* whatever comes next in
>> TLS setup -- and know which case has happened?  Is there a way to use
>> popular modular TLS libraries and have the application above the library
>> receive such a PCErr message?  I don't understand TLS nearly well enough
>> to know the answer to this, but it would probably help implementors if
>> answers were given to these questions.
>
> [[Dhruv Dhody]] If the TLS handshake is successful, both local and
> remote parties are aware of this. Same is the case for TLS failure. So
> receiving an error message in clear will not be a surprise. 
>
> Also, I checked some of the other documents that describe the use of
> TLS, but did not find any such handling. 

OK, I think I understand now; my previous comment was based on a
misunderstanding.  The correct sequence of operations for PCEPS
setup is:  Both endpoints send a StartTLS to each other.  After that, the
initiator starts the TLS setup.  Alternatively, the PCC sends StartTLS
and the non-PCEPS-implementing PCE sends a PCErr.  In either case, the
PCC sends a StartTLS and then listens for a PCEP message in response.
In any case, neither endpoint is ever in a situation where it could
receive either a PCEP message or a TLS setup message.

>> 5.  Backward Compatibility
...
> [[Dhruv Dhody]] Updated. 
>
>    If a PCEP implementation that does not support PCEPS receives a
>    StartTLS message, ...

I think this is a significant improvement, as you can never be too
careful about upward-compatibility issues, especially when security is
involved.

--

Concerning the figures:

                  +-+-+                 +-+-+
                  |PCC|                 |PCE|
                  +-+-+                 +-+-+
                    |                     | Does not send
                    |      StartTLS       | StartTLS as
                    |-------------------->| cannot establish
                    |                     | TLS
                    |                     |
                    |<--------------------| Send Error
                    |      PCErr          | Error-Value 3/4
                    |                     |


   Figure 2: Both PCEP Speaker supports PCEPS, But cannot establish TLS


                  +-+-+                 +-+-+
                  |PCC|                 |PCE|
                  +-+-+                 +-+-+
                    |                     |  Does not support
                    | StartTLS            |  PCEPS and thus
                    | msg                 |  sends Open
                    |-------              |
                    |       \   Open      |
                    |        \  msg       |
                    |         \  ---------|
                    |          \/         |
                    |          /\         |
                    |         /  -------->|
                    |        /            |
                    |<------              |
                    |                     |
                    |<--------------------| Send Error
                    |       PCErr         | (non-Open message
                    |                     |  received)


             Figure 3: One PCEP Speaker does not support PCEPS

IIUC, in Figure 2 the error has error-value 3/4 and is "Not supported
object" ... is that right?  I'd think it would be TBA2/4, "Failure,
connection without TLS possible" (or TBA2/3, depending on
circumstances).  And in Figure 3, the error is 1/1.  It seems like it
would be clearer if both the number and the text were shown for the
error messages in both the figures.

Is there also this flow?

                  +-+-+                 +-+-+
                  |PCC|                 |PCE|
                  +-+-+                 +-+-+
                    |                     |  Does not support
                    | StartTLS            |  PCEPS and thus
                    | msg                 |  sends Open
                    |-------              |
                    |       \   Open      |
                    |        \  msg       |
                    |         \  ---------|
                    |          \/         |
                    |          /\         |
                    |         /  -------->|
                    |        /            |
                    |<------              |
                    |                     |
                    |-------------------->|
                    |       PCErr         |
                    |                     |

Where the error indicates "Expecting a StartTLS but received an Open"?
Or is this situation always signaled by the receiver (as in Figure 3)
rather than the initiator?

Dale


From nobody Sun Jul 30 20:55:29 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73F2E131D6F for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 20:55:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 D86TVY1ikx_j for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 20:55:26 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 4C2AF131D6D for <ietf@ietf.org>; Sun, 30 Jul 2017 20:55:26 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dc1nf-0004eU-RY; Mon, 31 Jul 2017 03:55:24 +0000
Date: Mon, 31 Jul 2017 12:55:22 +0900
Message-ID: <m2y3r5w991.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: "John Levine" <johnl@taugh.com>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
In-Reply-To: <20170730231102.1014.qmail@ary.lan>
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/C9CX9JsKYtY4nVhNR-RgdgjF2Rg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 03:55:27 -0000

>> the question is how to progress fixing nat64/dns64, given that a lot
>> of folk come to ietf meetings to simply get work done and not debug a
>> semi- working transport.  how about a bug bounty?  and maybe a fix
>> bounty a few times larger!
> A bug bounty on ietf-v6only, perhaps spiffy tee-shirts, would be a
> dandy idea.

someone suggested a tee shirt if you stayed on v6only and/or nat64 all
week.  and a further prize if you found a new solution to a common
problem on those networks.

someone else suggested that we turn off all other ssids for the 6man and
v6ops wg meetings.  there would be leakage, of course.  and it's a pita
(we *really* do not like to make changes during the week).  perhaps the
chairs could strongly encourage those in the wg meetings to use either
v6only or nat64.

> Forcing the whole conference to participate would not.

doh

my impression is that the noc, for which i do not speak, jim does, has
been strongly of the idea that the job is a network where people can get
their work done with absolutely minimal speedbumps.  tragically and, for
some of us, enragingly, v6only and nat64 do not meet that bar; dual
stack seems to.

[ btw, i should confess that, despite continuing efforts which have
  eaten a lot of my copious free time, i still do not have ipv6 in our
  tokyo apartment.  ntt-east (the carrier, not the internet provider)
  has worked quite hard to inhibit consumer ipv6 deployment in japan.
  ask lorenzo or erik for a more detailed rant than i can give.

  on bainbridge, john gives us great native ipv6 and nat44able ipv4.
  thank you, john.
  ]

randy


From nobody Sun Jul 30 22:00:08 2017
Return-Path: <oritl@microsoft.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 87B3B131748; Sun, 30 Jul 2017 21:59:54 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Orit Levin <oritl@microsoft.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-curdle-ssh-modp-dh-sha2.all@ietf.org, curdle@ietf.org, ietf@ietf.org
Subject: Genart last call review of draft-ietf-curdle-ssh-modp-dh-sha2-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.57.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150147719452.17668.11130233205318099796@ietfa.amsl.com>
Date: Sun, 30 Jul 2017 21:59:54 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tXBn7lFI3rdpV9cl18KoqIWZJ5c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 04:59:55 -0000

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 Sun Jul 30 23:10:18 2017
Return-Path: <swmike@swm.pp.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46A1812706D for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 23:10:16 -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, RP_MATCHES_RCVD=-0.001, 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=swm.pp.se
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 PZtz3_jicun2 for <ietf@ietfa.amsl.com>; Sun, 30 Jul 2017 23:10:14 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (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 52FFD126C0F for <ietf@ietf.org>; Sun, 30 Jul 2017 23:10:13 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 1AC61A3; Mon, 31 Jul 2017 08:10:11 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1501481411; bh=x2mAZCDDTTM9Hy+BthsiF2pjip7qCv3QmVCZREkEhYU=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=S89Y1qvvEZ38pUp8pznfdPv//zi/K5yv20DNuvdbBCw4lJrQrJWe2Ed5E2LWCp/5Y /4ft8tUE3KdYW0kVwAxoZH4zfX89iJ6MFgTVd42KGsRsq1uhJJtVfXkxEyoNq23kup rJ3etkDDoR1btp1Sphqi0C35puYeGF//0njyS57Y=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 17352A1; Mon, 31 Jul 2017 08:10:11 +0200 (CEST)
Date: Mon, 31 Jul 2017 08:10:11 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Randy Bush <randy@psg.com>
cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
In-Reply-To: <m2y3r5w991.wl-randy@psg.com>
Message-ID: <alpine.DEB.2.02.1707310807010.29742@uplift.swm.pp.se>
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fGIDb2UQ3bnVoP1fNNqNw09EhlU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 06:10:16 -0000

On Mon, 31 Jul 2017, Randy Bush wrote:

> someone suggested a tee shirt if you stayed on v6only and/or nat64 all 
> week.  and a further prize if you found a new solution to a common 
> problem on those networks.

I could do this with my Android or iOS-device all week and feel no pain 
what so ever. It just works. That would be a lot of T-shirts.

However, if someone did this with their Windows or MacOS machine, that'd 
be a much bigger feat. I would personally buy $DRINK to whoever came up 
with a user-friendly installable CLAT solution for these OSes, and would 
whole-heartedly support giving T-shirts to people actually testing out 
this software all week, and reporting problems.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Mon Jul 31 03:05:37 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10169132066 for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 03:05:36 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 8aTomACZMY03 for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 03:05:34 -0700 (PDT)
Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (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 31A53128961 for <ietf@ietf.org>; Mon, 31 Jul 2017 03:05:34 -0700 (PDT)
Received: by mail-qk0-x22b.google.com with SMTP id u139so83085968qka.1 for <ietf@ietf.org>; Mon, 31 Jul 2017 03:05:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=DlZDYSdmlP3rM1n3LWF1RQjijMTaRfRWqxke7uJR+6g=; b=qcgXQeuwSFJLR3PR/StyejqKLQNbnclmh6HuznMdnkBni6XyQpeZom4teunSTwZnEU sRyb/ykxgDLO62D3NwudJCv9FrAUIyU3JOz+V7sFpaykrvLKBT8snzC/0Ejcx67R8ama zXB3I4na0xVMd+ctU4CxKJ4uLEEVg2Ckf0BgzvurKahEG9bv897C17KyAvty4mUdMh23 Yx1LNWQmIatuNOJ+XrmFP4SB1mt/tA2SKw4FHlShHM5M344pL9AXvLENyF2oHwp4jL3M rcXJnKZoz73beLxV5SomgRN5u5c/zFYQoJt/2slyFs5IPF1qIIQjYuzAqDuU0UT9uto6 ar/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=DlZDYSdmlP3rM1n3LWF1RQjijMTaRfRWqxke7uJR+6g=; b=GcZqwkYQ8Y1K9qI5+M+ir0isHoiNeF8IEpYVfiOwIaa7C4daGsxZPwZ16Fvz2ZiMAd CG8q4N/koAOuBrIB3DXADU0He0RnD3zZT+UGrPPzMglsVuRR6IS3l4QygkX3WeDK3B4H Y/+je7DPjOJD8irwCSjfN4rCN78C/UFzznjZpjGvU6BhyaRoDOG9R5ArGzX1hA2pYqZq PK+AIftsayVrKAPZK5fFra+HPDahf/oMlJyBIG9fHcwbIz1aJ6Y3qYl7yKOOMmaRqfGY l/yYK0FBu5IGUqo8WZxrzJwfkZkIKtRH/RYj3E+o2/YbIcFF9C2xm5s4DWOsqNKdFv/Q sIoQ==
X-Gm-Message-State: AIVw112bjLWC7DWim95Ycetv/cuEth9Yh+8MVYItR3ssXEsNPwGgXXGY kWQvLSBq0YtKoq25MFll+w==
X-Received: by 10.55.24.146 with SMTP id 18mr19578755qky.190.1501495533017; Mon, 31 Jul 2017 03:05:33 -0700 (PDT)
Received: from [10.0.30.153] (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id h42sm2435674qtb.97.2017.07.31.03.05.31 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 31 Jul 2017 03:05:32 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F757CD79-7CF9-4F70-9DA5-01A0174EA206"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Mon, 31 Jul 2017 06:05:30 -0400
References: <20170730231102.1014.qmail@ary.lan>
To: IETF Rinse Repeat <ietf@ietf.org>
In-Reply-To: <20170730231102.1014.qmail@ary.lan>
Message-Id: <6776ADFB-3EE0-4227-8A0F-7D140F7EB9F6@fugue.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Irvl0KPFhxDKtaFZUz7iLTC_cVE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 10:05:36 -0000

--Apple-Mail=_F757CD79-7CF9-4F70-9DA5-01A0174EA206
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jul 30, 2017, at 7:11 PM, John Levine <johnl@taugh.com> wrote:
> Forcing the whole conference to participate would not.

I would just like to point out that nobody here has proposed forcing the =
whole conference to participate.   What the draft proposes is changing =
the _default_, not making non-NAT64 IPv4 service unavailable.

On Jul 30, 2017, at 11:55 PM, Randy Bush <randy@psg.com> wrote:
> someone else suggested that we turn off all other ssids for the 6man =
and
> v6ops wg meetings.  there would be leakage, of course.  and it's a =
pita
> (we *really* do not like to make changes during the week).  perhaps =
the
> chairs could strongly encourage those in the wg meetings to use either
> v6only or nat64.

I don't see the point.   We already know that NAT64 mostly works, and we =
know when it breaks, and why.   The only really interesting question is =
how many people this breakage affects, and what specific apps break.

> On Jul 30, 2017, at 10:44 AM, Bill Fenner <fenner@fenron.com> wrote:
>> On the other hand, the corporate VPN I use publishes a support matrix =
on their public web site, and specifically says that IPv6 is not =
supported. I don't think they're embarrassed about it.

Would you be willing to share with us the name of the vendor?


--Apple-Mail=_F757CD79-7CF9-4F70-9DA5-01A0174EA206
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jul 30, 2017, at 7:11 PM, John Levine &lt;<a =
href=3D"mailto:johnl@taugh.com" class=3D"">johnl@taugh.com</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">Forcing the whole =
conference to participate would not.</span><br style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""></div></blockquote></div><br class=3D""><div class=3D"">I =
would just like to point out that nobody here has proposed forcing the =
whole conference to participate. &nbsp; What the draft proposes is =
changing the _default_, not making non-NAT64 IPv4 service =
unavailable.</div><div class=3D""><br class=3D""></div><div class=3D"">On =
Jul 30, 2017, at 11:55 PM, Randy Bush &lt;<a href=3D"mailto:randy@psg.com"=
 class=3D"">randy@psg.com</a>&gt; wrote:<br class=3D""><div><blockquote =
type=3D"cite" class=3D"">someone else suggested that we turn off all =
other ssids for the 6man and<br class=3D""><div class=3D"">v6ops wg =
meetings. &nbsp;there would be leakage, of course. &nbsp;and it's a =
pita<br class=3D"">(we *really* do not like to make changes during the =
week). &nbsp;perhaps the<br class=3D"">chairs could strongly encourage =
those in the wg meetings to use either<br class=3D"">v6only or nat64.<br =
class=3D""></div></blockquote><div class=3D""><div class=3D""><br =
class=3D""></div></div><div class=3D"">I don't see the point. &nbsp; We =
already know that NAT64 mostly works, and we know when it breaks, and =
why. &nbsp; The only really interesting question is how many people this =
breakage affects, and what specific apps break.</div><div class=3D""><br =
class=3D""></div><div class=3D""><blockquote type=3D"cite" class=3D"">On =
Jul 30, 2017, at 10:44 AM, Bill Fenner &lt;<a =
href=3D"mailto:fenner@fenron.com" class=3D"">fenner@fenron.com</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D"">On the =
other hand, the corporate VPN I use publishes a support matrix on their =
public web site, and specifically says that IPv6 is not supported. I =
don't think they're embarrassed about =
it.</div></blockquote></div></blockquote><br class=3D""></div><div =
class=3D"">Would you be willing to share with us the name of the =
vendor?</div><div class=3D""><br =
class=3D""></div></div></div></body></html>=

--Apple-Mail=_F757CD79-7CF9-4F70-9DA5-01A0174EA206--


From nobody Mon Jul 31 06:25:13 2017
Return-Path: <rsk@gsp.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B75F013229A for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 06:25:11 -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 ZG2Pah2vCWEc for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 06:25:10 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) (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 2E600132250 for <ietf@ietf.org>; Mon, 31 Jul 2017 06:25:10 -0700 (PDT)
Received: from gsp.org (localhost [127.0.0.1]) by taos.firemountain.net (8.15.1/8.14.9) with SMTP id v6VDP8QU009999 for <ietf@ietf.org>; Mon, 31 Jul 2017 09:25:08 -0400 (EDT)
Date: Mon, 31 Jul 2017 09:25:08 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: Next steps in IETF list email archiving
Message-ID: <20170731132508.GA22575@gsp.org>
References: <fe950cd9-bea8-7831-046d-2f48eaaeafb9@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <fe950cd9-bea8-7831-046d-2f48eaaeafb9@nostrum.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5-B-_J10DBJDI6Mq4waTqGztb0Q>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 13:25:12 -0000

This is partially tangential, but:

One of the best approaches to ensure the long-term preservation of these
archives is to (1) keep them in an open, standard, widely-supported
format -- "mbox" is clearly the best choice and (2) make them trivially
easy to mirror.  This has the desirable effect of allowing who wishes
to maintain their own copy and/or to use the search engine of their
choice on it.  (In my case, I find "grepmail" to be highly useful for
searching mail archives: it's better than anything else I've tried,
and I've tried a lot of things.)

It also allows folks to access the archives when disconnected from the
'net or when they're on a slow/expensive connection.  The former is
more than merely a matter of convenience: in some working environments:
it's a requirement, e.g., in environments that are always physically
disconnected from the 'net.

So whatever presentation format is chosen, the original/raw mbox files
should be available for download via -- at least -- https and rsync.
Gzip'd tarballs of them should be regenerated nightly and also made
available -- on a per-mailing-list basis and globally.  (To make that
clear: the latter means that it should be possible to download a single
gzip'd tarball that contains all archives of all IETF mailing lists.
Not only is that useful in its own right, but it'd be an excellent
way to initialize a mirror that can be subsequently maintained via rsync.)

A back-of-the-envelope calculation suggests that the complete archives of
all IETF mailing lists rendered as a gzip'd tarball would fit comfortably
on a 32G USB stick.

None of this is particularly hard to script and automate via cron: I've
set up similar things many times.  I'd be happy to do the work if nobody
else can spare the time.

---rsk


From nobody Mon Jul 31 06:36:42 2017
Return-Path: <dhruv.dhody@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C55313229E; Mon, 31 Jul 2017 06:36:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.819
X-Spam-Level: 
X-Spam-Status: No, score=-2.819 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_COMMENT_SAVED_URL=1.391, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, T_HTML_ATTACH=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 Fw_ogWTNCuSg; Mon, 31 Jul 2017 06:36:14 -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 23BF312EA95; Mon, 31 Jul 2017 06:36:12 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml701-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DSK43203; Mon, 31 Jul 2017 13:36:09 +0000 (GMT)
Received: from BLREML703-CAH.china.huawei.com (10.20.4.172) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 31 Jul 2017 14:36:03 +0100
Received: from BLREML501-MBB.china.huawei.com ([10.20.5.200]) by blreml703-cah.china.huawei.com ([::1]) with mapi id 14.03.0301.000; Mon, 31 Jul 2017 19:05:51 +0530
From: Dhruv Dhody <dhruv.dhody@huawei.com>
To: "'Dale R. Worley'" <worley@ariadne.com>
CC: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-pce-pceps.all@ietf.org" <draft-ietf-pce-pceps.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "dhruv.ietf@gmail.com" <dhruv.ietf@gmail.com>
Subject: RE: [Pce] Genart last call review of draft-ietf-pce-pceps-14
Thread-Topic: [Pce] Genart last call review of draft-ietf-pce-pceps-14
Thread-Index: AQHTCZfWzqPRSDFqSU+m/UcLVejzmaJtQ7rA
Date: Mon, 31 Jul 2017 13:35:50 +0000
Message-ID: <23CE718903A838468A8B325B80962F9B8CB962D9@blreml501-mbb>
References: <23CE718903A838468A8B325B80962F9B8CB95DF7@blreml501-mbb> (dhruv.dhody@huawei.com) <87379de85h.fsf@hobgoblin.ariadne.com>
In-Reply-To: <87379de85h.fsf@hobgoblin.ariadne.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.77.55]
Content-Type: multipart/mixed; boundary="_003_23CE718903A838468A8B325B80962F9B8CB962D9blreml501mbb_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.597F324A.00F1, ss=1, re=0.000, recu=0.000, reip=0.000,  vtr=str, vl=0, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 97a2993c040c166ea2819edd2dfdf4b1
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/U24NUH5pSel62FvfRHDjPDDbMGU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 13:36:20 -0000

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

Hi Dale,

Thanks for your further comments, please see inline..

> -----Original Message-----
> From: Dale R. Worley [mailto:worley@ariadne.com]
> Sent: 31 July 2017 06:26
> To: Dhruv Dhody <dhruv.dhody@huawei.com>
> Cc: gen-art@ietf.org; draft-ietf-pce-pceps.all@ietf.org; pce@ietf.org;
> ietf@ietf.org; dhruv.ietf@gmail.com
> Subject: Re: [Pce] Genart last call review of draft-ietf-pce-pceps-14
>=20
> Dhruv Dhody <dhruv.dhody@huawei.com> writes:
>=20
> The bulk of these items I either agree with completely or am willing to
> defer to your judgment.  The items that seem to merit further discussion
> are below.  Most of these items are consolidations of several remarks I
> made that seem to be the same fundamental question.
>=20
> >> section 3.2: whether error TBA2/2 is distinct from error 1/1
>=20
> > [[Dhruv Dhody]] The context of these error are different, one is
> > before TLS establishment (startTLS) and another is during PCEP session
> > establishment (which is after TLS has been established). IMHO it is
> > better to keep them distinct.
>=20
> It's more complicated than that:  If a PCE does not like the first messag=
e
> it receives, if it implements PCEPS, it replies TBA2/2.  But if it does
> not implement PCEPS, it replies 1/1.  Similarly, a PCC may reject an
> initial message with either of these error codes, depending on the
> situation.  If the other endpoint does not implement PCEPS, it might be
> surprised by receiving TBA2/2, which it has no way of understanding in
> detail (although it will probably simply disconnect, which is what it
> would do in reaction to a 1/1).
>=20
[[Dhruv Dhody]] You are right about this case, which I have clarified now -=
 =20

   If the PCEP speaker that only supports PCEPS connection (as a local
   policy), receives an Open message, it MUST treat it as an unexpected
   message and reply with a PCErr message with Error-Type set to 1 (PCEP
   session establishment failure) and Error-value set to 1 (reception of
   an invalid Open message or a non Open message).

In your description you mentioned the error TBA2/2, but the description of =
TBA2/2 is  -=20

   A PCEP
   speaker receiving any other message apart from StartTLS, Open, or
   PCErr as the first message, MUST treat it as an unexpected message
   and reply with a PCErr message with Error-Type set to [TBA2 by IANA]
   (PCEP StartTLS failure) and Error-value set to 2 (reception of any
   other message apart from StartTLS, Open, or PCErr message), and MUST
   close the TCP connection.

So receiving of open message would not trigger this error. The new text abo=
ve would take care of that.=20

> A non-implementing endpoint rejects an initial message only with 1/1.
>=20
> OTOH, once TLS has been established, then both endpoints can only object
> to the first encrypted message with 1/1.
>=20
> There's nothing intrinsically incorrect about this, but it is rather
> complicated, particularly in the upward-compatibility case where the PCC
> is willing to accept either PCEPS-implementing or non-PCEPS-implementing
> connections.
>=20
[[Dhruv Dhody]] I have created a table that describe all the cases as part =
the updated text. =20
See https://github.com/dhruvdhody-huawei/ietf/raw/master/Compare.pdf=20

> >> section 3.3: the distinction between StartTLSWait and OpenWait
>=20
> > [[Dhruv Dhody]] Both timers are wait timers but they wait for
> > different messages and used in different context. Also the values can
> > be set differently based on the deployment.
>=20
> There's a complication if a PCE allows both PCEPS and PCEP connections.
> In that case, it does not send its initial message until it receives a
> message from the PCC.  If the message is StartTLS, the PCC wants to
> connect using PCEPS and the PCE sends StartTLS; if the message is Open,
> the PCC wants to connect using PCEP and the PCE sends Open.
>=20
> The question is, what timeout does the PCE use while waiting for the
> initial message?  If the connection *will be* PCEPS, it should use
> StartTLSWait (per draft-ietf-pce-pceps), if the connection *will be* PCEP=
,
> it should use OpenWait (per RFC 5440).  But it does not have the
> information to choose the timer.  The difficulty is that initially, the
> PCE is simulating both a PCEP and a PCEPS device, and using the message i=
t
> receives from the PCC to disambiguate its situation.  But the timeout
> values prescribed for the two situations are different.
>=20
> My feeling is that the two situations -- waiting for Open and waiting for
> StartTLS -- are not sufficiently distinguishable to allow prescribing two
> different timers.  Of course, this could be cured by proper configuration
> -- giving the same value to StartTLSWait and OpenWait.
>=20
> OTOH, once TLS has been established and the Open messages are awaited,
> both endpoints use OpenWait.  However, this situation is not really the
> same as when the TCP connection has been just been established.  And yet,
> a PCE may be obligated to use the same timer for both situations.
>=20
[[Dhruv Dhody]] You have noted something important, thanks for that.=20

I would like to fix this by making sure that a PCEP speaker that supports P=
CEPS does not start OpenWait timer immediately after TCP session, it uses S=
tartTLSWait timer instead.=20
I would clarify that the OpenWait timer should be started after TLS establi=
shment only.=20

So a PCE that supports connection with TLS only or with/without TLS, it wou=
ld use StartTLSWait timer initially, the OpenWait timer is started once the=
 TLS is established.=20
I also state the StartTLSWait should never be set less than OpenWait timer.=
=20

Please see the diff, I hope these changes should solve the issue. =20

> >> 3.2.  Initiating the TLS Procedures
> ...
> > Do you feel strongly about changing this?
>=20
> Of course, I'm only a reviewer, you needn't defer to my opinion about
> anything.
>=20
> >> Is there a well-defined way for a participant in a TLS connection
> >> start to receive *either* a PCErr message in the clear *or* whatever
> >> comes next in TLS setup -- and know which case has happened?  Is
> >> there a way to use popular modular TLS libraries and have the
> >> application above the library receive such a PCErr message?  I don't
> >> understand TLS nearly well enough to know the answer to this, but it
> >> would probably help implementors if answers were given to these
> questions.
> >
> > [[Dhruv Dhody]] If the TLS handshake is successful, both local and
> > remote parties are aware of this. Same is the case for TLS failure. So
> > receiving an error message in clear will not be a surprise.
> >
> > Also, I checked some of the other documents that describe the use of
> > TLS, but did not find any such handling.
>=20
> OK, I think I understand now; my previous comment was based on a
> misunderstanding.  The correct sequence of operations for PCEPS setup is:
> Both endpoints send a StartTLS to each other.  After that, the initiator
> starts the TLS setup.  Alternatively, the PCC sends StartTLS and the non-
> PCEPS-implementing PCE sends a PCErr.  In either case, the PCC sends a
> StartTLS and then listens for a PCEP message in response.
> In any case, neither endpoint is ever in a situation where it could
> receive either a PCEP message or a TLS setup message.
>=20
> >> 5.  Backward Compatibility
> ...
> > [[Dhruv Dhody]] Updated.
> >
> >    If a PCEP implementation that does not support PCEPS receives a
> >    StartTLS message, ...
>=20
> I think this is a significant improvement, as you can never be too carefu=
l
> about upward-compatibility issues, especially when security is involved.
>=20
> --
>=20
> Concerning the figures:
>=20
>                   +-+-+                 +-+-+
>                   |PCC|                 |PCE|
>                   +-+-+                 +-+-+
>                     |                     | Does not send
>                     |      StartTLS       | StartTLS as
>                     |-------------------->| cannot establish
>                     |                     | TLS
>                     |                     |
>                     |<--------------------| Send Error
>                     |      PCErr          | Error-Value 3/4
>                     |                     |
>=20
>=20
>    Figure 2: Both PCEP Speaker supports PCEPS, But cannot establish TLS
>=20
>=20
>                   +-+-+                 +-+-+
>                   |PCC|                 |PCE|
>                   +-+-+                 +-+-+
>                     |                     |  Does not support
>                     | StartTLS            |  PCEPS and thus
>                     | msg                 |  sends Open
>                     |-------              |
>                     |       \   Open      |
>                     |        \  msg       |
>                     |         \  ---------|
>                     |          \/         |
>                     |          /\         |
>                     |         /  -------->|
>                     |        /            |
>                     |<------              |
>                     |                     |
>                     |<--------------------| Send Error
>                     |       PCErr         | (non-Open message
>                     |                     |  received)
>=20
>=20
>              Figure 3: One PCEP Speaker does not support PCEPS
>=20
> IIUC, in Figure 2 the error has error-value 3/4 and is "Not supported
> object" ... is that right?  I'd think it would be TBA2/4, "Failure,
> connection without TLS possible" (or TBA2/3, depending on circumstances).
> And in Figure 3, the error is 1/1.  It seems like it would be clearer if
> both the number and the text were shown for the error messages in both th=
e
> figures.
>=20
[[Dhruv Dhody]] Error-Value 3/4 meant Error TBA2/3 and Error TBA2/4 as I wa=
s focusing only on the error-values and not on error-type, but I agree this=
 could be confusing and I have updated the figures. Also I have added some =
more figures.=20

> Is there also this flow?
>=20
>                   +-+-+                 +-+-+
>                   |PCC|                 |PCE|
>                   +-+-+                 +-+-+
>                     |                     |  Does not support
>                     | StartTLS            |  PCEPS and thus
>                     | msg                 |  sends Open
>                     |-------              |
>                     |       \   Open      |
>                     |        \  msg       |
>                     |         \  ---------|
>                     |          \/         |
>                     |          /\         |
>                     |         /  -------->|
>                     |        /            |
>                     |<------              |
>                     |                     |
>                     |-------------------->|
>                     |       PCErr         |
>                     |                     |
>=20
> Where the error indicates "Expecting a StartTLS but received an Open"?
> Or is this situation always signaled by the receiver (as in Figure 3)
> rather than the initiator?

 [[Dhruv Dhody]] The text has been added which is generic and works for bot=
h PCC/PCE. =20

I don't think we need a figure for that :)

Thanks again for your reviews.=20

The diff between the last update and this is attached.=20

Working copy, Diff: https://github.com/dhruvdhody-huawei/ietf

Regards,
Dhruv=20
 =20
>=20
> Dale

--_003_23CE718903A838468A8B325B80962F9B8CB962D9blreml501mbb_
Content-Type: text/html; name="Diff_ draft-ietf-pce-pceps-15-old.txt -
 draft-ietf-pce-pceps-15.txt.html"
Content-Description: Diff_ draft-ietf-pce-pceps-15-old.txt -
 draft-ietf-pce-pceps-15.txt.html
Content-Disposition: attachment; filename="Diff_
 draft-ietf-pce-pceps-15-old.txt - draft-ietf-pce-pceps-15.txt.html";
	size=91462; creation-date="Mon, 31 Jul 2017 13:26:35 GMT";
	modification-date="Mon, 31 Jul 2017 13:26:35 GMT"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIGh0bWwgUFVCTElDICItLy9XM0MvL0RURCBYSFRNTCAxLjAgVHJhbnNpdGlvbmFs
Ly9FTiIgImh0dHA6Ly93d3cudzMub3JnL1RSL3hodG1sMS9EVEQveGh0bWwxLXRyYW5zaXRpb25h
bC5kdGQiPgo8IS0tIHNhdmVkIGZyb20gdXJsPSgwMDMwKWh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcv
cmZjZGlmZiAtLT4KPGh0bWwgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkveGh0bWwiPjxo
ZWFkPjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0idGV4dC9odG1sOyBj
aGFyc2V0PVVURi04Ij4gCiAgIAogIDxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtU3R5bGUtVHlw
ZSIgY29udGVudD0idGV4dC9jc3MiPiAKICA8dGl0bGU+RGlmZjogZHJhZnQtaWV0Zi1wY2UtcGNl
cHMtMTUtb2xkLnR4dCAtIGRyYWZ0LWlldGYtcGNlLXBjZXBzLTE1LnR4dDwvdGl0bGU+IAogIDxz
dHlsZSB0eXBlPSJ0ZXh0L2NzcyI+IAogICAgYm9keSAgICB7IG1hcmdpbjogMC40ZXg7IG1hcmdp
bi1yaWdodDogYXV0bzsgfSAKICAgIHRyICAgICAgeyB9IAogICAgdGQgICAgICB7IHdoaXRlLXNw
YWNlOiBwcmU7IGZvbnQtZmFtaWx5OiBtb25vc3BhY2U7IHZlcnRpY2FsLWFsaWduOiB0b3A7IGZv
bnQtc2l6ZTogMC44NmVtO30gCiAgICB0aCAgICAgIHsgZm9udC1zaXplOiAwLjg2ZW07IH0gCiAg
ICAuc21hbGwgIHsgZm9udC1zaXplOiAwLjZlbTsgZm9udC1zdHlsZTogaXRhbGljOyBmb250LWZh
bWlseTogVmVyZGFuYSwgSGVsdmV0aWNhLCBzYW5zLXNlcmlmOyB9IAogICAgLmxlZnQgICB7IGJh
Y2tncm91bmQtY29sb3I6ICNFRUU7IH0gCiAgICAucmlnaHQgIHsgYmFja2dyb3VuZC1jb2xvcjog
I0ZGRjsgfSAKICAgIC5kaWZmICAgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjQ0NGOyB9IAogICAgLmxi
bG9jayB7IGJhY2tncm91bmQtY29sb3I6ICNCRkI7IH0gCiAgICAucmJsb2NrIHsgYmFja2dyb3Vu
ZC1jb2xvcjogI0ZGODsgfSAKICAgIC5pbnNlcnQgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjOEZGOyB9
IAogICAgLmRlbGV0ZSB7IGJhY2tncm91bmQtY29sb3I6ICNBQ0Y7IH0gCiAgICAudm9pZCAgIHsg
YmFja2dyb3VuZC1jb2xvcjogI0ZGQjsgfSAKICAgIC5jb250ICAgeyBiYWNrZ3JvdW5kLWNvbG9y
OiAjRUVFOyB9IAogICAgLmxpbmViciB7IGJhY2tncm91bmQtY29sb3I6ICNBQUE7IH0gCiAgICAu
bGluZW5vIHsgY29sb3I6IHJlZDsgYmFja2dyb3VuZC1jb2xvcjogI0ZGRjsgZm9udC1zaXplOiAw
LjdlbTsgdGV4dC1hbGlnbjogcmlnaHQ7IHBhZGRpbmc6IDAgMnB4OyB9IAogICAgLmVsaXBzaXN7
IGJhY2tncm91bmQtY29sb3I6ICNBQUE7IH0gCiAgICAubGVmdCAuY29udCB7IGJhY2tncm91bmQt
Y29sb3I6ICNEREQ7IH0gCiAgICAucmlnaHQgLmNvbnQgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjRUVF
OyB9IAogICAgLmxibG9jayAuY29udCB7IGJhY2tncm91bmQtY29sb3I6ICM5RDk7IH0gCiAgICAu
cmJsb2NrIC5jb250IHsgYmFja2dyb3VuZC1jb2xvcjogI0RENjsgfSAKICAgIC5pbnNlcnQgLmNv
bnQgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjMEREOyB9IAogICAgLmRlbGV0ZSAuY29udCB7IGJhY2tn
cm91bmQtY29sb3I6ICM4QUQ7IH0gCiAgICAuc3RhdHMsIC5zdGF0cyB0ZCwgLnN0YXRzIHRoIHsg
YmFja2dyb3VuZC1jb2xvcjogI0VFRTsgcGFkZGluZzogMnB4IDA7IH0gCiAgICBzcGFuLmhpZGUg
eyBkaXNwbGF5OiBub25lOyBjb2xvcjogI2FhYTt9ICAgIGE6aG92ZXIgc3BhbiB7IGRpc3BsYXk6
IGlubGluZTsgfSAgICB0ci5jaGFuZ2UgeyBiYWNrZ3JvdW5kLWNvbG9yOiBncmF5OyB9IAogICAg
dHIuY2hhbmdlIGEgeyB0ZXh0LWRlY29yYXRpb246IG5vbmU7IGNvbG9yOiBibGFjayB9IAogIDwv
c3R5bGU+IAogICAgIDxzY3JpcHQ+CnZhciBjaHVua19pbmRleCA9IDA7CnZhciBvbGRfY2h1bmsg
PSBudWxsOwoKZnVuY3Rpb24gZm9ybWF0X2NodW5rKGluZGV4KSB7CiAgICB2YXIgcHJlZml4ID0g
ImRpZmYiOwogICAgdmFyIHN0ciA9IGluZGV4LnRvU3RyaW5nKCk7CiAgICBmb3IgKHg9MDsgeDwo
NC1zdHIubGVuZ3RoKTsgKyt4KSB7CiAgICAgICAgcHJlZml4Kz0nMCc7CiAgICB9CiAgICByZXR1
cm4gcHJlZml4ICsgc3RyOwp9CgpmdW5jdGlvbiBmaW5kX2NodW5rKG4pewogICAgcmV0dXJuIGRv
Y3VtZW50LnF1ZXJ5U2VsZWN0b3IoJ3RyW2lkJD0iJyArIG4gKyAnIl0nKTsKfQoKZnVuY3Rpb24g
Y2hhbmdlX2NodW5rKG9mZnNldCkgewogICAgdmFyIGluZGV4ID0gY2h1bmtfaW5kZXggKyBvZmZz
ZXQ7CiAgICB2YXIgbmV3X3N0cjsKICAgIHZhciBuZXdfY2h1bms7CgogICAgbmV3X3N0ciA9IGZv
cm1hdF9jaHVuayhpbmRleCk7CiAgICBuZXdfY2h1bmsgPSBmaW5kX2NodW5rKG5ld19zdHIpOwog
ICAgaWYgKCFuZXdfY2h1bmspIHsKICAgICAgICByZXR1cm47CiAgICB9CiAgICBpZiAob2xkX2No
dW5rKSB7CiAgICAgICAgb2xkX2NodW5rLnN0eWxlLm91dGxpbmUgPSAiIjsKICAgIH0KICAgIG9s
ZF9jaHVuayA9IG5ld19jaHVuazsKICAgIG9sZF9jaHVuay5zdHlsZS5vdXRsaW5lID0gIjFweCBz
b2xpZCByZWQiOwogICAgd2luZG93LmxvY2F0aW9uLmhhc2ggPSAiIyIgKyBuZXdfc3RyOwogICAg
d2luZG93LnNjcm9sbEJ5KDAsLTEwMCk7CiAgICBjaHVua19pbmRleCA9IGluZGV4Owp9Cgpkb2N1
bWVudC5vbmtleWRvd24gPSBmdW5jdGlvbihlKSB7CiAgICBzd2l0Y2ggKGUua2V5Q29kZSkgewog
ICAgY2FzZSA3ODoKICAgICAgICBjaGFuZ2VfY2h1bmsoMSk7CiAgICAgICAgYnJlYWs7CiAgICBj
YXNlIDgwOgogICAgICAgIGNoYW5nZV9jaHVuaygtMSk7CiAgICAgICAgYnJlYWs7CiAgICB9Cn07
CiAgIDwvc2NyaXB0PiAKPHN0eWxlIHR5cGU9InRleHQvY3NzIiBpZD0iR0lOR0VSX1NPRlRXQVJF
X3N0eWxlIj4uR0lOR0VSX1NPRlRXQVJFX25vTWFyayB7IGJhY2tncm91bmQgOiB0cmFuc3BhcmVu
dDsgfSAgLkdJTkdFUl9TT0ZUV0FSRV93cmFwcGVyeyBwb3NpdGlvbjogYWJzb2x1dGU7IG92ZXJm
bG93OiBoaWRkZW47IG1hcmdpbjogMHB4OyBwYWRkaW5nOiAwcHg7IGJvcmRlcjogMHB4IHNvbGlk
IHRyYW5zcGFyZW50IH0gLkdJTkdFUl9TT0ZUV0FSRV9jb250b3VyIHsgcG9zaXRpb24gOiBhYnNv
bHV0ZTsgbWFyZ2luOiAwcHg7IH0gIC5HSU5HRVJfU09GVFdBUkVfcmljaFRleHQgeyBtYXJnaW4g
OiAwcHg7IHBhZGRpbmctYm90dG9tOiAzcHg7IGJvcmRlci13aWR0aDogMHB4OyBib3JkZXItY29s
b3I6IHRyYW5zcGFyZW50OyBkaXNwbGF5OiBibG9jazsgY29sb3I6IHRyYW5zcGFyZW50OyAtd2Vi
a2l0LXRleHQtZmlsbC1jb2xvcjogdHJhbnNwYXJlbnQ7IG92ZXJmbG93OiBoaWRkZW47IHdoaXRl
LXNwYWNlOiBwcmUtd3JhcDt9ICAuR0lOR0VSX1NPRlRXQVJFX2lucHV0V3JhcHBlciAuR0lOR0VS
X1NPRlRXQVJFX3JpY2hUZXh0IHtwb3NpdGlvbjogYWJzb2x1dGU7fSAgLkdJTkdFUl9TT0ZUV0FS
RV9jYW52YXMgeyBkaXNwbGF5Om5vbmU7IGJhY2tncm91bmQtcmVwZWF0Om5vLXJlcGVhdDt9ICAu
R0lOR0VSX1NPRlRXQVJFX2NvbnRyb2wgLkdJTkdFUl9TT0ZUV0FSRV9jb3JyZWN0LCAuR0lOR0VS
X1NPRlRXQVJFX2NvbnRyb2wgLkdJTkdFUl9TT0ZUV0FSRV9TcGVsbGluZ0NvcnJlY3QsIC5HSU5H
RVJfU09GVFdBUkVfY29udHJvbCAuR0lOR0VSX1NPRlRXQVJFX3NwZWxsaW5nLCAuR0lOR0VSX1NP
RlRXQVJFX2NvbnRyb2wgLkdJTkdFUl9TT0ZUV0FSRV9tYXJrIHtib3JkZXItdG9wLWxlZnQtcmFk
aXVzOjJweDsgYm9yZGVyLXRvcC1yaWdodC1yYWRpdXM6MnB4OyBib3JkZXItYm90dG9tLXJpZ2h0
LXJhZGl1czoycHg7IGJvcmRlci1ib3R0b20tbGVmdC1yYWRpdXM6MnB4O30gLkdJTkdFUl9TT0ZU
V0FSRV9jb250cm9sIC5HSU5HRVJfU09GVFdBUkVfY29ycmVjdCwgLkdJTkdFUl9TT0ZUV0FSRV9j
b250cm9sIC5HSU5HRVJfU09GVFdBUkVfU3BlbGxpbmdDb3JyZWN0LCAuR0lOR0VSX1NPRlRXQVJF
X2NvbnRyb2wgLkdJTkdFUl9TT0ZUV0FSRV9zcGVsbGluZywgLkdJTkdFUl9TT0ZUV0FSRV9jb250
cm9sIC5HSU5HRVJfU09GVFdBUkVfbWFyayB7YmFja2dyb3VuZC1pbWFnZTp1cmwoZGF0YTppbWFn
ZS9naWY7YmFzZTY0LGlWQk9SdzBLR2dvQUFBQU5TVWhFVWdBQUFBRUFBQUFCQ0FJQUFBQ1FkMVBl
QUFBQUdYUkZXSFJUYjJaMGQyRnlaUUJCWkc5aVpTQkpiV0ZuWlZKbFlXUjVjY2xsUEFBQUF5QnBW
RmgwV0UxTU9tTnZiUzVoWkc5aVpTNTRiWEFBQUFBQUFEdy9lSEJoWTJ0bGRDQmlaV2RwYmowaTc3
dS9JaUJwWkQwaVZ6Vk5NRTF3UTJWb2FVaDZjbVZUZWs1VVkzcHJZemxrSWo4K0lEeDRPbmh0Y0cx
bGRHRWdlRzFzYm5NNmVEMGlZV1J2WW1VNmJuTTZiV1YwWVM4aUlIZzZlRzF3ZEdzOUlrRmtiMkps
SUZoTlVDQkRiM0psSURVdU1DMWpNRFl3SURZeExqRXpORGMzTnl3Z01qQXhNQzh3TWk4eE1pMHhO
em96TWpvd01DQWdJQ0FnSUNBZ0lqNGdQSEprWmpwU1JFWWdlRzFzYm5NNmNtUm1QU0pvZEhSd09p
OHZkM2QzTG5jekxtOXlaeTh4T1RrNUx6QXlMekl5TFhKa1ppMXplVzUwWVhndGJuTWpJajRnUEhK
a1pqcEVaWE5qY21sd2RHbHZiaUJ5WkdZNllXSnZkWFE5SWlJZ2VHMXNibk02ZUcxd1BTSm9kSFJ3
T2k4dmJuTXVZV1J2WW1VdVkyOXRMM2hoY0M4eExqQXZJaUI0Yld4dWN6cDRiWEJOVFQwaWFIUjBj
RG92TDI1ekxtRmtiMkpsTG1OdmJTOTRZWEF2TVM0d0wyMXRMeUlnZUcxc2JuTTZjM1JTWldZOUlt
aDBkSEE2THk5dWN5NWhaRzlpWlM1amIyMHZlR0Z3THpFdU1DOXpWSGx3WlM5U1pYTnZkWEpqWlZK
bFppTWlJSGh0Y0RwRGNtVmhkRzl5Vkc5dmJEMGlRV1J2WW1VZ1VHaHZkRzl6YUc5d0lFTlROU0JY
YVc1a2IzZHpJaUI0YlhCTlRUcEpibk4wWVc1alpVbEVQU0o0YlhBdWFXbGtPamhGUTBZMk9FTkdN
ekU1T1RFeFJUSTROak14T1RFeE5UVXlNRGhFTURNd0lpQjRiWEJOVFRwRWIyTjFiV1Z1ZEVsRVBT
SjRiWEF1Wkdsa09qaEZRMFkyT0VRd016RTVPVEV4UlRJNE5qTXhPVEV4TlRVeU1EaEVNRE13SWo0
Z1BIaHRjRTFOT2tSbGNtbDJaV1JHY205dElITjBVbVZtT21sdWMzUmhibU5sU1VROUluaHRjQzVw
YVdRNk9FVkRSalk0UTBRek1UazVNVEZGTWpnMk16RTVNVEUxTlRJd09FUXdNekFpSUhOMFVtVm1P
bVJ2WTNWdFpXNTBTVVE5SW5odGNDNWthV1E2T0VWRFJqWTRRMFV6TVRrNU1URkZNamcyTXpFNU1U
RTFOVEl3T0VRd016QWlMejRnUEM5eVpHWTZSR1Z6WTNKcGNIUnBiMjQrSUR3dmNtUm1PbEpFUmo0
Z1BDOTRPbmh0Y0cxbGRHRStJRHcvZUhCaFkydGxkQ0JsYm1ROUluSWlQejVSUnhSeEFBQUFEMGxF
UVZSNDJtSzQ4K3c3UUlBQkFBVmJBcm9vd04wOEFBQUFBRWxGVGtTdVFtQ0MpIWltcG9ydGFudDt9
IC5HSU5HRVJfU09GVFdBUkVfY29udHJvbCAuR0lOR0VSX1NPRlRXQVJFX2NvcnJlY3QuR0lOR0VS
X1NPRlRXQVJFX3N5bm9ueW0sIC5HSU5HRVJfU09GVFdBUkVfY29udHJvbCAuR0lOR0VSX1NPRlRX
QVJFX1NwZWxsaW5nQ29ycmVjdC5HSU5HRVJfU09GVFdBUkVfc3lub255bSwgLkdJTkdFUl9TT0ZU
V0FSRV9jb250cm9sIC5HSU5HRVJfU09GVFdBUkVfc3BlbGxpbmcuR0lOR0VSX1NPRlRXQVJFX3N5
bm9ueW0sIC5HSU5HRVJfU09GVFdBUkVfY29udHJvbCAuR0lOR0VSX1NPRlRXQVJFX21hcmsuR0lO
R0VSX1NPRlRXQVJFX3N5bm9ueW0ge2JhY2tncm91bmQtaW1hZ2U6dXJsKGRhdGE6aW1hZ2UvZ2lm
O2Jhc2U2NCxpVkJPUncwS0dnb0FBQUFOU1VoRVVnQUFBQUVBQUFBQkNBSUFBQUNRZDFQZUFBQUFD
WEJJV1hNQUFBc1RBQUFMRXdFQW1wd1lBQUFLVDJsRFExQlFhRzkwYjNOb2IzQWdTVU5ESUhCeWIy
WnBiR1VBQUhqYW5WTm5WRlBwRmozMzN2UkNTNGlBbEV0dlVoVUlJRkpDaTRBVWtTWXFJUWtRU29n
aG9ka1ZVY0VSUlVVRUc4aWdpQU9Pam9DTUZWRXNESW9LMkFma0lhS09nNk9JaXNyNzRYdWphOWE4
OStiTi9yWFhQdWVzODUyenp3ZkFDQXlXU0ROUk5ZQU1xVUllRWVDRHg4VEc0ZVF1UUlFS0pIQUFF
QWl6WkNGei9TTUJBUGgrUER3cklzQUh2Z0FCZU5NTENBREFUWnZBTUJ5SC93L3FRcGxjQVlDRUFj
QjBrVGhMQ0lBVUFFQjZqa0ttQUVCR0FZQ2RtQ1pUQUtBRUFHRExZMkxqQUZBdEFHQW5mK2JUQUlD
ZCtKbDdBUUJibENFVkFhQ1JBQ0FUWlloRUFHZzdBS3pQVm9wRkFGZ3dBQlJtUzhRNUFOZ3RBREJK
VjJaSUFMQzNBTURPRUF1eUFBZ01BREJSaUlVcEFBUjdBR0RJSXlONEFJU1pBQlJHOGxjODhTdXVF
T2NxQUFCNG1iSTh1U1E1UllGYkNDMXhCMWRYTGg0b3pra1hLeFEyWVFKaG1rQXV3bm1aR1RLQk5B
L2c4OHdBQUtDUkZSSGdnL1A5ZU00T3JzN09ObzYyRGw4dDZyOEcveUppWXVQKzVjK3JjRUFBQU9G
MGZ0SCtMQyt6R29BN0JvQnQvcUlsN2dSb1hndWdkZmVMWnJJUFFMVUFvT25hVi9OdytINDhQRVdo
a0xuWjJlWGs1TmhLeEVKYlljcFhmZjVud2wvQVYvMXMrWDQ4L1BmMTRMN2lKSUV5WFlGSEJQamd3
c3owVEtVY3o1SUpoR0xjNW85SC9MY0wvL3dkMHlMRVNXSzVXQ29VNDFFU2NZNUVtb3p6TXFVaWlV
S1NLY1VsMHY5azR0OHMrd00rM3pVQXNHbytBWHVSTGFoZFl3UDJTeWNRV0hUQTR2Y0FBUEs3YjhI
VUtBZ0RnR2lENGM5My8rOC8vVWVnSlFDQVprbVNjUUFBWGtRa0xsVEtzei9IQ0FBQVJLQ0JLckJC
Ry9UQkdDekFCaHpCQmR6QkMveGdOb1JDSk1UQ1FoQkNDbVNBSEhKZ0theUNRaWlHemJBZEttQXYx
RUFkTk1CUmFJYVRjQTR1d2xXNERqMXdEL3BoQ0o3QktMeUJDUVJCeUFnVFlTSGFpQUZpaWxnampn
Z1htWVg0SWNGSUJCS0xKQ0RKaUJSUklrdVJOVWd4VW9wVUlGVklIZkk5Y2dJNWgxeEd1cEU3eUFB
eWd2eUd2RWN4bElHeVVUM1VETFZEdWFnM0dvUkdvZ3ZRWkhReG1vOFdvSnZRY3JRYVBZdzJvZWZR
cTJnUDJvOCtROGN3d09nWUJ6UEViREF1eHNOQ3NUZ3NDWk5qeTdFaXJBeXJ4aHF3VnF3RHU0bjFZ
OCt4ZHdRU2dVWEFDVFlFZDBJZ1lSNUJTRmhNV0U3WVNLZ2dIQ1EwRWRvSk53a0RoRkhDSnlLVHFF
dTBKcm9SK2NRWVlqSXhoMWhJTENQV0VvOFRMeEI3aUVQRU55UVNpVU15SjdtUUFrbXhwRlRTRXRK
RzBtNVNJK2tzcVpzMFNCb2prOG5hWkd1eUJ6bVVMQ0FyeUlYa25lVEQ1RFBrRytRaDhsc0tuV0pB
Y2FUNFUrSW9Vc3BxU2hubEVPVTA1UVpsbURKQlZhT2FVdDJvb1ZRUk5ZOWFRcTJodGxLdlVZZW9F
elIxbWpuTmd4WkpTNld0b3BYVEdtZ1hhUGRwcitoMHVoSGRsUjVPbDlCWDBzdnBSK2lYNkFQMGR3
d05oaFdEeDRobktCbWJHQWNZWnhsM0dLK1lUS1laMDRzWngxUXdOekhybU9lWkQ1bHZWVmdxdGlw
OEZaSEtDcFZLbFNhVkd5b3ZWS21xcHFyZXFndFY4MVhMVkkrcFhsTjlya1pWTTFQanFRblVscXRW
cXAxUTYxTWJVMmVwTzZpSHFtZW9iMVEvcEg1Wi9Za0dXY05NdzA5RHBGR2dzVi9qdk1ZZ0MyTVpz
M2dzSVdzTnE0WjFnVFhFSnJITjJYeDJLcnVZL1IyN2l6MnFxYUU1UXpOS00xZXpVdk9VWmo4SDQ1
aHgrSngwVGdubktLZVg4MzZLM2hUdktlSXBHNlkwVExreFpWeHJxcGFYbGxpclNLdFJxMGZydlRh
dTdhZWRwcjFGdTFuN2dRNUJ4MG9uWENkSFo0L09CWjNuVTlsVDNhY0tweFpOUFRyMXJpNnFhNlVi
b2J0RWQ3OXVwKzZZbnI1ZWdKNU1iNmZlZWIzbitoeDlMLzFVL1czNnAvVkhERmdHc3d3a0J0c016
aGc4eFRWeGJ6d2RMOGZiOFZGRFhjTkFRNlZobFdHWDRZU1J1ZEU4bzlWR2pVWVBqR25HWE9NazQy
M0diY2FqSmdZbUlTWkxUZXBON3BwU1RibW1LYVk3VER0TXg4M016YUxOMXBrMW16MHgxekxubStl
YjE1dmZ0MkJhZUZvc3RxaTJ1R1ZKc3VSYXBsbnV0cnh1aFZvNVdhVllWVnBkczBhdG5hMGwxcnV0
dTZjUnA3bE9rMDZybnRabnc3RHh0c20ycWJjWnNPWFlCdHV1dG0yMmZXRm5ZaGRudDhXdXcrNlR2
Wk45dW4yTi9UMEhEWWZaRHFzZFdoMStjN1J5RkRwV090NmF6cHp1UDMzRjlKYnBMMmRZenhEUDJE
UGp0aFBMS2NScG5WT2IwMGRuRjJlNWM0UHppSXVKUzRMTExwYytMcHNieHQzSXZlUktkUFZ4WGVG
NjB2V2RtN09id3UybzI2L3VOdTVwN29mY244dzBueW1lV1ROejBNUElRK0JSNWRFL0M1K1ZNR3Zm
ckg1UFEwK0JaN1huSXk5akw1RlhyZGV3dDZWM3F2ZGg3eGMrOWo1eW4rTSs0enczM2pMZVdWL01O
OEMzeUxmTFQ4TnZubCtGMzBOL0kvOWsvM3IvMFFDbmdDVUJad09KZ1VHQld3TDcrSHA4SWIrT1B6
cmJaZmF5MmUxQmpLQzVRUlZCajRLdGd1WEJyU0ZveU95UXJTSDM1NWpPa2M1cERvVlFmdWpXMEFk
aDVtR0x3MzRNSjRXSGhWZUdQNDV3aUZnYTBUR1hOWGZSM0VOejMwVDZSSlpFM3B0bk1VODVyeTFL
TlNvK3FpNXFQTm8zdWpTNlA4WXVabG5NMVZpZFdFbHNTeHc1TGlxdU5tNXN2dC84N2ZPSDRwM2lD
K043RjVndnlGMXdlYUhPd3ZTRnB4YXBMaElzT3BaQVRJaE9PSlR3UVJBcXFCYU1KZklUZHlXT0Nu
bkNIY0puSWkvUk50R0kyRU5jS2g1TzhrZ3FUWHFTN0pHOE5Ya2t4VE9sTE9XNWhDZXBrTHhNRFV6
ZG16cWVGcHAySUcweVBUcTlNWU9Ta1pCeFFxb2hUWk8yWitwbjVtWjJ5NnhsaGJMK3hXNkx0eThl
bFFmSmE3T1FyQVZaTFFxMlFxYm9WRm9vMXlvSHNtZGxWMmEvelluS09aYXJuaXZON2N5enl0dVFO
NXp2bi8vdEVzSVM0WksycFlaTFZ5MGRXT2E5ckdvNXNqeHhlZHNLNHhVRks0WldCcXc4dUlxMktt
M1ZUNnZ0VjVldWZyMG1lazFyZ1Y3QnlvTEJ0UUZyNnd0VkN1V0ZmZXZjMSsxZFQxZ3ZXZCsxWWZx
R25ScytGWW1LcmhUYkY1Y1ZmOWdvM0hqbEc0ZHZ5citaM0pTMHFhdkV1V1RQWnRKbTZlYmVMWjVi
RHBhcWwrYVhEbTROMmRxMERkOVd0TzMxOWtYYkw1Zk5LTnU3ZzdaRHVhTy9QTGk4WmFmSnpzMDdQ
MVNrVlBSVStsUTI3dExkdFdIWCtHN1I3aHQ3dlBZMDdOWGJXN3ozL1Q3SnZ0dFZBVlZOMVdiVlpm
dEorN1AzUDY2SnF1bjRsdnR0WGExT2JYSHR4d1BTQS8wSEl3NjIxN25VMVIzU1BWUlNqOVlyNjBj
T3h4KysvcDN2ZHkwTk5nMVZqWnpHNGlOd1JIbms2ZmNKMy9jZURUcmFkb3g3ck9FSDB4OTJIV2Nk
TDJwQ212S2FScHRUbXZ0YllsdTZUOHcrMGRicTNucjhSOXNmRDV3MFBGbDVTdk5VeVduYTZZTFRr
MmZ5ejR5ZGxaMTlmaTc1M0dEYm9yWjc1MlBPMzJvUGIrKzZFSFRoMGtYL2krYzd2RHZPWFBLNGRQ
S3kyK1VUVjdoWG1xODZYMjNxZE9vOC9wUFRUOGU3bkx1YXJybGNhN251ZXIyMWUyYjM2UnVlTjg3
ZDlMMTU4UmIvMXRXZU9UM2R2Zk42Yi9mRjkvWGZGdDErY2lmOXpzdTcyWGNuN3EyOFQ3eGY5RUR0
UWRsRDNZZlZQMXYrM05qdjNIOXF3SGVnODlIY1IvY0doWVBQL3BIMWp3OURCWStaajh1R0RZYnJu
amcrT1RuaVAzTDk2ZnluUTg5a3p5YWVGLzZpL3N1dUZ4WXZmdmpWNjlmTzBaalJvWmZ5bDVPL2JY
eWwvZXJBNnhtdjI4YkN4aDYreVhnek1WNzBWdnZ0d1hmY2R4M3ZvOThQVCtSOElIOG8vMmo1c2ZW
VDBLZjdreG1Uay84RUE1anovR016TGRzQUFBQWdZMGhTVFFBQWVpVUFBSUNEQUFENS93QUFnT2tB
QUhVd0FBRHFZQUFBT3BnQUFCZHZrbC9GUmdBQUFCSkpSRUZVZU5waStQOWdFd0FBQVAvL0F3QUZj
d0tTM2Q3Qm53QUFBQUJKUlU1RXJrSmdnZz09KSFpbXBvcnRhbnQ7fSAuR0lOR0VSX1NPRlRXQVJF
X2NvbnRyb2wgLkdJTkdFUl9TT0ZUV0FSRV9jb3JyZWN0LkdJTkdFUl9TT0ZUV0FSRV9ub1N1Z2dl
c3Rpb24sIC5HSU5HRVJfU09GVFdBUkVfY29udHJvbCAuR0lOR0VSX1NPRlRXQVJFX1NwZWxsaW5n
Q29ycmVjdC5HSU5HRVJfU09GVFdBUkVfbm9TdWdnZXN0aW9uLCAuR0lOR0VSX1NPRlRXQVJFX2Nv
bnRyb2wgLkdJTkdFUl9TT0ZUV0FSRV9zcGVsbGluZy5HSU5HRVJfU09GVFdBUkVfbm9TdWdnZXN0
aW9uLCAuR0lOR0VSX1NPRlRXQVJFX2NvbnRyb2wgLkdJTkdFUl9TT0ZUV0FSRV9tYXJrLkdJTkdF
Ul9TT0ZUV0FSRV9ub1N1Z2dlc3Rpb24ge2JhY2tncm91bmQtaW1hZ2U6dXJsKGRhdGE6aW1hZ2Uv
Z2lmO2Jhc2U2NCxpVkJPUncwS0dnb0FBQUFOU1VoRVVnQUFBQUVBQUFBQkNBSUFBQUNRZDFQZUFB
QUFHWFJGV0hSVGIyWjBkMkZ5WlFCQlpHOWlaU0JKYldGblpWSmxZV1I1Y2NsbFBBQUFBeUJwVkZo
MFdFMU1PbU52YlM1aFpHOWlaUzU0YlhBQUFBQUFBRHcvZUhCaFkydGxkQ0JpWldkcGJqMGk3N3Uv
SWlCcFpEMGlWelZOTUUxd1EyVm9hVWg2Y21WVGVrNVVZM3ByWXpsa0lqOCtJRHg0T25odGNHMWxk
R0VnZUcxc2JuTTZlRDBpWVdSdlltVTZibk02YldWMFlTOGlJSGc2ZUcxd2RHczlJa0ZrYjJKbElG
aE5VQ0JEYjNKbElEVXVNQzFqTURZd0lEWXhMakV6TkRjM055d2dNakF4TUM4d01pOHhNaTB4Tnpv
ek1qb3dNQ0FnSUNBZ0lDQWdJajRnUEhKa1pqcFNSRVlnZUcxc2JuTTZjbVJtUFNKb2RIUndPaTh2
ZDNkM0xuY3pMbTl5Wnk4eE9UazVMekF5THpJeUxYSmtaaTF6ZVc1MFlYZ3Ribk1qSWo0Z1BISmta
anBFWlhOamNtbHdkR2x2YmlCeVpHWTZZV0p2ZFhROUlpSWdlRzFzYm5NNmVHMXdQU0pvZEhSd09p
OHZibk11WVdSdlltVXVZMjl0TDNoaGNDOHhMakF2SWlCNGJXeHVjenA0YlhCTlRUMGlhSFIwY0Rv
dkwyNXpMbUZrYjJKbExtTnZiUzk0WVhBdk1TNHdMMjF0THlJZ2VHMXNibk02YzNSU1pXWTlJbWgw
ZEhBNkx5OXVjeTVoWkc5aVpTNWpiMjB2ZUdGd0x6RXVNQzl6Vkhsd1pTOVNaWE52ZFhKalpWSmxa
aU1pSUhodGNEcERjbVZoZEc5eVZHOXZiRDBpUVdSdlltVWdVR2h2ZEc5emFHOXdJRU5UTlNCWGFX
NWtiM2R6SWlCNGJYQk5UVHBKYm5OMFlXNWpaVWxFUFNKNGJYQXVhV2xrT2poRlEwWTJPRU5HTXpF
NU9URXhSVEk0TmpNeE9URXhOVFV5TURoRU1ETXdJaUI0YlhCTlRUcEViMk4xYldWdWRFbEVQU0o0
YlhBdVpHbGtPamhGUTBZMk9FUXdNekU1T1RFeFJUSTROak14T1RFeE5UVXlNRGhFTURNd0lqNGdQ
SGh0Y0UxTk9rUmxjbWwyWldSR2NtOXRJSE4wVW1WbU9tbHVjM1JoYm1ObFNVUTlJbmh0Y0M1cGFX
UTZPRVZEUmpZNFEwUXpNVGs1TVRGRk1qZzJNekU1TVRFMU5USXdPRVF3TXpBaUlITjBVbVZtT21S
dlkzVnRaVzUwU1VROUluaHRjQzVrYVdRNk9FVkRSalk0UTBVek1UazVNVEZGTWpnMk16RTVNVEUx
TlRJd09FUXdNekFpTHo0Z1BDOXlaR1k2UkdWelkzSnBjSFJwYjI0K0lEd3ZjbVJtT2xKRVJqNGdQ
Qzk0T25odGNHMWxkR0UrSUR3L2VIQmhZMnRsZENCbGJtUTlJbklpUHo1UlJ4UnhBQUFBRDBsRVFW
UjQybUs0OCt3N1FJQUJBQVZiQXJvb3dOMDhBQUFBQUVsRlRrU3VRbUNDKSFpbXBvcnRhbnQ7fSAu
R0lOR0VSX1NPRlRXQVJFX3JpY2hUZXh0IC5HSU5HRVJfU09GVFdBUkVfY29ycmVjdCwgLkdJTkdF
Ul9TT0ZUV0FSRV9yaWNoVGV4dCAuR0lOR0VSX1NPRlRXQVJFX1NwZWxsaW5nQ29ycmVjdCwgLkdJ
TkdFUl9TT0ZUV0FSRV9yaWNoVGV4dCAuR0lOR0VSX1NPRlRXQVJFX3NwZWxsaW5nLCAuR0lOR0VS
X1NPRlRXQVJFX3JpY2hUZXh0IC5HSU5HRVJfU09GVFdBUkVfbWFyayB7cG9zaXRpb246cmVsYXRp
dmU7IGJhY2tncm91bmQtaW1hZ2U6bm9uZSFpbXBvcnRhbnQ7fSAuR0lOR0VSX1NPRlRXQVJFX3Jp
Y2hUZXh0IC5HSU5HRVJfU09GVFdBUkVfbWFya0hpZ2hsaWdodExlZnQgeyBwb3NpdGlvbiA6IGFi
c29sdXRlOyBsZWZ0Oi0ycHg7IHRvcDowcHg7IGJvdHRvbTowcHg7IHdpZHRoOjJweDt9IC5HSU5H
RVJfU09GVFdBUkVfcmljaFRleHQgLkdJTkdFUl9TT0ZUV0FSRV9tYXJrSGlnaGxpZ2h0UmlnaHQg
eyBwb3NpdGlvbiA6IGFic29sdXRlOyByaWdodDotMnB4OyB0b3A6MHB4OyBib3R0b206MHB4OyB3
aWR0aDoycHg7fSAuR0lOR0VSX1NPRlRXQVJFX3JpY2hUZXh0IC5HSU5HRVJfU09GVFdBUkVfbWFy
a0hpZ2hsaWdodFRvcCB7IHBvc2l0aW9uIDogYWJzb2x1dGU7IGxlZnQ6MHB4OyByaWdodDowcHg7
IHRvcDotMnB4OyBoZWlnaHQ6M3B4O30gLkdJTkdFUl9TT0ZUV0FSRV9yaWNoVGV4dCAuR0lOR0VS
X1NPRlRXQVJFX21hcmtIaWdobGlnaHRCb3R0b20geyBwb3NpdGlvbiA6IGFic29sdXRlOyBsZWZ0
OjBweDsgcmlnaHQ6MHB4OyBib3R0b206LTJweDsgaGVpZ2h0OjNweDt9PC9zdHlsZT48L2hlYWQ+
IAo8Ym9keSBnaW5nZXJfc29mdHdhcmVfc3R5bGVzaGVldD0idHJ1ZSIgZ2luZ2VyX3NvZnR3YXJl
X2RvYz0idHJ1ZSI+IAogIDx0YWJsZSBib3JkZXI9IjAiIGNlbGxwYWRkaW5nPSIwIiBjZWxsc3Bh
Y2luZz0iMCI+IAogIDx0Ym9keT48dHIgaWQ9InBhcnQtMSIgYmdjb2xvcj0ib3JhbmdlIj48dGg+
PC90aD48dGg+PGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9yZmNkaWZmP3VybDI9ZHJh
ZnQtaWV0Zi1wY2UtcGNlcHMtMTUtb2xkLnR4dCIgc3R5bGU9ImNvbG9yOiMwMDg7IHRleHQtZGVj
b3JhdGlvbjpub25lOyI+Jmx0OzwvYT4mbmJzcDs8YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYu
b3JnL2h0bWwvZHJhZnQtaWV0Zi1wY2UtcGNlcHMtMTUtb2xkLnR4dCIgc3R5bGU9ImNvbG9yOiMw
MDgiPmRyYWZ0LWlldGYtcGNlLXBjZXBzLTE1LW9sZC50eHQ8L2E+Jm5ic3A7PC90aD48dGg+IDwv
dGg+PHRoPiZuYnNwOzxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1p
ZXRmLXBjZS1wY2Vwcy0xNS50eHQiIHN0eWxlPSJjb2xvcjojMDA4Ij5kcmFmdC1pZXRmLXBjZS1w
Y2Vwcy0xNS50eHQ8L2E+Jm5ic3A7PGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9yZmNk
aWZmP3VybDE9ZHJhZnQtaWV0Zi1wY2UtcGNlcHMtMTUudHh0IiBzdHlsZT0iY29sb3I6IzAwODsg
dGV4dC1kZWNvcmF0aW9uOm5vbmU7Ij4mZ3Q7PC9hPjwvdGg+PHRoPjwvdGg+PC90cj4gCiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+UENFIFdv
cmtpbmcgR3JvdXAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IEQuIExvcGV6PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+UENFIFdvcmtpbmcgR3Jv
dXAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIEQuIExvcGV6
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij5JbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIE8uIEdvbnphbGV6IGRlIERpb3M8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij5JbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIE8uIEdvbnphbGV6IGRlIERpb3M8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPlVwZGF0ZXM6IDU0NDAgKGlmIGFwcHJvdmVkKSAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICBUZWxlZm9uaWNhIEkrRDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPlVw
ZGF0ZXM6IDU0NDAgKGlmIGFwcHJvdmVkKSAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBU
ZWxlZm9uaWNhIEkrRDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+SW50ZW5kZWQgc3RhdHVz
OiBTdGFuZGFyZHMgVHJhY2sgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFEuIFd1
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+SW50ZW5kZWQgc3RhdHVzOiBTdGFuZGFy
ZHMgVHJhY2sgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFEuIFd1PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9ImRpZmYwMDAxIj48dGQ+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxv
Y2siPkV4cGlyZXM6IDxzcGFuIGNsYXNzPSJkZWxldGUiPkphbnVhcnkgMjk8L3NwYW4+LCAyMDE4
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgRC4gRGhvZHk8L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJibG9jayI+RXhwaXJlczogPHNwYW4gY2xhc3M9Imluc2VydCI+RmVi
cnVhcnkgMTwvc3Bhbj4sIDIwMTggICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICBELiBEaG9keTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgSHVhd2VpPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgSHVhd2VpPC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9ImRpZmYwMDAyIj48dGQ+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2si
PiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgSnVseSA8c3BhbiBjbGFzcz0iZGVsZXRlIj4yODwvc3Bhbj4sIDIwMTc8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJibG9jayI+ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICBKdWx5IDxzcGFuIGNsYXNzPSJpbnNlcnQiPjMxPC9zcGFu
PiwgMjAxNzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAg
ICAgICAgIFNlY3VyZSBUcmFuc3BvcnQgZm9yIFBDRVA8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICAgICAgICAgICAgICAgICAgICAgIFNlY3VyZSBUcmFuc3BvcnQgZm9yIFBDRVA8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICAgICAgICAgIGRyYWZ0
LWlldGYtcGNlLXBjZXBzLTE1PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAg
ICAgICAgICAgICAgICAgICAgZHJhZnQtaWV0Zi1wY2UtcGNlcHMtMTU8L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQg
Y2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+QWJzdHJhY3Q8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij5BYnN0cmFjdDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBUaGUgUGF0aCBD
b21wdXRhdGlvbiBFbGVtZW50IENvbW11bmljYXRpb24gUHJvdG9jb2wgKFBDRVApIGRlZmluZXM8
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBUaGUgUGF0aCBDb21wdXRhdGlvbiBF
bGVtZW50IENvbW11bmljYXRpb24gUHJvdG9jb2wgKFBDRVApIGRlZmluZXM8L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPiAgIHRoZSBtZWNoYW5pc21zIGZvciB0aGUgY29tbXVuaWNhdGlvbiBi
ZXR3ZWVuIGEgUGF0aCBDb21wdXRhdGlvbjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgIHRoZSBtZWNoYW5pc21zIGZvciB0aGUgY29tbXVuaWNhdGlvbiBiZXR3ZWVuIGEgUGF0aCBD
b21wdXRhdGlvbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgQ2xpZW50IChQQ0MpIGFu
ZCBhIFBhdGggQ29tcHV0YXRpb24gRWxlbWVudCAoUENFKSwgb3IgYW1vbmcgUENFcy48L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBDbGllbnQgKFBDQykgYW5kIGEgUGF0aCBDb21w
dXRhdGlvbiBFbGVtZW50IChQQ0UpLCBvciBhbW9uZyBQQ0VzLjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGVmdCI+ICAgVGhpcyBkb2N1bWVudCBkZXNjcmliZSB0aGUgdXNhZ2Ugb2YgVHJhbnNwb3J0
IExheWVyIFNlY3VyaXR5IChUTFMpIHRvPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
ICAgVGhpcyBkb2N1bWVudCBkZXNjcmliZSB0aGUgdXNhZ2Ugb2YgVHJhbnNwb3J0IExheWVyIFNl
Y3VyaXR5IChUTFMpIHRvPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0ciBpZD0icGFydC0yIiBjbGFzcz0iY2hhbmdlIj48dGQ+PC90ZD48dGg+PHNtYWxsPnNr
aXBwaW5nIHRvIGNoYW5nZSBhdDwvc21hbGw+PGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9y
Zy9yZmNkaWZmI3BhcnQtMiI+PGVtPiBwYWdlIDEsIGxpbmUgNDM8c3BhbiBjbGFzcz0iaGlkZSI+
IMK2PC9zcGFuPjwvZW0+PC9hPjwvdGg+PHRoPiA8L3RoPjx0aD48c21hbGw+c2tpcHBpbmcgdG8g
Y2hhbmdlIGF0PC9zbWFsbD48YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL3JmY2RpZmYj
cGFydC0yIj48ZW0+IHBhZ2UgMSwgbGluZSA0MzxzcGFuIGNsYXNzPSJoaWRlIj4gwrY8L3NwYW4+
PC9lbT48L2E+PC90aD48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBJbnRlcm5ldC1EcmFmdHMgYXJlIHdvcmtpbmcgZG9j
dW1lbnRzIG9mIHRoZSBJbnRlcm5ldCBFbmdpbmVlcmluZzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgIEludGVybmV0LURyYWZ0cyBhcmUgd29ya2luZyBkb2N1bWVudHMgb2YgdGhl
IEludGVybmV0IEVuZ2luZWVyaW5nPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBUYXNr
IEZvcmNlIChJRVRGKS4gIE5vdGUgdGhhdCBvdGhlciBncm91cHMgbWF5IGFsc28gZGlzdHJpYnV0
ZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFRhc2sgRm9yY2UgKElFVEYpLiAg
Tm90ZSB0aGF0IG90aGVyIGdyb3VwcyBtYXkgYWxzbyBkaXN0cmlidXRlPC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij4gICB3b3JraW5nIGRvY3VtZW50cyBhcyBJbnRlcm5ldC1EcmFmdHMuICBU
aGUgbGlzdCBvZiBjdXJyZW50IEludGVybmV0LTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgIHdvcmtpbmcgZG9jdW1lbnRzIGFzIEludGVybmV0LURyYWZ0cy4gIFRoZSBsaXN0IG9m
IGN1cnJlbnQgSW50ZXJuZXQtPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBEcmFmdHMg
aXMgYXQgaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RyYWZ0cy9jdXJyZW50Ly48L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBEcmFmdHMgaXMgYXQgaHR0cDovL2RhdGF0cmFj
a2VyLmlldGYub3JnL2RyYWZ0cy9jdXJyZW50Ly48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+ICAgSW50ZXJuZXQtRHJhZnRzIGFyZSBkcmFmdCBkb2N1bWVudHMgdmFsaWQgZm9yIGEg
bWF4aW11bSBvZiBzaXggbW9udGhzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAg
SW50ZXJuZXQtRHJhZnRzIGFyZSBkcmFmdCBkb2N1bWVudHMgdmFsaWQgZm9yIGEgbWF4aW11bSBv
ZiBzaXggbW9udGhzPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBhbmQgbWF5IGJlIHVw
ZGF0ZWQsIHJlcGxhY2VkLCBvciBvYnNvbGV0ZWQgYnkgb3RoZXIgZG9jdW1lbnRzIGF0IGFueTwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGFuZCBtYXkgYmUgdXBkYXRlZCwgcmVw
bGFjZWQsIG9yIG9ic29sZXRlZCBieSBvdGhlciBkb2N1bWVudHMgYXQgYW55PC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij4gICB0aW1lLiAgSXQgaXMgaW5hcHByb3ByaWF0ZSB0byB1c2UgSW50
ZXJuZXQtRHJhZnRzIGFzIHJlZmVyZW5jZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgIHRpbWUuICBJdCBpcyBpbmFwcHJvcHJpYXRlIHRvIHVzZSBJbnRlcm5ldC1EcmFmdHMgYXMg
cmVmZXJlbmNlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBtYXRlcmlhbCBvciB0byBj
aXRlIHRoZW0gb3RoZXIgdGhhbiBhcyAid29yayBpbiBwcm9ncmVzcy4iPC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+ICAgbWF0ZXJpYWwgb3IgdG8gY2l0ZSB0aGVtIG90aGVyIHRoYW4g
YXMgIndvcmsgaW4gcHJvZ3Jlc3MuIjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHIgaWQ9ImRpZmYwMDAzIj48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIFRoaXMgSW50ZXJuZXQt
RHJhZnQgd2lsbCBleHBpcmUgb24gPHNwYW4gY2xhc3M9ImRlbGV0ZSI+SmFudWFyeSAyOTwvc3Bh
bj4sIDIwMTguPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIFRoaXMgSW50ZXJu
ZXQtRHJhZnQgd2lsbCBleHBpcmUgb24gPHNwYW4gY2xhc3M9Imluc2VydCI+RmVicnVhcnkgMTwv
c3Bhbj4sIDIwMTguPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPkNvcHlyaWdodCBO
b3RpY2U8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij5Db3B5cmlnaHQgTm90aWNlPC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIENvcHlyaWdodCAoYykgMjAxNyBJRVRG
IFRydXN0IGFuZCB0aGUgcGVyc29ucyBpZGVudGlmaWVkIGFzIHRoZTwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmlnaHQiPiAgIENvcHlyaWdodCAoYykgMjAxNyBJRVRGIFRydXN0IGFuZCB0aGUg
cGVyc29ucyBpZGVudGlmaWVkIGFzIHRoZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
ZG9jdW1lbnQgYXV0aG9ycy4gIEFsbCByaWdodHMgcmVzZXJ2ZWQuPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgZG9jdW1lbnQgYXV0aG9ycy4gIEFsbCByaWdodHMgcmVzZXJ2ZWQu
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRoaXMgZG9jdW1lbnQgaXMgc3Vi
amVjdCB0byBCQ1AgNzggYW5kIHRoZSBJRVRGIFRydXN0J3MgTGVnYWw8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICBUaGlzIGRvY3VtZW50IGlzIHN1YmplY3QgdG8gQkNQIDc4IGFu
ZCB0aGUgSUVURiBUcnVzdCdzIExlZ2FsPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBQ
cm92aXNpb25zIFJlbGF0aW5nIHRvIElFVEYgRG9jdW1lbnRzPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgUHJvdmlzaW9ucyBSZWxhdGluZyB0byBJRVRGIERvY3VtZW50czwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgKGh0dHA6Ly90cnVzdGVlLmlldGYub3JnL2xpY2Vu
c2UtaW5mbykgaW4gZWZmZWN0IG9uIHRoZSBkYXRlIG9mPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgKGh0dHA6Ly90cnVzdGVlLmlldGYub3JnL2xpY2Vuc2UtaW5mbykgaW4gZWZm
ZWN0IG9uIHRoZSBkYXRlIG9mPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBwdWJsaWNh
dGlvbiBvZiB0aGlzIGRvY3VtZW50LiAgUGxlYXNlIHJldmlldyB0aGVzZSBkb2N1bWVudHM8L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBwdWJsaWNhdGlvbiBvZiB0aGlzIGRvY3Vt
ZW50LiAgUGxlYXNlIHJldmlldyB0aGVzZSBkb2N1bWVudHM8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJwYXJ0LTMiIGNsYXNzPSJjaGFuZ2UiPjx0
ZD48L3RkPjx0aD48c21hbGw+c2tpcHBpbmcgdG8gY2hhbmdlIGF0PC9zbWFsbD48YSBocmVmPSJo
dHRwczovL3Rvb2xzLmlldGYub3JnL3JmY2RpZmYjcGFydC0zIj48ZW0+IHBhZ2UgMiwgbGluZSAz
NDxzcGFuIGNsYXNzPSJoaWRlIj4gwrY8L3NwYW4+PC9lbT48L2E+PC90aD48dGg+IDwvdGg+PHRo
PjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxhIGhyZWY9Imh0dHBzOi8vdG9v
bHMuaWV0Zi5vcmcvcmZjZGlmZiNwYXJ0LTMiPjxlbT4gcGFnZSAyLCBsaW5lIDM0PHNwYW4gY2xh
c3M9ImhpZGUiPiDCtjwvc3Bhbj48L2VtPjwvYT48L3RoPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGl0IGZvciBwdWJs
aWNhdGlvbiBhcyBhbiBSRkMgb3IgdG8gdHJhbnNsYXRlIGl0IGludG8gbGFuZ3VhZ2VzIG90aGVy
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgaXQgZm9yIHB1YmxpY2F0aW9uIGFz
IGFuIFJGQyBvciB0byB0cmFuc2xhdGUgaXQgaW50byBsYW5ndWFnZXMgb3RoZXI8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHRoYW4gRW5nbGlzaC48L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICB0aGFuIEVuZ2xpc2guPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPlRhYmxlIG9mIENvbnRlbnRzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+VGFi
bGUgb2YgQ29udGVudHM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgMS4gIElu
dHJvZHVjdGlvbiAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gICAzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgMS4gIEludHJvZHVjdGlv
biAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gICAzPC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAyLiAgUmVxdWlyZW1lbnRzIExhbmd1YWdlIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDQ8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICAyLiAgUmVxdWlyZW1lbnRzIExhbmd1YWdlIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDQ8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgIDMuICBBcHBseWluZyBQQ0VQUyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuICAgNDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIDMu
ICBBcHBseWluZyBQQ0VQUyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuICAgNDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAzLjEuICBPdmVydmll
dyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gICA0PC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAzLjEuICBPdmVydmlldyAgLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gICA0PC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij4gICAgIDMuMi4gIEluaXRpYXRpbmcgdGhlIFRMUyBQcm9jZWR1cmVz
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICAgIDMuMi4gIEluaXRpYXRpbmcgdGhlIFRMUyBQcm9jZWR1cmVzIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAgIDQ8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0ciBpZD0iZGlmZjAwMDQiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgICAzLjMuICBUaGUgU3RhcnRU
TFMgTWVzc2FnZSAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gICA8c3BhbiBj
bGFzcz0iZGVsZXRlIj42PC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4g
ICAgIDMuMy4gIFRoZSBTdGFydFRMUyBNZXNzYWdlICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAgIDxzcGFuIGNsYXNzPSJpbnNlcnQiPjc8L3NwYW4+PC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsYmxvY2siPiAgICAgMy40LiAgVExTIENvbm5lY3Rpb24gRXN0YWJsaXNobWVudCAg
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+ODwvc3Bh
bj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgICAzLjQuICBUTFMgQ29ubmVj
dGlvbiBFc3RhYmxpc2htZW50ICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDxzcGFuIGNs
YXNzPSJpbnNlcnQiPjExPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAg
IDMuNS4gIFBlZXIgSWRlbnRpdHkgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+MTA8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyYmxvY2siPiAgICAgMy41LiAgUGVlciBJZGVudGl0eSAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij4xMzwvc3Bh
bj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgICAzLjYuICBDb25uZWN0aW9uIEVz
dGFibGlzaG1lbnQgRmFpbHVyZSAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDxzcGFuIGNsYXNz
PSJkZWxldGUiPjExPC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAg
IDMuNi4gIENvbm5lY3Rpb24gRXN0YWJsaXNobWVudCBGYWlsdXJlICAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAgPHNwYW4gY2xhc3M9Imluc2VydCI+MTQ8L3NwYW4+PC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsYmxvY2siPiAgIDQuICBEaXNjb3ZlcnkgTWVjaGFuaXNtcyAgLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA8c3BhbiBjbGFzcz0iZGVsZXRlIj4xMjwvc3Bhbj48
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgNC4gIERpc2NvdmVyeSBNZWNoYW5p
c21zICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDxzcGFuIGNsYXNz
PSJpbnNlcnQiPjE1PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAgIDQu
MS4gIERBTkUgQXBwbGljYWJpbGl0eSAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+MTI8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyYmxvY2siPiAgICAgNC4xLiAgREFORSBBcHBsaWNhYmlsaXR5ICAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij4xNTwvc3Bhbj48
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgNS4gIEJhY2t3YXJkIENvbXBhdGliaWxp
dHkgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDxzcGFuIGNsYXNzPSJk
ZWxldGUiPjEyPC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICA1LiAg
QmFja3dhcmQgQ29tcGF0aWJpbGl0eSAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAgPHNwYW4gY2xhc3M9Imluc2VydCI+MTU8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsYmxvY2siPiAgIDYuICBJQU5BIENvbnNpZGVyYXRpb25zIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuICA8c3BhbiBjbGFzcz0iZGVsZXRlIj4xMzwvc3Bhbj48L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgNi4gIElBTkEgQ29uc2lkZXJhdGlvbnMg
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDxzcGFuIGNsYXNzPSJp
bnNlcnQiPjE2PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAgIDYuMS4g
IE5ldyBQQ0VQIE1lc3NhZ2UgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+MTM8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyYmxvY2siPiAgICAgNi4xLiAgTmV3IFBDRVAgTWVzc2FnZSAgLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuICA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij4xNjwvc3Bhbj48L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgICA2LjIuICBOZXcgRXJyb3ItVmFsdWVzICAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDxzcGFuIGNsYXNzPSJkZWxl
dGUiPjEzPC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAgIDYuMi4g
IE5ldyBFcnJvci1WYWx1ZXMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAgPHNwYW4gY2xhc3M9Imluc2VydCI+MTY8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
YmxvY2siPiAgIDcuICBTZWN1cml0eSBDb25zaWRlcmF0aW9ucyAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuICA8c3BhbiBjbGFzcz0iZGVsZXRlIj4xNDwvc3Bhbj48L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgNy4gIFNlY3VyaXR5IENvbnNpZGVyYXRpb25z
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDxzcGFuIGNsYXNzPSJpbnNl
cnQiPjE3PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICA4LiAgTWFuYWdl
YWJpbGl0eSBDb25zaWRlcmF0aW9ucyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAg
PHNwYW4gY2xhc3M9ImRlbGV0ZSI+MTU8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
YmxvY2siPiAgIDguICBNYW5hZ2VhYmlsaXR5IENvbnNpZGVyYXRpb25zICAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuICA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij4xODwvc3Bhbj48L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgICA4LjEuICBDb250cm9sIG9mIEZ1bmN0aW9uIGFu
ZCBQb2xpY3kgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDxzcGFuIGNsYXNzPSJkZWxldGUi
PjE1PC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAgIDguMS4gIENv
bnRyb2wgb2YgRnVuY3Rpb24gYW5kIFBvbGljeSAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAg
PHNwYW4gY2xhc3M9Imluc2VydCI+MTg8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxv
Y2siPiAgICAgOC4yLiAgSW5mb3JtYXRpb24gYW5kIERhdGEgTW9kZWxzIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuICA8c3BhbiBjbGFzcz0iZGVsZXRlIj4xNjwvc3Bhbj48L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgICA4LjIuICBJbmZvcm1hdGlvbiBhbmQgRGF0YSBN
b2RlbHMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDxzcGFuIGNsYXNzPSJpbnNlcnQi
PjE5PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAgIDguMy4gIExpdmVu
ZXNzIERldGVjdGlvbiBhbmQgTW9uaXRvcmluZyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgPHNw
YW4gY2xhc3M9ImRlbGV0ZSI+MTY8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxv
Y2siPiAgICAgOC4zLiAgTGl2ZW5lc3MgRGV0ZWN0aW9uIGFuZCBNb25pdG9yaW5nIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuICA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij4xOTwvc3Bhbj48L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgICA4LjQuICBWZXJpZnlpbmcgQ29ycmVjdCBPcGVyYXRp
b25zICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDxzcGFuIGNsYXNzPSJkZWxldGUiPjE2
PC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAgIDguNC4gIFZlcmlm
eWluZyBDb3JyZWN0IE9wZXJhdGlvbnMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgPHNw
YW4gY2xhc3M9Imluc2VydCI+MTk8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2si
PiAgICAgOC41LiAgUmVxdWlyZW1lbnRzIG9uIE90aGVyIFByb3RvY29scyAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuICA8c3BhbiBjbGFzcz0iZGVsZXRlIj4xNjwvc3Bhbj48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJibG9jayI+ICAgICA4LjUuICBSZXF1aXJlbWVudHMgb24gT3RoZXIgUHJv
dG9jb2xzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDxzcGFuIGNsYXNzPSJpbnNlcnQiPjE5
PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAgIDguNi4gIEltcGFjdCBv
biBOZXR3b3JrIE9wZXJhdGlvbiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgPHNwYW4g
Y2xhc3M9ImRlbGV0ZSI+MTY8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2si
PiAgICAgOC42LiAgSW1wYWN0IG9uIE5ldHdvcmsgT3BlcmF0aW9uIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuICA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij4xOTwvc3Bhbj48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxibG9jayI+ICAgOS4gIEFja25vd2xlZGdlbWVudHMgIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDxzcGFuIGNsYXNzPSJkZWxldGUiPjE2PC9z
cGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICA5LiAgQWNrbm93bGVkZ2Vt
ZW50cyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgPHNwYW4g
Y2xhc3M9Imluc2VydCI+MTk8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAg
IDEwLiBSZWZlcmVuY2VzICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuICA8c3BhbiBjbGFzcz0iZGVsZXRlIj4xNzwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJibG9jayI+ICAgMTAuIFJlZmVyZW5jZXMgIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDxzcGFuIGNsYXNzPSJpbnNlcnQiPjIwPC9z
cGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAgIDEwLjEuICBOb3JtYXRpdmUg
UmVmZXJlbmNlcyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgPHNwYW4gY2xh
c3M9ImRlbGV0ZSI+MTc8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAg
ICAgMTAuMS4gIE5vcm1hdGl2ZSBSZWZlcmVuY2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuICA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij4yMDwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQg
Y2xhc3M9ImxibG9jayI+ICAgICAxMC4yLiAgSW5mb3JtYXRpdmUgUmVmZXJlbmNlcyAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDxzcGFuIGNsYXNzPSJkZWxldGUiPjE4PC9zcGFu
PjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAgIDEwLjIuICBJbmZvcm1hdGl2
ZSBSZWZlcmVuY2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgPHNwYW4gY2xh
c3M9Imluc2VydCI+MjE8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIEF1
dGhvcnMnIEFkZHJlc3NlcyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuICA8c3BhbiBjbGFzcz0iZGVsZXRlIj4yMDwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJibG9jayI+ICAgQXV0aG9ycycgQWRkcmVzc2VzICAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDxzcGFuIGNsYXNzPSJpbnNlcnQiPjIzPC9zcGFu
PjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4xLiAgSW50cm9kdWN0aW9uPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+MS4gIEludHJvZHVjdGlvbjwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBUaGUgUGF0aCBDb21wdXRhdGlvbiBFbGVtZW50IENvbW11
bmljYXRpb24gUHJvdG9jb2wgKFBDRVApIFtSRkM1NDQwXTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgIFRoZSBQYXRoIENvbXB1dGF0aW9uIEVsZW1lbnQgQ29tbXVuaWNhdGlvbiBQ
cm90b2NvbCAoUENFUCkgW1JGQzU0NDBdPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBk
ZWZpbmVzIHRoZSBtZWNoYW5pc21zIGZvciB0aGUgY29tbXVuaWNhdGlvbiBiZXR3ZWVuIGEgUGF0
aDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGRlZmluZXMgdGhlIG1lY2hhbmlz
bXMgZm9yIHRoZSBjb21tdW5pY2F0aW9uIGJldHdlZW4gYSBQYXRoPC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij4gICBDb21wdXRhdGlvbiBDbGllbnQgKFBDQykgYW5kIGEgUGF0aCBDb21wdXRh
dGlvbiBFbGVtZW50IChQQ0UpLCBvcjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAg
IENvbXB1dGF0aW9uIENsaWVudCAoUENDKSBhbmQgYSBQYXRoIENvbXB1dGF0aW9uIEVsZW1lbnQg
KFBDRSksIG9yPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBiZXR3ZWVuIHR3byBQQ0Vz
LiAgVGhlc2UgaW50ZXJhY3Rpb25zIGluY2x1ZGUgcmVxdWVzdHMgYW5kIHJlcGxpZXM8L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBiZXR3ZWVuIHR3byBQQ0VzLiAgVGhlc2UgaW50
ZXJhY3Rpb25zIGluY2x1ZGUgcmVxdWVzdHMgYW5kIHJlcGxpZXM8L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPiAgIHRoYXQgY2FuIGJlIGNyaXRpY2FsIGZvciBhIHN1c3RhaW5hYmxlIG5ldHdv
cmsgb3BlcmF0aW9uIGFuZCBhZGVxdWF0ZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgIHRoYXQgY2FuIGJlIGNyaXRpY2FsIGZvciBhIHN1c3RhaW5hYmxlIG5ldHdvcmsgb3BlcmF0
aW9uIGFuZCBhZGVxdWF0ZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgcmVzb3VyY2Ug
YWxsb2NhdGlvbiwgYW5kIHRoZXJlZm9yZSBhcHByb3ByaWF0ZSBzZWN1cml0eSBiZWNvbWVzIGEg
a2V5PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgcmVzb3VyY2UgYWxsb2NhdGlv
biwgYW5kIHRoZXJlZm9yZSBhcHByb3ByaWF0ZSBzZWN1cml0eSBiZWNvbWVzIGEga2V5PC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBlbGVtZW50IGluIHRoZSBQQ0UgaW5mcmFzdHJ1Y3R1
cmUuICBBcyB0aGUgYXBwbGljYXRpb25zIG9mIHRoZSBQQ0U8L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICBlbGVtZW50IGluIHRoZSBQQ0UgaW5mcmFzdHJ1Y3R1cmUuICBBcyB0aGUg
YXBwbGljYXRpb25zIG9mIHRoZSBQQ0U8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyIGlkPSJwYXJ0LTQiIGNsYXNzPSJjaGFuZ2UiPjx0ZD48L3RkPjx0aD48
c21hbGw+c2tpcHBpbmcgdG8gY2hhbmdlIGF0PC9zbWFsbD48YSBocmVmPSJodHRwczovL3Rvb2xz
LmlldGYub3JnL3JmY2RpZmYjcGFydC00Ij48ZW0+IHBhZ2UgNCwgbGluZSA1MTxzcGFuIGNsYXNz
PSJoaWRlIj4gwrY8L3NwYW4+PC9lbT48L2E+PC90aD48dGg+IDwvdGg+PHRoPjxzbWFsbD5za2lw
cGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcv
cmZjZGlmZiNwYXJ0LTQiPjxlbT4gcGFnZSA0LCBsaW5lIDUxPHNwYW4gY2xhc3M9ImhpZGUiPiDC
tjwvc3Bhbj48L2VtPjwvYT48L3RoPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjMuMi4gIEluaXRpYXRpbmcgdGhlIFRMUyBQ
cm9jZWR1cmVzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+My4yLiAgSW5pdGlhdGlu
ZyB0aGUgVExTIFByb2NlZHVyZXM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
U2luY2UgUENFUCBjYW4gb3BlcmF0ZSBlaXRoZXIgd2l0aCBvciB3aXRob3V0IFRMUywgaXQgaXMg
bmVjZXNzYXJ5PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgU2luY2UgUENFUCBj
YW4gb3BlcmF0ZSBlaXRoZXIgd2l0aCBvciB3aXRob3V0IFRMUywgaXQgaXMgbmVjZXNzYXJ5PC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBmb3IgdGhlIFBDRVAgc3BlYWtlciB0byBpbmRp
Y2F0ZSB3aGV0aGVyIGl0IHdhbnRzIHRvIHNldCB1cCBhIFRMUzwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgIGZvciB0aGUgUENFUCBzcGVha2VyIHRvIGluZGljYXRlIHdoZXRoZXIg
aXQgd2FudHMgdG8gc2V0IHVwIGEgVExTPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBj
b25uZWN0aW9uIG9yIG5vdC4gIEZvciB0aGlzIHB1cnBvc2UsIHRoaXMgZG9jdW1lbnQgc3BlY2lm
aWVzIGEgbmV3PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgY29ubmVjdGlvbiBv
ciBub3QuICBGb3IgdGhpcyBwdXJwb3NlLCB0aGlzIGRvY3VtZW50IHNwZWNpZmllcyBhIG5ldzwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgUENFUCBtZXNzYWdlIGNhbGxlZCBTdGFydFRM
Uy4gIFRodXMgdGhlIFBDRVAgc2Vzc2lvbiBpcyBzZWN1cmVkIHZpYTwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmlnaHQiPiAgIFBDRVAgbWVzc2FnZSBjYWxsZWQgU3RhcnRUTFMuICBUaHVzIHRo
ZSBQQ0VQIHNlc3Npb24gaXMgc2VjdXJlZCB2aWE8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PiAgIFRMUyBmcm9tIHRoZSBzdGFydCBiZWZvcmUgZXhjaGFuZ2Ugb2YgYW55IG90aGVyIFBDRVAg
bWVzc2FnZSAodGhhdDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFRMUyBmcm9t
IHRoZSBzdGFydCBiZWZvcmUgZXhjaGFuZ2Ugb2YgYW55IG90aGVyIFBDRVAgbWVzc2FnZSAodGhh
dDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgaW5jbHVkZXMgdGhlIE9wZW4gbWVzc2Fn
ZSkuICBUaGlzIGRvY3VtZW50IHRodXMgdXBkYXRlcyBbUkZDNTQ0MF0sPC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+ICAgaW5jbHVkZXMgdGhlIE9wZW4gbWVzc2FnZSkuICBUaGlzIGRv
Y3VtZW50IHRodXMgdXBkYXRlcyBbUkZDNTQ0MF0sPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij4gICB3aGljaCByZXF1aXJlZCB0aGUgT3BlbiBtZXNzYWdlIHRvIGJlIHRoZSBmaXJzdCBQQ0VQ
IG1lc3NhZ2UuICBJbiB0aGU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICB3aGlj
aCByZXF1aXJlZCB0aGUgT3BlbiBtZXNzYWdlIHRvIGJlIHRoZSBmaXJzdCBQQ0VQIG1lc3NhZ2Uu
ICBJbiB0aGU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGNhc2Ugb2YgYSBQQ0VQIHNl
c3Npb24gdXNpbmcgVExTIHRoZSBTdGFydFRMUyBtZXNzYWdlIHdpbGwgYmUgc2VudDwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGNhc2Ugb2YgYSBQQ0VQIHNlc3Npb24gdXNpbmcg
VExTIHRoZSBTdGFydFRMUyBtZXNzYWdlIHdpbGwgYmUgc2VudDwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJkaWZmMDAwNSI+PHRkPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBmaXJz
dC48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgZmlyc3QuICA8c3BhbiBjbGFz
cz0iaW5zZXJ0Ij5BbHNvIGEgUENFUCBzcGVha2VyIHRoYXQgc3VwcG9ydHMgUENFUFMgTVVTVCBO
T1Qgc3RhcnQgdGhlPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgT3Blbldh
aXQgdGltZXIgYWZ0ZXIgdGhlIFRDUCBlc3RhYmxpc2htZW50LCBpbnN0ZWFkIGl0IHN0YXJ0cyBh
PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgU3RhcnRUTFNXYWl0IHRpbWVy
IGFzIGRlc2NyaWJlZCBpbiBTZWN0aW9uIDMuMy48L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQg
Y2xhc3M9ImxlZnQiPiAgIFRoZSBQQ0VQIHNwZWFrZXIgTUFZIGRpc2NvdmVyIHRoYXQgdGhlIFBD
RVAgcGVlciBzdXBwb3J0cyBQQ0VQUyBvcjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgIFRoZSBQQ0VQIHNwZWFrZXIgTUFZIGRpc2NvdmVyIHRoYXQgdGhlIFBDRVAgcGVlciBzdXBw
b3J0cyBQQ0VQUyBvcjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgY2FuIGJlIHByZWNv
bmZpZ3VyZWQgdG8gdXNlIFBDRVBTIGZvciBhIGdpdmVuIHBlZXIgKHNlZSBTZWN0aW9uIDQgZm9y
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgY2FuIGJlIHByZWNvbmZpZ3VyZWQg
dG8gdXNlIFBDRVBTIGZvciBhIGdpdmVuIHBlZXIgKHNlZSBTZWN0aW9uIDQgZm9yPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBtb3JlIGRldGFpbHMpLiAgU2VjdXJpbmcgdmlhIFRMUyBv
ZiBhbiBleGlzdGluZyBQQ0VQIHNlc3Npb24gaXMgbm90PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgbW9yZSBkZXRhaWxzKS4gIFNlY3VyaW5nIHZpYSBUTFMgb2YgYW4gZXhpc3Rp
bmcgUENFUCBzZXNzaW9uIGlzIG5vdDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgcGVy
bWl0dGVkLCB0aGUgc2Vzc2lvbiBNVVNUIGJlIGNsb3NlZCBhbmQgcmUtZXN0YWJsaXNoZWQgd2l0
aCBUTFMgYXM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBwZXJtaXR0ZWQsIHRo
ZSBzZXNzaW9uIE1VU1QgYmUgY2xvc2VkIGFuZCByZS1lc3RhYmxpc2hlZCB3aXRoIFRMUyBhczwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgcGVyIHRoZSBwcm9jZWR1cmUgZGVzY3JpYmVk
IGluIHRoaXMgZG9jdW1lbnQuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgcGVy
IHRoZSBwcm9jZWR1cmUgZGVzY3JpYmVkIGluIHRoaXMgZG9jdW1lbnQuPC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRoZSBTdGFydFRMUyBtZXNzYWdlIGlzIGEgUENFUCBtZXNz
YWdlIHNlbnQgYnkgYSBQQ0MgdG8gYSBQQ0UgYW5kIGJ5PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgVGhlIFN0YXJ0VExTIG1lc3NhZ2UgaXMgYSBQQ0VQIG1lc3NhZ2Ugc2VudCBi
eSBhIFBDQyB0byBhIFBDRSBhbmQgYnk8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGEg
UENFIHRvIGEgUENDIGluIG9yZGVyIHRvIGluaXRpYXRlIHRoZSBUTFMgcHJvY2VkdXJlIGZvciBQ
Q0VQLiAgVGhlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgYSBQQ0UgdG8gYSBQ
Q0MgaW4gb3JkZXIgdG8gaW5pdGlhdGUgdGhlIFRMUyBwcm9jZWR1cmUgZm9yIFBDRVAuICBUaGU8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIE1lc3NhZ2UtVHlwZSBmaWVsZCBvZiB0aGUg
UENFUCBjb21tb24gaGVhZGVyIGZvciB0aGUgU3RhcnRUTFMgbWVzc2FnZTwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPiAgIE1lc3NhZ2UtVHlwZSBmaWVsZCBvZiB0aGUgUENFUCBjb21t
b24gaGVhZGVyIGZvciB0aGUgU3RhcnRUTFMgbWVzc2FnZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9InBhcnQtNSIgY2xhc3M9ImNoYW5nZSI+PHRk
PjwvdGQ+PHRoPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxhIGhyZWY9Imh0
dHBzOi8vdG9vbHMuaWV0Zi5vcmcvcmZjZGlmZiNwYXJ0LTUiPjxlbT4gcGFnZSA1LCBsaW5lIDQw
PHNwYW4gY2xhc3M9ImhpZGUiPiDCtjwvc3Bhbj48L2VtPjwvYT48L3RoPjx0aD4gPC90aD48dGg+
PHNtYWxsPnNraXBwaW5nIHRvIGNoYW5nZSBhdDwvc21hbGw+PGEgaHJlZj0iaHR0cHM6Ly90b29s
cy5pZXRmLm9yZy9yZmNkaWZmI3BhcnQtNSI+PGVtPiBwYWdlIDUsIGxpbmUgNDI8c3BhbiBjbGFz
cz0iaGlkZSI+IMK2PC9zcGFuPjwvZW0+PC9hPjwvdGg+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgKFBDRVAgU3RhcnRU
TFMgZmFpbHVyZSkgYW5kIEVycm9yLXZhbHVlIHNldCB0byAyIChyZWNlcHRpb24gb2YgYW55PC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgKFBDRVAgU3RhcnRUTFMgZmFpbHVyZSkg
YW5kIEVycm9yLXZhbHVlIHNldCB0byAyIChyZWNlcHRpb24gb2YgYW55PC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij4gICBvdGhlciBtZXNzYWdlIGFwYXJ0IGZyb20gU3RhcnRUTFMsIE9wZW4s
IG9yIFBDRXJyIG1lc3NhZ2UpLCBhbmQgTVVTVDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgIG90aGVyIG1lc3NhZ2UgYXBhcnQgZnJvbSBTdGFydFRMUywgT3Blbiwgb3IgUENFcnIg
bWVzc2FnZSksIGFuZCBNVVNUPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBjbG9zZSB0
aGUgVENQIGNvbm5lY3Rpb24uPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgY2xv
c2UgdGhlIFRDUCBjb25uZWN0aW9uLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICBJZiB0aGUgUENFUCBzcGVha2VyIHRoYXQgZG9lcyBub3Qgc3VwcG9ydCBQQ0VQUywgcmVjZWl2
ZXMgYSBTdGFydFRMUzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIElmIHRoZSBQ
Q0VQIHNwZWFrZXIgdGhhdCBkb2VzIG5vdCBzdXBwb3J0IFBDRVBTLCByZWNlaXZlcyBhIFN0YXJ0
VExTPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBtZXNzYWdlLCBpdCB3aWxsIGJlaGF2
ZSBhY2NvcmRpbmcgdG8gdGhlIGV4aXN0aW5nIGVycm9yIG1lY2hhbmlzbTwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPiAgIG1lc3NhZ2UsIGl0IHdpbGwgYmVoYXZlIGFjY29yZGluZyB0
byB0aGUgZXhpc3RpbmcgZXJyb3IgbWVjaGFuaXNtPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij4gICBkZXNjcmliZWQgaW4gc2VjdGlvbiA2LjIgb2YgW1JGQzU0NDBdIChpbiBjYXNlIG1lc3Nh
Z2UgaXMgcmVjZWl2ZWQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBkZXNjcmli
ZWQgaW4gc2VjdGlvbiA2LjIgb2YgW1JGQzU0NDBdIChpbiBjYXNlIG1lc3NhZ2UgaXMgcmVjZWl2
ZWQ8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHByaW9yIHRvIGFuIE9wZW4gbWVzc2Fn
ZSkgb3Igc2VjdGlvbiA2Ljkgb2YgW1JGQzU0NDBdIChmb3IgdGhlIGNhc2U8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBwcmlvciB0byBhbiBPcGVuIG1lc3NhZ2UpIG9yIHNlY3Rp
b24gNi45IG9mIFtSRkM1NDQwXSAoZm9yIHRoZSBjYXNlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij4gICBvZiByZWNlcHRpb24gb2YgdW5rbm93biBtZXNzYWdlKS4gIFNlZSBTZWN0aW9uIDUg
Zm9yIG1vcmUgZGV0YWlscy48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBvZiBy
ZWNlcHRpb24gb2YgdW5rbm93biBtZXNzYWdlKS4gIFNlZSBTZWN0aW9uIDUgZm9yIG1vcmUgZGV0
YWlscy48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlk
PSJkaWZmMDAwNiI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+
ICAgPHNwYW4gY2xhc3M9Imluc2VydCI+SWYgdGhlIFBDRVAgc3BlYWtlciB0aGF0IG9ubHkgc3Vw
cG9ydHMgUENFUFMgY29ubmVjdGlvbiAoYXMgYSBsb2NhbDwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQg
Y2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNs
YXNzPSJpbnNlcnQiPiAgIHBvbGljeSksIHJlY2VpdmVzIGFuIE9wZW4gbWVzc2FnZSwgaXQgTVVT
VCB0cmVhdCBpdCBhcyBhbiB1bmV4cGVjdGVkPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imlu
c2VydCI+ICAgbWVzc2FnZSBhbmQgcmVwbHkgd2l0aCBhIFBDRXJyIG1lc3NhZ2Ugd2l0aCBFcnJv
ci1UeXBlIHNldCB0byAxIChQQ0VQPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2Nr
Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+
ICAgc2Vzc2lvbiBlc3RhYmxpc2htZW50IGZhaWx1cmUpIGFuZCBFcnJvci12YWx1ZSBzZXQgdG8g
MSAocmVjZXB0aW9uIG9mPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgYW4g
aW52YWxpZCBPcGVuIG1lc3NhZ2Ugb3IgYSBub24gT3BlbiBtZXNzYWdlKSwgYW5kIE1VU1QgY2xv
c2UgdGhlPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgVENQIGNvbm5lY3Rp
b24uPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+PC9zcGFuPjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNw
YW4gY2xhc3M9Imluc2VydCI+ICAgSWYgYSBQQ0MgdGhhdCBzdXBwb3J0cyBQQ0VQUyBjb25uZWN0
aW9uIGFzIHdlbGwgYXMgYWxsb3cgbm9uLVBDRVBTPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9
Imluc2VydCI+ICAgY29ubmVjdGlvbiAoYXMgYSBsb2NhbCBwb2xpY3kpLCBpdCBNVVNUIGZpcnN0
IHRyeSB0byBlc3RhYmxpc2ggUENFUFMsPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJs
b2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2Vy
dCI+ICAgYnkgc2VuZGluZyBTdGFydFRMUyBtZXNzYWdlIGFuZCBpbiBjYXNlIGl0IHJlY2VpdmVz
IGFuIFBDRXJyIGZyb20gdGhlPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAg
UENFLCBpdCBNQVkgcmV0cnkgdG8gZXN0YWJsaXNoIGNvbm5lY3Rpb24gd2l0aG91dCBQQ0VQUyBi
eSBzZW5kaW5nIGFuPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgT3BlbiBt
ZXNzYWdlLiAgSWYgYSBQQ0UgdGhhdCBzdXBwb3J0cyBQQ0VQUyBjb25uZWN0aW9uIGFzIHdlbGwg
YXM8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICBhbGxvdyBub24tUENFUFMg
Y29ubmVjdGlvbiAoYXMgYSBsb2NhbCBwb2xpY3kpLCBpdCBNVVNUIHdhaXQgdG88L3NwYW4+PC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJs
b2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICByZXNwb25kIGFmdGVyIFRDUCBlc3RhYmxpc2ht
ZW50LCBiYXNlZCBvbiB0aGUgbWVzc2FnZSByZWNlaXZlZCBmcm9tPC9zcGFuPjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNw
YW4gY2xhc3M9Imluc2VydCI+ICAgdGhlIFBDQy4gIEluIGNhc2Ugb2YgU3RhcnRUTFMgbWVzc2Fn
ZSwgUENFIHJlc3BvbmRzIHdpdGggc2VuZGluZzwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJp
bnNlcnQiPiAgIFN0YXJ0VExTIG1lc3NhZ2UgYW5kIG1vdmluZyB0byBUTFMgZXN0YWJsaXNobWVu
dCBwcm9jZWR1cmVzIGFzPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgZGVz
Y3JpYmVkIGluIHRoaXMgZG9jdW1lbnQuICBJbiBjYXNlIG9mIE9wZW4gbWVzc2FnZSwgUENFIHJl
c3BvbmRzPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgd2l0aCBPcGVuIG1l
c3NhZ2UgYW5kIG1vdmUgdG8gUENFUCBzZXNzaW9uIGVzdGFibGlzaG1lbnQgcHJvY2VkdXJlIGFz
PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgcGVyIFtSRkM1NDQwXS48L3Nw
YW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmJsb2NrIj4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICBBZnRlciB0aGUgZXhjaGFuZ2Ugb2YgU3RhcnRUTFMgbWVzc2FnZXMsIGlmIGEgUENFUCBzcGVh
a2VyIGNhbm5vdDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIEFmdGVyIHRoZSBl
eGNoYW5nZSBvZiBTdGFydFRMUyBtZXNzYWdlcywgaWYgYSBQQ0VQIHNwZWFrZXIgY2Fubm90PC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBlc3RhYmxpc2ggYSBUTFMgY29ubmVjdGlvbiBm
b3Igc29tZSByZWFzb24gKGUuZy4gdGhlIHJlcXVpcmVkPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgZXN0YWJsaXNoIGEgVExTIGNvbm5lY3Rpb24gZm9yIHNvbWUgcmVhc29uIChl
LmcuIHRoZSByZXF1aXJlZDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgbWVjaGFuaXNt
cyBmb3IgY2VydGlmaWNhdGUgcmV2b2NhdGlvbiBjaGVja2luZyBhcmUgbm90IGF2YWlsYWJsZSks
IGl0PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgbWVjaGFuaXNtcyBmb3IgY2Vy
dGlmaWNhdGUgcmV2b2NhdGlvbiBjaGVja2luZyBhcmUgbm90IGF2YWlsYWJsZSksIGl0PC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBNVVNUIHJldHVybiBhIFBDRXJyIG1lc3NhZ2UgKGlu
IGNsZWFyKSB3aXRoIEVycm9yLVR5cGUgc2V0IHRvIFtUQkEyPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgTVVTVCByZXR1cm4gYSBQQ0VyciBtZXNzYWdlIChpbiBjbGVhcikgd2l0
aCBFcnJvci1UeXBlIHNldCB0byBbVEJBMjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
YnkgSUFOQV0gKFBDRVAgU3RhcnRUTFMgZmFpbHVyZSkgYW5kIEVycm9yLXZhbHVlIHNldCB0bzo8
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBieSBJQU5BXSAoUENFUCBTdGFydFRM
UyBmYWlsdXJlKSBhbmQgRXJyb3ItdmFsdWUgc2V0IHRvOjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij4gICBvICAzIChub3Qgd2l0aG91dCBUTFMpIGlmIGl0IGlzIG5vdCB3aWxsaW5n
IHRvIGV4Y2hhbmdlIFBDRVAgbWVzc2FnZXM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICBvICAzIChub3Qgd2l0aG91dCBUTFMpIGlmIGl0IGlzIG5vdCB3aWxsaW5nIHRvIGV4Y2hh
bmdlIFBDRVAgbWVzc2FnZXM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIHdpdGhv
dXQgdGhlIHNvbGljaXRlZCBUTFMgY29ubmVjdGlvbiwgYW5kIGl0IE1VU1QgY2xvc2UgdGhlIFRD
UDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIHdpdGhvdXQgdGhlIHNvbGlj
aXRlZCBUTFMgY29ubmVjdGlvbiwgYW5kIGl0IE1VU1QgY2xvc2UgdGhlIFRDUDwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgc2Vzc2lvbi48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICAgICBzZXNzaW9uLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0icGFydC02IiBjbGFzcz0iY2hhbmdlIj48dGQ+PC90ZD48
dGg+PHNtYWxsPnNraXBwaW5nIHRvIGNoYW5nZSBhdDwvc21hbGw+PGEgaHJlZj0iaHR0cHM6Ly90
b29scy5pZXRmLm9yZy9yZmNkaWZmI3BhcnQtNiI+PGVtPiBwYWdlIDcsIGxpbmUgMTA8c3BhbiBj
bGFzcz0iaGlkZSI+IMK2PC9zcGFuPjwvZW0+PC9hPjwvdGg+PHRoPiA8L3RoPjx0aD48c21hbGw+
c2tpcHBpbmcgdG8gY2hhbmdlIGF0PC9zbWFsbD48YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYu
b3JnL3JmY2RpZmYjcGFydC02Ij48ZW0+IHBhZ2UgNywgbGluZSAyOTxzcGFuIGNsYXNzPSJoaWRl
Ij4gwrY8L3NwYW4+PC9lbT48L2E+PC90aD48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBleGNoYW5nZSBvZiBPcGVuIG1l
c3NhZ2VzIE1VU1QgYmUgYXBwbGllZCBieSB0aGUgUENFUCBwZWVycyBkdXJpbmc8L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBleGNoYW5nZSBvZiBPcGVuIG1lc3NhZ2VzIE1VU1Qg
YmUgYXBwbGllZCBieSB0aGUgUENFUCBwZWVycyBkdXJpbmc8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgIHRoZSBleGNoYW5nZSBvZiBTdGFydFRMUyBtZXNzYWdlcy48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICB0aGUgZXhjaGFuZ2Ugb2YgU3RhcnRUTFMgbWVzc2FnZXMu
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRoZSBmb3JtYXQgb2YgYSBTdGFy
dFRMUyBtZXNzYWdlIGlzIGFzIGZvbGxvd3M6PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+ICAgVGhlIGZvcm1hdCBvZiBhIFN0YXJ0VExTIG1lc3NhZ2UgaXMgYXMgZm9sbG93czo8L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgJmx0O1N0YXJ0VExTIE1lc3NhZ2Um
Z3Q7Ojo9ICZsdDtDb21tb24gSGVhZGVyJmd0OzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgICAgICZsdDtTdGFydFRMUyBNZXNzYWdlJmd0Ozo6PSAmbHQ7Q29tbW9uIEhlYWRlciZn
dDs8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgVGhlIFN0YXJ0VExTIG1lc3Nh
Z2UgTVVTVCBjb250YWluIG9ubHkgdGhlIFBDRVAgY29tbW9uIGhlYWRlciB3aXRoPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgVGhlIFN0YXJ0VExTIG1lc3NhZ2UgTVVTVCBjb250
YWluIG9ubHkgdGhlIFBDRVAgY29tbW9uIGhlYWRlciB3aXRoPC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICBNZXNzYWdlLVR5cGUgZmllbGQgc2V0IHRvIFtUQkExIGJ5IElBTkFdLjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIE1lc3NhZ2UtVHlwZSBmaWVsZCBzZXQgdG8g
W1RCQTEgYnkgSUFOQV0uPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0ciBpZD0iZGlmZjAwMDciPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgT25jZSB0aGUgVENQIGNvbm5lY3Rp
b24gaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IDxzcGFuIGNsYXNzPSJkZWxldGUiPmVzdGFibGlzaGVk
IGFuZDwvc3Bhbj4gdGhlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIE9uY2Ug
dGhlIFRDUCBjb25uZWN0aW9uIGhhcyBiZWVuIHN1Y2Nlc3NmdWxseSA8c3BhbiBjbGFzcz0iaW5z
ZXJ0Ij5lc3RhYmxpc2hlZCw8L3NwYW4+IHRoZSA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5QQ0VQPC9z
cGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICA8c3BhbiBjbGFzcz0iZGVsZXRl
Ij5TdGFydFRMUyBtZXNzYWdlIHNlbnQsIHRoZSBzZW5kZXI8L3NwYW4+IE1VU1Qgc3RhcnQgYSB0
aW1lciBjYWxsZWQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9
Imluc2VydCI+ICAgc3BlYWtlcjwvc3Bhbj4gTVVTVCBzdGFydCBhIHRpbWVyIGNhbGxlZCBTdGFy
dFRMU1dhaXQgdGltZXIsIGFmdGVyIHRoZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4g
ICBTdGFydFRMU1dhaXQgdGltZXIsIGFmdGVyIHRoZSBleHBpcmF0aW9uIG9mIHdoaWNoLCBpZiA8
c3BhbiBjbGFzcz0iZGVsZXRlIj5ubzwvc3Bhbj4gU3RhcnRUTFM8L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJibG9jayI+ICAgZXhwaXJhdGlvbiBvZiB3aGljaCwgaWYgPHNwYW4gY2xhc3M9Imlu
c2VydCI+bmVpdGhlcjwvc3Bhbj4gU3RhcnRUTFMgbWVzc2FnZSBoYXMgYmVlbiA8c3BhbiBjbGFz
cz0iaW5zZXJ0Ij5yZWNlaXZlZCw8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2si
PiAgIG1lc3NhZ2UgaGFzIGJlZW4gPHNwYW4gY2xhc3M9ImRlbGV0ZSI+cmVjZWl2ZWQgKGFuZCBp
bjwvc3Bhbj4gY2FzZSBvZiA8c3BhbiBjbGFzcz0iZGVsZXRlIj5mYWlsdXJlLCBhIFBDRXJyIG9y
IE9wZW48L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNz
PSJpbnNlcnQiPiAgIG5vciBhIFBDRXJyL09wZW4gKGluPC9zcGFuPiBjYXNlIG9mIDxzcGFuIGNs
YXNzPSJpbnNlcnQiPmZhaWx1cmUgYW5kIFBDRVBTPC9zcGFuPiBub3QgPHNwYW4gY2xhc3M9Imlu
c2VydCI+c3VwcG9ydGVkIGJ5IHRoZTwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9j
ayI+PHNwYW4gY2xhc3M9ImRlbGV0ZSI+ICAgbWVzc2FnZSBpczwvc3Bhbj4gbm90IDxzcGFuIGNs
YXNzPSJkZWxldGUiPnJlY2VpdmVkKSw8L3NwYW4+IGl0IE1VU1Qgc2VuZCBhIFBDRXJyIG1lc3Nh
Z2Ugd2l0aCA8c3BhbiBjbGFzcz0iZGVsZXRlIj5FcnJvci08L3NwYW4+PC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgIHBlZXIgcmVzcGVjdGl2
ZWx5KSw8L3NwYW4+IGl0IE1VU1Qgc2VuZCBhIFBDRXJyIG1lc3NhZ2Ugd2l0aCA8c3BhbiBjbGFz
cz0iaW5zZXJ0Ij5FcnJvci1UeXBlPC9zcGFuPiBzZXQ8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxi
bG9jayI+PHNwYW4gY2xhc3M9ImRlbGV0ZSI+ICAgVHlwZTwvc3Bhbj4gc2V0IHRvIFtUQkEyIGJ5
IElBTkFdIGFuZCBFcnJvci12YWx1ZSBzZXQgdG8gNSAobm8gU3RhcnRUTFMgKG5vcjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICB0byBbVEJBMiBieSBJQU5BXSBhbmQgRXJyb3It
dmFsdWUgc2V0IHRvIDUgKG5vIFN0YXJ0VExTIChub3IgPHNwYW4gY2xhc3M9Imluc2VydCI+UENF
cnIvPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICA8c3BhbiBjbGFzcz0i
ZGVsZXRlIj5QQ0Vyci9PcGVuKTwvc3Bhbj4gbWVzc2FnZSByZWNlaXZlZCBiZWZvcmUgdGhlIGV4
cGlyYXRpb24gb2YgdGhlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNs
YXNzPSJpbnNlcnQiPiAgIE9wZW4pPC9zcGFuPiBtZXNzYWdlIHJlY2VpdmVkIGJlZm9yZSB0aGUg
ZXhwaXJhdGlvbiBvZiB0aGUgU3RhcnRUTFNXYWl0PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxv
Y2siPiAgIFN0YXJ0VExTV2FpdCB0aW1lcikgYW5kIGl0IE1VU1QgcmVsZWFzZSB0aGUgVENQIGNv
bm5lY3Rpb24gLiBBPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIHRpbWVyKSBh
bmQgaXQgTVVTVCByZWxlYXNlIHRoZSBUQ1AgY29ubmVjdGlvbiAuIEEgUkVDT01NRU5ERUQgdmFs
dWU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgUkVDT01NRU5ERUQgdmFsdWUgZm9y
IFN0YXJ0VExTV2FpdCB0aW1lciBpcyA2MCBzZWNvbmRzLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmJsb2NrIj4gICBmb3IgU3RhcnRUTFNXYWl0IHRpbWVyIGlzIDYwIHNlY29uZHMuICA8c3Bh
biBjbGFzcz0iaW5zZXJ0Ij5UaGUgdmFsdWUgb2YgU3RhcnRUTFNXYWl0PC9zcGFuPjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+
PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgdGltZXIgTVVTVCBOT1QgYmUgbGVzcyB0aGFuIE9wZW5X
YWl0IHRpbWVyLjwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAg
ICAgICAgICAgICAgKy0rLSsgICAgICAgICAgICAgICAgICstKy0rPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICAgICAgKy0rLSsgICAgICAgICAgICAgICAgICst
Ky0rPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgICB8UENDfCAg
ICAgICAgICAgICAgICAgfFBDRXw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAg
ICAgICAgICAgICAgICB8UENDfCAgICAgICAgICAgICAgICAgfFBDRXw8L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQg
Y2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICAgICstKy0rICAgICAgICAgICAgICAgICArLSst
KzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgICAgICstKy0r
ICAgICAgICAgICAgICAgICArLSstKzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAg
ICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgfDwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICAgICAgIHw8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICAgICAgfCBTdGFydFRM
UyAgICAgICAgICAgIHw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAg
ICAgICAgICAgIHwgU3RhcnRUTFMgICAgICAgICAgICB8PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij4gICAgICAgICAgICAgICAgICAgIHwgbXNnICAgICAgICAgICAgICAgICB8PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICAgICAgICB8IG1zZyAgICAgICAg
ICAgICAgICAgfDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAgICAg
ICB8LS0tLS0tLSAgICAgICAgICAgICAgfDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgICAgICAgICAgICAgICAgICAgfC0tLS0tLS0gICAgICAgICAgICAgIHw8L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICAgICAgfCAgICAgICBcICAgU3RhcnRUTFMg
IHw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgICAgICAgIHwg
ICAgICAgXCAgIFN0YXJ0VExTICB8PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAg
ICAgICAgICAgICAgIHwgICAgICAgIFwgIG1zZyAgICAgICB8PC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgICAgICAgICAgICAgICAgICB8ICAgICAgICBcICBtc2cgICAgICAgfDwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9InBhcnQt
NyIgY2xhc3M9ImNoYW5nZSI+PHRkPjwvdGQ+PHRoPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2Ug
YXQ8L3NtYWxsPjxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvcmZjZGlmZiNwYXJ0LTci
PjxlbT4gcGFnZSA3LCBsaW5lIDQyPHNwYW4gY2xhc3M9ImhpZGUiPiDCtjwvc3Bhbj48L2VtPjwv
YT48L3RoPjx0aD4gPC90aD48dGg+PHNtYWxsPnNraXBwaW5nIHRvIGNoYW5nZSBhdDwvc21hbGw+
PGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9yZmNkaWZmI3BhcnQtNyI+PGVtPiBwYWdl
IDgsIGxpbmUgMjc8c3BhbiBjbGFzcz0iaGlkZSI+IMK2PC9zcGFuPjwvZW0+PC9hPjwvdGg+PHRk
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+ICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAgLyAgLS0tLS0tLS0mZ3Q7fDwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgICAgICAgfCAgICAgICAg
IC8gIC0tLS0tLS0tJmd0O3w8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAg
ICAgICAgICAgfCAgICAgICAgLyAgICAgICAgICAgIHw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICAgICAgICAgICAgICAgICAgIHwgICAgICAgIC8gICAgICAgICAgICB8PC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgICAgIHwmbHQ7LS0tLS0tICAg
ICAgICAgICAgICB8PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAg
ICAgICAgICB8Jmx0Oy0tLS0tLSAgICAgICAgICAgICAgfDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+ICAgICAgICAgICAgICAgICAgICB8Ojo6Ojo6Ojo6VExTOjo6Ojo6Ojo6fDwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgICAgICAgfDo6Ojo6Ojo6OlRM
Uzo6Ojo6Ojo6Onw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICAg
ICAgfDo6Ojo6RXN0YWJsaXNobWVudDo6Onw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICAgICAgICAgICAgICAgICAgIHw6Ojo6OkVzdGFibGlzaG1lbnQ6Ojp8PC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAg
ICB8PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICAgICAgICB8
ICAgICAgICAgICAgICAgICAgICAgfDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAg
ICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgfDwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICAgICAgIHw8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICAgICAgfDo6Ojo6OjpQ
Q0VQOjo6Ojo6Ojo6Onw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAg
ICAgICAgICAgIHw6Ojo6Ojo6UENFUDo6Ojo6Ojo6Ojp8PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij4gICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICB8PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAgICAg
ICAgICAgICAgfDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHIgaWQ9ImRpZmYwMDA4Ij48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgICAgICAgICAgIDxzcGFuIGNsYXNzPSJkZWxl
dGUiPiAgICBGaWd1cmUgMTogQm90aCBQQ0VQIFNwZWFrZXIgc3VwcG9ydHMgUENFUFM8L3NwYW4+
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgICAgICAgICAgIDxzcGFuIGNsYXNz
PSJpbnNlcnQiPkZpZ3VyZSAxOiBCb3RoIFBDRVAgU3BlYWtlciBzdXBwb3J0cyBQQ0VQUyAoc3Ry
aWN0KTwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICAg
ICstKy0rICAgICAgICAgICAgICAgICArLSstKzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgICAgICAgICAgICAgICAgICstKy0rICAgICAgICAgICAgICAgICArLSstKzwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAgICAgfFBDQ3wgICAgICAgICAgICAg
ICAgIHxQQ0V8PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICAg
ICAgfFBDQ3wgICAgICAgICAgICAgICAgIHxQQ0V8PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij4gICAgICAgICAgICAgICAgICArLSstKyAgICAgICAgICAgICAgICAgKy0rLSs8L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgICAgICArLSstKyAgICAgICAgICAg
ICAgICAgKy0rLSs8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBp
ZD0iZGlmZjAwMDkiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgICAgICAgICAgICAgICAgICA8c3BhbiBjbGFzcz0i
ZGVsZXRlIj58ICAgICAgICAgICAgICAgICAgICAgfCBEb2VzIG5vdCBzZW5kPC9zcGFuPjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9j
ayI+PHNwYW4gY2xhc3M9ImRlbGV0ZSI+ICAgICAgICAgICAgICAgICAgICB8ICAgICAgU3RhcnRU
TFMgICAgICAgfCBTdGFydFRMUyBhczwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJi
bG9jayI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNsYXNzPSJkZWxldGUi
PiAgICAgICAgICAgICAgICAgICAgfC0tLS0tLS0tLS0tLS0tLS0tLS0tJmd0O3wgY2Fubm90IGVz
dGFibGlzaDwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNsYXNzPSJkZWxldGUiPiAgICAgICAgICAgICAg
ICAgICAgfCAgICAgICAgICAgICAgICAgICAgIHwgVExTPC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmJsb2NrIj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAg
ICAgICAgICAgfCAgICAgICAgICAgICAgICAgICAgIHw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICB8PC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9ImRpZmYwMDEwIj48dGQ+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
YmxvY2siPiAgICAgICAgICAgICAgICAgICAgfCZsdDstLS0tLS0tLS0tLS0tLS0tLS0tLXwgU2Vu
ZCA8c3BhbiBjbGFzcz0iZGVsZXRlIj5FcnJvcjwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJibG9jayI+ICAgICAgICAgICAgICAgICAgICA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij58IFN0
YXJ0VExTICAgICAgICAgICAgfDwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAg
ICAgICAgICAgICAgICAgICAgfCBtc2cgICAgICAgICAgICAgICAgIHw8L3NwYW4+PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48
c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICAgICAgICAgICAgICAgICAgIHwtLS0tLS0tICAgICAgICAg
ICAgICB8PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgICAgICAgICAgICAg
ICAgICB8ICAgICAgIFwgICBTdGFydFRMUyAgfDwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJp
bnNlcnQiPiAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgXCAgbXNnICAgICAgIHw8L3NwYW4+
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICAgICAgICAgICAgICAgICAgIHwgICAgICAg
ICBcICAtLS0tLS0tLS18PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgICAg
ICAgICAgICAgICAgICB8ICAgICAgICAgIFwvICAgICAgICAgfDwvc3Bhbj48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFu
IGNsYXNzPSJpbnNlcnQiPiAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAvXCAgICAgICAg
IHw8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICAgICAgICAgICAgICAgICAg
IHwgICAgICAgICAvICAtLS0tLS0tLSZndDt8PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imlu
c2VydCI+ICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAvICAgICAgICAgICAgfDwvc3Bhbj48
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
YmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgICAgICAgICAgICAgICAgICAgfCZsdDstLS0t
LS0gICAgICAgICAgICAgIHw8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICAg
ICAgICAgICAgICAgICAgIHw6Ojo6Ojo6OjpUTFM6Ojo6Ojo6Ojp8IFRMUyBFc3RhYmxpc2htZW50
PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgICAgICAgICAgICAgICAgICB8
Ojo6OjpFc3RhYmxpc2htZW50Ojo6fCBGYWlsdXJlPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9
Imluc2VydCI+ICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgfDwvc3Bh
bj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyYmxvY2siPiAgICAgICAgICAgICAgICAgICAgfCZsdDstLS0tLS0tLS0tLS0tLS0tLS0tLXwg
U2VuZCA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5FcnJvci1UeXBlIFRCQTI8L3NwYW4+PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgICAgIHwgICAgICBQQ0VyciAgICAg
ICAgICB8IEVycm9yLVZhbHVlIDMvNDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAg
ICAgICAgICAgICAgICAgICAgfCAgICAgIFBDRXJyICAgICAgICAgIHwgRXJyb3ItVmFsdWUgMy80
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgICAgIHwgICAgICAg
ICAgICAgICAgICAgICB8PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAg
ICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgfDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9ImRpZmYwMDExIj48dGQ+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIEZp
Z3VyZSAyOiBCb3RoIFBDRVAgU3BlYWtlciBzdXBwb3J0cyA8c3BhbiBjbGFzcz0iZGVsZXRlIj5Q
Q0VQUywgQnV0PC9zcGFuPiBjYW5ub3QgZXN0YWJsaXNoIFRMUzwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmJsb2NrIj4gICAgICBGaWd1cmUgMjogQm90aCBQQ0VQIFNwZWFrZXIgc3VwcG9ydHMg
PHNwYW4gY2xhc3M9Imluc2VydCI+UENFUFMgKHN0cmljdCksIGJ1dDwvc3Bhbj4gY2Fubm90PC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJs
b2NrIj4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgZXN0YWJsaXNoIFRMUzwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgICArLSstKyAgICAgICAg
ICAgICAgICAgKy0rLSs8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAg
ICAgICAgICArLSstKyAgICAgICAgICAgICAgICAgKy0rLSs8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgICAgICAgICAgICAgICAgIHxQQ0N8ICAgICAgICAgICAgICAgICB8UENFfDwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgICAgIHxQQ0N8ICAgICAg
ICAgICAgICAgICB8UENFfDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAg
ICAgICAgKy0rLSsgICAgICAgICAgICAgICAgICstKy0rPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgICAgICAgICAgICAgICAgKy0rLSsgICAgICAgICAgICAgICAgICstKy0rPC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAg
ICAgICAgICAgICB8ICBEb2VzIG5vdCBzdXBwb3J0PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+ICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgfCAgRG9lcyBu
b3Qgc3VwcG9ydDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAgICAg
ICB8IFN0YXJ0VExTICAgICAgICAgICAgfCAgUENFUFMgYW5kIHRodXM8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgICAgICAgIHwgU3RhcnRUTFMgICAgICAgICAg
ICB8ICBQQ0VQUyBhbmQgdGh1czwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAg
ICAgICAgICAgICB8IG1zZyAgICAgICAgICAgICAgICAgfCAgc2VuZHMgT3BlbjwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgICAgICAgfCBtc2cgICAgICAgICAg
ICAgICAgIHwgIHNlbmRzIE9wZW48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAg
ICAgICAgICAgICAgfC0tLS0tLS0gICAgICAgICAgICAgIHw8L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICAgICAgICAgICAgICAgICAgIHwtLS0tLS0tICAgICAgICAgICAgICB8PC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgICAgIHwgICAgICAgXCAg
IE9wZW4gICAgICB8PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAg
ICAgICAgICB8ICAgICAgIFwgICBPcGVuICAgICAgfDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+ICAgICAgICAgICAgICAgICAgICB8ICAgICAgICBcICBtc2cgICAgICAgfDwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgXCAgbXNn
ICAgICAgIHw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICAgICAg
fCAgICAgICAgIFwgIC0tLS0tLS0tLXw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4g
ICAgICAgICAgICAgICAgICAgIHwgICAgICAgICBcICAtLS0tLS0tLS18PC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgXC8gICAgICAgICB8
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICAgICAgICB8ICAg
ICAgICAgIFwvICAgICAgICAgfDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAg
ICAgICAgICAgICB8ICAgICAgICAgIC9cICAgICAgICAgfDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAvXCAgICAgICAgIHw8L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgIC8g
IC0tLS0tLS0tJmd0O3w8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAg
ICAgICAgICAgIHwgICAgICAgICAvICAtLS0tLS0tLSZndDt8PC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICAgICAgICAgICAgICAgICAgIHwgICAgICAgIC8gICAgICAgICAgICB8PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAv
ICAgICAgICAgICAgfDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAg
ICAgICB8Jmx0Oy0tLS0tLSAgICAgICAgICAgICAgfDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPiAgICAgICAgICAgICAgICAgICAgfCZsdDstLS0tLS0gICAgICAgICAgICAgIHw8L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAg
ICAgICAgICAgIHw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAg
ICAgICAgIHwgICAgICAgICAgICAgICAgICAgICB8PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij4gICAgICAgICAgICAgICAgICAgIHwmbHQ7LS0tLS0tLS0tLS0tLS0tLS0tLS18IFNlbmQgRXJy
b3I8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgICAgICAgIHwm
bHQ7LS0tLS0tLS0tLS0tLS0tLS0tLS18IFNlbmQgRXJyb3I8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgICAgICAgICAgICAgICAgICAgfCAgICAgICBQQ0VyciAgICAgICAgIHwgKG5vbi1P
cGVuIG1lc3NhZ2U8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAg
ICAgICAgIHwgICAgICAgUENFcnIgICAgICAgICB8IChub24tT3BlbiBtZXNzYWdlPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9ImRpZmYwMDEyIj48dGQ+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxv
Y2siPiAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICAgICAgIHwgIDxzcGFuIGNs
YXNzPSJkZWxldGUiPnJlY2VpdmVkKTwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJi
bG9jayI+ICAgICAgICAgICAgICAgICAgICA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij58Jmx0Oy0tLS0t
LS0tLS0tLS0tLS0tLS0tfCAgcmVjZWl2ZWQpPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgICAgICAgICAgICAg
ICAgICB8ICAgICAgIDxzcGFuIGNsYXNzPSJpbnNlcnQiPkNsb3NlICAgICAgICAgfDwvc3Bhbj48
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
YmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgICAgICAgICAgICAgICAgICAgLy8vLy8vLy8v
IFRDUCAvLy8vLy8vLy88L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICAgICAg
ICAgICAgICAgICAgIC8vLy8vL3JlLWVzdGFibGlzaC8vLy8vPC9zcGFuPjwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4g
Y2xhc3M9Imluc2VydCI+ICAgICAgICAgIFNlbmQgT3BlbiB8IE9wZW4gICAgICAgICAgICAgICAg
fDwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgICAgICAgICB0aGlzIHRpbWUg
fCBtc2cgICAgICAgICAgICAgICAgIHw8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxv
Y2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0
Ij4gICAgICAgICAgICAgICAgICAgIHwtLS0tLS0tICAgICAgICAgICAgICB8PC9zcGFuPjwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9j
ayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgICAgICAgICAgICAgICAgICB8ICAgICAgIFwgICBP
cGVuICAgICAgfDwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgICAgICAgICAg
ICAgICAgICAgfCAgICAgICAgXCAgbXNnICAgICAgIHw8L3NwYW4+PC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFz
cz0iaW5zZXJ0Ij4gICAgICAgICAgICAgICAgICAgIHwgICAgICAgICBcICAtLS0tLS0tLS18PC9z
cGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgICAgICAgICAgICAgICAgICB8ICAg
ICAgICAgIFwvICAgICAgICAgfDwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAg
ICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAvXCAgICAgICAgIHw8L3NwYW4+PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48
c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAvICAtLS0t
LS0tLSZndDt8PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgICAgICAgICAg
ICAgICAgICB8ICAgICAgICAvICAgICAgICAgICAgfDwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNz
PSJpbnNlcnQiPiAgICAgICAgICAgICAgICAgICAgfCZsdDstLS0tLS08L3NwYW4+ICAgICAgICAg
ICAgICB8PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBp
ZD0iZGlmZjAwMTMiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgICAgICAgICAgIEZpZ3VyZSAzOiBPbmUgUENFUCBT
cGVha2VyIGRvZXMgbm90IHN1cHBvcnQgUENFUFM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJi
bG9jayI+ICAgIEZpZ3VyZSAzOiBPbmUgUENFUCBTcGVha2VyIDxzcGFuIGNsYXNzPSJpbnNlcnQi
PihQQ0UpIGRvZXMgbm90IHN1cHBvcnQgUENFUFMsIHdoaWxlIFBDQzwvc3Bhbj48L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxz
cGFuIGNsYXNzPSJpbnNlcnQiPiAgICAgICAgICAgICAgICAgICAgc3VwcG9ydHMgYm90aCB3aXRo
IG9yIHdpdGhvdXQgUENFUFM8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij48L3Nw
YW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICAgICAgICAgICAgICAgICArLSstKyAg
ICAgICAgICAgICAgICAgKy0rLSs8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2si
PjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4g
ICAgICAgICAgICAgICAgICB8UENDfCAgICAgICAgICAgICAgICAgfFBDRXw8L3NwYW4+PC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2Nr
Ij48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICAgICAgICAgICAgICAgICArLSstKyAgICAgICAgICAg
ICAgICAgKy0rLSs8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICAgICAgICAg
ICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICB8PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xh
c3M9Imluc2VydCI+ICAgICAgICAgICAgICAgICAgICB8IFN0YXJ0VExTICAgICAgICAgICAgfDwv
c3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgICAgICAgICAgICAgICAgICAgfCBt
c2cgICAgICAgICAgICAgICAgIHwgUENFIHdhaXRzPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9
Imluc2VydCI+ICAgICAgICAgICAgICAgICAgICB8LS0tLS0tLS0tLS0tLS0tLS0tLS0mZ3Q7fCBm
b3IgUENDIGFuZDwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgICAgICAgICAg
ICAgICAgICAgfCAgICAgICAgICAgIFN0YXJ0VExTIHwgcmVzcG9uZCB3aXRoPC9zcGFuPjwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9j
ayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgICAgICAgICAgICAgICAgICB8Jmx0Oy0tLS0tLS0t
LS0tLS0tLS0tLS0tfCBTdGFydCBUTFM8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxv
Y2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0
Ij4gICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICB8PC9zcGFuPjwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9j
ayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgICAgICAgICAgICAgICAgICB8Ojo6Ojo6Ojo6VExT
Ojo6Ojo6Ojo6fDwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgICAgICAgICAg
ICAgICAgICAgfDo6Ojo6RXN0YWJsaXNobWVudDo6Onw8L3NwYW4+PC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFz
cz0iaW5zZXJ0Ij4gICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICB8PC9z
cGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgICAgICAgICAgICAgICAgICB8ICAg
ICAgICAgICAgICAgICAgICAgfDwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAg
ICAgICAgICAgICAgICAgICAgfDo6Ojo6OjpQQ0VQOjo6Ojo6Ojo6Onw8L3NwYW4+PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48
c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAg
ICAgICB8PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+PC9zcGFuPjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+
PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgIEZpZ3VyZSA0OiBCb3RoIFBDRVAgU3BlYWtlciBzdXBw
b3J0cyBQQ0VQUyBhcyB3ZWxsIGFzIHdpdGhvdXQgUENFUFM8L3NwYW4+PC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBj
bGFzcz0iaW5zZXJ0Ij48L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICAgICAg
ICAgICAgICAgICArLSstKyAgICAgICAgICAgICAgICAgKy0rLSs8L3NwYW4+PC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3Bh
biBjbGFzcz0iaW5zZXJ0Ij4gICAgICAgICAgICAgICAgICB8UENDfCAgICAgICAgICAgICAgICAg
fFBDRXw8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICAgICAgICAgICAgICAg
ICArLSstKyAgICAgICAgICAgICAgICAgKy0rLSs8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0i
aW5zZXJ0Ij4gICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICB8PC9zcGFu
PjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgICAgICAgICAgICAgICAgICB8IE9wZW4g
ICAgICAgICAgICAgICAgfDwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgICAg
ICAgICAgICAgICAgICAgfCBtc2cgICAgICAgICAgICAgICAgIHwgUENFIHdhaXRzPC9zcGFuPjwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJi
bG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgICAgICAgICAgICAgICAgICB8LS0tLS0tLS0t
LS0tLS0tLS0tLS0mZ3Q7fCBmb3IgUENDIGFuZDwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJp
bnNlcnQiPiAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICBPcGVuIHwgcmVzcG9u
ZCB3aXRoPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgICAgICAgICAgICAg
ICAgICB8Jmx0Oy0tLS0tLS0tLS0tLS0tLS0tLS0tfCBPcGVuPC9zcGFuPjwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4g
Y2xhc3M9Imluc2VydCI+ICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAg
fDwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgICAgICAgICAgICAgICAgICAg
fDo6Ojo6OjpQQ0VQOjo6Ojo6Ojo6Onw8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxv
Y2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0
Ij4gICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICB8PC9zcGFuPjwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9j
ayI+PHNwYW4gY2xhc3M9Imluc2VydCI+PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJs
b2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2Vy
dCI+ICAgRmlndXJlIDU6IFBDRSBzdXBwb3J0cyBQQ0VQUyBhcyB3ZWxsIGFzIHdpdGhvdXQgUENF
UFMsIHdoaWxlIFBDQzwvc3Bhbj4gZG9lczwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICBub3Qgc3VwcG9ydCBQQ0VQUzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4z
LjQuICBUTFMgQ29ubmVjdGlvbiBFc3RhYmxpc2htZW50PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+My40LiAgVExTIENvbm5lY3Rpb24gRXN0YWJsaXNobWVudDwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBPbmNlIHRoZSBlc3RhYmxpc2htZW50IG9mIFRMUyBoYXMg
YmVlbiBhZ3JlZWQgYnkgdGhlIFBDRVAgcGVlcnMsIHRoZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgIE9uY2UgdGhlIGVzdGFibGlzaG1lbnQgb2YgVExTIGhhcyBiZWVuIGFncmVl
ZCBieSB0aGUgUENFUCBwZWVycywgdGhlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBj
b25uZWN0aW9uIGVzdGFibGlzaG1lbnQgU0hBTEwgZm9sbG93IHRoZSBmb2xsb3dpbmcgc3RlcHM6
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgY29ubmVjdGlvbiBlc3RhYmxpc2ht
ZW50IFNIQUxMIGZvbGxvdyB0aGUgZm9sbG93aW5nIHN0ZXBzOjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij4gICAxLiAgSW1tZWRpYXRlbHkgbmVnb3RpYXRlIGEgVExTIHNlc3Npb24g
YWNjb3JkaW5nIHRvIFtSRkM1MjQ2XS4gIFRoZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgIDEuICBJbW1lZGlhdGVseSBuZWdvdGlhdGUgYSBUTFMgc2Vzc2lvbiBhY2NvcmRpbmcg
dG8gW1JGQzUyNDZdLiAgVGhlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgZm9s
bG93aW5nIHJlc3RyaWN0aW9ucyBhcHBseTo8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICAgICAgZm9sbG93aW5nIHJlc3RyaWN0aW9ucyBhcHBseTo8L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgICAgICogIFN1cHBvcnQgZm9yIFRMUyB2MS4yIFtSRkM1MjQ2XSBv
ciBsYXRlciBpcyBSRVFVSVJFRC48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAg
ICAgKiAgU3VwcG9ydCBmb3IgVExTIHYxLjIgW1JGQzUyNDZdIG9yIGxhdGVyIGlzIFJFUVVJUkVE
LjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9InBh
cnQtOCIgY2xhc3M9ImNoYW5nZSI+PHRkPjwvdGQ+PHRoPjxzbWFsbD5za2lwcGluZyB0byBjaGFu
Z2UgYXQ8L3NtYWxsPjxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvcmZjZGlmZiNwYXJ0
LTgiPjxlbT4gcGFnZSAxMCwgbGluZSAyNjxzcGFuIGNsYXNzPSJoaWRlIj4gwrY8L3NwYW4+PC9l
bT48L2E+PC90aD48dGg+IDwvdGg+PHRoPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3Nt
YWxsPjxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvcmZjZGlmZiNwYXJ0LTgiPjxlbT4g
cGFnZSAxMywgbGluZSAyMjxzcGFuIGNsYXNzPSJoaWRlIj4gwrY8L3NwYW4+PC9lbT48L2E+PC90
aD48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPiAgICAgICAqICBUTFMgd2l0aCBYLjUwOSBjZXJ0aWZpY2F0ZXMgdXNp
bmcgY2VydGlmaWNhdGUgZmluZ2VycHJpbnRzOjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgICAgICAqICBUTFMgd2l0aCBYLjUwOSBjZXJ0aWZpY2F0ZXMgdXNpbmcgY2VydGlmaWNh
dGUgZmluZ2VycHJpbnRzOjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgIElt
cGxlbWVudGF0aW9ucyBNVVNUIGFsbG93IHRoZSBjb25maWd1cmF0aW9uIG9mIGEgbGlzdCBvZjwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICBJbXBsZW1lbnRhdGlvbnMg
TVVTVCBhbGxvdyB0aGUgY29uZmlndXJhdGlvbiBvZiBhIGxpc3Qgb2Y8L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQg
Y2xhc3M9ImxlZnQiPiAgICAgICAgICB0cnVzdGVkIGNlcnRpZmljYXRlcywgaWRlbnRpZmllZCB2
aWEgZmluZ2VycHJpbnQgb2YgdGhlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAg
ICAgICAgIHRydXN0ZWQgY2VydGlmaWNhdGVzLCBpZGVudGlmaWVkIHZpYSBmaW5nZXJwcmludCBv
ZiB0aGU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICBEaXN0aW5ndWlzaGVk
IEVuY29kaW5nIFJ1bGVzIChERVIpIGVuY29kZWQgY2VydGlmaWNhdGUgb2N0ZXRzLjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICBEaXN0aW5ndWlzaGVkIEVuY29kaW5n
IFJ1bGVzIChERVIpIGVuY29kZWQgY2VydGlmaWNhdGUgb2N0ZXRzLjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+ICAgICAgICAgIEltcGxlbWVudGF0aW9ucyBNVVNUIHN1cHBvcnQgU0hBLTI1
NiBhcyBkZWZpbmVkIGJ5IFtTSFNdIGFzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
ICAgICAgICAgIEltcGxlbWVudGF0aW9ucyBNVVNUIHN1cHBvcnQgU0hBLTI1NiBhcyBkZWZpbmVk
IGJ5IFtTSFNdIGFzPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgdGhlIGhh
c2ggYWxnb3JpdGhtIGZvciB0aGUgZmluZ2VycHJpbnQuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgICAgICAgIHRoZSBoYXNoIGFsZ29yaXRobSBmb3IgdGhlIGZpbmdlcnByaW50
LjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAzLiAgU3RhcnQgZXhjaGFuZ2lu
ZyBQQ0VQIG1lc3NhZ2VzLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIDMuICBT
dGFydCBleGNoYW5naW5nIFBDRVAgbWVzc2FnZXMuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMTQiPjx0ZD48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgICAgICA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij4qICBP
bmNlIHRoZSBUTFMgY29ubmVjdGlvbiBoYXMgYmVlbiBzdWNjZXNzZnVsbHkgZXN0YWJsaXNoZWQs
IHRoZTwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgICAgICAgICBQQ0VQIHNw
ZWFrZXIgTVVTVCBzdGFydCB0aGUgT3BlbldhaXQgdGltZXIgW1JGQzU0NDBdLCBhZnRlcjwvc3Bh
bj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgICAgICAgICB0aGUgZXhwaXJhdGlvbiBv
ZiB3aGljaCwgaWYgbm8gT3BlbiBtZXNzYWdlIGhhcyBiZWVuIHJlY2VpdmVkLDwvc3Bhbj48L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxv
Y2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgICAgICAgICBpdCBzZW5kcyBhIFBDRXJyIG1lc3Nh
Z2UgYW5kIHJlbGVhc2VzIHRoZSBUQ1AvVExTIGNvbm5lY3Rpb24uPC9zcGFuPjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgVG8gc3VwcG9ydCBU
TFMgcmUtbmVnb3RpYXRpb24gYm90aCBwZWVycyBNVVNUIHN1cHBvcnQgdGhlIG1lY2hhbmlzbTwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFRvIHN1cHBvcnQgVExTIHJlLW5lZ290
aWF0aW9uIGJvdGggcGVlcnMgTVVTVCBzdXBwb3J0IHRoZSBtZWNoYW5pc208L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPiAgIGRlc2NyaWJlZCBpbiBbUkZDNTc0Nl0uICBBbnkgYXR0ZW1wdCB0
byBpbml0aWF0ZSBhIFRMUyBoYW5kc2hha2UgdG88L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICBkZXNjcmliZWQgaW4gW1JGQzU3NDZdLiAgQW55IGF0dGVtcHQgdG8gaW5pdGlhdGUg
YSBUTFMgaGFuZHNoYWtlIHRvPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBlc3RhYmxp
c2ggbmV3IGNyeXB0b2dyYXBoaWMgcGFyYW1ldGVycyBub3QgYWxpZ25lZCB3aXRoIFtSRkM1NzQ2
XTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGVzdGFibGlzaCBuZXcgY3J5cHRv
Z3JhcGhpYyBwYXJhbWV0ZXJzIG5vdCBhbGlnbmVkIHdpdGggW1JGQzU3NDZdPC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij4gICBTSEFMTCBiZSBjb25zaWRlcmVkIGEgVExTIG5lZ290aWF0aW9u
IGZhaWx1cmUuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgU0hBTEwgYmUgY29u
c2lkZXJlZCBhIFRMUyBuZWdvdGlhdGlvbiBmYWlsdXJlLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij4zLjUuICBQZWVyIElkZW50aXR5PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+My41LiAgUGVlciBJZGVudGl0eTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij4gICBEZXBlbmRpbmcgb24gdGhlIHBlZXIgYXV0aGVudGljYXRpb24gbWV0aG9kIGluIHVzZSwg
UENFUFMgc3VwcG9ydHM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBEZXBlbmRp
bmcgb24gdGhlIHBlZXIgYXV0aGVudGljYXRpb24gbWV0aG9kIGluIHVzZSwgUENFUFMgc3VwcG9y
dHM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGRpZmZlcmVudCBvcGVyYXRpb24gbW9k
ZXMgdG8gZXN0YWJsaXNoIHBlZXIncyBpZGVudGl0eSBhbmQgd2hldGhlciBpdDwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGRpZmZlcmVudCBvcGVyYXRpb24gbW9kZXMgdG8gZXN0
YWJsaXNoIHBlZXIncyBpZGVudGl0eSBhbmQgd2hldGhlciBpdDwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGVmdCI+ICAgaXMgZW50aXRsZWQgdG8gcGVyZm9ybSByZXF1ZXN0cyBvciBjYW4gYmUgY29u
c2lkZXJlZCBhdXRob3JpdGF0aXZlIGluPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
ICAgaXMgZW50aXRsZWQgdG8gcGVyZm9ybSByZXF1ZXN0cyBvciBjYW4gYmUgY29uc2lkZXJlZCBh
dXRob3JpdGF0aXZlIGluPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgoKICAgICA8
dHI+PHRkPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij48L3RkPjx0ZD48L3RkPjwvdHI+CiAgICAgPHRyIGlkPSJlbmQiIGJnY29sb3I9ImdyYXki
Pjx0aCBjb2xzcGFuPSI1IiBhbGlnbj0iY2VudGVyIj4mbmJzcDtFbmQgb2YgY2hhbmdlcy4gMTQg
Y2hhbmdlIGJsb2Nrcy4mbmJzcDs8L3RoPjwvdHI+CiAgICAgPHRyIGNsYXNzPSJzdGF0cyI+PHRk
PjwvdGQ+PHRoPjxpPjQ1IGxpbmVzIGNoYW5nZWQgb3IgZGVsZXRlZDwvaT48L3RoPjx0aD48aT4g
PC9pPjwvdGg+PHRoPjxpPjEzNCBsaW5lcyBjaGFuZ2VkIG9yIGFkZGVkPC9pPjwvdGg+PHRkPjwv
dGQ+PC90cj4KICAgICA8dHI+PHRkIGNvbHNwYW49IjUiIGFsaWduPSJjZW50ZXIiIGNsYXNzPSJz
bWFsbCI+PGJyPlRoaXMgaHRtbCBkaWZmIHdhcyBwcm9kdWNlZCBieSByZmNkaWZmIDEuNDUuIFRo
ZSBsYXRlc3QgdmVyc2lvbiBpcyBhdmFpbGFibGUgZnJvbSA8YSBocmVmPSJodHRwOi8vd3d3LnRv
b2xzLmlldGYub3JnL3Rvb2xzL3JmY2RpZmYvIj5odHRwOi8vdG9vbHMuaWV0Zi5vcmcvdG9vbHMv
cmZjZGlmZi88L2E+IDwvdGQ+PC90cj4KICAgPC90Ym9keT48L3RhYmxlPgogICAKICAgCjxpZnJh
bWUgd2lkdGg9IjAiIGhlaWdodD0iMCIgZnJhbWVib3JkZXI9IjAiIHNyYz0iLi9EaWZmXyBkcmFm
dC1pZXRmLXBjZS1wY2Vwcy0xNS1vbGQudHh0IC0gZHJhZnQtaWV0Zi1wY2UtcGNlcHMtMTUudHh0
X2ZpbGVzL3NhdmVkX3Jlc291cmNlLmh0bWwiIGlkPSJHSU5HRVJfU09GVFdBUkVfYnViYmxlc0lG
cmFtZSIgc2Nyb2xsaW5nPSJubyIgc3R5bGU9ImJvcmRlcjogMHB4IHNvbGlkOyBkaXNwbGF5OiBu
b25lOyBwb3NpdGlvbjogYWJzb2x1dGU7IHotaW5kZXg6IDIxNDc0ODM2NDc7IGhlaWdodDogMHB4
OyB3aWR0aDogMHB4OyBiYWNrZ3JvdW5kLWNvbG9yOiB0cmFuc3BhcmVudDsiPjwvaWZyYW1lPjxk
aXYgaWQ9IkdpbmdlcldpZGdldEluZm8iIHN0eWxlPSJkaXNwbGF5Om5vbmU7Ij57InZlcnNpb24i
OiIwLjEuMC42MTgiLCJpc0V4dGVuc2lvbiI6dHJ1ZSwiZXh0ZW5zaW9uTmFtZSI6IkNocm9tZSJ9
PC9kaXY+PC9ib2R5PjxzY3JpcHQ+KGZ1bmN0aW9uKCl7KGZ1bmN0aW9uICgpewogICAgICAgICAg
ICAvL1RvZG86aXMgaW5qZWN0aW9uIG5lZWRlZCBoZXJlPwogICAgICAgICAgICB2YXIgZXZlbnRS
ZWdpc3RlciA9IHt9OwoKICAgICAgICAgICAgdmFyIGZpbmRSZWFjdFByb3AgPSBmdW5jdGlvbihl
bGVtKXsKICAgICAgICAgICAgICAgIGZvcih2YXIga2V5IGluIGVsZW0pewogICAgICAgICAgICAg
ICAgICAgIGlmKGtleS5pbmRleE9mKCJfX3JlYWN0SW50ZXJuYWxJbnN0YW5jZSIpPT09MCl7CiAg
ICAgICAgICAgICAgICAgICAgICAgIC8vdmFyIHAgPSBudWxsOwogICAgICAgICAgICAgICAgICAg
ICAgICAvL2lmKGVsZW1ba2V5XS5tZW1vaXplZFByb3BzKXsKICAgICAgICAgICAgICAgICAgICAg
ICAgLy8gICAgcCA9IGVsZW1ba2V5XS5tZW1vaXplZFByb3BzOwogICAgICAgICAgICAgICAgICAg
ICAgICAvL30gZWxzZSBpZihlbGVtW2tleV0uX2N1cnJlbnRFbGVtZW50KXsKICAgICAgICAgICAg
ICAgICAgICAgICAgLy8gICAgcCA9IGVsZW1ba2V5XS5fY3VycmVudEVsZW1lbnQucHJvcHMKICAg
ICAgICAgICAgICAgICAgICAgICAgLy99CgogICAgICAgICAgICAgICAgICAgICAgICAvL1RPRE86
IHJlcG9ydCBpZiBwcm9wcyBpcyBub3QgZm91bmQgd2l0aCBGYWNlYm9vayB2ZXJzaW9uCiAgICAg
ICAgICAgICAgICAgICAgICAgIHJldHVybiAoZWxlbVtrZXldLm1lbW9pemVkUHJvcHMgfHwgZWxl
bVtrZXldLl9jdXJyZW50RWxlbWVudC5wcm9wcyk7CiAgICAgICAgICAgICAgICAgICAgfQogICAg
ICAgICAgICAgICAgfQogICAgICAgICAgICAgICAgcmV0dXJuIG51bGw7CiAgICAgICAgICAgIH07
CgogICAgICAgICAgICBkb2N1bWVudC5hZGRFdmVudExpc3RlbmVyKCJnaW5nZXJNb2R1bGUtZXZl
bnRFbWl0dGVyLXJlYWN0LWZpcmUiLGZ1bmN0aW9uKGUpewogICAgICAgICAgICAgICAgLy9jb25z
b2xlLmxvZygiZmlyaW5nIiwgZSk7CiAgICAgICAgICAgICAgICB2YXIgcmVhY3RQcm9wcyA9IGZp
bmRSZWFjdFByb3AoZG9jdW1lbnQuYWN0aXZlRWxlbWVudCk7CiAgICAgICAgICAgICAgICB2YXIg
ZXZlbnROYW1lID0gZS5kZXRhaWwuZXZlbnQ7CiAgICAgICAgICAgICAgICB2YXIgZXZlbnRQYXJh
bXMgPSBlLmRldGFpbC5wYXJhbXMgfHwge307CiAgICAgICAgICAgICAgICBldmVudFBhcmFtcy5w
cmV2ZW50RGVmYXVsdCA9IGZ1bmN0aW9uKCl7fTsKICAgICAgICAgICAgICAgIGlmKHJlYWN0UHJv
cHMgJiYgZXZlbnROYW1lKSB7CiAgICAgICAgICAgICAgICAgICAgcmVhY3RQcm9wc1tldmVudE5h
bWVdKGV2ZW50UGFyYW1zKTsKICAgICAgICAgICAgICAgIH0KICAgICAgICAgICAgfSk7CiAgICAg
ICAgICAgIGRvY3VtZW50LmFkZEV2ZW50TGlzdGVuZXIoImdpbmdlck1vZHVsZS1ldmVudEVtaXR0
ZXItb25zZWxlY3QiLGZ1bmN0aW9uKGUpewogICAgICAgICAgICAgICAgdmFyIHJlYWN0UHJvcHMg
PSBmaW5kUmVhY3RQcm9wKGRvY3VtZW50LmFjdGl2ZUVsZW1lbnQpOwogICAgICAgICAgICAgICAg
Ly90cmlnZ2VyKCJzZWxlY3QiKTsKICAgICAgICAgICAgICAgIGlmKHJlYWN0UHJvcHMpIHsKICAg
ICAgICAgICAgICAgICAgICByZWFjdFByb3BzLm9uU2VsZWN0KCk7CiAgICAgICAgICAgICAgICB9
CiAgICAgICAgICAgIH0pOwogICAgICAgICAgICBkb2N1bWVudC5hZGRFdmVudExpc3RlbmVyKCJn
aW5nZXJNb2R1bGUtZXZlbnRFbWl0dGVyLW9ucGFzdGUiLGZ1bmN0aW9uKGUpewogICAgICAgICAg
ICAgICAgdmFyIHJlYWN0UHJvcHMgPSBmaW5kUmVhY3RQcm9wKGRvY3VtZW50LmFjdGl2ZUVsZW1l
bnQpOwogICAgICAgICAgICAgICAgdmFyIHBhc3RlT2JqID0gewogICAgICAgICAgICAgICAgICAg
IGRlZmF1bHRQcmV2ZW50ZWQ6IGZhbHNlLAogICAgICAgICAgICAgICAgICAgIHRhcmdldDogZG9j
dW1lbnQuYWN0aXZlRWxlbWVudCwKICAgICAgICAgICAgICAgICAgICBwcmV2ZW50RGVmYXVsdDog
ZnVuY3Rpb24oKSB7fSwKICAgICAgICAgICAgICAgICAgICBjbGlwYm9hcmREYXRhIDogewogICAg
ICAgICAgICAgICAgICAgICAgICBnZXREYXRhOiBmdW5jdGlvbiAoKSB7CiAgICAgICAgICAgICAg
ICAgICAgICAgICAgICByZXR1cm4gZS5kZXRhaWwgfHwgIiI7CiAgICAgICAgICAgICAgICAgICAg
ICAgIH0sCiAgICAgICAgICAgICAgICAgICAgICAgIGl0ZW1zOiBbInRleHQvcGxhaW4iXQogICAg
ICAgICAgICAgICAgICAgIH0KICAgICAgICAgICAgICAgIH07CiAgICAgICAgICAgICAgICAvL3Ry
aWdnZXIoInBhc3RlIixwYXN0ZU9iaik7CiAgICAgICAgICAgICAgICBpZihyZWFjdFByb3BzKSB7
CiAgICAgICAgICAgICAgICAgICAgcmVhY3RQcm9wcy5vblBhc3RlKHBhc3RlT2JqKTsKICAgICAg
ICAgICAgICAgIH0KICAgICAgICAgICAgfSk7CgogICAgICAgICAgICB2YXIgdHJpZ2dlciA9IGZ1
bmN0aW9uKGV2ZW50TmFtZSxkYXRhKXsKICAgICAgICAgICAgICAgIGlmKCFldmVudFJlZ2lzdGVy
W2V2ZW50TmFtZV0pIHJldHVybjsKICAgICAgICAgICAgICAgIGZvcih2YXIgaSA9IDA7IGk8ZXZl
bnRSZWdpc3RlcltldmVudE5hbWVdLmxlbmd0aDsgaSsrKXsKICAgICAgICAgICAgICAgICAgICB2
YXIgbGlzdGVuZXIgPSBldmVudFJlZ2lzdGVyW2V2ZW50TmFtZV1baV07CiAgICAgICAgICAgICAg
ICAgICAgbGlzdGVuZXIobmV3IEN1c3RvbUV2ZW50KGV2ZW50TmFtZSksZGF0YSk7CiAgICAgICAg
ICAgICAgICB9CiAgICAgICAgICAgIH07CgogICAgICAgICAgICB2YXIgbmF0aXZlRXZlbnRMaXN0
ZW5lciA9IGRvY3VtZW50LmFkZEV2ZW50TGlzdGVuZXIuYmluZChkb2N1bWVudCk7CiAgICAgICAg
ICAgIGRvY3VtZW50LmFkZEV2ZW50TGlzdGVuZXIgPSBmdW5jdGlvbihldmVudE5hbWUsIGNhbGxi
YWNrLCBvcHRpb25zKSB7CiAgICAgICAgICAgICAgICBjb25zb2xlLmxvZygicmVnaXN0ZXJpbmcg
ZXZlbnQiLGV2ZW50TmFtZSk7CiAgICAgICAgICAgICAgICB2YXIgZXZlbnRSZWdpc3Rlckl0ZW0g
PSBldmVudFJlZ2lzdGVyW2V2ZW50TmFtZV0gfHwgW107CiAgICAgICAgICAgICAgICBldmVudFJl
Z2lzdGVySXRlbS5wdXNoKGNhbGxiYWNrKTsKICAgICAgICAgICAgICAgIGV2ZW50UmVnaXN0ZXJb
ZXZlbnROYW1lXSA9IGV2ZW50UmVnaXN0ZXJJdGVtOwogICAgICAgICAgICAgICAgbmF0aXZlRXZl
bnRMaXN0ZW5lcihldmVudE5hbWUsIGNhbGxiYWNrLCBvcHRpb25zKTsKICAgICAgICAgICAgfTsK
CiAgICAgICAgfSkoKSB9KSgpPC9zY3JpcHQ+PC9odG1sPg==

--_003_23CE718903A838468A8B325B80962F9B8CB962D9blreml501mbb_
Content-Type: text/plain; name="draft-ietf-pce-pceps-15.txt"
Content-Description: draft-ietf-pce-pceps-15.txt
Content-Disposition: attachment; filename="draft-ietf-pce-pceps-15.txt";
	size=49611; creation-date="Mon, 31 Jul 2017 13:24:21 GMT";
	modification-date="Mon, 31 Jul 2017 13:24:21 GMT"
Content-Transfer-Encoding: base64

CgoKClBDRSBXb3JraW5nIEdyb3VwICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICBELiBMb3BlegpJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIE8uIEdvbnphbGV6IGRlIERpb3MKVXBkYXRlczogNTQ0MCAoaWYgYXBw
cm92ZWQpICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFRlbGVmb25pY2EgSStECkludGVu
ZGVkIHN0YXR1czogU3RhbmRhcmRzIFRyYWNrICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICBRLiBXdQpFeHBpcmVzOiBGZWJydWFyeSAxLCAyMDE4ICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgRC4gRGhvZHkKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgSHVhd2VpCiAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgSnVseSAzMSwgMjAx
NwoKCiAgICAgICAgICAgICAgICAgICAgICAgU2VjdXJlIFRyYW5zcG9ydCBmb3IgUENFUAogICAg
ICAgICAgICAgICAgICAgICAgICBkcmFmdC1pZXRmLXBjZS1wY2Vwcy0xNQoKQWJzdHJhY3QKCiAg
IFRoZSBQYXRoIENvbXB1dGF0aW9uIEVsZW1lbnQgQ29tbXVuaWNhdGlvbiBQcm90b2NvbCAoUENF
UCkgZGVmaW5lcwogICB0aGUgbWVjaGFuaXNtcyBmb3IgdGhlIGNvbW11bmljYXRpb24gYmV0d2Vl
biBhIFBhdGggQ29tcHV0YXRpb24KICAgQ2xpZW50IChQQ0MpIGFuZCBhIFBhdGggQ29tcHV0YXRp
b24gRWxlbWVudCAoUENFKSwgb3IgYW1vbmcgUENFcy4KICAgVGhpcyBkb2N1bWVudCBkZXNjcmli
ZSB0aGUgdXNhZ2Ugb2YgVHJhbnNwb3J0IExheWVyIFNlY3VyaXR5IChUTFMpIHRvCiAgIGVuaGFu
Y2UgUENFUCBzZWN1cml0eSwgaGVuY2UgdGhlIFBDRVBTIGFjcm9ueW0gcHJvcG9zZWQgZm9yIGl0
LiAgVGhlCiAgIGFkZGl0aW9uYWwgc2VjdXJpdHkgbWVjaGFuaXNtcyBhcmUgcHJvdmlkZWQgYnkg
dGhlIHRyYW5zcG9ydCBwcm90b2NvbAogICBzdXBwb3J0aW5nIFBDRVAsIGFuZCB0aGVyZWZvcmUg
dGhleSBkbyBub3QgYWZmZWN0IHRoZSBmbGV4aWJpbGl0eSBhbmQKICAgZXh0ZW5zaWJpbGl0eSBv
ZiBQQ0VQLgoKICAgVGhpcyBkb2N1bWVudCB1cGRhdGVzIFJGQyA1NDQwIHJlZ2FyZGluZyB0aGUg
UENFUCBpbml0aWFsaXphdGlvbgogICBwaGFzZSBzcGVjaWZpY2F0aW9uLgoKU3RhdHVzIG9mIFRo
aXMgTWVtbwoKICAgVGhpcyBJbnRlcm5ldC1EcmFmdCBpcyBzdWJtaXR0ZWQgaW4gZnVsbCBjb25m
b3JtYW5jZSB3aXRoIHRoZQogICBwcm92aXNpb25zIG9mIEJDUCA3OCBhbmQgQkNQIDc5LgoKICAg
SW50ZXJuZXQtRHJhZnRzIGFyZSB3b3JraW5nIGRvY3VtZW50cyBvZiB0aGUgSW50ZXJuZXQgRW5n
aW5lZXJpbmcKICAgVGFzayBGb3JjZSAoSUVURikuICBOb3RlIHRoYXQgb3RoZXIgZ3JvdXBzIG1h
eSBhbHNvIGRpc3RyaWJ1dGUKICAgd29ya2luZyBkb2N1bWVudHMgYXMgSW50ZXJuZXQtRHJhZnRz
LiAgVGhlIGxpc3Qgb2YgY3VycmVudCBJbnRlcm5ldC0KICAgRHJhZnRzIGlzIGF0IGh0dHA6Ly9k
YXRhdHJhY2tlci5pZXRmLm9yZy9kcmFmdHMvY3VycmVudC8uCgogICBJbnRlcm5ldC1EcmFmdHMg
YXJlIGRyYWZ0IGRvY3VtZW50cyB2YWxpZCBmb3IgYSBtYXhpbXVtIG9mIHNpeCBtb250aHMKICAg
YW5kIG1heSBiZSB1cGRhdGVkLCByZXBsYWNlZCwgb3Igb2Jzb2xldGVkIGJ5IG90aGVyIGRvY3Vt
ZW50cyBhdCBhbnkKICAgdGltZS4gIEl0IGlzIGluYXBwcm9wcmlhdGUgdG8gdXNlIEludGVybmV0
LURyYWZ0cyBhcyByZWZlcmVuY2UKICAgbWF0ZXJpYWwgb3IgdG8gY2l0ZSB0aGVtIG90aGVyIHRo
YW4gYXMgIndvcmsgaW4gcHJvZ3Jlc3MuIgoKICAgVGhpcyBJbnRlcm5ldC1EcmFmdCB3aWxsIGV4
cGlyZSBvbiBGZWJydWFyeSAxLCAyMDE4LgoKQ29weXJpZ2h0IE5vdGljZQoKICAgQ29weXJpZ2h0
IChjKSAyMDE3IElFVEYgVHJ1c3QgYW5kIHRoZSBwZXJzb25zIGlkZW50aWZpZWQgYXMgdGhlCiAg
IGRvY3VtZW50IGF1dGhvcnMuICBBbGwgcmlnaHRzIHJlc2VydmVkLgoKCgoKTG9wZXosIGV0IGFs
LiAgICAgICAgICAgRXhwaXJlcyBGZWJydWFyeSAxLCAyMDE4ICAgICAgICAgICAgICAgIFtQYWdl
IDFdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgU2VjdXJlIFRyYW5zcG9ydCBmb3IgUENFUCAg
ICAgICAgICAgICAgSnVseSAyMDE3CgoKICAgVGhpcyBkb2N1bWVudCBpcyBzdWJqZWN0IHRvIEJD
UCA3OCBhbmQgdGhlIElFVEYgVHJ1c3QncyBMZWdhbAogICBQcm92aXNpb25zIFJlbGF0aW5nIHRv
IElFVEYgRG9jdW1lbnRzCiAgIChodHRwOi8vdHJ1c3RlZS5pZXRmLm9yZy9saWNlbnNlLWluZm8p
IGluIGVmZmVjdCBvbiB0aGUgZGF0ZSBvZgogICBwdWJsaWNhdGlvbiBvZiB0aGlzIGRvY3VtZW50
LiAgUGxlYXNlIHJldmlldyB0aGVzZSBkb2N1bWVudHMKICAgY2FyZWZ1bGx5LCBhcyB0aGV5IGRl
c2NyaWJlIHlvdXIgcmlnaHRzIGFuZCByZXN0cmljdGlvbnMgd2l0aCByZXNwZWN0CiAgIHRvIHRo
aXMgZG9jdW1lbnQuICBDb2RlIENvbXBvbmVudHMgZXh0cmFjdGVkIGZyb20gdGhpcyBkb2N1bWVu
dCBtdXN0CiAgIGluY2x1ZGUgU2ltcGxpZmllZCBCU0QgTGljZW5zZSB0ZXh0IGFzIGRlc2NyaWJl
ZCBpbiBTZWN0aW9uIDQuZSBvZgogICB0aGUgVHJ1c3QgTGVnYWwgUHJvdmlzaW9ucyBhbmQgYXJl
IHByb3ZpZGVkIHdpdGhvdXQgd2FycmFudHkgYXMKICAgZGVzY3JpYmVkIGluIHRoZSBTaW1wbGlm
aWVkIEJTRCBMaWNlbnNlLgoKICAgVGhpcyBkb2N1bWVudCBtYXkgY29udGFpbiBtYXRlcmlhbCBm
cm9tIElFVEYgRG9jdW1lbnRzIG9yIElFVEYKICAgQ29udHJpYnV0aW9ucyBwdWJsaXNoZWQgb3Ig
bWFkZSBwdWJsaWNseSBhdmFpbGFibGUgYmVmb3JlIE5vdmVtYmVyCiAgIDEwLCAyMDA4LiAgVGhl
IHBlcnNvbihzKSBjb250cm9sbGluZyB0aGUgY29weXJpZ2h0IGluIHNvbWUgb2YgdGhpcwogICBt
YXRlcmlhbCBtYXkgbm90IGhhdmUgZ3JhbnRlZCB0aGUgSUVURiBUcnVzdCB0aGUgcmlnaHQgdG8g
YWxsb3cKICAgbW9kaWZpY2F0aW9ucyBvZiBzdWNoIG1hdGVyaWFsIG91dHNpZGUgdGhlIElFVEYg
U3RhbmRhcmRzIFByb2Nlc3MuCiAgIFdpdGhvdXQgb2J0YWluaW5nIGFuIGFkZXF1YXRlIGxpY2Vu
c2UgZnJvbSB0aGUgcGVyc29uKHMpIGNvbnRyb2xsaW5nCiAgIHRoZSBjb3B5cmlnaHQgaW4gc3Vj
aCBtYXRlcmlhbHMsIHRoaXMgZG9jdW1lbnQgbWF5IG5vdCBiZSBtb2RpZmllZAogICBvdXRzaWRl
IHRoZSBJRVRGIFN0YW5kYXJkcyBQcm9jZXNzLCBhbmQgZGVyaXZhdGl2ZSB3b3JrcyBvZiBpdCBt
YXkKICAgbm90IGJlIGNyZWF0ZWQgb3V0c2lkZSB0aGUgSUVURiBTdGFuZGFyZHMgUHJvY2Vzcywg
ZXhjZXB0IHRvIGZvcm1hdAogICBpdCBmb3IgcHVibGljYXRpb24gYXMgYW4gUkZDIG9yIHRvIHRy
YW5zbGF0ZSBpdCBpbnRvIGxhbmd1YWdlcyBvdGhlcgogICB0aGFuIEVuZ2xpc2guCgpUYWJsZSBv
ZiBDb250ZW50cwoKICAgMS4gIEludHJvZHVjdGlvbiAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gICAzCiAgIDIuICBSZXF1aXJlbWVudHMgTGFuZ3VhZ2Ug
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgNAogICAzLiAgQXBwbHlp
bmcgUENFUFMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAg
IDQKICAgICAzLjEuICBPdmVydmlldyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gICA0CiAgICAgMy4yLiAgSW5pdGlhdGluZyB0aGUgVExTIFByb2NlZHVy
ZXMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgNAogICAgIDMuMy4gIFRoZSBTdGFydFRM
UyBNZXNzYWdlICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDcKICAgICAz
LjQuICBUTFMgQ29ubmVjdGlvbiBFc3RhYmxpc2htZW50ICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gIDExCiAgICAgMy41LiAgUGVlciBJZGVudGl0eSAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxMwogICAgIDMuNi4gIENvbm5lY3Rpb24gRXN0YWJsaXNo
bWVudCBGYWlsdXJlICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTQKICAgNC4gIERpc2NvdmVy
eSBNZWNoYW5pc21zICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDE1
CiAgICAgNC4xLiAgREFORSBBcHBsaWNhYmlsaXR5ICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuICAxNQogICA1LiAgQmFja3dhcmQgQ29tcGF0aWJpbGl0eSAgLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTUKICAgNi4gIElBTkEgQ29uc2lkZXJhdGlv
bnMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDE2CiAgICAgNi4x
LiAgTmV3IFBDRVAgTWVzc2FnZSAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuICAxNgogICAgIDYuMi4gIE5ldyBFcnJvci1WYWx1ZXMgIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAgMTYKICAgNy4gIFNlY3VyaXR5IENvbnNpZGVyYXRpb25zIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDE3CiAgIDguICBNYW5hZ2VhYmls
aXR5IENvbnNpZGVyYXRpb25zICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxOAog
ICAgIDguMS4gIENvbnRyb2wgb2YgRnVuY3Rpb24gYW5kIFBvbGljeSAgLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAgMTgKICAgICA4LjIuICBJbmZvcm1hdGlvbiBhbmQgRGF0YSBNb2RlbHMgLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDE5CiAgICAgOC4zLiAgTGl2ZW5lc3MgRGV0ZWN0
aW9uIGFuZCBNb25pdG9yaW5nIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxOQogICAgIDguNC4g
IFZlcmlmeWluZyBDb3JyZWN0IE9wZXJhdGlvbnMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAgMTkKICAgICA4LjUuICBSZXF1aXJlbWVudHMgb24gT3RoZXIgUHJvdG9jb2xzIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gIDE5CiAgICAgOC42LiAgSW1wYWN0IG9uIE5ldHdvcmsgT3BlcmF0
aW9uIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxOQogICA5LiAgQWNrbm93bGVkZ2Vt
ZW50cyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTkKCgoK
TG9wZXosIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBGZWJydWFyeSAxLCAyMDE4ICAgICAgICAg
ICAgICAgIFtQYWdlIDJdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgU2VjdXJlIFRyYW5zcG9y
dCBmb3IgUENFUCAgICAgICAgICAgICAgSnVseSAyMDE3CgoKICAgMTAuIFJlZmVyZW5jZXMgIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDIwCiAgICAg
MTAuMS4gIE5vcm1hdGl2ZSBSZWZlcmVuY2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuICAyMAogICAgIDEwLjIuICBJbmZvcm1hdGl2ZSBSZWZlcmVuY2VzIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMjEKICAgQXV0aG9ycycgQWRkcmVzc2VzICAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDIzCgoxLiAgSW50cm9kdWN0
aW9uCgogICBUaGUgUGF0aCBDb21wdXRhdGlvbiBFbGVtZW50IENvbW11bmljYXRpb24gUHJvdG9j
b2wgKFBDRVApIFtSRkM1NDQwXQogICBkZWZpbmVzIHRoZSBtZWNoYW5pc21zIGZvciB0aGUgY29t
bXVuaWNhdGlvbiBiZXR3ZWVuIGEgUGF0aAogICBDb21wdXRhdGlvbiBDbGllbnQgKFBDQykgYW5k
IGEgUGF0aCBDb21wdXRhdGlvbiBFbGVtZW50IChQQ0UpLCBvcgogICBiZXR3ZWVuIHR3byBQQ0Vz
LiAgVGhlc2UgaW50ZXJhY3Rpb25zIGluY2x1ZGUgcmVxdWVzdHMgYW5kIHJlcGxpZXMKICAgdGhh
dCBjYW4gYmUgY3JpdGljYWwgZm9yIGEgc3VzdGFpbmFibGUgbmV0d29yayBvcGVyYXRpb24gYW5k
IGFkZXF1YXRlCiAgIHJlc291cmNlIGFsbG9jYXRpb24sIGFuZCB0aGVyZWZvcmUgYXBwcm9wcmlh
dGUgc2VjdXJpdHkgYmVjb21lcyBhIGtleQogICBlbGVtZW50IGluIHRoZSBQQ0UgaW5mcmFzdHJ1
Y3R1cmUuICBBcyB0aGUgYXBwbGljYXRpb25zIG9mIHRoZSBQQ0UKICAgZnJhbWV3b3JrIGV2b2x2
ZXMsIGFuZCBtb3JlIGNvbXBsZXggc2VydmljZSBwYXR0ZXJucyBlbWVyZ2UsIHRoZQogICBkZWZp
bml0aW9uIG9mIGEgc2VjdXJlIG1vZGUgb2Ygb3BlcmF0aW9uIGJlY29tZXMgbW9yZSByZWxldmFu
dC4KCiAgIFtSRkM1NDQwXSBhbmFseXplcyBpbiBpdHMgc2VjdGlvbiBvbiBzZWN1cml0eSBjb25z
aWRlcmF0aW9ucyB0aGUKICAgcG90ZW50aWFsIHRocmVhdHMgdG8gUENFUCBhbmQgdGhlaXIgY29u
c2VxdWVuY2VzLCBhbmQgZGlzY3Vzc2VzCiAgIHNldmVyYWwgbWVjaGFuaXNtcyBmb3IgcHJvdGVj
dGluZyBQQ0VQIGFnYWluc3Qgc2VjdXJpdHkgYXR0YWNrcywKICAgd2l0aG91dCBtYWtpbmcgYSBz
cGVjaWZpYyByZWNvbW1lbmRhdGlvbiBvbiBhIHBhcnRpY3VsYXIgb25lIG9yCiAgIGRlZmluaW5n
IHRoZWlyIGFwcGxpY2F0aW9uIGluIGRlcHRoLiAgTW9yZW92ZXIsIFtSRkM2OTUyXSByZW1hcmtz
IHRoZQogICBpbXBvcnRhbmNlIG9mIGVuc3VyaW5nIFBDRVAgY29tbXVuaWNhdGlvbiBwcml2YWN5
LCBlc3BlY2lhbGx5IHdoZW4KICAgUENFUCBjb21tdW5pY2F0aW9uIGVuZHBvaW50cyBkbyBub3Qg
cmVzaWRlIGluIHRoZSBzYW1lIEF1dG9ub21vdXMKICAgU3lzdGVtIChBUyksIGFzIHRoZSBpbnRl
cmNlcHRpb24gb2YgUENFUCBtZXNzYWdlcyBjb3VsZCBsZWFrCiAgIHNlbnNpdGl2ZSBpbmZvcm1h
dGlvbiByZWxhdGVkIHRvIGNvbXB1dGVkIHBhdGhzIGFuZCByZXNvdXJjZXMuCgogICBBbW9uZyB0
aGUgcG9zc2libGUgc29sdXRpb25zIG1lbnRpb25lZCBpbiB0aGVzZSBkb2N1bWVudHMsIFRyYW5z
cG9ydAogICBMYXllciBTZWN1cml0eSAoVExTKSBbUkZDNTI0Nl0gcHJvdmlkZXMgc3VwcG9ydCBm
b3IgcGVlcgogICBhdXRoZW50aWNhdGlvbiwgYW5kIG1lc3NhZ2UgZW5jcnlwdGlvbiBhbmQgaW50
ZWdyaXR5LiAgVExTIHN1cHBvcnRzCiAgIHRoZSB1c2FnZSBvZiB3ZWxsLWtub3duIG1lY2hhbmlz
bXMgdG8gc3VwcG9ydCBrZXkgY29uZmlndXJhdGlvbiBhbmQKICAgZXhjaGFuZ2UsIGFuZCBtZWFu
cyB0byBwZXJmb3JtIHNlY3VyaXR5IGNoZWNrcyBvbiB0aGUgcmVzdWx0cyBvZiBQQ0UKICAgZGlz
Y292ZXJ5IHByb2NlZHVyZXMgdmlhIEludGVyaW9yIEdhdGV3YXkgUHJvdG9jb2wgKElHUCkgKFtS
RkM1MDg4XQogICBhbmQgW1JGQzUwODldKS4KCiAgIFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzIGEg
c2VjdXJpdHkgY29udGFpbmVyIGZvciB0aGUgdHJhbnNwb3J0IG9mCiAgIFBDRVAgbWVzc2FnZXMs
IGFuZCB0aGVyZWZvcmUgaXQgZG9lcyBub3QgYWZmZWN0IHRoZSBmbGV4aWJpbGl0eSBhbmQKICAg
ZXh0ZW5zaWJpbGl0eSBvZiBQQ0VQLgoKICAgVGhpcyBkb2N1bWVudCBkZXNjcmliZXMgaG93IHRv
IGFwcGx5IFRMUyBpbiBzZWN1cmluZyBQQ0UKICAgaW50ZXJhY3Rpb25zLCBpbmNsdWRpbmcgaW5p
dGlhdGlvbiBvZiB0aGUgVExTIHByb2NlZHVyZXMsIHRoZSBUTFMKICAgaGFuZHNoYWtlIG1lY2hh
bmlzbXMsIHRoZSBUTFMgbWV0aG9kcyBmb3IgcGVlciBhdXRoZW50aWNhdGlvbiwgdGhlCiAgIGFw
cGxpY2FibGUgVExTIGNpcGhlcnN1aXRlcyBmb3IgZGF0YSBleGNoYW5nZSwgYW5kIHRoZSBoYW5k
bGluZyBvZgogICBlcnJvcnMgaW4gdGhlIHNlY3VyaXR5IGNoZWNrcy4gIEluIHRoZSByZXN0IG9m
IHRoZSBkb2N1bWVudCB3ZSB3aWxsCiAgIHJlZmVyIHRvIHRoaXMgdXNhZ2Ugb2YgVExTIHRvIHBy
b3ZpZGUgYSBzZWN1cmUgdHJhbnNwb3J0IGZvciBQQ0VQIGFzCiAgICJQQ0VQUyIuCgoKCgoKTG9w
ZXosIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBGZWJydWFyeSAxLCAyMDE4ICAgICAgICAgICAg
ICAgIFtQYWdlIDNdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgU2VjdXJlIFRyYW5zcG9ydCBm
b3IgUENFUCAgICAgICAgICAgICAgSnVseSAyMDE3CgoKICAgV2l0aGluIHRoaXMgZG9jdW1lbnQs
IFBDRVAgY29tbXVuaWNhdGlvbnMgYXJlIGRlc2NyaWJlZCB0aHJvdWdoIFBDQy0KICAgUENFIHJl
bGF0aW9uc2hpcC4gIFRoZSBQQ0UgYXJjaGl0ZWN0dXJlIGFsc28gc3VwcG9ydHMgdGhlIFBDRS1Q
Q0UKICAgY29tbXVuaWNhdGlvbiwgYnkgaGF2aW5nIHRoZSByZXF1ZXN0aW5nIFBDRSBmaWxsIHRo
ZSByb2xlIG9mIGEgUENDLAogICBhcyB1c3VhbC4gIFRodXMsIHRoZSBQQ0MgcmVmZXJzIHRvIGEg
UENDIG9yIGEgUENFIGluaXRpYXRpbmcgdGhlIFBDRVAKICAgc2Vzc2lvbiBhbmQgYWN0aW5nIGFz
IGEgY2xpZW50LgoKMi4gIFJlcXVpcmVtZW50cyBMYW5ndWFnZQoKICAgVGhlIGtleSB3b3JkcyAi
TVVTVCIsICJNVVNUIE5PVCIsICJSRVFVSVJFRCIsICJTSEFMTCIsICJTSEFMTCBOT1QiLAogICAi
U0hPVUxEIiwgIlNIT1VMRCBOT1QiLCAiUkVDT01NRU5ERUQiLCAiTUFZIiwgYW5kICJPUFRJT05B
TCIgaW4gdGhpcwogICBkb2N1bWVudCBhcmUgdG8gYmUgaW50ZXJwcmV0ZWQgYXMgZGVzY3JpYmVk
IGluIFtSRkMyMTE5XS4KCjMuICBBcHBseWluZyBQQ0VQUwoKMy4xLiAgT3ZlcnZpZXcKCiAgIFRo
ZSBzdGVwcyBpbnZvbHZlZCBpbiBlc3RhYmxpc2hpbmcgYSBQQ0VQUyBzZXNzaW9uIGFyZSBhcyBm
b2xsb3dzOgoKICAgMS4gIEVzdGFibGlzaG1lbnQgb2YgYSBUQ1AgY29ubmVjdGlvbi4KCiAgIDIu
ICBJbml0aWF0aW5nIHRoZSBUTFMgcHJvY2VkdXJlcyBieSB0aGUgU3RhcnRUTFMgbWVzc2FnZSBm
cm9tIFBDRSB0bwogICAgICAgUENDIGFuZCBmcm9tIFBDQyB0byBQQ0UuCgogICAzLiAgRXN0YWJs
aXNobWVudCBvZiBUTFMgY29ubmVjdGlvbi4KCiAgIDQuICBTdGFydCBleGNoYW5naW5nIFBDRVAg
bWVzc2FnZXMgYXMgcGVyIFtSRkM1NDQwXS4KCiAgIEltcGxlbWVudGF0aW9ucyBTSE9VTEQgZm9s
bG93IHRoZSBiZXN0IHByYWN0aWNlcyBhbmQgcmVjb21tZW5kYXRpb25zCiAgIGZvciB1c2luZyBU
TFMsIGFzIHBlciBbUkZDNzUyNV0uCgogICBJdCBzaG91bGQgYmUgbm90ZWQgdGhhdCB0aGlzIHBy
b2NlZHVyZSB1cGRhdGVzIHdoYXQgaXMgZGVmaW5lZCBpbgogICBzZWN0aW9uIDQuMi4xIGFuZCBz
ZWN0aW9uIDYuNyBvZiBbUkZDNTQ0MF0gcmVnYXJkaW5nIHRoZQogICBpbml0aWFsaXphdGlvbiBw
aGFzZSBhbmQgdGhlIHByb2Nlc3Npbmcgb2YgbWVzc2FnZXMgcHJpb3IgdG8gdGhlIE9wZW4KICAg
bWVzc2FnZS4gIFRoZSBkZXRhaWxzIG9mIHByb2Nlc3NpbmcgaW5jbHVkaW5nIGJhY2t3YXJkIGNv
bXBhdGliaWxpdHkKICAgYXJlIGRpc2N1c3NlZCBpbiB0aGUgZm9sbG93aW5nIHNlY3Rpb25zLgoK
My4yLiAgSW5pdGlhdGluZyB0aGUgVExTIFByb2NlZHVyZXMKCiAgIFNpbmNlIFBDRVAgY2FuIG9w
ZXJhdGUgZWl0aGVyIHdpdGggb3Igd2l0aG91dCBUTFMsIGl0IGlzIG5lY2Vzc2FyeQogICBmb3Ig
dGhlIFBDRVAgc3BlYWtlciB0byBpbmRpY2F0ZSB3aGV0aGVyIGl0IHdhbnRzIHRvIHNldCB1cCBh
IFRMUwogICBjb25uZWN0aW9uIG9yIG5vdC4gIEZvciB0aGlzIHB1cnBvc2UsIHRoaXMgZG9jdW1l
bnQgc3BlY2lmaWVzIGEgbmV3CiAgIFBDRVAgbWVzc2FnZSBjYWxsZWQgU3RhcnRUTFMuICBUaHVz
IHRoZSBQQ0VQIHNlc3Npb24gaXMgc2VjdXJlZCB2aWEKICAgVExTIGZyb20gdGhlIHN0YXJ0IGJl
Zm9yZSBleGNoYW5nZSBvZiBhbnkgb3RoZXIgUENFUCBtZXNzYWdlICh0aGF0CiAgIGluY2x1ZGVz
IHRoZSBPcGVuIG1lc3NhZ2UpLiAgVGhpcyBkb2N1bWVudCB0aHVzIHVwZGF0ZXMgW1JGQzU0NDBd
LAogICB3aGljaCByZXF1aXJlZCB0aGUgT3BlbiBtZXNzYWdlIHRvIGJlIHRoZSBmaXJzdCBQQ0VQ
IG1lc3NhZ2UuICBJbiB0aGUKICAgY2FzZSBvZiBhIFBDRVAgc2Vzc2lvbiB1c2luZyBUTFMgdGhl
IFN0YXJ0VExTIG1lc3NhZ2Ugd2lsbCBiZSBzZW50CiAgIGZpcnN0LiAgQWxzbyBhIFBDRVAgc3Bl
YWtlciB0aGF0IHN1cHBvcnRzIFBDRVBTIE1VU1QgTk9UIHN0YXJ0IHRoZQoKCgoKTG9wZXosIGV0
IGFsLiAgICAgICAgICAgRXhwaXJlcyBGZWJydWFyeSAxLCAyMDE4ICAgICAgICAgICAgICAgIFtQ
YWdlIDRdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgU2VjdXJlIFRyYW5zcG9ydCBmb3IgUENF
UCAgICAgICAgICAgICAgSnVseSAyMDE3CgoKICAgT3BlbldhaXQgdGltZXIgYWZ0ZXIgdGhlIFRD
UCBlc3RhYmxpc2htZW50LCBpbnN0ZWFkIGl0IHN0YXJ0cyBhCiAgIFN0YXJ0VExTV2FpdCB0aW1l
ciBhcyBkZXNjcmliZWQgaW4gU2VjdGlvbiAzLjMuCgogICBUaGUgUENFUCBzcGVha2VyIE1BWSBk
aXNjb3ZlciB0aGF0IHRoZSBQQ0VQIHBlZXIgc3VwcG9ydHMgUENFUFMgb3IKICAgY2FuIGJlIHBy
ZWNvbmZpZ3VyZWQgdG8gdXNlIFBDRVBTIGZvciBhIGdpdmVuIHBlZXIgKHNlZSBTZWN0aW9uIDQg
Zm9yCiAgIG1vcmUgZGV0YWlscykuICBTZWN1cmluZyB2aWEgVExTIG9mIGFuIGV4aXN0aW5nIFBD
RVAgc2Vzc2lvbiBpcyBub3QKICAgcGVybWl0dGVkLCB0aGUgc2Vzc2lvbiBNVVNUIGJlIGNsb3Nl
ZCBhbmQgcmUtZXN0YWJsaXNoZWQgd2l0aCBUTFMgYXMKICAgcGVyIHRoZSBwcm9jZWR1cmUgZGVz
Y3JpYmVkIGluIHRoaXMgZG9jdW1lbnQuCgogICBUaGUgU3RhcnRUTFMgbWVzc2FnZSBpcyBhIFBD
RVAgbWVzc2FnZSBzZW50IGJ5IGEgUENDIHRvIGEgUENFIGFuZCBieQogICBhIFBDRSB0byBhIFBD
QyBpbiBvcmRlciB0byBpbml0aWF0ZSB0aGUgVExTIHByb2NlZHVyZSBmb3IgUENFUC4gIFRoZQog
ICBNZXNzYWdlLVR5cGUgZmllbGQgb2YgdGhlIFBDRVAgY29tbW9uIGhlYWRlciBmb3IgdGhlIFN0
YXJ0VExTIG1lc3NhZ2UKICAgaXMgc2V0IHRvIFtUQkExIGJ5IElBTkFdLgoKICAgT25jZSB0aGUg
VENQIGNvbm5lY3Rpb24gaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IGVzdGFibGlzaGVkLCB0aGUgZmly
c3QKICAgbWVzc2FnZSBzZW50IGJ5IHRoZSBQQ0MgdG8gdGhlIFBDRSBhbmQgYnkgdGhlIFBDRSB0
byB0aGUgUENDIE1VU1QgYmUKICAgYSBTdGFydFRMUyBtZXNzYWdlIGZvciB0aGUgUENFUFMuICBO
b3RlIHRoaXMgaXMgYSBzaWduaWZpY2FudCBjaGFuZ2UKICAgZnJvbSBbUkZDNTQ0MF0gd2hlcmUg
dGhlIGZpcnN0IFBDRVAgbWVzc2FnZSBpcyB0aGUgT3BlbiBtZXNzYWdlLgoKICAgQSBQQ0VQIHNw
ZWFrZXIgcmVjZWl2aW5nIGEgU3RhcnRUTFMgbWVzc2FnZSwgYWZ0ZXIgYW55IG90aGVyIFBDRVAK
ICAgZXhjaGFuZ2UgaGFzIHRha2VuIHBsYWNlIChieSByZWNlaXZpbmcgb3Igc2VuZGluZyBhbnkg
b3RoZXIgbWVzc2FnZXMKICAgZnJvbSBlaXRoZXIgc2lkZSkgTVVTVCB0cmVhdCBpdCBhcyBhbiB1
bmV4cGVjdGVkIG1lc3NhZ2UgYW5kIHJlcGx5CiAgIHdpdGggYSBQQ0VyciBtZXNzYWdlIHdpdGgg
RXJyb3ItVHlwZSBzZXQgdG8gW1RCQTIgYnkgSUFOQV0gKFBDRVAKICAgU3RhcnRUTFMgZmFpbHVy
ZSkgYW5kIEVycm9yLXZhbHVlIHNldCB0byAxIChyZWNlcHRpb24gb2YgU3RhcnRUTFMKICAgYWZ0
ZXIgYW55IFBDRVAgZXhjaGFuZ2UpLCBhbmQgTVVTVCBjbG9zZSB0aGUgVENQIGNvbm5lY3Rpb24u
ICBBIFBDRVAKICAgc3BlYWtlciByZWNlaXZpbmcgYW55IG90aGVyIG1lc3NhZ2UgYXBhcnQgZnJv
bSBTdGFydFRMUywgT3Blbiwgb3IKICAgUENFcnIgYXMgdGhlIGZpcnN0IG1lc3NhZ2UsIE1VU1Qg
dHJlYXQgaXQgYXMgYW4gdW5leHBlY3RlZCBtZXNzYWdlCiAgIGFuZCByZXBseSB3aXRoIGEgUENF
cnIgbWVzc2FnZSB3aXRoIEVycm9yLVR5cGUgc2V0IHRvIFtUQkEyIGJ5IElBTkFdCiAgIChQQ0VQ
IFN0YXJ0VExTIGZhaWx1cmUpIGFuZCBFcnJvci12YWx1ZSBzZXQgdG8gMiAocmVjZXB0aW9uIG9m
IGFueQogICBvdGhlciBtZXNzYWdlIGFwYXJ0IGZyb20gU3RhcnRUTFMsIE9wZW4sIG9yIFBDRXJy
IG1lc3NhZ2UpLCBhbmQgTVVTVAogICBjbG9zZSB0aGUgVENQIGNvbm5lY3Rpb24uCgogICBJZiB0
aGUgUENFUCBzcGVha2VyIHRoYXQgZG9lcyBub3Qgc3VwcG9ydCBQQ0VQUywgcmVjZWl2ZXMgYSBT
dGFydFRMUwogICBtZXNzYWdlLCBpdCB3aWxsIGJlaGF2ZSBhY2NvcmRpbmcgdG8gdGhlIGV4aXN0
aW5nIGVycm9yIG1lY2hhbmlzbQogICBkZXNjcmliZWQgaW4gc2VjdGlvbiA2LjIgb2YgW1JGQzU0
NDBdIChpbiBjYXNlIG1lc3NhZ2UgaXMgcmVjZWl2ZWQKICAgcHJpb3IgdG8gYW4gT3BlbiBtZXNz
YWdlKSBvciBzZWN0aW9uIDYuOSBvZiBbUkZDNTQ0MF0gKGZvciB0aGUgY2FzZQogICBvZiByZWNl
cHRpb24gb2YgdW5rbm93biBtZXNzYWdlKS4gIFNlZSBTZWN0aW9uIDUgZm9yIG1vcmUgZGV0YWls
cy4KCiAgIElmIHRoZSBQQ0VQIHNwZWFrZXIgdGhhdCBvbmx5IHN1cHBvcnRzIFBDRVBTIGNvbm5l
Y3Rpb24gKGFzIGEgbG9jYWwKICAgcG9saWN5KSwgcmVjZWl2ZXMgYW4gT3BlbiBtZXNzYWdlLCBp
dCBNVVNUIHRyZWF0IGl0IGFzIGFuIHVuZXhwZWN0ZWQKICAgbWVzc2FnZSBhbmQgcmVwbHkgd2l0
aCBhIFBDRXJyIG1lc3NhZ2Ugd2l0aCBFcnJvci1UeXBlIHNldCB0byAxIChQQ0VQCiAgIHNlc3Np
b24gZXN0YWJsaXNobWVudCBmYWlsdXJlKSBhbmQgRXJyb3ItdmFsdWUgc2V0IHRvIDEgKHJlY2Vw
dGlvbiBvZgogICBhbiBpbnZhbGlkIE9wZW4gbWVzc2FnZSBvciBhIG5vbiBPcGVuIG1lc3NhZ2Up
LCBhbmQgTVVTVCBjbG9zZSB0aGUKICAgVENQIGNvbm5lY3Rpb24uCgogICBJZiBhIFBDQyB0aGF0
IHN1cHBvcnRzIFBDRVBTIGNvbm5lY3Rpb24gYXMgd2VsbCBhcyBhbGxvdyBub24tUENFUFMKICAg
Y29ubmVjdGlvbiAoYXMgYSBsb2NhbCBwb2xpY3kpLCBpdCBNVVNUIGZpcnN0IHRyeSB0byBlc3Rh
Ymxpc2ggUENFUFMsCiAgIGJ5IHNlbmRpbmcgU3RhcnRUTFMgbWVzc2FnZSBhbmQgaW4gY2FzZSBp
dCByZWNlaXZlcyBhbiBQQ0VyciBmcm9tIHRoZQoKCgpMb3BleiwgZXQgYWwuICAgICAgICAgICBF
eHBpcmVzIEZlYnJ1YXJ5IDEsIDIwMTggICAgICAgICAgICAgICAgW1BhZ2UgNV0KDApJbnRlcm5l
dC1EcmFmdCAgICAgICAgICBTZWN1cmUgVHJhbnNwb3J0IGZvciBQQ0VQICAgICAgICAgICAgICBK
dWx5IDIwMTcKCgogICBQQ0UsIGl0IE1BWSByZXRyeSB0byBlc3RhYmxpc2ggY29ubmVjdGlvbiB3
aXRob3V0IFBDRVBTIGJ5IHNlbmRpbmcgYW4KICAgT3BlbiBtZXNzYWdlLiAgSWYgYSBQQ0UgdGhh
dCBzdXBwb3J0cyBQQ0VQUyBjb25uZWN0aW9uIGFzIHdlbGwgYXMKICAgYWxsb3cgbm9uLVBDRVBT
IGNvbm5lY3Rpb24gKGFzIGEgbG9jYWwgcG9saWN5KSwgaXQgTVVTVCB3YWl0IHRvCiAgIHJlc3Bv
bmQgYWZ0ZXIgVENQIGVzdGFibGlzaG1lbnQsIGJhc2VkIG9uIHRoZSBtZXNzYWdlIHJlY2VpdmVk
IGZyb20KICAgdGhlIFBDQy4gIEluIGNhc2Ugb2YgU3RhcnRUTFMgbWVzc2FnZSwgUENFIHJlc3Bv
bmRzIHdpdGggc2VuZGluZwogICBTdGFydFRMUyBtZXNzYWdlIGFuZCBtb3ZpbmcgdG8gVExTIGVz
dGFibGlzaG1lbnQgcHJvY2VkdXJlcyBhcwogICBkZXNjcmliZWQgaW4gdGhpcyBkb2N1bWVudC4g
IEluIGNhc2Ugb2YgT3BlbiBtZXNzYWdlLCBQQ0UgcmVzcG9uZHMKICAgd2l0aCBPcGVuIG1lc3Nh
Z2UgYW5kIG1vdmUgdG8gUENFUCBzZXNzaW9uIGVzdGFibGlzaG1lbnQgcHJvY2VkdXJlIGFzCiAg
IHBlciBbUkZDNTQ0MF0uCgogICBBZnRlciB0aGUgZXhjaGFuZ2Ugb2YgU3RhcnRUTFMgbWVzc2Fn
ZXMsIGlmIGEgUENFUCBzcGVha2VyIGNhbm5vdAogICBlc3RhYmxpc2ggYSBUTFMgY29ubmVjdGlv
biBmb3Igc29tZSByZWFzb24gKGUuZy4gdGhlIHJlcXVpcmVkCiAgIG1lY2hhbmlzbXMgZm9yIGNl
cnRpZmljYXRlIHJldm9jYXRpb24gY2hlY2tpbmcgYXJlIG5vdCBhdmFpbGFibGUpLCBpdAogICBN
VVNUIHJldHVybiBhIFBDRXJyIG1lc3NhZ2UgKGluIGNsZWFyKSB3aXRoIEVycm9yLVR5cGUgc2V0
IHRvIFtUQkEyCiAgIGJ5IElBTkFdIChQQ0VQIFN0YXJ0VExTIGZhaWx1cmUpIGFuZCBFcnJvci12
YWx1ZSBzZXQgdG86CgogICBvICAzIChub3Qgd2l0aG91dCBUTFMpIGlmIGl0IGlzIG5vdCB3aWxs
aW5nIHRvIGV4Y2hhbmdlIFBDRVAgbWVzc2FnZXMKICAgICAgd2l0aG91dCB0aGUgc29saWNpdGVk
IFRMUyBjb25uZWN0aW9uLCBhbmQgaXQgTVVTVCBjbG9zZSB0aGUgVENQCiAgICAgIHNlc3Npb24u
CgogICBvICA0IChvayB3aXRob3V0IFRMUykgaWYgaXQgaXMgd2lsbGluZyB0byBleGNoYW5nZSBQ
Q0VQIG1lc3NhZ2VzCiAgICAgIHdpdGhvdXQgdGhlIHNvbGljaXRlZCBUTFMgY29ubmVjdGlvbiwg
YW5kIGl0IE1VU1QgY2xvc2UgdGhlIFRDUAogICAgICBzZXNzaW9uLiAgVGhlIHJlY2VpdmVyIE1B
WSBjaG9vc2UgdG8gcmUtZXN0YWJsaXNoIHRoZSBQQ0VQIHNlc3Npb24KICAgICAgd2l0aG91dCBU
TFMgbmV4dC4KCiAgIElmIHRoZSBQQ0VQIHNwZWFrZXIgc3VwcG9ydHMgUENFUFMgYW5kIGNhbiBl
c3RhYmxpc2ggYSBUTFMgY29ubmVjdGlvbgogICBpdCBNVVNUIHN0YXJ0IHRoZSBUTFMgY29ubmVj
dGlvbiBlc3RhYmxpc2htZW50IHN0ZXBzIGRlc2NyaWJlZCBpbgogICBTZWN0aW9uIDMuNCBiZWZv
cmUgdGhlIFBDRVAgaW5pdGlhbGl6YXRpb24gcHJvY2VkdXJlIChzZWN0aW9uIDQuMi4xCiAgIG9m
IFtSRkM1NDQwXSkuCgogICBBIFBDRVAgc3BlYWtlciB0aGF0IGRvZXMgbm90IHN1cHBvcnQgUENF
UFMgb3IgaGFzIGxlYXJuZWQgdGhlIHBlZXIKICAgd2lsbGluZ25lc3MgdG8gcmVlc3RhYmxpc2gg
c2Vzc2lvbiB3aXRob3V0IFRMUywgY2FuIHNlbmQgdGhlIE9wZW4KICAgbWVzc2FnZSBkaXJlY3Rs
eSwgYXMgcGVyIFtSRkM1NDQwXS4KCiAgIEdpdmVuIHRoZSBhc3ltbWV0cmljIG5hdHVyZSBvZiBU
TFMgZm9yIGNvbm5lY3Rpb24gZXN0YWJsaXNobWVudCBpdCBpcwogICByZWxldmFudCB0byBpZGVu
dGlmeSB0aGUgcm9sZXMgb2YgZWFjaCBvZiB0aGUgUENFUCBwZWVycyBpbiBpdC4gIFRoZQogICBQ
Q0MgU0hBTEwgYWN0IGFzIFRMUyBjbGllbnQsIGFuZCB0aGUgUENFIFNIQUxMIGFjdCBhcyBUTFMg
c2VydmVyLAogICBhY2NvcmRpbmcgdG8gW1JGQzUyNDZdLgoKICAgVGhlc2UgcHJvY2VkdXJlcyBt
aW5pbWl6ZSB0aGUgaW1wYWN0IG9mIFBDRVBTIHN1cHBvcnQgaW4gUENFUAogICBpbXBsZW1lbnRh
dGlvbnMgd2l0aG91dCByZXF1aXJpbmcgYWRkaXRpb25hbCBkZWRpY2F0ZWQgcG9ydHMgZm9yCiAg
IHJ1bm5pbmcgUENFUCB3aXRoIFRMUy4KCiAgIEFzIHBlciB0aGUgcmVjb21tZW5kYXRpb24gZnJv
bSBbUkZDNzUyNV0gdG8gYXZvaWQgZG93bmdyYWRlIGF0dGFja3MsCiAgIFBDRVAgcGVlcnMgdGhh
dCBzdXBwb3J0IFBDRVBTLCBTSE9VTEQgZGVmYXVsdCB0byBzdHJpY3QgVExTCiAgIGNvbmZpZ3Vy
YXRpb24gaS5lLiBkbyBub3QgYWxsb3cgbm9uLVRMUyBQQ0VQIHNlc3Npb25zIHRvIGJlCiAgIGVz
dGFibGlzaGVkLiAgUENFUFMgaW1wbGVtZW50YXRpb25zIE1BWSBwcm92aWRlIGFuIG9wdGlvbiB0
byBhbGxvdwogICB0aGUgb3BlcmF0b3IgdG8gbWFudWFsbHkgb3ZlcnJpZGUgc3RyaWN0IFRMUyBj
b25maWd1cmF0aW9uIGFuZCBhbGxvdwoKCgpMb3BleiwgZXQgYWwuICAgICAgICAgICBFeHBpcmVz
IEZlYnJ1YXJ5IDEsIDIwMTggICAgICAgICAgICAgICAgW1BhZ2UgNl0KDApJbnRlcm5ldC1EcmFm
dCAgICAgICAgICBTZWN1cmUgVHJhbnNwb3J0IGZvciBQQ0VQICAgICAgICAgICAgICBKdWx5IDIw
MTcKCgogICB1bnNlY3VyZWQgY29ubmVjdGlvbnMuICBFeGVjdXRpb24gb2YgdGhpcyBvdmVycmlk
ZSBTSE9VTEQgdHJpZ2dlciBhCiAgIHdhcm5pbmcgYWJvdXQgdGhlIHNlY3VyaXR5IGltcGxpY2F0
aW9ucyBvZiBwZXJtaXR0aW5nIHVuc2VjdXJlZAogICBjb25uZWN0aW9ucy4KCjMuMy4gIFRoZSBT
dGFydFRMUyBNZXNzYWdlCgogICBUaGUgU3RhcnRUTFMgbWVzc2FnZSBpcyB1c2VkIHRvIGluaXRp
YXRlIHRoZSBUTFMgcHJvY2VkdXJlIGZvciBhCiAgIFBDRVBTIHNlc3Npb24gYmV0d2VlbiB0aGUg
UENFUCBwZWVycy4gIEEgUENFUCBzcGVha2VyIHNlbmRzIHRoZQogICBTdGFydFRMUyBtZXNzYWdl
IHRvIHJlcXVlc3QgbmVnb3RpYXRpb24gYW5kIGVzdGFibGlzaG1lbnQgb2YgVExTCiAgIGNvbm5l
Y3Rpb24gZm9yIFBDRVAuICBPbiByZWNlaXZpbmcgYSBTdGFydFRMUyBtZXNzYWdlIGZyb20gdGhl
IFBDRVAKICAgcGVlciAoaS5lLiAgd2hlbiB0aGUgUENFUCBzcGVha2VyIGhhcyBzZW50IGFuZCBy
ZWNlaXZlZCBTdGFydFRMUwogICBtZXNzYWdlKSBpdCBpcyByZWFkeSB0byBzdGFydCBUTFMgbmVn
b3RpYXRpb24gYW5kIGVzdGFibGlzaG1lbnQgYW5kCiAgIG1vdmUgdG8gc3RlcHMgZGVzY3JpYmVk
IGluIFNlY3Rpb24gMy40LgoKICAgVGhlIGNvbGxpc2lvbiByZXNvbHV0aW9uIHByb2NlZHVyZXMg
ZGVzY3JpYmVkIGluIFtSRkM1NDQwXSBmb3IgdGhlCiAgIGV4Y2hhbmdlIG9mIE9wZW4gbWVzc2Fn
ZXMgTVVTVCBiZSBhcHBsaWVkIGJ5IHRoZSBQQ0VQIHBlZXJzIGR1cmluZwogICB0aGUgZXhjaGFu
Z2Ugb2YgU3RhcnRUTFMgbWVzc2FnZXMuCgogICBUaGUgZm9ybWF0IG9mIGEgU3RhcnRUTFMgbWVz
c2FnZSBpcyBhcyBmb2xsb3dzOgoKCiAgICAgIDxTdGFydFRMUyBNZXNzYWdlPjo6PSA8Q29tbW9u
IEhlYWRlcj4KCgogICBUaGUgU3RhcnRUTFMgbWVzc2FnZSBNVVNUIGNvbnRhaW4gb25seSB0aGUg
UENFUCBjb21tb24gaGVhZGVyIHdpdGgKICAgTWVzc2FnZS1UeXBlIGZpZWxkIHNldCB0byBbVEJB
MSBieSBJQU5BXS4KCiAgIE9uY2UgdGhlIFRDUCBjb25uZWN0aW9uIGhhcyBiZWVuIHN1Y2Nlc3Nm
dWxseSBlc3RhYmxpc2hlZCwgdGhlIFBDRVAKICAgc3BlYWtlciBNVVNUIHN0YXJ0IGEgdGltZXIg
Y2FsbGVkIFN0YXJ0VExTV2FpdCB0aW1lciwgYWZ0ZXIgdGhlCiAgIGV4cGlyYXRpb24gb2Ygd2hp
Y2gsIGlmIG5laXRoZXIgU3RhcnRUTFMgbWVzc2FnZSBoYXMgYmVlbiByZWNlaXZlZCwKICAgbm9y
IGEgUENFcnIvT3BlbiAoaW4gY2FzZSBvZiBmYWlsdXJlIGFuZCBQQ0VQUyBub3Qgc3VwcG9ydGVk
IGJ5IHRoZQogICBwZWVyIHJlc3BlY3RpdmVseSksIGl0IE1VU1Qgc2VuZCBhIFBDRXJyIG1lc3Nh
Z2Ugd2l0aCBFcnJvci1UeXBlIHNldAogICB0byBbVEJBMiBieSBJQU5BXSBhbmQgRXJyb3ItdmFs
dWUgc2V0IHRvIDUgKG5vIFN0YXJ0VExTIChub3IgUENFcnIvCiAgIE9wZW4pIG1lc3NhZ2UgcmVj
ZWl2ZWQgYmVmb3JlIHRoZSBleHBpcmF0aW9uIG9mIHRoZSBTdGFydFRMU1dhaXQKICAgdGltZXIp
IGFuZCBpdCBNVVNUIHJlbGVhc2UgdGhlIFRDUCBjb25uZWN0aW9uIC4gQSBSRUNPTU1FTkRFRCB2
YWx1ZQogICBmb3IgU3RhcnRUTFNXYWl0IHRpbWVyIGlzIDYwIHNlY29uZHMuICBUaGUgdmFsdWUg
b2YgU3RhcnRUTFNXYWl0CiAgIHRpbWVyIE1VU1QgTk9UIGJlIGxlc3MgdGhhbiBPcGVuV2FpdCB0
aW1lci4KCgoKCgoKCgoKCgoKCgpMb3BleiwgZXQgYWwuICAgICAgICAgICBFeHBpcmVzIEZlYnJ1
YXJ5IDEsIDIwMTggICAgICAgICAgICAgICAgW1BhZ2UgN10KDApJbnRlcm5ldC1EcmFmdCAgICAg
ICAgICBTZWN1cmUgVHJhbnNwb3J0IGZvciBQQ0VQICAgICAgICAgICAgICBKdWx5IDIwMTcKCgog
ICAgICAgICAgICAgICAgICArLSstKyAgICAgICAgICAgICAgICAgKy0rLSsKICAgICAgICAgICAg
ICAgICAgfFBDQ3wgICAgICAgICAgICAgICAgIHxQQ0V8CiAgICAgICAgICAgICAgICAgICstKy0r
ICAgICAgICAgICAgICAgICArLSstKwogICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAg
ICAgICAgICB8CiAgICAgICAgICAgICAgICAgICAgfCBTdGFydFRMUyAgICAgICAgICAgIHwKICAg
ICAgICAgICAgICAgICAgICB8IG1zZyAgICAgICAgICAgICAgICAgfAogICAgICAgICAgICAgICAg
ICAgIHwtLS0tLS0tICAgICAgICAgICAgICB8CiAgICAgICAgICAgICAgICAgICAgfCAgICAgICBc
ICAgU3RhcnRUTFMgIHwKICAgICAgICAgICAgICAgICAgICB8ICAgICAgICBcICBtc2cgICAgICAg
fAogICAgICAgICAgICAgICAgICAgIHwgICAgICAgICBcICAtLS0tLS0tLS18CiAgICAgICAgICAg
ICAgICAgICAgfCAgICAgICAgICBcLyAgICAgICAgIHwKICAgICAgICAgICAgICAgICAgICB8ICAg
ICAgICAgIC9cICAgICAgICAgfAogICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAvICAtLS0t
LS0tLT58CiAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgLyAgICAgICAgICAgIHwKICAgICAg
ICAgICAgICAgICAgICB8PC0tLS0tLSAgICAgICAgICAgICAgfAogICAgICAgICAgICAgICAgICAg
IHw6Ojo6Ojo6OjpUTFM6Ojo6Ojo6Ojp8CiAgICAgICAgICAgICAgICAgICAgfDo6Ojo6RXN0YWJs
aXNobWVudDo6OnwKICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgfAog
ICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICB8CiAgICAgICAgICAgICAg
ICAgICAgfDo6Ojo6OjpQQ0VQOjo6Ojo6Ojo6OnwKICAgICAgICAgICAgICAgICAgICB8ICAgICAg
ICAgICAgICAgICAgICAgfAoKICAgICAgICAgICAgRmlndXJlIDE6IEJvdGggUENFUCBTcGVha2Vy
IHN1cHBvcnRzIFBDRVBTIChzdHJpY3QpCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgpMb3Bl
eiwgZXQgYWwuICAgICAgICAgICBFeHBpcmVzIEZlYnJ1YXJ5IDEsIDIwMTggICAgICAgICAgICAg
ICAgW1BhZ2UgOF0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICBTZWN1cmUgVHJhbnNwb3J0IGZv
ciBQQ0VQICAgICAgICAgICAgICBKdWx5IDIwMTcKCgogICAgICAgICAgICAgICAgICArLSstKyAg
ICAgICAgICAgICAgICAgKy0rLSsKICAgICAgICAgICAgICAgICAgfFBDQ3wgICAgICAgICAgICAg
ICAgIHxQQ0V8CiAgICAgICAgICAgICAgICAgICstKy0rICAgICAgICAgICAgICAgICArLSstKwog
ICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICB8CiAgICAgICAgICAgICAg
ICAgICAgfCBTdGFydFRMUyAgICAgICAgICAgIHwKICAgICAgICAgICAgICAgICAgICB8IG1zZyAg
ICAgICAgICAgICAgICAgfAogICAgICAgICAgICAgICAgICAgIHwtLS0tLS0tICAgICAgICAgICAg
ICB8CiAgICAgICAgICAgICAgICAgICAgfCAgICAgICBcICAgU3RhcnRUTFMgIHwKICAgICAgICAg
ICAgICAgICAgICB8ICAgICAgICBcICBtc2cgICAgICAgfAogICAgICAgICAgICAgICAgICAgIHwg
ICAgICAgICBcICAtLS0tLS0tLS18CiAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgICBcLyAg
ICAgICAgIHwKICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAgIC9cICAgICAgICAgfAogICAg
ICAgICAgICAgICAgICAgIHwgICAgICAgICAvICAtLS0tLS0tLT58CiAgICAgICAgICAgICAgICAg
ICAgfCAgICAgICAgLyAgICAgICAgICAgIHwKICAgICAgICAgICAgICAgICAgICB8PC0tLS0tLSAg
ICAgICAgICAgICAgfAogICAgICAgICAgICAgICAgICAgIHw6Ojo6Ojo6OjpUTFM6Ojo6Ojo6Ojp8
IFRMUyBFc3RhYmxpc2htZW50CiAgICAgICAgICAgICAgICAgICAgfDo6Ojo6RXN0YWJsaXNobWVu
dDo6OnwgRmFpbHVyZQogICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICB8
CiAgICAgICAgICAgICAgICAgICAgfDwtLS0tLS0tLS0tLS0tLS0tLS0tLXwgU2VuZCBFcnJvci1U
eXBlIFRCQTIKICAgICAgICAgICAgICAgICAgICB8ICAgICAgUENFcnIgICAgICAgICAgfCBFcnJv
ci1WYWx1ZSAzLzQKICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgfAoK
CiAgICAgIEZpZ3VyZSAyOiBCb3RoIFBDRVAgU3BlYWtlciBzdXBwb3J0cyBQQ0VQUyAoc3RyaWN0
KSwgYnV0IGNhbm5vdAogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgZXN0YWJsaXNoIFRM
UwoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCkxvcGV6LCBldCBhbC4gICAgICAgICAgIEV4cGly
ZXMgRmVicnVhcnkgMSwgMjAxOCAgICAgICAgICAgICAgICBbUGFnZSA5XQoMCkludGVybmV0LURy
YWZ0ICAgICAgICAgIFNlY3VyZSBUcmFuc3BvcnQgZm9yIFBDRVAgICAgICAgICAgICAgIEp1bHkg
MjAxNwoKCiAgICAgICAgICAgICAgICAgICstKy0rICAgICAgICAgICAgICAgICArLSstKwogICAg
ICAgICAgICAgICAgICB8UENDfCAgICAgICAgICAgICAgICAgfFBDRXwKICAgICAgICAgICAgICAg
ICAgKy0rLSsgICAgICAgICAgICAgICAgICstKy0rCiAgICAgICAgICAgICAgICAgICAgfCAgICAg
ICAgICAgICAgICAgICAgIHwgIERvZXMgbm90IHN1cHBvcnQKICAgICAgICAgICAgICAgICAgICB8
IFN0YXJ0VExTICAgICAgICAgICAgfCAgUENFUFMgYW5kIHRodXMKICAgICAgICAgICAgICAgICAg
ICB8IG1zZyAgICAgICAgICAgICAgICAgfCAgc2VuZHMgT3BlbgogICAgICAgICAgICAgICAgICAg
IHwtLS0tLS0tICAgICAgICAgICAgICB8CiAgICAgICAgICAgICAgICAgICAgfCAgICAgICBcICAg
T3BlbiAgICAgIHwKICAgICAgICAgICAgICAgICAgICB8ICAgICAgICBcICBtc2cgICAgICAgfAog
ICAgICAgICAgICAgICAgICAgIHwgICAgICAgICBcICAtLS0tLS0tLS18CiAgICAgICAgICAgICAg
ICAgICAgfCAgICAgICAgICBcLyAgICAgICAgIHwKICAgICAgICAgICAgICAgICAgICB8ICAgICAg
ICAgIC9cICAgICAgICAgfAogICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAvICAtLS0tLS0t
LT58CiAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgLyAgICAgICAgICAgIHwKICAgICAgICAg
ICAgICAgICAgICB8PC0tLS0tLSAgICAgICAgICAgICAgfAogICAgICAgICAgICAgICAgICAgIHwg
ICAgICAgICAgICAgICAgICAgICB8CiAgICAgICAgICAgICAgICAgICAgfDwtLS0tLS0tLS0tLS0t
LS0tLS0tLXwgU2VuZCBFcnJvcgogICAgICAgICAgICAgICAgICAgIHwgICAgICAgUENFcnIgICAg
ICAgICB8IChub24tT3BlbiBtZXNzYWdlCiAgICAgICAgICAgICAgICAgICAgfDwtLS0tLS0tLS0t
LS0tLS0tLS0tLXwgIHJlY2VpdmVkKQogICAgICAgICAgICAgICAgICAgIHwgICAgICAgQ2xvc2Ug
ICAgICAgICB8CiAgICAgICAgICAgICAgICAgICAgLy8vLy8vLy8vIFRDUCAvLy8vLy8vLy8KICAg
ICAgICAgICAgICAgICAgICAvLy8vLy9yZS1lc3RhYmxpc2gvLy8vLwogICAgICAgICAgU2VuZCBP
cGVuIHwgT3BlbiAgICAgICAgICAgICAgICB8CiAgICAgICAgICB0aGlzIHRpbWUgfCBtc2cgICAg
ICAgICAgICAgICAgIHwKICAgICAgICAgICAgICAgICAgICB8LS0tLS0tLSAgICAgICAgICAgICAg
fAogICAgICAgICAgICAgICAgICAgIHwgICAgICAgXCAgIE9wZW4gICAgICB8CiAgICAgICAgICAg
ICAgICAgICAgfCAgICAgICAgXCAgbXNnICAgICAgIHwKICAgICAgICAgICAgICAgICAgICB8ICAg
ICAgICAgXCAgLS0tLS0tLS0tfAogICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgXC8gICAg
ICAgICB8CiAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAvXCAgICAgICAgIHwKICAgICAg
ICAgICAgICAgICAgICB8ICAgICAgICAgLyAgLS0tLS0tLS0+fAogICAgICAgICAgICAgICAgICAg
IHwgICAgICAgIC8gICAgICAgICAgICB8CiAgICAgICAgICAgICAgICAgICAgfDwtLS0tLS0gICAg
ICAgICAgICAgIHwKCgoKICAgIEZpZ3VyZSAzOiBPbmUgUENFUCBTcGVha2VyIChQQ0UpIGRvZXMg
bm90IHN1cHBvcnQgUENFUFMsIHdoaWxlIFBDQwogICAgICAgICAgICAgICAgICAgIHN1cHBvcnRz
IGJvdGggd2l0aCBvciB3aXRob3V0IFBDRVBTCgoKCgoKCgoKCgoKCgpMb3BleiwgZXQgYWwuICAg
ICAgICAgICBFeHBpcmVzIEZlYnJ1YXJ5IDEsIDIwMTggICAgICAgICAgICAgICBbUGFnZSAxMF0K
DApJbnRlcm5ldC1EcmFmdCAgICAgICAgICBTZWN1cmUgVHJhbnNwb3J0IGZvciBQQ0VQICAgICAg
ICAgICAgICBKdWx5IDIwMTcKCgogICAgICAgICAgICAgICAgICArLSstKyAgICAgICAgICAgICAg
ICAgKy0rLSsKICAgICAgICAgICAgICAgICAgfFBDQ3wgICAgICAgICAgICAgICAgIHxQQ0V8CiAg
ICAgICAgICAgICAgICAgICstKy0rICAgICAgICAgICAgICAgICArLSstKwogICAgICAgICAgICAg
ICAgICAgIHwgICAgICAgICAgICAgICAgICAgICB8CiAgICAgICAgICAgICAgICAgICAgfCBTdGFy
dFRMUyAgICAgICAgICAgIHwKICAgICAgICAgICAgICAgICAgICB8IG1zZyAgICAgICAgICAgICAg
ICAgfCBQQ0Ugd2FpdHMKICAgICAgICAgICAgICAgICAgICB8LS0tLS0tLS0tLS0tLS0tLS0tLS0+
fCBmb3IgUENDIGFuZAogICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICBTdGFydFRMUyB8
IHJlc3BvbmQgd2l0aAogICAgICAgICAgICAgICAgICAgIHw8LS0tLS0tLS0tLS0tLS0tLS0tLS18
IFN0YXJ0IFRMUwogICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICB8CiAg
ICAgICAgICAgICAgICAgICAgfDo6Ojo6Ojo6OlRMUzo6Ojo6Ojo6OnwKICAgICAgICAgICAgICAg
ICAgICB8Ojo6OjpFc3RhYmxpc2htZW50Ojo6fAogICAgICAgICAgICAgICAgICAgIHwgICAgICAg
ICAgICAgICAgICAgICB8CiAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICAgICAg
IHwKICAgICAgICAgICAgICAgICAgICB8Ojo6Ojo6OlBDRVA6Ojo6Ojo6Ojo6fAogICAgICAgICAg
ICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICB8CgogICAgRmlndXJlIDQ6IEJvdGggUENF
UCBTcGVha2VyIHN1cHBvcnRzIFBDRVBTIGFzIHdlbGwgYXMgd2l0aG91dCBQQ0VQUwoKCiAgICAg
ICAgICAgICAgICAgICstKy0rICAgICAgICAgICAgICAgICArLSstKwogICAgICAgICAgICAgICAg
ICB8UENDfCAgICAgICAgICAgICAgICAgfFBDRXwKICAgICAgICAgICAgICAgICAgKy0rLSsgICAg
ICAgICAgICAgICAgICstKy0rCiAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICAg
ICAgIHwKICAgICAgICAgICAgICAgICAgICB8IE9wZW4gICAgICAgICAgICAgICAgfAogICAgICAg
ICAgICAgICAgICAgIHwgbXNnICAgICAgICAgICAgICAgICB8IFBDRSB3YWl0cwogICAgICAgICAg
ICAgICAgICAgIHwtLS0tLS0tLS0tLS0tLS0tLS0tLT58IGZvciBQQ0MgYW5kCiAgICAgICAgICAg
ICAgICAgICAgfCAgICAgICAgICAgICAgICBPcGVuIHwgcmVzcG9uZCB3aXRoCiAgICAgICAgICAg
ICAgICAgICAgfDwtLS0tLS0tLS0tLS0tLS0tLS0tLXwgT3BlbgogICAgICAgICAgICAgICAgICAg
IHwgICAgICAgICAgICAgICAgICAgICB8CiAgICAgICAgICAgICAgICAgICAgfDo6Ojo6OjpQQ0VQ
Ojo6Ojo6Ojo6OnwKICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgfAoK
ICAgRmlndXJlIDU6IFBDRSBzdXBwb3J0cyBQQ0VQUyBhcyB3ZWxsIGFzIHdpdGhvdXQgUENFUFMs
IHdoaWxlIFBDQyBkb2VzCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgbm90IHN1cHBvcnQg
UENFUFMKCjMuNC4gIFRMUyBDb25uZWN0aW9uIEVzdGFibGlzaG1lbnQKCiAgIE9uY2UgdGhlIGVz
dGFibGlzaG1lbnQgb2YgVExTIGhhcyBiZWVuIGFncmVlZCBieSB0aGUgUENFUCBwZWVycywgdGhl
CiAgIGNvbm5lY3Rpb24gZXN0YWJsaXNobWVudCBTSEFMTCBmb2xsb3cgdGhlIGZvbGxvd2luZyBz
dGVwczoKCiAgIDEuICBJbW1lZGlhdGVseSBuZWdvdGlhdGUgYSBUTFMgc2Vzc2lvbiBhY2NvcmRp
bmcgdG8gW1JGQzUyNDZdLiAgVGhlCiAgICAgICBmb2xsb3dpbmcgcmVzdHJpY3Rpb25zIGFwcGx5
OgoKICAgICAgICogIFN1cHBvcnQgZm9yIFRMUyB2MS4yIFtSRkM1MjQ2XSBvciBsYXRlciBpcyBS
RVFVSVJFRC4KCiAgICAgICAqICBTdXBwb3J0IGZvciBjZXJ0aWZpY2F0ZS1iYXNlZCBtdXR1YWwg
YXV0aGVudGljYXRpb24gaXMKICAgICAgICAgIFJFUVVJUkVELgoKCgpMb3BleiwgZXQgYWwuICAg
ICAgICAgICBFeHBpcmVzIEZlYnJ1YXJ5IDEsIDIwMTggICAgICAgICAgICAgICBbUGFnZSAxMV0K
DApJbnRlcm5ldC1EcmFmdCAgICAgICAgICBTZWN1cmUgVHJhbnNwb3J0IGZvciBQQ0VQICAgICAg
ICAgICAgICBKdWx5IDIwMTcKCgogICAgICAgKiAgTmVnb3RpYXRpb24gb2YgbXV0dWFsIGF1dGhl
bnRpY2F0aW9uIGlzIFJFUVVJUkVELgoKICAgICAgICogIE5lZ290aWF0aW9uIG9mIGEgY2lwaGVy
c3VpdGUgcHJvdmlkaW5nIGZvciBpbnRlZ3JpdHkKICAgICAgICAgIHByb3RlY3Rpb24gaXMgUkVR
VUlSRUQuCgogICAgICAgKiAgTmVnb3RpYXRpb24gb2YgYSBjaXBoZXJzdWl0ZSBwcm92aWRpbmcg
Zm9yIGNvbmZpZGVudGlhbGl0eSBpcwogICAgICAgICAgUkVDT01NRU5ERUQuCgogICAgICAgKiAg
U3VwcG9ydCBmb3IgYW5kIG5lZ290aWF0aW9uIG9mIGNvbXByZXNzaW9uIGlzIE9QVElPTkFMLgoK
ICAgICAgICogIFBDRVBTIGltcGxlbWVudGF0aW9ucyBNVVNULCBhdCBhIG1pbmltdW0sIHN1cHBv
cnQgbmVnb3RpYXRpb24KICAgICAgICAgIG9mIHRoZSBUTFNfUlNBX1dJVEhfQUVTXzEyOF9HQ01f
U0hBMjU2LCBhbmQgU0hPVUxEIHN1cHBvcnQKICAgICAgICAgIFRMU19SU0FfV0lUSF9BRVNfMjU2
X0dDTV9TSEEzODQgYXMgd2VsbCBbUkZDNTI4OF0uICBJbgogICAgICAgICAgYWRkaXRpb24sIFBD
RVBTIGltcGxlbWVudGF0aW9ucyBNVVNUIHN1cHBvcnQgbmVnb3RpYXRpb24gb2YKICAgICAgICAg
IHRoZSBtYW5kYXRvcnktdG8taW1wbGVtZW50IGNpcGhlcnN1aXRlcyByZXF1aXJlZCBieSB0aGUK
ICAgICAgICAgIHZlcnNpb25zIG9mIFRMUyB0aGF0IHRoZXkgc3VwcG9ydC4KCiAgIDIuICBQZWVy
IGF1dGhlbnRpY2F0aW9uIGNhbiBiZSBwZXJmb3JtZWQgaW4gYW55IG9mIHRoZSBmb2xsb3dpbmcg
dHdvCiAgICAgICBSRVFVSVJFRCBvcGVyYXRpb24gbW9kZWxzOgoKICAgICAgICogIFRMUyB3aXRo
IFguNTA5IGNlcnRpZmljYXRlcyB1c2luZyBQdWJsaWMtS2V5IEluZnJhc3RydWN0dXJlCiAgICAg
ICAgICBFeGNoYW5nZSAoUEtJWCkgdHJ1c3QgbW9kZWxzOgoKICAgICAgICAgICsgIEltcGxlbWVu
dGF0aW9ucyBNVVNUIGFsbG93IHRoZSBjb25maWd1cmF0aW9uIG9mIGEgbGlzdCBvZgogICAgICAg
ICAgICAgdHJ1c3RlZCBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0aWVzIChDQXMpIGZvciBpbmNvbWlu
ZwogICAgICAgICAgICAgY29ubmVjdGlvbnMuCgogICAgICAgICAgKyAgQ2VydGlmaWNhdGUgdmFs
aWRhdGlvbiBNVVNUIGluY2x1ZGUgdGhlIHZlcmlmaWNhdGlvbiBydWxlcwogICAgICAgICAgICAg
YXMgcGVyIFtSRkM1MjgwXS4KCiAgICAgICAgICArICBQQ0VQUyBpbXBsZW1lbnRhdGlvbnMgU0hP
VUxEIGluY29ycG9yYXRlIHJldm9jYXRpb24gbWV0aG9kcwogICAgICAgICAgICAgKENSTCBkb3du
bG9hZGluZywgT0NTUC4uLikgYWNjb3JkaW5nIHRvIHRoZSB0cnVzdGVkIENBCiAgICAgICAgICAg
ICBwb2xpY2llcy4KCiAgICAgICAgICArICBJbXBsZW1lbnRhdGlvbnMgU0hPVUxEIGluZGljYXRl
IHRoZWlyIHRydXN0ZWQgQ0FzLiAgRm9yIFRMUwogICAgICAgICAgICAgMS4yLCB0aGlzIGlzIGRv
bmUgdXNpbmcgW1JGQzUyNDZdLCBTZWN0aW9uIDcuNC40LAogICAgICAgICAgICAgImNlcnRpZmlj
YXRlX2F1dGhvcml0aWVzIiAoc2VydmVyIHNpZGUpIGFuZCBbUkZDNjA2Nl0sCiAgICAgICAgICAg
ICBTZWN0aW9uIDYgIlRydXN0ZWQgQ0EgSW5kaWNhdGlvbiIgKGNsaWVudCBzaWRlKS4KCiAgICAg
ICAgICArICBQZWVyIHZhbGlkYXRpb24gYWx3YXlzIFNIT1VMRCBpbmNsdWRlIGEgY2hlY2sgb24g
d2hldGhlcgogICAgICAgICAgICAgdGhlIGxvY2FsbHkgY29uZmlndXJlZCBleHBlY3RlZCBETlMg
bmFtZSBvciBJUCBhZGRyZXNzIG9mCiAgICAgICAgICAgICB0aGUgcGVlciB0aGF0IGlzIGNvbnRh
Y3RlZCBtYXRjaGVzIGl0cyBwcmVzZW50ZWQKICAgICAgICAgICAgIGNlcnRpZmljYXRlLiAgRE5T
IG5hbWVzIGFuZCBJUCBhZGRyZXNzZXMgY2FuIGJlIGNvbnRhaW5lZAogICAgICAgICAgICAgaW4g
dGhlIENvbW1vbiBOYW1lIChDTikgb3Igc3ViamVjdEFsdE5hbWUgZW50cmllcy4gIEZvcgogICAg
ICAgICAgICAgdmVyaWZpY2F0aW9uLCBvbmx5IG9uZSBvZiB0aGVzZSBlbnRyaWVzIGlzIHRvIGJl
CiAgICAgICAgICAgICBjb25zaWRlcmVkLiAgVGhlIGZvbGxvd2luZyBwcmVjZWRlbmNlIGFwcGxp
ZXM6IGZvciBETlMgbmFtZQogICAgICAgICAgICAgdmFsaWRhdGlvbiwgc3ViamVjdEFsdE5hbWU6
RE5TIGhhcyBwcmVjZWRlbmNlIG92ZXIgQ047IGZvcgoKCgoKTG9wZXosIGV0IGFsLiAgICAgICAg
ICAgRXhwaXJlcyBGZWJydWFyeSAxLCAyMDE4ICAgICAgICAgICAgICAgW1BhZ2UgMTJdCgwKSW50
ZXJuZXQtRHJhZnQgICAgICAgICAgU2VjdXJlIFRyYW5zcG9ydCBmb3IgUENFUCAgICAgICAgICAg
ICAgSnVseSAyMDE3CgoKICAgICAgICAgICAgIElQIGFkZHJlc3MgdmFsaWRhdGlvbiwgc3ViamVj
dEFsdE5hbWU6aVBBZGRyIGhhcyBwcmVjZWRlbmNlCiAgICAgICAgICAgICBvdmVyIENOLgoKICAg
ICAgICAgICsgIEltcGxlbWVudGF0aW9ucyBNQVkgYWxsb3cgdGhlIGNvbmZpZ3VyYXRpb24gb2Yg
YSBzZXQgb2YKICAgICAgICAgICAgIGFkZGl0aW9uYWwgcHJvcGVydGllcyBvZiB0aGUgY2VydGlm
aWNhdGUgdG8gY2hlY2sgZm9yIGEKICAgICAgICAgICAgIHBlZXIncyBhdXRob3JpemF0aW9uIHRv
IGNvbW11bmljYXRlIChlLmcuLCBhIHNldCBvZiBhbGxvd2VkCiAgICAgICAgICAgICB2YWx1ZXMg
aW4gc3ViamVjdEFsdE5hbWU6VVJJIG9yIGEgc2V0IG9mIGFsbG93ZWQgWDUwOXYzCiAgICAgICAg
ICAgICBDZXJ0aWZpY2F0ZSBQb2xpY2llcykKCiAgICAgICAqICBUTFMgd2l0aCBYLjUwOSBjZXJ0
aWZpY2F0ZXMgdXNpbmcgY2VydGlmaWNhdGUgZmluZ2VycHJpbnRzOgogICAgICAgICAgSW1wbGVt
ZW50YXRpb25zIE1VU1QgYWxsb3cgdGhlIGNvbmZpZ3VyYXRpb24gb2YgYSBsaXN0IG9mCiAgICAg
ICAgICB0cnVzdGVkIGNlcnRpZmljYXRlcywgaWRlbnRpZmllZCB2aWEgZmluZ2VycHJpbnQgb2Yg
dGhlCiAgICAgICAgICBEaXN0aW5ndWlzaGVkIEVuY29kaW5nIFJ1bGVzIChERVIpIGVuY29kZWQg
Y2VydGlmaWNhdGUgb2N0ZXRzLgogICAgICAgICAgSW1wbGVtZW50YXRpb25zIE1VU1Qgc3VwcG9y
dCBTSEEtMjU2IGFzIGRlZmluZWQgYnkgW1NIU10gYXMKICAgICAgICAgIHRoZSBoYXNoIGFsZ29y
aXRobSBmb3IgdGhlIGZpbmdlcnByaW50LgoKICAgMy4gIFN0YXJ0IGV4Y2hhbmdpbmcgUENFUCBt
ZXNzYWdlcy4KCiAgICAgICAqICBPbmNlIHRoZSBUTFMgY29ubmVjdGlvbiBoYXMgYmVlbiBzdWNj
ZXNzZnVsbHkgZXN0YWJsaXNoZWQsIHRoZQogICAgICAgICAgUENFUCBzcGVha2VyIE1VU1Qgc3Rh
cnQgdGhlIE9wZW5XYWl0IHRpbWVyIFtSRkM1NDQwXSwgYWZ0ZXIKICAgICAgICAgIHRoZSBleHBp
cmF0aW9uIG9mIHdoaWNoLCBpZiBubyBPcGVuIG1lc3NhZ2UgaGFzIGJlZW4gcmVjZWl2ZWQsCiAg
ICAgICAgICBpdCBzZW5kcyBhIFBDRXJyIG1lc3NhZ2UgYW5kIHJlbGVhc2VzIHRoZSBUQ1AvVExT
IGNvbm5lY3Rpb24uCgogICBUbyBzdXBwb3J0IFRMUyByZS1uZWdvdGlhdGlvbiBib3RoIHBlZXJz
IE1VU1Qgc3VwcG9ydCB0aGUgbWVjaGFuaXNtCiAgIGRlc2NyaWJlZCBpbiBbUkZDNTc0Nl0uICBB
bnkgYXR0ZW1wdCB0byBpbml0aWF0ZSBhIFRMUyBoYW5kc2hha2UgdG8KICAgZXN0YWJsaXNoIG5l
dyBjcnlwdG9ncmFwaGljIHBhcmFtZXRlcnMgbm90IGFsaWduZWQgd2l0aCBbUkZDNTc0Nl0KICAg
U0hBTEwgYmUgY29uc2lkZXJlZCBhIFRMUyBuZWdvdGlhdGlvbiBmYWlsdXJlLgoKMy41LiAgUGVl
ciBJZGVudGl0eQoKICAgRGVwZW5kaW5nIG9uIHRoZSBwZWVyIGF1dGhlbnRpY2F0aW9uIG1ldGhv
ZCBpbiB1c2UsIFBDRVBTIHN1cHBvcnRzCiAgIGRpZmZlcmVudCBvcGVyYXRpb24gbW9kZXMgdG8g
ZXN0YWJsaXNoIHBlZXIncyBpZGVudGl0eSBhbmQgd2hldGhlciBpdAogICBpcyBlbnRpdGxlZCB0
byBwZXJmb3JtIHJlcXVlc3RzIG9yIGNhbiBiZSBjb25zaWRlcmVkIGF1dGhvcml0YXRpdmUgaW4K
ICAgaXRzIHJlcGxpZXMuICBQQ0VQUyBpbXBsZW1lbnRhdGlvbnMgU0hPVUxEIHByb3ZpZGUgbWVj
aGFuaXNtcyBmb3IKICAgYXNzb2NpYXRpbmcgcGVlciBpZGVudGl0aWVzIHdpdGggZGlmZmVyZW50
IGxldmVscyBvZiBhY2Nlc3MgYW5kL29yCiAgIGF1dGhvcml0YXRpdmVuZXNzLCBhbmQgdGhleSBN
VVNUIHByb3ZpZGUgYSBtZWNoYW5pc20gZm9yIGVzdGFibGlzaGluZwogICBhIGRlZmF1bHQgbGV2
ZWwgZm9yIHByb3Blcmx5IGlkZW50aWZpZWQgcGVlcnMuICBBbnkgY29ubmVjdGlvbgogICBlc3Rh
Ymxpc2hlZCB3aXRoIGEgcGVlciB0aGF0IGNhbm5vdCBiZSBwcm9wZXJseSBpZGVudGlmaWVkIFNI
QUxMIGJlCiAgIHRlcm1pbmF0ZWQgYmVmb3JlIGFueSBQQ0VQIGV4Y2hhbmdlIHRha2VzIHBsYWNl
LgoKICAgSW4gVExTLVguNTA5IG1vZGUgdXNpbmcgZmluZ2VycHJpbnRzLCBhIHBlZXIgaXMgdW5p
cXVlbHkgaWRlbnRpZmllZAogICBieSB0aGUgZmluZ2VycHJpbnQgb2YgdGhlIHByZXNlbnRlZCBj
ZXJ0aWZpY2F0ZS4KCiAgIFRoZXJlIGFyZSBudW1lcm91cyB0cnVzdCBtb2RlbHMgaW4gUEtJWCBl
bnZpcm9ubWVudHMsIGFuZCBpdCBpcwogICBiZXlvbmQgdGhlIHNjb3BlIG9mIHRoaXMgZG9jdW1l
bnQgdG8gZGVmaW5lIGhvdyBhIHBhcnRpY3VsYXIKICAgZGVwbG95bWVudCBkZXRlcm1pbmVzIHdo
ZXRoZXIgYSBwZWVyIGlzIHRydXN0d29ydGh5LiAgSW1wbGVtZW50YXRpb25zCiAgIHRoYXQgd2Fu
dCB0byBzdXBwb3J0IGEgd2lkZSB2YXJpZXR5IG9mIHRydXN0IG1vZGVscyBTSE9VTEQgZXhwb3Nl
IGFzCiAgIG1hbnkgZGV0YWlscyBvZiB0aGUgcHJlc2VudGVkIGNlcnRpZmljYXRlIHRvIHRoZSBh
ZG1pbmlzdHJhdG9yIGFzCgoKCkxvcGV6LCBldCBhbC4gICAgICAgICAgIEV4cGlyZXMgRmVicnVh
cnkgMSwgMjAxOCAgICAgICAgICAgICAgIFtQYWdlIDEzXQoMCkludGVybmV0LURyYWZ0ICAgICAg
ICAgIFNlY3VyZSBUcmFuc3BvcnQgZm9yIFBDRVAgICAgICAgICAgICAgIEp1bHkgMjAxNwoKCiAg
IHBvc3NpYmxlIHNvIHRoYXQgdGhlIHRydXN0IG1vZGVsIGNhbiBiZSBpbXBsZW1lbnRlZCBieSB0
aGUKICAgYWRtaW5pc3RyYXRvci4gIEF0IGxlYXN0IHRoZSBmb2xsb3dpbmcgcGFyYW1ldGVycyBv
ZiB0aGUgWC41MDkKICAgY2VydGlmaWNhdGUgU0hPVUxEIGJlIGV4cG9zZWQ6CgogICBvICBQZWVy
J3MgSVAgYWRkcmVzcwoKICAgbyAgUGVlcidzIGZ1bGx5IHF1YWxpZmllZCBkb21haW4gbmFtZSAo
RlFETikKCiAgIG8gIENlcnRpZmljYXRlIEZpbmdlcnByaW50CgogICBvICBJc3N1ZXIKCiAgIG8g
IFN1YmplY3QKCiAgIG8gIEFsbCBYNTA5djMgRXh0ZW5kZWQgS2V5IFVzYWdlCgogICBvICBBbGwg
WDUwOXYzIFN1YmplY3QgQWx0ZXJuYXRpdmUgTmFtZQoKICAgbyAgQWxsIFg1MDl2MyBDZXJ0aWZp
Y2F0ZSBQb2xpY2llcwoKICAgTm90ZSB0aGF0IHRoZSByZW1vdGUgSVAgYWRkcmVzcyB1c2VkIGZv
ciB0aGUgVENQIHNlc3Npb24KICAgZXN0YWJsaXNobWVudCBpcyBhbHNvIGV4cG9zZWQuCgogICBb
SS1ELmlldGYtcGNlLXN0YXRlZnVsLXN5bmMtb3B0aW1pemF0aW9uc10gc3BlY2lmeSBhIFNwZWFr
ZXIgRW50aXR5CiAgIElkZW50aWZpZXIgVExWIChTUEVBS0VSLUVOVElUWS1JRCksIGFzIGFuIG9w
dGlvbmFsIFRMViB0aGF0IE1BWSBiZQogICBpbmNsdWRlZCBpbiB0aGUgT1BFTiBPYmplY3QuICBJ
dCBjb250YWlucyBhIHVuaXF1ZSBpZGVudGlmaWVyIGZvciB0aGUKICAgbm9kZSB0aGF0IGRvZXMg
bm90IGNoYW5nZSBkdXJpbmcgdGhlIGxpZmV0aW1lIG9mIHRoZSBQQ0VQIHNwZWFrZXIuCiAgIEFu
IGltcGxlbWVudGF0aW9uIHdvdWxkIHRodXMgZXhwb3NlIHRoZSBzcGVha2VyIGVudGl0eSBpZGVu
dGlmaWVyIGFzCiAgIHBhcnQgb2YgdGhlIFg1MDl2MyBjZXJ0aWZpY2F0ZSwgc28gdGhhdCBhbiBp
bXBsZW1lbnRhdGlvbiBjb3VsZCB1c2UKICAgdGhpcyBpZGVudGlmaWVyIGZvciB0aGUgcGVlciBp
ZGVudGlmaWNhdGlvbiB0cnVzdCBtb2RlbC4KCiAgIEluIGFkZGl0aW9uLCBhIFBDQyBNQVkgYXBw
bHkgdGhlIHByb2NlZHVyZXMgZGVzY3JpYmVkIGluIFtSRkM2Njk4XQogICBETlMtQmFzZWQgQXV0
aGVudGljYXRpb24gb2YgTmFtZWQgRW50aXRpZXMgKERBTkUpIHRvIHZlcmlmeSBpdHMgcGVlcgog
ICBpZGVudGl0eSB3aGVuIHVzaW5nIEROUyBkaXNjb3ZlcnkuICBTZWUgc2VjdGlvbiBTZWN0aW9u
IDQuMSBmb3IKICAgZnVydGhlciBkZXRhaWxzLgoKMy42LiAgQ29ubmVjdGlvbiBFc3RhYmxpc2ht
ZW50IEZhaWx1cmUKCiAgIEluIGNhc2UgdGhlIGluaXRpYWwgVExTIG5lZ290aWF0aW9uIG9yIHRo
ZSBwZWVyIGlkZW50aXR5IGNoZWNrIGZhaWxzLAogICBhY2NvcmRpbmcgdG8gdGhlIHByb2NlZHVy
ZXMgbGlzdGVkIGluIHRoaXMgZG9jdW1lbnQsIHRoZSBwZWVyIE1VU1QKICAgZmlyc3Qgc2VuZCBh
IFBDRXJyIG1lc3NhZ2UgYXMgcGVyIFNlY3Rpb24gMy4yIGFuZCB0aGVuIHRlcm1pbmF0ZSB0aGUK
ICAgc2Vzc2lvbi4gIEl0IFNIT1VMRCBmb2xsb3cgdGhlIHByb2NlZHVyZSBsaXN0ZWQgaW4gW1JG
QzU0NDBdIHRvIHJldHJ5CiAgIHNlc3Npb24gc2V0dXAgYWxvbmcgd2l0aCBhbiBleHBvbmVudGlh
bCBiYWNrLW9mZiBzZXNzaW9uCiAgIGVzdGFibGlzaG1lbnQgcmV0cnkgcHJvY2VkdXJlLgoKCgoK
CgoKTG9wZXosIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBGZWJydWFyeSAxLCAyMDE4ICAgICAg
ICAgICAgICAgW1BhZ2UgMTRdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgU2VjdXJlIFRyYW5z
cG9ydCBmb3IgUENFUCAgICAgICAgICAgICAgSnVseSAyMDE3CgoKNC4gIERpc2NvdmVyeSBNZWNo
YW5pc21zCgogICBUaGlzIGRvY3VtZW50IGRvZXMgbm90IHNwZWNpZnkgYW55IGRpc2NvdmVyeSBt
ZWNoYW5pc20gZm9yIHN1cHBvcnQgb2YKICAgUENFUFMuICBPdGhlciBkb2N1bWVudHMsIFtJLUQu
d3UtcGNlLWRpc2NvdmVyeS1wY2Vwcy1zdXBwb3J0XSBhbmQKICAgW0ktRC53dS1wY2UtZG5zLXBj
ZS1kaXNjb3ZlcnldIGhhdmUgbWFkZSBwcm9wb3NhbHM6CgogICBvICBBIFBDRSBjYW4gYWR2ZXJ0
aXNlIGl0cyBjYXBhYmlsaXR5IHRvIHN1cHBvcnQgUENFUFMgdXNpbmcgdGhlCiAgICAgIElHUCdz
IGFkdmVydGlzZW1lbnQgbWVjaGFuaXNtIG9mIHRoZSBQQ0UgZGlzY292ZXJ5IGluZm9ybWF0aW9u
LgogICAgICBUaGUgUENFLUNBUC1GTEFHUyBzdWItVExWIGlzIGFuIG9wdGlvbmFsIHN1Yi1UTFYg
dXNlZCB0byBhZHZlcnRpc2UKICAgICAgUENFIGNhcGFiaWxpdGllcy4gIEl0IGlzIHByZXNlbnQg
d2l0aGluIHRoZSBQQ0UgRGlzY292ZXJ5IChQQ0VEKQogICAgICBzdWItVExWIGNhcnJpZWQgYnkg
T1NQRiBvciBJUy1JUy4gIFtSRkM1MDg4XSBhbmQgW1JGQzUwODldIHByb3ZpZGUKICAgICAgdGhl
IGRlc2NyaXB0aW9uIGFuZCBwcm9jZXNzaW5nIHJ1bGVzIGZvciB0aGlzIHN1Yi1UTFYgd2hlbiBj
YXJyaWVkCiAgICAgIHdpdGhpbiBPU1BGIGFuZCBJUy1JUywgcmVzcGVjdGl2ZWx5LiAgUENFIGNh
cGFiaWxpdHkgYml0cyBhcmUKICAgICAgZGVmaW5lZCBpbiBbUkZDNTA4OF0uICBBIG5ldyBjYXBh
YmlsaXR5IGZsYWcgYml0IGZvciB0aGUgUENFLUNBUC0KICAgICAgRkxBR1Mgc3ViLVRMViB0aGF0
IGNhbiBiZSBhbm5vdW5jZWQgYXMgYW4gYXR0cmlidXRlIHRvIGRpc3RyaWJ1dGUKICAgICAgUENF
UCBzZWN1cml0eSBzdXBwb3J0IGluZm9ybWF0aW9uIGlzIHByb3Bvc2VkIGluCiAgICAgIFtJLUQu
d3UtcGNlLWRpc2NvdmVyeS1wY2Vwcy1zdXBwb3J0XS4KCiAgIG8gIEEgUENFIGNhbiBhZHZlcnRp
c2UgaXRzIGNhcGFiaWxpdHkgdG8gc3VwcG9ydCBQQ0VQUyB1c2luZyB0aGUgRE5TCiAgICAgIFtJ
LUQud3UtcGNlLWRucy1wY2UtZGlzY292ZXJ5XSBieSBpZGVudGlmeWluZyB0aGUgc3VwcG9ydCBv
ZiBUTFMuCgo0LjEuICBEQU5FIEFwcGxpY2FiaWxpdHkKCiAgIERBTkUgW1JGQzY2OThdIGRlZmlu
ZXMgYSBzZWN1cmUgbWV0aG9kIHRvIGFzc29jaWF0ZSB0aGUgY2VydGlmaWNhdGUKICAgdGhhdCBp
cyBvYnRhaW5lZCBmcm9tIGEgVExTIHNlcnZlciB3aXRoIGEgZG9tYWluIG5hbWUgdXNpbmcgRE5T
LAogICBpLmUuLCB1c2luZyB0aGUgVExTQSBETlMgcmVzb3VyY2UgcmVjb3JkIChSUikgdG8gYXNz
b2NpYXRlIGEgVExTCiAgIHNlcnZlciBjZXJ0aWZpY2F0ZSBvciBwdWJsaWMga2V5IHdpdGggdGhl
IGRvbWFpbiBuYW1lIHdoZXJlIHRoZQogICByZWNvcmQgaXMgZm91bmQsIHRodXMgZm9ybWluZyBh
ICJUTFNBIGNlcnRpZmljYXRlIGFzc29jaWF0aW9uIi4gIFRoZQogICBETlMgaW5mb3JtYXRpb24g
bmVlZHMgdG8gYmUgcHJvdGVjdGVkIGJ5IEROUyBTZWN1cml0eSAoRE5TU0VDKS4gIEEKICAgUEND
IHdpbGxpbmcgdG8gYXBwbHkgREFORSB0byB2ZXJpZnkgc2VydmVyIGlkZW50aXR5IE1VU1QgY29u
Zm9ybSB0bwogICB0aGUgcnVsZXMgZGVmaW5lZCBpbiBzZWN0aW9uIDQgb2YgW1JGQzY2OThdLiAg
VGhlIHNlcnZlcidzIGRvbWFpbgogICBuYW1lIG11c3QgYmUgYXV0aG9yaXplZCBzZXBhcmF0ZWx5
LCBhcyBUTFNBIGRvZXMgbm90IHByb3ZpZGUgYW55CiAgIHVzZWZ1bCBhdXRob3JpemF0aW9uIGd1
YXJhbnRlZXMuCgo1LiAgQmFja3dhcmQgQ29tcGF0aWJpbGl0eQoKICAgVGhlIHByb2NlZHVyZXMg
ZGVzY3JpYmVkIGluIHRoaXMgZG9jdW1lbnQgZGVmaW5lIGEgc2VjdXJpdHkgY29udGFpbmVyCiAg
IGZvciB0aGUgdHJhbnNwb3J0IG9mIFBDRVAgcmVxdWVzdHMgYW5kIHJlcGxpZXMgY2FycmllZCBi
eSBhIFRMUwogICBjb25uZWN0aW9uIGluaXRpYXRlZCBieSBtZWFucyBvZiBhIHNwZWNpZmljIGV4
dGVuZGVkIG1lc3NhZ2UKICAgKFN0YXJ0VExTKSB0aGF0IGRvZXMgbm90IGludGVyZmVyZSB3aXRo
IFBDRVAgc3BlYWtlciBpbXBsZW1lbnRhdGlvbnMKICAgbm90IHN1cHBvcnRpbmcgaXQuCgogICBJ
ZiBhIFBDRVAgaW1wbGVtZW50YXRpb24gdGhhdCBkb2VzIG5vdCBzdXBwb3J0IFBDRVBTIHJlY2Vp
dmVzIGEKICAgU3RhcnRUTFMgbWVzc2FnZSwgaXQgd291bGQgYmVoYXZlIGFjY29yZGluZyB0byB0
aGUgZXhpc3RpbmcgZXJyb3IKICAgbWVjaGFuaXNtIG9mIFtSRkM1NDQwXS4gIE9uIHJlY2Vpdmlu
ZyB0aGUgZXJyb3IsIGJhc2VkIG9uIHRoZSBsb2NhbAogICBwb2xpY3ksIGEgcGVlciBjb3VsZCB0
cnkgdG8gZXN0YWJsaXNoaW5nIFBDRVAgc2Vzc2lvbiB3aXRob3V0IFRMUyBhcwogICBwZXIgdGhl
IHByb2NlZHVyZXMgZGVmaW5lZCBpbiBbUkZDNTQ0MF0uICBGb3Igc3VjY2Vzc2Z1bCBUTFMKCgoK
CkxvcGV6LCBldCBhbC4gICAgICAgICAgIEV4cGlyZXMgRmVicnVhcnkgMSwgMjAxOCAgICAgICAg
ICAgICAgIFtQYWdlIDE1XQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgIFNlY3VyZSBUcmFuc3Bv
cnQgZm9yIFBDRVAgICAgICAgICAgICAgIEp1bHkgMjAxNwoKCiAgIG9wZXJhdGlvbnMgd2l0aCBQ
Q0VQLCBib3RoIFBDRVAgcGVlcnMgaW4gdGhlIG5ldHdvcmsgd291bGQgbmVlZCB0byBiZQogICB1
cGdyYWRlZCB0byBzdXBwb3J0IHRoaXMgZG9jdW1lbnQuCgogICBBbiBleGlzdGluZyBQQ0VQIHNl
c3Npb24gY2Fubm90IGJlIHVwZ3JhZGVkIHRvIFBDRVBTLCB0aGUgc2Vzc2lvbgogICBuZWVkcyB0
byBiZSB0ZXJtaW5hdGVkIGFuZCByZWVzdGFibGlzaGVkIGFzIHBlciB0aGUgcHJvY2VkdXJlCiAg
IGRlc2NyaWJlZCBpbiB0aGlzIGRvY3VtZW50LiAgRHVyaW5nIHRoZSBpbmNyZW1lbnRhbCB1cGdy
YWRlLCB0aGUgUENFUAogICBzcGVha2VyIFNIT1VMRCBhbGxvdyBzZXNzaW9uIGVzdGFibGlzaG1l
bnQgd2l0aCBhbmQgd2l0aG91dCBUTFMuCiAgIE9uY2UgYm90aCBQQ0VQIHNwZWFrZXJzIGFyZSB1
cGdyYWRlZCB0byBzdXBwb3J0IFBDRVBTLCB0aGUgUENFUAogICBzZXNzaW9uIGlzIHJlLWVzdGFi
bGlzaGVkIHdpdGggVExTLCBvdGhlcndpc2UgUENFUCBzZXNzaW9uIHdpdGhvdXQKICAgVExTIGlz
IHNldHVwLiAgQSByZWR1bmRhbnQgUENFIE1BWSBhbHNvIGJlIHVzZWQgZHVyaW5nIHRoZQogICBp
bmNyZW1lbnRhbCBkZXBsb3ltZW50IHRvIHRha2Ugb3ZlciB0aGUgUENFIHVuZGVyZ29pbmcgdXBn
cmFkZS4gIE9uY2UKICAgdGhlIHVwZ3JhZGUgaXMgY29tcGxldGVkLCBzdXBwb3J0IGZvciB1bnNl
Y3VyZWQgdmVyc2lvbiBTSE9VTEQgYmUKICAgcmVtb3ZlZC4KCjYuICBJQU5BIENvbnNpZGVyYXRp
b25zCgo2LjEuICBOZXcgUENFUCBNZXNzYWdlCgogICBJQU5BIGlzIHJlcXVlc3RlZCB0byBhbGxv
Y2F0ZSBuZXcgbWVzc2FnZSB0eXBlcyB3aXRoaW4gdGhlICJQQ0VQCiAgIE1lc3NhZ2VzIiBzdWIt
cmVnaXN0cnkgb2YgdGhlIFBDRVAgTnVtYmVycyByZWdpc3RyeSwgYXMgZm9sbG93czoKCiAgICAg
IFZhbHVlICBEZXNjcmlwdGlvbiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgUmVmZXJlbmNl
CiAgICAgICBUQkExICBUaGUgU3RhcnQgVExTIE1lc3NhZ2UgKFN0YXJ0VExTKSAgICAgICAgVGhp
cyBkb2N1bWVudAoKNi4yLiAgTmV3IEVycm9yLVZhbHVlcwoKICAgSUFOQSBpcyByZXF1ZXN0ZWQg
dG8gYWxsb2NhdGUgbmV3IEVycm9yIFR5cGVzIGFuZCBFcnJvciBWYWx1ZXMgd2l0aGluCiAgIHRo
ZSAiIFBDRVAtRVJST1IgT2JqZWN0IEVycm9yIFR5cGVzIGFuZCBWYWx1ZXMiIHN1Yi1yZWdpc3Ry
eSBvZiB0aGUKICAgUENFUCBOdW1iZXJzIHJlZ2lzdHJ5LCBhcyBmb2xsb3dzOgoKCgoKCgoKCgoK
CgoKCgoKCgoKCgoKTG9wZXosIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBGZWJydWFyeSAxLCAy
MDE4ICAgICAgICAgICAgICAgW1BhZ2UgMTZdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgU2Vj
dXJlIFRyYW5zcG9ydCBmb3IgUENFUCAgICAgICAgICAgICAgSnVseSAyMDE3CgoKICAgRXJyb3It
CiAgIFR5cGUgICAgTWVhbmluZyAgICAgICAgICAgICAgIEVycm9yLXZhbHVlICAgICAgICAgICAg
IFJlZmVyZW5jZQoKICAgVEJBMiAgICBQQ0VQIFN0YXJ0VExTICAgICAgICAgMDpVbmFzc2lnbmVk
ICAgICAgICAgICAgVGhpcyBkb2N1bWVudAogICAgICAgICAgIGZhaWx1cmUgICAgICAgICAgICAg
ICAxOlJlY2VwdGlvbiBvZiAgICAgICAgICBUaGlzIGRvY3VtZW50CiAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIFN0YXJ0VExTIGFmdGVyCiAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIGFueSBQQ0VQIGV4Y2hhbmdlCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IDI6UmVjZXB0aW9uIG9mICAgICAgICAgIFRoaXMgZG9jdW1lbnQKICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgYW55IG90aGVyIG1lc3NhZ2UKICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgYXBhcnQgZnJvbSBTdGFydFRMUywKICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgT3BlbiBvciBQQ0VycgogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAzOkZh
aWx1cmUsIGNvbm5lY3Rpb24gICBUaGlzIGRvY3VtZW50CiAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgIHdpdGhvdXQgVExTIG5vdAogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICBwb3NzaWJsZQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICA0OkZhaWx1cmUsIGNv
bm5lY3Rpb24gICBUaGlzIGRvY3VtZW50CiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IHdpdGhvdXQgVExTIHBvc3NpYmxlCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIDU6
Tm8gU3RhcnRUTFMgbWVzc2FnZSAgIFRoaXMgZG9jdW1lbnQKICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgKG5vciBQQ0Vyci9PcGVuKQogICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICBiZWZvcmUgU3RhcnRUTFNXYWl0CiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IHRpbWVyIGV4cGlyeQoKNy4gIFNlY3VyaXR5IENvbnNpZGVyYXRpb25zCgogICBXaGlsZSB0aGUg
YXBwbGljYXRpb24gb2YgVExTIHNhdGlzZmllcyB0aGUgcmVxdWlyZW1lbnQgb24gcHJpdmFjeSBh
cwogICB3ZWxsIGFzIGZpbmUtZ3JhaW5lZCwgcG9saWN5LWJhc2VkIHBlZXIgYXV0aGVudGljYXRp
b24sIHRoZXJlIGFyZQogICBzZWN1cml0eSB0aHJlYXRzIHRoYXQgaXQgY2Fubm90IGFkZHJlc3Mu
ICBJdCBtYXkgYmUgYWR2aXNhYmxlIHRvCiAgIGFwcGx5IGFkZGl0aW9uYWwgcHJvdGVjdGlvbiBt
ZWFzdXJlcywgaW4gcGFydGljdWxhciBpbiB3aGF0IHJlbGF0ZXMKICAgdG8gYXR0YWNrcyBzcGVj
aWZpY2FsbHkgYWRkcmVzc2VkIHRvIGZvcmdpbmcgdGhlIFRDUCBjb25uZWN0aW9uCiAgIHVuZGVy
cGlubmluZyBUTFMsIGVzcGVjaWFsbHkgaW4gdGhlIGNhc2Ugb2YgbG9uZy1saXZlZCBjb25uZWN0
aW9ucy4KICAgT25lIG9mIHRoZXNlIG1lYXN1cmVzIGlzIHRoZSBhcHBsaWNhdGlvbiBvZiBUQ1At
QU8gKFRDUAogICBBdXRoZW50aWNhdGlvbiBPcHRpb24gW1JGQzU5MjVdKSwgd2hpY2ggaXMgZnVs
bHkgY29tcGF0aWJsZSB3aXRoIGFuZAogICBkZWVtZWQgYXMgY29tcGxlbWVudGFyeSB0byBUTFMu
ICBUaGUgbWVjaGFuaXNtcyB0byBjb25maWd1cmUgdGhlCiAgIHJlcXVpcmVtZW50cyB0byB1c2Ug
VENQLUFPIGFuZCBvdGhlciBsb3dlci1sYXllciBwcm90ZWN0aW9uIG1lYXN1cmVzCiAgIHdpdGgg
YSBwYXJ0aWN1bGFyIHBlZXIgYXJlIG91dHNpZGUgdGhlIHNjb3BlIG9mIHRoaXMgZG9jdW1lbnQu
CgogICBTaW5jZSBjb21wdXRhdGlvbmFsIHJlc291cmNlcyByZXF1aXJlZCBieSBUTFMgaGFuZHNo
YWtlIGFuZAogICBjaXBoZXJzdWl0ZSBhcmUgaGlnaGVyIHRoYW4gdW5lbmNyeXB0ZWQgVENQLCBj
bGllbnRzIGNvbm5lY3RpbmcgdG8gYQogICBQQ0VQUyBzZXJ2ZXIgY2FuIG1vcmUgZWFzaWx5IGNy
ZWF0ZSBoaWdoIGxvYWQgY29uZGl0aW9ucyBhbmQgYQogICBtYWxpY2lvdXMgY2xpZW50IG1pZ2h0
IGNyZWF0ZSBhIERlbmlhbC1vZi1TZXJ2aWNlIGF0dGFjayBtb3JlIGVhc2lseS4KCiAgIFNvbWUg
VExTIGNpcGhlcnN1aXRlcyBvbmx5IHByb3ZpZGUgaW50ZWdyaXR5IHZhbGlkYXRpb24gb2YgdGhl
aXIKICAgcGF5bG9hZCwgYW5kIHByb3ZpZGUgbm8gZW5jcnlwdGlvbi4gIFRoaXMgc3BlY2lmaWNh
dGlvbiBkb2VzIG5vdAogICBmb3JiaWQgdGhlIHVzZSBvZiBzdWNoIGNpcGhlcnN1aXRlcywgYnV0
IGFkbWluaXN0cmF0b3JzIG11c3Qgd2VpZ2h0CiAgIGNhcmVmdWxseSB0aGUgcmlzayBvZiByZWxl
dmFudCBpbnRlcm5hbCBkYXRhIGxlYWthZ2UgdGhhdCBjYW4gb2NjdXIKICAgaW4gc3VjaCBhIGNh
c2UsIGFzIGV4cGxpY2l0bHkgc3RhdGVkIGJ5IFtSRkM2OTUyXS4KCiAgIFdoZW4gdXNpbmcgY2Vy
dGlmaWNhdGUgZmluZ2VycHJpbnRzIHRvIGlkZW50aWZ5IFBDRVBTIHBlZXJzLCBhbnkgdHdvCiAg
IGNlcnRpZmljYXRlcyB0aGF0IHByb2R1Y2UgdGhlIHNhbWUgaGFzaCB2YWx1ZSB3aWxsIGJlIGNv
bnNpZGVyZWQgdGhlCgoKCkxvcGV6LCBldCBhbC4gICAgICAgICAgIEV4cGlyZXMgRmVicnVhcnkg
MSwgMjAxOCAgICAgICAgICAgICAgIFtQYWdlIDE3XQoMCkludGVybmV0LURyYWZ0ICAgICAgICAg
IFNlY3VyZSBUcmFuc3BvcnQgZm9yIFBDRVAgICAgICAgICAgICAgIEp1bHkgMjAxNwoKCiAgIHNh
bWUgcGVlci4gIFRoZXJlZm9yZSwgaXQgaXMgaW1wb3J0YW50IHRvIG1ha2Ugc3VyZSB0aGF0IHRo
ZSBoYXNoCiAgIGZ1bmN0aW9uIHVzZWQgaXMgY3J5cHRvZ3JhcGhpY2FsbHkgdW5jb21wcm9taXNl
ZCBzbyB0aGF0IGF0dGFja2VycwogICBhcmUgdmVyeSB1bmxpa2VseSB0byBiZSBhYmxlIHRvIHBy
b2R1Y2UgYSBoYXNoIGNvbGxpc2lvbiB3aXRoIGEKICAgY2VydGlmaWNhdGUgb2YgdGhlaXIgY2hv
aWNlLiAgVGhpcyBkb2N1bWVudCBtYW5kYXRlcyBzdXBwb3J0IGZvcgogICBTSEEtMjU2IGFzIGRl
ZmluZWQgYnkgW1NIU10sIGJ1dCBhIGxhdGVyIHJldmlzaW9uIG1heSBkZW1hbmQgc3VwcG9ydAog
ICBmb3Igc3Ryb25nZXIgZnVuY3Rpb25zIGlmIHN1aXRhYmxlIGF0dGFja3Mgb24gaXQgYXJlIGtu
b3duLgoKICAgVGhlIGd1aWRhbmNlIGdpdmVuIGluIFtSRkM3NTI1XSBTSE9VTEQgYmUgZm9sbG93
ZWQgdG8gYXZvaWQgYXR0YWNrcwogICBvbiBUTFMuCgo4LiAgTWFuYWdlYWJpbGl0eSBDb25zaWRl
cmF0aW9ucwoKICAgQWxsIG1hbmFnZWFiaWxpdHkgcmVxdWlyZW1lbnRzIGFuZCBjb25zaWRlcmF0
aW9ucyBsaXN0ZWQgaW4gW1JGQzU0NDBdCiAgIGFwcGx5IHRvIFBDRVAgcHJvdG9jb2wgZXh0ZW5z
aW9ucyBkZWZpbmVkIGluIHRoaXMgZG9jdW1lbnQuICBJbgogICBhZGRpdGlvbiwgcmVxdWlyZW1l
bnRzIGFuZCBjb25zaWRlcmF0aW9ucyBsaXN0ZWQgaW4gdGhpcyBzZWN0aW9uCiAgIGFwcGx5LgoK
OC4xLiAgQ29udHJvbCBvZiBGdW5jdGlvbiBhbmQgUG9saWN5CgogICBBIFBDRSBvciBQQ0MgaW1w
bGVtZW50YXRpb24gTVVTVCBhbGxvdyBjb25maWd1cmluZyB0aGUgUENFUCBzZWN1cml0eQogICB2
aWEgVExTIGNhcGFiaWxpdGllcyBhcyBkZXNjcmliZWQgaW4gdGhpcyBkb2N1bWVudC4KCiAgIEEg
UENFIG9yIFBDQyBpbXBsZW1lbnRhdGlvbiBzdXBwb3J0aW5nIFBDRVAgc2VjdXJpdHkgdmlhIFRM
UyBNVVNUCiAgIHN1cHBvcnQgZ2VuZXJhbCBUTFMgY29uZmlndXJhdGlvbiBhcyBwZXIgW1JGQzUy
NDZdLiAgQXQgbGVhc3QgdGhlCiAgIGNvbmZpZ3VyYXRpb24gb2Ygb25lIG9mIHRoZSB0cnVzdCBt
b2RlbHMgYW5kIGl0cyBjb3JyZXNwb25kaW5nCiAgIHBhcmFtZXRlcnMsIGFzIGRlc2NyaWJlZCBp
biBTZWN0aW9uIDMuNCBhbmQgU2VjdGlvbiAzLjUsIE1VU1QgYmUKICAgc3VwcG9ydGVkIGJ5IHRo
ZSBpbXBsZW1lbnRhdGlvbi4KCiAgIEEgUENFUCBpbXBsZW1lbnRhdGlvbiBTSE9VTEQgYWxsb3cg
Y29uZmlndXJpbmcgdGhlIFN0YXJ0VExTV2FpdCB0aW1lcgogICB2YWx1ZS4KCiAgIFBDRVBTIGlt
cGxlbWVudGF0aW9ucyBNQVkgcHJvdmlkZSBhbiBvcHRpb24gdG8gYWxsb3cgdGhlIG9wZXJhdG9y
IHRvCiAgIG1hbnVhbGx5IG92ZXJyaWRlIHN0cmljdCBUTFMgY29uZmlndXJhdGlvbiBhbmQgYWxs
b3cgdW5zZWN1cmUKICAgY29ubmVjdGlvbnMuICBFeGVjdXRpb24gb2YgdGhpcyBvdmVycmlkZSBT
SE9VTEQgdHJpZ2dlciBhIHdhcm5pbmcKICAgYWJvdXQgdGhlIHNlY3VyaXR5IGltcGxpY2F0aW9u
cyBvZiBwZXJtaXR0aW5nIHVuc2VjdXJlIGNvbm5lY3Rpb25zLgoKICAgRnVydGhlciwgdGhlIG9w
ZXJhdG9yIG5lZWRzIHRvIGRldmVsb3Agc3VpdGFibGUgc2VjdXJpdHkgcG9saWNpZXMKICAgYXJv
dW5kIFBDRVAgd2l0aGluIGhpcyBuZXR3b3JrLiAgRnVydGhlciB0aGUgUENFUCBwZWVycyBTSE9V
TEQKICAgcHJvdmlkZSB3YXlzIGZvciB0aGUgb3BlcmF0b3IgdG8gY29tcGxldGUgdGhlIGZvbGxv
d2luZyB0YXNrcyBpbgogICByZWdhcmRzIHRvIGEgUENFUCBzZXNzaW9uOgoKICAgbyAgRGV0ZXJt
aW5lIGlmIGEgc2Vzc2lvbiBpcyBwcm90ZWN0ZWQgdmlhIFBDRVBTLgoKICAgbyAgRGV0ZXJtaW5l
IHRoZSB2ZXJzaW9uIG9mIFRMUywgdGhlIG1lY2hhbmlzbSB1c2VkIGZvcgogICAgICBhdXRoZW50
aWNhdGlvbiwgYW5kIHRoZSBjaXBoZXJzdWl0ZSBpbiB1c2UuCgogICBvICBEZXRlcm1pbmUgaWYg
dGhlIGNlcnRpZmljYXRlIGNvdWxkIG5vdCBiZSB2ZXJpZmllZCwgYW5kIHRoZSByZWFzb24KICAg
ICAgZm9yIHRoaXMgY2lyY3Vtc3RhbmNlLgoKCgpMb3BleiwgZXQgYWwuICAgICAgICAgICBFeHBp
cmVzIEZlYnJ1YXJ5IDEsIDIwMTggICAgICAgICAgICAgICBbUGFnZSAxOF0KDApJbnRlcm5ldC1E
cmFmdCAgICAgICAgICBTZWN1cmUgVHJhbnNwb3J0IGZvciBQQ0VQICAgICAgICAgICAgICBKdWx5
IDIwMTcKCgogICBvICBJbnNwZWN0IHRoZSBjZXJ0aWZpY2F0ZSBvZmZlcmVkIGJ5IHRoZSBQQ0VQ
IHBlZXIuCgogICBvICBCZSB3YXJuZWQgaWYgU3RhcnRUTFMgcHJvY2VkdXJlIGZhaWxzIGZvciB0
aGUgUENFUCBwZWVycywgdGhhdCBhcmUKICAgICAga25vd24gdG8gc3VwcG9ydCBQQ0VQUywgdmlh
IGNvbmZpZ3VyYXRpb25zIG9yIGNhcGFiaWxpdHkKICAgICAgYWR2ZXJ0aXNlbWVudHMuCgo4LjIu
ICBJbmZvcm1hdGlvbiBhbmQgRGF0YSBNb2RlbHMKCiAgIFRoZSBQQ0VQIE1JQiBtb2R1bGUgaXMg
ZGVmaW5lZCBpbiBbUkZDNzQyMF0uICBUaGUgTUlCIG1vZHVsZSBjb3VsZCBiZQogICBleHRlbmRl
ZCB0byBpbmNsdWRlIHRoZSBhYmlsaXR5IHRvIHZpZXcgdGhlIFBDRVBTIGNhcGFiaWxpdHksIFRM
UwogICByZWxhdGVkIGluZm9ybWF0aW9uIGFzIHdlbGwgYXMgVExTIHN0YXR1cyBmb3IgZWFjaCBQ
Q0VQIHBlZXIuCgogICBBbiBpbXBsZW1lbnRhdGlvbiBTSE9VTEQgYWxzbyBhbGxvdyB0aGUgb3Bl
cmF0b3IgdG8gY29uZmlndXJlIHRoZQogICBQQ0VQUyBjYXBhYmlsaXR5IGFuZCB2YXJpb3VzIFRM
UyByZWxhdGVkIHBhcmFtZXRlcnMgaW4gYWRkaXRpb24gdG8KICAgYWJpbGl0eSB0byB2aWV3IHRo
ZSBjdXJyZW50IFRMUyBzdGF0dXMgZm9yIGEgUENFUCBzZXNzaW9uLiAgVG8gc2VydmUKICAgdGhp
cyBwdXJwb3NlLCB0aGUgUENFUCBZQU5HIG1vZHVsZSBbSS1ELmlldGYtcGNlLXBjZXAteWFuZ10g
aXMKICAgZXh0ZW5kZWQgdG8gaW5jbHVkZSBUTFMgcmVsYXRlZCBjb25maWd1cmF0aW9uIGFuZCBz
dGF0ZSBpbmZvcm1hdGlvbi4KCjguMy4gIExpdmVuZXNzIERldGVjdGlvbiBhbmQgTW9uaXRvcmlu
ZwoKICAgTWVjaGFuaXNtcyBkZWZpbmVkIGluIHRoaXMgZG9jdW1lbnQgZG8gbm90IGltcGx5IGFu
eSBuZXcgbGl2ZW5lc3MKICAgZGV0ZWN0aW9uIGFuZCBtb25pdG9yaW5nIHJlcXVpcmVtZW50cyBp
biBhZGRpdGlvbiB0byB0aG9zZSBhbHJlYWR5CiAgIGxpc3RlZCBpbiBbUkZDNTQ0MF0gYW5kIFtS
RkM1MjQ2XS4KCjguNC4gIFZlcmlmeWluZyBDb3JyZWN0IE9wZXJhdGlvbnMKCiAgIEEgUENFUFMg
aW1wbGVtZW50YXRpb24gU0hPVUxEIGxvZyBlcnJvciBldmVudHMgYW5kIHByb3ZpZGUgUENFUFMK
ICAgZmFpbHVyZSBzdGF0aXN0aWNzIHdpdGggcmVhc29ucy4KCjguNS4gIFJlcXVpcmVtZW50cyBv
biBPdGhlciBQcm90b2NvbHMKCiAgIE1lY2hhbmlzbXMgZGVmaW5lZCBpbiB0aGlzIGRvY3VtZW50
IGRvIG5vdCBpbXBseSBhbnkgbmV3IHJlcXVpcmVtZW50cwogICBvbiBvdGhlciBwcm90b2NvbHMu
ICBOb3RlIHRoYXQsIFNlY3Rpb24gNCBsaXN0IHBvc3NpYmxlIGRpc2NvdmVyeQogICBtZWNoYW5p
c20gZm9yIHN1cHBvcnQgb2YgUENFUFMuCgo4LjYuICBJbXBhY3Qgb24gTmV0d29yayBPcGVyYXRp
b24KCiAgIE1lY2hhbmlzbXMgZGVmaW5lZCBpbiB0aGlzIGRvY3VtZW50IGRvIG5vdCBoYXZlIGFu
eSBzaWduaWZpY2FudAogICBpbXBhY3Qgb24gbmV0d29yayBvcGVyYXRpb25zIGluIGFkZGl0aW9u
IHRvIHRob3NlIGFscmVhZHkgbGlzdGVkIGluCiAgIFtSRkM1NDQwXSwgYW5kIHRoZSBwb2xpY3kg
YW5kIG1hbmFnZW1lbnQgaW1wbGljYXRpb25zIGRpc2N1c3NlZAogICBhYm92ZS4KCjkuICBBY2tu
b3dsZWRnZW1lbnRzCgogICBUaGlzIHNwZWNpZmljYXRpb24gcmVsaWVzIG9uIHRoZSBhbmFseXNp
cyBhbmQgcHJvZmlsaW5nIG9mIFRMUwogICBpbmNsdWRlZCBpbiBbUkZDNjYxNF0gYW5kIHRoZSBw
cm9jZWR1cmVzIGRlc2NyaWJlZCBmb3IgdGhlIFNUQVJUVExTCiAgIGNvbW1hbmQgaW4gW1JGQzQ1
MTNdLgoKCgoKTG9wZXosIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBGZWJydWFyeSAxLCAyMDE4
ICAgICAgICAgICAgICAgW1BhZ2UgMTldCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgU2VjdXJl
IFRyYW5zcG9ydCBmb3IgUENFUCAgICAgICAgICAgICAgSnVseSAyMDE3CgoKICAgV2Ugd291bGQg
bGlrZSB0byB0aGFuayBKb2UgVG91Y2ggZm9yIGhpcyBzdWdnZXN0aW9ucyBhbmQgc3VwcG9ydAog
ICByZWdhcmRpbmcgdGhlIFRMUyBzdGFydCBtZWNoYW5pc21zLgoKICAgVGhhbmtzIHRvIERhbmll
bCBLaW5nIGZvciByZW1pbmRpbmcgdGhlIGF1dGhvcnMgYWJvdXQgbWFuYWdlYWJpbGl0eQogICBj
b25zaWRlcmF0aW9ucy4KCiAgIFRoYW5rcyB0byBDeXJpbCBNYXJnYXJpYSBmb3Igc2hlcGhlcmRp
bmcgdGhpcyBkb2N1bWVudC4KCiAgIFRoYW5rcyB0byBEYXZpZCBNYW5kZWxiZXJnIGZvciBlYXJs
eSBTRUNESVIgcmV2aWV3IGNvbW1lbnRzIGFzIHdlbGwKICAgYXMgcmUtcmV2aWV3aW5nIGR1cmlu
ZyBJRVRGIGxhc3QgY2FsbC4KCiAgIFRoYW5rcyB0byBEYW4gRnJvc3QgZm9yIHRoZSBSVEdESVIg
cmV2aWV3IGFuZCBjb21tZW50cy4KCiAgIFRoYW5rcyB0byBEYWxlIFdvcmxleSBmb3IgdGhlIEdl
bi1BUlQgcmV2aWV3IGFuZCBjb21tZW50cy4KCiAgIEFsc28gdGhhbmtzIHRvIFRpYW5yYW4gWmhv
dSBmb3IgT1BTRElSIHJldmlldy4KCiAgIFRoYW5rcyB0byBEZWJvcmFoIEJydW5nYXJkIGZvciBi
ZWluZyB0aGUgcmVzcG9uc2libGUgQUQgYW5kIGd1aWRpbmcKICAgdGhlIGF1dGhvcnMgYXMgbmVl
ZGVkLgoKMTAuICBSZWZlcmVuY2VzCgoxMC4xLiAgTm9ybWF0aXZlIFJlZmVyZW5jZXMKCiAgIFtS
RkMyMTE5XSAgQnJhZG5lciwgUy4sICJLZXkgd29yZHMgZm9yIHVzZSBpbiBSRkNzIHRvIEluZGlj
YXRlCiAgICAgICAgICAgICAgUmVxdWlyZW1lbnQgTGV2ZWxzIiwgQkNQIDE0LCBSRkMgMjExOSwK
ICAgICAgICAgICAgICBET0kgMTAuMTc0ODcvUkZDMjExOSwgTWFyY2ggMTk5NywKICAgICAgICAg
ICAgICA8aHR0cDovL3d3dy5yZmMtZWRpdG9yLm9yZy9pbmZvL3JmYzIxMTk+LgoKICAgW1JGQzUy
NDZdICBEaWVya3MsIFQuIGFuZCBFLiBSZXNjb3JsYSwgIlRoZSBUcmFuc3BvcnQgTGF5ZXIgU2Vj
dXJpdHkKICAgICAgICAgICAgICAoVExTKSBQcm90b2NvbCBWZXJzaW9uIDEuMiIsIFJGQyA1MjQ2
LAogICAgICAgICAgICAgIERPSSAxMC4xNzQ4Ny9SRkM1MjQ2LCBBdWd1c3QgMjAwOCwKICAgICAg
ICAgICAgICA8aHR0cDovL3d3dy5yZmMtZWRpdG9yLm9yZy9pbmZvL3JmYzUyNDY+LgoKICAgW1JG
QzUyODBdICBDb29wZXIsIEQuLCBTYW50ZXNzb24sIFMuLCBGYXJyZWxsLCBTLiwgQm9leWVuLCBT
LiwKICAgICAgICAgICAgICBIb3VzbGV5LCBSLiwgYW5kIFcuIFBvbGssICJJbnRlcm5ldCBYLjUw
OSBQdWJsaWMgS2V5CiAgICAgICAgICAgICAgSW5mcmFzdHJ1Y3R1cmUgQ2VydGlmaWNhdGUgYW5k
IENlcnRpZmljYXRlIFJldm9jYXRpb24gTGlzdAogICAgICAgICAgICAgIChDUkwpIFByb2ZpbGUi
LCBSRkMgNTI4MCwgRE9JIDEwLjE3NDg3L1JGQzUyODAsIE1heSAyMDA4LAogICAgICAgICAgICAg
IDxodHRwOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2luZm8vcmZjNTI4MD4uCgogICBbUkZDNTI4OF0g
IFNhbG93ZXksIEouLCBDaG91ZGh1cnksIEEuLCBhbmQgRC4gTWNHcmV3LCAiQUVTIEdhbG9pcwog
ICAgICAgICAgICAgIENvdW50ZXIgTW9kZSAoR0NNKSBDaXBoZXIgU3VpdGVzIGZvciBUTFMiLCBS
RkMgNTI4OCwKICAgICAgICAgICAgICBET0kgMTAuMTc0ODcvUkZDNTI4OCwgQXVndXN0IDIwMDgs
CiAgICAgICAgICAgICAgPGh0dHA6Ly93d3cucmZjLWVkaXRvci5vcmcvaW5mby9yZmM1Mjg4Pi4K
CgoKCgoKCkxvcGV6LCBldCBhbC4gICAgICAgICAgIEV4cGlyZXMgRmVicnVhcnkgMSwgMjAxOCAg
ICAgICAgICAgICAgIFtQYWdlIDIwXQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgIFNlY3VyZSBU
cmFuc3BvcnQgZm9yIFBDRVAgICAgICAgICAgICAgIEp1bHkgMjAxNwoKCiAgIFtSRkM1NDQwXSAg
VmFzc2V1ciwgSlAuLCBFZC4gYW5kIEpMLiBMZSBSb3V4LCBFZC4sICJQYXRoIENvbXB1dGF0aW9u
CiAgICAgICAgICAgICAgRWxlbWVudCAoUENFKSBDb21tdW5pY2F0aW9uIFByb3RvY29sIChQQ0VQ
KSIsIFJGQyA1NDQwLAogICAgICAgICAgICAgIERPSSAxMC4xNzQ4Ny9SRkM1NDQwLCBNYXJjaCAy
MDA5LAogICAgICAgICAgICAgIDxodHRwOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2luZm8vcmZjNTQ0
MD4uCgogICBbUkZDNTc0Nl0gIFJlc2NvcmxhLCBFLiwgUmF5LCBNLiwgRGlzcGVuc2EsIFMuLCBh
bmQgTi4gT3Nrb3YsCiAgICAgICAgICAgICAgIlRyYW5zcG9ydCBMYXllciBTZWN1cml0eSAoVExT
KSBSZW5lZ290aWF0aW9uIEluZGljYXRpb24KICAgICAgICAgICAgICBFeHRlbnNpb24iLCBSRkMg
NTc0NiwgRE9JIDEwLjE3NDg3L1JGQzU3NDYsIEZlYnJ1YXJ5IDIwMTAsCiAgICAgICAgICAgICAg
PGh0dHA6Ly93d3cucmZjLWVkaXRvci5vcmcvaW5mby9yZmM1NzQ2Pi4KCiAgIFtSRkM2MDY2XSAg
RWFzdGxha2UgM3JkLCBELiwgIlRyYW5zcG9ydCBMYXllciBTZWN1cml0eSAoVExTKQogICAgICAg
ICAgICAgIEV4dGVuc2lvbnM6IEV4dGVuc2lvbiBEZWZpbml0aW9ucyIsIFJGQyA2MDY2LAogICAg
ICAgICAgICAgIERPSSAxMC4xNzQ4Ny9SRkM2MDY2LCBKYW51YXJ5IDIwMTEsCiAgICAgICAgICAg
ICAgPGh0dHA6Ly93d3cucmZjLWVkaXRvci5vcmcvaW5mby9yZmM2MDY2Pi4KCiAgIFtSRkM2Njk4
XSAgSG9mZm1hbiwgUC4gYW5kIEouIFNjaGx5dGVyLCAiVGhlIEROUy1CYXNlZCBBdXRoZW50aWNh
dGlvbgogICAgICAgICAgICAgIG9mIE5hbWVkIEVudGl0aWVzIChEQU5FKSBUcmFuc3BvcnQgTGF5
ZXIgU2VjdXJpdHkgKFRMUykKICAgICAgICAgICAgICBQcm90b2NvbDogVExTQSIsIFJGQyA2Njk4
LCBET0kgMTAuMTc0ODcvUkZDNjY5OCwgQXVndXN0CiAgICAgICAgICAgICAgMjAxMiwgPGh0dHA6
Ly93d3cucmZjLWVkaXRvci5vcmcvaW5mby9yZmM2Njk4Pi4KCiAgIFtSRkM3NTI1XSAgU2hlZmZl
ciwgWS4sIEhvbHosIFIuLCBhbmQgUC4gU2FpbnQtQW5kcmUsCiAgICAgICAgICAgICAgIlJlY29t
bWVuZGF0aW9ucyBmb3IgU2VjdXJlIFVzZSBvZiBUcmFuc3BvcnQgTGF5ZXIKICAgICAgICAgICAg
ICBTZWN1cml0eSAoVExTKSBhbmQgRGF0YWdyYW0gVHJhbnNwb3J0IExheWVyIFNlY3VyaXR5CiAg
ICAgICAgICAgICAgKERUTFMpIiwgQkNQIDE5NSwgUkZDIDc1MjUsIERPSSAxMC4xNzQ4Ny9SRkM3
NTI1LCBNYXkKICAgICAgICAgICAgICAyMDE1LCA8aHR0cDovL3d3dy5yZmMtZWRpdG9yLm9yZy9p
bmZvL3JmYzc1MjU+LgoKICAgW1NIU10gICAgICBOYXRpb25hbCBJbnN0aXR1dGUgb2YgU3RhbmRh
cmRzIGFuZCBUZWNobm9sb2d5LCAiU2VjdXJlCiAgICAgICAgICAgICAgSGFzaCBTdGFuZGFyZCAo
U0hTKSwgRklQUyBQVUIgMTgwLTQiLAogICAgICAgICAgICAgIERPSSAxMC42MDI4L05JU1QuRklQ
Uy4xODAtNCwgQXVndXN0IDIwMTUsCiAgICAgICAgICAgICAgPGh0dHA6Ly9udmxwdWJzLm5pc3Qu
Z292L25pc3RwdWJzL0ZJUFMvCiAgICAgICAgICAgICAgTklTVC5GSVBTLjE4MC00LnBkZj4uCgox
MC4yLiAgSW5mb3JtYXRpdmUgUmVmZXJlbmNlcwoKICAgW1JGQzQ1MTNdICBIYXJyaXNvbiwgUi4s
IEVkLiwgIkxpZ2h0d2VpZ2h0IERpcmVjdG9yeSBBY2Nlc3MgUHJvdG9jb2wKICAgICAgICAgICAg
ICAoTERBUCk6IEF1dGhlbnRpY2F0aW9uIE1ldGhvZHMgYW5kIFNlY3VyaXR5IE1lY2hhbmlzbXMi
LAogICAgICAgICAgICAgIFJGQyA0NTEzLCBET0kgMTAuMTc0ODcvUkZDNDUxMywgSnVuZSAyMDA2
LAogICAgICAgICAgICAgIDxodHRwOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2luZm8vcmZjNDUxMz4u
CgogICBbUkZDNTA4OF0gIExlIFJvdXgsIEpMLiwgRWQuLCBWYXNzZXVyLCBKUC4sIEVkLiwgSWtl
amlyaSwgWS4sIGFuZCBSLgogICAgICAgICAgICAgIFpoYW5nLCAiT1NQRiBQcm90b2NvbCBFeHRl
bnNpb25zIGZvciBQYXRoIENvbXB1dGF0aW9uCiAgICAgICAgICAgICAgRWxlbWVudCAoUENFKSBE
aXNjb3ZlcnkiLCBSRkMgNTA4OCwgRE9JIDEwLjE3NDg3L1JGQzUwODgsCiAgICAgICAgICAgICAg
SmFudWFyeSAyMDA4LCA8aHR0cDovL3d3dy5yZmMtZWRpdG9yLm9yZy9pbmZvL3JmYzUwODg+LgoK
ICAgW1JGQzUwODldICBMZSBSb3V4LCBKTC4sIEVkLiwgVmFzc2V1ciwgSlAuLCBFZC4sIElrZWpp
cmksIFkuLCBhbmQgUi4KICAgICAgICAgICAgICBaaGFuZywgIklTLUlTIFByb3RvY29sIEV4dGVu
c2lvbnMgZm9yIFBhdGggQ29tcHV0YXRpb24KICAgICAgICAgICAgICBFbGVtZW50IChQQ0UpIERp
c2NvdmVyeSIsIFJGQyA1MDg5LCBET0kgMTAuMTc0ODcvUkZDNTA4OSwKICAgICAgICAgICAgICBK
YW51YXJ5IDIwMDgsIDxodHRwOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2luZm8vcmZjNTA4OT4uCgoK
CkxvcGV6LCBldCBhbC4gICAgICAgICAgIEV4cGlyZXMgRmVicnVhcnkgMSwgMjAxOCAgICAgICAg
ICAgICAgIFtQYWdlIDIxXQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgIFNlY3VyZSBUcmFuc3Bv
cnQgZm9yIFBDRVAgICAgICAgICAgICAgIEp1bHkgMjAxNwoKCiAgIFtSRkM1OTI1XSAgVG91Y2gs
IEouLCBNYW5raW4sIEEuLCBhbmQgUi4gQm9uaWNhLCAiVGhlIFRDUAogICAgICAgICAgICAgIEF1
dGhlbnRpY2F0aW9uIE9wdGlvbiIsIFJGQyA1OTI1LCBET0kgMTAuMTc0ODcvUkZDNTkyNSwKICAg
ICAgICAgICAgICBKdW5lIDIwMTAsIDxodHRwOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2luZm8vcmZj
NTkyNT4uCgogICBbUkZDNjYxNF0gIFdpbnRlciwgUy4sIE1jQ2F1bGV5LCBNLiwgVmVuYWFzLCBT
LiwgYW5kIEsuIFdpZXJlbmdhLAogICAgICAgICAgICAgICJUcmFuc3BvcnQgTGF5ZXIgU2VjdXJp
dHkgKFRMUykgRW5jcnlwdGlvbiBmb3IgUkFESVVTIiwKICAgICAgICAgICAgICBSRkMgNjYxNCwg
RE9JIDEwLjE3NDg3L1JGQzY2MTQsIE1heSAyMDEyLAogICAgICAgICAgICAgIDxodHRwOi8vd3d3
LnJmYy1lZGl0b3Iub3JnL2luZm8vcmZjNjYxND4uCgogICBbUkZDNjk1Ml0gIEpldGhhbmFuZGFu
aSwgTS4sIFBhdGVsLCBLLiwgYW5kIEwuIFpoZW5nLCAiQW5hbHlzaXMgb2YKICAgICAgICAgICAg
ICBCR1AsIExEUCwgUENFUCwgYW5kIE1TRFAgSXNzdWVzIEFjY29yZGluZyB0byB0aGUgS2V5aW5n
CiAgICAgICAgICAgICAgYW5kIEF1dGhlbnRpY2F0aW9uIGZvciBSb3V0aW5nIFByb3RvY29scyAo
S0FSUCkgRGVzaWduCiAgICAgICAgICAgICAgR3VpZGUiLCBSRkMgNjk1MiwgRE9JIDEwLjE3NDg3
L1JGQzY5NTIsIE1heSAyMDEzLAogICAgICAgICAgICAgIDxodHRwOi8vd3d3LnJmYy1lZGl0b3Iu
b3JnL2luZm8vcmZjNjk1Mj4uCgogICBbUkZDNzQyMF0gIEtvdXNoaWssIEEuLCBTdGVwaGFuLCBF
LiwgWmhhbywgUS4sIEtpbmcsIEQuLCBhbmQgSi4KICAgICAgICAgICAgICBIYXJkd2ljaywgIlBh
dGggQ29tcHV0YXRpb24gRWxlbWVudCBDb21tdW5pY2F0aW9uIFByb3RvY29sCiAgICAgICAgICAg
ICAgKFBDRVApIE1hbmFnZW1lbnQgSW5mb3JtYXRpb24gQmFzZSAoTUlCKSBNb2R1bGUiLAogICAg
ICAgICAgICAgIFJGQyA3NDIwLCBET0kgMTAuMTc0ODcvUkZDNzQyMCwgRGVjZW1iZXIgMjAxNCwK
ICAgICAgICAgICAgICA8aHR0cDovL3d3dy5yZmMtZWRpdG9yLm9yZy9pbmZvL3JmYzc0MjA+LgoK
ICAgW0ktRC5pZXRmLXBjZS1zdGF0ZWZ1bC1zeW5jLW9wdGltaXphdGlvbnNdCiAgICAgICAgICAg
ICAgQ3JhYmJlLCBFLiwgTWluZWksIEkuLCBNZWR2ZWQsIEouLCBWYXJnYSwgUi4sIFpoYW5nLCBY
LiwKICAgICAgICAgICAgICBhbmQgRC4gRGhvZHksICJPcHRpbWl6YXRpb25zIG9mIExhYmVsIFN3
aXRjaGVkIFBhdGggU3RhdGUKICAgICAgICAgICAgICBTeW5jaHJvbml6YXRpb24gUHJvY2VkdXJl
cyBmb3IgYSBTdGF0ZWZ1bCBQQ0UiLCBkcmFmdC0KICAgICAgICAgICAgICBpZXRmLXBjZS1zdGF0
ZWZ1bC1zeW5jLW9wdGltaXphdGlvbnMtMTAgKHdvcmsgaW4KICAgICAgICAgICAgICBwcm9ncmVz
cyksIE1hcmNoIDIwMTcuCgogICBbSS1ELmlldGYtcGNlLXBjZXAteWFuZ10KICAgICAgICAgICAg
ICBEaG9keSwgRC4sIEhhcmR3aWNrLCBKLiwgQmVlcmFtLCBWLiwgYW5kIGouCiAgICAgICAgICAg
ICAgamVmZnRhbnRAZ21haWwuY29tLCAiQSBZQU5HIERhdGEgTW9kZWwgZm9yIFBhdGgKICAgICAg
ICAgICAgICBDb21wdXRhdGlvbiBFbGVtZW50IENvbW11bmljYXRpb25zIFByb3RvY29sIChQQ0VQ
KSIsCiAgICAgICAgICAgICAgZHJhZnQtaWV0Zi1wY2UtcGNlcC15YW5nLTA1ICh3b3JrIGluIHBy
b2dyZXNzKSwgSnVuZSAyMDE3LgoKICAgW0ktRC53dS1wY2UtZG5zLXBjZS1kaXNjb3ZlcnldCiAg
ICAgICAgICAgICAgV3UsIFEuLCBEaG9keSwgRC4sIEtpbmcsIEQuLCBMb3BleiwgRC4sIGFuZCBK
LiBUYW50c3VyYSwKICAgICAgICAgICAgICAiUGF0aCBDb21wdXRhdGlvbiBFbGVtZW50IChQQ0Up
IERpc2NvdmVyeSB1c2luZyBEb21haW4KICAgICAgICAgICAgICBOYW1lIFN5c3RlbShETlMpIiwg
ZHJhZnQtd3UtcGNlLWRucy1wY2UtZGlzY292ZXJ5LTEwICh3b3JrCiAgICAgICAgICAgICAgaW4g
cHJvZ3Jlc3MpLCBNYXJjaCAyMDE3LgoKICAgW0ktRC53dS1wY2UtZGlzY292ZXJ5LXBjZXBzLXN1
cHBvcnRdCiAgICAgICAgICAgICAgTG9wZXosIEQuLCBXdSwgUS4sIERob2R5LCBELiwgYW5kIEQu
IEtpbmcsICJJR1AgZXh0ZW5zaW9uCiAgICAgICAgICAgICAgZm9yIFBDRVAgc2VjdXJpdHkgY2Fw
YWJpbGl0eSBzdXBwb3J0IGluIHRoZSBQQ0UKICAgICAgICAgICAgICBkaXNjb3ZlcnkiLCBkcmFm
dC13dS1wY2UtZGlzY292ZXJ5LXBjZXBzLXN1cHBvcnQtMDcgKHdvcmsKICAgICAgICAgICAgICBp
biBwcm9ncmVzcyksIE1hcmNoIDIwMTcuCgoKCgoKCkxvcGV6LCBldCBhbC4gICAgICAgICAgIEV4
cGlyZXMgRmVicnVhcnkgMSwgMjAxOCAgICAgICAgICAgICAgIFtQYWdlIDIyXQoMCkludGVybmV0
LURyYWZ0ICAgICAgICAgIFNlY3VyZSBUcmFuc3BvcnQgZm9yIFBDRVAgICAgICAgICAgICAgIEp1
bHkgMjAxNwoKCkF1dGhvcnMnIEFkZHJlc3NlcwoKICAgRGllZ28gUi4gTG9wZXoKICAgVGVsZWZv
bmljYSBJK0QKICAgRG9uIFJhbW9uIGRlIGxhIENydXosIDgyCiAgIE1hZHJpZCAgMjgwMDYKICAg
U3BhaW4KCiAgIFBob25lOiArMzQgOTEzIDEyOSAwNDEKICAgRU1haWw6IGRpZWdvLnIubG9wZXpA
dGVsZWZvbmljYS5jb20KCgogICBPc2NhciBHb256YWxleiBkZSBEaW9zCiAgIFRlbGVmb25pY2Eg
SStECiAgIERvbiBSYW1vbiBkZSBsYSBDcnV6LCA4MgogICBNYWRyaWQgIDI4MDA2CiAgIFNwYWlu
CgogICBQaG9uZTogKzM0IDkxMyAxMjkgMDQxCiAgIEVNYWlsOiBvc2Nhci5nb256YWxlemRlZGlv
c0B0ZWxlZm9uaWNhLmNvbQoKCiAgIFFpbiBXdQogICBIdWF3ZWkKICAgMTAxIFNvZnR3YXJlIEF2
ZW51ZSwgWXVodWEgRGlzdHJpY3QKICAgTmFuamluZywgSmlhbmdzdSAgMjEwMDEyCiAgIENoaW5h
CgogICBFTWFpbDogc3Vuc2Vhd3FAaHVhd2VpLmNvbQoKCiAgIERocnV2IERob2R5CiAgIEh1YXdl
aQogICBEaXZ5YXNocmVlIFRlY2hubyBQYXJrLCBXaGl0ZWZpZWxkCiAgIEJhbmdhbG9yZSwgS0Eg
IDU2MDA2NgogICBJbmRpYQoKICAgRU1haWw6IGRocnV2LmlldGZAZ21haWwuY29tCgoKCgoKCgoK
CgoKCgpMb3BleiwgZXQgYWwuICAgICAgICAgICBFeHBpcmVzIEZlYnJ1YXJ5IDEsIDIwMTggICAg
ICAgICAgICAgICBbUGFnZSAyM10K

--_003_23CE718903A838468A8B325B80962F9B8CB962D9blreml501mbb_--


From nobody Mon Jul 31 07:17:14 2017
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69864132325 for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 07:17:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, 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 YDZdE-Q6Uixw for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 07:17:12 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AB57132320 for <ietf@ietf.org>; Mon, 31 Jul 2017 07:17:08 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 0D888E1DB; Mon, 31 Jul 2017 10:18:52 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 3A52D80243; Mon, 31 Jul 2017 10:17:07 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Randy Bush <randy@psg.com>
cc: "John Levine" <johnl@taugh.com>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
In-Reply-To: <m2y3r5w991.wl-randy@psg.com>
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Mon, 31 Jul 2017 10:17:07 -0400
Message-ID: <21320.1501510627@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Zm4lnaLLCt4fikG2aYipvEX9wPc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 14:17:13 -0000

--=-=-=
Content-Type: text/plain


Randy Bush <randy@psg.com> wrote:
    > someone else suggested that we turn off all other ssids for the 6man and
    > v6ops wg meetings.  there would be leakage, of course.  and it's a pita
    > (we *really* do not like to make changes during the week).  perhaps the
    > chairs could strongly encourage those in the wg meetings to use either
    > v6only or nat64.

I think that this is a really good idea.

I lived from v6ops onwards on nat64 during IETF99.
(But, my "VPN" has always used IPv6-only on the inside, so I never noticed
any loss)

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAll/O+IACgkQgItw+93Q
3WUmagf+NiTbSTMk65HHfwizPBryv4P9vA7n44lHlUwwp+5Q2y4/GYrXofJ8RNLt
FmECru+SZNiF/BnXZsL49DFsk5LeHocKNOwGu6As1IXUXFDchKRokv5KLlk5eJZh
iShex9LznK5iC+nruxobtbXyuEyG+oE4KuOKrUXuGSOPnKSYICdmgv5AEutaS3ZC
of4O3wTvFJY4f0kJ2tNXfJvF4ni2P8GkulyA7vbfzeoPxVFuGSEEIRgllgD5oFv4
czy6TQRCLEk2wLRseZLWGpShfuMHQ2V38iM4hoYhuWR63hxpVz5z0i5VvtiiwObr
MSM8L4bbR8U9DqmbM/qjpwbBLvj7NQ==
=nf99
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Jul 31 07:25:25 2017
Return-Path: <eric.gray@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E36B213234C; Mon, 31 Jul 2017 07:25:23 -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 z6_tAP1cfp6N; Mon, 31 Jul 2017 07:25:19 -0700 (PDT)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (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 4961813233C; Mon, 31 Jul 2017 07:25:19 -0700 (PDT)
X-AuditID: c618062d-dc5689c000002716-59-597f5419368e
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usplmg20.ericsson.net (Symantec Mail Security) with SMTP id 3E.34.10006.9145F795; Mon, 31 Jul 2017 18:00:25 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.03.0352.000; Mon, 31 Jul 2017 10:25:17 -0400
From: Eric Gray <eric.gray@ericsson.com>
To: Ted Lemon <mellon@fugue.com>, Paul Hoffman <paul.hoffman@vpnc.org>
CC: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Thread-Topic: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Thread-Index: AQHS/s72kLMVBj7jjUiP+v4GRBo4o6JqCFUAgAAK1QCAAAlvAIAACKGAgAPs9eA=
Date: Mon, 31 Jul 2017 14:25:16 +0000
Message-ID: <48E1A67CB9CA044EADFEAB87D814BFF64B7A6930@eusaamb107.ericsson.se>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <B8D4A14E-7A79-4D72-9278-A3F89A343596@vpnc.org> <01D1995D-650F-4B8C-96C3-8694C5E5859A@fugue.com>
In-Reply-To: <01D1995D-650F-4B8C-96C3-8694C5E5859A@fugue.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.10]
Content-Type: multipart/alternative; boundary="_000_48E1A67CB9CA044EADFEAB87D814BFF64B7A6930eusaamb107erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprOIsWRmVeSWpSXmKPExsUyuXSPn65kSH2kQdN3WYuuh0oWzzbOZ7F4 s+YIk8Wt9V9YHVg8mi4sY/dYsuQnk8fn2VeZA5ijuGxSUnMyy1KL9O0SuDIed6xlKWizqji8 +DBrA+Njwy5GTg4JAROJcztvM3UxcnEICRxllDg57yyUs5xR4u2Wh6wgVWwCGhLH7qxlBLFF BNwkTl9ewAZSxCwwjVGi7esbsCJhgTCJs1eWM3cxcgAVhUt83iUDUe8nMW3bIbBeFgFViWvb XoKV8wr4Svzeu5gRYtliJokfc76ygCQ4BWwlvs6eAdbAKCAm8f3UGiYQm1lAXOLWk/lMEGcL SCzZc54ZwhaVePn4HyuErSQxaek5Voj6fInrD3vYIZYJSpyc+YRlAqPILCSjZiEpm4WkDCKu I7Fg9yc2CFtbYtnC18ww9pkDj5mQxRcwsq9i5CgtLsjJTTcy2MQIjK5jEmy6OxjvT/c8xCjA wajEw+vtUR8pxJpYVlyZe4hRgoNZSYR3vSFQiDclsbIqtSg/vqg0J7X4EKM0B4uSOO+E8xci hATSE0tSs1NTC1KLYLJMHJxSDYwR82y+RhUv1DSdK1JxX2mOm6VPWVlTz6LExczHxDdlzY0Q qjq6QlGlTOfu9H21Px6/OqrF4HJUqv3oAsf84il31TUkmMX81jW7fPgRsPi7+VR3609zU2fe PTW5SztF8OFWxz0v/q4WnHL+QbPBbwEOdbmTdvlreQtOmaeHzmsvjRX8IDdv4xElluKMREMt 5qLiRACM4ZwLqgIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MsPOQDb-fpTX1FSJN4P_6qDeWmQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 14:25:24 -0000

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

Ted,

                This does not seem to be a good idea, because it makes thin=
gs more difficult for most people so that it is easier for a few.  I rather=
 like the idea that all of my devices are able to connect to the IETF WiFi =
by default.

If people want to avoid automatically connecting to SSID "ietf," it is not =
hard for them to cause their device(s) to "forget" that SSID.

And, if there is a particular reason why connecting to the default WiFi wou=
ld be a problem at one IETF meeting, then we could change the SSID for that=
 meeting only.

--
Eric

From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Ted Lemon
Sent: Friday, July 28, 2017 6:22 PM
To: Paul Hoffman <paul.hoffman@vpnc.org>
Cc: draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org; ietf@ietf.org
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF=
 Meetings

On Jul 28, 2017, at 5:50 PM, Paul Hoffman <paul.hoffman@vpnc.org<mailto:pau=
l.hoffman@vpnc.org>> wrote:
The legacy network will have a different SSID. All laptops remember which S=
SIDs you have connected to successfully in the past. Thus, it is likely tha=
t if you encounter problems and have to switch to the example-ssid-legacy S=
SID, and you close your laptop to move to a new room and open it again, you=
'll be put back onto the ietf SSID.

This is a good point.   Arguably, we should use a different SSID every IETF=
.   E.g., ietf-100 instead of ietf.   We're already proposing to do that fo=
r ietf-legacy so that people don't automatically associate with that ssid.

So if ietf goes away in favor of ietf-100, and ietf-hotel becomes ietf-100-=
hotel (or something like that), then would that address your objection?


--_000_48E1A67CB9CA044EADFEAB87D814BFF64B7A6930eusaamb107erics_
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:Menlo-Regular;
	panose-1:0 0 0 0 0 0 0 0 0 0;}
/* 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:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle19
	{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: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"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Ted,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This does not seem to be a good idea=
, because it makes things more difficult for most people so that it is easi=
er for a few.&nbsp; I rather like the idea that all of my devices are able =
to connect to the IETF WiFi by default.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"text-indent:.5in">If people want to avoid a=
utomatically connecting to SSID &#8220;ietf,&#8221; it is not hard for them=
 to cause their device(s) to &#8220;forget&#8221; that SSID.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"text-indent:.5in"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"text-indent:.5in">And, if there is a partic=
ular reason why connecting to the default WiFi would be a problem at one IE=
TF meeting, then we could change the SSID for that meeting only.<o:p></o:p>=
</p>
<p class=3D"MsoNormal" style=3D"text-indent:.5in"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">--<o:p></o:p></p>
<p class=3D"MsoNormal">Eric<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> ietf [mailto:ietf-bounces@ietf.org] <b>=
On Behalf Of
</b>Ted Lemon<br>
<b>Sent:</b> Friday, July 28, 2017 6:22 PM<br>
<b>To:</b> Paul Hoffman &lt;paul.hoffman@vpnc.org&gt;<br>
<b>Cc:</b> draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org; ietf@ietf.=
org<br>
<b>Subject:</b> Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi f=
or IETF Meetings<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">On Jul 28, 2017, at 5:50 PM, Paul Hoffman &lt;<a hre=
f=3D"mailto:paul.hoffman@vpnc.org">paul.hoffman@vpnc.org</a>&gt; wrote:<o:p=
></o:p></p>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-family:&quot;Me=
nlo-Regular&quot;,serif">The legacy network will have a different SSID. All=
 laptops remember which SSIDs you have connected to successfully in the pas=
t. Thus, it is likely that if you encounter problems
 and have to switch to the example-ssid-legacy SSID, and you close your lap=
top to move to a new room and open it again, you'll be put back onto the ie=
tf SSID.</span><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">This is a good point. &nbsp; Arguably, we should use=
 a different SSID every IETF. &nbsp; E.g., ietf-100 instead of ietf. &nbsp;=
 We're already proposing to do that for ietf-legacy so that people don't au=
tomatically associate with that ssid.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">So if ietf goes away in favor of ietf-100, and ietf-=
hotel becomes ietf-100-hotel (or something like that), then would that addr=
ess your objection?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_48E1A67CB9CA044EADFEAB87D814BFF64B7A6930eusaamb107erics_--


From nobody Mon Jul 31 07:51:13 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAF68132420 for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 07:51:10 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 hTzz9iv4aMcM for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 07:51:09 -0700 (PDT)
Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (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 0956413247F for <ietf@ietf.org>; Mon, 31 Jul 2017 07:50:47 -0700 (PDT)
Received: by mail-qk0-x22b.google.com with SMTP id a77so51988585qkb.0 for <ietf@ietf.org>; Mon, 31 Jul 2017 07:50:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=i82Y++32W0la8sxDd19elRVqFo4R80E9OJSCJr7zQ+w=; b=SClbEkSWXOgJSaa5VecYOkUBUjA3Qs52SrFU6TUDLG7rcP4OYVeP0ON5+csOe4mpZv 2T9NgSH/35s916vcEOLpUWPdOw+Mr2PW8sujeRZ8CrgNVD0t8mcsl9Cq9fyrsRE6LT0S FXN0GwKccPFTetuckQwIW6NcUZEBdvR9AYlsg4B/xkqFvvIY2Vo+jFZQuxxKnsA7x2tB 17VeHHhdpEH1V4WT1G6SimUJWkPL23Eh/9z1Fo75ZqYT2/t1Qi6NRqMGCZCh1PUQEXmV i+4L2Jdn5rs/eRR44SWxvZzq6ATlHVsAKrazTtb81eqG+CD6MG09AuGv0sRl4rxT7IpG ny0A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=i82Y++32W0la8sxDd19elRVqFo4R80E9OJSCJr7zQ+w=; b=fa52/Ruqg84urvGXcM+vqqzCgs43aV/R0Qqpnh5xKZ7gUcKHU5cQOoQOhjk+uNwp8W DHy1vbTMZvdAS8uiaLEdY/2LxZM3g/KlkZTk7l7/iduClJac18Zq2Hupm1JK26Ptw1LY hk9jM+Vt8XyyEFCxBtFX6EJmevDc5nvixFoyc+CD6jyPEZhbg8mzNw1i1Gv5xq1ee5Vp xZTv5cHJphqjdFYGCetZ1X7sYNTc2nwqG4D8n3BV6ZbqIiQsTPEVe2knTht5jyWk+GhA +nm6pYiVdxwjq/xwaf606Fx5Ka1IQjMx49ulqQHh3C6+g9JjZhlijzNfZql7zn1ebrwa oQlQ==
X-Gm-Message-State: AIVw110Ymj7a901cpM1O+cxEoYuYozoauSaOAOdj2HHDt0N6iMP3rin6 M2vk6Ti5MQ5b0Dh65Ajkmg==
X-Received: by 10.55.54.84 with SMTP id d81mr19856266qka.143.1501512647085; Mon, 31 Jul 2017 07:50:47 -0700 (PDT)
Received: from [10.0.30.153] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id p52sm21464274qtc.74.2017.07.31.07.50.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 31 Jul 2017 07:50:46 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <1AC0EF3A-7520-4D10-B08E-84C14C123F50@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_767E666A-1A5C-4881-873B-66AE97B975DF"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Mon, 31 Jul 2017 10:50:45 -0400
In-Reply-To: <48E1A67CB9CA044EADFEAB87D814BFF64B7A6930@eusaamb107.ericsson.se>
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>
To: Eric Gray <eric.gray@ericsson.com>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <B8D4A14E-7A79-4D72-9278-A3F89A343596@vpnc.org> <01D1995D-650F-4B8C-96C3-8694C5E5859A@fugue.com> <48E1A67CB9CA044EADFEAB87D814BFF64B7A6930@eusaamb107.ericsson.se>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bHkeWsRlH5rJMYtX7WxZw7YSyAY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 14:51:11 -0000

--Apple-Mail=_767E666A-1A5C-4881-873B-66AE97B975DF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Jul 31, 2017, at 10:25 AM, Eric Gray <eric.gray@ericsson.com> wrote:
>                 This does not seem to be a good idea, because it makes =
things more difficult for most people so that it is easier for a few.  I =
rather like the idea that all of my devices are able to connect to the =
IETF WiFi by default.

This assertion is not based in fact, as far as I know.   The _fact_ is =
that we don't actually know whether this (v6-only+nat64 as the default) =
will create hardship for "most people".   It won't make it easier for =
anyone=E2=80=94that's not the point.

Also, none of your devices can connect to the IETF wifi automatically: =
it's protected by 802.1x, so you have to set that up, and in my =
experience doing so has not been trivial for some devices (e.g., my =
Chromebook and my Android).   I haven't had to introduce a new device to =
the IETF SSID in a while, but everybody who connects to the IETF SSID =
had to do something to connect to it=E2=80=94it didn't Just Happen.

FWIW, I don't think those folks who are reacting to this discussion =
negatively need to be so concerned.   As far as I can tell, the =
consensus on the mailing list is not to do this, and in particular if =
the NOC staff aren't willing to do it there's no point in us arguing =
about it.   I think the conversation has been useful, but if you feel =
the need to weigh in just to say you're against it, I think that need =
has passed.

I am disappointed with this apparent consensus, and surprised at and =
disappointed in some of the people who pushed back on the proposal.   =
But if you think I am continuing to participate in the conversation =
because I think I'm going to change the consensus, rest assured that I =
have no such illusions.


--Apple-Mail=_767E666A-1A5C-4881-873B-66AE97B975DF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jul 31, 2017, at 10:25 AM, Eric Gray &lt;<a =
href=3D"mailto:eric.gray@ericsson.com" =
class=3D"">eric.gray@ericsson.com</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; This does not seem to be a good idea, =
because it makes things more difficult for most people so that it is =
easier for a few.&nbsp; I rather like the idea that all of my devices =
are able to connect to the IETF WiFi by =
default.</div></div></blockquote><br class=3D""></div><div>This =
assertion is not based in fact, as far as I know. &nbsp; The _fact_ is =
that we don't actually know whether this (v6-only+nat64 as the default) =
will create hardship for "most people". &nbsp; It won't make it easier =
for anyone=E2=80=94that's not the point.</div><div><br =
class=3D""></div><div>Also, none of your devices can connect to the IETF =
wifi automatically: it's protected by 802.1x, so you have to set that =
up, and in my experience doing so has not been trivial for some devices =
(e.g., my Chromebook and my Android). &nbsp; I haven't had to introduce =
a new device to the IETF SSID in a while, but everybody who connects to =
the IETF SSID had to do something to connect to it=E2=80=94it didn't =
Just Happen.</div><div><br class=3D""></div><div>FWIW, I don't think =
those folks who are reacting to this discussion negatively need to be so =
concerned. &nbsp; As far as I can tell, the consensus on the mailing =
list is not to do this, and in particular if the NOC staff aren't =
willing to do it there's no point in us arguing about it. &nbsp; I think =
the conversation has been useful, but if you feel the need to weigh in =
just to say you're against it, I think that need has =
passed.</div><div><br class=3D""></div><div>I am disappointed with this =
apparent consensus, and surprised at and disappointed in some of the =
people who pushed back on the proposal. &nbsp; But if you think I am =
continuing to participate in the conversation because I think I'm going =
to change the consensus, rest assured that I have no such =
illusions.</div><div><br class=3D""></div></body></html>=

--Apple-Mail=_767E666A-1A5C-4881-873B-66AE97B975DF--


From nobody Mon Jul 31 08:33:11 2017
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4805E1324D4; Mon, 31 Jul 2017 08:33:10 -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, RP_MATCHES_RCVD=-0.001, 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=ecs.soton.ac.uk
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 TBXNp1JIelNv; Mon, 31 Jul 2017 08:33:08 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 204AD1324CC; Mon, 31 Jul 2017 08:33:03 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6VFUi6r011993; Mon, 31 Jul 2017 16:30:44 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v6VFUi6r011993
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1501515054; bh=Sn6Wbc2EmqyEMZj8Ji/e/ki5UP4=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=OwaGZp3cNY0aotD5dbmCXOR1FHmOj8tEuUQLXV2L2eGfzhHCU71ByzSo+brHSE+y2 rcgBxSaNHfHTiulrVRgw3WJvwggBGD0DN8QRxZM2tQKbVy3+xgp80ORxeGExteqkE7 EAOR/+0IHS1ZhnKpXYHlR+rP6YAEzU7uBww73H6M=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id y6UGUc1136007840qJ ret-id none; Mon, 31 Jul 2017 16:30:54 +0100
Received: from 20010a88d51011.ipv6.customer.clara.net (20010a88d51011.ipv6.customer.clara.net [IPv6:2001:a88:d510:1101:3d25:de87:64aa:5fc9] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6VFSNse029770 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 31 Jul 2017 16:28:24 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <1AC0EF3A-7520-4D10-B08E-84C14C123F50@fugue.com>
Date: Mon, 31 Jul 2017 16:28:23 +0100
Cc: Eric Gray <eric.gray@ericsson.com>, "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>,  Paul Hoffman <paul.hoffman@vpnc.org>, "ietf@ietf.org" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|ae58c68b0ee165f0e9d97b24a48e2f72y6UGUc03tjc|ecs.soton.ac.uk|6D8155AF-D7C8-4A3A-8233-456D7E40FD2C@ecs.soton.ac.uk>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <B8D4A14E-7A79-4D72-9278-A3F89A343596@vpnc.org> <01D1995D-650F-4B8C-96C3-8694C5E5859A@fugue.com> <48E1A67CB9CA044EADFEAB87D814BFF64B7A6930@eusaamb107.ericsson.se> <1AC0EF3A-7520-4D10-B08E-84C14C123F50@fugue.com> <6D8155AF-D7C8-4A3A-8233-456D7E40FD2C@ecs.soton.ac.uk>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3273)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=y6UGUc113600784000; tid=y6UGUc1136007840qJ; client=relay,ipv6; mail=; rcpt=; nrcpt=4:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v6VFUi6r011993
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9SwbDB0x4TCAiJJgeiM_6h7eCZQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 15:33:10 -0000

> On 31 Jul 2017, at 15:50, Ted Lemon <mellon@fugue.com> wrote:
>=20
> On Jul 31, 2017, at 10:25 AM, Eric Gray <eric.gray@ericsson.com> =
wrote:
>>                 This does not seem to be a good idea, because it =
makes things more difficult for most people so that it is easier for a =
few.  I rather like the idea that all of my devices are able to connect =
to the IETF WiFi by default.
>=20
> This assertion is not based in fact, as far as I know.   The _fact_ is =
that we don't actually know whether this (v6-only+nat64 as the default) =
will create hardship for "most people".   It won't make it easier for =
anyone=E2=80=94that's not the point.
>=20
> Also, none of your devices can connect to the IETF wifi automatically: =
it's protected by 802.1x, so you have to set that up, and in my =
experience doing so has not been trivial for some devices (e.g., my =
Chromebook and my Android).   I haven't had to introduce a new device to =
the IETF SSID in a while, but everybody who connects to the IETF SSID =
had to do something to connect to it=E2=80=94it didn't Just Happen.

This may be why 900+ devices associated to the ietf-legacy99 SSID =
automatically, even though they had not seen it before. I think Joel =
postulated about that previously.

> FWIW, I don't think those folks who are reacting to this discussion =
negatively need to be so concerned.   As far as I can tell, the =
consensus on the mailing list is not to do this, and in particular if =
the NOC staff aren't willing to do it there's no point in us arguing =
about it.   I think the conversation has been useful, but if you feel =
the need to weigh in just to say you're against it, I think that need =
has passed.

That is a pretty clear consensus.

Question is whether we can do more to help capture / share useful NAT64 =
usage data, or to feed into potential focused activity around a WG =
session or a hackathon event.

> I am disappointed with this apparent consensus, and surprised at and =
disappointed in some of the people who pushed back on the proposal.   =
But if you think I am continuing to participate in the conversation =
because I think I'm going to change the consensus, rest assured that I =
have no such illusions.

Tim




From nobody Mon Jul 31 12:55:20 2017
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3633B1327A6 for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 12:55:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, 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 tWCeClz7KFgY for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 12:55:17 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CED531327AD for <ietf@ietf.org>; Mon, 31 Jul 2017 12:55:17 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 8811BE1E7 for <ietf@ietf.org>; Mon, 31 Jul 2017 15:57:02 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id E8BA480243 for <ietf@ietf.org>; Mon, 31 Jul 2017 15:55:16 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
Subject: normative references to IANA registries
X-Attribution: mcr
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Mon, 31 Jul 2017 15:55:16 -0400
Message-ID: <523.1501530916@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ihwlPm3yqDQdFwapvOaW8ngBxq4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 19:55:19 -0000

--=-=-=
Content-Type: text/plain


I'm implementing draft-ietf-ipsecme-rfc4307bis.
It basically sets MUST/SHOULD/etc. values for various algorithms. The IPsec(ME)
WG updates things as the world evolves.

   "References to the specification
   defining these algorithms are in the IANA registry."

It would be nice if it gave the actual name of the Registry.
But, I think in this hyperlinked internet, it really should reference the
registry itself directly.

So I wonder out loud: shouldn't all of the IANA registries have clear
reference files that could be normatively referenced?

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAll/iyQACgkQgItw+93Q
3WWSCgf/Y+w4rzfpM7BHC2hBhax2OYpl2cSj/z9kRfiwwli268bf+4WtZ9U/0Fbv
uSGz5GS9S1Y2y+vDukYLZ4mK0Yl4k34y3ht8w2Km6JrjAYbGvwMQH1MQNaAsKFVp
Dye0GcE7noFLqUv1nt+PAWsYoYMNro907OL8aX2RXClSQojeSkOnW0/eKMeEb38d
XTk9p2jEGcYOrT0O+IRMbLQ9F3NGzmOSiceSseZnxyxQ7v8K8sS0tGPjVikO9Ai1
HhK3v7joRCyfFdGshiVlbZX3/NaR2QPBoE0uWHaJYaNFPQyKdzaKTQeTxiC/3FJm
rbSZCADjPFjhqkMTHQj5skvh1JwnBQ==
=IJBT
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Jul 31 13:03:34 2017
Return-Path: <adam@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09BBA127735; Mon, 31 Jul 2017 13:03:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level: 
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 fYmurtcwupDe; Mon, 31 Jul 2017 13:03:29 -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 9378F124B0A; Mon, 31 Jul 2017 13:03:29 -0700 (PDT)
Received: from Svantevit.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v6VK2b88068573 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 31 Jul 2017 15:02:39 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.local
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: Tim Chown <tjc@ecs.soton.ac.uk>, Ted Lemon <mellon@fugue.com>
Cc: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <B8D4A14E-7A79-4D72-9278-A3F89A343596@vpnc.org> <01D1995D-650F-4B8C-96C3-8694C5E5859A@fugue.com> <48E1A67CB9CA044EADFEAB87D814BFF64B7A6930@eusaamb107.ericsson.se> <1AC0EF3A-7520-4D10-B08E-84C14C123F50@fugue.com> <6D8155AF-D7C8-4A3A-8233-456D7E40FD2C@ecs.soton.ac.uk> <EMEW3|ae58c68b0ee165f0e9d97b24a48e2f72y6UGUc03tjc|ecs.soton.ac.uk|6D8155AF-D7C8-4A3A-8233-456D7E40FD2C@ecs.soton.ac.uk>
From: Adam Roach <adam@nostrum.com>
Message-ID: <e51114d0-63b8-e83d-ccd8-45474e3a56d9@nostrum.com>
Date: Mon, 31 Jul 2017 15:02:32 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <EMEW3|ae58c68b0ee165f0e9d97b24a48e2f72y6UGUc03tjc|ecs.soton.ac.uk|6D8155AF-D7C8-4A3A-8233-456D7E40FD2C@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary="------------8C416F4E85FC73D33F86A84B"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/A87_XjE3naZOE2PNVoZJaicW7K0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 20:03:32 -0000

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

On 7/31/17 10:28 AM, Tim Chown wrote:
> Question is whether we can do more to help capture / share useful NAT64 usage data

I posit that there is room to do so in the way of education: if users 
better understood the purpose and nature of the nat64 network, and if 
there were some *non-technical* steering of people to try it out, 
parties interested in collecting such information would likely get more 
of the data they want. Today, users at IETF meetings are presented with 
a dazzling array of:

  * ietf
  * ietf-legacy
  * ietf-2.4ONLY
  * ietf-v6ONLY
  * ietf-hotel
  * ietf-nat64

...and I suspect most people have little clue about why most of these 
exist or which to use. The "nat64" variation certainly gets lost in the 
noise.

We've had "awareness" posters on-site to educate participants about BOFs 
occurring during the week for a while now; perhaps a similar poster 
explaining what the nat64 network is, that the NOC now considers it 
production-quality, why people might want to try it out, and how to 
report issues when they arise, would be useful in driving enough traffic 
to gather additional statistics. If you wanted to be even more 
aggressive about it, you could even replicate it on little slips of 
paper handed to people when they get their badges.

/a


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

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 7/31/17 10:28 AM, Tim Chown wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:EMEW3|ae58c68b0ee165f0e9d97b24a48e2f72y6UGUc03tjc|ecs.soton.ac.uk|6D8155AF-D7C8-4A3A-8233-456D7E40FD2C@ecs.soton.ac.uk">
      <pre wrap="">Question is whether we can do more to help capture / share useful NAT64 usage data</pre>
    </blockquote>
    <br>
    I posit that there is room to do so in the way of education: if
    users better understood the purpose and nature of the nat64 network,
    and if there were some *non-technical* steering of people to try it
    out, parties interested in collecting such information would likely
    get more of the data they want. Today, users at IETF meetings are
    presented with a dazzling array of:<br>
    <ul>
      <li>ietf</li>
      <li>ietf-legacy</li>
      <li>ietf-2.4ONLY</li>
      <li>ietf-v6ONLY</li>
      <li>ietf-hotel</li>
      <li>ietf-nat64</li>
    </ul>
    <p>...and I suspect most people have little clue about why most of
      these exist or which to use. The "nat64" variation certainly gets
      lost in the noise.</p>
    <p>We've had "awareness" posters on-site to educate participants
      about BOFs occurring during the week for a while now; perhaps a
      similar poster explaining what the nat64 network is, that the NOC
      now considers it production-quality, why people might want to try
      it out, and how to report issues when they arise, would be useful
      in driving enough traffic to gather additional statistics. If you
      wanted to be even more aggressive about it, you could even
      replicate it on little slips of paper handed to people when they
      get their badges.<br>
    </p>
    <p>/a<br>
    </p>
  </body>
</html>

--------------8C416F4E85FC73D33F86A84B--


From nobody Mon Jul 31 13:10:55 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01A82131CAB for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 13:10:54 -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, FREEMAIL_FROM=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 NBNnLIXPgDAW for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 13:10:51 -0700 (PDT)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::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 13FFD1327B9 for <ietf@ietf.org>; Mon, 31 Jul 2017 13:10:51 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id k20so17879309wmg.0 for <ietf@ietf.org>; Mon, 31 Jul 2017 13:10:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=pIwi4UaGhE1Sw4AzgV1j98kVSD1nyqvqcJQ4ehtPlmY=; b=r541OAkSXxN5EF7UM5TdM1wQ5mJ8ciuIriUVZ822ra3o4d87uXMch6tAdjgXTf8Yah z1Rd1Itcf62COFyvTfBM0ueymHPKeEO8275xiFbl0QqwhEyoRzineis5JrRFnHXsO2NM 5EbXUoTDV52fry4KzE11pyb5IGxW3MNQyMryHbdTipqf6d53SwgRXsG8p2kqJfXg1olR bFhVGuTYnfUA8Uy9FiOuQiIsBHYKsmbNvvTcg8tMcNg4ZJVDxORb5we+mp/U8LyzSynv FbaWTi1TbjqDTp7BCtKefL6133LjedzeuIGIb6YilKV+vvpzQh00OcU+aC/yJm2w52HB poDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=pIwi4UaGhE1Sw4AzgV1j98kVSD1nyqvqcJQ4ehtPlmY=; b=Ewcvb8MSb5WVDGNgTFGv2atEfPRptRHm24nAOxU4PBMzJ4WC4Nr1FG7GxlKeJD+hKa Pa4Q3NwYHG0pAJQbeXZPwixJuABJ5YlNI6TY05vwy98TrSF/LaXfVwRDn3kToZezltMD X4sxLvgNFhrlfcL0iLJL0D56WNWY8/C39DLFHfnZqi2g3MrP8IHfgunjrEIakVP/M9ku eJ7CzH1bDfpPxhhKZGCEwrbGKJF86bNmB+N7I+eyUfvpaRzR0HQPAE8neC7dpbPtREL7 6AR54REmqDgxIf8lBskyiMuObiGDJwItFnoGxrADM87pM8+vfO+TSexue4xhFyGcRHyX CoIg==
X-Gm-Message-State: AIVw112F6MwvIbvGta945pecVzj186HBDOgMD1lTOimztGlKbgOTRfLb yHlyS8y+X//IQqlCzFg=
X-Received: by 10.28.97.134 with SMTP id v128mr12469970wmb.83.1501531849357; Mon, 31 Jul 2017 13:10:49 -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 d20sm30439783wrc.96.2017.07.31.13.10.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 31 Jul 2017 13:10:48 -0700 (PDT)
Subject: Re: normative references to IANA registries
To: Michael Richardson <mcr+ietf@sandelman.ca>, ietf@ietf.org
References: <523.1501530916@obiwan.sandelman.ca>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <dd33b6ad-4ace-942e-901b-4d763496076f@gmail.com>
Date: Mon, 31 Jul 2017 21:10:46 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <523.1501530916@obiwan.sandelman.ca>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tlZn-CcAlZRWW7yusqpJs2cpLcc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 20:10:54 -0000

> So I wonder out loud: shouldn't all of the IANA registries have clear
> reference files that could be normatively referenced?
>

Yes

- Stewart


From nobody Mon Jul 31 13:17:02 2017
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B483C129B30 for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 13:17:00 -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, RCVD_IN_DNSWL_MED=-2.3, 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 IhL9sdEN4qoF for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 13:16:59 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 6F104127735 for <ietf@ietf.org>; Mon, 31 Jul 2017 13:16:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v6VKGqnH016088; Mon, 31 Jul 2017 22:16:52 +0200 (CEST)
Received: from [192.168.217.124] (p5DC7FC78.dip0.t-ipconnect.de [93.199.252.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3xLrMS5Bm0zDLqT; Mon, 31 Jul 2017 22:16:52 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: normative references to IANA registries
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <523.1501530916@obiwan.sandelman.ca>
Date: Mon, 31 Jul 2017 22:16:51 +0200
Cc: ietf@ietf.org
X-Mao-Original-Outgoing-Id: 523225010.744532-12b00ed3db81c7d863299e9ff59a794f
Content-Transfer-Encoding: quoted-printable
Message-Id: <E8859A9F-7539-4C6B-962C-56E6F3323C14@tzi.org>
References: <523.1501530916@obiwan.sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RvmE2NgLDRyWIayLJK9TPYvJel0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 20:17:00 -0000

On Jul 31, 2017, at 21:55, Michael Richardson <mcr+ietf@sandelman.ca> =
wrote:
>=20
> So I wonder out loud: shouldn't all of the IANA registries have clear
> reference files that could be normatively referenced?

Try referencing, say, {{!IANA.cbor-tags}} =E2=80=94 it just works :-)

Gr=C3=BC=C3=9Fe, Carsten


From nobody Mon Jul 31 13:31:23 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D227131CC0 for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 13:31: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, 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 Mv3cY0juLvZy for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 13:31:20 -0700 (PDT)
Received: from mail-pf0-x230.google.com (mail-pf0-x230.google.com [IPv6:2607:f8b0:400e:c00::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 A334A131CAE for <ietf@ietf.org>; Mon, 31 Jul 2017 13:31:20 -0700 (PDT)
Received: by mail-pf0-x230.google.com with SMTP id z129so85831054pfb.3 for <ietf@ietf.org>; Mon, 31 Jul 2017 13:31:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=gDeFeX7KikM8Mk3ph/cuh4h8fTezFDcjCnayX/TVm2I=; b=b6cmbZNKSgBYAlJTH5xacvkCRG6I7G5UYvg1EszYFnf5ge4tux3xVY37AYwRUGTlEO avdRxOZjNkikclJO1kaIYm2zRPQMiogFQGwlnHK6S3jfDiPG9zNokMBOPY0PCkePs/CC 94WZWllwVhtCpP24/oWepmDMnecRfdRSnto7al0emTkvg57xwMlrLyf/s7ap57QwRxHQ FXnVZPq+Mm5BEHe3pXUHy9pcVYKwnrE7VEbhXqKkEpVQjK2xi3W2t5T55jkKIh5kgY2d nqEyH56t3JzRe2wK3Is7zF/CD/mInHjFIR6onZK5/+GTShKltDUNj2QKma29xFDlQGKY JMkA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=gDeFeX7KikM8Mk3ph/cuh4h8fTezFDcjCnayX/TVm2I=; b=V7B+olvKsOpD/vW+DXBnXYDN2p815H1HdocvolEgAdEf0A+SNEQE9DzxW0539O4r6N kHSx4datsX9/TSKXaqGwNud+L7LtIMqnWwGvZYlLfOAke8nFrEjyokbmy6h4UKbbKRNl VE7sJq3FCoAYy3w4TKho1QelGDjn9ohTc0eo8+BjuCB1YeJpWTHegS1NIuELMnxcvmpe AQvawcmkBazfw0iTHO9/6307I9mN+2lRux+VVmqPCLDDqOp5hLU1zXPvgKXNPxJQGXuC fq8AdxIeWQHC+olglr+DsiTvs/dvChHy0JFyUfxH9Zw5n/RoABMHhSx22LS59s2tjUbq HKqQ==
X-Gm-Message-State: AIVw1133AS+i+AbfF+3Fv7/izvmiNMJ1Gk/2Tjjg0aURmBT7GiHGipyo zfsGxgRcjBkOq4yE
X-Received: by 10.84.233.195 with SMTP id m3mr18523135pln.292.1501533079843; Mon, 31 Jul 2017 13:31:19 -0700 (PDT)
Received: from ?IPv6:2406:e007:521f:1:28cc:dc4c:9703:6781? ([2406:e007:521f:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id q3sm8012862pfl.89.2017.07.31.13.31.17 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 31 Jul 2017 13:31:18 -0700 (PDT)
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: ietf@ietf.org
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com>
Date: Tue, 1 Aug 2017 08:31:17 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <21320.1501510627@obiwan.sandelman.ca>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eaY254VJh0zKHMUtZXwZ6SDRcSU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 20:31:22 -0000

On 01/08/2017 02:17, Michael Richardson wrote:
> 
> Randy Bush <randy@psg.com> wrote:
>     > someone else suggested that we turn off all other ssids for the 6man and
>     > v6ops wg meetings.  there would be leakage, of course.  and it's a pita
>     > (we *really* do not like to make changes during the week).  perhaps the
>     > chairs could strongly encourage those in the wg meetings to use either
>     > v6only or nat64.> 
> I think that this is a really good idea.

It would have the advantage that more people would pay attention to the screen
and speaker rather than doing email. And also, more and more people would
become aware that nat64 breaks stuff. I suppose that's good too. As advertising
for IPv6, it would do rather badly.

    Brian


From nobody Mon Jul 31 13:46:33 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8976F131C99 for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 13:46:27 -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, 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=fugue-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 mQYOeUs-Dmdc for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 13:46:26 -0700 (PDT)
Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::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 CC11D124217 for <ietf@ietf.org>; Mon, 31 Jul 2017 13:46:25 -0700 (PDT)
Received: by mail-qk0-x234.google.com with SMTP id u139so93108447qka.1 for <ietf@ietf.org>; Mon, 31 Jul 2017 13:46:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=/x1b/DjkVAbNdxpInt3Rr1F/7s8HO8SIK1aG0ytZODk=; b=HXhONqzoIKCkk0iYO8lpFDfSy8zXTARhU2tWlx6edltslAbV7+F5ysPmsKeYsHqw7G QDyIP2GGEhQTkkcfJgOGlWn/LBsxHnc9FSYJ2dpO1d0MmkrH+D9Wpvm8SsANqrloQDgc Etpek9zKJ+zzRQTwIB/z3P/pX62mWOR2RSCRmoONVrj3qofWCoOLuzI9h2F6MXvufMF7 TLtPHpMgMVvRlxsWdK3hyNfbmKH5CnG2c4MHOumQf5Qgu4q4gus/TMtgVqKW25LVQwN0 r07k487Go9KtHojbF48J1sQnU5beqIKr3hc0QBVZIeGlswTffqQO4l8e5T92Zav0kKb8 KNMQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=/x1b/DjkVAbNdxpInt3Rr1F/7s8HO8SIK1aG0ytZODk=; b=R93y2R/hMpMJxop1lWXIyHoJc8KqaI1BL8YEwWe1BQ+zfmJbF1Jf0SEapgehTpVC1N 6GcmmnDc8Lyupa3s5+m8ixSysndK1JUPfreLB6Gg7DWXHpm2B7Um3QGfH247TGBGv/Ym vY8NR4nYUsIVLm/1apQrgN/6FsePVfYE4m5yhTA7uB5Ff4zsuegS5GOu5e/aXlMlTBy8 3gP0RZ21Q/UU/rlmgsGXZuVcyHJp2FzUjAgDXvQhyO34Nw2cOuDWRU2DrdvogmsYYLuu dmsLhl7NujAN5INtBHm6WP9n0PC1z41cTYgDZnvVIpshiJ8c4jZtFWGtDJ9uENmtkg5C +rRA==
X-Gm-Message-State: AIVw111byG8FEHOaE/wRzVjLVwgud2PGjUV4HZzMBNLUqTTte8F4i6Q8 Seh2HFcYHc0mFMoOBal2JQ==
X-Received: by 10.55.132.6 with SMTP id g6mr24493188qkd.300.1501533984880; Mon, 31 Jul 2017 13:46:24 -0700 (PDT)
Received: from [10.0.30.153] (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id s32sm12205979qth.71.2017.07.31.13.46.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 31 Jul 2017 13:46:24 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9372D9CC-8EF4-4145-A077-F4AC89A6F90E"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Mon, 31 Jul 2017 16:46:22 -0400
In-Reply-To: <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com>
Cc: ietf@ietf.org
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ob70wrSIGOYJT6BfK8Ytb4mWAxE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 20:46:28 -0000

--Apple-Mail=_9372D9CC-8EF4-4145-A077-F4AC89A6F90E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jul 31, 2017, at 4:31 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
> And also, more and more people would
> become aware that nat64 breaks stuff. I suppose that's good too. As =
advertising
> for IPv6, it would do rather badly.

Brian, why on earth would we want to advertise IPv6 to IETF attendees?   =
We invented IPv6.   If we really can't run a v6-only network at IETF, =
what that says is that we have failed utterly and expensively.   I do =
not believe that this is correct: IPv6 works very well.

The point of having NAT64 is that it lets us actually run without any =
IPv4 on the wire and see what happens.   If the only things that fail =
are things that go through NAT64, that's a good outcome, particularly if =
the number of things going through NAT64 that fail is small relative to =
the total number of things that go through it.


--Apple-Mail=_9372D9CC-8EF4-4145-A077-F4AC89A6F90E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jul 31, 2017, at 4:31 PM, Brian E Carpenter &lt;<a =
href=3D"mailto:brian.e.carpenter@gmail.com" =
class=3D"">brian.e.carpenter@gmail.com</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">And also, more and more people =
would</span><br style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">become aware that nat64 breaks stuff. I =
suppose that's good too. As advertising</span><br style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">for IPv6, it would =
do rather badly.</span></div></blockquote></div><br class=3D""><div =
class=3D"">Brian, why on <i class=3D"">earth</i>&nbsp;would we want to =
advertise IPv6 to IETF attendees? &nbsp; We <i =
class=3D"">invented</i>&nbsp;IPv6. &nbsp; If we really can't run a =
v6-only network at IETF, what that says is that we have failed utterly =
and expensively. &nbsp; I do not believe that this is correct: IPv6 =
works very well.</div><div class=3D""><br class=3D""></div><div =
class=3D"">The point of having NAT64 is that it lets us actually run =
without any IPv4 on the wire and see what happens. &nbsp; If the only =
things that fail are things that go through NAT64, that's a good =
outcome, particularly if the number of things going through NAT64 that =
fail is small relative to the total number of things that go through =
it.</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_9372D9CC-8EF4-4145-A077-F4AC89A6F90E--


From nobody Mon Jul 31 14:00:42 2017
Return-Path: <olejacobsen@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D190131CAB for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 14:00:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.722
X-Spam-Level: 
X-Spam-Status: No, score=-2.722 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_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=me.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 62Ys2azEiZ_q for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 14:00:40 -0700 (PDT)
Received: from mr11p00im-asmtp001.me.com (mr11p00im-asmtp001.me.com [17.110.69.252]) (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 4DAB5131CA1 for <ietf@ietf.org>; Mon, 31 Jul 2017 14:00:40 -0700 (PDT)
Received: from process-dkim-sign-daemon.mr11p00im-asmtp001.me.com by mr11p00im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun  7 2017)) id <0OTZ00G003F88V00@mr11p00im-asmtp001.me.com> for ietf@ietf.org; Mon, 31 Jul 2017 21:00:37 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017; t=1501534836; bh=GvzZzmhb+XBR5AHcc4ssXKf/S1yf8NSudFjaB53B91Q=; h=Date:From:To:Subject:Message-id:MIME-version:Content-type; b=keiFs3REvbLizvqAzCA4Tc/22yZzjPLe8alimA4caNID0s7dNd0yhvFS4Mhm31N5F o4+RI2e5imcVrkwPxRxZ2d6rC8zNyb5xFDkEFfSgZwZIYSLMWUrqgZjXCq57CAVqnp 8WEiOa4iA5Srb3HGHvviNtaFVECNoHNhyKlB6E6LocITNHp6MK5zSllWNwzlKTlPvW iOTUJ7DJGR+NokN9UdPfqL66FZ9fK8KeIClzMiBpUwaBgpxm2c2Da3P8NmZ406CrD8 XIGgXu9oyTX9RXeAByTN2KuV4KVLSBnRANvsvW91VpUHNNiRAUBVMDZtXFLUjPyel9 NqvFEPQj4k4Cw==
Received: from icloud.com ([127.0.0.1]) by mr11p00im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun  7 2017)) with ESMTPSA id <0OTZ00G343OYW510@mr11p00im-asmtp001.me.com>; Mon, 31 Jul 2017 21:00:35 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-07-31_08:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1701120000 definitions=main-1707310351
Date: Mon, 31 Jul 2017 14:00:33 -0700 (PDT)
From: Ole Jacobsen <olejacobsen@me.com>
Reply-to: Ole Jacobsen <olejacobsen@me.com>
To: Ted Lemon <mellon@fugue.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, ietf@ietf.org
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
In-reply-to: <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com>
Message-id: <alpine.OSX.2.01.1707311349320.2496@rabdullah.local>
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dIQYon5Ktm2_xeGQVlSznxQHZJk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 21:00:41 -0000

You said:
> 
> Brian, why on earth would we want to advertise IPv6 to IETF 
> attendees?  We invented IPv6.  If we really can't run a v6-only 
> network at IETF, what that says is that we have failed utterly and 
> expensively.  I do not believe that this is correct: IPv6 works very 
> well.

Putting on my naive end-user hat:

That might be true, but here is the thing: "The mission of the IETF is 
to make the INTERNET work better..." (my emphasis)

For at least a decade now, I've been told that I should "just use 
IPv6" and some conferences have even "forced" me to do so.

I always respond with this question: "Does running IPv6 allow me to 
connect to the Internet?" (meaning the v4 Internet for the most part). 
The answer always seems to be: "Yes, but you have to manually 
configure this and, oh by the way, this won't work at all and that app 
might not behave as expected."

Demonstrating this to people who are experts seems like a waste
of time.

So it sounds to me like we HAVE indeed failed utterly and expensively. 
99% of Internet users do not have any idea what version of IP they are 
running just as they have no idea what a MAC address is or why/if they 
should care.

I'd love to see IPv6 succeed, but it is apparently impossible to do so 
without teaching end-users a lot of stuff they really have no interest 
in or ability to learn. What a shame.

Ole


From nobody Mon Jul 31 14:06:26 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0631F129B35 for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 14:06:25 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 WCKG-VfXR8ME for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 14:06:23 -0700 (PDT)
Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::22c]) (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 2620B131CE1 for <ietf@ietf.org>; Mon, 31 Jul 2017 14:06:23 -0700 (PDT)
Received: by mail-qk0-x22c.google.com with SMTP id z18so74239164qka.4 for <ietf@ietf.org>; Mon, 31 Jul 2017 14:06:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=l7s5KILH+CjgxtmDdtHlz3lMR9knjySkeql5+ledrUk=; b=0GD7LnB1bpsjwlXp/tFVviojvLhAiX3WwiZzToJzqZ7aKMEmGduLvvUTKZ5JTgu70v RoxY+uu3iJJH2ECnEsg3k9yCi/RVxyzV80TDBzp/w87gB9ssUP3xOtXUx9AcyarohJvw FKp1W2OZMlN47vm+xkO2VaTdi/k8VqN+DoZWVK2QpnY7+ZS8J1JmL35rsA6RrRHsMkXW 3d4A30GqUaPpq8JCelOXzJ+W8zchNvZ+pzXFyEtqJua+d1Zgf780T4dl3IykefhX0yyx Gu1z+f8mp8yy5GyKF1zwP3Oj/tWSBlX2o4Z8hMb4NX6hTk3yn2jlgIXkBvvvU83qu5Y0 oc2g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=l7s5KILH+CjgxtmDdtHlz3lMR9knjySkeql5+ledrUk=; b=iOj2UeL2nHP9TonYhkj/FQc9lvuGc4YSbEM7PKS9wku5lG0c0G7g2h5Z7P9r6hEO0s sl2/ugMUmQli4snlMP+ArJky00skM4qZasWWeWRkRstHg1QwaMzwmD16R2jZzHfkwjR2 e3FjG0Gd/KePCSxY+Aa1w9Tj4hEelojzic0Uvm+P8/Bb/ow9s0ciKz+vuiOZo9u2YJsD Jjpi821trce5ESY6Wan/xShc9TTCM87hdS9fBxivokLj5HIntlu0iyTj2y8jiFEEDbCb u4riXeg1dK7wMOhdmjDQIexihK6hOJzN6RLEdQp8ncsESObgNHjpaFzVP/LQfSBZgzY2 BYpw==
X-Gm-Message-State: AIVw113pxdr2SL7VGa6muOClNyu+zwPtoHzP1QgGNlwvjQc2qiXtj/rJ NqItZb4Lizk8FW5p
X-Received: by 10.55.21.223 with SMTP id 92mr24044007qkv.199.1501535182209; Mon, 31 Jul 2017 14:06:22 -0700 (PDT)
Received: from [10.0.30.153] (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id v55sm5278166qtc.90.2017.07.31.14.06.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 31 Jul 2017 14:06:21 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <6C3D3B7C-9732-4BD2-97F6-F03A00CB6781@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_2FE1E039-CC7F-4A20-9405-8F3258C590DE"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Mon, 31 Jul 2017 17:06:19 -0400
In-Reply-To: <alpine.OSX.2.01.1707311349320.2496@rabdullah.local>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, ietf@ietf.org
To: Ole Jacobsen <olejacobsen@me.com>
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/X3XsToRLljdVyWW5xKRfj9qJ1kw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 21:06:25 -0000

--Apple-Mail=_2FE1E039-CC7F-4A20-9405-8F3258C590DE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jul 31, 2017, at 5:00 PM, Ole Jacobsen <olejacobsen@me.com> wrote:
> I'd love to see IPv6 succeed, but it is apparently impossible to do so=20=

> without teaching end-users a lot of stuff they really have no interest=20=

> in or ability to learn. What a shame.

This statement is why I think we need to be running IPv6 by default.   =
What you are saying here simply isn't true.   There are lots of internet =
users running IPv6 and not even aware that they are doing so.   This is =
very evident in the stats for service providers that offer their service =
over IPv6 as well as IPv4.

If you can't connect to the wire and start using it with no special =
settings, it's broken.   The point of having IETF people connecting to a =
v6-only wire is to see what problems they run into.   The answer should =
be "none," and at least for me at recent IETFs, _it has been_.   It =
would be nice to have a larger sample size.

The reason we are advocating this is not that we want you to debug the =
user interface.   It's that we think it works.


--Apple-Mail=_2FE1E039-CC7F-4A20-9405-8F3258C590DE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jul 31, 2017, at 5:00 PM, Ole Jacobsen &lt;<a =
href=3D"mailto:olejacobsen@me.com" class=3D"">olejacobsen@me.com</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">I'd love to see =
IPv6 succeed, but it is apparently impossible to do so<span =
class=3D"Apple-converted-space">&nbsp;</span></span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">without teaching end-users a lot of stuff they =
really have no interest<span =
class=3D"Apple-converted-space">&nbsp;</span></span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">in or ability to learn. What a =
shame.</span></div></blockquote></div><br class=3D""><div class=3D"">This =
statement is why I think we need to be running IPv6 by default. &nbsp; =
What you are saying here simply isn't true. &nbsp; There are lots of =
internet users running IPv6 and not even aware that they are doing so. =
&nbsp; This is very evident in the stats for service providers that =
offer their service over IPv6 as well as IPv4.</div><div class=3D""><br =
class=3D""></div><div class=3D"">If you can't connect to the wire and =
start using it with no special settings, it's broken. &nbsp; The point =
of having IETF people connecting to a v6-only wire is to see what =
problems they run into. &nbsp; The answer should be "none," and at least =
for me at recent IETFs, _it has been_. &nbsp; It would be nice to have a =
larger sample size.</div><div class=3D""><br class=3D""></div><div =
class=3D"">The reason we are advocating this is not that we want you to =
debug the user interface. &nbsp; It's that we think it works.</div><div =
class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_2FE1E039-CC7F-4A20-9405-8F3258C590DE--


From nobody Mon Jul 31 14:12:37 2017
Return-Path: <paul@nohats.ca>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D28F1131CDC; Mon, 31 Jul 2017 14:12:23 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Paul Wouters <paul@nohats.ca>
To: <secdir@ietf.org>
Cc: draft-ietf-teas-gmpls-scsi.all@ietf.org, ietf@ietf.org, teas@ietf.org
Subject: Secdir telechat review of draft-ietf-teas-gmpls-scsi-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150153554378.6396.10436130949472778994@ietfa.amsl.com>
Date: Mon, 31 Jul 2017 14:12:23 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3gWn0tRYyC8KF--GIcaOoWS6LgQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 21:12:24 -0000

Reviewer: Paul Wouters
Review result: Has Issues

I have reviewed this document as part of the security directorate's 
ongoing effort to review all IETF documents being processed by the 
IESG.  These comments were written primarily for the benefit of the 
security area directors.  Document editors and WG chairs should treat 
these comments just like any other last call comments.

The summary of the review HAS ISSUES (might be minor)

The security considerations section only lists those considerations of
other documents it references. While that likely covers most issues, I'm
not sure it covers all issues. The introduction of this document tells us the
goal of this new "Generalized SCSI" value only in a somewhat vague way:

        [...] can be used with routing protocols that define GMPLS ISCDs,
        and any specific technology.

Since it does not explain _how_ it can be used, it is a bit difficult to
figure out what the security impact of this new field could be when it
is abused. What happens when this new field contains wrong or malicious
information?

And when I read:

        SCSI-TLVs MUST be processed in the order received and, if
        re-originated, ordering MUST be preserved.

What happens if someone maliciously re-orders these?

        Unknown SCSI-TLVs MUST be ignored

What happens when someone mangles a valid SCSI-TLV value so
it becomes ignored?

Another issue that could use clarification is the padding. It is only
said "may contain padding", but it is not specified how to pad. Prefix
with leading zeros? Append with FFs?

NITS:

        "[RFC7138] introduced a "

This reference is broken

In diagrams we tend to use "~" and not "..." to indicate variable length

I tend to use +--------+------+ rather then +-+-+-+-+-+-+

I would not explain "octets (bytes)". IETF tends to use octets as term.

"The value of the field MUST" -> "The value MUST"

corollary - A word harder for non-native english speakers

        "MAY contain a sequence of zero or more SCSI- TLVs."

MAY and "zero or more" is a little odd.





From nobody Mon Jul 31 14:18:17 2017
Return-Path: <prvs=13856d59bf=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12E69131C21 for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 14:18: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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
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 YcI_uQJd9llb for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 14:18:14 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7C54131CE1 for <ietf@ietf.org>; Mon, 31 Jul 2017 14:18:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1501535891; x=1502140691; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=m8nHO+ktopePY5JHKCsbxdPQO JlcQkPQgyniU4vuDM8=; b=U6c2f1NdPrjSMrJCBL7dmsVD8IVDtf07VkYNN1I9v YZa9ZhJ4SzmzlaToMw72KEMIWAjekiK3x9baOZmV3jJ35zOcmZEr3xTxHIQYufVS 8zqjAr1A5Xe2dnLNEP2hQtLNslxecdJv9qCDBn9ZjAelsPoHmyV9vdYAIcHGKHFE LI=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=gYSv4C5pdy0Us+5tWDOwuH/TDwgGFxlsDBQJIDZgDjZspZsU0NQygxNhtPmu g9jBI2ziraTCujzE1bh0qv7PsknZsNLRjOOvpB1JMmOcI0QvfKV6nD/5M 8PkDDPU0zz+AuwSycOxH1F89y+IFGixXAfSh+s+edZMxTXWuJT06K0=;
X-MDAV-Processed: mail.consulintel.es, Mon, 31 Jul 2017 23:18:11 +0200
X-Spam-Processed: mail.consulintel.es, Mon, 31 Jul 2017 23:18:09 +0200
Received: from [10.10.10.133] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005491495.msg for <ietf@ietf.org>; Mon, 31 Jul 2017 23:18:09 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170731:md50005491495::4Va17Bkahl4KPOri:00000KBM
X-Return-Path: prvs=13856d59bf=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.24.1.170721
Date: Mon, 31 Jul 2017 23:18:07 +0200
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Message-ID: <62FE7E9A-9CC0-4DE6-93C6-61A08AC95281@consulintel.es>
Thread-Topic: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local>
In-Reply-To: <alpine.OSX.2.01.1707311349320.2496@rabdullah.local>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HvmyLmrC_diTOolI_o0slcBz990>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 21:18:16 -0000

NAT64 was invented for a specific case (when apps use DNS and the right API=
s).

We realized then that app/devices vendors are lazy, or just they are out of=
 the market, so we invented 464XLAT, which uses the same concept as NAT64/D=
NS64, but improves it by using the CLAT, a small daemon code in the OS or t=
he CPE to solve the problems of the literal addresses and non-APIs apps/dev=
ices.

We don=E2=80=99t need to tell the customers to disable IPv4 in their LANs, =
we need to make sure that we deploy CPEs that support CLAT. This way, users=
 don=E2=80=99t need to throw away old devices or apps, neither learn anythi=
ng about IPv4 or IPv6, and everybody is happy.

We are trying to solve a problem with NAT64 which we knew since it was inve=
nted that it can=E2=80=99t be solved. We don=E2=80=99t have the time (unles=
s some magic is discovered) to now tell every ISP that is deploying IPv6 an=
d NAT64, to instead of NAT64 have something different. The solution is ther=
e, if CPE vendors implement it, and we are talking about an available open =
source code (several implementations) that take a few bytes.

We are already doing this effort in v6ops, I started trying to tell the RFC=
7084 about the need to update it, but didn=E2=80=99t succeeded. It seems th=
at now we may want to have instead of a CPE requirements including this, an=
 additional document to be a must for CPE vendors to support it, in case th=
e CPE expects =E2=80=9CIPv4 old devices and apps=E2=80=9D in the LANs (whic=
h is real world life, and will be for 3-5 years).

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Ole Jacobsen <olejacobsen@me.=
com>
Responder a: Ole Jacobsen <olejacobsen@me.com>
Fecha: lunes, 31 de julio de 2017, 23:01
Para: Ted Lemon <mellon@fugue.com>
CC: <ietf@ietf.org>
Asunto: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF =
Meetings

   =20
    You said:
    >=20
    > Brian, why on earth would we want to advertise IPv6 to IETF=20
    > attendees?  We invented IPv6.  If we really can't run a v6-only=20
    > network at IETF, what that says is that we have failed utterly and=20
    > expensively.  I do not believe that this is correct: IPv6 works very=
=20
    > well.
   =20
    Putting on my naive end-user hat:
   =20
    That might be true, but here is the thing: "The mission of the IETF is=
=20
    to make the INTERNET work better..." (my emphasis)
   =20
    For at least a decade now, I've been told that I should "just use=20
    IPv6" and some conferences have even "forced" me to do so.
   =20
    I always respond with this question: "Does running IPv6 allow me to=20
    connect to the Internet?" (meaning the v4 Internet for the most part).=
=20
    The answer always seems to be: "Yes, but you have to manually=20
    configure this and, oh by the way, this won't work at all and that app=
=20
    might not behave as expected."
   =20
    Demonstrating this to people who are experts seems like a waste
    of time.
   =20
    So it sounds to me like we HAVE indeed failed utterly and expensively.=
=20
    99% of Internet users do not have any idea what version of IP they are=
=20
    running just as they have no idea what a MAC address is or why/if they=
=20
    should care.
   =20
    I'd love to see IPv6 succeed, but it is apparently impossible to do so=
=20
    without teaching end-users a lot of stuff they really have no interest=
=20
    in or ability to learn. What a shame.
   =20
    Ole
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Mon Jul 31 14:23:10 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF573131CE1 for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 14:23:08 -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 Ye8cPdGyXA0I for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 14:23:07 -0700 (PDT)
Received: from mail-pf0-x241.google.com (mail-pf0-x241.google.com [IPv6:2607:f8b0:400e:c00::241]) (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 48F6A131C51 for <ietf@ietf.org>; Mon, 31 Jul 2017 14:23:07 -0700 (PDT)
Received: by mail-pf0-x241.google.com with SMTP id q85so27486046pfq.2 for <ietf@ietf.org>; Mon, 31 Jul 2017 14:23:07 -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=xYyZerdeQfnr3S9vccQp+uxtbt213zR8HcBQaZsYK7c=; b=MhsVqpioOaGzah9EeuReoDgZYEpqBpfkiJVw9cXU1sSDfSxgvIr6JyuWW7Y9hGaV1x HcDw9x5ysViE7AFBcPkprQte/LUQz3k9r5xFFSgyhqhLYJPczlNghZefGrnqtiZ1oQxJ B5iYpstz7YINK0AV0RhV8/QnZcL2VxdOfNN8zCnvbU/84DtSXkV6lZWcRdDFp7OLDpQa R0IKY1Dkxn8NYtlywX+RYBL1Wf2Lr8fHQ7HLS/Yn+dmiBmYRnEx9NZ7apGJZTjdGOQgx uQWX+Y7MURvAvQBZdR18FWdf1aX6/syo5106VK+GtLP4PtRrNp6qN6DvVm2PX7CI49kN xyrg==
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=xYyZerdeQfnr3S9vccQp+uxtbt213zR8HcBQaZsYK7c=; b=Vzm9VT9MemmsIG+vMuZ58R6mFo9q+nvDbfghjIfGJKjOt9VQVVPBHFnMyTgmFHdUys EpJuHBgkFzXzL/6hjkmUTrlFcruqOcbkJ3q8osy/Ck6QaORCECyxZY9TD8mS36vxb2+6 eqPYNbhb/WDHiYSlNknNanTDS8UTJCz9+FDKOXcD3XJE3Xn1ArayCn5TtSbhmspBtwBD Xg4ETpZRUvLRobASpywI4SyAn02v6kOLOOdU4QDpY6tcB4qUHDjbvDlat0Arilmq0/fK KdtP3UHhRUGtYSLsJVC7eCUWnyh3vij3UhFeWQPPfSMTHsHo6gruj9xBZ5SN1o8QRiko wUXg==
X-Gm-Message-State: AIVw113R6Oksr/ERneNnRtLhCyux1WEjNTazjSCUn+VmfiEpoRbdeId/ 5I/vjENEc9Zk1bbv
X-Received: by 10.84.229.71 with SMTP id d7mr18667204pln.274.1501536186699; Mon, 31 Jul 2017 14:23:06 -0700 (PDT)
Received: from ?IPv6:2406:e007:521f:1:28cc:dc4c:9703:6781? ([2406:e007:521f:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id g70sm25418009pgc.23.2017.07.31.14.23.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 31 Jul 2017 14:23:05 -0700 (PDT)
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: Ted Lemon <mellon@fugue.com>
Cc: ietf@ietf.org
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <8c6fca34-c108-cfbb-8023-a85f92e33fe9@gmail.com>
Date: Tue, 1 Aug 2017 09:23:03 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OLoCxT9htoLlrZgeNrULwG7EL2g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 21:23:09 -0000

On 01/08/2017 08:46, Ted Lemon wrote:
> On Jul 31, 2017, at 4:31 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>> And also, more and more people would
>> become aware that nat64 breaks stuff. I suppose that's good too. As advertising
>> for IPv6, it would do rather badly.
> 
> Brian, why on earth would we want to advertise IPv6 to IETF attendees?   We invented IPv6.   If we really can't run a v6-only network at IETF, what that says is that we have failed utterly and expensively.   I do not believe that this is correct: IPv6 works very well.

Indeed it does. I use it whenever possible. Dual stack works very well, too.

> The point of having NAT64 is that it lets us actually run without any IPv4 on the wire and see what happens.   If the only things that fail are things that go through NAT64, that's a good outcome, particularly if the number of things going through NAT64 that fail is small relative to the total number of things that go through it.

There we differ. But then, I wrote RFC1671.

   Brian


From nobody Mon Jul 31 15:40:04 2017
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD6611327EB for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 15:40:02 -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] 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 qTG2aq4GflI2 for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 15:40:01 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 CD0DC1327E5 for <ietf@ietf.org>; Mon, 31 Jul 2017 15:40:01 -0700 (PDT)
Received: from [10.32.63.47] (142-254-101-176.dsl.dynamic.fusionbroadband.com [142.254.101.176]) (authenticated bits=0) by mail.proper.com (8.15.2/8.14.9) with ESMTPSA id v6VMd5ps032454 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 31 Jul 2017 15:39:08 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 142-254-101-176.dsl.dynamic.fusionbroadband.com [142.254.101.176] claimed to be [10.32.63.47]
From: "Paul Hoffman" <paul.hoffman@vpnc.org>
To: "Ted Lemon" <mellon@fugue.com>
Cc: ietf@ietf.org
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Mon, 31 Jul 2017 15:39:56 -0700
Message-ID: <3A586681-AAEC-4395-B386-450C0AE7950F@vpnc.org>
In-Reply-To: <6C3D3B7C-9732-4BD2-97F6-F03A00CB6781@fugue.com>
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local> <6C3D3B7C-9732-4BD2-97F6-F03A00CB6781@fugue.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.6r5347)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AO7WPcN_fGt8CeQccipJaAEidw0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 22:40:03 -0000

On 31 Jul 2017, at 14:06, Ted Lemon wrote:

> The reason we are advocating this is not that we want you to debug the 
> user interface.   It's that we think it works.

There's that "we" again. I'd like to hear from others in the operational 
community who agree with you, given that what I have heard from that 
community is that it "almost" works for technical users and "might not 
work" for typical users.

--Paul Hoffman


From nobody Mon Jul 31 15:40:17 2017
Return-Path: <fenner@fenron.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F63D1327E5 for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 15:40:04 -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, 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 (1024-bit key) header.d=fenron.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 IqaKZMCeaJqS for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 15:40:02 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (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 8D5D11327E9 for <ietf@ietf.org>; Mon, 31 Jul 2017 15:40:02 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id x3so193124279oia.1 for <ietf@ietf.org>; Mon, 31 Jul 2017 15:40:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fenron.com; s=google;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=wO87qiMxEnbOjlGkZB5DmF0+OMfz/p5ef9uXVkSRBGI=; b=FqsIt2blYwpC4mKxg/b5+T1hviXo+JGkVYkxFQMspJlAH6h940OD9xFCa+/2F7CMEy IRDKTbYDdos49WBCa1lsZhjc9jfU5zYp/tDG4+ytQQCewMwb9Y5JWI5oWyqwhM26dJKT ykpQXEEHXKAY9el9ucqia4Uy/FcXQfGbI2jsA=
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=wO87qiMxEnbOjlGkZB5DmF0+OMfz/p5ef9uXVkSRBGI=; b=jLnWl2FjlhBpQEy1Br54cJQWTdDa9/kmvyK7gPa0L4RHV3UPS7JZkzUr1AfOtVWROe wnTZedGuMJ6yYTUmHnvkkSrTiQg0A4na/upi34P+cHxesiLHrnV0teELBYfUokHnqVTT L7QGgtN/AFIh53zvOaXsh4ffBtfr2b0Z37X4b49cz2RrBV3eIwYGDD2jdWJN9uzKd6cG GY6XjFEstL3OTyLu07262OmwTWVYXF6Z6tDjRqsGbT4U38IU+jOWrIG2nZ1LH+X9BHBI B3rxNZBFwsdR7FYLOICRrsILtJ3gs2jn7+YLj85a+3QGzYlhL8wo/kiVJ8z96FVcyEdx Bspw==
X-Gm-Message-State: AIVw112ZvIHJVmKs1KSIinq21eCgCL0V+sYH8YxA4FXBj4LoZVuJw06i m8ljrWHWRkNNM5gYhLxHIKb8n3+WlKza3o4=
X-Received: by 10.202.236.3 with SMTP id k3mr13985484oih.20.1501540801860; Mon, 31 Jul 2017 15:40:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.143.194 with HTTP; Mon, 31 Jul 2017 15:40:00 -0700 (PDT)
In-Reply-To: <6776ADFB-3EE0-4227-8A0F-7D140F7EB9F6@fugue.com>
References: <20170730231102.1014.qmail@ary.lan> <6776ADFB-3EE0-4227-8A0F-7D140F7EB9F6@fugue.com>
From: Bill Fenner <fenner@fenron.com>
Date: Mon, 31 Jul 2017 18:40:00 -0400
Message-ID: <CAATsVbaFO1waGhsPXzXxC1GNtj4pyrWR=MXj=N24aLpt2Mas5g@mail.gmail.com>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: Ted Lemon <mellon@fugue.com>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a1134e9a01c6f350555a4b608"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/E5Mm5NMlbpVIzcUh79OpEVLdB1w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 22:40:04 -0000

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

On Mon, Jul 31, 2017 at 6:05 AM, Ted Lemon <mellon@fugue.com> wrote:

> On Jul 30, 2017, at 10:44 AM, Bill Fenner <fenner@fenron.com> wrote:
>
> On the other hand, the corporate VPN I use publishes a support matrix on
> their public web site, and specifically says that IPv6 is not supported. I
> don't think they're embarrassed about it.
>
>
> Would you be willing to share with us the name of the vendor?
>

There's no reason to post it to this list specifically.  The ticket I filed
is in Lucy's list that Randy posted a link to; I also filed a ticket on the
noc ticket tracker in Seoul when there was a push to test nat64 at that
meeting.

Let's think like a VPN vendor, though: why not provide IP addresses of the
VPN server from the orchestrator to the client over the secure channel
you've already established, rather than allowing the client to perform DNS
lookups and perhaps succumb to an attack via that channel?  The thing
they're doing isn't dumb, it just doesn't work in a nat64 network.

  Bill

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On M=
on, Jul 31, 2017 at 6:05 AM, Ted Lemon <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:mellon@fugue.com" target=3D"_blank">mellon@fugue.com</a>&gt;</span> wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><=
div><div><span class=3D""><div><blockquote type=3D"cite">On Jul 30, 2017, a=
t 10:44 AM, Bill Fenner &lt;<a href=3D"mailto:fenner@fenron.com" target=3D"=
_blank">fenner@fenron.com</a>&gt; wrote:<div><blockquote type=3D"cite"><div=
>On the other hand, the corporate VPN I use publishes a support matrix on t=
heir public web site, and specifically says that IPv6 is not supported. I d=
on&#39;t think they&#39;re embarrassed about it.</div></blockquote></div></=
blockquote><br></div></span><div>Would you be willing to share with us the =
name of the vendor?</div></div></div></div></blockquote><div><br></div><div=
>There&#39;s no reason to post it to this list specifically.=C2=A0 The tick=
et I filed is in Lucy&#39;s list that Randy posted a link to; I also filed =
a ticket on the noc ticket tracker in Seoul when there was a push to test n=
at64 at that meeting.</div><div><br></div><div>Let&#39;s think like a VPN v=
endor, though: why not provide IP addresses of the VPN server from the orch=
estrator to the client over the secure channel you&#39;ve already establish=
ed, rather than allowing the client to perform DNS lookups and perhaps succ=
umb to an attack via that channel?=C2=A0 The thing they&#39;re doing isn&#3=
9;t dumb, it just doesn&#39;t work in a nat64 network.</div><div><br></div>=
<div>=C2=A0 Bill</div><div><br></div></div><br></div></div>

--001a1134e9a01c6f350555a4b608--


From nobody Mon Jul 31 17:28:01 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F9F1131CE3 for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 17:28:00 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 pJZdUIKgSbWl for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 17:27:58 -0700 (PDT)
Received: from mail-pf0-x22f.google.com (mail-pf0-x22f.google.com [IPv6:2607:f8b0:400e:c00::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 903FF131CDD for <ietf@ietf.org>; Mon, 31 Jul 2017 17:27:58 -0700 (PDT)
Received: by mail-pf0-x22f.google.com with SMTP id z129so746760pfb.3 for <ietf@ietf.org>; Mon, 31 Jul 2017 17:27:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=kbywvLBLDn1+LCzjnB7+1Xr3Nu4LXPtuKTGu0oY1jGw=; b=kyM9eBVQyQ/GR8BerNUNyUtgv8NoHDsTEqEA6LVLN4IakHYJtkmbuJNvw+3TArF3Cf 0UN3NqOPUkzz7eZg2phHkIk49QPxaWeyCDNeH7cAN2O3zXyrw+asw5flr0UrkX17W2ri IKm3g3mmqc2HoOfBrcg1HWJI6AonHi3F38uZbO02OwDfHPGLoVnusLp7ta5Obv29N9Ee FepF/gsglyZOqjNANULzLCmMAAAXiKoCpEa7Y12MR+1uVycYGrp1g+PKjoGV/BfKI/2n DygKxNKojABXm4ZInFoH8VW1/DaDI2QherjweLHKuR4rk7hXSDZlvSVHK47ncOiYwpGx O2uw==
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=kbywvLBLDn1+LCzjnB7+1Xr3Nu4LXPtuKTGu0oY1jGw=; b=nJvfq8oDyYq/0/oBy3Sp4NAGm9QkhF0hmS5+IPQrXSwKP9G24D3O79vxL/FlQjJT3D 6EO+qkvbgPn6SBJcKUcDnFxoh470Xy/dFhp6bZGxQeCV8fCiIubQYvGLc8iaJPvlpprh l3Mh10rfFfddoB9w2Vi8m9Cue0hqxAQWSmn8kNU/oUDcBATrzl/OAaGnHJsh8G9sh59J RgI58Vygkf1c0FlqhxvZlEAjVz8bxlSRJcxnAJiQKcxWY12amScJ5QBndcyaAFzDYe74 b51aX8fmFM1jZzbUQvY399I96vTYugA1G6T/QKEpvpjmZio/ytVFJP1j4HAjraj2pe85 riTw==
X-Gm-Message-State: AIVw111kY+KlELSPd2aW4sbFgmYsDJ8kNlr5QnSM/zX4JsA89L07Lex0 FvWibRt6xb5qy3p5fKZZSIrh1wztoOoW
X-Received: by 10.84.167.2 with SMTP id c2mr19479376plb.368.1501547278170; Mon, 31 Jul 2017 17:27:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.180.131 with HTTP; Mon, 31 Jul 2017 17:27:56 -0700 (PDT)
Received: by 10.100.180.131 with HTTP; Mon, 31 Jul 2017 17:27:56 -0700 (PDT)
In-Reply-To: <3A586681-AAEC-4395-B386-450C0AE7950F@vpnc.org>
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local> <6C3D3B7C-9732-4BD2-97F6-F03A00CB6781@fugue.com> <3A586681-AAEC-4395-B386-450C0AE7950F@vpnc.org>
From: Ted Lemon <mellon@fugue.com>
Date: Mon, 31 Jul 2017 20:27:56 -0400
Message-ID: <CAPt1N1m+gTtTtvFtrQR87W9kdo0iOc+Rh0QGRajeMCHxQ0GQOQ@mail.gmail.com>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: Paul Hoffman <paul.hoffman@vpnc.org>
Cc: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c145bae210e7f0555a63843"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CWl1FR9-gTRnU-vHkbiEG_K-AyI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Aug 2017 00:28:00 -0000

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

I'm not the author of the draft, Paul. I just got involved in the
conversation because a lot of things were being said with which I disagree.
So "we" are the people who think this is a good idea, many of whom have a
great deal of operational experience.

On Jul 31, 2017 6:40 PM, "Paul Hoffman" <paul.hoffman@vpnc.org> wrote:

> On 31 Jul 2017, at 14:06, Ted Lemon wrote:
>
> The reason we are advocating this is not that we want you to debug the
>> user interface.   It's that we think it works.
>>
>
> There's that "we" again. I'd like to hear from others in the operational
> community who agree with you, given that what I have heard from that
> community is that it "almost" works for technical users and "might not
> work" for typical users.
>
> --Paul Hoffman
>

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

<div dir=3D"auto">I&#39;m not the author of the draft, Paul. I just got inv=
olved in the conversation because a lot of things were being said with whic=
h I disagree. So &quot;we&quot; are the people who think this is a good ide=
a, many of whom have a great deal of operational experience.=C2=A0</div><di=
v class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Jul 31, 2017 6:40=
 PM, &quot;Paul Hoffman&quot; &lt;<a href=3D"mailto:paul.hoffman@vpnc.org">=
paul.hoffman@vpnc.org</a>&gt; wrote:<br type=3D"attribution"><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">On 31 Jul 2017, at 14:06, Ted Lemon wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The reason we are advocating this is not that we want you to debug the user=
 interface.=C2=A0 =C2=A0It&#39;s that we think it works.<br>
</blockquote>
<br>
There&#39;s that &quot;we&quot; again. I&#39;d like to hear from others in =
the operational community who agree with you, given that what I have heard =
from that community is that it &quot;almost&quot; works for technical users=
 and &quot;might not work&quot; for typical users.<br>
<br>
--Paul Hoffman<br>
</blockquote></div></div>

--94eb2c145bae210e7f0555a63843--


From nobody Mon Jul 31 17:29:35 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 487151326A5 for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 17:29:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-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 ALDsBia56sDZ for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 17:29:32 -0700 (PDT)
Received: from mail-pg0-x233.google.com (mail-pg0-x233.google.com [IPv6:2607:f8b0:400e:c05::233]) (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 DF5491326D4 for <ietf@ietf.org>; Mon, 31 Jul 2017 17:29:31 -0700 (PDT)
Received: by mail-pg0-x233.google.com with SMTP id y129so766962pgy.4 for <ietf@ietf.org>; Mon, 31 Jul 2017 17:29:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=o4WNhx7s+yA8GaEnRvyYfFKz50klBzmDUUTyZwu0rjk=; b=XBA7BGkkGt3OjwARIG8bpJ+orPLtVwI4A0cBmQtTBlJwQ9xi+12ZxCYFDgw806Rwjw GZjh7iYSWDkbgOQrBkF+RpGFXm44ofo3zwsm5KYtaU547p2VesoloxHyEPPP4oeeIwoI +PT9E30E496fkGwX7PCCqdP3WyQa2th26xUDK90KlD0BZRlAd4kztSi+jf7xvtp4Iiml sjXmk2pb5U4Hb1rxMXu/9QKkfTILUo3okqku3fnCZzdZ6ehKclkHjlJrSkL9dv63/7DB Q+ZHposEslJ+Em+sUAcMkN3GMJnF55HG2LZ9orDQzgvioSHimTGkt9x7C9txNJdKbXyc H/cw==
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=o4WNhx7s+yA8GaEnRvyYfFKz50klBzmDUUTyZwu0rjk=; b=kwEVZYXE3nxYJmFxqAhkUWiFLA+iWFVew5aV2iYlRHbX2/My8mpgDTvAEqNcDq3xmi LYlz6fWOLuUaIom2clNwBF4wOwLKXzYYaPBLbQ7OW9Ryaagcyj/HFWqPPqTOCPYfPT/e 32sYfI4skI/hn7nOqijeKEGsYP0xh/2w0mtmLxXae+2wQo/rVCyYRadCtt2ZuANLyqpj lowC6jmccdvv8hVD+sdoVss2Hm9wdUAYT3eyHGWVEOqJ4SS3P7iUxtEA8wX806352nsF KN3EjsolWtZjYo5Xjp/lInFFnlMoH0Z9BiQXCJiqep9KzXgfjqVKfDnaUXomV44Ig7aP qJqg==
X-Gm-Message-State: AIVw112NjiAQUXsfUAapppE9KAabd7VjTdnb1c4f0yFzAYDK0ECn0aRk yKxPKEGqJsLRyS4/OywH7F6cn6qm3glv
X-Received: by 10.84.218.195 with SMTP id g3mr19739484plm.386.1501547371441; Mon, 31 Jul 2017 17:29:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.180.131 with HTTP; Mon, 31 Jul 2017 17:29:30 -0700 (PDT)
Received: by 10.100.180.131 with HTTP; Mon, 31 Jul 2017 17:29:30 -0700 (PDT)
In-Reply-To: <CAATsVbaFO1waGhsPXzXxC1GNtj4pyrWR=MXj=N24aLpt2Mas5g@mail.gmail.com>
References: <20170730231102.1014.qmail@ary.lan> <6776ADFB-3EE0-4227-8A0F-7D140F7EB9F6@fugue.com> <CAATsVbaFO1waGhsPXzXxC1GNtj4pyrWR=MXj=N24aLpt2Mas5g@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Mon, 31 Jul 2017 20:29:30 -0400
Message-ID: <CAPt1N1kDS0+LCoqPsYTC-1Ssa8wGK4V=Coe7UiNpfyYSbnt9ug@mail.gmail.com>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: Bill Fenner <fenner@fenron.com>
Cc: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c1a32d6b0430a0555a63d35"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eq7MwtvSoYnVzrq44P4OuzFHmcw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Aug 2017 00:29:34 -0000

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

Bill, you said they don't support IPv6. Did you mean they don't support
NAT64?

On Jul 31, 2017 6:40 PM, "Bill Fenner" <fenner@fenron.com> wrote:

> On Mon, Jul 31, 2017 at 6:05 AM, Ted Lemon <mellon@fugue.com> wrote:
>
>> On Jul 30, 2017, at 10:44 AM, Bill Fenner <fenner@fenron.com> wrote:
>>
>> On the other hand, the corporate VPN I use publishes a support matrix on
>> their public web site, and specifically says that IPv6 is not supported. I
>> don't think they're embarrassed about it.
>>
>>
>> Would you be willing to share with us the name of the vendor?
>>
>
> There's no reason to post it to this list specifically.  The ticket I
> filed is in Lucy's list that Randy posted a link to; I also filed a ticket
> on the noc ticket tracker in Seoul when there was a push to test nat64 at
> that meeting.
>
> Let's think like a VPN vendor, though: why not provide IP addresses of the
> VPN server from the orchestrator to the client over the secure channel
> you've already established, rather than allowing the client to perform DNS
> lookups and perhaps succumb to an attack via that channel?  The thing
> they're doing isn't dumb, it just doesn't work in a nat64 network.
>
>   Bill
>
>
>

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

<div dir=3D"auto">Bill, you said they don&#39;t support IPv6. Did you mean =
they don&#39;t support NAT64?</div><div class=3D"gmail_extra"><br><div clas=
s=3D"gmail_quote">On Jul 31, 2017 6:40 PM, &quot;Bill Fenner&quot; &lt;<a h=
ref=3D"mailto:fenner@fenron.com">fenner@fenron.com</a>&gt; wrote:<br type=
=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=
=3D"gmail_extra"><div class=3D"gmail_quote">On Mon, Jul 31, 2017 at 6:05 AM=
, Ted Lemon <span dir=3D"ltr">&lt;<a href=3D"mailto:mellon@fugue.com" targe=
t=3D"_blank">mellon@fugue.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 style=3D"word-wrap:break-word"><div><div><span><div><blockq=
uote type=3D"cite">On Jul 30, 2017, at 10:44 AM, Bill Fenner &lt;<a href=3D=
"mailto:fenner@fenron.com" target=3D"_blank">fenner@fenron.com</a>&gt; wrot=
e:<div><blockquote type=3D"cite"><div>On the other hand, the corporate VPN =
I use publishes a support matrix on their public web site, and specifically=
 says that IPv6 is not supported. I don&#39;t think they&#39;re embarrassed=
 about it.</div></blockquote></div></blockquote><br></div></span><div>Would=
 you be willing to share with us the name of the vendor?</div></div></div><=
/div></blockquote><div><br></div><div>There&#39;s no reason to post it to t=
his list specifically.=C2=A0 The ticket I filed is in Lucy&#39;s list that =
Randy posted a link to; I also filed a ticket on the noc ticket tracker in =
Seoul when there was a push to test nat64 at that meeting.</div><div><br></=
div><div>Let&#39;s think like a VPN vendor, though: why not provide IP addr=
esses of the VPN server from the orchestrator to the client over the secure=
 channel you&#39;ve already established, rather than allowing the client to=
 perform DNS lookups and perhaps succumb to an attack via that channel?=C2=
=A0 The thing they&#39;re doing isn&#39;t dumb, it just doesn&#39;t work in=
 a nat64 network.</div><div><br></div><div>=C2=A0 Bill</div><div><br></div>=
</div><br></div></div>
</blockquote></div></div>

--94eb2c1a32d6b0430a0555a63d35--


From nobody Mon Jul 31 17:45:37 2017
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2DA9131CBD for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 17:45:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, 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 uNxlEbyWLt9z for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 17:45:34 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95C6C13178D for <ietf@ietf.org>; Mon, 31 Jul 2017 17:45:34 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id E1FDB2009E; Mon, 31 Jul 2017 20:47:19 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 9D7EE80243; Mon, 31 Jul 2017 20:45:33 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Carsten Bormann <cabo@tzi.org>
cc: ietf@ietf.org
Subject: Re: normative references to IANA registries
In-Reply-To: <E8859A9F-7539-4C6B-962C-56E6F3323C14@tzi.org>
References: <523.1501530916@obiwan.sandelman.ca> <E8859A9F-7539-4C6B-962C-56E6F3323C14@tzi.org>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Mon, 31 Jul 2017 20:45:33 -0400
Message-ID: <716.1501548333@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cVUsD_5vksNFZ-yvzXaRIWIPzCo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Aug 2017 00:45:36 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Carsten Bormann <cabo@tzi.org> wrote:
    >> So I wonder out loud: shouldn't all of the IANA registries have clear
    >> reference files that could be normatively referenced?

    > Try referencing, say, {{!IANA.cbor-tags}} =E2=80=94 it just works :-)

wow. I'm sure it's documented in some place so obvious I can't see it.
Is the "cbor-tags" part the last part of the IANA registry URL?

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -=3D IPv6 IoT consulting =3D-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAll/zy0ACgkQgItw+93Q
3WVZvgf/XMSSjiD4xtaU0tscry9kdeUATl/5sx4tOPG5tr7Mzm11aE5DbWkOGt7G
OAej+/eqoCX4B57A1Lk3OXBdKu2HXx9vlwKO9fZxHFbfkm812wAC1+0GcpRJCBNK
3gQ+ihzqZHdD6Kp4MlS5Zkpl02AXyUEbEMqM9AnyEreb/CR1T3SkIM84frnJJ74D
/oGafXUQapnSbPRe2uP90heY/CdGrv52I1ExDu84sSmS32PWQ9Tb4EL4O2RYvzfX
Ha8EbVWeoKPiH9lq+7kNMj3/82iqcdB8zOeGnW5aKIsr7swWqdFRcbguZ/frl7IV
XqqcUV1i+7FqSq8oHndzwupPOoGyqQ==
=+hu7
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Jul 31 18:51:02 2017
Return-Path: <fenner@fenron.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA20D1317A4 for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 18:50:58 -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, HTML_FONT_LOW_CONTRAST=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 (1024-bit key) header.d=fenron.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 v1WHDZsRZMzi for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 18:50:57 -0700 (PDT)
Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::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 61222131600 for <ietf@ietf.org>; Mon, 31 Jul 2017 18:50:57 -0700 (PDT)
Received: by mail-oi0-x235.google.com with SMTP id g131so2573238oic.3 for <ietf@ietf.org>; Mon, 31 Jul 2017 18:50:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fenron.com; s=google;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=rYFpnebt45zydNCyeT/o0Gtep+4oyL/Vn+xF31lZPk0=; b=fOR8bUqtX0xjCtvypzJaUsYHJfyDaiy+ua7db9pL1njcRMz7yt+WF/bZGNuDikPIy0 pQoeYXO1yevFzJEC3AJPBTIFyOGtiWFybG8edIUGRZgbyubp3d/OgM8FykEXmDqHrtGF 9F+vs8Tjp/TNDvaNdqYhi51C6VEAPKdX6GcNc=
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=rYFpnebt45zydNCyeT/o0Gtep+4oyL/Vn+xF31lZPk0=; b=gCgLbG4BMRAnUenaDxpf3zXzMrWgmkz3PQtBV53aMVwXVtGGeUlZY3w6nb9t05U6cY vSdXhi+bbE/Mk4H4p84og9hzO0km5t8wO5+mexydbp+w7MWh6agg4OPO+QYdGbVIgh8T FOBW+Xm13TyV0732kgHu+zeBwOBU0R7WFQsvP3NKW2AEf/lxTDkpp6ONrtkGoL8TOJYT 4Cbczkxh7/DFSvPjgmXZtzcR3WiELOLiPyO8OkGmMOzLN/SA/l/UtyYqEFw1eBy/fNMX vQxag5BM53aaFIBb8gsi+kVYajU8LW7KLkd/RjiyNz8Gm212h9XrHlwKl3T8v0exFSbV emlQ==
X-Gm-Message-State: AIVw113e7rCxzZW/gMlNihKCkna5azCaplb1CmAKn+jKRZUit8QuH3S7 AXGxhXBUWbwTt0hamUtMmWLVbJ/u3UqA
X-Received: by 10.202.67.66 with SMTP id q63mr15138954oia.33.1501552256789; Mon, 31 Jul 2017 18:50:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.143.194 with HTTP; Mon, 31 Jul 2017 18:50:55 -0700 (PDT)
In-Reply-To: <CAPt1N1kDS0+LCoqPsYTC-1Ssa8wGK4V=Coe7UiNpfyYSbnt9ug@mail.gmail.com>
References: <20170730231102.1014.qmail@ary.lan> <6776ADFB-3EE0-4227-8A0F-7D140F7EB9F6@fugue.com> <CAATsVbaFO1waGhsPXzXxC1GNtj4pyrWR=MXj=N24aLpt2Mas5g@mail.gmail.com> <CAPt1N1kDS0+LCoqPsYTC-1Ssa8wGK4V=Coe7UiNpfyYSbnt9ug@mail.gmail.com>
From: Bill Fenner <fenner@fenron.com>
Date: Mon, 31 Jul 2017 21:50:55 -0400
Message-ID: <CAATsVbZpzv2e0qNb7L6y1tG87NfbXRNBSHkW-1CUoG_6L1kSkQ@mail.gmail.com>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: Ted Lemon <mellon@fugue.com>
Cc: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a113ddef2e0ca6c0555a7604a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dNhg2z6l_cEWOYeA8JBzBI3Jim0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Aug 2017 01:50:59 -0000

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

On Mon, Jul 31, 2017 at 8:29 PM, Ted Lemon <mellon@fugue.com> wrote:

> Bill, you said they don't support IPv6. Did you mean they don't support
> NAT64?
>

Perhaps I'm misreading the support matrix, but there's a list of versions
across the top and services across the side, and I think it says

Feature

IPv6 Support
  CoolOS X.0 CoolOS Y.0 CoolOS Z.0 CoolOS Z.1 CoolOS Q.0
SSL VPN No No No No No

And I take that to mean "in no version of CoolOS, including the
recently-released Q.0, is SSL VPN supported under IPv6".  And I think that
the CoolOS SSL VPN client needs to support IPv6 in order to work on an
IPv6-only network.

  Bill


> On Jul 31, 2017 6:40 PM, "Bill Fenner" <fenner@fenron.com> wrote:
>
>> On Mon, Jul 31, 2017 at 6:05 AM, Ted Lemon <mellon@fugue.com> wrote:
>>
>>> On Jul 30, 2017, at 10:44 AM, Bill Fenner <fenner@fenron.com> wrote:
>>>
>>> On the other hand, the corporate VPN I use publishes a support matrix on
>>> their public web site, and specifically says that IPv6 is not supported. I
>>> don't think they're embarrassed about it.
>>>
>>>
>>> Would you be willing to share with us the name of the vendor?
>>>
>>
>> There's no reason to post it to this list specifically.  The ticket I
>> filed is in Lucy's list that Randy posted a link to; I also filed a ticket
>> on the noc ticket tracker in Seoul when there was a push to test nat64 at
>> that meeting.
>>
>> Let's think like a VPN vendor, though: why not provide IP addresses of
>> the VPN server from the orchestrator to the client over the secure channel
>> you've already established, rather than allowing the client to perform DNS
>> lookups and perhaps succumb to an attack via that channel?  The thing
>> they're doing isn't dumb, it just doesn't work in a nat64 network.
>>
>>   Bill
>>
>>
>>

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On M=
on, Jul 31, 2017 at 8:29 PM, Ted Lemon <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:mellon@fugue.com" target=3D"_blank">mellon@fugue.com</a>&gt;</span> wro=
te:<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"><div dir=3D"auto">=
Bill, you said they don&#39;t support IPv6. Did you mean they don&#39;t sup=
port NAT64?</div></blockquote><div><br></div><div>Perhaps I&#39;m misreadin=
g the support matrix, but there&#39;s a list of versions across the top and=
 services across the side, and I think it says</div><div><br></div><div><ta=
ble class=3D"gmail-jiveBorder" border=3D"1" cellspacing=3D"0" cellpadding=
=3D"3" style=3D"box-sizing:inherit;border-collapse:collapse;color:rgb(51,51=
,51);font-family:Lato,&quot;Helvetica Neue&quot;,Helvetica,Arial,sans-serif=
;font-size:14px;width:874.182px;border:1px solid rgb(127,127,127);height:46=
6.182px"><tbody style=3D"box-sizing:inherit"><tr style=3D"box-sizing:inheri=
t"><th align=3D"left" valign=3D"middle" style=3D"box-sizing:inherit;padding=
:2.5px 5px;text-align:left;margin:0px;border:1px solid rgb(234,234,234);lin=
e-height:20px;word-break:normal;background-color:rgb(102,144,188)"><span st=
yle=3D"box-sizing:inherit;line-height:1.2;color:rgb(255,255,255)">Feature</=
span></th><th colspan=3D"5" align=3D"center" valign=3D"middle" style=3D"box=
-sizing:inherit;padding:2.5px 5px;text-align:center;margin:0px;border:1px s=
olid rgb(234,234,234);line-height:20px;word-break:normal;background-color:r=
gb(102,144,188)"><p style=3D"box-sizing:inherit;margin:0px;padding:0px;line=
-height:21px"><span style=3D"box-sizing:inherit;line-height:1.2;color:rgb(2=
55,255,255)">IPv6 Support</span></p></th></tr><tr style=3D"box-sizing:inher=
it"><td style=3D"box-sizing:inherit;padding:2.5px 5px;border:1px solid rgb(=
234,234,234);line-height:20px;word-break:normal;background-color:rgb(102,14=
4,188)">=C2=A0</td><td style=3D"box-sizing:inherit;padding:2.5px 5px;border=
:1px solid rgb(234,234,234);line-height:20px;word-break:normal;background-c=
olor:rgb(102,144,188);text-align:center"><span style=3D"box-sizing:inherit;=
line-height:1.2;color:rgb(255,255,255)">CoolOS X.0</span></td><td style=3D"=
box-sizing:inherit;padding:2.5px 5px;border:1px solid rgb(234,234,234);line=
-height:20px;word-break:normal;background-color:rgb(102,144,188);text-align=
:center"><font color=3D"#ffffff">CoolOS Y.0</font></td><td style=3D"box-siz=
ing:inherit;padding:2.5px 5px;border:1px solid rgb(234,234,234);line-height=
:20px;word-break:normal;background-color:rgb(102,144,188);text-align:center=
"><font color=3D"#ffffff">CoolOS Z.0</font></td><td style=3D"box-sizing:inh=
erit;padding:2.5px 5px;border:1px solid rgb(234,234,234);line-height:20px;w=
ord-break:normal;background-color:rgb(102,144,188);text-align:center"><span=
 style=3D"box-sizing:inherit;line-height:1.2;color:rgb(255,255,255)">CoolOS=
 Z.1</span></td><td style=3D"box-sizing:inherit;padding:2.5px 5px;border:1p=
x solid rgb(234,234,234);line-height:20px;word-break:normal;background-colo=
r:rgb(102,144,188);text-align:center"><span style=3D"box-sizing:inherit;lin=
e-height:1.2;color:rgb(255,255,255)">CoolOS Q.0</span></td></tr><tr style=
=3D"box-sizing:inherit"><td style=3D"box-sizing:inherit;padding:2.5px 5px;b=
order:1px solid rgb(234,234,234);line-height:20px;word-break:normal"></td><=
td align=3D"center" style=3D"box-sizing:inherit;padding:2.5px 5px;border:1p=
x solid rgb(234,234,234);line-height:20px;word-break:normal"></td><td align=
=3D"center" style=3D"box-sizing:inherit;padding:2.5px 5px;border:1px solid =
rgb(234,234,234);line-height:20px;word-break:normal"></td><td align=3D"cent=
er" style=3D"box-sizing:inherit;padding:2.5px 5px;border:1px solid rgb(234,=
234,234);line-height:20px;word-break:normal"></td><td align=3D"center" styl=
e=3D"box-sizing:inherit;padding:2.5px 5px;border:1px solid rgb(234,234,234)=
;line-height:20px;word-break:normal"></td><td align=3D"center" style=3D"box=
-sizing:inherit;padding:2.5px 5px;border:1px solid rgb(234,234,234);line-he=
ight:20px;word-break:normal"></td></tr><tr style=3D"box-sizing:inherit"><td=
 style=3D"box-sizing:inherit;padding:2.5px 5px;border:1px solid rgb(234,234=
,234);line-height:20px;word-break:normal">SSL VPN</td><td align=3D"center" =
style=3D"box-sizing:inherit;padding:2.5px 5px;border:1px solid rgb(234,234,=
234);line-height:20px;word-break:normal">No</td><td align=3D"center" style=
=3D"box-sizing:inherit;padding:2.5px 5px;border:1px solid rgb(234,234,234);=
line-height:20px;word-break:normal">No</td><td align=3D"center" style=3D"bo=
x-sizing:inherit;padding:2.5px 5px;border:1px solid rgb(234,234,234);line-h=
eight:20px;word-break:normal">No</td><td align=3D"center" style=3D"box-sizi=
ng:inherit;padding:2.5px 5px;border:1px solid rgb(234,234,234);line-height:=
20px;word-break:normal">No</td><td align=3D"center" style=3D"box-sizing:inh=
erit;padding:2.5px 5px;border:1px solid rgb(234,234,234);line-height:20px;w=
ord-break:normal">No</td></tr></tbody></table></div><div><br></div><div>And=
 I take that to mean &quot;in no version of CoolOS, including the recently-=
released Q.0, is SSL VPN supported under IPv6&quot;.=C2=A0 And I think that=
 the CoolOS SSL VPN client needs to support IPv6 in order to work on an IPv=
6-only network.</div><div><br></div><div>=C2=A0 Bill</div><div>=C2=A0</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"><div class=3D"gmail-HOEnZ=
b"><div class=3D"gmail-h5"><div class=3D"gmail_extra"><div class=3D"gmail_q=
uote">On Jul 31, 2017 6:40 PM, &quot;Bill Fenner&quot; &lt;<a href=3D"mailt=
o:fenner@fenron.com" target=3D"_blank">fenner@fenron.com</a>&gt; wrote:<br =
type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div=
 dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On Mon, =
Jul 31, 2017 at 6:05 AM, Ted Lemon <span dir=3D"ltr">&lt;<a href=3D"mailto:=
mellon@fugue.com" target=3D"_blank">mellon@fugue.com</a>&gt;</span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex"><div style=3D"word-wra=
p:break-word"><div><div><span><div><blockquote type=3D"cite">On Jul 30, 201=
7, at 10:44 AM, Bill Fenner &lt;<a href=3D"mailto:fenner@fenron.com" target=
=3D"_blank">fenner@fenron.com</a>&gt; wrote:<div><blockquote type=3D"cite">=
<div>On the other hand, the corporate VPN I use publishes a support matrix =
on their public web site, and specifically says that IPv6 is not supported.=
 I don&#39;t think they&#39;re embarrassed about it.</div></blockquote></di=
v></blockquote><br></div></span><div>Would you be willing to share with us =
the name of the vendor?</div></div></div></div></blockquote><div><br></div>=
<div>There&#39;s no reason to post it to this list specifically.=C2=A0 The =
ticket I filed is in Lucy&#39;s list that Randy posted a link to; I also fi=
led a ticket on the noc ticket tracker in Seoul when there was a push to te=
st nat64 at that meeting.</div><div><br></div><div>Let&#39;s think like a V=
PN vendor, though: why not provide IP addresses of the VPN server from the =
orchestrator to the client over the secure channel you&#39;ve already estab=
lished, rather than allowing the client to perform DNS lookups and perhaps =
succumb to an attack via that channel?=C2=A0 The thing they&#39;re doing is=
n&#39;t dumb, it just doesn&#39;t work in a nat64 network.</div><div><br></=
div><div>=C2=A0 Bill</div><div><br></div></div><br></div></div>
</blockquote></div></div>
</div></div></blockquote></div><br></div></div>

--001a113ddef2e0ca6c0555a7604a--


From nobody Mon Jul 31 19:10:18 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF40B131600 for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 19:10:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 3zVWjc2wRB2u for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 19:10:15 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 79C47127ABE for <ietf@ietf.org>; Mon, 31 Jul 2017 19:10:15 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dcMdQ-0005GX-Iu; Tue, 01 Aug 2017 02:10:12 +0000
Date: Tue, 01 Aug 2017 11:10:10 +0900
Message-ID: <m2r2wwt4vx.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Cc: Ted Lemon <mellon@fugue.com>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
In-Reply-To: <3A586681-AAEC-4395-B386-450C0AE7950F@vpnc.org>
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local> <6C3D3B7C-9732-4BD2-97F6-F03A00CB6781@fugue.com> <3A586681-AAEC-4395-B386-450C0AE7950F@vpnc.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Dr0-EducfG7Aen79oprmiXWe1yo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Aug 2017 02:10:17 -0000

Paul Hoffman wrote:
> On 31 Jul 2017, at 14:06, Ted Lemon wrote:
>> The reason we are advocating this is not that we want you to debug
>> the user interface.  It's that we think it works.
> There's that "we" again. I'd like to hear from others in the
> operational community who agree with you, given that what I have heard
> from that community is that it "almost" works for technical users and
> "might not work" for typical users.

i'm an operator who is fairly new to this ipv6 stuff; we only deployed
it commercially across our backbone (and through the cpe) in 1997.

in our meager experience, pure ipv6 with no hack to get to the ipv4
internet is not viable from the user perspective, period.  it won't be
for many years.  yes, this is a tragic failure; and we know where the
root causes lie.

nat64/dns64 is useful in constrained circumstances.  the ietf meeting
network is not one of them; as there is far too wide a variety of users,
some with laptops they can't even control due to IT departments, many
use vpns, applications are still incompatible, ...  this is yet another
tragedy.

the biggest obstacle to improvement on both these fronts is the denial
that there are serious problems, and hence far too little serious work
being done to ameliorate them.

but, no matter how hard we work, there is not going to be a magic day
when it all just works.  ipv6 is on-the-wire incompatible with ipv4;
so it is gonna be hacks; and hacks are tecnhnical debt.

randy


From nobody Mon Jul 31 20:22:12 2017
Return-Path: <akatlas@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29844131CE3 for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 20:22: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 6kOJFVvbWxc7 for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 20:22:09 -0700 (PDT)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::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 9BF85127ABE for <ietf@ietf.org>; Mon, 31 Jul 2017 20:22:08 -0700 (PDT)
Received: by mail-wm0-x234.google.com with SMTP id t201so2743941wmt.1 for <ietf@ietf.org>; Mon, 31 Jul 2017 20:22:08 -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=6Q+ddhg1MQBbFm9mSCSCOwbJKWjUBGjfHOa5a5l1L6o=; b=Uje8Jix4rEGPP6ByykZpG+i9JydLmMb4JZlb5d7lh6hH0cbwWW8UYGiIzQI5b9WQfH IBtZwZ5w0icHzJYWP3rZ7eoQYmZAuhk+5Hww616uW8JNXxK0Wcew9QlBsKY8eJ9YIT95 q1aKpXCw1qTiG/+C1cXfwyMEdnpbc5AJAvU5S6ASnp4zoBUFAd0JmB+iUwkbFZ4rBOVH W82AeGqi/AH9IVlsIntVvAfBfh+xY/cEyNm75eDKn7R5qhiyKJHQv+/IiPA/HJd/olmI icCKV5kGqdUkZqd4yDppZ258WBJ7EcJ7kHDrqhqlZ+EVdKhzy6ax7LDuO4gXtaKhxrf/ 0p+w==
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=6Q+ddhg1MQBbFm9mSCSCOwbJKWjUBGjfHOa5a5l1L6o=; b=oUdj0BSIAESjv3E/3osvxJXt216F1sruWryOpVO+Ub9hORVvtqH667e+XcjG9COl6T srQTw77mMlYOvGYHCfi2e2UxUifNQRGi0PvkMPWjqFAH1Rg8F/sjzUMoAlkF5+6zwY9b SdeR1mkfo8kt/i7lSj7Ek46OX3+w3PGrBNTa/QRlPx1d2x3VnFBr70avIn4CNzKB39G7 iC2jJPkG63usp7BWr4HYTTcajIfiRf8FaJMDIE5iP6TBNxsTm9Sjs9lvx+1NSt5lPjJv aORYQrpZyIo3up3TMEAb9FNB3uUNxrToeDos9WDZLL1WzEXktAumt7AOAxcQEaTIl5Q6 ns8A==
X-Gm-Message-State: AIVw112mKjHjalINm26bEunusQqgqCUGxsGPEgwRThKH951xsmRR+Us+ BgKECvLAQaIP+Ky3/8gckpQGODv3IrnR
X-Received: by 10.28.193.138 with SMTP id r132mr267066wmf.155.1501557727038; Mon, 31 Jul 2017 20:22:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.183.1 with HTTP; Mon, 31 Jul 2017 20:22:06 -0700 (PDT)
In-Reply-To: <3A586681-AAEC-4395-B386-450C0AE7950F@vpnc.org>
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local> <6C3D3B7C-9732-4BD2-97F6-F03A00CB6781@fugue.com> <3A586681-AAEC-4395-B386-450C0AE7950F@vpnc.org>
From: Alia Atlas <akatlas@gmail.com>
Date: Mon, 31 Jul 2017 23:22:06 -0400
Message-ID: <CAG4d1rd=0n_-s2ijhC+u=BCj=X90Nj_op4CHKr=-9WdymXBFLw@mail.gmail.com>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: Paul Hoffman <paul.hoffman@vpnc.org>
Cc: Ted Lemon <mellon@fugue.com>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c0d4c06ee12f90555a8a665"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OzI0K5KeD1NVYMkUrHu0uQVbCYA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Aug 2017 03:22:10 -0000

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

Paul,

On Mon, Jul 31, 2017 at 6:39 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> On 31 Jul 2017, at 14:06, Ted Lemon wrote:
>
> The reason we are advocating this is not that we want you to debug the
>> user interface.   It's that we think it works.
>>
>
> There's that "we" again. I'd like to hear from others in the operational
> community who agree with you, given that what I have heard from that
> community is that it "almost" works for technical users and "might not
> work" for typical users.


The last Routing Area Working Group Chairs training/workshop, we had
information about the increasing deployment of
IPv6 - including to many many many consumers.  I haven't gotten the video
up quite yet - but this conversation is making
me prioritize it.  IPv6 growth is extremely significant.

It may be that there are some IETFers who run such special applications or
old software ( ascii art programs ;-) ) that we will
encounter different or additional issues. Granted, I didn't take advantage
of my ability to try out the IPv6 SSIDs made available
this past IETF - but this conversation is enough to convince not merely to
do so, but to consider printing out stickers - "I
upgraded to the modern Internet - with several checkboxes (IPv6, DNSsec
perhaps, etc.)."  I welcome inspiration there.

To claim that IPv6 just "almost works" for technical users is to ignore the
world outside our email lists.

Regards,
Alia



> --Paul Hoffman
>
>

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

<div dir=3D"ltr">Paul,<div class=3D"gmail_extra"><br><div class=3D"gmail_qu=
ote">On Mon, Jul 31, 2017 at 6:39 PM, Paul Hoffman <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:paul.hoffman@vpnc.org" target=3D"_blank">paul.hoffman@vpnc.=
org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"=
">On 31 Jul 2017, at 14:06, Ted Lemon wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The reason we are advocating this is not that we want you to debug the user=
 interface.=C2=A0 =C2=A0It&#39;s that we think it works.<br>
</blockquote>
<br></span>
There&#39;s that &quot;we&quot; again. I&#39;d like to hear from others in =
the operational community who agree with you, given that what I have heard =
from that community is that it &quot;almost&quot; works for technical users=
 and &quot;might not work&quot; for typical users.</blockquote><div><br></d=
iv><div>The last Routing Area Working Group Chairs training/workshop, we ha=
d information about the increasing deployment of</div><div>IPv6 - including=
 to many many many consumers.=C2=A0 I haven&#39;t gotten the video up quite=
 yet - but this conversation is making</div><div>me prioritize it.=C2=A0 IP=
v6 growth is extremely significant.</div><div><br></div><div>It may be that=
 there are some IETFers who run such special applications or old software (=
 ascii art programs ;-) ) that we will</div><div>encounter different or add=
itional issues. Granted, I didn&#39;t take advantage of my ability to try o=
ut the IPv6 SSIDs made available</div><div>this past IETF - but this conver=
sation is enough to convince not merely to do so, but to consider printing =
out stickers - &quot;I</div><div>upgraded to the modern Internet - with sev=
eral checkboxes (IPv6, DNSsec perhaps, etc.).&quot; =C2=A0I welcome inspira=
tion there.</div><div><br></div><div>To claim that IPv6 just &quot;almost w=
orks&quot; for technical users is to ignore the world outside our email lis=
ts.</div><div><br></div><div>Regards,</div><div>Alia=C2=A0</div><div><br></=
div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"HOEnZb">=
<font color=3D"#888888">
--Paul Hoffman<br>
<br>
</font></span></blockquote></div><br></div></div>

--94eb2c0d4c06ee12f90555a8a665--


From nobody Mon Jul 31 23:06:57 2017
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E1B5124234 for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 23:06:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.4
X-Spam-Level: 
X-Spam-Status: No, score=-5.4 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, RP_MATCHES_RCVD=-0.001, 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 mQDjPAn3Dqvp for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 23:06:54 -0700 (PDT)
Received: from relais-inet.orange.com (mta136.mail.business.static.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01F30131748 for <ietf@ietf.org>; Mon, 31 Jul 2017 23:06:54 -0700 (PDT)
Received: from opfednr00.francetelecom.fr (unknown [xx.xx.xx.64]) by opfednr23.francetelecom.fr (ESMTP service) with ESMTP id EF790C0509; Tue,  1 Aug 2017 08:06:51 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.57]) by opfednr00.francetelecom.fr (ESMTP service) with ESMTP id C50A61A006B; Tue,  1 Aug 2017 08:06:51 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM23.corporate.adroot.infra.ftgroup ([fe80::787e:db0c:23c4:71b3%19]) with mapi id 14.03.0352.000; Tue, 1 Aug 2017 08:06:51 +0200
From: <mohamed.boucadair@orange.com>
To: "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Thread-Topic: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Thread-Index: AQHTCjv1UMUusSX/KkuDQRB83xzbqqJuRiMAgAAD94CAAATogIAAsNww
Date: Tue, 1 Aug 2017 06:06:50 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93300A0155F5@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local> <62FE7E9A-9CC0-4DE6-93C6-61A08AC95281@consulintel.es>
In-Reply-To: <62FE7E9A-9CC0-4DE6-93C6-61A08AC95281@consulintel.es>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.1]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AXZiqZD9gpYmig573Lxe2E4gIrM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Aug 2017 06:06:56 -0000

SGkgSm9yZGksDQoNClBsZWFzZSBzZWUgaW5saW5lLiANCg0KQ2hlZXJzLA0KTWVkDQoNCj4gLS0t
LS1NZXNzYWdlIGQnb3JpZ2luZS0tLS0tDQo+IERlwqA6IGlldGYgW21haWx0bzppZXRmLWJvdW5j
ZXNAaWV0Zi5vcmddIERlIGxhIHBhcnQgZGUgSk9SREkgUEFMRVQNCj4gTUFSVElORVoNCj4gRW52
b3nDqcKgOiBsdW5kaSAzMSBqdWlsbGV0IDIwMTcgMjM6MTgNCj4gw4DCoDogaWV0ZkBpZXRmLm9y
Zw0KPiBPYmpldMKgOiBSZTogUkVTRU5ESU5HIC0gSW5jcmVtZW50YWwgRGVwbG95bWVudCBvZiBJ
UHY2LW9ubHkgV2ktRmkgZm9yIElFVEYNCj4gTWVldGluZ3MNCj4gDQo+IE5BVDY0IHdhcyBpbnZl
bnRlZCBmb3IgYSBzcGVjaWZpYyBjYXNlICh3aGVuIGFwcHMgdXNlIEROUyBhbmQgdGhlIHJpZ2h0
DQo+IEFQSXMpLg0KDQpbTWVkXSBUaGlzIG1heSBiZSBtaXNpbnRlcnByZXRlZCBhcyB0aGVyZSBp
cyBhIGRlcGVuZGVuY3kgb2YgTkFUNjQgb24gRE5TLiBUaGlzIGlzIG5vdCB0ZWNobmljYWxseSB0
cnVlLiBUaGlzIHdhcyBjbGFyaWZpZWQgaW4gaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3Jm
YzY4ODkgDQoNCiAgIFRoaXMgYXBwcm9hY2ggaXMgcHJhZ21hdGljIGluIHRoZSBzZW5zZSB0aGF0
IHRoZXJlIGlzIG5vIGRlcGVuZGVuY3kNCiAgIG9uIEROUyBpbXBsZW1lbnRhdGlvbiBmb3IgdGhl
IHN1Y2Nlc3NmdWwgTkFUIGhhbmRsaW5nLiAgQXMgbG9uZyBhcw0KICAgdGhlcmUgaXMgYSBmdW5j
dGlvbiAoZS5nLiwgRE5TNjQgW1JGQzYxNDddIG9yIG90aGVyIG1lYW5zKSB0aGF0IGNhbg0KICAg
Y29uc3RydWN0IGFuIElQdjYtZW1iZWRkZWQgSVB2NCBhZGRyZXNzIHdpdGggYSBwcmUtY29uZmln
dXJlZCBJUHY2DQogICBwcmVmaXgsIGFuIElQdjQgYWRkcmVzcyBhbmQgYSBzdWZmaXggKHJlZmVy
IHRvIFtSRkM2MDUyXSksIE5BVDY0IHdpbGwNCiAgIHdvcmsganVzdCBmaW5lLg0KDQpGV0lXLCB0
aGVyZSBhcmUgZXZlbiBOQVQ2NCBkZXBsb3ltZW50cyB0aGF0IGRvIG5vdCBldmVuIHJlbHkgb24g
RE5TNjQuIA0KDQo+IA0KPiBXZSByZWFsaXplZCB0aGVuIHRoYXQgYXBwL2RldmljZXMgdmVuZG9y
cyBhcmUgbGF6eSwgb3IganVzdCB0aGV5IGFyZSBvdXQNCj4gb2YgdGhlIG1hcmtldCwgc28gd2Ug
aW52ZW50ZWQgNDY0WExBVCwgd2hpY2ggdXNlcyB0aGUgc2FtZSBjb25jZXB0IGFzDQo+IE5BVDY0
L0ROUzY0LCBidXQgaW1wcm92ZXMgaXQgYnkgdXNpbmcgdGhlIENMQVQsIGEgc21hbGwgZGFlbW9u
IGNvZGUgaW4gdGhlDQo+IE9TIG9yIHRoZSBDUEUgdG8gc29sdmUgdGhlIHByb2JsZW1zIG9mIHRo
ZSBsaXRlcmFsIGFkZHJlc3NlcyBhbmQgbm9uLUFQSXMNCj4gYXBwcy9kZXZpY2VzLg0KPiANCj4g
V2UgZG9u4oCZdCBuZWVkIHRvIHRlbGwgdGhlIGN1c3RvbWVycyB0byBkaXNhYmxlIElQdjQgaW4g
dGhlaXIgTEFOcywgd2UgbmVlZA0KPiB0byBtYWtlIHN1cmUgdGhhdCB3ZSBkZXBsb3kgQ1BFcyB0
aGF0IHN1cHBvcnQgQ0xBVC4NCg0KW01lZF0gSXMgdGhlcmUgYW55IENQRS1iYXNlZCA0NjR4bGF0
IGRlcGxveW1lbnQgb3V0IHRoZXJlPyANCg0KIFRoaXMgd2F5LCB1c2VycyBkb27igJl0DQo+IG5l
ZWQgdG8gdGhyb3cgYXdheSBvbGQgZGV2aWNlcyBvciBhcHBzLCBuZWl0aGVyIGxlYXJuIGFueXRo
aW5nIGFib3V0IElQdjQNCj4gb3IgSVB2NiwgYW5kIGV2ZXJ5Ym9keSBpcyBoYXBweS4NCj4gDQo+
IFdlIGFyZSB0cnlpbmcgdG8gc29sdmUgYSBwcm9ibGVtIHdpdGggTkFUNjQgd2hpY2ggd2Uga25l
dyBzaW5jZSBpdCB3YXMNCj4gaW52ZW50ZWQgdGhhdCBpdCBjYW7igJl0IGJlIHNvbHZlZC4gV2Ug
ZG9u4oCZdCBoYXZlIHRoZSB0aW1lICh1bmxlc3Mgc29tZQ0KPiBtYWdpYyBpcyBkaXNjb3ZlcmVk
KSB0byBub3cgdGVsbCBldmVyeSBJU1AgdGhhdCBpcyBkZXBsb3lpbmcgSVB2NiBhbmQNCj4gTkFU
NjQsIHRvIGluc3RlYWQgb2YgTkFUNjQgaGF2ZSBzb21ldGhpbmcgZGlmZmVyZW50Lg0KDQpbTWVk
XSBUaGVzZSBvcGVyYXRvcnMgKHdpdGggQ1BFcykgYXJlIGFscmVhZHkgZG9pbmcgc29tZXRoaW5n
ICpkaWZmZXJlbnQqOiBEUy1MaXRlIGFuZCB0aGUgbGlrZS4gTkFUNjQgaXMgd2lkZWx5IGRlcGxv
eWVkIGluIGNlbGx1bGFyIG5ldHdvcmtzIChob3N0LWJhc2VkIG1vZGVsKSwgd2hpY2ggaXMgcmVh
bGx5IHN0cmFpZ2h0Zm9yd2FyZC4gICANCg0KIFRoZSBzb2x1dGlvbiBpcw0KPiB0aGVyZSwgaWYg
Q1BFIHZlbmRvcnMgaW1wbGVtZW50IGl0LCBhbmQgd2UgYXJlIHRhbGtpbmcgYWJvdXQgYW4gYXZh
aWxhYmxlDQo+IG9wZW4gc291cmNlIGNvZGUgKHNldmVyYWwgaW1wbGVtZW50YXRpb25zKSB0aGF0
IHRha2UgYSBmZXcgYnl0ZXMuDQo+IA0KPiBXZSBhcmUgYWxyZWFkeSBkb2luZyB0aGlzIGVmZm9y
dCBpbiB2Nm9wcywgSSBzdGFydGVkIHRyeWluZyB0byB0ZWxsIHRoZQ0KPiBSRkM3MDg0IGFib3V0
IHRoZSBuZWVkIHRvIHVwZGF0ZSBpdCwgYnV0IGRpZG7igJl0IHN1Y2NlZWRlZC4gSXQgc2VlbXMg
dGhhdA0KPiBub3cgd2UgbWF5IHdhbnQgdG8gaGF2ZSBpbnN0ZWFkIG9mIGEgQ1BFIHJlcXVpcmVt
ZW50cyBpbmNsdWRpbmcgdGhpcywgYW4NCj4gYWRkaXRpb25hbCBkb2N1bWVudCB0byBiZSBhIG11
c3QgZm9yIENQRSB2ZW5kb3JzIHRvIHN1cHBvcnQgaXQsIGluIGNhc2UNCj4gdGhlIENQRSBleHBl
Y3RzIOKAnElQdjQgb2xkIGRldmljZXMgYW5kIGFwcHPigJ0gaW4gdGhlIExBTnMgKHdoaWNoIGlz
IHJlYWwNCj4gd29ybGQgbGlmZSwgYW5kIHdpbGwgYmUgZm9yIDMtNSB5ZWFycykuDQoNCltNZWRd
IEknbSBhZnJhaWQgd2UgZG9uJ3QgbmVlZCBpdC4gVGhlIElFVEYgYWxyZWFkeSBzcGVjaWZpZWQg
dG9vbHMgdG8gYWRkcmVzcyB0aGF0IGNhc2UgKERTLUxpdGUsIE1BUC1FKS4NCg0KPiANCj4gUmVn
YXJkcywNCj4gSm9yZGkNCj4gDQo+IA0KPiAtLS0tLU1lbnNhamUgb3JpZ2luYWwtLS0tLQ0KPiBE
ZTogaWV0ZiA8aWV0Zi1ib3VuY2VzQGlldGYub3JnPiBlbiBub21icmUgZGUgT2xlIEphY29ic2Vu
DQo+IDxvbGVqYWNvYnNlbkBtZS5jb20+DQo+IFJlc3BvbmRlciBhOiBPbGUgSmFjb2JzZW4gPG9s
ZWphY29ic2VuQG1lLmNvbT4NCj4gRmVjaGE6IGx1bmVzLCAzMSBkZSBqdWxpbyBkZSAyMDE3LCAy
MzowMQ0KPiBQYXJhOiBUZWQgTGVtb24gPG1lbGxvbkBmdWd1ZS5jb20+DQo+IENDOiA8aWV0ZkBp
ZXRmLm9yZz4NCj4gQXN1bnRvOiBSZTogUkVTRU5ESU5HIC0gSW5jcmVtZW50YWwgRGVwbG95bWVu
dCBvZiBJUHY2LW9ubHkgV2ktRmkgZm9yIElFVEYNCj4gTWVldGluZ3MNCj4gDQo+IA0KPiAgICAg
WW91IHNhaWQ6DQo+ICAgICA+DQo+ICAgICA+IEJyaWFuLCB3aHkgb24gZWFydGggd291bGQgd2Ug
d2FudCB0byBhZHZlcnRpc2UgSVB2NiB0byBJRVRGDQo+ICAgICA+IGF0dGVuZGVlcz8gIFdlIGlu
dmVudGVkIElQdjYuICBJZiB3ZSByZWFsbHkgY2FuJ3QgcnVuIGEgdjYtb25seQ0KPiAgICAgPiBu
ZXR3b3JrIGF0IElFVEYsIHdoYXQgdGhhdCBzYXlzIGlzIHRoYXQgd2UgaGF2ZSBmYWlsZWQgdXR0
ZXJseSBhbmQNCj4gICAgID4gZXhwZW5zaXZlbHkuICBJIGRvIG5vdCBiZWxpZXZlIHRoYXQgdGhp
cyBpcyBjb3JyZWN0OiBJUHY2IHdvcmtzIHZlcnkNCj4gICAgID4gd2VsbC4NCj4gDQo+ICAgICBQ
dXR0aW5nIG9uIG15IG5haXZlIGVuZC11c2VyIGhhdDoNCj4gDQo+ICAgICBUaGF0IG1pZ2h0IGJl
IHRydWUsIGJ1dCBoZXJlIGlzIHRoZSB0aGluZzogIlRoZSBtaXNzaW9uIG9mIHRoZSBJRVRGIGlz
DQo+ICAgICB0byBtYWtlIHRoZSBJTlRFUk5FVCB3b3JrIGJldHRlci4uLiIgKG15IGVtcGhhc2lz
KQ0KPiANCj4gICAgIEZvciBhdCBsZWFzdCBhIGRlY2FkZSBub3csIEkndmUgYmVlbiB0b2xkIHRo
YXQgSSBzaG91bGQgImp1c3QgdXNlDQo+ICAgICBJUHY2IiBhbmQgc29tZSBjb25mZXJlbmNlcyBo
YXZlIGV2ZW4gImZvcmNlZCIgbWUgdG8gZG8gc28uDQo+IA0KPiAgICAgSSBhbHdheXMgcmVzcG9u
ZCB3aXRoIHRoaXMgcXVlc3Rpb246ICJEb2VzIHJ1bm5pbmcgSVB2NiBhbGxvdyBtZSB0bw0KPiAg
ICAgY29ubmVjdCB0byB0aGUgSW50ZXJuZXQ/IiAobWVhbmluZyB0aGUgdjQgSW50ZXJuZXQgZm9y
IHRoZSBtb3N0IHBhcnQpLg0KPiAgICAgVGhlIGFuc3dlciBhbHdheXMgc2VlbXMgdG8gYmU6ICJZ
ZXMsIGJ1dCB5b3UgaGF2ZSB0byBtYW51YWxseQ0KPiAgICAgY29uZmlndXJlIHRoaXMgYW5kLCBv
aCBieSB0aGUgd2F5LCB0aGlzIHdvbid0IHdvcmsgYXQgYWxsIGFuZCB0aGF0IGFwcA0KPiAgICAg
bWlnaHQgbm90IGJlaGF2ZSBhcyBleHBlY3RlZC4iDQo+IA0KPiAgICAgRGVtb25zdHJhdGluZyB0
aGlzIHRvIHBlb3BsZSB3aG8gYXJlIGV4cGVydHMgc2VlbXMgbGlrZSBhIHdhc3RlDQo+ICAgICBv
ZiB0aW1lLg0KPiANCj4gICAgIFNvIGl0IHNvdW5kcyB0byBtZSBsaWtlIHdlIEhBVkUgaW5kZWVk
IGZhaWxlZCB1dHRlcmx5IGFuZCBleHBlbnNpdmVseS4NCj4gICAgIDk5JSBvZiBJbnRlcm5ldCB1
c2VycyBkbyBub3QgaGF2ZSBhbnkgaWRlYSB3aGF0IHZlcnNpb24gb2YgSVAgdGhleSBhcmUNCj4g
ICAgIHJ1bm5pbmcganVzdCBhcyB0aGV5IGhhdmUgbm8gaWRlYSB3aGF0IGEgTUFDIGFkZHJlc3Mg
aXMgb3Igd2h5L2lmIHRoZXkNCj4gICAgIHNob3VsZCBjYXJlLg0KPiANCj4gICAgIEknZCBsb3Zl
IHRvIHNlZSBJUHY2IHN1Y2NlZWQsIGJ1dCBpdCBpcyBhcHBhcmVudGx5IGltcG9zc2libGUgdG8g
ZG8gc28NCj4gICAgIHdpdGhvdXQgdGVhY2hpbmcgZW5kLXVzZXJzIGEgbG90IG9mIHN0dWZmIHRo
ZXkgcmVhbGx5IGhhdmUgbm8gaW50ZXJlc3QNCj4gICAgIGluIG9yIGFiaWxpdHkgdG8gbGVhcm4u
IFdoYXQgYSBzaGFtZS4NCj4gDQo+ICAgICBPbGUNCj4gDQo+IA0KPiANCj4gDQo+IA0KPiAqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqDQo+IElQdjQgaXMgb3Zl
cg0KPiBBcmUgeW91IHJlYWR5IGZvciB0aGUgbmV3IEludGVybmV0ID8NCj4gaHR0cDovL3d3dy5j
b25zdWxpbnRlbC5lcw0KPiBUaGUgSVB2NiBDb21wYW55DQo+IA0KPiBUaGlzIGVsZWN0cm9uaWMg
bWVzc2FnZSBjb250YWlucyBpbmZvcm1hdGlvbiB3aGljaCBtYXkgYmUgcHJpdmlsZWdlZCBvcg0K
PiBjb25maWRlbnRpYWwuIFRoZSBpbmZvcm1hdGlvbiBpcyBpbnRlbmRlZCB0byBiZSBmb3IgdGhl
IHVzZSBvZiB0aGUNCj4gaW5kaXZpZHVhbChzKSBuYW1lZCBhYm92ZS4gSWYgeW91IGFyZSBub3Qg
dGhlIGludGVuZGVkIHJlY2lwaWVudCBiZSBhd2FyZQ0KPiB0aGF0IGFueSBkaXNjbG9zdXJlLCBj
b3B5aW5nLCBkaXN0cmlidXRpb24gb3IgdXNlIG9mIHRoZSBjb250ZW50cyBvZiB0aGlzDQo+IGlu
Zm9ybWF0aW9uLCBpbmNsdWRpbmcgYXR0YWNoZWQgZmlsZXMsIGlzIHByb2hpYml0ZWQuDQo+IA0K
PiANCg0K


From nobody Mon Jul 31 23:52:22 2017
Return-Path: <prvs=13860e1204=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06DBF132804 for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 23:52: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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
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 PlRdrEXzZbKL for <ietf@ietfa.amsl.com>; Mon, 31 Jul 2017 23:52:17 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36BDB12706D for <ietf@ietf.org>; Mon, 31 Jul 2017 23:52:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1501570334; x=1502175134; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=B6ole4xefBGWgHG4Jid5V2skb Zbkjom21N0VobIehis=; b=cQbvcGz5J7H+KH1yET72KR4+EE1IMMt4HPwRE41Ut 1EVomZtcPtf0Yj0hZGxC+EzQrQbNJ43dc2pCB24CwfClgOPNNefT6gFG0EaVVZrv E92OKk0FMwWgw/HtHf5BwPnkf3pH+rb+aDWzyBBV7U4IMXZ9FbhJ18EjPJ7Pj7oN jY=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=PjZ74WJm88VpyGpgHqUUtAugEvaPEfoQKfs4XEFD5hIZJVhdf1gpoiT1i4gu MVsx3ZiTUtsih/bH+1J+9qilAW6hVjD2/q8Pxx20Wo6Qh+HAkXwPyvn2f hr3TAsuGs/fO59S/SgElABqQoqT8Tixe7KQvYkClB+rmJEtzkQKwpQ=;
X-MDAV-Processed: mail.consulintel.es, Tue, 01 Aug 2017 08:52:14 +0200
X-Spam-Processed: mail.consulintel.es, Tue, 01 Aug 2017 08:52:13 +0200
Received: from [10.10.10.133] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005491755.msg for <ietf@ietf.org>; Tue, 01 Aug 2017 08:52:11 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170801:md50005491755::REv7jyUCu18xI2Si:00001moP
X-Return-Path: prvs=13860e1204=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.24.1.170721
Date: Tue, 01 Aug 2017 08:52:10 +0200
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <65D79ACB-372A-4978-9030-FFAB4967A2BD@consulintel.es>
Thread-Topic: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local> <62FE7E9A-9CC0-4DE6-93C6-61A08AC95281@consulintel.es> <787AE7BB302AE849A7480A190F8B93300A0155F5@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B93300A0155F5@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BGJh_RXveb_HVTAPHSo-KuPXErM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Aug 2017 06:52:20 -0000

Hi Med,

In line =E2=80=A6

Saludos,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de <mohamed.boucadair@orange.com=
>
Responder a: <mohamed.boucadair@orange.com>
Fecha: martes, 1 de agosto de 2017, 8:07
Para: "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>, "ietf@ietf=
.org" <ietf@ietf.org>
Asunto: RE: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF =
Meetings

    Hi Jordi,
   =20
    Please see inline.=20
   =20
    Cheers,
    Med
   =20
    > -----Message d'origine-----
    > De : ietf [mailto:ietf-bounces@ietf.org] De la part de JORDI PALET
    > MARTINEZ
    > Envoy=C3=A9 : lundi 31 juillet 2017 23:18
    > =C3=80 : ietf@ietf.org
    > Objet : Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for=
 IETF
    > Meetings
    >=20
    > NAT64 was invented for a specific case (when apps use DNS and the rig=
ht
    > APIs).
   =20
    [Med] This may be misinterpreted as there is a dependency of NAT64 on D=
NS. This is not technically true. This was clarified in https://tools.ietf.=
org/html/rfc6889=20

[Jordi] Right, I was not pretending to be technically perfect, but introduc=
ing when NAT64 fails in our network.
   =20
       This approach is pragmatic in the sense that there is no dependency
       on DNS implementation for the successful NAT handling.  As long as
       there is a function (e.g., DNS64 [RFC6147] or other means) that can
       construct an IPv6-embedded IPv4 address with a pre-configured IPv6
       prefix, an IPv4 address and a suffix (refer to [RFC6052]), NAT64 wil=
l
       work just fine.
   =20
    FWIW, there are even NAT64 deployments that do not even rely on DNS64.=
=20

[Jordi] Agree, we can talk about =E2=80=9CDNS64 function=E2=80=9D instead o=
f DNS64. Again, in our IETF network there is a DNS64, so not the issue here=
.
   =20
    >=20
    > We realized then that app/devices vendors are lazy, or just they are =
out
    > of the market, so we invented 464XLAT, which uses the same concept as
    > NAT64/DNS64, but improves it by using the CLAT, a small daemon code i=
n the
    > OS or the CPE to solve the problems of the literal addresses and non-=
APIs
    > apps/devices.
    >=20
    > We don=E2=80=99t need to tell the customers to disable IPv4 in their =
LANs, we need
    > to make sure that we deploy CPEs that support CLAT.
   =20
    [Med] Is there any CPE-based 464xlat deployment out there?=20
=20
[Jordi] I=E2=80=99ve identified 4 vendors up to now, with different product=
s each. I=E2=80=99m sure there are more. I also know that other vendors did=
 the development for specific customers and I=E2=80=99m also aware of other=
 customers that asked for it. We have also the open source implementations,=
 such as OpenWRT, supporting thousands of devices. Precisely this is my poi=
nt. As IETF, our work is not just inventing transitions mechanism, but also=
 making sure that if we state a set of requirements for CPEs, we include th=
e support for those transition mechanisms.
  =20
     This way, users don=E2=80=99t
    > need to throw away old devices or apps, neither learn anything about =
IPv4
    > or IPv6, and everybody is happy.
    >=20
    > We are trying to solve a problem with NAT64 which we knew since it wa=
s
    > invented that it can=E2=80=99t be solved. We don=E2=80=99t have the t=
ime (unless some
    > magic is discovered) to now tell every ISP that is deploying IPv6 and
    > NAT64, to instead of NAT64 have something different.
   =20
    [Med] These operators (with CPEs) are already doing something *differen=
t*: DS-Lite and the like. NAT64 is widely deployed in cellular networks (ho=
st-based model), which is really straightforward.  =20
=20
[Jordi] I agree, but if you have a network with cellular and wireline acces=
s, you may want to have a single transition mechanisms instead of two. If w=
e don=E2=80=99t want to use NAT64 in wireline, then why we are trying to pu=
sh it as the default SSID in our IETF network? It is a matter of preference=
 of one or another transition mechanisms. All them have good and bad things=
. I see much simpler the combination of NAT64+CLAT than DS-Lite or MAP, in =
addition to the ONLY support in cellular networks is precisely NAT64/464XLA=
T, which means is the MOST extended transition mechanism by millions (billi=
ons?) of users. It makes a lot of sense to me to go in all the infrastructu=
res to the one that has more deployment already.
  =20
     The solution is
    > there, if CPE vendors implement it, and we are talking about an avail=
able
    > open source code (several implementations) that take a few bytes.
    >=20
    > We are already doing this effort in v6ops, I started trying to tell t=
he
    > RFC7084 about the need to update it, but didn=E2=80=99t succeeded. It=
 seems that
    > now we may want to have instead of a CPE requirements including this,=
 an
    > additional document to be a must for CPE vendors to support it, in ca=
se
    > the CPE expects =E2=80=9CIPv4 old devices and apps=E2=80=9D in the LA=
Ns (which is real
    > world life, and will be for 3-5 years).
   =20
    [Med] I'm afraid we don't need it. The IETF already specified tools to =
address that case (DS-Lite, MAP-E).

[Jordi] I guess no need to repeat myself =E2=80=A6

   =20
    >=20
    > Regards,
    > Jordi
    >=20
    >=20
    > -----Mensaje original-----
    > De: ietf <ietf-bounces@ietf.org> en nombre de Ole Jacobsen
    > <olejacobsen@me.com>
    > Responder a: Ole Jacobsen <olejacobsen@me.com>
    > Fecha: lunes, 31 de julio de 2017, 23:01
    > Para: Ted Lemon <mellon@fugue.com>
    > CC: <ietf@ietf.org>
    > Asunto: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for=
 IETF
    > Meetings
    >=20
    >=20
    >     You said:
    >     >
    >     > Brian, why on earth would we want to advertise IPv6 to IETF
    >     > attendees?  We invented IPv6.  If we really can't run a v6-only
    >     > network at IETF, what that says is that we have failed utterly =
and
    >     > expensively.  I do not believe that this is correct: IPv6 works=
 very
    >     > well.
    >=20
    >     Putting on my naive end-user hat:
    >=20
    >     That might be true, but here is the thing: "The mission of the IE=
TF is
    >     to make the INTERNET work better..." (my emphasis)
    >=20
    >     For at least a decade now, I've been told that I should "just use
    >     IPv6" and some conferences have even "forced" me to do so.
    >=20
    >     I always respond with this question: "Does running IPv6 allow me =
to
    >     connect to the Internet?" (meaning the v4 Internet for the most p=
art).
    >     The answer always seems to be: "Yes, but you have to manually
    >     configure this and, oh by the way, this won't work at all and tha=
t app
    >     might not behave as expected."
    >=20
    >     Demonstrating this to people who are experts seems like a waste
    >     of time.
    >=20
    >     So it sounds to me like we HAVE indeed failed utterly and expensi=
vely.
    >     99% of Internet users do not have any idea what version of IP the=
y are
    >     running just as they have no idea what a MAC address is or why/if=
 they
    >     should care.
    >=20
    >     I'd love to see IPv6 succeed, but it is apparently impossible to =
do so
    >     without teaching end-users a lot of stuff they really have no int=
erest
    >     in or ability to learn. What a shame.
    >=20
    >     Ole
    >=20
    >=20
    >=20
    >=20
    >=20
    > **********************************************
    > IPv4 is over
    > Are you ready for the new Internet ?
    > http://www.consulintel.es
    > The IPv6 Company
    >=20
    > This electronic message contains information which may be privileged =
or
    > confidential. The information is intended to be for the use of the
    > individual(s) named above. If you are not the intended recipient be a=
ware
    > that any disclosure, copying, distribution or use of the contents of =
this
    > information, including attached files, is prohibited.
    >=20
    >=20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.



